KEY TECHNOLOGIES FOR 5G NEW RADIO
Toward the Standardization of
Non-Orthogonal Multiple Access for
Next Generation Wireless Networks
Yan Chen, Alireza Bayesteh, Yiqun Wu, Bin Ren, Shaoli Kang, Shaohui Sun, Qi Xiong, Chen Qian, Bin Yu, Zhiguo Ding, Sen Wang,
Shuangfeng Han, Xiaolin Hou, Hao Lin, Raphael Visoz, and Razieh Razavi
Abstract
Non-orthogonal multiple access (NOMA) as
an efficient method of radio resource sharing has
its roots in network information theory. For gener-
ations of wireless communication systems design,
orthogonal multiple access schemes in the time,
frequency, or code domain have been the main
choices due to the limited processing capability
in the transceiver hardware, as well as the modest
traffic demands in both latency and connectivi-
ty. However, for the next generation radio sys-
tems, given its vision to connect everything and
the much evolved hardware capability, NOMA
has been identified as a promising technology to
help achieve all the targets in system capacity,
user connectivity, and service latency. This article
provides a systematic overview of the state-of-the-
art design of the NOMA transmission based on a
unified transceiver design framework, the related
standardization progress, and some promising use
cases in future cellular networks, based on which
interested researchers can get a quick start in this
area.
Introduction of Multiple Access
Radio resource is the medium in wireless com-
munications to transmit data information from
one device to another. The fundamental physical
radio resources are time and frequency, which
are usually interpreted as physical degrees of free-
dom to transmit data. The problem of multiple
access comes when multiple users are going to
be served with limited (or scarce) degrees of free-
dom in the radio resource.
Orthogonal Multiple Access
It is intuitive to consider dividing the available
degrees of freedom in an orthogonal way so that
each user’s transmission will not interfere with
another. Orthogonal multiple access (OMA)
design began very early in the development of
digital cellular communications such as the sec-
ond generation (2G) Global System for Mobile
Communications (GSM) through the recent fourth
generation (4G) Long Term Evolution (LTE). How-
ever, each generation has different ways to divide
Yan Chen, Alireza Bayesteh, and Yiqun Wu are with Huawei Technologies Co., Ltd.; Bin Ren, Shaoli Kang, and Shaohui Sun are with
China Academy of Telecommunications Technology; Qi Xiong, Chen Qian, and Bin Yu are with Samsung Research Institute China;
Zhiguo Ding is with Lancaster University; Sen Wang and Shuangfeng Han are with China Mobile Research Institute;
Xiaolin Hou is with DOCOMO Beijing Labs; Hao Lin and Raphael Visoz are with Orange Labs; Razieh Razavi is with Vodafone.
IEEE Communications Magazine • March 2018
the degrees of freedom, as illustrated in Fig. 1. The authors provide
In time-division multiple access (TDMA), time is a systematic overview
partitioned into time slots, each serving a digital of the state-of-the-art
data stream in a round-robin fashion; while in fre-
design of the NOMA
quency-division multiple access (FDMA), the avail-
able spectrum is partitioned into non-overlapped transmission based on a
frequency sub-bands, each accommodating one unified transceiver design
digital data stream. Orthogonal FDMA (OFDMA) framework, the related
is a multi-carrier multiple access scheme based standardization progress,
on the orthogonal frequency-division multiplex-
and some promising use
ing (OFDM) waveform, which enables tight and
orthogonal frequency-domain packing of the cases in future cellular
subcarriers with a subcarrier spacing inverse to networks, based on which
the symbol duration. In light of this, the time and interested researchers
frequency plane with OFDMA are divided into can get a quick start in
two-dimensional rasters, each transmitting a mod-
this area.
ulated symbol that belongs to one data stream.
On top of time and frequency resources, more
degrees of freedom can be created by introduc-
ing the code domain or spatial domain resource
together with the corresponding signaling pro-
cessing technologies. Code-division multiple
access (CDMA) is an example in which some
user-specific code signatures are used to spread
the modulated symbol by a factor of length N,
which is also known as the processing gain. Note
that the code signatures can be orthogonal to
each other, in which case CDMA can also be
taken as one type of OMA scheme, and the num-
ber of users that can be simultaneously supported
is less than or equal to N. However, it is also pos-
sible to trade off orthogonality for higher system
throughput in order to accommodate more users
simultaneously. In this sense, CDMA can also be
considered as a type of non-orthogonal multiple
access (NOMA) scheme. Similarly, spatial division
multiple access (SDMA) can be either orthogonal
or non-orthogonal, depending on which precod-
ing method is applied.
The benefit of the OMA schemes is clear, that
is, simplifying the transceiver design and avoiding
any intra-cell co-channel interference. However,
the limitations are obvious too. First, the num-
ber of users that can be served simultaneously is
limited strictly by the pool of the radio resource.
Second, careful user scheduling with dedicated
feedback channels at the expense of signaling
Digital Object Identifier:
10.1109/MCOM.2018.1700845
0163-6804/18/$25.00 © 2018 IEEE 19
 Power Frequency Power Frequency Power
User 4
User 3
User 2
User 1
User 1
User 2
User 3
User 4
User 1
User 3
User 4
User 2
(a)
Time
(b)
Time
(c)
Power/code/space Frequency Power/code Frequency
User 4
User 3
User 2
User 1
(d)
Time
(e)
Time
Figure 1. Illustrative example of different multiple access schemes: a) TDMA;
b) FDMA; c) OFDMA; d) CDMA/SDMA; e) possible NOMA solution.
overhead is needed to guarantee the orthogo-
nality.
Non-Orthogonal Multiple Access
Compared to OMA, NOMA opens the hori-
zon for a new angle of thinking. In particular,
by relaxing the constraint of orthogonal radio
resource allocation, the user scheduling problem
constrained by the limited time and bandwidth
resources is no longer a binary selection, but the
optimization of joint power, code signature, and
receiver design. As has long been predicted by
the network information theory [1], the total num-
ber of users served as well as the overall capac-
ity of the system can be greatly improved in a
NOMA network compared with that of an OMA
network, especially when advanced multi-user
detection algorithms are applied. Moreover, due
to the non-orthogonal nature, the requirement
of precise channel feedback and scheduling for
multi-user multiplexing is thus reduced, or even
removed in some scenarios.
A generic example of NOMA is described in
Fig. 1e, in which different users are multiplexed
in three domains of time, frequency, and power/
code, which means the users are not orthogonal
on any of the domains alone. However, by apply-
ing appropriate code design and time/frequen-
cy occupation patterns, users can be efficiently
decoded/separated, while better overall perfor-
mance can be achieved compared to OMA.
The rest of the article elaborates the recent
progress of NOMA standardization in the Third
Generation Partnership Project (3GPP), especial-
ly in the uplink (UL), and the basic features of
NOMA transceivers based on a unified frame-
work. The primary goal is to provide a systemat-
ic way for interested researchers to get a quick
understanding of the state-of-the-art design prin-
ciples for NOMA transceivers. Two interesting
application examples of NOMA enabled UL
grant-free transmission for small packets [2] and
NOMA enabled open-loop collaborative transmis-
sion in DL [3] are then given to further elaborate
the benefit of NOMA. Conclusions and challeng-
es are also outlined at the end of the article to
shed light on possible future works.
20
Frequency NOMA Standardization
Progress in 3GPP
The design of 5G radio networks is targeting
higher capacity, larger connectivity, and lower
latency, which shall not only provide better user
experience for enhanced mobile broadband
(eMBB) services, but also connect to new vertical
Time
industries and new devices, creating advanced
application scenarios such as massive machine
User 1 type communication (mMTC) and ultra reliable
User 2 low latency communication (URLLC) services.
The mMTC application scenario aims to support
User 3 a massive number of devices simultaneously,
User 4 while the URLLC scenario enables mission-critical
User 5 transmissions with ultra high reliability and ultra
low latency. Toward these goals and among all
User 6
components in the radio link design, NOMA has
attracted great attention across both academia
and industry [2–15].
For instance, the application of NOMA in
eMBB is expected to increase the multi-us-
er capacity, provide better fairness against the
near-far effect, and improve user experience in
ultra dense networks. For the URLLC scenario,
the application of NOMA can enable ultra reli-
able link quality when contention-based grant-free
transmission is applied to achieve ultra low laten-
cy. It is also important to point out that the appli-
cation of NOMA enables efficient multiplexing
of URLLC and eMBB services to further improve
resource utilization. Finally, for the mMTC scenar-
io, NOMA is by far the most competitive solution
to address the massive connectivity issue together
with the large coverage requirement. In the fol-
lowing, we elaborate the recent NOMA standard-
ization progress in 3GPP for both downlink (DL)
and UL, respectively.
DL NOMA Standardization
The recent study of NOMA in 3GPP started in
LTE Release-13 under the name Multi-User Super-
posed Transmission (MUST), mainly focusing on
DL transmission. The MUST schemes can be cat-
egorized into three categories [5]. In MUST Cate-
gory 1, coded bits of two or more co-scheduled
users are independently mapped to component
constellation symbols, but the composite constel-
lation does not have Gray mapping. In MUST Cat-
egory 2, coded bits of two or more co-scheduled
users are jointly mapped to component constel-
lations, and then the composite constellation has
Gray mapping. In MUST Category 3, coded bits
of two or more co-scheduled users are directly
mapped onto the symbols of a composite con-
stellation.
It is expected that in the future, MUST
schemes, possibly with some new features, will be
considered in 5G. The evolved techniques may
also be combined with the beam management
techniques designed in the scenario with a large
number of transmit and/or receive antennas.
UL NOMA Standardization
In 3GPP Release-14 study for New Radio (NR)
system design, 15 NOMA schemes have been
proposed, mainly targeting UL transmissions to
support massive connectivity and to enable the
newly defined grant-free transmission procedures
with low latency and high reliability. A full list of
IEEE Communications Magazine • March 2018
schemes and the corresponding 3GPP contribu-
tions describing the schemes are given below.
• Sparse code multiple access (SCMA)
• Multi-user shared access (MUSA)
• Low code rate spreading
• Frequency domain spreading
• Non-orthogonal coded multiple access
(NCMA)
• Non-orthogonal multiple access (NOMA)
• Pattern division multiple access (PDMA)
• Resource spread multiple access (RSMA)
• Interleave-grid multiple access (IGMA)
• Low density spreading with signature vector
extension (LDS-SVE)
• Low code rate and signature-based shared
access (LSSA)
• Non-orthogonal coded access (NOCA)
• Interleave-division multiple access (IDMA)
• Repetition-division multiple access (RDMA)
• Group orthogonal coded access (GOCA)
It was hard to reach a final decision on the
down selection of the schemes in the limited study
period; however, comprehensive link-level and
system-level simulations have been performed by
different companies to justify the gain of NOMA
over OFDMA, which is used as an OMA baseline.
From the comprehensive simulation campaign, it
has been agreed that for the evaluated scenarios,
significant benefit of NOMA can be observed in
terms of UL link-level sum throughput and over-
loading capability, as well as system capacity
enhancement in terms of supported packet arrival
rate (PAR) at a given system outage level such as
1 percent packet drop rate (PDR).
Moreover, a new Study Item (SI) has been
approved to continue studying UL NOMA
schemes in Release-15. The content of the SI will
cover transmitter side signal processing, multi-us-
er receiver design and complexity analysis, and
NOMA related procedures such as hybrid auto-
matic repeat request (HARQ), link adaptation,
and power/signature allocation. In addition, this
new study will also include more evaluation work
continued from performance metrics identified in
Release-14 and for all scenarios including eMBB,
URLLC, and mMTC, taking into consideration
more realistic modeling of non-ideal impairment
at both the transmitter and receiver side, such as
the potential peak-to-average power ratio (PAPR)
issue, channel estimation error, power control
accuracy, and NOMA signature collision.
Basic Features and
Unified Design Framework
In this section, we shall introduce the basic fea-
tures and design principles of NOMA schemes
based on a unified transceiver framework. The dis-
cussion will mainly focus on UL NOMA where the
random channel is applied to each user before
the multiple data signals from different users are
multiplexed together. Such a property prevents
the design of joint constellation with superposi-
tion in advance as in MUST category 2 and 3, and
calls for design from the per user (or per layer)
aspect that can accommodate the randomness
brought by the user-specific channels.
In general, each UL NOMA scheme at the
transmitter side by nature tries to map the
information bits to the available transmission
IEEE Communications Magazine • March 2018
OFDM
Bit-level operations Symbol-level operations operations
User-specific MA signature design under the framework
Bit-level Modulated Symbols
FEC interleaver symbol sequence to RE IFFT
/scrambler generator mapping
Cell/user- Single tone or multi-tone modulation
specific bit UE-specific symbol spreading
interleaver/ Cell/user-specific symbol
scrambler
interleaver/scrambler Channel
Sparse/non-sparse resource mapping
Power adjustment
Advanced receivers with multi-user detector and outer-loop structure
FEC bit decoder Symbol detector and FFT
demapper
Hard SIC/PIC Single-user detector
Soft SIC/PIC Joint multi-user detector
Figure 2. Unified framework for UL NOMA design.
resources by some user-specific operations to
facilitate decoding of the superposed multi-us-
er data at the receiver side with reasonable
complexity. These operations can involve both
the bit domain and symbol domain signal pro-
cessing, which can be unified in a general
framework as shown in Fig. 2. The differenc-
es between the NOMA schemes will then be
reflected in NOMA signature design at the
transmitter side by configuring all or a subset of
these component blocks.
Transmitter Side Building Blocks
Following the unified framework in Fig. 2, each
NOMA signature is a combination of different
components along the framework at the transmit-
ter side. Since the forward error correction (FEC)
coding and OFDM operation blocks are common
for all the NOMA schemes, the unique features of
any proposed NOMA transmitter design are thus
characterized by the three component blocks:
• Bit-level interleaver and/or scrambler
• Modulated symbol sequence generator
• Symbol to resource element (RE) mapping
Within each of these three component blocks,
there are further options to be configured, as illus-
trated below.
Bit-Level Interleaver and/or Scrambler: In
the current LTE system, both user-specific and
cell-specific bit scrambling can be applied. The
main benefit of having interleaving or scrambling
is to randomize the inter-user/inter-cell interfer-
ence. Then it is interesting to find out whether
a user-specific bit interleaver could bring extra
benefits on top of the user-specific bit scrambling,
and whether it could further facilitate symbol
domain NOMA signature design.
Modulated Symbol Sequence Generator:
This block converts the sequence of input coded
bits to a sequence of symbols to be mapped to
the REs that transmit over the air. The details of
how streams of bits are converted to streams of
symbols can be configured to be user-specific.
This block includes different ways of modula-
tion, spreading, and interleaver/scrambler that
21
 1100
MCS 1100 1100
conf. MCS
1100 conf.
1100
Info Coded
bits bits m1*s1 m1*s2 m1*s3 m1*s4 Info Coded
FEC m1 m1
S/P bits FEC bits
encoder S/P 0 0
s1 s2 s3 s4 encoder
Spreading sequence

(a) (b)

1100 1100 1100 0000 0000

MCS MCS
conf. conf. 0011
0010
1100 1100
0010
Info Coded Info Coded 1111 0011 1111
bits bits m1 m2 bits bits m1 m2
FEC FEC
S/P 0 0 S/P 0 0
encoder encoder

(c) (d)
RE 1 RE 1
RE 2 = + + + + + RE 2 = + + + + +
RE 3 RE 3
RE 4 RE 4
User User User User User User User User User User User User
1 2 3 4 5 6 1 2 3 4 5 6
(e) (f)

Figure 3. Illustration of different spreading features: a) sequence-based non-sparse spreading; b) repetition-based sparse spreading;
c) independent modulation-based sparse spreading; d) Joint modulation based sparse spreading; e) example of 6 sparse-spreading-
based NOMA signatures design of length 4 with equal weights (the number of non-zero elements in each signature is the same);
f) example of 6 sparse-spreading-based NOMA signatures design of length 4 with unequal weights (the number of non-zero ele-
ments in each signature is different).

