3 Definitions and abbreviations

25.4013GPPRelease 17TSUTRAN overall description

Tools: ARFCN - Frequency Conversion for 5G NR/LTE/UMTS/GSM

3.1 Definitions

For the purposes of the present document, the following terms and definitions apply:

[1.28Mcps TDD – Multi-frequency Cell: If multiple frequencies are configured in one cell, the cell is defined as the multi-frequency cell.]

[1.28Mcps TDD – Primary frequency: In a multi-frequency cell, the frequency on which the P-CCPCH is transmitted is defined as primary frequency.]

[1.28Mcps TDD – Secondary frequency: In a multi-frequency cell, any frequency other than the primary frequency is defined as secondary frequency.]

ALCAP: generic name for the transport signalling protocols used to set-up and tear-down transport bearers

Cell: Radio Network object that can be uniquely identified by a User Equipment from a (cell) identification that is broadcasted over a geographical area from one UTRAN Access Point
A Cell is either FDD or TDD mode.

DCN-ID: DCN identity identifies a specific decicated core network (DCN).

Iu: interface between an RNC and an MSC, SGSN or CBC, providing an interconnection point between the RNS and the Core Network. It is also considered as a reference point

Iub: interface between the RNC and the Node B

Iur: logical interface between two RNCs
Whilst logically representing a point to point link between RNCs, the physical realisation need not be a point to point link.

Iur-g: logical interface between RNC/BSS and BSS
Whilst logically representing a point to point link between RNC/BSS and BSS, the physical realisation need not be a point to point link.

Logical Model: Logical Model defines an abstract view of a network or network element by means of information objects representing network element, aggregations of network elements, the topological relationship between the elements, endpoints of connections (termination points), and transport entities (such as connections) that transport information between two or more termination points

The information objects defined in the Logical Model are used, among others, by connection management functions. In this way, a physical implementation independent management is achieved.

Network sharing supporting UE: as defined in TS 23.251 [28].

Network sharing non-supporting UE: as defined in TS 23.251 [28].

Node B: logical node in the RNS responsible for radio transmission / reception in one or more cells to/from the UE
The logical node terminates the Iub interface towards the RNC.

Radio Resources: resources that constitute the radio interface in UTRAN, e.g. frequencies, scrambling codes, spreading factors, power for common and dedicated channels

Node B Application Part: Radio Network Signalling over the Iub

Radio Network Controller: logical node in the RNS in charge of controlling the use and the integrity of the radio resources

Controlling RNC: role an RNC can take with respect to a specific set of Node B’s
There is only one Controlling RNC for any Node B. The Controlling RNC has the overall control of the logical resources of its node B’s.

MBMS Master RNC: role an RNC can take with respect to one or more specific MBSFN cluster(s)

MRNC may be used for Inter-RNC MBSFN operation whenever dynamic synchronization of radio resources used for MBMS services is centrally controlled. There is only one MBMS Master RNC for any MBSFN cluster, which may control one or more MBSFN cluster(s). The MRNC has the overall control of the logical resources of the RNSs that are used for MBSFN operation within the MBSFN cluster(s).

Radio Network Subsystem: RNS can be either a full UTRAN or only a part of a UTRAN
An RNS offers the allocation and release of specific radio resources to establish means of connection in between an UE and the UTRAN. A Radio Network Subsystem contains one RNC and is responsible for the resources and transmission/reception in a set of cells.

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.

Drift RNS: role an RNS can take with respect to a specific connection between an UE and UTRAN
An RNS that supports the Serving RNS with radio resources when the connection between the UTRAN and the UE need to use cell(s) controlled by this RNS is referred to as Drift RNS.

Radio Access Network Application Part: Radio Network Signalling over the Iu

Radio Network Subsystem Application Part: Radio Network Signalling over the Iur

RRC Connection: point-to-point bi-directional connection between RRC peer entities on the UE and the UTRAN sides, respectively
An UE has either zero or one RRC connection.

Stand-Alone SMLC: as defined in TS 25.305 [33].

User Equipment: Mobile Equipment with one or several UMTS Subscriber Identity Module(s)
A device allowing a user access to network services via the Uu interface. The UE is defined in ref. TS 23.101 [8]. If this term is used in the context of Iur-g, it means MS in case it uses radio resources of a DBSS.

