Tech-invite3GPPspaceIETF RFCsSIP
Quick21222324252627282931323334353637384‑5x

Content for  TS 25.413  Word version:  16.0.0

Top   Top   None   None   Next
1…   8…   9…   10…

 

1  ScopeWord‑p. 15

The present document specifies the radio network layer signalling protocol called Radio Access Network Application Part (RANAP) for the Iu interface. RANAP supports the functions of Iu interface by signalling procedures defined in this document. RANAP is developed in accordance to the general principles stated in TR 23.930 [1], TS 25.410 and TS 25.401.
Up

2  References

The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
  • References are either specific (identified by date of publication, edition number, version number, etc.) or non specific.
  • For a specific reference, subsequent revisions do not apply.
  • For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.
[1]
TR 23.930: (version.4.0.0, 2001-04) "Iu Principles".
[2]
TS 25.410: "UTRAN Iu Interface: General Aspects and Principles".
[3]
TS 25.401: "UTRAN Overall Description".
[4]
TR 25.931: "UTRAN Functions, Examples on Signalling Procedures".
[5]
TS 25.412: "UTRAN Iu interface signalling transport".
[6]
TS 25.415: "UTRAN Iu interface user plane protocols".
[7]
TS 23.107: "Quality of Service (QoS) concept and architecture".
[8]
TS 24.008: "Mobile radio interface layer 3 specification; Core network protocols; Stage 3".
[9]
TS 25.414: "UTRAN Iu interface data transport and transport signalling".
[10]
TS 25.331: "Radio Resource Control (RRC) protocol specification".
[11]
TS 48.008: "Mobile Switching Centre - Base Station System (MSC - BSS) interface; Layer 3 specification".
[12]  Void
[13]
ITU-T Recommendation X.691 (07/2002): "Information technology - ASN.1 encoding rules: Specification of Packed Encoding Rules (PER)".
[14]
ITU-T Recommendation X.680 (07/2002): "Information technology - Abstract Syntax Notation One (ASN.1): Specification of basic notation".
[15]
ITU-T Recommendation X.681 (07/2002): "Information technology - Abstract Syntax Notation One (ASN.1): Information object specification".
[16]
TS 23.110: "UMTS Access Stratum, Services and Functions".
[17]
TS 25.323: "Packet Data Convergence Protocol (PDCP) specification".
[18]
TR 25.921: (version.7.0.0) "Guidelines and principles for protocol description and error handling".
[19]
TS 23.003: "Numbering, addressing and identification".
[20]
TS 23.032: "Universal Geographical Area Description (GAD)".
[21]
TS 23.060: "General Packet Radio Service (GPRS); Service description; Stage 2".
[22]
TS 24.080: "Mobile radio Layer 3 supplementary services specification; Formats and coding".
[23]
TS 29.108: "Application of the Radio Access Network Application Part (RANAP) on the E interface".
[24]
TS 29.002: "Mobile Application Part (MAP) specification".
[25]
GSM TS 12.20: "Base Station System (BSS) management information".
[26]
TS 23.236: "Intra-domain connection of Radio Access Network (RAN) nodes to multiple Core Network (CN) nodes".
[27]
TS 43.051: "3rd Generation Partnership Project; Technical Specification Group GSM/EDGE Radio Access Network; Overall description - Stage 2".
[28]  Void.
[29]
TS 43.059: "Functional stage 2 description of Location Services (LCS) in GERAN".
[30]
TS 22.071: "Location Services (LCS); Service description - Stage 1".
[31]
TR 25.994: (version.5.0.0) "Measures employed by the UMTS Radio Access Network (UTRAN) to overcome early User Equipment (UE) implementation faults".
[32]
TR 25.995: (version.5.0.0) "Measures employed by the UMTS Radio Access Network (UTRAN) to cater for legacy User Equipment (UE) which conforms to superseded versions of the RAN interface specification".
[33]
TS 23.195: (version.5.4.0) "Provision of UE Specific Behaviour Information to Network Entities".
[34]
TS 49.031: "Location Services (LCS) - Base Station System Application Part LCS Extension - (BSSAP-LE)".
[35]
TR 21.905: "Vocabulary for 3GPP Specifications".
[36]
TS 48.018: "General Packet Radio Service (GPRS); BSS GPRS Protocol (BSSGP)".
[37]
TS 32.421: "Subscriber and equipment trace: Trace concepts and requirements".
[38]
TS 32.422: "Subscriber and equipment trace: Trace control and Configuration Management".
[39]
TS 23.251: "Network sharing - Architecture and functional description".
[40]
TS 22.146: "Multimedia Broadcast/Multicast Service; Stage 1".
[41]
TS 23.246: "Multimedia Broadcast Multicast Service; Architecture and Functional Description".
[42]
TS 25.346: "Introduction of the Multimedia Broadcast Multicast Service (MBMS) in the Radio Access Network (RAN); Stage 2".
[43]
TS 23.172: "Technical realization of Circuit Switched (CS) multimedia service UDI/RDI fallback and service modification; Stage 2".
[44]
TS 29.061: "Interworking between the Public Land Mobile Network (PLMN) supporting packet based services and Packet Data Networks (PDN)".
[45]
TS 44.018: "Mobile radio interface layer 3 specification; Radio Resource Control Protocol".
[46]
TS 44.060: "General Packet Radio Service (GPRS); Mobile Station (MS) - Base Station System (BSS) interface; Radio Link Control/Medium Access Control (RLC/MAC) protocol".
[47]
TS 43.055: "3rd Generation Partnership Project; Technical Specification Group GSM/EDGE Radio Access Network; Dual Transfer Mode (DTM) - Stage 2".
[48]
TS 23.401: "General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access".
[49]
TS 36.413: "Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP)".
[50]
TS 25.104: "Base Station (BS) radio transmission and reception(FDD)".
[51]
TS 25.446: "MBMS Synchronisation Protocol(SYNC)".
[52]
TS 36.300: "Evolved Universal Terrestrial Radio Access (E-UTRA), Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; stage 2".
[53]
TS 23.007: "Restoration procedures"
[54]
TS 23.216: "Single Radio Voice Call Continuity (SRVCC); Stage 2"
[55]
TS 25.467: "UTRAN architecture for 3G Home Node B (HNB) - Stage 2"
[56]
TS 22.220: "Service requirements for Home Node Bs and Home eNode Bs".
[57]
TS 29.060: "General Packet Radio Service (GPRS); GPRS Tunnelling Protocol (GTP) across the Gn and Gp Interface".
[58]
TS 36.101: "Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception".
[59]
TS 29.281: "General Packet Radio Service (GPRS); Tunnelling Protocol User Plane (GTPv1-U)".
[60]
TS 33.102: "3G Security; Security architecture".
[61]
TS 32.240: "Charging management; Charging architecture and principles".
[62]
TS 52.008: "Telecommunication management; GSM subscriber and equipment trace".
[63]
TS 33.401: "3GPP System Architecture Evolution (SAE); Security architecture".
[64]
TS 37.320: "Universal Terrestrial Radio Access (UTRA) and Evolved Universal Terrestrial Radio Access (E-UTRA); Radio measurement collection for Minimization of Drive Tests (MDT); Overall description; Stage 2".
[65]
TS 23.139: "3GPP system - fixed broadband access network interworking".
[66]
BDS-SIS-ICD-2.0: "BeiDou Navigation Satellite System Signal In Space Interface Control Document Open Service Signal (Version 2.0)", December 2013.
[67]
TS 23.272: "Circuit Switched (CS) fallback in Evolved Packet System (EPS); Stage 2".
[68]
TS 23.682: "Architecture enhancements to facilitate communications with packet data networks and applications".
[69]
RFC 4119:  "A Presence-based GEOPRIV Location Object Format".
[70]
RFC 5139:  "Revised Civic Location Format for Presence Information Data Format Location Object".
[71]
RFC 6848:  "Specifying Civic Address Extensions in the Presence Information Data Format Location Object (PIDF-LO)".
[72]
TS 25.300: "Universal Terrestrial Radio Access Network (UTRAN); General description; Stage 2".
Up