can be configured by each user to construct
its own NOMA signatures. For NOMA signa-
tures that include the feature of symbol-level
spreading, the spreading length, spreading type
(modulation dependent or not), and spreading
signatures/codebooks can be designed to facili-
tate the multi-user detection at the receiver side.
Besides the configured symbol-level spreading,
symbol-level interleaving/scrambling may be con-
figured by each user as another dimension to help
distinguish users and/or randomize interference.
Moreover, power adjustment as a power domain
feature can be configured with and without the
other spreading/scrambler features.
Symbol to RE Mapping: Symbol-to-RE map-
ping can be non-sparse (i.e., all symbols take all
available REs), or sparse (i.e., symbols occupy
only a portion of the available REs). In the latter
case, the sparsity level and the symbol-to-RE map-
ping pattern can be configured to be user-specific
to facilitate multi-user detection. Note that sparse
symbol-to-RE mapping can also be interpreted as
part of spreading in the sense that the actual REs
for the group of information bits are expanded by
adding zero tones.
One of the key tasks of the NOMA SI in
Release-15 is to figure out how to configure each
of these building blocks so that different per-
formance metrics such as block error rate, con-
nection density, throughput, PAPR, and energy
efficiency can be achieved for each of the eMBB,
URLLC, and mMTC scenarios with scenario-specif-
ic requirements and assumptions.
Example of Configurations: Having discussed
different options in each component block, Fig. 3
shows some examples of configured features at
the symbol level with different types of spreading
and RE mapping.
•Example configuration 1: Sequence-based
non-sparse spreading. In this configuration, per
symbol modulation is applied together with
sequence-based spreading and non-sparse sym-
bol-to-RE mapping, as shown in Fig. 3a. The opti-
mization variables in this configuration mainly lie
in the design of the low correlation spreading
sequence [6].
•Example configuration 2: Repetition-based
sparse spreading. In this configuration, per sym-
bol modulation is applied together with repeti-
tion-based spreading and sparse symbol-to-RE
mapping, as shown in Fig. 3b. The optimization
variables in this configuration lie in the choices of
spreading length and sparsity patterns with equal
or unequal weights [7], as shown in Figs. 3e and
3f, respectively.
•Example configuration 3: Independent mod-
ulation-based sparse spreading. In this configu-
ration, per symbol modulation with independent
bit groups is applied as well as interleaved zero
tones to have sparse symbol-to-RE mapping, as
shown in Fig. 3c. The optimization variables in
this configuration mainly depend on the symbol
interleaver design to introduce zeros into a block
of non-zero symbols with user-specific sparsity
patterns. By selecting different levels of sparsity,
this configuration can have the flexibility to trade
between larger channel coding gain and less
inter-user interference [8].
•Example configuration 4: Joint modula-
tion-based sparse spreading. In this configuration,
joint multi-symbol modulation with good distance
properties (Euclidean and/or product) among the

22 IEEE Communications Magazine • March 2018

 Received Decoded Received Decoded EPA takes a next step to
symbols bits symbols MU FEC bits
SU detector decoder reduce complexity by
detector De- FEC such as De-

•••

•••

•••

•••

•••

•••

•••
•••

•••
such as mapping decoder MPA/EPA/ mapping iteratively approximating
MF/MMSE FEC
MMSE/ESE decoder the posterior probability
1st stage 1st stage LLR of undecoded bit streams distribution as a Gauss-
••• ••• ian distribution, thus
Signal Signal Signal Signal
changing the message
•••

•••

•••

•••
cancel rebuild cancel rebuild
••• passing procedure to
Decoded Decoded
bits MU FEC bits
SU detector decoder update means and
detector De- FEC De-
such as
•••

•••

•••

•••

•••

•••

•••
•••

•••
such as mapping decoder MPA/EPA/ mapping variances only, whose
MF/MMSE FEC
MMSE/ESE decoder complexity grows lin-
•••
2nd stage 2nd stage early with the number
•••

•••
(a) (b) of users.

Figure 4. Illustration of typical receiver structures for NoMA multi-user detection: a) SU detector with hard
SIC; b) MU detector with hybrid soft and hard PIC.

points in the overall multi-symbol constellation is
applied together with sparse symbol-to-RE map-
ping, as shown in Figure 3d. The optimization vari-
ables in this configuration mainly lie in the joint
multi-symbol constellation design to maximize the
coding/shaping gain compared with per symbol
modulation and spreading, and also in the selec-
tion of spreading length and sparsity patterns to
adaptively trade between higher signal diversity
and lower inter-user interference based on scenar-
io requirement [9]. Note that in this configuration,
similar to example configurations 1 and 2, code
domain interference suppression techniques are
applied, and similar to example configurations
2 and 3, sparse symbol-to-RE mapping is intro-
duced for supporting more superposed users with
affordable receiver complexity. In addition, this
configuration exploits the modulation domain
optimization, which can further improve spectrum
efficiency.
Receiver Side Structures
In theory, the optimal multi-user receiver needs
a fully joint design of symbol-level detection and
bit-level FEC decoding, which, however, has
prohibitively high complexity for practical imple-
mentation. The other extreme is to completely
separate the two operations, which is simple but
may suffer from severe performance degradation
as compared with the joint design. In practical
systems, one can come up with a more realistic
design where a unified turbo-like outer-loop struc-
ture is adopted to allow iterations between the
symbol detector and the FEC decoder. This tur-
bo-like outer loop structure is briefly illustrated in
Fig. 2.
Both the single-user (SU) detection and joint
multi-user (MU) detection can be applied to
the symbol detector and demapper block. Here
SU detection means that a single user’s signal is
detected treating other users’ signals as noise,
while MU detection means multiple users’ sig-
nals are decoded together, and decoding one
user’s data uses information from the signal of
other users. A classic SU detector includes algo-
rithms such as the matched filter (MF) and SU
minimum mean square error (MMSE) estimator,
while a typical MU detector includes the maxi-
mum a posteriori probability (MAP) algorithm,
maximum likelihood (ML) algorithm, message
passing algorithm (MPA) [10], and expectation
propagation algorithm (EPA) [11], as well as the
MU MMSE estimator [6] and elementary signal
estimator (ESE) [12], and so on. Note that in the
case of spreading, the MAP/ML and MMSE can
be done either in a block-based way (perform the
detection method jointly for the-based manner
(e.g., chip-by-chip MAP [8]), in which the latter
has lower complexity.
In particular, MAP and ML refer to the opti-
mal receivers based on the maximum a posteri-
ori probability decision criterion and maximum
likelihood decision criterion, respectively. With a
uniform prior probability, MAP is equivalent to
ML. MPA can be considered as a kind of approx-
imation of MAP/ML detector by introducing the
message passing procedure on the factor graph
to replace the direct probability calculation [9],
where the sparsity in NOMA signature can further
reduce its complexity compared with ML detec-
tion but keep similar performance. EPA takes
a next step to reduce complexity by iteratively
approximating the posterior probability distribu-
tion as a Gaussian distribution, thus changing the
message passing procedure to update means and
variances only, whose complexity grows linearly
with the number of users.
On top of all these detectors, successive inter-
ference cancellation (SIC) can be applied in the
outer-loop structure with either hard SIC or soft
SIC operations. Specifically, for hard SIC oper-
ation, only the successfully decoded signals are
cancelled, and no soft information is fed from the
FEC decoder back to the symbol detector for the
unsuccessfully decoded data streams, as shown
in Fig. 4a. For soft SIC, on the contrary, soft infor-
mation from the FEC decoder such as extrinsic
log-likelihood ratio (LLR) is fed back to the sym-
bol detector as the prior information for the next
round of detection. Note that for the joint MU
detector, parallel interference cancellation (PIC)
instead of SIC can be applied to reduce decoding
latency. Hard PIC and soft PIC can be combined
in the sense that for users with decoded bits,

IEEE Communications Magazine • March 2018 23

 Packet Receive Send 1ms Frequency
arrival Send SR UL grant data delay bound

Grant-
C1 C2 ••• CM
NOMA signature set
based
Mapping
Packet Send 3 slots Time
arrival data
One slot with 7
OSs, 60 kHz SCS, 8
Grant- P1 P2 ••• PN
Pilot/RS set
free
slots/ms
Time

7 slots Time Frequency

Packet Receive
arrival Send SR UL grant
One slot with 7
OSs, 30 kHz SCS, Grant- Contention region
4 slots/ms based
UE1 UE2 UE3 UE4
Packet Send 0 slot Time
arrival data
NoMA signatures
Grant- overlaid on time-
Max available Tx free frequency resources
opportunities before
1 ms delay bound
Time Time
3 slots
(a) (b)
NOMA-enabled grant-free in URLLC NOMA-enabled grant-free in mMTC
100.00% 0.016
OMA, Pkt 40 Byte NOMA, Pkt 40 Byte
90.00% OMA, Pkt Pareto NOMA, Pkt Pareto
0.014
80.00%
0.012
70.00%
3.52 X
US satisfied ratio

60.00% 0.01
PDR 1.88 X
50.00% 0.008
40.00%
0.006
30.00%
0.004
20.00%
10.00% OMA, 15RB, 3partitions NoMA, 15RB 0.002
OMA, 25RB, 5partitions NoMA, 25RB
0.00% 0
0.5 0.75 1 1.25 1.5 0 0.05 0.1 0.15 0.2
PAR (pkt/ms/user) PAR (pkt/ms/sector)

PAR @ 1500 OMA NOMA Gain (times)

PAR @ PDR 1% OMA NOMA Gain (times)
15 RB (3 partitions for OMA) 0.2667 0.9381 3.52
Pkt size = 40 Bytes 0.08 0.15 1.88
25 RB (5 partitions for OMA) 0.3875 0.9952 2.57
Pkt size = Pareto 0.1 0.175 1.75

(c)
(d)

Figure 5. Illustration and benefit of NOMA-enabled grant-free network: a) illustrative example of how grant-free URLLC can have more
data repetition/retransmission opportunities; b) illustrative example of how a NOMA-enabled grant-free network works: c) example
performance gain of NOMA-enabled grant-free over OFDMA-based grant-free in terms of the ratio of satisfied users (successfully
delivering more than 99.99 percent of its total packets each within 1 ms) among all users at given PAR in the URLLC scenario;
d) example performance gain of NoMA-enabled grant-free over OFDMA-based grant-free in terms of supported PAR at given PDR
(e.g., 1 percent) in the mMTC scenario with extreme coverage case (maximum coupling loss, MCL, of 164 dB) considered.

reconstruction and cancellation are performed,
while for those users with non-decoded bits, soft
LLR can be fed back as inputs for the symbol
detector, as shown in Fig. 4b.
Use Cases in Cellular Networks
NOMA-Enabled Grant-Free Transmission
Grant-free transmission is a mechanism that elim-
inates the dynamic scheduling request (SR) and
grant signaling overhead for UL data transmission,
and a user can transmit UL data in an “arrive-
and-go” manner [2]. The benefits of grant-free
transmission include overhead reduction, latency
reduction, and energy saving, especially at the
user side with longer sleeping time.
With grant-free transmission, contention is
usually allowed to increase the system resource
utilization, that is, the users may transmit on the
same time and frequency resource as there is no
coordination from the base station. In this case,
NOMA-based grant-free transmission will show its
advantage as a solution for contention resolution
with high reliability, since it is designed with high
overloading capability. The design of NOMA-based
grant-free transmission has been proposed and
discussed during Release-14 NR Study, in which
NOMA signatures are taken as part of grant-free
resource besides the traditional physical resource
such as time and frequency resource. Prior to
transmission, a user can either randomly select one
NOMA signature to transmit from a given resource
pool or transmit with a pre-configured NOMA sig-
nature. Then in each contention region (the basic
unit of physical resource for grant-free transmis-
sion), multiple NOMA signatures from different
users will be multiplexed, as shown in Fig. 5b. User

24 IEEE Communications Magazine • March 2018

 One design challenge
for NOMA-based grant-
free transmission is to
deal with the potential
signature collision,
which will happen in
the case of random
signature selection, or
when the number of
(a) (b) potential users is much
larger than the pool size
Serving TP Cooperating TP Serving TP Cooperating TP
Tx - 1 Tx - 2 Tx - 3 Tx - 4 Tx - 1 Tx - 2 Tx - 3 Tx - 4 of the NOMA
Signal of signatures.
user 2

Signal of Signal of User 2

user 1 user 1
Signal targeting Strong
to user 1 (open interference (soft
loop joint interference
transmission cancellation with
CoMP) joint detection at
User 1 User 1 user 1)

(c) (d)

Figure 6. Illustration of NOMA-enabled open-loop collaborative communications: a) application of

NOMA-enabled CoMP transmission in UDN scenarios; b) application of NOMA-enabled CoMP trans-
mission in high mobility networks; c) NOMA-based open-loop join transmission; d) NOMA-based inter-
ference cancellation.

specific pilots are assumed for user activity identifi-
cation and channel estimation.
One design challenge for NOMA-based grant-
free transmission is to deal with the potential sig-
nature collision, which will happen in the case of
random signature selection, or when the number
of potential users is much larger than the pool
size of the NOMA signatures. This demands the
consideration of collision robustness in the com-
ponent configuration at the transmitter side and
the selection of collision-resilient MU detectors at
the receiver side. Moreover, with more users mul-
tiplexed together, how to guarantee good user
detection performance and channel estimation
quality offered by the extended pool of pilots is
another interesting topic to explore [13].
Some example system-level simulation results
are shown in Figs. 5c and 5d for URLLC and mMTC
scenarios, respectively. The attributes of simulation
methodology including physical layer abstraction are
delineated in [14]. In each figure, NOMA (taking
SCMA as an example) enabled grant-free transmis-
sion is compared with OFDMA-based grant-free
transmission with the same parameter settings
(e.g., the same traffic model and path loss model,
the same total available bandwidth, and the same
average power per user). It can be observed
from the figures that with NOMA design, at the
same PAR, the ratio of satisfied users (i.e., both
the latency and reliability requirement are met) in
URLLC can be significantly increased. The smaller
the total bandwidth, the larger the gain. And in
the mMTC case, even with some users in very
deep coverage, NOMA-enabled grant-free trans-
mission could still bring about 88 percent gain at
1 percent system PDR.
NOMA-Enabled Collaborative Communications
One of the solutions for interference coordina-
tion in wireless networks is cooperation among
transmit points (TPs) which is also known as
coordinated multipoint (CoMP) transmission.
Most proposed CoMP schemes in 3GPP up to
Release-14 are closed-loop precoding based on
the short-term channel state information (CSI)
feedback from users to the cooperating TPs. CSI
feedback can be quite challenging in future net-
works due to an excessive number of users and
TPs, especially for ultra dense networks (UDNs)
where a user is seen by a large number of TPs.
NOMA with inter-TP layer assignment through
a central scheduler can provide an open-loop
CoMP solution without the knowledge of short-
term multi-TP CSI [3]. It can bring two main
advantages to the system:
• Dramatic reduction of the overhead caused
by dynamic multi-TP CSI feedback
• Significant increase of the robustness to
channel aging
More specifically, in an open-loop CoMP solution
enabled by NOMA, different NOMA signature
sets are assigned to different TP antennas. Each
transmit antenna uses a specific NOMA signature
set to multiplex UEs. Terminals jointly detect the
signals from multiple TPs within their CoMP col-
laborative cluster. The cluster size depends on
the network topology. On the other hand, a TP
may serve multiple users if they have overlapped

IEEE Communications Magazine • March 2018 25


