FORUM ON NEXT GENERATION STANDARDIZATION
(Colombo, Sri Lanka, 7-10 April 2009)
Requirements and capabilities for
an evolving NGN infrastructure
Marco Carugi
ITU-T SG13 WP2 co-chair and
Q.3/13 Rapporteur
Senior Advisor, Nortel Networks
FRANCE
marco.carugi@nortel.com
Outline
o
Requirements and capabilities of an evolving NGN
infrastructure in some key technical domains
•
•
•
•
•
•
o
Architecture
QoS
Mobility
Security and Identity Management
Interconnection
Accounting and charging
NOTE: presentation focused on ITU-T SG13 work (but
NGN related deliverables have been developed in
various Study Groups)
Colombo, Sri Lanka, 7-10 April 2009
2
Y.2012: basic functional view
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
UNI
Control
Transport stratum
Colombo, Sri Lanka, 7-10 April 2009
NNI
Media
Management
3
Applications
Service Stratum
Application Support
Functions and
Service Support Functions
Application
Functions
A “NGN
components”
view
S. User
Profile
Functions
Other NGN Service
Components
Service
Control
Functions
IP Multimedia
Component
IP Multimedia
&PSTN/ISDN
Simulation
Service Component
GW
Legacy
Terminals
Legacy
Terminals
GW
Network Access
T.User
User Network Attachment
Control Functions
Profile
ProfileAttachment
Functions
(NACF)
Functions
Functions
Customer
Networks
NGN
Terminals
Access
Access Network
Transport
Functions
Functions
Edge
Functions
Resource and Admission
Control Functions
(RACF)
Other
Networks
Other Networks
PSTN / ISDN Emulation
Service Component
Core
Transport
Core
transport
Functions
Functions
Transport Stratum
End User
Functions
Colombo, Sri Lanka, 7-10 April 2009
4
Y.2201 : NGN Release 1 Requirements
and Capabilities
o Scope of Y.2201
• High level requirements and capabilities to support NGN Release
1 service objectives
NOTES:
• Rel.1 addresses only NGN “network capabilities” (no user equipment)
• Service-specific requirements are out of scope
• Each NGN realisation may use an arbitrary set of services & capabilities
o The NGN Capabilities identified in Y.2201
• Derived essentially from functionalities already developed in various
technical bodies and considered ready for use in Rel.1 time frame
• Described in terms of requirements (but these are not precise
“Functional Requirements” for specific NGN entities)
• Providing guidelines for the NGN architecture work so that the specified
architecture FEs are able to support these capabilities and associated
requirements (architecture FEs and related protocol specifications)
o Y.2201 NGN Release planned for approval in Q2-Q3 2009
Colombo, Sri Lanka, 7-10 April 2009
5
IMS (IP Multimedia Subsystem)
o 3GPP IMS subsystem
• Provision of call processing and a variety of multimedia services in
an IP-based packet-switching domain
• Compliance with IETF standardized session control (SIP); profiling
• Unique features of SIP for interactive end-to-end communications
• Voice, video, presence, messaging, conferencing and others
• Independence from Access Network
• Application platform itself is outside the scope of IMS
Application platform
IMS (SIP)
IP transport network
(IP-CAN)
Colombo, Sri Lanka, 7-10 April 2009
6
The central role of 3GPP IMS
in NGN Release 1 Architecture
o Advanced Architecture objectives
• Comprehensive set of services over a unifying IP layer network
• Services separable from transport stratum into service stratum
• Transport stratum support of a multiplicity of access networks
and a variety of mobile and fixed terminal types
• Services not limited to those provided by the “home network”
• Services shall be able to traverse multiple providers’ networks
o About IP Multimedia Subsystem (IMS) in NGN
• IMS was unanimously agreed as central component in NGN
• Leveraging the 3GPP IMS capabilities
— but they need some extensions
— other functions still needed
• Y.2012 (NGN Rel.1 functional requirements and architecture)
• Y.2021 (IMS for NGN)
Colombo, Sri Lanka, 7-10 April 2009
7
Instantiation of NGN reference points –
Appendix III Y.2012
Applications
Applications
Applications
ANI
Service
termination
Transport
termination
Service
Transport
End-user functions
(including enterprise
networks)
UNI
Service
termination
Transport
termination
SVI: Server to
network interface
Transport
NNI
Service
Transport
Transport
End-server
functions
Other
networks
Service
Service
Transport
Transport
Y.2012(06)Amd1_FIII.1
Colombo, Sri Lanka, 7-10 April 2009
8
Key architectural challenges
o Application-driven QoS:
•
•
•
•
QoS classes
Explicit bandwidth selection
Mapping & Control from Service to Transport
Flow awareness (monitoring, accounting)
o Mobility
• Seamless handover
• Fixed Mobile Convergence (FMC)
o Scalability
• Multicast
• Ubiquitous networking
Colombo, Sri Lanka, 7-10 April 2009
9
“Ubiquitous networking” as a future target
o Which capabilities to enable “Any Service, Any Time,
Any Where, Any Device” operations using NGN
o Human-to-human, but also human-to-machine and
machine-to-machine communications
o “Draft” definition of ubiquitous networking [Y.NGNUbiNet]
• Ability for all of objects to communicate and access services
without any restrictions at services, places, time, users, etc.,
in the context of the service(s) subscribed to
o Y.NGN-UbiNet - Overview and principles for ubiquitous
networking in NGN (work just started)
• Objectives of ubiquitous networking in NGN, fundamental
characteristics and design principles including architectural
model and enhanced capabilities
Colombo, Sri Lanka, 7-10 April 2009
10
Quality of Service (QoS)
High level objectives in NGN Release 1
o End-to-end QoS environment for the services offered to end users
via QoS coordination across the transport stratum
o NGN Release 1 shall provide an initial set of requirements,
architectures, mechanisms and guidelines to enable end-to-end QoS
Key items under study
o Dynamic QoS controls, including
• Resource and admission control
• Negociation of QoS requirements
• Interworking of QoS mechanisms
• Inter-domain considerations
• Frameworks aspects
o Performance objectives
• Network performance classes and allocation
o Performance measurement, management and prediction
Aiming to develop a comprehensive QoS solution allowing
incremental
deployment
Colombo,
Sri Lanka, 7-10 April
2009
11
Resource and Admission Control Functions (RACF)
o Application-driven, policy-based resource management
o Bridging service control and packet transport to dynamically
guarantee QoS and enforce certain network security measures
• QoS coordination in transport stratum through Access Network,
Core Network and other NGNs
• Different modes for policy control
• Different resource management methods measurement,
reservation
• Endpoints of various QoS control capabilities
• Relative and absolute QoS, including priority
• Existing and emerging QoS transport mechanisms
Colombo, Sri Lanka, 7-10 April 2009
12
Generic RACF architecture in NGN – Y.2111
Service Control Functions
Service Stratum
Transport Stratum
RACF
Rs
Rd
Ru
Rp
TRC-FE
Rh
Rn
Rc
PD-FE
Rt
Ri
Other NGNs
Network
Attachment
Control
Functions
Rw
CGPE-FE
TRE-FE
CPN
o
o
o
o
PE-FE
Transport Functions
Decomposition of PD-FE (Policy decision functional entity) and TRC-FE (Transport
resource control functional entity) enables RACF to support a variety of access and
core networks (e.g. fixed and mobile access networks) within a general resource
control framework.
PE-FE (Policy enforcement functional entity), packet-to-packet gateway at the
boundary of different packet networks and/or between the CPN and access network,
is key injection node to enforce dynamic QoS and resource control, NAPT control
and NAT traversal.
CGPE-FE (CPN Gateway Policy Enforcement Functional Entity) in CPN enforces
transport policy rules for upstream traffic instructed by PD-FE.
TRE-FE (Transport resource enforcement functional entity) enforces transport
resource policy rules instructed by TRC-FE at the technology-dependent aggregate
level.
Colombo, Sri Lanka, 7-10 April 2009
13
QoS challenges in customer premise network
Desktop
PC
Network
Terminating 10/100
Base-T
Unit
Home
Gateway
Desktop
PC
Customer
Premise
Network
Set Top Box
Television
Other
Devices,
Appliances,
etc
Set Top Box
Television
….
….
….
….
IP
phone
Home Gateway issues and QoS per device/terminal
Colombo, Sri Lanka, 7-10 April 2009
14
Mobility: a fundamental enabler of NGN
Complex and
heterogeneous
environment
Basic User Requirements
• Access from a variety of environments with a variety of
terminals with varying capabilities
• Global roaming, and ubiquitous and seamless solutions
Colombo, Sri Lanka, 7-10 April 2009
15
Mobility domains and types - Y.2011
Device mobility domain
User/service
mobility domain
Network
Points of attachment (POA)
Telecommunications objects (mobile with transient binding to POA)
Transient binding (mobile with transient binding to device/service)
Colombo, Sri Lanka, 7-10 April 2009
16
Other dimensions of mobility
Mobility
Service continuity
Seamless Handover
Service discontinuity
Handover
Nomadicity
Portability
Q.1706/Y.2801
Colombo, Sri Lanka, 7-10 April 2009
17
Limited Mobility objectives
in NGN Release 1
o NGN Release 1 shall support “Nomadism”
• “The ability to change network access point on
moving, without maintaining service continuity”
• To be supported between networks and within a network
• But support for service continuity is not excluded
o No new interfaces defined for Release 1 mobility
• Personal mobility
• Terminal Mobility
The initial step towards
Generalized Mobility and Fixed Mobile Convergence
Colombo, Sri Lanka, 7-10 April 2009
18
MM functional architecture – Q.1707/Y.2804
o Mobility management control function (MMCF) model
o MMCF functional architecture in NGN
Colombo, Sri Lanka, 7-10 April 2009
19
Example of MMCF network configuration –
Q.1707/Y.2804
Initial step of detailed functional mapping within the NGN
architecture framework is currently progressing in Y.MMCF
o Architecture and functional requirements for management of logical
location information and control of mobility in NGN transport
stratum
Colombo, Sri Lanka, 7-10 April 2009
20
Towards Fixed Mobile Convergence:
but which convergence ?
The multiple dimensions of convergence
• Converged services
• Service integration (voice and
multimedia, messaging, presence etc.)
Mobile
Network
• Converged service platform
• Converged networks
• Access and core, incumbent and
competitive, wireline or wireless,
VNO, ISPs and Broadband SPs
Fixed
Network
• Converged devices
•
Phones, smartphones, PDAs, laptops, …
IP
Network
Cable
Network
Corporate
Network
• Converged management
• Seamless service provisioning
Colombo, Sri Lanka, 7-10 April 2009
21
Functional scenarios of convergence - Q.1762/Y.2802
Management
Layer
Charging and
Billing Functions
Applications
Application
Layer
Application
/Service Support
Functions
Service Control
Functions
Control
Layer
Service Control
Functions
Fixed
Networ
k
Example of
convergence at
Application/Service
Support Functions
Mobile
Network
Fixed access
network
Mobile access
network
Convergence may be happen at different functional levels
Y.2802: FMC characteristics, requirements, capabilities and scenarios
Colombo, Sri Lanka, 7-10 April 2009
22
Security
Security objectives
o Address security dimensions
o Address security features required for secure domain interconnection
Security Requirements for NGN Release 1 (Y.2701)
o Security dimensions and countered
o
o
o
o
threats (ITU-T X.805 principles)
Security threats and risks in NGN
Security trust models
Security architecture
Security objectives
o Requirements of NGN
network elements
• Common requirements
• In Trusted Zone
• Network border elements
• CPE border elements
o Objectives and reqts for
Emergency Telecom. Services
Other security topics:
o NGN Authentication and authorization requirements (Y.2702)
o AAA service in NGN (Y.2703)
o Ongoing: NGN Certificate Mgt, NGN Security mechanisms and procedures,
Mobility security framework in NGN, Secure solutions for mobile commerce
and banking
o Identity Management
Colombo, Sri Lanka, 7-10 April 2009
23
Security of financial transactions – future item
Security solutions supporting scenarios where
o
•
•
a mobile terminal serves as a payment or banking
terminal, and
NGN is used as transport to carry transaction flows
Related security issues include
o
•
network and interface functions to support transaction
protection, privacy policy, financial infrastructure
protection, subscriber protection and identity
management aspects
Planned draft Recommendations
o
•
•
“Security requirements for mobile financial transactions
in NGN”
“Architecture for secure mobile financial transactions in
NGN”
Colombo, Sri Lanka, 7-10 April 2009
24
Identities are not needed only for “Users”
o The figure below shows examples of identities mapped
into the NGN architecture
• Identities for devices, network elements, network components,
applications, service providers etc.
Identities in
applications
A p p lic a tio n s
S e r v ic e S tr a tu m
User
Identity
Data
A p p lic atio n S u pA
p oprtpFlic
u n ctio
n duSnecrvtio
icenSsu p p o rt F u n c tio n s
a tion sna F
S . U se r
P ro file
F u n ctio n s
Identities
in NACF
O th er N G N S e rvic e
C o m p o n e n ts
S e rv ic e
C o n tro l
F u n ctio n s
IP M u ltim
ed u
ialtim
C om
onent
IP M
e dp ia
& PSSeTrv
N /IS
N oSmimpuola
ic eDC
n etiontn
Legacy
T e rm ina ls
L egacy
T e rm in a ls
GW
N
c ech
ssm e n t
N eetw
tw oork
rk A
A ctta
T . UUse
ser
r
l F u nctio n s
PProrofile
file A tta cChomnetro
n
t
F
u
nctio
(N A C F ) n s
ctionnss
FFuunnctio
GW
C u sto m er
N e tw o rk s
User and
terminal
identities
A
c ce
ssTN
A cc
ess
raetw
n sp oortrk
FFuunnctio
ctio nnss
NGN
T e r m in als
Edge
F u n ctio n s
R e so u rc e a n d A d m is sio n
C o n tro l F u nctio ns
(R A C F )
*
Identity
Interoperability
Identities in
RACF
C oCreo re
traTnra
spnosp
rt o rt
F
u
n
c
tio
n
F u n c tio n s s
T ra n sp o rt S tra tu m
E n d -U ser
F u n c tio n s
Other Networks
P S T N / IS D N E m u la tio n
S e rv ic e C o m p o n e n t
Identities in IMS
PES, and other
components
Network elements
identities
N o te : G a te w a y (G W ) m a y e xis t in e ith e r T ra n s p o rt S tra tu m
o r E n d -U s e r F u n c tio n s .
Colombo, Sri Lanka, 7-10 April 2009
25
Identity Management (IdM): a key ongoing activity
o Working definition for IdM (Q.16/13)
• “Management by NGN providers of trusted attributes of an entity
such as a subscriber, a device or a provider”.
This is not intended to indicate positive validation of a person.
o Challenges of identity information assurance, security and
management
• End users are increasingly using multiple identities
• These identities may be associated with differing contexts and
service privileges
• The identities may only partially identify the end user
• The identities may be used anywhere, anytime
• The identities may not be interoperable between providers
Colombo, Sri Lanka, 7-10 April 2009
26
NGN Identity Management framework - Y.2720
o A structured approach for designing, defining, and
implementing interoperable Identity Management
(IdM) solutions for NGN
o Y.2720 identifies a set of capabilities
• e.g., administration, discovery, communication
exchanges, correlation and binding, policy
enforcement, authentication and authorization
o These capabilities
• allow assurance of identity information (e.g.,
identifiers, credentials, and attributes)
• allow assurance of the identity of an entity (e.g.,
users/subscribers, user devices, service providers, and
network elements)
• support and enhance business and security applications
Colombo, Sri Lanka, 7-10 April 2009
27
Interconnection of NGN with other networks
o Interconnection at Network to Network Interface
• Between multiple NGN domains, between NGN and other networks
o Two types of Interconnection
• Connectivity-oriented Interconnect (CoIx) is required
— Simple IP connectivity, irrespective of interoperability levels
— No service awareness, no specific requirements assurance
• Service-oriented Interconnect (SoIx) is not precluded (R1)
— Services offered with defined levels of interoperability
Source for figure: ETSI TISPAN
Colombo, Sri Lanka, 7-10 April 2009
28
SoIX versus CoIX
o
Service
Transport
Service
Transport
Transport
Transport
o
Terminating
network
Originating
network
Connectivity only transit
Hub
Hub
Service
Transport
Originating
network
o
o
Service
Transport
Transport
Transport
Terminating
network
Service related transit
CoIX – transit network is an IP
pipe
• Transit network operator
not aware of service
SoIX – sessions routed through
transit network SIP proxies
• Transit network aware of
service
Both require a SIP NNI
SoIX enables transit network
to:
• Account + charge based on
service (phone call, video
call etc.)
• Apply dynamic (transport)
resource reservation based
on service
o Both likely to co-exist
• CoIX is a special case of SoIX (with no intervention at the service layer)
• Different markets – some carriers will want to peer with a transit
network and account based on phone calls/sessions, others will want to
peer at IP level only. Depends on pricing / revenue flow / traffic mix.
• GSMA IPX allows either pure L3 or Application layer peering
Colombo, Sri Lanka, 7-10 April 2009
29
Interconnection capabilities and specifications
Interconnection capabilities (R1 objectives)
o
o
o
o
o
routing;
signalling interworking;
numbering, naming and/or
addressing interworking;
accounting and charging related
information exchange;
security interworking;
o
o
o
o
o
QoS interworking;
user and terminal profile
information exchange;
media interworking;
management interworking;
policy management
ITU-T NGN NNI deliverables
o Q.3401 NGN NNI signalling profile (protocol set 1)
• SIP-NNI with codecs/RTP profiles rules and recommendations
• Includes ability to carry MIME encapsulated ISUP (SIP-I)
• Originally for voice services only – recently amended for video/data
services
o Q.1912.5
• Interworking between Session Initiation Protocol (SIP) and Bearer
Independent Call Control protocol or ISDN User Part
• Not an “interconnection” spec but useful in defining SIP-I
Colombo, Sri Lanka, 7-10 April 2009
30
Y.2233 Rev1 (ongoing): Y.2233 extensions to enable
policy-based accounting and charging capabilities in NGN
o
Multiple relevant attributes for policy enabled charging and accounting
• access specific characteristics, bearer QoS, service type, time, user
subscription information, others
B illin g D o m a in
SCF
Cb
C h a rg in g a n d A c c o u n tin g F u n c tio n s
Rs
Cp
C h a rg in g
G a te w a y
F u n c tio n
In te r -P ro v id e r
C h a rg in g G a te w a y
F u n c tio n
A ccount
M anagem ent
F u n c tio n
R a tin g
F u n c tio n
Cc
Cg
P D -F E
Cr
C h a rg in g
C o lle c tio n
F u n c tio n
O n lin e
C h a rg in g
F u n c tio n
Ca
Ci
O th e r
NGN
C h a rg in g
A nd
A c c o u n tin g
F u n c tio n s
Rw
Ct
P E -F E
Co
Ce
C h a rg in g
T rig g e r
F u n c tio n
N G N S Colombo,
e rv ic e &
r a n s 7-10
p o r tApril
F u 2009
n c tio n s
Sri T
Lanka,
31
Numerous other developments …
o ITU-T ongoing standards developments address NGN capabilities in
numerous other technical domains including
•
•
•
•
•
•
•
•
•
Management,
Migration
Performance, measurement, testing
IPv6
Home networking
Advanced service enablers and service oriented infrastructure
Enhanced access and core transport
Emergency telecommunications and accessibility
And others
A global ITU standardization effort for an advanced
telecommunication infrastructure able to evolve and
adapt to the emerging and varying requirements of
the user community
Colombo, Sri Lanka, 7-10 April 2009
32
Thank you for your
attention
Questions ?
Colombo, Sri Lanka, 7-10 April 2009
33