3  Definitions, symbols and abbreviationsWord‑p. 18

3.1  Definitions

For the purposes of the present document, the following terms and definitions below apply. Terms and definitions not defined below can be found in TR 21.905.
Cell Load-Based Inter-System Handover:
This mechanism, which is contained within a UTRAN RNC, consists of three primary functions:
  1. The RNC has the capability to generate and send Cell Load Information towards the target/source system.
  2. The RNC has the capability to receive Cell Load Information from the target/source system, and is able to interpret this information.
  3. The ability of the RNC to make a handover decision by comparing the Cell Load Information that it has received from the target system with the Cell Load Information it has about its own cells.
Ciphering Alternative:
defines both the Ciphering Status (started/not started) together with the Ciphering Algorithm considered altogether.
Core Network operator:
as defined in TS 23.251.
Corresponding RNC-ID:
RNC-ID corresponding to an eNB ID, which enables a source RNC to address a target eNB for handover purposes via CN elements that cannot interprete an eNB ID (see TS 23.401).
CSG Cell:
a UTRAN cell broadcasting a CSG Indicator and a CSG identity. This cell operates in Closed Access Mode as defined in TS 22.220.
DCN-ID:
DCN identity identifies a specific decicated core network (DCN).
Default CN node:
An RNC with an inactive or not implemented NAS Node Selection Function TS 23.236 has one single permanent default CN node per CN domain. It always initiates the Initial UE Message procedure towards its default CN node. If the NAS Node Selection Function is active, then no Default CN node exists.
Directed retry:
Directed retry is the process of assigning a User Equipment to a radio resource that does not belong to the serving RNC e.g. in situations of congestion. It is triggered by the RAB Assignment procedure and employs relocation procedures.
Elementary Procedure:
RANAP protocol consists of Elementary Procedures (EPs). An Elementary Procedure is a unit of interaction between the RNS and the CN. These Elementary Procedures are defined separately and are intended to be used to build up complete sequences in a flexible manner. If the independence between some EPs is restricted, it is described under the relevant EP description. Unless otherwise stated by the restrictions, the EPs may be invoked independently of each other as stand alone procedures, which can be active in parallel. Examples on using several RANAP EPs together with each other and EPs from other interfaces can be found in reference TR 25.931.
An EP consists of an initiating message and possibly a response message. Three kinds of EPs are used:
  • 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.
