Ims

1 Introduction
IMS Basics, Version 1.1e
T.O.P. BusinessInteractive GmbH
Page 1 of 40
1.1 The Need for IMS (1/3)...................................................................3

1.1 The Need for IMS (2/3)...................................................................4
1.1 The Need for IMS (3/3)...................................................................5
1.2 UMTS Architecture RAN and CN (1/4) ...........................................6
1.3 UMTS Architecture Planes (1/3) ................................................... 10
1.4 UMTS R99 Architecture (1/9) ....................................................... 13
1.5 UMTS R4 Architecture (1/2) ......................................................... 22
1.7 UMTS R6 Aspects........................................................................ 28
1.8 UMTS R7 Aspects........................................................................ 29
1.9 NGN Aspects................................................................................ 30
1.10 Involved Standardization Bodies (1/10) ...................................... 31
1.10 Involved Standardization Bodies (10/10) .................................... 40
Page 2 of 40
1.1 The Need for IMS (1/3)
The new communication paradigm is about networking Internet Protocol (IP)-based mobile
devices. These terminals have built-in cameras, large, high-precision displays and plentyful
applications resources. They are always-on-always-connected application devices.
Page 3 of 40
This redefines applications. Applications are no longer isolated entities exchanging

information only with the user interface. The next generation of more exciting applications are
peer- to- peer entities, which facilitate sharing: shared browsing, shared whiteboard, shared
game experience and shared two-way radio session (i.e. push to talk).
Page 4 of 40
True integration of voice and data services increases productivity and overall effectiveness
while the development of innovative applications integrating voice, data and multimedia will
create demands for new services. These will include, presence, multimedia chat, push to talk
and conferencing. The ability to combine mobility and the IP-network will be crucial to service
success in the future and will require more capable networks than the present 3G mobile
networks.
Page 5 of 40
1.2 UMTS Architecture RAN and CN (1/4)
The Radio Access Network (RAN) and Core Network (CN) were concepts developed to
overcome the problem of compatibility between the many fixed and wireless network types
being developed throughout the world.
Page 6 of 40
The basis of the concept is that the RAN part of the fixed network architecture takes care of
the radio aspects of the radio link for the mobile station. The aspects covered by the RAN
include handover, power control, random access and radio bearer load control.
Page 7 of 40
In its ultimate form, there will be many different types of RAN (GERAN, UTRAN, UMA,
WLAN) as well as many types of CN (IP, Narrow-band-ISDN, Broadband-ISDN, UMTS Core
network, Public Data Networks).
Page 8 of 40
The UMTS Release 99 architecture will focus on the UTRAN connected to a GSM CN. I.e.,
the Network Subsystem NSS for circuit Switched (CS) services, and the GPRS network for
Packet Switched (PS) services. Both parts together create the UMTS Core Network CN.
Page 9 of 40
1.3 UMTS Architecture Planes (1/3)
Another concept introduces the two logically independent planes - the control and user
planes - used to separate control messages, i.e., signaling from user information flow,i.e.,
content between user equipment (UE) and the CN.
Page 10 of 40
The user plane in the UMTS system, for instance, will transport all of the user data traffic
between the UE and the CN. The user data can be any type of user data associated with a
Circuit Switched (CS) or a Packet Switched (PS) connection, e.g., voice and e-mail or Web
access data.
Page 11 of 40
The Control Plane is used to pass control messages between the UTRAN / CN and the UE.
The control messages are varied and include signaling messages which relate to functions
like location updates, handover and call setup.
Page 12 of 40
1.4 UMTS R99 Architecture (1/9)
The UMTS network architecture is divided into three subsystems, with well defined
interfaces:
The Radio Access Network (RAN) - the Core Network (CN) and the Operations Support
Systems (OSS).
The functions of each subsystem are similar to those of GSM. This makes it very easy for
operators to upgrade their existing networks.
Page 13 of 40
UMTS Release 99 introduces the UTRAN, the radio access network for UMTS, and provides
all transmission and control functions needed for area wide radio coverage.
The Air-Interface Uu connects the mobile user equipment UE to the UTRAN.
The CN provides the main switching and subscriber handling functions and connects to the
UTRAN via the Iu interface. The OSS is responsible for the management of the whole
network.
In the following steps we will introduce the network elements of the different subsystems and
show the network structure will develop within future releases.
Page 14 of 40
The new UMTS Terrestial Radio Access Network (UTRAN) consists of the base station
Node-B and the RNC.
The base station is responsible for the W-CDMA transmission on the air interface, and
connects to the Radio Network Controller RNC via the Iub Interface The main tasks of RNC
are radio resource management, mobility management and radio network supervision.
Page 15 of 40
The UMTS Core Network consists of two logical independent domains:

