The IMS: IP Multimedia Concepts and Services

Part I

IMS Architecture and Concepts

1

Introduction

1.1 What is the Internet Protocol Multimedia Subsystem (IMS)?

Fixed and mobile networks have gone through a major transition in the past 20 years. In the mobile world, first-generation (1G) systems were introduced in the mid-1980s. These networks offered basic services for users. The main emphasis was on speech and speech-related services. Second-generation (2G) systems in the 1990s brought some data services and more sophisticated supplementary services to the users. The third generation (3G and 3.5G) and its evolution (LTE) is now enabling faster data rates and various multimedia services. In the fixed side, traditional Public Switched Telephone Network (PSTN) and Integrated Services Digital Network (ISDN) networks have dominated traditional voice and video communication. In recent years the usage of the Internet has exploded and more and more users are taking advantage of faster and cheaper Internet connection such as Asymmetric Digital Subscriber Line (ADSL). These types of Internet connections enable always-on connectivity, which is a necessity for people to start using real-time communication means – e.g., chatting applications, online gaming, Voice over IP (VoIP).

At the moment we are experiencing the fast convergence of fixed and mobile worlds as the penetration of mobile devices is increasing on a yearly basis. These mobile devices have large, high-precision displays, they have built-in cameras and a lot of resources for applications. They are always-on always-connected application devices. 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, shared two-way radio session (i.e., Push to Talk Over Cellular). The concept of being connected will be redefined. Dialling a number and talking will soon be seen as a narrow subset of networking. The ability to establish a peer-to-peer connection between the new Internet Protocol (IP) enabled devices is the key required ingredient. This new paradigm of communications reaches far beyond the capabilities of the Plain Old Telephone Service (POTS).

In order to communicate, IP-based applications must have a mechanism to reach the correspondent. The telephone network currently provides this critical task of establishing a connection. By dialling the peer, the network can establish an ad hoc connection between any two terminals over the IP network. This critical IP connectivity capability is offered only in isolated and single-service provider environments in the Internet; closed systems compete on user base, where user lock-in is key and interworking between service providers is an unwelcome feature. Therefore, we need a global system – the IP Multimedia Subsystem (IMS). It allows applications in IP-enabled devices to establish peer-to-peer and peer-to-content connections easily and securely. Our definition for the IMS is:

IMS is a global, access-independent and standard-based IP connectivity and service control architecture that enables various types of multimedia services to end-users using common Internet-based protocols.

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, such as presence, multimedia chat, push to talk and conferencing. The skill to combine mobility and the IP network will be crucial to service success in the future.

Figure 1.1 shows a converged communication network for the fixed mobile environment. It is the IMS which introduces multimedia session control in the packet-switched domain and at the same time brings circuit-switched functionality in the packet-switched domain. The IMS is a key technology for such network consolidation.

Figure 1.1 IMS in converged networks

1.2 Fixed and Mobile Convergence

Since the IMS architecture integrates both wireless and wireline networks, the IMS becomes an inexpensive medium for Fixed to Mobile Convergence (FMC). It is currently one of the crucial strategic issues in the telecommunications industry. Trends in different regions and countries are different, but on a global level operators are facing increasing competition and declining prices for voice traffic, fixed lines and fixed minutes. At the same time, mobile voice traffic is growing rapidly and substituting that of voice traffic over fixed lines. End users now expect high quality with reliable mobility and are using the Internet more as the penetration of broadband grows rapidly. Now, Voice over IP (VoIP) is starting to substitute PSTN. Meanwhile, key enabling technologies, such as smart phones, wireline and wireless broadband and IMS for seamless service over different access types are readily available. Combined, this means that operators are looking for long-term evolutionary strategies towards converged, access-agnostic networks, with service integration and interoperability across domains and devices. From the end user’s perspective this delivers seamless end user experience across multiple locations, devices and services. Convergence can be viewed from three separate angles:

convergence of networks

convergence of services

convergence of devices

Convergence of Networks

Network convergence simplifies the end user experience and dissolves the barriers and complexities that separate today’s network islands. The same services are available across all networks and, in an ideal world, appear and perform in exactly the same way, making usage easy, transparent and intuitive.

From an operator’s perspective, the goal of network convergence is to migrate today’s separate PSTN, PLMN, backbone and IP networks to a fully converged network that supports any access technology. The full evolution includes a cost effective migration to an All-IP network using IMS as the unifying platform, allowing all new services to be accessed in a standard and consistent manner as shown in Figure 1.2 manner. Advancing in this evolution will be the key to an operator’s ability to reduce OPEX and CAPEX, and increasing competitiveness and profitability.

Many locations, such as homes, enterprises and public places already have access networks available (xDSL, WLAN, cable etc.). When operators launch new services such as video streaming or hosted email they can take advantage of these existing networks, extending service access to more potential subscribers. In turn this will mean launching services to new market segments for new revenue opportunities. With multiple access networks operators can attract existing and new customers with an enhanced convergence service portfolio using unified billing.

