Procedures

UMTS System Overview

Informa

Telecoms

Procedures
1. UMTS PROCEDURES GENERAL 1.1 UMTS Defined Procedures 1.2 UE Identifiers (Held by the User Equipment and Core Network) 1.3 UTRAN Identifiers 1.4 UMTS Areas MODES AND STATES 2.1 Service States 2.2 UTRAN RRC States EXAMPLE RRC PROCEDURES 3.1 RRC Idle Mode 3.2 RRC Connection Establishment 3.3 Paging 3.4 Handover Types 3.5 The Soft Handover Procedure 3.6 Hard Handover 3.7 Compressed Mode UTRAN PROCEDURES 4.1 Example Power Control NON-ACCESS STRATUM PROCEDURES 5.1 The Mobility Management Concept 5.2 NAS Procedures Example Service Registration and Updates 5.3 NAS Procedures Example PDP Addresses & Context (Session Management) 5.4 PDP Context States 5.5 NAS Procedures Example Detach 5.6 Call Set-up, Routing & Addressing 5.7 CAMEL Interactions 1 3 5 7 9 11 13 15 17 19 21 23 25 27 29 31 33 35 37 39 41

2.

3.

4. 5.

UMTS System Overview

Informa

Telecoms

Procedures

1. UMTS PROCEDURES GENERAL

1.1 UMTS Defined Procedures
The procedures described in the first phase of UMTS specifications concentrate predominantly on the air interface and UTRAN. The Core Network is considered as an evolved GSM network, hence the procedures are those specified for the GSM Core Network, including GPRS. As network operators move to an All-IP network, the procedures in the core network will reflect this and will be based more on the IETF (Internet Engineering Task Force) specifications. As the core network is not the subject for UMTS standardisation, it follows that the way it interacts with UE will remain essentially that specified for GSM. Hence, when considering UMTS procedures, we can initially concentrate on the Air Interface and UTRAN. It is still useful to examine the Non-Access stratum and Core Network procedures in order to show the overall system operation, and how UTRAN and Air Interface procedures fit into the bigger picture.

UMTS System Overview

1
Informa

Telecoms

Procedures Based on Evolved GSM/GPRS Network Non Access Stratum Core Network Uu RRC RRC UTRAN Iu RANAP

Procedures Defined in UMTS (+ Lower Layers)

Fig. 1 UMTS Procedures - General

Informa

Telecoms

Procedures

1.2 UE Identifiers (Held by the User Equipment and Core Network)

The identifiers held by the User Equipment and Core Network are shown opposite: The IMSI (International Mobile Subscriber Identity) is used in the network to identify the Subscriber Identity Module (SIM), or UMTS SIM (USIM) within the mobile. It is held within the location registers in the network against information, including the services supported, current location (down to Location Area - LA or Routing Area RA only), and status for that mobile. It is unique to the mobile in question as it reflects the Mobile Country Code, Mobile Network Code, and Subscriber Identity within that network. The TMSI (Temporary Mobile Subscriber Identity) is used as a code word for the IMSI over the radio interface. It is shorter than the IMSI and unique only within the Visitor location Register (VLR) / Mobile Switching Centre (MSC) area. It is changed at regular intervals by the VLR in order to maintain security. The P-TMSI (Packet TMSI) is essentially similar to the TMSI, but is used in the Serving GPRS Support Node (SGSN) rather than in the VLR. Again, it is used as a code word and changed at regular intervals. The IMEI (International Mobile Equipment Identity) is used to identify the mobile equipment itself, rather than the subscriber (via the Subscriber Identity Module). Through its numbering structure it gives details of the manufacturer, model, type approval code, and importantly in terms of procedures, its capabilities can therefore be assessed. The TLLI (Temporary Logical Link Identity) is used between the SGSN and User Equipment to identify the established logical link for packet services. It is unique within the Routing Area.

UMTS System Overview

3
Informa

Telecoms

IMSI TMSI P - TMSI IMEI TLLI

Fig. 2 (Core Network) UE Identities

Informa

Telecoms

Procedures

1.3 UTRAN Identifiers

