02a Iu-PS Interface

1 © Nokia Siemens Networks CN3203EN01GLN00

PCNSIG

Iu-PS interface


Objectives

After the module, the participants will be able to:

• Describe the main functions of RANAP signalling protocols in Iu-PS interface

• Explain the Attach procedure in the Iu-PS interface

• Explain the PDP Context Activation procedure in the Iu-PS interface

• Describe the main Function of GTP-U in Iu-PS


NSN - Fully ETSI Compliant Interfaces

Gi

Gn

IuPS

Gc

Gp

Signalling and Data Transfer Interface

Signalling Interface

UE RAN TE PDN

Uu

Gr

HLR

Other PLMN

SGSN

GGSN

GGSN

SGSN

Gn

SGSN

Gp


User Plane protocol stacks for Iu-PS

IuPS over ATM IuPS over IP

ATM

UDP/IP

GTP-U

AAL5

L1

UDP/IP

GTP-U

L2

Relay


Control Plane protocol stacks for Iu-PS

IuPS over IP IuPS over ATM

RANAP

SCCP

MTP - 3b

SSCF SSCOP

AAL5

ATM

M3UA

SCTP

IP

L2

SCCP - SAP

Iu - PS Control Plane

SAAL - NNI

RANAP

SCCP

MTP - 3b

SSCF SSCOP

AAL5

ATM

M3UA

SCTP

IP

L2

SCCP - SAP

Iu - PS Control Plane

SAAL - NNI


SCCP services

Basic

Connectionless

Service

Sequenced

Connectionless

Service

Basic

Connection -

oriented

Service

Flow Control

Connection -

oriented

Service

Connectionless

Services

Connection - oriented

Services

0 1 2 3

Services provided by the SCCP

Protocol Class

Basic

Connectionless

Service

Basic

Connectionless

Service

Sequenced

Connectionless

Service

Sequenced

Connectionless

Service

Basic

Connection -

oriented

Service

Basic

Connection -

oriented

Service

Flow Control

Connection -

oriented

Service

Flow Control

Connection -

oriented

Service

Connectionless

Services

Connectionless

Services


Services


Services

0 1 2 3

Services provided by the SCCP Services provided by the SCCP

Protocol Class

Data packets delivered out of

sequence

Data packets delivered in

sequence using the same path bi-directional transfer of data

units by establishing a

temporary connection

(not used in GSM)


SCCP connectionless messages

Message Protocol

class

Description

UDT 0,1 Unitdata

UDTS 0,1 Unitdata Service. Used to indicate to the originating SCCP that a

UDT cannot be delivered to its destination.

XUDT 0,1 Extended Unitdata. Used to send data along with optional

parameters.

XUDTS 0,1 Extended Unitdata Service. Used to indicate to the originating

SCCP that an XUDT cannot be delivered to its destination.

LUDT 0,1 Long Unitdata. Used to send data along with optional parameters

over MTP3b (Q.2210). Up to 3952 octets without segmentation are

allowed.

LUDTS 0,1 Long Unitdata Service. Used to indicate to the originating SCCP

that an LUDT cannot be delivered to its destination.


SCCP connection-oriented messages

Message Service type

Description

CC 2,3

Connection Confirm

CR 2,3

Connection Request

2,3

Connection Refused

AK 3

Data acknowledgement. Used to control the window flow control mechanism selected for

the data transfer phase.

DT1 2

Data Form 1 (=protocol class 2)

DT2 3

Data Form 2 (=protocol class 3)

ED 3

Expedited Data. Similar to DT2 but it can bypass the flow control mechanism.

EA 3

Expedited Data acknowledgement. Every ED message must be acknowledged with EA

message before another ED is sent.

IT 2,3

Inactivity Test. Sent periodically to check if the connection is still active at both ends and

to audit the consistency of data.

ERR 2,3

Protocol Data Unit Error. Sent on detection of the SCCP protocol error.

RLSD 2,3

Released

RLC 2,3

Release Complete

RSC 3

Reset Confirm.

RSR 3

Reset Request. Indicates that the SCCP needs to reset the sequence numbers.

REF


Example of SCCP Messages 1 CR - CONNECTION REQUEST

Source Local Reference

- 61F144h

Protocol Class

- 2h, connection oriented

Called Party Address

- length 2 (02h)

- no global title present

- routing based on SSN and MTP routing label

- subsystem: RANAP

Calling Party Address

- length 4 (04h)



- point code : 4144 (1030h)

- subsystem: RANAP

SCCP User Data

- length: 97 (61h)

- data :

00 13 40 5D 00 00 07 00 03 40 01 80 00 0F 40 06 00 32 F4 02 00 05 00 37

40 01 02 00 3A 40 08 00 32 F4 02 00 05 00 A2 00 10 40 26 25 08 01 02 E5

00 79 07 02 05 F4 38 A9 05 5A 32 F4 02 00 05 02 0A 14 F3 82 33 4C 03 26

3C A0 60 19 63 92 B6 17 16 00 4F 40 03 01 61 01 00 56 40 05 32 F4 02 00

01

End of Optional Parameters


Example of SCCP Messages 2

CC - CONNECTION CONFIRM

Destination Local Reference

- 61F144h


- 040000h

Protocol Class



- length 4 (04h)



- point code : 4144 (1030h)

- subsystem: RANAP



Example of SCCP Messages 3

RLSD - RELEASED


- 61F144h


- 040000h

Release Cause

- end user originated

RLC - RELEASE COMPLETE


- 040000h


- 61F144h


3G SGSN-UE Control Plane

UE Uu RNC Iu-PS SGSN


RANAP Functions

The most important functions of RANAP are:

• Relocating the Serving RNC.

This function facilitates the change of the Serving RNC including the related Iu resources.

• Radio Access Bearer (RAB) management.

This function is responsible for setting up, modifying and releasing RABs (for example, PDP contexts).

• Paging.

This function provides the SGSN with the capability to page the UE.

• Location reporting.

This function is used for transferring the actual location information from the RNC to the SGSN.

• Reporting general error situations.


RANAP Procedures

RANAP functions are implemented by one or more RANAP elementary procedures.

RANAP procedures are divided into three classes depending on the number of possible response messages:

Class 1: procedures have exactly one response message.

Class 2: procedures have no response messages.

Class 3: procedures have at least one response message.


Initial UE Message

The purpose of the Initial UE Message procedure is to establish an Iu signalling

connection between a CN domain and the RNC and to transfer the initial NAS-PDU to

the default CN node.


Example of Initial UE-Message INITIAL UE-MESSAGE RANAP-PDU

- extension flag: 0

- choice index: 00

initiatingMessage

- procedureCode: 19

- padding: 00000

- contents

- criticality: ignore

- contents (in bits): 01

initiatingMessage

- padding: 000000

- opentype length

InitialUE-Message

- extension flag: 0

- preamble: 0

protocolIEs

- padding: 000000

- length

- id: 3

- contents



- padding: 000000

- opentype length

CN-DomainIndicator: ps-domain

-contents (in bits): 1

- trailing bits: 0000000

- id: 15

- contents



- padding: 000000

- opentype length

LAI

- preamble: 0

- pLMNidentity: '32F403'H

- padding: 0000000

- contents

- lAC: '03EF'H

- contents

- id: 55

- contents



- padding: 000000

- opentype length

RAC: '01'H

- contents

- id: 58

- contents



- padding: 000000

- opentype length SAI

- preamble: 0


- padding: 0000000

- contents

- lAC: '03EF'H

- contents

- SAC: 'EA62'H

- contents

- id: 16

- contents



- padding: 000000

- opentype length

NAS-PDU: '080C1605F42A00035B32022000'H

- length

- contents

- id: 79

- contents



- padding: 000000

- opentype length

IuSignallingConnectionIdentifier:

'000000011111011000000000'B

- contents

- id: 86

- contents



- padding: 000000

- opentype length

GlobalRNC-ID