A converged core network is the key enabler for converged networks. Multi-access to a common, converged core network enables cost optimization for both mobile and hybrid operators. Re-use of existing access network infrastructure and integration with the service infrastructure results in both OPEX and CAPEX savings. And multi-access enables operators to introduce end-to-end quadruple-play services (voice, data, video/TV and mobility), to new customers.

Figure 1.2 Convergence of networks

IP-based access connection using the SIP protocol between the device and the converged core network – so called ‘Native IP access’ – allows voice, video and other multimedia applications over any access network. Native IP access supports a wide variety of applications in different devices, including mobile handsets, PC clients and SIP desktop phones. POTS phones too, can also be supported, via a connection to an SIP-capable DSLAM or analog terminal adapter (ATA). Native IP access architecture allows the introduction of new rich IP multimedia services through IMS functionality, such as presence, media push, multimedia telephony, games and various other SIP enabled applications, furthering revenue streams for operators.

Device Convergence

Typically, a device is only used – in the main – for a single purpose and the support for its other functions is limited. PSTN phones, low end mobile phones and set-top boxes are good examples. Consumers use these devices for a single purpose. When they change tasks they change device and access network. This means service islands, which lead to mis-matched user experiences from different public and private networks. What’s needed are unifying devices that can access services in a similar and easy way.

Smart phones are serious contenders for voice-plus multimedia services in a truly mobile environment. Multiple radio interfaces provide access over circuit and packet-switched networks (cellular, WLAN etc) and IMS allows services and applications to traverse different IP networks. Mobile phone development has been rapid in the last decade and new models take increasing advantage of new technologies. They incorporate the enhanced colour displays and high quality imaging features needed to support service consumption and the creation of own content. Plus the exponential growth of memory capacity and processing power means that smart phones can now replicate the applications currently employed in notebook PCs and PDAs.

Consumers want the quality of fixed services with the flexibility of mobile and convergence lets this happen, by allowing service access through the most suitable access network, and by letting consumers choose the best device for the service. In many cases that device will be a smart phone, but it could just as easily be a PC or laptop with VoIP software or converged fixed clients who can share IM, presence etc with mobile devices, a fixed VoIP phone or even a TV with a set-top box.

Service Convergence

The mobility model has become ‘me-centric’, with my phone book, my contact information, my agenda, my messages, my availability and preferred communication method, my Internet, my pictures and video clips (received and shared), my personal and business email, my wall-paper, my music and so on. Multimedia services, such as Presence, Push-to-talk, messaging, interactive applications, data or video sharing plus streaming, browsing and downloading, are being delivered over fixed and mobile packet networks. To launch new services and applications quickly, operators can use IMS to eliminate the complexity of different service platforms in the network. Standards based Service Delivery Framework (SDF) provides comprehensive lifecycle management, making the launch of new services and applications quicker and easier to integrate and operate; delivering solutions more speedily to market and reducing the total cost of ownership. In effect the operator can provision – and the end-user quickly and conveniently self-provision – the new services.

VoIP and Instant Messaging are two developments that helped kick-start service convergence. VoIP has had a seismic impact on telephony within enterprises and, as the penetration of broadband access increases, so does the availability of this transport mechanism within the home. Users also benefit from personalized VoIP, including same number, same contacts and the same supplementary services like call barring, call waiting, ring back tones, one voice mail, option for one postpaid bill or prepaid account, etc through any access network. IP DSLAMs are letting operators offer both DSL access and traditional two-wire POTS connections using a SIP client in the DSLAM. This development and others like fixed VoIP phones, Analog Telephony Adapters (ATA) and fixed soft switches place fixed line operators in an excellent position. They can offer multimedia services via DSL and attractive tariffs for analog POTS connected to an IP network, thereby maintaining existing services where required and evolving the core network to an IP-based solution. Smart phones, on the other hand, have WLAN interfaces so they can access fixed broadband networks. This allows the mobile phone to be used as an IP phone and users to continue employing their personalized services at home, or via WLANs, connected to DSL, in hot spots or offices. Convergence in this case enables a practical combination of cellular and fixed broadband access. The user experience doesn’t change: the same voice and multimedia services are used in the same way. Fixed to Mobile Substitution and fixed VoIP are gradually replacing PSTN voice telephony. Multimedia services are being delivered over fixed and mobile packet networks. Operators must now decide on the kinds of services they wish to provide by themselves or by partners, to whom and in which regions. And what they might offer is no longer limited to traditional telecom services only, but perhaps entry into new businesses.

1.3 Example of IMS Services

Switching on my Internet Protocol Multimedia Subsystem (IMS) enabled device, it will automatically register to the IMS network using information in the identity module (such as USIM). During registration both device and network are authenticated and my device will get my user identities from the network. After this single registration, all my services will be available, including push to talk, presence, voice and video sessions, messaging and multiplayer games. Moreover, my availability information is updated at the presence server as being online and listing my current applications.

