Home Gateway Technical Requirements: Residential Profile

Transcription

1 0 0 Home Gateway Technical Requirements: Residential Profile Version.0 /0/00 Home Gateway Initiative 00 All Rights Reserved

2 0 0 PAGE LEFT INTENTIONALLY BLANK Page of

3 Table of Contents Table of Contents... Important notice, IPR statement, disclaimer and copyright... Acronyms... Definitions... Introduction and scope of the Home Gateway Initiative (HGI).... Cooperation with other bodies and initiatives... cope and Purpose of this document.... tructure of the pecification.... Definition of profiles and terms... ervices Overview and Use Case ummary.... Overview of Use Cases..... Broadband Connection..... Communication..... Fixed-mobile and ervice Convergence Mobile integration scenarios in the home Guest and Hotspot Access Using IM services from non-im enabled devices: IM proxy..... Home Office..... Entertainment & Information Audio content Gaming IPTV (real-time delivery) Extended IPTV (request and store IPTV) Media server..... Remote access..... Home Management & ecurity Home surveillance Home ecurity Home Automation...0. Home Gateway General Requirements ummary Ease of use and simplicity ecurity Quality of service: unmanaged services / managed services Remotely managed gateway / home network Performance Monitoring and Diagnostics.... ervice Provider Role models..... Role model definitions..... Role model assumptions... HGI Reference Architecture.... End to End Network Architecture..... HG upply Model..... Integrated NT and HG..... WAN interfaces..... LAN interfaces..... Connectivity..... Qo..... Management..... Encapsulation and session support..... IP Addressing ecurity..... Fixed-Mobile and ervice Convergence... Page of

4 Multicast support..... Remote Device Access..... Parental Control..... Messaging.... Moving towards a more IM like architecture..... IM-based remote access.... Parental control.... Guest and Hotspot Access.... Home Gateway Functional Overview..... Home Gateway Functional Blocks..... Interworking with IM and an NGN core...0. Home Networking Technologies and Architecture..... Home Network Architecture..... Home Network Connectivity..... Home Networking Technologies.... Management Architecture..... Device Management..... ecurity Management..... oftware Management and Upgrade..... Performance Monitoring and Diagnostics & Troubleshooting..... Local Management Application..... Multi ervice Provider upport..... Home Gateway Provisioning.... Quality of ervice Architecture..... Congestion Points..... Bridges and switches in the Home Network..... Basic principle of operation..... DCP and VLAN Usage..... Traffic Classification..... Upstream Classifiers..... Downstream Classifiers..... Transit classifiers..... Qo Mapping Upstream Queue structure..... Downstream and Transit Queue tructure Class Based Qo, essions and Policy DLNA coexistence Fragmentation and Classification..... Classification and NAT for WAN Ingress.... ecurity Architecture..... Firewall protection..... VPN Capabilities..... Encryption algorithms..... Code authentication / ignature..... Local Configuration ecured Access..... Remote access... Home Gateway Requirements.... WAN ide Interfaces..... Type - ATM over DL Interface (*)..... Type - Ethernet over DL Interface (*)..... Type - Ethernet WAN Interface (*)..... WAN Interface Combinations (+)..... PTN (FXO) Interface (+).... LAN side interfaces... Page of

5 Wired..... Wireless..... Telephony interfaces.... WAN and LAN Networking Requirements WAN Connectivity and Addressing Routed Model and Local Area Networking upport NAT/NAPT IP Addressing schemes LAN-side DHCP requirements..... upport of Hybrid Model and Extensions..... ession Initiation and upport.... LANside Interoperability.... Guest Access and Wi-Fi Hotspot (+).... Management..... Northbound Interfaces..... General HG configuration and management..... Definition of the data model supported..... Diagnostics, notifications and alarms Notifications and logging Mechanisms Notification cases tatistics and Diagnostics Mechanisms Defined diagnostics and statistics..... End device management Device Identification Activity discovery and Database management..... Local HG management user interface General Design guidelines Operator Portal User Interface link Contents and functionality..... Firmware management and updates General Firmware upgrades Configuration Application Layer Gateway Management..... Multi-service provider management.... Remote End-Device Access..... Authentication and Authorization Web Based Approach (LM Remote UI) IM Approach (+, to be applied in conjunction with ection.. only).. Remote Access Configuration.... ervice upport..... ALGs..... Local IP devices registration..... IP non IM Communication ervices upport (+)..... IM communication services support (+) IM Protocol tack IM telephony user agent IM Interworking Local registration and local services support upport of call forking and call transfer inside the HN Messaging... Page of