Recent studies have
demonstrated the
transmission features of
massive MIMO, such as
geometric channel cor-
relation and the use of
finite resolution analog
beamforming, facilitate
the implementation
of NoMA in massive
MIMO scenarios, and
improve the spectral
efficiency significantly
compared to the OMA
scenarios.
26
CoMP clusters. It enables user-centric CoMP via
NOMA signature allocation across multiple TPs.
Multiple links to a user can facilitate soft handover
across a UDN network or high-mobility networks
such as in vehicle-to-everything (V2X), as shown
in Figs. 6a and 6b, where frequent handover
becomes a technical challenge.
Note that a neighboring TP can be either a
cooperating TP or an interfering TP. In the coop-
erating TP case of Fig. 6c, the signal from a
neighboring TP targets the same user, and the
open-loop joint transmission is performed to
improve the coverage for cell edge users. An alter-
native CoMP solution is to use the NOMA receiv-
er for soft interference cancellation, as shown in
Fig. 6d. Moreover, the mode of joint transmission
and soft interference cancellation through an MU
detector can be combined to improve both the
cell edge and cell average throughputs, especially
in a UDN network.
Summary and Future Directions
In summary, NOMA is an attractive solution to
boost the system capacity by accommodating
more users at the same time/frequency resource,
reduce system latency caused by scheduling and
queueing to guarantee inter-user orthogonality, as
well as to relax the dependency on precise CSI and
feedback quality. In particular, for UL, NOMA-en-
abled grant-free is a competitive solution for small
packet transmission in many scenarios including
mMTC, URLLC, and eMBB, while for DL, besides
MUST, a NOMA-enabled open-loop CoMP solu-
tion can be attractive in UDNs and high-mobility
networks to help boost cell edge performance and
solve the frequent handover issues.
In the coming study of 3GPP NOMA SI, more
works will be dedicated to comprehensive eval-
uations of the various candidate schemes based
on the unified framework to better understand
the commonality and differentiation of differ-
ent schemes, and thus to find the recommend-
ed configurations for different target scenarios.
Moreover, as other technologies are evolving in
parallel in 3GPP, the study of how these radio
technologies can be integrated with NOMA
shall be carried out. As one example, the inte-
gration of NOMA with massive multiple-input
multiple-output (MIMO) has been raised in the
literature [15]. Recent studies have demonstrated
the transmission features of massive MIMO, such
as geometric channel correlation and the use of
finite resolution analog beamforming, facilitating
the implementation of NOMA in massive MIMO
scenarios and improving the spectral efficiency
significantly compared to the OMA scenarios.
References
[1] T. M. Cover and J. A. Thomas, Elements of Information The-
ory, Wiley, 2012.
[2] K. Au et al., “Uplink Contention Based SCMA for 5G Radio
Access,” Proc. IEEE GLOBECOM Wksp. Emerg. Tech. for 5G
Wireless Cellular Net., Austin, TX, 2014, pp. 900–05.
[3] U. Vilaipornsawai et al., “SCMA for Open-Loop Joint Trans-
mission CoMP,” Proc. IEEE VTC-Fall, Boston, MA, 2015, pp.
1–5.
[4] L. Dai et al., “Non-Orthogonal Multiple Access for 5G:
Solutions, Challenges, Opportunities, and Future Research
Trends,” IEEE Commun. Mag., vol. 53, no. 9, Sept. 2015,
pp. 74–81.
[5] Y. Yuan et al., “Non-Orthogonal Transmission Technology
in LTE Evolution,” IEEE Commun. Mag., vol. 54, no. 7, July
2016, pp. 68–74.
[6] N. Yee et al., “Multi-Carrier CDMA in Indoor Wireless Radio
Networks,” IEICE Trans. Commun., vol. 77, no. 7, July 1994,
pp. 900–04.
[7] S. Chen et al., “Pattern Division Multiple Access (PDMA)
— A Novel Non-Orthogonal Multiple Access for 5G Radio
Networks,” IEEE Trans. Vehic. Tech., vol. 66, no. 4, Apr.
2017, pp. 3185–96.
[8] Q. Xiong et al., “Advanced NOMA Scheme for 5G Cellular
Network: Interleave-Grid Multiple Access,” Proc. IEEE GLO-
BECOM Wksp. NOMA Tech. for 5G, Singapore, 2017.
[9] M. Taherzadeh et al., “SCMA Codebook Design,” Proc. IEEE
VTC-Fall, Vancouver, Canada, 2014, pp. 1-5.
[10] R. Razavi et al., “On Receiver Design for Uplink Low Den-
sity Signature OFDM (LDS-OFDM),” IEEE Trans. Commun.,
vol. 60, no. 11, Nov. 2012, pp. 3499–3508.
[11] X. Meng et al., “Low Complexity Receiver for Uplink SCMA
System Via Expectation Propagation,” Proc. IEEE WCNC, San
Francisco, CA, 2017, pp. 1–5.
[12] P. Li et al., “Interleave Division Multiple-Access,” IEEE Trans.
on Wireless Commun., vol. 5, no. 4, Apr. 2006, pp. 938–47.
[13] A. Bayesteh et al., “Blind Detection of SCMA for Uplink
Grant-Free Multiple-Access,” Proc. IEEE ISWCS, Barcelona,
Spain, 2014, pp. 853–57.
[14] M. Cheng et al., “PHY Abstraction and System Evaluation
for SCMA with UL Grant-Free Transmission,” Proc. VTC-
Spring Wksp. Emerg. NOMA Tech. for 5G, Sydney, Australia,
2017, pp. 1–5.
[15] Z. Ding et al., “A Survey on Non-Orthogonal Multiple
Access for 5G Networks: Research Challenges and Future
Trends,” IEEE JSAC, vol. 35, no. 10, Oct. 2017, pp. 2181–95.
Biographies
Yan Chen (bigbird.chenyan@huawei.com) received her B.Sc.
and Ph.D. degrees in 2004 and 2009, respectively, from Zhe-
jiang University. She was a visiting researcher at Hong Kong
University of Science and Technology from 2008 to 2009. She
joined Huawei Technologies (Shanghai) in 2009 and was the
project leader of Green Radio research from 2010 to 2013.
She is now technical leader of multiple access research and
standardization. She won the IEEE Advances in Communications
award in 2017.
Alireza Bayesteh (Alireza.Bayesteh@huawei.com) received his
Ph.D. in electrical and computer engineering from the University
of Waterloo, Canada, in 2008. Since 2011, he has been with
Huawei Canada, Ottawa, where he is currently a staff engineer.
His research interests include 5G wireless communications with
focus on NOMA.
Yiqun Wu (wuyiqun@huawei.com) received his Ph.D. degree in
electronic engineering from Tsinghua University, China, in 2012.
Since 2012, he has been with Huawei Technologies, Shanghai,
China. His research interests include energy-efficient wireless
networks, new waveforms, and multiple access schemes for 5G.
Bin Ren (renbin@catt.cn) received his M.S. and Ph.D. degrees
from Beijing University of Posts and Telecommunications, China,
in 2009 and 2017, respectively. Since 2009, he has been with
the Key Laboratory of Wireless Mobile Communications, China
Academy of Telecommunication Technology, Beijing, China.
His research interests include pattern-division multiple access,
non-orthogonal multiple access, and 5G wireless communi-
cations systems. He has published 10 academic papers and
applied for more than 32 patents.
Shaoli Kang (kangshaoli@catt.cn) received her Ph.D. in elec-
tronic engineering from Beijing Jiaotong University, China.
She joined Datang Telecom Group in 2000 doing research
on TD-SCDMA. She was a research fellow at the University of
Surrey, United Kingdom, during 2005–2007. Since September
2007, she has been working in Datang, focusing on 4G and 5G
technologies. She was in charge of the China 863 5G project
“R&D on 5G Novel Modulation and Coding Technologies.”
S haohui S un (sunshaohui@catt.cn) received his Ph.D. from
Xi’dian University, China, in 2003, and was a postdoctoral fellow
with the China Academy of Telecommunication Technology
in 2006. Since 2011, he has been the chief technical officer
with Datang Wireless Mobile innovation Center of the China
Academy of Telecommunication Technology. He is involved in
the development and standardization of 3GPP LTE and 5G. His
research areas of interest include multiple antenna technology,
heterogeneous wireless networks, and NOMA.
Qi Xiong (q1005.xiong@samsung.com) received his Ph.D. in
electrical and electronic engineering from Nanyang Techno-
logical University, Singapore. He joined the Communication
IEEE Communications Magazine • March 2018
Research Lab at the Beijing Samsung Telecommunication R&D
Center as a 5G research engineer in 2015. His research interests
include physical layer security, non-orthogonal multiple access,
5G communication PHY/MAC design, and more. Currently, he
is involved in standardization for 5G in 3GPP.
C hen Q ian (chen.qian@samsung.com) received his Ph.D. in
electrical engineering from Tsinghua University, China. He
joined the Communication Research Lab at the Beijing Samsung
Telecommunication R&D Center as a 5G research engineer in
2015. His research interests include MIMO systems, waveform
design, non-orthogonal multiple access, 5G communication
PHY/MAC design, and more. Currently, he is involved in stan-
dardization for 5G in 3GPP.
Bin Yu (bin82.yu@samsung.com) received his M.S. in electrical
engineering from the University of Southampton, United King-
dom. He joined the Communication Research Lab at the Beijing
Samsung Telecommunication R&D Center as a 5G research lab
leader in 2013. His research interests include MIMO systems,
waveform design, non-orthogonal multiple access, 5G communi-
cation PHY/MAC design, and more. Currently, he is involved in
standardization for 5G in 3GPP.
Z higuo D ing (z.ding@lancaster.ac.uk) received his Ph.D.
degree from Imperial College London in 2005, and is currently
a Chair Professor at Lancaster University, United Kingdom. His
research interests include 5G communications, MIMO and
relaying networks, and energy harvesting. He has served as
an Editor for several journals including IEEE Transactions on
Communications, IEEE Communications Letters, IEEE Wireless
Communications Letters, and Wireless Communications and
Mobile Computing.
Sen Wang (wangsenyjy@chinamobile.com) received his Ph.D.
degree in information and communication engineering from
Beijing University of Posts and Telecommunications, China, in
2013. After graduation, he joined the Green Communication
Research Center (GCRC), China Mobile Research Institute, as a
project manager. His research interests include 5G air interface
technologies, especially MIMO, multiple access, radio resource
allocation, and performance evaluation for future cellular net-
works.
Shuangfeng Han (hanshuangfeng@chinamobile.com) graduat-
ed from Tsinghua University in 2006 and is now a senior project
IEEE Communications Magazine • March 2018
manager in the Green Communication Research Center of the
China Mobile Research Institute, leading 5G R&D. He is also
vice chair of the wireless technology work group of China’s IMT-
2020 (5G) promotion group. His research interests are mainly
focused on 5G wireless communication systems, including mas-
sive MIMO, flexible duplex, NOMA, high-speed train communi-
cation, and wireless big data with AI.
Xiaolin Hou (hou@docomolabs-beijing.com.cn) received his
Ph.D. in communication and information systems from Beijing
University of Posts and Telecommunications. He joined DOCO-
MO Beijing Laboratories in 2005 and is now the deputy director
of the wireless technology department. He has been actively
contributing to 4G and 5G research, standardization and trials.
His current research interests include massive MIMO, mmWave,
flexible duplex, NOMA, URLLC, and cellular V2X.
H ao L in (hao.lin@orange.com) received his Ph.D. degree in
communication and electronics from the Ecole National
Supérieure des Télécommunications (ENST), Paris, France, in
2009. In 2010, he joined Orange Labs (Rennes) as a research
engineer. His research interests include multi-carrier modulation
and signal processing for communications. He has led several
European research projects, including FP7 and 5GPPP. He is
now involved in standardization for 5G representing Orange as
a 3GPP RAN1 delegate.
Raphael Visoz (raphael.visoz@orange.com) received his Ph.D.
degree in digital communications from ENST in 2002. Since
November 1997, he has been working for Orange in the field
of 3/4/5G mobile radio systems. His research interests include
network information theory, PHY/MAC cross-layer optimiza-
tion mechanisms, multi-antenna technology (MIMO systems),
and iterative decoding on graphs. He is now involved in stan-
dardization for 5G representing Orange as a 3GPP RAN1
delegate.
Razieh Razavi (razieh.razavi@vodafone.com) received her Ph.D.
degree in mobile communications from the University of Surrey
in 2012. She continued her research as a research fellow with
the Institute for Communication Systems (ICS), Home of the 5G
Innovation Centre, University of Surrey. In November 2015, she
joined Vodafone Group’s R&D team, focusing on 4G and 5G
technologies. Her research interests include 5G wireless com-
munications systems, non-orthogonal multiple access, advanced
multi-user detection, and decoding techniques.
27
COMUNICACIONES MÓVILES 3G
Agenda

1 Introducción

2 Fundamentos de Red 3G

3 Arquitectura general de red 3G

1. Introducción
Introducción
Evolucion de Red
Diversos factores definen la ruta de
tecnología a seguir
• La evolución tecnológica como ruta es compleja de predecir con
exactitud.
• Y esto se debe a diversos factores que lo condicionan como:
› Comportamiento del consumo del usuario final,
› Necesidad de generar más ingresos en el operador, etc.
Diversos factores definen la ruta de
tecnología a seguir
Existen diversos tipos de Operadores (o Carriers) sin embargo podemos catalogar 2 grandes grupos y son
los Operadores que brindan servicios:
Móviles (redes celulares o móviles con servicio de voz y/o datos)
Fijos (redes de telefonía fija, pública, servicios de banda ancha fijos, etc.)
También los hay híbridos, los cuales brindan ambos servicios.
Pronóstico de implementación

EuropaOcc. EuropaOr.
2010/2011 ~2014
Japan y Asia Pacífico
2010/2011

Norte America
2010/2011 China
2011/2012

América Central y Sur

~2014 Africa Asia Sur 2014
~2018

La introducción de los servicios LTE será de manera progresiva y dependerá de la realidad del país (demanda,
frecuencia, etc.)

⚫ Primero en Europa, Japón y US para el 2010/2011

⚫ El mercado masivo de LTE se espera para el 2014
3GPP Releases
GPRS HSUPA
171.2Kbit/s 5.76 Mbit/s
UMTS LTE
Phase 2 Release 97 2 Mbit/s 100 Mbit/s
Release 6
Release 99 Release 8

LTE Advanced
1Gbit/s

Release 99 Release 7/8 Release 9/10

Phase 1
EDGE Release 5
HSDPA+
GSM 473.6 Kbit/s HSDPA 28.8 Mbit/s
9.6Kbit/s
14.4 Mbit/s 42Mbit/s
 UMTS Protocol Version Evolution
⚫ Include all the services and functions of R99 ⚫ Include all the services and functions of R4

CS domain change: control is separated from ⚫ IMS domain is adopted

⚫ Include all the services and functions of ⚫
2G ( GSM and GPRS ) bearer, the function of MSC can be fulfilled by ⚫ Enhanced IP QoS ability , supporting end to
MSC SERVER and MGW. end IP multimedia service
⚫ CN is composed of CS domain and PS
domain ⚫ Packet voice supported by CS domain,
supporting ATM, IP, TDM
⚫ Adopt WCDMA UTRAN
⚫ Iu interface between RAN and CN is
based on ATM
R5
R4

R99

functionally frozen time

2000 2001 2002
Page 10
UMTS R99 Network Architecture

Other PLMN
MSC/VLR GMSC PSTN,ISDN
GSM /GPRS BSS

BSC
BTS HLR/AUC

PCU SCE
SS7
RNC
SMS
NodeB SCP
GPRS
Internet,
backbone
SGSN Intranet
UMTS
GGSN
UTRAN

CG BG

Other PLMN’s
GPRS network

Page 11
R99 Feature(1)

• Core Network is split into CS domain and PS domain.

› CS domain is in charge of call control and mobility managementof circuit
service.
» Call control: ISUP/TUP
» Mobility management: enhanced MAP
» Physical node:MSC,GMSC,VLR
› PS domain is in charge of session management and mobilitymanagement
of Packet service.
» There are some change from GPRS: interfaces, flows, some functions
» Physical node: SGSN,GGSN,CG

Page 12
R99 Feature(2)

• Transcoders is placed in CN side

