S.Barre Song Jun Name App. R.Sabellek: SYT Manager DPM Syt DPM BSC

not permitted without written authorization from Evolium.
All rights reserved. Passing on and copying of this

document, use and communication of its contents
Site
VELIZY EVOLIUM™ SAS
Originator(s)
PAGING, ACCESS GRANT CONTROL AND NOTIFICATION
RELEASE B10
M.WOCH
System : ALCATEL 900/BSS

Sub-system : SYT/TLA
Document Category : PRODUCT DEFINITION
ABSTRACT
This document describes the management of the common control channel (CCCH) and the Paging
and Notification procedures. It includes GPRS common channels procedures when there is no packet
common control channel (PCCCH) on a cell.
Approvals
Name R.MAUGER S.BARRE SONG JUN
SYT Manager DPM SYT DPM BSC
App.
Name R.SABELLEK
DPM BTS
App.
REVIEW
206009.doc 12/12/05
HISTORY
Release B10: 3BK 11202 0439 DSZZA
Ed 2 3 Released PAGING, ACCESS GRANT CONTROL AND

NOTIFICATION
0439_03_Rel.doc0439_02.doc
3BK 11202 0439 DSZZA 1/81

10/01/2007
Ed. 01 Proposal 01 2005/10/19 Document created based on B9 version of the document

(i.e. 3BK 11202 0415 DSZZA Ed.2 RL).
Addition of the following B10 features:
- DTM and mCCCH feature
Ed 01 Proposal 02 2005/12/08 Updated according to the remarks for Proposal 01
MPDCH frozen to B9.
Ed 01 Released 2006-01-03 Updated according to the remarks for Proposal 02 (report
review 206009_1.doc)
Ed 02 Proposal 01 2006-10-17 Including of CRQ: CR 3BKA20CBR195288
- Introduction of Multiple Paging command
Ed 02 Released 2006-10-23 No review report for Proposal 01
Ed 03 Released 2007-01-10 Including of CRQ CR 3BKA20CBR200791
- Multiple Paging Command implemented only on
BSC Evolution.
Including of CRQ CR 3BKA20CBR195537
- Impact of RFD 193412 (compressed INTER RAT
HO INFO element)

NOTIFICATION
0439_03_Rel.doc0439_02.doc
3BK 11202 0439 DSZZA 2/81

10/01/2007
UNSUPPORTED FEATURES
The following paging features are not supported by this release of the Alcatel BSS:
- Dynamic CCCH Partition (TFD 3BK 10204 0183 DRZZA),
- Extended Paging Mode (TFD 3BK 10204 0378 DRZZA),
-
- Paging reorganisation mode, Paging repetition performed by the BSS,
- Use of the channel needed information in the paging message.
- VBS feature (of the ASCI features set).

NOTIFICATION
0439_03_Rel.doc0439_02.doc
3BK 11202 0439 DSZZA 3/81

10/01/2007
TABLE OF CONTENTS
TABLE OF CONTENTS .........................................................................................................43

INTERNAL REFERENCED DOCUMENTS............................................................................65
REFERENCED DOCUMENTS...............................................................................................65
RELATED DOCUMENTS.......................................................................................................76
PREFACE ..............................................................................................................................76
OPEN POINTS / RESTRICTIONS .........................................................................................76
1 SCOPE............................................................................................................................87
2 FUNCTIONAL DESCRIPTION .......................................................................................98
2.1 General Description...............................................................................................98
2.1.1 Circuit Switched Paging procedure...........................................................98
2.1.2 Packet Switched Paging procedure ..........................................................98
2.1.3 Circuit Switched Immediate Assignment procedure .................................98
2.1.4 Packet Switched Access procedure........................................................109
2.1.5 VGCS Notification procedure..................................................................109
2.1.6 CCCH channel ........................................................................................109
2.2 CCCH organization ............................................................................................1211
2.2.1 Radio Multiplexing.................................................................................1211
2.2.2 (Packet) CCCH Group ..........................................................................1413
2.2.3 CCCH_GROUP selection algorithm .....................................................1413
2.2.4 Paging...................................................................................................1514
2.3 PCH, AGCH and NCH channels ........................................................................1615
2.3.1 Sharing the CCCH ................................................................................1615
2.3.2 Sharing the AGCH ................................................................................1615
2.3.3 PCH, (Packet) Paging Groups and Paging procedure..........................1817
2.3.4 AGCH and Immediate Assignment and Packet Access procedure ......2019
2.3.5 NCH and Notification procedure ...........................................................2019
2.3.6 Example ................................................................................................2019
2.3.7 Dimensioning ........................................................................................2221
3 DYNAMIC BEHAVIOUR .............................................................................................2322
3.1 Message exchanges ..........................................................................................2322
3.1.1 Circuit Paging scenario .........................................................................2322
3.1.2 Packet Paging scenario ........................................................................2928
3.1.3 Circuit Access scenario.........................................................................3433
3.1.4 Packet Access scenario........................................................................3837
3.1.5 Dynamic configuration of PBCCH & PCCCH........................................4039
3.1.6 Notification scenarios............................................................................4645
3.2 Detailed Behaviour ............................................................................................5251
3.2.1 (Packet) Paging procedure ...................................................................5251
3.2.2 (Packet) Paging queues and PDA queues ...........................................5453
3.2.3 Access Grant procedure .......................................................................5756
3.2.4 Access Grant queues............................................................................6059
3.2.5 Notification procedure ...........................................................................6261
3.2.6 Notification Response procedure..........................................................6362

NOTIFICATION
0439_03_Rel.doc0439_02.doc
3BK 11202 0439 DSZZA 4/81

10/01/2007
Telecom and O&M interworking ..............................................................................6564

3.2.7 Configuration Management...................................................................6564
3.2.8 Performance Management ...................................................................6665
3.2.9 Error Checking ......................................................................................6766
4 INTERFACE DESCRIPTION ......................................................................................7069
4.1 Message names .................................................................................................7069
4.1.1 Paging and Packet Downlink Assignment procedure ...........................7069
4.1.2 Immediate Assignment and (EGPRS) Packet Uplink Assignment
procedure .....................................................................................................7170
4.1.3 Notification procedure ...........................................................................7271
4.2 GSM interfaces / Physical interfaces ...............................................................7271
4.2.1 Gb Interface ..........................................................................................7271
4.2.2 A Interface (SS7 or GSL) ......................................................................7271
4.2.3 Abis Interface ........................................................................................7372
4.2.4 Radio Interface......................................................................................7473
4.3 Internal interfaces..............................................................................................7776
4.4 External interfaces.............................................................................................7776
4.5 Timers list...........................................................................................................7776
4.6 Parameters list ...................................................................................................7978
4.6.1 Configuration parameters .....................................................................7978
4.6.2 Queues parameters ..............................................................................7978
4.6.3 Other parameters..................................................................................8079
5 GLOSSARY AND ABBREVIATIONS.........................................................................8180

NOTIFICATION
0439_03_Rel.doc0439_02.doc
3BK 11202 0439 DSZZA 5/81

10/01/2007
INTERNAL REFERENCED DOCUMENTS

Not applicable
REFERENCED DOCUMENTS
3GPP References
[1] 3GPP TS 44.006 Mobile Station - Base Stations System (MS - BSS) Interface Data
Link (DL) Layer Specification
[2] 3GPP TS 44.018 Mobile Radio Interface Layer 3 Specification; Radio Resource
Control Protocol.
[3] 3GPP TS 45.002 Multiplexing and Multiple Access on the radio path.
[4] 3GPP TS 48.058 Base Station Controler - Base Transceiver Station (BCS-BTS)
Interface Layer 3 Specification .
[5] 3GPP TS 48.008 Mobile Switching Centre - Base Station system (MSC-BSS) Interface
Layer 3 Specification .
[6] 3GPP TS 23.060 General Packet Radio Service (GPRS) Service description; Stage 2.
[7] 3GPP TS 43.064 Overall description of the GPRS radio interface; Stage 2.
[8] 3GPP TS 44.060 General Packet Radio Service (GPRS); Mobile Station (MS) - Base
Station System (BSS) interface; Radio Link Control/ Medium Access
Control (RLC/MAC) protocol.
The version numbers of the 3GPP Technical Specifications used in this release are given in [1212].
Alcatel References
[9] Radio and link establishment 3BK 11202 0440 DSZZA
[10] Protocol error handling 3BK 11202 0173 DSZZA
[11] BSS logical configuration management 3BK 11204 0397 DSZZA
[12] Alcatel BSS application document 3BK 11203 0141 DSZZA
[13] SMS Cell Broadcast 3BK 11202 0329 DSZZA
[14] System Information Management 3BK 11202 0457 DSZZA
[15] FBS GPRS – MFS-BSC interface - BSCGP Layer 3BK 11202 0460 DSZZA
[16] GPRS Radio Interface: MAC sub-layer 3BK 11202 0462 DSZZA
[17] FBS GPRS – Radio Interface: RLC sub-layer 3BK 11202 0450 DSZZA
[18] GPRS Radio Interface: RRM sub-layer (PRH) 3BK 11202 0443 DSZZA
[19] GPRS Radio Interface: RRM sub-layer (PCC) 3BK 11202 0441 DSZZA
[20] BSS Telecom Parameters 3BK 11203 0134 DSZZA
[21] BSC Counters Catalogue 3BK 11203 135DSZZA
[22] Layer 3 message dictionary – Abis interface 3BK 11203 0140 DSZZA
[23] Dual Transfer Mode – Functional Specification 3BK 11202 0434 DSZZA
[24] ASCI Functional Specification 3BK 10202 0405 DSZZA
[25] SFD Multiple CCCH 3BK 12204 0028 DTZZA

NOTIFICATION
0439_03_Rel.doc0439_02.doc
3BK 11202 0439 DSZZA 6/81

10/01/2007
RELATED DOCUMENTS
Not applicable
PREFACE
Not applicable
OPEN POINTS / RESTRICTIONS

Not applicable

NOTIFICATION
0439_03_Rel.doc0439_02.doc
3BK 11202 0439 DSZZA 7/81

10/01/2007
1 SCOPE
This document describes the Paging procedure, the Notification procedure and CCCH management
in regard to the BSS. The complete Immediate Assignment procedure is described in document [9].
GPRS common channels procedures are only described when they are performed on standard
common GSM channel (CCCH), i.e. when there is no PCCCH channel in the cell. All GPRS related
informations are taken from 3GPP TS [6], [7], [8], and from Alcatel internal specifications [15], [16],
[17], [18], [19].
The management of multiple CCCH slots TS0, TS2 is

part of this release.
The impacts of DTM are given in the related functional specification (see ref [23])

NOTIFICATION
0439_03_Rel.doc0439_02.doc
3BK 11202 0439 DSZZA 8/81

10/01/2007
2 FUNCTIONAL DESCRIPTION
2.1 General Description
2.1.1 Circuit Switched Paging procedure

The Circuit Switched (CS) Paging procedure allows the PLMN-network to find a mobile subscriber,
who is roaming in it.
The Location Area, the MS is just roaming in, was sent to the MSC in the last Location Update
procedure. Such a Location Area can consist of one or more cells, maybe controlled by different
BSCs.
When the MSC tries to initiate a connection to a mobile (MT Call, SMS Terminated, etc.), it sends to
the BSC a PAGING message containing a ‘Cell Identifier List’ describing the cells concerned by this
PAGING message. Depending on the Paging strategy of the MSC, the PAGING message may
contain a detailed ‘Cell Identifier List’, or a ‘Location Area Code’, or even a ‘All Cells’ indication (see
section 3.2.1.1). Following this information, the BSC performs the Paging procedure on the
concerned cells.
When sending the PAGING message on the A interface, the MSC starts a timer T3113. It waits for a
response from the paged MS until T3113 has expired. If no response is received during T3113, the
MSC may end the Paging procedure, or repeat it by sending a new PAGING message.
As paging messages can be sent via different cells on the radio interface, only the MSC can
recognize, if a paging answer from the MS corresponds to a former paging message. So for the
Alcatel BSS, the paging and the answer to the paging are completely independent procedures.
Important note:
In this document, the “Circuit Switched Paging”, “Circuit Paging” and “CS Paging” denomination are
used for Paging routed from MSC to BSC, without involving SGSN or MFS. “CS paging via SGSN” is
only presented in the end of section 2.3.3, and has no impact on the mechanisms described in this
document.
2.1.2 Packet Switched Paging procedure

The Packet Switched (PS) paging procedure follows the same principles as the CS paging
procedure. Nevertheless, PS and CS paging procedures use a distinct set of mobility parameters.
This leads to the following differences:
The Routing Area (RA) is used instead of the Location Area (LA) for mobility management
procedures.
The SGSN replaces the MSC in the described operations, such as Paging message construction,
transmission and repetition (T3313 is used instead of T3113).
The Paging messages, adressed to cells where there is no PCCCH, are sent by the SGSN to the
BSC through the MFS.
2.1.3 Circuit Switched Immediate Assignment procedure

The paging response is one reason, that a mobile will try to establish a signalling connection to the
network. Other reasons could be an emergency call, originating call, etc. This signalling link
establishment procedure is called the Immediate Assignment procedure. It is described in details in
ref.[9]. In this document we focus more precisely on the Access Grant control, which is the major part
of the Immediate Assignment procedure concerning the ‘dedicated channel’ allocation.

NOTIFICATION
0439_03_Rel.doc0439_02.doc
3BK 11202 0439 DSZZA 9/81

10/01/2007
Important note:
In this document, IMMEDIATE ASSIGNMENT (EXTENDED) messages refers to CS Immediate
Assignments only. An IMMEDIATE ASSIGNMENT containing in the "IA Rest Octets" IE the
information of either a “Packet Downlink Assignment” or a "(EGPRS) Packet Uplink Assignment" is
simply called respectively a PACKET DOWNLINK ASSIGNMENT message or a (EGPRS) PACKET
UPLINK ASSIGNMENT message in the rest of the document, in order to avoid any confusion
between CS and PS domain. Only IMMEDIATE ASSIGNMENT REJECT message can be a CS
Immediate Assignment Reject message or a Packet uplink assignment reject message.
2.1.4 Packet Switched Access procedure
The purpose of the Packet Access procedure is to establish a connection to support the transfer of
data between the mobile station and the network. As for the CS Immediate Assignment procedure,
the reason of a Packet Access procedure may be an answer to a PS Paging, or a MS initiated data
transfer. The packet access can be done in either one phase or in two phases. In the two phases
case, the second phase of the procedure is out of the scope of this document.
Because a GPRS/EGPRS data transmission is mono-directional (except control messages
transferred on PACCH), there is a distinction between Uplink Assignment procedure and Downlink
Assignment procedure.
2.1.5 VGCS Notification procedure

Only the Circuit Switched (CS) domain, and more particularly the Voice Group Call Service (VGCS),
is concerned by the notification procedure.The Notification procedure allows the network to inform
mobile stations supporting VGCS about new or on-going voice group calls. Notifications may be sent
on the NCH, on the PCH, or on the FACCH of other on-going calls in the cell, according to the mode
of the notified mobile station (see 3.2.5). The presence of a NCH is indicated in the SYSTEM
INFORMATION TYPE 1 message. A notification contains the group call reference and possibly other
related information.
Upon receipt of every notification message, a mobile station may decide, either not to react on the
notification, or to join the voice group call, as listener (and maybe later as talker). If a mobile station
decides to join the voice group call, but the notification does not contain a description of the
associated VGCS channel of the cell, the mobile station shall initiate the notification response
procedure. If the description of the VGCS channel was included, the mobile station could directly join
the VGCS call.
The Reduced NCH monitoring mechanism is provided mainly for power saving. When a mobile
station is interested on notifications for new group calls, such mechanism allows to not monitor the
NCH all the time. For this, in addition to indicate any change on NCH (e.g. new notification, updated
notification, removed notification), the network indicates also the changes via the NLN and NLN
status parameters, which are both sent on the PCH (within Pi Rest Octets IE) and on all SACCHs
(within SYSTEM INFORMATION TYPE 6). They warn the mobile station about VGCS call change,
then, if occurred, the MS will listen to the NCH to receive the change content.
The Notification Response procedure is used when the channel description is not included in the
notification for a voice group call the mobile station decided to join. The mobile station has to
establish before a dedicated signaling channel with the BSS to ask the network for the VGCS channel
description. On the other side, this mobile station capability allows the network not to immediately
allocate a VGCS channel in the cell for a new voice group call. The network may allocate a VGCS
channel only on demand, e.g. when asked by a mobile station using the Notification Response
procedure, ie when at least one listener is interested in the new VGCS call in the cell.
2.1.6 CCCH channel

In order to pass information to or from the MS, if there exists no dedicated signalling connection
between MS and network, 3GPP defines the channel type CCCH (Common Control CHannel).

NOTIFICATION
0439_03_Rel.doc0439_02.doc
3BK 11202 0439 DSZZA 10/81

10/01/2007
Depending on the expected traffic, different channel combinations are possible. They are set within
the configuration data generated by the O&M function.
3GPP defines up to 4 Time Slots (TS0, TS2, TS4, TS6 )to carry CCCH informations on the beacon
TRX of one cell .. Each one of these Time Slots corresponds to a CCCH group, and a PCCCH
group (if GPRS supported and no PCCCH channel is available). This releasedescribes theTS0 and
TS2 implementation .
The CCCH channel is used by PCH (Paging), AGCH (Access Grant), NCH (Notification) and RACH
(Random Access Channel) Channels.
• PCH is used by the Paging, Packet Downlink Assignment and Notification procedures.
Messages sent on PCH are:
- PAGING REQUEST messages (by Paging and Notification procedures),
- PACKET DOWNLINK ASSIGNMENT messages (with paging group; see below).
• AGCH is used by the Immediate Assignment, Packet Uplink Assignment procedures and
Packet Downlink Assignment.
Messages sent on AGCH are called ACCESS GRANT messages.
Note : ‘ACCESS GRANT message’ term is not defined by 3GPP Technical Specifications, but it is
used in this document to represent all the possible Radio Interface messages sent on AGCH:
- IMMEDIATE ASSIGNMENT messages,
- IMMEDIATE ASSIGNMENT EXTENDED messages,
- IMMEDIATE ASSIGNMENT REJECT messages,
- PACKET UPLINK ASSIGNMENT messages,
- EGPRS PACKET UPLINK ASSIGNMENT messages,
- PACKET DOWNLINK ASSIGNMENT messages (without paging group; see below).
The PACKET DOWNLINK ASSIGNMENT message is sent on the first available occurrence of AGCH
blocks or on the first available occurrence of PCH of the MS Paging Group depending on the MS
DRX mode:
- When the MS is in non-DRX mode, the Paging Group IE is not provided to the BTS. The BTS
shall then send the PACKET DOWNLINK ASSIGNMENT message on the first available
occurrence of AGCH block.
- When the MS is in DRX mode, the Paging Group IE is provided to the BTS together with the
assignment message. The BTS shall then send the PACKET DOWNLINK ASSIGNMENT
message on the first occurrence of PCH block corresponding to the Paging Group of the MS.
The valuation of the DRX/non-DRX mode of the MS is performed in the MFS and specified in ref.[19].
• NCH is used by the Notification procedure.

Messages sent on NCH are:
- NOTIFICATION/NCH messages.
• RACH is used (uplink only) to request allocation of SDCCH channels .

NOTIFICATION
0439_03_Rel.doc0439_02.doc
3BK 11202 0439 DSZZA 11/81

10/01/2007
PCH, AGCH, BCCH Extended and NCH share the available CCCH blocks in the (51-frames)
multiframe.
CCCH blocks reserved for PCH are called PCH blocks, CCCH blocks reserved for AGCH are called
AGCH blocks. The BCCH Extended, when configured, is on the first CCCH block of the multiframe.
The NCH, when configured in cell supporting VGCS, is always mapped onto contiguous AGCH
blocks. The AGCH blocks reserved for NCH are called NCH blocks. The unused NCH blocks may be
reused for ACCESS GRANT messages
Because they are using the same CCCH resource, there is a fixed relationship between PCH and
AGCH capacities corresponding to BS_AG_BLKS_RES value.
- When no blocks are reserved for AGCH (i.e. BS_AG_BLKS_RES = 0), Access Grant messages
are sent on stolen PCH blocks.
- If the BCCH Extended is configured, the BS_AG_BLKS_RES shall be set to a value greater than
0, i.e. at least one AGCH shall be reserved among CCCH blocks in order to use it as an BCCH
Extended.
- If NCH is configured, the BS_AG_BLKS_RES shall be equal or greater than the number of NCH
blocks (NUMBER_NCH_BLOCKS).
- If NCH and the BCCH Extended are both configured, the BS_AG_BLKS_RES shall be equal or
greater than the number of NCH blocks plus one block. Since the first CCCH block is reserved
for the BCCH Extended, the first NCH block is not allowed to start on this first CCCH block.
- If CCCH is not combined with SDCCH (see section 2.2.1) and CBCH is configured in the cell, the
BS_AG_BLKS_RES shall be set to a value greater than 0, i.e. at least one AGCH block shall be
reserved to let enough time to the MS for switching from BCCH/CBCH to PCH (see 3GPP TS
45.002 [3]).
When BS_AG_ BLKS_RES ≠ 0, the possibility to send Access Grant messages on stolen PCH
blocks is offered to the operator as an option. This is provided especially for the case where the
BCCH Extended is configured.
PCH is subdivided in PCH sub-channels. Each sub-channel corresponds to a specific Paging Group
and a specific Packet Paging Group (if GPRS supported and no PCCCH channel) and can convey
one PAGING REQUEST or one PACKET DOWNLINK ASSIGNMENT message.
(P)CCCH Group and (Packet) Paging Group are derived from the IMSI of the MS. The MS also has
to analyse the Control channel description IE within the SYSTEM INFORMATION TYPE 3 message
in order to get the knowledge about the CCCH organisation.
Mobiles in a specific CCCH_GROUP will listen for paging messages and make random access
specific CCCH to which the CCCH_GROUP belongs .
2.2 CCCH organization
2.2.1 Radio Multiplexing
The PCH and AGCH/NCH are carried on the CCCH downlink. Following types of logical channel
configuration in the (51-frames) multiframe on TS0/TS2 are supported in this release :
• Not Combined CCCH (CCCH_CONF=0)
Downlink
F S B C F S C C F S C C F S C C F S C C -
Uplink
R