6 Multimedia ervices upport.... ecurity..... Parental Control (+)..... Firewalling Firewall management....0 Quality of ervice Classification of traffic Requirements for Classification of packets received upon the WAN ingress Requirements for Classification of LAN-LAN traffic Requirements for Multi-field Classification packets received on the LAN ingress ports Requirements for Classification of packets received on the LAN ingress using information determined by DHCP Requirements for Classification of bridged packets received on the LAN ingress ports Requirements for Classification of internally generated packets LAN-side VLAN support Classification Rule ets Overview Requirements for Classification Rule ets Requirements for equencing Among Classification Rule ets Overload Protection Mechanism Qo Mappings Integrated Access Devices Dropping/Congestion Management Class Queue structure and cheduling Queuing into the WAN Egress port Queuing into the LAN Egress ports Example of Queuing Configuration Requirements on Queue tatistics ervice class monitoring on a per queue basis Requirements for Admission Control (+) BBUA requirements for CAC using IP signalling LAN Interface Capacity Monitoring Qo Requirement Mapping to TR Non-Integrated Device Requirements LAN Infrastructure Devices Non-integrated Ethernet Infrastructure Devices Informative notes on et Top Boxes and VoIP Client Devices DLNA Coexistence Guidelines.... Basic system features... References...0 Page of

7 0 0 0 Important notice, IPR statement, disclaimer and copyright The Home Gateway Initiative (HGI) is a non-profit making organization created to define guidelines and specifications for broadband Home Gateways. This document is the output of the Working Groups of the HGI and its members as of the date of release. Readers of this document must be aware that it can be revised, edited or have its status changed according to the HGI working procedures. The HGI makes no representation or warranty on the contents, completeness and accuracy of this publication. This document, though formally approved by the HGI member companies, is not binding in any part on the HGI members. IPRs essential or potentially essential to the present document may have been declared in conformance to the HGI IPR Policy and tatutes available at the HGI website Any parts of this document may be freely reproduced (for example in RFPs and ITTs) by HGI and non-hgi members subject only to the following: HGI Requirement numbers not being changed an acknowledgement to the HGI being given in the resulting document. Trademarks and copyrights mentioned in this document are the property of their respective owners. The HGI membership list as of the date of the formal review of this document is: Wire, Inc., Atheros, Alcatel-Lucent, AVM, Belgacom, BeWAN, BT, Conexant, Deutsche Telekom, D, Echelon EMEA, ECI, Emotum, Ericsson AB, Fastweb pa, France Telecom, Fraunhofer EK, Freescale emiconductor, Gigle emiconductor, Huawei, IBM, InAccess Networks, Infineon Technologies AG, Intel, Intellon, Jungo oftware Technologies, KDDI, KPN, LEA - Laboratoire Europeen ADL, Legerity Inc., LG-Nortel Co Ltd, Linksys/Cisco, Marvell emiconductors, Microsoft, Mimos, Motive, Inc, Motorola, Netgear, Netopia, NTT, Philips, Pirelli Broadband olutions, PMC ierra, Portugal Telecom, agem, iconnect, iemens, phairon Access ystems, pidcom, upportsoft, wisscom AG, Telcordia, Telecom Italia, Telefonica, Telekom lovenije, Telekomunikacja Polska, Telenor, Teliaonera, Telkom ZA, Telsey pa, Telstra, Telus Communications Inc., Texas Instruments, Thomson, Tilgin AB, TNO, UEA Technologies Limited, Ubicom Inc., Vtech, ZTE, ZyXEL. Page of

8 Acronyms AAL ACL AC ADL ALG ALL AN AP ATA ATF ATM BBUA BG BRA BP B CAC CBR CE CFB CFNR CFU CLF CLIP CNGCF Co CPE CWMP DA DECT DHCP DMZ DN D DCP DL ATM Adaptation Layer Access Control List Auto-Configuration erver Asymmetric Digital ubscriber Line Application Layer Gateway Application Layer Logic Access Network Access Point Analogue Terminal Adapter Architecture Task Force of HGI Asynchronous Transfer Mode Back to Back User Agent Business Group of HGI Broadband Remote Access erver Broadband ervice Provider Business upport ystem Call Admission Control/Connection Admission Control Constant Bit Rate Consumer Electronics Call Forwarding on mobile customer Busy Call Forwarding on No Reply Call Forwarding Unconditional Connectivity session Location and repository Function Calling Line Identification Presentation Customer Network Gateway Configuration Function Class of ervice Customer Premises Equipment CPE WAN Management Protocol Destination Address Digital Enhanced Cordless Telecommunications Dynamic Host Configuration Protocol De-Militarised Zone Domain Name ystem Downstream Differentiated ervices Code Point Digital ubscriber Line Page of

9 0 0 0 DVB Digital Video Broadcasting EAP Extensible Authentication Protocol ED End Device EDR (Bluetooth) Extended Data Rate EU End User EUD End User Device FTTB Fibre To The Building/Business FTTCab Fibre To The Cabinet FTTH Fibre to the Home FXO Foreign exchange Office FX Foreign exchange ubscriber HG Home Gateway HGI Home Gateway Initiative HGW Home Gateway and Home Network Architecture Working Group of HGI HN Home Network HTTP HyperText Transfer Protocol IEEE Institute of Electrical and Electronics Engineers IGMP Internet Group Management Protocol ILMI Interim Local Management Interface IMPI IP Multimedia Private Identity IMPU IP Multimedia Public Identity IM IP Multimedia ubsystem IP Internet Protocol IPv Internet Protocol version IIM IP Multimedia ervices Identity Module IP Internet ervice Provider ITU-T International Telecommunication Union Telecommunication standardisation sector LTP Layer Tunnelling Protocol LAN Local Area Network LF Location Function LM Remote UI Local Management Remote User Interface MAC Media Access Control MPEG Moving Picture Expert Group NAPT Network Address and Port Translation NAT Network Address Translation NGN Next Generation Network NTP Network Time Protocol Page of

