Radio Access Network Signalling

PS Call Setup

Nokia Siemens Networks

RN33022EN10GLA00 PS Call Setup

Content

Attach and Detach

PDP Context Activation
Iu-CS vs Iu-PS
Encryption

Nokia Siemens Networks

RN33022EN10GLA00 PS Call Setup

PMM and SM State

PMM State

SM State

Detached
Inactive
OFF

ON

Detach

Attach

PDP
Context
Activation

PDP
Context
Deactivation

Connect
Active
Iu Release
Command
Message

Idle

Nokia Siemens Networks

RN33022EN10GLA00 PS Call Setup

An MS shall perform a GPRS Attach to the SGSN in order to obtain access to the GPRS
services. If the MS is connected via a UMTS radio access network, it shall perform a
UMTS GPRS Attach procedure.In the attach procedure, the MS shall provide its identity
and an indication of which type of attach that is to be executed. The identity provided to
the network shall be the MS's Packet TMSI (P-TMSI) or IMSI. P-TMSI and the RAI
associated with the P-TMSI shall be provided if the MS has a valid P-TMSI. If the MS
does not have a valid P-TMSI, the MS shall provide its IMSI.
A GPRS-attached MS makes an IMSI attach via the SGSN with the combined RA / LA
update procedure if the network operates in mode I (Gs interface is present.). If the
network operates in mode II ( Gs interface is not present.), or if the MS is not GPRSattached, the MS makes a normal IMSI attach. An IMSI-attached MS engaged in a CS
connection shall use the (non-combined) GPRS Attach procedure when it performs a
GPRS attach.
After having executed the GPRS attach, the MS is in the PMM-CONNECTED state and
MM contexts are established in the MS and the SGSN. The MS may then activate PDP
contexts as described in subclause "Activation Procedures".
An IMSI-attached MS that cannot operate in CS/PS mode of operation shall follow the
normal IMSI detach procedure before it makes a GPRS attach. A GPRS-attached MS that
cannot operate in CS/PS mode of operation shall perform a GPRS detach before it makes
an IMSI attach.

GPRS Attach

UE
ATTACH REQUEST ( )
(Identification Procedure)

3G-SGSN

Authentication and Ciphering Procedure

ATTACH ACCEPT ( )
e.g. new TMSI
or P-TMSI

ATTACH COMPLETE ( )

Nokia Siemens Networks

RN33022EN10GLA00 PS Call Setup

Registration and Routing Area Update

In the CS mode of operation, we use the Location Updating Request both for the initial
registration and for location updates. This is different in the PS mode of operation:
GPRS Attach
A GPRS Attach is used to establish a GMM context between the UE and the 3G-SGSN. It
can be used for a
- normal GPRS attach, which is an IMSI attach for ps services, or a
- combined GPRS attach for a combined cs and ps IMSI attach. This is only possible with
NMO I.

UE Initiated PDP Context Activation

UE

3GSGSN
GGSN
ACTIVATE PDP CONTEXT REQUEST ( )
CREATE PDP CONTEXT REQUEST
CREATE PDP CONTEXT RESPONSE
Radio Bearer Setup
UPDATE PDP CONTEXT REQUEST
UPDATE PDP CONTEXT RESPONSE
ACTIVATE PDP CONTEXT ACCEPT ( )

Nokia Siemens Networks

RN33022EN10GLA00 PS Call Setup

GPRS Session Management

Session management is only possible after the establishment of the GMM context
between the UE and the network. The session management is then responsible to handle
PDP contexts. This incorporates PDP context activation, PDP context modification, and
PDP context deactivation
procedures. In the TS24.008 you can find all session management messages, which are
transmitted over the radio interface. The peer entities are the UE and the SGSN.
The UE send the session management message ACTIVATE PDP CONTEXT REQUEST
to the SGSN to activate a PDP context. In parallel, it starts the timer T3380 (30 =
seconds). The IE contained in this message are sketched in the figure on the right hand
side. The SGSN is analysing the message. The APN is analysed to determine a suitable
GGSN. The QoS requested by the UE may be modified. The SGSN may even reject the
subscribers request. If the SGSN accepts the UEs request, it has to establish a GTP
tunnel to the selected GGSN by sending the message CREATE PDP CONTEXT
REQUEST. The GGSN analysis the message in order to establish a connection to the
external PDN. It returns the message CREATE PDP CONTEXT RESPONSE to the
SGSN. This message holds among others the Negotiated QoS and the GPRS Charging
Identifier. Based on the Negotiated QoS, the SGSN determines the a radio priority level
for the UE. The SGSN returns the message ACTIVATE PDP CONTEXT ACCEPT. Upon
its reception, the UE stops the timer T3380. If the QoS requested derivates from the
Negotiated QoS, the UE either accepts it, or initiates the PDP context deactivation
procedure. Upon expiry of T3380, the UE transmits the ACTIVATE PDP CONTEXT
REQUEST message again. Retransmission is possible up to four times.

