3GPP Work Item description

This page contains informal descriptive text only.  See master WID page for further details.

Feature: All-IP Network

The 3GPP system currently supports GERAN and UTRAN based Access Networks in conjunction with Circuit-Switched and Packet-Switched Core Network domains and IP Multimedia CN subsystem from Rel-5. The All-IP concept was initially introduced within 3GPP in Rel-4 with the standardisation of the MSC Server - MGW split core network architecture for the CS domain and extended from Rel-5 by the standardisation of the IP Multimedia CN subsystem. WLAN as an alternative access technology to access services in the mobile core network is recognized from Rel-6 onwards. 

In order for the 3GPP system to cope with the rapid growth in IP data traffic, the packet-switched technology utilised within 3G mobile networks requires further enhancement. A continued evolution and optimisation of the system concept is also necessary in order to maintain a competitive edge in terms of both performance and cost. It is anticipated that the progression towards an AIPN may enable leverage of information technology (IT) hardware and software with general-purpose, and mobile network specific software that should provide cost reduction (CAPEX and OPEX) for infrastructure equipment and applications of 3GPP based mobile networks. Moreover, it is important to ensure compliance with Internet protocols within future developments of the 3GPP system.

Motivations for further evolving the 3GPP system to an AIPN include (non-exhaustive list):

    §        Rapid increase in IP traffic

    §        Potential network and traffic cost reduction

    §        Industry trend towards IP services

    §        Convergence of telecommunications and IT industries towards IP technology

    §         IP technology being mainstream technology

    §        Flexible accommodation and deployment of existing and new access technologies with mobility by a common IP-based network

    §        Ability to offer enhanced and flexible IP services (e.g. PtP, integrated services) increasing revenues for network operators

    §        Leverage of existing capabilities to evolve the 3GPP system towards an AIPN

Additionally, the following aspects identified within TR 21.902 “Evolution of 3GPP System” are considered relevant to the long-term evolution of the 3GPP system:

    §         A seamless integrated network comprising a variety of networking access systems connected to a common IP based network supported by a centralised mobility manager

    §        A similarity of services and applications across the different systems is beneficial to users

    §         3GPP should focus on the inter-working between 3GPP Mobile Networks and other Networks considering mobility, high security, charging and QoS management

Taking the above into consideration it is necessary to further define the AIPN concept, explore business and technological drivers and evaluate the feasibility of evolving the 3GPP system towards an AIPN. Furthermore, aspects of the 3GPP system requiring enhancement need to be identified and developed in accordance with this common vision. The reuse of existing standards also needs to be investigated.

The objectives of this work item are to study further application of the AIPN concept. Identify and evaluate needs/drivers and identify work required to satisfy the short term and long term needs of 3GPP, specifically:

    §        Investigate the user, business and technological drivers for progression of the 3GPP system to an AIPN:

            -  Study High level Objectives, Motivations and Drivers and impacts on current models (e.g. business/charging/service models)

    §        To define and develop the end-user and operator aspects of a 3GPP AIPN concept:

            - Investigate the feasibility of evolving the 3GPP system towards an AIPN from existing functionalities:

i.               Produce an AIPN vision, taking into account the special requirements for the mobile community e.g. carrier grade, optimisation for the radio environment, recognizing support of multiple access system scenarios.

ii.                Investigate needs and requirements associated with the evolution of the 3GPP System to an AIPN.

iii.               Investigate requirements associated with the reuse of legacy infrastructure and support of legacy  terminals

iv.               Study migration and cost effective introduction of new technology

    §       Identify the capability expansion required to introduce the AIPN concept into the 3GPP system (migration and co-existence).

    §       Define the scope, target, and roadmap for work to be undertaken within Rel-7and future 3GPP releases.

    §       Technical Specification work based on feedback received from other groups, in particular SA2, on the conclusions of the AIPN Feasibility Study (TR 22.978).

Service Aspects:

The expected advantages of an AIPN for network operators from a service provisioning point of view (e.g. rapid application development, service diversity, ubiquitous and seamless services) and potential Service Requirements for an AIPN shall be investigated.

 Potential service aspects to be investigated (non-exhaustive list):

    §       QoS (e.g. End-to-end QoS, policy coordination)

    §       Multiple Access System scenarios

    §       Network/Domain/Access System Selection principles and policies

    §       Mobility  enhancements

    §       Network resiliency, redundancy  and reliability

    §       Resource availability and optimisation

    §       Network management (e.g. ‘back-office’ considerations for new services

    §       Interoperability Service

 Compatibility and reuse of existing standards (e.g. OMA, Web Services/Liberty Alliance Project, IETF, etc…) should be investigated where appropriate.

 Interactions with, and impacts upon existing features, service enablers and services (e.g. IMS, Presence, MMS, SMS, CS voice, etc.) should be investigated.

 The roles of existing and future addresses/identities/numbers (e.g. IMSI, MSISDN, e-mail address, web-address, SIP URI) should be investigated.