Huawei Ranap Protocol Analysis Iu Cs

Iu CS Interface and RANAP Protocol Analysis
www.huawei.com
Copyright 2008 Huawei Technologies Co., Ltd. All rights reserved.
Foreword
The Iu interface is specified at the boundary between the Core Network and UTRAN. All the signalling and service between UE and CN must go through it. Iu CS is the interface between RNC and CS. RANAP provides the signalling service between UTRAN and CN. The course discusses Iu CS interface protocol stack, RANAP basic process and Iu interface main service flows.
Page1
Objectives
Upon completion of this course, you will be able to:
Understand Iu interface protocol stack and Function Know classification of RANAP messages Grasp Iu connection Management , RAB assignment, SRNS Relocation and know other basic processes.
Grasp CS Domain MM, CC signalling procedures in Iu Interfaces
Page2
Contents
1. Iu Interface Protocol and Functions 2. RANAP Procedure Analysis 3. RANAP Main Procedure
Page3
Contents
1. Iu Interface Protocol and Functions 2. RANAP Procedure Analysis 3. Iu Interface Main Service Flow
Page4
Iu Interface with tree CN domains

UTRAN
Node B
RNC Node B
Core Network (CN)

CS Domain Iu-CS PS Domain Iu-PS
Node B RNC Node B
BC Domain
Iu-BC
Iu Interface
The hierarchy for the CN - UTRAN signalling connection described as below:

Each CN Access Point may be connected to one or more UTRAN Access Points For the PS and CS domains, each UTRAN Access Point shall not be connected to more than one CN Access Point per CN domain For the BC domain, each UTRAN Access Point may be connected to one or more CN Access Points
Page5
Protocol structure for Iu and Uu

MM / CC / SMS MM / CC / SMS
Relay RRC RLC MAC RRC RLC MAC RANAP SCCP

signalling Bearer
RANAP SCCP
signalling Bearer
L1
Uu
L1
AAL5
ATM
Iu
AAL5
ATM MSC
MS
RNS
The figure shows the protocol structure for Iu and Uu. The Application signalling between UE and MSC(NAS) is transferred through RRC connection and Iu connection, such as MM, CC.
Page6
Protocol structure for Iu-CS(1/4)

Radio Network Layer Control Plane RANAP User Plane Iu UP Protocol Layer
Transport Network Layer
Transport Network User Plane
Transport Network Control Plane

Q.2630.1
Transport Network User Plane
SCCP MTP3b SSCF-NNI SSCOP AAL5
Q.2150.1 MTP3b SSCF-NNI SSCOP AAL5 AAL2
ATM Physical Layer
Page7

HorizontallyRadio Network layer and Transport Network Layer
Radio Network: Fulfill the Iu interface signalling interaction (RANAP) and Service (Iu UP)
RANAP
Iu UP
Q.2630.1
SCCP MTP-3B SAAL-NNI ATM PHY
STC
MTP-3B
SAAL-NNI
ATM PHY
AAL2 ATM PHY
Transport Network Layer: Provide respective transport function for Radio Network and service as well as control function of User Plane bear.
Page8

Vertically: Control Plane and User Plane
RANAP
Iu UP
Q.2630.1 SCCP MTP-3B STC MTP-3B SAAL-NNI ATM PHY
SAAL-NNI ATM
PHY Control Plane
AAL2
ATM PHY User Plane
Page9
Control Plane for Iu-CS (4/4)

Iu-CS Control Plane
RANAPsignalling Interactive between Iu interface
RANAP
SCCP-SAP
SCCPProvide Type 0 and 2 service for RANAP MTP3-BBandwidth MTP3, similar function as MTP3 SAALATM Signaling Adapter Layer
SCCP MTP3-B SAAL-NNI ATM
SSCF: Maps the requirements
of the layer above to the requirements of SSCOP

SSCOP: Connection control, signalling
transport reliability Control

AAL5 Adapts the upper layer protocol to
the requirements of the Lower ATM cells.

Copyright 2008 Huawei Technologies Co., Ltd. All rights reserved. Page10
Iu Connection in R4 CS
MSC Server RANAP RNC MC:H.248 IP Backbone Nc:BICC MSC Server
MGW Iu UP
MGW
CN is soft switch, bear control and call control is separated, Control plane and User plane in Iu interfaces are: >Control PlaneRNCMSC Server, RANAP >User Plane: RNCMGW, IuUP
Page11
Iu-CS Control Plane Function

Iu CsControl Plane Function RNC
RANAP
SCCP MTP-3B SAAL-NNI
MSC/MSC server
RANAP
SCCP MTP-3B SAAL-NNI
ATM
PHY
ATM
PHY
Iu signalling connection Management RAB Assignment SRNS Relocation Transfer NAS Signaling UTRAN Security Mode Control CN send IMSI to RNC Paging UE Activity Tracubg Location Report Iu Overload Report
Page12
Iu-CS User Plane Function