When I need to contact my friend Bob, I select Bob from my device’s phone book and, based on his presence information, I see immediately that he is available. After pressing the ‘green button’ on my device it will place an ‘ordinary’ call to him. The IMS network will take care of finding and setting up a Session Initiation Protocol (SIP) session between our devices, even though Bob is currently abroad. When my call reaches Bob’s terminal he will see that the call is coming from me and, additionally, he sees a text string inserted by me (‘Free tickets to movie next Wednesday’). Bob answers, but tells me that he’s not sure whether he is able to come. We decide to check the issue again on Sunday. Before hanging up, Bob says to me, ‘You won’t believe what I saw today but just wait a second, I’ll show you.’ Bob starts streaming a video clip to me, and while I’m watching the video, Bob keeps explaining what happened in the zoo earlier that day.

Mike realizes that today is the birthday of his good friend Jill. Although he’s travelling and can’t meet her today, he wants to send Jill a personal birthday message. While Mike is sitting in a local coffee shop enjoying coffee and reading the latest news from the Internet using his brand-new Wireless Local Area Network (WLAN) device, he decides to send her a video clip as a birthday greeting. Jill is having a bath when she hears her phone ringing. She sees that she has received a message and checks it. She saves the video clip and decides to send something in return. Knowing that Mike knows her weird sense of humour, she sends a picture of herself taking a bath (Figure 1.3).

Peter Simpson is a Londoner and a die-hard Arsenal fan. With sheer luck he has managed to get tickets to an Arsenal–Tottenham derby and sets off to see the game. There he is, sitting at the stadium during the match, when suddenly he gets an irresistible urge to make his friend envious. He gets his mobile phone and makes a call to his friend John Clark, a Tottenham supporter. John is sitting at his desk and receives an incoming call pop-up on his PC screen, informing him that Peter is calling. He answers and they start to talk. Peter can’t contain himself and starts the video-sharing application while zooming onto the field. John receives an incoming video request and accepts the stream. The PC client starts to show the game, and with a pang of jealousy and disappointment John watches Arsenal score. ‘Nice goal, huh?’ asks Peter. ‘It ain’t over yet,’ says John, gritting his teeth, and ends the video stream. They continue to argue good-naturedly about the game and their teams over the phone.

Figure 1.3 Multimedia messaging

Figure 1.4 The role of the IMS in the packet switched networks

All the required communication takes place using the IP connectivity provided by the IMS as shown in Figure 1.4. The IMS offers the capability to select the best and most suitable communication media, to change the media during the session spontaneously, and use the preferred (SIP-capable) communication device over any IP access.

1.4 Where did it come from?

The European Telecommunications Standards Institute (ETSI) was the standardization organization that defined the Global System for Mobile Communications (GSM) during the late 1980s and 1990s. ETSI also defined the General Packet Radio Service (GPRS) network architecture. The last GSM-only standard was produced in 1998, and in the same year the 3GPP was founded by standardization bodies from Europe, Japan, South Korea, the USA and China to specify a 3G mobile system comprising Wideband Code Division Multiple Access (WCDMA) and Time Division/Code Division Multiple Access (TD-CDMA) radio access and an evolved GSM core network (www.3gpp.org/About/3gppagre.pdf). Most of the work and cornerstone specifications were inherited from the ETSI Special Mobile Group (SMG). The 3GPP originally decided to prepare specifications on a yearly basis, the first specification release being Release 99.

1.4.1 3GPP Release 99 (3GPP R99)

It took barely a year to produce the first release – Release 1999. The functionality of the release was frozen in December 1999 although some base specifications were frozen afterward – in March 2001. Fast completion was possible because the actual work was divided between two organizations: 3GPP and ETSI SMG. 3GPP developed the services, system architecture, WCDMA and TD-CDMA radio accesses, and the common core network. ETSI SMG developed the GSM/Enhanced Data Rates for Global Evolution (EDGE) radio access.

WCDMA radio access was the most significant enhancement to the GSM-based 3G system in Release 1999. In addition to WCDMA, UMTS Terrestrial Radio Access Network (UTRAN) introduced the Iu interface as well. Compared with the A and Gb interfaces, there are two significant differences. First, speech transcoding for Iu is performed in the core network. In the GSM it was logically a Base Transceiver Station (BTS) functionality. Second, encryption and cell-level mobility management for Iu are done in the Radio Network Controller (RNC). In GSM they were done in the Serving GPRS Support Node (SGSN) for GPRS services.

The Open Service Architecture (OSA) was introduced for service creation. On the service side the target was to stop standardizing new services and to concentrate on service capabilities, such as toolkits (CAMEL, SIM Application Toolkit and OSA). This principle was followed quite well, even though the Virtual Home Environment (VHE), an umbrella concept that covers all service creation, still lacks a good definition.

1.4.2 3GPP Release 4

After Release 1999, 3GPP started to specify Release 2000, including the so-called All-IP that was later renamed as the IMS. During 2000 it was realized that the development of IMS could not be completed during the year. Therefore, Release 2000 was split into Release 4 and Release 5.

It was decided that Release 4 would be completed without the IMS. The most significant new functionalities in 3GPP Release 4 were: the Mobile Switching Centre (MSC) Server–Media Gateway (MGW) concept, IP transport of core network protocols, Location Services (LCS) enhancements for UTRAN and multimedia messaging and IP transport for the Gb user plane.