The procedures defined within the UTRAN are extensive. Since mobility is an essential requirement of any mobile network, it is important to be able to identify the elements and areas concerned. The figure shown opposite illustrates how the different elements within the UTRAN are identified. It shows how the network elements are identified, together with the cell areas and the Public Land Mobile Network itself. The UE may have Radio Network Temporary Identifiers (RNTI) assigned by the Serving, Drift and Controlling RNC. It allows a level of identification separate to that used by the Core Network (IMSI / TMSI), which allows some mobility procedures to be handled entirely within the UTRAN. The RNTIs are applicable to the Serving, Drift, or Controlling RNC. These are otherwise known as the Cell RNTI. The U-RNTI is also used for certain procedures, which is a long UTRAN UE identity used to ensure routing of uplink messages to the UEs Serving RNC, irrespective of the receiving RNC. The cell is identified (UTRAN Cell Id) using a hierarchical scheme which takes its controlling RNC Identity and adds a cell identity to it. Because the Global RNC Identity includes the Public Land Mobile Network Identifier (PLMN Id), it is a unique identifier, and so therefore is the UTRAN Cell Id. The PLMN Id is made up of a Mobile Country Code and Mobile Network Code. From the UTRAN, the core network domains use identifiers which include the PLMN Id and either the Location Area Code (LAC) for the Circuit Switched Domain, or the LAC and Routing Area Code (RAC) for the Packet Switched Domain.

UMTS System Overview

5
Informa

Telecoms

PLMN-Id=MCC+MNC CORE NETWORK

PLMN

SGSN CN PS Domain-Id =PLMN-Id+LAC +RAC RNC RNC

MSC

CN CS Domain-Id =PLMN-Id+LAC

RNC

RNC

Global RNC-Id= PLMN-Id+RNC-Id

Node B

UTRAN Cell Identity UC-ID=RNC-Id+C-Id

Serving RNC RNTI (s-RNTI) Drift RNC RNTI (d-RNTI) Controlling RNC RNTI (c-RNTI) Note: The URNTI is also used in certain procedures

Fig. 3 UTRAN Identifiers

Informa

Telecoms

Procedures

1.4 UMTS Areas

The cells in UMTS are organised into a series of areas for mobility purposes. The basic area is that of the cell itself. A number of cells (varying from a single cell to all the cells in the area served by a Core Network Node, i.e. MSC / VLR area), are grouped into location areas. A mobile is tracked on a location area (LA) basis by the Visitor Location register (VLR). Any incoming calls result in the mobile being paged over all the cells in the Location Area. This negates the need for the mobile to update its position constantly as it moves from cell to cell when it would otherwise be in idle mode (saving power and reducing interference and load on the radio network). Of course, a bigger LA requires more cells to carry the paging message. The Routing Area (RA) is a subset of the LA (with cells numbering between one and all the cells in the LA). The boundary of the RA must be coincident with, or confined within the LA boundary. The RA is used in the Packet Switched Core Network in a similar way that the LA is used in the Circuit Switched, but it gives a greater degree of accuracy and flexibility. In addition, the UTRAN Registration Area (URA) is specified for use within the UTRAN (the Core Network is not aware of this area). Once in the connected mode, the mobile is allowed to fall back into a less active state if using shared channels (only applicable for packet services). In this case, the UTRAN can track the mobile on a cell-by-cell or URA-by-URA basis. The mobile will signal the UTRAN if it changes cell or URA area respectively. So far as the Core Network is concerned, the mobile is still in connected mode. This means data is forwarded through to the UTRAN as if the mobile were connected, without any paging being initiated. The UTRAN would then initiate the paging to bring back the mobile into a more active connected mode. A cell can belong to several URAs at once. Only if the mobile detects that its current URA is not on the list within its current cell would a URA update procedure be executed. This reduces the signalling required to inform the Serving RNC of the mobiles current location. Other areas used in relevant procedures include RNC, MSC, VLR and SGSN.

UMTS System Overview

7
Informa

Telecoms

To Core Network Element(s) (Via RNCs)

UMSC MSC / SGSN Area

Cell, with base site Used by UTRAN only UTRAN Registration Area (PS Services)

Routing Area (PS Services) Known by Core Network Location Area (CS Services)

In addition, RNC, MSC, VLR and SGSN areas are all identifiable.

Fig. 4 UMTS Areas

Informa

Telecoms

Procedures

2. MODES AND STATES

2.1 Service States
The Service State is used to describe the activity of the mobile. In each case, the mobile can be in one of three modes, or states. They are used in both the core network and UE to model activity. State models are used in both the Packet and Circuit Switched domains. In each case, the mobile is considered Idle, Connected or Detached. An example of where the state would affect the service is that for an incoming call. A detached mobile may be configured to forward to voice mail, an idle mobile would be paged in order to establish a connection to receive the call, and a mobile already connected to the network could have forwarding (again possibly to voice mail), or call waiting active.

