ETSI TR 185 004-2007 Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN) High level customer network architectures (V1 1 1)《电信和互联网融合业务_1.pdf

1、 ETSI TR 185 004 V1.1.1 (2007-08)Technical Report Telecommunications and Internet converged Services andProtocols for Advanced Networking (TISPAN);High level customer network architecturesETSI ETSI TR 185 004 V1.1.1 (2007-08) 2 Reference DTR/TISPAN-05013-NGN-R2 Keywords analysis, architecture, netwo

2、rk ETSI 650 Route des Lucioles F-06921 Sophia Antipolis Cedex - FRANCE Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 Siret N 348 623 562 00017 - NAF 742 C Association but non lucratif enregistre la Sous-Prfecture de Grasse (06) N 7803/88 Important notice Individual copies of the present document ca

3、n be downloaded from: http:/www.etsi.org The present document may be made available in more than one electronic version or in print. In any case of existing or perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF). In case of dispute, the

4、 reference shall be the printing on ETSI printers of the PDF version kept on a specific network drive within ETSI Secretariat. Users of the present document should be aware that the document may be subject to revision or change of status. Information on the current status of this and other ETSI docu

5、ments is available at http:/portal.etsi.org/tb/status/status.asp If you find errors in the present document, please send your comment to one of the following services: http:/portal.etsi.org/chaircor/ETSI_support.asp Copyright Notification No part may be reproduced except as authorized by written per

6、mission. The copyright and the foregoing restriction extend to reproduction in all media. European Telecommunications Standards Institute 2007. All rights reserved. DECTTM, PLUGTESTSTM and UMTSTM are Trade Marks of ETSI registered for the benefit of its Members. TIPHONTMand the TIPHON logo are Trade

7、 Marks currently being registered by ETSI for the benefit of its Members. 3GPPTM is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners. ETSI ETSI TR 185 004 V1.1.1 (2007-08) 3 Contents Intellectual Property Rights4 Foreword.4 1 Scope 5 2 References

8、 5 2.1 Informative references5 3 Definitions and abbreviations.6 3.1 Definitions6 3.2 Abbreviations .6 4 Overview of customer networks.7 4.1 Single service provider.7 4.1.1 Single customer gateway 7 4.1.2 No gateways8 4.2 Multiple service providers8 4.2.1 Single customer network gateway 9 4.2.2 Mult

9、iple gateways (separate Customer Networks) .9 4.2.3 Multiple gateways (communicating networks).10 4.2.4 No gateways10 4.3 Considerations on multiple network access providers (multiple WAN entry points) 10 5 CPN technologies.10 History 11 ETSI ETSI TR 185 004 V1.1.1 (2007-08) 4 Intellectual Property

10、Rights IPRs essential or potentially essential to the present document may have been declared to ETSI. The information pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found in ETSI SR 000 314: “Intellectual Property Rights (IPRs); Essent

11、ial, or potentially Essential, IPRs notified to ETSI in respect of ETSI standards“, which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web server (http:/webapp.etsi.org/IPR/home.asp). Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has b

12、een carried out by ETSI. No guarantee can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web server) which are, or may be, or may become, essential to the present document. Foreword This Technical Report (TR) has been produced by ETSI Technic

13、al Committee Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN). ETSI ETSI TR 185 004 V1.1.1 (2007-08) 5 1 Scope The objective of the present document is to analyse the possible architectures for the customer environment, combining different possibiliti

14、es in terms of elements to be considered. In particular, the analysed architectures will cover the possibility of managing one or more than one entry points from the WAN side, using one or more than one customer gateway, or possibly excluding the adoption of a customer gateway. Different alternative

15、s for Customer Network Gateway ownership will also be examined. The detailed architectures of customer devices and customer network gateways will be addressed in other WIs and will take into account the possible alternatives analysed in the present document. The customer network is intended to suppo

16、rt residential or small office scenarios, so that the scope of the document does not include corporate scenarios which are to be covered by other documents. 2 References References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For a

17、specific reference, subsequent revisions do not apply. Non-specific reference may be made only to a complete document or a part thereof and only in the following cases: - if it is accepted that it will be possible to use all future changes of the referenced document for the purposes of the referring

