End device management - Data plane Control Management

Data plane Control Management

8.6.5 End device management

8.6.5.1 Device Identification 5

N°

Requirement

R169. The HG MUST be able to discover and uniquely identify the managed devices connected

to the home network.

R170. The HG SHOULD be able to discover and uniquely identify the unmanaged devices

connected to the home network.

R171. The HG SHOULD be able to discover and uniquely identify the unmanageable devices

connected to the home network.

R172. A database of devices (device repository) MUST be held in the HG. This database

contains the results of the device discovery and capabilities detection mechanisms.

Home Gateway Technical Requirements: Residential Profile

N°

Requirement

R173.

Each record of the database defined in R172 MUST contain fields that can contain the following information:

• LAN side Private IP address and management port number.

• WAN side Public IP address and management port number (NA(P)T binding) • Hardware (MAC) address

• ManufacturerOUI, which is the organizationally unique identifier of the Device manufacturer as provided to the Gateway by the Device as defined by [46]. • SerialNumber

• UUID (Universally Unique IDentity), as defined by RFC4122 [7] and given by the UDN in the UPnP Device Description.

• ProductClass • Device Type • Friendly name • Manufacturer • Model name

• Type of physical interface through which the ED is connected to the HG. • ‘Active flag’ (device connectivity status)

• Management protocol by which the device is manageable

R174.

The database of R172 MUST enable the RMS to distinguish the devices in the home network uniquely. This is required not only for root devices, but also for embedded devices. This may be achieved, for instance, by using UUID, and if the UUID is not available, using {ManufacturerOUI, SerialNumber},{ManufacturerOUI, ProductClass, SerialNumber} or MAC address.

R175.

This list of TR-069 manageable end devices as presented by the database of R172 MUST be the same as given by the

InternetGatewayDevice.ManagementServer.ManageableDevice.{i} object."

R176. The HG MUST update the database described in R172 with the IP and hardware

addresses provided by the DHCP clients on the network.

R177. For every ED (managed and unmanaged), the HG MUST determine the IP address and

hardware address from its ARP cache [17], if not obtained via DHCP.

R178. The HG MUST read additional ID information provided by managed EDs of type D (see

Table 1) and update its database accordingly.

R179.

The HG SHOULD also read ID information provided by the DHCP options 60 (vendor class identifier) [18], 61 (client identifier) [18], 77 (User Class) [23], 124 (V-I vendor class) [19] or 125 for other managed and unmanaged devices, and update its database accordingly.

Home Gateway Technical Requirements: Residential Profile

N°

Requirement

R180.

The HG MUST contain an SSDP Control Point stack as defined in [16] for the discovery of the ID information of managed EDs of type U and CU (see Table 1) and unmanaged UPnP devices.

R181.

The HG MUST be able to interpret all standardized UPnP Device Descriptions (XML schemas), and extract the mandatory device ID information from it, such as DeviceType and Friendly Name.

R182. When the ID-information is retrieved, the HG MUST update its database accordingly. S

R183. The HG MUST discover embedded UPnP devices in UPnP root devices. S

R184.

A number of values in the database might be provided by the clients by means of DHCP as well as UPnP (Friendly Name, MAC and OUI). In the case of inconsistency, the HG MUST choose the DHCP values.

R185.

For devices of type S, The HG MUST be able to extract the SIP URI or SIPS URI from the SIP Register Message and register the discovered SIP or SIPS URIs in the discovered devices data base.

R186. The HG MUST discover the managed devices placed behind an access point or a bridge

in the same way as those directly connected to the HG.

R187. The HG MUST determine if the newly discovered ED supports DHCP, and/or UPnP,

and/or CWMP, and if the ED is following the HGI recommendations (see section 7.7.1). S

R188.

EDs that follow the TR-069 specs can be discovered as such, if they also use the mechanisms as defined in Annex F of TR-069 Amendment 1. Therefore, the HG MUST follow the TR-069 Amendment 1 Annex F specification.

8.6.5.2 Activity discovery and Database management 1

N°

Requirement

R189. The database defined in R172 MUST be accessible by the ACS by means of CWMP. S

R190. The entries in the device database defined in R172 MUST be kept even if the device is

disconnected from the HN.

R191. The database defined in R172 MUST be able to store the data from at least 32 devices. S

R192. If more devices are discovered than can be stored in the database defined in R172 the _{oldest inactive entry MUST be removed from the database.} S

R193. The HG MUST support the ‘byebye’ message in the UPnP discovery mechanism and

update the ‘active flag’ in the database defined in R172.

R194. The default DHCP lease time from the HG MUST be 10000 seconds. S

Home Gateway Technical Requirements: Residential Profile

N°

Requirement

R196.

If a device is present in the database defined in R172, but has not been active (i.e. discovered by Gratuitous ARP or DHCP Inform) within a time equal to the DHCP lease time, the “active” flag MUST automatically be set to “False”.

R197. The “active” flag MUST be automatically set to “False” at the end of DHCP lease time

(DHCP option 51).

S 1

8.6.6 Local HG management user interface

In document Home Gateway Technical Requirements: Residential Profile (Page 74-77)