UMTS Core Network

UMTS System Overview

Informa

Telecoms

UMTS Core Network

UMTS Core Network

1. CORE NETWORK ARCHITECTURE AND FUNCTIONS 1.1 Review of Core Network Architecture & Elements (R 99) 1.2 The main functions provided by the core network 1.3 The User Equipment and The Core Network THE 2.1 2.2 2.3 CORE NETWORK CS DOMAIN User and Control Information in the CS Domain Signalling in the CS Domain SS7 Overview CS Domain Control Plane Protocols: the SS7 Protocol Stack 2.4 CS Domain User Plane Control Protocols THE CORE NETWORK PS DOMAIN 3.1 User and Control Information in the PS Domain 3.2 PS Domain Protocols 1: GSN to Service/Database communications 3.3 PS Domain Protocols 2: GSN to GSN communications 3.4 Tunnelling MOBILE IP 4.1 Mobile IP: Basics 4.2 Mobile IPv4 vs. IPv6 CORE NETWORK TRANSMISSION CHARGING NETWORK MANAGEMENT IN/CAMEL IN UMTS 8.1 Intelligent Networks 8.2 CAMEL 1 3 5 7 9 11 13 15 17 19 21 25 27 29 31 33 35 37 39 41

2.

3.

4.

5. 6. 7. 8.

ANNEX 1 OSI 7 LAYER MODEL A.1 Protocols & Stack: Basics A.2 The OSI Model

UMTS System Overview

Informa

Telecoms

UMTS Core Network

1. CORE NETWORK ARCHITECTURE AND FUNCTIONS

1.1 Review of Core Network Architecture & Elements (R 99)
The Core Network of UMTS, in its first release, is taken directly from the architecture and elements of GSM Phase 2+. Two domains are defined, circuit switched (CS) and packet-switched (PS). The latter is provided by the implementation of GPRS within the GSM network. These two transport and signalling domains will both interact with a number of databases, which are sometimes grouped under the Home Server Subsystem (HSS), and with service platforms such as the CAMEL Service Environment (CSE), which provide services and support for the Virtual Home Environment. The two key elements of the Circuit-Switched domain are as follows: Serving MSC (MSC), the switching node at which the core network interfaces to that part of the access network in which the mobile station is located. The Serving MSC interacts with, or includes, a database called the Visitor Location Register (VLR), containing information regarding the mobile stations which it is currently serving. Gateway MSC (GMSC), the switching node which connects a UMTS core network with an external circuit-switched network, such as ISDN or PSTN. The two key and equivalent elements in the Packet-Switched domain are: Serving GPRS Support Node (SGSN), the packet router at which the core network interfaces to the part of the access network in which the mobile station is located. Gateway GSN (GGSN), another packet router, connecting the UMTS core network with an external packet-switched network, such as the Internet, X.25 or similar. In many networks, the Serving MSC/VLR and the SGSN will interact in order to ensure better integrated management and information updating between PS and CS services. The HSS includes database such as the Home Location Register (HLR), which includes a variety of subscriber related data, enabling users to be offered the services to which they are entitled. Also included within the HSS is the database for authentication. The interface connecting the core and radio access networks (at the Serving MSC and SGSN) is known as the Iu Interface, and is fully defined in UMTS. This interface is subdivided into the IuPS and IuCS, in order to support each domain in the core network, but within this subdivision there remains much commonality. An important new feature of UMTS is that the core network and radio access network are kept entirely separate and independent by means of this Iu Interface, allowing any UMTS core network to be connected to any UMTS radio access network.

UMTS System Overview

1
Informa

Telecoms

PS Domain Internet, X.25 etc

CS Domain ISDN, PSTN

GGSN

GMSC

CORE NETWORK

HSS, OSA, CSE etc

SGSN

MSC/ VLR

luPS

luCS

RADIO ACCESS NETWORK

Fig. 1 Core Network Architecture (R 99)

Informa

Telecoms

UMTS Core Network

1.2 The main functions provided by the core network