3GPP Release 4 was functionally frozen and officially completed in March 2001. The backward compatibility requirement for changes, essential for the radio interface, was enforced as late as September 2002.

1.4.3 3GPP Releases 5 and 6

Release 5 finally introduced the IMS as part of 3GPP specifications. The IMS is supposed to be a standardized access-independent IP-based architecture that interworks with existing voice and data networks for both fixed (e.g., PSTN, ISDN, Internet) and mobile users (e.g., GSM, CDMA). The IMS architecture makes it possible to establish peer-to-peer IP communications with all types of clients with the requisite quality of services. In addition to session management, the IMS architecture also addresses functionalities that are necessary for complete service delivery (e.g., registration, security, charging, bearer control, roaming). All in all, the IMS will form the heart of the IP core network.

The content of Release 5 was heavily discussed and, finally, the functional content of 3GPP Release 5 was frozen in March 2002. The consequence of this decision was that many features were postponed to the next release – Release 6. After freezing the content, the work continued and reached stability at the beginning of 2004. The Release 5 defines a finite architecture for SIP-based IP multimedia service machinery. It contains a functionality of logical elements, a description of how elements are connected, selected protocols (see Chapter 2) and procedures (see Chapter 3). In addition, it is important to realize that optimization for the mobile communication environment has been also designed in the form of user authentication and authorization based on mobile identities (see Chapter 11), definite rules at the user network interface for compressing SIP messages (see Section 3.18) and security (see Section 3.21) and policy control mechanisms (see Section 3.10.3) that allow radio loss and recovery detection. Moreover, important aspects from the operator point of view are addressed while developing the architecture, such as the charging framework (see Section 3.11) and policy (see Section 3.10), and service control (see Section 3.13).

Release 6 IMS fixes the shortcomings in Release 5 IMS and also contains novel features. Release 6 was completed in September 2005. If Release 5 created the IMS machine we call Release 6 as the IMS application and interworking release. The Release 6 introduced standardized enhancements for services such as routing and signalling modifications e.g. Public Service Identity (see Section 3.5.5 and Section 12.11), sharing a single user identity between multiple devices (see Section 3.7). Improvements in routing capabilities smoothed the road to complete new standardized services such as presence (see Chapter 4), messaging (see Chapter 7), conferencing (see Chapter 8), PoC (see Chapter 6). In addition, IMS-CS voice interworking and WLAN access to IMS were completed. Moreover, improvements in security, policy and charging control and overall architecture were also completed.

1.4.4 IMS Development in other Standardization Development Organizations

While 3GPP has finalized its Release 5 and Release 6 other standardization development organizations have done parallel developments to define their IMS variants. Most notable development organizations having own variants are ETSI Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN), Third Generation Partnership Project 2 (3GPP2) and Cablelabs.

TISPAN is the outcome of the merger of two ETSI bodies and it is building specifications to enable migration from fixed circuit switched networks to fixed packet-based networks with an architecture that can serve in both, also known as Next Generation Network (NGN). December 2005 TISPAN declared that they have completed the first NGN release (Release 1) that contained IP multimedia component. This IP multimedia component was based on 3GPP Release 6 and 7 IMS with TISPAN specific extensions and modifications. Since 2005 TISPAN has been working with its Release 2 which is expected to be completed during 2008.

3GPP2 created its IMS variant to support CDMA2000 access. This IMS variant is also known as Multimedia Domain (MMD). 3GPP2 has used 3GPP IMS specification as a starting point and at the time of writing 3GPP2 has three MMD releases: MMD-0, MMD-A, MMD-B.

Cablelabs is a development consortium that is defining specification for cable operators. An IMS like building block is present in their PacketCable 2.0 release. Again Cablelabs is using 3GPP IMS as a baseline.

Figure 1.5 depicts major development paths of IMS standards. This figure clearly reveals that there exists fragmentation in the IMS standardization arena. Luckily the industry has taken decisive steps towards harmonized IMS, the common IMS. Common IMS technology in all mobile and fixed ecosystems provides economies of scale to both the operators and vendors in different ways. IMS vendors will be able to create the functionality once, and reuse it later. This means faster time to market, lower research and development cost due to eliminated replication effort. From an operator and service provider point of view it means that they will have a larger choice of vendors to select from and procurement cost of IMS products is lower. During 2007 3GPP and TISPAN made an agreement to stop IMS related development in TISPAN and focus all IMS development to 3GPP. Based on this agreement lot of functions and procedures developed in TISPAN Release 1 were included in 3GPP Release 7. TISPAN Release 2 is expected to be the last TISPAN release on IMS matters and functions and procedures are expected to be harmonized in 3GPP Release 8. Some Packetcable ‘IMS’ features were already included in 3GPP Release 7 and additional features and procedures originating from cable operators will be addressed in 3GPP Release 8. Harmonization of 3GPP2 MMD and 3GPP IMS is starting in Release 8. Due to late start full harmonization will probably happen in future 3GPP IMS releases.

Figure 1.5 Road to standardized common IMS standards

1.4.5 3GPP Release 7 and common IMS

