6 Mapping of identifiers

6.0 Introduction

The BBF TR-069 [4] specification defines three (3) types of devices, known as CPEs, that are capable of being managed from the perspective of the BBF TR-069 agent:

  • CPE that hosts the BBF TR-069 agent: Section A.3.3.1 Inform ofTable 39 of BBF TR-069 [4] defines the fields required fields for a CPE to be identified. These fields include the OUI and Serial Number of the CPE assigned by the CPE manufacturer. Optionally the manufacturer may assign a Product Class to the CPE. The format of the identifier is as follows: OUI-[PC-]SN.
  • Virtual Device: This type of device is addressed as a CPE. The Virtual Device has its own OUI-[PC-]SN as represented by the CPE Proxier. The CPE Proxier emulates a CWMP agent for each Virtual Device.
  • Embedded Device: This type of device is addressed as one or more objects within the data model of the CPE that hosts the BBF TR-069 agent.

6.1 Mapping of Device identifiers to the Node Resource

Node Resources are identified for each instance of an ADN, ASN and MN node and are identified using the M2M Node Identifier (M2M-Node-ID) defined in the oneM2M Functional Architecture [1].

CPE Device identifiers shall map to the nodeID attribute of the resource. The CPE Device identifiers are obtained from the contents of the following attributes: resource. The CPE Device identifiers are obtained from the contents of the following attributes:

  • Device.DeviceInfo.ManufacturerOUI
  • Device.DeviceInfo.ProductClass
  • Device.DeviceInfo.SerialNumber

Virtual Device identifiers shall map to the nodeID attribute of the resource. The Virtual Device identifiers are obtained from the CPE Proxier using the contents of the attributes: resource. The Virtual Device identifiers are obtained from the CPE Proxier using the contents of the attributes:

  • Device.ManagementServer.VirtualDevice.{i}.ManufacturerOUI
  • Device.ManagementServer.VirtualDevice.{i}.ProductClass
  • Device.ManagementServer.VirtualDevice.{i}.SerialNumber

Embedded Device identifiers shall map to the nodeID attribute of the resource. The Embedded Device identifiers are obtained using the containing CPE Device or Virtual Device identifiers along with the contents of the attributes of the:

  • Device.ManagementServer.EmbeddedDevice.{i}.ControllerID
  • Device.ManagementServer.EmbeddedDevice.{i}.ProxiedDeviceID

6.2 Identifier of an object instance

The BBF TR-069 [4] specification permits objects to have multiple object instances where each object instance is contained within the objectPath attribute of the Resource within the context of the Resource's objectId as defined in clause 7.1.

In order to allow the AE or CSE that originated the request that manipulates a Resource to easily align the M2M Service Layer with the Resource's external technology identifier, the value of the object instance "{i}" should be a part of the identifier of the Resource in the M2M Service Layer where possible. For example if the [areaNetwork] resource has an object instance identifier of "Device.X_oneM2M_org_CSE.1.M2MareaNetworkDevice.[foo]" then the M2M Service Layer Resource should be identified using the object instance of the underlying technology (e.g. "/foo" for the Resource areaNetwork).