Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Instanciating TR135 "Device.Services.STBService.{i}.Components.FrontEnd.{i}." #6

Open
GoogleCodeExporter opened this issue Mar 23, 2015 · 0 comments

Comments

@GoogleCodeExporter
Copy link

Hi,
  I need a help on making a decision on how to implement a basic TR135 data model as I'm facing problem with FrontEnds.
As specified in TR135 
(http://www.broadband-forum.org/cwmp/tr-135-1-1-0.html#D.STBService.{i}.Componen
ts.FrontEnd.{i}.), the data model could have many FrontEnd like:
Device.Services.STBService.{i}.Components.FrontEnd.{i}.DVBT.Modulation.xxxx
Device.Services.STBService.{i}.Components.FrontEnd.{i}.IP.Inbound.{i}.xxxx

I've tried a data model where I've addedthe 2 frontends (IP and DVBT) and 
created 2 FrontEnd instances using evcpe_attr_add_obj() applied on the 
multi-object FrontEnd but what I've got is wrong:

Expected:
---------
Device.Services.STBService.1.Components.FrontEnd.1.DVBT.Modulation.xxxx
Device.Services.STBService.1.Components.FrontEnd.2.IP.Inbound.1.xxxx

(note here the index of each FrontEnd)

Results:
--------
Device.Services.STBService.1.Components.FrontEnd.1.DVBT.Modulation.xxxx
Device.Services.STBService.1.Components.FrontEnd.1.IP.Inbound.1.xxxx
Device.Services.STBService.1.Components.FrontEnd.2.DVBT.Modulation.xxxx
Device.Services.STBService.1.Components.FrontEnd.2.IP.Inbound.1.xxxx

This is wrong as the schema has been duplicated across the 2 objects.

My data model declaration was:
------------------------------
Device: object
Services: object
STBService: multi-object
Components: object
FrontEnd:multi-object
DVBT: object
Modulation: object
xxxx: parameter

IP: object
Inbound: multi-object

My temporary solution is
------------------------
Instead of using multi-objects, use a simple object. However this is ugly in my 
humble opinion

Device: object
Services: object
STBService: multi-object
Components: object
FrontEnd:object
1: object       <<<<< Note here the instance number as an object
DVBT: object
Modulation: object
xxxx: parameter

2: object       <<<<< Note here the instance number as an object
IP: object
Inbound: multi-object

Is there an ideal solution to deal a such complex data model ?

Thank you

Original issue reported on code.google.com by [email protected] on 15 Aug 2011 at 7:23

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant