requirements and capabilities for an evolving ngn ......architecture fes are able to support these...
TRANSCRIPT
Requirements and capabilities for an evolving NGN infrastructure
FORUM ON NEXT GENERATION STANDARDIZATION
(Colombo, Sri Lanka, 7-10 April 2009)
Marco CarugiITU-T SG13 WP2 co-chair and
Q.3/13 Rapporteur Senior Advisor, Nortel Networks
Colombo, Sri Lanka, 7-10 April 2009 2
Outline
o Requirements and capabilities of an evolving NGN infrastructure in some key technical domains
• Architecture• QoS • Mobility• Security and Identity Management• Interconnection • Accounting and charging
o 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 3
Y.2012: basic functional view
Transport stratum
Service stratum
ControlMedia
Man
agem
ent
Func
tions
Management
ANI
Transport Control Functions
Resource and Admission
Control Functions
Network AttachmentControl Functions
NNIUNI
Application Support Functions & Service Support Functions
Applications
Transport Functions
End-UserFunctions
OtherNetworks
Service ControlFunctions
Service UserProfiles
Transport User Profiles
Colombo, Sri Lanka, 7-10 April 2009 4
A “NGN components”
view
LegacyTerminals
LegacyTerminals
Transport Stratum
Service Stratum
End UserFunctions
Application Functions
Core transport Functions
NGNTerminals
Customer Networks
Other N
etworks
Application Support Functions and Service Support Functions
Core TransportFunctions
Other N
etworks
EdgeFunctions
Access Transport
Functions
ServiceControl
Functions
Network Access
Attachment Functions
Network Attachment Control Functions
(NACF)
Access NetworkFunctions
Resource and AdmissionControl Functions
(RACF)
UserProfile
Functions
T. UserProfileFunctions
GWGW
Other NGN ServiceComponents
PSTN / ISDN EmulationService ComponentIP Multimedia Component&PSTN/ISDN Simulation
IP MultimediaService Component
S. UserProfile
Functions
GWGW
Applications
Colombo, Sri Lanka, 7-10 April 2009 5
Y.2201 : NGN Release 1 Requirements and Capabilities
o Scope of Y.2201 • High level requirements and capabilities to support NGN Release
1 service objectivesNOTES: • 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 6
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
IP transport network IP transport network (IP(IP--CAN)CAN)
IMS (SIP)
Application platformApplication platform
Colombo, Sri Lanka, 7-10 April 2009 7
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 8
Instantiation of NGN reference points – Appendix III Y.2012
Y.2012(06)Amd1_FIII.1
TransportTransporttermination
Applications
Transport
Service
Servicetermination Service
TransportTransportTransport
Othernetworks
End-user functions(including enterprise networks)
Transport
UNI NNI
ANI
Transporttermination
Servicetermination
Applications
End-serverfunctions
SVI: Server tonetwork interface
Applications
ServiceService
Colombo, Sri Lanka, 7-10 April 2009 9
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 10
“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.NGN- UbiNet] • 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 11
Quality of Service (QoS)
High level objectives in NGN Release 1o End-to-end QoS environment for the services offered to end users
via QoS coordination across the transport stratumo NGN Release 1 shall provide an initial set of requirements,
architectures, mechanisms and guidelines to enable end-to-end QoS
Key items under studyo 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 12
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 13
Generic RACF architecture in NGN – Y.2111
o 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.
o 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.
o CGPE-FE (CPN Gateway Policy Enforcement Functional Entity) in CPN enforces transport policy rules for upstream traffic instructed by PD-FE.
o TRE-FE (Transport resource enforcement functional entity) enforces transport resource policy rules instructed by TRC-FE at the technology-dependent aggregate level.
RACF
Service Control Functions
Network Attachment
Control Functions
Other N
GN
s
TRC-FE
Rn
Service Stratum
Transport Stratum
PE-FE
PD-FE
TRE-FE
Transport Functions
Rc Rw
Rt
Rs
RiRd
Rp
Ru
CGPE-FE
CPN
Rh
Colombo, Sri Lanka, 7-10 April 2009 14
QoS challenges in customer premise network
CustomerPremiseNetwork
HomeGateway Set Top Box
Set Top Box
NetworkTerminating
Unit10/100Base-T
Television
Desktop PC
Desktop PC
OtherDevices,
Appliances,etc
IPphone
Television
….….….….
Home Gateway issues and QoS per device/terminal
Colombo, Sri Lanka, 7-10 April 2009 15
Mobility: a fundamental enabler of NGN
Basic User Requirements• Access from a variety of environments with a variety of
terminals with varying capabilities • Global roaming, and ubiquitous and seamless solutions
Complex and heterogeneous
environment
Colombo, Sri Lanka, 7-10 April 2009 16
Mobility domains and types - Y.2011
Points of attachment (POA)Telecommunications objects (mobile with transient binding to POA)Transient binding (mobile with transient binding to device/service)
Network
Device mobility domainUser/service
mobility domain
Colombo, Sri Lanka, 7-10 April 2009 17
Other dimensions of mobility
Mobility
Service continuity Service discontinuity
Seamless Handover Handover Nomadicity Portability
Q.1706/Y.2801
Colombo, Sri Lanka, 7-10 April 2009 18
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 19
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 20
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 21
Towards Fixed Mobile Convergence: but which convergence ?
• Converged services• Service integration (voice and multimedia, messaging, presence etc.)
• Converged service platform • Converged networks
• Access and core, incumbent and competitive, wireline or wireless, VNO, ISPs and Broadband SPs
• Converged devices• Phones, smartphones, PDAs, laptops, …
• Converged management• Seamless service provisioning
CableNetwork
MobileNetwork
IPNetwork
CorporateNetwork
FixedNetwork
The multiple dimensions of convergence
Colombo, Sri Lanka, 7-10 April 2009 22
Mobile access networkFixed access
network
Service Control Functions
Mobile Network
Service Control Functions
Applications
Charging and Billing Functions
Fixed Networ k
Application /Service Support
Functions
Control Layer
Application Layer
Management Layer
Functional scenarios of convergence - Q.1762/Y.2802
Convergence may be happen at different functional levels
Example of convergence at Application/Service Support Functions
Y.2802: FMC characteristics, requirements, capabilities and scenarios
Colombo, Sri Lanka, 7-10 April 2009 23
Security
Security objectiveso Address security dimensionso Address security features required for secure domain interconnection
o Security dimensions and countered threats (ITU-T X.805 principles)
o Security threats and risks in NGNo Security trust modelso Security architectureo 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
Security Requirements for NGN Release 1 (Y.2701)
Colombo, Sri Lanka, 7-10 April 2009 24
Security of financial transactions – future item
o Security solutions supporting scenarios where• a mobile terminal serves as a payment or banking
terminal, and • NGN is used as transport to carry transaction flows
o Related security issues include• network and interface functions to support transaction
protection, privacy policy, financial infrastructure protection, subscriber protection and identity management aspects
o Planned draft Recommendations• “Security requirements for mobile financial transactions
in NGN”• “Architecture for secure mobile financial transactions in
NGN”
Colombo, Sri Lanka, 7-10 April 2009 25
L egacyT erm inals
N ote : G atew ay (G W ) m ay exis t in e ither T ransport S tra tum o r E nd-U ser Functions .
*
L egacyT erm inals
T ran sp ort S tra tu m
S ervice S tra tu m
E nd-U serFunctions
A pplication F unctions
C ore transpo rt F unctions
N G NT erm inals
C ustom erN etw orks
Other N
etworks
A pp lication S upport Fun ctions and S erv ice S uppo rt Func tions
C ore T ranspo rtF unctions
Other N
etworks
E dgeFunctions
A ccess T ransport Functions
A ccess T ransport Functions
S erv iceC ontro l
Functions
N etw ork A ccess
A ttachm ent F unctions
N etw ork A ttachm ent C ontrol F unctions
(N A C F )
A ccess N etw o rkF unctions
R esource and A dm issionC ontrol F unctions
(R A C F )
U serP rofile
F unctions
T . U serP rofileF unctions
U serP rofile
F unctions
T . U serP rofileF unctions
G WG WG WG W
O ther N G N ServiceC om ponents
P S T N / IS D N E m ulationS ervice C om ponent
IP M ultim ed ia C om ponent& P S TN /IS D N S im u la tion
IP M ultim ediaS ervice C om ponent
S . U serP rofile
F unctions
G WG WG WG W
A pp lica tions
User Identity Data
Identities in applications
Identities in IMS PES, and other components
Identities in RACF
Identities in NACF
User and terminal identities Network elements
identities
Identity Interoperability
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.
Colombo, Sri Lanka, 7-10 April 2009 26
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 27
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 28
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 precludedprecluded (R1)— Services offered with defined levels of interoperability
Source for figure: ETSI TISPAN
Colombo, Sri Lanka, 7-10 April 2009 29
SoIX versus CoIX
o CoIX – transit network is an IP pipe• Transit network operator
not aware of serviceo SoIX – sessions routed through
transit network SIP proxies• Transit network aware of
serviceo Both require a SIP NNIo SoIX enables transit network
to:• Account + charge based on
service (phone call, video call etc.)
• Apply dynamic (transport) resource reservation based on service
Originatingnetwork
Terminatingnetwork
Transport Transport Transport Transport
Service Service
Originatingnetwork
Terminatingnetwork
Transport Transport Transport Transport
Service Service
Service related transit
Connectivity only transit
Hub Hub
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 30
Interconnection capabilities and specifications
Interconnection capabilities (R1 objectives)
ITU-T NGN NNI deliverableso 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
serviceso 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
o routing;o signalling interworking;o numbering, naming and/or
addressing interworking;o accounting and charging related
information exchange;o security interworking;
o QoS interworking; o user and terminal profile
information exchange;o media interworking;o management interworking;o policy management
Colombo, Sri Lanka, 7-10 April 2009 31
o Multiple relevant attributes for policy enabled charging and accounting• access specific characteristics, bearer QoS, service type, time, user
subscription information, others
N G N S e r v i c e & T r a n s p o r t F u n c t i o n s
C h a r g i n gT r i g g e r
F u n c t i o n
C h a r g i n gC o l l e c t i o nF u n c t i o n
O n l i n eC h a r g i n gF u n c t i o n
C h a r g i n gG a t e w a yF u n c t i o n
S C F
O t h e rN G N
C h a r g i n gA n d
A c c o u n t i n gF u n c t i o n s
R a t i n gF u n c t i o n
A c c o u n tM a n a g e m e n t
F u n c t i o n
C t C o
C i
C c
C aC r
C b
C h a r g i n g a n d A c c o u n t in g F u n c t i o n s
B i l l i n g D o m a i n
C g
I n t e r - P r o v i d e rC h a r g i n g G a t e w a y
F u n c t i o n
C p
P E - F E
P D - F E
R w
R s
C e
N G N S e r v i c e & T r a n s p o r t F u n c t i o n s
C h a r g i n gT r i g g e r
F u n c t i o n
C h a r g i n gC o l l e c t i o nF u n c t i o n
O n l i n eC h a r g i n gF u n c t i o n
C h a r g i n gG a t e w a yF u n c t i o n
S C F
O t h e rN G N
C h a r g i n gA n d
A c c o u n t i n gF u n c t i o n s
R a t i n gF u n c t i o n
A c c o u n tM a n a g e m e n t
F u n c t i o n
C t C o
C i
C c
C aC r
C b
C h a r g i n g a n d A c c o u n t in g F u n c t i o n s
B i l l i n g D o m a i n
C g
I n t e r - P r o v i d e rC h a r g i n g G a t e w a y
F u n c t i o n
C p
P E - F E
P D - F E
R w
R s
C e
Y.2233 Rev1 (ongoing): Y.2233 extensions to enable policy-based accounting and charging capabilities in NGN
Colombo, Sri Lanka, 7-10 April 2009 32
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 A global ITU standardization effort for an advanced telecommunication infrastructure able to evolve and telecommunication infrastructure able to evolve and adapt to the emerging and varying requirements of adapt to the emerging and varying requirements of the user community the user community
Colombo, Sri Lanka, 7-10 April 2009 33
Thank you for your attention
Questions ?