Professional Documents
Culture Documents
04 CN3203EN01GLN01 Iu-PS Interface 1
04 CN3203EN01GLN01 Iu-PS Interface 1
Iu-PS Interface
Training Document
Iu-PS Interface
The information in this document is subject to change without notice and describes only the
product defined in the introduction of this documentation. This document is intended for the
use of Nokia's customers only for the purposes of the agreement under which the document is
submitted, and no part of it may be reproduced or transmitted in any form or means without
the prior written permission of Nokia. The document has been prepared to be used by
professional and properly trained personnel, and the customer assumes full responsibility
when using it. Nokia welcomes customer comments as part of the process of continuous
development and improvement of the documentation.
The information or statements given in this document concerning the suitability, capacity, or
performance of the mentioned hardware or software products cannot be considered binding
but shall be defined in the agreement made between Nokia and the customer. However,
Nokia has made all reasonable efforts to ensure that the instructions contained in the
document are adequate and free of material errors and omissions. Nokia will, if necessary,
explain issues which may not be covered by the document.
Nokia's liability for any errors in the document is limited to the documentary correction of
errors. NOKIA WILL NOT BE RESPONSIBLE IN ANY EVENT FOR ERRORS IN THIS
DOCUMENT OR FOR ANY DAMAGES, INCIDENTAL OR CONSEQUENTIAL (INCLUDING
MONETARY LOSSES), that might arise from the use of this document or the information in it.
This document and the product it describes are considered protected by copyright according
to the applicable laws.
NOKIA logo is a registered trademark of Nokia Oyj.
Other product names mentioned in this document may be trademarks of their respective
companies, and they are mentioned for identification purposes only.
Copyright © Nokia Oyj 2009. All rights reserved.
2 (161)
Contents
Contents
2 Objectives....................................................................................4
3 Introduction.................................................................................5
3 (161)
Iu-PS Interface
2 Objectives
After this module the student 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
4 (161)
Contents
3 Introduction
The Iu interface connects the UTRAN or GERAN and the Core Network packet
domains allowing the exchange of signalling information and user data. The
user plane of the Iu interface shall allow user data from many users to be
multiplexed over the same physical resource. Resources are given to a user
upon activity (when data is sent or received) and are reallocated immediately
thereafter.
In UMTS only user data is transmitted on this shared physical medium.
Signalling data is transferred via an SCCP connection. A reference
configuration for the Iu interface control and user plane is given in Figure 1.
3G SGSN
5 (161)
Iu-PS Interface
RANAP
SCCP-SAP
SCCP
M3UA MTP-3b
SCTP SSCF
SSCOP SAAL-NNI
IP
AAL5
L2 ATM
Figure 2: SAP between RANAP and its transport for the Iu-PS Control Plane
Figure 2 shows, for the Iu-PS Control Plane, the point at which the service
primitives are invoked. A single SAP is defined independently of the signalling
bearer. The SAP provides the SCCP primitives. The figure is not intended to
constrain the architecture.
6 (161)
Contents
1. SCCP (ITU-T Rec. Q.711 (07/1996)) The SCCP protocol offers direct
signalling connections (Layer 3 Session and Mobility Management) for
each active UE. The SCCP connections are used to differentiate the
signalling transactions between different subscribers. It provides
connectionless service, class 0, connection oriented service, class 2,
separation of the connections mobile by mobile basis on the connection
oriented link and establishment of a connection oriented link mobile by
mobile basis.
2. MTP-3b (ITU-T Rec. Q.2210 (07/1996)) The MTP-3b protocol is used
to transport the Signalling Connection Control Part (SCCP) packets over
several parallel signalling links, if one of the signalling links fails,
MTP-3b layer directs the traffic to the remaining links. It provides
message routing, discrimination and distribution (for point-to-point link
only), signalling link management load sharing and changeover/back
between links within one link-set. The need for multiple link-sets is
precluded.
7 (161)
Iu-PS Interface
8 (161)
Contents
9 (161)
Iu-PS Interface
10 (161)
Contents
11 (161)
Iu-PS Interface
RRC The Radio Resource Control manages the physical layer and its activities
whenever required. For instance, if a radio link is to set up, the RRC layer
commands to perform this activity, command is delivered through RLC to the
MAC and MAC performs this activity and finally, the radio link set up is
carried through the Layer 1.
12 (161)
Contents
RLC The functionality of the Radio Link Control is similar than in “normal”
Layer 2. This means mainly flow control related activities like for instance data
block sequencing.
MAC The Medium Access Control physically implements radio link
management, i.e. radio link set-up, maintaining, physical radio channel
configuration, error protection, encryption and radio link deletion.
L1 The physical layer (Layer 1) of the Uu interface (Air interface) is
implemented with WCDMA technology and either FDD or TDD variant can be
used.
SCCP The Signalling Connection Control Part protocol offers direct signalling
connections (Layer 3 Session and Mobility Management) for each active UE.
The SCCP connections are used to differentiate the signalling transactions
between different subscribers. It provides connectionless service, class 0,
connection oriented service, class 2, separation of the connections mobile by
mobile basis on the connection oriented link and establishment of a connection
oriented link mobile by mobile basis.
13 (161)
Iu-PS Interface
Update Location
Ack
SCCP CC
“Follow-on request” NOT set to pending in Attach Request, thus SGSN will release Iu
(and RNC the RRC connection) – continued on next page
14 (161)
Contents
15 (161)
Iu-PS Interface
4.4 SCCP
The SCCP protocol offers direct signaling connections (Layer 3 Session and
Mobility Management) for each active UE. The SCCP connections are used to
differentiate the signalling transactions between different subscribers.
Connectionless Connection-oriented
Services Services
Protocol Class 0 1 2 3
Basic Flow Control
Basic Sequenced
Connection- Connection-
Connectionless Connectionless
oriented oriented
Service Service
Service Service
16 (161)
Contents
The Signalling Connection Control Part (SCCP) messages are used by the peer-
to-peer protocol. All messages are uniquely identified by means of a message
type code, which is to be found in all the messages. The meaning and definition
of the various parameter fields contained in these messages are specified in
clause 2. The actual inclusion of these parameter fields in a given message
depends on the class of protocol and is specified in clause 3.
17 (161)
Iu-PS Interface
18 (161)
Contents
19 (161)
Iu-PS Interface
CR - CONNECTION REQUEST
Source Local Reference
20 (161)
Contents
- 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
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
RLSD - RELEASED
Destination Local Reference
- 61F144h
Source Local Reference
- 040000h
Release Cause
- end user originated
21 (161)
Iu-PS Interface
In SCCP Messages, the following sub fields might be analysed in further detail:
4.4.2.4 credit:
The “credit” parameter field is used in the acknowledgements to indicate to the
sender how many messages it may send, i.e. window size. It is also used in the
CR and CC message to indicate the proposed and selected credit, and in the IT
message to audit the consistency of this connection data at both ends of a
connection section.
4.4.2.5 data:
The “data” parameter field contains information coming from upper layers or
from SCCP management. In connectionless and connection-oriented messages
the “data” parameter field contains information coming from upper layers.
22 (161)
Contents
4.4.2.6 diagnostic:
The “diagnostic” parameter field has been deleted.
4.4.2.7 error cause:
The “error cause” parameter field is used in the Protocol Data Unit Error
message in order to indicate what is the exact protocol error.
23 (161)
Iu-PS Interface
4.4.2.16 segmenting/reassembling:
The “segmenting/reassembling” parameter field is used in the data message for
the segmenting and reassembling function. It is the more data indicator (M-bit).
This is used only in connection-oriented messages. It is set to one in a data
message to indicate that more data will follow in a subsequent message. It is set
to zero in a data message to indicate that the data in this message forms the end
of a complete data sequence.
4.4.2.17 sequencing/segmenting:
The “sequencing/segmenting” parameter field contains the information
necessary for the following functions: sequence numbering, flow control,
segmenting and reassembling.
4.4.2.20 segmentation:
The “segmentation” parameter field is used in the XUDT, XUDTS, LUDT and
LUDTS messages to indicate that a SCCP message has been segmented, or, in
case of the LUDT(S), that it may undergo segmenting at an MTP/MTP-3b
interworking node. The parameter also contains all the information necessary to
allow the correct reassembly of the message.
4.4.2.21 importance:
The “importance” parameter is an optional parameter transported in CR, CC,
RLSD, CREF, LUDT, LUDTS, XUDT and XUDTS messages. It gives SCCP
the ability to restrict messages based on their importance.
24 (161)
Contents
4.5 RANAP
4.5.1 Functions
25 (161)
Iu-PS Interface
INITIAL UE-MESSAGE
RANAP-PDU
- extension flag: 0
- choice index: 00
initiatingMessage
- procedureCode: 19 RAC: '01'H
- padding: 00000 - contents
- contents - id: 58
- criticality: ignore - contents
- contents (in bits): 01 - criticality: ignore
initiatingMessage - contents (in bits): 01
- padding: 000000 - padding: 000000
- opentype length - - opentype length SAI
InitialUE-Message - preamble: 0
- extension flag: 0 - pLMNidentity: '32F403'H
- preamble: 0 - padding: 0000000
protocolIEs - contents
- padding: 000000 - lAC: '03EF'H
- length - contents
- id: 3 - sAC: 'EA62'H
- contents - contents
- criticality: ignore - id: 16
- contents (in bits): 01 - contents
- padding: 000000 - criticality: ignore
- opentype length - contents (in bits): 01
CN-DomainIndicator: ps-domain - padding: 000000
26 (161)
Contents
27 (161)
Iu-PS Interface
DIRECT TRANSFER
RANAP-PDU
- extension flag: 0
- choice index: 00
initiatingMessage
- procedureCode: 20 - contents (in bits): 01
- padding: 00000 - padding: 000000
- contents - opentype length
- criticality: ignore NAS-PDU: '8A47'H
- contents (in bits): 01 - length
initiatingMessage - contents
- padding: 000000 - id: 59
- opentype length - contents
DirectTransfer - criticality: ignore
- extension flag: 0 - contents (in bits): 01
- preamble: 0 - padding: 000000
protocolIEs - opentype length
- padding: 000000 SAPI: sapi-0
- length - extension range: 0
- id: 16 - contents (in bits): 0
- contents - trailing bits: 000000
- criticality: ignore
28 (161)
Contents
The figure below describes the UTRAN originated Direct Transfer procedure.
DIRECT TRANSFER
RANAP-PDU
- extension flag: 0
- choice index: 00 LAI
initiatingMessage - preamble: 0
- procedureCode: 20 - pLMNidentity: '32F403'H
- padding: 00000 - padding: 0000000
- contents - contents
- criticality: ignore - lAC: '03EF'H
- contents (in bits): 01 - contents
initiatingMessage - id: 55
- padding: 000000 - contents
- opentype length - criticality: ignore
DirectTransfer - contents (in bits): 01
- extension flag: 0 - padding: 000000
- preamble: 0 - opentype length
protocolIEs RAC: '01'H
- padding: 000000 - contents
- length - id: 58
- id: 16 - contents
- contents - criticality: ignore
- criticality: ignore - contents (in bits): 01
- contents (in bits): 01 - padding: 000000
- padding: 000000 - opentype length
- opentype length SAI
NAS-PDU: '0A4624'H - preamble: 0
- length - pLMNidentity: '32F403'H
- contents - padding: 0000000
- id: 15 - contents
- contents - lAC: '03EF'H
- criticality: ignore - contents
- contents (in bits): 01 - sAC: 'EA62'H
- padding: 000000 - contents
- opentype length
29 (161)
Iu-PS Interface
RNC CN
RAB ASSIGNMENT
REQUEST
RAB ASSIGNMENT
RESPONSE
.
.
.
*
30 (161)
Contents
31 (161)
Iu-PS Interface
32 (161)
Contents
- shall not be handed over to GSM, i.e. the RAB shall never be handed over
to GSM. This means that UTRAN shall not initiate handover to GSM for
the UE unless the RABs with this indication have first been released with
the normal release procedures.
The value of the Service Handover IE is valid throughout the lifetime of the
RAB or until changed by a RAB modification.
The Service Handover IE shall only influence decisions made regarding
UTRAN initiated inter-system handovers.
If the Service Handover IE is not included, the decision whether to perform an
inter-system handover to GSM is only an internal UTRAN matter.
UTRAN shall report to CN, in the first RAB ASSIGNMENT RESPONSE
message, the result for all the requested RABs, such as:
- List of RABs successfully established or modified.
- List of RABs released.
- List of RABs queued.
- List of RABs failed to establish or modify.
- List of RABs failed to release.
The same RAB ID shall only be present once in the whole RAB
ASSIGNMENT RESPONSE message.
For each RAB successfully established towards the PS domain, the RNC shall
include the Transport Layer Address IE and the Iu Transport Association IE in
the RAB ASSIGNMENT RESPONSE message.
For each RAB successfully modified or released towards the PS domain, for
which data volume reporting has been requested, the RNC shall include the DL
Data Volumes IE in the RAB ASSIGNMENT RESPONSE message.
For each RAB successfully released towards the PS domain, the RNC shall
include in the RAB ASSIGNMENT RESPONSE message, if available, the DL
GTP-PDU Sequence Number IE and the UL GTP-PDU Sequence Number IE, if
the release was initiated by UTRAN.
The RNC shall report in the RAB ASSIGNMENT RESPONSE message at least
one RAB:
set-up/modified or;
released or;
queued or;
failed to set-up/modify or;
failed to release.
For each RAB successfully modified towards the PS domain, if the RNC has
changed the Transport Layer Address IE and/or the Iu Transport Association
33 (161)
Iu-PS Interface
IE, it shall include the new value(s) in the RAB ASSIGNMENT RESPONSE
message.
Before reporting the successful outcome of a specific RAB to establish or
modify, the RNC shall have executed the initialisation of the user plane mode as
requested by the CN in the User Plane Mode IE. This initialisation is described
in 3GPP TS 25.415: “UTRAN Iu interface user plane protocols.
In case of establishment of a RAB for the PS domain, the CN must be prepared
to receive user data before the RAB ASSIGNMENT RESPONSE message has
been received.
If none of the RABs have been queued, the CN shall stop timer T RABAssgt. And
the RAB Assignment procedure terminates. In that case, the procedure shall
also be terminated in UTRAN.
When the request to establish or modify one or several RABs is put in the
queue, UTRAN shall start the timer TQUEUING. This timer specifies the maximum
time for queuing of the request of establishment or modification. The same
timer TQUEUING is supervising all RABs being queued.
For each RAB that is queued the following outcomes shall be possible:
- successfully established or modified;
- failed to establish or modify;
- failed due to expiry of the timer TQUEUING.
For the queued RABs, indicated in the first RAB ASSIGNMENT RESPONSE
message, UTRAN shall report the outcome of the queuing for every RAB
individually or for several RABs in subsequent RAB ASSIGNMENT
RESPONSE message(s). This is left to implementation. UTRAN shall stop
TQUEUING when all RABs have been either successfully established or modified
or failed to establish or modify. The RAB Assignment procedure is then
terminated both in CN and UTRAN when all RABs have been responded to.
When CN receives the response that one or several RABs are queued, CN shall
expect UTRAN to provide the outcome of the queuing function for each RAB
before expiry of the T RABAssgt timer. In case the timer T RABAssgt expires, the CN
shall consider the RAB Assignment procedure terminated and the RABs not
reported shall be considered as failed.
In the case the timer TQUEUING expires, the RAB Assignment procedure
terminates in UTRAN for all queued RABs, and UTRAN shall respond for all
of them in one RAB ASSIGNMENT RESPONSE message. The RAB
Assignment procedure shall also be terminated in CN.
In case a request to modify or release a RAB contains the RAB ID of a RAB
being queued, the RAB shall be taken out of the queue and treated according to
the second request. The first request shall be responded to as a RAB failed to
set-up or modify with the cause value “Request superseded”.
When UTRAN reports unsuccessful establishment/modification of a RAB, the
cause value should be precise enough to enable the core network to know the
34 (161)
Contents
35 (161)
Iu-PS Interface
36 (161)
Contents
If, for a RAB requested to be modified, one (or more) of these IEs except RAB
ID IE are not present in RAB ASSIGNMENT REQUEST message the RNC
shall continue to use the value(s) currently in use for the not present IEs.
For each RAB request to release, the message shall contain:
- RAB ID.
- Cause.
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
37 (161)
Iu-PS Interface
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
38 (161)
Contents
userPlaneInformation
- extension flag: 0
- preamble: 0
- userPlaneMode: transparent-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
- extension flag: 0
- choice index: 0
- gTP-TEI: '0000011F'H
- 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
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
39 (161)
Iu-PS Interface
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
- padding: 000000
- contents
In the RAB Assignment Request and response, the following sub-fields might
be analysed in further detail:
RAB ID
This element uniquely identifies the radio access bearer for a specific CN
domain for a particular UE, which makes the RAB ID unique over one Iu
connection. The RAB ID shall remain the same for the duration of the RAB
even when the RAB is relocated to another Iu connection.
The purpose of the element is to bind data stream from the Non-Access Stratum
point of view (e.g. bearer of call or PDP context) and radio access bearer in
40 (161)
Contents
Access Stratum. The value is also used in the RNC to relate Radio Bearers to a
RAB. The content of this information element is transferred unchanged from the
CN node (i.e., MSC or SGSN) via RNC to UE by RANAP messages and RRC
messages. For RRC messages refer to 3GPP TS 25.331: “Radio Resource
Control (RRC) protocol specification”.
The element contains binary representation of either the Stream Identifier (SI)
for CS domain or the Network Service Access Point Identifier (NSAPI) for PS
domain. These identifiers are coded in the RAB ID element in accordance with
the coding of the Stream Identifier IE and with the coding of the NSAPI IE in
3GPP TS 24.008: “Mobile radio interface layer 3 specification; Core network
protocols; Stage 3”.
RAB Parameters
The purpose of the RAB parameters IE group and other parameters within the
RAB parameters IE group is to indicate all RAB attributes as defined in 3GPP
TS 23.107: “Quality of Service (QoS) concept and architecture” for both
directions. For more details on RAB Parameters refer to Appendix B.
41 (161)
Iu-PS Interface
Iu Transport Association
This element is used to associate the RAB and the corresponding transport
bearer. In PS domain this information element is the GTP Tunnel Endpoint
Identifier.
Service Handover
This IE tells if intersystem handover to GSM should, should not, or shall not be
performed for the RAB in question.
42 (161)
Contents
Cause
The purpose of the Cause IE is to indicate the reason for a particular event for
the RANAP protocol.
- Radio Network Layer Cause:
Value Cause
1 RAB preempted
2 Trelocoverall Expiry
3 Trelocprep Expiry
4 Treloccomplete Expiry
5 Tqueing Expiry
6 Relocation Triggered
7 TRELOCalloc Expiry
10 Relocation Cancelled
11 Successful Relocation
16 User Inactivity
43 (161)
Iu-PS Interface
28 Iu UP Failure
30 Invalid RAB ID
31 No remaining RAB
39 Request superseded
45 Directed Retry
- NAS Cause
81 User Restriction Start Indication
83 Normal Release
- Protocol Cause
113 Transfer Syntax Error
44 (161)
Contents
- Miscellaneous Cause
113 O&M Intervention
45 (161)
Iu-PS Interface
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
46 (161)
Contents
4.5.2.5 Iu Release
The purpose of the Iu Release procedure is to enable the CN to release the Iu
connection and all UTRAN resources related only to that Iu connection to be
released. The procedure uses connection-oriented signalling.
Data Volume reporting is never required, so data volume reports are never
accepted on Iu Release Complete.
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
47 (161)
Iu-PS Interface
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
48 (161)
Contents
4.5.2.6 Paging
The purpose of the Paging procedure is to enable the CN to request the UTRAN
to contact an UE. The procedure uses connectionless signalling. The figure
below describes the 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
49 (161)
Iu-PS Interface
- 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
50 (161)
Contents
4.5.2.7 Common ID
The purpose of the Common ID procedure is to inform the RNC about the
permanent NAS UE identity (IMSI) of a user. This is used by the RNC, for
example, to create a reference between the permanent NAS UE identity of the
user and the Radio Resource Control (RRC) connection of that user for UTRAN
paging coordination. The procedure uses connection-oriented signalling. The
figure below describes the Common ID procedure.
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
51 (161)
Iu-PS Interface
The figure below describes the successful Security Mode Control procedure.
52 (161)
Contents
IntegrityProtectionInformation
- preamble: 0
permittedAlgorithms
- length (in bits): 0000
- IntegrityProtectionAlgorithm: standard-UMTS-integrity-algorithm--
contents (in bits): 0000
- key:
'01100010111111100000110100110110100000111010111010100101001101101110000101
010000101
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:
'10000011101011101010010100110110111000010101000010101000000000001000001110
101110101
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
53 (161)
Iu-PS Interface
- 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
54 (161)
Contents
55 (161)
Iu-PS Interface
56 (161)
Contents
57 (161)
Iu-PS Interface
58 (161)
Contents
59 (161)
Iu-PS Interface
60 (161)
Contents
Layer 3 radio interface messages sent from the 3G SGSN are encapsulated into
Radio Access Network Application Protocol (RANAP) protocol messages and
received by the Serving RNC (SRNC). The SRNC forwards the messages
transparently to the UE/MS across the Uu interface by employing the Radio
Resource Control (RRC) protocol.
61 (161)
Iu-PS Interface
62 (161)
Contents
63 (161)
Iu-PS Interface
new old
MS UTRAN new SGSN old SGSN GGSN EIR MSC/VLR HLR MSC/VLR
1. Attach Request
2. Identification Request
2. Identification Response
3. Identity Request
3. Identity Response
4. Authentication
5. IMEI Check
C1
8. Attach Accept
9. Attach Complete
10. TMSI Reallocation Complete
64 (161)
Contents
65 (161)
Iu-PS Interface
66 (161)
Contents
Attach Request
67 (161)
Iu-PS Interface
- 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
- Value: 63 92 B6
GPRS Timer
- Value: 44 sec
68 (161)
Contents
From the Mobility Management part we can find several more fields in the trace
of an analyser. In the case of the Attach Request message we can see:
MS network capability
The purpose of the MS network capability information element is to provide the
network with information concerning aspects of the mobile station related to
GPRS. The contents might affect the manner in which the network handles the
operation of the mobile station. The MS network capability information
indicates general mobile station characteristics and it shall therefore, except for
fields explicitly indicated, be independent of the frequency band of the channel
it is sent on. For further information about the sub-fields, please refer to 3GPP
TS 24.008, chapter 10.5.5.12.
The Attach Type
The Attach Type indicates which type of attach that is to be performed, i.e.,
GPRS attach only, GPRS Attach while already IMSI attached, or combined
GPRS / IMSI attach.
The Attach Type, 3 bits
value Type of Attach Text
1. GPRS Attach
2. GPRS Attach while IMSI attached
3. Combined GPRS/IMSI attach
Follow-on request, 1 bit
value Follow-on request Text
4. No follow-on request pending
5. Follow-on request pending
Follow-on request pending is applicable only in UMTS
In UMTS, if the MS wishes to prolong the established PS signalling connection
after the GPRS attach procedure, it may set a follow-on request pending.
GPRS Ciphering Key Seq. Nr
In a UMTS authentication challenge, the purpose of the Ciphering Key
Sequence Number information element is to make it possible for the network to
identify the ciphering key CK and integrity key IK which are stored in the MS
without invoking the authentication procedure. CK and IK form a Key Set
Identifier (KSI) (see 3GPP TS 33.102) which is encoded the same as the CKSN
and is therefore included in the CKSN field.
GPRS Ciphering Key Seq. Nr, 1 bit
value GPRS Ciphering Key Seq. Nr. Text
0-6 Possible values for the ciphering key
7 No key is available (MS to network)
69 (161)
Iu-PS Interface
DRX Parameter
DRX Parameters indicates whether the MS uses discontinuous reception or not.
For further information about the sub-fields, please refer to 3GPP TS 24.008,
chapter 10.5.5.6.
Mobile Station Identity
This element is used to uniquely identify a mobile station. Identification is done
using International Mobile Subscriber Identity (IMSI), Temporary Mobile
Subscriber Identity (TMSI), International Mobile Equipment Identity (IMEI) or
International Mobile Equipment Identity with Software Version (IMEISV). In
the ciphering mode setting procedure and in the GMM authentication and
ciphering procedure the mobile shall select the IMEISV.
Routing Area Id.
The purpose of the Routing Area Identification information element is to
provide an unambiguous identification of routing areas within the area covered
by the UMTS system.
MS Radio Access Cap.
The purpose of the MS RA capability information element is to provide the
radio part of the network with information concerning radio aspects of the
mobile station. The contents might affect the manner in which the network
handles the operation of the mobile station. For further information about the
sub-fields, please refer to 3GPP TS 24.008, chapter 10.5.5.12a.
Due to shared radio frequency channel numbers between 1800 and 1900, the
mobile should provide MS Radio Access capability for either 900/1800 band(s)
OR 1900 band.
Identity Request
70 (161)
Contents
Force to standby
The SGSN indicates an immediate return to PMM-IDLE state before the
READY timer expires.
Identity Response
Attach Accept
71 (161)
Iu-PS Interface
Attach Result
Here, possible values are either 'GPRS only attached' or 'Combined GPRS/IMSI
attached'
Please note, that in the request message above, a combined attach was
requested. However, the response notifies about a GPRS attach only. A reason
for this might be, that the Gs interface is down or missing.
Force to Standby
The purpose of the Force to Standby information element is to force the MS to
change the GMM stop the READY timer in order to prevent the MS to perform
cell updates. In UMTS, the network shall always indicate force to standby not
indicated in the force to standby information element.
Radio Priority
The purpose of the Radio Priority information element is to specify the priority
level that the MS shall use at the lower layers for transmission of data related to
a PDP context or for mobile originated SMS transmission.
72 (161)
Contents
Attach complete
73 (161)
Iu-PS Interface
2. Service Request
3. Security Functions
4. Service Accept
8. Uplink PDU
74 (161)
Contents
75 (161)
Iu-PS Interface
the MS shall not perform the PDP context deactivation procedure for this PDP
context because the list of active and inactive PDP contexts is included in the
Service Request Message sent prior to the network.
1. Downlink PDU
2. Paging
2. Paging
4. Service Request
5. Security Functions
8. Downlink PDU
76 (161)
Contents
77 (161)
Iu-PS Interface
reflects current configurations and settings of the test-bed from where the trace
has been taken.
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
78 (161)
Contents
The figure on the next Page shows the different messages of a PDP Context
Activation Procedure. Furthers, we will have a closer look at the procedure to
analyse the single steps that need to be performed to complete this procedure.
MS UTRAN 3G-SGSN 3G-GGSN
C1
4. Invoke Trace
C2
6. Activate PDP Context Accept
1. The MS sends an Activate PDP Context Request (NSAPI, TI, PDP Type,
PDP Address, Access Point Name, QoS Requested, PDP Configuration
Options) message to the SGSN. The MS shall use PDP Address to
indicate whether it requires the use of a static PDP address or whether it
requires the use of a dynamic PDP address. The MS shall leave PDP
Address empty to request a dynamic PDP address. The MS may use
Access Point Name to select a reference point to a certain external
network and/or to select a service. Access Point Name is a logical name
referring to the external packet data network and/or to a service that the
subscriber wishes to connect to. QoS Requested indicates the desired QoS
profile. PDP Configuration Options may be used to request optional PDP
parameters from the GGSN (see GSM 09.60). PDP Configuration
Options is sent transparently through the SGSN.
2. The SGSN validates the Activate PDP Context Request using PDP Type
(optional), PDP Address (optional), and Access Point Name (optional)
provided by the MS and the PDP context subscription records. The
validation criteria, the APN selection criteria, and the mapping from APN
to a GGSN are described in annex A.
79 (161)
Iu-PS Interface
If no GGSN address can be derived or if the SGSN has determined that the
Activate PDP Context Request is not valid according to the rules described in
annex A, the SGSN rejects the PDP context activation request.
If a GGSN address can be derived, the SGSN creates a TEID for the requested
PDP context. If the MS requests a dynamic address, the SGSN lets a GGSN
allocate the dynamic address. The SGSN may restrict the requested QoS
attributes given its capabilities and the current load, and it shall restrict the
requested QoS attributes according to the subscribed QoS profile.
The SGSN sends a 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) message to the affected GGSN.
Access Point Name shall be the APN Network Identifier of the APN selected
according to the procedure described in Annex A. PDP Address shall be empty
if a dynamic address is requested. The GGSN may use Access Point Name to
find an external network and optionally to activate a service for this APN.
Selection Mode indicates whether a subscribed APN was selected, or whether a
non-subscribed APN sent by an MS or a non-subscribed APN chosen by the
SGSN was selected. Selection Mode is set according to Annex A. The GGSN
may use Selection Mode when deciding whether to accept or reject the PDP
context activation. For example, if an APN requires subscription, the GGSN is
configured to accept only the PDP context activation that requests a subscribed
APN as indicated by the SGSN with Selection Mode. Charging Characteristics
indicates which kind of charging the PDP context is liable for. The charging
characteristics on the GPRS subscription and individually subscribed APNs as
well as the way the SGSN handles Charging Characteristics and chooses to send
them or not to the GGSN is defined in 3G TS 32.015 [70]. The SGSN shall
include Trace Reference, Trace Type, Trigger Id, and OMC Identity if GGSN
trace is activated. The SGSN shall copy Trace Reference, Trace Type, and
OMC Identity from the trace information received from the HLR or OMC.
The GGSN creates a new entry in its PDP context table and generates a
Charging Id. The new entry allows the GGSN to route PDP PDUs between the
SGSN and the external PDP network, and to start charging. The way the GGSN
handles Charging Characteristics that it may have received from the SGSN is
defined in 3G TS 32.015. The GGSN then returns a Create PDP Context
Response (TEID, PDP Address, PDP Configuration Options, QoS Negotiated,
Charging Id, Cause) message to the SGSN. PDP Address is included if the
GGSN allocated a PDP address. If the GGSN has been configured by the
operator to use External PDN Address Allocation for the requested APN, PDP
Address shall be set to 0.0.0.0, indicating that the PDP address shall be
negotiated by the MS with the external PDN after completion of the PDP
Context Activation procedure. The GGSN shall relay, modify and monitor these
negotiations as long as the PDP context is in ACTIVE state, and use the GGSN-
Initiated PDP Context Modification procedure to transfer the currently used
PDP address to the SGSN and the MS. PDP Configuration Options contain
optional PDP parameters that the GGSN may transfer to the MS. These optional
PDP parameters may be requested by the MS in the Activate PDP Context
80 (161)
Contents
81 (161)
Iu-PS Interface
C2) CAMEL_GPRS_PDP_Context_Establishment_Acknowledgement.
82 (161)
Contents
The purpose of the LLC Service Access Point Identifier information element is
to identify the service access point that is used for the GPRS data transfer at
LLC layer.
SAPI identifies a point at which LLC services are provided by a Logical Link
Entity (LLE) to a layer-3 entity. Consequently, SAPI identifies an LLE that
should process an LLC frame and also a layer-3 entity that is to receive
information carried by the LLC frame.
SAPI is a four bit field. Possible values are:
SAPI Related Service
1 GPRS Mobility Management
3 User data 1
5 User data 2
7 SMS
9 User data 3
11 User data 4
83 (161)
Iu-PS Interface
NOTE: The radio priority level and the LLC SAPI parameters, though not
used in UMTS, shall be included in the messages, in order to support handover
between UMTS and GSM networks.
Quality of Service
The purpose of the quality of service information element is to specify the QoS
parameters for a PDP context. . The trace shows sub-fields of which possible
values are as follows:
The quality of service is a type 4 information element with a length of 13 octets.
The QoS requested by the MS shall be encoded both in the QoS attributes
specified in octets 3-5 and in the QoS attributes specified in octets 6-13.
A QoS IE received without octets 6-13 shall be accepted by a receiving entity.
NOTE: This behaviour is required for interworking with entities supporting
an earlier version of the protocol.
The quality of service information element is coded as shown in figure below:
8 7 6 5 4 3 2 1
Quality of service IEI Octet 1
Length of quality of service IE Octet 2
0 0 Delay Reliability Octet 3
spare class class
Peak 0 Precedence Octet 4
throughput spare class
0 0 0 Mean Octet 5
spare throughput
Traffic Class Delivery order Delivery of erroneous Octet 6
SDU
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 Octet 11
priority
Guaranteed bit rate for uplink Octet 12
Guaranteed bit rate for downlink Octet 13
84 (161)
Contents
85 (161)
Iu-PS Interface
3 Up to 4 000 octet/s
4 Up to 8 000 octet/s
5 Up to 16 000 octet/s
6 Up to 32 000 octet/s
7 Up to 64 000 octet/s
8 Up to 128 000 octet/s
9 Up to 256 000 octet/s
86 (161)
Contents
87 (161)
Iu-PS Interface
88 (161)
Contents
89 (161)
Iu-PS Interface
90 (161)
Contents
91 (161)
Iu-PS Interface
The purpose of the Radio Priority information element is to specify the priority
level that the MS shall use at the lower layers for transmission of data related to
a PDP context or for mobile originated SMS transmission.
Value Radio Priority text
1. priority level 2
2. priority level3
3. priority level 4 (lowest)
4. priority level 1 (highest)
92 (161)
Contents
Application
Relay Relay
93 (161)
Iu-PS Interface
94 (161)
Contents
5.1.1 UDP/IP
UDP/IP is the only path protocol defined to transfer GTP messages in the
version 1 of GTP. A User Datagram Protocol (UDP) compliant with RFC 768
shall be used.
Request Messages
The UDP Destination Port number for GTP-C request messages is 2123. It is
the registered port number for GTP-C.
The UDP Destination Port number for GTP-U request messages is 2152. It is
the registered port number for GTP-U.
95 (161)
Iu-PS Interface
The UDP Source Port is a locally allocated port number at the sending
GSN/RNC.
Response Messages
The UDP Destination Port value shall be the value of the UDP Source Port of
the corresponding request message.
The UDP Source Port shall be the value from the UDP Destination Port of the
corresponding request message.
Encapsulated T-PDUs
The UDP Destination Port number shall be 2152. It is the registered port
number for GTP-U. The UDP Source Port is a locally allocated port number at
the sending GSN/RNC.
The UDP destination port for the Error Indication shall be the user plane UDP
port (2152).
The UDP destination port for the Version Not Supported message shall be the
control plane UDP port (2123)
The UDP destination port for the Supported Extension Headers Notification
shall be the UDP port for User plane (2152) if the trigger for it was a user plane
message, the control plane port (2123) if the trigger for it was a control plane
message.
The UDP source port shall be locally assigned at the sending node.
5.1.1.2 IP Header
96 (161)
Contents
Response Messages
The IP source address shall be an address of the source GSN/RNC from which
the message is originated. In particular, the source Address of the “Version Not
Supported” or the “Supported Extension Headers Notification” message, shall
be set to the destination address of the message that triggered the GSN/RNC to
send the “Version Not Supported” or the “Supported Extension Headers
Notification” message.
The IP destination address shall be the source address of the GTP-PDU that is
the cause for the GSN/RNC to send one of these messages.
5.1.2 GTP-U
GTP-U Tunnels are used to carry encapsulated T-PDUs and signalling
messages between a given pair of GTP-U Tunnel Endpoints. The Tunnel
Endpoint ID (TEID), which is present in the GTP header, shall indicate which
tunnel a particular T-PDU belongs to. In this manner, packets are multiplexed
and de-multiplexed by GTP-U between a given pair of Tunnel Endpoints. The
TEID value to be used in the TEID field shall be negotiated for instance during
the GTP-C Create PDP Context and the RAB assignment procedures that take
place on the control plane.
The maximum size of a T-PDU that may be transmitted without fragmentation
by GGSN or the MS is defined in 3GPP TS 23.060. The GGSN shall fragment,
reject or discard T-PDUs, depending on the PDP type and implementation
decisions, directed to the MS if the T-PDU size exceeds the maximum size. The
decision if the T-PDUs shall be fragmented or discarded is dependent on the
external packet data network protocol.
97 (161)
Iu-PS Interface
The GTP-U protocol entity provides packet transmission and reception services
to user plane entities in the GGSN, in the SGSN and, in UMTS systems, in the
RNC. The GTP-U protocol entity receives traffic from a number of GTP-U
tunnel endpoints and transmits traffic to a number of GTP-U tunnel endpoints.
There is a GTP-U protocol entity per IP address.
The TEID in the GTP-U header is used to de-multiplex traffic incoming from
remote tunnel endpoints so that it is delivered to the User plane entities in a way
that allows multiplexing of different users, different packet protocols and
different QoS levels. Therefore no two remote GTP-U endpoints shall send
traffic to a GTP-U protocol entity using the same TEID value except for data
forwarding as part of the SRNS relocation or Intersystem Change procedures.
The GTP-U protocol is used to transmit T-PDUs between GSN pairs (or
between an SGSN and an RNC in UMTS), encapsulated in G-PDUs. A G-PDU
is a packet including a GTP-U header and a T-PDU. The Path Protocol defines
the path and the GTP-U header defines the tunnel. Several tunnels may be
multiplexed on a single path. The frames have the following general structure.
GTP-U GTP-U
Iu-PS
RNC SGSN
98 (161)
Contents
- If the Sequence Number flag (S) is set to '1' the sequence number field is
present and meaningful otherwise it is set to '0'. For GTP-U messages Echo
Request, Echo Response, Error Indication and Supported Extension
Headers Notification, the S flag shall be set to '1'.
- N-PDU Number flag (PN): the GTP-U header contains a meaningful N-
PDU Number field if the PN flag is set to 1.
- Message Type shall be set according to table 1. The value 255 is used when
T-PDUs are transmitted. The value 1 and 2 are used for “Echo” messages.
The value 26 is used for “Error Indication” message. The value 31 is used
for “Supported Extension Headers Notification” message.
- Length: This field indicates the length in octets of the payload, i.e. the rest
of the packet following the mandatory part of the GTP header (that is the
first 8 octets). The Sequence Number, the N-PDU Number or any Extension
headers shall be considered to be part of the payload, i.e. included in the
length count.
- Sequence Number: This field is meaningful if and only if the S field is set to
1. Its presence is defined in clause 6. The handling of this field is specified
in sub-clause 9.1.1. It shall be used in order to decide whether or not to
discard a received T-PDU, as specified in sub-clause 9.3.1.1 Usage of the
Sequence Number or as a transaction identity for GTP-U signalling
messages having a response message defined for a request message. For
GTP-U message, Supported Extension Headers Notification and Error
Indication, the Sequence Number shall be ignored by the receiver.
- N-PDU Number: This field is meaningful if and only if the PN flag is set to
1. Its presence is defined in clause 6. In this case, the old SGSN (or RNC)
uses it, at the Inter SGSN Routeing Area Update procedure (or SRNS
relocation), to inform the new SGSN (or RNC) of the N-PDU number
assigned to T-PDU. If an N-PDU number was not assigned to the T-PDU
by PDCP, or if the T-PDU is to be transferred using unacknowledged peer-
to-peer LLC operation, then PN shall be set to 0.
- TEID: Contains the Tunnel Endpoint Identifier for the tunnel to which this
T-PDU belongs. The TEID shall be used by the receiving entity to find the
PDP context, except for the following cases.
- The Echo Request/Response and Supported Extension Headers notification
messages, where the Tunnel Endpoint Identifier shall be set to all zeros.
- The Error Indication message where the Tunnel Endpoint Identifier shall be
set to all zeros.
99 (161)
Iu-PS Interface
The receiving GGSN and SRNC shall set the content of a counter to zero, only
during the PDP context activation. When the receiving GGSN and SRNC
receive a valid G-PDU, it shall increment this counter by one. This counter shall
wrap to zero after 65535. It defines the 'Expected Sequence Number'.
Based on the received and Expected Sequence Number values, the receiving
GGSN and SRNC may decide whether or not to discard the received G-PDU.
Annex A (Informative) describes a method to determine whether a received G-
PDU is valid.
The receiving GGSN and SRNC shall reorder the incoming T-PDUs in
sequence if the Reordering Required flag in the PDP context is set. In this case,
if needed, the receiving GGSN and SRNC shall take into account a maximum
number of valid received frames and a maximum elapsed time to assume that a
G-PDU was lost.
The G-PDU sequence numbers allocated by the GGSN (down-link) and SRNC
(uplink) are kept unchanged irrespective of the number of GTP tunnels the PDU
is transferred over. Therefore, SGSN shall use on the Iu interface for down-link
PDUs the G-PDU sequence number received from the GGSN, and shall use on
the Gn interface for uplink PDUs the G-PDU sequence number received from
the SRNC. In case of SRNS relocation and intersystem change, the SRNC and
SGSN shall tunnel PDUs without changing the G-PDU sequence numbers.
100 (161)
Contents
Radio Radio Iu UP Iu UP
proto- proto-
cols
cols User plane Transport User plane
Data Layer Data
Bearers Bearers
protocols protocols
Access Stratum
UE UTRAN CN
Radio Iu
(Uu)
101 (161)
Iu-PS Interface
Iu Interface
UTRAN CN
Iu UP layer in Iu UP layer in
transparent mode transparent mode
Radio Interface
Protocols
TNL-SAP TNL-SAP
In this mode, the Iu UP protocol instance does not perform any Iu UP protocol
information exchange with its peer over the Iu interface: no Iu frame is sent.
The Iu UP protocol layer is crossed through by PDUs being exchanged between
upper layers and transport network layer.
For instance, the transfer of GTP-U PDUs could utilise the transparent mode of
the Iu UP protocol.
The Iu UP layer in transparent mode is present in the Iu User plane for
transferring data transparently over the Iu interface.
The two strata communicate through a Service Access Point for Non Access
Stratum (NAS) Data Streams transfer.
Interfaces of the Iu UP protocol layer in transparent mode are the transport
network layer and the upper layers. The Iu UP protocol layer in transparent
mode is an empty layer through which NAS Data Streams PDUs are crossing
between the Transport Network Layer and upper layers.
The Iu UP protocol layer in transparent mode is using services of the Transport
layers in order to transfer the Iu UP PDUs over the Iu interface.
102 (161)
Contents
Iu Interface
UTRAN CN
Iu UP layer in Iu UP layer in
support mode support mode
Radio Interface
Functions Functions
Transfer of Iu
UP protocol
frames
TNL-SAP TNL-SAP
For instance, the transfer of AMR speech PDUs would utilise the support mode
for predefined SDU size of the Iu UP protocol because it requires some
Procedure Control functions and some NAS Data Streams specific functions
while the sizes of the user data being transferred can vary in a predefined
manner.
103 (161)
Iu-PS Interface
The Iu UP protocol layer in Support mode is present for data streams that need
frame handling in the UP.
The two strata communicate through a Service Access Point for Non Access
Stratum (NAS) Data Streams transfer.
104 (161)
Contents
105 (161)
Iu-PS Interface
6.1.1 SGSN SG6.0 Iu over IP Control Plane and User Plane stacks
RANAP messages from the SGSN (both to the RNC and the MS) are
transferred over IP protocol using SS7 over IP (SIGTRAN) stack.
The user PDP context data, tunnelled over IP, forms the user plane of the Iu
interface. The GPRS Tunnelling Protocol (GTP) has been adopted as the user
plane technology on the Iu interface. The GTP used for the user plane is called
GTP-U. This is to separate it from the GTP control plane protocol – GTP-C –
that is used on the Gn interface. Signalling (tunnel management) on the Iu is
handled by the control plane (RANAP) procedures.
106 (161)
Contents
The IETF SIGTRAN protocols change the three lowest layers (Message
Transfer Part (MTP) layers 1-3) of narrowband SS7 signalling protocol stacks,
while the upper layers stay the same as with PCM based signalling. The main
enabling protocol for Internet Protocol (IP) -based signalling transfer is the
Stream Control Transmission Protocol (SCTP). This protocol was specifically
designed to support capabilities similar to those found in Message Transfer Part
(MTP), but on an unreliable IP transport.
The IETF SIGTRAN working group has defined multiple ways of integrating
(or adapting) the new SCTP signalling functionality with the existing SS7
architecture. Several user adaptation layers have been defined, for providing an
interface equivalent to Message Transfer Part Level 2 (MTP2), Message
Transfer Part Level 3 (MTP3) and Signalling Connection Control Part (SCCP).
The user adaptations fill in any missing functionality between the SCTP base
and the chosen interface. In Iu over IP Control Plane, MTP3 User Adaptation
Layer (M3UA) is used. M3UA provides an interface that is compatible with
MTP3. In other words, M3UA supports MTP3 applications on top of SCTP and
IP. As integration is done at the SS7 network layer, it is possible to provide
signalling between IP- and PCM-based signalling nodes through Signalling
Gateways.
107 (161)
Iu-PS Interface
SCTP functions:
The term "stream" is used in SCTP to refer to a sequence of user messages that
are to be delivered to the upper-layer protocol in order with respect to other
messages within the same stream. This is in contrast to its usage in TCP, where
it refers to a sequence of bytes.
The SCTP user can specify the number of streams to be supported by the
association at the association start-up time. This number is negotiated with the
remote end. User messages are associated with stream numbers. Internally,
SCTP assigns a stream sequence number to each message passed to it by the
SCTP user. On the receiving side, SCTP ensures that messages are delivered to
the SCTP user in sequence within a given stream. However, while one stream
may be blocked waiting for the next in-sequence user message, delivery from
other streams may proceed.
108 (161)
Contents
When needed, SCTP fragments user messages to ensure that the SCTP packet
passed to the lower layer conforms to the path MTU. Upon receipt, fragments
are reassembled into complete messages before being passed to the SCTP user.
Chunk Bundling
The SCTP packet delivered to the lower layer consists of a common header
followed by one or more chunks. Each chunk may contain either user data or
SCTP control information. The SCTP user has the option to request bundling
more than one user message into a single SCTP packet. The SCTP chunk
bundling function is responsible for assembling the complete SCTP packet and
disassembling it at the receiving end.
Packet Validation
A mandatory Verification Tag field and a 32-bit checksum field are included in
the SCTP common header. The Verification Tag value is chosen by each end of
the association during the association start-up. Packets received without the
expected Verification Tag value are discarded as protection against blind
masquerade attacks or stale SCTP packets from a previous association. The
checksum should be set by the sender of each SCTP packet to provide
additional protection against data corruption in the network. The receiver of an
SCTP packet with an invalid checksum silently discards the packet.
109 (161)
Iu-PS Interface
MTP3 User Adaptation Layer (M3UA) defines a protocol for supporting the
transport of any Message Transfer Part Level 3 (MTP3) user signalling over
Internet Protocol (IP) using the services of Stream Control Transmission
Protocol (SCTP). It handles the MTP level 3 functions and services in the IP
network.
M3UA sets up associations between signalling endpoints so that when one
association breaks up it does not stop all the traffic between the endpoints.
M3UA does network address translation and mapping for ongoing routing to the
final IP destination.
M3UAwas designed to support fault tolerance and loadsharing. Fault tolerance
is provided using many IP Server Processes (IPSPs) or M3UA instances, which
provide the services at the same time. If a local M3UA instance fails, the
Signalling Connection Control Part (SCCP) service provider and the remote
node (IPSP instance) diverts the traffic to the remaining active instances.
M3UA is specified in RFC 3332.
For further details about SIGTRAN protocols please refer to the “Packet core network
signalling_Sigtran” document of PCNSIG course training documentation.
Attach Request
110 (161)
Contents
111 (161)
Iu-PS Interface
Identity Request
112 (161)
Contents
Identity Response
113 (161)
Iu-PS Interface
Attach Accept
114 (161)
Contents
Attach complete
115 (161)
Iu-PS Interface
116 (161)
Contents
117 (161)
Iu-PS Interface
RAB-ASSIGNMENT REQUEST
118 (161)
Contents
RAB-ASSIGNMENT RESPONSE
119 (161)
Iu-PS Interface
120 (161)
Contents
121 (161)
Iu-PS Interface
Figure 39: Iu-PS interface over ATM Control Plane Protocol Stack
122 (161)
Contents
Attach Request
123 (161)
Iu-PS Interface
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
CN-DomainIndicator: ps-domain (RANAP Layer)
- 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
RAC: '2C'H (RANAP Layer)
- 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
124 (161)
Contents
- 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
- id: 79 (RANAP Layer)
- 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
125 (161)
Iu-PS Interface
126 (161)
Contents
Attach Accept
127 (161)
Iu-PS Interface
128 (161)
Contents
- 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
129 (161)
Iu-PS Interface
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
NAS-PDU: '080201490022F211D9032C196051431805F4E3055770'H (RANAP Layer)
- 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
130 (161)
Contents
Attach Complete
131 (161)
Iu-PS Interface
132 (161)
Contents
- contents: 00 10
- criticality: ignore
- contents (in bits): 01
- padding: 000000
- opentype length: 03
NAS-PDU: '0803'H (RANAP Layer)
- 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
RAC: '2C'H (RANAP Layer)
- contents: 2C
- id: 58
- contents: 00 3A
- criticality: ignore
- contents (in bits): 01
- padding: 000000
- opentype length: 08
SAI
133 (161)
Iu-PS Interface
- preamble: 0
- pLMNidentity: '22F211'H
- padding: 0000000
- contents: 22 F2 11
- lAC: 'D903'H
- contents: D9 03
- sAC: 'D903'H
- contents: D9 03
ATTACH COMPLETE (GPRS MM) (GSM/3G L3 Layer)
7.1.1.2 Example Trace of the PDP Context Activation Procedure in Iu over ATM interface
We will have a look at 'normal' PDP Context Activation messages. 'Normal'
here means, that the system is configured to provide full service and we are not
expecting extraordinary reactions. It was taken using the Nethawk protocol
analyser and reflects current configurations and settings of the test-bed from
where the trace has been taken.
134 (161)
Contents
135 (161)
Iu-PS Interface
- 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
NAS-PDU:
'0A4105030B00001F0000000000000000020121280908696E7465726E6574272680C0230F0111
000F094
F363430303035325C0080211001050010810600000000830600000000'H
- length: 46
(RANAP Layer)
- 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
136 (161)
Contents
- 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
RAC: '2C'H (RANAP Layer)
- 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
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)
137 (161)
Iu-PS Interface
138 (161)
Contents
RAB-ASSIGNMENT REQUEST
139 (161)
Iu-PS Interface
140 (161)
Contents
- rAB-AsymmetryIndicator: symmetric-bidirectional
- extension range: 0
- contents (in bits): 00
maxBitrate (RANAP Layer)
- 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
- deliveryOfErroneousSDU: yes (RANAP Layer)
- contents (in bits): 00
allocationOrRetentionPriority
- extension flag: 0
- preamble: 0
- priorityLevel: 2
- contents (in bits): 0010
141 (161)
Iu-PS Interface
- 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
transportLayerInformation (RANAP Layer)
- 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
- secondCriticality: ignore (RANAP Layer)
142 (161)
Contents
RAB-ASSIGNMENT RESPONSE
143 (161)
Iu-PS Interface
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
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
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
144 (161)
Contents
145 (161)
Iu-PS Interface
146 (161)
Contents
- 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
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
- 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
147 (161)
Iu-PS Interface
148 (161)
Contents
Paging PAGING
Common ID COMMON ID
149 (161)
Iu-PS Interface
150 (161)
Contents
151 (161)
Iu-PS Interface
Condition Explanation
IftrafficConv-Stream This IE shall be present if the Traffic Class IE is set to
“Conversational” or “Streaming”.
IftrafficInteractiv This IE shall be present if the Traffic Class IE is set to “Interactive”.
152 (161)
Contents
Condition Explanation
IfErroneousSDU This IE shall be present if the Delivery Of Erroneous SDU IE is set
to “Yes” or “No”.
153 (161)
Iu-PS Interface
154 (161)
Contents
155 (161)
Iu-PS Interface
156 (161)
Contents
Resource Optimisation Relocation The reason for requesting relocation is resource optimisation.
Successful Relocation The reason for the action is completion of successful relocation.
Time Critical Relocation Relocation is requested for time critical reason.
TQUEUING Expiry The action failed due to expiry of the timer TQUEUING.
TRELOCalloc Expiry Relocation Resource Allocation procedure failed due to expiry of the
timer TRELOCalloc.
TRELOCcomplete Expiry The reason for the action is expiry of timer TRELOCcomplete.
TRELOCoverall Expiry The reason for the action is expiry of timer TRELOCoverall.
TRELOCprep Expiry Relocation Preparation procedure is cancelled when timer TRELOCprep
expires.
Unable To Establish During Relocation RAB failed to establish during relocation because it cannot be
supported in the target RNC.
Unknown Target RNC Relocation rejected because the target RNC is not known to the CN.
User Inactivity The action is requested due to user inactivity.
User Plane Versions Not Supported The action failed because requested user plane versions were not
supported.
157 (161)
Iu-PS Interface
References
158 (161)
Contents
Glossary
AA Anonymous Access
ABM Asynchronous Balanced Mode
ACK ACKnowledgement
ADM Asynchronous Disconnected Mode
APN Access Point Name
ATM Asynchronous Transfer Mode
BG Border Gateway
BSSAP+ Base Station System Application Part +
BSSGP Base Station System GPRS Protocol
BVCI BSSGP Virtual Connection Identifier
CCU Channel Codec Unit
CGI Cell Global Identification
CNF Confirm
CS Circuit Switched
DCOMP Identifier of the user data compression algorithm used for the N-PDU
DISC DISConnect
DL Downlink
DM Disconnected Mode
DNS Domain Name System
FRMR FRaMe Reject
GGSN Gateway GPRS Support Node
GMM/SM GPRS Mobility Management and Session Management
GRR GPRS Radio Resources service access point
GSN GPRS Support Node
GTP GPRS Tunnelling Protocol
ICMP Internet Control Message Protocol
IETF Internet Engineering Task Force
IHOSS Internet-Hosted Octet Stream Service
IND Indication
IOV Input Offset Value
IP Internet Protocol
IPv4 Internet Protocol version 4
IPv6 Internet Protocol version 6
IPX Internet Packet eXchange
ISP Internet Service Provider
L2TP Layer-2 Tunnelling Protocol
LAPD Link Access Procedure on the D-channel
LL Logical Link
LLC Logical Link Control
LLE Logical Link Entity
LLGMM LLC to GPRS Mobility Management service access point
LLM Logical Link Management
LLME Logical Link Management Entity
LL-PDU LC PDU
M More bit used to indicate the last segment of N-PDU
MAC Medium Access Control
MNRF Mobile station Not Reachable Flag
159 (161)
Iu-PS Interface
160 (161)
Contents
161 (161)