Professional Documents
Culture Documents
Please note that at any time during the training, you can access the acronym list by clicking on the
Attachments button at the top right of the window.
The Core Network is independent of the Access Network. The specificity of the access network due to
mobile system should be transparent to the core network, which may potentially use any access
technique. The radio specificity of the access network is hidden to the core network. UE radio mobility is
fully controlled by UTRAN.
The RNC takes a more important place in UTRAN than the BSC in the GSM BSS. Indeed, the RNC can
perform soft handover, while in GSM there is no connection between BSCs and only hard handover can be
applied. Generally, the RNC is in charge of Radio resource management, the call management for the
users, the connection to the Core Network and the radio mobility management.
The RNC can take 3 roles. 2 roles with regards to the mobile (Serving RNC with which the mobile starts
the RRC connection, Drift RNC with which the mobile is currently connected during soft handover) and
one role with regards to Node B (Controlling RNC which is controlling Node B resources). At a given time,
the CRNC is then either the SRNC or DRNC.
To report the
measurments
A Node-B is also more complex than the GSM BTS, because it handles softer handover. The main role of
the Node-B is to convert the Radio signal received from the antennas into a digital signal on the E1 link
of the Iub.
The other protocols are the Radio Protocols used between the UE and the RNC. On this Uu Interface, we
use the Radio Resource Control (RRC) protocol, the Radio Link Control or RLC protocol and the Medium
Access Control or MAC protocol.
Finally, the Non Access Stratum, or NAS, refers to higher layers (from 3 to 7). Entities of this part will
exchange teleservices and bearer services.
The same general protocol model, which is illustrated here is applied for all Iu interfaces. When we look
at the model we can wonder what the purpose of the separation between the Radio Network Layer and
the Transport Network Layer is. Moreover, we can wonder why ALCAP is necessary.
ATM
IP
For IP transport of the Iub user plane over Ethernet, there are several 3GPP requirements, in TS 25426.
First, UDP over IP shall be supported as the transport for DCH data streams on Iub.
Then, the transport bearer is identified by the UDP port number and an IP address.
Moreover, the source and destination IP addresses exchanged via the Radio Network Layer on the Iur/Iub
interface shall use the NSAP structure.
Finally, IP Differentiated Services code point marking shall be supported. The mapping between traffic
categories and Diffserv code points shall be configurable by O&M. The UDP port number and IP address
which are the bearer identifiers are exchanged between RNC and Node B at each Radio Link Setup via
NBAP signaling messages. The DSCP is determined by the RNC and given to the Node B at each Radio Link
Setup via NBAP signaling messages.
For IP transport of the Iub Control plane over Ethernet, there are other 3GPP requirements, in TS 25432.
First, SCTP over IP shall be supported as the transport for NBAP signaling bearer on Iub Interface.
Then, the checksum method specified in RFC 3309 shall be used instead of the method specified in RFC
2960.
Each signaling bearer between the RNC and Node B shall also correspond to one single SCTP stream in UL
and one single SCTP stream in DL direction, both streams belonging to the same SCTP association.
IP Differentiated Services code point marking shall be supported. The DiffServ Code Point may be
determined from the application parameters.
An RNC equipped with the SCTP stack option shall initiate the INIT procedure for establishing association.
This is new in Release 7.
Finally, Multi-homing is not required.
For IP transport of the Iur User Plane, the transport bearer is identified by the UDP port number and the
IP address (source UDP port number, destination UDP port number, source IP address, destination IP
address). The source and destination IP addresses and the associated UDP port numbers are exchanged
via RNSAP and shall use the NSAP structure.
For the Iur control plane, the MTP3 User Application (or M3UA) performs a role similar to that of MTP3 in
SS7 signaling. That is, it transports messages from MTP3 users (SCCP or ISUP) to remote MTP3 users. The
difference between M3UA and MTP3 is that instead of transporting messages over SS7 networks, M3UA
transports messages over an IP network using the services of SCTP.
The Radio Access Network Application Protocol or RANAP performs RAB management, relocation of an
SRNC, transport of NAS signaling messages, paging, security mode control and location reporting.
ATM and IP stacks for Iu-PS are supported. On this interface, the SCCP supports transport of RANAP
messages used by the Control Plane. SCCP performs connectionless and connection-oriented procedures
to support the RANAP. In the ATM stack, the MTP3-B forwards the messages and manages the signaling
link connection.
SAAL-NNI is Signaling ATM Adaptation Layer and is sub-divided in the SSCF, the SSCOP and AAL5. The
AAL5/ATM used to transport IP packets across the Iu interface towards the packet-switched domain is no
longer supported.
The IP stack is sub-divided into the M3UA and the SCTP to transport the signaling on the IP network.
UDP/IP is used for the User Plane. In this release, only IPv4 is supported. Dynamic management of GTP
tunnel is ensured by the user plane towards the PS domain.
The transport bearer is identified by the GTP TEID and the IP address (source GTP TEID, destination GTP
TEID, source IP address, destination IP address).
The IP addresses and GTP TEID are exchanged between RNC and SGSN by using the RANAP protocol.
There may be one or several IP addresses in the RNC and in the CN.
In the ATM stack, MTP3-B forwards the messages and manages the signaling link connection.
As for Iu-PS, SAAL-NNI is sub-divided in SSCF, SSCOP and AAL5.
The User Plane uses the stack AAL2/ATM.
The physical layer is the OC-3/STM-1 interface.
The Transport Network Layer has an own Control Plane to manage AAL2 connections.
Radio bearers are the highest level of bearer services exchanged between UTRAN and UE.
Radio bearers are mapped successively on logical channels, transport channels and physical channels
(corresponding to the Radio Physical Bearer Service on the figure).
The Radio Protocols are independent of the applied transport layer technology that may be changed in
the future while the Radio Protocols remain intact. The main part of radio protocols are located in the
RNC (and in the UE). The Node-B is mainly a relay between UE and RNC.
One RAB can be divided into RAB sub-flows. Each sub-flow is mapped on one user plane RB. Please note
that Radio Access Bearers are only provided in the user plane.
The traffic channels are the Dedicated Traffic Channel, the Common Traffic Channel and the MBMS
Traffic Channel. They are used for the transfer of user plane information.
What does the TFS provide? The selection at each TTI of a number of transport block among the allowed
list provides the required flexibility for the variable traffic and allows one to manage the priority.
In this slide, you can see the possible mapping between logical and transport channels.
The BCCH, the CCCH, the MSCH, the MCCH, the DCCH, the CTCH and the MTCH can be mapped on the
FACH.
The BCCH can also be mapped on the BCH and the CCCH can be mapped on the RACH.
The PCCH can be mapped on the PCH.
Here you can see that the DCCH and the DTCH can be mapped on the RACH, on the FACH, on the DSCH,
on the CPCH or on the DCH.
Except for BCH and PCH, each type of transport channel can be used for the transfer of either control or
traffic logical channels.
Here, you can see that the downlink channels not associated with transport channels. The CPICH is used
as the reference for the estimation of the radio condition and measurements in the active cell. The PICH
is used for the paging message and the MICH is used for MBMS. The AICH is used to send
acknowledgement or non acknowledgement in the access process on the PRACH. Finally the P-SCH and
the S-SCH are used for synchronization.
The channels associated with transport channels are divided into two groups. The dedicated channels are
the DPDCH and DPCCH used in downlink and uplink to transport the control and user information on the
DCH.
The common physical channel are the PRACH which can support an RACH in uplink, the PDSCH which can
support a DSCH in downlink and the PCPCH which can support a CPCH in uplink. Finally, the P-CCPCH is
used to support a BCH as the S-CCPCH supports a PCH and one or several FACH. The P-CCPCH and the S-
CCPCH are downlink channels.
Some common transport channels are multiplexed on the same physical channels, such as the FACH and
the PCH on the S-CCPCH.
Following the same principles, several dedicated channels belonging to the same user are mapped on one
physical channel, the DPDCH. The DPCCH is its control channel at the physical level.
There are less channels in uplink. For the physical channels, there are the dedicated channels (DPDCH)
and the common channels (PRACH).
The PCPCH is not implemented in the Alcatel-Lucent Solution.
the transport
channel of CPCH
is removed from
standard
The radio protocols are responsible for exchanges of signaling and user data between the UE and the
UTRAN over the Uu interface.
The radio protocols are layered into the RRC, the RLC and the MAC located in the RNC* and UE, and the
physical layer (on the air interface) located in the Node-B and UE.
Two additional service-dependent protocols exist in the user plane in the layer 2: these are the PDCP and
the BMC protocols.
Each layer provides services to upper layers at Service Access Points on a peer-to-peer communication
basis. The Service Access points are marked with circles. A service is defined by a set of service
primitives.
The Radio Interface Protocol Architecture is described in 3GPP 25.301. (*except for a part of protocol
used for BCH which is terminated in the Node-B)
RRC is in charge of call management which consists of the RRC connection establishment/release (initial
access). RRC also performs radio Bearer establishment, release and reconfiguration (in the control plane
and in the user plane) and the Transport and Physical Channels reconfiguration. Another function of the
RRC protocol is the radio mobility management in the soft and hard Handover procedures, in the Cell and
URA update, in the paging procedure and the measurements control (on UTRAN side) and reporting (on
UE side). The RRC protocol has also a role in the Outer Loop Power Control to manage the radio channel
ciphering and deciphering and to control locally the configuration of the lower layers (RLC, MAC, etc.)
through Control SAP. These Control services do not require peer-to-peer communication. One or more
sub-layers can be bypassed.
The Broadcast/Multicast Services is used in the user plane to adapt broadcast and multicast services from
NAS on the radio interface.
In R99, the only service using this protocol is SMS Cell Broadcast Service (directly taken from GSM).
The RLC protocol has a role in the connection Establishment/Release which can be in 3 different
configuration modes. The first mode is the data transfer Transparent Mode. It means without adding any
protocol information. The second mode is the data transfer unacknowledged mode. It means without
guaranteeing delivery to the peer entity (but it can detect transmission errors). The third mode is the
data transfer acknowledged mode which means with guaranteeing delivery to the peer entity. The AM
mode provides a reliable link for error detection and recovery, in-sequence delivery, duplicate
detection, flow Control and ARQ mechanisms.
The RLC protocol is also responsible for transmission/Reception buffer, for segmentation and reassembly
(to adjust the radio bearer size to the actual set of transport formats), and for mapping between Radio
Bearers and Logical Channels (one to one). Finally, another function of the RLC protocol is the ciphering
for non-transparent RLC data (if not performed in MAC), using the UEA1, Kasumi algorithm specified in
R99. Encryption is performed in accordance with TS 33.102 (radio interface), 25.413, 25.331 (RRC
signaling messages) and supports the settings of integrity with CN (CS-domain/PS-domain).
The MAC protocol performs several main functions such as the data transfer (MAC provides
unacknowledged data transfer without segmentation), the multiplexing of logical channels (possible only
if they require the same QoS) and the mapping between Logical Channels and Transport Channels. The
MAC protocol is also responsible for the selection of the appropriate Transport Format for each Transport
Channel depending on instantaneous source rate, the reporting of monitoring to RRC and the Ciphering
for RLC transparent data (if not performed in RLC). Finally, the MAC protocol manages the priority
handling/Scheduling according to priorities given by upper layers (between data flows of one UE or
between different UEs). Priority Handling and Scheduling are done through Transport Format
Combination (TFC) selection.
The main functions of the Physical layer are the multiplexing/de-multiplexing of transport channels on a
Coded Composite Transport Channel (CCTrCH) even if the transport channels require different QoS, the
mapping of CCTrCH on physical channels, the spreading/de-spreading and modulation/demodulation of
physical channels and the RF processing (3 GPP 25.10x). The physical layer also performs the frequency
and time (chip, bit, slot, frame) synchronization, the measurements and indication to higher layers (e.g.
FER, SIR, interference power, transmit power, etc.) and the macro-diversity distribution/combining and
soft handover execution. The open loop and Inner loop power control are performed at physical level.
Here the important point is that all the UEs send and receive at the same time and at the same
frequency. The WCDMA is really different because with the GSM, the UEs are separated by the time (TS
of TDMA) and the frequency. Here the UEs are separated with codes applied on the signals.
Another important point is that for someone the conversation on a neighbor table is considered as being
some noise. It is the same principle with the WCDMA. For a user, the other UE generates some noise.
Here, the neighbor conversation are interference.
As a result, we can deduce that the power control and the Control admission are very important!
What is the interference level? The interference level is the power received on the UMTS bandwidth
used. These interferences are made up of the background noise, the messages of the other users, and
the traffic in the neighboring cells.
Because all the users on a cell use the same bandwidth at the same time, and the users on the other
cells too, the decoding and so the error ratio depend on the interference level.
Concerning the code synchronization, it is difficult to acquire and to maintain the synchronization of the
locally generated code signal and the received signal. Indeed synchronization has to be kept within a
fraction of the chip time.
The determination of the bit value is based on the area of the received signal. Here there are 2 area
units over 4.
power after
sppreding
spreaded power
Several pieces of information are important to analyze the signal. First, the RSSI is the total received
wideband (UTRA carrier RSSI) power over 5Mhz including thermal noise.
It is estimating the uplink interference at the Node B, and by difference with the thermal noise, the rise
due to traffic and external interference.
Second, ISCP represent interference on the received signal although the RSCP is an unbiaised power
measurement on the received signal on one channelization code.
Then, the energy bit Eb is the energy per useful bit. Finally, the Processing gain is the power gain after
despreading.
Quasi-orthogonal: it is not necessary to have primary colors at the receiver to separate the users. Red
and orange for example can also be distinguished.
Orthogonality between the codes is impossible to maintain after transfer over the radio interface (multi-
path on DL, UEs not synchronized on UL).
CDMA is unstable by nature. For example, one user may jam a whole cell by transmitting with too high
power and also too many users in one cell would have the same effect. That‟s why it requires accurate
power and congestion control.
A CDMA resource has 2 dimensions: the codes and the power. Obviously the power is the limiting factor.
The better we can control the power usage, the more capacity (users) we can allocate.
The channelization codes can be defined in a code tree, which is shared by several users. If one code is
used by a physical channel, the codes of underlying branches may not be used. The number of codes is
consequently variable: the minimum is 4 codes of length 4, the maximum is 256 codes of length 256. The
channelization code (and consequently the spreading factor) may change on a frame-by-frame basis.
The codes within each cell are managed by the RNC. There is no need to coordinate code tree resource
between different base stations or terminals. There is usually one code tree per cell. If two code trees
are used, it is necessary to use the secondary scrambling code.
The Drift RNC performs the routing of information from/to the Serving RNC. There may be up to 4 Drift
RNCs per UE.
The delay dispersion depends on the environment and is typically of 1 µs for 300m in urban areas and of
20 µs for 6000 m in hilly areas. The delay dispersion should be compared to the chip duration 0,26 µs (78
m) of the CDMA system.
If the delay dispersion is greater than the chip duration, the multipath components of the signal can be
separated by a Rake Receiver.
In this case, CDMA can take advantage of multipath propagation.
Multi-path propagation usually reduces the quality of the signal. But, in most cases, a Rake Receiver can
take advantage of multi-path to improve the quality of the signal because the dispersion is often greater
than the chip duration.
Two main power control algorithms can be distinguished: on the one hand, the Open-loop power control
(in UL only) and on the other hand, the Closed-loop power control (in UL and DL).
In the outer loop, the RNC controls parameters of the SIR estimation (outer loop) and sets the initial SIR
target, defined by the operator and modifies it according to the error measurement reports. The big
issue is to meet constantly the required quality: no worse and also no better, because it would be a
waste of capacity. The outer loop management is handled by the Controlling RNC because a soft HO may
be performed. The frequency of the outer loop is 10-100 Hz typically.
The Node-B controls the power of the UE (and vice versa) by performing a SIR estimation (inner loop)
and by generating TPC command for each time slot of the radio frame.
The RNC controls parameters of the SIR estimation (outer loop) and set the initial SIR target, defined by
the operator and modify it according to the error measurement reports.
First, the Adaptative Multi-Rate speech Codec enables to switch to a lower bit rate if the mobile is
moving out of the cell coverage area: it is a trade-off between quality and coverage. It offers 8 AMR
modes between 4,75 kbps and 12,2 kbps. It is capable of switching its bit rate every 20 ms upon
command of the RNC.
Then, the Multipath diversity consists of combining the different paths of a signal (due to reflections,
diffractions or scattering) by using a Rake Receiver.
Multipath diversity is very efficient with WCDMA.
Another possibility is the Soft or softer handover. In this case, the transmission from the mobile is
received by two or more base stations.
With the Receive antenna diversity, the base station collects the signal on two uncorrelated branches. It
can be obtained by space or polarization diversity.
Finally, the base stations algorithm is an accuracy of SIR estimation in power control process.
The quality is measured with the Block Error Ratio (BLER). You can see in this table some examples
according to different services.
The Coverage depends on the environment: For example if we have a coverage of about 300 meters in a
dense Urban Cell, we will have about 1 km in a SubUrban Cell and 3km in a rural Cell.
The capacity also depends on the radio environment (rural, suburban, indoor), the terminal speeds, the
distribution of the terminals and the load of the cell: trade-off capacity/coverage (breathing cells). Due
to all these parameters, it is harder than in GSM to give a typical value of the capacity of a cell.
When a UE requests a service, the Core Network will ask the UTRAN to assign a RAB with some
characteristics related to data to be allocated (for example the maximum bit rate), to QoS and to mobile
priority. The UTRAN must check if it has enough resources to establish new dedicated channels.
We will also see how the data are mapped on the physical channels.
In uplink, the dedicated logical channels (DTCH and DCCH) can be mapped on the DCH, the RACH and on
the CPCH.
The DCH can be mapped on the CCTrCH mapped on the physical channel DPDCH and DPCCH. But the
transport channel RACH is mapped on the physical channel PRACH. Finally the CPCH is mapped on the
PCPCH.
MIB
Just after the switch is on, the UE can decode only the P-SCH and S-SCH if it is on a covered area. The UE
synchronize itself at the slot on the P-SCH and at the frame level on the S-SCH and retrieves a group of 8
Scrambling codes. Then, the UE tests the 8 scrambling codes on the CPICH to find the SC of the cell.
Next, to read the system information, the UE decodes the BCH channel. Finally, the UE selects the best
cell.
Now, you can see the cell search procedure (also called synchronization procedure).
The first step is the slot synchronization. In all the cell of any PLMN, the P-SCH is made up of a unique &
same primary code sequence of 256 chips repeated at each Time Slot Occurrence. This is typically done
with a single matched filter (or any similar device) to the primary synchronization code which is common
to all cells. The slot timing of the cell can be obtained by detecting peaks in the matched filter output.
The UE uses it to acquire the slot synchronization to a cell.
The second step is the frame synchronization and code-group identification. The Secondary SCH (S-SCH)
contains a sequence of 15 codes which identifies the Code Group of the Downlink Scrambling Code (DL
SC) of the cell. It is made up of 15 repetitions of a secondary code sequence of 256 chips (one per Time
Slot) transmitted in perfect synchronization with the P-SCH code sequences. The UTRAN uses 64 distinct
secondary synchronization code sequences (reused in distant cells of the UTRAN). Each secondary code
sequence corresponds to a unique group of 8 possible Primary Scrambling codes
The UE uses it to acquire the frame synchronization to a cell and to identify the Code Group of the DL
SC.
Finally, the third step is the scrambling code identification. The UE determines the (primary) scrambling
code used by the found cell through symbol-by-symbol correlation over the pilot CPICH with all codes
within the Code Group identified in step 2 (8 possibilities). Afterwards the P-CCPCH can be detected and
the system- and cell-specific BCH information can be read.
It is a reference to aid the channel estimation at the terminal (time or phase reference), to perform
handover measurements and cell selection/reselection (power reference).
The UE tests the 8 DL SCs of the Group Code. The DL SC used to retrieve the pre-define sequence is the
DL SC of the cell.
The broadcast system information may come from the CN, RNC or Node-B. It contains static parameters
such as the Cell identity and the supported PLMN types. It also contains dynamic parameters such as the
UL interference level. It is arranged in System Information Blocks also called SIBs, which group together
elements of the same nature.
To make the link with the 2G network, we can now answer 2 questions.
What is the relationship with the states of the mobile phone in GSM?
In fact, the two GSM states, idle mode and connected mode, are similar to the idle mode and cell_DCH
state in UMTS.
What is the relationship with the states of the mobile phone in GPRS?
There is no correspondence between the idle, standby and ready states in GPRS and the states in UMTS.
Indeed, there is no notion of connection on GPRS.
The initial state of the UE is determined by the DCCH established during RRC connection establishment.
If the DCCH is mapped on a DCH, the UE is in cell_DCH state. If the DCCH is mapped on RACH/FACH, the
UE is in cell_FACH state.
The UE can move from one state to another during the time of the RRC connection. The transitions
between states are always triggered by UTRAN signaling and based on traffic volume measurements and
network load.
In Cell_PCH state, there is no transmission of signaling and traffic data dedicated to the UE (no DCCH and
no DTCH). But the RRC connection is still active and UE location is performed at a cell level. A DCCH (and
possibly a DTCH) can be reestablished very quickly (this procedure is initiated by sending a paging signal
PCH) .
The URA_PCH state is very similar to the cell_PCH state. But the UTRAN keeps the location of the UE at
the UTRAN Registration Area level (which corresponds to a set of UMTS cells).
What is the difference between idle mode, Cell_PCH and URA_PCH states?
In idle mode, the location of the UE is not known by the UTRAN, but only by the CN at a Location Area
(LA) or Routing Area (RA) level and sets of cells larger than URA.
The paging message PCH must then be sent in an LA or in an RA when the UE is in idle mode. Inversely, it
only needs to be sent in a cell in Cell_PCH state or in an URA when the UE is in URA_PCH state.
Consequently, the paging procedure is much faster.
When the UE has selected a cell, it has to declared its identity and its location (LA & RA) to the Core
Network.
So, it requests an RRC connection to send information about its situation to the Core Network.
The parameters are mainly the LA (=Location Area = Set of cells for the CSCN), the RA (RA = Routinf Area
= Set of cells for the PSCN) and its IMSI.
The Visitor Location Register (VLR) serves the terminal in its current location for CS services and holds a
copy of the visiting user‟s service profile. It stores the Location Area where the terminal is located.
The Serving GPRS Support Node (SGSN) serves the terminal in its current location for PS services and
holds a copy of the visiting user‟s service profile. It stores the Routing Area where the terminal is
located.
If the Radio access control has not been passed, the call can‟t be established for CS services.
For PS services, the UTRAN may try to assign a radio bearer with a lower bit rate. There are different
levels of bit rates that can be used on a given requested RAB. The Node B tries to assign first the highest,
and then goes to the lower rates, as long as the RAC rejects the Radio Link Reconfiguration.
To see if there is sufficient UL Radio Resource, we analyze the Rx RAC. We compare the UL interference
level and the estimated new user contribution to a predefined threshold.
(If UL interference level + estimated new user contribution < threshold Then Rx RAC ok)
To see if there is sufficient DL Radio Resource, we analyze the Tx RAC. We compare the Total DL Tx
Power and the estimated new user contribution to a predefined threshold.
(If Total DL Tx Power + estimated new user contribution < threshold Then Tx RAC ok)
There is a parameter managing the processing resource, which is the Processing RAC. To determine the
value of this parameter, 3 main points are checked: the channelization codes, the DSP (in BBs) load and
the number of user and radio links limited respectively to 64 users and 90 RLs.
Can the UE send user information (e.g voice call) just after Radio Access Bearer establishment?
The answer is YES. At the end of this signaling procedure, a RAB has been assigned to the UE to carry
user information. The RAB is mapped on the RB which has been set up. The RB is mapped on a Dedicated
traffic channel that is RACH/FACH or DCH.
In this procedure, a radio link is set up by the RNC on the Node-B side using the NBAP protocol (a similar
task is performed on the UE side using the RRC protocol). A terrestrial link (AAL2 bearer) is set up on the
Iub interface using the ALCAP protocol.
So UTRAN has to free a time window so that the UEs perform these measurements on other FDD
frequencies or on GSM frequencies.
The main method is to divide the SF of certain frame by 2, so it divides the length of the frame by 2.
The compressed mode method is done by puncturing: the rate matching is applied for creating a
transmission gap in one or two frames (not in UL) and by reducing the SF by 2. So Compressed frames can
be obtained by higher layer scheduling. Higher layers then set restrictions so that only a subset of the
allowed TFCs are used in a compressed frame. The maximum number of bits that will be delivered to the
physical layer during the compressed radio frame is then known and a transmission gap can be
generated.
In terms of Customer Benefits, we can say that we use an efficient delivery method to many users.
Compared to CBS, MBMS-broadcast allows high data rates and multimedia services. Moreover, it is
possible for UEs to receive this data in any state. For the operators, this means additional data revenue
streams (e.g. Mobile TV and advertising). This also means improved subscriber loyalty. Moreover, the
Transport bearer sharing unloads the transport network.
A new Mac-m layer also appears with new functionality like handling of the mapping of MTCH, PCCH to
the appropriate FACH, and Scheduling/Buffering/Priority handling of MBMS transmissions. This function is
located at RNC.
The operator can define the MBMS Service Areas in a flexible way. The service area can be as small as
one cell, and one cell can belong to up to 8 service areas.
In case of a native IP Iub, all traffic, including the MBMS PTM traffic is carried on IP/Ethernet in RNC and
in Node B. The default DSCP used for MBMS PTM are configurable in the RNC. Configured values have to
be consistent with the global IP QoS strategy on Iub. The default DSCP used for MBMS PTM Streaming and
MBMS PTM Background are different.
Page 2
A
A interface between BSC and MSC
AAL2 ATM Adaptation Layer 2
AAL5 ATM Adaptation Layer 5
A-GPS Assisted Global Positioning System
AICH Acquisition Indicator Channel
ALCAP Access Link Control Application Part
AM Acknowledged Mode
AMR Adaptative Multi Rate
ANSI American National Standards Institute (USA)
ANSI-41 American National Standard ANSI/TIA/EIA-41
ARIB Association of Radio Industries and Businesses (Japan)
AS Access Stratum
AT&T American Telephony & Telegraph
ATIS Alliance for Telecommunications Industry Solutions
ATM Asynchronous Transfer Mode
B
BCCH Broadcast Control Channel
BCH Broadcast Channel
BGCF Breakout Gateway Control Function
BICC Bearer Independent Call Control
BLER Block Error Ratio
BSC Base Station Controller
BSS Base Station Subsystem
BTS Base Transceiver Station
C
CAPEX Capital Expenditure
CBC Cell Broadcast Center
CC Call Control
CCCH Common Control Channel
CCM Core Control Module
CCTrCH Coded Composite Transport Channel
CDMA Code Division Multiple Access
CPICH Common Pilot Channel
CN Core Network
CPCH Common Packet Channel
CPU Central Processing Unit
CRNC Controlling RNC
CS Coding Scheme
CS Circuit Switching
CSCF Call Session Control Function
CSCN Circuit Switched Core Network
CTCH Common Traffic Channel
CWTS China Wireless Telecommunications Standard Group
D
DBm decibel referenced to a milliwatt
DCCH Dedicated Control Channel
DCH Dedicated Channel
Diffserv Differentiated Services
DL Downlink
DPCCH Dediated Physical Control Channel
DPDCH Dedicated Physical Data Channel
DRNC Drift RNC
DSCP Differentiated Services Code Point
DSCH Downlink Shared Channel
DTCH Dedicated Traffic Channel
Page 3
E
EDGE Enhanced Data rates for GSM Evolution
EGPRS Enhanced GPRS
EIA Electronic Industries Alliance
ETSI European Telecommunications Standard Institute
Eb Energy per useful bit
F
FACH Forward Access Channel
FDD Frequency Division Duplex
FDMA Frequency Division Multiple Access
G
Gb BSS-SGSN interface
Gc HLR-GGSN interface
GERAN GSM EDGE Radio Access Network
GGSN Gateway GPRS Support Node
GHz Giga Hertz
Gi GGSN-PDN interface
GMM GPRS Mobility Management
GMSC Gateway MSC
Gn intra-GSS interface
GPRS General Packet Radio Service
GPS Global Positioning System
Gr HLR-SGSN interface
Gs MSC-SGSN interface
GSM Global System for Mobile communications
GTP GPRS Tuneling Protocol
GTP-U GTP for transfer of user data in separated tunnels for each PDP context
H
HLR Home Location Register
HO Handover
HSDPA High-Speed Downlink Packet Access
HS-DSCH High-Speed Downlink Shared Channel
HSPA High-Speed Packet Access
HSS Home Subscriber Service
HSUPA High-Speed Uplink Packet Access
Hz Hertz
I
I-CSCF Interrogating CSCF
IEEE Institute of Electrical and Electronics Engineers
IETF Internet Engineering Task Force
IMSI International Mobile Subscriber Identity
IN Intelligent Network
IP Internet Protocol
ISCP Interference Signal Code Power
ISDN Integrated Services Digital Network
ISM Industrial Scientific Medicine
ISUP ISDN User Part
ITU International Telecommunications Unit
Iu interface between UTRAN and Core Network
Iub interface between node B and RNC
Iub-FP Iub Frame Protocol
Iu-CS interface between RNC and MSC
Iu-PS interface between RNC and SGSN
Iur interface between RNC and RNC
Iur-FP Iur Frame Protocol
Iu-UP Iu interface User Plane
Page 4
K
KB KiloByte
Kbps kilobits per second
L
LA Location Area
LAI Location Area Identity
LCG Local Cell Group
M
M3UA MTP3 User Application
MAC Medium Access Contol
MAC-m Media Access Control - MBMS
MAP Mobile Application Part
Mbps Megabits per second
MB MegaByte
MB Megabits per second
MBMS Multimedia Boradcast Multicast Service
MCCH MBMS Control Channel
Mcps Megachips per second
MCS Modulation and Coding Scheme
ME Mobile Equipment
MGCF Media Gateway Control Function
MGW Media Gateway
MHz Mega Hertz
MIB Master Information Block
MICH MBMS Indication Channel
MM Mobility Management
MSC Mobile services Switching Center
MSCH MBMS Scheduling Channel
MSS Mobile Satellite System
MT Mobile Terminal
MTCH MBMS Traffic Channel
MTP Message Transfer Part
mW milliWatt
N
NAS Non-Access Stratum
NBAP Node B Application Part
NNI Network-Node Interface
NSS Network Subsystem
O
OC Optical Channel
OMC Operation and Maintenance Center
OS Operating System
OVSF Orthogonal Variable Spreading Factor
P
PC Personal Computer
PCCH Paging Control Channel
P-CCPCH Primary Common Control Channel
PCPCH Physical Common Packet Channel
P-CSCF Proxy CSCF
PCH Paging Channel
PCU Packet Control Unit
PDC Personal Digital Cellular
PDCP Packet Data Convergence Protocol
Page 5
PDN Packet Data Network
PDSCH Physical Downlink Shared Channel
PG Processing Gain
PICH Page Indicator Channel
PLMN Public Land Mobile Network
PO Power Offset
POC Point Of Concentration
POTS Plain Old Telephone Service
PRACH Physical Random Access Channel
P-SCH Primary Synchronization Channel
PS Packet Switching
PSCN Packet Switched Core Network
PSE Personal Service Environment
PSTN Public Switched Telephone Network
PTMSI Packet Temporay Mobile Subscriber Identity
PTP Precision Timing Protocol
Q
QoS Quality of Service
R
RA Routing Area
RB Radio Bearer
RAB Radio Access Bearer
RACH Random Access Channel
RAI Routing Area Identity
RAN Radio Access Network
RANAP RAN Application Part
RLC Radio Link Control
RNC Radio Network Controller
RNL Radio Network Layer
RNS Radio Network Subsystem
RNSAP RNS Application Part
RRC Radio Resource Control
RSCP Received Signal Code Power
RSSI Received Signal Strength Indicator
RTCP Real Time Control Protocol
RTP Real-Time Transport Protocol
Rx Reception
S
SAAL
SAP Service Access Point
SAS Standalone Assisted GPS SMLC
SAT SIM Application Toolkit
SCCP Signaling Connection Control Part
S-CCPCH Secondary Common Control Channel
SCS Service Capability Server
S-CSCF Serving CSCF
SCTP Stream Control Transmission Protocol
SDU Service Data Unit
SF Spreading Factor
SGSN Serving GPRS Support Node
SIB System Information Broadcast
SIG Special Interest Group
SIM Subscriber Identity Module
SIP Session Initiation Protocol
Page 6
S
SIR Signal on Interference Ratio
SMS Short Message Service
SRB Signaling Radio Bearer
SRNC Serving RNC
SRNS Serving Radio Network Subsystem
SS7 Signaling System no.7
SSCF Signaling Connection Control Function
SSCOP Service Specific Connection Oriented Protocol
S-SCH Secondary Synchronization Channel
STM-1 Synchronous Transport Module level 1
T
T1 Standard Committee T1 Telecommunications
TD-CDMA Time Division and Code Division Multiple Access
TDD Time Division Duplex
TDMA Time Division Multiple Access
TE Terminal Equipment
TF Transport Format
TFC Transport Format Combination
TFS Transport Format Set
TIA Telecommunications Industry Association (USA)
TM Transparent Mode
TMN Telecommunications Management Network
TMSI Temporary Mobile Subscriber Identity
TR Technical Report
TRX Transmitter Receiver
TS Technical Specification
TS Time Slot
TTA Telecommunications Technology Association (Korea)
TTC Telecommunications Technology Committee (Japan)
TTI Time Transmission Interval
Tx Transmission
U
UDP User Datagram Protocol
UE User Equipment
UL UpLink
Um interface between MS and BSS
UM Unacknowledged Mode
UMTS Universal Mobile Telecommunications System
UNI User-Node Interface
USAT UMTS SIM Application Toolkit
USIM UMTS Subscriber Identity Module
UTRA UMTS Terrestrial Radio Access
UTRAN UMTS Terrestrial Radio Access Network
V
VHE Virtual Home Environment
VLAN Virtual LAN
VLR Visitor Location Register
VMSC Visited MSC
VoIP Voice over IP
VR Virtual Router
W
W Watt
WAP Wireless Application Part
WCDMA Wireless CDMA
Page 7
Page 8