page 1 sprint pcs sc.allip-20000323-003 for a next generation network all-ip architectural...

Sprint PCS

SC.ALLIP-20000323-003

for a

Next Generation Network

All-IP Architectural PrinciplesAll-IP Architectural Principles

The information contained in this contribution is provided for the sole purpose of promoting discussion within the 3GPP2 and its Organization Partners and is not binding on the contributor. The contributor reserves the right to add to, amend, or withdraw the statements contained herein.

The contributor grants a free, irrevocable license to 3GPP2 and its Organizational Partners to incorporate text or other copyrightable material contained in the contribution and any modifications thereof in the creation of 3GPP2 publications; to copyright and sell in Organizational Partner’s name any Organizational Partner’s standards publication even though it may include portions of the contribution; and at the Organizational Partners sole discretion to permit others to reproduce in whole or in part such contributions or the resulting Organizational Partner’s standards publication. The contributor may hold one or more patents or copyrights that cover information contained in this contribution. The contributor must also be willing to grant licenses under such contributor copyrights to third parties on reasonable, non-discriminatory terms and conditions, as appropriate

Authors: Richard Robinson +1.913.664.8321 [email protected] Ferguson +1.913.664.8342 [email protected]

Sprint PCS

SC.ALLIP-20000323-003

Architecture PrinciplesArchitecture Principles

Separation of Service from Delivery Transport Independence (to control heterogeneous bearer mechanisms):

The All-IP reference architecture shall be independent of the underlying transport mechanism (e.g. Frame Relay, ATM or IP). Furthermore the operators shall have the freedom to utilize a single or any combination of transport technologies.

Decomposition of network functions: The All-IP reference architecture shall be defined in terms of separate functions and clear interfaces such that it is possible to separate transport from signaling and to separate call/session, mobility and service control. Thus operators shall have the freedom to provision, dimension and upgrade these network functions in a modular fashion. This modularity shall give operators flexibility and scaleability of network implementations.

Sprint PCS

SC.ALLIP-20000323-003


Continued - Separation of Service from Delivery Separation of mobility management from session control, i.e.,

Decomposition of subscriber-related data: The All-IP reference architecture shall allow the mobility aspects of the subscriber to be isolated from session and service management.

• Mobility Management is separated from call and feature processing. The Session Manager should be independent of mobility specific information

– allows the Call Agent (part of Session Manager) to be isolated from the mobility aspects of the subscriber

– MM enables mobile roaming, mobile hard handoffs between systems, and other mobile-centric features

– MM also interacts with Service Agent to handle ubiquitous mobile features such as Short Message Service (SMS), cell broadcast, etc.

– provide for legacy mobility support of roaming 2G users– MM also uses location-based information– Aid Operators/ISPs ability to independently upgrade sub-systems– Allow Operators/ISPs to build multi-vendor systems

• MM enables the core network to support multiple access networks at the same time, thereby allowing a set of common features across the various access networks.

– MM provides support for all mobility specific features of any given RAN– Key to subscriber and service mobility across wireless & wireline

Sprint PCS

SC.ALLIP-20000323-003


Open All Pertinent Interfaces Including RAN internal interfaces, core network interfaces Floating transcoder function (not tied to radio access network)

• The All-IP reference architecture shall allow operators to place the vocoder function in the most practical, cost-effective part(s) of the network

RAN Open A and Abis interfaces Enables plug & play components Improves scalability

• across multiple environments (e.g., pico-cell deployment on campus application)

in RAN, allows BTS independence from BSC/RNC Decompose the classic BSC/RNC Open interface for OAM&P Leverage current evolution of RAN within 3GPP2 TSG-A

Sprint PCS

SC.ALLIP-20000323-003


Use of internet protocols: The All-IP reference architecture shall use, as appropriate,

existing/evolving internet protocols e.g. to support multi-media services, interoperability with other next generation fixed or mobile networks (NGNs), and media gateway controllers.

Independence of access technology Extend IP transport of traffic and control to BTS Provide IP end-to-end from terminal for data applications Inter-technology mobility management (separate mobility management

function) • support mobility across multiple access environments