Universal Terrestrial Radio Access Network: UTRAN is a conceptual term identifying that part of the network which consists of RNCs and Node Bs between Iu an Uu
The concept of UTRAN instantiation is currently undefined.

User Datagram Protocol: as defined in IETF RFC 768 [14].

UTRAN Access Point: conceptual point within the UTRAN performing radio transmission and reception
A UTRAN access point is associated with one specific cell, i.e. there exists one UTRAN access point for each cell. It is the UTRAN-side end point of a radio link.

Radio Link: "radio link" is a logical association between a single User Equipment and a single UTRAN access point
Its physical realisation comprises one or more radio bearer transmissions.

Radio Link Set: set of one or more Radio Links that has a common generation of Transmit Power Control (TPC) commands in the DL

Uu: Radio interface between UTRAN and the User Equipment

RAB sub-flows: Radio Access Bearer can be realised by UTRAN through several sub-flows
These sub-flows correspond to the NAS service data streams that have QoS characteristics that differ in a predefined manner within a RAB e.g. different reliability classes.

RAB sub-flows have the following characteristics:

1) The sub-flows of a RAB are established and released at the RAB establishment and release, respectively.

2) The sub-flows of a RAB are submitted and delivered together at the RAB SAP.

3) The sub-flows of a RAB are carried over the same Iu transport bearer.

4) The sub-flows of a RAB are organised in a predefined manner at the SAP and over the Iu interface. The organisation is imposed by the NAS as part of its co-ordination responsibility.

Set of co-ordinated DCHs: set of co-ordinated DCHs is a set of dedicated transport channels that are always established and released in combination
Individual DCHs within a set of co-ordinated DCHs cannot be operated on individually e.g. if the establishment of one DCH fails, the establishment of all other DCHs in the set of co-ordinated DCHs shall be terminated unsuccessfully. A set of coordinated DCHs is transferred over one transport bearer. All DCHs in a set of co-ordinated DCHs shall have the same TTI.

Shared Network Area (SNA): Area consisting of one or more LA’s to which access can be controlled.

3.2 Abbreviations

For the purposes of the present document, the following abbreviations apply:

AAL ATM Adaptation Layer

AAL2 ATM Adaptation Layer 2

ALCAP Access Link Control Application Part

APN Access Point Name

ATM Asynchronous Transfer Mode

BM-IWF Broadcast Multicast Interworking Function

BMC Broadcast/Multicast Control

BSS Base Station Subsystem

CBC Cell Broadcast Centre

CBS Cell Broadcast Service

CN Core Network

CRNC Controlling Radio Network Controller

DCH Dedicated Channel

DCN Dedicated Core Network

DL Downlink

DRNS Drift RNS

DSP Domain Specific Part

EAB Extended Access Barring

E-DCH Enhanced UL DCH

EDGE Enhanced Data rates for Global Evolution

FACH Forward Access Channel

FFS For Further Study

GERAN GSM EDGE Radio Access Network

GSM Global System for Mobile Communications

GTP GPRS Tunnelling Protocol

GWCN GateWay Core Network

HPLMN Home PLMN

IDP Initial Domain Part

IPv4 Internet Protocol, version 4

IPv6 Internet Protocol, version 6

LA Location Area

L-GW Local GateWay

MAC Medium Access Control

MBMS Multimedia Broadcast Multicast Service

MCCH MBMS point-to-multipoint Control Channel

MDT Minimization of Drive-Tests

MOCN Multi Operator Core Network

MRNC MBMS Master Radio Network Controller

MSCH MBMS point-to-multipoint Scheduling Channel

MTCH MBMS point-to-multipoint Traffic Channel

NACC Network Assisted Cell Change

NAS Non Access Stratum

NBAP Node B Application Part

NNSF NAS Node Selection Fuction

NSAP Network Service Access Point

PCH Paging Channel

PLMN Public Land Mobile Network

PTM Point To Multipoint

PTP Point To Point

QoE Quality of Experience

QoS Quality of Service

RAB Radio Access Bearer

RACH Random Access Channel

RANAP Radio Access Network Application Part

RET Remote Electrical Tilting

RIM RAN Information Management

RNC Radio Network Controller

RNL Radio Network Layer

RNS Radio Network Subsystem

RNSAP Radio Network Subsystem Application Part

RNTI Radio Network Temporary Identity

SAB Service Area Broadcast

SAS Stand-Alone SMLC

SIPTO Selected IP Traffic Offload