The core network must facilitate the transport of user data between the Mobile station and the application with which it is interacting, be that application resident in the core network itself, or operating on some remote party. In addition to user data transport, the core network is involved in or controls a number of important processes which are required in order that services can be offered. These processes involve signalling and control information transport (described as the control plane) within the core network which will generally be dealt with separately from user data transport (user plane). The key functions are: Mobility Management (MM), including security functions Connection Management (CM) Session Management (SM) charging network management interworking with external networks service provision (hosting of Open Service Architecture, CAMEL etc.) MM, CM & SM messages are not interpreted by the radio access network. They are simply exchanged between the MSC/SGSN and the mobile station, transparent to the UTRAN. Note that Connection Management incorporates Call Control (CC), Supplementary Services (SS) and Short Message Service Point-to-Point (SMS). Unlike CC and SS, the Short Message Service can be provided via Circuit Switched or Packet Switched domains.

UMTS System Overview

3
Informa

Telecoms

 Transport of User Data Mobility Management (MM) Connection Management (CM) Bearer Management Call Control Supplementary Services Short Message Service Session Management (SM) Charging Network Management

CS and PS CS and PS CS

PS CS and PS CS and PS

Interworking with external networks CS and PS Service Provision (hosting of Open Service Architecture, CAMEL etc.) Security

CS and PS CS and PS

CS Applicable to the CS domain PS Applicable to the PS domain

Fig. 2 Main Functions of the Core Network

Informa

Telecoms

UMTS Core Network

1.3 The User Equipment and The Core Network

The main functions of the core network can be provided only if sufficient control information is passed between the core network and user equipment. Hence Mobility Management, Connection Management (incorporating Call Control, Short Message Service and Supplementary Services), and Session Management protocols have been specified. These protocols were all initially specified within GSM. UTRAN has been specified to carry both User Data and the necessary control information (MM, CM and SM). An additional protocol called Radio Resources Control (RRC) is used between UTRAN and the User Equipment to set up radio bearers for both the user data and control information. The control information (MM, CM and SM messages) are transferred from Core Network to the UTRAN within a further protocol called Radio Access Network Application Protocol, and then through the UTRAN within RRC messages. User data is simply framed and transferred through the UTRAN.

UMTS System Overview

5
Informa

Telecoms

Connection Management, Session Management Mobility Management CORE NETWORK

Signalling Bearer Provided by UTRAN and Radio Resources /RANAP Protocols

Note: User Data is transferred on the User Plane

Fig. 3 CN to UE Control Plane

Informa

Telecoms

UMTS Core Network

2. THE CORE NETWORK CS DOMAIN

2.1 User and Control Information in the CS Domain
Within the CS Domain of the Core Network, MSCs provide the switching functionality and control for setting up, tearing down and supervising circuits, as well as some support for supplementary services. In addition, the HLR and SCP provide support for Mobility and Operator Specific Services respectively. The VLR also provides support for mobility and is co-located with the MSC. This is illustrated in Fig 4. User data is transferred between MSCs, and between the GMSC and external network via traffic circuits, without further protocols being added (although overhead is introduced at the physical level, the amount and format being dependent on the transmission system being used). The control information is passed within Signalling System Number 7 protocols, and makes use of the lower layer signalling network (which would usually share the same transmission infrastructure as the user data).

UMTS System Overview

7
Informa

Telecoms

HLR

Signalling (Control Information) Circuits (User Data)

SCP 3

MSC

MSC/ VLR

GMSC

MSC 1
Cir ata D cui r t ( U se )

Core Network 1 User Data 2 Traffic Channel Set Up, Clear Down and Supervision (includes Supplementary Service Support)

3 Service Control 4 Mobility Management

Fig. 4 User and Control Information in the CS Domain

Informa

Telecoms

UMTS Core Network

2.2 Signalling in the CS Domain SS7 Overview