The CS circuit switched domain and the PS packet switched domain.
Already familiar from GSM NSS and GPRS, the CS and the PS domain are based on the
same main elements:
CS consists mainly of MSC, VLR and Gateway-MSC, while PS is based on GPRS core
network elements like the GGSN, also introducing a 3G SGSN.
The CS and PS domains share HLR, AC and EIR as common network elements.
Page 16 of 40
The Iu interface between the UTRAN and the CN is divided into two separate functional parts
according to the services supported: For the circuit switched services the RNC is connected
to a Media Gateway / MSC tandem via the Iu-CS interface.The Media Gateway functionality
will be explained later. For the packet switched services the Iu-PS interface is used between
RNC and SGSN. RNCs can also be interconnected via the Iur-interface.
Page 17 of 40
Now lets have a look at the combination of the UMTS network with an existing GSM and
GPRS structure. The 2G Base Station Subsystem BSS , consisting of BTS and BSC, is
connected to the CS domain via the A interface towards the MSC, whereas the connection to
the PS domain takes place via the Gb interface between the BSC and the 2G-SGSN.
Page 18 of 40
Apart from the new W-CDMA structure on the air interface, there are two more major
differences between GSM and UMTS networks:
1. In GSM, transmission is based on circuit switching of TDMA timeslots, but in UMTS
transport takes place via the network ATM cell transmission.
2. 2. In 2G, transcoding is defined as a BSS functionality, whereas in UMTS it is part of the
CS-domain of the CN.
Page 19 of 40
As a consequence, with Rel. 99 a new network element is introduced in the CS-domain: the
Multimedia Gateway.
With the help of the MGW an existing MSC can be reused. This combination of MSC and
new MGW is also called a 3G-MSC.
The main function of the MGW is to provide UTRAN interworking functions for CS services
towards MSC.
At the user plane the MGW takes care of both UMTS transcoding functionality and the
ATM/TDM conversion.
Page 20 of 40
On the control plane the MGW is responsible for interface signalling conversion between the
different protocols, BSSAP protocol stack defined on A-interface and RANAP signalling stack
on the Iu-CS interface.
In the same manner, in the PS domain a new ATM-based 3G SGSN takes responsible for
the 3G packet oriented traffic on the Iu-PS interface, while timeslot based 2G SGSN is still in
use.
Page 21 of 40
The purpose of Rel. 4 is to offer higher flexibility and better efficiency of transport resources
in the core network.
Thus the user plane and the control plane are strictly separated. As a consequence the
network elements in the circuit switched domain 3G MSC, VLR and GMSC are replaced by
MSC Server (MSS) that either provides IP or ATM backbone connectivity.
Page 22 of 40
The MSC user plane switching functions are brought to the Multimedia Gateway for MSS
which is responsible for bearer control. Thus, calls can be switched at MGW sites without
being routed to the MSC server site.
The MSC Server handles all control plane functions for CS-call control and mobility control
parts from MSC and VLR. The Release 4 architecture allows a centralization of call control
functions to relatively few MSC servers.
In the interest of convergence with the packet switched domain the telephony core is based
on an ATM and IP backbone.
Page 23 of 40
The major changes in the Rel.5 network will be the IP Multimedia Subsystem enabling
simpler service integration. UTRAN will be improved by the High Speed Uplink & Downlink
Packet Access (HSUPA / HSDPA) for enhanced uplink data rates at a max. of 1.8Mbps and
downlink data rates at a max. of 10Mbps. 2G BSC and 3G RNC will be directly connected by
a new Iur-g Interface. The whole network will become an All-IP network, meaning IP
transport in the core network as well as in the UTRAN, offering End-to-end IP services.
Page 24 of 40
By introducing the IP Multimedia Subsystem (IMS) network operators can offer an universal
all-IP backbone network that is able to support any kind of wireless and wire-line access
networks.
Thus, network operators can offer seamless services, operate all network subsystems more
easily and benefit from an utmost flexibility in services creation and network extension.
Page 25 of 40
IMS introduces new categories of server-based network components with dedicated