Global alignment Eliminate regional/country differences in key interfaces Globally accessible services (see also Services Requirements) Interoperability with 2G and non-IP networks and services

Sprint PCS

SC.ALLIP-20000323-003


Harmonization with Access Technologies Extends from Wireless to Wireline, xDSL, Cable, Wireless LAN, Digital

Broadcast, etc.• includes 2G and 3G

Harmonization between Networks Harmonization is a key design goal as operators networks expand within

and across regional boundaries Support for legacy networks and terminals: The All-IP reference

architecture shall provide support for all-IP multi-mode terminals roaming onto legacy networks and legacy terminals roaming onto all-IP networks. In addition the architecture should allow the gradual deployment of the all-IP approach and hence support handoff back into and from legacy networks. Key requirements:

• All-IP to Legacy as evolution steps within the evolved network

• Gateways to PSTN / traditional networks - designed to ensure service and feature transparency

• Must have interoperation between Next Generation Networks

Sprint PCS

SC.ALLIP-20000323-003


Distributed Architecture Intelligence distributed in the network and end points Scalable Evolve from the Traditional MSC - Move to Client Server

• for example, Gateway to translate legacy call control to IP call control

• Distribution of MSC functionality into a distributed IP based system enables a far more scaleable, open network, with open, standardized interfaces

• Deployment of new features and services is greatly enhanced due to client server architecture - feature servers can obtain new loads from multiple sources - less development time

• Key to evolution from traditional telephony to All-IP

• However, phased transition is necessary to protect existing subscribers and features

Cost and Quality are Driving Considerations to the level of distribution Also provides open interfaces for innovation and accelerated time-to-

market Work to minimize Risk of excessive regulatory intervention due to

increased number of interfaces and elements

Sprint PCS

SC.ALLIP-20000323-003


Quality, Reliability End-to-end QoS mechanism for any given service

• need the flexibility to apply QoS to a wide variety of services at the appropriate places within the architecture - QoS tied to subscriber

• reuse QoS conceptual developments currently underway in 3GPP, 3GPP2, IETF, ITU, TIPHON• Needs to take into account both wholesale and retail requirements

Reliability• platform, element and system (or sub-system) reliability is driven by a combination of operator,

subscriber, and regulatory needs - the All-IP architecture must account for these variations and expectations

Security Support mutual authentication (subscribers, 3rd party services, etc.),

confidentiality, integrity and non-repudiation In support of accounting and billing Encryption - most appropriate level to satisfy customer and 3rd party needs Law enforcement (support their mission) Data protection (rights of access, privacy) Some service demands (e.g., e-commerce)

Sprint PCS

SC.ALLIP-20000323-003


O&M Standardized, compatible network management interfaces

• within the NGN

• with legacy but within cost constraints

Access Devices Mobile Terminal User Interface - Ease of Use and Interactivity Application Usage Variety of Mobile Terminals Expected (Mobile Phone, PDA, Laptop, etc.) Multi-mode across environments Connectivity, e.g., Bluetooth Smartcards (R-UIM)

Sprint PCS

SC.ALLIP-20000323-003


Service Requirements of the All-IP Architecture Support wide range of services, including real-time, non-real-time, multi-media

services• VOIP will be required and will drive certain QoS requirements• Some services will be offered in both real-time and non-real-time modes and will drive certain QoS

requirements

Rapid service creation Support of third party services

• development by third party– example - use of Parlay, etc.

• service offered by third party– examples - AAA, Data collection

• New service/business model

User customisation of services Roaming - de-couple subscriber from geographic based provider

• Mobile Virtual Network Operators (MVNO)• Subscriber Roaming - independent of the terminal• Need for standard records/usage information interchange

Current and Future Services

Sprint PCS

SC.ALLIP-20000323-003

Architectural PrinciplesArchitectural Principles

Support Regulatory Requirements Legal intercept Number portability Other regional requirements Avoid anti-competitive practice

page 1 sprint pcs sc.allip-20000323-003 for a next generation network all-ip architectural...

Documents