In the circuit-switched domain, MSCs are switching centres which hold all the switching functions needed to support mobiles in their area, routing transmission paths for both the actual user data, and the signalling messages needed to control services. They may also hold interworking functions required to interwork with other networks such as the PSTN. These MSCs are connected to each other and to the HLR and other databases using a variation of the ITU standardised SS7 (signalling system 7). SS7 is a commonchannel signalling system, and the circuit-switched user data network is actually separated from the packet-switched SS7 signalling network. SS7 operates using a specified stack of protocols. SS7 provides call control by exchanging control messaging between the MSCs and fixed network switches. This may be via direct paths or via signalling transfer points (STPs), designed to route packets across this network. A third entity, the service control point (SCP), is a database which may control information relevant to routing, for example translating a freephone (0800) number into a routing address within the network. No longer do individual switches need to be modified to introduce a new service. Instead, such changes are made to the SCP elements within the signalling network, which controls the user data switching performed at the MSCs/Switches. The SCPs and MSCs/Switches communicate via a standardised interface, and (if it has this functionality), the MSC/Switched is termed a Service Switching Point (SSP). In the UMTS CS domain, the MSCs correspond to the SS7 SSPs, providing both basic switching, plus access points to supplementary and advanced IN services. Location registers, such as the HLR and VLR, and additional service elements such as the CAMEL Service Environment, are similar in functionality to the SCPs. Where remote data bases are being accessed, a Signalling Point Relay (SPR) allows the SS7 entitys unique global address to be translated into the simpler format (point codes) used in the individual SS7 packet-switched networks (called the Message Transfer Port), as the signalling message is passed from one network to another en-route to its remote destination.

UMTS System Overview

9
Informa

Telecoms

SS7 NETWORK

MSC (SSP)

STP

STP

MSC (SSP)
Signalling between MSCs may be direct or via STPs SPRs are also available for accessing remote databases

Fig. 5 SS7 within the Core Network CS Domain

Informa

Telecoms

User Data

Databases (SCP, HLR, CSE)

10

UMTS Core Network

2.3 CS Domain Control Plane Protocols: the SS7 Protocol Stack

In mobile networks, there is a high proportion of signalling messages which is necessary to ensure that the relevant control information is passed between the various network entities. This control information is in addition to the standard call control messages found in basic fixed networks. More protocols are involved due to the complex nature of the SS7 network when extended to such controlling entities. The protocols are described below. Delivery via MTP levels 1, 2 and 3 is common to both the (database) control information and the standard call control messages. Communication between MSCs and between MSCs and location registers within the CS domain utilises the protocol stack shown in Fig , the functions of which define the SS7 network. Above the physical layer, which defines the actual physical network over which the signalling information is transmitted, sit three elements which comprise the network services layer of the standard SS7 protocol stack: MTP2, Message Transfer Part Level 2 This is known as the Signalling Link Level and ensures reliable transmission through flow control, sequence validation, error checking and so on, and is applied to individual SS7 links. MTP3, Message Transfer Part Level 3 This is the Signalling Network Level, providing message handling (routing) and signalling network management for the signalling messages themselves. SCCP These two layers, in combination with the underlying physical infrastructure provide a highspeed, low-delay, connectionless link. The 3rd element of the network services layer lies above these, and is known as the Signalling Connection Control Protocol (SCCP), providing the link through which higher level protocols can communicate via SS7. Transaction Capabilities Above this Network Services Layer is the Transaction Capabilities Application Part, TCAP , again a standard SS7 protocol. TCAP is used above the previous layers to control the non circuit-related communications between the signalling nodes. These communications between signalling nodes are the control functions and procedures which for example query the various databases, perform mobility management and support the other components to provide specific services (for example communication between the GMSC and HLR). MAP In GSM networks, the actual GSM information, functions and procedures are contained within the Mobile Application Part (MAP) messages. MAP is used to control implementation of functions such as location updating & roaming, SMS delivery, authentication and call routing, supplementary service support. This is also the case for UMTS.

UMTS System Overview

11
Informa

Telecoms

CAP TCAP SCCP MTP3 MTP2

Physical Layer

HLR

MAP TCAP SCCP MTP3 MTP2

Physical Layer

SCP

MSC

MSC/ VLR

GMSC

MSC
)

