Beruflich Dokumente
Kultur Dokumente
GPRS telecom
All rights reserved. Passing on and copying of this
document, use and communication of its contents
Originator(s)
presentation
Jardel JP
PREDISTRIBUTION:
MCD/TD Vlizy: L. Cruchant PJ Pietri D. Isidoro
JY Amaudrut M. Wu JP Humeau
S. Baudet JC Barthelemy F. Huet
R Bialobroda R Le Hegarat
C. Charmont G. Linden
S. Bourdeaut B. De-Jaeger S. Pega
E. Desorbay M. Delprat C. Ramond
P. Dupuy T. Donzel
B. Landais J. Guinand
ABSTRACT
Approvals
Name D.Berthoumieux R. Gdecker R. Bialobroda
SM BTS SSAM MFS SSAM
App.
Name L. Dierick
BSC SSAM
App.
HISTORY
Ed. 01 Proposal 01 06-07-98 first draft
Ed. 01 ip02 21-08-98 - remarks of last working meeting
- O&M interfaces have been detailed
- RRM and BSCGP specification evolutions, taken into
account
- NS-VC management function description
Ed. 01 released 02-02-99 document updated according to review remarks
(TD/SYT/JPJ/81243/Ed.1)
Ed. 02 Proposal 01 10-06-99 miscellaneous updates
Ed. 02 released 30-09-99
Not applicable
Not applicable
END OF DOCUMENT
HISTORY ......................................................................................................................................... 2
REFERENCED DOCUMENTS ......................................................................................................... 2
RELATED DOCUMENTS ................................................................................................................. 2
PREFACE ........................................................................................................................................ 2
1. SCOPE 6
2.1 Introduction 7
3.1 Definitions 12
3.1.1 GPRS Mobile station classes 12
3.1.2 IMSI (International Mobile Subscriber Identity) 12
3.1.3 P-TMSI (Packet Temporary Mobile Subscriber Identity) 12
3.1.4 TLLI (Temporary Logical Link Identity) 12
3.1.5 Location Area Identity (LAI) 12
3.1.6 Routeing Area Identity (RAI) 13
4. ALCATEL ARCHITECTURE 20
5.2 Um interface 33
5.2.1 GSM-RF layer 33
5.2.2 packet data logical channels 34
5.2.3 Channel coding 38
5.2.4 Cell re-selection 39
5.2.5 Timing advance 39
5.2.6 Power control 42
5.2.7 Discontinuous reception (DRX) 43
5.2.8 System information broadcasting 44
6. GB INTERFACE 68
6.2 Addressing 69
6.2.1 Permanent Virtual Channel (PVC) 69
6.2.2 Bearer Channel (BC) 69
6.2.3 Network Service Virtual Connection (NS-VC) 69
6.2.4 Network Service Entity (NSE) 70
6.2.5 BSSGP Virtual Connection (BVC) 70
6.3 NS functionalities 73
6.3.1 Load sharing function 73
6.3.2 NS-VC management function 76
8. GPRS SCENARIOS 99
REFERENCED DOCUMENTS
RELATED DOCUMENTS
PREFACE
The aim of this document is to introduce telecom layer specifications ([6] to [15]), to give to the
reader a general overview.
Therefore, protocols which are described in this document do not deal with all the cases.
Furthermore, in the case of ambiguities between this document and a specific layer
specification, the specific layer specification takes precedence.
(see [1])
not permitted without written authorization from Alcatel
All rights reserved. Passing on and copying of this
document, use and communication of its contents
2.1 Introduction
In many software applications (e.g. web server consultation), data traffic is bursty (i.e. a session may
last several minutes, whereas data is only transmitted during a few seconds).
Data transmission in circuit-switched mode has the drawback to allocate resources during the whole
session, General Packet Radio Service (GPRS) defines a network architecture dedicated to packet
transfer mode, with radio access, which allows service subscriber to send and receive data in an
end-to-end packet transfer mode, without utilizing network resource in circuit-switched mode.
A GPRS network can be linked to different fixed data networks (e.g. IP, X25).
GPRS uses the BSS architecture, but defines a fixed network (GPRS backbone) which is different
from the NSS, and which links the BSS to PDNs (Packet Data Networks).
The BSS is used for both circuit-switched and GPRS services.
The BSS has 2 clients:
- the MSC, for circuit-switched services (A interface)
- the GPRS backbone network, for GPRS (Gb interface)
A
MSC/VLR PSTN
BSS Gi
PDN
e.g. X25
GPRS
Gb Backbone PDN
e.g. IP
Gi
New GPRS radio channels are defined, and the allocation of these channels is flexible, from 1 to 8
radio interface timeslots can be allocated per TDMA frame, timeslots are shared by the active users,
and up and downlink are allocated separately.
The radio interface resources can be shared statically or dynamically between CS and PS traffics as
a function of service load or operator preference.
PLMN
BSS
GGSN PDN
SGSN
GGSN
other PLMN
The following figure shows new interfaces which have been introduced for GPRS needs.
MSC/ HLR
VLR
Gs Gr
Gc
Gp Gf
SGSN
SGSN
other PLMN
signalling interface
The transmission plane consists of a layered protocol structure providing user information transfer,
along with associated information transfer control procedures (e.g. flow control, error detection and
recovery,..)
application
IP/X25 IP/X25
relay
SNDCP SNDCP GTP GTP
LLC LLC
UDP/ UDP/
RLC relay TCP TCP
RLC
BSSGP
MAC BSSGP IP IP
MAC
GSM-RF NS NS L2 L2
GSM-RF
L1bis L1bis L1 L1
- IP (Internet Protocol):
This is the GPRS backbone network used for routeing user data and control signalling.
- BSS-relay:
This function relays LLC PDUs between the Um and Gb interfaces.
- SGSN-relay:
This function relays PDP PDUs between the Gb and Gn interfaces.
- NS (Network Service):
not permitted without written authorization from Alcatel
All rights reserved. Passing on and copying of this
document, use and communication of its contents
It transports BSSGP PDUs and is based on frame relay connection between BSS and SGSN.
- GSM-RF layer
It is the radio subsystem which supports a certain number of logical channels
The signalling plane consists of protocols for control and support of the transmission plane functions:
- controlling the GPRS network access connections such as attaching to and detaching from
the GPRS network
- controlling the attributes of an established network access connection, such as activation of
a PDP address
- controlling the routing path of an established network connection in order to support user
mobility
- controlling the assignment of network resources to meet changing user demands
- and providing supplementary services
relay
GMM/SM GMM/SM GTP GTP
LLC LLC
UDP UDP
RLC relay
RLC
BSSGP
MAC BSSGP IP IP
MAC
GSM-RF NS NS L2 L2
GSM-RF
L1bis L1bis L1 L1
3.1 Definitions
An IMSI is allocated to each mobile subscriber in GSM. This is also the case for GPRS-only mobile
subscribers.
Between the MS and the SGSN, TLLI unambiguously identifies the logical link.
It is used for addressing purposes at the RR sub-layer.
Within a routing area, there is a one-to-one correspondence between TLLI and IMSI that is only
known in the MS and SGSN.
TLLI is derived from a P-TMSI and does then provide user identity confidentiality.
There are 4 types of TLLIs:
- Local TLLI: derived from the P-TMSI allocated by the SGSN and only valid in the RA
associated to the P-TMSI
- Foreign TLLI: derived from a P-TMSI allocated in another RA
- Random TLLI: selected randomly by the MS, when the MS has no valid P-TMSI
- Auxiliary TLLI: used for an anonymous access
For GPRS, as paging is more frequent than in GSM, Routeing Areas (RA) have been defined, which
not permitted without written authorization from Alcatel
In order to access the GPRS services, an MS shall first make its presence known to the network, by
performing a GPRS-attach to the SGSN.
This operation establishes a logical link between the MS and the SGSN, and makes the MS available
for paging via SGSN and notification of incoming GPRS data.
In the attach procedure the MS provides its identity and an indication of the type of attach (GPRS-
attach or combined GPRS/IMSI attach).
The identity provided to the network is
- either the P-TMSI (if the MS has a valid P-TMSI)
- or the IMSI
At the RLC/MAC layer, the MS identifies itself with a TLLI (a Foreign TLLI if a P-TMSI is available or
a Random TLLI if valid P-TMSI is not available).
The Foreign or Random TLLI is used as an identifier during the attach procedure until a new P-TMSI
is allocated.
GPRS attach function is similar to IMSI attach
- MS authentication
- ciphering key generation
- TLLI allocation (derived from the new P-TMSI)
- subscriber profile request to the HLR
After having executed the GPRS attach,
- the MS is in STANDBY state and may activate PDP contexts
- MS location is tracked (RA accuracy)
- communication between MS and SGSN is secured
- charging information is collected
- HLR knows MS location in accuracy of the SGSN
The detach function allows an MS to inform the network that it wants to make a GPRS and/or IMSI
detach and the network to inform an MS that it has been GPRS-detached or IMSI-detached by the
network.
A PTP (Point-To-Point) GPRS subscription contains the subscription of one or more PDP (Packet
Data Protocol) addresses.
Each PDP address is described by an individual PDP context in the MS, the SGSN and the GGSN.
The PDP state indicates whether the PDP address is activated for data transfer or not.
- inactivate: no routing information
- activate: contains mapping and routing information for transferring PDUs, between MS
and GGSN.
The PDP context is updated according to changed subscriber location initiated by MM procedures.
In order to send and receive GPRS data, the MS shall activate the PDP address that it wants to use.
This operation makes the MS known in the corresponding GGSN, and interworking with external data
networks can begin.
User data is transferred transparently between the MS and the external data networks (encapsulation
and tunnelling)
MS SGSN GGSN
PDP context deactivation can be initiated either by the MS or by the SGSN, or by the GGSN.
3.3.1 MM states
The MM activities related to a GPRS subscriber are characterised by the following states:
- IDLE
The subscriber is not attached to the GPRS MM, paging is not possible.
The subscriber is not known from the different GPRS nodes.
The MM context holds no valid location or routing information for the subscriber.
- STANDBY
The subscriber is attached to GPRS MM.
CS and PS paging are possible but data transmission and reception are not possible.
The SGSN MM context contains only the RAI location information.
The MS may initiate activation or deactivation of PDP contexts while in this state.
- READY
After paging, the MM state in the SGSN is changed to READY when data or signalling
information is received from the MS.
The location information in the SGSN MM context is extended to cell level.
The MS may send and receive data in this state.
Regardless if a radio resource is allocated to the subscriber or not, the MM context remains
in the READY state even when there is no data being communicated.
The READY state is supervised by a timer. When it expires, the state becomes STANDBY.
This interaction needs the presence of the Gs interface, which provides interactions between SGSN
and MSC/VLR.
The association supports the following actions:
- IMSI attach and detach via SGSN (combined GPRS/IMSI attach/detach are possible)
- coordination of LA and RA update (combined RA/LA update)
- paging for a CS connection via the SGSN
MSC
Gs
BTS BSS
CS Paging
PPCH/PCH
PS Paging
SGSN
Gs
BTS BSS
CS Paging
PACCH
SGSN
MSC
CS Paging
BTS BSS
PCH
PS Paging
SGSN
MSC
CS Paging
BTS BSS
PCH
PPCH PS Paging
SGSN
An MS in STANDBY state is paged by the SGSN before a downlink transfer to that MS.
At the response of the paging (any LLC PDU), the MM state moves to READY and the downlink
transfer begins.
MS BSS SGSN
STANDBY
PDP PDU
Paging request (1)
GPRS Paging request (2)
READY
- (1): On reception of a downlink PDP PDU, in the STANDBY state, the SGSN sends a BSSGP
paging request, with the IMSI (to calculate the MS paging group), the P-TMSI (identifier by
which the MS is paged), the Routing Area (determine the set of cells to be paged), QoS (not
used in B6.2) and the DRX parameters
- (2): The BSS pages the MS with one message in each cell belonging to the Routing Area
- (3): The MS responds with any LLC PDU which is interpreted by the SGSN as a page response.
CS paging are received from the SGSN, only in network operation mode I.
When a MS is attached to GPRS, the MSC/VLR executes paging for circuit-switched services via
SGSN. Class A and B MSs have the capability to receive CS page while attached to GPRS.
If the MS is in STAND-BY state, then it is paged in the routeing area.
If the MS is in READY state, then it is paged in the cell.
Upon receipt of a paging request message for a circuit-switched service, the MS may accept to
respond to this request and shall then follow the CS procedures for paging response.
When received at the BSS, the paging response message is sent to the MSC.
A Packet Control Unit (PCU) has been defined in [1], where are implemented RLC/MAC functions:
- LLC layer PDU segmentation into RLC blocks for downlink transmission
- LLC layer PDU reassembly from RLC blocks for uplink transmission
- PDCH scheduling functions for the uplink and downlink data transfers
- downlink and uplink ARQ (Automatic Retransmission Request) functions
- channel access control functions (e.g. access request and grant)
- radio channel management functions (e.g. power control, congestion control, broadcast
control information)
A PCU controls the GPRS activity of one cell.
The functions implemented, inside the Channel Codec Unit (CCU) are:
- channel coding functions, including FEC (Forwarding Error Correction) and interleaving
- radio channel measurement functions, including received quality level, received signal level
and information related to timing advance measurements.
The CCUs are implemented in the BTS.
CCU BTS
not permitted without written authorization from Alcatel
All rights reserved. Passing on and copying of this
document, use and communication of its contents
PCU
CCU
BTS
CCU
PCU
CCU
BTS
CCU
PCU
CCU
Abis Gb
packet-switching function
The Alcatel approach for the implementation of GPRS in the BSS consists of a smooth and cost
effective introduction of GPRS by minimizing the hardware modification needed to the already
installed network elements (i.e. BTS and BSC).
To this end, a new network element, the MFS, supporting nearly all the GPRS specific functions of
the BSS, defined in the GPRS standard:
- PCU function
- standard Gb interface protocol stack
is introduced.
From the BTS perspective, the radio channels can be dynamically configured as TCH or PDCH.
The MFS is connected to the BSC by means of already installed Ater physical lines.
In order to support low GPRS traffic load, in a more optimized way, the transmission resources can
be shared between GPRS and circuit-switched traffic
CCU Abis
CCU
BSC MFS
BTS
CCU PCU
Gb
Um BTS
BSC Ater
- PCU location
Since PCU functionalities are located in the MFS, GSM-RF layer has to be extended to the MFS
(L1/L2 GCH layer) (see Figure 14 and Figure 15)
Two proprietary layers are implemented to extend the radio interface to the MFS (see Figure 14):
- L1-GCH is the physical layer which uses a synchronous mode of transmission (16 kbit/s)
- L2-GCH consists in a protocol between the MFS and the BTS for synchronisation with the
radio interface and channel activation.
GCH links go through the BSC transparently.
application
IP/X25
SNDCP SNDCP
LLC LLC
RLC relay
RLC
BSSGP
MAC BSSGP
MAC
GSM-RF relay L2-GCH NS NS
L2-GCH
GSM-RF
L1-GCH L1-GCH L1bis L1bis
In this case, CCCH is not used, by GPRS functions and the BSC is transparent for GPRS common
signalling (see Figure 15).
- GMM/SM (GPRS Mobility Management/Session Management)
This protocol supports mobility management functionality such as GPRS attach/detach,
security, routeing area update, location update, PDP context activation/deactivation.
- RRM (Radio Resource Management) layer provides services for packet connection
management, for radio resource management and for paging requests routing.
GMM/SM GMM/SM
LLC LLC
relay
RR/RRM
RRM
RLC RLC BSSGP BSSGP
MAC MAC
GSM-RF relay L2-GCH NS NS
L2-GCH
GSM-RF
L1-GCH L1-GCH L1bis L1bis
In this case, BSC signalling layers are concerned, in the connection establishment phase to access
not permitted without written authorization from Alcatel
All rights reserved. Passing on and copying of this
document, use and communication of its contents
GMM/SM
LLC
BSSGP
RR/RRM RRM
relay BSCGP NS
RR BSCGP
GSM-RF relay L2-GSL
L2-RSL L2-RSL L2-GSL
GSM-RF
L1-RSL L1-RSL L1-GSL L1-GSL L1bis
4.1.5.1 Principles
not permitted without written authorization from Alcatel
All rights reserved. Passing on and copying of this
document, use and communication of its contents
AterMux
Ater A
signalling n 7
TC MSC
SM SM
BSC
GCH
MFS SGSN
GSL
Gb
Abis Ater
- Abis interface: This interface is used both for CS and GPRS traffic.
With G2 BSC, resources are dynamically allocated either to GPRS traffic or
to circuit-switched traffic.
16kbit/s channels are dynamically switched by the BSC between Abis and
Ater interfaces.
- Ater interface: This interface is used both for CS and GPRS traffic.
On this interface, two functionally different types of channels are used, for
GPRS traffic:
- GPRS Signalling Links (GSL) for signalling purposes between the BSC and
the MFS (not supported by G1 BSC)
One GSL channel consists of one 64 kbit/s LAPD channel. For redundancy
reason it is duplicated.
they are used for:
- dynamic configuration of radio timeslots
- CS/PS paging, GPRS access procedure (when CCCH is used)
- O&M purposes
- GPRS traffic Channels (GCH) carrying the GPRS traffic between the MFS
and one GPRS radio timeslot in the BTS (16 kbit/s)
GCH channels are dynamically through connected by the BSC between Abis
and Ater interfaces.
TS
TS
tributary 1 (4 nibbles)
tributary 2
SM
tributary 3
tributary 4
PCM link
CS nibbles between BSC
and MFS
(AterMux)
CIRCUIT
N7 signalling link(s) SWITCHED
data
nibbles
GPRS
GSL link(s)
When the AterMux is mixed CS/GPRS, the CS timeslots are cross-connected transparently towards
the MFS-TC interface in order to transcode the voice, and the GPRS timeslots are converted into the
Gb interface protocol to be forwarded to the SGSN. (see Figure 20)
AterMux
MFS
MSC
BSC
SGSN
PCM
Gb
CS circuit
1) combined AterMux links and Gb links through TC and MSC (see Figure 21)
- CS timeslots are routed transparently through the MFS
- GPRS timeslots are processed in the MFS and replaced by Gb timeslots
- GPRS timeslots are set as transparent in the TC
BSC
SGSN
Gb
CS circuit
3) Gb links between MFS and SGSN through MSC (see Figure 22)
- a PCM is dedicated to Gb interface
- GPRS timeslots are processed in the MFS and replaced by Gb timeslots
MFS MSC
PCM
BSC
SGSN
Gb
(all the 3 options may use a synchronous frame relay network to access the SGSN)
OMC-R HLR
BSS Gr
Gb
Gn
Gs
MSC/VLR
1 to n relation
- Gs interface:
Through this interface, an association is created between SGSN and MSC/VLR to provide for
interactions between SGSN and MSC/VLR.
The association is used for coordinating MSs that are both GPRS-attached anf IMSI attached
(coordination of LA and RA update, CS paging via SGSN,...)
When this interface is present, Network operates in mode I (see 3.4.1)
- Gn interface
Interface between GSN nodes in the GPRS backbone network.
The GTP on this interface includes both signalling and data transfer procedures.
- Gr interface
Interface between SGSN and HLR.
MM procedures use MAP protocol on this interface.
RLC
PCCCH
MAC
PBCCH
L2-GCH L2-GCH
PDTCH GCH
L1-GCH L1-GCH
- Packet data transfer and associated signalling
Um - common signalling on PBCCH/PCCCH
5.2 Um interface
The purpose of this layer is to provide communication between the MSs and the BTS.
This layer supports multiple MSs sharing a single physical channel.
The access scheme is Time Division Multiple Access (TDMA) with eight basic physical channels per
carrier (TS 0 to 7).
A GPRS time-slot is named a Packet Data CHannel (PDCH)
0 2 7 0 2 7 0 2 7
0 1 2 3 48 49 50 51
frame 0 4 8 1 13 17 21 2 26 30 34 3 39 43 47 5
2 5 8 1
block B0 B1 B2 B3 B4 B5 x B6 B7 B8 B9 B10 B11 x
Figure 26 52- multiframe
- burst types
On PRACH access bursts are used. On all other packet data logical channels, radio blocks
comprising 4 normal bursts are used. The only exception is the Packet Control ACK message on
uplink PACCH which comprise 4 consecutive access bursts.
In this case, BCCH and CCCH are used both for circuit-switched traffic and packet traffic.
So BSC has to forward uplink CCCH flow either towards the MSC or the MFS.
BCCH
PTCCH
BCCH
PBCCH
PTCCH
On the radio interface, data can be coded according to four different coding schemes, CS1 to CS4
(CS3 and CS4 are not part of the GPRS step 1).
These coding schemes offer different redundancy levels.
RLC/MAC block
MAC header (1 byte) RLC header (2 bytes) RLC data unit spare bits
RLC data block without spare bits
CS1 is always used for signalling. (it is the most protected CS)
CS1 and CS2 can both be used for traffic, depending on radio conditions.
This choice is done by the MFS (RRM/RLC layer), according to
- reception quality
- and level measurements performed by the BTS,
and coding is applied, on the radio interface, on RLC/MAC PDU + BCS (Block Check Sequence);
In the UL, the coding scheme is transmitted to the MS in the TBF establishment phase.
If the MFS decides to change the coding scheme, it sends an extra PACKET UL ACK/NACK
message to the MS.
An O&M parameter allows to enable/disable the CS adaptation mechanism.
MS BTS MFS
coding
channel coding scheme coding O&M
scheme
determination
uplink flow
reception
measurements
RXQUAL/RXLEV
BTS type
The timing advance procedure is used to derive the correct value for timing advance that the MS has
to use for the uplink transmission of radio blocks.
The timing advance procedure comprises 2 parts:
- initial advance estimation
- continuous timing advance update
It is based on BTS measurements, on the single access burst carrying the Packet Channel Request.
The Packet UL Resource Assignment then carries the estimated timing advance value (TA) to the
MS. This value shall be used by the MS for the uplink transmissions until the continuous timing
advance update provides a new value.
MS BTS MFS
In this case a polling indication (see 5.5.4.2) is sent in the Packet DL Resource assignment to
request to the MS a Packet Control ACK as four access bursts, on which the timing advance will be
calculated, by the BTS.
MS BTS MFS
LLC PDU
(PACCH)
timing
advance
calculation Packet control ACK
(timing advance)
TA
calculation
TA-message n/38
n/38
TA
calculation
TA-message n+1/12
n+1/12
TA
calculation
TA-message n+1/38
n+1/38
TA
calculation
TA-message n+2/12
TA-message
update
This function allows a MS not to monitor all PCCCH blocks, but only blocks defined by its paging
group.
Negotiation of DRX parameters is per MS, an MS may choose to use DRX or not together with some
operating parameters given to the SGSN, in the GPRS-Attach message:
- DRX/non-DRX indicator
- [DRX period] defined by SPLIT_PG_CYCLE
(the DRX period is equal to about 15,36/SPLIT_PG_CYCLE seconds, 15,36 s corresponds to
64 52-multiframes)
- [non-DRX timer] time period within which non-DRX mode is kept after leaving the transfer
state.
These parameters and the IMSI (which is used to determine the paging group) are sent to the MFS in
- page request (to determine on which block the paging request will be sent)
- DL blocks (to determine on which block the Packet DL assignment will be sent)
B0 B1 B2 B3 B4 B5 B6 B7 B8 B9 B10 B11
PBCCH PG 0 PBCCH PG 2 PBCCH PG 1 PBCCH PG 3 0
PBCCH PG 4 PBCCH PG 6 PBCCH PG 5 PBCCH PG 7 1
When page for CS services is conveyed on PPCH, it follows the same scheduling principles as the
page for packet data
The BCCH indicates whether or not packet switched traffic is supported (RA_COLOUR field in SI3 is
present if GPRS is supported in the cell), SI13 message shall be sent on BCCH if and only if GPRS
is supported in the cell.
There are two distinct cases for the network to convey the relevant information to the MS:
- no PBCCH in the cell
The MS uses the common BCCH system information messages for both CS and GPRS services (in
this case it is not possible to indicate to the MS the neighbour cells which effectively support GPRS,
nor to use specific reselection parameters for GPRS).
SI13 contains all necessary parameters for GPRS.
- PSI2:
- list of PCCCHs
- list of mobile allocations
- PSI3:
- BA_lists ( BCCH allocation in the neighbour cells)
- cell reselection parameters
To avoid that MSs which are involved in a data transfer have to read PBCCH or BCCH,
- PSI1 is broadcast on PACCHs, if there is a master PDCH
- PSI13 (same information than in SI13) is broadcast on PACCHs, if there is no master
PDCH
In addition to radio resource management, the BSCGP layer is also used for the following purposes:
- radio signalling
- CS/PS paging (when there is no GPRS master channel)
- channel request/assignment (when there is no GPRS master channel) (see 5.5.2.1.1.2
and 5.5.2.1.2.2)
- system control
- GSL reset procedure
After link recovery, this procedure is performed to synchronize PDCH allocation and
entity status information.
- state change indication (related to: cell, BSS, and PCM entities)
- traffic control (access class changes)
- cell start/stop for GPRS traffic (MFS has to notify this information, in order to broadcast
this information on SI3)
BSC MFS
radio signalling
BSCGP BSCGP
GPRS radio resource management
system control
L2-GSL L2-GSL
L1-GSL L1-GSL
A cell supporting GPRS may allocate resources on one or several physical channels (i.e. PDCHs) in
order to support the GPRS traffic.
Those PDCHs, shared by the GPRS MSs are taken from the common pool of physical channels
available in the cell.
The allocation of physical channels to circuit switched services and GPRS is done dynamically
according to the capacity on-demand.
Common control signalling required by GPRS in the initial phase of the packet transfer is conveyed
on PCCCH, when allocated, or on CCCH.
GPRS does not require permanently allocated PDCHs.
However, the existence of PDCH does not imply the existence of PCCCH.
The information about PCCCH is broadcast on BCCH.
This management is realized, by the RRM layer, through the BSCGP layer (GPRS radio resource
management) (see Figure 36):
The dynamic allocation of the GPRS Master channel is not supported in B6.2 (i.e. there is no
not permitted without written authorization from Alcatel
All rights reserved. Passing on and copying of this
document, use and communication of its contents
The operator configures statically whether a GPRS cell supports or not a MPDCH (6).
At cell activation, MFS requests the BSC to allocate one slot which is then afterwards
marked as a master PDCH (4).
PDCH
BSC_LOAD management
(3)
packet channel
req/rel.
GCH ch.
act/release. (2)
This layer has to provide the continuation of the radio interface from the BTS to the MFS.
For this purpose, the radio and GCH interfaces have to be synchronised.
A L1GCH channel has a transmission rate of 16 kbit/s (320 bits frames, every 20 ms)
The following figure shows the ideal alignment between the MFS and the BTS, in terms of buffer
delay in the BTS.
F F F F
F N N N N
N 1 2 3 5
0 2 5 8 1
52 multiframe B0 B1 B2 B3 B4 B5 B6 B7 B8 B9 B 10 B 11
Downlink
GPRS
frames
(ideal
B1 B2 B3 B4 B5 B6 B7 B8 B9 B 10 B 11 B0
alignment)
T1 T2 T3 T4 T5 T6 T7 T8 T9 T10 T11 T0
The MAC function defines the procedures that enable multiple MSs to share a common transmission
medium, which may consist of several physical channels (PDCHs).
The MAC function provides arbitration between multiple MSs attempting to transmit simultaneously.
The RLC function defines the procedures for a bit-map selective retransmission of unsuccessfully
delivered RLC data blocks and for segmentation and re-assembly of LLC PDUs.
The RRM function provides services for packet connection management, for radio resource
management, for paging requests over radio interface.
5.5.1 Definitions
A TBF is a physical connection used by 2 RR entities (one in the MS, the other in the MFS, both
involved in a point to point dialogue for packet connection establishment) to support the
unidirectional transfer of LLC PDUs on packet data physical channels.
The TBF is allocated radio resource on one or more PDCHs and comprises a number of RLC/MAC
blocks carrying one or more LLC PDUs.
A TBF is temporary and is maintained only for the duration of the data transfer.
UL TBF
DL TBF
PDCH4
PDCH2
PDCH1 PDCH
PDCH3
MS
MS1 MS2 MS3 MS4
downlink flow
uplink flow
Each TBF is assigned a TFI, by the MFS. The TFI is unique in each direction, within a cell, but the
not permitted without written authorization from Alcatel
All rights reserved. Passing on and copying of this
document, use and communication of its contents
same TFI value may be used concurrently for TBFs in opposite directions.
(32 values , per cell, for each direction: DL and UL)
In the STANDBY or in the READY state (see 3), a TLLI is allocated, by the SGSN, to the MS.
The TLLI identifies a link between a MS and the SGSN.
5.5.1.4 RR modes
The establishment of a Temporary Block Flow can be initiated by either the MS or the network.
The request for the establishment of a TBF is performed
- on the PCCCH, if it exists
- if not, on the CCCH
The purpose of MS initiated TBF establishment is to establish a TBF to support the transfer of LLC
PDUs in the direction from the MS to the network (uplink).
Packet access shall be done on PCCCH
The PACKET CHANNEL REQUEST message is sent on PRACH and contains the following
parameters, according to the packet channel access:
Priority field exists only in 11 bits format, the 8 bits format has a default priority: 4 the lowest.
Short access shall be used if the amount of data can fit in 8 or less than 8 RLC/MAC blocks.
On receipt of the PACKET CHANNEL REQUEST, radio resources are allocated and a PACKET UL
ASSIGNMENT message is returned to the MS with the following parameters:
- allocation type (dynamic allocation)
- resource allocation (PDCH(s))
- coding scheme to apply
- TFI
- USF(s) (one for each PDCH)
- packet timing advance (initial value and timing advance index)
GPRS telecom presentation
ED 02 released
256_02.DOC
MCD 30/09/1999
3BK 11202 0256 DSZZA 52/122
- packet request reference
This field provides the information field sent in the PACKET CHANNEL REQUEST and the
frame number (modulo 42432), in which the PACKET CHANNEL REQUEST was received.
The purpose of this field is to address the MS and to solve possible contention situations.
not permitted without written authorization from Alcatel
All rights reserved. Passing on and copying of this
document, use and communication of its contents
The MS is requested to send a Packet Control Acknowledgement. Allocation of radio blocks, to the
TBF, will start only on Packet Control Acknowledgement reception.
If radio resources are not available, the MFS sends a PACKET ACCESS REJECT to the MS, on the
same PCCCH on which the Packet Channel request message was received.
To solve the case where 2 MSs would have sent a PACKET CHANNEL REQUEST with the same
information field, on the same frame number, the MS shall send its TLLI in the first 3 RLC data
blocks.
The MFS acknowledges, with PACKET UL ACK/NACK, the first correctly received RLC data block.
This message contains the TLLI which should solve the contention (the discarded MS will receive a
PACKET UL ACK/NACK with the right TFI, but with another TLLI)
MS BTS MFS
(PRACH)
timing idle
advance
calculation packet channel
req. (+ TA)
resource
packet UL assignment allocation
(packet req., ref., TFI,
USF,TA, TAI) (polling) (*)
ack.1ph
waiting
assigning
LLC PDU (TLLI, TFI)
LLC PDU (TLLI, TFI)
contention
resolution
Note: For state definition (idle, ack.1ph waiting,....) see Erreur! Source du renvoi introuvable.
(*): On the same PCCCH on which the Packet Channel request was received
Figure 40 one phase access, UL TBF establishment, nominal case, on PCCCH
GPRS telecom presentation
ED 02 released
256_02.DOC
MCD 30/09/1999
3BK 11202 0256 DSZZA 53/122
5.5.2.1.1.1.2 Two phases packet access
A 2 phases access can be initiated by the MS, in the PACKET CHANNEL REQUEST, provided the
not permitted without written authorization from Alcatel
All rights reserved. Passing on and copying of this
document, use and communication of its contents
On receipt of a PACKET RESOURCE REQUEST message, MFS assigns a TFI, radio resources (on
one or more PDCHs, with the associated USF(s)) and TAI, with a PACKET UL ASSIGNMENT
message sent on PAGCH, containing the TLLI for contention resolution.
The MS is requested to send a Packet Control Acknowledgement. Allocation of radio blocks, to the
TBF, will start only on Packet Control Acknowledgement reception.
(PRACH) idle
timing
advance
calculation packet channel
req. + TA
one UL block
packet UL assignment allocation
(packet req. ref.,
starting-time, TA)
idle
(PAGCH) ack.2ph
contention waiting
resolution
transfering
Note: For state definition (idle, ack.2ph waiting,....) see Erreur! Source du renvoi introuvable.
Figure 41 two phase access, UL TBF establishment, nominal case, on PCCCH
(RACH) idle
timing
advance
calculation
channel req. + TA
resource
allocation
immediate assignment
(TFI, USF, TAI, TA) timer
(AGCH) (T_ul_assign
switch on
_ccch)
assigned wait
PDCH
radio blocks
LLC PDU (TLLI, TFI) allocation
activation
Note: For state definition (idle, ack.1ph waiting,....) see Erreur! Source du renvoi introuvable.
Figure 42 one phase access, UL TBF establishment, nominal case, on CCCH
GPRS telecom presentation
ED 02 released
256_02.DOC
MCD 30/09/1999
3BK 11202 0256 DSZZA 56/122
- single block packet access, one block period on a PDCH is needed for 2 phases access.
In this case, the immediate assignment message doesnt contain a TFI, nor an USF, nor a
TAI, it contains only a TBF starting time indicating a block to send a RLC/MAC block (e.g. a
not permitted without written authorization from Alcatel
All rights reserved. Passing on and copying of this
document, use and communication of its contents
Packet Resource request for 2 phases access) and an initial timing advance value.
(RACH) idle
timing
advance
calculation
channel req. + TA
immediate assignment
(TBF starting time, TA)
(AGCH)
transfering
Note: For state definition (idle, ack.2ph waiting,....) see Erreur! Source du renvoi introuvable.
Figure 43 two phase access, UL TBF establishment, nominal case, on CCCH
5.5.2.1.1.3 TBF establishment initiated by the MS during a downlink data block transfer
The purpose of network initiated TBF establishment is to establish a TBF to support the transfer of
LLC PDUs in the direction from the network to the MS (downlink).
The procedure is triggered, in the MFS, when receiving a LLC PDU to a MS not already having any
DL assigned radio resources (paging has been performed previously, by SGSN, but no context is
kept in the MFS).
The allocated radio resource (may be assigned on one or more PDCHs) is assigned to the MS in a
PACKET DL ASSIGNMENT message, sent on PCCCH (or PACCH, if an UL TBF is already
established for this MS).
As timing advance value is not provided in the PACKET DL ASSIGNMENT message, the poll bit is
set to receive from the MS a PACKET CONTROL ACKNOWLEDGEMENT as four access bursts,
(the CONTROL_ACK_TYPE parameter in the SYSTEM INFORMATION indicates acknowledgement
in access bursts).
On PACKET CONTROL ACK, the timing advance is calculated and forwarded to the MS with an
TIMING ADVANCE/POWER CONTROL message.
MS BTS MFS
idle
LLC PDU
resource
allocation
Packet DL assignment
(PPCH) (polling) (TFI, TAI)
Note: For state definition (idle, assigning,....) see Erreur! Source du renvoi introuvable.
Figure 44 DL TBF establishment, nominal case, on PCCCH
In this case, a channel assignment message is sent on CCCH, through GSL interface, to assign the
PACCH slot.
Then a packet DL assignment, with a polling indication, is forwarded via GCH interface to ask for a
PACKET CONTROL ACKNOWLEDGEMENT, in order to calculate the timing adavance.
This second assignment is also necessary since it is impossible to assign a multi-slot TBF on CCCH
channel.
idle
LLC PDU
resource
allocation
transfering
Note: For state definition (idle, assigning,....) see Erreur! Source du renvoi introuvable.
Figure 45 DL TBF establishment, nominal case, on CCCH
5.5.2.1.2.3 TBF establishment initiated by the network during an uplink data block transfer
During UL transfer, the MFS may initiate a DL TBF by sending a PACKET DL ASSIGNMENT
message to the MS on the PACCH.
The different cases of radio resource allocation are shown in the following table:
A mobile class determines the multislot configuration which can be used by the MS.
The MS constraints are the following:
- MS type (whether the MS is able to transmit and receive simultaneously)
- type1: simplex MS
- type2: duplex MS
- maximum number of receive timeslots per TDMA frame.
- maximum number of transmit timeslots per TDMA frame.
- maximum number of transmit and receive timeslots per TDMA frame
- minimum time (in timeslots) between the different windows (receive, transmit,
measurement windows)
With dynamic allocation (USF), an UL transfer requires symetric capabilities (the MS has to listen all
the allocated PDCHs for USF reading).
That means that simplex MS may only be granted a configuration of class 1 (1 DL TS + 1 UL TS) or
class 5 ( 2 DL TS + 2 UL TS) (see the figure below)
0 1 2 3 4 5 6 7
Rx Rx Mx
DL
Ttb Tra
Tx Tx
UL
0 1 2 3 4 5 6 7
- Rx: DL slot
- Tx: UL slot
- Ttb: minimum number of slots between the end of the last previous transmit or receive slot and
the first next transmit
- Tra: minimum number of slots between the previous transmit or receive slot and the next receive
slot when measurement (Mx) is to be performed between
(These values are defined in GSM 05.02, annex B, for each multi-slot class)
(for more details, see also [14])
Figure 46 class 5, symetric configuration
The allocation strategy consists to maximise the usage of the allocated PDCHs and, if necessary, to
require additional PDCH(s) to the BSC.
The maximum number of TBFs per PDCH is limited by the following parameters:
- 16 TAI values are available per PDCH
- 6 USF values are available for UL traffic on GPRS master PDCH
- 7 USF values are available for UL traffic on GPRS non-master PDCH
- 32 TBF per cell
O&M parameters define thresholds used to invoke allocation of new PDCH:
- An O&M constant defines the max. number of TBFs per PDCH (N_TBF_PER_PDCH)
- An O&M constant defines the max. number of TBFs per MPDCH (N_TBF_PER_MASTER)
When a cell becomes unavailable for GPRS traffic (e.g. following either an O&M command or a Gb
failure), PDCH release messages are sent to all the MSs of the cell which are involved in a data
transfer, before releasing the PDCH.
On reception, the MS shall immediately stop transmitting.
5.5.2.6 QoS
The radio QoS is the QoS granted on the radio interface to transfer LLC PDUs.
The radio QoS is defined by the following parameters:
- throughput
- service precedence
- RLC reliability mode
- BSS transfer delay
5.5.2.6.2 Throughput
In B6.2, the throughput information is only taken into account, UL, for NS load-sharing.
BSS transfer delay information, is given, DL, through PDU life time, provided by DL BSSGP PDUs.
The transfer of RLC data blocks in the RLC acknowledged mode uses retransmissions of RLC data
blocks.
The transmitting side numbers the RLC data blocks via the Block Sequence Number (BSN) for
retransmission and reassembly.
The receiving side sends PACKET UPLINK ACK/NACK or PACKET DOWNLINK ACK/NACK
messages in order to request retransmission of RLC data blocks.
The transfer of RLC data blocks in the RLC unacknowledged mode does not include any
retransmissions.
The BSN is used to number the blocks for reassembly.
The receiving side sends PACKET ACK/NACK messages in order to convey the necessary other
control signalling messages while the fields for requesting retransmission are not used.
Each received LLC PDU shall be segmented into RLC data blocks.
If the contents of an LLC PDU do not fill an integer number of RLC data blocks, the beginning of the
next LLC PDU shall be placed within the final RLC data block of the first LLC PDU with no padding
between the end of the first LLC PDU and the beginning of the next.
If the final LLC PDU in the TBF does not fill an integer number of RLC data blocks, filler octets shall
be used to fill the remainder of the RLC data block.
RLC data blocks shall be collected at the receiver until all RLC data blocks comprising an LLC PDU
have been received.
During RLC acknowledged mode operation, received LLC PDUs shall be delivered to the higher
layer in the order in which they were originally transmitted.
During RLC unacknowledged mode operation, received LLC PDUs shall be delivered to the higher
layer in the order they are received.
The MFS initiates the release of a DL TBF by sending an RLC data block with the Final Bit Indicator
(FBI) set.
The MS can initiate a DL TBF release by setting the TBF_release_bit in the Packet DL ACK/NACK
message and in all subsequent Packet DL ACK/NACK message, until the TBF is released.
not permitted without written authorization from Alcatel
All rights reserved. Passing on and copying of this
document, use and communication of its contents
Each PDCH is a shared medium between multiple MSs and the network.
It consists of asymmetric and independent uplink an downlink channels.
5.5.4.1.1 Downlink
The DL, from the MFS to multiple MSs, does not require contention arbitration.
Different logical channels share the same PDCH:
- PBCCH
It is mapped on 1 to 4 blocks (B0, B6, B3, B9).
The number of blocks (BS_PBCCH_BLKS) is broadcast on PBCCH in B0, which always exists, in
case of GPRS master channel.
The MS shall attempt to decode every DL RLC/MAC block on all assigned PDCHs.
Whenever the MS receives an RLC/MAC block containing an RLC control block, the MS shall
attempt to interpret the message therein. If the message addresses the MS (the identity of the MS is
a specific field of the control message according to its type, e.g UL TFI in Packet UL ACK/NACK) ,
the MS shall act on the message.
5.5.4.1.2 Uplink
The UL is shared among multiple MSs and requires contention control procedures.
Multiplexing is handled by dynamic allocation medium access mode, in GPRS step1.
The medium access mode the MS is to use is signalled in the Packet UL Assignment.
The allocation mechanism is based on a token (USF: Uplink Status Flag) distributed by the MFS,
allowing the sharing of the UL resource between different MSs which are involved in UL packet
transfer, on the same PDCH.
All these MSs having received one USF value in the Packet UL Assignment, listen to the USF sent,
by the MFS, in all DL blocks. When the decoded USF, in DL block Bn, matches the USF allocated to
the MS, by the MFS, the MS gets the right to transmit one RLC/MAC block in UL block Bn+1.
A MS which wants to initiate a packet access procedure, has to send a Packet Channel Request, on
PRACH.
With this aim, the MS has to listen DL PDCH to denote a specific USF value (FREE) denoting
PRACH.
A FREE USF value in a DL block Bn, means that UL block Bn+1 is a PRACH.
Another value (no emission) is used to authorize one MS, without USF, to transfer in the UL direction
(e.g. MS involved in a DL packet transfer)
A MS involved in a DL packet transfer shall attempt to decode every DL RLC/MAC block on the
assigned PDCH, carrying the PACCH.
Whenever a MS receives a RLC data block addressed to itself and with a valid RRBP field
(scheduling an UL block) in the MAC data block header, the MS shall transmit a Packet DL
ACK/NACK. (except at the end of a DL transfer, in unacknowledged mode!!)
Whenever a MS receives a RLC control block addressed to itself and with a valid RRBP field in the
MAC data block header, the MS shall transmit a Packet Control ACK.
The RRBP field contained in DL block Bn specifies a single UL block in which the MS shall transmit.
The UL block can be either Bn+2, Bn+3, Bn+4 or Bn+5.
Consistency between USF and RRBP indications shall be ensured.
PDTCHj
USFj
PACCHj
PRACH USF=FREE
Furthermore, this DL block is addressed to MSk and the RRBP indication is set (+3), which
means that MSk has to send a Packet DL ACK/NACK in UL Bn+4 (Bn+1 + 3)
- DL Bn+2 has its USF equal to FREE. It means that UL Bn+3 is a PRACH.
- DL Bn+3 has its USF equal to no emission. It means that UL Bn+4 has already been
scheduled by the RRBP mechanism.
downlink uplink
block number USF RRBP
Bn USFi false
Bn+1 USFj +3 MSi
Bn+2 FREE false MSj
Bn+3 no emission false PRACH
Bn+4 USFi false PACCHk
Bn+5 USFj false MSi
Bn+6 MSj
Note: During the establishment of an UL TBF, on CCCH, with 2 phase access, another mechanism
is used (see Figure 43). One block (Bx) is assigned, thanks to the TBF starting time parameter of
the immediate assignment message.
DL Bx-1 block shall have its USF value equal to no emission.
This mechanism is used by the MFS to request a response from the MS.
It is based on the RRBP mechanism which allocates a block for this response.
It is used for different purposes:
- to require a Packet Control ACK either to measure initial timing advance or to acknowledge
a control message.
Particularly, the MS will be requested to send a Packet Control Acknowledgement upon
receipt of any Packet Assignment, in order to allocate radio blocks, to this TBF, only when
the acknowledgement is received, to optimize the radio resources usage.
- to require blocks acknowledgement in DL transfer, in acknowledged mode
- to allocate an UL PACCH block, during DL transfer in unacknowledged mode.
The different cases are summarized in the following table:
The Gb interface connects the BSS and the SGSN, allowing the exchange of signalling information
All rights reserved. Passing on and copying of this
document, use and communication of its contents
MFS SGSN
Gb
BSSGP interface BSSGP
NS (NSC) NS (NSC)
NS (SNS) NS (SNS)
FR
L1 network L1
Figure 48 Gb interface
The Gb interface link layer is based on Frame Relay (FR). Frame relay virtual circuits are
established between SGSN and BSS. LLC PDUs from many users are multiplexed on these virtual
circuits.
The virtual circuits may be multi-hop and traverse a network of frame relay switching nodes.
Frame relay core functions are implemented (DL-CORE protocol defined in Q922, Annex A) enabling
the sending/reception of frame relay unacknowledged frames.
see [4]
(see [5])
The primary function of BSSGP is to convey LLC PDUs and GPRS MM signalling.
In the BSS, it acts as an interface between LLC frames and RLC/MAC blocks.
In the SGSN, it forms an interface between RLC/MAC-derived information and LLC frames.
The main functions for the BSSGP protocol are to:
- provide a connectionless link between the SGSN and the MFS
- transfer data unconfirmed between the SGSN and the MFS
- provide tools for DL data flow control between the SGSN and the MFS
- handle paging requests from the SGSN to the MFS
- give support for flushing of old messages in the MFS (e. g. when an MS changes BSS)
6.2 Addressing
A BC is a nx64 kbit/s channel on a 2048 kbit/s link and supports a set of PVCs.
In order to provide end-to-end communication between the MFS and the SGSN irrespective of the
exact configuration of the Gb interface, the concept of NS-VC is used.
The peer-to-peer communication between remote NSC user entities is performed over NS-VCs.
NS-VCs are end-to-end virtual connections between the MFS and the SGSN.
Each NS-VC is identified by means of a NSVCI having end-to-end significance across the Gb
interface.
NS-VCs are statically configured by O&M.
In GPRS step1, there is a one to one mapping between one NS-VC and one FR PVC.
In step1, only one NS-VC (PVC) per BC.
In Alcatel implementation, a NSE is defined as the connection of one BSS to one GPU.
(in step1: one NSE corresponds to one BSS).
The BVCI together with the NSEI uniquely identifies a BVC within a SGSN.
The BVCI and NSEI are used on the NS-SAP for layer-to-layer communication.
cells
All rights reserved. Passing on and copying of this
document, use and communication of its contents
BVC BSSGP
NSE
NSE
NSC
NS-VC
PVC
SNS
Bearer channel
NSEI=1
Load sharing Bearer
Bearer Channel=3
Channel=1
Cell id2 BVCI=2 BVCI=2
NSVCI=3
NSVCI=1
DLCI=16
DLCI=34
Frame
Cell id3 BVCI=4 Relay BVCI=4
network NSVCI=1
DLCI=98
Bearer
Cell id9 BVCI=5 Channel=2 BVCI=5
NSVCI=3
DLCI=17
6.3 NS functionalities
(see [4])
The load sharing function distributes the NS-PDU traffic among the unblocked NS-VCs of the same
NSE.
The NS-VC selection is based on the LSP value.
At one side of the Gb interface, all BSSGP UNITDATA PDUs related to an MS shall be passed with
the same LSP, to the underlying network service.
The LSPs used at the MFS and SGSN for the same MS may be set to different values.
Thus, the load sharing function guarantees that for each BVC, the order of all NS-PDUs marked with
the same LSP value is preserved.
At the data transfer establishment (see Figure 51), the BSSGP layer sends a NS-UNITDATA-req
primitive to the NS layer with the following information:
- NSEI
- BVCI
- LSP (Link Selector Parameter)
- bit rate
A set of NS-VCs is associated to each NSEI.
Among these NS-VCs, one is chosen which is able to provide the requested bit rate.
The following relationship is established: NSEI, BVCI, LSP --> NS-VC.
All the following NS-UNITDATA-req with the same NSEI, BVCI,LSP identification will use the same
NS-VC.
The previous relationship is withdrawn, at the end of the data transfer, on TRN-STOP-req primitive
reception, from the upper layer (see Figure 52).
access to
routing table
(BVCIb, LSPc)
Y
(BVCIb, Does the identif ication
LSPc)? (NSEIa, BVCIb, LSPc)
exists in the routing table?
N
access to the a list of NS-VCs
NSEIa is associated to NSEIa
NS-VCs list
according t o the
NS-VC choice
request ed bit rat e
registration in relationship
the routing NSEIa, BVCIb, LSPc --> NS-VC
table is registered in the routing table
NS PDU is routed on the NS-VC
routing given by the routing table
Figure 51 NS routing (routing relationship creation)
GPRS telecom presentation
ED 02 released
256_02.DOC
MCD 30/09/1999
3BK 11202 0256 DSZZA 74/122
Procedure load_sharing 2(2)
end of triggered on TRN-STOP-req
transf er reception
not permitted without written authorization from Alcatel
access to
routing table
(BVCIy, LSPz)
suppression in relationship
the routing NSEIx, BVCIy, LSPz --> NS-VC
table is withdrawn from the routing table
Figure 52 NS routing (roting relationship deletion)
GPRS telecom presentation
ED 02 released
256_02.DOC
MCD 30/09/1999
3BK 11202 0256 DSZZA 75/122
not permitted without written authorization from Alcatel
When a NS-VC becomes locally unavailable either at the MFS or at the SGSN, the remote NS entity
shall be informed by means of a blocking procedure.
A NS-VC may be blocked, because of:
- O&M command (administrative state = locked)
- equipment failure (operational state = disabled)
- test procedure failure (operational state = disabled)
When a NS-VC becomes available again, the NS entity which initiated the blocking procedure (or the
reset procedure) informs the remote NS entity by means of an unblocking procedure.
NS NS
entity entity
NS-BLOCK
NS-BLOCK-ACK
Note: These PDUs are sent on any enabled NS-VC belonging to the same NSE
Figure 53 NS-VC Blocking procedure
NS NS
entity entity
NS-UNBLOCK
NS-UNBLOCK-ACK
Note: These PDUs are sent on any enabled NS-VC belonging to the same NSE
Figure 54 NS-VC Unblocking procedure
The reset procedure is used when a new NS-VC is set-up, after processor restart, after failure
not permitted without written authorization from Alcatel
All rights reserved. Passing on and copying of this
document, use and communication of its contents
NS NS
entity entity
NS-RESET
NS-RESET-ACK
This procedure is used to check that end-to-end communication exists between peer NS entities, on
a given NS-VC.
This procedure is initialised upon successful completion of the reset procedure and shall be then
periodically repeated.
When the procedure is successful, the operational state is enabled otherwise it is disabled and the
NS-VC becomes blocked.
NS NS
entity entity
NS-ALIVE
NS-ALIVE-ACK
(see [5])
MFS SGSN
LLC GMM NM
RL GMM
NM BSSGP
RLC
MAC NS NS
MFS SGSN
RL SAP BSSGP SAP
DL-UNITDATA
UL-UNITDATA
DL UNITDATA PDUs contain PDU life-time information element which is used by the
RRM/RLC/MAC function, for radio resource scheduling on the MS-network interface.
LSP (TLLI), BVCI, NSEI and QoS profile information (requested throughput) is used for load sharing
at NS layer level.
MFS SGSN
GMM SAP GMM SAP
PAGING-CS
PAGING-PS
RADIO-STATUS
acknowledgement
6.4.2.1 Paging
6.4.2.1.1 CS paging
When instructed by the MSC/VLR to initiate circuit-switched transmission between the MSC and a
MS, the SGSN shall send a PAGING CS PDU to the MFS. (network operation mode I)
6.4.2.1.2 PS paging
When wishing to initiate packet-switched transmission between an SGSN and MS, an SGSN shall
send a Paging PS PDU to the MFS.
MFS SGSN
not permitted without written authorization from Alcatel
All rights reserved. Passing on and copying of this
NM SAP NM SAP
document, use and communication of its contents
FLUSH-LL
LLC-DISCARDED
BVC-FLOW-CONTROL
MS-FLOW-CONTROL
BVC-BLOCK
BVC-UNBLOCK
BVC-RESET
STATUS
acknowledgement
The SGSN sends a FLUSH-LL to MFS to ensure that LLC-PDUs queued at a cell for an MS are
deleted.
The parameters are : TLLI and BVCI.
This PDU is acknowledged.
The MFS sends a LLC-DISCARDED PDU to SGSN, when a local LLC-PDU deletion has been
not permitted without written authorization from Alcatel
All rights reserved. Passing on and copying of this
document, use and communication of its contents
Only downlink flow control is performed (from the MFS to the SGSN)
This flow control applies on the 2 following entities:
- the cell (i.e. one BVCI)
by means of FLOW-CONTROL-BVC PDU which has the following parameters:
- tag (reference to be returned in the acknowledgement)
- BVC throughput indication
- BVC measurement (not used in B6.2)
describes average queuing delay for a BVC
A FLOW-CONTROL-BVC-ACK, containing the field tag acknowledges the previous PDU.
The MFS uses flow control to adjust the flow of BSSGP UNITDATA PDU to its buffers.
This flow control is triggered by RRM/RLC/MAC layer (see 8.2.2.2).
BSSGP UNITDATA PDUs queued within the MFS that are not transferred across the radio interface
before the PDU life time expires shall be deleted and the SGSN shall be notified by a LLC-
DISCARDED PDU.
The BVC blocking and unblocking procedures are initiated by the MFS to remove from use, or bring
into use, a BVC
The MFS may block a BVC because of:
- O&M blocking for intervention purpose (O&M request)
- equipment failure at the BSS (RRM request)
- cell equipment failure at the BSS (RRM request)
To block a BVC, the MFS shall send a BVC-BLOCK PDU with BVCI and cause as parameters.
This PDU has to be acknowledged (BVC-BLOCK-ACK, with BVCI as parameter).
To unblock a BVC, the MFS sends a BVC-UNBLOCK PDU with BVCI indication.
This PDU has to be acknowledged with BVCI indication.
- processor recovery
- underlying network recovery
- ....
After performing a BVC-RESET procedure, the affected BVC is assumed to be in the unblocked
state in the SGSN. So the MFS has to initiate a block procedure if the affected BVC is marked
blocked in the MFS.
The BVC-RESET PDU has the following parameters:
- BVCI
- cause
This PDU has to be acknowledged by a BVC-RESET-ACK PDU with the BVCI indication.
MFS SGSN
RESET unblocked
unblocked
O&M O&M
blocking BVC-UNBLOCK
unblocking BVC-BLOCK or
or or
failure RESET
recovery
RESET blocked
blocked
(1)
6.4.3.5 Status
When an exception condition occurs (e.g. BVCI unknown, BVCI blocked, ...) either in the MFS or the
SGSN, a STATUS PDU is sent to the peer entity.
This PDU has the following parameters:
-cause
- PDU in error
This PDU is not acknowledged.
Telecom layer - O&M interface is of type manager-agent, where The O&M is the manager and the
telecom layer the agent.
This interface can be modeled through entity classes (by analogy with object classes).
These classes can be instanciated.
O&M
operations
notifications
attributes
Telecom
layer
entity
Note: In this paragraph, distinction between RRM, RLC and MAC is not taken into account.
- L2-GCH:
- GCH class (only one instance to model the layer)
- BSCGP:
- GSL class
A GSL is one 64 kbit/s LAPD link, between BSC and MFS.
- RRM:
- CELL class
GSM cell
- Gic_Group class
A Gic_Group is a set of AterC circuits (64 Kbit/s circuits), which can be used for GPRS traffic
and which are carried by the same PCM
- BSS class
- BSSGP:
- BVC-PTP class
One BVC-PTP represents the GPRS traffic of one cell on Gb interface
It is managed, by O&M, through the cell entity.
- BVC-SIG class
One BVC-SIG represents, on Gb interface, signalling related to one NSE (i.e. a couple GPU-
BSS, in B6.2, one BSS is handled by only one GPU).
It is managed, by O&M, through the BSS entity.
- SNS:
- PVC class
One PVC is a frame relay Permanent Virtual Channel mapped on a bearer channel, on Gb
interface.
- BC class
One BC is a Bearer Channel on the Gb interface.
GPU
BSS BVC_ BC
SIG
GSL Gic_
Group cell BVC_ NSVC PVC
PTP
1 to 1 association
1 to n association
BSCGP
LM-GSL-create-req
LM-GSL-delete-req
O&M
NTM-BSC-State-ind RRM
GSL
dl-establich-req
L2GSL dl-release-req NTM-BSC-Reset-ind/req
dl-release-ind
dl-establish-ind
acknowledgement
NTM-BSC-State-ind
LM-BSS-create-req NTM-BSC-State-req
BSCGP
LM-BSS-delete-req
LM-BSS-SET-req RRM
O&M NTM-BSC-Reset-ind/req
LM-BSS-State-change-ind
BSS NM-BVC-SIG-CREATE-req
NM-BVC-SIG-DELETE-req
NM-BVC-SIG-START-req BSSGP
NM-BVC-SIG-STOP-req
BVC-SIG
NM-BVC-SIG-T-STATUS-ind
LM-Gic-Group-create-req
LM-Gic-Group-delete-req
NTM-GICGROUP-State-req
LM-Gic-Group-GET-req
O&M
BSCGP NTM-GICGROUP-state-ind
RRM LM-Gic-Group-state-change-ind
NTM-BSC-reset-ind GIC
Group
RRM BSSGP
LM-CELL-create-req NM-BVC-PTP-CREATE-req
LM-CELL-delete-req NM-BVC-PTP-DELETE-req
O&M
LM-CELL-state-change NM-BVC-PTP-START-req
cell NM-BVC-PTP-STOP-req
NTM-CELL start/stop-req
NTM-CELL-Detach-req
NTM-CELL-Detach-ind
indication
disabled dependency locked/unlocked BVC-PTP
unavailability
disabled off-line + dependency locked/unlocked
disabled failed unlocked MFS internal failure
enabled 0 locked/unlocked
RRM SGSN
BSSGP (via NS)
BVC-BLOCK
BVC-UNBLOCK
NM-BVC-PTP-CREATE-req
NM-BVC-PTP-DELETE-req
BVC-RESET
NM-BVC-PTP-START-req
BVC-PTP
NM-BVC-PTP-STOP-req
Cell
NM-BVC-PTP-T-STATUS-ind
BSSGP NSC
NM-BVC-SIG-CREATE-req
NM-BVC-SIG-DELETE-req TRN-CONNECT-req
TRN-DECONNECT-req
RRM
NM-BVC-SIG-START-req TRN-NSE-Start-req
NM-BVC-SIG-STOP-req BVC-SIG
TRN-NSE-Stop-req
NM-BVC-SIG-T-STATUS-ind TRN-NSE-Capacity-ind
BVC-RESET SGSN
(via NS)
LM-NSVC-create-req SGSN
LM-NSVC-delete-req NSC (via SNS)
LM-NSVC-SET-req
(administrative state)
O&M
NS-ALIVE
NS-BLOCK
NS-UNBLOCK
LM-NSVC-state- NS-RESET
change-ind NSVC
LM-NSVC-ERR-
CONF-ind
SNS
TRN-FAILURE-ind
TRN-AVAILABLE-ind
SNS
LM-PVC-create-req Network
O&M LM-PVC-delete-req (FR)
LM-PVC-state-
change-ind
STATUS
PVC Availability Bit
New Bit
NSC
TRN-FAILURE-ind
TRN-AVAILABLE-ind
7.2.9 BC entity
All rights reserved. Passing on and copying of this
document, use and communication of its contents
SNS
LM-BC-create-req Network
O&M LM-BC-delete-req (FR)
BC
STATUS ENQUIRY
LM-BC-state-change-ind
Performance counters are related to a monitored entity class. (each monitored entity instance
having its counters)
For performance management purposes, 2 counter types are defined (see ITU-X721):
- counter
A counter is regarded as associated with some event. The current value is incremented by 1 when
this event occurs.
A counter shall be reset at the end of the granularity period.
A threshold may be associated.
counter
value qualityOfService
alarm report
threshold
c
time
granularity
period
gauge
value
qualityOfService
alarm report
threshold
time
granularity
period
Note: Only these raw counters are implemented at telecom layer level, ( CPU run-time has not to be
wasted at this level, and more complex counters could be operator dependant), which means, for
example, that:
- average counters should be implemented with 2 counters at protocol level:
- for percentage, for example: one counter for specific events and another one for all
the events. The percentage counter elaboration should be O&M responsability (or
OMC-R?)
- time during which an entity is available or unavailable should be calculated by O&M, from
state change notifications.
Counters are automatically created when the monitored entity instance is created.
This monitored instance is created either by O&M or by the telecom layer. In the last case O&M has
to be notified, to take into account the created entity and its associated counters.
O&M is responsible for periodical counter retrieval, according to the granularity period (GET
operation or a more sophisticated operation allowing, for example, to freeze all the counter values at
the very same instant, to have coherent results and then to read them before the next granularity
period occurence).
After this retrieval, counters are reset to zero (gauges are not reset)
In telecom layers, after each counter incrementation, the value of the counter is compared with an
associated threshold (if any).
Threshold values are modifiable, on a counter/gauge class basis.
If the counter value reaches the threshold, a qualityofService alarm report is forwarded to O&M.
Note: the following numbers are related to Figure 74 and Figure 75.
3. A PACKET PAGING REQUEST (RLC/MAC control message) is sent to MSs on PCH or PPCH.
4. In order to answer to SGSN (with a LLC PDU), the MS shall establish an UL TBF, using a
PACKET CHANNEL REQUEST; with cause value of page response, on (P)RACH
7. Upon reception of the LLC PDU (implicit paging response), the SGSN stops the paging response
timer and
8. starts the downlink transfer towards the MSs cell (BVCI), by sending a BSSGP DL-UNITDATA
which will trigger, in the MFS, a DL TBF establishment.
PDP (1)
stand-by
Paging PS (2)
Packet paging request (3)
(PPCH)
super-
vision
(PRACH) Packet channel request (4)
(PAGCH) timer
Packet uplink assignment (5) UL TBF
Ready
(8)
DL-UNITDATA
stand-by
PDP (1)
Paging PS (2)
PS Paging
Paging command
(PCH) (3)
timer
immediate assignment (5)
(AGCH)
UL TBF
LLC-PDU (6)
(7)
ready
(8)
DL-UNITDATA
8.2.1 Definitions
N layer N-PDU
N-1 PDU
PDU: Protocol Data Unit
SDU: Service Data Unit
PCI: Protocol Control Information
Figure 76 Data unit mapping between adjacent layers (without segmentation)
N layer N-PDU
A packet data downlink transfer has to be preceded by a paging procedure as shown on the following
figure.
MS MFS SGSN
STAND-BY
PDP PDU
PAGING PS
LLC PDU
READY
DL packet data transfer procedure
This paragraph indicates the mapping between data units in the different layers for a downlink
not permitted without written authorization from Alcatel
All rights reserved. Passing on and copying of this
document, use and communication of its contents
transfer.
L3-PDU
L3-PDU
LLC-PDU
LLC LLC
RLC RLC-PDU relay
RLC BSSGP-PDU
BSSGP
MAC BSSGP
radio GCH MAC
GSM-RF block relay PDU NS NS-PDU NS
L2-GCH L2-GCH
GSM-RF FR PDU
L1-GCH L1-GCH L1bis L1bis
GCH
frame
MS Um BTS MFS SGSN
Abis/Ater Gb
L3 PDU
address control information field FCS
field field
- address field
- PD: protocol discriminator (LLC protocol or different protocol)
- C/R: (command/response)
- SAPI (GPRS MM, QoS priority level 1, level 2, level 3, level 4, SMS)
SAPI identifies a point at which LLC services are provided by a LLE (Logical Link
Entity) to a layer-3 entity.
- control field
4 types of control field formats are specified:
- confirmed information transfer (I format)
- supervisory functions (S format)
- unconfirmed information transfer (UI format)
- control functions (U format)
LLC PDU
header information field
- BSSGP header
- PDU type (DL-UNITDATA)
- TLLI (current)
- QoS profile
- bit rate ( 0 to 6 553 500 bit/s)
The 0 value means best effort
- precedence ( high/normal/low priority)
- A-bit (acknowledged or unacknowledged RLC mode)
- T-bit (LLC-PDU contains signalling (e.g. related to GMM) or data)
- PDU lifetime (PDU life time inside the BSS)
- MS radio access capability
- [priority] (priority of the PDU)
- [DRX parameters] (SPLIT_PG_CYCLE code, non-DRX timer)
- [IMSI]
- [TLLI (old)]
8.2.2.1.3 NS PDU
BSSGP PDU
PDU type BVCI information field
(NS-
UNITDATA)
8.2.2.1.4 FR PDU
NS PDU
synchroni header information field FCS
sation
flag
- synchronisation flag
All frames shall start and end with a flag sequence equal to 01111110.
The closing flag may also serve as the opening flag of the next frame.
- header
- DLCI (Data Link Control Identifier)
- FECN (Forwarded Explicit Congestion Notification)
may be set by a congested network to notify the user that congestion avoidance
procedures should be initiated where applicable for traffic in the direction of
the frame carrying the FECN indication.
- BECN (Backward Explicit Congestion Notification)
may be set by a congested network to notify the user that congestion avoidance
procedures should be initiated where applicable for traffic in the opposite
direction of the frame carrying the FECN indication.
- MAC header
- payload type (RLC data block)
- RRBP (relative Reserved Block Period)
- S/P (Supplementary/polling) (RRBP valid or not)
- USF (Uplink State Flag)
- RLC header
- TFI (Temporary Flow Identifier)
identifies the TBF (Temporary Block Flow) to which the RLC data block belongs
- BSN (Block Sequence Number)
sequence number of each RLC data block within the TBF
- FBI (Final Block Indicator)
indicates that the DL RLC data block is the last RLC data block of the DL TBF.
- PR (Power Reduction) indicates the power level reduction of the next RLC blocks in
the PDCH, relative to the BCCH level.
- RLC data
Each LLC PDU shall be segmented into RLC data blocks.
A RLC data block may contain octets from one or more LLC PDUs.
The size of RLC data will depend on the coding scheme which will be applied on the
radio interface:
- CS1: 20 octets
- CS2: 30 octets
- CS3: 36 octets (not in step1)
- CS4: 50 octets (not in step1)
- spare bits
The size of this field depends on the coding scheme:
- CS1: 0
- CS2: 7 bits
- CS3: 3 bits (not in step1)
- CS4: 7 bits (not in step1)
RLC/MAC PDU
header information field
- GCH header
- GCH PDU type (traffic)
- DL block number
- coding scheme
- uplink burst (normal burst, access burst, no burst)
- BS_TXPWR (BTS emission relative power)
- CRC (Cyclic Redundancy Check)
- RLC/MAC PDU
- CS1: 184 bits
- CS2: 271 bits
GCH PDU
synchroni information field
sation
pattern
RLC/MAC PDU
information field BCS
4 radio bursts
- cell (BVC)
- and MS
For these 2 entities, bit rate information and average queuing delay , per BVC, are sent to the SGSN,
for flow control purpose.
LLC-PDU
FLOW-CONTROL-MS FLOW-CONTROL-MS MS
MS flow
control
Downlink flow control (FLOW-CONTROL-MS/BVC towards SGSN) is initiated at RRM layer level on
the following information (see Figure 81):
- at cell creation time the cell throughput is forwarded to the SGSN
- On each received DL LLC-PDU, flow control mechanisms are performed on a MS basis
then on a cell (BVC) basis.
RLC layer can notify a congestion on a MS basis (when a TBF transmission queue reaches an upper
limit) or for the whole DSP (on memory overload).
The first notification will stop MS LLC-PDU at RRM layer level and the second one will stop LLC-
PDU for the cells reached by this DSP.
Of course as these notifications stop LLC-PDUs, they will have consequences on RRM flow control
mechanisms.
MS LLC-PDU
All rights reserved. Passing on and copying of this
document, use and communication of its contents
flow control
FLOW-CONTROL-MS
BVC
available flow control FLOW-CONTROL-BVC
PDCH
capacity
flow
LLC-PDU control
ind.
flow
control
ind. threshold DSP
RLC emission
queue
L3-PDU
L3-PDU
LLC-PDU
LLC LLC
RLC RLC-PDU relay
RLC BSSGP-PDU
BSSGP
MAC BSSGP
radio GCH MAC
GSM-RF block relay PDU NS NS-PDU NS
L2-GCH L2-GCH
GSM-RF FR PDU
L1-GCH L1-GCH L1bis L1bis
GCH
frame
MS Um BTS MFS SGSN
Abis/Ater Gb
L3 PDU
address control information field FCS
field field
- address field
- PD: protocol discriminator (LLC protocol or different protocol)
- C/R: (command/response)
- SAPI (GPRS MM, QoS priority level 1, level 2, level 3, level 4, SMS)
SAPI identifies a point at which LLC services are provided by a LLE (Logical Link
Entity) to a layer-3 entity.
- control field
4 types of control field formats are specified:
- confirmed information transfer (I format)
- supervisory functions (S format)
- unconfirmed information transfer (UI format)
- control functions (U format)
- MAC header
- payload type (RLC data block)
- countdown value
allows the MFS to calculate the number of RLC data blocks remaining for the
current UL TBF
- SI (Stall Indicator)
indicates whether the transmit window can (or cannot) advance
- R (Retry)
indicates whether the MS transmitted the Packet Channel request one time or more
during its most recent channel access
- RLC header
- TFI (Temporary Flow Identifier)
identies the TBF (Temporary Block Flow) to which the RLC data block belongs
- BSN (Block Sequence Number)
sequence number of each RLC data block within the TBF
- TI (TLLI Indicator)
indicates the presence of an optional TLLI field within the RRLC/MAC PDU
- RLC data
Each RLC data block may contain octets from one or more LLC PDUs.
The size of RLC data will depend on the coding scheme which will be applied on the
radio interface:
- CS1: 20 octets
- CS2: 30 octets
- CS3: 36 octets (not in step1)
- CS4: 50 octets (not in step1)
- spare bits
The size of this field depends on the coding scheme:
- CS1: 0
- CS2: 7 bits
- CS3: 3 bits (not in step1)
- CS4: 7 bits (not in step1)
RLC/MAC PDU
information field BCS
4 radio bursts
GCH PDU
synchroni information field
sation
pattern
RLC/MAC PDU
header information field
- GCH header
- GCH PDU type (traffic)
- UL block number
- block number error (to correct clock drifts between radio and GCH interfaces)
- coding scheme (CS1/CS2)
- RXQUAL (reception quality measured, by the BTS, on the radio interface)
- RXLEV (reception level measured, by the BTS, on the radio interface)
- CRC (Cyclic Redundancy Check)
- RLC/MAC PDU
- CS1: 184 bits
- CS2: 271 bits
LLC PDU
header information field
BSSGP PDU
PDU type BVCI information field
(NS-
UNITDATA)
8.2.3.1.8 FR PDU
NS PDU
synchroni header information field FCS
sation
flag
The purpose of this function is to adapt UL flow, according to Gb throughput and Gb congestion
not permitted without written authorization from Alcatel
All rights reserved. Passing on and copying of this
document, use and communication of its contents
state.
In case of NSE capacity bandwidth reduction the following procedure is activated, if enabled by an
O&M parameter:
- The maximum number of available GCHs within the BSS is reduced from the percentage of
loss of bandwidth at Gb side.
- Ongoing traffic is not impacted (i.e. the number of active PDCHs is not reduced even if it is
greater than the number of GCHs allowed due to the NSE capacity bandwith reduction)
In case of NSE congestion, the following procedure is undertaken, if enabled by an O&M parameter:
- RRM stops the UL data traffic on one PDCH in each cell of the BSS where there is on-
going data traffic (by means of PDCH Release messages)
- The MFS does not allocate any new PDCH in the BSS
- This procedure is restarted periodically if the Gb congestion is still present.
When a cell reselection is autonomously determined by the MS (NC0), the MS may continue its
operation in the old serving cell, while acquiring certain system information for the target cell.
The operation in the old cell shall be aborted when one of the following conditions are met:
- the MS station starts to receive information on PBCCH, in the target cell
- the MS has received the SI13 message and there is no PBCCH present in the target cell
- the criterions for camping on the old cell are no longer fulfilled.
While the operation is maintained in the old cell, the MS may suspend its TBF in order to receive
necessary information on BCCH in the target cell.
It is performed without notification to the network.
Under no circumstances, operations in the old cell shall be continued more than 5s after a cell
reselection has been determined
When a new cell has been selected, the MS shall perform a complete acquisition of (P)BCCH
messages.
If there is a MPDCH, the MS shall not perform packet access in the selected cell until it has acquired
the PSI1 message, a consistent set of PSI2 messages and made at least one attempt to receive the
complete set of PSI messages.
If there is no MPDCH, the MS shall not perform packet access in the selected cell until it has
acquired the SI3, SI13 and if present the SI1 messages and made at least one attempt to receive
other SI messages that may be scheduled within one TC cycle on BCCH.
(2): When the operation in the old cell is aborted (i.e. the UL TBF is aborted), the MFS receives
no more messages in the UL blocks scheduled for this MS by the USF mechanism.
N3101 is incremented in the MFS for each radio block allocated to that MS for which no data
is received. When N3101 reaches N3101 max (default value = 16), radio resource
scheduling is stopped and T3169 is activated (USF and TFI values are frozen until T3169
expiry).
(3): When (P)SI information has been acquired, an UL TBF is established in the new cell.
(4): The SGSN is informed of the cell change, when receiving a LLC PDU, in which the MFS
adds the cell identifier.
MS MFS SGSN
(P)SI
(1) (2)
acquisition
(2): When the operation in the old cell is aborted (i.e. the DL TBF is aborted), the MFS receives
no more acknowledgement from the MS, so an abnormal release is undertaken.
(3): When (P)SI information has been acquired, an UL TBF is established in the new cell. in
order to send a cell update to the SGSN.
(4): When receiving the new cell location, the SGSN sends a FLUSH to discard DL LLC PDUs
buffered for the MS in the old cell.
(5): The SGSN resumes the DL transfer by sending a DL LLC PDU which will trigger a DL TBF
establishment in the new cell.
MS MFS SGSN
(P)SI
(1) (2)
acquisition
FLUSH ACK
(5)
DL LLC PDU (cell B)
DL TBF establishment (cell B)
In the different telecom layers, functions have been split into 5 functional blocks:
All rights reserved. Passing on and copying of this
document, use and communication of its contents
- PAGing (PAG)
It is in charge of addressing paging requests (circuit switched or packet switched) received
from SGSN.
- TRaNsport (TRN)
It transfers signalling and LLC PDUs between MS and SGSN.
telecom
layer
n+1
telecom
layer
n-1
BC Bearer Channel
All rights reserved. Passing on and copying of this
document, use and communication of its contents
END OF DOCUMENT
GPRS telecom presentation
ED 02 released
256_02.DOC
MCD 30/09/1999
3BK 11202 0256 DSZZA 124/122