18、 document; - for informative references. Referenced documents which are not found to be publicly available in the expected location might be found at http:/docbox.etsi.org/Reference. For online referenced documents, information sufficient to identify and locate the source shall be provided. Preferab

19、ly, the primary source of the referenced document should be cited, in order to ensure traceability. Furthermore, the reference should, as far as possible, remain valid for the expected life of the document. The reference shall include the method of access to the referenced document and the full netw

20、ork address, with the same punctuation and use of upper case and lower case letters. NOTE: While any hyperlinks included in this clause were valid at the time of publication ETSI cannot guarantee their long term validity. 2.1 Informative references 1 ETSI ES 282 001: “Telecommunications and Internet

21、 converged Services and Protocols for Advanced Networking (TISPAN); NGN Functional Architecture Release 1“. 2 Home Gateway Initiative: “Home Gateway Technical Requirements: Release 1“. 3 ETSI TS 181 005: “Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPA

22、N); Services and Capabilities Requirements“. 4 ETSI ES 282 003: “Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Resource and Admission Control Sub-system (RACS); Functional Architecture“. 5 ETSI ES 282 004: “Telecommunications and Internet converge

23、d Services and Protocols for Advanced Networking (TISPAN); NGN Functional Architecture; Network Attachment Sub-System (NASS)“. 6 ETSI ES 282 007: “Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); IP Multimedia Subsystem (IMS); Functional architecture

24、“. ETSI ETSI TR 185 004 V1.1.1 (2007-08) 6 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the terms and definitions given in ES 282 003 4, ES 282 004 5, ES 282 007 6 and the following apply: Customer Network Device (CND): physical device enabling service(s)

25、 usage NOTE. CNDs can be dedicated to the internet, conversational and audio-video services. But they could be also Consumer Electronics equipment and other devices which may have nothing to do with these premium services (e.g. services performing a content sharing within a CPN, typically between a

26、PC and a music system, through the CNG). Customer Network Gateway (CNG): gateway between the Customer Premises Network (CPN) and the Access Network able to perform networking functions from physical connection to bridging and routing capabilities, but also possibly implementing functions related to

27、the service support Customer Premises Network (CPN): in-house network composed by customer network gateway, customer network devices, network segments (physical wired or wireless connections between customer network elements), network adapters (performing a L1/L2 conversion between different network

28、 segments) and nodes (network adapters with L3 routing capabilities) NOTE: Other terms used to identify CPN in TISPAN NGN R1 deliverables or outside TISPAN are Home Area Network (HAN), Home or Residential Network, Customer LAN (C-LAN). Network Addapter (NA): Allows management of the home segment at

29、the layer 2. NA is the master on the customer network segment for all the CNDs that want to access the media. It can be part of the CNG or a separate box providing an integration point for non-common technologies. These devices are called sometimes also “gateways“. 3.2 Abbreviations For the purposes

30、 of the present document, the following abbreviations apply: AN Access Network AP Access Point AS Application Server BR Bridge CND Customer Network Device CNG Customer Network Gateway CNGCF Customer Network Gateway Control Function CNS Customer Network Segment CPN Customer Premises Network Mgmt Mana

31、gement NA Network Adapter NASS Network Attachment SubSystem NAT Network Address TranslationNGN Next Generation Network NSP NGN Service Provider NT Network Termination P-CSCF Proxy-CSCF PPPoE Point to Point Protocol over Ethernet PSTN Public Switched Telephone Network RACS Resource and Admission Cont

32、rol Subsystem QoS Quality of Service VoIP Voice over IP ETSI ETSI TR 185 004 V1.1.1 (2007-08) 7 4 Overview of customer networks 4.1 Single service provider 4.1.1 Single customer gateway Assuming a single access plus service provider offers its services in the customer network, via a single access te

33、chnology and customer gateway, the following reference architecture is proposed 2. ConnectivityCNS2CNS1NA2NA1NTCND11QoSARFCND12CND2CND3RouterBridgeMgmtCNGCNGCFServiceRACSASPCSCFQoSMgmtService interfaceCPN interfaceLogical linksPhysical linksNASSGlossary: NT: Network Termination. BR: Bridge. Network

34、adaptor that interconnects two or more home segments that are sharing the same data link layer. CNDx: Customer Network Device, the point of service usage for the end user (PC, TV+set top box, PDA etc.). CNSx: Customer Network Segment, that can be wired or wireless APx. Mgmt: Management. CNS: Custome