- contents

-RNC-ID: 3007

- contents


CN originated Direct Transfer Message

The purpose of the Direct Transfer procedure is to carry UE-CN signalling messages

over the Iu interface.


Example of CN originated Direct Transfer Message

DIRECT TRANSFER RANAP-PDU

- extension flag: 0

- choice index: 00

initiatingMessage

- procedureCode: 20

- padding: 00000

- contents



initiatingMessage

- padding: 000000

- opentype length

DirectTransfer

- extension flag: 0

- preamble: 0

protocolIEs

- padding: 000000

- length

- id: 16

- contents

-criticality: ignore


- padding: 000000

- opentype length

NAS-PDU: '8A47'H

- length

- contents

- id: 59

- contents



- padding: 000000

- opentype length

SAPI: sapi-0

- extension range: 0




UTRAN originated Direct Transfer

The purpose of the Direct Transfer procedure is to carry UE-CN signalling messages

over the Iu interface.


Example of UTRAN originated Direct Transfer Message

DIRECT TRANSFER RANAP-PDU

- extension flag: 0

- choice index: 00

initiatingMessage

- procedureCode: 20

- padding: 00000

- contents



initiatingMessage

- padding: 000000

- opentype length

DirectTransfer

- extension flag: 0

- preamble: 0

protocolIEs

- padding: 000000

- length

- id: 16

- contents



- padding: 000000

- opentype length

NAS-PDU: '0A4624'H

- length

- contents

- id: 15

- contents



- padding: 000000

- opentype length

LAI

- preamble: 0


- padding: 0000000

- contents

- lAC: '03EF'H

- contents

- id: 55

- contents



- padding: 000000

- opentype length

RAC: '01'H

- contents

- id: 58

- contents



- padding: 000000

- opentype length

SAI

- preamble: 0


- padding: 0000000

- contents

- lAC: '03EF'H

- contents

- SAC: 'EA62'H

- contents


RAB Assignment procedure

The purpose of the RAB Assignment procedure is to establish new RABs and/or to

enable modifications and/or releases of already established RABs for a given UE.


Example of RAB Assignment Request Message RAB-ASSIGNMENT REQUEST RANAP-PDU

- extension flag: 0

- choice index: 00

initiatingMessage

- procedureCode: 0

- padding: 00000

- contents



initiatingMessage

- padding: 000000

- opentype length

RAB-AssignmentRequest

- extension flag: 0

- preamble: 0

protocolIEs

- padding: 000000

- length

- id: 54

- contents



- padding: 000000

- opentype length

RAB-SetupOrModifyList

- length

- length

- id: 53

- contents

- firstCriticality: reject


- padding: 000000

- opentype length

firstValue

- extension flag: 0

- preamble: 111100

- rAB-ID: '00000101'B


- nAS-SynchronisationIndicator: '1111'B

-contents (in bits): 1111 rAB-Parameters

- extension flag: 0

- preamble: 0011010

- trafficClass: interactive


- contents (in bits): 10 - rAB-AsymmetryIndicator: symmetric-bidirectional



maxBitrate

- length (in bits): 0

- MaxBitrate: 64000


- padding: 0000

- contents

- deliveryOrder: delivery-order-not-requested


- maxSDU-Size: 12000

- padding: 0000000

- contents

sDU-Parameters


- extension flag: 0

- preamble: 100

sDU-ErrorRatio

- preamble: 0

- mantissa: 1


- exponent: 4

-contents (in bits): 011 residualBitErrorRatio

- preamble: 0

- mantissa: 1


- exponent: 5


- deliveryOfErroneousSDU: no


- trafficHandlingPriority: 3

-contents (in bits): 0011 allocationOrRetentionPriority

- extension flag: 0

- preamble: 0

- priorityLevel: 3


- pre-emptionCapability: shall-not-trigger-pre-emption


- pre-emptionVulnerability: not-pre-emptable


- queuingAllowed: queueing-allowed


- relocationRequirement: none



userPlaneInformation

- extension flag: 0

- preamble: 0

- userPlaneMode: transparent-mode (user data transfer without framing and

control function on user data transfer (SDU size) as Support mode)



- uP-ModeVersions: '0000000000000001'B

- contents (in bits): 00000000 0000 0001

transportLayerInformation

- extension flag: 0

- preamble: 0

- transportLayerAddress: '10101100000100100110001011000110'- extension range: 0


- padding: 0

- contents

iuTransportAssociation (RAB – bearer association)

- extension flag: 0

- choice index: 0

- gTP-TEI: '0000011F'H (TEID in SGSN)

- padding: 000000

- contents

- secondCriticality: ignore


- padding: 000000

- opentype length

secondValue

- extension flag: 0

- preamble: 1100000

pDP-TypeInformation


- PDP-Type: ipv4



- dataVolumeReportingIndication: do-report


- trailing bits: 00


Example of RAB Assignment Response Message

RAB-ASSIGNMENT RESPONSE RANAP-PDU

- extension flag: 0

- choice index: 11

outcome

- procedureCode: 0

- padding: 00000

- contents

- criticality: reject


outcome

- padding: 000000

- opentype length

RAB-AssignmentResponse

- extension flag: 0

- preamble: 0

protocolIEs

- padding: 000000

- length

- id: 52

- contents



- padding: 000000

- opentype length

RAB-SetupOrModifiedList

- length

- length

- id: 51

- contents



- padding: 000000

- opentype length

RAB-SetupOrModifiedItem

- extension flag: 0

- preamble: 1100

- rAB-ID: '00000101'B


- transportLayerAddress: '10101100000100100110000110000011'B



- padding: 00

- contents

iuTransportAssociation

- extension flag: 0

- choice index: 0

- gTP-TEI: '00000000'H (TEID in RNC)

- padding: 000000

- contents


Iu Release Request

The purpose of the Iu Release Request procedure is to enable the UTRAN to request

the CN to release the Iu connection for a particular UE due to some UTRAN generated

reasons (for example 'O&M Intervention', 'Unspecified Failure', 'User Inactivity',

'Repeated Integrity Checking Failure', 'Release due to UE generated signalling

connection release‘).


Example of Iu Release Request Message

Iu-Release Request

- extension flag: 0

- preamble: 0

protocolIEs

- padding: 000000

- length: 00 01

- id: 4

- contents: 00 04



- padding: 000000

- opentype length: 02

Cause

- extension flag: 0

- choice index: 000

- radioNetwork: radio-connection-with-UE-Lost



Iu Release Procedure

The purpose of the Iu Release procedure is to enable the CN to release the Iu connection

and all the UTRAN resources related only to that Iu connection to be released.


Examples of Iu Release Procedure Messages

IU-RELEASE COMMAND RANAP-PDU

- extension flag: 0

- choice index: 00

initiatingMessage

- procedureCode: 1

- padding: 00000

- contents



initiatingMessage

- padding: 000000

- opentype length

Iu-ReleaseCommand

- extension flag: 0

- preamble: 0

protocolIEs

- padding: 000000

- length

- id: 4

- contents



- padding: 000000

- opentype length

Cause

- extension flag: 0

- choice index: 000

- radioNetwork: no-remaining-rab

- contents (in bits):

IU-RELEASE COMPLETE RANAP-PDU

- extension flag: 0

- choice index: 01

successfulOutcome

- procedureCode: 1

- padding: 00000

- contents



successfulOutcome

- padding: 000000

- opentype length

Iu-ReleaseComplete

- extension flag: 0

- preamble: 0

protocolIEs

- padding: 000000

- length

- id: 31

- contents



- padding: 000000

- opentype length

RAB-DataVolumeReportList

- length

- length

- id: 30

- contents



- padding: 000000

- opentype length

RAB-DataVolumeReportItem

- extension flag: 0

- preamble: 10

- rAB-ID: '00000101'B


dl-UnsuccessfullyTransmittedDataVolume


- extension flag: 0

- preamble: 00