PDP Context Activation

UE

3GSGSN

ACTIVATE PDP CONTEXT REQUEST ( )

1010: GPRS session management messages

Protocol discriminator
Transaction indicator
Activate PDP context
request message ID

01000001: Activate PDP context request

Requested NSAPI
Requested LLC SAPI
Requested QoS
Requested PDP address
Access Point Name

OP

Protocol configuration
options

OP

Nokia Siemens Networks

RN33022EN10GLA00 PS Call Setup

Delay class
Reliability class
Precedence class
Mean and peak throughput
class
Maximum UL/DL bit rate
Transfer delay
Guaranteed UL/DL bit rate
Residual BER
Delivery order
etc.

The RAB establishment is initiated by the SGSN at the reception of the CREATE PDP CONTEXT RESPONSE. The QoS
attributes may be downgraded during the RAB establishment process. If so, the GGSN may be informed about it by the sending
the UPDATE PDP CONTEXT REQUEST message to the GGSN.
Please note, that the radio priority level and the LLC parameters are not used in UMTS. They are only transmitted to support
cell re-selection between UMTS and GSM.

In the PDP Context Activation Request message, we again find a list of parameters, which need
further explanation. A basic idea here is, that the mobile has the chance to request certain features,
values or qualities, which might be conceded or downgraded or even rejected by the PDP Context
Activation Response.
The PDP Context Activation Request contains:
Network Serv. Access Point Id.
The purpose of the Network Service Access Point Identifier information element is to identify the
service access point that is used for the GPRS data transfer at layer 3. An NSAPI is assigned when
the MS initiates the PDP Context Activation function.
LLC Service Access point Id
The purpose of the LLC Service Access Point Identifier information element is to identify the
service access point that is used for the GPRS data transfer at LLC layer.
SAPI identifies a point at which LLC services are provided by an Logical Link Entity (LLE) to a
layer-3 entity. Consequently, SAPI identifies an LLE that should process an LLC frame and also a
layer-3 entity that is to receive information carried by the LLC frame.
SAPI is a four bit field. Possible values are:
SAPI

Related Service

GPRS Mobility Management

User data 1

User data 2

SMS

User data 3

11

User data 4

Other values are reserved

PDP Context Activation

UE

ACTIVATE PDP CONTEXT ACCEPT ( )

3GSGSN

1010: GPRS session management messages

Protocol discriminator
Transaction indicator
Activate PDP context
request message ID

01000010: Activate PDP context accept

Negotiated LLC SAPI

Not required in UMTS, but transmitted to
support UMTS GPRS cell reselection

Negotiated QoS
Radio priority
Spare half octet
PDP address
Protocol configuration
options
Packet Flow Identifier
9

Nokia Siemens Networks

OP
OP
OP
RN33022EN10GLA00 PS Call Setup

In UMTS, both the network and the MS shall store the LLC SAPI and the radio priority in
the PDP context. If a UMTS to GSM system change is performed, the new SGSN shall
initiate establishment of the logical link using the negotiated QoS profile, the negotiated
LLC SAPI, and selected radio priority level stored in the PDP context as in a GSM to GSM
Routing Area Update.
An MS, which is capable of operating in both GSM and UMTS, shall use a valid LLC
SAPI, while an MS which is capable of operating only in UMTS shall indicate the LLC
SAPI value as "LLC SAPI not assigned" in order to avoid unnecessary value range
checking and any other possible confusion in the network. When the MS uses a valid LLC
SAPI, the network shall return a valid LLC SAPI. However, in this version of the protocol,
if the network does not support handover to GSM, it may return the "LLC SAPI not
assigned" value.
NOTE:
The radio priority level and the LLC SAPI parameters, though not used in
UMTS, shall be included in the messages, in order to support handover between UMTS
and GSM networks.
Quality of Service
The purpose of the quality of service information element is to specify the QoS
parameters for a PDP context. . The trace shows subfields of which possible values are
as follows:
The quality of service is a type 4 information element with a length of 13 octets. The QoS
requested by the MS shall be encoded both in the QoS attributes specified in octets 3-5
and in the QoS attributes specified in octets 6-13.
A QoS IE received without octets 6-13 shall be accepted by a receiving entity.
NOTE:
This behavior is required for interworking with entities supporting an earlier
version of the protocol.