For Class 1 EPs, the types of responses can be as follows:
Successful:
  • A signalling message explicitly indicates that the elementary procedure successfully completed with the receipt of the response.
Unsuccessful:
  • A signalling message explicitly indicates that the EP failed.
  • On time supervision expiry (i.e. absence of expected response).
Successful and Unsuccessful:
  • One signalling message reports both successful and unsuccessful outcome for the different included requests. The response message used is the one defined for successful outcome.
Class 2 EPs are considered always successful.
Class 3 EPs have one or several response messages reporting both successful, unsuccessful outcome of the requests and temporary status information about the requests. This type of EP only terminates through response(s) or EP timer expiry.
Enhanced relocation:
denotes a method where the relocation of the SRNS functionality is prepared via RNSAP means. The CN is not informed until the preparation and execution of the relocation has taken place.
Gateway Core Network:
as defined in TS 23.251.
GERAN BSC in Iu mode:
In the context of this specification no distinction between an UTRAN RNC and a GERAN BSC in Iu mode is made. The GERAN BSC in Iu mode will behave as a RNC unless explicitely stated (see TS 43.051).
Hybrid Cell:
a UTRAN cell broadcasting a CSG Identity and operating in Hybrid Access Mode as defined in TS 22.220.
Integrity Protection Alternative:
defines both the Integrity Protection Status (started/not started) together with the Integrity Protection Algorithm considered altogether.
Local Home Network:
as defined in TS 23.060.
Management Based Activation:
as defined in TS 32.421.
MBMS Bearer Service:
as defined in TS 23.246.
MBMS Iu signalling connection:
as defined in TS 25.346.
MBMS RAB:
as defined in TS 25.346.
MBMS Service Area:
as defined in TS 23.246.
MBMS Service Context:
as defined in TS 25.346.
MBMS Session:
as defined in TS 25.346.
MBMS session start:
as defined in TS 25.346.
MBMS session stop:
as defined in TS 25.346.
Multicast Service:
as defined in TS 22.146.
Multi-Operator Core Network:
as defined in TS 23.251.
Network sharing non-supporting UE:
as defined in TS 23.251.
Network sharing supporting UE:
as defined in TS 23.251.
Packet System Information:
as defined in TS 44.060.
PUESBINE feature:
as defined in TS 23.195.
Relocation of SRNS:
relocation of SRNS is a UMTS functionality used to relocate the serving RNS role from one RNS to another RNS. This UMTS functionality is realised by several elementary procedures executed in several interfaces and by several protocols and it may involve a change in the radio resources used between UTRAN and UE
It is also possible to relocate the serving RNS role from:
  • one RNS within UMTS to another relocation target external to UMTS;
  • functionality equivalent to the serving RNS role from another relocation source external to UMTS to another RNS.