Cir ata D cui t ( U ser

Core Network

MAP Mobile Application Part (Mobility Management) CAP CAMEL Application Part (Service Control)

Fig. 6 CS Domain Protocols (Non Circuit-Related Signalling)

Informa

Telecoms

12

UMTS Core Network

CAP
An exception to the use of MAP for control messages occurs where CAMEL is present. In this case communication between the CAMEL Service Environment (CSE) and the MSC is carried as CAMEL Application Part (CAP) messages, although signalling between the CSE and HLR and other databases still uses MAP.

2.4 CS Domain User Plane Control Protocols

Although control plane (signalling) data is transferred across the SS7, packetswitched network made up of the MSCs and intervening STPs, the user data itself simply transfers across the circuit-switched network between MSCs. The lower layers of the SS7 protocols are still applied, MTP2 & MTP3, providing routing and reliability of the Call Control messages themselves. TCAP is required only to control the non circuit-related information of MAP or CAP messages, and so is not relevant to the circuit-switched call. Instead, the ISDN User Part (ISUP) protocol is used to provide control for these circuit-switched user services, both between MSCs and between MSCs and switches of other external networks. Since ISUP includes basic functionality for the establishment and clearing of CS calls, ISUP lies directly above the MTP3 layer, replacing also the functions of SCCP. A protocol known as TUP can also be used for communications between MSCs and other networks, and is another standard SS7 protocol, but provides fewer features than ISUP.

UMTS System Overview

13
Informa

Telecoms

HLR

ISUP MTP3 MTP2

Physical Layer

SCP

MSC

MSC/ VLR

GMSC

MSC
)