Iu CSUser Plane Fucntion
RNC
Iu UP
MSC/MGW
Iu UP
Support Mode:
Transfer Data
AAL2 ATM PHY
AAL2 ATM PHY
Initialize User Plane

Rate Control Time Adjustment
Error Indication
Frame quality classification.
Page13
Q.2630 (Q.AAL2)
Q.2630.1 STC MTP-3B SAAL-NNI ATM PHY MSC Server
MSC Server
Nb UP:RTP
RNC
IP Backbone
MGW
MGW
Control Plane User Plane
Q.2630 (Q.AAL2) AAL2
IPBCP (Q.1970) RTP
Q.AAL2 is used for establishment and maintenance AAL2.

Q.2630 Message
Q.2630 represent message type with one Byte, shown as below:

Message Block Confirm BLC Acronym Message Identifier 0000 0001
Block Request
Confusion Establish Confirm Establish Request Release Confirm Release Request Reset Confirm Reset Request Unblock Confirm Unblock Request
BLO
CFN ECF ERQ RLC REL RSC RES UBC UBL
0000 0010
0000 0011 0000 0100 0000 0101 0000 0110 0000 0111 0000 1000 0000 1001 0000 1010 0000 1011
Page15
Summary
The chapter introduce Iu CS protocol structure. Including Control Plane for transferring signalling and User Plane transferring circuit service. RANAP is the control plane protocol with bear of AAL5. IuUP is the user plane protocol with bear of AAL2. Transport Network Layer has protocol Q.2630 to fulfill AAL2 connection Control in Transport control layer.
Page16
Contents
1. Iu Interface Protocol and Functions 2. RANAP Procedure Analysis 3. Iu Interface Main Service Flow
Page17
Three types of RANAP Service
RANAP provides the signalling service between UTRAN and CN with a unit of interaction EP(Elementary Procedure). The EPs are defined separately and are intended to be used to build up complete sequences in a flexible manner.
Uu Iu CS UTRAN
E
MSC GMSC
RANAP
UE
From the point of view SAP (Service Access Points), RANAP provide three services:
General control services related to the whole Iu interface instance, accessed in CN through the General Control SAP, connectionless signalling transport. Notification servicesrelated to specified UEs or all UEs in specified area, through the Notification SAP, connectionless signalling transport
Dedicated control servicesrelated to one UE, through the Dedicated Control SAP, connection oriented signaling transport.
Page18
RANAP service modes
RANAP is user part of SCCP, SCCP provide service Type 0 and Type 2 for RANAP. Therefore, RANAP SCCP MTP-3B SAAL-NNI
RANAP EP also provide two related service mode.
Connection oriented data transfer service. dynamically establish and release based on the need ,Each active UE shall have its own signalling connection. Such as Iu Signaling management, RAB Assignment.
ATM
PHY
Connectionless data transfer service. No need to establish logic link, just directly transfer. Messages related to system maintenance management. Such
as Reset, Reset Resource, Overload Control, Paging

etc.
Page19
Elementary Procedure Classification
EP ClassificationClass1Class2Class3
An EP consists of an initiating message and possibly a response message. - Class 1: Elementary Procedures with response (success and/or failure). - Class 2: Elementary Procedures without response. - Class 3: Elementary Procedures with possibility of multiple responses.
Request Uu Iu CS RNC MSC
UE
Response
Page20
Class1:one request and one response

Elementary Procedure Iu Release Relocation Preparation Relocation Resource Allocation Relocation Cancel SRNS Context Transfer Security Mode Control Data Volume Report Reset Reset Resource Initiating Message IU RELEASE COMMAND RELOCATION REQUIRED RELOCATION REQUEST RELOCATION CANCEL SRNS CONTEXT REQUEST SECURITY MODE COMMAND DATA VOLUME REPORT REQUEST RESET RESET RESOURCE Successful Outcome Response message IU RELEASE COMPLETE RELOCATION COMMAND RELOCATION REQUEST ACKNOWLEDGE RELOCATION CANCEL ACKNOWLEDGE SRNS CONTEXT RESPONSE SECURITY MODE COMPLETE DATA VOLUME REPORT RESET ACKNOWLEDGE RESET RESOURCE ACKNOWLEDGE LOCATION RELATED DATA RESPONSE
Page21
Unsuccessful Outcome Response message
RELOCATION PREPARATION FAILURE RELOCATION FAILURE
SECURITY MODE REJECT
Location related Data
LOCATION RELATED DATA REQUEST
LOCATION RELATED DATA FAILURE
Class2:request without response

