Seminar on ITU-T hot topics for
Standardization
(Mar del Plata, Argentina, 2 September 2009)
Access to NGN
Olivier Le Grand
WP3/13 chairman,
France Telecom
Mar del Plata, Argentina, 2 September 2009
International
Telecommunication
Union
Access to NGN: introduction
"Access to NGN" may imply several form/level of "access":
Access to "NGN transport network":
Authentication and authorization of user for network access
(e.g., authentication and authorization of an end user device, a
home or enterprise gateway to obtain access to the network)
Access to "NGN services":
Authentication and authorization of user for access to NGN
services/applications (e.g., authentication and authorization of
an user, a device or a combined user/device where the
authentication and authorization apply to NGN
services/applications access)
Access to a specific "NGN service/application"
Each service/application may have its own assurance level
requirement to validate the identity and privileges of a user, user
device or user and device combination
Note that access to "NGN transport network" and "NGN services" may
in some cases be coupled: "bundled" case
This presentation will mainly focus on access to "NGN
transport network", also referred as "Network
attachment".
Mar del Plata, Argentina, 2 September 2009
International
Telecommunication
Union
2
Access to NGN: general view
Services
WEB
VoD
ASP
ASP
Network
Network
MMS
SIP
E911
PSAP
IMS
Network
NGN Core (IP)
Transport
Wi-Fi
DSL
/FTTH
Cable
GSM/
UMTS
/…
PSTN
Access
User
Mar del Plata, Argentina, 2 September 2009
International
Telecommunication
Union
3
ITU-T general requirements (Y.2201)
It is an ITU-T NGN objective to support services and
applications independently of the access network
technologies. Thus:
1) NGN is required to support diverse access transport
technologies.
2)The transport stratum is required to be capable of providing
IP connectivity between the end-user functions and core
transport functions
For the services to which mobility is appropriate:
1) NGN is required to provide nomadism for personal mobility
and terminal mobility
2) NGN is recommended to provide support for handover and
seamless handover which realize service continuity for InterAN (access network) and Intra-AN scenarios. Service continuity
includes Service continuity on the same terminal and Service
continuity on different terminals;
Roaming:
An access network is required to be able to authenticate and
authorize access by a user roaming on this access network from
another access network.
International
Mar del Plata, Argentina, 2 September 2009
Telecommunication
Union
4
NGN functional components (Y.2012 Rev1)
"Service delivery
platform" making
use of NGN easily
(OSE +SIDE)
Applications
Service Stratum
IP-based
mobility
(Rec Y.2018)
Application Support
Functions and
Service Support Functions
Application
Functions
S. User
Profile
Functions
Network
attachment
(Rec Y.2014)
IP Multimedia
Component
IP Multimedia
&PSTN/ISDN Simulation
Legacy
Terminals
Legacy
Terminals
Customer
Networks
NGN
Terminals
Service Component
GW
GW
T. User
User
Profile
Profile
Functions
Functions
Network Attachment
Control Functions
(NACF)
AccessTransport
Network
Access
Functions
Functions
End-User
Functions
Mar del Plata, Argentina, 2 September 2009
Mobility Management
and Control Functions
(MMCF)
Edge
Functions
Resource and Admission
Control Functions
(RACF)
Core
Transport
Core
transport
Functions
Functions
Transport Stratum
Other Networks
Other NGN Service
Components
IPTV
Service Component
PSTN / ISDN Emulation
Service Component
Provision of IPTV
services
Service
(cf. Y.1910)
Control
And
Delivery
Evolution
Functions
scenario of PSTN
and short-term
solution (Y.2031)
Adaptation of
3GPP IMS to
provide
multimedia
services
(Rec Y.2021)
A unified IP
network with
improved security
and QoS
(Rec Y.2111)
International
Telecommunication
Union
5
Role of NACF (Rec. Y.2014)
Control the attachment to the NGN
Dynamic provision of IP address and other user
equipment configuration parameters (e.g. using
DHCP).
User authentication, prior or during the IP address
allocation procedure.
Authorization of network access, based on user
profile.
Access network configuration, based on user
profile.
Location management at the IP layer.
Mar del Plata, Argentina, 2 September 2009
International
Telecommunication
Union
6
NACF functional architecture (Y.2014)
Service Control Functions
S-TC1
NACF
HGWC-FE
Ni
TC-Ux
Ng
Nx
TLM-FE
Nc
Nb
TAA-FE
Nk
Na
TC-TC1
PD-FE
Ne
NAC-FE
Other NGNs
TUP-FE
RACF
Nd
AM-FE
TC-T1
TE
HGW
CPE
T-U1
AR-FE
Mar del Plata, Argentina, 2 September 2009
PE-FE
Transport Functions
International
Telecommunication
Union
7
ITU-T NACF (Y.2014)
Ideally, ITU-T NACF should be "access technology agnostic" and
should make service providers agnostic to the details of transport
facilities
However, ITU-T NACF is focusing on the fixed-network (xDSL,
FTTH,..).
It was designed in harmonization with ETSI TISPAN NASS
See back-up slide for a high-level mapping between both architectures
But does not cover network attachment (see back up slide) for e.g.:
Mobile networks (such as 3GPP and WiMax networks)
Cable
No common/generic solution since intrinsically different access
technologies but also studied in different SDOs
ITU-T NACF can operate with ITU-T MMCF (Mobility Management
and Control Functions) to provide IP based mobility:
Can be viewed as a way of introducing mobility support in "fixed"
networks
But lacking overall "harmonization" with "mobile architectures" (e.g.
3GPP SAE/EPC)
Similar issue of harmonization between fixed and mobile architectures
exist regarding Resource and Admission Control (RACF)
Mar del Plata, Argentina, 2 September 2009
International
Telecommunication
Union
8
Other issues related to NACF (Y.2014)
Harmonization of inter-domain roaming interfaces
between ITU-T, ETSI TISPAN and 3GPP for
supporting:
Authentication
Location Updating
Profile downloading
Key inter-domain reference points
ITU-T NACF Ni / ETSI NASS e5
ITU-T NACF Ru / ETSI NASS e4
ITU-T NACF Ng /ETSI NASS e2
Mar del Plata, Argentina, 2 September 2009
International
Telecommunication
Union
9
Identity Management (IdM) functions
in the NGN
Applications
ANI
Management Functions
Application Support Functions & Service Support Functions
Service User
Profiles
Service Control
Functions
Service stratum
Network Attachment
Control Functions
Transport User
Profiles
End-User
Functions
Resource and
Admission
Control Functions
Other
Networks
Transport Control Functions
Transport Functions
NNI
UNI
Transport stratum
Mar del Plata, Argentina, 2 September 2009
Control
Media
Management
International
Telecommunication
Union
10
IdM functions in NGN (under study)
Application Services
AS-FE
IC-AS
E-FE
IC-E
IdMC-FE
IC-C
IdMC-FE
IC-S
S-FE
IC-T
T-FE
Mar del Plata, Argentina, 2 September 2009
IC-C Reference Point
Between IdM Coordination
Functional Entity (IdMC-FE)s
IC-AS Reference Point
Between IdMC-FE and Application
Support Functional Entity (AS-FE)
IC-S Reference Point:
Between IdMC-FE and Service
Stratum Functional Entity (S-FE)
IC-T Reference Point:
Between IdMC-FE and
Transport Stratum Functional
Entity (T-FE)
IC-E Reference Point:
Between IdMC-FE and End User
Functional Entity (E-FE)
International
Telecommunication
Union
11
IdM functions and NACF (Y.2014)
IdM functions and NACF relationship (and more
generally NGN components involved in "access to
NGN") needs further study
NACF issues to be looked at include:
Identify IdM-related FEs in NACF
The IdMC-FE may interact with the following functional entities
within the NACF of Transport Stratum via the IC-T Reference
Point:
T-10
T-11
T-12
T-13
T-14
Network access configuration functional entity (NAC-FE)
Transport authentication and authorization functional entity (TAA-FE)
Transport user profile functional entity (TUP-FE)
Transport location management functional entity (TLM-FE)
Access management functional entity (AM-FE)
Information flows between related entities to be studied
Mar del Plata, Argentina, 2 September 2009
International
Telecommunication
Union
12
Thank you!!!
Mar del Plata, Argentina, 2 September 2009
International
Telecommunication
Union
13
ITU-T NACF/ ETSI NASS high-level mapping
Service Control Functions
e2
NACF
CNGCF
HGWC-FE
e3
Ni
e5
UAAF
a4
Nc
Nb
TAA-FE
a3
Ng
Nx
TLM-FE
Nk
Na
Ne
NAC-FE
a2
a1
Nd
e2
e4
TC-TC1
CLF (Ru)
PD-FE
NACF
Other NGNs
TUP-FE
RACF
e2
PBDF
TC-Ux
S-TC1
AM-FE
TC-T1
TE
HGW
CPE
e1
T-U1
AMF
e1
AR-FE
ARF
Mar del Plata, Argentina, 2 September 2009
PE-FE
Transport Functions
International
Telecommunication
Union
14
Network attachment solutions
ITU-T
NACF
3GPP/SAE
ETSI
TISPAN
NASS
WiMax
NAC-FE
PDNGW(DHCP)
NACF
TAA-FE,
TUP-FE
MME
(identification,
authentication
/key
agreement),
HSS (HLR),
AuC
UAAF, PDBF,
ASN-GW
UPSF
Location
Management
TLM-FE
MME
(tracking/
routing area
management)
Remarks
For only
fixed
networks
Configuration
Authentication
&
Authorization
-
CLF
For only
fixed
networks
DHCP (w/
ASN-GW)
Cable
DHCP
KDC,
DPS,
CMTS
LA (in
MN/BS)
LC (in
ASN-GW)
-
-
No common solution since each SDO is working on a
different access and transport technologies
Mar del Plata, Argentina, 2 September 2009
International
Telecommunication
Union
15