3GPP Release 7 functional content was frozen in March 2007. It introduces two more access technologies (Data Over Cable Service Interface Specification (DOCSIS)¹ and xDSL²) and features and procedures originating from those and other general improvements. This can be considered as a step towards the ultimate goal of single common IMS. Major new features in Release 7 are: IMS multimedia telephony including supplementary services (see Chapter 9 and Chapter 12), SMS over any IP access (see Chapter 7, Section 7.4), Voice Call Continuity (see Section 3.20 and Chapter 13), local numbering (see Section 3.16), Combining CS calls and IMS sessions (see Section 3.19), Transit IMS (see Section 3.15), Interconnection Border Control Function (IBCF) (see Section 2.2.6.2), Globally Routable User Agent’s URI (see Section 3.5.6 and Section 12.10), IMS emergency sessions (see Section 3.17), Identification of Communication Services in IMS(see Section 12.3.9) and new authentication model for fixed access (see Section 3.21.2.3).

1.4.6 Insight to 3GPP Release 8

Standardization work on Release 8 is ongoing at the time of writing and work is expected to be completed by the end of 2008. This release will introduce a number of novel IMS features such as IMS centralized services which enables the use of IMS service machinery even though devices are using CS connection (GSM/3G CS radio) towards the network; multimedia session continuity which would improve the voice call continuity feature to enable continuity of multimedia media streams when IP access is changed; corporate access to IMS, a feature that enables integratation of IP-PBX to the IMS network; service level interworking for messaging and number portability.

1.5 Why a SIP Solution Based on 3GPP Standards?

IETF is the protocol factory for Internet world and it is doing great work in this space but it does not define the ways that they are used, especially in the mobile domain. 3GPP is the body that took Session Initiation Protocol (SIP) as the control protocol for multimedia communication and 3GPP has built a finite architecture for SIP-based IP multimedia service machinery (the IMS). It contains a functionality of logical elements, a description of how elements are connected, selected protocols and procedures. 3GPP standardized solutions are needed to provide: interoperability between terminals from different vendors, interoperability between network elements from different vendors, interoperability across operator boundaries. The following advantages of 3GPP IMS against a pure IETF SIP service model can be listed:

optimization for wireless usage:

– SIP compression (see Section 3.18);

– implicit registration (see Section 3.3);

– network initiated re-authentication (see Section 11.14.2);

– network initiated deregistration (see Section 11.15.3);

authentication:

– GPRS-IMS-Bundled Authentication (see Section 11.16);

– NASS-IMS-Bundled Authentication (see Section 3.21.2.3);

– ISIM/USIM authentication (see Section 11.6);

policy control (see Section 3.10):

– policy control and policy enforcement functions;

– Rx and Gx reference points;

– quality of Service (QoS);

charging (see Section 3.11):

– charging correlation (online and offline charging);

– charging entity information;

services and application server interfaces:

– ISC interface (see Section 2.3.3);

– Initial Filter Criteria (see Section 3.12.4);

access network information available in IMS (see Section 11.11.1);

mobility and roaming models defined (see Section 2.1.7);

visited network identification (see Section 11.11.2);

regulator requirements specified:

– emergency call (incl. location information) (see Section 3.17);

– legal interception;

– number portability.

¹ Access technology of Cablelabs.

² Access technology of TISPAN.

2

IP Multimedia Subsystem Architecture

This chapter introduces the reader to the Internet Protocol (IP) Multimedia Subsystem (IMS). Section 2.1 explains basic architectural concepts: for instance, we explain why bearers are separated and why the home control model was selected. Section 2.2 gives a wide overview of IMS architecture, including an introduction to different network entities and main functionalities. Section 2.3 goes deeper and shows how the entities are connected and what protocols are used between them; it also describes their relationships to other domains: IP networks, Circuit Switched Core Network (CS CN) and IP Connectivity Access Networks (IP-CAN).

2.1 Architectural Requirements

There is a set of basic requirements which guides the way in which the IMS architecture has been created and how it should evolve in the future. This section covers the most significant requirements. Third Generation Partnership Project (3GPP) IMS requirements are documented in [3GPP TS 22.228].

2.1.1 IP Multimedia Sessions

Existing communication networks are able to offer voice, video and messaging type of services using circuit-switched bearers. Naturally, end users’ service offerings should not decline when users move to the packet-switched domain and start using the IMS. The IMS will take communication to the next level by offering enriched communication means see e.g. Chapter 9 and Chapter 12. IMS users are able to mix and match a variety of IP-based services in any way they choose during a single communication session. Users can integrate voice, video and text, content sharing and presence as part of their communication and can add or drop services as and when they choose. For example, two people can start a session as a voice session and later on add a game or video component to the same session.

2.1.2 IP Connectivity

As the name IP Multimedia Subsystem implies, a fundamental requirement is that a device has to have IP connectivity to access it. Peer-to-peer applications require end-to-end reachability and this connectivity is most easily attained with IP version 6 (IPv6) because IPv6 does not have address shortage. Therefore, 3GPP has arranged matters so that the IMS exclusively supports IPv6 [3GPP TS 23.221]. However, early IMS implementations and deployments may use IP version 4 (IPv4). 3GPP has created recommendations about how IP version interworking is handled in the IMS [3GPP TR 23.981]. This is further described in Section 3.17.

