ETSI TS 185 006 V2.0.0 (2008-03)

Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Customer Devices architecture and interfaces and Reference Points

DTS/TISPAN-05015-NGN-R2

General Information

• Status: Published
• Publication Date: 03-Mar-2008
• Technical Committee: TISPAN 5 - TISPAN NGN Home Networking
• Current Stage: 12 - Completion
• Due Date: 06-Feb-2008
• Completion Date: 04-Mar-2008

Standards Content (Sample)

Technical Specification
Telecommunications and Internet converged Services and
Protocols for Advanced Networking (TISPAN);
Customer Devices architecture and Reference Points

2 ETSI TS 185 006 V2.0.0 (2008-03)

Reference
DTS/TISPAN-05015-NGN-R2
Keywords
architecture, interface
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: [phone]  Fax: [phone]

Siret N° 348 623 562 00017 - NAF 742 C
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° 7803/88

Important notice
Individual copies of the present document can 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 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 documents 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 permission.
The copyright and the foregoing restriction extend to reproduction in all media.

© European Telecommunications Standards Institute 2008.
All rights reserved.
TM TM TM TM
DECT , PLUGTESTS , UMTS , TIPHON , the TIPHON logo and the ETSI logo are Trade Marks of ETSI registered
for the benefit of its Members.
TM
3GPP is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners.
ETSI
3 ETSI TS 185 006 V2.0.0 (2008-03)
Contents
Intellectual Property Rights.4
Foreword.4
Introduction .4
1 Scope.5
2 References.5
2.1 Normative references.5
2.2 Informative references.6
3 Definitions and abbreviations.7
3.1 Definitions.7
3.2 Abbreviations.7
4 Customer Network Device classification.9
4.1 Non IMS capable CNDs.11
4.2 Non-IP CNDs.11
4.2.1 Non-IP CNDs connected to the NGN without a CNG.11
4.2.2 Non-IP CNDs connected to the NGN through a CNG .11
4.3 IP CNDs.12
4.4 SIP IETF capable CNDs.12
4.4.1 Non-IMS SIP CND connected to the NGN through a CNG.12
4.5 Consumer Electronics.13
4.6 IMS capable CNDs.13
4.7 IMS Customer Network Device connected to the NGN through a CNG .13
4.8 Consumer Electronics.14
4.9 IMS customer network device architecture .14
4.9.1 The Customer Network Devices- Network Attachment Subsystem entities (CND-NASS) .14
4.9.2 The transfer level functions .15
4.9.3 The transport level functions .15
4.9.4 The Customer Network Devices - Service-related Functional entities (CND-SF) .15
5 Reference Points.16
5.1 Network attachment reference points.16
5.2 Transport level reference points .17
5.3 Service layer reference points .17
6 Authentication issues.18
6.1 CNG based.18
6.2 Non CNG based .20
7 The CND Data Model .21
8 Information Flows.21
8.1 Attachment Flows.21
'
8.1.1 Example of Information Flows on e .21
8.2 Configuration and management flows.22
8.2.1 Example of management reference point selection .22
'
8.2.2 Example of Information Flows on e .24
8.3 Signalling flows.25
8.3.1 CND attachment and NGN registration.25
8.3.2 Outgoing call.26
8.3.3 Internal Call.27
8.3.4 Admission Control (CNG-ACF).29
8.4 Remote Access information flows.30
8.4.1 Connection Setup.30
8.4.2 Download of content.31
8.4.3 Upload of content .32
History .34
ETSI
4 ETSI TS 185 006 V2.0.0 (2008-03)
Intellectual Property 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); Essential, 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 been 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 Specification (TS) has been produced by ETSI Technical Committee Telecommunications and Internet
converged Services and Protocols for Advanced Networking (TISPAN).
Introduction
The present document describes the main type of Customer Devices that take part in Customer Premises Network in
terms of general architecture and in terms of reference points with the NGN and CNG.
The present document gives a Customer Devices classification based on services and access technology supported.
ETSI
5 ETSI TS 185 006 V2.0.0 (2008-03)
1 Scope
The present document defines the stage 2 Customer Network Devices (CND) specifications, including architectural
building blocks to be included in the Customer Network Devices to support the interworking with control plane NGN
architecture, both for the transport layers (NASS, RACS) and for the service layer. The present document will also
define the reference points between the NGN architectural blocks involved and the corresponding CNDs functions here
defined (for the cases in what the CNG will be transparent for the service and control planes point of view), as well as
between the Customer Network Devices and the CNG when appropriate. The present document will perform, as first
step, a categorization of the different user equipment with reference to the type of service supported and the different
levels of implementation of the related functionalities.
Please note that in relation to the Customer Network Devices for IPTV usage the present document will cover only the
classification step and will not provide any detail about the architecture and reference points. The IPTV CND are
specified in TS 185 009 [20].
2 References
References are either specific (identified by date of publication and/or edition number or version number) or
non-specific.
• For a 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 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. Preferably,
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 network 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 Normative references
The following referenced documents are indispensable for the application of the present document. For dated
references, only the edition cited applies. For non-specific references, the latest edition of the referenced document
(including any amendments) applies.
[1] ETSI ES 282 002: "Telecommunications and Internet converged Services and Protocols for
Advanced Networking (TISPAN); PSTN/ISDN Emulation Sub-system (PES); Functional
architecture".
[2] ETSI TS 183 043: "Telecommunications and Internet converged Services and Protocols for
Advanced Networking (TISPAN); IMS-based PSTN/ISDN Emulation Stage 3 specification".
[3] ETSI TS 182 012: "Telecommunications and Internet converged Services and Protocols for
Advanced Networking (TISPAN); IMS-based PSTN/ISDN Emulation Subsystem; Functional
architecture".
ETSI
6 ETSI TS 185 006 V2.0.0 (2008-03)
[4] ETSI ES 283 003 "Telecommunications and Internet converged Services and Protocols for
Advanced Networking (TISPAN); IP Multimedia Call Control Protocol based on Session
Initiation Protocol (SIP) and Session Description Protocol (SDP) Stage 3 [3GPP TS 24.229
(Release 7), modified]".
[5] ETSI TS 185 005 "Telecommunications and Internet converged Services and Protocols for
Advanced Networking (TISPAN); Services requirements and capabilities for customer networks
connected to TISPAN NGN".
[6] ETSI TS 185 003: "Telecommunications and Internet converged Services and Protocols for
Advanced Networking (TISPAN); Customer Network Gateway Architecture and Reference
Points".
[7] HGI - Home Gateway Technical Requirements.
NOTE: Available at http://www.homegateway.org.
[8] DSL-Forum TR-069 Amendment 1: "CPE WAN Management Protocol".
[9] DSL-Forum TR-104: "DSLHome Provisioning Parameters for VoIP CPE".
[10] DSL Forum TR-106: "DSLHomeTM Data Model Template for TR-069-Enabled Devices".
NOTE: Available at http://www.dslforum.org.
[11] ETSI TS 183 023: "Telecommunications and Internet converged Services and Protocols for
Advanced Networking (TISPAN); PSTN/ISDN simulation services; Extensible Markup Language
(XML) Configuration Access Protocol (XCAP) over the Ut interface for Manipulating NGN
PSTN/ISDN Simulation Services".
[12] IETF RFC 3261: "SIP: Session Initiation Protocol".
[13] ETSI ES 282 007 "Telecommunications and Internet converged Services and Protocols for
Advanced Networking (TISPAN); IP Multimedia Subsystem (IMS); Functional architecture".
[14] ETSI ES 282 004: "Telecommunications and Internet converged Services and Protocols for
Advanced Networking (TISPAN); NGN Functional Architecture; Network Attachment
Sub-System (NASS)".
[15] ETSI TS 183 019: "Telecommunications and Internet converged Services and Protocols for
Advanced Networking (TISPAN); Network Attachment; User-Network Interface Protocol
Definitions".
[16] ETSI ES 282 001: "Telecommunications and Internet converged Services and Protocols for
Advanced Networking (TISPAN); NGN Functional Architecture".
[17] ETSI TS 131 103: "Digital cellular telecommunications system (Phase 2+); Universal Mobile
Telecommunications System (UMTS); Characteristics of the IP Multimedia Services Identity
Module (ISIM) application (3GPP TS 31.103 version 7.3.0 Release 7)".
[18] IETF RFC 2131: "Dynamic Host Configuration Protocol".
[19] ETSI TS 124 229: "Digital cellular telecommunications system (Phase 2+); Universal Mobile
Telecommunications System (UMTS); Internet Protocol (IP) multimedia call control protocol
based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3
(3GPP TS 24.229 version 8.2.0 Release 8)".
2.2 Informative references
[20] ETSI TS 185 009: "Telecommunications and Internet converged Services and Protocols for
Advanced Networking (TISPAN) Architecture and reference points of customer network devices
for IPTV services".
[21] ETSI TS 187 001: "Telecommunications and Internet converged Services and Protocols for
Advanced Networking (TISPAN); NGN SECurity (SEC); Requirements - Release 2".
ETSI
7 ETSI TS 185 006 V2.0.0 (2008-03)
[22] ETSI TR 187 008: "Telecommunications and Internet converged Services and Protocols for
Advanced Networking (TISPAN); NAT traversal feasibility study report".
[23] ETSI TR 185 007: "Telecommunications and Internet converged Services and Protocols for
Advanced Networking (TISPAN); Analysis of protocols for customer networks connected to
TISPAN NGN".
[24] ETSI TR 182 005: "Telecommunications and Internet converged Services and Protocols for
Advanced Networking (TISPAN); Organization of user data".
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the following definitions are applied:
CPN Device: device that is physically installed in the CPN allowing user access to network services; this can be a
Customer Network Gateway with gateway functionalities towards the NGN, or a Customer Network Device being the
end user terminal
Customer Network Device (CND): CPN device enabling the final user to have direct access to services through a
specific user interface
NOTE 1: 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 PC and a music
system). CND classification is reported in clause 4.
NOTE 2: For CND classifications see clause 4.
Customer Network Gateway (CNG): CPN device acting as a gateway between the CPN and the NGN
NOTE: CNG is able to perform networking functions from physical connection to bridging and routing
capabilities (L1-L3), but also possibly implementing functions related to the service support (up to L7).
Customer Premises Network (CPN): in-house network composed by customer network gateway, customer network
devices, network segments, network adapters and nodes
NOTE: Network segments are physical wired or wireless connections between customer premises network
elements); network adapters are elements performing a L1/L2 conversion between different network
segments; nodes are network adapters with L3 routing capabilities.
"Multiple" Play Services (can be: double, triple, quadruple, etc.): delivery by a single service provider of different
types of concurrent services to one or multiple users within the same CPN. Services can be categorized in the following
way: data (e.g. Web browsing, best effort traffic etc.), person(s) to person(s) communication, entertainment
3.2 Abbreviations
For the purposes of the present document, the following abbreviations apply:
ACS Auto Configuration Server
AKA Authentication and Key Agreement
ALG Application Layer Gateway
A-MGF Access-Media Gateway Function
ARF Access Relay Function
ARP Address Resolution Protocol
ASF Application Server Function
B2BUA Back to Back User Agent
C-BGF Core Border Gateway Function
CLF Connectivity session Location and repository Function
ETSI
8 ETSI TS 185 006 V2.0.0 (2008-03)
CND Customer Network Device
CND Customer Network Devices
CND-A CND-client Application
CND-AtF CND-Attachment Function
CND-CMF CND-Configuration and Maintenance Function
CND-CSMF CND-Communication Services Media Function
CND-LAF CND-Local Authentication Function
CND-NTF CND-NAPT Traversal Function
CND-PPCF CND-Plug and Play Function
CND-SC CND-Self Configuration
CND-SF Customer Network Devices - Service related Functional entities
CND-SIP UA CND-SIP User Agent
CNG Customer Network Gateway
CNG-ACF CNG-Admission Control Function
CNG-AtF CNG Attachment Function
CNG-AuF CNG Authentication Function
CNGCF Customer Network Gateway Configuration Function
CNG-CMF CNG Configuration and Maintenance Function
CNG-CSMF CNG Communication Services Media Function
CNG-LF CNG Location Function
CNG-NFF CNG NAPT and Firewall Function
CNG-PCF CNG Policy Control Function
CNG-PPF CNG Plug and Play Function
CNG-UIF CNG User reference point Function
CPN Customer Premises Network
DB DataBase
DHCP Dynamic Host Configuration Protocol
FXS Foreign eXchange Subscribre
GUI Graphic User Interface
HG Home Gateway
IMS IP Multimedia Subsystem
ISDN Integrated Services Digital Network
ISIM IP Multimedia Services Identity Module
LAN Local Area Network
MG Media Gateway
NACF Network Access Configuration Function
NAPT Network Address and Port Translation
NAS Network Attached Storage
NASS Network Attachment SubSystem
NAT Network Address Translation
NBA NASS Bundled Authentication
NTF NAPT Traversal Function
P-CSCF Proxy Call Session Control Function
PDA Personal Digital Assistant
PES PSTN/ISDN Emulation Sub-system
PLC Power Line Communication
POTS Plain Old Telephone Service
PSTN Public Switched Telephone Network
RACS Resource and Admission Control Sub-system
RM Remote Management
SIP Session Initiation Protocol
SSID Service Set Identifier
STB Set Top Box
UA User Agent
UE User Equipment
UICC Universal Integrated Circuit Card
USIM Universal Subscriber Identity Module
VGCF Voice Gateway Control Function
WAN Wide Area Network
ETSI
9 ETSI TS 185 006 V2.0.0 (2008-03)
4 Customer Network Device classification
The Customer Network Devices connected to the Customer Premises Network can be of different types. The services
supported from each CND depends of the CND's type. In this clause a macro-classification is given. More in general, in
a customer premises network End Devices used by end user, Network Devices to support the CPN infrastructure and
Gateway Devices to connect the Customer Premises Network to the NGN are present.
End Devices:
The end devices can be divided into two main categories: non-IMS capable and IMS capable.
1) Non-IMS capable devices:
- non-IP device: It can be a POTS (Plain Old Telephone Service) phone that support traditional voice
services and STS (Supplementary Telephone Services) services. It can be connected to the NGN through
the CNG (e.g. in case of PSTN simulation services) or without the CNG (e.g. PSTN emulation services);
it supports the Z interface.
It can be a common ISDN phone supporting the S/T interfaces or also a DECT phone.
- IP device: It is a generic IP based device without any SIP stack. For example: PC, Personal Digital
Assistant (PDA), network printer, Network Attached Storage (NAS), IP-PBX.
In some cases IP devices, such as a PC or PDA, can evolve in a easy way to IMS capable devices.
- SIP Device:It is an IP device with a SIP stack not compliant with ES 283 003 [4] e.g. ietf based RFC
3261 [12]. For example Videophone, PDA, STB.
- Consumer Electronics: There are a number of consumer electronics equipment that can be connected to
the CPN and they can be IP based or not. Some examples are the Set Top Box (STB),gaming console,
Network Attached Storage (NAS). These devices in some cases do not need a connection with WAN side
and are used for Intra-Customer Environment services.
- Mobile Device: It can be a 2G/3G mobile device that take part into CPN through a wireless local access
(mobility enable) offered by CNG.
2) IMS capable device:
An IMS capable device is able to register with the IM CN via exchange of SIP messages with the P-CSCF, and
then create/accept/end multimedia IP sessions, in compliance with ES 283 003 [4]. The establishment of a trust
relationship to the IM CN shall be by one of the 3 methods defined in ES 283 003 [4] (by ISIM, or if that is not
present then by USIM, or if that is not present then by device-internal transmission of a private user identity, a
public user identity and a home network domain name).
For authentication issues, see also clause 6.
- Fixed device: It can be a fixed corded phone, dual mode phone (equipped with 2G/3G and
Wi-Fi/Bluetooth), PC, PDA (with IMS client soft phone), IP-PBX.
The dual mode phone (mobile + wireless) is considered as a fixed device when it is attached by
Wi-Fi/Bluetooth.
- Mobile device: It can be a mobile phone or a PC/PDA with 2G/3G interface.
- Consumer Electronics: They can be a STB, Media Servers or media players, etc.
Network Device:
It is a device that can be connected to the CPN infrastructure (e.g. network adapter and nodes as defined in clause 3).
ETSI
10 ETSI TS 185 006 V2.0.0 (2008-03)
Gateway:
CNG: It is the Customer Network Gateway to access the NGN side, as specified in TS 185 003 [6].
Table 4.1 classifies the customer devices in order to support the use case define in TS 185 005 [5]. Moreover the
CNDs are related to a number of possible local physical interfaces: FXS, Ethernet, Wireless (with or without
mobility), where mobility is defined as service and session continuity independently from the location.
In case of wired local access, both analogue and digital access are considered. Wired digital includes Ethernet and
other technologies.
In table 4.1 the "X" means that the CND may be able to support a service or that local physical interface.
Table 4.1: Customer Network Devices classification
Device Services CPN interfaces
Non IMS
capable
Non IP X   X X X
(e.g., POTS,
ISDN phone)
IP X  X X X
(e.g. PC, PDA,
IP-PBX, NAS,
Printer)
SIP X X X  X X X
(e.g.
VideoPhone,
PDA, STB)
Consumer X  X X X
Electronics
(e.g. STB,
gaming console,
NAS)
Mobile 2G/ 3G X X    X
Phone
IMS capable
Fixed X X X X X X X X X
(e.g. Fixed
phone, multi
mode phone,
PC, PDA (with
IMS client soft
phone),
IP-PBX)
Mobile (mobile X X X X X X  X
phone,
PC/PDA with
2G/3G itf
Consumer  X  X X X
Electronics
(e.g. STB, etc.)
The CNDs related to IP-TV are specified in TS 185 009 [20].
ETSI
Customer
Network
Device Type
Communi-
cation
service
Data service
Video
Streaming
Presence
Messaging
Intra-
Customer
Environment
Wired
analogue
Wired digital
Wireless not
enabling
mobility
Wireless
enabling
mobility
11 ETSI TS 185 006 V2.0.0 (2008-03)
4.1 Non IMS capable CNDs
4.2 Non-IP CNDs
The non-IP devices include the POTS phone and ISDN devices; these type of devices can be connected to the NGN
through the CNG or directly. In any case, the architecture of these devices is out of scope of the present document. The
voice services on POTS/ISDN devices can be done in emulation [1], [2] and [3] or simulation mode on NGN. In next
clause the impact on customer premises network is analyzed for both modes.
4.2.1 Non-IP CNDs connected to the NGN without a CNG
In this case the POTS and ISDN device is connected to the MG (Media Gateway) [3] via the Z interface for voice
services, as shown in figure 4.1. In case of data services, for ISDN device, the S/T interface is needed.
The case of voice services for POTS/ISDN in PES scenario is shown in figure 4.1

POT
MG
TISPAN PSTN/ISDN
Emulation Subsystem
Z
ISD
AGW
AG
S/T
Customer Premises
Network
Figure 4.1: Non-IP CNDs connected to the NGN network without a CNG (PES scenario)
The case of voice services for POTS/ISDN supported in the Core IMS scenario is shown in figure 4.2

POT
VG
IMS Core
Z Gm
ISD
VG
S/T
Customer Premises
Gm
Network
Figure 4.2: Non-IP CNDs connected to the NGN network without a CNG (Core IMS scenario)
4.2.2 Non-IP CNDs connected to the NGN through a CNG
In this case, the CNG includes all the CPN functionalities necessary to fulfill a service between the analogue or ISDN
phone and the NGN network. The voice services can be based on PES or Core IMS scenario. The details of CNG
architecture are specified in TS 185 003 [6].
ETSI
12 ETSI TS 185 006 V2.0.0 (2008-03)
POPOTSTS
IMIMIMSSS C C Cooorrreee
FXFXSS
ZZ
CNGCNG
GmGm
FXFXSS
CCuuststomeromer PPrremiemisseess
NeNetwtwoorrkk
Figure 4.3: Non-IP CNDs connected to the NGN network trough a CNG (Core IMS scenario)
POTPOTSS
TTIISPANSPAN PS PSTTNN//IISSDDNN
FXFXSS
ZZ EEmmulatulatiioonn SSubsubsyysstteemm
CNGCNG
aa
FXFXSS
CCuuststomomerer PrPremiemisseess
NeNetwtworkork
Figure 4.4: Non-IP devices connected to the NGN network trough a CNG (PES scenario)
In order to support the Z interfaces on FXS ports the CNG shall support protocol conversion as defined in
TS 185 003 [6].
4.3 IP CNDs
These devices are able to get IP connectivity within the CPN, but they are not implementing the RFC 3261 [12]
functionalities to manage signalling. This can be a communication device non compliant with RFC 3261 [12], but also
devices not specifically devoted to communication services (for example: webcam with HTTP server, general purpose
PC, etc.).
4.4 SIP IETF capable CNDs
4.4.1 Non-IMS SIP CND connected to the NGN through a CNG
A non-IMS SIP IETF device shall utilize the G ' reference point (instead of the G reference point that is utilized by
m m
IMS capable devices) in order to get a service from NGN-IMS. See figure 4.5.
ETSI
13 ETSI TS 185 006 V2.0.0 (2008-03)