functionality:
Session Management and routing servers, e.g., the Call Session Control Function
Data bases, e.g., the Home Subscriber Server which is an evolved HLR
Interworking Elements, e.g., Media Gateways
Support Entities
Charging Entities and
Application Servers
We'll present all entities in detail later.
Page 26 of 40
The latter requires an enhancement of our plane model that we discussed earlier. An
Application Plane is added for bearer-independent content presentation and handling.
Page 27 of 40
1.7 UMTS R6 Aspects
During its ongoing specification work 3GPP has shifted some original UMTS R5 features to a
later introduction date. R6 main features related to IMS will include:
Full interworking with circuit-switched networks, WLANs and other IP networks

Multiple registration
Emergency sessions
Usage of Public Key Infrastructure
Presence services, group management, conferencing
Page 28 of 40
1.8 UMTS R7 Aspects
Furthermore, 3GPP continues with R7 specification work including a set of IMS features like
Multiple Input Multiple Output antennas (MIMO)

Improvements to the Radio Interface, i.e., UMTS at 900 / 1,700 / 2,600MHz
PS domain and IMS impacts for the support of IMS Emergency calls
Location Services enhancements
Advanced Global Navigation Satellite System (A-GNSS) concept
System enhancements for fixed broadband access to IMS
WLAN 3GPP IP Access
Voice over IMS bearer related enhancements
3GPP work items are always subject to modification, this list provides the status as of April
2006.
Page 29 of 40
1.9 NGN Aspects
Earlier, we said that IMS is access network-independent, although 3GPP has focussed on
making sure that the radio access networks are ready for IMS services. IMS services from
fixed broadband networks such as Asymmetric Digital Subscriber Lines (ADSL) are also
referred to as Next Generation Networks (NGN). We will look at VoIP-based NGN aspects in
a later module.
Page 30 of 40
1.10 Involved Standardization Bodies (1/10)
As we have seen already, IMS was developed by 3GPP from UMTS network and service
concepts. To achieve better global interoperability other major standardization bodies
contribute to the IMS specifications. We will now have a look at some of them.
Page 31 of 40
The Internet Engineering Task Force (IETF) is a standardization body that assumes the task
of developing and evolving the Internet and its architecture, as well as ensuring its smooth
and secure operation. The IETF is made up of network designers, academics, engineers and
researchers from many companies. IETF participation does not require membership and is
open to any individuals who share the same interests.
Page 32 of 40
3GPP and IETF work closely together. 3GPP adopts protocols developed at the IETF as
needed (e.g. SIP, SDP, RTP, DIAMETER). 3GPP generates requirements for a specific
problem and then contacts the IETF for a possible solution to its requirements. The IETF
evaluates the 3GPP requirements and provides 3GPP with a protocol that satisfies those
requirements.
Page 33 of 40
In June 2002 the mobile industry set up a new, global organization called the Open Mobile
Alliance (OMA). OMA has taken its place as the leading standardization organization for
doing mobile specification work. OMAs role is to specify different service enablers, such as
digital rights management or push to talk over cellular service (PoC).
Page 34 of 40
OMA has recognized that it is not beneficial for each service enabler to have its own
mechanism for security, quality of service, charging, session management, etc. On the
contrary, service enablers should be able to use an infrastructure like the IMS that provides
these basic capabilities in a very efficient way.
Page 35 of 40
Therefore, OMA and 3GPP will increase their cooperation in the future. OMA might gradually
take overall responsibility for the invention and design of applications and services, while
3GPP continues to develop the core IMS.
Page 36 of 40
The Third Generation Partnership Project 2 (3GPP2) is a collaborative project for developing
3G systems for the ANSI (American National Standards Institute) community. Like its sister
project 3GPP, 3GPP2 cooperates with several important organization like ARIB (Association
of Radio Industries and Businesses), CCSA (China Communications Standards Association),
TIA (Telecommunications Industry Association) and market representation partners, e.g.,
CDMA Development Group and the IPv6 Forum.
Page 37 of 40
3GPP2s role in IMS standardization lies in specifying IMS as part of the Multimedia Domain.
Multimedia Domain and the CDMA2000 Access Network together form 3GPP2s 3G All-IP
Core Network. In turn, 3GPP contributes with its Release 5 IMS specifications.
Page 38 of 40
However, there are differences between 3GPP IMS and 3GPP2 IMS Release 5 solutions due
to different underlying packet and radio technology.
Page 39 of 40
Additionally, both IMS approaches have defined further additions or limitations. The most
significant differences are
IP version 4 is also supported in 3GPP2 IMS, whereas 3GPP IMS exclusively