- dl-UnsuccessfullyTransmittedDataVolume: 0


- padding: 0000000

- contents


Paging procedure

The purpose of the Paging procedure is to enable the CN to request the UTRAN to

contact the UE


Example of Paging procedure Paging - extension flag: 0

- preamble: 0

protocolIEs

- padding: 000000

- length: 00 06

- id: 3

- contents: 00 03



- padding: 000000





- id: 23

- contents: 00 17



- padding: 000000


PermanentNAS-UE-ID

- extension flag: 0

- iMSI: '62029903000040F1'H


- padding: 0000

- contents: 62 02 99 03 00 00 40 F1

- id: 64

- contents: 00 40



- padding: 000000


TemporaryUE-ID

- extension flag: 0

- choice index: 1

- p-TMSI: '09C24B3C'H

- padding: 000000

- contents: 09 C2 4B 3C

- id: 21

- contents: 00 15



- padding: 000000


PagingAreaID

- extension flag: 0

- choice index: 1

rAI

- extension flag: 0

- preamble: 0

lAI

- preamble: 0


- padding: 000

- contents: 62 F2 90

- lAC: '00C9'H

- contents: 00 C9

- rAC: '17'H

- contents: 17

- id: 22

- contents: 00 16



- padding: 000000


PagingCause: terminating-background-call




- id: 17

- contents: 00 11



- padding: 000000


NonSearchingIndication: searching




Common ID procedure

The purpose of the Common ID procedure is to inform the RNC about the permanent

NAS UE Identity (IMSI) of a user. It is used by the RNC to create a reference between

the permanent NAS UE identity of the user and the RRC connection of that user for

UTRAN paging coordination.


Example of Common ID Message

COMMONID

RANAP-PDU

- extension flag: 0

- choice index: 00

initiatingMessage

- procedureCode: 15

- padding: 00000

- contents



initiatingMessage

- padding: 000000

- opentype length

CommonID

- extension flag: 0

- preamble: 0

protocolIEs

- padding: 000000

- length

- id: 23

- contents



- padding: 000000

- opentype length

PermanentNAS-UE-ID

- extension flag: 0

- iMSI: '32349030037865F9'H


- padding: 0000

- contents


Security Mode Control

The purpose of the Security Mode Control procedure is to allow the CN to pass

cipher and integrity mode information to the UTRAN. 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.


Example of Security Mode Command Message

SECURITY MODE COMMAND RANAP-PDU

- extension flag: 0

- choice index: 00

initiatingMessage

- procedureCode: 6

- padding: 00000

- contents



initiatingMessage

- padding: 000000

- opentype length

SecurityModeCommand

- extension flag: 0

- preamble: 0

protocolIEs

- padding: 000000

- length

- id: 12

- contents



- padding: 000000

- opentype length

IntegrityProtectionInformation

- preamble: 0

permittedAlgorithms


- IntegrityProtectionAlgorithm: standard-UMTS-integrity-algorithm--

contents (in bits): 0000

- key:

'01100010111111100000110100110110100000111010111010100101001101101110

000101010000101

010000000000001100010111111100000110100110110'B

- padding: 0000000

- contents

- id: 11

- contents



- padding: 000000

- opentype length

EncryptionInformation

- preamble: 0

permittedAlgorithms


- EncryptionAlgorithm: no-encryption


- key:

'10000011101011101010010100110110111000010101000010101000000000001000

001110101110101

001010011011011100001010100001010100000000000'B

- padding: 0000000

- contents

- id: 75

- contents



- padding: 000000

- opentype length

KeyStatus: old





Example of Security Mode Complete Message

SECURITY MODE COMPLETE RANAP-PDU

- extension flag: 0

- choice index: 01

successfulOutcome

- procedureCode: 6

- padding: 00000

- contents



successfulOutcome

- padding: 000000

- opentype length

SecurityModeComplete

- extension flag: 0

- preamble: 0

protocolIEs

- padding: 000000

- length

- id: 6

- contents



- padding: 000000

- opentype length

ChosenIntegrityProtectionAlgorithm: standard-UMTS-integrity-algorithm-UIA1



- id: 5

- contents



- padding: 000000

- opentype length

ChosenEncryptionAlgorithm: no-encryption




Relocation Preparation (step 1)


Relocation Resource Allocation (step 2)

The purpose of the Relocation Resource Allocation procedure is to allocate resources

from the S-RNC to the T-RNC.


Relocation Detect (step 3)

The purpose of the Relocation Detect procedure is to get indicated the detection of the

SRNS relocation execution to the CN by the RNC.


SRNS Context Transfer (step 4)

The purpose of the SRNS Context Transfer procedure is to trigger the transfer of the

SRNS contexts from the source RNC to the CN (PS domain).


SRNS Data Forwarding Initiation (step 5)

The purpose of the SRNS Data Forwarding procedure is to trigger the transfer of

network protocol data units (N-PDUs) from the RNC to the CN (PS domain).


SRNS Context Forwarding from Source RNC to CN (step 6)

The purpose of the SRNS Context Forwarding from Source RNC to CN procedure is

to transfer the SRNS contexts from the source RNC to the CN (PS domain).

The contexts contain the sequence numbers of the GTP-PDUs to be transmitted next

in the uplink and downlink directions and the PDCP sequence numbers that would

have been used next to send and receive data from the UE.


SRNS Context Forwarding to Target RNC from CN (step 7)

The purpose of the SRNS Context Forwarding to Target RNC from CN procedure is to

transfer SRNS contexts from the CN (PS domain) to the target RNC.

The contexts contain the sequence numbers of the GTP-PDUs to be transmitted next in

the uplink and downlink directions and the PDCP sequence numbers that would have

been used next to send and receive data from the UE.


Relocation Complete (step 8)

The purpose of the Relocation Complete procedure is to get indicated the completion

of the SRNS relocation to the CN by the target RNC. The SGSN updates the PDP

contexts to the GGSN when a Relocation Complete message is received.


Relocation Cancel (step 9)

The purpose of the Relocation Cancel procedure is to enable the source RNC to

cancel an ongoing relocation of the SRNS.


L3-SMM Signalling

UE Uu RNC Iu-PS SGSN


L3-SMM Procedures

The L3 signalling procedures are the following:

• Common procedures: P-TMSI reallocation, authentication, identification and IMSI detach

• Mobility Management procedures: Attach, detach, location updating, periodic updating, IMSI attach and several connection management procedures

• Session Management procedures: PDP context activation, modification and deactivation

• SMS: Short Message Control (SMC) and Short Message Relay function(SM-RL).


Combined GPRS/ IMSI Attach Procedure

7d. Cancel Location Ack

7c. Cancel Location

7b. Update Location

7g. Update Location Ack

7e. Insert Subscriber Data

7f. Insert Subscriber Data Ack

6d. Insert Subscriber Data

6c. Cancel Location Ack

6b. Cancel Location

3. Identity Response

2. Identification Response

2. Identification Request

1. Attach Request

5. IMEI Check

3. Identity Request

4. Authentication

6a. Update Location

7a. Location Update Request

7h. Location Update Accept

6f. Update Location Ack

6e. Insert Subscriber Data Ack

MS UTRAN new SGSN old SGSN GGSN HLR EIR

old MSC/VLR

new MSC/VLR

9. Attach Complete

8. Attach Accept

10. TMSI Reallocation Complete

C1


Example of Attach Request Message ATTACH REQUEST (GPRS MM) MS Network Capability

- Encryption algorithm GEA/1 available

- SM capabilities via dedicated channels supported

- SM capabilities via GPRS channels supported

- Use of default alphabet over UCS2 prefered

- Capab. of ellipsis notation and phase 2 error handling

- The ME does not support SoLSA

- Mobile station supporting R99 or later versions

- Mobile station does not support BSS packet flow procedures

- encryption algorithm GEA/2 not available






Attach Type

- GPRS attach

- Follow-on request pending