NOTIFICATION
0439_03_Rel.doc0439_02.doc
3BK 11202 0439 DSZZA 12/81

10/01/2007
• Combined CCCH (CCCH_CONF=1)
Downlink
F S B C F S C C F S D0 D1 F S D2 D3 F S A0 A1 -
F S B C F S C C F S D0 D1 F S D2 D3 F S A2 A3 -
Uplink
D3 R A2 A3 R D0 D1 R D2
D3 R A0 A1 R D0 D1 R D2
• Not Combined CCCH (CCCH_CONF = 2)
TS0 is the same as Not Combined CCCH (CCCH_CONF = 0)
TS2 is as following:
Downlink
- - B C - - C C - - C C - - C C - - C C -
Uplink
R
This distinction is given either by the parameter CCCH_CONF or by the parameters BS_CC_CHANS
and BS_CCCH_SDCCH_COMB. 3GPP TS 44.018 [2] uses only CCCH_CONF and 3GPP TS 45
series namely 3GPP TS 45.002 [3] uses BS_CC_CHANS and BS_CCCH_SDCCH_COMB. Table 1
gives the correspondence between the two possibilities.
CCCH_CONF BS_CC_CHANS BS_CCCH_SDCCH_COMB

0 1 no
1 1 yes
2 2 no
4 3 no
6 4 no
Table 1: Correspondence between CCCH parameters
As given in 3GPP TS 45.002 [3], the list of permitted BCCH/CCCH channel combinations is:
- FCCH + SCH + BCCH + CCCH
- FCCH + SCH + BCCH + CCCH + SDCCH/4(0..3) + SACCH/4(0..3) (1)
- BCCH + CCCH (2)where CCCH =

PCH (downlink) + AGCH (downlink) + RACH (uplink) + optionally Ext BCCH (downlink) + optionally
NCH (downlink)

NOTIFICATION
0439_03_Rel.doc0439_02.doc
3BK 11202 0439 DSZZA 13/81

10/01/2007
Note: (1)This combination is allowed if there is only one CCCH Group.

(2) This combination is used on TS2 in case of multiple CCCH Groups.
2.2.2 (Packet) CCCH Group

The CCCH Group informs the MS on which Time Slot (of those which are available), it should listen
to for the Paging procedure. The same CCCH Group is also used in the Immediate Assignment
procedure. The PCCCH Group shall be used in the GPRS attached mode for paging and uplink /
downlink access procedures. It has the same function as the CCCH Group for TS determination. It is
computed as described hereafter:
CCCH_GROUP = ((IMSI mod 1000) mod (BS_CC_CHANS * N)) div N
PCCCH_GROUP = CCCH_GROUP
with:
- BS_CC_CHANS = number of basic physical channels supporting CCCH (range 1..4).
BS_CC_CHANS is derived from CCCH_CONF (see table 1).
- For definition of N, see section 2.3.3.
Warning: In this release, only TS0 and TS2 (i.e. (P)CCCH_GROUP = 0 and (P)CCCH_GROUP = 1)
are supported.
The following table gives the relationship between the (P)CCCH_GROUP number and used time slot.
(P)CCCH_GROUP TS
0 0
1 2
2 4
3 6
Table 2: Correspondence between (P)CCCH_GROUP and TS concerned
2.2.3 CCCH_GROUP selection algorithm
Each CCCH carries its own CCCH_GROUP of mobiles in idle mode. Mobiles in a specific
CCCH_GROUP will listen for paging messages and make random accesses only on the specific
CCCH to which the CCCH_GROUP belongs. The method by which a mobile determines the
CCCH_GROUP to which it belongs is defined in TS 45.002 Section 6.5.1 and 6.5.2:
CCCH_GROUP (0 .. BS_CC_CHANS-1) = ((IMSI mod 1000) mod (BS_CC_CHANS x N)) div N
Where
BS_CC_CHANS = number of basic physical channels supporting common control channels
(CCCHs).
N = number of paging blocks "available" on one CCCH = (number of paging blocks "available" in
a 51-multiframe on one CCCH) x BS_PA_MFRMS.
BS_PA_MFRMS = number of 51-multiframes between transmissions of paging messages to
mobiles in idle mode of the same paging group.
IMSI = International Mobile Subscriber Identity, as defined in 3GPP TS 23.003.
mod = Modulo.
div = Integer division.

NOTIFICATION
0439_03_Rel.doc0439_02.doc
3BK 11202 0439 DSZZA 14/81

10/01/2007
The following table gives the relationship between the CCCH_GROUP number and Timeslot Number.
CCCH_GROUP TN
0 0
1 2
TABLE 3: Correspondence between CCCH_GROUP and TS concerned
2.2.4 Paging
During paging procedure(both CS and PS), BSC need to count the CCCH_GROUP and
PAGING_GROUP for the MS. BSC use the same fomula as the MS defined in TS 45.002 Section
6.5.2 for CCCH_GROUP and PAGING_GROUP:
The CCCH_GROUP formula is described in Section and the PAGING_GROUP formula is as flowing.
PAGING_GROUP (0 .. N-1) = ((IMSI mod 1000) mod (BS_CC_CHANS x N)) mod N

(See Section 2.2.3 for the meaning of BS_CC_CHANS and N).
BSC gets the CCCH TN base on the CCCH_GROUP(see Table 3 ).
BSC sends the CCCH TN and PAGING_GROUP to BTS in PAGING COMMAND or MULTIPLE
PAGING COMMAND.
BTS then sends the PAGING REQUEST on the radio channel.

Note : Multiple Paging Command concerns only BSC Evolution.

NOTIFICATION
0439_03_Rel.doc0439_02.doc
3BK 11202 0439 DSZZA 15/81

10/01/2007
2.3 PCH, AGCH and NCH channels
2.3.1 Sharing the CCCH
The parameter, BS_AG_BLKS_RES, gives the number of reserved AGCH blocks. The value of this
parameter is:
in the interval 0 to 7 if CCCH_CONF is different from 1 (see also ref.[20] for the list of constraints
on the setting of the parameter BS_AG_BLKS_RES),
or in the interval 0 to 2 if the value of CCCH_CONF is equal to 1 (i.e. if

BS_CCCH_SDCCH_COMB is true).
But there is always, at least, one block reserved for PCH.
When the AGCH is present, it occupies the BS_AG_BLKS_RES first CCCH blocks. In the case when
no block is reserved for AGCH (BS_AG_BLKS_RES = 0), or when BS_AG_BLKS_RES=1 and the
flag AG_PREMPT_PCH is true, then the AGCH messages are sent, using a pre-emption mechanism,
on PCH blocks (see section 3.2.4).
CCCH 0 CCCH 1 CCCH 2 CCCH 3 CCCH 4 CCCH 5 CCCH 6 CCCH 7 CCCH 8

Reserved for AGCH 6 CCCH blocks are available for the PCH
Example of AGCH and PCH organisation when BS_AG_BLKS_RES = 3
Note: BCCH Extended is made of one stolen CCCH block normally reserved for AGCH. When the
BSS uses BCCH Extended, the parameter BS_AG_BLKS_RES shall be set to at least 1. The
first block can be used either as a BCCH Extended or as an AGCH block (ie SYSTEM
INFORMATION messages and ACCESS GRANT messages may be send on the same
block).To allow the operator to still use the pre-emption mechanism (ie AG_PREMPT_PCH
set to true) with BCCH Extended, BS_AG_BLKS_RES must be equal to 1. The OMC-R is in
charge of checking the consistency of the BS_AG_BLKS_RES and AG_PREMPT_PCH
values. For more information on BCCH Extended, see ref.[14] and FHS Extension feature (§
10).
2.3.2 Sharing the AGCH
The NCH channel configuration is linked to the VGCS feature support (if not supported by the cell,
NCH is not present).
An MS which has its membership of at least one voice group call group set to the active state shall, in
addition to monitoring the paging channel, monitor the notification channel, NCH.
The presence of NCH is signalled by the NCH Position IE in the SYSTEME INFORMATION TYPE 1
message, broadcast on the BCCH (defined in 3GPP TS 44.018 [2]). NCH is always mapped onto
contiguous blocks reserved for access grants, in a position and number as given by the parameter
NCH Position.
The coding of the various structural parameters is not changed. Information within a block, when
deinterleaved and decoded, allows the MS to determine whether the block contains access grant
messages or notification messages or system information messages.(see 3GPP TS 45.002, section
6.5.1)

NOTIFICATION
0439_03_Rel.doc0439_02.doc
3BK 11202 0439 DSZZA 16/81

10/01/2007
The configuration of the NCH is restricted as it can only exist within a portion of the AGCH (section
6.5.1 of 3GPP TS 45.002). The BTS will send AGCH messages on the AGCH (or on the pre-empted
PCH or on the unused NCH) and NOTIFICATION messages on the NCH part of the AGCH
The parameter, NUMBER_NCH_BLOCKS, gives the number of reserved NCH blocks, ie the
maximum number of AGCH blocks used as NCH blocks. The value of this parameter is:
in the interval 1 to 7 if CCCH is not combined
or in the interval 1 to 2 if CCCH is combined

Maximum used for NCH
CCCH blocks are available for the PCH
Reserved for AGCH
Example of AGCH and NCH organisation when BS_AG_BLKS_RES = 5 and

NUMBER_NCH_BLOCKS = 3 (without BCCH Extended)

Maximum used for NCH
CCCH blocks are available for the PCH
Reserved for AGCH
Example of AGCH and NCH organisation when BS_AG_BLKS_RES = 5 and

NUMBER_NCH_BLOCKS = 3 (with BCCH Extended)
Note: When the BSS uses NCH, the parameter BS_AG_BLKS_RES shall be set to at least
NUMBER_NCH_BLOCKS. If, in addition it uses BCCH Extended, the parameter
BS_AG_BLKS_RES shall be set to at least NUMBER_NCH_BLOCKS+1 To allow the operator
to still use the pre-emption mechanism when NCH is used, BS_AG_BLKS_RES must be
equal to NUMBER_NCH_BLOCKS+1 (if BCCH Extended is unused), equal to
NUMBER_NCH_BLOCKS+3 (if BCCH Extended is used). For more information on NCH see
section.
According to 3GPP TS 44.018, table 10.5.2.32.1b, the NCH Position coding allows the first NCH
blocks to start at different position block, depending on the reserved NUMBER_NCH_BLOCKS. In
the Alcatel implementation, the starting block position is restricted to the first or the second CCCH
block, according to the Extended BCCH usage. The available NCH position values are given in the
following table:

NOTIFICATION
0439_03_Rel.doc0439_02.doc
3BK 11202 0439 DSZZA 17/81

10/01/2007
CCCH block which is used

NUMBER NCH position coding for the first NCH block
BCCH
_NCH_B (5 bits, see 3GPP 44.018,
Extended (see 3GPP 45.002 clause 7
LOCKS Table 10.5.2.32.1b) table 3)
1 0 (disabled) 00000 0 [B0 (6..9)]
1 1 (enabled) 00001 1 [B1 (12..15)]
2 0 00111 0 [B0 (6..9)]
2 1 01000 1 [B1 (12..15)]

3 0 01101 0 [B0 (6..9)]
3 1 01110 1 [B1 (12..15)]

4 0 10010 0 [B0 (6..9)]
4 1 10011 1 [B1 (12..15)]

5 0 10110 0 [B0 (6..9)]
5 1 10111 1 [B1 (12..15)]

6 0 11001 0 [B0 (6..9)]
6 1 11010 1 [B1 (12..15)]

7 0 11011 0 [B0 (6..9)]
2.3.3 PCH, (Packet) Paging Groups and Paging procedure
The PCH is used to send PAGING REQUEST and GPRS PACKET DOWNLINK ASSIGNMENT
messages (when paging group is known) to Mobile Stations.
The PCH can also be used to send NOTIFICATION messages when VGCS is supported in the cell
(see 3.2.5).
The Paging Group is a number allocated to a Mobile Station which allows it to listen to a specific PCH
sub-channel. With this number, the formula of which is given below, the Mobile Station is not obliged
to listen to all the CCCH blocks reserved for PCH. It will only listen to its own Paging Group in order
to save battery power. MS goes to idle mode between two occurrences of its Paging Group, and
wakes up at the relevant time only. This is the DRX Paging.
Packet Paging Groups are used for GPRS paging. On CCCH (No PCCCH channel), these groups
are the same as Paging Groups. As for CS Paging, DRX is used and the MS monitors its own
Paging Group.
On CCCH, there is no multiple Paging Group management with SPLIT_PG_CYCLE parameter like
on PCCCH channel. Thus the SPLIT_PG_CYCLE_SUPPORTED field in the SYSTEM
INFORMATION TYPE 13 message shall be set to false. As described in 3GPP TS 45.002, the same
formula, using BS_PA_MFRMS parameter is used for Paging Group computation.

NOTIFICATION
0439_03_Rel.doc0439_02.doc
3BK 11202 0439 DSZZA 18/81

10/01/2007
• In the non-DRX mode, the mobile station shall listen to all the blocks located on the CCCH
channel defined by its CCCH Group, which corresponds to the PCCCH Group it belongs to.
• In the DRX mode, the mobile station shall listen to the paging group on PCH defined by the IMSI
of the MS (Alcatel BSS does not support the SPLIT_PG_CYCLE option on CCCH);
Whatever the DRX mode of the MS, the BTS shall send (Packet) PAGING message on the next
occurrence of the MS Packet Paging Group.
When the MS is in DRX mode, the BTS shall send the PACKET DOWNLINK ASSIGNMENT
message on the next occurrence of the MS Packet Paging Group on PCH.
When the MS is in non-DRX mode, the BTS shall send the PACKET DOWNLINK ASSIGNMENT
message on the next occurrence of AGCH.
See also section 2.1.6 and for more details, see ref.[19].
The occurrence of a (Packet) Paging Group can vary from:
2 * duration of a CCCH-multiframe (470.76ms) to 9 * duration of a CCCH-multiframe (2118.46 ms).
The combination of BS_AG_BLKS_RES and BS_PA_MFRMS gives the number of (Packet) Paging
Groups. This number is called N. It is obtained when multiplying the number of PCH blocks
"available" on one (51-frames) multiframe by BS_PA_MFRMS (see paragraphs related to
dimensioning for the range of each parameter). BS_PA_MFRMS gives the number of (51-frames)
multiframes between two occurrences of the same (Packet) Paging Group.
PAGING_GROUP = (( IMSI mod 1000 ) mod ( BS_CC_CHANS * N )) mod N

PACKET_PAGING_GROUP = PAGING_GROUP
The CCCH parameters are broadcast on the BCCH into the "Control Channel Description" parameter
of "SYSTEM INFORMATION TYPE 3" messages.
Each MS knowing the CCCH organisation, has access to all the parameters previously defined. The
Mobile Station is able to calculate its (Packet) Paging Group and its (P)CCCH Group (the same
calculation is also performed by the BSC).
There is a waiting queue for each Paging Group. The size of this queue is the maximum number of
PAGING REQUEST messages that may be stored in one single queue. Each PAGING REQUEST
message sent on Radio interface may contain between 1 and 4 PAGING COMMAND messages. For
GPRS cells, there is another waiting queue for PACKET DOWNLINK ASSIGNMENT messages sent
on PCH. When a PACKET DOWNLINK ASSIGNMENT message (sent on PCH) is present in the
queue, it has priority over pending PAGING REQUEST messages and shall be sent in the next
occurrence of the Packet Paging Group.
GPRS specific note :

CS Paging messages shall be sent through PCH channels except when the following conditions are
simultaneously fulfilled:
• Network Operation Mode I, i.e. Gs (MSC-SGSN interface) is present,
• GSM & GPRS Attached MS,
• a primary MPDCH is activated in the cell and T_EST_MPDCH_PROC is not running (see
section 3.1.5)
or MS in packet transfer mode
If all the described conditions are met, CS Paging messages shall be routed from the MSC to the
SGSN (via the Gs interface) and sent on a PDCH (either PCCCH or PACCH).

NOTIFICATION
0439_03_Rel.doc0439_02.doc
3BK 11202 0439 DSZZA 19/81

10/01/2007
2.3.4 AGCH and Immediate Assignment and Packet Access procedure
The AGCH is used to send ACCESS GRANT messages to Mobile Stations.
An ACCESS GRANT message can be a PACKET UPLINK ASSIGNMENT, an EGPRS PACKET

UPLINK ASSIGNMENT, a PACKET DOWNLINK ASSIGNMENT (only when the MS is in non-DRX
mode), an IMMEDIATE ASSIGNMENT, an IMMEDIATE ASSIGNMENT EXTENDED or an
IMMEDIATE ASSIGNMENT REJECT message.
• PACKET UPLINK ASSIGNMENT, EGPRS PACKET UPLINK ASSIGNMENT, PACKET

DOWNLINK ASSIGNMENT, IMMEDIATE ASSIGNMENT and IMMEDIATE ASSIGNMENT
EXTENDED messages are used to provide allocated dedicated channels description to the MS.
• IMMEDIATE ASSIGNMENT REJECT message is sent to the Mobile Stations, when all suitable
resources are busy, in order to delay the Mobile random access attempts. Note that on CCCH
(No PCCCH channel), this message shall be sent to the MS instead of a PACKET ACCESS
REJECT message.
The Immediate Assignment procedure takes place at the beginning of the transaction, after the
Mobile Station has accessed the network with a Random Access burst on RACH (uplink).
There is a global waiting queue for the Immediate Assignment procedure. Its size is the maximum
number of ACCESS GRANT messages that may be stored in the queue. For IMMEDIATE
ASSIGNMENT messages only, using IMMEDIATE ASSIGNMENT EXTENDED messages allows to
send 2 IMMEDIATE ASSIGN COMMAND messages in the same message on Radio interface (see
3.1.3.2).
2.3.5 NCH and Notification procedure
The NCH is used to send NOTIFICATION messages to mobile stations.
The Notification procedure is similar to the Paging procedure used in the standard point-to-point CS
call. A VGCS mobile station needs to be informed of any new VGCS call(s) being established in the
cell. It needs to be informed of the on-going VGCS call(s) also, throughout their duration, in order to
permit the “late entry” of other mobile stations into the cell.
In addition to NCH, the NOTIFICATION messages may be sent, optionally, on FACCH or on PCH,
according to the Mobile Stations mode (idle, group receive, group transmit, dedicated group transmit
or dedicated). For more information, see section Notification procedures of ASCI specification[24].
A reduced NCH monitoring mechanism has been defined for Mobile Stations which read both NCH
and PCH in order to keep their reception load to a minimum. When the mobile station, in idle mode,
enters a cell where NCH is present, it shall read the NCH until it has received the two last messages
with identical Notification List Number (NLN). Then it may stop reading NCH and read PCH only, until
it receives on PCH an indication of change occured on NCH (via NLN and/or NLN status). For more
information, see section NLN and NLN Status of ASCI specification[24].
2.3.6 Example
The following figure gives an example of the (51-frames) multiframes and Paging Groups with the
following set of parameters:

NOTIFICATION
0439_03_Rel.doc0439_02.doc
3BK 11202 0439 DSZZA 20/81

10/01/2007
CCCH_CONF = 0
==> the CCCH_GROUP has the zero value for CCCH on TS0
==> The number of CCCH blocks per (51-frames) multiframe is equal to 9 (no SDCCH).
BS_AG_BLKS_RES = 3
==> There are 3 AGCH blocks per (51-frames) multiframe.

==> There are 6 (9-3) PCH blocks per (51-frames) multiframe.
BS_PA_MFRMS = 4
==> 4 consecutive (51-frames) multiframes are used for one cycle on all the available Paging
Groups.
There are 24 Paging Groups (24 = 6 * 4).
NUMBER_NCH_BLOCKS = 1
==> Among the 3 AGCH blocks, there is 1 NCH block per (51-frames) multiframe.
First 51-TDMA frame
NCH AGCH AGCH PGR 0 PGR 1 PGR 2 PGR 3 PGR 4 PGR 5

Second 51-TDMA frame

Third 51-TDMA frame

Fourth 51-TDMA frame

