Data plane Control Management
7.6.3 Home Networking Technologies
Home Network Access Network 1
Figure 11 Possible HN connectivity 2
3
7.6.3 Home Networking Technologies 4
The ideal LAN technology to be incorporated into the HGI home gateway would: 5
• support the distribution of multi-channel video throughout the home (WAN-LAN and 6
LAN-LAN) with the appropriate aggregate bitrate (~20-30 Mbit/s net payload). Where 7
the PHY rate of a technology is time or location variant, then this aggregate bitrate 8
must be able to be supported under near worst-case conditions. 9
• not require any significant installation of new cabling2. 10
• conform to mandatory EMC emissions standards and not interfere with access 11
network technologies such as ADSL and VDSL, or other home network 12
technologies/devices. 13
Unfortunately none of the existing HN technologies meets all these requirements, so a 14
combination solution is therefore required. The HN technologies chosen by the HGI are: 15
• IEEE802.11a/b/g and IEEE 802.11n Draft 2. This will provide connectivity to laptops, 16
PCs and wireless devices such as PDAs where the key requirement is in-house 17
mobility. It will not necessarily provide whole house coverage, or QoS such that 18
video streaming applications can be supported. 19
• 100BaseT Ethernet. This will provide high rate, predictable performance, with video 20
streaming support, but only where it is acceptable to install the required new cabling 21
i.e. within the room containing the HG, with a small amount of additional inter-room 22
wiring in some cases. 23
• USB 1.1/2.0 slave and USB 2.0 host. This will provide PC or peripheral connection 24
2
The amount of new cabling that can be tolerated might differ from country to country due to different existing home infrastructures
Home Gateway Technical Requirements: Residential Profile
Page 37 of 125 © Home Gateway Initiative – 2008 – All rights reserved In order to support the full range of services and connectivity, a combination of the above 1
solutions would typically be incorporated in the HG along with a basic Ethernet switch. Other 2
technologies (e.g. PLT or HPNA) and further infrastructure devices may be required, but these will 3
be external to the HG. This is taken into account to some degree in the QoS architecture. 4
7.7
Management Architecture
5
The HGI approach is based on DSL Forum TR-069 Amendment 1 [1] (hereinafter “TR- 6
069”). Various amendments, additions and the selection of some options from the DSL Forum 7
specification are detailed in this document. 8
TR-069 Amendment 1 defines the CPE Remote Management Protocol (CWMP) and the 9
Auto Configuration Server (ACS) to manage the HG and TR-069 enabled devices located in the 10
HN. Annex F allows an ACS to determine the identity of the HG through which a given ED is 11
connected, and is an updated version of TR-111 part 1. Annex G allows an ACS to initiate a TR- 12
069 session with an ED that is operating behind a NAT gateway, and is an updated version of TR- 13
111 part 2. 14
The others TRs relate to the data model: 15
• TR-106 Amendment 1 [21]: defines baseline data model requirements for all TR-069 16
HGs and EDs. 17
• TR-098 Amendment 1 [47]: defines v1.2 of the Internet Gateway Device HG data 18
model. 19
• TR-104 [97]: defines v1.0 of the VoIP ED data model. 20
The HG is under the control of a single RMS at any one time. 21
22
The high level management architecture and the entities involved are shown in Figure 12. 23 Home Gateway
RMS
OSS/BSS
Service provider
Service provider
End-users
ED Local Mngt Interface Home Network TR69 config Device discovery ACS Access Network TR-069 Config Home GatewayRMS
OSS/BSS
Service provider
Service provider
End-users
ED Local Mngt Interface Home Network TR69 config Device discovery ACS Access Network TR-069 Config 24Figure 12 Management entities interactions 25
Home Gateway Technical Requirements: Residential Profile
Page 38 of 125 © Home Gateway Initiative – 2008 – All rights reserved The Auto-Configuration Server (ACS) is the management application which implements 1
device configuration, software updates, device diagnostics, remote operations and reboot requests 2
as defined in TR-069 Amendment 1. This means that devices (HGs and TR-069 managed EDs) are 3
managed via the CWMP protocol from the ACS. 4
The Remote Management System (RMS) is the management entity which includes the Auto- 5
Configuration Server capabilities but provides additional management functionalities. The RMS 6
includes resource and device inventory, event notification and alarm management, diagnostics and 7
troubleshooting. 8
The RMS has a northbound interface to the OSS/BSS. With this interface, the OSS/BSS of 9
the operator is able to establish the policies that the RMS implements (by applying the required 10
configurations to the HG). The OSS/BSS allows for multi-service provider support as detailed in 11
section 7.7.6. 12
The HG and the end devices are able to interact autonomously to some degree, performing 13
operations such as device discovery. 14
Finally, the user may be allowed to have an interface to tune the configuration of the HG to a 15
small degree. Such an interface may have one part based in the HG itself and the other one 16
located in the Operator’s portal OSS/BSS. 17
The management architecture of the Home Gateway is shown in Figure 13 and can be 18
broken down into these main functions: 19 • Device Management 20 • QoS Management 21 • Security Management 22 • Configuration Management 23
• Firmware Upgrade Management 24
• Performance Monitoring 25
• Diagnostics and Troubleshooting (alarms/notifications and log management) 26
Two other components are identified: 27
• CWMP Client 28
• Local Management Application 29
For both remote and local HG management there is a common Management Abstraction 30
Layer and a Data Model Management module to allow uniform DB access. 31
The main HG management interfaces are: 32
• IHG-LM for local management, is an HTML interface
33
• IHG-ACS for remote management, is a CWMP interface
34
The ED interfaces are: 35
• IED-ACS for remote management of bridged ED, is a CWMP interface
36
• IED-HG is a communication ED/HG interface; it can be a DHCP or UPnP interface
37 38
Home Gateway Technical Requirements: Residential Profile
Page 39 of 125 © Home Gateway Initiative – 2008 – All rights reserved Remote Management System Local Mgmt App TR-069 Client Mgmt Abstraction Layer Device Mgmt QoS Mgmt Security Mgmt Configuration Mgmt Fw Upgrade Mgmt
Diagnostics & Troubleshooting Performance Monitoring HG & ED DB Home Gateway Local Mgmt Auto Configuration Server Bridged Managed Device Un- Managed Device IHG-LM IED-ACS TR-069 Client IED-HG Routed Managed Device TR-069 Client IHG-ACS Device Discovery 1
Figure 13 Management Architecture 2
7.7.1 Device Management