RAN Information Management:
as defined in TS 48.018.
RNSAP Relocation:
see definition in TS 25.467.
Trace Recording Session:
as defined in TS 32.421.
Trace Recording Session Reference:
as defined in TS 32.421.
Trace Reference:
as defined in TS 32.421.
Trace Session:
as defined in TS 32.421.
Serving RNC:
SRNC is the RNC belonging to SRNS
Serving RNS:
role an RNS can take with respect to a specific connection between an UE and UTRAN. There is one serving RNS for each UE that has a connection to UTRAN. The serving RNS is in charge of the radio connection between a UE and the UTRAN. The serving RNS terminates the Iu for this UE
Signalling Based Activation:
as defined in TS 32.421.
Source RNC:
source RNC is the RNC belonging to source RNS
Source RNS:
role, with respect to a specific connection between UTRAN and CN, that RNS takes when it decides to initiate a relocation of SRNS
System Information in GERAN:
as defined in TS 44.018.
Target RNC:
target RNC is the RNC belonging to target RNS
Target RNS:
role an RNS gets with respect to a specific connection between UTRAN and CN when it is being a subject of a relocation of SRNS which is being made towards that RNS
UE Specific Behaviour Information - Iu:
as defined in TS 23.195.
Up

3.2  SymbolsWord‑p. 20

Void.

3.3  Abbreviations

Applicable abbreviations can be found in TR 21.905. For the purposes of the present document, the following abbreviations apply:
AAL2
ATM Adaptation Layer type 2
ALCAP
Access Link Control Application Part
APN
Access Point Name
AS
Access Stratum
ASN.1
Abstract Syntax Notation One
ATM
Asynchronous Transfer Mode
BDS
BeiDou Navigation Satellite System
BBF
Broadband Forum
BSC
Base Station Controller
CC
Call Control
CN
Core Network
CRNC
Controlling RNC
CS
Circuit Switched
CSG
Closed Subscriber Group
DCH
Dedicated Channel
DCN
Dedicated Core Network
DL
Downlink
DRNC
Drift RNC
DRNS
Drift RNS
DSCH
Downlink Shared Channel
eNB
E-UTRA NodeB
EP
Elementary Procedure
E-UTRA
Evolved UTRA
E-UTRAN
Evolved UTRAN
GANSS
Galileo and Additional Navigation Satellite Systems
GERAN
GSM/EDGE Radio Access Network
GPRS
General Packet Radio System
GSM
Global System for Mobile communications
GTP
GPRS Tunnelling Protocol
GWCN
GateWay Core Network
HNB
Home Node B
IE
Information Element
IMEI
International Mobile Equipment Identity
IMSI
International Mobile Subscriber Identity
IPv4
Internet Protocol (version 4)
IPv6
Internet Protocol (version 6)
IRAT
Inter-RAT
L-GW
Local GateWay
LIPA
Local IP Access
LHN
Local Home Network
LHN ID
Local Home Network ID
MBMS
Multimedia Broadcast Multicast Service
MBS
Metropolitan Beacon System
MDT
Minimization of Drive Tests
MM
Mobility Management
MOCN
Multi Operator Core Network
MSC
Mobile services Switching Center
MSISDN
MS International PSTN/ISDN Number
MTSI
Multimedia Telephony Service for IMS
NACC
Network Assisted Cell Change
NAS
Non Access Stratum
NNSF
NAS Node Selection Function
NRT
Non-Real Time
N-PDU
Network - Protocol Data Unit
OSP:IHOSS
Octet Stream Protocol: Internet-Hosted Octet Stream Service
P-TMSI
Packet TMSI
PDCP
Packet Data Convergence Protocol
PDP
Packet Data Protocol
PDU
Protocol Data Unit
PLMN
Public Land Mobile Network
PPP
Point-to-Point Protocol
PS
Packet Switched
PSI
Packet System Information
PTP
Point To Point
PUESBINE
Provision of UE Specific Behaviour Information to Network Entities
QoE
Quality of Experience
QoS
Quality of Service
RAB
Radio Access Bearer
RANAP
Radio Access Network Application Part
RAT
Radio Access Technology
RIM
RAN Information Management
RNC
Radio Network Controller
RNS
Radio Network Subsystem
RRC
Radio Resource Control
rSRVCC
reverse Single Radio Voice Call Continuity
RT
Real Time
SAI
Service Area Identifier
SAP
Service Access Point
SDU
Service Data Unit
SGSN
Serving GPRS Support Node
S-GW
Serving GateWay
SI
System Information in GERAN
SIPTO
Selected IP Traffic Offload
SIPTO@LN
Selected IP Traffic Offload at the Local Network
SNA
Shared Network Area
SNAC
Shared Network Area Code
SRNC
Serving RNC
SRNS
Serving RNS
SRVCC
Single Radio Voice Call Continuity
TEID
Tunnel Endpoint Identifier
TMGI
Temporary Mobile Group Identity
TMSI
Temporary Mobile Subscriber Identity
UE
User Equipment
UEA
UMTS Encryption Algorithm
UESBI-Iu
UE Specific Behaviour Information - Iu
UIA
UMTS Integrity Algorithm
UL
Uplink
UMTS
Universal Mobile Telecommunications System
USCH
Uplink Shared Channel
UTRA
UMTS Terrestrial Radio Access
UTRAN
UMTS Terrestrial Radio Access Network
Up

