IuPS Standart

Nokia Siemens Networks SGSN, Rel. SG70 CD8, Product Documentation, v. 2

SGSN - RNC Interface Description

DN05196936

Issue 7-0

2 DN05196936Issue 7-0


Id:0900d80580815502

The information in this document is subject to change without notice and describes only the product defined in the introduction of this documentation. This documentation is intended for the use of Nokia Siemens Networks customers only for the purposes of the agreement under which the document is submitted, and no part of it may be used, reproduced, modified or transmitted in any form or means without the prior written permission of Nokia Siemens Networks. The documentation has been prepared to be used by professional and properly trained personnel, and the customer assumes full responsibility when using it. Nokia Siemens Networks welcomes customer comments as part of the process of continuous development and improvement of the documentation.

The information or statements given in this documentation concerning the suitability, capacity, or performance of the mentioned hardware or software products are given "as is" and all liability arising in connection with such hardware or software products shall be defined conclusively and finally in a separate agreement between Nokia Siemens Networks and the customer. However, Nokia Siemens Networks has made all reasonable efforts to ensure that the instructions contained in the document are adequate and free of material errors and omissions. Nokia Siemens Networks will, if deemed necessary by Nokia Siemens Networks, explain issues which may not be covered by the document.

Nokia Siemens Networks will correct errors in this documentation as soon as possible. IN NO EVENT WILL Nokia Siemens Networks BE LIABLE FOR ERRORS IN THIS DOCUMENTA-TION OR FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT, INDI-RECT, INCIDENTAL OR CONSEQUENTIAL OR ANY LOSSES, SUCH AS BUT NOT LIMITED TO LOSS OF PROFIT, REVENUE, BUSINESS INTERRUPTION, BUSINESS OPPORTUNITY OR DATA,THAT MAY ARISE FROM THE USE OF THIS DOCUMENT OR THE INFORMATION IN IT.

This documentation and the product it describes are considered protected by copyrights and other intellectual property rights according to the applicable laws.

The wave logo is a trademark of Nokia Siemens Networks Oy. Nokia is a registered trademark of Nokia Corporation. Siemens is a registered trademark of Siemens AG.

Other product names mentioned in this document may be trademarks of their respective owners, and they are mentioned for identification purposes only.

Copyright © Nokia Siemens Networks 2011/7/7. All rights reserved

f Important Notice on Product SafetyThis product may present safety risks due to laser, electricity, heat, and other sources of danger.

Only trained and qualified personnel may install, operate, maintain or otherwise handle this product and only after having carefully read the safety information applicable to this product.

The safety information is provided in the Safety Information section in the “Legal, Safety and Environmental Information” part of this document or documentation set.

The same text in German:

f Wichtiger Hinweis zur Produktsicherheit Von diesem Produkt können Gefahren durch Laser, Elektrizität, Hitzeentwicklung oder andere Gefahrenquellen ausgehen.

Installation, Betrieb, Wartung und sonstige Handhabung des Produktes darf nur durch geschultes und qualifiziertes Personal unter Beachtung der anwendbaren Sicherheits-anforderungen erfolgen.

Die Sicherheitsanforderungen finden Sie unter „Sicherheitshinweise“ im Teil „Legal, Safety and Environmental Information“ dieses Dokuments oder dieses Dokumentations-satzes.

DN05196936Issue 7-0

3


Id:0900d80580815502

Table of ContentsThis document has 44 pages.

1 Main changes in SGSN - RNC interface . . . . . . . . . . . . . . . . . . . . . . . . . 7

2 Introduction to SGSN-RNC interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

3 SGSN-RNC interface description. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103.1 Iu protocol stacks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103.2 Functions of RANAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113.3 RANAP procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133.3.1 RAB Assignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153.3.2 RAB Release Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153.3.3 Iu Release Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163.3.4 Iu Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163.3.5 Relocation Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173.3.5.1 Successful Operation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183.3.5.2 Unsuccessful operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183.3.6 Relocation Resource Allocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183.3.6.1 Successful Operation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193.3.6.2 Unsuccessful Operation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193.3.7 Relocation Detect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193.3.8 Relocation Complete . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203.3.9 Relocation Cancel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203.3.10 SRNS Context Transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213.3.11 SRNS Data Forwarding Initiation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213.3.12 SRNS Context Forwarding from Source RNC to CN. . . . . . . . . . . . . . . 213.3.13 SRNS Context Forwarding to Target RNC from CN . . . . . . . . . . . . . . . 223.3.14 Paging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223.3.15 Common ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233.3.16 CN Invoke Trace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233.3.17 Security Mode Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233.3.17.1 Successful Operation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243.3.17.2 Unsuccessful Operation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243.3.18 Location Reporting Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243.3.19 Location Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243.3.20 Data Volume Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253.3.21 Initial UE Message. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253.3.22 Direct Transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253.3.22.1 CN Originated Direct Transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263.3.22.2 UTRAN Originated Direct Transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263.3.23 Overload Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263.3.23.1 Overload at the CN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273.3.23.2 Overload at the UTRAN. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273.3.24 Reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273.3.24.1 Reset Procedure Initiated from the CN . . . . . . . . . . . . . . . . . . . . . . . . . 283.3.24.2 Reset Procedure Initiated from the UTRAN. . . . . . . . . . . . . . . . . . . . . . 283.3.25 Error Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

4 DN05196936Issue 7-0


Id:0900d80580815502

3.3.26 CN Deactivate Trace. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293.3.27 Reset Resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293.3.27.1 Reset Resource procedure initiated from the RNC. . . . . . . . . . . . . . . . . 293.3.27.2 Reset Resource procedure initiated from the CN . . . . . . . . . . . . . . . . . . 303.3.28 RAB Modification Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303.3.29 Location Related Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303.3.29.1 Successful Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303.3.29.2 Unsuccessful Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313.3.30 Information Transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313.3.30.1 Successful Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313.3.30.2 Unsuccessful Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313.3.31 UE Specific Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313.3.31.1 Successful Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323.3.32 Direct Information Transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323.3.33 Uplink Information Exchange . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323.3.34 MBMS Session Start. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323.3.35 MBMS Session Update. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323.3.36 MBMS Session Stop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323.3.37 MBMS UE Linking. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333.3.38 MBMS Registration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333.3.39 MBMS CN De-registration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333.3.40 MBMS RAB Establishment Indication. . . . . . . . . . . . . . . . . . . . . . . . . . . 333.3.41 MBMS RAB Release. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333.4 GTP-U. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343.4.1 Echo sending . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343.5 RAB creation for multiple PDP contexts . . . . . . . . . . . . . . . . . . . . . . . . . 34

4 Elements for RANAP communication in SGSN - RNC interface . . . . . . 354.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 354.2 Message Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 354.3 Information Element Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 394.3.1 IEs Related to the Radio Network Layer. . . . . . . . . . . . . . . . . . . . . . . . . 394.3.2 IEs Related to the Transport Network Layer. . . . . . . . . . . . . . . . . . . . . . 424.3.3 IEs Related to NAS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 424.4 Message and Information Element Abstract Syntax (with ASN.1) . . . . . 444.5 Message Transfer Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 444.6 Timers and Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 444.7 Handling of Unknown, Unforeseen and Erroneous Protocol Data . . . . . 444.8 Special Procedures for RNC to RNC Communication . . . . . . . . . . . . . . 44

DN05196936Issue 7-0

5


Id:0900d80580815502

