Date post: | 28-Jan-2016 |
Category: |
Documents |
Upload: | nizar-touaiti |
View: | 21 times |
Download: | 1 times |
1 © Nokia Siemens Networks CN3203EN01GLN00
PCNSIG
Iu-PS interface
2 © Nokia Siemens Networks CN3203EN01GLN00
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
3 © Nokia Siemens Networks CN3203EN01GLN00
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
4 © Nokia Siemens Networks CN3203EN01GLN00
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
5 © Nokia Siemens Networks CN3203EN01GLN00
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
6 © Nokia Siemens Networks CN3203EN01GLN00
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
Connection - oriented
Services
Connection - oriented
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)
7 © Nokia Siemens Networks CN3203EN01GLN00
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.
8 © Nokia Siemens Networks CN3203EN01GLN00
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
9 © Nokia Siemens Networks CN3203EN01GLN00
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)
- no global title present
- routing based on SSN and MTP routing label
- 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
10 © Nokia Siemens Networks CN3203EN01GLN00
Example of SCCP Messages 2
CC - CONNECTION CONFIRM
Destination Local Reference
- 61F144h
Source Local Reference
- 040000h
Protocol Class
- 2h, connection oriented
Called Party Address
- length 4 (04h)
- no global title present
- routing based on SSN and MTP routing label
- point code : 4144 (1030h)
- subsystem: RANAP
End of Optional Parameters
11 © Nokia Siemens Networks CN3203EN01GLN00
Example of SCCP Messages 3
RLSD - RELEASED
Destination Local Reference
- 61F144h
Source Local Reference
- 040000h
Release Cause
- end user originated
RLC - RELEASE COMPLETE
Destination Local Reference
- 040000h
Source Local Reference
- 61F144h
12 © Nokia Siemens Networks CN3203EN01GLN00
3G SGSN-UE Control Plane
UE Uu RNC Iu-PS SGSN
13 © Nokia Siemens Networks CN3203EN01GLN00
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.
14 © Nokia Siemens Networks CN3203EN01GLN00
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.
15 © Nokia Siemens Networks CN3203EN01GLN00
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.
16 © Nokia Siemens Networks CN3203EN01GLN00
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
- criticality: ignore
- contents (in bits): 01
- padding: 000000
- opentype length
CN-DomainIndicator: ps-domain
-contents (in bits): 1
- trailing bits: 0000000
- id: 15
- contents
- criticality: ignore
- contents (in bits): 01
- padding: 000000
- opentype length
LAI
- preamble: 0
- pLMNidentity: '32F403'H
- padding: 0000000
- contents
- lAC: '03EF'H
- contents
- id: 55
- contents
- criticality: ignore
- contents (in bits): 01
- padding: 000000
- opentype length
RAC: '01'H
- contents
- id: 58
- contents
- criticality: ignore
- contents (in bits): 01
- padding: 000000
- opentype length SAI
- preamble: 0
- pLMNidentity: '32F403'H
- padding: 0000000
- contents
- lAC: '03EF'H
- contents
- SAC: 'EA62'H
- contents
- id: 16
- contents
- criticality: ignore
- contents (in bits): 01
- padding: 000000
- opentype length
NAS-PDU: '080C1605F42A00035B32022000'H
- length
- contents
- id: 79
- contents
- criticality: ignore
- contents (in bits): 01
- padding: 000000
- opentype length
IuSignallingConnectionIdentifier:
'000000011111011000000000'B
- contents
- id: 86
- contents
- criticality: ignore
- contents (in bits): 01
- padding: 000000
- opentype length
GlobalRNC-ID
- pLMNidentity: '32F403'H
- contents
-RNC-ID: 3007
- contents
17 © Nokia Siemens Networks CN3203EN01GLN00
CN originated Direct Transfer Message
The purpose of the Direct Transfer procedure is to carry UE-CN signalling messages
over the Iu interface.
18 © Nokia Siemens Networks CN3203EN01GLN00
Example of CN originated Direct Transfer Message
DIRECT TRANSFER RANAP-PDU
- extension flag: 0
- choice index: 00
initiatingMessage
- procedureCode: 20
- padding: 00000
- contents
- criticality: ignore
- contents (in bits): 01
initiatingMessage
- padding: 000000
- opentype length
DirectTransfer
- extension flag: 0
- preamble: 0
protocolIEs
- padding: 000000
- length
- id: 16
- contents
-criticality: ignore
- contents (in bits): 01
- padding: 000000
- opentype length
NAS-PDU: '8A47'H
- length
- contents
- id: 59
- contents
- criticality: ignore
- contents (in bits): 01
- padding: 000000
- opentype length
SAPI: sapi-0
- extension range: 0
- contents (in bits): 0
- trailing bits: 000000
19 © Nokia Siemens Networks CN3203EN01GLN00
UTRAN originated Direct Transfer
The purpose of the Direct Transfer procedure is to carry UE-CN signalling messages
over the Iu interface.
20 © Nokia Siemens Networks CN3203EN01GLN00
Example of UTRAN originated Direct Transfer Message
DIRECT TRANSFER RANAP-PDU
- extension flag: 0
- choice index: 00
initiatingMessage
- procedureCode: 20
- padding: 00000
- contents
- criticality: ignore
- contents (in bits): 01
initiatingMessage
- padding: 000000
- opentype length
DirectTransfer
- extension flag: 0
- preamble: 0
protocolIEs
- padding: 000000
- length
- id: 16
- contents
- criticality: ignore
- contents (in bits): 01
- padding: 000000
- opentype length
NAS-PDU: '0A4624'H
- length
- contents
- id: 15
- contents
- criticality: ignore
- contents (in bits): 01
- padding: 000000
- opentype length
LAI
- preamble: 0
- pLMNidentity: '32F403'H
- padding: 0000000
- contents
- lAC: '03EF'H
- contents
- id: 55
- contents
- criticality: ignore
- contents (in bits): 01
- padding: 000000
- opentype length
RAC: '01'H
- contents
- id: 58
- contents
- criticality: ignore
- contents (in bits): 01
- padding: 000000
- opentype length
SAI
- preamble: 0
- pLMNidentity: '32F403'H
- padding: 0000000
- contents
- lAC: '03EF'H
- contents
- SAC: 'EA62'H
- contents
21 © Nokia Siemens Networks CN3203EN01GLN00
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.
22 © Nokia Siemens Networks CN3203EN01GLN00
Example of RAB Assignment Request Message RAB-ASSIGNMENT REQUEST RANAP-PDU
- extension flag: 0
- choice index: 00
initiatingMessage
- procedureCode: 0
- padding: 00000
- contents
- criticality: ignore
- contents (in bits): 01
initiatingMessage
- padding: 000000
- opentype length
RAB-AssignmentRequest
- extension flag: 0
- preamble: 0
protocolIEs
- padding: 000000
- length
- id: 54
- contents
- criticality: ignore
- contents (in bits): 01
- padding: 000000
- opentype length
RAB-SetupOrModifyList
- length
- length
- id: 53
- contents
- firstCriticality: reject
- contents (in bits): 00
- padding: 000000
- opentype length
firstValue
- extension flag: 0
- preamble: 111100
- rAB-ID: '00000101'B
- contents (in bits): 00000101
- nAS-SynchronisationIndicator: '1111'B
-contents (in bits): 1111 rAB-Parameters
- extension flag: 0
- preamble: 0011010
- trafficClass: interactive
- extension range: 0
- contents (in bits): 10 - rAB-AsymmetryIndicator: symmetric-bidirectional
- extension range: 0
- contents (in bits): 00
maxBitrate
- length (in bits): 0
- MaxBitrate: 64000
- length (in bits): 01
- padding: 0000
- contents
- deliveryOrder: delivery-order-not-requested
- contents (in bits): 1
- maxSDU-Size: 12000
- padding: 0000000
- contents
sDU-Parameters
- length (in bits): 000
- extension flag: 0
- preamble: 100
sDU-ErrorRatio
- preamble: 0
- mantissa: 1
- contents (in bits): 0000
- exponent: 4
-contents (in bits): 011 residualBitErrorRatio
- preamble: 0
- mantissa: 1
- contents (in bits): 0000
- exponent: 5
- contents (in bits): 100
- deliveryOfErroneousSDU: no
- contents (in bits): 01
- trafficHandlingPriority: 3
-contents (in bits): 0011 allocationOrRetentionPriority
- extension flag: 0
- preamble: 0
- priorityLevel: 3
- contents (in bits): 0011
- pre-emptionCapability: shall-not-trigger-pre-emption
- contents (in bits): 0
- pre-emptionVulnerability: not-pre-emptable
- contents (in bits): 0
- queuingAllowed: queueing-allowed
- contents (in bits): 1
- relocationRequirement: none
- extension range: 0
- contents (in bits): 1
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)
- extension range: 0
- contents (in bits): 0
- uP-ModeVersions: '0000000000000001'B
- contents (in bits): 00000000 0000 0001
transportLayerInformation
- extension flag: 0
- preamble: 0
- transportLayerAddress: '10101100000100100110001011000110'- extension range: 0
- length (in bits): 00011111
- 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
- contents (in bits): 01
- padding: 000000
- opentype length
secondValue
- extension flag: 0
- preamble: 1100000
pDP-TypeInformation
- length (in bits): 0
- PDP-Type: ipv4
- extension range: 0
- contents (in bits): 011
- dataVolumeReportingIndication: do-report
- contents (in bits): 0
- trailing bits: 00
23 © Nokia Siemens Networks CN3203EN01GLN00
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
- contents (in bits): 00
outcome
- padding: 000000
- opentype length
RAB-AssignmentResponse
- extension flag: 0
- preamble: 0
protocolIEs
- padding: 000000
- length
- id: 52
- contents
- criticality: ignore
- contents (in bits): 01
- padding: 000000
- opentype length
RAB-SetupOrModifiedList
- length
- length
- id: 51
- contents
- criticality: ignore
- contents (in bits): 01
- padding: 000000
- opentype length
RAB-SetupOrModifiedItem
- extension flag: 0
- preamble: 1100
- rAB-ID: '00000101'B
- contents (in bits): 00000101
- transportLayerAddress: '10101100000100100110000110000011'B
- extension range: 0
- length (in bits): 00011111
- padding: 00
- contents
iuTransportAssociation
- extension flag: 0
- choice index: 0
- gTP-TEI: '00000000'H (TEID in RNC)
- padding: 000000
- contents
24 © Nokia Siemens Networks CN3203EN01GLN00
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‘).
25 © Nokia Siemens Networks CN3203EN01GLN00
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
- criticality: ignore
- contents (in bits): 01
- padding: 000000
- opentype length: 02
Cause
- extension flag: 0
- choice index: 000
- radioNetwork: radio-connection-with-UE-Lost
- contents (in bits): 101101
26 © Nokia Siemens Networks CN3203EN01GLN00
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.
27 © Nokia Siemens Networks CN3203EN01GLN00
Examples of Iu Release Procedure Messages
IU-RELEASE COMMAND RANAP-PDU
- extension flag: 0
- choice index: 00
initiatingMessage
- procedureCode: 1
- padding: 00000
- contents
- criticality: reject
- contents (in bits): 00
initiatingMessage
- padding: 000000
- opentype length
Iu-ReleaseCommand
- extension flag: 0
- preamble: 0
protocolIEs
- padding: 000000
- length
- id: 4
- contents
- criticality: ignore
- contents (in bits): 01
- 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
- criticality: reject
- contents (in bits): 00
successfulOutcome
- padding: 000000
- opentype length
Iu-ReleaseComplete
- extension flag: 0
- preamble: 0
protocolIEs
- padding: 000000
- length
- id: 31
- contents
- criticality: ignore
- contents (in bits): 01
- padding: 000000
- opentype length
RAB-DataVolumeReportList
- length
- length
- id: 30
- contents
- criticality: ignore
- contents (in bits): 01
- padding: 000000
- opentype length
RAB-DataVolumeReportItem
- extension flag: 0
- preamble: 10
- rAB-ID: '00000101'B
- contents (in bits): 00000101
dl-UnsuccessfullyTransmittedDataVolume
- length (in bits): 0
- extension flag: 0
- preamble: 00
- dl-UnsuccessfullyTransmittedDataVolume: 0
- length (in bits): 00
- padding: 0000000
- contents
28 © Nokia Siemens Networks CN3203EN01GLN00
Paging procedure
The purpose of the Paging procedure is to enable the CN to request the UTRAN to
contact the UE
29 © Nokia Siemens Networks CN3203EN01GLN00
Example of Paging procedure Paging - extension flag: 0
- preamble: 0
protocolIEs
- padding: 000000
- length: 00 06
- id: 3
- contents: 00 03
- criticality: ignore
- contents (in bits): 01
- padding: 000000
- opentype length: 01
CN-DomainIndicator: ps-domain
- contents (in bits): 1
- trailing bits: 0000000
- 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
- id: 64
- contents: 00 40
- criticality: ignore
- contents (in bits): 01
- padding: 000000
- opentype length: 05
TemporaryUE-ID
- extension flag: 0
- choice index: 1
- p-TMSI: '09C24B3C'H
- padding: 000000
- contents: 09 C2 4B 3C
- id: 21
- contents: 00 15
- criticality: ignore
- contents (in bits): 01
- padding: 000000
- opentype length: 07
PagingAreaID
- extension flag: 0
- choice index: 1
rAI
- extension flag: 0
- preamble: 0
lAI
- preamble: 0
- pLMNidentity: '62F290'H
- padding: 000
- contents: 62 F2 90
- lAC: '00C9'H
- contents: 00 C9
- rAC: '17'H
- contents: 17
- id: 22
- contents: 00 16
- criticality: ignore
- contents (in bits): 01
- padding: 000000
- opentype length: 01
PagingCause: terminating-background-call
- extension range: 0
- contents (in bits): 011
- trailing bits: 0000
- id: 17
- contents: 00 11
- criticality: ignore
- contents (in bits): 01
- padding: 000000
- opentype length: 01
NonSearchingIndication: searching
- contents (in bits): 1
- trailing bits: 0000000
30 © Nokia Siemens Networks CN3203EN01GLN00
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.
31 © Nokia Siemens Networks CN3203EN01GLN00
Example of Common ID Message
COMMONID
RANAP-PDU
- extension flag: 0
- choice index: 00
initiatingMessage
- procedureCode: 15
- padding: 00000
- contents
- criticality: ignore
- contents (in bits): 01
initiatingMessage
- padding: 000000
- opentype length
CommonID
- extension flag: 0
- preamble: 0
protocolIEs
- padding: 000000
- length
- id: 23
- contents
- criticality: ignore
- contents (in bits): 01
- padding: 000000
- opentype length
PermanentNAS-UE-ID
- extension flag: 0
- iMSI: '32349030037865F9'H
- length (in bits): 101
- padding: 0000
- contents
32 © Nokia Siemens Networks CN3203EN01GLN00
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.
33 © Nokia Siemens Networks CN3203EN01GLN00
Example of Security Mode Command Message
SECURITY MODE COMMAND RANAP-PDU
- extension flag: 0
- choice index: 00
initiatingMessage
- procedureCode: 6
- padding: 00000
- contents
- criticality: reject
- contents (in bits): 00
initiatingMessage
- padding: 000000
- opentype length
SecurityModeCommand
- extension flag: 0
- preamble: 0
protocolIEs
- padding: 000000
- length
- id: 12
- contents
- criticality: reject
- contents (in bits): 00
- padding: 000000
- opentype length
IntegrityProtectionInformation
- preamble: 0
permittedAlgorithms
- length (in bits): 0000
- IntegrityProtectionAlgorithm: standard-UMTS-integrity-algorithm--
contents (in bits): 0000
- key:
'01100010111111100000110100110110100000111010111010100101001101101110
000101010000101
010000000000001100010111111100000110100110110'B
- padding: 0000000
- contents
- id: 11
- contents
- criticality: ignore
- contents (in bits): 01
- padding: 000000
- opentype length
EncryptionInformation
- preamble: 0
permittedAlgorithms
- length (in bits): 0000
- EncryptionAlgorithm: no-encryption
- contents (in bits): 0000
- key:
'10000011101011101010010100110110111000010101000010101000000000001000
001110101110101
001010011011011100001010100001010100000000000'B
- padding: 0000000
- contents
- id: 75
- contents
- criticality: reject
- contents (in bits): 00
- padding: 000000
- opentype length
KeyStatus: old
- extension range: 0
- contents (in bits): 0
- trailing bits: 000000
34 © Nokia Siemens Networks CN3203EN01GLN00
Example of Security Mode Complete Message
SECURITY MODE COMPLETE RANAP-PDU
- extension flag: 0
- choice index: 01
successfulOutcome
- procedureCode: 6
- padding: 00000
- contents
- criticality: reject
- contents (in bits): 00
successfulOutcome
- padding: 000000
- opentype length
SecurityModeComplete
- extension flag: 0
- preamble: 0
protocolIEs
- padding: 000000
- length
- id: 6
- contents
- criticality: reject
- contents (in bits): 00
- padding: 000000
- opentype length
ChosenIntegrityProtectionAlgorithm: standard-UMTS-integrity-algorithm-UIA1
- contents (in bits): 0000
- trailing bits: 0000
- id: 5
- contents
- criticality: ignore
- contents (in bits): 01
- padding: 000000
- opentype length
ChosenEncryptionAlgorithm: no-encryption
- contents (in bits): 0000
- trailing bits: 0000
35 © Nokia Siemens Networks CN3203EN01GLN00
Relocation Preparation (step 1)
36 © Nokia Siemens Networks CN3203EN01GLN00
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.
37 © Nokia Siemens Networks CN3203EN01GLN00
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.
38 © Nokia Siemens Networks CN3203EN01GLN00
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).
39 © Nokia Siemens Networks CN3203EN01GLN00
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).
40 © Nokia Siemens Networks CN3203EN01GLN00
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.
41 © Nokia Siemens Networks CN3203EN01GLN00
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.
42 © Nokia Siemens Networks CN3203EN01GLN00
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.
43 © Nokia Siemens Networks CN3203EN01GLN00
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.
44 © Nokia Siemens Networks CN3203EN01GLN00
L3-SMM Signalling
UE Uu RNC Iu-PS SGSN
45 © Nokia Siemens Networks CN3203EN01GLN00
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).
46 © Nokia Siemens Networks CN3203EN01GLN00
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
47 © Nokia Siemens Networks CN3203EN01GLN00
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
- encryption algorithm GEA/3 not available
- encryption algorithm GEA/4 not available
- encryption algorithm GEA/5 not available
- encryption algorithm GEA/6 not available
- encryption algorithm GEA/7 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/2 available
- Encrypt. algorithm A5/3 not available
- Encrypt. algorithm A5/4 not available
- Encrypt. algorithm A5/5 not available
- Encrypt. algorithm A5/6 not available
- Encrypt. algorithm A5/7 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)
- Controlled early Classmark Sending implemented
- PS capability not present
- VGCS capability and notifications not wanted
- VBS capability and notifications not wanted
- COMPACT Interference Meas. Capab. is not implemented
- The ME is Release '98 onwards
- UMTS FDD supported
- UMTS TDD not supported
- CDMA2000 not supported
- Spare ok
P-TMSI signature (authentication value)
- Value: 63 92 B6
GPRS Timer (Ready timer in mobile phone)
- Value: 44 sec
48 © Nokia Siemens Networks CN3203EN01GLN00
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
49 © Nokia Siemens Networks CN3203EN01GLN00
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
50 © Nokia Siemens Networks CN3203EN01GLN00
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.
- Mobile Country Code: 234
- Mobile Network Code: 20
- 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
51 © Nokia Siemens Networks CN3203EN01GLN00
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)
52 © Nokia Siemens Networks CN3203EN01GLN00
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
53 © Nokia Siemens Networks CN3203EN01GLN00
Example of Service Request Message
SERVICE REQUEST (GPRS MM)
- Skip Indicator: 00h
GPRS Ciphering Key Seq. Nr
- value: 0 (00h)
Signalling
P-TMSI
- length: 5 (05h)
- TMSI/P-TMSI: F0E2E797
PDP context status
- length: 2
- NSAPI(5) context is PDP-INACTIVE
- NSAPI(6) context is PDP-INACTIVE
- NSAPI(7) context is PDP-INACTIVE
- NSAPI(8) context is PDP-INACTIVE
- NSAPI(9) context is PDP-INACTIVE
- NSAPI(10) context is PDP-INACTIVE
- NSAPI(11) context is PDP-INACTIVE
- NSAPI(12) context is PDP-INACTIVE
- NSAPI(13) context is PDP-INACTIVE
- NSAPI(14) context is PDP-INACTIVE
- NSAPI(15) context is PDP-INACTIVE
54 © Nokia Siemens Networks CN3203EN01GLN00
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)
55 © Nokia Siemens Networks CN3203EN01GLN00
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
56 © Nokia Siemens Networks CN3203EN01GLN00
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
57 © Nokia Siemens Networks CN3203EN01GLN00
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
- Mean throughput: Best effort
- 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
- Transfer delay: Subscribed (MS only)
- Traffic handling priority: level 2
- Guaranteed bit rate for uplink: Subscribed (MS only)
- Guaranteed bit rate for downlink: Subscribed (MS only)
Radio Priority
- Priority level 4
Packet Data Protocol Address
- Length: 6 (06h)
- PDP type organisation: IETF allocated address
- PDP type number: IPv4
- Address: 10.1.1.133
Protocol Conf. Options
- length: 20 (14h)
- Configuration protocol: IP PDP type
Internet Protocol Control Protocol (IPCP)
Contents: 03 05 00 10 81 06 7F 00 00 01 83 06 7F 5E 00 00 01
58 © Nokia Siemens Networks CN3203EN01GLN00
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
59 © Nokia Siemens Networks CN3203EN01GLN00
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
60 © Nokia Siemens Networks CN3203EN01GLN00
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
61 © Nokia Siemens Networks CN3203EN01GLN00
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
62 © Nokia Siemens Networks CN3203EN01GLN00
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
63 © Nokia Siemens Networks CN3203EN01GLN00
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
64 © Nokia Siemens Networks CN3203EN01GLN00
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)
65 © Nokia Siemens Networks CN3203EN01GLN00
Example Trace of the Attach procedure in Iu over IP interface Attach Request (1/3)
66 © Nokia Siemens Networks CN3203EN01GLN00
Example Trace of the Attach procedure in Iu over IP interface Attach Request (2/3)
67 © Nokia Siemens Networks CN3203EN01GLN00
Example Trace of the Attach procedure in Iu over IP interface Attach Request (3/3)
68 © Nokia Siemens Networks CN3203EN01GLN00
Example Trace of the Attach procedure in Iu over IP interface Identity Request (1/2)
69 © Nokia Siemens Networks CN3203EN01GLN00
Example Trace of the Attach procedure in Iu over IP interface Identity Request (2/2)
70 © Nokia Siemens Networks CN3203EN01GLN00
Example Trace of the Attach procedure in Iu over IP interface Identity Response (1/2)
71 © Nokia Siemens Networks CN3203EN01GLN00
Example Trace of the Attach procedure in Iu over IP interface Identity Response (2/2)
72 © Nokia Siemens Networks CN3203EN01GLN00
Example Trace of the Attach procedure in Iu over IP interface Attach Accept (1/3)
73 © Nokia Siemens Networks CN3203EN01GLN00
Example Trace of the Attach procedure in Iu over IP interface Attach Accept (2/3)
74 © Nokia Siemens Networks CN3203EN01GLN00
Example Trace of the Attach procedure in Iu over IP interface Attach Accept (3/3)
75 © Nokia Siemens Networks CN3203EN01GLN00
Example Trace of the Attach procedure in Iu over IP interface Attach complete (1/2)
76 © Nokia Siemens Networks CN3203EN01GLN00
Example Trace of the Attach procedure in Iu over IP interface Attach complete (2/2)
77 © Nokia Siemens Networks CN3203EN01GLN00
Example Trace of the PDP Context Activation Procedure in Iu over IP interface Activate PDP Context Request (1/2)
78 © Nokia Siemens Networks CN3203EN01GLN00
Example Trace of the PDP Context Activation Procedure in Iu over IP interface Activate PDP Context Request (2/2)
79 © Nokia Siemens Networks CN3203EN01GLN00
Example Trace of the PDP Context Activation Procedure in Iu over IP interface RAB-ASSIGNMENT REQUEST (1/2)
80 © Nokia Siemens Networks CN3203EN01GLN00
Example Trace of the PDP Context Activation Procedure in Iu over IP interface RAB-ASSIGNMENT REQUEST (2/2)
81 © Nokia Siemens Networks CN3203EN01GLN00
Example Trace of the PDP Context Activation Procedure in Iu over IP interface RAB-ASSIGNMENT RESPONSE (1/2)
82 © Nokia Siemens Networks CN3203EN01GLN00
Example Trace of the PDP Context Activation Procedure in Iu over IP interface RAB-ASSIGNMENT RESPONSE (2/2)
83 © Nokia Siemens Networks CN3203EN01GLN00
Example Trace of the PDP Context Activation Procedure in Iu over IP interface Activate PDP Context Accept (1/2)
84 © Nokia Siemens Networks CN3203EN01GLN00
Example Trace of the PDP Context Activation Procedure in Iu over IP interface Activate PDP Context Accept (2/2)
85 © Nokia Siemens Networks CN3203EN01GLN00
Iu-PS interface over ATM Control Plane
86 © Nokia Siemens Networks CN3203EN01GLN00
ATM Conn:1 VPI:0 VCI:72 CID:0 Line:1 203 13:09:06.897974
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)
87 © Nokia Siemens Networks CN3203EN01GLN00
CR - CONNECTION REQUEST (SCCP Layer)
Source Local Reference
- 293045h
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)
- no global title present
- routing based on SSN and MTP routing label
- 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
Example Trace of the Attach procedure in Iu over ATM interface
Attach Request (2/10)
88 © Nokia Siemens Networks CN3203EN01GLN00
RANAP-PDU (RANAP Layer)
- extension flag: 0
- choice index: 00
initiatingMessage
- procedureCode: 19
- padding: 00000
- contents: 13
- criticality: ignore
- contents (in bits): 01
initiatingMessage
- padding: 000000
- opentype length: 59
InitialUE-Message
- extension flag: 0
- preamble: 0
protocolIEs
- padding: 000000
- length: 00 07
- id: 3
- contents: 00 03
- criticality: ignore
- contents (in bits): 01
- padding: 000000
- opentype length: 01
Attach Request (3/10)
Example Trace of the Attach procedure in Iu over ATM interface
89 © Nokia Siemens Networks CN3203EN01GLN00
CN-DomainIndicator: ps-domain
- contents (in bits): 1
- trailing bits: 0000000
- id: 15
- contents: 00 0F
- criticality: ignore
- contents (in bits): 01
- padding: 000000
- opentype length: 06
LAI
- preamble: 0
- pLMNidentity: '22F211'H
- padding: 0000000
- contents: 22 F2 11
- lAC: 'D903'H
- contents: D9 03
- id: 55
- contents: 00 37
- criticality: ignore
- contents (in bits): 01
- padding: 000000
- opentype length: 01
Example Trace of the Attach procedure in Iu over ATM interface
Attach Request (4/10)
90 © Nokia Siemens Networks CN3203EN01GLN00
RAC: '2C‘H
- contents: 2C
- id: 58
- contents: 00 3A
- criticality: ignore
- contents (in bits): 01
- padding: 000000
- opentype length: 08
SAI
- preamble: 0
- pLMNidentity: '22F211'H
- padding: 0000000
- contents: 22 F2 11
- lAC: 'D903'H
- contents: D9 03
- sAC: 'D903'H
- contents: D9 03
- id: 16
- contents: 00 10
- criticality: ignore
- contents (in bits): 01
- padding: 000000
- opentype length: 22
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
Attach Request (5/10)
Example Trace of the Attach procedure in Iu over ATM interface
91 © Nokia Siemens Networks CN3203EN01GLN00
- id: 79
- contents: 00 4F
- criticality: ignore
- contents (in bits): 01
- padding: 000000
- opentype length: 03
IuSignallingConnectionIdentifier: '000001010010100100000000'B
- contents: 05 29 00
- id: 86
- contents: 00 56
- criticality: ignore
- contents (in bits): 01
- padding: 000000
- opentype length: 05
GlobalRNC-ID
- pLMNidentity: '22F211'H
- contents: 22 F2 11
- rNC-ID: 1
- contents: 00 01
Example Trace of the Attach procedure in Iu over ATM interface
Attach Request (6/10)
92 © Nokia Siemens Networks CN3203EN01GLN00
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
- encryption algorithm GEA/3 not available
- encryption algorithm GEA/4 not available
- encryption algorithm GEA/5 not available
- encryption algorithm GEA/6 not available
- encryption algorithm GEA/7 not available
Attach Type
- GPRS attach
- Follow-on request pending
GPRS Ciphering Key Seq. Nr
- value: 7 (07h)
Attach Request (7/10)
Example Trace of the Attach procedure in Iu over ATM interface
93 © Nokia Siemens Networks CN3203EN01GLN00
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.
- Mobile Country Code: 222
- Mobile Network Code: 11
- Location Area Code: 55555 (D903h)
- Routing Area Code: 44 (2Ch)
MS Radio Access Capability
GSM 900-E Access Technology Type
- Length: 39 bits
- RF Power class: 4, max 2 W (33 dBm)
- Encrypt. algorithm A5/1 available
- Encrypt. algorithm A5/2 available
- Encrypt. algorithm A5/3 not available
- Encrypt. algorithm A5/4 not available
- Encrypt. algorithm A5/5 not available
- Encrypt. algorithm A5/6 not available
- Encrypt. algorithm A5/7 not available
Example Trace of the Attach procedure in Iu over ATM interface
Attach Request (8/10)
94 © Nokia Siemens Networks CN3203EN01GLN00
- 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
Example Trace of the Attach procedure in Iu over ATM interface
Attach Request (9/10)
95 © Nokia Siemens Networks CN3203EN01GLN00
GSM 1800 Access Technology Type
- Length: 15 bits
- RF Power class: 1, max 1 W (30 dBm)
- Controlled early Classmark Sending implemented
- PS capability not present
- VGCS capability and notifications not wanted
- VBS capability and notifications not wanted
- COMPACT Interference Meas. Capab. is not implemented
- The ME is Release '98 onwards
- UMTS FDD supported
- UMTS TDD not supported
- CDMA2000 not supported
- Spare ok
GPRS Timer
- Value: 44 sec
Example Trace of the Attach procedure in Iu over ATM interface
Attach Request (10/10)
96 © Nokia Siemens Networks CN3203EN01GLN00
ATM Conn:1 VPI:0 VCI:72 CID:0 Line:1 306 13:09:09.496583
USER PART INFORMATION (MTP-3B Layer)
Service Information Octet
- 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
Example Trace of the Attach procedure in Iu over ATM interface
SCCP connection establishment (1/2)
97 © Nokia Siemens Networks CN3203EN01GLN00
CC - CONNECTION CONFIRM (SCCP Layer)
Destination Local Reference
- 293045h
Source Local Reference
- 500000h
Protocol Class
- 2h, connection oriented
Called Party Address
- length 4 (04h)
- no global title present
- routing based on SSN and MTP routing label
- point code : 1536 (600h)
- subsystem: RANAP
End of Optional Parameters
Example Trace of the Attach procedure in Iu over ATM interface
SCCP connection establishment (2/2)
98 © Nokia Siemens Networks CN3203EN01GLN00
ATM Conn:1 VPI:0 VCI:72 CID:0 Line:1 307 13:09:09.496647
USER PART INFORMATION (MTP-3B Layer)
Service Information Octet
- 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
Example Trace of the Attach procedure in Iu over ATM interface
Common ID (1/4)
99 © Nokia Siemens Networks CN3203EN01GLN00
DT1 - DATA FORM 1 (SCCP Layer)
Destination Local Reference
- 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
Example Trace of the Attach procedure in Iu over ATM interface
Common ID (2/4)
100 © Nokia Siemens Networks CN3203EN01GLN00
RANAP-PDU (RANAP Layer)
- extension flag: 0
- choice index: 00
initiatingMessage
- procedureCode: 15
- padding: 00000
- contents: 0F
- criticality: ignore
- contents (in bits): 01
initiatingMessage
- padding: 000000
- opentype length: 10
CommonID
- extension flag: 0
- preamble: 0
Example Trace of the Attach procedure in Iu over ATM interface
Common ID (3/4)
101 © Nokia Siemens Networks CN3203EN01GLN00
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: '22122100000001F0'H
- length (in bits): 101
- padding: 0000
- contents: 22 12 21 00 00 00 01 F0
Example Trace of the Attach procedure in Iu over ATM interface
Common ID (4/4)
102 © Nokia Siemens Networks CN3203EN01GLN00
ATM Conn:1 VPI:0 VCI:72 CID:0 Line:1 308 13:09:09.496716
USER PART INFORMATION (MTP-3B Layer)
Service Information Octet
- 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
Example Trace of the Attach procedure in Iu over ATM interface
Attach Accept (1/5)
103 © Nokia Siemens Networks CN3203EN01GLN00
DT1 - DATA FORM 1 (SCCP Layer)
Destination Local Reference
- 293045h
Segmenting/Reassembling
- no more data
- the Segment./Reas. octet : 00
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
Example Trace of the Attach procedure in Iu over ATM interface
Attach Accept (2/5)
104 © Nokia Siemens Networks CN3203EN01GLN00
RANAP-PDU (RANAP Layer)
- extension flag: 0
- choice index: 00
initiatingMessage
- procedureCode: 20
- padding: 00000
- contents: 14
- criticality: ignore
- contents (in bits): 01
initiatingMessage
- padding: 000000
- opentype length: 23
DirectTransfer
- extension flag: 0
preamble: 0
protocolIEs
- padding: 000000
- length: 00 02
- id: 16
- contents: 00 10
- criticality: ignore
- contents (in bits): 01
- padding: 000000
- opentype length: 17
Example Trace of the Attach procedure in Iu over ATM interface
Attach Accept (3/5)
105 © Nokia Siemens Networks CN3203EN01GLN00
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
- criticality: ignore
- contents (in bits): 01
- padding: 000000
- opentype length: 01
SAPI: sapi-0
- extension range: 0
- contents (in bits): 0
- trailing bits: 000000
Example Trace of the Attach procedure in Iu over ATM interface
Attach Accept (4/5)
106 © Nokia Siemens Networks CN3203EN01GLN00
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.
- Mobile Country Code: 222
- Mobile Network Code: 11
- 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)
107 © Nokia Siemens Networks CN3203EN01GLN00
ATM Conn:1 VPI:0 VCI:72 CID:0 Line:1 315 13:09:09.632195
USER PART INFORMATION (MTP-3B Layer)
Service Information Octet
- 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
Example Trace of the Attach procedure in Iu over ATM interface
Attach Complete (1/6)
108 © Nokia Siemens Networks CN3203EN01GLN00
DT1 - DATA FORM 1 (SCCP Layer)
Destination Local Reference
- 500000h
Segmenting/Reassembling
- no more data
- the Segment./Reas. octet : 00
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
Example Trace of the Attach procedure in Iu over ATM interface
Attach Complete (2/6)
109 © Nokia Siemens Networks CN3203EN01GLN00
RANAP-PDU (RANAP Layer)
- extension flag: 0
- choice index: 00
initiatingMessage
- procedureCode: 20
- padding: 00000
- contents: 14
- criticality: ignore
- contents (in bits): 01
initiatingMessage
- padding: 000000
- opentype length: 25
DirectTransfer
- extension flag: 0
- preamble: 0
protocolIEs
- padding: 000000
- length: 00 04
- id: 16
- contents: 00 10
- criticality: ignore
- contents (in bits): 01
- padding: 000000
- opentype length: 03
Example Trace of the Attach procedure in Iu over ATM interface
Attach Complete (3/6)
110 © Nokia Siemens Networks CN3203EN01GLN00
NAS-PDU: '0803'H
- length: 02
- contents: 08 03
- id: 15
- contents: 00 0F
- criticality: ignore
- contents (in bits): 01
- padding: 000000
- opentype length: 06
LAI
- preamble: 0
- pLMNidentity: '22F211'H
- padding: 0000000
- contents: 22 F2 11
- lAC: 'D903'H
- contents: D9 03
- id: 55
- contents: 00 37
- criticality: ignore
- contents (in bits): 01
- padding: 000000
- opentype length: 01
Example Trace of the Attach procedure in Iu over ATM interface Attach Complete (4/6)
111 © Nokia Siemens Networks CN3203EN01GLN00
RAC: '2C'H
- contents: 2C
- id: 58
- contents: 00 3A
- criticality: ignore
- contents (in bits): 01
- padding: 000000
- opentype length: 08
SAI
- preamble: 0
- pLMNidentity: '22F211'H
- padding: 0000000
- contents: 22 F2 11
- lAC: 'D903'H
- contents: D9 03
- sAC: 'D903'H
- contents: D9 03
Example Trace of the Attach procedure in Iu over ATM interface
Attach Complete (5/6)
112 © Nokia Siemens Networks CN3203EN01GLN00
ATTACH COMPLETE (GPRS MM) (GSM/3G L3 Layer)
Example Trace of the Attach procedure in Iu over ATM interface
Attach Complete (6/6)
113 © Nokia Siemens Networks CN3203EN01GLN00
ATM Conn:1 VPI:0 VCI:72 CID:0 Line:1 548 13:09:15.724861
USER PART INFORMATION (MTP-3B Layer)
Service Information Octet
- 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)
114 © Nokia Siemens Networks CN3203EN01GLN00
DT1 - DATA FORM 1 (SCCP Layer)
Destination Local Reference
- 500000h
Segmenting/Reassembling
- no more data
- the Segment./Reas. octet : 00
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)
115 © Nokia Siemens Networks CN3203EN01GLN00
RANAP-PDU (RANAP Layer)
- extension flag: 0
- choice index: 00
initiatingMessage
- procedureCode: 20
- padding: 00000
- contents: 14
- criticality: ignore
- contents (in bits): 01
initiatingMessage
- padding: 000000
- opentype length: 69
DirectTransfer
- extension flag: 0
- preamble: 0
protocolIEs
- padding: 000000
- length: 00 04
- id: 16
- contents: 00 10
- criticality: ignore
- contents (in bits): 01
- padding: 000000
- opentype length: 47
Example Trace of the PDP Context Activation Procedure in Iu
over ATM interface Activate PDP Context Request (3/7)
116 © Nokia Siemens Networks CN3203EN01GLN00
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
- criticality: ignore
- contents (in bits): 01
- padding: 000000
- opentype length: 06
LAI
- preamble: 0
- pLMNidentity: '22F211'H
- padding: 0000000
- contents: 22 F2 11
- lAC: 'D903'H
- contents: D9 03
- id: 55
- contents: 00 37
- criticality: ignore
- contents (in bits): 01
- padding: 000000
- opentype length: 01
Example Trace of the PDP Context Activation Procedure in Iu
over ATM interface Activate PDP Context Request (4/7)
117 © Nokia Siemens Networks CN3203EN01GLN00
RAC: '2C'H
- contents: 2C
- id: 58
- contents: 00 3A
- criticality: ignore
- contents (in bits): 01
- padding: 000000
- opentype length: 08
SAI
- preamble: 0
- pLMNidentity: '22F211'H
- padding: 0000000
- contents: 22 F2 11
- lAC: 'D903'H
- contents: D9 03
- sAC: 'D903'H
- contents: D9 03
Example Trace of the PDP Context Activation Procedure in Iu
over ATM interface Activate PDP Context Request (5/7)
118 © Nokia Siemens Networks CN3203EN01GLN00
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
- 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)
Example Trace of the PDP Context Activation Procedure in Iu
over ATM interface Activate PDP Context Request (6/7)
119 © Nokia Siemens Networks CN3203EN01GLN00
Packet Data Protocol Address
- Length: 2 (02h)
- Dynamic PDP addressing is applied
- PDP type organisation: IETF allocated address
- PDP type number: IPv4
Access Point Name
- length : 9 (09h)
- value (hex) : 08 69 6E 74 65 72 6E
65 74
Protocol Conf. Options
- length: 38 (26h)
- Configuration protocol: IP PDP type
Password Authentic. Protocol (PAP)
Contents: 01 11 00 0F 09 4F 36 34 30 30 30 35 32 5C 00
Internet Protocol Control Protocol (IPCP)
Contents: 01 05 00 10 81 06 00 00 00 00 83 06 00 00 00 00
Example Trace of the PDP Context Activation Procedure in Iu
over ATM interface Activate PDP Context Request (7/7)
120 © Nokia Siemens Networks CN3203EN01GLN00
ATM Conn:1 VPI:0 VCI:72 CID:0 Line:1 563 13:09:16.097122
USER PART INFORMATION (MTP-3B Layer)
Service Information Octet
- 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)
Example Trace of the PDP Context Activation Procedure in Iu
over ATM interface
121 © Nokia Siemens Networks CN3203EN01GLN00
DT1 - DATA FORM 1 (SCCP Layer)
Destination Local Reference
- 293045h
Segmenting/Reassembling
- no more data
- the Segment./Reas. octet : 00
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
Example Trace of the PDP Context Activation Procedure in Iu
over ATM interface
RAB-ASSIGNMENT REQUEST (2/8)
122 © Nokia Siemens Networks CN3203EN01GLN00
RANAP-PDU (RANAP Layer)
- extension flag: 0
- choice index: 00
initiatingMessage
- procedureCode: 0
- padding: 00000
- contents: 00
- criticality: reject
- contents (in bits): 00
initiatingMessage
- padding: 000000
- opentype length: 30
RAB-AssignmentRequest
- extension flag: 0
- preamble: 0
protocolIEs
- padding: 000000
- length: 00 01
- id: 54
- contents: 00 36
- criticality: ignore
- contents (in bits): 01
- padding: 000000
- opentype length: 29
Example Trace of the PDP Context Activation Procedure in Iu over ATM
interface RAB-ASSIGNMENT REQUEST (3/8)
123 © Nokia Siemens Networks CN3203EN01GLN00
RAB-SetupOrModifyList
- length: 00
- length: 00 01
- id: 53
- contents: 00 35
- firstCriticality: reject
- contents (in bits): 00
- padding: 000000
- opentype length: 1D
firstValue
- extension flag: 0
- preamble: 011110
- rAB-ID: '00000101'B
- contents (in bits): 00000101
rAB-Parameters
- extension flag: 0
- preamble: 0001010
- trafficClass: background
- extension range: 0
- contents (in bits): 11
- rAB-AsymmetryIndicator: symmetric-bidirectional
- extension range: 0
- contents (in bits): 00
Example Trace of the PDP Context Activation Procedure in Iu over ATM interface RAB-ASSIGNMENT REQUEST (4/8)
124 © Nokia Siemens Networks CN3203EN01GLN00
maxBitrate
- length (in bits): 0
- MaxBitrate: 384000
- length (in bits): 10
- contents: 05 DB FF
- deliveryOrder: delivery-order-not-requested
- contents (in bits): 1
- maxSDU-Size: 12016
- padding: 0000000
- contents: 2E F0
sDU-Parameters
- length (in bits): 000
- extension flag: 0
- preamble: 100
sDU-ErrorRatio
- preamble: 0
- mantissa: 1
- contents (in bits): 0000
- exponent: 4
- contents (in bits): 011
residualBitErrorRatio
- preamble: 0
- mantissa: 4
- contents (in bits): 0011
- exponent: 3
- contents (in bits): 010
Example Trace of the PDP Context Activation Procedure in Iu over ATM interface
RAB-ASSIGNMENT REQUEST (5/8)
125 © Nokia Siemens Networks CN3203EN01GLN00
- deliveryOfErroneousSDU: yes
- contents (in bits): 00
allocationOrRetentionPriority
- extension flag: 0
- preamble: 0
- priorityLevel: 2
- contents (in bits): 0010
- pre-emptionCapability: shall-not-trigger-pre-emption
- contents (in bits): 0
- pre-emptionVulnerability: pre-emptable
- contents (in bits): 1
- queuingAllowed: queueing-not-allowed
- contents (in bits): 0
- relocationRequirement: none
- extension range: 0
- contents (in bits): 1
userPlaneInformation
- extension flag: 0
- preamble: 0
- userPlaneMode: transparent-mode
- extension range: 0
- contents (in bits): 0
- uP-ModeVersions: '0000000000000001'B
- contents: 00 01
Example Trace of the PDP Context Activation Procedure in Iu over ATM interface
RAB-ASSIGNMENT REQUEST (6/8)
126 © Nokia Siemens Networks CN3203EN01GLN00
transportLayerInformation
- extension flag: 0
- preamble: 0
- transportLayerAddress: '11000000000000010000000100000011'B
- extension range: 0
- length (in bits): 00011111
- padding: 00000
- contents: C0 01 01 03
iuTransportAssociation
- 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
- extension range: 0
- contents (in bits): 01
- trailing bits: 00000
Example Trace of the PDP Context Activation Procedure in Iu over ATM interface
RAB-ASSIGNMENT REQUEST (7/8)
127 © Nokia Siemens Networks CN3203EN01GLN00
- secondCriticality: ignore
- contents (in bits): 01
- padding: 000000
- opentype length: 03
secondValue
- extension flag: 0
- preamble: 1100000
pDP-TypeInformation
- length (in bits): 1
- PDP-Type: ipv4
- extension range: 0
- contents (in bits): 011
- PDP-Type: ipv4
- extension range: 0
- contents (in bits): 011
- dataVolumeReportingIndication: do-not-report
- contents (in bits): 1
- trailing bits: 000000
Example Trace of the PDP Context Activation Procedure in Iu over ATM interface
RAB-ASSIGNMENT REQUEST (8/8)
128 © Nokia Siemens Networks CN3203EN01GLN00
ATM Conn:1 VPI:0 VCI:72 CID:0 Line:1 570 13:09:16.291551
USER PART INFORMATION (MTP-3B Layer)
Service Information Octet
- 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
Example Trace of the PDP Context Activation Procedure in Iu over ATM interface
RAB-ASSIGNMENT RESPONSE (1/4)
129 © Nokia Siemens Networks CN3203EN01GLN00
DT1 - DATA FORM 1 (SCCP Layer)
Destination Local Reference
- 500000h
Segmenting/Reassembling
- no more data
- the Segment./Reas. octet : 00
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
Example Trace of the PDP Context Activation Procedure in Iu over ATM interface
RAB-ASSIGNMENT RESPONSE (2/4)
130 © Nokia Siemens Networks CN3203EN01GLN00
RANAP-PDU (RANAP Layer)
- extension flag: 0
- choice index: 11
outcome
- procedureCode: 0
- padding: 00000
- contents: 00
- criticality: reject
- contents (in bits): 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
- criticality: ignore
- contents (in bits): 01
- padding: 000000
- opentype length: 13
Example Trace of the PDP Context Activation Procedure in Iu over ATM interface
RAB-ASSIGNMENT RESPONSE (3/4)
131 © Nokia Siemens Networks CN3203EN01GLN00
RAB-SetupOrModifiedList
- length: 00
- length: 00 01
- id: 51
- contents: 00 33
- criticality: ignore
- contents (in bits): 01
- padding: 000000
- opentype length: 0C
RAB-SetupOrModifiedItem
- extension flag: 0
- preamble: 1100
- rAB-ID: '00000101'B
- contents (in bits): 00000101
- transportLayerAddress: '00001010000101000001010000000011'B
- extension range: 0
- length (in bits): 00011111
- padding: 00
- contents: 0A 14 14 03
iuTransportAssociation
- extension flag: 0
- choice index: 0
- gTP-TEI: '00000000'H
- padding: 000000
- contents: 00 00 00 00
Example Trace of the PDP Context Activation Procedure in Iu over ATM interface
RAB-ASSIGNMENT RESPONSE (4/4)
132 © Nokia Siemens Networks CN3203EN01GLN00
ATM Conn:1 VPI:0 VCI:72 CID:0 Line:1 587 13:09:16.697225
USER PART INFORMATION (MTP-3B Layer)
Service Information Octet
- 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)
Example Trace of the PDP Context Activation Procedure in Iu over ATM interface
133 © Nokia Siemens Networks CN3203EN01GLN00
DT1 - DATA FORM 1 (SCCP Layer)
Destination Local Reference
- 293045h
Segmenting/Reassembling
- no more data
- the Segment./Reas. octet : 00
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
Example Trace of the PDP Context Activation Procedure in Iu over ATM interface
Activate PDP Context Accept (2/6)
134 © Nokia Siemens Networks CN3203EN01GLN00
RANAP-PDU (RANAP Layer)
- extension flag: 0
- choice index: 00
initiatingMessage
- procedureCode: 20
- padding: 00000
- contents: 14
- criticality: ignore
- contents (in bits): 01
initiatingMessage
- padding: 000000
- opentype length: 3B
DirectTransfer
- extension flag: 0
- preamble: 0
protocolIEs
- padding: 000000
- length: 00 02
- id: 16
- contents: 00 10
- criticality: ignore
- contents (in bits): 01
- padding: 000000
- opentype length: 2F
Example Trace of the PDP Context Activation Procedure in Iu over ATM interface
Activate PDP Context Accept (3/6)
135 © Nokia Siemens Networks CN3203EN01GLN00
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
- criticality: ignore
- contents (in bits): 01
- padding: 000000
- opentype length: 01
SAPI: sapi-0
- extension range: 0
- contents (in bits): 0
- trailing bits: 000000
Example Trace of the PDP Context Activation Procedure in Iu over ATM interface
Activate PDP Context Accept (4/6)
136 © Nokia Siemens Networks CN3203EN01GLN00
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
- Mean throughput: Best effort
- 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
Example Trace of the PDP Context Activation Procedure in Iu over ATM interface
Activate PDP Context Accept (5/6)
137 © Nokia Siemens Networks CN3203EN01GLN00
- 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)
Radio Priority
- Priority level 2
Packet Data Protocol Address
- Length: 6 (06h)
- PDP type organisation: IETF allocated address
- PDP type number: IPv4
- Address: 10.98.2.14
Protocol Conf. Options
- length: 20 (14h)
- Configuration protocol: IP PDP type
Internet Protocol Control Protocol (IPCP)
Contents: 04 05 00 10 81 06 00 00 00 00 83 06 00 00 00 00
Example Trace of the PDP Context Activation Procedure in Iu over ATM interface
Activate PDP Context Accept (6/6)