Reserved for the AGCH PGR: Paging Group (from 0 to 23)
Example of CCCH organisation

NOTIFICATION
0439_03_Rel.doc0439_02.doc
3BK 11202 0439 DSZZA 21/81

10/01/2007
2.3.7 Dimensioning
2.3.7.1 Inputs Parameters
- CCCH_CONF: 0, 1, 2, 4, 6
- BS_AG_BLKS_RES: 0 - 2 if CCCH_CONF = 1
0 - 7 if CCCH_CONF ≠ 1 (see also ref.[20] for the list of constraints on
the setting of the parameter BS_AG_BLKS_RES)
- BS_PA_MFRMS: 2-9
- NUMBER_NCH_BLOCKS: 1 - 7
2.3.7.2 Deduced Values
- BS_CC_CHANS: 1 - 4 depending on the value of CCCH_CONF (see table 1)
- Number of PCH blocks available per (51-frames) multiframes: 1 - 3 if CCCH_CONF = 1

2 - 9 if CCCH_CONF ≠ 1
The values given hereafter are relative to one CCCH Time Slot. In case of several CCCH Time Slots,
the global dimension for the whole BTS is obtained by multiplying these values by the number of
CCCH Time Slots.
- N (Number of Paging Groups): 2 - 81
N is obtained when multiplying BS_PA_MFRMS by the number of PCH blocks available per (51-
frames) multiframe. The minimum value is determined with BS_PA_MFRMS equal to 2 and number
of PCH blocks equal to 1. The maximum value is determined with BS_PA_MFRMS equal to 9 and
number of PCH blocks equal to 9.

NOTIFICATION
0439_03_Rel.doc0439_02.doc
3BK 11202 0439 DSZZA 22/81

10/01/2007
3 DYNAMIC BEHAVIOUR
3.1 Message exchanges
3.1.1 Circuit Paging scenario

3.1.1.1 Case of Paging command.
This scenario is applied in case of G2 BTS or if NB_MAX_MSG_MULTIPLE_PAGING_CMD=1

(Paging command is used).

NOTIFICATION
0439_03_Rel.doc0439_02.doc
3BK 11202 0439 DSZZA 23/81

10/01/2007
MSs Radio Channel BTS BSC MSC
PAGING (MS1)
1 <-----------------------------------------
PAGING COMMAND (MS1,pgr1) Start T3113
2 <------------------------------------------ for MS1
PAGING (MS3)
1a <-----------------------------------------
2a <------------------------------------------ for MS3
PAGING (MS2)
1b <-----------------------------------------
2b <------------------------------------------ for MS2
. . .
. . (Repeated for MS4 - MS9) .
. . .
. (Repeated for . .
. MS4-MS5 of pgr2, . .
. MS6-MS9 of pgr4) . .
. . .
PAGING REQUEST TYPE 1
3a <-------------PCH,pgr1--------------
(MS1,MS2)

3b <-------------PCH,pgr2--------------
(MS3,MS4,MS5) (®)

3c <-------------PCH,pgr3--------------
(No Identity)

3d <-------------PCH,pgr4--------------
(MS6,MS7,MS8,MS9) (®)
4
Access Grant scenario for all MSs
which answer to a Paging Request
PAGING RESPONSE (MSn)

5 ----------SDCCH-------------------->------------------------------------------>------------------------------------->
Stop T3113
for Msn
Note: - This scenario is for one CCCH-group only.

- ‘pgrX’ means Paging Group X.
(®) Needs the use of TMSI numbers.
The following, describes the general behaviour within the BSS. The given number refers to the steps
as indicated on the left side of the scenario:

NOTIFICATION
0439_03_Rel.doc0439_02.doc
3BK 11202 0439 DSZZA 24/81

10/01/2007
1-1b MSC sends a PAGING message in connectionless mode and starts the timer T3113 to
supervise the PAGING RESPONSE message from the MS. The MSC may repeat the PAGING
message if no answer arrives before T3113 expiry.
2-2b The BSC sends a PAGING COMMAND to each cell in which the Paging shall be transmitted
except for cells whose BTS_TEL SBL is disabled and cells where PAG_BAR=1 (see note
below).
When the MSC sends a PAGING message to be transmitted in one or more Location Areas
(i.e. the Cell Identifier List IE contains a list of LAC or LAI), the BSC sends a PAGING
COMMAND in each cell of each listed Location Area only in case the number of different listed
Location Areas is equal or less than 10. Otherwise, the BSC sends a PAGING COMMAND in
all its cells (Alcatel restriction). No Paging is transmitted to cells whose BTS_TEL SBL is
disabled and cells where PAG_BAR=1.
Note: the PAG_BAR parameter enables the operator to prevent mobile stations from ringing in
specific cells (for instance, during a concert).
- The Channel Number - IE within the message header is set to the calculated CCCH timeslot.
- The Paging Group - IE is set according to the calculated Paging Group.
- The MS Identity is set to the TMSI, if TMSI was sent in the PAGING message via the A
Interface, if not, to the IMSI.
3 BTS receives the PAGING COMMAND messages from the BSC and builds PAGING
REQUEST messages to be sent on Radio interface. As the receiving of these messages is not
time synchronous with the transmission of the PAGING REQUEST message on the Radio
Interface, there is the need to store the PAGING REQUEST messages in a transmission buffer,
the waiting queue (see 2.3.3), until the next occurrence of the corresponding Paging Group.
• The buffer is organized according to the FIFO principle

• The length of one Paging Group buffer is defined according to T_PAG_PS and
T_PAG_CS, the maximum duration a PAGING REQUEST message is allowed to be stored
in this buffer (see section 3.2.2).
• The maximum number of all PAGING REQUEST messages, that can be stored in the
BTS for one CCCH group is limited to the parameter PG_FULL (see section 3.2.2).
With the PAGING COMMAND messages received from the BSC, the BTS builds PAGING
REQUEST messages. The PAGING COMMAND contains two main parameters: Paging Group
and Mobile Identity (IMSI or TMSI). On the radio interface, 3 different messages (PAGING
REQUEST TYPE 1, 2 or 3) can be sent according to the number of Mobile Stations with the
same Paging Group and CCCH group to be paged and also according to the type (IMSI or
TMSI) of the Mobile Identity.
3a Occurrence of Paging Group 1: PAGING REQUEST TYPE 1 with 2 MS Identities is

transmitted.
3b Occurrence of Paging Group 2: PAGING REQUEST TYPE 2 with 3 MS Identities is

transmitted.
3c Occurrence of Paging Group 3: If no PAGING COMMAND message is pending, a Paging

Filling Frame is transmitted. For informations related to the “Paging Filling Frame” format, see
3GPP TS 04.06 [1].
3d Occurrence of Paging Group 4: PAGING REQUEST TYPE 3 with 4 MS Identities (only TMSIs)
is transmitted.
4 Access Grant scenario is performed as described in section 3.1.2.23.1.3.

NOTIFICATION
0439_03_Rel.doc0439_02.doc
3BK 11202 0439 DSZZA 25/81

10/01/2007
5 After the successful allocation of the SDCCH see ref.[9].

3.1.1.2 Case of Multiple Paging command.
This scenario applies to Evolium BTS, when NB_MAX_MSG_MULTIPLE_PAGING_CMD > 1 (more

than one Paging command ).

NOTIFICATION
0439_03_Rel.doc0439_02.doc
3BK 11202 0439 DSZZA 26/81

10/01/2007
MSs Radio Channel BTS BSC MSC
PAGING (MS1)
1 <-----------------------------------------
Start T3113
for MS1
PAGING (MS3)
1a <-----------------------------------------
Start T3113
for MS3
PAGING (MS2)
1b <-----------------------------------------
Start T3113
for MS2
PAGING (MS4)
1c <-----------------------------------------
Start T3113
for MS4
PAGING (MS5)
1d <-----------------------------------------
Start T3113
for MS5
Stop
T_SEND_MULTIPLE_PAGING_CMD
MULTIPLE PAGING COMMAND (MS1,pgr1;
MS3,pgr2; MS2,pgr1; MS4, pgr2; MS5, pgr2)
2 <------------------------------------------
Start
expired
MS7,pgr4; MS8,pgr4; MS9, pgr4)
2b <------------------------------------------
Start
3a <-------------PCH,pgr1--------------
(MS1,MS2)

3b <-------------PCH,pgr2--------------
(MS3,MS4,MS5) (®)

3c <-------------PCH,pgr3--------------
(No Identity)

3d <-------------PCH,pgr4--------------
(MS6,MS7,MS8,MS9) (®)
4

NOTIFICATION
0439_03_Rel.doc0439_02.doc
3BK 11202 0439 DSZZA 27/81

10/01/2007
Access Grant scenario for all MSs

which answer to a Paging Request
PAGING RESPONSE (MSn)

5 ----------SDCCH-------------------->------------------------------------------>------------------------------------->
Stop T3113
Note: - This scenario is for one CCCH-group only.

(®) Needs the use of TMSI numbers.
The following, describes the general behaviour within the BSS. The given number refers to the steps
as indicated on the left side of the scenario:
1-1d MSC sends a PAGING message in connectionless mode and starts the timer T3113 to
supervise the PAGING RESPONSE message from the MS. The MSC may repeat the PAGING
message if no answer arrives before T3113 expiry. . If not yet running, BSC starts
T_SEND_MULTIPLE_PAGING_CMD.
2-2b When the number of PAGING messages queued in the BSC (i.e. received from MSC, but not
sent yet to the BTS) equals NB_MAX_MSG_MULTIPLE_PAGING_CMD, or at
T_SEND_MULTIPLE_PAGING_CMD expiry the BSC sends a MULTIPLE PAGING
COMMAND to each cell in which the Paging shall be transmitted except for cells whose
BTS_TEL SBL is disabled and cells where PAG_BAR=1 (see note below).
When the MSC sends a PAGING message to be transmitted in one or more Location Areas
(i.e. the Cell Identifier List IE contains a list of LAC or LAI), the BSC sends a MULTIPLE
PAGING COMMAND in each cell of each listed Location Area only in case the number of
different listed Location Areas is equal or less than 10. Otherwise, the BSC sends a MULTIPLE
PAGING COMMAND in all its cells (Alcatel restriction). No Paging is transmitted to cells whose
BTS_TEL SBL is disabled and cells where PAG_BAR=1.
Note: the PAG_BAR parameter enables the operator to prevent mobile stations from ringing in
specific cells (for instance, during a concert).
For each contained Paging Information:
- The Channel Number - IE within the message header is set to the calculated CCCH timeslot.
- The Paging Group - IE is set according to the calculated Paging Group.
- The MS Identity is set to the TMSI, if TMSI was sent in the PAGING message via the A
Interface, if not, to the IMSI.
3 BTS receives the MULTIPLE PAGING COMMAND messages from the BSC and builds
PAGING REQUEST messages to be sent on Radio interface. As the receiving of these
messages is not time synchronous with the transmission of the PAGING REQUEST message
on the Radio Interface, there is the need to store the PAGING REQUEST messages in a
transmission buffer, the waiting queue (see 2.3.3Error! Reference source not found.), until
the next occurrence of the corresponding Paging Group.
• The buffer is organized according to the FIFO principle

• The length of one Paging Group buffer is defined according to T_PAG_PS and
T_PAG_CS, the maximum duration a PAGING REQUEST message is allowed to be stored
in this buffer (see section 3.2.20).
• The maximum number of all PAGING REQUEST messages, that can be stored in the
BTS for one CCCH group is limited to the parameter PG_FULL (see section 3.2.20).

NOTIFICATION
0439_03_Rel.doc0439_02.doc
3BK 11202 0439 DSZZA 28/81

10/01/2007
With the MULTIPLE PAGING COMMAND messages received from the BSC, the BTS builds
PAGING REQUEST messages. The MULTIPLE PAGING COMMAND contains two main
parameters: Paging Group and Mobile Identity (IMSI or TMSI). On the radio interface, 3
different messages (PAGING REQUEST TYPE 1, 2 or 3) can be sent according to the number
of Mobile Stations with the same Paging Group and CCCH group to be paged and also
according to the type (IMSI or TMSI) of the Mobile Identity.

transmitted.

transmitted.
3c Occurrence of Paging Group 3: If no PAGING REQUEST message is pending, a Paging Filling

Frame is transmitted. For informations related to the “Paging Filling Frame” format, see 3GPP
TS 04.06
3d Occurrence of Paging Group 4: PAGING REQUEST TYPE 3 with 4 MS Identities (only TMSIs)
is transmitted.
4 Access Grant scenario is performed as described in section

5 After the successful allocation of the SDCCH see ref
3.1.2 Packet Paging scenario

3.1.2.1 Case of Paging command


NOTIFICATION
0439_03_Rel.doc0439_02.doc
3BK 11202 0439 DSZZA 29/81

10/01/2007
MSs Radio Channel BTS BSC [MSC] / [SGSN via MFS]
PS PAGING (MS1) from SGSN

1 <-----------------------------------------
2 <------------------------------------------ for MS1
1a <-----------------------------------------
2a <------------------------------------------ for MS2
1b <-----------------------------------------
2b <------------------------------------------ for MS3
. . .
CS PAGING (MS4) from SGSN
1c <-----------------------------------------
2c <------------------------------------------ for MS4
CS PAGING (MS5) from MSC
1d <-----------------------------------------
2d <------------------------------------------ for MS5
. . .
3a <-------------PCH,pgr1--------------
(MS1,MS2)

3b <-------------PCH,pgr2--------------
(MS3,MS4,MS5)
4
(Packet) Access Grant scenario for all MSs
which answer to a (Packet) Paging Request
PACKET PAGING RESPONSE (MS1, MS2, MS3)

5 ----------PDTCH-------------------->------------------------------------------>-------------------------------------->
Stop T3313
for Msn
PAGING RESPONSE (MS4, MS5)
5a ----------SDCCH-------------------->------------------------------------------>------------------------------------->
Stop T3113
for Msn
Note: - This scenario is for one (P)CCCH-group only.

The following, describes the general Packet Paging behaviour within the BSS. The mechanism is
similar to the CS Paging mechanism, therefore only differences between CS and PS Paging will be
described. The given number refers to the steps as indicated on the left side of the scenario:
1-1b Same as CS Paging, the only difference is that BSC receives it from MFS instead of MSC.

NOTIFICATION
0439_03_Rel.doc0439_02.doc
3BK 11202 0439 DSZZA 30/81

10/01/2007
1c In specific circumstances (see end of section 2.3.3), CS Paging may transit through SGSN and
MFS.
1d See CS Paging section 3.1.1.
2-2b Same as CS Paging, the only differences are: the Packet Paging is sent by the MFS to the
BSC. The BSC forwards a PAGING COMMAND message to the BTS if:
- no primary MPDCH is configured in the cell
- or if a primary MPDCH is configured in the cell and T_EST_MDPCH_PROC timer is running
(see section 3.1.5).
A PTMSI (Packet TMSI) is used instead of a TMSI. Nevertheless, the following point shall be
observed for (P)TMSI and IMSI:
• The BSC shall set the Packet Page Indication bit to 1 for each Abis PAGING COMMAND
message constructed with a received PS Paging from MFS.
• The BSC shall set the Packet Page Indication bit to 0 for each Abis PAGING COMMAND
message constructed with a received CS Paging, whatever its origin, i.e. MSC or MFS.
2c See CS Paging section 3.1.1. with the following condition: when the MFS sends a CS PAGING
message to the BSC, the BSC forwards a PAGING COMMAND message to the BTS if:
(see section 3.1.5).
2d See CS Paging section 3.1.1.
PAGING REQUEST messages use some of the "rest octets" bits to transfer the "Packet Page
Indication" value. There is a Packet Page Indication IE for each possible IMSI identity included
in a PAGING REQUEST TYPE 1 & 2 messages. Because different sets of numbers are used
for PTMSI and TMSI identities, there is no need to have this IE for such a temporary Identity. A
MS attached to both GSM and GPRS shall have one TMSI identity AND one PTMSI identity.
CS and PS Paging messages can be sent in the same PAGING REQUEST message with the
following combinations:
- PAGING REQUEST TYPE 1 may contain 1 or 2 (Packet) Paging Messages.
- PAGING REQUEST TYPE 2 may up to 3 (Packet) Paging Message.
Note: there are some restrictions among all the possible combinations (see section 3.2.2).

transmitted.

transmitted.
4 Access Grant scenario is performed as described in section 3.1.4.
5 See GPRS specification 3GPP TS 04.64.
5a After the successful allocation of the SDCCH see ref.[9].


NOTIFICATION
0439_03_Rel.doc0439_02.doc
3BK 11202 0439 DSZZA 31/81

10/01/2007
MSs Radio Channel BTS BSC [MSC] / [SGSN via MFS]
PS PAGING (MS1)
1 <-----------------------------------------
Start T3113
for MS1
PS PAGING (MS3)
1a <-----------------------------------------
Start T3113
for MS3
PS PAGING (MS2)
1b <-----------------------------------------
Start T3113
for MS2
CS PAGING (MS4)
1c <-----------------------------------------
Start T3113
for MS4
CS PAGING (MS5)
1d <-----------------------------------------
Start T3113
for MS5
Stop
MS3,pgr2; MS2,pgr1; MS4, pgr2; MS5, pgr2)
2 <------------------------------------------
Start
expired
MS7,pgr4; MS8,pgr4; MS9, pgr4)
2b <------------------------------------------
Start
3a <-------------PCH,pgr1--------------
(MS1,MS2)

3b <-------------PCH,pgr2--------------
(MS3,MS4,MS5)
4
(Packet) Access Grant scenario for all MSs
which answer to a (Packet) Paging Request
PACKET PAGING RESPONSE (MS1, MS2, MS3)

5 ----------PDTCH-------------------->------------------------------------------>-------------------------------------->
Stop T3313
for Msn
PAGING RESPONSE (MS4, MS5)
5a ----------SDCCH-------------------->------------------------------------------>------------------------------------->

NOTIFICATION
0439_03_Rel.doc0439_02.doc
3BK 11202 0439 DSZZA 32/81

10/01/2007
Stop T3113
for Msn
Note: - This scenario is for one (P)CCCH-group only.

