Upload
others
View
11
Download
0
Embed Size (px)
Citation preview
InternationalTelecommunicationUnion
ITU-T NGN GSI: progress in standardization of capabilities
for an evolving NGN
Marco CarugiITU-T SG13 WP2 co-chair and
Q.3/13 Rapporteur Senior Advisor, Nortel Networks, FRANCE
Yogyakarta, Indonesia, 27-29 July 2009
ITU-D Regional Development Forum for the Asia Pacific Region
“NGN and Broadband, Opportunities and Challenges” Yogyakarta, Indonesia, 27 – 29 July 2009
Yogyakarta, Indonesia, 27-29 July 2009 2
Outline
o NGN capabilities [Y.2201]o Requirements and ITU-T NGN GSI standardization
progress in some key technical areas • Architecture• QoS • Mobility and FMC• Security and Identity Management• Interconnection • Accounting and charging
NOTE: this presentation focuses on the work of SG13 and SG11 - core SGsof ITU-T NGN GSI - but other SGs have also produced NGN deliverables(SG2, ex-SG4, SG9, SG12, SG15, SG16, SG17, ex-SG19)
Yogyakarta, Indonesia, 27-29 July 2009 3
Y.2012 : basic functional view of NGN
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
Yogyakarta, Indonesia, 27-29 July 2009 4
LegacyTerminals
LegacyTerminals
Transport Stratum
Service Stratum
End-UserFunctions
Application Functions
Core transport Functions
NGNTerminals
Customer Networks
Other N
etworks
Application Support Functions andService Support Functions (ASF&SSF)
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)User
ProfileFunctions
T. UserProfileFunctions
GWGW
Other NGN ServiceComponents
PSTN/ISDN EmulationService Component
IP Multimedia Component&PSTN/ISDN Simulation
IP MultimediaService Component
S. UserProfile
Functions
GWGW
Applications
Re-use and adaptation of 3GPP IMS to
provide multimedia
services (Y.2021)
A unified IP network with improved
security and QoS(Y.2111)
"Service platform"
Evolution scenario of PSTN
and short-term solution (Y.2031)
Network attachment
(Y.2014)
A “NGN components” view
Yogyakarta, Indonesia, 27-29 July 2009 5
Requirements and Capabilities of NGN
o Y.2201 ”High level requirements and capabilities to support NGN Release 1 service objectives” – approved in April 07• Only network capabilities (no user equipment capabilities)• No service-specific requirements• Identified capabilities derived from functionalities developed in
various SDOs and ready for use at Rel.1 time frame • No precise “functional requirements” for specific NGN entities,
rather guidelines for the NGN architecture so that the Architecture FEs are able to support these capabilities and associated requirements
o Y.2201 Rev.1 (formerly NGN Rel.2) Requirements and capabilities for ITU-T NGN – determined in May 09• Includes user related and service-specific requirements
NOTE: each specific NGN realisation may support an arbitraryset of services, thus requiring the implementation of anarbitrary set of capabilities
Yogyakarta, Indonesia, 27-29 July 2009 6
The NGN capabilities identified in Y.2201
o Transport connectivityo Communication modeso Multicast o Media resource managemento Codecs o Access Networks, network
attachmento User networkso Interconnection, Interoperability
and Interworkingo Numbering, naming, addressingo Identific., authentic., authoriz.o Securityo Routingo QoSo OAM and Survivabilityo Accounting and Chargingo Management
o Mobility handlingo Service enablers o Open service environmento Profile managemento Policy managemento PSTN/ISDN emulation and
simulationo Public Interest Services supporto Critical infrastructure protectiono Non disclosure of info across NNIo Inter-provider exchange of user-
related informationo Context managemento Identity managemento Content managemento IPTV services support capabilitieso Enterprise Networks support
capabilitieso IPV6 support capabilities
Y.2201 Rev.1
Yogyakarta, Indonesia, 27-29 July 2009 7
3GPP IP Multimedia Subsystem (IMS)
o IMS highlights• 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 other
features• Independence from the Access Network• The Service platform itself is outside the scope of IMS
IP transport network IP transport network (IP(IP--CAN)CAN)
IMS
Service platformService platform
Yogyakarta, Indonesia, 27-29 July 2009 8
NGN Architecture objectives and IMS
o The advanced objectives of the NGN Architecture• Support of a comprehensive set of services over a unifying IP
layer network• Transport stratum support of a multiplicity of access networks
and a variety of mobile and fixed terminal types• Services separable from transport stratum into service stratum• Services not limited to those provided by the “home network”• Services able to traverse multiple providers’ networks
o IMS is a core component of the NGN Architecture• IP Multimedia Service component • The capabilities of 3GPP IMS can be used by the NGN
— but some extensions of 3GPP IMS specifications are required— IMS alone is not sufficient for the NGN
• Y.2012 “NGN Rel.1 functional requirements and architecture”• Y.2021 “IMS for NGNs” – NGN Rel.1 deliverable
Yogyakarta, Indonesia, 27-29 July 2009 9
NGN reference points in the NGN Architecture
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
Instantiation of NGN reference points – Appendix III Y.2012 (Jan 08)o ANI provides control-level interaction (no media flows across ANI) o SVI introduced as access interface for service partners (content
providers, data information providers, application service providers)• Support of special requirements (transport and signalling resource capacity,
customized policy, multicast injection of media flows, unrestricted server role) • Exchange of transport-level media flows and service-level signalling flows• How to implement SVI as detailed functional entities is for further study
Yogyakarta, Indonesia, 27-29 July 2009 10
Key NGN 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
Yogyakarta, Indonesia, 27-29 July 2009 11
Quality of Service (QoS)
High level objectives (NGN Release 1)o End-to-end QoS environment for the services offered to end users
via QoS coordination across the transport stratumo Initial set of requirements, architectures, mechanisms and
guidelines to enable end-to-end QoS
Key items 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
Yogyakarta, Indonesia, 27-29 July 2009 12
Resource and Admission Control Functions – generic RACF architecture in NGN (Y.2111)
Rs
Rw
Service Stratum
Transport Functions
PolicyDecisionFunction
Transport Resource Control
Function RACF
Transport Stratum
Service Control Functions
Rt
RdRp
RcRn
Ru
Other N
GN
s
Ri
TransportResource
EnforcementFunction
PolicyEnforcement
Function
Network Attachment Control Functions
o Policy Decision service facing, transport independent
o Transport Resource Controlservice independent, transport dependent, network-segment specific (PD-TRC functional decoupling for support of different ANs/CNs)
o Policy Enforcementtypically part of border transport elements, enforces dynamic QoS and resource control, NAPT control and NAT traversal
o Transport Resource Enforcementenforces policy rules instructed by TRC at technology-dependent level
RACFo Application-driven, policy-based resource
management for dynamic QoS guaranteeo Bridges service control and packet
transport thus augmenting native transport QoS support
• Preempting transport congestion at the service control layer
• Protecting ongoing premium traffico Enforces certain network security
measures
Yogyakarta, Indonesia, 27-29 July 2009 13
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
Yogyakarta, Indonesia, 27-29 July 2009 14
Mobility: fundamental enabler of NGN
Users’ basic requirements• Access from a variety of environments with a variety of
terminals with varying capabilities • Global roaming, ubiquitous and seamless solutions
A complex and heterogeneous
environment
Yogyakarta, Indonesia, 27-29 July 2009 15
Mobility: relationship of users, devices, locations - Y.2011
Points of attachment (POA)Telecommunications objects (mobile with transient binding to POA)Transient binding (mobile with transient binding to device)
Network
Device mobility domainUser mobility
domain
Yogyakarta, Indonesia, 27-29 July 2009 16
Mobility dimensions
Mobility
Service continuity Service discontinuity
Seamless Handover Handover Nomadicity Portability
Q.1706/Y.2801
Network view
Quality of Service view
Yogyakarta, Indonesia, 27-29 July 2009 17
Limited Mobility capabilities in NGN Release 1
o NGN Release 1 requires support of “Nomadism”• “The ability to change network access point on
moving, without maintaining service continuity”• To be supported between networks and within a network • NOTE: support for service continuity is not excluded
(where specifications already exist)
o Two types of mobility [Y.2201, Q.1706]• Personal mobility: the user moves (between terminals)• Terminal (Device) Mobility: the device moves (with its
binded user)
o No new interfaces defined for Release 1 mobility
Nomadism is the initial step towards Generalized Mobility and Fixed Mobile Convergence
Yogyakarta, Indonesia, 27-29 July 2009 18
Service continuity as step 2 of mobility [Y.2201 Rev.1]
o NGN support of service continuity is recommended in Intra-AN and Inter-AN scenarios for personal and terminal mobility • Implementation levels may vary (depending on conditions such as
access technology restrictions and Provider’s service level support)• For voice services, service continuity required for terminal mobility
o NGN capabilities for service continuity support are required to consider network conditions and users’ reqts
o NGN is recommended to allow adaptation for service continuity when users’ reqts and network conditions mismatch (e.g. (re)negotiation of network QoS and terminal parameters (codec))
“Mobility roadmap”: an important ongoing activityo Working on a multi-dimension matrix which includes the various
mobility features, mobility scenarios and existing solution specifications
Yogyakarta, Indonesia, 27-29 July 2009 19
MM functional architecture – Q.1707/Y.2804
o Mobility management control function (MMCF) model
o Functional architecture-level view of MMCF in NGN
Location Management
(Y.1708 - Framework)
Handover Control (Y.1709 -
Framework)
Yogyakarta, Indonesia, 27-29 July 2009 20
MMCF network configuration example – Q.1707/Y.2804
The detailed functional mapping in the NGN architecture is in progresso Y.2018 “Architecture and functional requirements for management of logical
location information and control of mobility in NGN transport stratum” (consent in May 09)• Limited to transport stratum (Q.1707 considers both service and transport)• Provides mechanisms for seamless mobility if network conditions permit,
but doesn’t deal with service adaptation if post-handover QoS degradation
Yogyakarta, Indonesia, 27-29 July 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
Yogyakarta, Indonesia, 27-29 July 2009 22
Mobile access networkFixed access
network
Service Control Functions
Mobile Network
Service Control Functions
Applications
Charging and Billing
Functions
Fixed Netwo rk
Application /Service Support
Functions
Control Layer
Applicatio n Layer
Manageme nt 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 level
• Y.2802: FMC characteristics, requirements, capabilities, scenarios• Y.2803: FMC service using legacy PSTN/ISDN as fixed AN for mobile users• Y.2808: FMC with a common IMS session control domain
Yogyakarta, Indonesia, 27-29 July 2009 23
Progress in NGN security
Key Security objectiveso To address security dimensionso To 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 Management, NGN Security mechanisms and
procedures, Mobility security framework in NGN, Secure solutions for mobile commerce and banking
o Identity Management (IdM)
Security Requirements for NGN Release 1 (Y.2701)
Yogyakarta, Indonesia, 27-29 July 2009 24
L e g a c yT e rm in a ls
N o te : G a te w a y (G W ) m a y e x is 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 .
*
L e g a c yT e rm in a ls
T r a n sp o r t S tra tu m
S e r v ic e S tr a tu m
E n d -U s e rF u n c tio n s
A p p lic a t io n F u n c tio n s
C o re t ra n s p o r t F u n c tio n s
N G NT e r m in a ls
C u s to m erN e tw o rk s
Other N
etworks
A p p lic a tio n S u p p o rt F u n c t io n s a n d S e rv ic e S u p p o rt F u n c tio n s
C o re T ra n s p o rtF u n c tio n s
Other N
etworks
E d g eF u n c tio n s
A c c e ss T ra n s p o rt F u n c tio n s
A c c e ss T ra n s p o rt F u n c tio n s
S e rv ic eC o n tro l
F u n c tio n s
N e tw o rk A c c e ss
A tta c h m e n t F u n c tio n s
N e tw o rk A tta c h m e n t C o n tro l F u n c tio n s
(N A C F )
A c c e s s N e tw o rkF u n c tio n s
R e so u rc e a n d A d m is sio nC o n tro l F u n c tio n s
(R A C F )
U se rP ro file
F u n c tio n s
T . U se rP ro fileF u n c tio n s
U se rP ro file
F u n c tio n s
T . U se rP ro fileF u n c tio n s
G WG WG WG W
O th e r N G N S e rv ic eC o m p o n e n ts
P S T N / IS D N E m u la tio nS e rv ic e C o m p o n e n t
IP M u ltim e d ia C o m p o n e n t& P S T N /IS D N S im u la tio n
IP M u ltim e d iaS e rv ic e C o m p o n e n t
S . U se rP ro file
F u n c tio n s
G WG WG WG W
A p p lic a tio n s
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 in NGN : needed not only for “Users” !
o Multiple identity domains within the NGN architecture• Identities for devices, network elements, network components,
applications, service providers etc.
Yogyakarta, Indonesia, 27-29 July 2009 25
Identity Management (IdM): a key ongoing NGN standardization activity
o “IdM” working definition • “Management by NGN providers of trusted attributes of an entity
such as a subscriber, a device or a provider”
NOTE: it’s not intended to indicate positive validation of a person
o Identity information assurance, security and management are challenging• 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
Yogyakarta, Indonesia, 27-29 July 2009 26
Current progress on NGN Identity Management
Y.2720 “NGN IdM framework”o A structured approach for designing, defining, and implementing
interoperable Identity Management (IdM) solutions for NGNo 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
Y.NGN IdM Requirements “NGN IdM requirements”o Includes former Y.NGN IdM Use Cases as an appendixo Planned for consent in Sept 09
Yogyakarta, Indonesia, 27-29 July 2009 27
Interconnection
o Interconnection at Network to Network Interface • Between multiple NGN domains, between NGN and other networks
o Two types of Interconnection have been identified• Connectivity-oriented Interconnect (CoIx) is requiredrequired
— Simple IP connectivity, irrespective of interoperability levels— No service awareness, no specific requirements assurance
• Service-oriented Interconnect (SoIx) is not precludednot precluded (R1)— Services offered with defined levels of interoperability
Source for figure: ETSI TISPAN
Yogyakarta, Indonesia, 27-29 July 2009 28
NGN capabilities and specifications for Interconnection
Interconnection capabilities (objectives)
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 services
o Q.1912.5 • Interworking between SIP and BICC 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
Yogyakarta, Indonesia, 27-29 July 2009 29
Accounting and Charging capabilities in NGN
o Y.2233: A&C functional architecture for NGN Release 1o Y.2233 Rev.1 (ongoing): policy-enabled A&C capabilities
Y.2233(08)_F02
NGN service and transport functions
Chargingtrigger
function
Chargingcollectionfunction
Onlinechargingfunction
Charginggatewayfunction
Charging andaccounting
policyconfiguration
function
OtherNGN
chargingand
accountingfunctions
RatingFunction
Accountmanagement
function
Ct Co
Ci
Cc
CaCr
Cb
Charging and accounting functions
Billing domain
Cg
Inter-providercharging gateway
function
Cp
Yogyakarta, Indonesia, 27-29 July 2009 30
Key NGN A&C requirements - Y.2233 Rev.1
• secure, reliable, scalable and seamless A&C operations • an A&C architecture with open-standard interfaces • interfaces and protocols between
— Network Elements and Accounting Elements— Accounting Elements and Charging Elements— Policy control Elements and A&C Elements
• A&C functionalities for both unicast and multicast based services• different charging policies (e.g. fixed rate, usage based)• per-user offline charging and online charging• service level and transport level charging• per-service and per-medium charging• per-QoS level charging (incl. network resource usage based)• appropriate charging arrangement models (incl. for inter-provider
settlements)• coordination with Resource Control functions (RACF) • flow-based charging• 3rd party charging, real-time modification of accounting policies,
dynamic rating, customer account hierarchy
o Y.2233 has been developed in cooperation with ITU-T NGN Management Focus Group/SG4, 3GPP SA5, ATIS TMOC, ETSI TISPAN
Yogyakarta, Indonesia, 27-29 July 2009 31
A global ITU effort for NGN standards development
o ITU-T ongoing standards developments address NGN capabilities in numerous other technical domains (than those covered here), including • Management • Migration • Performance, measurement, testing• IPv6• Home networking• Enterprise networks connected to NGN• Advanced service enablers and service oriented infrastructure • Enhanced access and core transport • Emergency telecommunications and accessibility
o ITU-T NGN GSI is the ITU focal and harmonization point for NGN standards development• Coordinating within ITU (the other two ITU sectors, ITU-T Study Groups, other
ITU-T efforts/GSIs (e.g. on IPTV, IdM, HN, NID)• Coordinating with external Standards Organizations
AA global ITU standardization effort for an advanced global ITU standardization effort for an advanced telecommunication infrastructure able to evolve and adapt to thetelecommunication infrastructure able to evolve and adapt to the emerging and varying requirements of the user community emerging and varying requirements of the user community
Yogyakarta, Indonesia, 27-29 July 2009 32
Thank you for your attention
Questions ?
Yogyakarta, Indonesia, 27-29 July 2009 33
Backup
Yogyakarta, Indonesia, 27-29 July 2009 34
“Ubiquitous networking” as a future target
o Enabling “Any Service, Any Time, Any Where, Any Device” operations in NGN via enhanced capabilities
o Support of human-to-human, but also human-to-machine and machine-to-machine communications
NGN
PC
Human-to-Human Communication
Human-to-Object Communication
Human-to-Object Communication
Object-to-Object Communication
PDA
Wearable PC
Mobile Phone
Home Electronics
VehicleRFID tag
SensorsTV
Smart Card Telematics,
Navigation Device
Ubiquitous Networking
Database, Web,
application server
Medical Device
Camera
Humanswith
Attached Devices
Objects (Remote Monitoring and
Information Devices)
Home server, gateway
Yogyakarta, Indonesia, 27-29 July 2009 35
Ubiquitous networking work items
o “Draft” definition of ubiquitous networking [Y.NGN-UbiNet] • The ability for all objects to communicate and access services without
any restrictions of services, locations, time, users, etc., in the context (application environment) of the subscribed services
o Y.NGN-UbiNet - Overview and principles for ubiquitous networking in NGN (started in Jan 09)• Objectives and basic characteristics of ubiquitous networking in NGN
• Design principles including architectural model and enhanced capabilities
Specific to sensor device networking: o Y.USN-reqts - Requirements for support of Ubiquitous Sensor
Networking applications and services in NGN environment (planned for consent in Sept 09)
o Draft definition of ubiquitous sensor networking [Y.USN-reqts]• A conceptual structured network which delivers sensed information and
knowledge services to anyone, anywhere and at anytime where the information and knowledge is developed via context awareness
Yogyakarta, Indonesia, 27-29 July 2009 36
Security of financial transactions – Jan 09 work item
o Security solutions supporting scenarios where• Mobile terminal used as payment or banking terminal• NGN used as transport to carry transaction flows
o Related security issues include• network and interface functions for transaction protection• privacy policy• financial infrastructure protection• subscriber protection and identity management aspects
o Draft Recommendations in progress• “Security requirements for mobile financial transactions in NGN”• “Architecture for secure mobile financial transactions in NGN”
Yogyakarta, Indonesia, 27-29 July 2009 37
Management of context information
o Context management capability [Y.2201 Rev.1]• Enabling influence or determination of a telecommunication
process by referring to the status of relevant entities• Individual and aggregated entities’ status form a coherent set of
information known as “context information”• Requirements include security, reliability, standardized format and
semantic, real-time and on-demand support of context informationo Context generator, requestor and distributor
• Distributor collects, distributes, processes and optionally stores context information (as broker between provider and consumer)
o Key enabler of advanced and future services: e.g. Targeted Advertising• benefiting from knowledge of user’s context information such as
location (e.g. at home, in town, in a shopping mall), activity (e.g. at work, on holidays, on business trip), sociality (e.g. alone, with family, with friends)
o All possible dimensions of “context“ still to be explored• E.g. correlation with past behaviours of the User
Yogyakarta, Indonesia, 27-29 July 2009 38
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. That depends on pricing/revenue flow/traffic mix.
• GSMA IPX allows either pure L3 or Application layer peering
Yogyakarta, Indonesia, 27-29 July 2009 39
o Multiple attributes are relevant for policy enablement• access specific characteristics, bearer QoS, service type, time, user
subscription information, etc.
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 n
F 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 i n 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 n
F 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 i n 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
Ongoing Y.2233 Rev.1: NGN policy-enabled A&C capabilities