List of FiguresFigure 1 Iu interface in the SGSN (Iu over IP and Iu over ATM) . . . . . . . . . . . . . 11Figure 2 RAB Assignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Figure 3 RAB Release Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Figure 4 Iu Release Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Figure 5 Iu Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Figure 6 Relocation Preparation Successful Operation . . . . . . . . . . . . . . . . . . . . 18Figure 7 Relocation Preparation Unsuccessful Operation . . . . . . . . . . . . . . . . . . 18Figure 8 Relocation Resource Allocation Successful Operation . . . . . . . . . . . . . 19Figure 9 Relocation Resource Allocation Unsuccessful Operation . . . . . . . . . . . 19Figure 10 Relocation Detect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20Figure 11 Relocation Complete . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20Figure 12 Relocation Cancel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Figure 13 SRNS Context Transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Figure 14 SRNS Data Forwarding Initiation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Figure 15 SRNS Context Forwarding from Source RNC to CN. . . . . . . . . . . . . . . 22Figure 16 SRNS Context Forwarding to Target RNC from CN . . . . . . . . . . . . . . . 22Figure 17 Paging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22Figure 18 Common ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Figure 19 CN Invoke Trace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Figure 20 Security Mode Control Successful Operation . . . . . . . . . . . . . . . . . . . . 24Figure 21 Security Mode Control Unsuccessful Operation . . . . . . . . . . . . . . . . . . 24Figure 22 Location Reporting Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24Figure 23 Location Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25Figure 24 Data Volume Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25Figure 25 Initial UE Message. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25Figure 26 CN Originated Direct Transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26Figure 27 UTRAN Originated Direct Transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26Figure 28 Overload at the CN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27Figure 29 Overload at the UTRAN. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27Figure 30 Reset Procedure Initiated from the CN . . . . . . . . . . . . . . . . . . . . . . . . . 28Figure 31 Reset Procedure Initiated from the UTRAN. . . . . . . . . . . . . . . . . . . . . . 28Figure 32 Error Indication from CN to RNC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28Figure 33 Error Indication from RNC to CN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29Figure 34 CN Deactivate Trace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29Figure 35 Reset Resource procedure initiated from the RNC . . . . . . . . . . . . . . . . 29Figure 36 Reset Resource procedure initiated from the CN . . . . . . . . . . . . . . . . . 30Figure 37 RAB Modification Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30Figure 38 Location Related Data Successful Operation . . . . . . . . . . . . . . . . . . . . 30Figure 39 Location Related Data Unsuccessful Operation . . . . . . . . . . . . . . . . . . 31Figure 40 Information Transfer Successful Operation . . . . . . . . . . . . . . . . . . . . . . 31Figure 41 Information Transfer Unsuccessful Operation . . . . . . . . . . . . . . . . . . . . 31Figure 42 UE Specific Information Successful Operation . . . . . . . . . . . . . . . . . . . 32Figure 43 Echo sending . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

6 DN05196936Issue 7-0


Id:0900d80580815502

List of TablesTable 1 Class 1 RANAP procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Table 2 Class 2 RANAP procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Table 3 Class 3 RANAP procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

DN05196936Issue 7-0

7

SGSN - RNC Interface Description Main changes in SGSN - RNC interface

Id:0900d8058081a32c

1 Main changes in SGSN - RNC interfaceChanges between releases SG70 CD7 and SG70 CD6Changes in content

No Changes

Changes in documentation

A reference to alarm 3514 added in section Echo sending.

Changes between releases SG70 CD6 and SG70 CD2Changes in content

Echo sending is now used on the user plane.

RAB can be created for multiple PDP contexts.


SGSN-RNC interface description

Section GTP-U has been added.

Section RAB creation for multiple PDP contexts has been added.

Changes between releases SG70 CD2 and SG70Changes in content

3GPP TS 23.060 General Packet Radio Service (GPRS); Service description; Stage 2, version 5.10.0 has been upgraded to version 7.8.0.

3GPP TS 23.107 Quality of Service (QoS) concept and architecture, version 5.13.0 has been upgraded to version 7.1.0.

3GPP TS 24.008 Mobile radio interface Layer 3 specification; Core network protocols; Stage 3, version 5.12.0 has been upgraded to version 7.13.0.

3GPP TS 25.413 UTRAN Iu Interface Radio Access Network Application Part (RANAP) signalling, version 5.10.0 specification has been upgraded to version 7.9.0.



Uplink Information Exchange and MBMS RANAP overall function have been added to Section Functions of RANAP.

Tables Class 1RANAP procedures and Class 2 RANAP procedures in Section RANAP procedures have been updated.

Subsections Iu Release, Relocation Preparation, CN Invoke Trace, Location Reporting Control, Location Report, Initial UE Message, and CN Deactivate Trace in Section RANAP procedures have been updated.

New Subsections Direct Information Transfer, Uplink Information Exchange, MBMS Session Start, MBMS Session Update, MBMS Session Stop, MBMS UE Linking, MBMS Registration, MBMS CN De-registration, MBMS RAB Establishment Indication, and MBMS RAB Release have been added to Section RANAP procedures.

Elements for RANAP communication in SGSN - RNC interface

Chapter Elements for RANAP communication has been renamed to Elements for RANAP communication in SGSN - RNC interface.

8 DN05196936Issue 7-0


Id:0900d8058081a32c

Main changes in SGSN - RNC interface

Messages have been updated and new messages have been added to Section Message Contents.

Information elements in Section Information Element Definitions' Subsection IEs Related to the Radio Network Layer have been updated and new elements have been added.

New information elements have been added to Subsection IEs Related to NAS in Section Information Element Definitions.

DN05196936Issue 7-0

9

SGSN - RNC Interface Description Introduction to SGSN-RNC interface

Id:0900d8058054d8f5

2 Introduction to SGSN-RNC interfaceSGSN - RNC Interface Description defines the Iu interface of Nokia Siemens Networks SGSN in the packet-switched (PS) domain of the universal mobile telecommunications system (UMTS) network, concentrating on the radio access network application part (RANAP) protocol. The RANAP protocol is used on the signalling plane between the core network (CN) and the radio access network (RAN).

For information on the support of multipoint Iu, see 3GPP TS 23.236 Intra-domain con-nection of Radio Access Network (RAN) nodes to multiple Core Network (CN) nodes, version 5.3.0 and Feature SG02002: Multipoint Iu, Feature Description.

This interface description describes mostly how the upper layers of the Iu interface are implemented in the SGSN. The structure of the description follows the structure of the 3GPP TS 25.413 UTRAN Iu Interface Radio Access Network Application Part (RANAP) signalling, version 7.9.0 specification. To avoid repeating all the messages and details on Information Elements (IEs), this interface description is best read with the specifica-tion mentioned above at hand.

10 DN05196936Issue 7-0


Id:0900d8058081a297


3 SGSN-RNC interface description

3.1 Iu protocol stacksSignalling over the Iu interface towards RAN uses the radio access network application part (RANAP) protocol. RANAP consists of mechanisms to handle all the procedures between the core network (CN) and the UMTS terrestrial radio access network (UTRAN). RANAP can also convey messages transparently between the CN and the user equipment (UE) without being interpreted or processed by the UTRAN.

The SGSN is capable of the Iu over IP or Iu over ATM protocol stack solutions. Figure Iu interface in the SGSN (Iu over IP and Iu over ATM) shows the different protocol stacks. There can be simultaneously some RNCs with ATM stacks and other RNCs with IP stacks defined, but not towards the same RNC.

IP

SGSN

SCCP

RANAP

GTP-U

UDP

Link Layer

M3UA

SCTP

Iu

Physical Layer

Signalling

User data

IP

ATM

NNI SSCF (Q.2140)

SSCOP (Q.2110)

MTP-3b (Q.2210)

SCCP (Q.711-Q.716)

RANAP

ATM (I.361)

SDH/SONET(STM-1/STS-3c)

AAL5 (I.363)

Layer 3 GMM/SM

Iu

Signalling User data

GTP-U

UDP

IP

LLC encp (RFC 1483)

User data

RANAP radio access network application part

SCCP signalling connection control part

M3UA SS7 MTP-3 user adaptation layer SCTP stream control transport protocol

IP Internet protocol GTP-U GPRS tunnelling protocol - user plane

UDP user datagram protocol GMM/SM GPRS mobility management and session management

DN05196936Issue 7-0

11

SGSN - RNC Interface Description SGSN-RNC interface description

Id:0900d8058081a297

Figure 1 Iu interface in the SGSN (Iu over IP and Iu over ATM)

For more information on user plane, see SGSN Packet Data Transfer, Feature Descrip-tion.

The RANAP protocol is specified in 3GPP TS 25.413 UTRAN Iu Interface Radio Access Network Application Part (RANAP) signalling, version 7.9.0.

3.2 Functions of RANAPThe RANAP protocol has the following functions (functionalities in italics are not sup-ported):

• Relocating the serving radio network controller (RNC). This function enables the changing of the serving RNC functionality as well as the related Iu resources (RAB(s) and signalling connection) from one RNC to another.

• Overall radio access bearer (RAB) management. This function is responsible for setting up, modifying and releasing RABs.

• Queuing the setup of RAB. The purpose of this function is to allow placing some requested RABs into a queue, and indicate the peer entity about queuing.

• Requesting a RAB release. While the overall RAB management is a function of the CN, the UTRAN has the capability to request the release of a RAB.