UMTS System Overview

9
Informa

Telecoms

CS Service State

MSC/ VLR

SGSN

PS Service State

UTRAN

No Knowledge of Service State in UTRAN

CS IDLE CS CONNECTED CS DETACHED CS Service State & PS Service State PS IDLE PS CONNECTED PS DETACHED

Fig. 5 Service States

Informa

Telecoms

10

Procedures

2.2 UTRAN RRC States

States are also used within the UTRAN. They are actually termed the Radio Resource Control (RRC) states. The mobile can be either in idle or connected mode. Idle is where the mobile is switched on and monitoring network system information on the Broadcast Channel. The core network holds location information (LA Id for the CS domain, and RA Id for the PS domain), but no information is held within the UTRAN. Connected, where the mobile has an established connection through the UTRAN to the core network. In the packet switched case, this can be in the form of an established logical link (denoted by the Temporary Logical Link Identity). The Core Network will be connected to the mobile for circuit switched services (in the Cell_DCH state) and location will not be a problem. For packet switched services, the mobile may be in the Cell_DCH state, or in the Cell_FACH state, from where it can fall back to one of two less active states, known as URA_PCH, and Cell_PCH. The designators give a good clue as to the purpose of each state. The first part (Cell or URA) indicates the accuracy of mobile tracking being performed in the UTRAN. The second part indicates the type of resources being used in that state. For DCH, dedicated channels are being used. For FACH, shared channels are being utilised by the mobile. But for PCH, the mobile is simply monitoring the paging channel and providing location information to the UTRAN when URA or cell boundaries are crossed (depending on whether in the URA_PCH or Cell_PCH state). As explained, therefore, the RRC states are closely related to the use of the different UMTS areas.

UMTS System Overview

11
Informa

Telecoms

Dedicated Resources

Shared Resources (Mobile Tracked by Cell, Paging Used)

CONNECTED Cell_DCH IDLE Cell_PCH

Cell_FACH

URA_PCH

Mobile known by Core Network identities (IMSI, TMSI, P-TMSI) No information held in UTRAN

Shared Resources

Shared Resources (Mobile Tracked by URA, Paging Used)

RRC Connection must be established in order for PS Connected or CS Connected Service states to exist

Fig. 6 UTRAN RRC States

Informa

Telecoms

12

Procedures

3. EXAMPLE RRC PROCEDURES

3.1 RRC Idle Mode
The tasks of the mobile in idle mode are shown opposite: The mobile continuously monitors the System Information Broadcasts on the Broadcast Channel, interpreting the information appropriately. This information contains parameters such as the serving cell id, UTRAN registration area identities and information on how to access the network (random access information codes and slots). The mobile selects the Public Land Mobile Network, and the required cell, based on measurements taken on the radio interface, and the cell selection / reselection algorithms. Once the cell is selected, the mobile leaves the idle state to register its location with the network. In the absence of any other activity, it then falls back to the idle mode, to monitor the paging channel (within its assigned paging block), updating its location as required (periodically, or as Location Area or Routing Area boundaries are transited).

UMTS System Overview

13
Informa

Telecoms

RRC

IDLE MODE: Monitor System Information Broadcast (Contains MM Information). PLMN Selection and Reselection Cell Selection Cell Reselection Location Registration and Updating Monitor Paging Channel/Block

Fig. 7 RRC Idle Mode

Informa

Telecoms

14

Procedures

3.2 RRC Connection Establishment