10 0 0 0 OAM O PCF PCP P-CCF PIN PLT POT PPP PPPoA PPPoE PPTP PTN PVC PVR Qo RCE RM RODM A DO IP NMP OHO P ID TB UI UPnP VA VCI VDL VLAN VoD VoIP VP VPI VPN Operations, Administration & Maintenance Operations upport ystem Parental Control Function Parental Control Profile Proxy-Call ession Control Function Personal Identification Number Power Line Transmission Plain Old Telephone ervice Point-to-Point Protocol PPP over ATM PPP over Ethernet Point to Point Tunnelling Protocol Public witched Telephone Network Permanent Virtual Connection Personal Video Recorder Quality of ervice Remotely Configurable Equipment Remote Management ystem Remote Operations and Device Management group (of HGI) ource Address tandards Development Organization ession Initiation Protocol imple Network Management Protocol mall Office Home Office ervice Provider ervice et Identifier et Top Box User Interface Universal Plug&Play Value Added ervice (equivalent to Managed ervice) Virtual Channel Identifier Very high speed Digital ubscriber Line Virtual Local Area Network Video on Demand Voice over IP Virtual Path Virtual Path Identifier Virtual Private Network Page 0 of

11 WAN WEP WPA WRR XCAP Wide Area Network Wired Equivalent Privacy Wireless Protected Access Weighted Round Robin XML Configuration Access Protocol Page of

12 Definitions Access Point: connection point where devices using the same link layer technology could be connected to the home network. It can be part of the HG or a separate box providing an integration point for non-common technologies Bridge: link layer function connecting two or more HN segments sharing the same data link layer. For management purposes it may also have an IP address Global usage scenario: As the HG needs to support several usage scenarios at the same time, the global usage scenario describes a scenario where several single usage scenarios are happening at the same time o Example Dual play: Television over broadband + Voice communication using an analogue phone Home Gateway: device connecting the HN to the Internet and ervice Platforms LM Remote UI (Local Management User Interface): UI (typically, but not limited to, a Web-based) to let a user manage the RM client on the gateway from a device on the HN Managed Device: device that has a remote management client that communicates directly or indirectly (via the HG) with a remote management server Managed service: A managed service is a service for which the BP provides preferential treatment (that can include Qo...) for the customer. The service can be a service offered by the BP or operated by the BP on behalf of a third party. A managed service can also be local: watching a video on a PC recorded on the IPTV TB; as explained in the IPTV PVR use case. Managed services do not necessarily involve use of the remote management system; management only means that the operator has taken some responsibility for the service (e.g. its Qo treatment) in order to provide the appropriate quality of experience. Per class Qo management: Qo treatment based on a service classes rather than individual flows. Relative Qo: This term is used to refer to a traffic delivery service without absolute bounds on the achieved bandwidth, packet delay or packet loss rates. It is used to handle certain classes of traffic differently from other classes. Remote Management ystem (RM): is the management entity which includes the Auto-Configuration erver capabilities but provides additional management functionalities. The RM include resource and device inventory, event notification and alarm management, diagnostics and troubleshooting. Unmanaged Device: device that does not have a remote management client or that does not communicate directly or indirectly (via the HG) with a remote management server. Use case: Description of a general user need. It contains the context of usage behaviour that meets the need and serves as an umbrella scenario. o Example: Voice communication Usage scenario: The usage scenario is a real scenario demonstrating the use case. o Each scenario provides details about the user (attitude, knowledge, habits, etc.), the use context (social factors, environment, information requirements, etc.), and a solution that supports or enables the particular use. o Example: Voice communication using an analogue phone. Page of

13 Unmanaged ervice: An unmanaged service is a service for which the BP has no commitment to the customer (especially in terms of Qo). Page of