• Release of all Iu connection resources. This function is used to explicitly release all the resources related to one Iu connection.

• Requesting the release of all Iu connection resources. While the Iu release is managed from the CN, the RNC has the capability to request the release of all Iu connection resources from the corresponding Iu connection.

• Serving radio network subsystem (SRNS) Context Forwarding function. This function is responsible for transferring SRNS context from the RNC to the CN for the inter-system change in case of packet forwarding.

• Controlling overload in the Iu interface. This function allows the adjustment of load in the Iu interface.

g Receiving overload has no impact on the signalling load. Overload messages may, however, be sent by the SGSN.

• Resetting the Iu. This function is used for resetting an Iu interface. • Sending the UE Common Id (permanent NAS UE identity) to the RNC. This function

makes the RNC be aware of the UE's Common Id. • Paging the user. This function provides capability for the CN to page the UE.

MTP-3b message transfer part level 3 for broadband networks

NNI SSCF service specific coordination function - network node interface

SSCOP service specific connection oriented protocol

LLC encp logical link control layer encapsulation

AAL5 ATM adaptation layer type 5 ATM asynchronous transfer mode

SDH (STM-1)

synchronous digital hierarchy (synchronous transport module 1)

SONET (STS-3c)

synchronous optical network (synchro-nous transport signal, level 3, concate-nated)

12 DN05196936Issue 7-0


Id:0900d8058081a297


• Controlling the trace of the subscriber or user equipment activity. This function allows setting the trace mode for a given subscriber or user equipment. This function also allows the deactivation of a previously established trace.

• Transport of non-access stratum (NAS) information between the UE and the CN. This function has two subclasses:1. Transport of the initial NAS signalling message from the UE to the CN. This

function transparently transfers NAS information. As a consequence, also the Iu signalling connection is set up.

2. Transport of NAS signalling messages between the UE and the CN. This function transparently transfers NAS signalling messages on the existing Iu sig-nalling connection. It also includes a specific service to handle signalling messages differently.

• Controlling the security mode in the UTRAN. This function is used to send the security keys (ciphering and integrity protection) to the UTRAN, and to set the oper-ation mode for security functions.

• Controlling location reporting. This function allows the CN to set the mode in which the UTRAN reports the location of the UE.

• Location reporting. This function is used for transferring the actual location informa-tion from the RNC to the CN.

• Data volume reporting function. This function is responsible for reporting unsuccess-fully transmitted downlink (DL) data volume over the UTRAN for specific RABs.

• Reporting general error situations. This function allows the reporting of general error situations, for which function specific error messages have not been defined.

• Location-related data. This function allows the CN either to retrieve the deciphering keys (to be forwarded to the UE) for the assistance data broadcasted from the RNC, or to request the RNC to deliver dedicated assistance data to the UE.

• Information transfer function. This function allows the configuration data to be passed from the CN to the RNC upon a CN trigger. This function is operated in acknowledged mode. It should be used by the CN to maintain the alignment between the data as configured in the CN and the configuration data provided to the UTRAN. It may be used, for example, to coordinate the short number addressing (SNA) geographical definition (LA to SNA mapping) between the CN and the UTRAN in order to apply access control on an SNA basis.

• Uplink Information Exchange. This function allows the RNC to transfer or request information to the CN. For instance the RNC has the capability to request MBMS specific information to the CN, for example the Multicast Service lists for a given UE or the IP Multicast Address and APN for one or several MBMS Bearer Services.

• MBMS RANAP overall function. This function allows the following different sub-func-tions: • MBMS RAB management. This function is responsible for setting up, updating

and releasing the MBMS RAB as well as the MBMS Iu signalling connection cor-responding to one MBMS Session. The MBMS RAB is defined for the CN PS domain only.

• MBMS CN (PS domain) de-registration. This function makes the RNC aware that a given Multicast Service is no longer available.

• MBMS UE linking/de-linking. This function makes the RNC aware that a given UE, with existing Iu-ps signalling connection, has joined/left some Multicast Ser-vice(s).

DN05196936Issue 7-0

13


Id:0900d8058081a297

• Requesting MBMS Service registration/de-registration. While the overall MBMS CN de-registration is a function of the CN (PS domain), the RNC has the capa-bility to register/de-register to a specific Multicast Service.

3.3 RANAP proceduresThe RANAP procedures are divided into three classes depending on the number of response messages there can be. Class 1 procedures have exactly one response message, Class 2 procedures have no response messages and Class 3 procedures have at least one response message.

g Procedures marked with (*) are not supported.

Elementary Proce-dure Initiating Message

Successful Out-come/Response Message

Unsuccessful Out-come/Response Message

Iu Release IU RELEASE COMMAND IU RELEASE COMPLETE

Relocation Preparation RELOCATION REQUIRED

RELOCATION COMMAND

RELOCATION PREPA-RATION FAILURE

Relocation Resource Allocation

RELOCATION REQUEST

RELOCATION REQUEST ACKNOWL-EDGE

RELOCATION FAILURE

Relocation Cancel RELOCATION CANCEL RELOCATION CANCEL ACKNOWLEDGE

SRNS Context Transfer

SRNS CONTEXT REQUEST

SRNS CONTEXT RESPONSE

Security Mode Control SECURITY MODE COMMAND

SECURITY MODE COMPLETE

SECURITY MODE REJECT

Data Volume Report (*) DATA VOLUME REPORT REQUEST

DATA VOLUME REPORT

Reset RESET RESET ACKNOWL-EDGE

Reset Resource RESET RESOURCE RESET RESOURCE ACKNOWLEDGE

Location Related Data (*)

LOCATION RELATED DATA REQUEST

LOCATION RELATED DATA RESPONSE

LOCATION RELATED DATA FAILURE

Information Transfer (*) INFORMATION TRANSFER INDICA-TION

INFORMATION TRANSFER CONFIRMA-TION

INFORMATION TRANSFER FAILURE

Uplink Information Exchange (*)

UPLINK INFORMATION EXCHANGE REQUEST

UPLINK INFORMATION EXCHANGE RESPONSE

UPLINK INFORMATION EXCHANGE FAILURE

MBMS Session Start (*)

MBMS SESSION START MBMS SESSION START RESPONSE

MBMS SESSION START FAILURE

MBMS Session Update (*)

MBMS SESSION UPDATE

MBMS SESSION UPDATE RESPONSE

MBMS SESSION UPDATE FAILURE

Table 1 Class 1 RANAP procedures

14 DN05196936Issue 7-0


Id:0900d8058081a297


MBMS Session Stop (*)

MBMS SESSION STOP REQUEST

MBMS SESSION STOP RESPONSE

MBMS UE Linking (*) MBMS UE LINKING REQUEST

MBMS UE LINKING RESPONSE

MBMS Registration (*) MBMS REGISTRATION REQUEST

MBMS REGISTRATION RESPONSE

MBMS REGISTRATION FAILURE

MBMS CN De-Regis-tration (*)

MBMS CN DE-REGIS-TRATION REQUEST

MBMS CN DE-REGIS-TRATION RESPONSE

MBMS RAB Release (*)

MBMS RAB RELEASE REQUEST

MBMS RAB RELEASE MBMS RAB RELEASE FAILURE

Elementary Proce-dure Initiating Message

Successful Out-come/Response Message

Unsuccessful Out-come/Response Message

Table 1 Class 1 RANAP procedures (Cont.)

Elementary Procedure Initiating Message

RAB modification Request RAB MODIFY REQUEST

RAB Release Request RAB RELEASE REQUEST

Iu Release Request IU RELEASE REQUEST

Relocation Detect RELOCATION DETECT

Relocation Complete RELOCATION COMPLETE

SRNS Data Forwarding Initiation SRNS DATA FORWARD COMMAND

SRNS Context Forwarding from Source RNC to CN FORWARD SRNS CONTEXT

SRNS Context Forwarding to Target RNC from CN FORWARD SRNS CONTEXT

Paging PAGING

Common ID COMMON ID

CN Invoke Trace CN INVOKE TRACE

CN Deactivate Trace CN DEACTIVATE TRACE

Location Reporting Control LOCATION REPORTING CONTROL

Location Report LOCATION REPORT

Initial UE Message INITIAL UE MESSAGE

Direct Transfer DIRECT TRANSFER

Overload Control OVERLOAD

Error Indication ERROR INDICATION

UE Specific Information (*) UE SPECIFIC INFORMATION INDICATION

Direct Information Transfer (*) DIRECT INFORMATION TRANSFER