Overview of Setting Up Call

Mobile Terminated Call (MTC)

Mobile Originated Call

Paging

RRC
Connection

Service
Request

Radio
Access
Bearer

L3 Call Setup

10

Nokia Siemens Networks

RN33022EN10GLA00 PS Call Setup

In case of a mobile terminated call (MTC), the process starts with paging. Paging is the
procedure by which a mobile network attempts to locate the UE within its location area
before any other network-initiated procedure can take place.
If the UE originates the call, paging is not needed and the UE directly requests RRC
connection setup.
After having established an RRC connection, the UE starts setting up a signalling
connection to the CN. For that, a new radio link is needed.
Finally, the radio access bearer setup procedure builds a radio access bearer service
between the UE and the core network (CN), and the call is established.

Iu-CS VS Iu-PS Call Setup

RRC

Service
Req

Security Mode Command

11

Nokia Siemens Networks

RN33022EN10GLA00 PS Call Setup

Non-real-time services (NRT) only involve packet switched data calls. For nonreal time services, the radio access bearer is created without immediately
reserving radio resources. The resources are allocated on demand by using the
signalling link between the UE and the RNC. The following figures illustrate the
process of establishing a packet switched call.

RAB Establishment Iu-CS VS Iu-PS

Iu-CS

Iu-PS

RAB

PDP Context Activation

For non-real time services,

the radio access bearer is created without immediately reserving radio resources

12

Nokia Siemens Networks

RN33022EN10GLA00 PS Call Setup

RAB Assignment Iu-CS VS Iu-PS

Iu-CS RAB-ASSIGNMENT REQUEST

RANAP-PDU

initiatingMessage

initiatingMessage

- procedureCode: 0
- criticality: reject

- procedureCode: 0
- criticality: reject

initiatingMessage

initiatingMessage

RAB-AssignmentRequest

RAB-AssignmentRequest

protocolIEs

protocolIEs

- id: 54

- id: 54

- criticality: ignore

- criticality: ignore

RAB-SetupOrModifyList

RAB-SetupOrModifyList

- id: 53

- id: 53

- firstCriticality: reject

- firstCriticality: reject

firstValue

firstValue

- rAB-ID: '00000001'B

- rAB-ID: '00000101'B

rAB-Parameters

rAB-Parameters

- trafficClass: conversational

- trafficClass: background

- rAB-AsymmetryIndicator: symmetric-bidirectional

- rAB-AsymmetryIndicator: symmetric-bidirectional

maxBitrate

maxBitrate

Bit rate

- MaxBitrate: 12200
guaranteedBitRate

- MaxBitrate: 128000
- deliveryOrder: delivery-order-not-requested

- GuaranteedBitrate: 4750

- maxSDU-Size: 12016

- deliveryOrder: delivery-order-requested

sDU-Parameters

- maxSDU-Size: 244

residualBitErrorRatio

sDU-Parameters

- mantissa: 1

sDU-ErrorRatio

- exponent: 5

- mantissa: 7
- exponent: 3
13

Iu-PS RAB-ASSIGNMENT REQUEST

RANAP-PDU

Nokia Siemens Networks

RN33022EN10GLA00 PS Call Setup

RAB Assignment Iu-CS VS Iu-PS

Iu-CS

residualBitErrorRatio

Iu-PS

residualBitErrorRatio

- mantissa: 1

- exponent: 5

- deliveryOfErroneousSDU: yes

- deliveryOfErroneousSDU: no-error-detection-consideration

sDU-FormatInformationParameters
- subflowSDU-Size: 81
:

residualBitErrorRatio

- priorityLevel: 2
- pre-emptionCapability: shall-not-trigger-pre-emption
- pre-emptionVulnerability: pre-emptable
- queuingAllowed: queueing-not-allowed

- exponent: 3

- relocationRequirement: none

- deliveryOfErroneousSDU: no-error-detection-consideration
- subflowSDU-Size: 103
:

residualBitErrorRatio
- mantissa: 5
- exponent: 3
- deliveryOfErroneousSDU: no-error-detection-consideration
sDU-FormatInformationParameters
- subflowSDU-Size: 60
:

- transferDelay: 80
- sourceStatisticsDescriptor: speech

Nokia Siemens Networks

allocationOrRetentionPriority

- mantissa: 1

sDU-FormatInformationParameters

14

- mantissa: 1

- exponent: 6

RN33022EN10GLA00 PS Call Setup

RAB Assignment Iu-CS VS Iu-PS

Iu-CS

Iu-PS
userPlaneInformation
userPlaneInformation