Figure 4.5: SIP IETF CND connected to the NGN-IMS network through a CNG
4.5 Consumer Electronics
These types of CNDs are out of scope. The case of CND correlated to IPTV is detailed in TS 185 009 [20].
4.6 IMS capable CNDs
4.7 IMS Customer Network Device connected to the NGN
through a CNG
In this case, the Customer Network Device includes all the service-related functionalities necessary to fulfill a service
between itself and the NGN-IMS network, as shown in figure 4.6. The CNG offers the capabilities to support
attachment and transport in case of IMS customer device connected via Wi-Fi/Bluetooth, Ethernet port (wired) or femto
cell (for mobile devices).
ETSI
14 ETSI TS 185 006 V2.0.0 (2008-03)

Figure 4.6: IMS CND connected to the NGN-IMS network through a CNG
4.8 Consumer Electronics
The definition of consumer electronics architecture is out of scope for the present document. The architecture of CND
involved in IPTV services are covered in TS 185 009 [20]
4.9 IMS customer network device architecture
In the following clause a detailed description of the entities on figure 6 is given.
4.9.1 The Customer Network Devices- Network Attachment Subsystem
entities (CND-NASS)
CND-CMF: Customer Network Device - Configuration and Management Function.
The CND-CMF entity shall enable the configuration of CND based on data obtained from the CNGCF. The CNG-CMF
(in CNG) should be able particularly to store configuration information dedicated to several CNDs, after sending only
one request to the CNGCF. As soon as one CND is connected, the CNG-CMF should be able to deliver configuration
parameters to it is CND-CMF. Otherwise the CND-CMF can be directly accessed by the CNGCF without the CNG
mediation.
The CND-CMF shall manage a mutual authentication between the CNGCF and the CND.
The CND-CMF shall enable the CND configuration and firmware upgrade.
The CND-CMF shall access the credential keys for authentication (via ISIM or stored parameters received from CNGF
e.g. for HTTP digest).
The CND-CMF should provide, for example, the functionality and interfaces of a DSL Forum Auto Configuration
Client [8].
ETSI
15 ETSI TS 185 006 V2.0.0 (2008-03)
Finally, the CND-CMF should allow device maintenance from the NGN network, through the CNG-CMF, with the
opportunity to do diagnostic and performance tests too.
Some authentication parameters may be stored in a UICC (containing the ISIM).
CND-AtF: Customer Network Attachment Function.
The CND-AtF entity shall store the private or public IP addresses sent by CNG-AtF or NASS (e.g. a DHCP client).
CND-LAF: Customer Network Device - Local Authentication Function.
The CND-LAF shall manage local authentication procedure to the CPN environment. For instance, a CND requesting
for a CPN Wireless attachment should be authorized by the access point embedded in the CNG.
In order to ask for local authentication the CND-LAF interacts with the CNG-AuF.
The CNG-AuF can thus be configured by the user for such a case, by using the CNG User Interface Function (CNG-
UIF).
4.9.2 The transfer level functions
CND-NTF: NAPT Traversal Function
The function shall allow the CNG-NFF (in CNG) traversal (as detailed in the TR 187 008 [22]) and particularly
maintain the binding between the SIP UA and the P-CSCF/C-BGF. The CND-NTF should also supply the SIP UA with
the mapping made by the CNG on the NGN side so as to fill the SDP field of SIP messages sent by the CND.
4.9.3 The transport level functions
CND-CSMF: Customer Network Device-Communication Services Media Function
The CND-CSMF shall terminate the media flows.
In some cases the media flows may be encrypted.
4.9.4 The Customer Network Devices - Service-related Functional entities
(CND-SF)
CND-SIP UA: Customer Network Device SIP UA
This block shall implement the G reference points on IMS customer devices. This SIP UA shall perform the service
m
authentication and manage signaling flows securely.
CND-A: Customer Network Device Client Application
At least one CND-A shall be installed on CND to support a service. There can be on or more CND-As depending on the
applications installed over CND. It is a client specific for application. This client can implement local application or
network services through the use of SIP UA.
CND-SC: Customer Network Device Self Configuration
This functionality is optional. It implements the U reference point; the U enables the access to an Application Sever to
t t
support the user in configuration updates related to services.
CND-PPCF: Customer Network Device - Plug and Play Function
The CNG-PPF in the CNG may obtain some device information (service discovery, description) and allow their control
from the CND-PPF. Particularly, the CNG-PPF entity may allow a communication between many types of Customer
Device within the CPN, not only conversational (based UPnP for instance).
ETSI
16 ETSI TS 185 006 V2.0.0 (2008-03)
5 Reference Points
5.1 Network attachment reference points
'
e ': The e reference point is defined between the CND and the CNG-AtF. The CNG-AtF provides IP addresses
1 1
(IPv4 or IPv6 format) to the CND through the CND-AtF, it may also send some configuration information for
the CND (typically through DHCP options).
The CND and CNG shall mutually exchange their hardware identities (e.g. MAC address, DeviceID, etc.) on
'
e reference point. The CNG has to know which CNDs are behind itself within CPN and each CND has to
know its CNG.
This reference point is mandatory if the CNG runs in a routed mode.
' '
e : The e reference point is defined between the CND and the CNG-CMF. The CNG-CMF may provide the
3 3
CND with parameters that are pre-configured in the CNGCF and sent to the CNG through the e reference
point or, as an alternative, directly defined by the user. The CNG-CMF also configures the CNG, using
information received from the CNGCF or supplied by the user himself.
The CNG-CMF also configures the CNG, it can also be provided by the CNGCF or the user himself.
Finally the CND-CMF should provide information on device status to allow the CNGCF to make some
diagnostic and performance tests through the CNG-CMF.
'
To sum up, the e reference point support a variety of functionality to manage a collection of user equipment
(CNG/CNDs), including the following capabilities:
- auto-configuration and dynamic service provisioning;
- software/firmware management;
- status and performance monitoring;
- diagnostics.
This reference point is recommended as the e reference point could also be used" with "This reference point is
recommended as integration of the mandatory e interface described below.
In order to simplify the management functions on the CNG, the e reference point can be implemented directly
between CND and CNGCF as specified in ES 282 004 [14]. In this case, the direct reference point between
'
CND and CNG, e , could be limited to service provisioning functions; this may be required in addition or as
an alternative to the corresponding functionalities on the e reference point between CND and CNGCF.
a : The a reference point is defined between the Customer Network Device and the CNG-AuF. There may be two
u u
types of authentication/authorization, according to:
CPN pairing (attachment, encryption and security processes (WEP, WPA2, …)) based on specific CPN
technologies (e.g. Wife SSID, PLC technology).
Access rights for some LAN services like the CNG Configuration (through the CNG-UIF).
This reference point is recommended, except if a wireless access point is embedded in the CNG in which case
it is mandatory.
e : This reference point is based on TS 183 019 [15].
The e reference point is dedicated to the network attachment of the User Equipment.
The e reference point is mandatory (in coherence with WG2 specifications).
ETSI
17 ETSI TS 185 006 V2.0.0 (2008-03)
e : This reference point is based on the ES 282 004 [14]:
The e reference point is defined between the CNG-CMF and the CNGCF and should be extended also
between the CNG-CMF and the CND for configuration purposes.
Through a remote management protocol it is possible to support a variety of functionalities to manage a
collection of user equipment (CNG/Customer Network Devices), including the following capabilities:
- auto-configuration and dynamic service provisioning;
- software/firmware management;
- status and performance monitoring;
- diagnostics.
The e implementation between the CNG-CMF and the CNGCF is mandatory (in coherence with WG2
specifications), whereas the e implementation between the CNG-CMF and the CND-CMF is recommended,
'
as e should be an alternative.
5.2 Transport level reference points
D : The D reference point is responsible for the exchange of media flows between the User Equipment (CNG or
j j
CND) and the C-BGF.
This reference point is mandatory. It is based on the ES 282 001 [16].
5.3 Service layer reference points
G : The G reference point supports the communication between UE and the IMS, e.g. related to registration and
m m
session control.
G between the P-CSCF and the SIP proxy B2BUA) is used to support several actions:
m
- send SIP messages to/from the NGN;
- call forking at the CNG level.
The protocol used for the G reference point is SIP.
m
To be noticed that the definition is extracted from the ES 282 007 [13].
This reference point is in line with specifications:
- ES 283 003 [4]
- TS 182 012 [3]
- TS 131 103 [17]
This reference point is mandatory (in coherence with WG2 specifications).
' '
G : The G reference point supports the communication between one CND and the CNG, e.g. related to
m m
registration and session control.
'
The difference between G and G is related to the conformance to the IMS and to the need to go through the
m m
'
B2BUA to support local services. Further details about G possible implementations can be found in the
m
TR 185 007 [23].
This reference point is recommended (it shall be used in case a SIP B2BUA is implemented inside the CNG).
ETSI
18 ETSI TS 185 006 V2.0.0 (2008-03)
U : The U reference point enables the user to manage information related to his services, such a creation and
t t
assignment of Public Service Identities, management of authorization policies that are used e.g. by Presence
service, conference policy management, etc.
This reference point is in line with the specification ES 282 007 [13].
This reference point is optional (in coherence with WG2 specifications, see [13]).
u: The u reference point gives the possibility to one or several users authorized (via the CNG-AuF) to have
access to the CNG Configuration, through the CNG-UIF. The liaison should be as secure as possible (using
HTTPs for instance).
This reference point is recommended.
C: The C reference point is defined between the CNG-PPF and the CND-PPF.
It provides some CND information (service discovery, description) to the CNG and allow its control.
Also, a communication between many types of Customer Network Device within the CPN may be established
through the C reference point, using UPnP for instance.
This reference point is optional.
6 Authentication issues
This clause is related to the authentication method used by customer network devices for registration and authentication
on IMS core. The target authentication method is IMS AKA authentication based on ISIM/UICC, but in coherence with
TS 187 001 [21] there are other two methods to be considered: HTTP Digest and NBA.
For that reason in the present document customer network devices, without UICC, that support HTTP Digest and NBA
are considered as early deployments.
In these case of HTTP Digest or NBA a CND R2 shall be able to provide it is private and public identity in every
method that requires authentication (e.g. REGISTER) in order to support shared public identity for multi device use
case (shared IMPU). The CND that does not support this feature can be extended through a CNG.
In order to clarify the concept of early deployments some schemas are presented.
6.1 CNG based
In case of CNG in the CPN, the CNG can be add the private identity in the Authorization Header ES 283 003 [4], if
needed, both for HTTP Digest and NBA authentication method.
ETSI
19 ETSI TS 185 006 V2.0.0 (2008-03)
HtHtttpp Di Diggeesstt
R2R2
RREEGGIISTSTERER((((IIMMPUPU,, I IMMPIPI,,
CNDCND
AAuuththororizizationation hhead. mead. maannddatatorory)y)
IIMMSS cap capabablele
401 U401 Unnautauthorhorizedized
NGNNGN
(ea(earrllyy dedeplplooyy))
((CChhaalllleengngee nnononccee ……))
CNGCNG
RREEGISGISTTEERR (IM (IMPPUU,, IM IMPPI, rI, respesponseonse ……))
AAuuthth HtHtttpp Di Diggeesstt
200 OK200 OK
RREEGGIISTSTERER HHttpttp D Diiggestest
RREEGGIISTSTERER
(l(lococaall SISIP URP URII))
(IM(IMPPUU,, IM IMPPII,,
HttHttpp Di Diggeesstt
CCNNG adG addd AAuthuthoorriizzaationtion hhead.)ead.)
CNDCND
CNGCNG
401 U401 Unnauauththororizedized (C(Challenghallengee nonnonce)ce)
NNoon IMn IMS capS capabablele
NGNNGN
SISIP PrP Proxoxyy
SISIP IEP IETFTF
RREE
...