14 0 0 0 Introduction and scope of the Home Gateway Initiative (HGI) Home connectivity has evolved dramatically over recent times. From the initial simple voice service, home services evolved in the 0s to include things such as fax and video text, with the 0s seeing the advent of mass-market Internet access via dial-up modems. At the start of the st century, the world has entered the broadband era. Network operators have deployed technology that offers much larger bandwidths, such as DL, cable or fibre-based access systems. The Internet has been a major driver for the evolution to broadband, creating a new experience for the customer and offering him new services such as and Internet browsing, and online versions of existing services such as digital photo labs, ticket booking etc. The next generation of broadband services (triple or even multiple-play ) has created a set of new requirements for the Home Gateway, namely: the need to manage the Home Gateway, and to a lesser extent, the home network and the devices beyond the Home Gateway allowing the right device or application to connect to the right service platform with the right service class / Quality of ervice unifying device capabilities in order to offer customers a better integrated home environment. Due to the lack of suitable off-the-shelf and standardized products to support this new, endto-end network and service model, several major Telecom Operators have recently worked separately with a very small number of Home Gateway vendors to specify and develop suitable Gateways. However, such custom development is not cost-effective for either operators or vendors. It became apparent that many operators had similar service aspirations, and so were asking for similar equipment. Therefore in December 00, nine Telecom Operators founded the Home Gateway Initiative to agree on a common Gateway specification. The intention was to involve the relevant vendor community (i.e. vendors of gateways, chipsets, software, devices and transmission systems) so that the specifications would also be pragmatic and could be realized in a costeffective manner. The aim of HGI is therefore to specify a small range of low cost, high capability Gateways which will provide multi-service communication support for the residential and OHO environments. While an end-to-end network view has been taken, the specifications mainly focus on the Home Gateway device which sits between the access network and service platforms on one side, and the in-home networked devices and applications on the other. 0. Cooperation with other bodies and initiatives The Home Gateway Initiative does not wish to become a new, long-term de facto standardization body. Its task is to agree a set of functional requirements for a Home Gateway, wherever possible re-using or referring out to existing specifications. An important aspect of the work is to identify gaps and inconsistencies in or between existing specifications. The HGI will publish its own specifications, but will work alongside other DOs to ensure that issues are addressed in the most appropriate body, that there is no unnecessary duplication of effort, and that the HGI specifications are downstreamed in the most appropriate way. Page of

15 0 cope and Purpose of this document. tructure of the pecification The HGI starts with prioritized topics proposed by the HGI telecom operators from which specific use cases and business requirements are derived. These are then used to create a set of high level requirements for the HG and, where appropriate, other parts of the network. A summary of the Business Working Group output can be found in ection. The Architectural Requirements (from the Architectural Task Force and detailed architectures derived by the Working Groups) are covered in ection. The Technical Working Groups (Home Gateway and Home Network Architecture, Quality of ervice, Remote Operations and Device Management) then produced detailed sets of formal functional requirements which are contained in ection Definition of profiles and terms The HGI is based on the recognition that there is a high degree of consensus among operators about the functionality required in an HG. However the intention was never to produce a rigid specification for a single box, for reasons: there still needs to be the opportunity for vendor product differentiation there is likely to remain a market need for more than one class of HG, e.g. Baseline and Enhanced. Note however that going to too many classes would defeat the purpose of the HGI, and that even a Baseline variant would still be an HG with multiservice support, as opposed to a simple DL modem/router. This specification addresses these needs in the following way. The majority of requirements are all expected be present in a Baseline HG. These are written as MUTs, and denoted by an in the rightmost column of ection. Note that MUT and the designation are not synonymous for the reason given below. In addition to the Baseline requirements there are types of options. The first type, Individual options, are contained within a ection consisting largely of Baseline requirements. These are written as HOULDs, and marked with a + in the rightmost column. They usually (but not always) follow a Baseline requirement and increase the basic requirement in some way (e.g. the number of ports or instances of a function). These options are the ones which vendors might choose to implement to differentiate their product, but would not be sufficient to change the class of device. The other type of option is an Optional ection. This specifies additional (as opposed to enhanced) functionality. An Optional ection is a set of requirements that contains both mandatory and optional requirements and should be considered in its entirety. Optional ections as a whole are marked with a + in the ection heading. + ections add functionality that would only be needed to implement specific services or to support certain network architectures. Within these Optional ections, the essential requirements are written as MUTs, and denoted by *, whereas the associated enhancement options are written as HOULDs and marked by +*. There has been no attempt to indicate which combination of Optional ections would be expected to be present in an Enhanced HG, as it is hard to get consensus on this, and in some cases there are alternative types of additional functionality which serve a similar purpose. In the latter case it would not make sense to implement both of the alternatives. uch ections are marked by +A, with the reference to the alternative ection also being given. The definitions of MUT and HOULD in this document are therefore as follows: Page of

16 0 MUT A functional requirement which is based on a clear consensus among HGI ervice Provider members, and is the base level of required functionality for a given class of HG. MUT NOT A function which is prohibited by the specification HOULD Functionality which goes beyond the base requirements for a given class of HG, and can be used to provide vendor product differentiation (within that class). Notes: These definitions are specific to the HGI and should not be confused with the same or similar terms used by other bodies. These terms only have these meanings when capitalized and used in the Requirements ection of this specification (ection ). Page of