35、r Network Segment. NA: Network Adapter, it allows management of the home segment at the layer 2. NA is the master on the customer network segment for all the CNDs that want to access the media. It can be part of the CNG or a separate box providing an integration point for non-common technologies. Th

36、ese devices are called sometimes also “gateways“. Figure 1: Customer network architecture for single gateway, single service provider The above architecture is access agnostic, and throughout the present document we will keep this assumption. There are two possibilities for intra-CPN traffic: Centra

37、lized, where all traffic is forced via the CNG (this increases the complexity of the CNG, but allows the SP more control over the CPN). This means that all APs are integrated in the CNG itself. Distributed, which allows direct device-device communication without going via the CNG or via an AP that i

38、s not integrated in the CNG. In figure 1 the green arrows illustrate that both cases are possible. ETSI ETSI TR 185 004 V1.1.1 (2007-08) 8 The CNG supports both bridged and/or routed models. There are several architectural solutions for the Customer Network to support these models 2. The most compli

39、cated scenario is depicted in figure 2. Figure 2: Hybrid model with separate physical networks The hybrid model with separate physical networks offers two or more physically separated CPNs, one corresponding to the routed, and the other(s) to the bridged modes of operation. The CNG has distinct phys

40、ical interfaces for each network type. Devices can only directly communicate with other devices on the same network segment. Communication between network segments is only possible via the Access Network. More simplified architectures could include the presence of only one CPN (either routed or brid

41、ged), thus implementing the routed or bridged model separately. While the routed model supports fully intra-CPN connectivity, this is not the case for the purely bridged model. A specific case of coexistence of the bridged and routed approaches is the following: Routed model with NAT + PPPoE Passthr

42、ough (L2 partial bridge): to support the case where a device on the CPN needs to be able to directly communicate (at L2) with a server on the AN. The L2 connectivity is limited to PPPOE traffic. The broadcast PPPoE set-up requests are recognized by the CNG, which sets up L2 bridging for all PPP traf

43、fic coming from that device. Intra-CPN communication can be fully supported in this case. 4.1.2 No gateways In case of PSTN replacement a device can be directly connected to NGN (PES or IMS core) to support voice services. A second case is the adoption of Femtocells, allowing the connection of a num

44、ber of mobile customer devices directly to NGN. Intra-CPN communication could be supported in this case only using additional interfaces. A third case can be the presence of a single customer device in the CPN with an embedded modem and able to access the NGN, in order to consume a single service or

45、 a restricted subset of services (e.g. a videotelephone with an embedded modem). 4.2 Multiple service providers With reference to contents of TS 181 005 3 defining the operator roles, the following scenarios can be considered. ETSI ETSI TR 185 004 V1.1.1 (2007-08) 9 4.2.1 Single customer network gat

46、eway CNGCPNAggregator Access networknodeAN provider Connectivity provider NSPaNSPbGlossary: NSPa/b: NGN Service Provider a and b. Figure 3: Customer network architecture for single gateway, multiple service providers The Customer Network has the architecture presented in clause 4.1.1. 4.2.2 Multiple

47、 gateways (separate Customer Networks) CNG aCNG bNT (L2 device)CPN1CPN2Access networknodeAN provider Connectivity provider NSPaNSPbFigure 4: Customer network architecture for multiple gateways, multiple service providers In figure 4, each NSP has its own CNG, which is connected to the NT. The two CN

48、Gs do not communicate to each other. At each CNG a Customer Premises Network (CPN) is connected, and each one can have the architecture presented in clause 4.1.1. In this configuration it is not possible to communicate from a device connected to CPN1 to a device connected to CPN2 unless via the NGN

49、itself. Point to point connectivity between devices (at non IP level) can be established (e.g. infrared or Bluetooth communication). Each SP will manage its corresponding CNG and CPN, using for example DSL Forums TR-069. The different flows coming from the NSPs can be mapped by the NT with different ports on the CPN side, using a number of possible mechanisms, such as Ethernet VLANs, ATM PVCs, PPPoE, VPN sessions, etc. ETSI ETSI TR 185 004 V1.1.1 (2007-08) 104.2.3 Multiple gateways (communicating networks) This is not a typical case for