4  GeneralWord‑p. 22

4.1  Procedure Specification Principles

The principle for specifying the procedure logic is to specify the functional behaviour of the RNC exactly and completely. The CN functional behaviour is left unspecified. The EPs Relocation Preparation, Reset, Reset Resource and Overload Control are exceptions from this principle.
The following specification principles have been applied for the procedure text in clause 8:
  • The procedure text discriminates between:
    1. Functionality which "shall" be executed
      The procedure text indicates that the receiving node "shall" perform a certain function Y under a certain condition. If the receiving node supports procedure X but cannot perform functionality Y requested in the REQUEST message of a Class 1 of Class 3 EP, the receiving node shall respond with the message used to report unsuccessful outcome for this procedure, containing an appropriate cause value.
    2. Functionality which "shall, if supported" be executed
      The procedure text indicates that the receiving node "shall, if supported," perform a certain function Y under a certain condition. If the receiving node supports procedure X, but does not support functionality Y, the receiving node shall proceed with the execution of the EP, possibly informing the requesting node about the not supported functionality.
  • Any required inclusion of an optional IE in a response message is explicitly indicated in the procedure text. If the procedure text does not explicitly indicate that an optional IE shall be included in a response message, the optional IE shall not be included. For requirements on including Criticality Diagnostics IE, see section 10. For examples on how to use the Criticality Diagnostics IE, see Annex A.2.
Up

4.2  Forwards and Backwards CompatibilityWord‑p. 23

The forwards and backwards compatibility of the protocol is assured by mechanism where all current and future messages, and IEs or groups of related IEs, include ID and criticality fields that are coded in a standard format that will not be changed in the future. These parts can always be decoded regardless of the standard version.

4.3  Specification Notations

For the purposes of the present document, the following notations apply:
Procedure
When referring to an elementary procedure in the specification the Procedure Name is written with the first letters in each word in upper case characters followed by the word "procedure", e.g. RAB Assignment procedure.
Message
When referring to a message in the specification the MESSAGE NAME is written with all letters in upper case characters followed by the word "message", e.g. RAB ASSIGNMENT REQUEST message.
IE
When referring to an information element (IE) in the specification the Information Element Name is written with the first letters in each word in upper case characters and all letters in Italic font followed by the abbreviation "IE", e.g. User Plane Mode IE.
Value of an IE
When referring to the value of an information element (IE) in the specification the "Value" is written as it is specified in subclause 9.2 enclosed by quotation marks, e.g. "Abstract Syntax Error (Reject)" or "Geographical Coordinates".
Up

5  RANAP Services

