Location: Home > TIA > Management Enablement (BBF) (oneM2M TS-0006-v1.0.1)

Management Enablement (BBF) (oneM2M TS-0006-v1.0.1)

TIA 02-23
Management Enablement (BBF) (oneM2M TS-0006-v1.0.1)

1. Scope
The present document describes the protocol mappings between the management Resources for oneM2M and the BBF TR-181i2 Data Model [6] .
2 References
2.1 Normative references
The following referenced documents are necessary, partially or totally, for the application of the present document.
Their use in the context of this TS is specified by the normative statements that are referring back to this clause.
[1] oneM2M TS-0001:“Functional Architecture”.
[2 oneM2M TS-0004:“Service Layer Core Protocol Specification”.
[3] oneM2M TS-001 1:“Definitions and Acronyms”.
[4] BBF:“TR-069 CPE WAN Management Protocol” Issue: 1 Amendment 5, November 2013.
[5] BBF:“TR- 106 Data Model Template for TR -069 -Enabled Devices”, Issue 1, Amendment 7,September 2013.
[6] BBF:“TR-181 Device Data Model for TR-069, Issue 2 Amendment 8″, September 2014.
[7] BBF:“TR-131 ACS Northbound Interface Requirements, Issue:1”, November 2009.
2.2 Informative references
[i.1] oneM2M Drafting Rules
(http://member.onem2m.org/Static pages/Others/Rules_ Pages/oneM2M-Drafting-Rules V1 0.doc)
3 Definitions, symbols, abbreviations and acronyms
3.1 Definitions
For the purposes of the present document, the terms and definitions given in TS-0011 [3] apply.
CPE Proxier
A CPE that is capable of proxying the communication between an ACS and a Proxied Device as defined in TR-069 [4].
IN-CSE CSE which resides in the Infrastructure Node
LAN Local Area Network
Middle Node
OUI Organizationally Unique Identifier
PC Product Class
RPC Remote Procedure Call
Serial Number
URI Uniform Resource Identifier
URL Uniform Resource Locator
USB Universal Serial Bus
UUID Universal Unique Identifier
XML Extensible Markup Language
3.4 Acronyms
For the purposes of the present document, the acronyms given in TR-0004 [3] apply.
4 Conventions
The key words“Shall”;, “Shall not”,“May”, “Need not”,“Should”, “Should not” in this document are to be interpreted as described in the oneM2M Drafting Rules [i.1]
5 Mapping of basic data types
TR- 106 [5] specifies the object structure supported by TR -069 enabled devices and specifies the structural requirements for the data hierarchy. This clause includes the mapping attribute data types to TR-181 [6] parameters which follows the onventions of section 3 of TR- 106 [5] and data types described in Table 4 of TR- 106 [5].