IP connectivity can be obtained either from the home network or the visited network. The furthest left part of Figure 2.1 presents an option in which User Equipment (UE) has obtained an IP address from a visited network. In the UMTS network, this means that the Radio Access Network (RAN), Serving GPRS Support Node (SGSN) and Gateway GPRS Support Node (GGSN) are located in the visited network when a user is roaming in the visited network. The furthest right part of Figure 2.1 presents an option in which a UE has obtained an IP address from the home network. In the UMTS network this means that the RAN and SGSN are located in the visited network when a user is roaming in the visited network. Obviously, when a user is located in the home network all necessary elements are in the home network and IP connectivity is obtained in that network.

It is important to note that a user can roam and obtain IP connectivity from the home network as shown in the figure. This would allow users to use new, fancy IMS services even when they are roaming in an area that does not have an IMS network but provides IP connectivity. In theory, it is possible to deploy an IMS network in a single area/country and use, say, General Packet Radio Service (GPRS) roaming to connect customers to the home network. In practice, this would not happen because routing effciency would not be high enough. Consider routing Real-time Transport Protocol (RTP) voice packets from the USA to Europe and then back to the USA. However, this deployment model is important when operators are ramping up IMS networks or, in an initial phase, when they are offering non or near-real time multimedia services.

Figure 2.1 IMS connectivity options when a user is roaming

2.1.3 Ensuring Quality of Service for IP Multimedia Services

On the public Internet, delays tend to be high and variable, packets arrive out of order and some packets are lost or discarded. This will no longer be the case with the IMS. The underlying access and transport networks together with the IMS to provide end-to-end Quality of Service (QoS). Via the IMS, the UE negotiates its capabilities and expresses its QoS requirements during a Session Initiation Protocol (SIP) session setup or session modification procedure. The UE is able to negotiate such parameters as:

media type, direction of traffic;

media type bit rate, packet size, packet transport frequency;

usage of RTP payload for media types;

bandwidth adaptation.

After negotiating the parameters at the application level, UEs reserve suitable resources from the access network if not already available (typical case in mobile access). When end-to-end QoS is created, the UEs encode and packetize individual media types with an appropriate protocol (e.g., RTP) and send these media packets to the access and transport network by using a transport layer protocol (e.g., TCP or UDP) over IP. It is assumed that operators negotiate service-level agreements for guaranteeing the required QoS in the interconnection backbone. In the case of UMTS, operators could utilize the GPRS Roaming Exchange backbone.

2.1.4 IP Policy Control for Ensuring Correct Usage of Media Resources

IP policy control means the capability to authorize and control the usage of bearer traffic intended for IMS media, based on the signalling parameters at the IMS session. This requires interaction between the IP connectivity access network and the IMS. The means of setting up interaction can be divided into three different categories [3GPP TS 22.228, 23.207, 23.228]:

The policy control element is able to verify that values negotiated in SIP signalling are used when activating bearers for media traffic. This allows an operator to verify that its bearer resources are not misused (e.g., the source and destination IP address and bandwidth in the bearer level are exactly the same as used in SIP session establishment).

The policy control element is able to enforce when media traffic between the end points of a SIP session start or stop. This makes it possible to prevent the use of the bearer until session establishment is completed and allows traffic to start/stop in synchronization with the start/stop of charging for a session in IMS.

The policy control element is able to receive notifications when the IP connectivity access network service has either modified, suspended or released the bearer(s) of a user associated with a session. This allows IMS to release an ongoing session because, for instance, the user is no longer in the coverage area.

This is described further in Section 3.10.

2.1.5 Secure Communication

Security is a fundamental requirement in every telecommunication system and the IMS is not an exception. The IMS has its own authentication and authorization mechanisms between the UE and the IMS network in addition to access network procedures (e.g., GPRS network). Moreover, the integrity and optional confidentiality of the SIP messages is provided between the UE and the IMS network and between IMS network entities regardless of the underlaying core network (e.g., RAN and GPRS). Therefore, the IMS provides at least a similar level of security as the corresponding GPRS and circuit-switched networks: for example, the IMS ensures that users are authenticated before they can start using services, and users are able to request privacy when engaged in a session. Section 3.21 will discuss security features in more detail. An overview of applied security solutions is depicted in Figure 2.2.

2.1.6 Charging Arrangements

From an operator or service provider perspective the ability to charge users is a must in any network. The IMS architecture allows different charging models to be used. This includes, say, the capability to charge just the calling party or to charge both the calling party and the called party based on used resources in the transport level. In the latter case the calling party could be charged entirely on an IMS-level session: that is, it is possible to use different charging schemes at the transport and IMS level. However, an operator might be interested in correlating charging information generated at transport and IMS (service and content) charging levels. This capability is provided if an operator utilizes a policy control reference point. The charging correlation mechanism is further described in Section 3.11.7 and policy control is explained in Section 3.10.