ta Cir Da cui r e t ( Us

Core Network

ISUP ISDN User Part (Traffic Channel Set Up, Clear Down and Supervision (includes Supplementary Service Support)

Fig. 7 CS Domain Protocols (Circuit-Related Signalling)

Informa

Telecoms

14

UMTS Core Network

3. THE CORE NETWORK PS DOMAIN

3.1 User and Control Information in the PS Domain
The Packet-Switched domain uses packets of information to carry both user data and the control information for the user data between GSNs. This means a common set of packet protocols can be defined to allow this exchange of information to take place. The intermediate routers handle the information in the same way, simply routing it on to its final destination (the SGSN or GGSN). For mobility control and provision of operator specific services, the GSNs communicate with the HLR and SCP respectively using the standard techniques found within the Circuit-Switched domain.

UMTS System Overview

15
Informa

Telecoms

HLR

Signalling (Control Information) Packets of Data (Control and User Information)

4 3

SCP

Router

SGSN

GGSN

2
Pa cke ts (U

Router

s er & C

) ata D rol ont

Core Network

1 2 3 4

User Data Control Data Service Control Mobility Management

Fig. 8 User and Control Information in the PS Domain

Informa

Telecoms

16

UMTS Core Network

3.2 PS Domain Protocols 1: GSN to Service/Database communications

Within the PS Domain, packets of actual user data, plus any higher layer control information, pass transparently between the external data network and the mobile station, using tunnelling and encapsulation. The GGSN and SGSN are simply routers, which send these data packets on to the correct location, based on the PDP Context. However signalling & control communications may occur not only between the SGSN and GGSN, but also between the SGSN/GGSN and the HLR, SMS-GMSC, SMSIWMSC and other components which are shared with the CS domain. For signalling communication between a GSN and one of these common CS/PS domain elements, the same protocol stack as in the CS domain is used, consisting of MAP or CAP lying above a standard SS7 protocol stack. An interworking function is required at the GSN to convert between this stack and a different protocol stack which is used for communications between the SGSNs and GGSNs. One exception to this is in the case of signalling between the SGSN and MSC/VLR. In this case, a protocol known as the Base Station Subsystem Application Part + (BSSAP+) is used in place of the TCAP & MAP layers, although this is simply an enhanced version of the standard protocol used between the MSC and BSC in GSM.

UMTS System Overview

17
Informa

Telecoms

GSN HLR, CSE, SMS-GMSC etc

SGSN

MSC/VLR

MAP/CAP BSSAP+ TCAP

SCCP

MTP3

MTP2

Physical Layer

Fig. 9 PS Domain Protocols 1 Control Signalling Between GSN and Service/Mobility Databases
Informa

Telecoms

18

UMTS Core Network

3.3 PS Domain Protocols 2: GSN to GSN communications

The protocol stack for communication between two GSNs can be described in five layers. Since the purpose of this communication is simply to route PDUs which arrive at the GGSN through to the user via the SGSN, whether the PDU consists of just user data or user data plus some higher level control information is irrelevant. Each node just sees this PDU as a packet of information to be tunnelled. L1 and L2 are equivalent to the Physical Layer and Network Interface Layer of the standard TCP/IP protocol stack most commonly associated with the Internet. L1 controls the physical network hardware, and L2 describes how to organise the data for transmission over the physical network. These layers are not defined in the core network in the first phase of UMTS, although they are defined to support ATM at the interface between the core network and UTRAN (the Iu Interface). IP is used on the next layer, the internet layer of TCP/IP, to specify the format of packets, and the mechanisms to forward these packets to the correct nodes. Nodes must have valid IPv4 addresses in order to achieve this, with IPv6 as an option, and the likely direction of future evolution. The next layer, the transport layer, uses either UDP, the User Datagram Protocol or TCP. UDP sends a message from one application to another, without requiring that the destination application be active. It is therefore connectionless, but does not guarantee delivery or protection against duplicate data. However it does allow very rapid data transfer, and minimum network resource and requirements. TCP is used for protocol data units which require a reliable connection, since TCP supports reliable, point-to-point, connection oriented services. In particular, TCP will ensure that transmission is repeated if packets are lost, and that connections dont shut down until all data has been transferred. Finally, above UDP/TCP is the GPRS Tunnelling Protocol, GTP. GTP includes both signalling (GTP-C) and data transfer (GTP-U) procedures, and allows multi-protocol packets to be tunnelled through the PS domain core network between the GGSN and SGSN and (after conversion for the Iu interface) onwards through the UTRAN to the end user.

UMTS System Overview

19
Informa

Telecoms

USER INFORMATION PACKET DATA UNITS PDU'S

Information to be "tunnelled" GTP-U (User) GTP-C (Control)

UDP/TCP

IP

L2

L1

Fig. 10 PS Domain Protocols 2 GSN to GSN Communications

Informa

Telecoms

20

UMTS Core Network

3.4

Tunnelling

3.4.1 Tunnelling in the PS Domain 1: Transmission

The GGSN provides interworking with external packet-data networks, and connects to the SGSN via an IP-based backbone network. The actual structure of this IP network is not important, since the aim is simply to tunnel data packets through it, using the PDP context information. Tunnelling occurs in both directions. Packet Data Units (PDUs) arrive at the GGSN or SGSN as either IP datagrams or X25 packets. The GTP encapsulates the PDU, by adding a GTP header. For signalling purposes, GTP can specify a tunnel control protocol which is used to create, modify and delete tunnels, with the effect of allowing the SGSN to provide network access to the mobile station. This packet is then handed down to be encapsulated further as either UDP or TCP, and finally down to the IP layer, where an IP header is added. This IP header contains the address of the SGSN or GGSN to which the message should be tunnelled. In cases where the final IP Datagram which results from encapsulation through these layers is bigger than a defined maximum transfer unit (defined to ensure speed and reliability of connection), the datagram may then need to be fragmented. Note that the GTP protocol is also used to tunnel packets of data over the Iu Interface between the core network and UTRAN.

UMTS System Overview

21
Informa

Telecoms

PDU

GTP

Header, Tunneling Info

UDP/TCP

Header

IP

Header (IPv4 Address) Fragmentation

Prepare for Transmission

Fig. 11 Tunnelling Transmission

Informa

Telecoms

22

UMTS Core Network

3.4.2 Tunnelling in the PS Domain 2: Reception

IP datagrams which arrive at the SGSN or GGSN (or RNC for Iu Interface tunnels) are first reassembled if they were fragmented, and then the IP header is removed. This payload is then passed upwards to the UDP/TCP layer, with processes such as checksum performed as required, and the UDP/TCP header is removed. Finally the GTP layer strips off the GTP header such that the PDU is now ready for transport across to the Radio Access Network or into the external network. This latter process requires further modification, via an interworking function, in order to format the PDU ready for transport across the Iu Interface.

UMTS System Overview

23
Informa

Telecoms

PDU

GTP

Remove Header

UDP/TCP

Checksum etc

IP

Remove Header Reassemble

Received Data

Fig. 12 Tunnelling Reception

Informa

Telecoms

24

UMTS Core Network

4. MOBILE IP
4.1 Mobile IP: Basics
Mobile IP is an ongoing standardisation project within the IETF (Internet Engineering Task Force), who are now also a market representation partner within 3GPP. The aim of Mobile IP is to enable a mobile to communicate using the same IP address at all times, regardless of the IP network through which it accesses the Internet. If this were not the case, then active TCP sessions would be broken each time the mobile wanted to access through a different network (e.g. UMTS vs. LAN), meaning that guarantees of service quality, and a seamless view for the application, would not be possible. Mobile IP provides a mechanism whereby a mobile station is given a permanent IP home address, which belongs within its original home network. If accessing through this home network, it will therefore just act like any non-mobile station and can be reached through normal IP routing. However when it accesses through some visited network, it is assigned a care of address (COA) which belongs to this visited network, and which identifies the current location of the mobile. Since other stations do not know the location of the mobile, they will send packets to its permanent home address, where the packets are received by a router which is assigned the status of the home agent (HA). This HA forwards packets onto the mobile station using tunnelling, having previously been provided with the COA by the mobile. The mobile station can answer directly to the other station, although using its home address rather than the COA as the source address for the message. Any time the mobile station moves to attach via a different IP subnetwork, it will register its new COA with its HA.

UMTS System Overview

25
Informa

Telecoms

Home Agent

Permanent (Home) Address

COA Can Answer Direct (Uses Home Address, not COA) Caller Called

Visited Network

COA Care of Address

Fig. 13 Mobile IP
Informa

Telecoms

26

UMTS Core Network

4.2 Mobile IPv4 vs. IPv6

In the case of IPv4, a COA address will most likely be a router, called the foreign agent (FA), which will have the functionality to enable it to forward messages on to the mobile station. A single COA may apply to more than one mobile station. Overlaying Mobile IP onto a GPRS/UMTS network means enabling the GGSN to have this FA functionality, able to set up a PDP context for the mobile station, and tunnel PDUs from the GGSN towards the user. A key advantage in moving to IPv6 is that the number of IP addresses available becomes effectively unlimited. It is possible to assign mobile stations a direct COA, using some form of automatic assignment mechanism. Messages from the home agent can be tunnelled directly towards the mobile station. If the mobile station has a direct COA, then the core network tunnelling provided by GTP becomes redundant, since data can be tunnelled directly from source to user. Indeed it will be possible to combine the GGSN and SGSN into a single Internet GPRS Support node (IGSN), which acts as the FA and marks the end of the UMTSspecific network. The IGSN would need to support current SGSN functionality, supporting MAP communication with UMTS location registers, plus of course support Mobile IP and any accounting procedures required by an FA. In effect, an ultimate scenario is that Mobile IP may handle mobility management and tunnelling within the PS domain core network.

UMTS System Overview

27
Informa

Telecoms

a) IPv4 Plus GPRS/UMTS

HA PDP/ GTP SGSN PDP/ GTP GGSN/ FA

COA

Visited Network COA Care of Address HA Home Agent FA Foreign Agent IGSN Internet GPRS Support Node

b) IPv6 Plus GPRS/UMTS