17 ervices Overview and Use Case ummary. Overview of Use Cases The HGI use cases are based around a typical family of four people named the Martins. Mr. Martin purchases his broadband service from a Broadband ervice Provider (BP). The BP is responsible for the operation of the broadband access network and the HG itself. The BP can offer several services over the broadband access. The use cases also take into account the evolution of new technologies in the operator networks, e.g. IM is slowly being introduced into core networks and all the HGI operators are looking at IM as the target architecture. As part of every use case, enhanced customer support has been taken into account by providing diagnostic tools... Broadband Connection Installing a broadband modem/router and its associated Internet connection is still a complex experience for most users. Thus, one use case concerns Mr Martin installing a new broadband connection with Internet service, and sharing that connection between several PCs. Another use case concerns Mr Martin purchasing additional services through his BP which require different versions of HG software. A further use case is about parental control. Mr Martin sees that several devices are connected to the Internet and he wants to ensure that the appropriate parental control and firewall functionalities are applied. Mr Martin s Internet services have evolved to a multiple service environment (with IPTV, voice over IP etc.) and so the HG needs to support a fully featured home network where devices can interact on a single logical home network. The last usage scenario of this type covers the situation when a customer needs to replace the HG in the case of malfunction, or when he wants to migrate to another access network type... Communication Voice is still the main means of communication. Thus, more and more BPs are offering voice services over IP as part of their broadband service bundle. Users expect this service to be as easy to configure and use as their current POT service. The basic use cases cover the connection of a legacy analogue phone to the HG, and of IP phones used for VoIP. The first communication use case concerns Mr. Martin using an IP phone on his home network to connect to the BP s VoIP (Voice over IP) service with plug and play mechanisms. The next use case is about Mr. Martin using a legacy analogue phone or fax to connect to the voice port of his Home Gateway. The last use case adds a videophone for use of a video communication service. Advanced use cases have been devised which extend this basic VoIP functionality to provide Mr Martin with an enriched calling experience i.e.: Call forwarding: Mr Martin is able to pick-up a call from any VoIP device with voice capabilities (thus maintaining a consistent user experience with analogue telephony). Mr Martin can also perform voice call transfer within the home. Distribution of the caller ID to multiple devices throughout the home, e.g. TV, PC. Page of

18 ession-based content sharing. After establishing a voice communication channel between two locations, Mr Martin wants to share content (e.g. photo, video ) either from the web or local storage with another home. Messaging. Mr Martin is able to receive a message on different devices in the home (TV, PC or phone), based on an IM messaging service... Fixed-mobile and ervice Convergence... Mobile integration scenarios in the home Mr Martin brings a mobile phone into the home and uses the Wireless LAN (Wi-Fi) to connect to his mobile services. Three Fixed-Mobile convergence scenarios have been studied: UMA (extending the mobile reach into the home), a G/Wi-Fi dual phone based on a IP stack located in the phone and evolution to a IP-IM phone.... Guest and Hotspot Access Mr Martin s friend visits him and wants to connect a nomadic device (e. g. laptop computer) to the Internet. This use case is about Mr Martin allowing such a guest to connect to the Internet using Mr Martin s broadband connection, without interfering with Mr. Martin premium services and at the discretion of Mr Martin. The HG can also be enabled to allow unknown guest access by acting as a hotspot.... Using IM services from non-im enabled devices: IM proxy Mr Martin is now a customer of the next generation of IM-based services offered by his BP. This use case is about Mr Martin using non IM-capable terminals via an IM-enabled HGI HG to gain access to IM services. This functionality provides the support needed to connect legacy, non-im equipment to the home network. It also provides presence information, e.g. informing the IM core when the user is at home... Home Office Working from home is more and more common today with broadband. This usage scenario describes Mr. Martin using a secure connection to his office. He expects to have a certain Quality of ervice (Qo) for his voice and data service, and to have preferential treatment over other members of the family using other broadband services. However Mr Martin still wants to be able to use local network resources like the family printer... Entertainment & Information Access to entertainment content such as IPTV and IP radio is one of the largest residential markets and it is thus often offered as part of a broadband package.... Audio content The use case deals with audio content and a new way to distribute audio via broadband. Mr. Martin expects to be able to listen to a personal radio station (including a compilation based on his musical tastes) with the same quality of service as his current FM radio service.... Gaming This use case is about using the broadband connection for online gaming. Mr Martin s children want to connect their new networked game consoles and use an online gaming service. The use case considers these different situations: Ethernet connected consoles for online gaming, Wi-Fi multiplayer gaming with Wi-Fi guest accounts for on-line gaming, and Ethernet connected PCs for on-line gaming using additional applications such as instant messaging and VoIP. Page of