SIPTO@LN Selected IP Traffic Offload at the Local Network

SMLC Serving Mobile Location Centre

SNA Shared Network Area

SRNC Serving Radio Network Controller

SRNS Serving RNS

S-GW Serving GateWay

TMA Tower Mounted Amplifier

TBSS Target BSS

TEID Tunnel Endpoint Identifier

TMGI Temporary Mobile Group Identity

TNL Transport Network Layer

TTI Transmission Time Interval

UDP User Datagram Protocol

UE User Equipment

UL Uplink

UMTS Universal Mobile Telecommunication System

URA UTRAN Registration Area

USIM UMTS Subscriber Identity Module

UTRAN Universal Terrestrial Radio Access Network

3.3 Notation

For the purposes of the present document, the following notations apply:

[FDD] This tagging of a word indicates that the word preceding the tag "[FDD]" applies only to FDD. This tagging of a heading indicates that the heading preceding the tag "[FDD]" and the section following the heading applies only to FDD.

[TDD] This tagging of a word indicates that the word preceding the tag "[TDD]" applies only to TDD, including 3.84Mcps TDD, 7.68Mcps TDD and 1.28Mcps TDD. This tagging of a heading indicates that the heading preceding the tag "[TDD]" and the section following the heading applies only to TDD, including 3.84Mcps TDD, 7.68Mcps TDD and 1.28Mcps TDD.

[3.84Mcps TDD] This tagging of a word indicates that the word preceding the tag "[3.84Mcps TDD]" applies only to 3.84Mcps TDD. This tagging of a heading indicates that the heading preceding the tag "[3.84Mcps TDD]" and the section following the heading applies only to 3.84Mcps TDD.

[1.28Mcps TDD] This tagging of a word indicates that the word preceding the tag "[1.28Mcps TDD]" applies only to 1.28Mcps TDD. This tagging of a heading indicates that the heading preceding the tag "[1.28Mcps TDD]" and the section following the heading applies only to 1.28Mcps TDD.

[7.68Mcps TDD] This tagging of a word indicates that the word preceding the tag "[7.68Mcps TDD]" applies only to 7.68Mcps TDD. This tagging of a heading indicates that the heading preceding the tag "[7.68Mcps TDD]" and the section following the heading applies only to 7.68Mcps TDD.

[FDD – …] This tagging indicates that the enclosed text following the "[FDD – " applies only to FDD. Multiple sequential paragraphs applying only to FDD are enclosed separately to enable insertion of TDD specific (or common) paragraphs between the FDD specific paragraphs.

[TDD – …] This tagging indicates that the enclosed text following the "[TDD – " applies only to TDD including 3.84Mcps TDD, 7.68Mcps TDD and 1.28Mcps TDD. Multiple sequential paragraphs applying only to TDD are enclosed separately to enable insertion of FDD specific (or common) paragraphs between the TDD specific paragraphs.

[3.84Mcps TDD – …] This tagging indicates that the enclosed text following the "[3.84Mcps TDD – " applies only to 3.84Mcps TDD. Multiple sequential paragraphs applying only to 3.84Mcps TDD are enclosed separately to enable insertion of FDD and TDD specific (or common) paragraphs between the 3.84Mcps TDD specific paragraphs.

[1.28Mcps TDD – …] This tagging indicates that the enclosed text following the "[1.28Mcps TDD – " applies only to 1.28Mcps TDD. Multiple sequential paragraphs applying only to 1.28Mcps TDD are enclosed separately to enable insertion of FDD and TDD specific (or common) paragraphs between the 1.28Mcps TDD specific paragraphs.

[7.68Mcps TDD – …] This tagging indicates that the enclosed text following the "[7.68Mcps TDD – " applies only to 7.68Mcps TDD. Multiple sequential paragraphs applying only to 7.68Mcps TDD are enclosed separately to enable insertion of FDD and TDD specific (or common) paragraphs between the 7.68Mcps TDD specific paragraphs.

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. RADIO LINK SETUP 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. Transport Format Set IE.

Value of an IE When referring to the value of an information element (IE) in the specification, the "Value" is enclosed by quotation marks, e.g. "Abstract Syntax Error (Reject)".

Frame When referring to a control or data frame in the specification, the CONTROL/DATA FRAME NAME is written with all letters in upper case characters followed by the words "control/data frame", e.g. FACH FLOW CONTROL control frame.