This is instigated from Idle mode. The RRC Connection Request is sent from the mobile to the controlling RNC (which becomes the Serving RNC as the connection is established) on a Common Control Channel, CCCH (which is a bi-directional logical channel used to transfer control information between the network and UEs). The CCCH is always mapped in the uplink to the Random Access Channel (a transport channel), which itself allows mobiles to access the network randomly as a requirement arises. This may be to make a call, transfer data, or update a Location or Routing Area. The Serving RNC now sets up the Radio Link over the Iub interface, including the data bearer setup within the ATM (Asynchronous Transfer Mode) transport network. Once achieved, the RRC Connection setup indication is sent to the UE over the CCCH (now using the Forward Access Channel, FACH (a transport channel) in the downlink. The mobile now moves into the connected state, sending a RRC Connection Setup Complete indication to the Serving RNC on the designated dedicated channel.

UMTS System Overview

15
Informa

Telecoms

RRC

UE RRC Idle

NODE B

SERVING RNC

(RACH CCCH) RRC Connection Req RRC RRC

Radio Link Setup (Including Iub Data Bearer Setup)

RRC RRC Connected RRC

(FACH CCC) RRC Connection Setup

RRC

(DCCH) RRC Connection Setup Complete

RRC

Fig. 8 RRC Connection Establishment (DCH)

Informa

Telecoms

16

Procedures

3.3 Paging
Paging can be initiated either by the Core Network, for mobiles in Idle Mode, or by the Serving RNC for mobiles in the URA_PCH or Cell_PCH mode. For Idle mobiles, the paging is initiated over the required Location Area, or Routing Area for incoming calls, or for session setup in the case of packet services. The core network node (MSC / VLR or SGSN) initiates the procedure over the Iu interface using RANAP (Radio Access Network Application Part) signalling in this case. If the mobile is in the URA_PCH or Cell_PCH state, the Serving RNC responds to incoming (downlink) packet data activity by paging the mobile over the appropriate URA or Cell respectively. This is done to bring the mobile into the Cell_FACH state ready for data transfer. In core network initiated, or RNC initiated cases, the Paging message is broadcast by RRC on the PCCH (Paging Control Channel). In addition, the RNC can indicate a change of system information by using a paging message with no paging record, but with the new information carried within it. These messages would be aimed at all UEs in a cell.

UMTS System Overview

17
Informa

Telecoms

Core Network

RANAP
Pag ing

Paging

RNC RRC
RC

RNC RRC Paging (-RRC) (PCCH)

RRC
ng gi

Paging

(-R

)
(PCCH

CC

H)

(-RRC)

Pa

(P

Core Network knows LA or RA of UE Applicable to RRC Idle Mode (No RRC Connection), or RRC Connected Mode Cell_PCH and URA_PCH states For RRC Connected Mode (Cell_DCH and Cell_FACH), DCCH would be used with existing RRC connection no paging required

Fig. 9 Paging (Eg RRC Idle Mode)

Informa

Telecoms

18

Procedures

3.4 Handover Types

There are three different handover types in UMTS: The Softer handover is where the mobile receives the signal via two radio interfaces at the same time, both interfaces being provided by the same Node B. The information from the different sectors, or cells, is handled by the same Node B, hence combining is done within the Rake receiver. The Soft handover is where the mobile receives the signal via two radio interfaces at the same time, but the interfaces are provided by different Node Bs. The information from the different cells is channelled from both Node Bs to the serving RNC (possibly via a Drift RNC) handled by different Node Bs, hence combining is done now in the RNC. Hard handover is the same sort of handover found in GSM, where the new radio resources are established, and the mobile makes contact via the new resources before the old resources are released. Communication only ever occurs via a single interface. This can be used for handover between WCDMA frequencies, or between different systems.

UMTS System Overview

19
Informa

Telecoms

Node B

Softer Handover

Node B RNC Node B Carrier 1 Node B

Soft Handover

Hard Handover

Carrier 2

UTRAN

Node B

MSC BTS

Hard Handover

GSM BSS

Fig. 10 Handover Types

Informa

Telecoms

20

Procedures

3.5 The Soft Handover Procedure

The soft handover procedure relies on an active set of cells being maintained. It is applicable only to mobiles in the RRC Connected Cell_DCH state. This active set simply includes the cells, which are currently providing a radio interface for the mobile in question. Addition and deletion to and from the active set is carefully controlled, based on a soft handover algorithm. The parameters for this algorithm are configurable, and allow cells to be added and deleted by the Serving RNC based on measurement reports continually being sent in by the mobile. Hysteresis and time above or below specified values minimise the number of active set updates required, and hence signalling is minimised. The mobile itself monitors system information messages sent from the network to identify candidate (neighbouring) cells. Once known, the active and candidate cell pilot channels are monitored and appropriate measurement reports sent in to the network, allowing the energy per chip and interference to be assessed. The RNC then uses this information in the soft handover algorithm. The active set update message contains the information required for a mobile to access the network via the required cells (codes etc.). Typically, one, two or three cells will be in the active set at any one time. A maximum number can be set.

UMTS System Overview

21
Informa

Telecoms

RRC System Information Measurement Reports Serving RNC

UE

CELL_DCH State

(DCCH) Active Set Update RRC RRC

(DCCH) Active Set Update Complete RRC RRC

UE
Based on Measurement Reports, Serving RNC assesses the Pilot channels of active and candidate cells. Cells can be added, replaced or removed from the active set based on: - Energy per chip and interference - Max number of cells in active set - Hysteresis and required time at measured value

Fig. 11 Soft Handover Procedure

Informa

Telecoms

22

Procedures

3.6 Hard Handover

For the hard handover, the mobile monitors the appropriate radio resources, sending the required measurement reports into the network. The network sends system information messages to the mobile, which are used to identify the resources to be monitored. The Serving RNC assesses the measurement results and may decide to hand over from one WCDMA frequency to another, or from UTRAN to GSM BSS. The first case may be achieved within the UTRAN, but the inter-system handover necessitates the involvement of the core network, as shown.

UMTS System Overview

23
Informa

Telecoms

RRC, RANAP, BSSAP

Core Network Connection

MSC RANAP
Re qu u q es ements (with e g d t le R GS w o M n k

d ire

Relocation

(Gsm) BSSAP

Ac

) fo In

UTRAN RNC
1

(GSM) BSS

*H /O Co ce G SM H/
6

O SM

Ac G
2

RRC

UE

Fig. 12 Hard Handover (Example - UMTS to GSM)

Informa

Telecoms

ss d to or ts

M ea su Sy st em In

m m an tR ep n rm io at en

m re fo

* RRC Physical Channel Reconfiguration Message

24

Procedures

3.7 Compressed Mode

For a mobile to monitor resources, on anything other than the WCDMA frequency it is currently using requires a break in reception. This is required because the mobile cannot operate on two frequencies, or therefore on two systems, at once, and WCDMA operation is continuous (unlike Time Division Multiple Access (TDMA) systems, such as GSM, which effectively have gaps between time slots which are used to monitor other cell transmissions). Compressed mode is used in WCDMA to give the break required. It is a technique used to compress (rather than lose) data in order to provide a sufficient gap. In normal operation, each frame is 10ms long, the time taken to transmit the data can be compressed by: Reducing the data rate from the upper layers (although in this case, less data is actually transmitted) Lowering the spreading factor so that fewer chips are used to represent the same amount of data (same amount of data transmitted, but with potentially poorer quality) Reducing the symbol rate by puncturing at the physical layer (taking out unnecessary data, and relying more on forward error correction to maintain quality) Each frame is made up of a possible 15 slots, and two adjacent frames would therefore have 30 slots available. Out of the 30 slots, 3, 7, 10, 14 slot gaps can be configured.

UMTS System Overview

25
Informa

Telecoms

Compressed Mode - Allows time for other UMTS frequencies to be measured.

Transmission Gap Length Power

3,7 ,10 or 14 slots

10ms

10ms

10ms

10ms

Achieved by: 1. Lower data rates from upper layers. 2. Increasing data rate by changing spreading factor. 3. Reducing symbol rate by puncturing at physical layer.

Fig. 13 Compressed Mode (Slotted Mode)

Informa

Telecoms

26

Procedures

4. UTRAN PROCEDURES
4.1 Example Power Control
Power control is required to minimise the interference in the system. Fast closed loop power control is performed 1500 times a second and is designed to adjust the power to meet a defined signal to interference (SIR) ratio. The SIR is set to give the required quality whilst minimising the contribution to overall system interference. Outer loop power control is the process of changing the SIR. Outer loop power control is usually implemented in the Radio Network Controller (RNC), which performs checks on some form of frame quality indicator which is tagged along with the user data to indicate when error rates become unacceptable. The RNC informs the Node B of changes to SIR using Node B Application Part (NBAP) messages. If required, more than one Node B, each with cells in the active set for a given mobile will be sent the required SIR, as shown. This can be extended via the Drift RNC where cells belonging to different RNCs are involved. Open loop power control is the third type, which is applied by the mobile only prior to initiating transmission on the RACH or CPCH. It is not very accurate, since accurate power assessments are difficult to achieve in the mobile. Also, information on power gained in the downlink is then applied to transmissions in the uplink, which is at a large duplex spacing.

UMTS System Overview

27
Informa

Telecoms

UTRAN Procedure

UE

Node B Drift RNS

Node B Serving RNS 1 NBAP

Drift RNC

Serving RNC

NBAP

2 RNSAP RNSAP

3 NBAP NBAP

1 2 3

DL Power Control Request (Iub) DL Power Control Request (Iur) DL Power Control Request (Iub)

Fig. 14 Downlink Power Control

Informa

Telecoms

28

Procedures

5. NON-ACCESS STRATUM PROCEDURES

5.1 The Mobility Management Concept
The mobility management concept is illustrated opposite. The system needs to know where the mobile is in all states other than detached. For idle mode, the core network tracks the mobile, whilst in dedicated mode, the UTRAN tracks the mobile. Essentially two levels of mobility management exist. In idle mode, the mobile monitors the selected and adjacent cells, reselecting where necessary and listening to the system information in each cell. The network does not need to know precisely where the mobile is, but for the circuit switched domain, needs to know the Location Area (LA) in order that it can page the mobile for incoming calls. For the packet switched domain, the network tracks down the mobile to Routing Area (RA), which may be coincident with the LA, or a subset of it. The mobile will leave the idle mode and enter the connected mode in order to perform the LA or RA updates. In connected mode, the handover is used with dedicated channels for both circuit switched and packet switched connections. This is sufficient for the UTRAN to track the mobile. In cases where shared channels are being used (Cell_FACH, Cell_PCH or URA_PCH), the mobile keeps the UTRAN informed of any changes to its cell or UTRAN Registration Area (URA) respectively. No information is exchanged with the core network. A cell can belong to several URAs in order to stop the ping-pong effect of mobiles near to URA boundaries. Only if the new cell does not belong to the existing URA will an update be made. Serving Radio Network Sub-system (SRNS) relocation decisions are made in cases of URA or cell updates into new RNC areas. The existing SRNC makes the relocation decision, and not the target RNC. In this case, the core network would be involved in relocating the Iu interface. Although closely related to inter RNC updates, and occurring at the time of the update, this is considered a separate procedure. The SRNS Relocation procedure is applicable only to the connected mode.

UMTS System Overview

29
Informa

Telecoms

Circuit Switched

LA Update (MM)

UTRAN

MSC

(Instigated from RRC Idle State)

HANDOVER (RRC)

UTRAN

MSC

(RRC Connected State)

Packet Switched

RA Update (GMM)

UTRAN

SGSN

(Instigated from RRC Idle State) URA Updating Common Cell Updating Channels Handover Dedicated

)
SGSN

( Channels )

(RRC)

UTRAN

(RRC Connected State)

Fig. 15 The Mobility Management (MM) Concept

Informa

Telecoms

30

Procedures

5.2 NAS Procedures Example Service Registration and Updates

Registration is essentially a location update which occurs when a mobile is initially switched on. The other two scenarios when a location update is performed are on a periodic basis (the period to be used is broadcast in the system information on the broadcast channel), and on transiting a Location Area (LA) or Routing Area (RA) boundary. Location Updates are initiated from idle mode and are performed in order to keep the core network informed of the mobiles location for paging purposes. They are used either to update the LA within the VLR, or in the case of an update into a new MSC / VLR area, to inform the new VLR of its presence. This allows the new VLR to communicate with the mobiles Home Location Register (HLR) in order to retrieve the mobiles service profile and other required data. It also informs the HLR that the mobile is now located within the VLR area. This is used to route any incoming calls from the home network. The inter VLR handover case is shown opposite. Routing Area Updates are very similar to Location Updates, but are relevant to the Serving GPRS Support Node. The RA is used as the update area. The SGSN either changes the RA for that mobile internally, or in cases of inter SGSN updates, the SGSN will contact the HLR to retrieve the subscriber data, and the Gateway GPRS Support Node (GGSN) to update any established contexts. Combined Updates can be performed when either a UMSC (UMTS Mobile Switching Centre) is present, or an additional interface exists between the MSC / VLR and SGSN. The UMSC provides combined circuit switched and packet switched functionality. The updates can be within the UMSC or VLR and SGSN areas, or can be across areas. In the case of a combined update into a new UMSC area, information is retrieved from the previous SGSN (or UMSC if applicable) whilst updating the context information. The UMSC then updates context information in the GGSN whilst contacting the HLR. The HLR cancels the location in the previous SGSN and VLR (or in the previous UMSC where applicable) before inserting the subscriber data into the new UMSC. As in all location updates, the mobile is informed of the successful completion of the procedure before it falls back into the idle mode.

UMTS System Overview

31
Informa

Telecoms

ExampleLocation Update (other scenarios exist)

HLR

LO CA SU TIO BS N CR IBE R DA TA

EL NC CA

UP DA TE

N TIO CA LO

IN SE RT

Re

(O

LD

LA

NEW 3G MSC/VLR

2
REQ ID & SECURITY INFO

OLD 3G MSC/VLR

I)

da

TY

1
LA

7
CU

te

Up

SE

RRC Connection is established before 1 For Location update within same MSC/VLR area, delete 2 , 4 , 5 and 6 . For RA update, the same basic procedure is followerd, replacing MSC/VLR with SGSN and changing Messages/Parameters.

Fig. 16 Registration/Location Update (New MSC/VLR Area)

Informa

Telecoms

LA

Up

da

te

Ac

ce

RI

pt

32

Procedures

5.3 NAS Procedures Example PDP Addresses & Context (Session Management)
In order to exchange data packets with external packet Data Networks (PDNs), following a successful attach to the UMTS network, a mobile station must apply for one or more addresses used in the PDN. These will be IP addresses if the external network is IP-based. These addresses are known as PDP (Packet Data Protocol) addresses. PDP addresses may be static, in which case they are permanently assigned by the home network to the user. Or they may be dynamic, assigned as needed by the Home Operator or the Visited Operator. In the case of dynamic PDP addresses, the GGSN is responsible for the allocation and activation/deactivation of these addresses. The PDP Context describes the characteristics of the session and contains: PDP type (e.g. IPv4) PDP address assigned to the mobile station requested QoS address of the GGSN which serves as the access point for the external PDN This context is stored in the mobile station, the SGSN and the GGSN, and acts to make the mobile visible to the external PDN, and thus able to send and receive packets.

UMTS System Overview

33
Informa

Telecoms

PDP Context:
PDP Type PDP Address of UE Quality of Service GGSN Address

Fig. 17 THE PDP Context

Informa

Telecoms

34

Procedures

5.4 PDP Context States

There are two PDP contexts/states, with the PDP Context activation procedure lying between them. PDP Inactive means that the data service for a certain PDP address of a subscriber is not activated. Thus the PDP context contains none of the routing or mapping information which would be required to process packet data units (PDUs) associated with that address. PDP Active means that the PDP Context Activation procedure has taken place. Now mapping and routing information for transferring the PDUs between the mobile and the external network or application is present in the MS, SGSN and GGSN. The PDP Active state is possible only in a MM state of Idle or Connected, i.e. where the core network is aware of the existence and location of the mobile. Moving to MM Detached will move the PDP context to inactive. More than one PDP context can be open for a subscriber, each associated with different services. Compare this with the MM context, where a subscriber can have only one state at any one time. In order to activate a PDP context, the Mobile Station must request to the SGSN. After security functions are performed, the SGSN will then request that a PDP context be created within the GGSN. Once the GGSN responds, this PDP context acceptance is signalled to the mobile. If the request for activation comes from the network side (i.e. the GGSN has received a PDU from another network), the GGSN may need to first request routing information for the appropriate SGSN. It will do this by communicating with the HLR. It then sends a notification to the SGSN, which can act to create the PDP context between the GGSN and the mobile.

UMTS System Overview

35
Informa

Telecoms

PDP Inactive

1. MS Request to SGSN MM Detach or PDP Deactivation 2.Security 3.SGSN Request to GGSN 4.PDP Context in GGSN 5.Acceptance SGSN MS

PDP Active (MM Idle/ Connected)

Fig. 18 PDP Context States

Informa

Telecoms

36

Procedures

5.5 NAS Procedures Example Detach

The detach is used simply to take the service state (Mobility Management Context) into the detached state, where the core network will no longer hold valid location information on the mobile. The message is sent from the mobile and includes the detach type (packet switched, circuit switched, or both), and a switch off indicator. A Detach Accept message is sent to the mobile, but only if the detach reason is NOT due to switch off. For packet switched detach, PDP Contexts in the GGSN are deactivated.

UMTS System Overview

37
Informa

Telecoms

Example: UE Initiated Combined Detach

GGSN
2

Co nt ex

tD

UMSC

ta

ch

Re

De

1 2 3

Includes Detach Type (PS, CS or both) and Switch off indicator. If PS detach, PDP contexts in GGSN are deactivated (Session Management Layer). Only sent if detach is not due to switch off.

De

ta

ch

Ac

ce

pt

Fig. 19 Detach
Informa

Telecoms

PD

ele

Core Network

te d

38

Procedures

5.6 Call Set-up, Routing & Addressing

Using the example of an incoming call/data packet, it is possible to highlight the basic differences between providing a connection in the CS and PS domains. 1. CS Domain establishing a circuit In a fixed network, a terminal is semi-permanently wired to a central point, and a circuit-switched route can be directly established. However in mobile networks a user can roam. The number actually dialed for a subscriber in GSM Phase 2+ networks is called the Mobile Subscriber ISDN Number (MSISDN), and includes a country code and a code which identifies the subscribers home operator. An incoming call is directed to the Gateway MSC. The MSISDN number will enable this switch to identify and interrogate the subscribers HLR. The HLR stores information regarding the subscribers current MSC/VLR, including an address within the SS7 signalling system which is used to communicate with this entity. The HLR will obtain from this VLR a temporary Mobile Station Roaming Number, an internal network routing number which remains unseen by the user. This is passed back to the GMSC, and allows routing of the incoming call through to the appropriate Serving MSC, and the establishment of a circuit which then remains open for the duration of the call. 2. PS Domain Addressing & Routing In the PS Domain, no permanent circuit is set up. Instead packets of data arriving from an external packet data network (PDN) are simply routed through to the mobile equipment as they arrive. Taking the example of communication with an external IP network, hosts and routers in the PS domain require unique IP addresses. Indeed a router may have two or more addresses, since IP addresses do not specify computers but connections between computers and networks. Thus since a router connects at least two networks together, it will have an address relating to each connection. In the UMTS context, this means that each SGSN and GGSN will have at least one IP address. This must be an IPv4 address, and may optionally also be an IPv6 address. These addresses will form part of a private address space (an Intranet), innaccessible directly from the public Internet. In addition to routing between the nodes within the core network, the core network itself needs to facilitate and manage the establishment of an IP address for the mobile equipment, after which incoming data packets can be tunnelled directly to this address. To do this the GGSN may have to initially request the IP address of the current SGSN from the HLR. After this, further packets which form part of this session can be communicated directly to the SGSN, as can any further signalling processes. These processes comprise Session Management.

UMTS System Overview

39
Informa

Telecoms

CS Domain: establishing a circuit 6 MSRN GMSC Return Return MSRN MSRN 4 5 1 MSISDN Circuit Retrieving Routing Establishment Information Establish Routing Information
40

Serving MSC/ VLR

3 Request MSRN

2 Request Routing Information

HLR Signalling Traffic Signalling PS Domain: establishing a route

SGSN 2.Return IPv4

GGSN

1.Request SGSN HLR

Fig. 20 Routing and Addressing

Informa

Telecoms

Route

IPv4

IPv4

IPv4

Procedures

5.7 CAMEL Interactions

Customised Applications for Mobile Networks Enhanced Logic (CAMEL), is a network feature which allows operator specific services to be provided for mobiles even when roaming in other operators networks. CAMEL is based on the Intelligent Network concept, which provides a toolkit of functionality rather than specifying a set of standard complete procedures. A CAMEL modified MSC, SGSN, or UMSC is able to detect preconfigured triggers within control information. The triggers are included in the subscriber information sent to the serving VLR, SGSN or UMSC during the Location Update procedure. They can be as simple as triggering on any call or any series of address digits. On encountering a trigger, the core network node will then send a message containing all relevant information to the mobile subscribers home network CAMEL Service Environment (CSE). This contains the Service Control Point which interacts with the core network node in the visited network to provide user interactions (announcements and voice responses), billing information, number translation, security functions etc. CAMEL is applicable to procedures including packet switched or circuit switched procedures, location and routing update procedures, handovers, and short message transfer. It forms an integral part of the Virtual Home Environment (VHE) concept in UMTS.

UMTS System Overview

41
Informa

Telecoms

 Note: CAMEL provides Home Network services in any (CAMEL compatible) network

Subscriber's Home Network CAMEL Service Environment Service Control Point

3 2 MSC or SGSN

Serving Network 1 UE

1 UE & CN Interaction 2 Specified event(s) and data trigger CAMEL Interaction.

May be CS or PS procedures, Location Update, Handover, Short Message Transfer etc. 3 CAMEL Interactions (Control of service by SCP in home network). May involve user interactions, number or address translation, billing information etc. 4 On completion of interaction, data transfer may be modified, billed or continue as required (if applicable)

Fig. 21 CAMEL Interactions

Informa

Telecoms

42