MBMS RAB Establishment Indication (*) MBMS RAB ESTABLISHMENT INDICATION


DN05196936Issue 7-0

15


Id:0900d8058081a297

3.3.1 RAB AssignmentThe 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. The procedure uses connection-oriented signalling.

Figure 2 RAB Assignment

Due to SGSN restrictions, the SGSN supports four simultaneous RABs for each UE.

Quality of Service (QoS) parameters are supported according to 3GPP TS 23.107 Quality of Service (QoS) concept and architecture, version 7.1.0.

Service Data Unit (SDU) parameters: there is always one subflow used, the SDU Information parameter is never included.

Queuing RABs is never allowed.

The pre-emption capability is always set to 'shall not trigger pre-emption'.

The pre-emption vulnerability is always set to 'pre-emptable'.

The Relocation Requirement is always set to 'None'.

The NAS Synchronisation Indicator is never included in a RAB Assignment message.

The handover is always set to 'Handover to GSM should not be performed'.

The User Plane Mode is always set to 'Transparent Mode'.

The IP addresses from the SGSN side are IPv4/IPv6 addresses.

Only IP is allowed as a PDP type.

The alternative RAB parameter values are included with the value 'unspecified'.

3.3.2 RAB Release RequestThe purpose of the RAB Release Request procedure is to enable the UTRAN to request the release of one or several RABs. The procedure uses connection-oriented signalling.

Elementary Procedure Initiating Message Outcome

RAB Assignment RAB ASSIGNMENT REQUEST RAB ASSIGNMENT RESPONSE x N (N>=1)


RNC CN

RAB ASSIGNMENT RESPONSE

RAB ASSIGNMENT REQUEST

* it can be several responses

*

16 DN05196936Issue 7-0


Id:0900d8058081a297


Figure 3 RAB Release Request

If procedure collision (or other error) is not detected by the SGSN, it initiates the RAB Assignment (release) procedure when it receives a RAB Release Request message.

3.3.3 Iu Release RequestThe 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 connec-tion release' or 'Radio Connection With UE Lost'). The procedure uses connection-oriented signalling.

Figure 4 Iu Release Request

If procedure collision (or other error) is not detected by the SGSN, it initiates the Iu Release procedure when it receives an Iu Release Request message.

3.3.4 Iu ReleaseThe purpose of the Iu Release procedure is to enable the CN to release the Iu connec-tion and all the UTRAN resources related only to that Iu connection to be released. The procedure uses connection-oriented signalling.

The Iu Release procedure can be initiated for at least the following reasons:

• Completion of a transaction between the UE and the CN. • UTRAN-generated reasons, for example the reception of an IU RELEASE

REQUEST message. • Completion of a successful SRNS relocation. • Cancellation of a relocation after the successful completion of the Relocation

Resource Allocation procedure. • Detection of two Iu connections in the same domain toward one UE.

RNC CN

RAB RELEASE REQUEST

RNC CN

IU RELEASE REQUEST

DN05196936Issue 7-0

17


Id:0900d8058081a297

Figure 5 Iu Release

The SGSN has a configurable timer to release the Iu connection. This functionality can also be disabled. The Iu release timer is used for situations where the subscriber makes an attach or a RAU, and using the follow on pending parameter in the Attach/RAU Request message, informs the SGSN that they want to keep the Iu connection active after the attach/RAU. At that point, the Iu release timer is activated in the SGSN. If, during the time set in the Iu release timer, there is no signalling from the subscriber towards the SGSN, the SGSN releases the Iu connection.

The value of the Iu release timer is not valid, for example, in the following cases:

• the SGSN releases the last RAB from the subscriber using the RAB Release proce-dure

• the SGSN removes the last RAB from the subscriber because of a PDP context deactivation

In these situations, the Iu connection is released immediately when the last RAB has been released or other signalling procedure related to it has been performed.

3.3.5 Relocation PreparationThe purpose of the Relocation Preparation procedure is to prepare the relocation of the SRNS either with involving the UE or without involving it. The relocation procedure is coordinated in all Iu signalling connections that exist for the UE in order to allow Relo-cation coordination in the target RNC. The procedure uses connection-oriented signal-ling.

The source RNC does not initiate the Relocation Preparation procedure for an Iu signal-ling connection in the following cases:

• Prepared Relocation exists in the RNC for that Iu signalling connection • Relocation Preparation procedure is ongoing for that Iu signalling connection • In the case of a MOCN configuration if the Rerouting Function is ongoing

RNC CN

IU RELEASE COMPLETE

IU RELEASE COMMAND

18 DN05196936Issue 7-0


Id:0900d8058081a297


3.3.5.1 Successful Operation

Figure 6 Relocation Preparation Successful Operation

g Inter-system SRNS relocation for the PS domain will always fail. It is assumed that the RNC does not initiate the serving radio network controller (SRNC) relocation in a UMTS-GSM inter-system change.

MS Classmark 2, MS Classmark 3 and Old BSS To New BSS Information is always ignored.

3.3.5.2 Unsuccessful operation

Figure 7 Relocation Preparation Unsuccessful Operation

3.3.6 Relocation Resource AllocationThe purpose of the Relocation Resource Allocation procedure is to allocate resources from the target RNS to the relocation of the SRNS. The procedure is coordinated in all Iu signalling connections existing for the UE. The procedure uses connection-oriented signalling.

SourceRNC

CN

RELOCATION COMMAND

RELOCATION REQUIRED

SourceRNC

CN

RELOCATION

PREPARATION FAILURE

RELOCATION REQUIRED

DN05196936Issue 7-0

19


Id:0900d8058081a297


Figure 8 Relocation Resource Allocation Successful Operation

Queuing RABs is never allowed.

The pre-emption capability is always set to 'shall not trigger pre-emption'.

The pre-emption vulnerability is always set to 'pre-emptable'.

The QoS parameters are supported according to 3GPP TS 23.107 Quality of Service (QoS) concept and architecture, version 7.1.0.

The SDU parameters: there is always one subflow used, the SDU Information parameter is never included.

The Relocation Requirement is always set to 'None'.

The NAS Synchronisation Indicator is never included in a Relocation Request message.

The Service Handover is always set to 'Handover to GSM should not be performed'. Please note that in an inter-SGSN SRNS relocation case the new SGSN currently selects this IE by itself as the information is not carried by the GTP message 'Forward Relocation Request'.

The User Plane Mode is always set to 'Transparent Mode'.

The IP addresses from the SGSN side are IPv4/IPv6 addresses.

Only IP is allowed as a PDP type.

The alternative RAB parameter values are included with the value 'unspecified'.

3.3.6.2 Unsuccessful Operation

Figure 9 Relocation Resource Allocation Unsuccessful Operation

3.3.7 Relocation DetectThe purpose of the Relocation Detect procedure is to get indicated the detection of the SRNS relocation execution to the CN by the RNC. The procedure is coordinated in all

TargetRNC

CN

RELOCATION

REQUEST ACKNOWLEDGE

RELOCATION REQUEST

TargetRNC

CN

RELOCATION FAILURE

RELOCATION REQUEST

20 DN05196936Issue 7-0


Id:0900d8058081a297


Iu signalling connections existing for the UE. The procedure uses connection-oriented signalling.

Figure 10 Relocation Detect

The SGSN updates the packet data protocol (PDP) contexts to the gateway GPRS support node (GGSN) when a Relocation Complete message is received.

3.3.8 Relocation CompleteThe purpose of the Relocation Complete procedure is to get indicated the completion of the SRNS relocation to the CN by the target RNC. The procedure is coordinated in all Iu signalling connections existing for the UE. The procedure uses connection-oriented signalling.

Figure 11 Relocation Complete

The SGSN updates the PDP contexts to the GGSN when a Relocation Complete message is received (not on Relocation Detect).

3.3.9 Relocation CancelThe purpose of the Relocation Cancel procedure is to enable the source RNC to cancel an ongoing relocation of the SRNS. The Relocation Cancel procedure may be initiated by the source RNC during and after the Relocation Preparation procedure if either of the following criteria are met:

• The source RNC has not yet initiated the execution of the SRNS relocation, neither through the Iur interface nor through the Uu interface.

• After having initiated the execution of the SRNS relocation, the UE has returned to the source RNC by transmitting a radio resource control (RRC) message which indi-cates that the UE considers the source RNC as its serving RNC.