19 IPTV (real-time delivery) IPTV is a managed service defined as delivering broadcast quality TV over IP. IPTV also allows watching multiple streams (e.g. tandard Definition video channels over an ADL line) with simultaneous High Definition video distribution within the home. The focus is on network and service connectivity issues and not on the service layers; the HGI addresses the delivery of IPTV services, but currently excludes the involvement of the HG in DRM and/or descrambling of IPTV. Multiple IPTV channels need to be simultaneously accessible by different members of the Martin family from different set top boxes. There are the following additional scenarios: free IPTV (e.g. public service or sponsored), pay IPTV (e.g. premium content or pay-per-view), multiple family members viewing IPTV simultaneously and viewing content from a Video on Demand (VoD) service. Another use case describes viewing a previously recorded movie. The movie was recorded on the main et Top Box (TB) but is being viewed on a device other than the TV, that is physically connected to that TB. The PVR use case also takes into account advanced functions such as VoD trickmodes (play, pause, fast forward) offering Mr Martin a DVD-like experience, PVR-based timeshifting of broadcast IPTV, PVR based scheduled recording. The PVR functionality can be placed either in the home network, or in the BP s network. Another scenario addresses an IPTV interactive service where interaction is happening at the same time as Mr Martin is watching his IPTV program. This includes new types of services such as tele-voting. Finally, the use of multiple devices (TV/TB, PC, PDA, multiservice mobile phones) to deliver free-to-air unprotected content to Mr Martin and his family members at the same time is covered.... Extended IPTV (request and store IPTV) Whereas IPTV can be thought of as just broadcast TV over IP, a new experience can also be offered using the TV to view stored podcasts. One use case of this type is about TV video content being downloaded to the TB both for on-demand and scheduled download (streaming / file transfer). Another use case is about extended IPTV multimedia where Mr Martin can consume or manage TV content from TV content service providers outside the home, or consume or manage video content from local devices.... Media server This scenario covers the Home Gateway supporting a media server (a device storing photos, videos, music, etc.) by delivering media content to the different multimedia devices in the home... Remote access Remote access to home devices and content is one of the latest consumer market trends. Two use cases have been developed: Remote access for recording video content. Mr Martin accesses his Personal Video Recorder (PVR) to initiate a recording remotely. Accessing content stored in the home: Mr Martin can upload/download photos or videos from local storage (e.g. PVR, networked hard disk) from a remote location. The Home Gateway is required to protect access to the home network resources. Page of

20 0.. Home Management & ecurity Users want to be able to manage their digital home and be in control of their environment.... Home surveillance This use case details Mrs. Martin being able to check, via a web camera, that her children have returned home while she is still in her office.... Home ecurity The home security usage scenario is about Mr Martin using an intrusion detection and alarm system provided over broadband.... Home Automation Two use cases were developed. One that allows Mr Martin to remotely control home appliances, and another that allows Mr Martin to authorize his gas or electricity company to access the home network in order to take a meter reading Home Gateway General Requirements ummary This section details some key requirements and concepts developed in the HGI business group that illustrate the above use cases... Ease of use and simplicity The Home Gateway, home network and associated devices and services must be easy to install and configure. Zero-touch configuration and plug and play are key concepts when designing services and devices that will work in the HG eco-system. Appropriate tools for end-users and operators must be made available... ecurity The Home Gateway provides security functions including firewalls, access control and personal monitoring, that makes the home user feel secure against threats that originate on the Internet... Quality of service: unmanaged services / managed services The HGI considered Quality of ervice (Qo) to be one of the first issues to be tackled and so derived a set of business requirements around Qo. A managed service is defined as a service for which the service provider is able to give preferential treatment to the customer s traffic. IPTV and Voice over IP are two such services. Unmanaged services are services for which the service provider has no commitment to the customer (especially in terms of Qo). Examples are peer-peer applications, and general LAN flows within the home. Other examples of services supported included gaming and home working. As a consequence, these unmanaged services can become managed... Remotely managed gateway / home network The HG must support a remote management system to enable remote operations and customer care procedures and to enhance and enable the provisioning of managed services at home. Therefore, the HG needs to be a managed device. In addition, a managed home network is needed to deliver some managed services. The managed network contains managed devices. The managed home network must coexist with home network segments and terminals that are not managed. The interaction between the two networks Page 0 of

21 or sections (that in practice cannot be simply physically separated) will be controlled and monitored with the support of the HG... Performance Monitoring and Diagnostics The HG must provide a performance monitoring function. The expected approach requires that an action is taken only when a problem is reported by the customer, but then it must be possible to diagnose the problem, i.e. reactive rather than proactive mode. Operators must be able to monitor service performance ervice Provider Role models.. Role model definitions The HGI model is based on the following roles: The Access Network Provider (ANP) takes responsibility for operating the access network active equipment. The ANP can provide layer bitstream connections to BPs. The Broadband ervice Provider (BP) takes responsibility for operating the IP network, including the HG. The BP provides IP connectivity to APs. The BP often provides Internet access to end customers as part of his broadband IP connectivity service. The BP would also be responsible for the IM infrastructure deployed in the HG. The Managed Application ervice Provider (Managed AP) takes responsibility for operating an application, and has a relationship with the BP that allows it to benefit from Qo, multicast, or other advanced network-related features. The Unmanaged Application ervice Provider (Unmanaged AP) takes responsibility for operating an application but does not benefit from Qo, multicast, or other advanced networkrelated features... Role model assumptions The HGI assumes that there is only one BP per customer as there is a need for a single customer facing entity capable of managing the network, Qo and troubleshooting. Multiple APs (both Managed and Unmanaged) may offer their applications on top of the broadband connectivity provided by the BP. Page of