RANAP provides the signalling service between UTRAN or GERAN (in Iu mode) and CN that is required to fulfil the RANAP functions described in clause 7. RANAP services are divided into four groups. The first three are based on Service Access Points (SAP) defined in TS 23.110:
  1. General control services: They are related to the whole Iu interface instance between RNC and logical CN domain, and are accessed in CN through the General Control SAP. They utilise connectionless signalling transport provided by the Iu signalling bearer.
  2. Notification services: They are related to specified UEs or all UEs in specified area, and are accessed in CN through the Notification SAP. They utilise connectionless signalling transport provided by the Iu signalling bearer.
  3. Dedicated control services: They are related to one UE, and are accessed in CN through the Dedicated Control SAP. RANAP functions that provide these services are associated with Iu signalling connection that is maintained for the UE in question. The Iu signalling connection is realised with connection oriented signalling transport provided by the Iu signalling bearer.
  4. MBMS control services: They are related to one MBMS Bearer Service. RANAP functions that provide these services are associated with one or several Iu signalling connection that is maintained for the MBMS Bearer Service in question during the MBMS Session. The Iu signalling connection is realised with connection oriented signalling transport provided by the Iu signalling bearer.
Up

6  Services Expected from Signalling Transport

Signalling transport (See TS 25.412) shall provide two different service modes for the RANAP.
  1. Connection oriented data transfer service. This service is supported by a signalling connection between RNC and CN domain. It shall be possible to dynamically establish and release signalling connections based on the need. Each active UE shall have its own signalling connection. Each MBMS Bearer Service during a given MBMS Session shall have one or several signalling connections. The signalling connection shall provide in sequence delivery of RANAP messages. RANAP shall be notified if the signalling connection breaks.
  2. Connectionless data transfer service. RANAP shall be notified in case a RANAP message did not reach the intended peer RANAP entity.
Up

7  Functions of RANAPWord‑p. 24

RANAP protocol has the following functions:
  • Relocating serving RNC. This function enables to change the serving RNC functionality as well as the related Iu resources (RAB(s) and Signalling connection) from one RNC to another.
  • Overall 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 the queuing.
  • Requesting RAB release. While the overall RAB management is a function of the CN, the RNC has the capability to request the release of RAB.
  • Release of all Iu connection resources. This function is used to explicitly release all 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.
  • SRNS context forwarding function. This function is responsible for transferring SRNS context from the RNC to the CN for intersystem change in case of packet forwarding.
  • Controlling overload in the Iu interface. This function allows adjusting the load in the control plane of the Iu interface.
  • 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 aware of the UE's Common ID.
  • Paging the user. This function provides the CN for capability to page the UE.
  • Controlling the tracing 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.
  • MDT function. This function is to enable the transfer of MDT measurements collected by the UE.
  • Transport of NAS information between UE and CN (see TS 24.008). This function has two sub-classes:
    1. Transport of the initial NAS signalling message from the UE to CN. This function transfers transparently the NAS information. As a consequence also the Iu signalling connection is set up.
    2. Transport of NAS signalling messages between UE and CN, This function transfers transparently the NAS signalling messages on the existing Iu signalling 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 setting the operation mode for security functions.
  • Controlling location reporting. This function allows the CN to operate the mode in which the UTRAN reports the location of the UE.
  • Location reporting. This function is used for transferring the actual location information from RNC to the CN.
  • Data volume reporting function. This function is responsible for reporting unsuccessfully transmitted DL data volume over UTRAN for specific RABs.
  • Reporting general error situations. This function allows reporting of general error situations, for which function specific error messages have not been defined.
  • Location related data. This function allows the CN to either retrieve from the RNC deciphering keys (to be forwarded to the UE) for the broadcast assistance data, or request the RNC to deliver dedicated assistance data to the UE.
  • Information Transfer. This function allows the CN to transfer information to the RNC.
  • 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 e.g. 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-functions:
    • MBMS RAB management. This function is responsible for setting up, updating and releasing the MBMS RAB as well as the MBMS Iu signalling connection corresponding 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 Service(s).
    • 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 capability to register/de-register to a specific Multicast Service.
  • QoE function. This function is to enable the transfer of QoE measurements collected by the UE.
These functions are implemented by one or several RANAP elementary procedures described in the following clause.
Up

Up   Top   ToC