HA

COA COA IGSN

Visited Network

Fig. 14 Mobile IP Evolution

Informa

Telecoms

28

UMTS Core Network

5. CORE NETWORK TRANSPORT

The CS Domain will in most cases be brought forward directly from an operators existing GSM Phase 2+ core network. Such networks commonly use PDH or SDH, although there is no standard specified for this. Equally in the PS domain, no standard transport is specified any IP network can lie between the GGSN and SGSN. ATM is a common choice, since it is designed for robust support of packet networks. ATM is already specified for transport within the UTRAN. It seems likely that both core network domains may also migrate to ATM in UMTS networks, particularly when operators seek to combine the transport systems of the CS and PS domains, a major goal behind the network architectures proposed in Release 4 and beyond. Such an upgrade will require the addition of an interworking function within the MSCs to support ATM-PSTN interworking, and provide support for the ATM protocol stack. However currently, the choice of transport layers remains up to the operator, and is not defined in the standards.

UMTS System Overview

29
Informa

Telecoms

CS DOMAIN PS DOMAIN

Any IP Network Commonly uses ATM

Mobility & Service Databases

PDH or SDH UTRAN

ATM Based

Goal is to combine PS & CS Transport Systems (Release 4 Architecture)

Fig. 15 Transport in the Core Network