Elementary Procedure
RAB Modification Request RAB Release Request Iu Release Request Relocation Detect Relocation Complete SRNS Data Forwarding Initiation SRNS Context Forwarding from Source RNC to CN SRNS Context Forwarding to Target RNC from CN Paging Common ID CN Invoke Trace CN Deactivate Trace Location Reporting Control Location Report Initial UE Message Direct Transfer Overload Control Error Indication
Message
RAB MODIFY REQUEST RAB RELEASE REQUEST IU RELEASE REQUEST RELOCATION DETECT RELOCATION COMPLETE SRNS DATA FORWARD COMMAND FORWARD SRNS CONTEXT
FORWARD SRNS CONTEXT PAGING COMMON ID CN INVOKE TRACE CN DEACTIVATE TRACE LOCATION REPORTING CONTROL LOCATION REPORT INITIAL UE MESSAGE DIRECT TRANSFER OVERLOAD ERROR INDICATION
Page22
Class3:request with more than one response

Elementary Procedure RAB Assignment Initiating Message RAB ASSIGNMENT REQUEST Response Message RAB ASSIGNMENT RESPONSE x N (N>=1)
RAB ASSIGNMENT REQUESTone request can require more than one RAB to establish, modify. RAB is distinguish by RAB ID More details in next chapter.
Page23
RANAP Message Format
RANAP message adopts ASN.1 PER code. Its massage need decoding tolls to analysis. The type of message is fixed in front two bytes of position in message code. The following code example is RANAP message Relocation Complete
0x00 0x0D 0x40 0x03 0x00 0x00 0x00 0x00
ThereintoThe first byte 0x00 denotes procedure initiating message; The second byte 0x0D denotes process codeand 0x0D denotes Relocation Complete procedureAccording to the front of two bytesWe can judge that the message is Relocation Complete message. A RANAP message only with message type, its ASN.1 PER code is 7 bytes which likes last example. the length of RANAP message can not less than 7bytes after ASN.1 PER coding.
relocationComplete RANAP-ELEMENTARY-PROCEDURE ::= { INITIATING MESSAGE RelocationComplete PROCEDURE CODE id-RelocationComplete CRITICALITY ignore}
Page24
RANAP Message Classification
For better understand so many messages, We make a summary

Iu signalling Management Initial UE Message Direct Transfer Iu Release RAB setup RAB modify RAB Release Relocation Required Relocation Request Relocation Complete Cancel, Failure Common ID Paging Reset Reset Recourse Overload Control
Page25
RAB Management RANAP Message
SRNS Relocation
Security Mode Control Paging and Common ID
Related Maintenance
Iu signalling
The signalling between UE and CN is through RRC and Iu interface signalling, shown as below.
Uu Iu CS RNC MSC
UE
NAS signalling between UE and MSCCCMM)
RRC
Iu signalling
Iu signalling Management
Iu signalling Initial NAS Direct Transfer Iu signalling release
NASnon-Access Stratum
Iu signalling connection Establishment
Initial UE Message procedure is to establish an Iu signalling connection between a CN domain and the RNC and to transfer the initial NAS-PDU to the default CN node. The procedure uses connection oriented signalling.
RNC MSC
Initial UE Message
[ Initial UE Message ] CN domain indicatorIndicate CS or PS LAILocation Area Identifier

SAIService Area Identifier Iu signaling connection identifier Global RNC identifierRNC ID NAS-PDUNon Access Stratum Packet Date Unit
NAS signalling Direct Transfer
Direct Transfer procedure is to carry UE CN signalling messages transparently over the Iu Interface. Not interpreted by the UTRAN.
It belongs to connection oriented signalling and class 2 message.

RNC MSC
Direct Transfer or Direct Transfer
[ Direct Transfer ] NAS-PDUUE-CN SINGALLING LAILocation Area ID SAIService Area ID SAPIService Access Point ID
Iu Release Request
Iu Release Request procedure is to enable UTRAN to request the CN to release the Iu connection for a particular UE due to some UTRAN
generated reason . e.g. "O&M Intervention", "Unspecified Failure", "User

Inactivity etc.
The procedure uses connection oriented signalling and has no response.

RNC
MSC
Iu Release Request
[ Iu Release Request ] Iu Release Request Cause
Page29
Iu Release
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 and has response.

RNC MSC
Iu Release Request Iu Release Command [Cause] Iu Release Complete
[ Iu Release ]
Iu Release Command has Iu release cause

Iu Release Complete has RABs Released List ( RAB ID)
Page30
RAB Concept
RAB, Radio Access Bear, is the service bear between UE and CN(MSC) . RAB includes RB (radio bear) and Iu interface bear. Shown as below.
Uu Iu CS
UE
RNC
MSC
RAB
RB
AAL2 Connection
RAB Management
RAB Establish RAB Modify RAB Release
Page31
RAB Assignment
RNC MSC
RAB Assignment Request
RAB Assignment Response