GPRS Ciphering Key Seq. Nr

- value: 7 (07h)

DRX Parameter

- Split PG Cycle value: 7

- DRX cycle length coefficient not specified by the MS

- Split pg cycle on CCCH not supported

- max. 2 sec non-DRX mode after transfer state

Mobile identity

- length: 5 (05h)

- TMSI/P-TMSI: 38A9055A

Routing Area Id.

- Mobile Country Code: 234

- Mobile Network Code: 20

- Location Area Code: 5 (5h)

- Routing Area Code: 2 (02h)

MS Radio Access Capability

GSM 900-E Access Technology Type

- Length: 39 bits

- Radio capability : 4

- Encrypt. algorithm A5/1 available


- Encrypt. algorithm A5/3 not available





- Controlled early Classmark Sending implemented

- PS capability not present

- VGCS capability and notifications not wanted

- VBS capability and notifications not wanted

- HSCSD Multislot Class: 6

- GPRS Multislot Class: 6

- GPRS Ext. Dynamic Alloc. Capability not implemented

- COMPACT Interference Meas. Capab. is not implemented

- The ME is Release '98 onwards

- UMTS FDD supported

- UMTS TDD not supported

- CDMA2000 not supported

GSM 1800 Access Technology Type

- Length: 15 bits

- RF Power class: 1, max 1 W (30 dBm)










- Spare ok

P-TMSI signature (authentication value)

- Value: 63 92 B6

GPRS Timer (Ready timer in mobile phone)

- Value: 44 sec


Identity Request Examples

IDENTITY REQUEST (GMM) (GPRS MM)

Identity Type 2

- IMSI

Force to Standby

- not indicated

IDENTITY REQUEST (GMM) (GPRS MM)

Identity Type 2

- IMEISV

Force to Standby

- not indicated


Identity Response Examples

IDENTITY RESPONSE (GMM) (GPRS MM)

Mobile identity

- length: 8 (08h)

- IMSI: 262099300000041

IDENTITY RESPONSE (GMM) (GPRS MM)

Mobile identity

- length: 9 (09h)

- IMEISV: 3509891000263900


Example of Attach Accept Message

ATTACH ACCEPT (GPRS MM)

Attach Result

- GPRS only attached

Force to Standby

- not indicated

GPRS Timer (periodic RA update)

- Value: 30 min

Radio Priority

- Priority level 4

Routing Area Id.



- Location Area Code: 5 (5h)

- Routing Area Code: 2 (02h)

P-TMSI signature (authentication value stored in SGSN)

-Value: 4E 4C 63

GPRS Timer (Negotiated Ready Timer) (used only in case of 3G–2G HO)

- Value: 44 sec

P-TMSI

-length: 5 (05h)

-TMSI/P-TMSI: 1C711B1C


MS Initiated Service Request Procedure

SGSN MS