• TFO: Tandem Free Operation

• Supporting inter-system handover (UMTS/GSM)

• Enhanced security and charging

Page 13
UMTS R4 Network Architecture

IP/ATM Backbone
Other PLMN
MGW MGW
PSTN,ISDN
GSM /GPRS BSS
VMSC Server GMSC Server
BSC
BTS HLR/AUC

PCU SCE
SS7
RNC
SMS
NodeB SCP
GPRS
Internet,
backbone
SGSN Intranet
UMTS
GGSN
UTRAN

CG BG

Other PLMN’s
GPRS network

Page 14
 Difference between R99 and R4
CS domain evolution

SCP HLR SCP HLR

CAP Over TDM MAP Over TDM CAP Over TDM/IP MAP Over TDM/IP

TUP/ISUP
MSC TDM MSC MSC Server TUP/ISUP/BICC
MSC Server
H.248 H.248
CS-MGW TDM/ATM/IP
CS-MGW

RAN RAN RAN RAN RAN RAN

R99 R4
Notes: PS domain structure remain unchanged

Page 15
R4 CN Feature(1)

• CS domain
› Control is separated from bearer,MSC is split into
server and MGW MSC
› Traffic bearer can be IP , ATM or
TDM
› Signaling bearer can be IP or TDM
› TrFO: Transcoder Free Operation

Page 16
R5 Network Architecture
CS domain IP/ATM Backbone
Other PLMN
MGW MGW
GSM /GPRS BSS PSTN,ISDN

VMSC Server GMSC Server

BSC
BTS HLR/AUC/HSS
Iu-CS
SCE
PCU
SS7
RNC SMS
SCP
NodeB Iu-PS Internet,
GPRS Intranet
backbone
UTRAN SGSN
GGSN
MGW
PS domain MGCF
CG BG
IP backbone
P-CSCF S-CSCF
MRFC
MRFP

IMS domain

Page 17
R5 CN Feature

• Multimedia service based on IP

›IP multimedia subsystem
›SIP call control protocol
›Interworking with other domain
» Interworking with CSdomain
» Interworking with IPdomain
• CAMEL4
• IPV6

Page 18
 The Trend of Network: Network Layer Structure

Service Policy App Server IN

MRS
iOSS
Server

Control
SoftSwitch SoftSwitch

IP core network
Switch
S R
R

IAD UMG
AMG
Broadband Access SG 3G Access
Access TMG
UMG
PSTN
PLMN

Page 19
UMTS Architecture

Home
N e tw o r k
Domain

[Z u]

Cu Uu Iu [Y u]

Serving Transit
Netw ork N e tw o r k
Domain Domain

USIM Mobile Access Core

D o m a in E q u ip m e n t N e tw o r k N e tw o r k
Domain Domain Domain

User Equipment Infra s tr uc ture

Domain Domain

The core network domain may result from evolutions of existing network infrastructure.

Page 20
Interfaces in R99 network

PSTN
MSC/VLR GMSC ISDN
GSM /GPRS BSS
A
BSC
BTS HLR/AUC
C/D/Gs
Iu-CS
PCU SCE
SS7
Gb
RNC
Gr/Gs/Gd/Ge Gc SMS
NodeB Iu-PS
SCP
GPRS
Internet,
backbone
SGSN Gi Intranet
UMTS
GGSN
UTRAN Ga

CG BG
Gp Other PLMN

Page 21
Iu-CS Interface Protocol Stack

RNC MSC/VLR GMSC

Iub Iu-CS
PSTN
Node B
HLR/AuC

SS7 SCP
Control Plane User Plane
RANAP IuUP Iu-PS
SGSN GGSN
SCCP
GPRS
MTP3B backbone

SSCF-NNI
SSCOP CGF BG
AAL5 AAL2 Inter-PLMN
ATM

L1（PHY）

Page 22
SS7 Interface Protocol Stack

RNC MSC/VLR GMSC

Iub
PSTN
Node B
HLR/AuC
SS7
SCP
B
M C S SGSN GGSN
A A S I
P P T GPRS
A S
P+ U U backbone
TCAP P P

SCCP CGF BG
MTP3 Inter-PLMN

MTP2

MTP1

Page 23
PS Domain Interface Protocol Stack

RNC MSC/VLR GMSC

Iub
PSTN
Node B
Iu-PS HLR/AuC
SS7
Control Plane User Plane SCP
RANAP GTP-U
SGSN GGSN
SCCP
GPRS
MTP3B backbone

SSCF-NNI UDP Gn/Gp/Ga

SSCOP IP CGF BG
AAL5 AAL5 Inter-PLMN
G T P (G T P ' )
ATM
UDP
L1（PHY） IP
L 2 (M A C )
L1(PHY)

Page 24
New Interfaces in R4

IP/ATM Backbone PSTN

MGW Nb MGW ISDN
GSM /GPRS BSS Mc
VMSC Server GMSC Server
BSC
BTS Nc HLR/AUC

PCU SCE
SS7
RNC
SMS
NodeB SCP
GPRS Internet,
backbone Intranet
UMTS SGSN
GGSN
UTRAN

CG BG

Other PLMN

Page 25
Interfaces in R4 CS Domain
BICC/ISUP/TUP
MTP3 MTP3B M3UA
MTP2 SSCF/SSCOP SCTP
MTP1 AAL5/ATM IP

MSC GMSC
Server Nc Server
H.248
Mc Mc SCTP UDP MTP3B
IP SSCF/SSCOP/AAL5
Nb
MGW MGW

RTP AAL2 Voice

UDP/IP ATM PCM

Page 26
R5 network interface

IP Multimedia Networks Legacy mobile

PSTN signalling Net wor ks

Mb Mb PSTN
BGCF CSCF
PSTN Mm
Mk Mk

Mw
C, D,
Mj BGCF Gc, Gr
Mi
Cx
IMS- MGCF HSS
MGW Mg C SCF
Mn

Mr Mw Dx SLF
Mb

P -C S C F
M RFP M RFC PDF UE
Mp Gm
M Subsystem
Mb Mb Mb Go

Page 27
Interfaces List
Type Name Bearer Loation Function

CN-R Iu-CS AT M / MSC-RNC WCDMA user signaling access and voice bearer
AN （RANAP） IP(R5) assignment
Iu-PS AT M / SGSN-RNC WCDMA user signaling access and data bearer
（RANAP） IP(R5) assignment
A ( BSS AP ) TDM MSC- BSC G S M u s e r signaling a c c e s s a n d vo ic e b e a r e r a s s ign me n t
Gs TDM MSC-SGSN Inter-wor kin g b e t we e n P S d o ma in a n d C S domain,
( BSSAP +) e.g. c o m b i n e d location u p d a t e , c o m b i n e d pagin g.
MAP B Internal MSC-VLR Inner interface, usedfor user information query, for
interface example, mobility management, LAU, supplemental
s e r vic e s activate a n d s o o n .
C TDM/ MSC-HLR G e t M S R N , g e t u s e r ’s in t e llige n t s e r v i c e s t a t u s ,
IP Get user’s location(29.002, 23.078)
D VLR- H LR G e t M S R N , g e t u s e r ’s in t e llige n t s e r v i c e s t a t u s ,
Get user’s location(29.002, 23.078)
E MSC-MSC H a n d o ve r b e t we e n different M S C . An d t he S M S t ransfer
between S M C and MSC.(29. 00 2)
F MSC-EIR Check UE IMEI status
G VLR- V LR E x c h a n ge user’s informat io n(IM SI, authentication data)
b e t we e n different V L R ( 2 9 . 0 0 2 )
Gr SGSN-HLR P S user subscribe informat ion, U E location informat ion
Gc GGSN-HLR S u p p o r t P U S H s e r v i c e ( n e t w o r k in it ia t e P D P c o n t e x t
activation )
Page 28
Interfaces List
Type Name Bearer Location Function

CAP CAP TDM/ MSC(SSP)- W i r e l e s s intelligent n e t w o r k i n t e r f a c e , u s e d for

IP SCP inte lligent s e r vi c e l o gi c a l c o n t r o l
Media M c ( H.248 ) IP/ M S C Server – Inter-working b e t w e e n control plane a n d bearer
Control ATM MGW plane
Inter- Nc( ISUP / TDM/ M S C Se r ve r --- C o n t r o l plane negotiate b e t w e e n M S C Servers
face BICC) ATM/ G M S C Server
IP
Nb TDM/ MGW—MGW U s e r plane negotiate b e t w e e n M G W s
(NbUP/IuUP) ATM/
IP
MTUP TDM GMSC—PSTN C o m m u n i c a t e with outside n e t w o r k, e.g. P S T N ,
/MISUP /TMSC ISDN
PS CN Gn/Gp IP SGSN-GGSN S M management
interface Ga GSN-CG Charging
Gr TDM/ SGSN-HLR Location manage men t, subscriber information
IP management
Gc GGSN-HLR O p t i o n a l interface a n d support P S M T service:
PUSH
Gi IP GGSN-PDN C o m m u n i c a t i o n w i t h t h e o u t s ide d a t a n e t w o r k
RAN Uu Radio UE—NodeB Air interfac e
interface Iub ATM/ NodeB—RNC Radio resource management
IP(R5)
Iur ATM/ RNC-RNC Soft h a n d o ve r
IP(R5)

Page 29
COMUNICACIONES MÓVILES 3G

2da parte
Contents
GPRS Overview

GPRS Related Procedure

Typical Solution

Page 2
GPRS: General Packet Radio Services
IMS
Full Circuit Switch
UMTS PS
2.5G GPRS
Full Packet Switch

GSM Expanding phase of

Packet Switch

Initial phase of
Packet Switch

GSM: All network is used for circuited Mobile services

2.5G GPRS: Packet switch is appended to GSM network providing low speed
packet services.
UMTS PS: With higher radio access speed, high speed packet services
become popular.
IMS: All services including telephone services are based on packet switch.

To full packet switching is the direction of network evolution.

Page 3
 What can GPRS do?
 G P R S : Low speed and
gusty low traffic services
➢ MMS
Bandwidth High Quality
➢ WAP information
Mobile
Experience ➢ Internet Browsing
➢ Low speed VPN
Multimedia and B3G
Mobile
broadband  E D G E : Medium speed
Internet
Mobile services
Narrow 3G
band ➢ Mobile TV
Mobile Internet ➢ Streaming
Voice/SMS
2.5G ➢ Medium VPN (Mobile Office)
➢ Online Game
2G  U M T S : High speed
Mobile Service
services
➢ VOD
➢ Streaming
➢ POC

➢ City Navigation

Page 4
PS Can Provide Multiple Data Services
MMS
Browse PoC

Multiple
Data
Services
VP
Streaming

Game

So Many Attractive Services

Page 5
 GPRS Architecture
EIR SMSC SCP MSC/VLR HLR GMLC

BG
Gf Gd Ge Gs Gr Lg Other PLMN
Gc
GSM/GPRS
WAP Gateway
SGSN Gp GGSN
BSC/PCU
BSS
Gn Gi Firewall
Abis Gb Intranet/Internet
CG
BTS
Ga
Iu-ps
RADIUS MMSC
RNC DNS/DHCP server
UTRAN
SNMP Gom X-1/2/3
Iub
Node B

UMTS

NMS M2000 LIG

Page 6
Important Entity Function

•Saving and updating • Session management

GPRS subscriber HLR • Routing and transfer
subscription data
• Charging
• User authentication
• Dynamic IP allocation
•Providing location/routing
information • Service management
Gr
SGSN GGSN

Gn/Gp
Ga Ga

•Real-time collection of GPRS

• Mobility management CDRs
• Session management •Temporary storage and
• Routing and transfer buffering of GPRS CDRs
CG •Pre-processing of GPRS
• Charging
CDRs
• Lawful Interception
•Sending GPRS CDRs to the
• NTP billing center

Page 7
Important Entity Function-PCU
PCU (Packet Control Unit):
 Radio Resource Management
 Packet Routing and Transferring

PCU

BSC BTS
Abis Gb

BTS
BSC Gb GPRS
Backbone Gb
PCU
PCU SGSN SGSN

BTS Abis
BSC
BSC BTS

Page 8
Important Entity Function- RNC
UE UTRAN CN
Uu Iu
Iu-CS
RNC
Iub
CS
NodeB
Iu-PS

Iu-BC Iur
NodeB SGSN
Iu-BC

Iub

NodeB RNC
CBC

RNC (Radio Network Controller) :

• Provides the system information broadcast and system access control
functions
•Provides such mobility management functions as handover and RNC
transition
•Provides radio resource management and control functions such as macro
diversity combination, power control and radio bearer allocation

Page 9
 Important Entity Function: DNS

SGSN GGSN(A)

ISP A
GPRS backbone
ISP B

BSS

DNS Internet/
GGSN(B) Intranet

MS Resolve the APN to a GGSN IP in the PDP active procedure

Resolve the RAI to a SGSN IP in the inter-SGSN RAU procedure
Resolve the RNCID to a SGSN IP in the relocation procedure (UMTS)

Page 10
Gb interface- SGSN & PCU
A p p lication
IP IP
R ela y
SNDCP SNDC P G TP -U GTP-U

LLC LLC
R ela y UDP UDP
R LC R LC BSSGP BSSGP
IP IP
MAC MAC N etw ork N etw ork L2 L2
Service Service
GSM RF GSM RF L1bis L1bis L1 L1
Um Gb Gn Gi
MS BSS SGSN GGSN

User Plane for A/Gb mode

GMM/SM GMM/SM
LLC LLC
Relay
RLC RLC BSSGP BSSGP

MAC MAC Network Network Control Plane MS - SGSN in A/Gb mode

Service Service
GSM RF GSM RF L1bis L1bis
Um Gb
MS BSS SGSN

Page 11
Iu-PS interface
Control Plane User Plane
Application

E.g., IP, E.g., IP,

PPP PPP

Relay Relay

PDCP PDCP GTP-U GTP-U GTP-U GTP-U

RLC RLC UDP/IP UDP/IP UDP/IP UDP/IP

MAC MAC L2 L2 L2 L2
L1 L1 L1 L1 L1 L1
Uu Iu-PS Gn Gi
MS UTRAN 3G-SGSN 3G-GGSN

ATM
Physical Bearer
UDP/IP
RNC SGSN

Page 12
SS7 interface

TCAP TCAP
SCCP SCCP

Signaling Signaling
Bearer Bearer

Ge
SGSN SCP

Page 13
GnGp interface

GPRS
Gn Backbone
GGSN
SGSN
Gp
BG

GPRS
Gn Backbone
GGSN
SGSN

Page 14
 Gi interface
AAA Portal Server DHCP Server
HLR

IP IP over GTP AAA

Internet LNS
SGSN GGSN

Private network SSM

Gi interface:

• Original user IP packet

AAA
• IP address allocation LNS

• Access to services network Private network

SSM
• Security

Page 15
Contents
GPRS Overview

GPRS Related Procedure

Typical Solution

Page 16
GPRS Related Procedure

Mobility Management

Radio Resource Management

Session Management

Page 17
GPRS Related Procedure- Mobility Management

Basic concepts

Attach and Detach

Security Function

Loaction Management

Service Request (UMTS only)

Page 18
MM (Mobility Management)

Main procedures
•Attach
keep track of the •RAU and periodic RAU
•Detach
current location
GMM •Service request (PMM)
of an MS
PMM •SRNS relocation(PMM)
Subscription
MS states
data other procedures
management
management
• P-TMSI reallocation
MM • Authentication
• Identification
• Subscriber management
NOTE: MM stores in MS and SGSN.

Page 19
 GMM States

Timer Function
IDLE IDLE
READY Timer Function (GSM )

•The READY timer controls the time an MS

GPRS Attach GPRS Detach GPRS Attach
GPRS Detach
or
remains in READY state in the MS and the
Cancel Location SGSN. When the READY timer expires,
the MS and SGSN MM contexts shall
return to STANDBY state.

RE ADY Implicit Detach

or
RE ADY Periodic RA Update Timer Function
Cancel Location
•Upon expiry of the periodic RAupdate
RE AD Y timer expiry timer, the MS shall start a periodic
R E A D Y timer expiry
or PD U transmission
or
PD U reception routeing area update procedure.
Force to ST AN D BY
Force to ST AN D BY or
Abnormal RLC condition
Mobile Reachable Timer Function
• If the mobile reachable timer expires,
STANDB Y ST AN DBY
the SGSN shall clear PPF.
•After expiry of the mobile reachable
timer the SGSN may perform an
implicit detach.
M M State Model of M S M M State Model of S GS N

Page 20
PMM States

PM M- PMM-
DETACHED DETACHED

Detach, D etach,
PS Detach PS Attach R eject, PS Detach PS Attach Reject
PS Attach RAU Rej ect PS Attach RAU R eject

PS Signalling PS Signalling
Connection Releas e PMM- Connection Releas e PM M-
PMM- IDLE CONNE CTE D PMM-IDLE CONNE CTE D
SM-ACTIVE or SM-ACTIVE or SM-ACTIVE or SM-ACTIVE or
INA CTIVE P S S ig nalling INACTIV E INA CTIVE PS Signalling INAC TIVE
Connection Establish Connection Establish

Serving RNC
reloc ation

MS MM States 3G-SGSN MM States

Page 21
MS/UE Operation Modes

Class-A mode of operation

•The MS is attached to both GPRS and other GSM services, and the MS
supports simultaneous operation of GPRS and other GSM services.
Class-B mode of operation
GSM •The MS is attached to both GPRS and other GSM services, but the MS
can only operate one set of services at a time.
Class-C mode of operation
• The MS is exclusively attached to GPRS services.

PS/CS mode of operation

•The MS is attached to both the PS domain and CS domain, and
the MS is capable of simultaneously operating PS services and
CS services.
PS mode of operation
•The MS is attached to the PS domain only and may only operate
UMTS services of the PS domain. However, this does not prevent CS-
like services to be offered over the PS domain (e.g. VoIP).
CS mode of operation
•The MS is attached to the CS domain only and may only operate
services of the CS domain. However, this does not prevent PS-
like service to be offered over the CS domain.

Page 22
Network Operation Modes
Mode Circuit Paging GPRS Paging Channel Paging
Channel co-
ordination
Packet Paging Packet Paging Channel
Channel
CCCH Paging CCCH Paging Channel
I Channel Yes
GSM Packet Data Not Applicable
Channel
CCCH Paging CCCH Paging Channel
II No
Channel
CCCH Paging Packet Paging Channel
Channel
III No
CCCH Paging CCCH Paging Channel
Channel

Mode Network configuration Combined procedure by MT

I Gs interface is present Yes

UMTS
II Gs interface is not present No

Page 23
GPRS Related Procedure- Mobility Management

Basic concepts

Attach and Detach

Security Function

Loaction Management

Service Request (UMTS only)

Page 24
 Attach Procedure

Period RAU

Inter-RAU SGSN

After attach, MM context will occupy SGSN memory, and period RAU, Inter-SGSN
RAU will occupy SGSN CPU.

Additional less PDP contexts are activated in GPRS initional.

High attach required high capacity of SGSN, but the high attachment don’t bring
any profit.

Page 25
 Attach Procedure

FUNCTION
•An MS/UE shall perform a GPRS Attach to
the SGSN in order to obtain access to the
GPRS services.
•If the MS/UE is connected via a GSM radio,
(IMSI or (PTMSI) it shall perform a GSM GPRS Attach
PTMSI+RAI) procedure.
(IMSI)
•If the MS/UE is connected via a UMTS radio
(Identity Type =
access network, it shall perform a UMTS
IMSI(IM)SI) GPRS Attach procedure.

RESULT
• SGSN get subscriber data from HLR
•HLR recorded the MS’s serving SGSN
number
• SGSN and MS create MM context for the
MS
•MS/UE become the ready or PMM-
CONNECTED state
.MS can request Session Management
services

Note: Only MS/UE can initiate the attach procedure.

Page 26
Reject Caused by GPRS Core Network
Cause in attach reject
Illegal MS
Illegal ME
GPRS services not allowed
GPRS services not allowed in this
PLMN
PLMN not allowed
Location area not allowed
Roaming not allowed in this location
area
No Suitable Cells In Location Area
Actions in PS domain
The MS shall set the GPRS update status to
GU3 ROAMING NOT ALLOWED The
SIM/USIM shall be considered as invalid for
GPRS services until switching off or the
SIM/USIM is removed
The MS shall set the GPRS update status to
GU3 ROAMING NOT ALLOWED; The
SIM/USIM shall be considered as invalid for
GPRS services until switching off or the
SIM/USIM is removed.
shall set the GPRS update status to GU3
ROAMING NOT ALLOWED
shall set the GPRS update status to GU3
ROAMING NOT ALLOWED), shall reset the
GPRS attach attempt counter and shall
change to state GMM-DEREGISTERED
shall set the GPRS update status to GU3
ROAMING NOT ALLOWED
Actions in CS domain
If the MS is IMSI attached, the MS
shall in addition set the update
status to U3 ROAMING NOT
ALLOWED, shall delete any TMSI,
LAI and ciphering key sequence
number
no effect
The MS shall perform a PLMN
selection
The MS shall search for a suitable
cell in another location area in the
same PLMN
Page 27
 MM Context