As IMS sessions may include multiple media components (e.g., audio and video), it is required that the IMS provides a means for charging per media component. This would allow charging the called party if they add a new media component in a session. It is also required that different IMS networks are able to exchange information on the charging to be applied to a current session [3GPP TS 22.101, TR 23.815].

The IMS architecture supports both online and offline charging capabilities. Online charging is a charging process in which the charging information can affect in real time the service rendered and, therefore, directly interacts with session/service control. In practice, an operator could check the user’s account before allowing the user to engage a session and to stop a session when all credits are consumed. Prepaid services are applications that need online charging capabilities. Offline charging is a charging process in which the charging information does not affect in real time the service rendered. This is the traditional model in which the charging information is collected over a particular period and, at the end of the period, the operator posts a bill to the customer.

Figure 2.2 Overview of IMS security

Figure 2.3 IMS charging overview

Figure 2.3 shows a simplified view of general charging arrangements in an IMS environment. The key observation is: the IMS adds the possibility to charge for user IP traffic in a more granular manner than before.

2.1.7 Support of Roaming

From a user point of view it is important to get access to their services regardless of their geographical location. The roaming feature makes it possible to use services even though the user is not geographically located in the service area of the home network. Section 2.1.2 has already described two instances of roaming: namely, GPRS roaming and IMS roaming. In addition to these two there exists an IMS circuit switched roaming case. GPRS roaming means the capability to access the IMS when the visited network provides the RAN and SGSN and the home network provides the GGSN and IMS. The IMS roaming model refers to a network configuration in which the visited network provides IP connectivity (e.g., RAN, SGSN, GGSN) and the IMS entry point (i.e., P-CSCF) and the home network provides the remaining IMS functionalities. The main benefit of this roaming model compared with the GPRS roaming model is optimum usage of user-plane resources. Roaming between the IMS and the CS CN domain refers to inter-domain roaming between IMS and CS. When a user is not registered or reachable in one domain a session can be routed to the other domain. It is important to note that both the CS CN domain and the IMS domain have their own services and cannot be used from another domain. Some services are similar and available in both domains (e.g., Voice over IP in IMS and speech telephony in CS CN). Figure 2.4 shows different IMS/CS roaming cases.

Figure 2.4 IMS/CS roaming alternatives

2.1.8 Interworking with Other Networks

It is evident that the IMS is not deployed over the world at the same time. Moreover, people may not be able to switch terminals or subscriptions very rapidly. This will raise the issue of being able to reach people regardless of what kind of terminals they have or where they live. To be a new, successful communication network technology and architecture the IMS has to be able to connect to as many users as possible. Therefore, the IMS supports communication with PSTN, ISDN, mobile and Internet users. Additionally, it will be possible to support sessions with Internet applications that have been developed outside the 3GPP community [3GPP TS 22.228]. Voice and video IMS-CS interworking is further described in Section 3.14. Messaging interworking is covered in Section 7.4.

2.1.9 Service Control Model

In 2G mobile networks the visited service control is in use. This means that, when a user is roaming, an entity in the visited network provides services and controls the traffic for the user. This entity in the second generation (2G) is called a visited mobile service switching centre. In the early days of Release 5 both visited and home service control models were supported. Supporting two models would have required that every problem have more than one solution; moreover, it would reduce the number of optimal architecture solutions, as simple solutions may not fit both models. Supporting both models would have meant additional extensions for Internet Engineering Task Force (IETF) protocols and increased the work involved in registration and session flows. The visited service control was dropped because it was a complex solution and did not provide any noticeable added value compared with the home service control. On the contrary, the visited service control imposes some limitations. It requires a multiple relationship and roaming models between operators. Service development is slower as both the visited and home network would need to support similar services, otherwise roaming users would experience service degradations. In addition, the number of interoperator reference points increase, which requires complicated solutions (e.g., in terms of security and charging). Therefore, home service control was selected; this means that the entity that has access to the subscriber database and interacts directly with service platforms is always located at the user’s home network.

2.1.10 Layered Design and Access Independence

3GPP has decided to use a layered approach to architectural design. This means that transport and bearer services are separated from the IMS signalling network and session management services. Further services are run on top of the IMS signalling network. Figure 2.5 shows the design.

In some cases it may be impossible to distinguish between functionality at the upper and lower layers. The layered approach aims at a minimum dependence between layers. A benefit is that it facilitates the addition of new access networks to the system later on. The IMS was originally designed to be access-independent so that IMS services can be provided over any IP connectivity network. Unfortunately, Release 5 IMS specifications contain some GPRS-specific features. In Release 6 onwards access-specific issues are separated from the core IMS description and the IMS architecture returned to its born state (i.e., access independent). A number of different accesses have been added since then. Wireless Local Area Network (WLAN) access to the IMS was added in 3GPP Release 6, fixed broadband access was added in Release 7 and additional access like DOCSIS®, WiMAX™ and cdma2000® are being harmonized in Release 8 and post Release 8 as shown in Figure 2.6.

Figure 2.5 IMS and layered architecture

Figure 2.6 Access independence