- userPlaneMode: transparent-mode

- userPlaneMode: support-mode-for-predefined-SDU-sizes
- uP-ModeVersions: '0000000000000001'B
transportLayerInformation

- transportLayerAddress: '00001010001110100001010100000101'B

- transportLayerAddress:
'01000101000000000000000000000110011000011
000000110010000000100010001111100000000000
00000000000000000000000000000000000000000
00000000000000000000000000000000000 0'B
- extension range: 0
- length (in bits): 10011111
- padding: 000000
- contents

MGW A2EA

45 00 00 06 61 81 90 11 1F 00 00 00 00 00 00 00 00 00 00 00
iuTransportAssociation
- bindingID: '01025550'H
- secondCriticality: ignore
secondValue

15

Nokia Siemens Networks

- uP-ModeVersions: '0000000000000001'B
transportLayerInformation

-extension range:

- length (in bits): 00011111

- padding: 00000
- contents: 0A 3A 52 0C
iuTransportAssociation
- gTP-TEI: '3C000000'H

Tunnel Unit (TU) of SGSN

i.e. 10.58.82.12

Tunnel Endpoint

- service-Handover: handover-to-GSM-should-not-be-performed
- secondCriticality: ignore
secondValue
pDP-TypeInformation
- PDP-Type: ipv4
- PDP-Type: ipv4
- dataVolumeReportingIndication: do-not-report

RN33022EN10GLA00 PS Call Setup

RAB Assignment on IP transport (1/2)

Frame
Frame49
49(182
(182bytes
byteson
onwire,
wire,182
182bytes
bytescaptured)
captured)
Ethernet
EthernetII,II,Src:
Src:EmersonN_13:ce:1a
EmersonN_13:ce:1a(00:80:42:13:ce:1a),
(00:80:42:13:ce:1a),Dst:
Dst:Cisco_a9:fa:4d
Cisco_a9:fa:4d(00:1b:2a:a9:fa:4d)
(00:1b:2a:a9:fa:4d)
Internet
Protocol,
Src:
10.2.60.88
(10.2.60.88),
Source and destination IP Address
Internet Protocol, Src: 10.2.60.88 (10.2.60.88),Dst:
Dst:10.2.80.130
10.2.80.130(10.2.80.130)
(10.2.80.130)
Stream
StreamControl
ControlTransmission
TransmissionProtocol,
Protocol,Src
SrcPort:
Port:2906
2906(2906),
(2906),Dst
DstPort:
Port:m3ua
m3ua(2905)
(2905)
Source
Sourceport:
port:2906
2906
Source and destination SCTP port
Destination
Destinationport:
port:2905
2905
Verification
tag:
0x64722d39
Verification tag: 0x64722d39
Checksum:
Checksum:0x58d7f7ed
0x58d7f7ed(not
(notverified)
verified)
SACK
SACKchunk
chunk(Cumulative
(CumulativeTSN:
TSN:3641121891,
3641121891,a_rwnd:
a_rwnd:192000,
192000,gaps:
gaps:0,0,duplicate
duplicateTSNs:
TSNs:0)0)
DATA
chunk(ordered,
complete
DATA chunk(ordered, completesegment,
segment,TSN:
TSN:2507691165,
2507691165,SID:
SID:12,
12,SSN:
SSN:2,2,PPID:
PPID:3,3,payload
payloadlength:
length:104
104bytes)
bytes)
Chunk
Chunktype:
type:DATA
DATA(0)
(0)
Chunk
Chunkflags:
flags:0x03
0x03
Chunk
Chunklength:
length:120
120
TSN:
TSN:2507691165
2507691165
SCTP Stream ID
Stream
Identifier:
Stream Identifier:0x000c
0x000c
Stream
Streamsequence
sequencenumber:
number:22
Payload
Payloadprotocol
protocolidentifier:
identifier:M3UA
M3UA(3)
(3)
MTP
MTP33User
UserAdaptation
AdaptationLayer
Layer
Signalling
Connection
Control
Part
Signalling Connection Control Part
Radio
RadioAccess
AccessNetwork
NetworkApplication
ApplicationPart
Part
RANAP-PDU:
RANAP-PDU:initiatingMessage
initiatingMessage(0)
(0)
initiatingMessage
initiatingMessage
procedureCode:
id-RAB-Assignment
procedureCode: id-RAB-Assignment(0)
(0)
criticality:
criticality:reject
reject(0)
(0)
value
value
RAB-AssignmentRequest
RAB-AssignmentRequest

RAB Assignment Request Message

16

Nokia Siemens Networks