Field Description A/Gb Iu mode
mode

IMSI IMSI is the main reference key. X X

MM State Mobility management state, IDLE, STANDBY, READY, PMM-DETACHED, PMM-IDLE, or X X

PMM-CONNECTED.

P-TMSI Packet Temporary Mobile Subscriber Identity. X X

P-TMSI Signature A signature used for identification checkingpurposes. X X

IMEI International Mobile Equipment Identity X X

MSISDN The basic MSISDN of the MS. X X

Routeing Area Current routeing area. X X

Cell Identity Current cell in READY state, last known cell in STANDBY or IDLE state. X

Cell Identity Age Time elapsed since the last LLC PDU was received from the MS at the SGSN. X

Service Area Code Last known SAC when initial UE message was received or Location Reporting procedure was X
executed.

Service Area Code Age Time elapsed since the last SAC was received at the 3G-SGSN. X

VLR Number The VLR number of the MSC/VLR currently serving this MS. X X

New SGSN Address The IP address of the new SGSN where buffered and not sent N-PDUs should be forwarded to. X X

Authentication Vectors Authentication and ciphering parameters (authentication tripletsor quintets). X X

Kc Currently used A/Gb mode ciphering key. X 2)

CKSN Ciphering key sequence number ofKc. X 2)

Ciphering algorithm Selected ciphering algorithm (GEA). X X

CK Currently used Iu mode cipheringkey. 1) X

Page 28
 MM Context
IK Currently used Iu mode integrity key. 1) X

KSI Key Set Identifier. 1) X

MS Radio Access Capability MS radio access capabilities. X

MS Network Capability MS network capabilities. X X

DRX Parameters Discontinuous reception parameters. X X

Radio Priority SMS The RLC/MAC radio priority level for uplink SMS transmission. X

MNRG Indicates whether activity from the MS shall be reported to the HLR. X X

NGAF Indicates whether activity from the MS shall be reported to the MSC/VLR. X X

PPF Indicates whether paging for PS and CS services can be initiated. X X

Subscribed Charging Characteristics The charging characteristics for the MS, e.g. normal, prepaid, flat-rate, and/or hot billing X X
subscription.

SMS Parameters SMS-related parameters, e.g. operator-determined barring. X X

Recovery Indicates if HLR or VLR is performing database recovery. X X

GPRS-CSI Optional GPRS CAMEL subscription information, see 3GPP TS 23.016 X X

ODB for PS parameters Indicates that the status of the operator determined barring for packet oriented services. X X

⚫ The information marked with a "1)" may be maintained if authentication is performed by the UMTS
authentication procedure.
⚫ The information marked with a "2)" may be maintained if authentication is performed by theGSM
authentication procedure.

Page 29
Detach Type
Type of detach (octet 1)
8 7 6 5 4 3 2 1
Detach type Power Type of detach
In the MS to network direction:
IEI off
Bits
Detach Type IE 3 2 1

0 0 1 GPRS detach

The different types of detach 0 1 0 IMSI detach

• IMSI detach; 0 1 1 Combined GPRS/IMSI detach
• GPRS detach;
•Combined GPRS / IMSI detach All other values are interpreted as Combined
GPRS/IMSI detach by this version of the
(MS-initiated only).
protocol.

In the network to MS direction:

Bits
The following three entity can
3 2 1
initiate the detach procedure
•MS 0 0 1 re-attach required
• SGSN 0 1 0 re-attach not required
Network side
• HLR
0 1 1 IMSI detach (after VLR failure)

All other values are interpreted as re-attach not

required by this version of the protocol.

Page 30
 Detach Procedure (MS Initiated)
Function
•Allow an MS to inform the network
that it does not want to access the
MS BSS/UTRAN SGSN GGSN MSC/VLR SGSN-based services any longer

1. DetachRequest
2. Delete PDP Context Request
2. Delete PDP Context Response
C1
3. IMSI Detach Indication
4. GPRS Detach Indication
C2
5. DetachAccept
6. PS Signalling Connection Release
Results
•The SGSN shall not service the detached
MS, unless reattach
•The MS is in idle or PMM-DETACHED state
Two types of the MS IMSI detach
•A GPRS-attached MS sends a Detach
Request message to the SGSN, indicating
an IMSI detach. This can be made in
combination with GPRS detach.
•An MS that is not GPRS-attached makes
the IMSI detach as already defined in
A/Gb mode or UMTS.

Page 31
Detach Procedure (SGSN & HLR Initiated)
MS BSS/UTRAN SGSN GGSN MSC/VLR Function
•Allow the network to inform an MS
1. Detach Request
2. Delete PDP Context Request that it does not have access to the
SGSN-based services any more
2. Delete PDP Context Response

C1
3. GPRS Detach Indication Results :
4. Detach Accept
•The SGSN shall not service the detached
MS, unless reattach
C2
•The MS is in idle or PMM-DETACHED state
5. PS Signalling Connection Release

The MS is detached either explicitly

MS BSS/UTRAN SGSN GGSN HLR MSC/VLR or implicitly:
•Explicit detach: The network or the
1. Cancel Location
2. Detach Request MS explicitly requests detach
3. Delete PDP Context Request
•Implicit detach: The network
3. Delete PDP Context Response detaches the MS, without notifying
C1 the MS, a configuration-dependent
5. Detach Accept
4. GPRS Detach Indication time after the mobile reachable
C2
timer expired, or after an
6. Cancel Location Ack irrecoverable radio error causes
7. PS Signalling Connection Release disconnection of the logical link.

Page 32
Purge Function

⚫ Function
The Purge function allows an SGSN to
inform the HLR that it has deleted the MM
and PDP contexts of a detached MS

⚫ After the MS detach from the network: SGSN HLR

The SGSN may delete the MM/PDP
1. Purge MS
context immediately
2. Purge MS Ack
the SGSN may keep the MM/PDP context
for some time of the detached MS
⚫ Purge Timer Function
Allows the SGSN to inform the HLR that it
has deleted the MM and PDP contexts of a
detached MS.

The purge timer is set longer than the

mobile reachable timer

Page 33
GPRS Related Procedure- Mobility Management

Basic concepts

Attach and Detach

Security Function

Loaction Management

Service Request (UMTS only)

Page 34
Authentication Function

Function
• Permit the network to check whether the identity provided by the mobile station;
• Provide parameters enabling the mobile station to calculate a new ciphering key ;
（UMTS and GSM）
• Provide parameters enabling the mobile station to calculate a new UMTS integrity key;
（UMTS only）
• Permit the mobile station to authenticate the network. （UMTSonly）

Authentication types
GSM
• Using triplet: RAND, SRES, Kc
•Using GPRS Encryption Algorithm
(GEA)

UMTS
• Using quintet: RAND, XRES, AUTN, CK, IK
• AUTN: for UE authenticate network
• IK: for data integrity function
• Using UMTS Encryption Algorithm

Page 35
Authentication Function(3G)
MS V LR /SG SN HE/HLR

Authentication data request

Generate authentication
Distribution of vectors AV(1..n)
authentication
vectors from HE
to SN Authentication data response
AV(1..n)

Store authentication vectors

Select authentication vector AV(i)

User authentication request

RAND(i) || AUTN(i)

Verify AUTN(i)
Compute RES(i)
Authentication and
key establishment
User authentication response
RES(i)

Compare RES(i) and XRES(i)

Compute CK(i) and IK(i) Select CK(i) and IK(i)

Page 36
 Ciphering & Identity Check
Scope
⚫ A/Gb mode: from the ciphering function in the Identity
SGSN to the ciphering function in the MS.
Check
⚫ Iu mode: from the ciphering function in the UTRAN
to the ciphering function in the MS.
Function
Start
⚫ A/Gb mode: the MS starts ciphering after sending the •Get IMSI from
MS
Authentication and Ciphering Response message.
• Check the IMEI
⚫ Iu mode: the start is controlled by the security mode
procedure after authentication procedure.
MS BSS/UTRAN SGSN EIR

1. Identity Request
MS BSS/UTRAN SGSN
1. Identity Response
Scope of GSM GPRS ciphering 2. Check IMEI

2. Check IMEI Ack

Scope of UMTS ciphering

Ciphering Identity Check

Page 37
P-TMSI Reallocation

⚫ Function
The SGSN may reallocate the P-TMSI at any time
The reallocation procedure can be performed by the
P-TMSI Reallocation procedure

The P-TMSI can be included in the Attach or RouteingArea

Update procedures.

MS BSS/UTRAN SGSN

1. P-TMSI Reallocation Command

2. P-TMSI Reallocation Complete

Page 38
GPRS Related Procedure- Mobility Management

Basic concepts

Attach and Detach

Security Function

Loaction Management

Service Request (UMTS only)

Page 39
 Location Management

Function

• cell and PLMN selection;

• know the Routeing Area;
•identity :know the URA identity or cell
identity;
• indicate to an MS in RRC Connected mode
• know the address of the serving

3G

2G Layered Location
Management Mode

Page 40
Network Architecture

PDN
⚫ Routing area update
procedure
Gi
GGSN
SGSN can manage
the MS location Gn/Gp Gn/Gp
old SGSN new SGSN
information via RAU
Gn
procedure in RAI level
Gr Gr
Iu IU
Iu IU

⚫ Relocation procedure
(UMTS only) Iur RNC1 HLR/AUC
RNC3
RNC2 RNC4
Move the Iu interface
to the other RNC RA4 RA5 RA9 RA10

RA1 RA2 RA3

RA6 RA7 RA9

⚫ Handover procedure

Move the radio link to

the other BTS/NodeB MS

Page 41
Routing Area Update Procedure

In the viewpoint of
SGSN:
intra-SGSN RAU
Inter-SGSN RAU

RAU procedure will happen in the following two case:

• MS entered a new Route Area
• Periodic RAU ( after periodic timer expires)

Page 42
Inter-SGSN RAU Procedure (2G)

Page 43
Inter-SGSN RAU Procedure (2G)

Page 44
Inter-SGSN RAU

new old

RA1 SGSN SGSN GGSN

RA2
Routing_Area_update_req (RA1)
SGSN_context_req (RA1, TLLI, @SGSN2)
SGSN_context_resp (MM_ctxt, PDP_ctxt)
SGSN_context_ack
transfer of stored packets

Update_PDP_context_req (TID, @SGSN2)

Update_PDP _context_resp

Page 45
 Inter-SGSN RAU
new old

RA1 SGSN SGSN HLR

RA2
Update_location (IMSI, @SGSN2)

cancel_location (IMSI)
cancel_location_ack

insert_subscriber_data (+ack)

Update_location_ack
Routing_Area_update_accept (TLLI)
Routing_Area_update_complete