The procedure is coordinated in all Iu signalling connections for which the Relocation Preparation procedure has been initiated. The procedure uses connection-oriented sig-nalling.

TargetRNC

CN

RELOCATION DETECT

TargetRNC

CN

RELOCATION COMPLETE

DN05196936Issue 7-0

21


Id:0900d8058081a297

Figure 12 Relocation Cancel

3.3.10 SRNS Context TransferThe 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) in case of an inter-system change, or in some further cases described in 3GPP TS 23.060 General Packet Radio Service (GPRS); Service description; Stage 2, version 7.8.0. The procedure uses con-nection-oriented signalling.

Figure 13 SRNS Context Transfer

3.3.11 SRNS Data Forwarding InitiationThe 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) in case of an inter-system change or in some further cases described in 3GPP TS 23.060. The pro-cedure uses connection-oriented signalling.

Figure 14 SRNS Data Forwarding Initiation

3.3.12 SRNS Context Forwarding from Source RNC to CNThe 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) in case of a handover through the CN. The procedure uses connection-oriented signalling. SRNS

SourceRNC

CN

RELOCATION

CANCEL ACKNOWLEDGE

RELOCATION CANCEL

RNC CN

SRNS CONTEXT RESPONSE

SRNS CONTEXT REQUEST

RNC CN

SRNS DATA FORWARD COMMAND

22 DN05196936Issue 7-0


Id:0900d8058081a297


contexts are sent to each concerned RAB among those that are supported by the target system, and for which at least either a GPRS tunnelling protocol - protocol data unit (GTP-PDU) or a packet data convergence protocol (PDCP) sequence numbering is available. The contexts contain the sequence numbers of the GTP-PDUs to be transmit-ted next in the uplink and downlink directions, if available, and the PDCP sequence numbers that would have been used next to send and receive data from the UE, if avail-able.

Figure 15 SRNS Context Forwarding from Source RNC to CN

3.3.13 SRNS Context Forwarding to Target RNC from CNThe 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 in case of a handover through the CN. The procedure uses connection-oriented signalling. SRNS contexts are sent for each referenced RAB for which at least either a GTP-PDU or a PDCP sequence numbering is available. The contexts contain the sequence numbers of the GTP-PDUs to be transmitted next in the uplink and downlink directions, if avail-able, and the PDCP sequence numbers that would have been used next to send and receive data from the UE, if available.

Figure 16 SRNS Context Forwarding to Target RNC from CN

3.3.14 PagingThe purpose of the Paging procedure is to enable the CN to request the UTRAN to contact the UE. The procedure uses connectionless signalling.

Figure 17 Paging

Packet temporary mobile subscriber identity (P-TMSI) IE is included, if available.

SourceRNC

CN

FORWARD SRNS CONTEXT

TargetRNC

CN

FORWARD SRNS CONTEXT

RNC CN

PAGING

DN05196936Issue 7-0

23


Id:0900d8058081a297

3.3.15 Common IDThe purpose of the Common ID procedure is to inform the RNC about the permanent NAS UE Identity (that is, IMSI) of a user. It is used by the RNC, for example, to create a reference between the permanent NAS UE identity of the user and the RRC connection of that user for UTRAN paging coordination. The procedure uses connection-oriented signalling.

Figure 18 Common ID

3.3.16 CN Invoke TraceWhen used for signalling based activation, the purpose of the CN Invoke Trace proce-dure is to inform the RNC that it should begin a trace session with the parameters indi-cated by the CN and related to the UE, the Iu connection is used for. When used for management based activation, the purpose of the CN Invoke Trace procedure is to provide the RNC with the equipment identity of the UE for which the RNC should begin a trace recording session.. The procedure uses connection-oriented signalling.

Figure 19 CN Invoke Trace

3.3.17 Security Mode ControlThe 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 param-eters, and also to store the appropriate parameters for the integrity algorithm. The pro-cedure uses connection-oriented signalling.

RNC CN

COMMON ID

RNC CN

CN INVOKE TRACE

24 DN05196936Issue 7-0


Id:0900d8058081a297



Figure 20 Security Mode Control Successful Operation


Figure 21 Security Mode Control Unsuccessful Operation

3.3.18 Location Reporting ControlThe purpose of the Location Reporting Control procedure is to allow the CN to request information on the location and optionally velocity of a given UE. The procedure uses connection-oriented signalling.

Figure 22 Location Reporting Control

The SGSN uses this procedure to locate the subscriber. The procedure is also used to receive the service area identifier (SAI) from the SRNS after relocation.

3.3.19 Location ReportThe purpose of the Location Report procedure is to provide information on the location and optionally velocity of the UE to the CN. The procedure uses connection-oriented sig-nalling.

RNC CN

SECURITY MODE COMPLETE

SECURITY MODE COMMAND

RNC CN

SECURITY MODE REJECT

SECURITY MODE COMMAND

RNC CN

LOCATION REPORTING CONTROL

DN05196936Issue 7-0

25


Id:0900d8058081a297

Figure 23 Location Report

3.3.20 Data Volume ReportThe Data Volume Report procedure is used by the CN to request the unsuccessfully transmitted DL data volume for some specific RABs. This procedure only applies to the PS domain. The procedure uses connection-oriented signalling.

g According to 3GPP TS 32.200 Telecommunication management; Charging manage-ment; Charging principles, version 5.8.0 this procedure is not used, and the RNC should ignore a DATA VOLUME REPORT REQUEST message if received.

Figure 24 Data Volume Report

Data Volume Report procedure is not supported.

3.3.21 Initial UE MessageThe purpose of the Initial UE Message procedure is to establish an Iu signalling connec-tion between a CN domain and the RNC, and to transfer the initial NAS-PDU to the default CN node, or to be used for the Rerouting Function in case of MOCN configura-tion. The procedure uses connection-oriented signalling.

Figure 25 Initial UE Message

3.3.22 Direct TransferThe purpose of the Direct Transfer procedure is to carry UE-CN signalling messages over the Iu interface. The UE-CN signalling messages are not interpreted by the

RNC CN

LOCATION REPORT

RNC CN

DATA VOLUME REPORT

DATA VOLUME REPORT REQUEST

RNC CN

INITIAL UE MESSAGE

26 DN05196936Issue 7-0


Id:0900d8058081a297


UTRAN, and their content (for example Mobility Management or Call Control message) is outside the scope of this document. For more information see 3GPP TS 24.008 Mobile radio interface Layer 3 specification; Core network protocols; Stage 3, version 7.13.0. The UE-CN signalling messages are transported as parameters in the DIRECT TRANSFER messages. The procedure uses connection-oriented signalling.

3.3.22.1 CN Originated Direct Transfer

Figure 26 CN Originated Direct Transfer

3.3.22.2 UTRAN Originated Direct Transfer

Figure 27 UTRAN Originated Direct Transfer

3.3.23 Overload ControlThis procedure is defined to provide a certain degree of signalling flow control. At the UTRAN 'Processor Overload' and 'Overload in the Capability to Send Signalling Messages to the UE' are handled, and at the CN 'Processor Overload' is handled. The procedure uses connectionless signalling.

The philosophy used is to stem the traffic at the source with the known effects on the service.

The algorithm used at the CN side:

• If TigOC is not running, and an OVERLOAD message or 'Signalling Point Congested' information is received, the traffic should be reduced by one step. It is also possible, optionally, to indicate the number of steps to reduce the traffic within the Number of Steps IE. At the same time timers TigOC and TinTC should be started.

• During TigOC all received OVERLOAD messages or 'Signalling Point Congested' information should be ignored.

• This step-by-step reduction of traffic should be continued until the maximum reduc-tion is obtained with the last step.

• If TinTC expires (that is, no OVERLOAD message or 'Signalling Point Congested' information is received during TinTC), the traffic should be increased by one step, and TinTC should be started unless normal load has been resumed.

The algorithm used at the UTRAN side:

RNC CN

DIRECT TRANSFER

RNC CN

DIRECT TRANSFER

DN05196936Issue 7-0

27


Id:0900d8058081a297

• If TigOR is not running, and an OVERLOAD message or 'Signalling Point Congested' information is received, the traffic should be reduced by one step. It is also possible, optionally, to indicate the number of steps to reduce the traffic within the Number of Steps IE. At the same time timers TigOR and TinTR should be started.

• During TigOR all received OVERLOAD messages or 'Signalling Point Congested' information should be ignored.

• This step-by-step reduction of traffic should be continued until the maximum reduc-tion is obtained with the last step.