22 0 0 HGI Reference Architecture. End to End Network Architecture Although the HGI has largely been driven by the Use Case approach, most Network Providers have some more general architectural requirements, and these also need to be taken into account. uch requirements may arise from a need to continue to support existing network features, a view of the overall topology and connectivity required, or the likely architectural evolution (e.g. towards IM). This aspect of the requirements was covered by an Architectural Task Force (ATF). The ATF also translated the business group s (Use Case) commercial requirements into high level technical requirements. The starting point for the ATF work was the overall architectural reference diagram which is shown in Figure. The key features of the diagram are: Multiple service edges which do not connect to a single service aggregation point e.g. a BRA. This has implications for L connectivity and Qo control upport for multiple service providers (APs) A single management entity at any one time controlling the HG (operated by the BP) Qo control via the Remote Management ystem (RM) (see ection.), not directly from a network Qo Manager The HG operating as both a router and a bridge Local turnaround of in-home traffic in the HG upport for remote access to devices on the HN upport for end-device management (both via the RM and not via the RM) upport for the delivery of messages to a variety of end device types upport for intra-home voice Guest access support via Wi-Fi Page of

23 Remote Access O O Home Environment BP Domain RM NBI Internet 0. RAD Mgmt Qo POT AP BRA Access and Agg 00BaseT Hotspot P AP DL Fibre Ethernet M HG UB M 0 0 Key to the figure: L+.. HG upply Model L 0. Figure. End to End Architectural Model (Unknown) Guest Access M = Managed Device; RAD = Remotely Accessible Device It is assumed that the Home Gateway is provided and managed by the BP although a few mechanisms have been provided which are appropriate to a slight extension of this model in which the Home Gateway is purchased (from a retail outlet) by the customer by selecting it from a list of supported Home Gateways provided by his BP... Integrated NT and HG In most current deployments the HG is an integrated device which includes the appropriate WANside technology. However in some environments, and with the increasing move to fibre based access, the WAN interface may be contained in a separate NT. Optional support for a WAN 00BaseT/GBE interface has therefore also been included. NOTE: The following ections contain a summary of the high-level architectural requirements. The detailed technical requirements are given in ection... WAN interfaces ADL ADL+ VDL Ethernet (00BaseT/GBE) FXO Page of

24 LAN interfaces Wired Ethernet Wireless (0.a/b/g/n) UB.0 slave and host ports Telephony interfaces (DECT, FX, IDN).. Connectivity Map services into the appropriate L pipe to reach the correct service edge node and/or provide connectivity to different APs upport for multiple BRAs Allow direct connection of other access technologies to end-devices imultaneous routing and bridging upport direct data connectivity (i.e. not via the Access network) between in-home devices. Provide local PBX (Private Branch exchange) functionality without requiring the signalling and media to traverse the Access Network upport secure, Wi-Fi based guest access to provide (e.g. Internet) connectivity for both known and unknown guests (see ection.) No direct connection between guest access and the Home Network.. Qo upport downstream Qo, upstream Qo, and prioritising intrahome traffic with respect to Access Network traffic. upport the Qo remarking of LAN-side traffic Provide a local (i.e. in the HG) Connection Admission Control (CAC) function for IP based voice Provide a means for the End User (EU) to associate devices with a Qo service class Provide locally generated Qo classifier to support remote access (as a transient service) Only allow user Qo configuration via profiles managed via the AC Provide congestion statistics on all queues Co-existence with other, in-home Qo schemes, e.g. DLNA Provide differentiated, service class-specific Qo for both the home and guest user... Management Only allow a single RM per HG at any one time upport RM selection by the HG Manage end-devices (including UPnP) devices as well as the HG itself Remote firmware download Configuration changes without requiring a complete firmware download.. Encapsulation and session support Terminate, originate and transparently pass PPP sessions upport both PPP encapsulated traffic and non-ppp encapsulated traffic Trigger PPP sessions on the basis of LAN-side activity.. IP Addressing upport PPP and DHCP based IP address allocation Page of

25 upport end-devices which have a static, public IP address upport different IP address schemes and subnets on the same physical LAN port, and on different LAN ports upport different IP address schemes and subnets on the WAN port upport IPv with and without NAT/NAPT (simultaneously) upport for multiple WAN-side IP addresses..0 ecurity The management system and HG both need to be authenticated HG authentication must be non service specific upport a specified (and updatable) list of ALGs Provide a Firewall which is remotely configurable by the BP but which must not be applied to Guest access Provide a unique (gateway) hardware ID which can be remotely read upport different classes of user with regard to management access rights Pairing is required for devices connected through a shared (physical) link upport IM-based authentication Provide a proxy function for devices with no IM capability.. Fixed-Mobile and ervice Convergence upport of non-im services based on IP Personalised and non-personalised service support hare a public IM ID between non IM devices The HG must have its own unique IM ID upport individual and group identities upport IM authentication Terminate a limited set of IM services in the HG to support legacy non IM devices such as some phone types upport UMA passthrough Presence support by association with a mobile phone.. Multicast support Multiple in-home devices (in a given HN) able to join the same multicast stream IGMP snooping on all LANside interfaces Ability to support L conversion of multicast to unicast traffic (for shared medium home network technologies).. Remote Device Access upport for accessing data on and controlling end devices not only via the AC ecure remote access to authenticated entities not including content encryption Multiple mechanisms for authenticating remote access with different security levels to allow a security breach to be remedied ACLs to manage remote access Remote access logging.. Parental Control There are different types of Parental control: Restricting access to certain types of content, or sources of content (specific URLs) Page of