Informa

Telecoms

30

UMTS Core Network

6. CHARGING
In the circuit-switched domain, charging continues to be based simply on the duration of the call, as in 2nd Generation Networks today, combined with information on the location of the mobile. However in the PS domain, charging can be not only time based, but also data volume based or QoS based. In the PS domain, a Charging Gateway function (CGF) collects charging records which are collected at the GSNs as follows:

Charging data recorded at the SGSN: usage of the radio interface (amount of data & QoS characterisation) length of time for which PDP addresses were used usage of PS domain resources location of the mobile station

at the GGSN: destination and source addresses usage of external data network (amount of data) length of time for which PDP addresses were used Another new requirement in UMTS is that such data needs to be available on a real-time basis, to allow real-time and online billing to the user.

UMTS System Overview

31
Informa

Telecoms

CS Domain: Time Location Number of Channels PS Domain: Time Location QoS Data volume

Fig. 16 Charging
Informa

Telecoms

32

UMTS Core Network

7. NETWORK MANAGEMENT
Network Management refers to a huge range of processes and functions which link together the various network elements, operations and systems within a UMTS network. This includes managing information flows which are related to communications between network elements, fault tracking & solving, security, billing & accounting, performance measurements, service provisioning & assurance operations, and various customer care operations. In implementing a network management structure, the key aims for the UMTS Operator are as follows: minimise the cost & complexity maximise the flexibility manage equipment supplied by different vendors ensure scaleability re-use existing standards, and ensure interoperability with other networks The ITU has developed a model known as TMN (Telecommunications Management Network Standard), which is used as the basis for UMTS network management whenever relevant and possible. TMN provides: an architecture of Operational Systems and Network elements with defined interfaces between them tools to refine the management architecture in a given network management area common functions which can be applied to various TMN interfaces A broad overview of the interactions needed within a network management scheme is shown in Fig. . The definition of standards for interfaces within an operators own operational system is not required. However interfaces between the UMTS operational system (OS) and the enterprise systems of that same UMTS organisation, and between the operational systems of different UMTS organisations were not defined in R 99. As a first priority, interfaces between the UMTS OS and the network elements are being defined. The latter are to be prepared on the basis of protocol-independent information models, since UMTS may involve convergence of elements from various technologies, and because information needs generally change on a much longer timescale than do protocols.

UMTS System Overview

33
Informa

Telecoms

Enterprise Systems

UMTS Operations System TMN

Operations System

Network Elements

UMTS Organisation A

UMTS Organisation B

Fig. 17 Network Management

Informa

Telecoms

34

UMTS Core Network

8. IN/CAMEL IN UMTS
8.1 Intelligent Networks
Intelligent Networks originally provided advanced features such as freephone, calling card and so on, by providing intelligence within databases which could translate these dialled numbers into standard routing numbers within networks. These early services were soon followed up by further advanced services based on this intelligence, incorporating interaction with the user to further customise services. Traditionally, switching equipment would need to be upgraded each time a new service was required. IN separates service intelligence and switching, such that to implement any defined Capability Set of services, upgrades to switches are required, but the addition of the actual services within this capability set do not require switch upgrades. This means that new services can be quicker and cheaper to install, and that service creation and switching is split into two markets, thereby increasing vendor competition. IN can provide such services only when there is an exchange of data between the switch and an application or database which has knowledge about number translation or other features. Most INs, including GSM Phase 2+ networks, use lower layer SS7 protocols to enable the Switches (known as Service Switching Points, or SSPs) to communicate with databases known as Service Control Points (or SCPs). The application or database must reside in the IN, and a standardised protocol layer known as INAP is used to enable interaction between the SSP and SCP. INAP lies above the internationally standard protocols which form the SS7 signalling system, incorporating MTP, SCCP and TCAP. The intelligent applications which control IN services are defined by the operator, and are not themselves standardised. This means that IN offers a route to operator differentiation, but equally that in many cases the same services cannot be offered outside the network of that operator.

UMTS System Overview

35
Informa

Telecoms