Page 46
Inter-SGSN RAU Procedure (3G)

Page 47
Inter-SGSN RAU Procedure (3G)

Page 48
Serving RNS Relocation Procedure (3G)

HLR/AuC HLR/AuC

GGSN GGSN

old MSC/VLR old SGSN new SGSN new MSC/VLR old MSC/VLR old SGSN new SGSN new MSC/VLR

source SRNC target RNC source RNC target SRNC

LA1, RA1 LA2, RA2 LA1, RA1 LA2, RA2

MS MS

⚫ Before relocation ⚫ After relocation

Page 49
Serving RNS Relocation Procedure (3G)
MS Source Target Old New GGSN
RNC RNC SGSN SGSN

1. Decision to perform
SRNS relocation

2. Relocation Required

3. Forward Relocation Request

4. Relocation Request

Establishment of Radio Access Bearers

4. Relocation Request Acknowledge

5. Forward Relocation Response

C1
6. Relocation Command

7. Forwarding of data

8. Relocation Commit

9. Relocation Detect
10. UTRAN Mobility Information 11. Update PDP Context Request

10. UTRAN Mobility Information Confirm 11. Update PDP Context Response

12. Relocation Complete

12. Forward Relocation Complete

12. Forward Relocation Complete Acknowledge

13. Iu Release Command
13. Iu Release Complete

14. Routing Area Update C2

C3

Page 50
GPRS Related Procedure- Mobility Management

Basic concepts

Attach and Detach

Security Function

Loaction Management

Service Request (UMTS only)

Page 51
Service Request Procedure

Function
⚫ The Service Request procedure is used by a 3G-MS in PMM-IDLE state to request the
establishment of a secure connection to a 3G-SGSN.

1. Send uplink signalling messages (e.g. Activate PDP Context Request), user data,
2. Paging response,
3. Regained radio coverage.
⚫ This procedure is also used by an MS in PMM-CONNECTED state to request resource
reservation for active PDP contexts.

Service Type IE of Service Request Msg.

• MS initiated Network initiated

• Service type= signalling. •Service type= paging
• Service type= data. response

Page 52
Service Request Procedure –MS initiated
MS RNC SGSN HLR GGSN
1. RRC Connection Request

1. RRC Connection Setup

2. Service Request

3. Security Functions

4. Service Accept

4. Radio Access Bearer

Assignment Request
5. Radio Bearer Setup

6. Radio Bearer Setup

Complete
6. Radio Access Bearer
Assignment Response
7. SGSN-Initiated PDP Context Modification

8. Uplink PDU

Page 53
Service Request Procedure－network initiated
MS RNC SGSN HLR GGSN

1. Downlink PDU
2. Paging
1. Paging

2. RRC Connection Request

3. RRC Connection Setup

4. Service Request

5. Security Functions

6. Radio Access Bearer Assignment

6. Radio Bearer Setup Request

6. Radio Bearer Setup

Complete 6. Radio Access Bearer Assignment
Response

7. SGSN-Initiated PDP Context Modification Procedure

8. Downlink PDU

Page 54
Summary

⚫ Attach, location management, security function and detach

procedures are the main procedures in PS core network.

⚫ SRNS relocation procedure and Service request procedure are

newly added in UMTS PS core network.

Page 55
GPRS Related Procedure

Mobility Management

Radio Resource Management

Session Management

Page 56
 Radio Resource Management

Main function
of GPRS RRM

Distribute and Inspect the Cell system

release the GPRS utilization of Congestion control information
physics channel the GPRS channel boardcasting

Successful Paging

3G Identification of MS in Paging message:

PMM-IDLE PMM-
Connected
• P-TMSI is used to identify the MS
2G
•If P-TMSI is invalid or MS not
STANDBY Ready
respond , then use IMSI

Page 57
 Paging for GPRS (2G)
MS BSS SGSN

1. PDP PDU
STANDB 2. Paging Request
Y
3. GPRS Paging Request
(IMSI,
4. Any LLC Frame P-TMSI,
(Receive Ready or
Area,
5. Any LLC Frame
Information frame) Channel
Needed, QoS,
READY
DRX
Parameters)
NOTE:
1. An MS in STANDBY state is paged by the SGSN before a downlink to the MS
2. Paging move the MS state from STANDBY to READY
3. Any uplink data from MS is a valid response to paging

Page 58
Paging Initiated by CN (3G)

Without
RRC
connect
for CS

With RRC
connect
for CS

Page 59
CS Paging
MS BSS SGSN MSC/VLR

1. Page
2. Paging Request
3. Paging Request
GSM
4. SABM (Paging Response)
5. SCCP Connection Request (Paging Response)

MS RNS 3G-SGSN MSC/VLR

1. Page
2. Paging
UMTS 3. Paging Request

4. RRC Initial Dire ct Transfer (Paging Response)

5. RANAP Initial UE (Paging Response)

Page 60
Summary

⚫ In UMTS, Paging type 1 for UE without RRC connection with

RNC, Paging type 2 for UE with RRC connection with RNC.

⚫ CS paging can be executed via PS.

Page 61
GPRS Related Procedure

Mobility Management

Radio Resource Management

Session Management

Page 62
GPRS Related Procedure - Session Management

Basic concepts

PDP Context Activation Procedure

PDP Context Modification Procedure

PDP Context Deactivation Procedure

Preservation Procedure (UMTS only)

Page 63
Session Management

⚫ Function
Establish and monitor a packet tunnel from MS to GGSN, and
allocate system resource for the packet service.
⚫ Important Procedure
PDP Context Activation
PDP Context Modification
PDP Context Deactivation

⚫ PDP Context: Packet Data Protocol context

PDP context contains all the information needed to transfer user
data between MS and GGSN, associating with MM.
The context includes parameters such as Routing, QoS (Quality
of Service), Charging ID etc.
PDP context exists in MS, SGSN, GGSN.

Page 64
 PDP Context
Each MM context contains zero or more of the following PDP contexts:

Field Description A/Gb mode Iu mode

PDP Context Identifier Index of the PDP context. X X

PDP State Packet data protocol state, INACTIVE or ACTIVE. X X

PDP Type PDP type, e.g. PPP or IP. X X

PDP Address PDP address, e.g. an IP address. X X

APN Subscribed The APN received from the HLR. X X

APN in Use The APN currently used. This APN shall be composed of the APNNetwork X X
Identifier and the APN Operator Identifier.

NSAPI Network layer Service Access Point Identifier. X X

TI Transaction Identifier. X X

TEID for Gn/Gp Tunnel Endpoint Identifier for the Gn and Gp interfaces. X X

TEID for Iu Tunnel Endpoint Identifier for the Iu interface. X

GGSN Address in Use The IP address of the GGSN currently used. X X

VPLMN Address Allowed Specifies whether the MS is allowed to use the APN in the domain of the X X
HPLMN only, or additionally the APN in the domain of the VPLMN.

QoS Profile Subscribed The quality of service profile subscribed. X X

Page 65
 PDP Context
QoS Profile Requested The quality of service profile requested. X X

QoS Profile Negotiated The quality of service profile negotiated. X X

Radio Priority The RLC/MAC radio priority level for uplink user data transmission. X

Packet Flow Id Packet flow identifier. X

Aggregate BSS QoS Profile The aggregate BSS quality of service profile negotiated for the packet flow that X
Negotiated this PDP context belongs to.

Send N-PDU Number SNDCP sequence number of the next downlink N-PDU to be sent to the MS. X

Receive N-PDU Number SNDCP sequence number of the next uplink N-PDU expected from the MS. X

GTP-SND GTP-U sequence number of the next downlink N-PDU to be sent to the MS. X X

GTP-SNU GTP-U sequence number of the next uplink N-PDU to be sent to the GGSN. X X

PDCP-SND Sequence number of the next downlink in-sequence PDCP-PDU to be sent to X

the MS.

PDCP-SNU Sequence number of the next uplink in-sequence PDCP-PDU expected from the X
MS.

Charging Id Charging identifier, identifies charging records generated by SGSN and GGSN. X X

PDP Context Charging The charging characteristics of this PDP context, e.g. normal, prepaid, flat-rate, X X
Characteristics and/or hot billing.

RNC Address in Use The IP address of the RNC currently used. X

Page 66
MM Context and PDP Context

HLR

MS BSC SGSN GGSN

Uu Gb/ Iu Gn
or RNC
MM context PDP context #1
MM context

PDP context #1 PDP context #1 .

. . .

. . .

PDP context #n PDP context #n PDP context #n

Page 67
 PDP Parameters
⚫ QoS: quality of service
⚫ PDP state
It is a group of parameters that
Inactive (cannot transmit data) can define the network ability,
such as the bit rate for downlink or
Active Deactive the PDP uplink data transmission and the
PDP Context or MM state to
Context IDLE or PMM-DETACH
reliability class and so on

It is end to end concept

Active (can transimt data)

⚫ PDPAddress
⚫ PDP Type Static IP
IPV4 − Public IP
IPV6 − Allocate by the operator
PPP Dynamic IP
− Private IP
− Allocate by GGSN, DNCP or
Radius

Page 68
 APN Architecture

cmwap. mnc<MNC>.mcc<MCC>.gprs

APN Network APN Operator

Identity Identity

APN: Access Point Name, defines services accessing point and accessing mode.
------The APN Network Identifier; this defines to which external network the GGSN is
connected and optionally a requested service by the MS. This part of the APN is
mandatory. It’s a string defined by operator.
------The APN Operator Identifier; this defines in which PLMN GPRS backbone the
GGSN is located. This part of the APN is optional.

Page 69
 APN in Element
HLR

SGSN GGSN MMSC

BSS/UTRAN
WAP Gateway
Firewall

Intranet/Internet

DNS
RADIUS

MS: User must configure APN NI and its responding URL, user name, password, IP address, PortNo, etc. In the
activation procedure, MS must send APN OI to network in PDP Context Activation procedure.
HLR: Operator configures APN NI in subscription data persubscribers.
SGSN: It gets registered APN NI from HLR, and compares APN in the subscription data and PDP context
activation message. If different, reject activation. If same, construct APN based on APN OI and IMSI, and send
parse request to DNS. If get IP address from DNS, relay PDP context activation message to GGSN.
DNS: Configure the corresponding relationship of APN and IP address
GGSN: Allocate IP address and selection access mode based on APN

Page 70
APN(2)

⚫ Local APN

⚫ General APN

Page 71
DNS Architecture in GPRS network
Top Level DNS
“.gprs”

DNS in GRX
mcc460.gprs mcc450.gprs mcc234.gprs

DNS controlled by
mnc01.mcc460.gprs Operator

Region DNS
cuwap

cuwap.mnc01.mcc460.gprs

Page 72
GRX Architecture
Operator A

GPRS Roaming Network Operator D

Operator B

GRX GRX Operator G

Operator C
DNS DNS DNS

GRX

Operator E Operator F

Page 73
 GGSN Selection
BTS BSC
/NodeB /RNC
ISP A
GGSN (A) ISP B
MS

• APN-NI/
SGSN GGSN (B)
Backbone Corp.
• OrAPN-NI+APN-OI DNS Network
• APN-NI

DNS DNS

• APN-NI+APN-OI ＝
GGSN IP address

Page 74
GPRS Related Procedure - Session Management

Basic concepts

PDP Context Activation Procedure

PDP Context Modification Procedure

PDP Context Deactivation Procedure

Preservation Procedure (UMTS only)

Page 75
Activation Procedure

⚫ PDP context activation procedure

To establish a PDP context between the MS and the SGSN,

the GGSN

⚫ Activation procedure types:

PDP context activation procedure

Secondary PDP Context Activation Procedure

Network-Requested PDP Context Activation Procedure

Page 76
 PDP Context Activation Procedure (3G)

MS UTRAN 3G-SGSN 3G-GGSN • Check the APN providedby

SGSN
1. Activate PDP Context Request • QoS negotiation
(PDP Type, PDPAddress, Access Point Name, •Allocate a dynamic IP to the
QoS Requested) C1 MS
• Allocate a charging ID for
2. Create PDP Context Requestthe PDPcontext
• Return message to SGSN
• Update PDP context
If the QoS not 3. Create PDP Context Response
accept by MS, then
starts delete PDP 4. Radio Access Bearer Setup （Qos） Charging ID allocation
context procedure
IP address

5. Update PDP Context Request

6. Update PDP Context Response

RAB assignment :
Allocate radio • Check subscriber data
resource and Iu C2 • APN selection
interface resource 7. Activate PDP Context Accept • Interrogate DNS
• QoS negotiation
• Send message GGSN
• RAB assignment
• Send message MS
Page 77
PDP Context Activation Procedure (2G)

MS BSS 2G-SGSN 2G-GGSN

1. Activate PDP ContextRequest

C1
2. Security Functions

3. Create PDP Context Request

3. Create PDP Context Response

4. BSS Packet Flow Context Procedures

C2
5.Activate PDP ContextAccept

Page 78
PDP Context Activation Procedure-Detail

SGSN DNS GGSN

Activate_PDP_context_req
TLLI (NSAPI ,type [+ @ of PDP] , APN, QoS)
1

DNS_query (APN)

DNS_response (@ IP of GGSN1)

Create_PDP_context_req
@ GGSN1 TID1 (type [+ @ of PDP] , APN, QoS)

TID1  IP @  current SGSN

Create_PDP_context response (IP @)

Activate_PDP_context_accept (IP @)
Page 79
 Data Transmission in 2.5G

SGSN GGSN

NSAPI1 → TLLI PDP network

TLLI  IMSI 
NSAPI1 → TID1 + @ GGSN1

TLLI NSAPI1 User packet

@ TID User packet
GGSN1 1

User packet

Page 80
 Secondary PDP Context Activation Procedure
MS BSS 2G-SGSN 2G-GGSN

1. Activate Secondar y PDP Context Request

⚫ For GPRS
C1
2. Security Functions
3. Create PDP Context Request

3. Create PDP Context Response

⚫ For UMTS
5. BSS Packet Flow Context Procedures

C2
MS UTRAN 3G-SGSN 3G-GGSN
7. Activate Secondary PDP Context Accept
1. Activate Secondary PDP Context Request

C1
• Reusing the PDP address and other PDP
3. Create PDP Context Request
context information from an already active PDP
context, but with a different QoS profile 3. Create PDP Context Response
4. Radio Access Bearer Setup
•Procedures for APN selection and PDP
6. Update PDP Context Request
address negotiation are not executed.
6. Update PDP Context Response
• A unique TI and a unique NSAPI shall identify
each PDP context sharing the same PDP C2
address and APN. 7. Activate PDP Context Accept

Page 81
Network-Requested PDP Context Activation Procedure

MS SG SN H LR G G SN

1. PD P PD U

2. Send Routeing Info for GPRS

2. Send Routeing Info for GPRS Ack

3. PD U Notification Request

3. PD U Notification Response

4. Request PD P Con text Activation

5. PD P Context Activation pr ocedure

•When receiving a PDP PDU the GGSN checks if a PDP context is established for that
PDP address. If no PDP context has been previously established, the GGSN may try to
deliver the PDP PDU by initiating the Network-Requested PDP Context Activation
procedure.

Page 82
GPRS Related Procedure - Session Management

Basic concepts

PDP Context Activation Procedure

PDP Context Modification Procedure

PDP Context Deactivation Procedure

Preservation Procedure (UMTS only)

Page 83
Modification Procedures

⚫ Modification procedures modify parameters that were negotiated

during an activation procedure for one or several PDP contexts.
⚫ An MS, a GGSN, an SGSN, or an RNC can request a modification
procedure.

⚫ The following parameters can be modified:

QoS Negotiated;
Radio Priority;
Packet Flow Id;
PDP Address (in case of the GGSN-initiated modification
procedure);
TFT (in case of MS-initiated modification procedure).

Page 84
SGSN-Initiated Modification Procedure

MS UTRAN SGSN GGSN

1. Update PDP Context Request

2. Update PDP Context Response

3. Modify PDP C ontext Request