• If TinTR expires (that is, no OVERLOAD message or 'Signalling Point Congested' information is received during TinTR), the traffic should be increased by one step, and TinTR should be started unless normal load has been resumed.

The number of steps and the method of reducing the load are considered to be an imple-mentation-specific function. There may be other traffic control mechanisms from O&M activities occurring simultaneously.

These principles with traffic increase/decrease and timers are not fully implemented in the SGSN. The received overload messages are ignored in the SGSN. Overload control is used in parallel with the Overload Control feature. For more information, see Feature SG01037: Overload Control, Feature Description.

3.3.23.1 Overload at the CN

Figure 28 Overload at the CN

3.3.23.2 Overload at the UTRAN

Figure 29 Overload at the UTRAN

Currently, receiving an Overload message in the SGSN has no impact on the signalling traffic load.

3.3.24 ResetThe purpose of the Reset procedure is to initialise the UTRAN in case of a failure in the CN or vice versa. The procedure uses connectionless signalling.

RNC CN

OVERLOAD

RNC CN

OVERLOAD

28 DN05196936Issue 7-0


Id:0900d8058081a297


3.3.24.1 Reset Procedure Initiated from the CN

Figure 30 Reset Procedure Initiated from the CN

When the SGSN restarts, it sends Reset messages to all known RNCs.

3.3.24.2 Reset Procedure Initiated from the UTRAN

Figure 31 Reset Procedure Initiated from the UTRAN

3.3.25 Error IndicationThe Error Indication procedure is initiated by a node to report the detected errors in one incoming message, provided that they cannot be reported by an appropriate failure message.

If an error situation arises due to the reception of a message utilising dedicated signal-ling, the Error Indication procedure uses connection-oriented signalling. Otherwise the procedure uses connectionless signalling.

Figure 32 Error Indication from CN to RNC

RNC CN

RESET ACKNOWLEDGE

RESET

RNC CN

RESET ACKNOWLEDGE

RESET

RNC CN

ERROR INDICATION

DN05196936Issue 7-0

29


Id:0900d8058081a297

Figure 33 Error Indication from RNC to CN

Currently, receiving an Error indication message in the SGSN has no impact.

3.3.26 CN Deactivate TraceThe purpose of the CN Deactivate Trace procedure is to inform the RNC to stop the trace session, initiated by a signalling based activation, for the indicated trace reference and related to the UE the Iu connection is used for. The procedure uses connection-oriented signalling.

Figure 34 CN Deactivate Trace

3.3.27 Reset ResourceThe purpose of the Reset Resource procedure is to initialise a part of the UTRAN in case of an abnormal failure in the CN or vice versa. The procedure uses connectionless sig-nalling.

3.3.27.1 Reset Resource procedure initiated from the RNC

Figure 35 Reset Resource procedure initiated from the RNC

RNC CN

ERROR INDICATION

RNC CN

CN DEACTIVATE TRACE

RNC CN

RESET RESOURCE ACKNOWLEDGE

RESET RESOURCE

30 DN05196936Issue 7-0


Id:0900d8058081a297


3.3.27.2 Reset Resource procedure initiated from the CN

Figure 36 Reset Resource procedure initiated from the CN

3.3.28 RAB Modification RequestThe purpose of the RAB Modification procedure is to allow the RNC to initiate the rene-gotiation of RABs for a given UE after a RAB establishment. The procedure uses con-nection-oriented signalling.

Figure 37 RAB Modification Request

3.3.29 Location Related DataThe purpose of the Location Related Data procedure is to provide the means to handle additional location-related requests over the Iu interface: the procedure allows the CN either to retrieve the deciphering keys (to be forwarded to the UE) for the assistance data broadcasted from the RNC, or to request the RNC to deliver dedicated assistance data to the UE. The procedure uses connection-oriented signalling.

Location Related Data procedures are not supported.


Figure 38 Location Related Data Successful Operation

RNC CN

RESET RESOURCE ACKNOWLEDGE

RESET RESOURCE

RNC CN

RAB MODIFY REQUEST

RNC CN

LOCATION RELATED

DATA RESPONSE

LOCATION RELATED

DATA REQUEST

DN05196936Issue 7-0

31


Id:0900d8058081a297


Figure 39 Location Related Data Unsuccessful Operation

3.3.30 Information TransferThe purpose of the Information Transfer procedure is to transfer information from the CN to the RNC. This procedure uses connectionless signalling.

Information Transfer procedures are not supported.


Figure 40 Information Transfer Successful Operation


Figure 41 Information Transfer Unsuccessful Operation

3.3.31 UE Specific InformationThe purpose of the UE Specific Information procedure is to transfer data related to a par-ticular UE and a particular communication from the CN to the RNC. The procedure uses connection-oriented signalling.

RNC CN

LOCATION RELATED

DATA FAILURE

LOCATION RELATED

DATA REQUEST

RNC CN

INFORMATION

TRANSFER CONFIRMATION

INFORMATION

TRANSFER INDICATION

RNC CN

INFORMATION

TRANSFER FAILURE

INFORMATION

TRANSFER INDICATION

32 DN05196936Issue 7-0


Id:0900d8058081a297


UE Specific Information procedure is not supported.


Figure 42 UE Specific Information Successful Operation

3.3.32 Direct Information TransferThe purpose of the Direct Information Transfer procedure is to transfer some information from the RNC to the CN or vice versa in unacknowledged mode. This procedure uses connectionless signalling.

Direct Information Transfer procedure is not supported.

3.3.33 Uplink Information ExchangeThe purpose of the Uplink Information Exchange procedure is to transfer or request some information to the CN. This procedure uses connectionless signalling.

Uplink Information Exchange procedure is not supported.

3.3.34 MBMS Session StartThe purpose of the MBMS Session Start procedure is to request the UTRAN to notify UEs about an up-coming MBMS Session of a given MBMS Bearer Service and to estab-lish a MBMS RAB and MBMS Iu signalling connection for this MBMS Session. The MBMS Session Start procedure is triggered by the CN (PS domain). The procedure uses connection oriented signalling.

MBMS Session Start procedure is not supported.

3.3.35 MBMS Session UpdateThe purpose of the MBMS Session Update procedure is to inform the RNC during a MBMS Session whenever the RA List of Idle Mode UEs changes compared to one pre-viously sent. The MBMS Session Update procedure is triggered by the CN (PS domain). The procedure uses connection oriented signalling.

MBMS Session Update procedure is not supported.

3.3.36 MBMS Session StopThe purpose of the MBMS Session Stop procedure is to request the UTRAN to notify UEs about the end of a given MBMS Session and to release the corresponding MBMS RAB and MBMS Iu signalling connection for this MBMS Session. The MBMS RAB Session Stop procedure may also be used as the last MBMS session stop to make the RNC aware that a certain Multicast Service is no longer available. The MBMS Session

RNC CN

UE SPECIFIC

INFORMATION INDICATION

DN05196936Issue 7-0

33


Id:0900d8058081a297

Stop procedure is triggered by the CN (PS domain). The procedure uses connection-oriented signalling.

MBMS Session Stop procedure is not supported.

3.3.37 MBMS UE LinkingThe purpose of the MBMS UE Linking procedure is to make the RNC aware that a given UE, with existing Iu-ps signalling connection, joined and/or left one or several Multicast Services. The procedure uses connection oriented signalling.

MBMS UE Linking procedure is not supported.

3.3.38 MBMS RegistrationThe purpose of the MBMS Registration procedure is to request the CN (PS domain) to register or de-register the RNC for a certain Multicast Service. The procedure uses con-nectionless signalling, unless the procedure is used to request CN to de-register the RNC for a Multicast Service which has an existing Iu signalling connection towards the RNC, for example during a MBMS Session. In this last case, the procedure uses con-nection-oriented signalling.

MBMS Registration procedure is not supported.

3.3.39 MBMS CN De-registrationThe purpose of the MBMS CN De-registration procedure is to make the RNC aware that a certain Multicast Service is no longer available. The MBMS CN De-registration proce-dure is triggered by the CN (PS domain). The procedure uses connectionless signalling.

MBMS CN De-registration procedure is not supported.

3.3.40 MBMS RAB Establishment IndicationThe purpose of the MBMS RAB Establishment Indication procedure is to inform the CN (PS domain) of the establishment of the MBMS RAB corresponding to the MBMS Iu sig-nalling connection used for this procedure. The procedure uses connection oriented sig-nalling.

