Showing posts with label AIPN. Show all posts
Showing posts with label AIPN. Show all posts

Thursday 9 February 2012

Evolution towards ALL-IP Single RAN (SRAN)

Presented by Matthias Sauder and Dr. Volker Sebastian, VodafoneD2 GmbH in the 2nd FOKUS FUSECO Forum 2011, Berlin 17-18 Nov. 2011

Friday 3 December 2010

Presentation: IMS for 3G Voice Services and Migration Strategies

Very interesting presentation from NTT DoCoMo in the IMS workshop I blogged about yesterday. It shows their strategy to move from legacy core network to an All IP Network (AIPN).

Saturday 13 September 2008

Next Generation All-IP Telecom Networks: Quality of Service Challenges and Is...

There is an Interesting tutorial on Next generation All IP Networks from Google on Youtube. Unfortunately they have not allowed sharing of that but you can see that on youtube:

Wednesday 4 July 2007

AIPN Scenarios

AIPN or All-IP Network is being introduced part of 3GPP Release 7. TS 22.978 shows some scenarios where AIPN will play a big part

USE CASE 1 (see left in the daigram): Bob has his own Personal Area Network (PAN). While at home, this network is composed with the Home Area Network using WLAN, which in turn connects externally with a local hotspot service, which in turn connects to a cellular network. Bob's PAN, Bob’s Home-WLAN, the local hotspot service and the AIPN cellular access system are under different administrative domains. Still, if Bob moves outside coverage of his Home-WLAN, his PAN will communicate with the outside world via the local hotspot service. If he moves outside coverage from the hotspot service, his PAN will communicate with the outside world via the AIPN cellular access system.

USE CASE 2: The user is driving a car. While being under good radio coverage, he starts an IMS session with several media. The car goes through a tunnel where there is no radio coverage, and comes out of the tunnel into good radio coverage a minute later. Connections using disruption resilient transport protocols are automatically re-established and these protocols restore the communication to the point they were before the interruption.

USE CASE 3: Alice has a mobile device and Bob has a fixed one. Both devices have equal audio but different video capabilities in terms of screen size, number of colors and video codecs supported. Alice establishes a multimedia connection with audio and video components to Bob. The terminal capabilities are discovered and it is realized that Bob's terminal has better video capabilities than Alice. The terminal informs the network that it is unable to support new the new video codec and the AIPN then introduces a video transcoder in the path of the video media to adapt the video signal (stream, codec, format, etc) to the video capabilities and bit rates available on each side of the transcoder.

Enhanced Services should be possible with AIPN:

  • Support for advanced application services
  • Support for group communication services, e.g. voice group call, instant group messaging, and multicast delivery. In some cases, a group may include a large number of participants.
  • Support for integrated services, e.g. a service including a mixture of services among SMS/MMS/Instant Message, or a service including voice call/video call/voice mail.
  • Provision of seamless services (e.g. transparent to access systems, adaptable to terminal capabilities, etc) Users should be able to move transparently and seamlessly between access systems and to move communication sessions between terminals.
  • Support ubiquitous services (e.g. associations with huge number of sensors, RF tags, etc.) ... see right side of diagram above.
  • Improve disruption-prone situations when network connectivity is intermittent.

Disruption-free network connectivity may not be cost effective, or even feasible, in all cases (e.g. cell planning for full radio coverage for all services, disruption-free inter-access system handovers, disruption-free IP connectivity in all network links). An AIPN should consider solutions for making services as resilient to temporary lack of connectivity as possible.

Monday 2 July 2007

Introduction to All-IP Network (AIPN)

The All-IP Network (AIPN) is an evolution of the 3GPP system to meet the increasing demands of the mobile telecommunications market. Primarily focused upon enhancements of packet switched technology, AIPN provides a continued evolution and optimisation of the system concept in order to provide a competitive edge in terms of both performance and cost. Moreover, it is important that developments of the 3GPP system are compliant with Internet protocols. The AIPN is not limited to consideration of only the transport protocol used within the 3GPP system but adheres to the general concept of a network based upon IP and associated technologies, able to accommodate a variety of different access systems. Although, it is possible to use a variety of different access systems to connect to the AIPN, the AIPN provides an advanced, integrated service set independent as far as possible from the access system used.

The high level objectives of introduction of the AIPN are to realise:

  • universal seamless access
  • improved user experience
  • reduction of cost (for AIPN operators)
  • flexibility of deployment.

There are also a number of motivations and drivers for the introduction of the AIPN which include but are not limited to:

  • diversification of mobile services
  • need to satisfy user experience of early adopters
  • anticipation of PS traffic to surpass CS
  • desire to encompass a variety of access systems
  • need for increased system efficiency and cost reduction (OPEX and CAPEX) and
  • advances of next generation radio access systems and broadband wireless IP-based networks.
The key aspects of the AIPN can be summarised as follows:
  • Support for a variety of different access systems
  • Common capabilities provided independent to the type of service provided with convergence to IP technology considered from the perspective of the system as a whole
  • High performance mobility management that provides end-user, terminal and session mobility
  • Ability to adapt and move sessions from one terminal to another
  • Ability to select the appropriate access system based on a range of criteria
  • Provision of advanced application services as well as seamless and ubiquitous services
  • Ability to efficiently handle and optimally route a variety of different types of IP traffic including user-to-user, user-to-group and ubiquitous service traffic models
  • High level of security and support for user privacy e.g. location privacy, identity privacy
  • Methods for ensuring QoS within and across AIPNs
  • Appropriate identification of terminals, subscriptions and users
  • Federation of identities across different service providers
Further Reading:
3GPP TS 22.258: Service Requirements for the All-IP Network (AIPN);
Stage 1

3GPP TR 22.978: All-IP Network (AIPN) feasibility study

Wireless and Mobile All-IP Core Networks and Services

Next Generation Mobile Systems: 3G & Beyond