4. Modify PDP Context Accept

TEID, NSAPI,
C1 QoS Negotiated,
5. Radio Access Bearer Modification Trace Reference,
Trace Type,
Trigger Id,
6. Invoke Trace
OMC Identity

• TEID: Tunnel Identifier

• NSAPI: Network layer Service Access Point Identifier

Page 85
GGSN-Initiated Modification Procedure

MS UTRAN SGSN GGSN

1. Update PDP Context Request
2. Modify PDP Context Request
TEID, NSAPI,
PDP Address,
3. Modify PDP Context Accept
QoS Requested
4. Radio Access Bearer Modification
5. Update PDP Context Response

C1

Page 86
 MS-Initiated Modification Procedure

MS UTRAN SGSN GGSN

1. Modify PDP Context Request

TI, 2. Update PDP Context Request
QoS
Requested, 3. Update PDP Context Response
TFT
4. Radio Access Bearer Modification

5. Modify PDP Context Accept

C1

• TI : Transaction Identifier
• TFT: Traffic Flow Template

Page 87
 RNC-initiated RAB Modification Procedure

⚫ RNC modify RAB may cause SGSN modify PDP context.

MS RNC SGSN GGSN

1. RAB Modify Request

RAB ID,
RAB Parameter Values

2. SGSN initiated PDP Context Modification Procedure

• RAB: Radio Access Bearer

Page 88
GPRS Related Procedure - Session Management

Basic concepts

PDP Context Activation Procedure

PDP Context Modification Procedure

PDP Context Deactivation Procedure

Preservation Procedure (UMTS only)

Page 89
MS Initiated Deactivation Procedure

⚫ For GPRS

MS 2G-SGSN 2G-GGSN

1. Deactivate PDP Context Request

C1
2. Security Functions
3. Delete PDP Context Request

3. Delete PDP Context Response

4. Deactivate PDP Context Accept

Page 90
MS Initiated Deactivation Procedure

⚫ For UMTS

MS UTRAN 3G-SGSN 3G-GGSN

1. Deactivate PDP C ontext Request

C1
3. Delete PDP Context Request

3. Delete PDP Context Response

4. Deactivate PDP Context Accept

5. Radio Access Bearer Release

Page 91
SGSN-initiated Deactivation Procedure

MS UTRAN SGSN GGSN

C1

1. Delete PDP Context Request

1. Delete PDP Context Response

2. Deactivate PDP Context Request

2. Deactivate PDP Context Accept

3. Radio Access Bearer Release

Page 92
GGSN-initiated Deactivation Procedure

MS UTRAN SGSN GGSN

1. Delete PDP Context Request

C1
2. Deactivate PDP Context Request
2. Deactivate PDP Context Accept
3. Delete PDP Context Response
4. Radio Access Bearer Release

Page 93
GPRS Related Procedure - Session Management

Basic concepts

PDP Context Activation Procedure

PDP Context Modification Procedure

PDP Context Deactivation Procedure

Preservation Procedure (UMTS only)

Page 94
RAB Release Procedure

⚫ RAB release procedure to release one or several RABs.

MS UTRAN 3G-SGSN 3G-GGSN FUNCTION

1. RAB ReleaseRequest
2. RABAssignmentRequest
3. Release Radio
Bearer(s)
4. RABAssignment Response
Background or interactive traffic
class PDP context:
Be preserved with no modifications in
UE, SGSN and GGSN.
Streaming or conversational traffic
class PDP context:
Be preserved, but the maximum bit rate
is downgraded to 0 kbit/s (for both uplink
and downlink) in UE, SGSN and GGSN.

•The preservation procedure allows the active PDP contexts associated with the released RABs to
be preserved without modification in the CN, and the RABs can then be re-established at a later
stage (e.g. by service request procedure).

Page 95
Re-establishment of RABs

⚫ In case of uplink data to be transfer for the active PDP context

without RAB:
Background or interactive traffic class PDP context:
− UE initiates the Service Request procedure (Service Type =
Data) to re-establish PDP context.

Streaming or conversational traffic class PDP context:

− UE initiates the PDP context modification procedure to re-
establish PDP context, or deactivation procedure to delete
the PDP context.
⚫ In case of downlink data to be transfer for the active PDP context
without RAB: CN must first page the UE, then re-establish the RAB
by network-initiated service request procedure.

Page 96
 Iu Release Procedure
⚫ UTRAN initiates an Iu release procedure to release all RABs of an
MS and the Iu connection.
MS UTRAN 3G-SGSN
1. Iu Release Request
2. Iu Release Command
3. Release of RRC Connection
4. Iu Release Complete
3G-GGSN
FUNCTION
Background or interactive traffic
class PDP context:
Be preserved with no modifications in
UE, SGSN and GGSN.
Streaming or conversational traffic
class PDP context:
Be preserved, but the maximum bit rate
is downgraded to 0 kbit/s (for both uplink
and downlink) in UE, SGSN and GGSN.
Page 97
Summary

⚫ The session management function includes the flowing functions:

PDP context activation function;
PDP context modification function;
PDP context deactivation function;
PDP context preservation function.

Page 98
Typical Application

⚫ Packet Data Service initiated by MS

1. Establish the wireless connection
2. Execute attach procedure
3. Active the PDP content M BSS SGS HLR GGS PD
S N N N
1
4. Send Packet Data

MM
ready/standby 3

PDP 4
active

Page 99
 Typical Application
⚫ Packet Data Service initiated by Network
1. GGSN receive PDP PDU, and store the PDU
2. GGSN get the MS route information from HLR
3. GGSN inform SGSN
MS BSS SGS HLR GGS PDN
4. Paging the MS in RA, MM shift to ready N N
1

5. SGSN request MS to active PDP context 2

6. MS active PDP context 3

7. Send the Packet Date 4

5
Omit if MM is
ready 6

7
PDP
active

Page 100
GSM vs UMTS Summary

ITEM GSM UMTS

Network background GSM network GPRS network

interface A/Gb Iu-Ps (Separated Bearer and Control )

MM states and procedure GMM PMM(Service request

SRNS relocation)

MS/UE operation modes Class A ,Class B,ClassC PS CS PS/CS

Network Operation Modes Mode I mode2 mode3 Mode1 mode2

Authentication triplet quintet

Ciphering start & scope SGSN-MS UTRAN-UE

LM HLR-SGSN HLR-SGSN-RNC, Service Request

Session Management / Preservation Procedure (UMTS only)

Page 101
Contents
GPRS Overview

GPRS Related Procedure

Typical Solution

Page 102
Networking Solution
Gi Gi Gi
GGSN
GGSN 3G GGSN
Gn Gn
Gn Gn
2G/3G SGSN
2G SGSN 3G SGSN
Gb Iu- Iu-
Gb
PS PS

UTRAN BSS UTRAN

BSS

Unified PS Mode Separated PS Mode

Unified mode－－provide 2G/3G interface and services simultaneously

Separated mode－－2G and 3G interface and service are provide by 2G
equipments and 3G equipments separately

Page 103
Charging Solution

Prepaid based on Prepaid and postpaid

CAMEL 3 based on RADIUS AAA
AAA
SCP

SGSN GGSN

CG Billing system
Postpaid and Hot-billing
Postpaid
Hot-billing
AAA charging
CAMEL based prepaid: SGSN or GGSN CAMEL solution
Time-duration, data flux, content based or QoS based charging
Flat rate

Page 104
 Charging: S-CDR and G-CDR
S-CDR G-CDR
Field Category Description Field Category Description

recordType M GPRS GGSN PDP context record. recordType M GPRS GGSN PDP context record.
networkInitiation C Present if this is a network initiated PDP context. networkInitiation C Present if this is a network initiated PDP context.

servedIMSI M IMSI of the served party (if Anonymous Access Indicator is FALSE servedIMSI M IMSI of the served party (if Anonymous Access Indicator is FALSE
or not supplied).
or not supplied).
ggsnAddress M The IP address of the GGSN used.
ggsnAddress M The IP address of the GGSN used.
M
chargingID PDP context identifier used to identify this PDP context in different
chargingID M PDP context identifier used to identify this PDP context in different
records created by GSNs
records created by GSNs
sgsnAddress M List of SGSN addresses used during this record.
sgsnAddress M List of SGSN addresses used during this record.
accessPointNameNI M The logical name of the connected access point to the external
accessPointNameNI M The logical name of the connected access point to the external
packet data network (network identifier part of APN).
packet data network (network identifier part of APN).
pdpType M PDP type, i.e. IP, PPP, or IHOSS:OSP
pdpType M PDP type, i.e. IP, PPP, or IHOSS:OSP servedPDPAddress M PDP address, i.e. IPv4 or IPv6
servedPDPAddress M PDP address, i.e. IPv4 or IPv6 dynamicAddressFlag C Indicates whether served PDP address is dynamic, which is allocated
dynamicAddressFlag C Indicates whether served PDP address is dynamic, which is allocated during PDP context activation.
during PDP context activation.
listOfTrafficVolumes M A list of changes in charging conditions for this PDP context, each
listOfTrafficVolumes M A list of changes in charging conditions for this PDP context, each time stamped. Charging conditions are used to categorise traffic
volumes, such as per tariff period. Initial and subsequently changed
time stamped. Charging conditions are used to categorise traffic
QoS and corresponding data values are listed. In GSM, data
volumes, such as per tariff period. Initial and subsequently changed volumes are in octets above the GTP layer and are separated for
QoS and corresponding data values are listed. In GSM, data uplink and downlink traffic.
volumes are in octets above the GTP layer and are separated for
uplink and downlink traffic. In 3G, data volumes are in octets above the GTP-U layer and are
separated for uplink and downlink traffic.
In 3G, data volumes are in octets above the GTP-U layer and are
separated for uplink and downlink traffic. recordOpeningTime M Time stamp when this record was opened.
duration M Duration of this record in the GGSN.
recordOpeningTime M Time stamp when this record was opened.
causeForRecClosing M The reason for the release of record from this GGSN.
duration M Duration of this record in the GGSN.
diagnostics O A more detailed reason for the release of the connection.
causeForRecClosing M The reason for the release of record from this GGSN.
recordSequenceNumb C Partial record sequence number.
diagnostics O A more detailed reason for the release of the connection.
er
recordSequenceNumb C Partial record sequence number.
nodeID O Name of the recording entity.
er
recordExtensions O A set of network/ manufacturer specific extensions to the record.
nodeID O Name of the recording entity. localSequenceNumber O Consecutive record number created by this node. The number is
recordExtensions O A set of network/ manufacturer specific extensions to the record. allocated sequentially including all CDR types.
localSequenceNumber O Consecutive record number created by this node. The number is
apnSelectionMode O An index indicating how the APN was selected.
allocated sequentially including all CDR types.
servedMSISDN O The primary MSISDN of the subscriber.
apnSelectionMode O An index indicating how the APN was selected. chargingCharacteristic C The Charging Characteristics flag retrieved from subscriber's data.
servedMSISDN O The primary MSISDN of the subscriber. s
chargingCharacteristic C The Charging Characteristics flag retrieved from subscriber's data. chChSelectionMode O Holds information about how Charging Characteristics were
selected.
s
chChSelectionMode O Holds information about how Charging Characteristics were sgsnPLMNIdentifier O SGSN PLMN identifier (MCC and MNC) used during this record.
selected.

sgsnPLMNIdentifier O SGSN PLMN identifier (MCC and MNC) used during this record.

Page 105
Charging: Prepaid Solution

Real-time Prepaid
HLR
SCP

CAMEL 3 SCP

SGSN

SGSN

CG Billing system

GGSN

Anti-real-time Prepaid

Page 106
Charging: Content Based Charging

Online Charging System*

Policy and Charging
Control Node Gq
Service Data (PCCN)
CAMEL AF
SCP Flow Based
Ry Rx
Credit Control
PDF CRF

Go
Gx
Gy

Gateway
(GW)

TPF PEP
Charging
Gateway
Function Gz

Charging
Collection
Function

Page 107
 Roaming Scenario: Visiting GGSN

Home PLMN ISP

Network
SGSN GGSN
MS
UE
MS BG
HLR

Subscription
data

Roaming
UE BG
Re-attach ISP
- SGSN GGSN Network
ME
U S
Visiting PLMN

Page 108
 Roaming Scenario: Home GGSN

Home PLMN ISP

Network
SGSN GGSN
MS
UE
MS BG
HLR
IPSec
Subscription Tunnel
Hop-by-hop
data
GRX Network
GTP addressing

Roaming
UE BG
Re-attach GGSN
ME
U S SGSN
SGSN S
GSN
Visiting PLMN

Page 109
 Gb Networking

Mode I Mode II
The PCU is put at the BSS side, and is directly connected with the SGSN The PCU is put at the BSS side, and is connected with the SGSN through the frame
through point-to-point relay. The mode I is suitable when the PCU and SGSN are relay network.
close in distance. It is used more frequently in actual application.

Mode III Mode IV

If the PCU does not support Gb over IP but E1 only, use routers to realize switching If the PCU supports Gb over IP, it can be directly connected with the SGSN through IP links
from E1 to FR over IP for the connection between the SGSN and the PCU.

Page 110
IU-PS Networking

MGW transmitting mode

ATM networking mode If the operator does not have the ATM network, and the transmission resource is
If the operator has ATM network, the RNC is connected with the limited, so data in the Iu-PS interface can first be converged to the MGW, and
SGSN through the ATM network. then be transmitted to the SGSN through the PVC.

IP networking mode
The SGSN9810 must support the feature of Iu over IP on both user plane and control plane. Therefore, the RNC can be directly connected with the SGSN
through the IP network.

Page 111
COMUNICACIONES MÓVILES
4G/LTE
1. Introducción
3GPP Releases
GPRS HSUPA
171.2Kbit/s 5.76 Mbit/s
UMTS LTE
Phase 2 Release 97 2 Mbit/s 100 Mbit/s
Release 6
Release 99 Release 8

LTE Advanced
1Gbit/s

Release 99 Release 7/8 Release 9/10

Phase 1
EDGE Release 5
HSDPA+
GSM 473.6 Kbit/s HSDPA 28.8 Mbit/s
9.6Kbit/s
14.4 Mbit/s 42Mbit/s
Voice Solutions in the LTE Era

➢ It is a transitional solution. ➢ It is a standard

➢ It is a supplement to Circuit mainstream
single radio voice call switched solution for LTE
continuity (SRVCC). IMS-SRVCC voice services.
fallback
➢ It provides voice services (CSFB) ➢ It has been
for long term evolution accepted by
(LTE) roaming subscribers mainstream
RCSe
before IMS roaming carriers.
standards matures.
VoLTE
➢ Mobile phones used the ➢ It is the way in which OTT
simultaneous voice and providers run multimedia
LTE solution to support “Dual- Over the communication services.
2G/3G voice services standby” Top (OTT) ➢ It is a great challenge for
and LTE data services. carriers.
➢ It is not a real VoLTE
solution, but only a
transitional solution.
2. Fundamentos de Red 4G

23
 LTE Key Technology
Key LTE Technologies M M E / S- GW M M E / S- GW

1
S

1
S
X2 E -U T R A N
eNB eNB

Sys tem Bandwidth

Sub- c ar r iers
eNB

Sub-f rame Scalable BW

Frequency
Flat
Architecture
Time frequency
resource for User 1
Time frequency
resource for User 2
T im e
DL OFDMA Time frequency
resource for User 3

Supporting
High Performance
S y s t e m Ba ndwi dt h

S u b -f ra m e
Si ngle Ca rri e r
MIMO
Frequency

T i m e f re q ue nc y
H.O.M
re s o urc e f o r U s e r 1

T i m e f re q ue nc y
re s o urc e f o r U s e r 2
T i me
T i m e f re q ue nc y
re s o urc e f o r U s e r 3

UL SC-FDMA Data MIMO

Streaming Channel
Multiple Access Techniques

LTE uses:
DL: OFDMA
UL: SC-FDMA