26 0 Restricting the use of specific devices (e.g. a particular PC) or types of device (e.g. networked Games machines) either completely, or on the basis of application type and/or time of day. The HGI decided to completely separate these two, and to provide support for the latter (in the HG), but not the former, on the grounds that this would place an excessive maintenance burden on the HG (e.g. to keep the blacklists updated), and would mean establishing the identity of individuals, rather than machines. The requirements on Parental Control therefore become: Device, time of day and application type control with no explicit user awareness Local configuration only, by the local administrator AC override for troubleshooting purposes Parental control must not be applied to guest access (ee ection. for further detail)... Messaging tore and forward and transparent messaging (e.g. IM, IP, M) support Message delivery to a variety of device types Moving towards a more IM like architecture Most of the HGI operators are moving towards an IM oriented architecture. However they also have to take into account their legacy networks and services, and the fact that not all services are necessarily best delivered over an IM infrastructure. Therefore this migration has not been rapid and ultimately the pace will be dictated by whether or not there is a business case to support it. Various IM upport capabilities have however been included, e.g. IM based authentication (IIMs) and identity management. There is also the concept of the HG acting as a proxy so some IM services can be delivered to legacy devices. In certain areas, notably Qo, the HGI approach is somewhat at variance with that of IM, although the latter still needs considerable work before it seriously addresses the Access Network and HG. The reason for this is that IM comes from the mobile world where most services are session based and revenue generating, and network resources are scarce and expensive. These are all far less true in a broadband access network. There are some moves towards a more IM like Qo approach with the addition of some limited CAC functionality, but it is believed that the current HGI Qo approach is well suited to the types of services and access networks which are currently being deployed... IM-based remote access Figure shows a high level architecture using IM to enable Remote Access to home devices. The device types of interest include both UPnP and non-upnp devices. Page of

27 IM Control plane IM Media plane UPnP/DLNA. IP INVITE (IM Control Plane) IM Network non- UPnP Mobile devices Home Gateway. ession (IM Media Plane). IP INVITE Remote Device Figure High level IM based Remote Architecture: overview The principle of IM based Remote Access is that IM control plane is used to route the INVITE message to the HG and to set up the session on the IM media plane between the Remote Device and the HG. The architecture uses an IM/NGN infrastructure to deliver managed remote access services end-to-end with different requirements on Qo, e.g. real-time IPTV streaming (place shifting) versus background upload of JPEG pictures 0 0. Parental control The HG contains a Parental Control Function (PCF) and a Parental Control Profile (PCP). The PCP is the set of restrictions in the HG limiting access to home network attached users. The PCP does not apply to guest access users. The PCF can be activated and de-activated by the AC (for troubleshooting purposes), but is managed locally. The PCP is based on device-id, device type, time of day, day of week, and application type. The PCP is managed by the home parental control administrator. All other parental control restrictions such as content or site categories, and those which depend on knowledge of the user, are beyond the scope of the HGI. These are assumed to be addressed via a separate, network based parental control service which is totally independent of the functions described in ection... The only requirement on the HG to support such an additional service is being able to set the URL of the Parental Control Proxy related to this additional service in the HG management data base. Page of

28 Home Gateway ervice request Guest Network AC Logging ettings Filtering PCF ervice request Home network Enable/ disable Activate /deactivate Home administrator PCP () settings settings Figure. Parental control scenario 0 0. Guest and Hotspot Access While, the HGI is primarily concerned with supporting the family of users associated with the HG owner at their home location, nomadic access is likely to become increasingly important, and this requires the nomadic user to be able to get Broadband access, normally via some kind of Wireless access. This can obviously be done via a commercial Wireless hotspot, but the coverage of these is still fairly limited, and the services that the user may wish to use in such an open environment may also be limited. Any given HG/access link is likely to be idle or less than fully utilized for a large proportion of the day. This raises the possibility of using some of this capacity for nomadic Guest Access. There are distinct types of Guest, both of which need to be supported: Those who are known to the HG owner, and physically present within the home Those who are not known to the HG owner and are outside the home The key requirements of such a service are: Ensuring the security and integrity of the HG and HN, and its stored data, information and content so that it cannot be compromised by a Guest user. Ensuring that the HG owner s services get the appropriate priority, but without completely starving the Guest User. Ensuring that Guest services which require Qo (in particular voice) can get the appropriate priority, but again without adversely impacting the HG owner s services. The Guest Access Architecture is shown in Figure. Guests are separated from the Home Users by being on separate IDs. The unknown guest uses a broadcast ID, and there is no data encryption at the Wireless layer. The unknown guest can only connect to a commercial hotspot service provider. This could be achieved by a (L) tunnel from the HG to the hotspot AP. Traffic is steered into the tunnel on the basis of the appropriate ID. Traffic arriving in the tunnel is Page of