2. Service Request (P-TMSI, RAI, CKSN, Service Type (e.g.Data)

3. Security Functions

RNC 1. RRC Connection Request

8. Uplink PDU

1. RRC Connection Setup

4. Radio Access Bearer Assignment Request (RAB ID, TEID, QoS Profile, SGSN IP Address)

6. Radio Access Bearer Assignment

Response (RAB ID, TEID, QoS Profile, RNC IP Address)

5. Radio Bearer Setup

6. Radio Bearer Setup Complete

HLR GGSN

7. SGSN-Initiated PDP Context Modification (RAB re-established)

4. Service Accept (Data)


Network Initiated Service Request Procedure

7. SGSN-Initiated PDP Context Modification Procedure (RAB re-established)

8. Downlink PDU

SGSN MS

5. Security Functions

RNC

3. RRC Connection Request

1. Downlink PDU

3. RRC Connection Setup

6. Radio Access Bearer Assignment Request (RAB ID, TEID, QoS Profile, SGSN IP Address)

6. Radio Access Bearer Assignment Response (RAB ID, TEID, QoS Profile, RNC IP Address)

6. Radio Bearer Setup

6. Radio Bearer Setup Complete

2. Paging

2. Paging

4. Service Request (P-TMSI, RAI, CKSN, Service Type (e.g Paging Response)

HLR GGSN


Example of Service Request Message

SERVICE REQUEST (GPRS MM)

- Skip Indicator: 00h


- value: 0 (00h)

Signalling

P-TMSI

- length: 5 (05h)

- TMSI/P-TMSI: F0E2E797

PDP context status

- length: 2

- NSAPI(5) context is PDP-INACTIVE












PDP Context Activation Procedure for UMTS

3G - GGSN

6. Activate PDP Context Accept (PDP Type, PDP Address, TI, QoS Negotiated, Radio Priority, Packet Flow Id, PDP Configuration Options)

2. Create PDP Context Response (TEID, PDP Address, PDP Configuration Options, QoS Negotiated, Charging Id, Cause)

2. Create PDP Context Request (PDP Type, PDP Address, Access Point Name, QoS Negotiated, TEID, NSAPI,

MSISDN, Selection Mode, Charging Characteristics, Trace Reference, Trace Type,

Trigger Id, OMC Identity, PDP Configuration Options)

1. Activate PDP Context Request (NSAPI, TI, PDP Type, PDP Address, Access Point Name, QoS Requested, PDP Configuration Options)

3G - SGSN UTRAN MS

3. Radio Access Bearer Setup

4. Invoke Trace (Trace Reference, Trace Type, Trigger Id, OMC Identity)

5. Update PDP Context Response

5. Update PDP Context Request (QoS downgraded/

Direct Tunnel)


Example of PDP Context Activation Request Message

ACT. PDP CONTEXT REQUEST (GPRS SM) Network Serv. Access Point Id

- NSAPI 5

LLC Serv. Access point Id only used in SGSN in case of 3G – 2G HO

- SAPI 3

Quality of Service

- length: 11 (0Bh)

- Reliab. class: Subscribed (MS only)

- Delay class: Subscribed

- Precedence class: Subscribed

- Peak throughput: Subscribed

- Mean throughput: Best effort

- Traffic class: Subscribed

- Delivery order: Subscribed

- Delivery of erroneous SDUs: Subscribed

- Maximum SDU size: Subscribed maximum SDU size

- Maximum bit rate for uplink: Subscribed (MS only)

- Maximum bit rate for downlink: Subscribed (MS only)

- Residual BER: Subscribed

- SDU error ratio: Subscribed

- Transfer delay: Subscribed (MS only)

- Traffic handling priority: Subscribed

- Guaranteed bit rate for uplink: Subscribed (MS only)

- Guaranteed bit rate for downlink: Subscribed (MS only)

Packet Data Protocol Address

- Length: 2 (02h)

- Dynamic PDP addressing is applied

- PDP type organisation: IETF allocated address

- PDP type number: IPv4

Protocol Conf. Options

- length: 37 (25h)

- Configuration protocol: IP PDP type

Password Authentic. Protocol (PAP)

Internet Protocol Control Protocol (IPCP)

Contents: 01 05 00 10 81 06 00 00 00 00 83 06 00 00 00 00


Quality of service information element

8 7 6 5 4 3 2 1

Quality of service IE Octet 1

Length of quality of service IE Octet 2

0 0 spare

Delay class Reliability class Octet 3

Peak throughput 0 spare

Precedence class Octet 4

0 0 0 spare

Mean throughput Octet 5

Traffic Class Delivery order Delivery of erroneous SDU

Octet 6

Maximum SDU size Octet 7

Maximum bit rate for uplink Octet 8

Maximum bit rate for downlink Octet 9

Residual BER SDU error ratio Octet 10

Transfer delay Traffic Handling priority

Octet 11

Guaranteed bit rate for uplink Octet 12

Guaranteed bit rate for downlink Octet 13


Example of PDP Context Activation Response Message

ACT. PDP CONTEXT ACCEPT (GPRS SM) LLC Serv. Access point Id

- SAPI 3

Quality of Service

- length: 11 (0Bh)

- Reliab. class: Unack. GTP and LLC Ack. RLC Protected data

- Delay class: Delay class 4 (best effort)

- Precedence class: Normal priority

- Peak throughput: Up to 16 000 octet/s


- Traffic class: Background class

- Delivery order: Without delivery order ('no')

- Delivery of erroneous SDUs: No detect (‘-‘)

- Maximum SDU size: 1510 Octets

- Maximum bit rate for uplink: 64 kbps

- Maximum bit rate for downlink: 128 kbps

- Residual BER: 1*10-5

- SDU error ratio: 1*10-3


- Traffic handling priority: level 2



Radio Priority

- Priority level 4


- Length: 6 (06h)



- Address: 10.1.1.133


- length: 20 (14h)



Contents: 03 05 00 10 81 06 7F 00 00 01 83 06 7F 5E 00 00 01


Iu-PS User Plane

L1

RLC

PDCP

MAC

E.g. , IP , PPP

Application

L1

RLC

PDCP

MAC

ATM

UDP/IP

GTP - U

AAL5

Relay

L1

UDP/IP

L2

GTP - U

E .g. , IP , PPP

UTRAN MS

Iu - PS Uu Gn Gi

GGSN SGSN

ATM

UDP/IP

GTP - U

AAL5

L1

UDP/IP

GTP - U

L2

Relay


Iu UP protocol layer occurrence in UTRAN overall architecture

UTRAN UE CN Access Stratum

Non-Access Stratum

Radio

(Uu) Iu

Iu UP Radio protocols

Iu UP

User plane Data

Bearers protocols

Transport Layer

NAS Data Streams

NAS Data Streams

Radio protocols

User plane Data

Bearers protocols


Iu UP protocol layer in transparent occurrence over Iu interface

Iu UP layer intransparent mode

TNL-SAP

RNL-SAP

Iu Interface

TNL-SAP

Iu UP layer intransparent mode

CNUTRAN

Rad

io In

terf

ace

Pro

toco

ls

Non AccessStratum

Access Stratum


Iu UP protocol layer in support mode occurrence over Iu interface

Iu UP layer insupport mode

TNL-SAP

RNL-SAP

Iu Interface

TNL-SAP

Support ModeFunctions

Iu UP layer insupport mode

CNUTRAN

Rad

io In

terf

ace

Pro

toco

ls

Non AccessStratum

Access Stratum

Transfer of IuUP protocol

frames

Support ModeFunctions


GTP-U Message-1

ATM Conn:1 VPI:0 VCI:100 CID:0 Line:1 7983 15:48:22.538714

AAL5

CPCS-PDU

AA AA 03 00 00 00 08 00 45 00 00 60 30 EB 00 00 3F 11 C7 90 0A 0A 0A 1F

0A DE 64 0B 05 27 08 68 00 4C 3D 7A 30 FF 00 3C 00 00 00 00 45 00 00 3C

C2 2E 00 00 FD 01 6A BC C0 A8 03 3C C0 A8 0C 49 00 00 A3 5B 16 00 9C 00

61 62 63 64 65 66 67 68 69 6A 6B 6C 6D 6E 6F 70 71 72 73 74 75 76 77 61

62 63 64 65 66 67 68 69

CIP (Classic IP layer)

- LLC Header: SNAP AAAA03h

SNAP Header

- OUI: Ethertype

- PID: IPv4

CIP Data:

45 00 00 60 30 EB 00 00 3F 11 C7 90 0A 0A 0A 1F 0A DE 64 0B 05 27 08 68

00 4C 3D 7A 30 FF 00 3C 00 00 00 00 45 00 00 3C C2 2E 00 00 FD 01 6A BC

C0 A8 03 3C C0 A8 0C 49 00 00 A3 5B 16 00 9C 00 61 62 63 64 65 66 67 68

69 6A 6B 6C 6D 6E 6F 70 71 72 73 74 75 76 77 61 62 63 64 65 66 67 68 69

IP DATAGRAM

IP version : 4

Internet header length (in octets) : 20

Type of service :

- 000 - Routine

- normal delay (minimize delay)

- normal throughput

- normal reliability

Total length (in octets) : 96

Identification : 12523 (30EB)

Flags:

- May fragment

- Last fragment

Fragment offset (in octets) : 0

Time to live (in seconds) : 63

Next level protocol : UDP

Checksum : 51088 (C790)

Source address : 10.10.10.31

Destination address : 10.222.100.11

data:

05 27 08 68 00 4C 3D 7A 30 FF 00 3C 00 00 00 00 45 00 00 3C C2 2E 00 00

FD 01 6A BC C0 A8 03 3C C0 A8 0C 49 00 00 A3 5B 16 00 9C 00 61 62 63 64

65 66 67 68 69 6A 6B 6C 6D 6E 6F 70 71 72 73 74 75 76 77 61 62 63 64 65

66 67 68 69


GTP-U Message-2

UDP DATAGRAM

Source port: 1319

Destination port: 2152

Length: 76

Checksum: 15738 (3D7A)

data:

30 FF 00 3C 00 00 00 00 45 00 00 3C C2 2E 00 00 FD 01 6A BC C0 A8 03 3C

C0 A8 0C 49 00 00 A3 5B 16 00 9C 00 61 62 63 64 65 66 67 68 69 6A 6B 6C

6D 6E 6F 70 71 72 73 74 75 76 77 61 62 63 64 65 66 67 68 69

G-PDU

- Version number: 1 (1h)

- Protocol type: 1 (1h)

- Extension header flag: 0 (0h)

- Sequence number flag: 0 (0h)

- N-PDU number flag: 0 (0h)

- Message Type: 255 (G-PDU)

- Header Length: 60 (3ch)

- Tunnel endpoint id: 0 (00000000h)

45 00 00 3C C2 2E 00 00 FD 01 6A BC C0 A8 03 3C C0 A8 0C 49 00 00 A3 5B

16 00 9C 00 61 62 63 64 65 66 67 68 69 6A 6B 6C 6D 6E 6F 70 71 72 73 74

75 76 77 61 62 63 64 65 66 67 68 69

Transparent Iu UP

IP DATAGRAM

IP version : 4

Internet header length (in octets) : 20

Type of service :

- 000 - Routine

- normal delay (minimize delay)

- normal throughput

- normal reliability

Total length (in octets) : 60

Identification : 49710 (C22E)

Flags:

- May fragment

- Last fragment

Fragment offset (in octets) : 0

Time to live (in seconds) : 253

Next level protocol : ICMP

Checksum : 27324 (6ABC)

Source address : 192.168.3.60

Destination address : 192.168.12.73

data:

00 00 A3 5B 16 00 9C 00 61 62 63 64 65 66 67 68 69 6A 6B 6C 6D 6E 6F 70

71 72 73 74 75 76 77 61 62 63 64 65 66 67 68 69


SGSN Iu over IP Control Plane and User Plane stacks

Relay

GTP

UDP

IP

Ethernet Iu user/IP (RAN) Gn

IOCP-E/IPPU

GTP

UDP

IP

Ethernet

Ethernet

PAPU

IP

SCTP

M3UA

RANAP

SCCP

Iu control/IP (RAN)


Example Trace of the Attach procedure in Iu over IP interface Attach Request (1/3)


Example Trace of the Attach procedure in Iu over IP interface Identity Request (1/2)


Example Trace of the Attach procedure in Iu over IP interface Identity Request (2/2)


Example Trace of the Attach procedure in Iu over IP interface Identity Response (1/2)


Example Trace of the Attach procedure in Iu over IP interface Identity Response (2/2)


Example Trace of the Attach procedure in Iu over IP interface Attach Accept (1/3)


Example Trace of the Attach procedure in Iu over IP interface Attach complete (1/2)


Example Trace of the Attach procedure in Iu over IP interface Attach complete (2/2)


Example Trace of the PDP Context Activation Procedure in Iu over IP interface Activate PDP Context Request (1/2)


Example Trace of the PDP Context Activation Procedure in Iu over IP interface Activate PDP Context Request (2/2)


Example Trace of the PDP Context Activation Procedure in Iu over IP interface RAB-ASSIGNMENT REQUEST (1/2)


Example Trace of the PDP Context Activation Procedure in Iu over IP interface RAB-ASSIGNMENT REQUEST (2/2)


Example Trace of the PDP Context Activation Procedure in Iu over IP interface RAB-ASSIGNMENT RESPONSE (1/2)


Example Trace of the PDP Context Activation Procedure in Iu over IP interface RAB-ASSIGNMENT RESPONSE (2/2)


Example Trace of the PDP Context Activation Procedure in Iu over IP interface Activate PDP Context Accept (1/2)


Example Trace of the PDP Context Activation Procedure in Iu over IP interface Activate PDP Context Accept (2/2)


Iu-PS interface over ATM Control Plane



USER PART INFORMATION (MTP-3B Layer)

Service Information Octet

- SCCP

- Reserved

- spare bits: 00

Label

- DPC : 1792 (700h) (3GSGSN SPC)

- OPC : 1536 (600h) (RNC SPC)

- SLS : 9 (9h)

User Data

01 29 30 45 02 02 04 02 42 8E 04 04 43 00 06 8E 0F 5D 00 13 40 59 00 00

07 00 03 40 01 80 00 0F 40 06 00 22 F2 11 D9 03 00 37 40 01 2C 00 3A 40

08 00 22 F2 11 D9 03 D9 03 00 10 40 22 21 08 01 02 E5 40 79 07 02 05 F4

D8 F3 40 12 22 F2 11 D9 03 2C 0A 14 F3 82 33 4C 03 26 3C A0 60 17 16 00

4F 40 03 05 29 00 00 56 40 05 22 F2 11 00 01 00

Example Trace of the Attach procedure in Iu over ATM interface

Attach Request (1/10)


CR - CONNECTION REQUEST (SCCP Layer)


- 293045h

Protocol Class



- length 2 (02h)



- subsystem: RANAP

Calling Party Address

- length 4 (04h)



- point code : 1536 (600h)

- subsystem: RANAP

SCCP User Data

- length: 93 (5Dh)

- data :

00 13 40 59 00 00 07 00 03 40 01 80 00 0F 40 06 00 22 F2 11 D9 03 00 37

40 01 2C 00 3A 40 08 00 22 F2 11 D9 03 D9 03 00 10 40 22 21 08 01 02 E5

40 79 07 02 05 F4 D8 F3 40 12 22 F2 11 D9 03 2C 0A 14 F3 82 33 4C 03 26

3C A0 60 17 16 00 4F 40 03 05 29 00 00 56 40 05 22 F2 11 00 01




RANAP-PDU (RANAP Layer)

- extension flag: 0

- choice index: 00

initiatingMessage

- procedureCode: 19

- padding: 00000

- contents: 13



initiatingMessage

- padding: 000000


InitialUE-Message

- extension flag: 0

- preamble: 0

protocolIEs

- padding: 000000

- length: 00 07

- id: 3

- contents: 00 03



- padding: 000000








- id: 15

- contents: 00 0F



- padding: 000000


LAI

- preamble: 0


- padding: 0000000


- lAC: 'D903'H

- contents: D9 03

- id: 55

- contents: 00 37



- padding: 000000





RAC: '2C‘H

- contents: 2C

- id: 58

- contents: 00 3A



- padding: 000000


SAI

- preamble: 0


- padding: 0000000


- lAC: 'D903'H

- contents: D9 03

- sAC: 'D903'H

- contents: D9 03

- id: 16

- contents: 00 10



- padding: 000000


NAS-PDU: '080102E54079070205F4D8F3401222F211D9032C0A14F382334C03263CA0601716'H

- length: 21

- contents

08 01 02 E5 40 79 07 02 05 F4 D8 F3 40 12 22 F2 11 D9 03 2C 0A 14 F3 82

33 4C 03 26 3C A0 60 17 16




- id: 79

- contents: 00 4F



- padding: 000000


IuSignallingConnectionIdentifier: '000001010010100100000000'B

- contents: 05 29 00

- id: 86

- contents: 00 56



- padding: 000000


GlobalRNC-ID



- rNC-ID: 1

- contents: 00 01




ATTACH REQUEST (GPRS MM) (GSM/3G L3 Layer)

MS Network Capability

- Encryption algorithm GEA/1 available

- SM capabilities via dedicated channels supported

- SM capabilities via GPRS channels supported

- Use of default alphabet over UCS2 prefered

- Capab. of ellipsis notation and phase 2 error handling

- The ME does not support SoLSA

- Mobile station supporting R99 or later versions

- Mobile station does not support BSS packet flow procedures

- encryption algorithm GEA/2 available






Attach Type

- GPRS attach

- Follow-on request pending


- value: 7 (07h)




DRX Parameter

- Split PG Cycle value: 7

- DRX cycle length coefficient not specified by the MS

- Split pg cycle on CCCH not supported

- max. 2 sec non-DRX mode after transfer state

Mobile identity

- length: 5 (05h)

- TMSI/P-TMSI: D8F34012

Routing Area Id.



- Location Area Code: 55555 (D903h)

- Routing Area Code: 44 (2Ch)

MS Radio Access Capability

GSM 900-E Access Technology Type

- Length: 39 bits
















- HSCSD Multislot Class: 6

- GPRS Multislot Class: 6

- GPRS Ext. Dynamic Alloc. Capability not implemented









GSM 1800 Access Technology Type

- Length: 15 bits











- Spare ok

GPRS Timer

- Value: 44 sec







- SCCP

- Reserved

- spare bits: 01

Label

- DPC : 1536 (600h)

- OPC : 1792 (700h)

- SLS : 2 (2h)

User Data: 02 29 30 45 50 00 00 02 01 03 04 43 00 06 8E 00


SCCP connection establishment (1/2)


CC - CONNECTION CONFIRM (SCCP Layer)


- 293045h


- 500000h

Protocol Class



- length 4 (04h)



- point code : 1536 (600h)

- subsystem: RANAP



SCCP connection establishment (2/2)





- SCCP

- Reserved

- spare bits: 00

Label

- DPC : 1536 (600h)

- OPC : 1792 (700h)

- SLS : 2 (2h)

User Data

06 29 30 45 00 01 14 00 0F 40 10 00 00 01 00 17 40 09 50 22 12 21 00 00

00 01 F0


Common ID (1/4)


DT1 - DATA FORM 1 (SCCP Layer)


- 293045h

Segmenting/Reassembling

- no more data

- the Segment./Reas. octet : 00

SCCP User Data

- length: 20 (14h)

- data : 00 0F 40 10 00 00 01 00 17 40 09 50 22 12 21 00 00 00 01 F0


Common ID (2/4)



- extension flag: 0

- choice index: 00

initiatingMessage

- procedureCode: 15

- padding: 00000

- contents: 0F



initiatingMessage

- padding: 000000


CommonID

- extension flag: 0

- preamble: 0


Common ID (3/4)


protocolIEs

- padding: 000000

- length: 00 01

- id: 23

- contents: 00 17



- padding: 000000


PermanentNAS-UE-ID

- extension flag: 0

- iMSI: '22122100000001F0'H


- padding: 0000

- contents: 22 12 21 00 00 00 01 F0


Common ID (4/4)





- SCCP

- Reserved

- spare bits: 00

Label

- DPC : 1536 (600h)

- OPC : 1792 (700h)

- SLS : 2 (2h)

User Data

06 29 30 45 00 01 27 00 14 40 23 00 00 02 00 10 40 17 16 08 02 01 49 00

22 F2 11 D9 03 2C 19 60 51 43 18 05 F4 E3 05 57 70 00 3B 40 01 00


Attach Accept (1/5)




- 293045h


- no more data


SCCP User Data

- length: 39 (27h)

- data :

00 14 40 23 00 00 02 00 10 40 17 16 08 02 01 49 00 22 F2 11 D9 03 2C 19

60 51 43 18 05 F4 E3 05 57 70 00 3B 40 01 00


Attach Accept (2/5)



- extension flag: 0

- choice index: 00

initiatingMessage

- procedureCode: 20

- padding: 00000

- contents: 14



initiatingMessage

- padding: 000000


DirectTransfer

- extension flag: 0

preamble: 0

protocolIEs

- padding: 000000

- length: 00 02

- id: 16

- contents: 00 10



- padding: 000000



Attach Accept (3/5)


NAS-PDU: '080201490022F211D9032C196051431805F4E3055770'H

- length: 16

- contents

08 02 01 49 00 22 F2 11 D9 03 2C 19 60 51 43 18 05 F4 E3 05 57 70

- id: 59

- contents: 00 3B



- padding: 000000


SAPI: sapi-0





Attach Accept (4/5)


ATTACH ACCEPT (GPRS MM) (GSM/3G L3 Layer)

Attach Result

- GPRS only attached

Force to Standby

- not indicated

GPRS Timer

- Value: 54 min

Radio Priority

- Priority level 4

Routing Area Id.



- Location Area Code: 55555 (D903h)

- Routing Area Code: 44 (2Ch)

P-TMSI signature

- Value: 60 51 43

P-TMSI

- length: 5 (05h)

- TMSI/P-TMSI: E3055770

Example Trace of the Attach procedure in Iu over ATM interface Attach Accept (5/5)





- SCCP

- Reserved

- spare bits: 01

Label

- DPC : 1792 (700h)

- OPC : 1536 (600h)

- SLS : 9 (9h)

User Data

06 50 00 00 00 01 29 00 14 40 25 00 00 04 00 10 40 03 02 08 03 00 0F 40

06 00 22 F2 11 D9 03 00 37 40 01 2C 00 3A 40 08 00 22 F2 11 D9 03 D9 03


Attach Complete (1/6)




- 500000h


- no more data


SCCP User Data

- length: 41 (29h)

- data :

00 14 40 25 00 00 04 00 10 40 03 02 08 03 00 0F 40 06 00 22 F2 11 D9 03

00 37 40 01 2C 00 3A 40 08 00 22 F2 11 D9 03 D9 03





- extension flag: 0

- choice index: 00

initiatingMessage

- procedureCode: 20

- padding: 00000

- contents: 14



initiatingMessage

- padding: 000000


DirectTransfer

- extension flag: 0

- preamble: 0

protocolIEs

- padding: 000000

- length: 00 04

- id: 16

- contents: 00 10



- padding: 000000





NAS-PDU: '0803'H

- length: 02

- contents: 08 03

- id: 15

- contents: 00 0F



- padding: 000000


LAI

- preamble: 0


- padding: 0000000


- lAC: 'D903'H

- contents: D9 03

- id: 55

- contents: 00 37



- padding: 000000


Example Trace of the Attach procedure in Iu over ATM interface Attach Complete (4/6)


RAC: '2C'H

- contents: 2C

- id: 58

- contents: 00 3A



- padding: 000000


SAI

- preamble: 0


- padding: 0000000


- lAC: 'D903'H

- contents: D9 03

- sAC: 'D903'H

- contents: D9 03




ATTACH COMPLETE (GPRS MM) (GSM/3G L3 Layer)







- SCCP

- Reserved

- spare bits: 01

Label

- DPC : 1792 (700h)

- OPC : 1536 (600h)

- SLS : 9 (9h)

User Data

06 50 00 00 00 01 6D 00 14 40 69 00 00 04 00 10 40 47 46 0A 41 05 03 0B

00 00 1F 00 00 00 00 00 00 00 00 02 01 21 28 09 08 69 6E 74 65 72 6E 65

74 27 26 80 C0 23 0F 01 11 00 0F 09 4F 36 34 30 30 30 35 32 5C 00 80 21

10 01 05 00 10 81 06 00 00 00 00 83 06 00 00 00 00 00 0F 40 06 00 22 F2

11 D9 03 00 37 40 01 2C 00 3A 40 08 00 22 F2 11 D9 03 D9 03

Example Trace of the PDP Context Activation Procedure in Iu over ATM interface

Activate PDP Context Request (1/7)




- 500000h


- no more data


SCCP User Data

- length: 109 (6Dh)

- data :

00 14 40 69 00 00 04 00 10 40 47 46 0A 41 05 03 0B 00 00 1F 00 00 00 00

00 00 00 00 02 01 21 28 09 08 69 6E 74 65 72 6E 65 74 27 26 80 C0 23 0F

01 11 00 0F 09 4F 36 34 30 30 30 35 32 5C 00 80 21 10 01 05 00 10 81 06

00 00 00 00 83 06 00 00 00 00 00 0F 40 06 00 22 F2 11 D9 03 00 37 40 01

2C 00 3A 40 08 00 22 F2 11 D9 03 D9 03

Example Trace of the PDP Context Activation Procedure in Iu

over ATM interface Activate PDP Context Request (2/7)



- extension flag: 0

- choice index: 00

initiatingMessage

- procedureCode: 20

- padding: 00000

- contents: 14



initiatingMessage

- padding: 000000


DirectTransfer

- extension flag: 0

- preamble: 0

protocolIEs

- padding: 000000

- length: 00 04

- id: 16

- contents: 00 10



- padding: 000000





NAS-PDU: '0A4105030B00001F0000000000000000020121280908696E7465726E6574272680C0230F0111000F094

F363430303035325C0080211001050010810600000000830600000000'H

- length: 46

- contents

0A 41 05 03 0B 00 00 1F 00 00 00 00 00 00 00 00 02 01 21 28 09 08 69 6E

74 65 72 6E 65 74 27 26 80 C0 23 0F 01 11 00 0F 09 4F 36 34 30 30 30 35

32 5C 00 80 21 10 01 05 00 10 81 06 00 00 00 00 83 06 00 00 00 00

- id: 15

- contents: 00 0F



- padding: 000000


LAI

- preamble: 0


- padding: 0000000


- lAC: 'D903'H

- contents: D9 03

- id: 55

- contents: 00 37



- padding: 000000





RAC: '2C'H

- contents: 2C

- id: 58

- contents: 00 3A



- padding: 000000


SAI

- preamble: 0


- padding: 0000000


- lAC: 'D903'H

- contents: D9 03

- sAC: 'D903'H

- contents: D9 03




ACT. PDP CONTEXT REQUEST (GPRS SM) (GSM/3G L3 Layer)

Network Serv. Access Point Id

- NSAPI 5

LLC Serv. Access point Id

- SAPI 3

Quality of Service

- length: 11 (0Bh)

- Reliab. class: Subscribed (MS only)

- Delay class: Subscribed

- Precedence class: Subscribed

- Peak throughput: Subscribed


- Traffic class: Subscribed

- Delivery order: Subscribed

- Delivery of erroneous SDUs: Subscribed

- Maximum SDU size: Subscribed maximum SDU size

- Maximum bit rate for uplink: Subscribed (MS only)

- Maximum bit rate for downlink: Subscribed (MS only)

- Residual BER: Subscribed

- SDU error ratio: Subscribed









- Length: 2 (02h)

- Dynamic PDP addressing is applied



Access Point Name

- length : 9 (09h)

- value (hex) : 08 69 6E 74 65 72 6E

65 74


- length: 38 (26h)


Password Authentic. Protocol (PAP)

Contents: 01 11 00 0F 09 4F 36 34 30 30 30 35 32 5C 00


Contents: 01 05 00 10 81 06 00 00 00 00 83 06 00 00 00 00







- SCCP

- Reserved

- spare bits: 00

Label

- DPC : 1536 (600h)

- OPC : 1792 (700h)

- SLS : 2 (2h)

User Data

06 29 30 45 00 01 34 00 00 00 30 00 00 01 00 36 40 29 00 00 01 00 35 00

1D 3C 0A 14 C2 05 DB FF 80 2E F0 08 06 34 04 90 00 01 03 E0 C0 01 01 03

00 12 00 00 00 20 40 03 60 99 C0

RAB-ASSIGNMENT REQUEST (1/8)


over ATM interface




- 293045h


- no more data


SCCP User Data

- length: 52 (34h)

- data :

00 00 00 30 00 00 01 00 36 40 29 00 00 01 00 35 00 1D 3C 0A 14 C2 05 DB

FF 80 2E F0 08 06 34 04 90 00 01 03 E0 C0 01 01 03 00 12 00 00 00 20 40

03 60 99 C0


over ATM interface




- extension flag: 0

- choice index: 00

initiatingMessage

- procedureCode: 0

- padding: 00000

- contents: 00



initiatingMessage

- padding: 000000


RAB-AssignmentRequest

- extension flag: 0

- preamble: 0

protocolIEs

- padding: 000000

- length: 00 01

- id: 54

- contents: 00 36



- padding: 000000


Example Trace of the PDP Context Activation Procedure in Iu over ATM

interface RAB-ASSIGNMENT REQUEST (3/8)


RAB-SetupOrModifyList

- length: 00

- length: 00 01

- id: 53

- contents: 00 35

- firstCriticality: reject


- padding: 000000

- opentype length: 1D

firstValue

- extension flag: 0

- preamble: 011110

- rAB-ID: '00000101'B


rAB-Parameters

- extension flag: 0

- preamble: 0001010

- trafficClass: background



- rAB-AsymmetryIndicator: symmetric-bidirectional



Example Trace of the PDP Context Activation Procedure in Iu over ATM interface RAB-ASSIGNMENT REQUEST (4/8)


maxBitrate


- MaxBitrate: 384000


- contents: 05 DB FF

- deliveryOrder: delivery-order-not-requested


- maxSDU-Size: 12016

- padding: 0000000

- contents: 2E F0

sDU-Parameters


- extension flag: 0

- preamble: 100

sDU-ErrorRatio

- preamble: 0

- mantissa: 1


- exponent: 4


residualBitErrorRatio

- preamble: 0

- mantissa: 4


- exponent: 3





- deliveryOfErroneousSDU: yes


allocationOrRetentionPriority

- extension flag: 0

- preamble: 0

- priorityLevel: 2


- pre-emptionCapability: shall-not-trigger-pre-emption


- pre-emptionVulnerability: pre-emptable


- queuingAllowed: queueing-not-allowed


- relocationRequirement: none



userPlaneInformation

- extension flag: 0

- preamble: 0

- userPlaneMode: transparent-mode



- uP-ModeVersions: '0000000000000001'B

- contents: 00 01




transportLayerInformation

- extension flag: 0

- preamble: 0




- padding: 00000

- contents: C0 01 01 03


- extension flag: 0

- choice index: 0

- gTP-TEI: '12000000'H

- padding: 000000

- contents: 12 00 00 00

- service-Handover: handover-to-GSM-should-not-be-performed







- secondCriticality: ignore


- padding: 000000


secondValue

- extension flag: 0

- preamble: 1100000

pDP-TypeInformation


- PDP-Type: ipv4



- PDP-Type: ipv4



- dataVolumeReportingIndication: do-not-report









- SCCP

- Reserved

- spare bits: 01

Label

- DPC : 1792 (700h)

- OPC : 1536 (600h)

- SLS : 9 (9h)

User Data

06 50 00 00 00 01 1E 60 00 00 1A 00 00 01 00 34 40 13 00 00 01 00 33 40

0C 60 28 7C 0A 14 14 03 00 00 00 00 00


RAB-ASSIGNMENT RESPONSE (1/4)




- 500000h


- no more data


SCCP User Data

- length: 30 (1Eh)

- data :

60 00 00 1A 00 00 01 00 34 40 13 00 00 01 00 33 40 0C 60 28 7C 0A 14 14

03 00 00 00 00 00





- extension flag: 0

- choice index: 11

outcome

- procedureCode: 0

- padding: 00000

- contents: 00



outcome

- padding: 000000

- opentype length: 1A

RAB-AssignmentResponse

- extension flag: 0

- preamble: 0

protocolIEs

- padding: 000000

- length: 00 01

- id: 52

- contents: 00 34



- padding: 000000





RAB-SetupOrModifiedList

- length: 00

- length: 00 01

- id: 51

- contents: 00 33



- padding: 000000

- opentype length: 0C

RAB-SetupOrModifiedItem

- extension flag: 0

- preamble: 1100

- rAB-ID: '00000101'B





- padding: 00

- contents: 0A 14 14 03


- extension flag: 0

- choice index: 0

- gTP-TEI: '00000000'H

- padding: 000000

- contents: 00 00 00 00







- SCCP

- Reserved

- spare bits: 00

Label

- DPC : 1536 (600h)

- OPC : 1792 (700h)

- SLS : 2 (2h)

User Data

06 29 30 45 00 01 3F 00 14 40 3B 00 00 02 00 10 40 2F 2E 8A 42 03 0B 23

62 1F 92 97 68 68 44 00 00 00 02 2B 06 01 21 0A 62 02 0E 27 14 80 80 21

10 04 05 00 10 81 06 00 00 00 00 83 06 00 00 00 00 00 3B 40 01 00

Activate PDP Context Accept (1/6)





- 293045h


- no more data


SCCP User Data

- length: 63 (3Fh)

- data :

00 14 40 3B 00 00 02 00 10 40 2F 2E 8A 42 03 0B 23 62 1F 92 97 68 68 44

00 00 00 02 2B 06 01 21 0A 62 02 0E 27 14 80 80 21 10 04 05 00 10 81 06

00 00 00 00 83 06 00 00 00 00 00 3B 40 01 00





- extension flag: 0

- choice index: 00

initiatingMessage

- procedureCode: 20

- padding: 00000

- contents: 14



initiatingMessage

- padding: 000000

- opentype length: 3B

DirectTransfer

- extension flag: 0

- preamble: 0

protocolIEs

- padding: 000000

- length: 00 02

- id: 16

- contents: 00 10



- padding: 000000

- opentype length: 2F




NAS-PDU:

'8A42030B23621F9297686844000000022B0601210A62020E27148080211004050010810600

000000830

600000000'H

- length: 2E

- contents

8A 42 03 0B 23 62 1F 92 97 68 68 44 00 00 00 02 2B 06 01 21 0A 62 02 0E

27 14 80 80 21 10 04 05 00 10 81 06 00 00 00 00 83 06 00 00 00 00

- id: 59

- contents: 00 3B



- padding: 000000


SAPI: sapi-0







ACT. PDP CONTEXT ACCEPT (GPRS SM) (GSM/3G L3 Layer)

LLC Serv. Access point Id

- SAPI 3

Quality of Service

- length: 11 (0Bh)

- Reliab. class: Unack. GTP and LLC Ack. RLC Protected data

- Delay class: Delay class 4 (best effort)

- Precedence class: Normal priority

- Peak throughput: Up to 32 000 octet/s


- Traffic class: Background class

- Delivery order: Without delivery order ('no')

- Delivery of erroneous SDUs: delivered

- Maximum SDU size: 1502 Octets

- Maximum bit rate for uplink: 384 kbps

- Maximum bit rate for downlink: 384 kbps

- Residual BER: 4*10-3

- SDU error ratio: 1*10-4








Radio Priority

- Priority level 2


- Length: 6 (06h)



- Address: 10.98.2.14


- length: 20 (14h)



Contents: 04 05 00 10 81 06 00 00 00 00 83 06 00 00 00 00



02a Iu-PS Interface

Documents

Transcript of 02a Iu-PS Interface