OFDMA
Each user allocated a
different resource
which can vary in time
and frequency.
Multiple Access Technology
Multiple Access Technology

HHU
I SAL
IWC
I EOI TNESCEHMNO
I COLONGDIUECSTCOOR,. LTD. Page 27
HoM (High Order Modulation) 2 bit per symbol 4 bit per symbol 6 bit per symbol

AMC (Adaptive Modulation & Coding)

64 QAM

Usually, 64QAM is activated in area near antenna

3. Arquitectura de Red 4G

30
 3 Network Architecture

3.1 SAE Network Architecture

3.2 Interfaces and Protocols

3.3 Roaming Architecture

3.4 Interworking with GERAN/UTRAN

HHU
I SAL
IWC
I EOI TNESCEHMNO
I COLONGDIUECSTCOOR,. LTD. Page 31 Page 31
 Network Architecture LTE SAE (System Architecture
Evolution
SAE: System Architecture Evolution SAE
EUTRAN: evolved UTRAN
UTRAN: Universal terrestrial radio
access network
BTS: Base station Transceiver
BSC: Base station controller
Node B: node B
RNC: Radio network controller
SGSN: Supporting GPRS serving node
HLR: Home location register

eNodeB: evolved node B

MME: mobility management entity EUTRAN
PDN GW: PDN Gateway
SGW: Serving gateway
HSS: Home subscriber server
PCRF: Policy control and charging
rules function
Network Architecture LTE architecture becomes much more simple and flat, and lead to:
• lower networking cost

Comparison • higher networking flexibility

• shorter time delay of user data and signaling

3G: Legacy Architecture LTE: Flat Architecture

M M E / S-GW M M E / S-GW
MSC/SGSN/GGSN

1
S

1
S
RNC RNC
X2 E -U T R A N
Iub Iub eNB
eNB

eNB
NodeB NodeB NodeB NodeB
 2G/3G to LTE/SAE Architecture

PGW
SGW
MMEPCRF
Terminals LTE Network SAE/EPC Network

• Flat and all-IP Network Architecture

• Reduced Complexity
• Seamless Mobility
• Separation of Control Plane (MME) and User Plane (SGW) with open interface S11

Page 35
LTE/SAE Architecture - 2 • Negotiates QoS requirement with application
• Authorizes QoS request against user
• NAS signaling with UE GERAN subscription data
(+security) • End-users profile
SGSN (MSISDN, IMSI, APN) • Receives network events
• Tracking Area list • HDSSe/HcLiRdes policy rules to be applied
management (filters, QoS parameters QCI, MBR, GBR, ARP)
• PGW and SGW selection
• Bearer control PCRF • Application
• Authentication HSSUTRAN S12 S3 S6a • Signalling (PCRF
HSS
• Handover coord. with S4 and terminal)
SGW, MME or SGSN Gx
S1-MME Rx AS
MME S11 S5/S8
SGi INTERNET / intranet /
Terminal LTE Operators in-house
S1-U
S-GW & 3rd Party AS
eNODE-B PDN-GW
• Application (incl. signaling) • Radio resources allocation
• UL filtering of traffic flow • Admission Control • Mobility anchor for
to bearer • UL filtering, inter-eNB handover • IP address allocation
• APN-AMBR policing • interference control (ICIC) • Lawful Interception • EPS bearer control
• Mobility support • Handover • Packet Routing and • Lawful Interception
• Idle mode reselection • Idle mode cell reselection forwarding • DPI
3 Network Architecture

3.1 SAE Network Architecture

3.2 Interfaces and Protocols

Page 38
 User Plane Control Plane

LTE-Uu Interface

• Transfer of upper layer PDUs

•Error correction through ARQ (CRC check provided by
the physical layer)
• Segmentation • Header compression and decompression for user plane data.
• Concatenation of SDUs for the same radio bearer • Ciphering and deciphering for user plane and control plane data.
• In-sequence delivery of upper layer PDUs except at HO. • Integrity protection and verification for control plane data.
• Duplicate Detection • Handover support functions.
• Protocol error detection and recovery • Discard for user plane data due timeout.
• SDU discard
• Reset

The AS protocols on E-UTRAN-Uu (RRC, PDCP, RLC, MAC and the physical LTE layer) implements the Radio Resource Management and supports the
NAS protocols by transporting the NAS messages across the E-UTRAN-Uu interface.

Page 39
Interface S1 It carries signaling messages
between eNodeB and MME

S1-MME
MME

S1-U

SGW
E-UTRUAN
It carries user traffic between
eNodeB and SGW

S1 interface connects the EUTRAN to the EPC. S1 is split into control plane, called S1-MME, and a user plane, called
S1-U.

Page 40
 User Plane Control Plane

S1-MME Interface • One logical S1AP

connection per UE.
•Multiple UEs supported via a
single SCTP association.
NAS NAS
R e la y
RRC S1-AP
RRC S1-AP
PDCP PDCP SCTP SCTP

RLC RLC IP IP
MAC MAC L2 L2

L1 L1 L1 L1

LTE-Uu S 1 -M M E
UE eNodeB MME
• Set up, modification and release of E-RABS.
• Establishment of an initial S1 UE context
Provides reliable transport.
• Paging and S1 management functions.
• it’s rate adaptative and message-oriented.
• NAS signaling transport functions between UE and MME.
• Multi-streaming function
• Status transfer functionality
• Trace of active UE’s, and location reporting. • Multi homing
•Mobility functions for UE to enable inter and intra RAT
HO.

S1MME is responsible for EPS bearer setup and release procedures, handover signaling, paging, NAS Signaling transport
and UE context management.

Page 41
 User Plane Control Plane

S10 and S11 Interfaces

The main function is to transfer the contexts
for individual terminals attached to EPC and
thus sent on a per UE basis.

Keeps the control and user plane procedures in sync for

a terminal durng the period that the terminal is seen
active/attached in the EPS.

Page 42
 User Plane Control Plane

Interfaces S5/S8 (Control Plane)

There are two protocol options to be used in S5/S8 interface: GTP or PMIPv6

PMIPv6 PMIPv6

IPv4/IPv6 IPv4/IPv6

L2 L2

L1 L1

Serving G W
PDN GW

S 5 or S 8

S5/S8 over GTP S5/S8 over PMIPv6

•Provides the functionality associated with •Provides tunneling management between the Serving
creation/deletion/modification/change of bearers for Gateway and PDN Gateway.
individual user connected to EPS.

Page 43
 User Plane Control Plane

S6a and Gx Interfaces

D iamet er D iamet er

SCTP/TCP SCTP/TCP

IP IP

L2 L2

L1 L1

S6a
MME HSS

Interface Functionality: Interface Functionality:

• Exchange location information
• Authorize a user to access the EPS •Gx enables the
• Exchange authentication information
transfer/modification/removal of PCC rules
• Download and handle changes in the subscriber data stored in the server
• Upload the PGW identity and APN being used for a specificPDN connection. from the PCRF to PCEF function within the
•Download the PGW identity and APN pairs being stored in HSS for already ongoingPDN PGW.
connection.

Page 44
 User Plane Control Plane

Interface S13

Interface Functionality:
The S13 and S 1 3 ’ interfaces between the MME and the EIR and between the SGSN and the EIR respectively are used to check the
status of the UE (e.g. if it has been reported stolen). The MME or SGSN checks the ME Identity by sending the Equipment Identity to
an EIR and analyzing the response.

Page 45
 User Plane Control Plane

Interfaces S1-U,SGi and S5/S8 (User Plane)

One or more GTP tunnels
per user
Note that both IPv4 and IPv6 are supported on the transport layer ofIP

Application

IP IP

Relay R e lay
PDCP G T P -U
G T P -U G T P -U
PDCP GTP-U

RLC RLC U D P /IP U D P /IP U D P /IP U D P /IP

MAC MAC L2 L2 L2 L2

L1 L1 L1 L1 L1 L1

L T E -U u S 1 -U S 5 /S 8 S Gi

UE eNodeB Serving G W PDN GW

•GTPU carry encapsulated payload and signalling messages
between nodes.
•Provides non-guaranted data delivery.
• S1-U is the user plane interface between EUTRAN and SGW, carrying user traffic in a GTP-U tunnel.
•SGi is the reference point between the PDN GW and the packet data network. PDN may be an operator external public or private
packet data network or an intra operator packet data network, e.g. for provision of IMS services. This reference point corresponds to Gi
for 3GPP accesses.

Page 46
VoLTE solution overview
Application Server Legacy
O&M Service
Presence/IM/DS/XDMS CTAS
(MMTel AS/SCC AS/IP-SM-GW/Anchor AS/IM-SSF) SCP

EMS
Converged DataBase IMS Core
Legacy
network
MGCF
I/S-CSCF/MRFC/E-
HLR/IMS-HSS/SAE-HSS
CSCF
Provisioning /ENUM /DNS
MRFP IM-MGW
GW

SBC
CS (P-CSCF/A-BCF/A-BGF/ATCF/ATGW)
CCF

EMSC
(SRVCC-IWF/mAGCF/CSFB Proxy)
EPC
DMS

MGW MME S/P-GW PCRF

2G/3G 2G/3G LTE LTE

LTE Handset LTE CPE LTE data-card + softclient

Terminal
4. Funcionalidades de los elementos en una Red 4G

55
 Key Functional Entities of IMS
S-CSCF: Serving-Call Session Control
⚫ CSCF (Call Session Control Function)
Function
⚫ The core element with the same position as softswitch and MSC P-CSCF：Proxy-Call Session Control
⚫ S-CSCF performs routing and triggers services Application
Function
⚫ P-CSCF validates and forwards requests I-CSCF：Interrogating-Call Session Control
⚫ I-CSCF interworks with other IMS networks Function
⚫ In a small network, S-CSCF, P-CSCF, and I-CSCF are commonly integrated into ISC (SIP)
one physical element. PSTN
Cx/Dx(Diameter)
⚫ HSS (Home Subscriber Server) Mg (SIP)
⚫ Stores all subscriber and service-related data
⚫ The same as the HLR in the existing mobile network HSS P/I/S-CSCF MGCF PLMN
⚫ MRS (Media Resource Server) Gq(Diameter) Mr (SIP)

⚫ Plays announcements and collects digits

H.323
⚫ PCRF (Policy Control Rule Function) PDF Core
MGW
MRS
⚫ Manages QoS policies
⚫ MGCF (Media Gateway Control Function)
⚫ Provides conversion between SIP and SUP signaling
⚫ Interworks with the existing signaling network GGSN AC
⚫ MGW (Media Gateway) BAS PGW
GSM/WCDMA WiMAX/
⚫ Provides the conversion between the IP bearer and
WiFi
⚫ the TDM bearer xDSL/LAN LTE
⚫ Interworks with the existing bearer network

Page 56
Key Network Entities: CSCF
⚫ CSCF – Call Session Control Function SIP based Interface
Diameter based Interface
⚫ can be viewed as a SIP based Session Controller.
⚫ includes the three functions: S-CSCF, I-CSCF, P-CSCF.
IMS Application Servers
Sh
HSS
PDF C
x
C ISC BGCF
IMS Terminal G M x
M M
q I- CSCF w i M
w j
G Mw M
m g
Proxy - CSCF Interrogating -CSCF Serving -CSCF MGCF
(P -CSCF) (I -CSCF) (S -CSCF)

- First access point for the UE
- Forwarding of SIP messages
- Generation of Charging CDRs
- Integrity and Confidentiality
Protection Support
- QoS Authorization Support
- Local Service Support
- Lawful Interception Support
- SIP Header Compression
- First contact point of
an operator‘s network.
- Assignment of S-CSCFs
-- Forwarding of SIP messages
- Generation of Charging CDRs
- Topology Hiding Support
- Acts as SIP Register
- Performs the IMS User Authentication
- Loads IMS User Profiles from the HSS
- Performs Session Control
- Performs Service (AS) Control
- May behave as SIP-Proxy or SIP-UA
- Generation of Charging CDRs

Page 57
Key Network Entities: HSS
⚫ HSS – Home Subscriber Server
⚫ is the main centralized database for user related information.
⚫ stores the IMS User Profiles that includes e.g.:
› the User Identification, Addressing information (SIP URI, TE-URI, IMSI, MSISDN, ...)
› the Service Provisioning Information (Filter Criteria).
› the User Mobility Information (S-CSCF address).
› the Charging Server Information (CCF-, ECF address).

H S S
Mobility M a n a g e m e n t Identification ha ndling

Use r security info. generation Service authorization support

Use r security support Ac c e ss authorization

Service Provisioning support Applica tio n Services Su pport

Call / Session establishment support C A M E L Services Su pport

C D G r G c S h S i C x

g s m S C F S IP Application
S e rv e r
G M S C M S C / V L R
IM -S S F C S C F
S G S N G G S N
O S A -S C S

C S D o m a i n P S D o m a i n I M C N s u b s y s t e m

Page 58
Key Network Entities: AS
⚫ IMS Application Servers (AS)
I M S Ap p l i c a t i o n S e r ve r s
⚫ provide SIP-based IMS services (e.g. Presence, PTT, Instant Messaging, Sh
HSS
Supplementary Services, etc. ).
C IS C
⚫ may act as SIP-UA, SIP-Proxy, SIP B2BUA. x

⚫ are invoked by the S-CSCF via the SIP-based ISC interface. S IP S IP

Signaling Signaling
⚫ Different AS types are defined: S -C S C F
⚫ SIP-AS (SIP-Application Server)
⚫ IM-SSF (IP Multimedia Service Switching Function)
⚫ OSA-SCS (OSA Service Capability Server)

Se
SeSrevirvrce
v s Ad mi n i st r a t i ve
CORB
S
See r vi
v i ce
c A S
S
ices EEs
i ce D o ma i n of t h e
e
ss Tr a n s p o S IMS Operator
OSA OSA API CAP Services
rt E S e r vi c
API es
O SA SCS
OSAOSA IIM
IMM- -S S F SIP-AS
SIPS IP -
SCSSCS SSF SS - ASAS
Ad mi n i st r a t i ve I S C (SIP)
F I S C (SIP) ISC S e r vi ce
Se c s
D o ma i n o f t h e (SIP) e
Execution s
3 r d Pa r t y Env ironm ent
Se r vi ce SS--C S C F
Pr o vi d e r CSCF
Page 59
Key Network Entities: MGCF/MGW

⚫ MGCF – Media Gateway Control Function

SIP based Interface
⚫ IM-MGW – IMS Media Gateway Diameter based Interface

Sh
HSS

IS C
C BGCF
x
I M S T e r m i na l M
i M
IS U P ,
S IP M j
B IC C
Signaling g over PSTN /
S -C S C F M GCF IPM/S S 7
n CS-Domain
V oice over V oice
IP over
MGW TDM,
ATM
MGCF:
- performs the signaling conversion SIP → ISUP/BICC.
- controls the MGW via H.248 (Mn reference point).
- generates Charging CDRs for Interoperator Charging.
MGW:
- performs the IMS Bearer traffic conversion e.g. Voice/RTP/UDP/IP → Voice/TDM.
- may perform transcoding e.g. AMR → G.711. May provide Tones/Announcements.

Page 60
Key Network Entities: BGCF
⚫ BGCF – Breakout Gateway Control Function
⚫ is responsible for selecting the MGCF that controls SIP based Interface
the IMS Interworking to the PSTN/CS-Domain. Diameter based Interface

⚫ the Local Breakout and the Remote Breakout are defined.

⚫ the BGCF generates Charging CDRs.

Loc a l B r e a k out R e m ot e B r e a k out

Sh in the local Operator in another Operator
HSS N e two r k N e two r k

IS C
C BGCF M BGCF
x
M k
i M M
M j
M GCF j M GCF
g
S -C S C F MGW MGW
V oice over V oice over
IP IS U P , IP IS U P ,
V oice over T D M , B IC C V oice over T D M , B IC C
ATM ATM

PSTN / PSTN /
CS-Domain CS-Domain

Page 61