The layered approach increases the importance of the application layer as services are designed to work independently of the access network and the IMS is equipped to bridge the gap between them. Whether the subscriber is using a mobile phone or a PC client to communicate, the same presence and group list functions in IMS will be used. Different services have different requirements. These include:

bandwidth;

latency;

processing power in the device.

This means that in order for different services to be executed properly, the network has to be equipped with access-aware control and service logic for multimedia services. Multi-access functionality is built into the IMS architecture, which offers a way for fixed and mobile operators to deliver a fixed to mobile convergence solution. This will enable service providers to use the characteristics and capabilities of the currently selected device and its network access method and adapt to it dynamically.

2.2 Description of IMS-related Entities and Functionalities

This section discusses IMS entities and key functionalities. These entities can be roughly classified into six main categories:

session management and routing family (CSCFs);

databases (HSS, SLF);

services (application server, MRFC, MRFP);

interworking functions (BGCF, MGCF, IMS-MGW, SGW);

support functions (PCRF, SEG, IBCF, TrGW, LRF);

charging.

It is important to understand that IMS specifications are set up so that the internal functionality of the network entities is not specified in detail. Instead, specifications describe reference points between entities and functionalities supported at the reference points. For instance, how does CSCF obtain user data from databases? Different reference points will be described in Section 2.3. Additionally, GPRS functions are described at the end of this section.

2.2.1 Call Session Control Functions (CSCF)

There are four different kinds of Call Session Control Functions (CSCF): Proxy-CSCF (P-CSCF), Serving-CSCF (S-CSCF), Interrogating-CSCF (I-CSCF) and Emergency-CSCF (E-CSCF). Each CSCF has its own special tasks and these tasks are described in the following subsections. Common to P-CSCF, S-CSCF and I-CSCF is that they all play a role during registration and session establishment and form the SIP routing machinery. Moreover, all functions are able to send charging data to an offline charging function. There are some common functions that P-CSCF and S-CSCF are able to perform. Both entities are able to release sessions on behalf of the user (e.g., when S-CSCF detects a hanging session or P-CSCF receives a notification that a media bearer is lost) and are able to check that the content of the SIP request or response conforms operator’s policy and user’s subscription (e.g. content of the Session Description Protocol (SDP) payload contains media types or codecs, which are allowed for a user).

2.2.1.1 Proxy Call Session Control Function (P-CSCF)

Proxy Call Session Control Function (P-CSCF) is the first contact point for users within the IMS. It means that all SIP signalling traffic from the UE will be sent to the P-CSCF. Similarly, all terminating SIP signalling from the network is sent from the P-CSCF to the UE. There are four unique tasks assigned for the P-CSCF: SIP compression, IPSec security association, interaction with Policy and Charging Rules Function (PCRF) and emergency session detection.

As the SIP protocol is a text-based signalling protocol, it contains a large number of headers and header parameters, including extensions and security-related information which means that their message sizes are larger than with binary-encoded protocols. For speeding up the session establishment 3GPP has mandated the support of SIP compression between the UE and P-CSCF. The P-CSCF needs to compress messages if the UE has indicated that it wants to receive signalling messages compressed. SIP compression is described in Sections 3.18 and 11.10 and 12.4.

P-CSCF is responsible for maintaining Security Associations (SAs) and applying integrity and confidential protection for SIP signalling. This is achieved during SIP registration as the UE and P-CSCF negotiate IPSec SAs. After the initial registration the P-CSCF is able to apply integrity and confidential protection of SIP signalling. See Sections 11.6 and 11.7 and 11.8 for more detailed descriptions.

The P-CSCF is tasked to relay session and media-related information to the PCRF when an operator wants to apply policy and charging control. Based on the received information the PCRF is able to derive authorized IP QoS information and charging rules that will be passed to the access gateway (e.g. GGSN). This concept is covered in Section 3.10. Moreover, via the PCRF and P-CSCF the IMS is able to deliver IMS charging correlation information to the access network and, similarly, via the PCRF and P-CSCF the IMS is able to receive access charging correlation information from the access network. This makes it possible to merge charging data records coming from the IMS and access networks in the billing system. How this is done is shown in Section 3.11.7.

P-CSCF plays an important role in IMS emergency session handling as the P-CSCF is tasked to detect emergency requests in all possible cases. P-CSCF is expected to reject emergency attempts based on operator policy (e.g. user is attempting to make emergency call via home P-CSCF when roaming) or based on network capability (P-CSCF or the rest of the IMS core is pre-Release 7 which do not support IMS functionality.

2.2.1.2 Interrogating Call Session Control Function (I-CSCF)

Interrogating Call Session Control Function (I-CSCF) is a contact point within an operator’s network for all connections destined to a subscriber of that network operator. There are three unique tasks assigned for the I-CSCF:

Obtaining the name of the next hop (either S-CSCF or application server) from the Home Subscriber Server (HSS).

Assigning an S-CSCF based on received capabilities from the HSS. The assignment of the S-CSCF will take place when a user is registering with the network or a user receives a SIP request while they are unregistered from the network but has services related to an unregistered state (e.g., voice mail). This procedure is described in