RN33022EN10GLA00 PS Call Setup

RAB Assignment on IP transport (2/2)

RAB-AssignmentRequest
.
.
.
RAB-SetupOrModifyItemFirst
rAB-ID: 05 [bit length 8]
rAB-Parameters
trafficClass: background (3)
rAB-AsymmetryIndicator: asymmetric-bidirectional (3)
maxBitrate: 2 items
Item 0
RAB-Parameter-MaxBitrateList: 8640000
Item 1
RAB-Parameter-MaxBitrateList: 2048000
deliveryOrder: delivery-order-not-requested (1)
maxSDU-Size: 12000
sDU-Parameters: 1 item
RAB QoS
Item 0
SDU-Parameters
sDU-ErrorRatio
mantissa: 1
exponent: 4
residualBitErrorRatio
mantissa: 1
exponent: 5
deliveryOfErroneousSDU: no (1)

17

Nokia Siemens Networks

RN33022EN10GLA00 PS Call Setup

allocationOrRetentionPriority
priorityLevel: Unknown (2)
pre-emptionCapability: shall-not-trigger-pre-emption (0)
pre-emptionVulnerability: pre-emptable (1)
queuingAllowed: queueing-not-allowed (0)
relocationRequirement: none (1)
userPlaneInformation
userPlaneMode: transparent-modeTransport
(0)
Layer Address,
uP-ModeVersions: 0001 [bit lengthGTP
16] Tunnel Endpoint ID
transportLayerInformation
transportLayerAddress: 0A 02 3C CA [bit length 32]
iuTransportAssociation: gTP-TEI (0)
gTP-TEI: 00000004
service-Handover: handover-to-GSM-should-not-be-performed (1)
.
.
.

Encryption in SGSN

Encryption setting in 3G SGSN

18

Nokia Siemens Networks

RN33022EN10GLA00 PS Call Setup

Encryption Off vs. Encryption On

Encryption OFF

Encryption ON

User Data can not be decoded

19

Nokia Siemens Networks

RN33022EN10GLA00 PS Call Setup

Encryption Off vs. Encryption On

Encryption OFF

20

Nokia Siemens Networks

RN33022EN10GLA00 PS Call Setup

Encryption ON

Iu-PS Attach (1/2)

UE

Node-B

SGSN

RNC
RRC Connection Setup

RRC

Initial Direct Transfer

RRC

Attach Request GMM

RANAP

Initial UE Message

RANAP

Attach Request GMM

RANAP

RRC

RRC

Identity Request (GMM)

Identity Response (GMM)

Nokia Siemens Networks

RN33022EN10GLA00 PS Call Setup

RANAP

RRC

RRC

RANAP

21

GMM : Identity Request

GMM: Identity Response

RANAP

Iu-PS Attach (2/2)

Node-B

UE

SGSN

RNC
RRC Connection Setup
RANAP

GMM: Authentication & Ciphering Request

RRC
RRC

GMM: Authentication & Ciphering Response

GMM: Authentication &

Ciphering Request

RANAP

RRC
RRC
RANAP
RANAP

GMM: Authentication &

Ciphering Response
Common
ID

RANAP
RANAP

Security Mode Command

RANAP
RRC
RRC

GMM: Attach Accept

GMM: Attach Complete

Nokia Siemens Networks

RANAP

RRC
RRC
RANAP

22

GMM: Attach Accept

GMM: Attach Complete

RANAP

RN33022EN10GLA00 PS Call Setup

Common ID
The purpose of the Common ID procedure is to inform the RNC about the permanent NAS UE identity (IMSI) of
a user. This is used by the RNC, for example, to create a reference between the permanent NAS UE identity of
the user and the Radio Resource Control (RRC) connection of that user for UTRAN paging coordination. The
procedure uses connection-oriented signalling. The figure below describes the Common ID procedure.
Security Mode Command
The purpose of the Security Mode Control procedure is to allow the CN to pass cipher and integrity mode
information to the UTRAN. The UTRAN uses this information to select and load the encryption device for user
and signalling data with the appropriate parameters, and also to store the appropriate parameters for the
integrity algorithm. The procedure uses connection-oriented signalling
CommonID
- extension flag: 0
- preamble: 0
protocolIEs
- padding: 000000
- length: 00 01
- id: 23
- contents: 00 17
- criticality: ignore
- contents (in bits): 01
- padding: 000000
- opentype length: 09
PermanentNAS-UE-ID
- extension flag: 0
- iMSI: '62029903000040F1'H
- length (in bits): 101
- padding: 0000
- contents: 62 02 99 03 00 00 40 F1