MBMS RAB Establishment Indication procedure is not supported.

3.3.41 MBMS RAB ReleaseThe purpose of the MBMS RAB Release procedure is to enable the UTRAN to request the release of an MBMS RAB. The MBMS RAB is defined for the PS domain only. The procedure uses connection oriented signalling.

MBMS RAB Release procedure is not supported.

34 DN05196936Issue 7-0


Id:0900d8058081a297


3.4 GTP-U

3.4.1 Echo sending

Figure 43 Echo sending

Echo Request messages are sent for each path in use to find out if the peer RNC is alive.

If the RNC does not respond to an echo request during T3-RESPONSE seconds, Nokia Siemens Networks SGSN resends the echo request for N3-REQUEST times and if there is no response, all existing RABs to this RNC are deactivated from the SGSN and the alarm 3514 RNC unavailable is set.

g If the Direct Tunnel feature is in use, RNC Echo sending must be disabled with the PRFILE parameter 2:1501 by setting it to value 3. This is because RNCs do not usually respond to echo requests when the Direct Tunnel feature is in use.

3.5 RAB creation for multiple PDP contextsWhen subscriber has multiple PDP contexts and downlink data is to be sent for one or more of the PDP contexts, SGSN establishes one or more RABs only for the PDP con-text(s) needing one.

The same applies to the uplink case, if UE indicates to the SGSN which PDP contexts need a RAB. If indication is not given, all RABs are established.

RNC CN

ECHO RESPONSE

ECHO REQUEST

DN05196936Issue 7-0

35

SGSN - RNC Interface Description Elements for RANAP communication in SGSN - RNCinterface

Id:0900d805805656c7

4 Elements for RANAP communication in SGSN - RNC interfaceThis chapter contains additional information to the procedures defined in 3GPP TS 25.413 UTRAN Iu Interface Radio Access Network Application Part (RANAP) Signalling, version 7.9.0. If only the name of the procedure is listed, no additional information is needed.

4.1 GeneralUE-Specific Behaviour Information (UESBI)-Iu is currently not supported.

Global CN-ID is supported when the Multipoint Iu feature has been activated and it has been configured properly. For more information, see Feature SG02002: Multipoint Iu, Feature Description.

Redirect Attempt Flag, Redirection Indication, Redirection Completed and Selected PLMN Identity are supported when the Multi Operator Core Network (MOCN) feature has been activated and it has been configured properly. For more information, see SGSN Network Sharing, Feature Description.

The SGSN supports both IPv4 and IPv6 IP addresses.

4.2 Message Contents • RAB ASSIGNMENT REQUEST

Due to SGSN restrictions the SGSN supports four simultaneous RABs per UE.Queuing RABs is never allowed.The pre-emption capability is always set to 'shall not trigger pre-emption'.The pre-emption vulnerability is always set to 'pre-emptable'.The QoS parameters are supported according to 3GPP TS 23.107 Quality of Service (QoS) concept and architecture, version 7.1.0.The SDU parameters: there is always one subflow used, the SDU Information parameter is never included.The Relocation Requirement is always set to 'None'.The NAS Synchronisation Indicator is never included in a RAB Assignment message.The Service Handover is always set to 'Handover to GSM should not be performed'.The User Plane Mode is always set to 'Transparent Mode'.Only IP is allowed as a PDP type.

• RAB ASSIGNMENT RESPONSEDue to SGSN restrictions the SGSN supports four simultaneous RABs per UE.Queuing RABs is never allowed.

• RAB RELEASE REQUEST • IU RELEASE REQUEST • IU RELEASE COMMAND • IU RELEASE COMPLETE • RELOCATION REQUIRED

36 DN05196936Issue 7-0


Id:0900d805805656c7


g Inter-system SRNS relocation for PS will always fail.

MS Classmark 2, MS Classmark 3, Old BSS To New BSS Information, and Source BSS To Target BSS Transparent Container is always ignored.

• RELOCATION REQUESTQueuing RABs is never allowed.The pre-emption capability is always set to 'shall not trigger pre-emption'.The pre-emption vulnerability is always set to 'pre-emptable'.The QoS parameters are supported according to 3GPP TS 23.107 Quality of Service (QoS) concept and architecture, version 7.1.0.The SDU parameters: there is always one subflow used, the SDU Information parameter is never included.The Relocation Requirement is always set to 'None'.The NAS Synchronisation Indicator is never included in a Relocation Request message.The Service Handover is always set to 'Handover to GSM should not be performed'. Please note that in case of an inter-SGSN SRNS relocation the new SGSN currently selects this IE by itself as the information is not carried by the 'Forward Relocation Request' GTP message.The User Plane Mode is always set to 'Transparent Mode'.Only IP is allowed as a PDP type.The CN MBMS Linking Information is never included in a Relocation Request message.

• RELOCATION REQUEST ACKNOWLEDGE • RELOCATION COMMAND

Layer 3 (L3) Information is not included.Target BSS to Source BSS Transparent Container is not included.

• RELOCATION DETECT • RELOCATION COMPLETE • RELOCATION PREPARATION FAILURE • RELOCATION FAILURE • RELOCATION CANCEL • RELOCATION CANCEL ACKNOWLEDGE • SRNS CONTEXT REQUEST

RAT Type IE is not included. • SRNS CONTEXT RESPONSE • SRNS DATA FORWARD COMMAND • FORWARD SRNS CONTEXT • PAGING

P-TMSI IE is included if available. • COMMON ID • CN INVOKE TRACE

Trace Propagation Parameters IE is not included. • SECURITY MODE COMMAND • SECURITY MODE COMPLETE • SECURITY MODE REJECT • LOCATION REPORTING CONTROL

Include Velocity IE is not included.Periodic Location Info is not included.

DN05196936Issue 7-0

37


Id:0900d805805656c7

• LOCATION REPORTPosition Data Specific To GERAN Iu Mode is ignored if received.Accuracy Fulfilment Indicator is ignored if received.Velocity Estimate is ignored if received.

• DATA VOLUME REPORT REQUESTNot supported by the SGSN.

• DATA VOLUME REPORTNot supported by the SGSN.

• INITIAL UE MESSAGEExtended RNC-ID is ignored if received.

• DIRECT TRANSFER • OVERLOAD

Currently, receiving overload has no impact on the signalling traffic load.Extended RNC-ID is ignored if received.

• RESETExtended RNC-ID is ignored if received.

• RESET ACKNOWLEDGEExtended RNC-ID is ignored if received.

• ERROR INDICATIONCurrently, receiving an Error Indication message has no impact on the SGSN.Extended RNC-ID is ignored if received.

• CN DEACTIVATE TRACE • RANAP RELOCATION INFORMATION

Not relevant for the SGSN (carried over the Iur interface through radio network sub-system application part (RNSAP)).

• RESET RESOURCEExtended RNC-ID is ignored if received.

• RESET RESOURCE ACKNOWLEDGEExtended RNC-ID is ignored if received.

• RAB MODIFY REQUEST • LOCATION RELATED DATA REQUEST

Not supported by the SGSN. • LOCATION RELATED DATA RESPONSE

Not supported by the SGSN. • LOCATION RELATED DATA FAILURE

Not supported by the SGSN. • INFORMATION TRANSFER INDICATION

Not supported by the SGSN. • INFORMATION TRANSFER CONFIRMATION

Not supported by the SGSN. • INFORMATION TRANSFER FAILURE

Not supported by the SGSN. • UE SPECIFIC INFORMATION INDICATION

Not supported by the SGSN. • DIRECT INFORMATION TRANSFER

Not supported by the SGSN. • UPLINK INFORMATION EXCHANGE REQUEST

Not supported by the SGSN.

38 DN05196936Issue 7-0


Id:0900d805805656c7


• UPLINK INFORMATION EXCHANGE RESPONSENot supported by the SGSN.

• UPLINK INFORMATION EXCHANGE FAILURENot supported by the SGSN.

• MBMS SESSION STARTNot supported by the SGSN.

• MBMS SESSION START RESPONSENot supported by the SGSN.

• MBMS SESSION START FAILURENot supported by the SGSN.

• MBMS SESSION UPDATENot supported by the SGSN.

• MBMS SESSION UPDATE RESPONSENot supported by the SGSN.

• MBMS SESSION UPDATE FAILURENot supported by the SGSN.

• MBMS SESSION STOPNot supported by the SGSN.

• MBMS SESSION STOP RESPONSENot supported by the SGSN.