Pre-IN:

Switching & Service Control

IN: Intelligent Applications Service Creation Tools Service Control Point SS7 (INAP)

Service Switching Point Switching

SCP controls user interaction when required

Fig. 18 Intelligent Networks

Informa

Telecoms

36

UMTS Core Network

8.2 CAMEL
CAMEL (Customised Application for Mobile network Enhanced Logic) is a feature designed to provide support for services of operators which are not standardised services (e.g. operator-specific IN services), even when subscribers are roaming outside the home network. CAMEL is a network feature, not a supplementary service. In order for CAMEL to function, information exchange is required between the Home and Visited networks, and subscribers who have access to CAMEL services are marked within each network. The concept is basically that of IN, in that it is the MSCs (now termed SSPs within the CAMEL context) which communicate with the SCP. The big difference is that the MSC and SCP may well be in different networks (the SCP will be located in the subscribers home network for home network operator specific service support). Due to different networks being involved, the CAMEL standard is more tightly defined than IN capability set 1 (IN CS-1), although it is still seen as an extension of CS-1. It is specified within GSM Phase 2+, but is a core feature of the Virtual Home Environment (VHE) concept of UMTS. GPRS and Circuit-Switched connections are both supported by CAMEL.

UMTS System Overview

37
Informa

Telecoms

SCP

CAMEL Service Environment HOME UMTS NETWORK

Ca

me

l In

ter

ac

tio

ns

Serving MSC/GSN (SSP)

a Tr

ffic

Ch SERVING UMTS NETWORK

n an

el

Gateway MSC/GSN

User interactions are supervised by SCP where required

Fig. 19 CAMEL Within UMTS

Informa

Telecoms

38

UMTS Core Network

UMTS Systems Overview

39
Informa

Telecoms

ANNEX 1 OSI 7 LAYER MODEL

Informa

Telecoms

40

UMTS Core Network

ANNEX
A.1 A.1.1 OSI 7 LAYER MODEL Protocols & Stack: Basics
A network protocol simply defines a set of rules for communication between elements in a network, so governing things like format, timing, sequencing and so on, without which a network element cannot make sense of the bits. Because there are many processes and complexities involved, communication is broken down into a series of steps. Each step has its own rules of operation its own protocol. These steps are executed in a certain order. The hierarchical arrangement of these protocol steps is known as a stack. A stack as a whole therefore represents the set of rules for a communication, and is executed in the order from top to bottom in transmission, and bottom to top in reception, as shown in Fig. A1. Thus applications sit at the highest layers in protocol stacks. Data from an application will pass down through the stack in order to prepare the data for actual transmission over a physical network. At each stage, signalling information may be added to the original data, and/or its format may be changed, for example by being divided into packets. At the receiving end, data is taken off the physical network, and passed up through the layers, where reverse operations are performed. So packets may be reassembled, signalling information removed and so on, until the original data arrives once again at the highest layers, for example another application.

UMTS System Overview

41
Informa

Telecoms

Data In

Data Out

Applications

L4

L4

L3

L3

L2

L2

L1

L1

Transmission

Reception

Fig. A1 Protocol Stack Operation

Informa

Telecoms

42

UMTS Core Network

A.1.2

The OSI Model

The OSI model provides a reference model for protocol layering, and is often referred to in numbered layers in a protocol stack. However protocol stacks can consist of any number of layers, and multiple functionalities shown in the OSI reference model may be combined within a single protocol, or multiple protocols may be used to define sublayers within such a reference model. The OSI layers are as follows: Layer 7 Application Layer Layer 6 Presentation Layer Layer 5 Session Layer Layer 4 Transport Layer Layer 3 Network Layer Layer 2 Data Link Layer Layer 1 Physical Layer Type of communication, e.g. e-mail, file transfer etc. Encryption, data conversion and so on

Starts and stops sessions, and maintains order Ensures delivery of entire messages or files Routes data between and through different networks, based on network addresses Transmits packets from node to node within networks Electrical and mechanical interface to the actual network medium (cable, radio)

UMTS System Overview

43
Informa

Telecoms

Application Presentation Session Transport Network Data Link Physical

Fig. A2 The OSI Model

Informa

Telecoms

44