|Abstract: |Specifies the usage of the BBF TR-069 protocol and the corresponding message flows including normal cases as well as error cases to fulfil the oneM2M management requirements.<br/>Protocol mapping between the oneM2M service layer and BBF TR-069 protocol. The Mca reference point, ms interface and la interface are possibly involved in this protocol mapping.<br/>Mapping between the oneM2M management related resources and the TR-069 protocol RPCs and TR-181i2 data model.<br/>Specification of new TR-181 data model elements to fulfil oneM2M specific management requirements that cannot be currently translated. |
|Abstract: |Specifies the usage of the BBF TR-069 protocol and the corresponding message flows including normal cases as well as error cases to fulfil the oneM2M management requirements.<br/>Protocol mapping between the oneM2M service layer and BBF TR-069 protocol. The Mca reference point, ms interface and la interface are possibly involved in this protocol mapping.<br/>Mapping between the oneM2M management related resources and the TR-069 protocol RPCs and TR-181i2 data model.<br/>Specification of new TR-181 data model elements to fulfil oneM2M specific management requirements that cannot be currently translated. |
|Template Version: January 2017 (Do not modify) |Template Version: January 2017 (Do not modify) |
|Template Version: January 2017 (Do not modify) |Template Version: January 2017 (Do not modify) |
...
@@ -1621,17 +1621,19 @@ TR-181 <a href="#_ref_6">[6]</a> provides a list of management objects that have
...
@@ -1621,17 +1621,19 @@ TR-181 <a href="#_ref_6">[6]</a> provides a list of management objects that have