The following, describes the general Packet Paging behaviour within the BSS. The mechanism is
similar to the CS Paging mechanism, therefore only differences between CS and PS Paging will be
described. The given number refers to the steps as indicated on the left side of the scenario:
1-1d Same as CS Paging, the only difference is that BSC receives it from MFS instead of MSC.
1c In specific circumstances (see end of section, CS Paging may transit through SGSN and MFS.
2-2b Same as CS Paging, the only differences are: the Packet Paging is sent by the MFS to the
BSC. The BSC forwards a MULTIPLE PAGING COMMAND message to the BTS if:
(see section .A PTMSI (Packet TMSI) is used instead of a TMSI. Nevertheless, the
following point shall be observed for (P)TMSI and IMSI:
• The BSC shall set the Packet Page Indication bit to 1 for each Abis PAGING Information
message constructed with a received PS Paging from MFS.
• The BSC shall set the Packet Page Indication bit to 0 for each Abis PAGING Information
message constructed with a received CS Paging, whatever its origin, i.e. MSC or MFS.
3a
PAGING REQUEST messages use some of the "rest octets" bits to transfer the "Packet Page
Indication" value. There is a Packet Page Indication IE for each possible IMSI identity included
in a PAGING REQUEST TYPE 1 & 2 messages. Because different sets of numbers are used
for PTMSI and TMSI identities, there is no need to have this IE for such a temporary Identity. A
MS attached to both GSM and GPRS shall have one TMSI identity AND one PTMSI identity.
CS and PS Paging messages can be sent in the same PAGING REQUEST message with the
following combinations:
- PAGING REQUEST TYPE 1 may contain 1 or 2 (Packet) Paging Messages.
Note: there are some restrictions among all the possible combinations (see section 3.2.20).

transmitted.

transmitted.
4 Access Grant scenario is performed as described in section..
5 See GPRS specification 3GPP TS 04.64.
5a After the successful allocation of the SDCCH see ref..

NOTIFICATION
0439_03_Rel.doc0439_02.doc
3BK 11202 0439 DSZZA 33/81

10/01/2007
3.1.3 Circuit Access scenario
MSs Radio Channel BTS BSC
CHANNEL REQUEST
1 ------------------------RACH--------------------------->
CHANNEL REQUIRED
2 ------------------------------------------------------------>
CHANNEL ACTIVATION
3 <------------------------------------------------------------
CHANNEL ACTIVATION ACK
4 ------------------------------------------------------------>
IMMEDIATE ASSIGN COMMAND (IMMEDIATE ASSIGNMENT)
5 <------------------------------------------------------------
IMMEDIATE ASSIGNMENT
6 <-----------------------AGCH----------------------------
CHANNEL REQUEST
7 ------------------------RACH--------------------------->
CHANNEL REQUIRED
8 ------------------------------------------------------------>
CHANNEL ACTIVATION
9 <------------------------------------------------------------
10 ------------------------------------------------------------>
11 <------------------------------------------------------------
12 IMMEDIATE ASSIGNMENT
<-----------------------AGCH----------------------------
CHANNEL REQUEST
13 ------------------------RACH--------------------------->
CHANNEL REQUIRED
14 ------------------------------------------------------------>
CHANNEL ACTIVATION
15 <------------------------------------------------------------
16 ------------------------------------------------------------>
17 <------------------------------------------------------------
IMMEDIATE ASSIGNMENT EXTENDED
18 <-----------------------AGCH----------------------------
CHANNEL REQUEST (MS a)

19 ------------------------RACH--------------------------->
CHANNEL REQUIRED
20 ------------------------------------------------------------>
IMMEDIATE ASSIGN COMMAND (IMMEDIATE ASSIGNMENT REJECT)
21 <------------------------------------------------------------
CHANNEL REQUEST (MS b)
22 ------------------------RACH--------------------------->
CHANNEL REQUIRED
23 ------------------------------------------------------------>
IMMEDIATE ASSIGN COMMAND (IMMEDIATE ASSIGNMENT REJECT)
24 <------------------------------------------------------------
IMMEDIATE ASSIGNMENT REJECT

NOTIFICATION
0439_03_Rel.doc0439_02.doc
3BK 11202 0439 DSZZA 34/81

10/01/2007
25 <-----------------------AGCH----------------------------
Start T3122 (both MS a and MS b)
Note: This scenario is for one CCCH-group only.
The Access Grant Procedure is described here mainly in relation to the RACH and AGCH and only
the successful or unsuccessful allocation of a SDCCH is shown. For the detailed protocol behaviour,
see ref.[9]. The given numbers correspond to the steps as indicated on the left side of the scenario:
3.1.3.1 Immediate Assignment
After the MS has transmitted the CHANNEL REQUEST message, it starts the timer T3120.
Remark: "T3120" appellation is GSM phase 1. It has been removed in GSM phase 2, but the
timer still exists and is expressed in terms of number of RACH timeslots to wait before sending a
new CHANNEL REQUEST message. The T3120 range of values differs following the Tx_integer
value.
If the MS does not receive an IMMEDIATE ASSIGNMENT or IMMEDIATE ASSIGNMENT

EXTENDED or IMMEDIATE ASSIGNMENT REJECT message corresponding to one of its 3 last
random accesses within T3120, it repeats the CHANNEL REQUEST message and restarts
T3120 as long as it is allowed by the Max_retrans parameter.
After the last CHANNEL REQUEST message sending (i.e. Max_retrans reached), the MS waits
for a response from the network during a certain time before returning to idle mode. For a phase
1 MS, this time is not strictly defined, for a phase 2 MS, it corresponds to T3126 timer.
Note: Tx_integer and Max_retrans are elements within the RACH control parameter IE, the MS
had received in the SYSTEM INFORMATION TYPE 1, 2, 3 and 4 messages.
2 After the correct decoding of a CHANNEL REQUEST message, the BTS generates the
CHANNEL REQUIRED message with:
- Channel number IE: timeslot(TN), on which the message was received (0,2,4,6).
- Request reference IE: Absolute frame number modulo 42432 on which the CHANNEL
REQUEST message was received, and random reference generated by the MS and received
in the CHANNEL REQUEST message (see 3GPP TS 44.018 [2] § 10.5.2.30).
- Timing advance IE: measured delay between the beginning of the RACH timeslot which
carries that CHANNEL REQUEST message and the receipt of the Access Burst.
3 The BSC sends the CHANNEL ACTIVATION message to the BTS, in order to allocate a
dedicated signalling connection (SDCCH) to the MS. For SDCCH allocation procedure, see
ref.[9].
4 The BTS sends the CHANNEL ACTIVATION ACK message to the BSC, in order to acknowledge
the SDCCH allocation procedure.
5 After this successful SDCCH allocation, the IMMEDIATE ASSIGN COMMAND is sent to the BTS.
The Request reference IE within the Immediate Assign Info IE is set to the value received in the
CHANNEL REQUIRED message before. The MS will compare this Request reference value with
its own one in order to see if it corresponds to one of its 3 former CHANNEL REQUEST
messages.
6 The BTS generates the corresponding ACCESS GRANT message. This ACCESS GRANT
message has to be sent on the same CCCH timeslot (0,2) as the one where the CHANNEL
REQUEST message has been received. That means, that the timeslot in the Channel Number IE
of the IMMEDIATE ASSIGN COMMAND message must be the same than in the CHANNEL
REQUIRED message.

NOTIFICATION
0439_03_Rel.doc0439_02.doc
3BK 11202 0439 DSZZA 35/81

10/01/2007
ACCESS GRANT messages are stored in the AGCH queue. The dequeuing is done following the
‘bottom to top’ principle. For queuing method, refer to sections 3.1.3.2, 3.1.3.3 and 3.2.3.2.
Each AGCH block occurrence, the first ACCESS GRANT message in the AGCH queue is sent
on Radio Interface. If the AGCH queue is empty (no pending ACCESS GRANT message), then a
LAPDm - Fill frame (see 3GPP TS 04.06 [1]) is sent.
The total number of ACCESS GRANT messages in the AGCH queue should not exceed AG_Q.
Parameter definition and calculation is defined in section 3.2.4. If the AGCH queue is full with
IMMEDIATE ASSIGNMENT EXTENDED and IMMEDIATE ASSIGNMENT messages, and the
incoming IMMEDIATE ASSIGNMENT message cannot be merged with any IMMEDIATE
ASSIGNMENT message of the queue, it is discarded.
If no AGCH is reserved (BS_AG_BLKS_RES = 0), the BTS has to send ACCESS GRANT
messages over PCH blocks. See section 3.2.4 for details on the pre-emption mechanism.
3.1.3.2 Immediate Assignment Extended
Note: This paragraph is only valid for CS IMMEDIATE ASSIGNMENT messages.
7 to 11 & 12 to 16: Same as 1 to 5.
17 When an IMMEDIATE ASSIGNMENT message is received from the BSC, the BTS checks if
there are already ACCESS GRANT messages in the AGCH queue.
• If the incoming IMMEDIATE ASSIGNMENT message can be merged with an IMMEDIATE
ASSIGNMENT message already present in the AGCH queue, starting from the first to be
sent, an IMMEDIATE ASSIGNMENT EXTENDED message is created and replaces the
IMMEDIATE ASSIGNMENT message in the queue. Two IMMEDIATE ASSIGNMENT
messages can always be merged into one IMMEDIATE ASSIGNMENT EXTENDED
message except if:
⇒ Both granted channels are hopping and their Mobile Allocations (MA) are different,
⇒ Both granted channels are hopping with the same MA, but this MA is longer than 5 bytes
(1 byte length + 4 bytes data).
• If the incoming IMMEDIATE ASSIGNMENT cannot be merged with any of the ones in the
queue, then it is placed in the queue after all the (EGPRS) PACKET UPLINK ASSIGNMENT,
IMMEDIATE ASSIGNMENT and IMMEDIATE ASSIGNMENT EXTENDED messages, but
before all IMMEDIATE ASSIGNMENT REJECT messages (see 3.2.3.2).
3.1.3.3 Immediate Assignment Reject
18 to 19 & 21 to 22: Same as 1 to 2.
20 & 23: The Immediate Assignment Reject feature may be activated or deactivated by the
parameter EN_IM_ASS_REJ (only CS Immediate Assignment Reject messages):
• EN_IM_ASS_REJ = false: No IMMEDIATE ASSIGNMENT REJECT message are generated
by the BSC and sent to the BTS.
• EN_IM_ASS_REJ = true: IMMEDIATE ASSIGNMENT REJECT messages may be generated
by the BSC and sent to the BTS.
If there is no free SDCCH available and parameter EN_IM_ASS_REJ is set to "true" and the
Request Reference IE indicates an establishment cause different from "Answer to paging", the
BSC sends an IMMEDIATE ASSIGN COMMAND message to the BTS containing an
IMMEDIATE ASSIGNMENT REJECT message. The 4 Request Reference IEs (see IMMEDIATE
ASSIGNMENT REJECT message structure in section 3.2.3.2) are set to the value received in the
CHANNEL REQUIRED message. The 4 Wait Indication values are set to the value which
correspond to the establishment cause indicated in the RA part of the Request Reference IE:
• WI_EC if the establishment cause is "Emergency Call"

NOTIFICATION
0439_03_Rel.doc0439_02.doc
3BK 11202 0439 DSZZA 36/81

10/01/2007
• WI_CR if the establishment cause is "Call Re-establishment"

• WI_OC if the establishment cause is "Originating Call"
• WI_OP if the establishment cause is "Other Procedures"
24 Each time an IMMEDIATE ASSIGNMENT REJECT message is built by the BSC, the 4 Request
Reference IEs are set to one common value and the 4 Wait Indication IEs are set also to one
common value. As the BSC is not synchronised with the Radio Interface multiframe, it cannot
wait for several CHANNEL REQUIRED messages to reject together: it is up to the BTS, if the
occasion arises, to merge IMMEDIATE ASSIGNMENT REJECT messages received from the
BSC into IMMEDIATE ASSIGNMENT REJECT messages sent on the Radio Interface. Then it
should set one Request Reference IE and one Wait Indication IE to the values of one
IMMEDIATE ASSIGNMENT REJECT message. It is possible to send from 1 to 4 IMMEDIATE
ASSIGNMENT REJECT messages in the same time on the Radio Interface (see section 3.2.3.2).
The IMMEDIATE ASSIGNMENT REJECT message is sent on the Radio Interface on AGCH.
When an MS receives an IMMEDIATE ASSIGNMENT REJECT containing a Request Reference
corresponding to one of its last 3 random accesses, it initializes timer T3122 with the Wait
Indication value associated to the Request Reference and then stops to send any random access
until T3122 expires (except in case of a new Emergency Call attempt, when the rejected call
attempt is NOT an Emergency Call attempt).
Note: For a phase 2 mobile, another timer (T3126) is set after reception of an IMMEDIATE
ASSIGNMENT REJECT message or if it has sent the maximum allowed number of CHANNEL
REQUEST messages. As long as T3126 is running, the phase 2 MS accepts IMMEDIATE
ASSIGNMENT or IMMEDIATE ASSIGNMENT EXTENDED messages corresponding to one of its
3 last random accesses. It returns to idle mode at the expiration of T3126.

NOTIFICATION
0439_03_Rel.doc0439_02.doc
3BK 11202 0439 DSZZA 37/81

10/01/2007
3.1.4 Packet Access scenario
MSs Radio Channel BTS BSC MFS
1 CHANNEL REQUEST (PS)

or
EGPRS PACKET CHANNEL REQUEST
--------------RACH---------------->
2 CHANNEL REQUIRED
-------------------------------------->
3 CHANNEL REQUEST
------------------------------------------>
4 CHANNEL ASSIGNMENT UL
((EGPRS) PACKET UPLINK
ASSIGNMENT)
<------------------------------------------
5 IMMEDIATE ASSIGN COMMAND(IMM.ASS.
((EGPRS)PACKET UPLINK ASSIGNMENT))
<--------------------------------------
6 IMMEDIATE ASSIGNMENT
((EGPRS) PACKET UPLINK ASSIGNMENT)
<--------------AGCH----------------
1a - 6a: Repeat procedure described between 1 and 6.
7a Any LLC Frame (To SGSN)

---------------------------------------------------GCH------------------------------------------------------------------>
8a CHANNEL ASSIGNMENT DL
(PACKET DOWNLINK ASSIGNMENT)
<------------------------------------------
9a IMMEDIATE ASSIGN COMMAND ( IMM.ASS.
((PACKET DOWNLINK ASSIGNMENT))
<--------------------------------------
10a IMMEDIATE ASSIGNMENT
(PACKET DOWNLINK ASSIGNMENT)
<---------------PCH/AGCH-----------------
1b CHANNEL REQUEST (PS, MS a)

----------------RACH-------------->
2b CHANNEL REQUIRED
-------------------------------------->
3b CHANNEL REQUEST
------------------------------------------>
4b CHANNEL ASSIGNMENT UL
(IMMEDIATE ASSIGNMENT REJECT)
<------------------------------------------
5b IMMEDIATE ASSIGN COMMAND
(IMMEDIATE ASSIGNMENT REJECT)
<--------------------------------------
1c CHANNEL REQUEST (MS b)
----------------RACH-------------->
2c CHANNEL REQUIRED
-------------------------------------->
6b IMMEDIATE ASSIGNMENT REJECT

NOTIFICATION
0439_03_Rel.doc0439_02.doc
3BK 11202 0439 DSZZA 38/81

10/01/2007
<--------------AGCH----------------
Start T3122 for MS a
Note: This scenario is for one (P)CCCH-group only.
The Packet Access Grant Procedure is described here mainly in relation to the RACH, PCH and
AGCH and only the successful or unsuccessful allocation of a PDTCH is shown. For the detailed
protocol behaviour, refer to 3GPP GPRS specifications and ref.[9]. The mechanism is similar to the
CS Access Grant mechanism, therefore only differences between CS and PS Access Grant will be
described. The given numbers correspond to the steps as indicated on the left side of the scenario:
3.1.4.1 (EGPRS) Packet Uplink / Downlink Assignment
1–6 Same as CS Access Grant, the only differences are:

- MFS allocation procedure and T3140 (See section 3.2.3.2) instead of T3120. If the MS
does not receive an IMMEDIATE ASSIGNMENT message containing a (EGPRS)
PACKET UPLINK ASSIGNMENT, or an IMMEDIATE ASSIGNMENT REJECT message,
corresponding to one of its 3 last random accesses within T3140, it repeats the
CHANNEL REQUEST (PS) message or the EGPRS PACKET CHANNEL REQUEST
message and restarts T3140 as long as it is allowed by the Max_retrans parameter.
- In case of EGPRS PACKET CHANNEL REQUEST message, the "Request reference" IE
is not coded and used the same way than for CS, as it can't contain the 11 bits access
burst sent by the MS. Additional OIE and fields containing the extended RA are added to
the CHANNEL REQUIRED and IMMEDIATE ASSIGNMENT messages: see ref.[19] &
[22] for details.
- The BTS sends the (EGPRS) PACKET UPLINK ASSIGNMENT messages through the
AGCH channel. It uses the same waiting queues as CS IMMEDIATE ASSIGNMENT
messages, but cannot be merged into an IMMEDIATE ASSIGNMENT EXTENDED
message. It has the same priority as CS IMMEDIATE ASSIGNMENT messages and thus
higher priority than IMMEDIATE ASSIGNMENT REJECT messages (either CS or PS).
1a - 6a Same as 1 to 6, expect that the CHANNEL REQUEST (PS) cause is "answer to paging".
7a Any LLC frame is sent to the SGSN, through the MFS, as a Packet Paging Response.
8a The MFS sends the PACKET DOWNLINK ASSIGNMENT message to the BSC.
9a The BSC sends the IMMEDIATE ASSIGN COMMAND message to the BTS.
10a The BTS sends the PACKET DOWNLINK ASSIGNMENT within IMMEDIATE ASSIGNMENT
messages either on the PCH channel when the MS is in DRX mode or on AGCH when the
MS is in non-DRX mode, depending on the presence of Paging Group IE (see section 2.1.6).
1b - 5b When there is no free GPRS resource to perform the requested Assignment, the MFS may
send to the GPRS MS, an IMMEDIATE ASSIGNMENT REJECT message. This message is
built exactly like the ones for CS Immediate Assignment Rejection.
4b The Wait-Indication field shall be filled with only following parameter:
WI_PR: the establishment cause is "Packet Reject” procedure.

NOTIFICATION
0439_03_Rel.doc0439_02.doc
3BK 11202 0439 DSZZA 39/81

10/01/2007
2c If the GSL link between the BSC and the MFS is absent or failed, the BSC shall discard the
CHANNEL REQUEST messages received with a packet establishment cause.
6b See CS Immediate Assignment Reject procedure. The only differences are:

- the GPRS MS timers: T3142 is used instead of T3122, and T3146 is used instead of
T3126,
- In case of EGPRS PACKET CHANNEL REQUEST message, the "Request reference" IE
is not coded and used the same way than for CS, as it can't contain the 11 bits access
burst sent by the MS. Additional fields, containing the extended RA, are added to the
IMMEDIATE ASSIGNMENT REJECT message (see ref.[19] for details).
3.1.5 Dynamic configuration of PBCCH & PCCCH
At any time, the MFS may request the allocation of MPDCH in a cell supporting GPRS traffic. The
MFS is in charge to activate/deactivate MPDCH, and to notify the BSC about the
allocation/deallocation of primary MPDCH (i.e. MPDCH supporting PBCCH) sending UPDATE SI13
REQUEST message on BSCGP interface (see ref.[15]).
3.1.5.1 Activation of a primary MPDCH
3.1.5.1.1 Case of Paging command


NOTIFICATION
0439_03_Rel.doc0439_02.doc
3BK 11202 0439 DSZZA 40/81

10/01/2007
UPDATE SI13 REQUEST

1 <-----------------------------------------
BCCH INFO (SYST INFO TYPE 13)
2 <------------------------------------------
3 Start T_MPDCH_
EST_PROC timer
UPDATE SI13 CONF.
4 ----------------------------------------->
SYST INFO TYPE 13
5 <-------------BCCH--------------
PS / CS PAGING
6 <-----------------------------------------
PAGING COMMAND
7 <-------------------------------------
8 <-------------PCH,pgr1--------------
PACKET PAGING RESPONSE
9 ----------PDTCH-------------------->----------------------------------->-------------------------------------->
10 T_MPDCH_
EST_PROC expiry
PS / CS PAGING
11 <-----------------------------------------
not forwarded
anymore in this cell.
1 The MFS triggers the primary MPDCH establishment in the BSC sending UPDATE SI13
REQUEST message to the BSC.
2 & 5 The BSC shall update the SYSTEM INFORMATION TYPE 13 including the new PBCCH
characteristics to be provided to the MS, and sends it to the BTS in the BCCH INFORMATION
message. See ref.[14].
3 The BSC starts the timer T_MPDCH_EST_PROC, which corresponds to the time needed by
the MS to get the new information broadcast in SYSTEM INFORMATION TYPE 13 message.
During this period, the BSS can’t be sure whether the MS is listening the BCCH/CCCH or the
PBCCH/PCCCH of the primary MPDCH. The CS / PS PAGING messages are thus sent on
both CCCH and PCCCH channels during this period.
4 The BSC acknowledges towards the MFS the primary MPDCH establishment command,
sending the UPDATE SI13 CONFIRM message.
5 See point 2.
6 - 9 Upon receipt of CS PAGING or PS PAGING message from the MFS (i.e. on GSL link), the BSC
checks for each cell of the RA if it exists a primary MPDCH configured in the cell, and if the
timer T_MDCH_EST_PROC is running.
The CS / PS PAGING message is sent to the MS on PCH channel when:
- a primary MPDCH is configured in the cell and the timer T_MDCH_EST_PROC is running.

NOTIFICATION
0439_03_Rel.doc0439_02.doc
3BK 11202 0439 DSZZA 41/81

10/01/2007
10 After the T_MDCH_EST_PROC expiry, the BSC is sure that the MS is now getting information
on the primary MPDCH of the cell.
11 Upon receipt of CS PAGING or PS PAGING message from the MFS (i.e. on GSL link), the BSC
does the same checks than above (see 6 - 9).
The CS / PS PAGING message is not sent to the MS on PCH channel (because it has been
sent by the MFS itself on PPCH channel) when:
- a primary MPDCH are configured in the cell and the timer T_MDCH_EST_PROC is not
running.
3.1.5.1.2 Case of Multiple Paging command.

UPDATE SI13 REQUEST

1 <-----------------------------------------
2 <------------------------------------------
3 Start T_MPDCH_
EST_PROC timer
UPDATE SI13 CONF.
4 ----------------------------------------->
SYST INFO TYPE 13
5 <-------------BCCH--------------
PS / CS PAGING
6 <-----------------------------------------
MULTIPLE PAGING COMMAND
7 <-------------------------------------
8 <-------------PCH,pgr1--------------
9 ----------PDTCH-------------------->----------------------------------->-------------------------------------->
10 T_MPDCH_
EST_PROC expiry
PS / CS PAGING
11 <-----------------------------------------
not forwarded
anymore in this cell.

NOTIFICATION
0439_03_Rel.doc0439_02.doc
3BK 11202 0439 DSZZA 42/81

10/01/2007
2 & 5 The BSC shall update the SYSTEM INFORMATION TYPE 13 including the new PBCCH
characteristics to be provided to the MS, and sends it to the BTS in the BCCH INFORMATION
message.
3 The BSC starts the timer T_MPDCH_EST_PROC, which corresponds to the time needed by
the MS to get the new information broadcast in SYSTEM INFORMATION TYPE 13 message.
During this period, the BSS can’t be sure whether the MS is listening the BCCH/CCCH or the
PBCCH/PCCCH of the primary MPDCH. The CS / PS PAGING messages are thus sent on
both CCCH and PCCCH channels during this period.
4 The BSC acknowledges towards the MFS the primary MPDCH establishment command,
sending the UPDATE SI13 CONFIRM message.
5 See point 2.
6 - 9 Upon receipt of CS PAGING or PS PAGING message from the MFS (i.e. on GSL link), the BSC
checks for each cell of the RA if it exists a primary MPDCH configured in the cell, and if the
timer T_MDCH_EST_PROC is running.
The CS / PS PAGING message is sent to the MS on PCH channel when:
- a primary MPDCH is configured in the cell and the timer T_MDCH_EST_PROC is running.
Upon receipt of a CS/PS PAGING , BSC put the paging information in the queue for each cell
with the above conditions. The paging information is sent to cell within a MULTIPLE PAGING
COMMAND.
Message when either the NB_MAX_MSG_MULTIPLE_PAGING_COMMAND or a timeout
T_SEND_MULTIPLE_PAGING_CMD is reached.
10 After the T_MDCH_EST_PROC expiry, the BSC is sure that the MS is now getting information
on the primary MPDCH of the cell.
11 Upon receipt of CS PAGING or PS PAGING message from the MFS (i.e. on GSL link), the BSC
does the same checks than above (see 6 - 9).
The CS / PS PAGING message is not sent to the MS on PCH channel (because it has been
sent by the MFS itself on PPCH channel) when:
- a primary MPDCH are configured in the cell and the timer T_MDCH_EST_PROC is not
running.
3.1.5.2 Deactivation of a primary MPDCH
3.1.5.2.1 Case of Paging command


NOTIFICATION
0439_03_Rel.doc0439_02.doc
3BK 11202 0439 DSZZA 43/81

10/01/2007
UPDATE SI13 REQUEST

1 <-----------------------------------------
2 <------------------------------------------
UPDATE SI13 CONF.
3 ----------------------------------------->
SYST INFO TYPE 13
4 <-------------BCCH--------------
PS / CS PAGING
5 <-----------------------------------------
no MPDCH
in the cell
PAGING COMMAND
6 <------------------------------------------
7 <-------------PCH,pgr1--------------
8 ----------PDTCH-------------------->------------------------------------------>-------------------------------------->
1 The MFS triggers the primary MPDCH release in the BSC sending UPDATE SI13 REQUEST
message to the BSC.
2 & 4 The BSC shall update the SYSTEM INFORMATION TYPE 13 removing the PBCCH radio
configurations, and sends it to the BTS in the BCCH INFORMATION message. See ref.[14].
3 The BSC acknowledges towards the MFS the primary MPDCH release command, sending the
UPDATE SI13 CONFIRM message.
5-8 Upon receipt of CS PAGING or PS PAGING message from the MFS (i.e. on GSL link), the BSC
checks for each cell of the RA if it exists a primary MPDCH configured in the cell: the CS / PS
PAGING message is sent to the MS on PCH channel as no primary MPDCH is configured in the
cell anymore.
3.1.5.2.2 Case of Multiple Paging command.


NOTIFICATION
0439_03_Rel.doc0439_02.doc
3BK 11202 0439 DSZZA 44/81

10/01/2007
UPDATE SI13 REQUEST

1 <-----------------------------------------
2 <------------------------------------------
UPDATE SI13 CONF.
3 ----------------------------------------->
SYST INFO TYPE 13
4 <-------------BCCH--------------
PS / CS PAGING
5 <-----------------------------------------
no MPDCH
in the cell
6 <------------------------------------------
7 <-------------PCH,pgr1--------------
8 ----------PDTCH-------------------->------------------------------------------>-------------------------------------->
1 The MFS triggers the primary MPDCH release in the BSC sending UPDATE SI13 REQUEST
message to the BSC.
2 & 4 The BSC shall update the SYSTEM INFORMATION TYPE 13 removing the PBCCH radio
configurations, and sends it to the BTS in the BCCH INFORMATION message..
3 The BSC acknowledges towards the MFS the primary MPDCH release command, sending the
UPDATE SI13 CONFIRM message.
5-8 Upon receipt of CS PAGING or PS PAGING message from the MFS (i.e. on GSL link), the BSC
checks for each cell of the RA if it exists a primary MPDCH configured in the cell: the CS / PS
PAGING message is sent to the MS on PCH channel as no primary MPDCH is configured in the
cell anymore.
The paging information are queued up per cell , collected and transfered together within a
PAGING MULTIPLE COMMAND when aither the
NB_MAX_MSG_MULTIPLE_PAGING_COMMAND or a timeout
T_SEND_MULTIPLE_PAGING_CMD is reached.

NOTIFICATION
0439_03_Rel.doc0439_02.doc
3BK 11202 0439 DSZZA 45/81

10/01/2007
3.1.6 Notification scenarios

3.1.6.1 Notification with Channel Description
The BSC sends NOTIFICATION messages (with VGCH description) to the mobile stations as soon
as the VGCH has been established in the cell.
It occurs when :
- the MSC asks the BSC to allocate immediately the common VGCH in each cell of the group call
area. If the MSC disallowed any further de-allocation of the VGCH, all the further NOTIFICATION
messages will include the channel description. If the MSC allows further de-allocation of the VGCH,
the NOTIFICATION messages will contain the channel description as long as the BSC detects a
listener in the cell.
- the MSC asked the BSC to allocate with delay allowed a VGCS call. The NOTIFICATION messages
will include the channel description as soon as a listener initiated the notification response procedure,
ie asked for the VGCH establishment on-demand.
MS BTS BSC MFS

The BSS has allocated a VGCH in the cell
(1)
NOTIFICATION COMMAND
<---------------------------------------
(1) NOTIFICATION/NCH
<------------------------------
(1) NOTIFICATION/PCH
<------------------------------
(2)
DATA REQUEST
(Notification/FACCH)
<--------------------------------------
(2) NOTIFICATION/FACCH
<------------------------------
(3)
PERIODIC NOTIF REQ
(NCH)
<------------------------------
1 The first NOTIFICATION message (with the VGCH channel description) is broadcast in the
cell on NCH. Then, periodically, the BTS continue the notification process on NCH as long
as the group call is alive.
A particular scheduling of the notification messages is performed by the BTS :
The three first notifications (for a new given group call) have a higher priority over other
notifications (for the on-going group calls). So they are sent before.
In addition the high priority VGCS call (ie priority above a configured threshold), then the BTS
sends the NOTIFICATION on PCH
2 One NOTIFICATION message may be also sent on FACCH of all other on-going VGCS
calls and on FACCH of all other on-going standard point-to-point calls.The Notification on
FACCH is one-shot message: It is not repeated. (see 3.2.5.3)
3 Afterwards, the NOTIFICATION messages (with the VGCH channel description) are
broadcast periodically on NCH

NOTIFICATION
0439_03_Rel.doc0439_02.doc
3BK 11202 0439 DSZZA 46/81

10/01/2007
3.1.6.2 Notification without Channel Description
The BSC sends NOTIFICATION messages (without VGCH description) to the mobile stations as
soon as a VGCS call has been initiated, but without any VGCH currently established in the cell.
It occurs when :
- the MSC asks the BSC to allocate immediately the common VGCH in each cell of the group call
area, allowing further de-allocation of the VGCH. The BSS will use the listener detection procedure
(see “Uplink reply procedure” of ref 24) in order to know if a VGCS mobile station is still in the cell. If
not, the BSC will release the VGCH in the cell and ask the BTS to send NOTIFICATION messages
containing no channel description as long as no listener asks for the VGCH establishment.
- the MSC asked the BSC to allocate with delay allowed a VGCS call. The NOTIFICATION messages
will not include any channel description as long as no mobile station asks for the VGCH
establishment.
MS BTS BSC MFS

The BSS has NOT yet allocated a VGCH in the cell
(1)
<---------------------------------------
<------------------------------
(1) NOTIFICATION/PCH
<------------------------------
(2)
DATA REQUEST
(Notification/FACCH)
<--------------------------------------
(2) NOTIFICATION/FACCH
<------------------------------
(3)
PERIODIC NOTIF REQ
(NCH)
<------------------------------
1 The first NOTIFICATION message (without the VGCH channel description) is broadcast in
the cell on NCH. Then, periodically, the BTS continue the notification process on NCH as
long as the group call is alive.
A particular scheduling of the notification messages is performed by the BTS :
The three first notifications (for a new given group call) have a higher priority over other
notifications (for the on-going group calls). So they are sent before.
In addition the high priority VGCS call (ie priority above a configured threshold), then the BTS
sends the NOTIFICATION on PCH
2 One NOTIFICATION message may be also sent on FACCH of all other on-going VGCS
calls and on FACCH of all other on-going standard point-to-point calls.The Notification on
FACCH is one-shot message: It is not repeated. (see 3.2.5.3)
3 Afterwards, the NOTIFICATION messages (without the VGCH channel description) are
broadcast periodically on NCH

NOTIFICATION
0439_03_Rel.doc0439_02.doc
3BK 11202 0439 DSZZA 47/81

10/01/2007
3.1.6.3 Notification Response Procedure with Uplink Busy
When a VGCS Mobile Station moves to a cell, where the NOTIFICATION messages doesn’t contain
any VGCH channel description, it will use the notification response procedure in order to retrieve the
VGCH description and be able to receive the group call.
MS BTS BSC MFS
Periodic notification (without the VGCH description)
(1)
PERIODIC NOTIF REQ
(NCH)
<---------------------------
A MS initiates the Notification Response procedure
(2)
CHANNEL REQUEST
---------------------------->
(2) CHANNEL REQUIRED
-------------------------------------->
(2) CHANNEL ACTIVATION
<--------------------------------------
(2) CHANNEL ACTIVATION ACK
-------------------------------------->
(2) IMMEDIATE ASSIGN CMD
<--------------------------------------
(2) IMMEDIATE ASSIGN
<----------(SDCH)---------
(2) SABM (Notif response)
--------(FACCH)-----------
>
(2) UA (Notif response) ESTABLISH INDICATION
<-------(FACCH)----------- ------------------------------------->
BSC allocates the VGCS Channel in the cell
(3)
CHANNEL ACTIVATION (VGCH)
<--------------------------------------
(3) CHANNEL ACTIVATION ACK VGCS/VBS
--------------------------------------> ASSIGNMENT RES
------------------------->
BSS asks the MS to join the new VGCH
(4)
DR (CHANNEL RELEASE)
<--------------------------------------
(4) CHANNEL RELEASE
(VGCH)
<---------------------------
First notification (with the VGCH description)
(5)
<------------------------------------------
---
<------------------------------

NOTIFICATION
0439_03_Rel.doc0439_02.doc
3BK 11202 0439 DSZZA 48/81

10/01/2007
Periodic notifications (with the VGCH description)

(6)
PERIODIC NOTIF REQ
(NCH)
<---------------------------
In the previous figure, only the notifications on NCH are mentioned.
1 NOTIFICATION messages (without the VGCS TCH channel description) are broadcast
periodically in the cell on NCH.
2 A VGCS capable mobile station moves to the cell, it sends the Channel Request message
(establishment cause: “procedures that can be completed with a SDCCH”) to establish the
dedicated signaling channel with the BSS.
3 The BSC allocates the VGCS channel.
The BSC sends VGCS ASSIGNMENT RESULT message to MSC.
4 The BSS sends the Channel Release message (with the VGCS channel description) to ask
the MS switching from the old channel (SDCCH channel) to the new channel (VGCS
channel).
5 The first Notification message (with the VGCS channel description) is sent on NCH.
6 NOTIFICATION messages (with the VGCS TCH channel description) are broadcast
periodically on NCH.

NOTIFICATION
0439_03_Rel.doc0439_02.doc
3BK 11202 0439 DSZZA 49/81

10/01/2007
3.1.6.4 Notification Response Procedure with Uplink Free
MS BTS BSC MFS

Periodic notification (without the VGCH description)
(1) PERIODIC NOTIF REQ
(NCH)
<---------------------------
A MS initiates the Notification Response procedure
(2) CHANNEL REQUEST
---------------------------->
(2) CHANNEL REQUIRED
-------------------------------------->
(2) CHANNEL ACTIVATION
<--------------------------------------
(2) CHANNEL ACTIVATION ACK
-------------------------------------->
(2) IMMEDIATE ASSIGN CMD
<--------------------------------------
(2) IMMEDIATE ASSIGN
<----------(SDCH)---------
(2) SABM (Notif response)
--------(FACCH)-----------
>
(2) UA (Notif response) ESTABLISH INDICATION
<-------(FACCH)---------- ------------------------------------->
BSC allocates the VGCS Channel in the cell
(3) CHANNEL ACTIVATION (VGCH)
<--------------------------------------
(3) CHANNEL ACTIVATION ACK VGCS/VBS
--------------------------------------> ASSIGNMENT RES
------------------------->
BSS asks the MS to join the new VGCH
(4) DR (CHANNEL RELEASE)
<--------------------------------------
(4) CHANNEL RELEASE
(VGCH)
<---------------------------
First notification (with the VGCH description)
(5) NOTIFICATION COMMAND
<------------------------------------------
<------------------------------
BSS send the first Uplink Free
(6) VGCS DOWNLINK REQUEST
(Uplink Free)
<------------------------------------------
(6) UPLINK FREE
<------------------------------
Periodic notifications (with the VGCH description)
(7) PERIODIC NOTIF REQ
(NCH)
<---------------------------

NOTIFICATION
0439_03_Rel.doc0439_02.doc
3BK 11202 0439 DSZZA 50/81

10/01/2007
Periodic sending of Uplink Free

(8) UPLINK FREE
<------------------------------
1-5 Same as the Uplink Busy case ( see 3.1.6.3).
6 The BSC starts the timer T_NOTIF_RESPONSE_DELAY (Note).

At this timer expiry, the BSC asks the BTS to send the first occurrence of Uplink Free
message;
Note: the timer T_NOTIF_RESPONSE_DELAY gives the MS a chance to receive the

immediately transmitted Uplink Free
7 Same as the Uplink Busy case ( see 3.1.6.3)
8 The subsequent occurrences of Uplink Free message are repeated on FACCH

NOTIFICATION
0439_03_Rel.doc0439_02.doc
3BK 11202 0439 DSZZA 51/81

10/01/2007
3.2 Detailed Behaviour
3.2.1 (Packet) Paging procedure

3.2.1.1 (Packet) Paging message destinations
This task has to be done by the BSC. For the message format checking, refer to [10].
The Cell Identifier list discriminator IE determines the cells performing the paging procedure.
The LAC (Location Area Code) is mostly used for CS Paging, the RAC (Routine Area Code) is mostly
used for PS Paging and “CS Paging via SGSN in network mode I operation mode”. Nevertheless, the
BSC shall have the knowledge of RA informations, because it can receive, from the MFS, a CS
Paging message using a RAC as identifier. This is due to the following:
The GPRS-MFS entity only has to know the GPRS cell identities. A RA may contain NO-GPRS cells.
Thus it is impossible for the MFS to convert the RA identifier to an exhaustive cell list before sending
it to the BSC.
When the BSC receives a CS PAGING or a PS PAGING from the MFS, it sends a PAGING
COMMAND or MULTIPLE PAGING COMMAND (see note 1) message only on the cells of the given
area (RA, LA, all) where no PCCCH channel is active or where a primary MPDCH is active with
T_MPDCH_EST_PROC(BSC) is running (see section 3.1.5). This is the case when the PS/CS
PAGING Cell Identifier List indicates an RA, an LA or the "whole BSS" and even when it indicates
only one cell.
For each PS Paging message received from MFS, the BSC shall discard the message sending to
cells not supporting GPRS. This is performed by checking the EN_GPRS parameters on each
concerned cell. If EN_GPRS = True, the PS Paging is sent to the cell. If EN_GPRS = False, the PS
Paging is not sent to the cell.
Note 1:
This command applies to Evolium BTS, when NB_MAX_MSG_MULTIPLE_PAGING_CMD > 1 (more
• Paging messages received from MSC:
Cell Identifier list Performed task

Discr. = MCC+MNC+LAC For each C.G.I, which points to one specific cell, the
+CI (C.G.I) paging task is performed. If not all the C.G.Is are known
in the BSC, the paging is performed on all cells
controlled by the BSC.
Discr. = LAC +CI Same task as for C.G.I,
Except that only LAC + CI is checked.
Discr = CI Same task as for C.G.I,
Except that only CI is checked.
Discr. = MCC+MNC On each cell of the defined L.A.Is, the paging task is
+LAC (L.A.I) performed. If not all the L.A.Is are known in the BSC, the
paging is performed on all cells controlled by the BSC.
Discr. = LAC Same task as for L.A.I,
Except that only LAC is checked.
Discr. = all Paging is performed on all cells, controlled by the BSC.
Discr. = no cell No cell is associated with the paging transaction
No IE present or incorrect Paging is performed on all cells, controlled by the BSC.
When Discr. = MCC + MNC + LAC + CI (C.G.I.), the cell identifier list may contain cells from different
PLMN (i.e. having different (MCC, MNC) couples. The BSC only pages the MS in the cells of the own
PLMN.

NOTIFICATION
0439_03_Rel.doc0439_02.doc
3BK 11202 0439 DSZZA 52/81

10/01/2007
Upon reception of PAGING messages from the MSC, the BSC may trigger the in-band paging (if
EN_INBAND_PAGING is enabled) to warn the terminated MS, currently involved in a VGCS call,
about a new point-to-point call. The eMLPP Priority OIE of the received PAGING message must be
above the INBAND_PAGING_THR.
• Paging messages received from MFS :
Cell Identifier list Performed task

Discr. = MCC+MNC+LAC+CI For each C.G.I, which points to one specific cell, the
(C.G.I) paging task is performed. If not all the C.G.Is are known
in the BSC, the paging is performed on all cells
controlled by the BSC.
Discr. = MCC+MNC+LAC (L.A.I) On each cell of the defined L.A.Is, the paging task is
performed. If not all the L.A.Is are known in the BSC, the
paging is performed on all cells controlled by the BSC.
Discr. = MCC+MNC+LAC+RAC On each cell of the defined R.A.Is, the paging task is
(R.A.I) performed. If not all the R.A.Is are known in the BSC,
the paging is performed on all cells controlled by the
BSC.
Discr. = all Paging is performed on all cells, controlled by the BSC.
Discr. = no cell No cell is associated with the paging transaction
No IE present or incorrect Paging is performed on all cells, controlled by the BSC.
3.2.1.2 (Packet) Paging group computation
This task has to be performed by the BSC. The (Packet) Paging Group which is included in the
PAGING COMMAND message is calculated with the following equation:
PAGING_GROUP = (( IMSI mod 1000 ) mod ( BS_CC_CHANS * N )) mod N

PACKET_PAGING_GROUP = PAGING_GROUP
with:
- NUM_PB_PER_51_MFRMS = number of PCH blocks per CCCH multiframe
- BS_PA_MFRMS = nb. of CCCH multiframes between transmission of the same paging group
- N = NUM_PB_PER_51_MFRMS * BS_PA_MFRMS
- BS_CC_CHANS = number of CCCH timeslots
3.2.1.3 (P)CCCH Group computation
This task has to be performed by the BSC.(P)CCCH Group is calculated with the following formula:
CCCH_GROUP = ((IMSI mod 1000) mod (BS_CC_CHANS * N)) div N

PCCCH_GROUP = CCCH_GROUP
The correspondance between (P)CCCH_GROUP and TS is given in table 2 section 2.2.2.

NOTIFICATION
0439_03_Rel.doc0439_02.doc
3BK 11202 0439 DSZZA 53/81

10/01/2007
3.2.1.4 Mapping of logical channels to physical channels
This task has to be performed by the BTS.

When PAGING COMMAND or MULTIPLE PAGING COMMAND (see note 2) messages are received
from the BSC, the BTS proceeds to the mapping of logical channels to physical channels. The
following formula indicates the indexes of the Paging Groups which can send PAGING REQUEST
messages in the (51-frames) multiframe indexed by the absolute Frame Number ‘FN’:
PAGING_GROUP div (NUM_PB_PER_51_MFRMS) = (FN div 51) mod (BS_PA_MFRMS)
An index calculation which is used to gain access to the appropriate paging block is given below. This
paging block index is used to access the following table to obtain the actual CCCH block index.
Paging Block Index = PAGING_GROUP mod (NUM_PB_PER_51_MFRMS)
COMBINED BS_AG_ N_PB_PER Paging Block Index ‘X’ → CCCH Block Index ‘BX’
_
CCCH BLKS_RES 51_MFRMS 0 1 2 3 4 5 6 7 8
False 0 (Note 1) 9 B0 B1 B2 B3 B4 B5 B6 B7 B8
False 1 8 B1 B2 B3 B4 B5 B6 B7 B8
False 2 7 B2 B3 B4 B5 B6 B7 B8
False 3 6 B3 B4 B5 B6 B7 B8
False 4 5 B4 B5 B6 B7 B8
False 5 4 B5 B6 B7 B8
False 6 3 B6 B7 B8
False 7 2 B7 B8
True 0 3 B0 B1 B2
True 1 2 B1 B2
True 2 1 B2
Note 1: BS_AG_BLKS_RES may be set to 0, when CCCH_CONF = 0 (i.e. CCCH Not combined),
only if no CBCH is configured in the cell. Otherwise, BS_AG_BLKS_RES shall be greater
than 0 (see 3GPP TS 45.002 [3] & ref.[20]).
Note 2:
This command applies to Evolium BTS, when NB_MAX_MSG_MULTIPLE_PAGING_CMD >
1 (more than one Paging command ).
3.2.2 (Packet) Paging queues and PDA queues

Within the BTS, all the available Paging Groups are represented by FIFO queues (up to 81 x 2 FIFO
queues, i.e. one queue per CCCH Group and per message type (Paging or PDA)). The FIFO queues
are initialized at every configuration time when receiving the SYSTEM INFORMATION TYPE 3
message with parameter modifications. It means that pending PAGING REQUEST and PACKET
DOWNLINK ASSIGNMENT messages are lost when a new configuration is set.
• The maximum number of PAGING REQUEST messages that may be stored on one single queue
per Paging Group is:
  Max (T _ PAG _ PS , T _ PAG _ CS)  
PAG _ Q = Max1, INT   
  (tmf ∗ BS _ PA _ MFRS) 

NOTIFICATION
0439_03_Rel.doc0439_02.doc
3BK 11202 0439 DSZZA 54/81

10/01/2007
• The maximum number of PACKET DOWNLINK ASSIGNMENT messages that may be stored on
one single queue per Paging Group is:
  T _ PDA 
PDA _ Q = Max1, INT   
  (tmf ∗ BS _ PA _ MFRS ) 
• And furthermore the total number of pending messages is limited to:

∑ Nb_PAG ≤ PG_FULL
all the paging groups
∑ Nb_PDA ≤ PDA_FULL
all the paging groups
where:
- INT(x) means ‘taking the integer part of the value’
- T_PAG_PS is the maximum time a PS PAGING message can remain in the paging queue.
- T_PAG_CS is the maximum time a CS PAGING message can remain in the paging queue.
- T_PDA is the maximum time a PACKET DOWNLINK ASSIGNMENT message (to be sent on
PCH) can remain in the PDA queue.
- tmf = 235 ms is the approximate duration of one CCCH multiframe.
- PG_FULL is the maximum number of all PAGING REQUEST messages that can be stored in the
BTS per CCCH Group.
- PDA_FULL is the maximum number of all PACKET DOWNLINK ASSIGNMENT messages that
can be stored in the BTS per CCCH Group.
- Nb_PAG is the number of pending PAGING REQUEST messages in the paging queue.
- Nb_PDA is the number of pending PACKET DOWNLINK ASSIGNMENT messages (to be sent
on PCH) in the PDA queue.
Message filtering in the queue
In order to respect the maximum allowed queuing time for each type of incoming messages, the
following tests are performed:
− An incoming CS PAGING message is put in the paging queue only if:
(Nb_PAG + Nb_PDA) * tmf * BS_PA_MFRMS < T_PAG_CS (1)
− An incoming PS PAGING message is put in the paging queue only if:
(Nb_PAG + Nb_PDA) * tmf * BS_PA_MFRMS < T_PAG_PS (2)

− When an incoming PAGING or PACKET DOWNLINK ASSIGNMENT message is received, the
BTS may discard it according to the maximum length of the queue defined by PAG_Q and
PDA_Q and the maximum number of pending messages defined by PAG_FULL and PDA_FULL.
Eq. (1) and (2) are not checked on receipt of a PACKET DOWNLINK ASSIGNMENT message. As
PACKET DOWNLINK ASSIGNMENT messages have an higher priority than PAGING messages, it
may happen that a PAGING message is queued longer than the filtering timer T_PAG_CS or
T_PAG_PS.
All the PAGING REQUEST messages are stored in one queue according to the Paging Group and
the CCCH Group. When a PAGING COMMAND or MULTIPLE PAGING COMMAND (see note 1)
message is received from BSC, an algorithm manages the storage of pending PAGING COMMAND
or MULTIPLE PAGING COMMAND (see note 1) messages into PAGING REQUEST messages. The
principle is to merge, if possible, the maximum number of PAGING COMMAND messages to one

NOTIFICATION
0439_03_Rel.doc0439_02.doc
3BK 11202 0439 DSZZA 55/81

10/01/2007
PAGING REQUEST message (which enables up to 4 MSs to be paged at the same time). Following
combinations are possible for each type of PAGING REQUEST message:
TYPE 1 TYPE 2 TYPE 3

- IMSI - (P)TMSI, (P)TMSI, (P)TMSI - (P)TMSI, (P)TMSI, (P)TMSI, (P)TMSI
- (P)TMSI - (P)TMSI, (P)TMSI,IMSI
- IMSI,IMSI (®)
- IMSI, (P)TMSI
- (P)TMSI, (P)TMSI
(®) This combination can be used for 2 CS Paging using any IMSI numbers. An IMSI PS Paging can
only be merged with another IMSI PS or CS Paging, if it remains some bytes left for Packet Page
Indication field in PAGING REQUEST type 1 rest octets. 1 PS Paging and 1 PS or CS Paging using
both full IMSI numbers on 16 bytes cannot be merged into 1 PAGING REQUEST type 1 message,
because there is no room left for rest octets.
The PAGING REQUEST message is generated with the PAGING COMMAND messages of the
concerned Paging Group occurrence.
The BTS builds a new PAGING REQUEST message containing the first PAGING COMMAND
message available.
- If it is possible to complete the PAGING REQUEST message, the message is rebuilt including
the next PAGING COMMAND message with its new MS identity ((P)TMSI or IMSI).
- If it is not possible to complete the PAGING REQUEST message because the message is
already full (for example IMSI/IMSI, (P)TMSI/(P)TMSI/IMSI or
(P)TMSI/(P)TMSI/(P)TMSI/(P)TMSI), or if it is not possible to merge the next PAGING
COMMAND message in the PAGING REQUEST message (for example IMSI/(P)TIMSI + IMSI),
the PAGING REQUEST message is closed and ready to be sent on Radio Interface.
PACKET DOWNLINK ASSIGNMENT messages sent on PCH (when paging group is known) have
priority over PAGING REQUEST messages. Each Paging Group occurrence, the BTS checks first if
there is pending PACKET DOWNLINK ASSIGNMENT to send, and then if there is pending PAGING
REQUEST to send. The above priority rule applies to the PCH, only when pre-emption by Access
Grant messages is not enabled. When pre-emption of paging sub-channels by Access Grant
messages is enabled, the priority rules must consider all messages which can be sent on the CCCH.
The priority rules with pre-emption are defined in section 3.2.4.
Thus, the decision to build and store a new PAGING REQUEST in the queue, or to discard a
received PAGING COMMAND, shall depend on the filtering system described in a preceding
paragraph. Because PACKET DOWNLINK ASSIGNMENT messages (with paging group) have the
highest priority, the Access Grant pre-emption, when BS_AG_BLKS_RES = 0, or when
AG_PREMPT_PCH is true, is not taken into account in the described filtering system (see
section 3.2.4).
Note 1:
This command applies to Evolium BTS, when NB_MAX_MSG_MULTIPLE_PAGING_CMD > 1 (more
Important Notes:
• A PACKET DOWNLINK ASSIGNMENT message is never merged with other messages (either a
PAGING message or another PACKET DOWNLINK ASSIGNMENT message).
• When constructing a new PAGING REQUEST message, there is no rearrangement of the
PAGING COMMAND messages contained in all PAGING REQUEST of the Paging Queue in
order to maximize the use of the PAGING REQUEST messages. A Paging Group occurrence is
time critical due to its real time constraint. Therefore it is given a higher priority to have PAGING
REQUEST messages ready than to optimize the content of the PAGING REQUEST messages.

NOTIFICATION
0439_03_Rel.doc0439_02.doc
3BK 11202 0439 DSZZA 56/81

10/01/2007
• The Alcatel BSS only supports Packet Paging Group computation using standard GSM DRX
mode (i.e. with BS_PA_MFRMS) for Packet Paging and Packet Downlink Assignment messages
on CCCH. The appropriate PCCCH_GROUP and Packet Paging Group are equal to
CCCH_GROUP and Paging Group. Thus they are computed in the BSC for Packet Paging and
Packet Downlink Assignment messages exactly as for CS Paging messages.
3.2.3 Access Grant procedure

3.2.3.1 CS Access Grant timers
T3120: This timer is used by the MS to wait after sending a CHANNEL REQUEST. It is stopped at
the reception of an IMMEDIATE ASSIGNMENT or an IMMEDIATE ASSIGNMENT
EXTENDED or an IMMEDIATE ASSIGNMENT REJECT message. When T3120 expires, the
mobile will be allowed to send a new channel request (if Max_retrans value is not reached).
Phase 1 MS:
T3120 = T1 + T_Random
T1 is set to: - 250 ms in case of non combined CCCH
- 350 ms in case of combined CCCH / SDCCH
T_Random is set to a random value ‘n’ which gives the number of RACH timeslots between
the T1 expiry and the end of the period T3120 (n = 0 ... Tx_integer (range:3-50) - 1).
Phase 2 MS:
This timer name has been removed from GSM phase 2 TS. Two timers expressed in number
of available RACH timeslots replace it .The MS sends maximally M + 1 CHANNEL
REQUEST messages on the RACH in a way such that:
• The number of RACH timeslots between initiation of the Immediate Assignment
procedure and the first CHANNEL REQUEST message (excluding the slot containing the
message itself) is a random value drawn for each new initial assignment initiation with
uniform probability distribution in the set {0, 1, ..., max (T,8) - 1};
• The number of RACH timeslots between two successive CHANNEL REQUEST
messages (excluding the slots containing the messages themselves) is a random value
drawn for each new transmission with uniform probability distribution in the set {S, S + 1,
..., S + T - 1};
- T is the value of the O&M parameter Tx_integer broadcast on the BCCH,

- M is the value of the O&M parameter Max_retrans broadcast on the BCCH,
- S is a parameter depending on the CCCH configuration and on the value of Tx_integer as
defined in following table:
Values of parameter S
Tx_integer Non combined CCCH combined CCCH/SDCCH
3,8,14,50 55 41
4,9,16 76 52
5,10,20 109 58
6,11,25 163 86
7,12,32 217 115
T3122: MS timer used to delay the Random Access procedure when an IMMEDIATE ASSIGNMENT
REJECT message has been received. This timer is started with the value in Wait Indication
IE.
If the IMMEDIATE ASSIGNMENT REJECT message has not been received for an
emergency call connection attempt, the MS may attempt to enter the dedicated mode for an
emergency call in the same cell before T3122 has expired.

NOTIFICATION
0439_03_Rel.doc0439_02.doc
3BK 11202 0439 DSZZA 57/81

10/01/2007
T3126: MS timer indicating the waiting time after receiving an IMMEDIATE ASSIGNMENT REJECT
message, or after sending the last CHANNEL REQUEST message before going back to idle
mode. This timer name is newly defined by GSM phase 2 TS.
Phase 1 MS:
After receiving an IMMEDIATE ASSIGNMENT REJECT message, a phase 1 MS goes back
directly to idle mode. After sending the last CHANNEL REQUEST message allowed, the MS
waits a "certain time" not strictly defined by 3GPP TS 44.018. There is no explicit value given
for this timer in this recommendation.
Phase 2 MS:
The minimum value of this timer is equal to the time taken by T+2S RACH timeslots. S and T
are defined in T3120 paragraph. The maximum value of this timer is 5 seconds.
3.2.3.2 Packet Access Grant timers
The Packet Access Grant timers have the same functions as CS Access Grant timers. GPRS MS
shall be at least Phase 2 MS. Therefore, the following description concerns only Phase 2 MS.
(T3140): Like T3120 for Phase 2 MS, this timer is not a real timer. The mean waiting time between
two “Packet” Channel Requests is computed as described in section 3.2.3.1, T3120 / Phase
2.
T3142: Same function as T3122 for Packet Transfer.
T3146: Same function as T3126 / Phase 2 for Packet Transfer.
T3190: This timer is used by the MS to monitor the receipt of downlink RLC data blocks with the
assigned DL TFI for packet downlink assignment on AGCH for a MS in non-DRX mode.
The BTS receives an IMMEDIATE ASSIGN COMMAND message from the BSC containing an
IMMEDIATE ASSIGNMENT REJECT message. The BTS checks if there are already some
IMMEDIATE ASSIGNMENT REJECT messages pending in the AGCH queue:
• If no, the BTS creates a new entry at the top of the AGCH queue with the IMMEDIATE
ASSIGNMENT REJECT message received from the BSC. If the AGCH queue is full, the BTS
discards the IMMEDIATE ASSIGNMENT REJECT message.
• If yes, the BTS checks how many different Request References are already present in the last to
be sent IMMEDIATE ASSIGNMENT REJECT message in the AGCH queue.
- If the message is full (i.e. 4 different Request References are present), then the BTS creates
a new entry at the end of the AGCH queue with the IMMEDIATE ASSIGNMENT REJECT
message received from the BSC. If the AGCH queue is full, the BTS discards the
- If the message is not full (i.e. n different Request References are present, 0 < n < 4), then the
BTS copies the Request Reference and Wait Indication received from the BSC respectively
at Request Reference n+1 and Wait Indication n+1 positions in the already stored
IMMEDIATE ASSIGNMENT REJECT message. The following figure illustrates this
mechanism:

NOTIFICATION
0439_03_Rel.doc0439_02.doc
3BK 11202 0439 DSZZA 58/81

10/01/2007
Top of the AGCH queue Top of the AGCH queue

IMMEDIATE
ASSIGN
COMMAND
(IMMEDIATE
ASSIGNMENT
REJECT
IMMEDIATE ASSIGNMENT for MS 11) IMMEDIATE ASSIGNMENT
REJECT for MS 9 & 10 REJECT for MS 9, 10 & 11
IMMEDIATE ASSIGNMENT ⇓ IMMEDIATE ASSIGNMENT
REJECT for MS 5, 6, 7 & 8 REJECT for MS 5, 6, 7 & 8
IMMEDIATE ASSIGNMENT IMMEDIATE ASSIGNMENT
REJECT for MS 1, 2, 3 & 4 REJECT for MS 1, 2, 3 & 4
before after
The (EGPRS) PACKET UPLINK ASSIGNMENT, PACKET DOWNLINK ASSIGNMENT, IMMEDIATE

ASSIGNMENT and IMMEDIATE ASSIGNMENT EXTENDED messages have always priority over the
IMMEDIATE ASSIGNMENT REJECT message. This rule implies the following BTS behaviours:
- If an IMMEDIATE ASSIGNMENT or a (EGPRS) PACKET UPLINK ASSIGNMENT or a PACKET

DOWNLINK ASSIGNMENT message (for MS in non-DRX mode) is received from the BSC and
some IMMEDIATE ASSIGNMENT REJECT messages are present in the AGCH queue, then the
incoming message shall be inserted between the last to be sent (EGPRS) PACKET UPLINK
ASSIGNMENT, PACKET DOWNLINK ASSIGNMENT, IMMEDIATE ASSIGNMENT or
IMMEDIATE ASSIGNMENT EXTENDED message and the first to be sent IMMEDIATE
ASSIGNMENT REJECT message. The following figure illustrates this mechanism :

IMMEDIATE IMMEDIATE ASSIGNMENT
ASSIGN REJECT 2
COMMAND
IMMEDIATE ASSIGNMENT (IMMEDIATE IMMEDIATE ASSIGNMENT
REJECT 2 ASSIGNMENT) REJECT 1
IMMEDIATE ASSIGNMENT IMMEDIATE ASSIGNMENT 1
REJECT 1
PACKET UPLINK ⇓ PACKET UPLINK
ASSIGNMENT 1 ASSIGNMENT 1
EXTENDED 1 EXTENDED 1
before after
- If an IMMEDIATE ASSIGNMENT or a (EGPRS) PACKET UPLINK ASSIGNMENT or a PACKET

DOWNLINK ASSIGNMENT message (for MS in non-DRX mode) is received from the BSC and
the AGCH queue is full, then, if some IMMEDIATE ASSIGNMENT REJECT messages are
present in the queue, the last to be sent IMMEDIATE ASSIGNMENT REJECT message is
discarded and the incoming message is inserted between the last to be sent (EGPRS) PACKET
UPLINK ASSIGNMENT, PACKET DOWNLINK ASSIGNMENT, IMMEDIATE ASSIGNMENT or
IMMEDIATE ASSIGNMENT EXTENDED message and the first to be sent IMMEDIATE
ASSIGNMENT REJECT message (if any). The following figure illustrates this mechanism:

NOTIFICATION
0439_03_Rel.doc0439_02.doc
3BK 11202 0439 DSZZA 59/81

10/01/2007

IMMEDIATE ASSIGNMENT IMMEDIATE IMMEDIATE ASSIGNMENT
REJECT 3 ASSIGN REJECT 2
COMMAND
IMMEDIATE ASSIGNMENT (IMMEDIATE IMMEDIATE ASSIGNMENT
REJECT 2 ASSIGNMENT) REJECT 1
IMMEDIATE ASSIGNMENT IMMEDIATE ASSIGNMENT 1
REJECT 1
PACKET UPLINK ⇓ PACKET UPLINK
ASSIGNMENT 1 ASSIGNMENT 1
EXTENDED 1 EXTENDED 1
before after
3.2.3.4 Packet Uplink/Downlink Assignment message destination
For each (EGPRS) Packet Uplink Assignment and Packet Downlink Assignment message received
from MFS, the BSC shall check if the cell supports GPRS. This is performed by checking the
EN_GPRS parameter on the concerned cell.
- If EN_GPRS = True, the (EGPRS) Packet Uplink Assignment or Packet Downlink Assignment
message is sent to the cell.
- If EN_GPRS = False, the (EGPRS) Packet Uplink Assignment or Packet Downlink Assignment
message is not sent to the cell and the message is discarded by the BSC.
Nevertheless, it must be noted that no check is performed on the availability, or not, of a PCCCH on
the concerned cell. As the PCCCH existence may be dynamically set or unset, some Packet
Assignment can be received by the BSC, for a cell whose PCCCH was just added. In order to fulfil
the Packet Assignment procedure, the message shall still be sent on CCCH, even if it should have
been sent on PCCCH.
3.2.4 Access Grant queues

Within the BTS, there is one Access Grant queue per CCCH Group (Warning: There is only one
CCCH Group in this release). An Access Grant queue is only initialized at configuration time when
receiving a SYSTEM INFORMATION TYPE 3 message with CCCH_CONF parameter modification. It
means that pending ACCESS GRANT messages are lost when such a new configuration is set.
The maximum number of ACCESS GRANT messages that may be stored in the Access Grant queue
is:
  Max (T_IA, T_PUA) ∗ X  

AG_Q = Max  1, INT   
  tmf 
And furthermore the total number of pending messages is limited to: Nb_AG ≤ AG_FULL .
where:
- INT means ‘taking the integer part of the value’.
- X = BS_AG_BLKS_RES if BS_AG_BLKS_RES <> 0 and if AG_PREMPT_PCH = false.
X = 3 (combined CCCH), or X = 9 (not combined CCCH) if BS_AG_BLKS_RES = 0 or if
AG_PREMPT_PCH = true.
- T_IA is the maximum time a CS IMMEDIATE ASSIGNMENT message or IMMEDIATE
ASSIGNMENT EXTENDED can remain in the access grant queue.

NOTIFICATION
0439_03_Rel.doc0439_02.doc
3BK 11202 0439 DSZZA 60/81

10/01/2007
- T_PUA is the maximum time a (EGPRS) PACKET UPLINK ASSIGNMENT message or a

PACKET DOWNLINK ASSIGNMENT message (to be sent on AGCH) can remain in the access
grant queue.
- tmf = 235 ms (approximate duration of one CCCH multiframe).
- AG_FULL is the maximum number of all ACCESS GRANT messages that can be stored in the
BTS per CCCH Group.
- Nb_AG is the number of pending IA, IAE, PDA and PUA messages in the access grant queue.
Note that IAR shall not be considered in this computation because of their lower priority against
IA, IAE, PDA and PUA.
Message filtering in the access grant queue
In order to respect the maximum allowed queuing time for each type of incoming access grant
messages, the following tests are performed:
− An incoming IMMEDIATE ASSIGNMENT message or IMMEDIATE ASSIGNMENT EXTENDED

message is put in the access grant queue only if:
(Nb_AG * tmf) / X < T_IA
− An incoming (EGPRS) PACKET UPLINK ASSIGNMENT message or an incoming PACKET

DOWNLINK ASSIGNMENT message (to be sent on AGCH) is put in the access grant queue only
if:
(Nb_AG * tmf) / X < T_PUA
− When an incoming message is inserted in the access grant queue, the BTS may discard it
according to the maximum length of the queue defined by AG_Q and the maximum number of
pending access grant messages defined by AG_FULL.
In the message filtering, the BTS does not taken into account the AGCH blocks occupied by system
information sent on the BCCH Extended, if activated in the serving cell.
Pre-emption mechanism:
The pre-emption mechanism of Access Grant over PCH is enabled when BS_AG_BLKS_RES = 0 or
AG_PREMPT_PCH = true.
Note: The purpose of the flag AG_PREMPT_PCH is to be able to use the pre-emption mechanism
when the BCCH Extended is configured or when the CBCH is supported in a non-combined CCCH
configuration (the value BS_AG_BLKS_RES = 0 is not allowed in these cases). The value
AG_PREMPT_PCH = true shall be allowed only with BS_AG_BLKS_RES = 1, in order to minimise
the disturbance of the paging sub-channels. The OMC is in charge of checking this last rule, the BTS
does not check it.
When pre-emption is enabled, the BTS has to send Access Grant Messages on possibly reserved
AGCH blocks and over PCH sub-channels. The following priority relation is defined (1=highest
priority, 4=lowest priority) for messages to send on the PCH sub-channels.
1. PACKET DOWNLINK ASSIGNMENT messages sent on PCH (when paging group is
known, i.e for MS in DRX mode)
2. Access Grant messages (on FIFO basis):

− IMMEDIATE ASSIGNMENT
− IMMEDIATE ASSIGNMENT EXTENDED

NOTIFICATION
0439_03_Rel.doc0439_02.doc
3BK 11202 0439 DSZZA 61/81

10/01/2007
− PACKET UPLINK ASSIGNMENT

− EGPRS PACKET UPLINK ASSIGNMENT
− PACKET DOWNLINK ASSIGNMENT sent on AGCH (when paging group is not
known, i.e. for MS in non-DRX mode)
3. Immediate Assignment Reject messages
4. CS PAGING (including NOTIFICATION/PCH message for VGCS) and PS PAGING

messages
At each paging group occurrence, the BTS will use the above priority to search the waiting queue for
a pending message.
3.2.5 Notification procedure

When a VGCS call is established, Notification messages are required to be sent in all the cells
involved in the call. The cells involved are determined by the MSC which is aware of the Group Call
Area. MSC requests a Call Controlling SCCP connection in each of the BSSs containing the cells,
some or all of which comprise the Group Call Area.
The BSC, on receiving the VGCS Setup Request will setup the VGCS Context for the Call. For each
cell involved in the VGCS Call, a VGCS Channel Assignment Request is then received by the BSC.
Depending on the Assignment Requirement, a channel is assigned, or delayed until a listening MS is
detected in the cell.
On completion of the VGCS Channel activation, Notification Procedure is started to inform the MS in
the cell of the VGCS Call. The Notification Messages sent in the procedure contains the Channel
Description of the VGCS Channel. If the Assignment Requirement specifies, Allocation on Demand,
then a VGCS Channel is not allocated immediately, but the Notification Messages are still sent, but
without any VGCS Channel Description.
The BSC sends the Notification Command to inform the BTS to start the Notification Procedure.
3.2.5.1 Notification on NCH
Notification messages are scheduled and sent on the NCH ensuring:
- the three, first initial notifications (the first for a given group call) have priority over subsequent
notifications (for the on-going group calls).
- any on-going group call in the cell is periodically notified on the NCH
3.2.5.2 Notification on PCH
In addition to the initial notification messages on NCH, the BSS sends the notification messages on
the PCH. To support the reduced NCH monitoring (see § 2.1.5 and §) the BTS inserts the actual NLN
and NLN status parameter, as received from the latest NOTIFICATION CMD, in the Rest Octets of all
PAGING REQUEST TYPE 1, 2 (only if space available in rest octets) and 3 messages sent on PCH
This provides an indication of any change of information sent on the NCH (3GPP TS 44.018, sec.
3.3.3.2), ie NLN(PCH).The group Call Information can be included only in the PAGING REQUEST
TYPE 1 message.
For VGCS calls which have a priority above the parameter NOTIF_PCH_THR, the BTS tries to send
in addition initial notifications on PCH according to the following rules:

NOTIFICATION
0439_03_Rel.doc0439_02.doc
3BK 11202 0439 DSZZA 62/81

10/01/2007
The scheduling of the high priority group call information is provided separately per paging group.
On reception of a high priority notification, the BTS tries, for ONE paging group cycle, to send the
high priority notification in a PAGING REQUEST TYPE 1 message to each paging group:
- If no PAGING REQUEST message is queued for a paging group, then the BTS generates a
PAGING REQUEST TYPE 1 message with "Mobile Identity" coded as "No Identity" (3GPP TS
24.008 clause 10.5.1.4). and the high priority notification in the P1 Rest Octets.
- If a PAGING REQUEST TYPE 1 message is queued to be send as next paging request for the
paging group, then the BTS appends the high priority notification in the P1 Rest Octets.
- If a PAGING REQUEST TYPE 2 or TYPE 3 is queued to be send as next paging request for the
paging group, then no specific notification is sent to this paging group (the BTS will NOT rebuild
the queued messages). Only the P2/P3 Rest Octets are updated with the actual NLN and NLN
status values as it is done for all paging request messages (see Note).
If more than one VGCS call have a priority above the threshold, then the same rules as above apply
but the group call information for these VGCS groups are used round robin so that all are notified on
the PCH equally, i.e. with the same frequency of occurrence. After one notification has been sent to
each paging group (i.e. one paging group cycle has been finished) the notification on PCH is stopped
until another initial notification for a high priority VGCS call is received.
Note: If the group call information can not be included in the next PAGING REQUEST sent to a
paging group, then the mobiles could have already read all notifications from the NCH (triggered by
NLN(PCH)) before the next PAGING REQUEST is sent to this paging group. So there is no speed up
for a high priority notification if it could not be included in the very first PAGING REQUEST to a
paging group.
Note: The Alcatel BSS does not require to generate an additional PAGING REQUEST TYPE 1 if
already a TYPE 2 or TYPE 3 message is queue for transmission to a paging group. The Alcatel BSS
does not require to rebuild/reassemble a queued TYPE 2 (or 3) message into one TYPE 1 message
including the notification and a separate TYPE 1 or TYPE 2 message containing the rest information
of the original queue message.
3.2.5.3 Notification on FACCH
The parameter EN_INBAND_NOTIF, if enabled, allows sending of initial notification messages, for
new VGCS calls, on FACCH, providing the priority of the new call is above or equal to the threshold
defined by the parameter NOTIF_FACCH_OTHER_VGCS_CALL_THR.
The BSS sends an initial notification message to inform mobile stations, which are partaking in these
calls, of the new voice group call that is being set up in the cell. Notification on FACCH is a one-shot
message, sent only once (to ensure voice quality) :
- on FACCH of all other on-going voice group calls in the cell

- on FACCH of dedicated TCH of any talking subscribers of all other on-going voice group calls in
the cell.
3.2.6 Notification Response procedure
Notification messages are sent without the VGCS channel description in the case of :
- a VGCS Channel Allocation on-demand, and

- a VGCS Channel has been de-allocated due to no listener in the cell.

NOTIFICATION
0439_03_Rel.doc0439_02.doc
3BK 11202 0439 DSZZA 63/81

10/01/2007
3.2.6.1 Notification Response Procedure with Uplink Busy
Notification messages are sent without the VGCS Channel description until a mobile station has
responded to the Notification message. Following the Notification Response procedure, a successful
VGCS Channel allocation will mean that the VGCS Channel description is included in the subsequent
Notification messages.
3.2.6.2 Notification Response Procedure with Uplink Free
Same as for Notification Response procedure with Uplink Busy.

NOTIFICATION
0439_03_Rel.doc0439_02.doc
3BK 11202 0439 DSZZA 64/81

10/01/2007
Telecom and O&M interworking
3.2.7 Configuration Management

The following table shows all the system parameters within a BSS which have an influence on the
Paging, Immediate Assignment and Notification procedures and the affected tasks, if they are
modified.
System parameter Configuration message Meaning of the parameter Infos

CCCH_CONF Control Chl. descr./ Type of CCCH configuration : see note 1
SYS INFO TYPE 3 0 : one physical channel, not
combined ;
1 : one physical channel,
combined ;
2 : two physical channels, not
combined ;
other value : not supported
in this release
BS_AG_BLKS_RES Control Chl. descr./ num. of reserved AGCH see note 1
SYS INFO TYPE 3 within a CCCH multiframe.
BS_PA_MFRMS Control Chl. descr./ period in num. of multiframes see note 1
SYS INFO TYPE 3 of a Paging Group repetition.
Max retrans RACH-control-parameter/ Num. of random access transparent
SYS INFO TYPE 1,2,3,4 attempts of the MS. for the BSS.
see note 2
Tx integer RACH-control-parameter/ Used to calculate the random transparent
SYS INFO TYPE 1,2,3,4 access values for T3120 and for the BSS.
T3126 timers. see note 2
DRX_TIMER_MAX Non-DRX control param. Set the maximum value for the
for GPRS transfers MS timer used for non-DRX
SYS INFO TYPE 13 mode after downlink transfers.
NUMBER_NCH_BLOCKS This parameter defines the see note 2
maximum number of blocks
reserved for NCH.
EN_INBAND_NOTIF Flag to disable/enable the in- see note 2
band notification
EN_INBAND_PAGING Flag to disable/enable the in- see note 2
band paging
INBAND_PAGING_THR If the eMLPP priority included see note 2
in the Paging message from
the MSC is higher than this
parameter, then the BSS shall
trigger in-band paging within
cells, that are identified to be
paged from the PAGING
message, and that have
existing VGC active.
NOTIF_FACCH_OTHER_ Threshold (eMLPP priority) see note 2
VGCS_CALL_THR above which the Notifications
message shall be sent on
FACCH of all other on-going
VGCS call.

NOTIFICATION
0439_03_Rel.doc0439_02.doc
3BK 11202 0439 DSZZA 65/81

10/01/2007
NOTIF_FACCH_PTP_CA Threshold (eMLPP priority) see note 2

LL_THR above which the Notifications
message shall be sent on
FACCH of all on-going point to
point call.
NOTIF_PCH_THR The BSS shall consider for see note 2
Notification/PCH only VGCS-
Calls which have a priority
(eMLPP priority) above this
threshold. If more than one is
selected, all these voice group
calls shall be notified on PCH
and all with the same
frequency of occurrence.
NB_MAX_MSG_MULTIPL Number of paging messages The
E_PAGING_CMD that shall be included in the mechanism
Abis message MULTIPLE does not
PAGING COMMAND before apply to G2
sending it to the BTS BTS.
Value 1
disables the
function (i.e
Paging
Command
is used)
T_SEND_MULTIPLE_PA Maximum time between two The
GING_CMD sending of MULTIPLE mechanism
PAGING COMMAND does not
message apply to G2
BTS.
note 1:
The change of these parameters has a great impact on OMC/BSC/BTS. This is described in ref.[11].
The main influence for the Paging / Access Grant / Notification –process is:
During reconfiguration, the PCH queues are emptied and new Paging Command messages are
discarded until reconfiguration is completed.
Only if the CCCH_CONF parameter is modified, messages in the AGCH queue are discarded during
reconfiguration.
note 2:
This parameter has influence on the performance of the Paging / Access Grant / Notification process.
This parameter doesn't interrupt the Paging / Access-Grant / Notification process.
3.2.8 Performance Management
Some CCCH load measurements are done by counting the number of PAGING REQUEST buffers
which are free for the Paging queues associated with one CCCH timeslot.
B = 4 x ( GS - BS )
B = Free Buffer space, in term of PAGING COMMAND messages, for one CCCH timeslot.
GS = Global Space of all PAGING REQUEST buffers for one CCCH timeslot.

NOTIFICATION
0439_03_Rel.doc0439_02.doc
3BK 11202 0439 DSZZA 66/81

10/01/2007
BS = number of pending PAGING REQUEST messages for one CCCH timeslot.
Note: the "4" factor is used as an approximation of the possible number of PAGING COMMAND
messages in a PAGING REQUEST message. It is considered that the ratio (TMSI and PTMSI
identities) / (IMSI identities) is very high.
This snapshot value is sent within the CCCH LOAD INDICATION message from the BTS to the BSC.
In this release, the BSC does not perform any tasks on receipt of this message and the message is
discarded.
The CCCH LOAD INDICATION message contains also the RACH load information element.
This message is only sent if a certain RACH load is reached (THR_CCCH_LOAD).
After matching of this threshold, there is a guard time until the next transmission of this message (but
only if the threshold is reached again).
3.2.9 Error Checking
3.2.9.1 PAGING COMMAND message checking
The following message checking is performed by the BTS on the PAGING COMMAND messages
received from the BSC:
PAGING COMMAND CHECK ON ERROR

MIE Channel number "C1....C5" field shall correspond to Discard the message and send
"downlink CCCH channel". ERROR REPORT to the BSC
"C1....C5" and "TN" fields shall be with cause :
compliant with the TRX configuration. "Radio Resource not available"
MIE Paging Group The Paging group shall be compatible Discard the message and send
with the configuration (i.e. shall not be ERROR REPORT to the BSC
out of the values range derived from with cause :
BS_AG_BLKS_RES, CCCH_CONF "Invalid Information Element
and BS_PA_MFRMS parameters) contents"
MIE MS Identity The "Type of Identity" field shall be Discard the message and send
either IMSI, TMSI or PTMSI ERROR REPORT to the BSC
with cause :
"Invalid Information Element
contents"
The "Length" field shall be 4 bytes for Discard the message and send
a TMSI or a PTMSI, and shall be ERROR REPORT to the BSC
1 byte ≤ Length ≤ 8 bytes (15 digits) with cause :
for an IMSI. "Information Element length
error"
Packet Page The Packet Page Indication shall Discard the message and send
Indication correspond either to a Circuit Paging ERROR REPORT message to
or to a Packet Paging. the BSC with cause :
contents"
The BSC will not perform any specific task when receiving an ERROR REPORT message with one of
the above cause values.

NOTIFICATION
0439_03_Rel.doc0439_02.doc
3BK 11202 0439 DSZZA 67/81

10/01/2007
3.2.9.2 IMMEDIATE ASSIGN COMMAND checking
The following message checking is performed by the BTS on the IMMEDIATE ASSIGN COMMAND
messages received from the BSC:
IMMEDIATE ASSIGN CHECK ON ERROR

COMMAND
"downlink CCCH channel". ERROR REPORT message to
"C1....C5" and "TN" fields shall be the BSC with cause :
MIE Full Immediate The "Length Indicator" field shall indicate Discard the message and send
Assign Info a length of 23. ERROR REPORT message to
the BSC with cause :
"Information Element length
error"
The "Message Type" shall correspond Discard the message and send
either to an IMMEDIATE ASSIGNMENT ERROR REPORT message to
or IMMEDIATE ASSIGNMENT REJECT the BSC with cause :
message. "Invalid Information Element
contents"
Packet Assignment The Packet Assignment type shall Discard the message and send
type correspond either to a (EGPRS) Packet ERROR REPORT message to
Uplink Assignment or a Packet Downlink the BSC with cause :
Assignment "Invalid Information Element
contents"
Paging Group The Paging group shall be compatible Discard the message and send
with the configuration (i.e. shall not be ERROR REPORT message to
out of the values range derived from the BSC with cause :
BS_AG_BLKS_RES, CCCH_CONF and "Invalid Information Element
BS_PA_MFRMS parameters) contents"
A Paging Group IE shall not be present Discard the message and send
when the Packet Assignment type is not ERROR REPORT message to
present or when the Packet Assignment the BSC with cause :
type is set to (EGPRS) Packet Uplink "Invalid Information Element
Assignment. contents"
The BSC will not perform any specific task when receiving an ERROR REPORT message with one of
the above cause values.
3.2.9.3 NOTIFICATION COMMAND message checking
The following message checking is performed by the BTS on the NOTIFICATION COMMAND
messages received from the BSC:
NOTIFICATION CHECK ON ERROR

COMMAND
"downlink CCCH channel". ERROR REPORT message to
"C1....C5" and "TN" fields shall be the BSC with cause :
MIE Command The command indicator shall correspond Discard the message and send
indicator to « Start » or « Stop » ERROR REPORT message to
the BSC with cause :
contents"

NOTIFICATION
0439_03_Rel.doc0439_02.doc
3BK 11202 0439 DSZZA 68/81

10/01/2007
NCH DRX information The NCH DRX information (NLN, NLN Discard the message and send
status and eMLPP priority) shall be ERROR REPORT message to
present the BSC with cause :
contents"

NOTIFICATION
0439_03_Rel.doc0439_02.doc
3BK 11202 0439 DSZZA 69/81

10/01/2007
4 INTERFACE DESCRIPTION
4.1 Message names
4.1.1 Paging and Packet Downlink Assignment procedure

4.1.1.1 Case of Paging command

MS Radio Interface (PCH) BTS Abis Interface (RSL) BSC A Interface (SS7) MSC
PAGING REQUEST PAGING COMMAND CS PAGING

message message Message
← ← ←
MS Radio Interface (PCH) BTS Abis Interface (RSL) BSC BSCGP Interface (GSL) MFS
PAGING REQUEST PAGING COMMAND PS / CS PAGING

message message Message
← ← ←
PACKET DOWNLINK IMMEDIATE ASSIGN CHANNEL

ASSIGNMENT COMMAND ASSIGNMENT
message message DOWNLINK message
(Downlink Assign.)
← ← ←
A PAGING REQUEST message may contain from 2 PAGING COMMAND messages using IMSI or
(P)TMSI numbers and up to 4 PAGING COMMAND messages using only (P)TMSI numbers.
The PACKET DOWNLINK ASSIGNMENT message is sent on PCH when the MS is in DRX mode.
This scenario does not apply to G2 BTS and NB_MAX_MSG_MULTIPLE_PAGING_CMD shall be >
1 (more than one Paging command ).
MS Radio Interface (PCH) BTS Abis Interface (RSL) BSC A Interface (SS7) MSC
PAGING REQUEST MULTIPLE PAGING CS PAGING

message COMMAND message Message
← ← ←
MS Radio Interface (PCH) BTS Abis Interface (RSL) BSC BSCGP Interface MFS
(GSL)
PAGING REQUEST MULTIPLE PAGING PS / CS PAGING

message COMMAND message Message
← ← ←
  

NOTIFICATION
0439_03_Rel.doc0439_02.doc
3BK 11202 0439 DSZZA 70/81

10/01/2007
PACKET DOWNLINK IMMEDIATE ASSIGN CHANNEL

ASSIGNMENT COMMAND ASSIGNMENT
message message DOWNLINK message
(Downlink Assign.)
4.1.2 Immediate Assignment and (EGPRS) Packet Uplink Assignment procedure
MS Radio Interface (AGCH) BTS Abis Interface (RSL) BSC
IMMEDIATE IMMEDIATE
ASSIGNMENT ASSIGNMENT
message message
ACCESS IMMEDIATE IMMEDIATE

GRANT ASSIGNMENT ASSIGN
message EXTENDED COMMAND
message message
← ←
IMMEDIATE IMMEDIATE
ASSIGNMENT ASSIGNMENT
REJECT REJECT
message message
MS Radio Interface (AGCH) BTS Abis Interface (RSL) BSC BSCGP Interface (GSL) MFS
(EGPRS) IMMEDIATE CHANNEL

PACKET ASSIGN ASSIGNMENT
UPLINK COMMAND UPLINK message
ASSIGNMENT message ((EGPRS) Uplink
message Assign.)
← ← ←
ACCESS PACKET IMMEDIATE CHANNEL
GRANT DOWNLINK ASSIGN ASSIGNMENT
message ASSIGNMENT COMMAND DOWNLINK
message message message
(Downlink Assign.)
← ← ← ←
IMMEDIATE IMMEDIATE CHANNEL
ASSIGNMENT ASSIGN ASSIGNMENT
REJECT COMMAND UPLINK message
message message (Assign. Reject)
← ← ←
An IMMEDIATE ASSIGN COMMAND message may contain either a (EGPRS) PACKET UPLINK
ASSIGNMENT message, a PACKET DOWNLINK ASSIGNMENT message, an IMMEDIATE
ASSIGNMENT message or an IMMEDIATE ASSIGNMENT REJECT message.
An ACCESS GRANT message may contain either a (EGPRS) PACKET UPLINK ASSIGNMENT
message, a PACKET DOWNLINK ASSIGNMENT message (when MS is in non-DRX mode), an
IMMEDIATE ASSIGNMENT message, an IMMEDIATE ASSIGNMENT EXTENDED message, or an
An IMMEDIATE ASSIGNMENT EXTENDED message contains two IMMEDIATE ASSIGNMENT
messages.

NOTIFICATION
0439_03_Rel.doc0439_02.doc
3BK 11202 0439 DSZZA 71/81

10/01/2007
4.1.3 Notification procedure

MS Radio Interface (NCH/FACCH) BTS Abis Interface (RSL) BSC
NOTIFICATION/
PCH message
NOTIFICATION NOTIFICATION/ NOTIFICATION

message NCH COMMAND
Message message
← ←
4.2 GSM interfaces / Physical interfaces
4.2.1 Gb Interface
(PACKET) PAGING
- Message type
- IMSI
- DRX Parameters optional (1)
- TLLI optional (2)
- (P)TMSI optional
- Cell Identifier list optional
- Channel needed optional
- eMLPP priority optional (3)
(1) These parameters are only used by the MFS Paging Procedure on PCCCH.
(2) This IE is used for CS paging only. It is needed for MFS routing purposes when the MS is
performing GPRS transfers.
(3) This IE is used for CS paging only, and it is always ignored by the MFS.
4.2.2 A Interface (SS7 or GSL)
(PACKET) PAGING
- Message type
- IMSI
- (P)TMSI optional (1)
- Cell Identifier list optional (2)
- Channel needed optional (3)
- eMLPP priority optional (3)
(1) If IE is present, paging to the MS is performed with the (P)TMSI.

(2) If this IE is not present, paging is performed on all cells, regardless if it is a multicell BSS
or not. For GSM phase 2, this IE is mandatory but it remains optional for this release.
When this I.E. is present and the PAGING message is received from the MSC, if more than
10 different Location Areas are included in the cell identifier list, the BSC will send a PAGING
COMMAND in all its cells (Alcatel restriction). See section 3.1.1.
(3) This IE is always ignored by the BSS.

NOTIFICATION
0439_03_Rel.doc0439_02.doc
3BK 11202 0439 DSZZA 72/81

10/01/2007
Restriction: If the CGI coding is used in the cell identifier list, a maximum of 30 cells can be included
in the message. The service of segmentation is not offered by the BSS implementation of the SCCP
on the A interface.
4.2.3 Abis Interface
PAGING COMMAND
- Message discriminator
- Message type
- Channel Number
- Paging Group
- MS Identity (IMSI, TMSI or PTMSI)
- Channel needed (1)
- eMLPP priority
- Packet Page Indication (2)
(1) Not sent by the BSC

(2) This IE is set to 1 if it is a GPRS Paging (IMSI or PTMSI). If not, it is set to 0 or is absent.
- Paging information
- Paging information repeated up to n times
This command contains more than one PAGING COMMAND
IMMEDIATE ASSIGN COMMAND, PACKET UPLINK/DOWNLINK ASSIGNMENT, EGPRS

PACKET UPLINK ASSIGNMENT
- Message type
- Imm. Assign Info (1)
- Packet Assignment Type optional (3)
- Paging Group optional (2)
(1) This IE contains a complete IMMEDIATE ASSIGNMENT or IMMEDIATE ASSIGNMENT

REJECT. In case of PS Assignments, the IMMEDIATE ASSIGNMENT message
encapsulates a PACKET DOWNLINK ASSIGNMENT, a PACKET UPLINK ASSIGNMENT or
a EGPRS PACKET UPLINK ASSIGNMENT.
message as defined in the Radio interface section.
(2) IE only included for PACKET DOWNLINK ASSIGNMENT messages towards MS in DRX
mode, which are sent on PCH.
(3) IE used to indicate a PACKET ASSIGNMENT and its type : UPLINK or DOWNLINK.
CCCH LOAD INDICATION
- Message type
- Channel number (1)
- RACH Load (2)
- Paging Load (2)
(1) The channel number IE indicates 'uplink CCCH'.

NOTIFICATION
0439_03_Rel.doc0439_02.doc
3BK 11202 0439 DSZZA 73/81

10/01/2007
(2) The two IEs are always present in the message, they are not considered as conditional
elements following the channel number.
Note: The message is discarded within the BSC.
- Message type
- Channel Number
- Command indicator (1)
- Group call reference optional
- Channel Description optional
- NCH DRX information optional (2)
(1) This information element indicates the type of command that is to be performed by the BTS
with respect to information contained in the the rest of the message. In the case of “start” the
notification is either added to the notification list or updated if already available in the list. In
the case of “stop” the notification is removed from the notification list.
(2) This IE is always present in Alcatel implementation (due to the reduced NCH monitoring for
MS in DRX mode)
This IE includes NLN, NLN status and eMLPP priority
4.2.4 Radio Interface
Each time it is used, the L2 pseudo length is equal to:

23 (length of a layer 2 frame) - length of the 'Rest octets' IE - 1 (length of this IE)
Or is equal to:
the sum of lengths of all the IEs except 'Rest octet' IE and this IE.
- L2 pseudo length
- message header (Protocol discriminator/ Skip indicator/Message type)
- Page mode (1)
- Mobile identity 1 (2)
- Mobile identity 2 optional (2)
- P1 rest octets optional (4)
(1) Set to 'normal paging'.

(2) IMSI or (P)TMSI.
(3) It is always set to 'any channel'. These bits are spare bits for Phase 1 mobiles.
(4) - Following IE used for Packet Paging are included in these rest octets: (See § 3.1.2 item 3)
Packet Page Indication 1 for MS identity 1,
Packet Page Indication 2 for MS identity 2.
- Following IE used for Reduced Notification and Notification/PCH are included in these rest
octets:
NLN(PCH) if NCH is configured,
NLN status if NCH is configured,
Group Call information, if a high priority VGCS call needs to be notified on PCH.

NOTIFICATION
0439_03_Rel.doc0439_02.doc
3BK 11202 0439 DSZZA 74/81

10/01/2007
- Following IE used for eMLPP are included in these rest octets:

Priority1,
Priority2.
- L2 pseudo length
- Page mode (1)
- (P)TMSI - Mobile Identity 1
- Mobile identity 3 (2)

(1) (P)TMSI or IMSI, this message is only sent with 3 mobile station Identities, therefore this
element is always present.
(3) It is always set to 'any channel'. These bits are spare bits for phase 1 mobiles.
(4) - Following IE used for Packet Paging are included in these rest octets: (See §3.1.2 item 3)
Packet Page Indication 3 for MS identity 3.
- Following IE used for Reduced Notification are included in these rest octets:
Priority1,
Priority2,
Priority3.
- L2 pseudo length
- Page mode (1)

(2) It is always set to 'any channel'. These bits are spare bits for phase 1 mobiles.
(3) - Following IE used for Reduced Notification are included in these rest octets:
Priority1,
Priority2,
Priority3,
Priority4.

NOTIFICATION
0439_03_Rel.doc0439_02.doc
3BK 11202 0439 DSZZA 75/81

10/01/2007
IMMEDIATE ASSIGNMENT & PACKET UPLINK/DOWNLINK ASSIGNMENT & EGPRS PACKET

UPLINK ASSIGNMENT
- L2 pseudo length
- Message type (1)
- page mode (2)
- dedicated mode or TBF
- channel description
- packet channel description
- request reference (6)
- timing advance
- mobile allocation (3)
- starting time optional (4)
- IA rest octets (5)
(1) This IE indicates, besides, the type of Assignment, i.e. Immediate Assignment, Immediate
Assignment Extended or Immediate Assignment Reject message.
(2) Set to 'same as before' (by the BSC) for Immediate Assignment (CS). Set to ‘normal’ (by the
MFS) for Packet Uplink/Downlink Assignment and EGPRS Packet Uplink Assignment. As the
paging is always sent with page mode = ‘normal’, the difference is coding between CS and
PS has no impact..
(3) in the case of fixed frequency, the length indication is set to 0.
(4) this IE is not sent.
(5) this IE contains the frequency parameters, before time and is used for frequency redefinition
for GSM phase 2 mobiles and indication whether the MS shall send inter RAT information in
compressed mode or in normal mode (depending on EN_COMPRESSED
INTER_RAT_INFO value.For PS Assignments, it contains the (EGPRS) Packet Uplink
Assignment or the Packet Downlink Assignment message.
(6) See ref.[19] in case of IMMEDIATE ASSIGNMENT message containing an EGPRS PACKET
UPLINK ASSIGNMENT.
IMMEDIATE ASSIGNMENT EXTENDED
- L2 pseudo length
- page mode (1)
- channel description 1 (2)
- request reference 1 (2)
- timing advance 1 (2)
- channel description 2 (3)
- request reference 2 (3)
- timing advance 2 (3)
- mobile allocation (4)
- starting time optional (5)
- IAX rest octets (6)
(1) Set to 'same as before'.

(2) these IEs are related to the first MS.
(3) these IEs are related to the second MS.
(4) in the case of fixed frequencies (for both MS 1 and MS 2), the length indication is set to 0.
(5) this IE is not sent.
(6) this IE contains only spare bits.

NOTIFICATION
0439_03_Rel.doc0439_02.doc
3BK 11202 0439 DSZZA 76/81

10/01/2007
IMMEDIATE ASSIGNMENT REJECT
- L2 pseudo length
- page mode (1)
- request reference 1 (2 & 7)
- wait indication 1 (2)
- IAR rest octets (6)
(1) Set to 'same as before' (by the BSC) when used for a CS request. Set to ‘normal’ (by the
MFS) when used for a PS request. As the paging is always sent with page mode = ‘normal’,
the difference is coding between CS and PS has no impact.
(2) these IEs are related to the first MS.
(3) these IEs are related to a second MS (if more than one MS shall be rejected).
(4) these IEs are related to a third MS (if more than two MS shall be rejected).
(5) these IEs are related to a fourth MS (if more than three MS shall be rejected).
(6) This IE contains only spare bits for CS assignments. For PS assignments, see ref.[19].
(7) See ref.[19] in case the IMMEDIATE ASSIGNMENT REJECT message is related to an
EGPRS PACKET CHANNEL REQUEST.
NOTIFICATION / NCH
- L2 pseudo length
- Message type
- NT/N rest octets
NOTIFICATION / FACCH
-Short header
- Group Call Information : (1)
Call reference
Channel description optional
- Paging Information : (1)
Mobile identity
Channel first
eMLPP priority optional
(1) The two IEs are exclusive, either Group Call information or Paging information is present, but
not both
4.3 Internal interfaces
4.4 External interfaces
4.5 Timers list

NOTIFICATION
0439_03_Rel.doc0439_02.doc
3BK 11202 0439 DSZZA 77/81

10/01/2007
T_PAG_PS: BTS timer indicating the maximum time a PS PAGING message can remain in a
Paging Group queue.
T_PAG_CS: BTS timer indicating the maximum time a CS PAGING message can remain in a
Paging Group queue.
T_PDA: BTS timer indicating the maximum time a PACKET DOWNLINK ASSIGNMENT
message (to be sent on PCH) can remain in the PDA queue.
T_PUA: BTS timer indicating the maximum time a (EGPRS) PACKET UPLINK ASSIGNMENT
message or a PACKET DOWNLINK ASSIGNMENT message (to be sent on AGCH)
can remain in the access grant queue.
T_IA: BTS timer indicating the maximum time a CS IMMEDIATE ASSIGNMENT message
can remain in the queue.
T_MPDCH_EST_PROC(BSC): BSC timer indicating the duration of the primary MPDCH

establishment procedure. It covers the maximum time needed by the MS to be aware
of the new cell configuration.
T3101: BSC timer used to monitor the seizure of the channel by the MS and the completion of
the immediate assignment procedure.
T3113: MSC timer started after sending of a PAGING message and stopped after the receipt
of the associated PAGING RESPONSE message.
T3313: SGSN timer started after sending of a PACKET PAGING message and stopped after
the receipt of the associated PACKET PAGING RESPONSE message.
T3120: Phase 1 MS timer used to monitor the reception of an ACCESS GRANT message.
This timer name has been removed from GSM phase 2 TS.
T3122: Phase 1 & 2 MS timer used to delay a Random Access procedure when an
IMMEDIATE ASSIGNMENT REJECT message has been received. This timer is
started with the value indicated in Wait Indication IE.
T3126: Phase 2 MS timer indicating the waiting time after receiving an IMMEDIATE
ASSIGNMENT REJECT message, or after sending the last CHANNEL REQUEST
before going back to idle mode.
T3142: Phase 2 MS timer used to delay a Random Access procedure when an IMMEDIATE
ASSIGNMENT REJECT (Packet Access Reject) message has been received. This
timer is started with the value indicated in Wait Indication IE.
T3146: Phase 2 MS timer indicating the waiting time after receiving an IMMEDIATE
ASSIGNMENT REJECT (Packet Access Reject) message, or after sending the last
CHANNEL REQUEST(PS) / EGPRS PACKET CHANNEL REQUEST before going
back to idle mode.
T3190: This timer is used by the MS to monitor the receipt of downlink RLC data blocks with
the assigned DL TFI for packet downlink assignment on AGCH for a MS in non-DRX
mode.
T_SEND_MULTIPLE_PAGING_CMD : This timer is used by BSC and indicating the

maximum time between two sending MULTIPLE PAGING
COMMAND messages.

NOTIFICATION
0439_03_Rel.doc0439_02.doc
3BK 11202 0439 DSZZA 78/81

10/01/2007
In case if the timer expires the message is sent even

than if the number of paging messages available for
inclusion is lower than
NB_MAX_MSG_MULTIPLE_PAGING_CMD.
4.6 Parameters list
4.6.1 Configuration parameters
- BCCH_EXT: flag which enables/disables the BCCH Extended configuration in the cell.
- AG_PREMPT_PCH: flag to enable paging sub-channels pre-emption when the BCCH Extended is
configured in the cell.
- BS_CC_CHANS: number of CCCH timeslots (range: 1-2)
- CCCH_CONF: CCCH configuration, which shows the number of physical channels combined
or not with SDCCH (binary representation with 3 Bits, see table below).
The following table shows the relationship between BS_CC_CHANS and CCCH_CONF:
BS_CC_CHANS CCCH_CONF Remark
1 000 1 basic physical channel.- not combined with SDCCH
1 001 1 basic physical channel.- combined with SDCCH
2 010 2 basic physical channel.- not combined with SDCCH
3 (not used) 100 3 basic physical channel.- not combined with SDCCH
4 (not used) 110 4 basic physical channel.- not combined with SDCCH
- BS_AG_BLKS_RES: number of reserved AGCHs per CCCH multi-frame (range: 0 - 7).
- BS_PA_MFRMS: number of CCCH-multiframes between two occurrences of a specific paging

group (range: 2 - 9).
- DRX_TIMER_MAX: This parameter is broadcast in each cell. The value to be applied for the MS
timer is the minimum of DRX TIMER MAX and the value negotiated in the
GPRS attach procedure.
- Max_retrans: Maximum number of retransmissions of CHANNEL REQUEST or EGPRS

PACKET CHANNEL REQUEST by the MS on the RACH.
- Tx_integer: Number of RACH timeslots that spread transmission of CHANNEL REQUEST

or EGPRS PACKET CHANNEL REQUEST.
4.6.2 Queues parameters
AGCH queue
- AG_FULL: maximum value permitted for the parameter AG_Q. Its value is equal to 100 messages.
PCH queues
- PG_FULL: maximum number of all PAGING REQUEST messages that can be stored in the BTS
per CCCH group.
Its value is equal to: 200 messages (TRX type = FUCO).
400 messages (TRX type ≠ FUCO).

NOTIFICATION
0439_03_Rel.doc0439_02.doc
3BK 11202 0439 DSZZA 79/81

10/01/2007
- PDA_FULL: maximum number of all PACKET DOWNLINK ASSIGNMENT messages to be sent on

PCH that can be stored in the BTS per CCCH group.
Its value is equal to: 0 message (TRX type = FUCO, such TRX cannot handle
GPRS).
200 messages (TRX type ≠ FUCO).
4.6.3 Other parameters
- PAG_BAR: BSC flag (on cell basis) indicating whether transmission of PAGING REQUEST
messages to the concerned cell is inhibited or not.
PAG_BAR=0: PAGING REQUEST messages can be sent to the cell.
PAG_BAR=1: PAGING REQUEST messages are not sent to the cell.
- EN_IM_ASS_REJ: enable / disable Immediate Assignment Reject messages.
- WI_EC: wait indication if the establishment cause is "Emergency Call",

- WI_CR: wait indication if the establishment cause is "Call Re-establishment",
- WI_OC: wait indication if the establishment cause is "Originating Call",
- WI_OP: wait indication if the establishment cause is "Other Procedures".
- WI_PR: wait indication if the establishment cause is "Packet Reject".

NOTIFICATION
0439_03_Rel.doc0439_02.doc
3BK 11202 0439 DSZZA 80/81

10/01/2007
5 GLOSSARY AND ABBREVIATIONS
CGI Cell Global Identifier

CI Cell Identifier
CR Connection Request
CRQ Channel ReQuest
CS Circuit Switched
DRX Discontinuous Reception
DTM Dual Transfer Mode
EGPRS Enhanced GPRS
eMLPP Enhanced Multi-Level Precedence and Pre-emption
FACCH Fast Associated Control CHannel
FHS Frequency Hopping Sequence
FIFO First In, First Out
FN Frame Number
FUCO Frame Unit COntroller
GPRS General Packet Radio Service
GSL GPRS Signalling Link
IE Information Element
IMSI International Mobile Subscriber Identity
LAC Location Area Code
LAI Location Area Identifier
MCC Mobile Country Code
MFS Multi-function Server
MNC Mobile Network Code
MPDCH Master PDCH
MS Mobile Station
MSC Mobile Switching Centre
NCH Notification Channel
NLN Notification List Number
OMU Operation and Maintenance Unit
OMC-R Operation and Maintenance Centre Radio
PCCCH Packet Common Control CHannel
PBCCH Packet Broadcast Control CHannel
PCH Paging CHannel
PDA Packet Downlink Assignment
PDCH Packet Data CHannel
PS Packet Switched
PTMSI Packet Temporary Mobile Subscriber Identity
PUA Packet Uplink Assignment
RAC Routing Area Code
RACH Random Access CHannel
RAI Routing Area Identifier
RSL Radio Signalling link
SACCH Slow Associated Control CHannel
SBL Security BLock
SCCP Signalling Connection Control Part
SDCCH Stand alone Dedicated Control CHannel
SGSN Service GPRS Support Node
SS7 Signalling System Nb 7
TBF Temparory Block Flow
TFI Temporary Flow Identifier
TMSI Temporary Mobile Subscriber Identity
TS Technical Specification OR Time Slot
VGCS Voice Group Call Service
VGCH VGCS Channel
END OF DOCUMENT

NOTIFICATION
0439_03_Rel.doc0439_02.doc
3BK 11202 0439 DSZZA 81/81

10/01/2007

S.Barre Song Jun Name App. R.Sabellek: SYT Manager DPM Syt DPM BSC

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

S.Barre Song Jun Name App. R.Sabellek: SYT Manager DPM Syt DPM BSC

Încărcat de

Drepturi de autor:

Formate disponibile

not permitted without written authorization from Evolium.

All rights reserved. Passing on and copying of this

System : ALCATEL 900/BSS

Release B10: 3BK 11202 0439 DSZZA

Ed 2 3 Released PAGING, ACCESS GRANT CONTROL AND

3BK 11202 0439 DSZZA 1/81

Ed. 01 Proposal 01 2005/10/19 Document created based on B9 version of the document

Ed 2 3 Released PAGING, ACCESS GRANT CONTROL AND

3BK 11202 0439 DSZZA 2/81

Ed 2 3 Released PAGING, ACCESS GRANT CONTROL AND

3BK 11202 0439 DSZZA 3/81

TABLE OF CONTENTS .........................................................................................................43

Ed 2 3 Released PAGING, ACCESS GRANT CONTROL AND

3BK 11202 0439 DSZZA 4/81

Telecom and O&M interworking ..............................................................................6564

Ed 2 3 Released PAGING, ACCESS GRANT CONTROL AND

3BK 11202 0439 DSZZA 5/81

INTERNAL REFERENCED DOCUMENTS

Ed 2 3 Released PAGING, ACCESS GRANT CONTROL AND

3BK 11202 0439 DSZZA 6/81

OPEN POINTS / RESTRICTIONS

Ed 2 3 Released PAGING, ACCESS GRANT CONTROL AND

3BK 11202 0439 DSZZA 7/81

The management of multiple CCCH slots TS0, TS2 is

Ed 2 3 Released PAGING, ACCESS GRANT CONTROL AND

3BK 11202 0439 DSZZA 8/81

2.1 General Description

2.1.1 Circuit Switched Paging procedure

2.1.2 Packet Switched Paging procedure

2.1.3 Circuit Switched Immediate Assignment procedure

Ed 2 3 Released PAGING, ACCESS GRANT CONTROL AND

3BK 11202 0439 DSZZA 9/81

2.1.5 VGCS Notification procedure

2.1.6 CCCH channel

Ed 2 3 Released PAGING, ACCESS GRANT CONTROL AND

3BK 11202 0439 DSZZA 10/81

• NCH is used by the Notification procedure.

• RACH is used (uplink only) to request allocation of SDCCH channels .

Ed 2 3 Released PAGING, ACCESS GRANT CONTROL AND

3BK 11202 0439 DSZZA 11/81

2.2.1 Radio Multiplexing

• Not Combined CCCH (CCCH_CONF=0)

Ed 2 3 Released PAGING, ACCESS GRANT CONTROL AND

3BK 11202 0439 DSZZA 12/81

• Combined CCCH (CCCH_CONF=1)

• Not Combined CCCH (CCCH_CONF = 2)

TS0 is the same as Not Combined CCCH (CCCH_CONF = 0)

CCCH_CONF BS_CC_CHANS BS_CCCH_SDCCH_COMB

Table 1: Correspondence between CCCH parameters

- FCCH + SCH + BCCH + CCCH

- FCCH + SCH + BCCH + CCCH + SDCCH/4(0..3) + SACCH/4(0..3) (1)

- BCCH + CCCH (2)where CCCH =

Ed 2 3 Released PAGING, ACCESS GRANT CONTROL AND

3BK 11202 0439 DSZZA 13/81

Note: (1)This combination is allowed if there is only one CCCH Group.

2.2.2 (Packet) CCCH Group

Table 2: Correspondence between (P)CCCH_GROUP and TS concerned

2.2.3 CCCH_GROUP selection algorithm

CCCH_GROUP (0 .. BS_CC_CHANS-1) = ((IMSI mod 1000) mod (BS_CC_CHANS x N)) div N

Ed 2 3 Released PAGING, ACCESS GRANT CONTROL AND

3BK 11202 0439 DSZZA 14/81

TABLE 3: Correspondence between CCCH_GROUP and TS concerned

PAGING_GROUP (0 .. N-1) = ((IMSI mod 1000) mod (BS_CC_CHANS x N)) mod N