Could be more than one responses
RAB Assignment is originated by CN(MSC/MSC Server), but CN only specify RAB ID and other RAB parameters. It is RNC to execute the command to assign the resource for USER PART and send them back to CN with response message. The procedure is connection originated
Page32
RAB Establishment
RAB Establishment: create RL in Uu, RB in Iub and AAL2 in Iu CS

RNC RAB Assignment Request (Setup) MSC
ERQ(Q.2630.1 Message)
ECF(Q.2630.1 Message) Establish AAL2 Connection
RAB Assignment Response (Setup)
[RAB ASSIGNMENT REQUEST ] RAB ID8Bits RAB ParametersQoS Mapping User Plane ModeTransparent or Support Mode UP Mode VersionsIuUP mode version Transport Layer Address NSAP (ATM Address) Iu Transport Association Binding ID(Termination ID)
RAB Release
RAB Release Request procedure is to enable UTRAN to request the release of one or several radio access bearers. The procedure uses connection oriented signalling and has no response.
Causes: "RAB pre-empted", "Release due to UTRAN Generated Reason",
"Radio Connection With UE Lost".
RNC
RAB Release Request
MSC RAB ID,Cause
RAB Assignment Request (release)

RAB Assignment Response (release) REL(Q.2630.1 Message) RLC(Q.2630.1 Message) [ RANAP:RAB ASSIGNMENT REQUEST(release) ] RAB IDs Cause
Release AAL2 connection
Iu Release companied with RAB Release
RAB Release RAB Release after Iu Release.

RNC MSC
Iu Release Request
Iu Release Command Iu Release Complete REL(Q.2630.1 Message) RLC(Q.2630.1 Message) AAL2 Release
Iu Release with RAB Release
Iu Release Command has the cause of Iu Release. Iu Release Complete has the RABs Released List ( RAB ID)
Page35
SRNS Relocation
SRNS Relocation is a UMTS functionality used to relocate the serving RNS role from one RNS to another RNS. it may
involve a change in the radio resources used between

UTRAN and UE. Resources include signalling and service bear.
Uu Source SRNS
Iur
UE
Uu
Target RNS MSC
Source RNS decides to perform SRNS Relocation with the measurement of neighbor LAI.
SRNS Relocation: Procedures