• MBMS UE LINKING REQUESTNot supported by the SGSN.

• MBMS UE LINKING RESPONSENot supported by the SGSN.

• MBMS REGISTRATION REQUESTNot supported by the SGSN.

• MBMS REGISTRATION RESPONSENot supported by the SGSN.

• MBMS REGISTRATION FAILURENot supported by the SGSN.

• MBMS CN DE-REGISTRATION REQUESTNot supported by the SGSN.

• MBMS CN DE-REGISTRATION RESPONSENot supported by the SGSN.

• MBMS RAB ESTABLISHMENT INDICATIONNot supported by the SGSN.

• MBMS RAB RELEASE REQUESTNot supported by the SGSN.

• MBMS RAB RELEASENot supported by the SGSN.

• MBMS RAB RELEASE FAILURENot supported by the SGSN.

DN05196936Issue 7-0

39


Id:0900d805805656c7

4.3 Information Element Definitions

4.3.1 IEs Related to the Radio Network Layer • RAB ID

Due to SGSN restrictions the SGSN supports four simultaneous RABs per UE. • RAB Parameters

Queuing RABs is never allowed.The pre-emption capability is always set to 'shall not trigger pre-emption'.The pre-emption vulnerability is always set to 'pre-emptable'.The QoS parameters are supported according to 3GPP TS 23.107 Quality of Service (QoS) concept and architecture, version 7.1.0.The SDU parameters: there is always one subflow used, the SDU Information parameter is never included.The Relocation Requirement is always set to 'None'.

• Cause • CN Domain Indicator • Trace Type • Trigger ID • Trace Reference • UE Identity

IMEISV is not supported as an UE Identity. • OMC ID • Integrity Protection Information • Encryption Information • Chosen Integrity Protection Algorithm • Chosen Encryption Algorithm • Request Type • Data Volume Reporting Indication • User Plane Mode

Always set to 'transparent mode'. • UP Mode Versions

Always set to 1.

g UP Mode Versions is a dummy value as transparent mode is always used but it has to be included according to some specification interpretations.

• Paging Area ID • Non Searching Indication

IE is not included. • Relocation Type • Source ID

Extended RNC-ID field is not supported in Source RNC-ID IE. • Target ID

Extended RNC-ID field is not supported in Taget RNC-ID IE.RAC field is not supported in CGI IE.

• MS Classmark 2IE is ignored.

40 DN05196936Issue 7-0


Id:0900d805805656c7


• MS Classmark 3IE is ignored.

• Source RNC to Target RNC Transparent Container • Old BSS to New BSS Information

IE is ignored. • Target RNC to Source RNC Transparent Container • L3 Information

IE is not included. • Number of Steps • DL N-PDU Sequence Number • Uplink (UL) N-PDU Sequence Number • Criticality Diagnostics

In the Criticality Diagnostics IE only one item is included. Repetition number or message structure is not included.

• Key Status • DRX Cycle Length Coefficient

IE is not included. • Iu signalling connection identifier • Global RNC-ID • Extended RNC-ID

IE is ignored. • PDP Type Information

Only IP is allowed as a PDP type. • Service Handover

Always set to 'Handover to GSM should not be performed'. • Message Structure

IE is not included. • Alternative RAB Parameter Values

Always set to 'Unspecified'. • Assigned RAB Parameter Values • Requested RAB Parameter Values

IE is ignored. • Global CN-ID

In order to support multipoint Iu, this IE is needed in a connectionless RANAP to identify the sending SGSN for the RNC. It is needed since the RNC can be con-nected to several SGSNs at the same time.

• Vertical Accuracy Code • Response Time • Positioning Priority • Client Type • New BSS to Old BSS Information

IE is ignored. • Inter-System Information Transparent Container

IE is not included. • Cell Load Information

IE is not included. • Cell Capacity Class Value

IE is not included.

DN05196936Issue 7-0

41


Id:0900d805805656c7

• Load ValueIE is not included.

• RT Load ValueIE is not included.

• NRT Load Information ValueIE is not included.

• Source RNC PDCP context info • Information Transfer ID

IE is ignored. • Provided Data

IE is ignored. • GERAN Classmark

IE is ignored. • GERAN BSC Container

IE is ignored. • UESBI-Iu

IE is not included. • Cell Load Information Group

IE is ignored. • Source Cell Identifier

IE is ignored. • Inter-system Information Transfer Type

IE is not supported. • Information Transfer Type

IE is ignored. • RNC Trace Session Information

IE is ignored. • Equipments To Be Traced

IE is ignored. • Trace Recording Session Information • Trace Recording Session Reference • Trace Propagation Parameters

IE is not included. • Trace Depth

IE is not included. • List Of Interfaces To Trace

IE is not included. • Information Exchange ID

IE is not supported. • Information Exchange Type

IE is ignored. • Information Request Type

IE is ignored. • Information Requested

IE is not included. • PTP RAB ID

IE is not included.

42 DN05196936Issue 7-0


Id:0900d805805656c7


• Frequency Layer Convergence FlagIE is not included.

• Session Update IDIE is not supported.

• MBMS IP Multicast Address and APN RequestIE is ignored.

• Source BSS to Target BSS Transparent ContainerIE is ignored.

• Target BSS to Source BSS Transparent ContainerIE is not included.

• Include VelocityIE is not included.

• Periodic Location InfoIE is not included.

4.3.2 IEs Related to the Transport Network Layer • Transport Layer Address • Iu Transport Association • DL GTP-PDU Sequence Number • UL GTP-PDU Sequence Number

4.3.3 IEs Related to NAS • Permanent NAS UE Identity • Temporary UE ID • Paging Cause • NAS PDU • LAI • RAC • SAPI • SAI • Area Identity • Geographical Area • Unsuccessfully Transmitted Data Volume

IE is ignored. • Data Volume Reference • NAS Synchronisation Indicator

IE is not included. • Location Related Data Request Type

IE is not included. • Broadcast Assistance Data Deciphering keys

IE is not included. • Requested GPS Assistance Data

IE is ignored. • Last Known Service Area • Shared Network Information

IE is not included.

DN05196936Issue 7-0

43


Id:0900d805805656c7

• SNA Access InformationIE is not included.

• SNACIE is not included.

• Location Related Data Request Type Specific To GERAN Iu ModeIE is not included.

• Position Data • Position Data Specific To GERAN Iu Mode

IE is not included. • Accuracy Fulfilment Indicator

IE is not included. • RIM Transfer

IE is not supported. • RIM Information

IE is not supported • RIM Routing Address

IE is not supported. • Selected PLMN Identity • NAS Sequence Number

IE is not supported. • Redirection Completed • Redirection Indication • TMGI

IE is not supported. • MBMS Session Identity

IE is ignored. • MBMS Bearer Service Type

IE is not included. • MBMS Counting Information

IE is not included. • MBMS Session Duration

IE is not included. • MBMS Service Area

IE is not included. • RA List of Idle Mode Ues

IE is not included. • Delta RA List of Idle Mode Ues

IE is not included. • MBMS CN De-Registration

IE is not included. • MBMS Registration Request Type

IE is ignored. • Requested MBMS IP Multicast Address and APN

IE is not included. • Requested Multicast Service List

IE is not included. • MBMS Session Repetition Number

IE is not included.

44 DN05196936Issue 7-0


Id:0900d805805656c7


• Time to MBMS Data TransferIE is not included.

• Redirect Attempt Flag • Velocity Estimate

IE is not included. • RAT Type

IE is not included. • Requested GANSS Assistance Data

IE is not included.

4.4 Message and Information Element Abstract Syntax (with ASN.1) • Usage of private message mechanism for non-standard use

Private messages are not sent and they are ignored when received. • Elementary Procedure Definitions • PDU Definitions • Information Element Definitions • Common Definitions • Constant Definitions • Container Definitions

4.5 Message Transfer SyntaxNo additional information is needed.

4.6 Timers and ParametersThe SGSN Iu-specific timers and parameters are configurable and they are described in Radio Network Controller Parameter Handling in SGSN, E6 Command Group.

4.7 Handling of Unknown, Unforeseen and Erroneous Protocol Data • General • Transfer Syntax Error • Abstract Syntax Error • Logical Error • Exceptions

4.8 Special Procedures for RNC to RNC CommunicationNot relevant for the SGSN (carried over the Iur interface through radio network subsys-tem application part (RNSAP)).

IuPS Standart

Documents