supports IP version 6
3GPP2 specifics no default codec.
There are differences in the charging solutions.
3GPP2 does not support a Universal Integrated Circuit Card which could contain IMS
access parameters.
3GPP2 does not support Customized Applications for Mobile network Enhanced
Logic-related functions.
Page 40 of 40

Ims

Transféré par

Informations du document

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

Ims

Transféré par

Droits d'auteur :

Formats disponibles

1 Introduction

IMS Basics, Version 1.1e

T.O.P. BusinessInteractive GmbH

1.1 The Need for IMS (1/3)...................................................................3

IMS Basics, Version 1.1e

T.O.P. BusinessInteractive GmbH

1.1 The Need for IMS (1/3)

IMS Basics, Version 1.1e

T.O.P. BusinessInteractive GmbH

1.1 The Need for IMS (2/3)

This redefines applications. Applications are no longer isolated entities exchanging

IMS Basics, Version 1.1e

T.O.P. BusinessInteractive GmbH

1.1 The Need for IMS (3/3)

IMS Basics, Version 1.1e

T.O.P. BusinessInteractive GmbH

1.2 UMTS Architecture RAN and CN (1/4)

IMS Basics, Version 1.1e

T.O.P. BusinessInteractive GmbH

1.2 UMTS Architecture RAN and CN (2/4)

IMS Basics, Version 1.1e

T.O.P. BusinessInteractive GmbH

1.2 UMTS Architecture RAN and CN (3/4)

IMS Basics, Version 1.1e

T.O.P. BusinessInteractive GmbH

1.2 UMTS Architecture RAN and CN (4/4)

IMS Basics, Version 1.1e

T.O.P. BusinessInteractive GmbH

1.3 UMTS Architecture Planes (1/3)

IMS Basics, Version 1.1e

T.O.P. BusinessInteractive GmbH

1.3 UMTS Architecture Planes (2/3)

IMS Basics, Version 1.1e

T.O.P. BusinessInteractive GmbH

1.3 UMTS Architecture Planes (3/3)

IMS Basics, Version 1.1e

T.O.P. BusinessInteractive GmbH

1.4 UMTS R99 Architecture (1/9)

IMS Basics, Version 1.1e

T.O.P. BusinessInteractive GmbH

1.4 UMTS R99 Architecture (2/9)

IMS Basics, Version 1.1e

T.O.P. BusinessInteractive GmbH

1.4 UMTS R99 Architecture (3/9)

IMS Basics, Version 1.1e

T.O.P. BusinessInteractive GmbH

1.4 UMTS R99 Architecture (4/9)

The UMTS Core Network consists of two logical independent domains:

IMS Basics, Version 1.1e

T.O.P. BusinessInteractive GmbH

1.4 UMTS R99 Architecture (5/9)

IMS Basics, Version 1.1e

T.O.P. BusinessInteractive GmbH

1.4 UMTS R99 Architecture (6/9)

IMS Basics, Version 1.1e

T.O.P. BusinessInteractive GmbH

1.4 UMTS R99 Architecture (7/9)

IMS Basics, Version 1.1e

T.O.P. BusinessInteractive GmbH

1.4 UMTS R99 Architecture (8/9)

IMS Basics, Version 1.1e

T.O.P. BusinessInteractive GmbH

1.4 UMTS R99 Architecture (9/9)

IMS Basics, Version 1.1e