Source RNC MSC Target RNC
Relocation Required
Relocation Request Relocation Request Ack Relocation Command Relocation Detect Relocation Complete
SRNS Relocation procedure includes Relocation Preparation, Relocation Resource Allocation, Relocation Detect, Relocation Complete, Cancel etc.
SRNS Relocation: Preparation
Relocation: Preparation The source RNC shall initiate the procedure by generating RELOCATION REQUIRED message. The source RNC shall decide whether to initiate Relocation by RNS measurement.
Source RNC Relocation Required Relocation Request Relocation Request Ack Relocation Command MSC Target RNC
[ Relocation Required ]: Relocation Type: involving UE or not Cause Source ID: Source RNC ID Target ID: Target RNC ID Source RNC To Target RNC Transparent Container
SRNS Relocation: Preparation Successful
Preparation Successful The source RNC shall send the RELOCATION REQUIRED message to the CN and the source RNC shall start the timer TRELOCprep.. When the preparation including resource allocation in the target system is ready and the CN has decided to continue the relocation of SRNS, the CN shall send RELOCATION COMMAND message to the source RNC.
Source RNC Relocation Required Relocation Command MSC Relocation Request Relocation Request Ack Target RNC
[ Relocation Command ]: Source RNC To Target RNC Transparent Container L3 Information RABs To Be Released List
Page39
SRNS Relocation Preparation Unsuccessful
Preparation Unsuccessful If the CN or target system is not able to accept the relocation of SRNS or a failure occurs during the Relocation Preparation procedure in the CN or the CN decides not to continue, the CN shall send RELOCATION PREPARATION FAILURE message to the source RNC. CN shall release the possibly existing Iu signalling connection towards the target RNC with Cause IE, 'Relocation Cancelled'
Source RNC Relocation Required Relocation Request Relocation Request Ack RELOCATION PREPARATION FAILURE Target RNC
MSC
[RELOCATION PREPARATION FAILURE ]: Cause
Page40
SRNS Relocation:Relocation Resource Allocation
Relocation Resource Allocation :Allocate resources from target RNS for a relocation of SRNS. Procedure shall be co-ordinated in all Iu signalling connections existing for the UE. The procedure uses connection oriented signalling.
MSC Relocation Request Target RNC
Source RNC Relocation Required Relocation Command
Relocation Request Ack
Target Resource Allocation
[ Relocation Request ]: Permanent NAS UE IdentityIMSI Cause CN Domain IndicatorCS or PS Iu signalling Connection IdentifierIu signaling connection ID RABs To Be Setup List (RAB ID,User Plane Mode Source RNC To Target RNC Transparent Container Integrity signallingn Information (O) Encryption Information (O)
SRNS Relocation: Successful Resource Allocation
Relocation Resource Allocation: Successful After all necessary resources for accepted RABs including the Iu user plane, are successfully allocated, the target RNC shall send RELOCATION REQUEST ACKNOWLEDGE message to the CN
Source RNC Relocation Required Relocation Command MSC Target RNC
Relocation Request
Relocation Request Ack
[ Relocation Request Ack]: Source RNC To Target RNC Transparent Container RABs To Be Setup List RAB IDTransport Layer Address Iu Transport Association Assigned RAB Parameter Values RABs Failed To Setup List (O)(RAB ID,Cause Choosen Integrity Protection Information (O) Choosen Encryption Information (O)
SRNS Relocation: Unsuccessful Resource Allocation
Relocation Resource Allocation: Unsuccessful If the target RNC can not accept the relocation of SRNS or a failure occurs in the target RNC, the target RNC shall send RELOCATION FAILURE message to the CN. CN shall stop timer TRELOCalloc and shall assume possibly allocated resources within target RNC completely released.
Source RNC MSC
Target RNC
Relocation Required RELOCATION REQUEST
RELOCATION FAILURE
RELOCATION PREPARATION FAILURE
[ RELOCATION FAILURE ]: Cause

SRNS Relocation: Relocation Cancel
Relocation Cancel
Enable source RNC to cancel an ongoing relocation of SRNS. The procedure shall be coordinated in all Iu signalling connections existing for the UE. The procedure uses connection oriented signaling. It could be two situation: 1. If Source RNC can not receive Relocation Required ACK message, it will start the procedure. 2. Source RNC starts the procedure if UE reason.
Source RNC Relocation Required Relocation Cancel Relocation Cancel Ack
MSC Relocation Request
Target RNC
[ RELOCATION CANCEL ]: Cause

SRNS Relocation: Relocation Detect

Relocation Detect To indicate by the RNC the detection of SRNS relocation execution to the CN. The target RNC shall send RELOCATION DETECT message to the CN when relocation execution trigger is received. The target RNC shall start SRNC operation. The procedure uses connection oriented signalling.
Source RNC
MSC
Target RNC
Relocation Required
Relocation Request Relocation Request Ack
Relocation Command Relocation Detect
[ DETECT ] No Parameter
Page45
SRNS Relocation: Relocation Complete

Relocation Complete To indicate by the Target RNC the completion of relocation of SRNS to the CN. When the new SRNC-ID + S-RNTI (Serving RNC Radio Network Temporary Identity) are successfully exchanged with the UE by the radio protocols, target RNC shall initiate Relocation Complete procedure by sending RELOCATION COMPLETE message to CN.
Source RNC
MSC
Target RNC
Relocation Required
Relocation Command
Relocation Request Relocation Request Ack Relocation Detect Relocation Complete
Fulfill Relocation
Page46
UMTS Security Mode Control
UMTS Security Mode Control scope is between RNC and UE.

Uu
Iu CS
RNC MSC
UE
Security Mode Control Scope
Security Mode Control include cipher and integrity mode. Integrity is for signalling protection. Cipher is for signalling and service. When RLC using confirm or non-confirm mode, cipher is in RLC. When RLC using transparent mode, cipher is in MAC. IKCK is generated during authentication. They are transferred from MSC to RNC in Security Mode Control.
Page47
Security Mode Control Command
Security Mode Control To allow the CN to pass cipher and integrity mode information to the UTRAN. UTRAN uses this information to select and load the encryption device for user and signalling data with the appropriate parameters, and also to store the appropriate parameters for the integrity algorithm. The procedure uses connection oriented signalling.
RNC MSC
SECURITY MODE COMMAND SECURITY MODE COMPLETE

[ SECURTIY MODE COMMAND ]: Integrity Protection Information Encryption Information Key Status
Security Mode Control: Successful
Security Mode Complete Successful IK, integrity algorithm, CK and encryption algorithms.
RNC
MSC
SECURITY MODE COMMAND SECURITY MODE COMPLETE
[ SECURTIY MODE COMPLETE ]: Chosen Integrity Protection Algorithm Chosen Encryption Algorithm
Page49
Security Mode Control: Unsuccessful
Security Mode Reject
Unsuccessful IK, integrity algorithm, CK and encryption algorithms IK negotiation with the cause:

Requested Ciphering and/or Integrity Protection Algorithms are not Supported , Failure in the Radio Interface Procedure RNC MSC
SECURITY MODE COMMAND SECURITY MODE REJECT

[ SECURTIY MODE COMMAND ]: Integrity Protection Information Encryption Information Key Status [ SECURTIY MODE REJECT ]: Cause
COMMON ID
Common ID
To inform the RNC about the permanent NAS UE Identity (i.e. IMSI) of a user. This is used by the RNC e.g. to create a reference between the permanent NAS UE identity of the user and the RRC connection of that user for UTRAN paging co-ordination. The procedure uses connection oriented signalling.
RNC MSC
COMMON ID
[ COMMON ID ]: Permanent NAS UE Identity ( such as IMSI
Page51
Paging
To enable the CN to page a UE for a UE terminating service request. The procedure uses connectionless signalling. It will use common paging
channel when UE is in idle mode. It will use specified RRC if UE has

already RRC connection.
RNC MSC
PAGING
[ PAGING ]: CN Domain Indicator Permanent NAS UE Identity Temporary UE Identity Paging Area ID Paging Cause
UE Location Reporting Control
Location Reporting Control
Allow the CN to request information on the location of a given UE. The procedure uses connection oriented signalling
RNC LOCATION REPORTING CONTROL MSC
[ LOCATION REPORTING CONTROL ]: Request Type Vertical Accuracy Code Response Time Positioning Priority Client Type
UE Location Report
UE Location Report
Provide the UE's location information to the CN. The procedure uses connection oriented signalling..
RNC MSC
LOCATION REPORT
[ LOCATION REPORT ]: Request Type Area Identity Cause Last Known Service Area
Overload Control
Give some degree of signalling flow control. Algorithms are used to stem the traffic at source with known effect on the service. The procedure uses connectionless signalling.
RNC MSC
OVERLOAD
[ OVERLOAD ]: Number Of Steps Global RNC-ID CN Domain Indicator
Page55
Reset
Initialize the UTRAN in the event of a failure in the CN or vice versa. used by the UTRAN to release affected RAB and to erase all affected references, After a guard period of T(RatC) seconds, UEs which were involved in a call are no longer transmitting and that all references at the UTRAN have been cleared. The procedure uses RNCconnectionless signalling. MSC
RESET RESET ACKNOWLEGE
[ RESET ]: Cause CN Domain Indicator Global RNC-ID Global CN-ID
[ RESET ACKNOWLEGE ]: Criticality Diagnostics CN Domain Indicator Global RNC-ID Global CN-ID
Page56
Reset Resource
To initialize part of the UTRAN(Iu connection) in the event of an abnormal failure in the CN or vice versa (e.g. signalling Transport
processor reset). The procedure uses connectionless signalling.

RNC MSC
RESET RESOURCE RESET RESOURCE ACK
[ RESET RESOURCE ]: Cause CN Domain Indicator Global RNC-ID Global CN-ID Reset Resource List (Iu signalling Connection Identifier )
Reset Resource Acknowledge
Reset Resource Ack
RNC shall release locally the resources and references (i.e. radio resources
and Iu signalling connection identities) associated to the Iu signalling

connection identities indicated in the received message. The RNC shall always return the RESET RESOURCE ACKNOWLEDGE message to the CN.
RNC MSC
RESET RESOURCE RESET RESOURCE ACK

[ RESET RESOURCE ACK ]: Criticality Diagnostics CN Domain Indicator Global RNC-ID Global CN-ID Reset Resource List (Iu signalling Connection Identifier )
Error Indication
Initiated by a node to report detected errors in one incoming message, provided they cannot be reported by an appropriate failure message. If the error situation arises due to reception of a message utilising dedicated signalling, then the Error Indication procedure uses connection oriented signalling. Otherwise the procedure uses connectionless signalling.
Direction: RNC CN and CN RNC.
RNC
MSC
Error Indication
[ Error Indication ]: Cause Criticality Diagnostics CN Domain Indicator
Global RNC-ID Global CN-ID
Page59
Summary
This chapter analyzed RANANP processes and messages in details in the area of Iu connection Management, RAB Management, SRNS
Relocation, Security Mode Control, Paging and Maintenance.

Iu signalling Management RAB Management Iu signalling is used for transferring NAS signaling between UE and MSC. Including Initial UE Message, Direct Transfer, Iu Release Command RAB is the bear for User Plane service, which managed by RANAP. RAB Assignment Request is to establish , modify and release RAB.
RANAP Messages
SRNS Relocation Security Mode Control
Relocate serving RNS role from one RNS to another and service from old Iu to new Iu interface. Includes Relocation Preparation, Resource Allocation, Detect, Complete etc
MSC send IK, CK to RNC and manage Integrity and encryption algorism Common ID:IMSI from MSC to RNC Paging and Common ID Paging Reset Related Reset Recourse Maintenance Overload Control
RANAP Message Classification
For better understand so many messages, We make a summary

Iu signalling Management
RAB Management RANAP Message
Initial UE Message Direct Transfer Iu Release RAB setup RAB modify RAB Release
Relocation Required Relocation Request Relocation Complete Cancel, Failure Common ID Paging
SRNS Relocation
Security Mode Control Paging and Common ID Related Maintenance
Reset Reset Recourse Overload Control

Page61
Contents
1. Iu Interface Protocol and Function 2. RANAP Procedure Analysis 3. Iu Interface Main Service Flow
Page62
Iu Interface Service Flow
In previous chapter we have already analyzed control plane, user plane of Iu interface and related message. Next, we will analyze signalling interface of call flow and location upgrade flow how to transferr in Iu interface.
Iu CS UTRAN MSC
Iu CS
MSC
UTRAN
CN
Page63
UE Calling Flow signalling in Iu interface

RNC 1. SCCP:CR(Initial UE Message(CM Service Request)) MSC
2. SCCP:CC
3. COMMON ID 4. SECURITY FUNCTION 5. DIRECT TRANSFER(setup) 6. DIRECT TRANSFER(call proceeding) 7. RAB ASSIGNMENT
Iu Connection EstablishmentUE originate service request in calling flow, which included in NAS-PDU of Initial UE message. SCCP make a connect with CRCC message.(step 1,2) MSC send IMSI to RNCCommon ID (step 3). Security Modesometime need authentication (through DT message), and start Security mode control (step4). Number AnalysisCalled number is carried in L3 setup message, MSC judges the call attribute (outgoing PSTN, intra office calling etc) and send Call proceeding once successfully analyzed. All these messages are transferred in DT message.(step5,6).
Page64

RNC MSC
5. DIRECT TRANSFER(setup) 6. DIRECT TRANSFER(call proceeding)
7. RAB ASSIGNMENT
RAB AssignmentAfter MSC send Call Proceeding, MSC send RAB ASSIGNMENT to MSC, require RNC to prepare resource, establish user plane bear (AAL2 connection) in Iu interface and wireless bear RB. AAL2 connection is fulfilled with Q.2630 sending ERQ and receiving ECF.
Page65

RNC MSC
5. DIRECT TRANSFER(setup)
6. DIRECT TRANSFER(call proceeding) 7. RAB ASSIGNMENT
8. DIRECT TRANSFER(alerting) 9. DIRECT TRANSFER(connect) 10. DIRECT TRANSFER(connect acknowledge)
Calling EstablishMsc send Alerting message to calling party when called party alerting, Msc send Connect message to calling party when called party pick hook and calling party send back Connect Acknowledge . All these messages are L3 message, transfering in DT(Step8, 9, 10)

RNC MSC
9. DIRECT TRANSFER(connect) 10. DIRECT TRANSFER(connect acknowledge)
Conversation
ConversationVoice streams of Voice Conversation are formatted into Iu UP frame and transferred in AAL2 connection of IuUP .

RNC
10. DIRECT TRANSFER(connect acknowledge) Conversation 11. DIRECT TRANSFER(disconnect ) 12. DIRECT TRANSFER(release) 13. DIRECT TRANSFER(release complete) 14. Iu Release Request/Response 15. SCCP connection Release
MSC
Conversation Release :MSC send calling party disconnect message while called party hang hook, Calling party send release message and MSC send back Acknowledge message. All these messages are L3 message transferred in DT messages(step11,12,13) Resource Release: After finish conversation, Iu connection will release if there is no other service. RAB (step 14) and SCCP connection(step 15) are released either.

RNC
1. SCCP:CR(Initial UE Message(CM Service Request)) 2. SCCP:CC 3. COMMON ID 4. SECURITY FUNCTION 5. DIRECT TRANSFER(setup) 6. DIRECT TRANSFER(call proceeding) 7. RAB ASSIGNMENT 8. DIRECT TRANSFER(alerting) 9. DIRECT TRANSFER(connect) 10. DIRECT TRANSFER(connect acknowledge) Conversation 11. DIRECT TRANSFER(disconnect ) 12. DIRECT TRANSFER(release) 13. DIRECT TRANSFER(release complete) 14. Iu Release Request/Response 15. SCCP connection Release Call Release Stage Conversation Flow Call Establish Stage
MSC
Page69
Other Flow
The previous slides analyze UE Calling Flow signalling in Iu interfaces. In coming slides, please analyze the UE Called Flow and location update signalling in Iu interfaces.
Page70
UE Called Flow signalling in Iu Interface

RNC
Paging 1. SCCP:CR(Initial UE Message(Paging Response)) 2. SCCP:CC 3. COMMON ID 4. SECURITY FUNCTION 5. DIRECT TRANSFER(setup) Paging and response, Iu Connection Establishment
MSC
6. DIRECT TRANSFER(call confirm)

7. RAB ASSIGNMENT 8. DIRECT TRANSFER(alerting) 9. DIRECT TRANSFER(connect) 10. DIRECT TRANSFER(connect acknowledge) Conversation 11. DIRECT TRANSFER(disconnect ) 12. DIRECT TRANSFER(release) 13. DIRECT TRANSFER(release complete) 14. Iu Release Request/Response 15. SCCP connection Release Call Release Stage Conversation Call Establish Stage
Page71
Location Update signalling Transfer in Iu Interface

RNC
SCCP:CR(Initial UE Message(Location Update Request)) SCCP:CC DIRECT TRANSFER(Authentication Request) DIRECT TRANSFER(Authentication Response) Security Mode Command Security Mode Complete DIRECT TRANSFER(Location Updage Accept) DIRECT TRANSFER(TMSI Relocation Complete) Iu Release Command Iu Release Complete SCCP:RLSD Connection Release Stage signalling Transfer Stage
MSC
Iu Connection Establishment
SCCP:RLC
Page72
Summary
This chapter introduces NAS signalling how to transfer in Iu interface. Including call control originating signalling, terminating signalling and Location Upgrade. Comprehension of these flow help further understanding of RANAP protocol
Page73
Thank you
www.huawei.com

Huawei Ranap Protocol Analysis Iu Cs

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Huawei Ranap Protocol Analysis Iu Cs

Uploaded by

Copyright:

Available Formats

Iu CS Interface and RANAP Protocol Analysis

Copyright 2008 Huawei Technologies Co., Ltd. All rights reserved.

Copyright 2008 Huawei Technologies Co., Ltd. All rights reserved.

Upon completion of this course, you will be able to:

Grasp CS Domain MM, CC signalling procedures in Iu Interfaces

Copyright 2008 Huawei Technologies Co., Ltd. All rights reserved.

Copyright 2008 Huawei Technologies Co., Ltd. All rights reserved.

Copyright 2008 Huawei Technologies Co., Ltd. All rights reserved.

Iu Interface with tree CN domains

Core Network (CN)

Node B RNC Node B

The hierarchy for the CN - UTRAN signalling connection described as below:

Copyright 2008 Huawei Technologies Co., Ltd. All rights reserved.

Protocol structure for Iu and Uu

Relay RRC RLC MAC RRC RLC MAC RANAP SCCP

Copyright 2008 Huawei Technologies Co., Ltd. All rights reserved.

Protocol structure for Iu-CS(1/4)

Transport Network Layer

Transport Network User Plane

Transport Network Control Plane

Transport Network User Plane

SCCP MTP3b SSCF-NNI SSCOP AAL5

Q.2150.1 MTP3b SSCF-NNI SSCOP AAL5 AAL2

ATM Physical Layer

Copyright 2008 Huawei Technologies Co., Ltd. All rights reserved.

Protocol structure for Iu-CS(2/4)

AAL2 ATM PHY

Copyright 2008 Huawei Technologies Co., Ltd. All rights reserved.

Protocol structure for Iu-CS(3/4)

Q.2630.1 SCCP MTP-3B STC MTP-3B SAAL-NNI ATM PHY

Copyright 2008 Huawei Technologies Co., Ltd. All rights reserved.

Control Plane for Iu-CS (4/4)

SCCP MTP3-B SAAL-NNI ATM

SSCF: Maps the requirements

of the layer above to the requirements of SSCOP

transport reliability Control

the requirements of the Lower ATM cells.

Copyright 2008 Huawei Technologies Co., Ltd. All rights reserved.

Iu-CS Control Plane Function

Copyright 2008 Huawei Technologies Co., Ltd. All rights reserved.

Iu-CS User Plane Function

AAL2 ATM PHY

AAL2 ATM PHY

Initialize User Plane

Copyright 2008 Huawei Technologies Co., Ltd. All rights reserved.

Control Plane User Plane

Q.2630 (Q.AAL2) AAL2

IPBCP (Q.1970) RTP

Q.AAL2 is used for establishment and maintenance AAL2.

Q.2630 represent message type with one Byte, shown as below:

Copyright 2008 Huawei Technologies Co., Ltd. All rights reserved.

Copyright 2008 Huawei Technologies Co., Ltd. All rights reserved.

Copyright 2008 Huawei Technologies Co., Ltd. All rights reserved.

Three types of RANAP Service

Copyright 2008 Huawei Technologies Co., Ltd. All rights reserved.

RANAP service modes

RANAP EP also provide two related service mode.

as Reset, Reset Resource, Overload Control, Paging

Copyright 2008 Huawei Technologies Co., Ltd. All rights reserved.

Elementary Procedure Classification

Request Uu Iu CS RNC MSC

Copyright 2008 Huawei Technologies Co., Ltd. All rights reserved.

Class1:one request and one response

Unsuccessful Outcome Response message