## 3 Radio Resource management procedures

04.083GPPMobile radio interface Layer 3 specificationRelease 1998TS

## 3.1 Overview/General

### 3.1.1 General

Radio Resource management procedures include the functions related to the management of the common transmission resources, e.g. the physical channels and the data link connections on control channels.

The general purpose of Radio Resource procedures is to establish, maintain and release RR connections that allow a point-to-point dialogue between the network and a mobile station. This includes the cell selection/reselection and the handover procedures. Moreover, Radio Resource management procedures include the reception of the uni-directional BCCH and CCCH when no RR connection is established. This permits automatic cell selection/reselection.

If VGCS listening or VBS listening are supported, the radio resource management also includes the functions for the reception of the voice group call channel or the voice broadcast channel, respectively, and the automatic cell reselection of the mobile station in Group receive mode.

If VGCS talking is supported, the radio resource management also includes the functions for the seizure and release of the voice group call channel.

If GPRS point-to-point services are supported, the radio resource management procedures includes functions related to the management of transmission resources on packet data physical channels. This includes the broadcast of system information to support a mobile station in packet idle and packet transfer modes, see also 3GPP TS 04.60.

NOTE 1: This chapter includes some procedures used for multislot operation and for the TCH/H + TCH/H configuration which need not be supported by simple mobile stations.

NOTE 2: The procedures and the information content relating to the TCH/H + TCH/H configuration in RR messages is for further study.

### 3.1.2 Services provided to upper layers

A RR connection is a physical connection used by the two peer entities to support the upper layers’ exchange of information flows.

#### 3.1.2.1 Idle mode

In idle mode no RR connection exists.

The RR procedures include (on the mobile station side) those for automatic cell selection/reselection. The RR entity indicates to upper layers the unavailability of a BCCH/CCCH and the cell change when decided by the RR entity. Upper layers are advised of the BCCH broadcast information when a new cell has been selected, or when a relevant part of this information changes.

In Idle mode, upper layers can require the establishment of an RR connection.

#### 3.1.2.2 Dedicated mode

In dedicated mode, the RR connection is a physical point-to-point bi-directional connection, and includes a SAPI 0 data link connection operating in multiframe mode on the main DCCH. If dedicated mode is established, RR procedures provide the following services:

– establishment/release of multiframe mode on data link layer connections other than SAPI 0, on the main DCCH or on the SACCH associated with the channel carrying the main signalling link;

– transfer of messages on any data link layer connection;

– indication of temporary unavailability of transmission (suspension, resuming);

– indication of loss of RR connection;

– automatic cell reselection and handover to maintain the RR connection;

– setting/change of the transmission mode on the physical channels, including change of type of channel, change of the coding/decoding/transcoding mode and setting of ciphering;

– allocation/release of an additional channel (for the TCH/H + TCH/H configuration);

– allocation/release of additional channels for multislot operation;

– release of an RR connection.

Only applicable for mobile stations supporting VGCS listening or VBS listening.

In this mode, the RR procedures on the mobile station side provide the services:

– local connection to the voice broadcast channel or voice group call channel;

– reception of messages in unacknowledged mode;

– automatic cell reselection for the mobile station in Group receive mode;

– local disconnection from the received voice group call or broadcast call channels.

For mobile stations supporting both VGCS listening and VGCS transmit, in addition, the RR procedures on the mobile station side provide the service:

– uplink access procedures to establish the RR connection.

#### 3.1.2.4 Group transmit mode

Only applicable for mobile stations supporting VGCS talking.

In group transmit mode, the RR connection is a physical point-to-point bi-directional connection, and includes a SAPI 0 data link connection operating in multiframe mode on the main DCCH. If the group transmit mode is established, RR procedures provide the following services:

– transfer of messages on the SAPI 0 of the data link layer connection;

– indication of loss of RR connection;

– automatic cell reselection and handover to maintain the RR connection;

– setting of the transmission mode on the physical channels, change of type of channel and setting of ciphering;

– release of the RR connection..

#### 3.1.2.5 Packet idle mode

Only applicable for mobile stations supporting GPRS.

In packet idle mode, no temporary block flow exists (see 3GPP TS 04.60). Upper layers may require the transfer of a LLC PDU, which implicitly triggers the establishment of a temporary block flow.

#### 3.1.2.6 Packet transfer mode

Only applicable for mobile stations supporting GPRS.

In packet transfer mode, the mobile station is allocated radio resource providing a temporary block flow on one or more packet data physical channels. The RR sublayer provides the following services, see also 3GPP TS 04.60:

– transfer of LLC PDUs in acknowledged mode;

– transfer of LLC PDUs in unacknowledged mode.

Depending on the GPRS mode of operation (class A or B), the mobile station may leave both packet idle mode and packet transfer mode before entering dedicated mode, group receive mode or group transmit mode.

Cell reselection in packet idle and packet transfer modes is specified in 3GPP TS 05.08. The RR entity on the mobile station side indicates to the upper layers the availability of a cell and a cell change when decided by the RR sublayer. Upper layers are advised of system information broadcast in the cell when a new cell has been selected, or when a relevant part of this information changes.

### 3.1.3 Services required from data link and physical layers

The RR sublayer uses the services provided by the data link layer as defined in 3GPP TS 04.05.

Moreover, the RR sublayer directly uses services provided by the physical layer such as BCCH searching and transfer of RLC/MAC blocks, as defined in 3GPP TS 04.04.

### 3.1.4 Change of dedicated channels

#### 3.1.4.1 Change of dedicated channels using SAPI = 0

In case a change of dedicated channels is required using a dedicated assignment and handover procedure, respectively, the RR sublayer will request the data link layer to suspend multiple frame operation before the mobile station leaves the old channel. When the channel change has been completed, layer 3 will request the data link layer to resume multiple frame operation again. The layer 2 suspend/resume procedures are described in 3GPP TS 04.05 and 04.06.

These procedures are specified in such a way that a loss of a layer 3 message cannot occur on the radio interface. However, messages sent from the mobile station to the network may be duplicated by the data link layer if a message has been transmitted but not yet completely acknowledged before the mobile station leaves the old channel (see 3GPP TS 04.06).

As the RR sublayer is controlling the channel change, a duplication of RR messages does not occur. However, there are some procedures for which a duplication is possible, e.g. DTMF procedures. For all upper layer procedures using the transport service of the RR sub-layer (e.g., MM and CM procedures), the request messages sent by the mobile station contain a sequence number in order to allow the network to detect duplicated messages, which are then ignored by the network. The procedures for sequenced transmission on layer 3 are described in sub-clause 3.1.4.2.

#### 3.1.4.2 Change of dedicated channels using other SAPIs than 0

For SAPIs other than 0, the data link procedures described in 3GPP TS 04.06 do not provide any guarantee against message loss or duplication.

Therefore, if an application uses a SAPI other than 0 and if this application is sensitive to message loss or duplication, then it has to define its own protection mechanism. No general protection mechanism is provided by the protocol defined in the present document.

#### 3.1.4.3 Sequenced message transfer operation

Upper layer messages sent using the RR sub-layer transport service from the mobile station to the network can be duplicated by the data link layer in the following case:

– a channel change of dedicated channels is required (assignment or handover procedure) and the last layer 2 frame has not been acknowledged by the peer data link layer before the mobile station leaves the old channel.

In this case, the mobile station does not know whether the network has received the message correctly. Therefore, the mobile station has to send the message again after the new dedicated channel is established (see 3GPP TS 04.06).

The network must be able to detect the duplicated received message. Therefore, each concerned upper layer message must be marked with a send sequence number.

To allow for different termination points in the infrastructure of the messages of different PDs, the sequence numbering is specific to each PD. For historical reasons, an exception is that messages sent with the CC, SS and MM PDs share the same sequence numbering. In the following, the phrase upper layer message flow refers to a flow of messages sharing the same sequence numbering. The different upper layer flows are MM+CC+SS, GCC, BCC, PDSS1 and PDSS2.

##### 3.1.4.3.1 Variables and sequence numbers

3.1.4.3.1.1 Send state variable V(SD)

The RR sublayer of the mobile station shall have one associated send state variable V(SD) ("Send Duplicated") for each upper layer message flow. The send state variable denotes the sequence number of the next in sequence numbered message in the flow to be transmitted. The value of the corresponding send state variable shall be incremented by one with each numbered message transmission. Arithmetic operations on V(SD) are performed modulo 2.

###### 3.1.4.3.1.2 Send sequence number N(SD)

At the time when such a message to be numbered is designated for transmission, the value of N(SD) for the message to be transferred is set equal to the value of the send state variable V(SD). See 3GPP TS 04.07.

##### 3.1.4.3.2 Procedures for the initiation, transfer execution and termination of the sequenced message transfer operation

3.1.4.3.2.1 Initiation

The sequenced message transfer operation is initiated by establishing a RR connection. The send state variables V(SD) are set to 0.

###### 3.1.4.3.2.2 Transfer Execution

The network must compare the send sequence numbers of pairs of subsequent messages in the same upper layer messages flow. In case the send sequence numbers of two subsequent messages in a flow are not identical, no duplication has occurred. In case the send sequence numbers are identical, the network must ignore the second one of the received messages.

3.1.4.3.2.3 Termination

The sequenced message transfer operation is terminated by the RR connection release procedure.

### 3.1.5 Procedure for Service Request and Contention Resolution

Upon seizure of the assigned dedicated channel, the mobile station establishes the main signalling link on this channel by sending a layer 2 SABM frame containing a layer 3 service request message. The data link layer will store this message to perform the contention resolution. The service request message will be returned by the network in the UA frame.

The data link layer in the mobile station compares the content of the information field (i.e. the layer 3 service request message) received in the UA frame with the stored message and leaves the channel in case they do not match. This procedure resolves contentions in the case where several mobile stations have accessed at the same random access slot and with the same random reference and one has succeeded due to capture. The full description of the procedure is given in 3GPP TS 04.06.

The purpose of the service request message is to indicate to the network which service the mobile station is requesting. This then allows the network to decide how to proceed (e.g. to authenticate or not).

The service request message must contain the identity of the mobile station and may include further information which can be sent without encryption.

The layer 3 service request message is typically one of the following:

– CM SERVICE REQUEST

– LOCATION UPDATING REQUEST

– IMSI DETACH

– PAGING RESPONSE

– CM RE-ESTABLISHMENT REQUEST

– IMMEDIATE SETUP

– RR INITIALISATION REQUEST

Mobile Station Network

+——————————————+

│ SABM ("layer 3 service request message") │

│ —————————————> │

│ │

│ UA ("layer 3 service request message") │

│ <————————————– │

+——————————————+

Figure 3.1/3GPP TS 04.08: Service request and contention resolution

### 3.1.6 Preemption

The datalink layer provides the capability to assign a priority to any message transferred in dedicated mode on SAPI 0 with multiframe operation. The available message priorities defined in 3GPP TS 04.06 are "high", "normal" and "low". Messages assigned a "high" priority are enabled to preempt, in the data link layer, all preceeding untransmitted and partially transmitted messages assigned a "low" priority that are using the same data link connection (same SAPI and logical channel). Messages or message portions that are preempted are discarded without notification to higher layers except that the first 2*N201 octets of any partially transmitted message are not discarded. The following priority assignments are defined for those Radio Resource, Mobility Management and Connection Management messages that use SAPI 0.

Table 2.1/3GPP TS 04.08: Priority Values of Layer 3 Messages

 Priority Messages Low RR Application Information message Normal All MM messagesAll CM messagesAll other RR messages using SAPI 0 not listed here High RR Channel Establishment: ADDITIONAL ASSIGNMENTRR Configuration Change: CONFIGURATION CHANGE COMMANDRR Handover related ASSIGNMENT COMMAND HANDOVER COMMAND RR-CELL CHANGE ORDER PDCH ASSIGNMENT COMMANDRR Channel release CHANNEL RELEASE PARTIAL RELEASE

Use of the preemption capability by layer 3 is not required in a BSS or MS that does not send any "low" priority message. In this case, all messages may be treated as having "normal" priority.

Preemption capabilities in Layer 3 are not applicable to the Uplink messages, hence all UL messages are treated as having "normal" priority.

NOTE: The "Suspension and Resumption of Multiple frame operation" (See 3GPP TS 04.06) will affect the order in which the layer 3 messages are delivered on the Uplink.

## 3.2 Idle mode procedures and general procedures in packet idle and packet transfer modes

### 3.2.1 Mobile Station side

In idle mode, the MS listens to the BCCH and to the paging sub-channel for the paging group the MS belongs to in idle mode (cf. 3GPP TS 03.13); it measures the radio propagation for connection with other cells.

In packet idle and packet transfer modes (applicable only to a GPRS mobile station), the mobile station listens to either the PBCCH, if that is present in the cell, or BCCH. The requirements for the monitoring of system information is further specified in 3GPP TS 04.60. Moreover, the mobile station measures the radio propagation for connection with other cells.

In packet idle mode (applicable only to a GPRS mobile station), the mobile station listens to the paging sub-channels on the PCCCH or CCCH. Paging sub-channels are monitored according to the paging group determined for the mobile station and its current discontinuous reception (DRX) mode. The determination of paging group for the mobile station is defined in 3GPP TS 05.02. The DRX procedures are defined in 3GPP TS 04.60 and 3GPP TS 05.02.

Measurements are treated to assess the need of a cell change as specified in 3GPP TS 05.08. When the decision to change cells is made, the mobile station switches to the BCCH or PBCCH of the new cell. The broadcast information is then checked to verify the allowance to camp on this cell (cf. sub-clause 3.2.2). Dependent on the mobile station type and configuration, the mobile station may be required to try to read further BCCH and PBCCH information. If allowed, the cell change is confirmed, and the broadcast information is then treated for Mobility Management actions (cf. sub-clause 4). Similarly, physical contexts are updated (list of neighbouring cells frequencies, thresholds for some actions, etc. (cf. 3GPP TS 05.08 and sub-clause 3.2.2)).

### 3.2.2 Network side

SYSTEM INFORMATION TYPE 2 to 4 messages, and optionally TYPE 1, 2bis, 2ter, 7, 8, 13, 16 and 17 and further types are regularly broadcast by the network on the BCCH. Based on this information the mobile station is able to decide whether and how it may gain access to the system via the current cell. The SYSTEM INFORMATION TYPE 2bis message shall be sent if and only if the EXT-IND bit in the Neighbour Cells Description IE in both the TYPE 2 and TYPE 2bis messages indicates that each IE only carries part of the BA. SYSTEM INFORMATION TYPE 2ter message shall be sent if and only if this is indicated in SYSTEM INFORMATION TYPE 3 message.

A GSM 900 mobile station which only supports the primary GSM band P-GSM 900 (cf. 3GPP TS 05.05) may consider the EXT-IND bit in the Neighbour Cells Description IE in the SYSTEM INFORMATION TYPE 2 message as a spare bit. If it does so it shall assume that the information element carries the complete BA and it shall ignore any SYSTEM INFORMATION TYPE 2bis and 2ter messages.

If the additional cell reselection parameters are broadcast then SYSTEM INFORMATION TYPE 3 message shall always contain these parameters. In addition to SYSTEM INFORMATION TYPE 3 at least either SYSTEM INFORMATION TYPE 4 or SYSTEM INFORMATION TYPE 7 and 8 messages shall contain these parameters too.

If additional SoLSA specific parameters are broadcast then SYSTEM INFORMATION TYPE 16 and 17 messages, shall always contain these parameters. In addition to SYSTEM INFORMATION TYPE 16 and 17 messages at least either SYSTEM INFORMATION TYPE 4 or SYSTEM INFORMATION TYPE 7 and 8 messages shall contain these SoLSA specific parameters too.

The support of GPRS shall be indicated in SYSTEM INFORMATION TYPE 3 message. In addition, the support of GPRS shall be indicated in either SYSTEM INFORMATION TYPE 4 or SYSTEM INFORMATION TYPE 7 and 8 messages. If GPRS is supported, SYSTEM INFORMATION TYPE 13 message shall be sent. SI 13 message shall not be sent if GPRS is not supported. Additional requirements for the broadcast of system information in a cell supporting GPRS are specified in 3GPP TS 04.60.

NOTE 1: The allowed scheduling of SYSTEM INFORMATION messages on the BCCH are specified in 3GPP TS 05.02.

NOTE 2: The network should take into account limitations of certain mobile stations to understand SYSTEM INFORMATION TYPE 2bis, TYPE 2ter, the EXT-IND bit in the Neighbour Cells Description, the indication of 2ter in SYSTEM INFORMATION TYPE 3 and formats used in the Neighbour Cells Description IE and Cell Channel Description IE used in SYSTEM INFORMATION messages, see this sub-clause, sub-clause 10.5.2.1b, and sub-clause 10.5.2.22.

NOTE 3: The network should take into account the limitations of earlier version of mobile equipments to understand the 3-digit MNC format of the location area identification, see sub-clause 10.5.1.3.

The information broadcast may be grouped in the following classes:

– information giving unique identification of the current network, location area and cell;

– information used for candidate cell measurements for handover and cell selection procedures;

– information describing the current control channel structure;

– information controlling the random access channel utilization;

– information defining different options supported within the cell; and

– information about the length of the part of the message belonging to the phase 1 protocol.

The network may send to the mobile station BCCH scheduling information as specified below:

1) The BCCH scheduling information may be contained in the SYSTEM INFORMATION TYPE 9 messages. If so, SYSTEM INFORMATION TYPE 3 specifies where to find SYSTEM INFORMATION TYPE 9 messages carrying BCCH scheduling information.

2) If the mobile station has received BCCH scheduling information, it shall assume that this BCCH scheduling information is valid in the location area until new scheduling information is received. It may store the information in the ME and assume its validity after switch on in the same location area.

3) The network need not indicate the schedule of all SYSTEM INFORMATION messages in SYSTEM INFORMATION 9. For any System Information message, the MS shall monitor all blocks specified in 3GPP TS 05.02 for that System Information message and all blocks specified in the SYSTEM INFORMATION TYPE 9 message for that System Information message.

4) When the mobile station detects that the BCCH information is not scheduled as defined in the last received SI 9 message, it shall read the SYSTEM INFORMATION TYPE 3 message. If presence of BCCH scheduling information in SYSTEM INFORMATION TYPE 9 message is indicated, it shall try to read the information and continue as in 2 above. If presence of BCCH scheduling information in SYSTEM INFORMATION TYPE 9 message is not indicated, it shall assume that there is no valid BCCH scheduling information.

#### 3.2.2.2 Paging

The network is required to send valid layer 3 messages continuously on all paging subchannels on CCCH.

## 3.3 RR connection establishment

### 3.3.1 RR connection establishment initiated by the mobile station

The purpose of the immediate assignment procedure is to establish an RR connection between the mobile station and the network.

#### 3.3.1.1 Entering the dedicated mode : immediate assignment procedure

The immediate assignment procedure can only be initiated by the RR entity of the mobile station. Initiation is triggered by request from the MM sublayer or LLC layer to enter the dedicated mode or by the RR entity in response to a PAGING REQUEST message or to initiate a notification response procedure. Upon such a request,

– if access to the network is allowed (as defined in sub-clause 3.3.1.1.1), the RR entity of the mobile station initiates the immediate assignment procedure as defined in sub-clause 3.3.1.1.2;

– otherwise, it rejects the request.

The request from the MM sublayer to establish an RR connection specifies an establishment cause. Similarly, the request from the RR entity to establish a RR connection in response to a PAGING REQUEST 1, 2 or 3 message specifies one of the establishment causes "answer to paging"; the request from the RR entity to establish an RR connection in order to initiate a notification response procedure specifies one of the establishment causes " procedures that can be completed with a SDCCH".

##### 3.3.1.1.1 Permission to access the network

All mobile stations with an inserted SIM are members of one out of 10 access classes numbered 0 to 9. The access class number is stored in the SIM. In addition, mobile stations may be members of one or more out of 5 special access classes (access classes 11 to 15) (see 3GPP TS 02.11), this is also held on the SIM card.

The system information messages on the BCCH broadcast the list of authorized access classes and authorized special access classes in the system information messages, and whether emergency calls are allowed in the cell to all mobile stations or only to the members of authorized special access classes.

If the establishment cause for the request of the MM sublayer is not "emergency call", access to the network is allowed if and only if the mobile station is a member of at least one authorized:

– access class; or

– special access class.

If the establishment cause for the request of the MM sublayer is "emergency call", access to the network is allowed if and only if:

– emergency calls are allowed to all mobile stations in the cell; or

– the mobile station is a member of at least one authorized special access class.

##### 3.3.1.1.2 Initiation of the immediate assignment procedure

The RR entity of the mobile station initiates the immediate assignment procedure by scheduling the sending on the RACH and leaving idle mode (in particular, the mobile station shall ignore PAGING REQUEST messages).

It then sends maximally M + 1 CHANNEL REQUEST messages on the RACH in a way such that:

– the number of slots belonging to the mobile station’s RACH 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 randomly for each new initial assignment initiation with uniform probability distribution in the set {0, 1, …, max (T,8) ‑ 1};

– the number of slots belonging to the mobile station’s RACH between two successive CHANNEL REQUEST messages (excluding the slots containing the messages themselves) is a random value drawn randomly for each new transmission with uniform probability distribution in the set {S, S + 1, …, S + T ‑ 1};

– here, T is the value of the parameter "Tx-integer" broadcast on the BCCH;

– M is the value of the 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 table 3.1/3GPP TS 04.08.

The CHANNEL REQUEST messages are sent on the RACH (cf. sub-clause 1.5) and contain as parameters:

– an establishment cause which corresponds to the establishment cause given by the MM sublayer and the broadcast NECI value, or which corresponds to one of the establishment causes "answer to paging" given by the RR entity in response to a PAGING REQUEST message including the Channel Needed information, or which corresponds to one of the establishment causes " procedures that can be completed with a SDCCH" given by the RR entity in order to initiate a notification response procedure;

– a random reference which is drawn randomly from a uniform probability distribution for every new transmission.

After sending the first CHANNEL REQUEST message, the mobile station shall start listening to the BCCH; it shall also listen to the full downlink CCCH timeslot corresponding to its CCCH group.

Having sent M + 1 CHANNEL REQUEST messages, the RR entity of the mobile station starts timer T3126. At expiry of timer T3126, the immediate assignment procedure is aborted; if the immediate assignment procedure was triggered by a request from the MM sublayer, a random access failure is indicated to the MM sublayer.

Table 3.1/3GPP TS 04.08: Values of parameter S

 TX-integer non combined CCCH combined CCH/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
##### 3.3.1.1.3 Answer from the network
###### 3.3.1.1.3.1 On receipt of a CHANNEL REQUEST message

The network may allocate a dedicated channel to the mobile station by sending an IMMEDIATE ASSIGNMENT message or IMMEDIATE ASSIGNMENT EXTENDED message in unacknowledged mode on the same CCCH timeslot on which it has received the CHANNEL REQUEST. There is no further restriction on what part of the downlink CCCH an IMMEDIATE ASSIGNMENT message or IMMEDIATE ASSIGNMENT EXTENDED message can be sent. The type of channel allocated (SDCCH or TCH; the channel mode shall be set to signalling only) is a network operator decision. Timer T3101 is then started on the network side.

NOTE: There are two types of immediate assignment messages:

– IMMEDIATE ASSIGNMENT message, containing assignment information for one mobile station only;

– IMMEDIATE ASSIGNMENT EXTENDED message, containing assignment information for two mobile stations at the same time.

The IMMEDIATE ASSIGNMENT or IMMEDIATE ASSIGNMENT EXTENDED message contains:

– the description of the assigned channel;

– the information field of the CHANNEL REQUEST message and the frame number of the frame in which the CHANNEL REQUEST message was received;

– the initial timing advance (cf. 3GPP TS 04.04);

– optionally, a starting time indication.

If frequency hopping is applied, the mobile station uses the last CA received on the BCCH to decode the Mobile Allocation.

On receipt of an IMMEDIATE ASSIGNMENT or IMMEDIATE ASSIGNMENT EXTENDED message corresponding to one of its 3 last CHANNEL REQUEST messages, the mobile station stops T3126 (if running), stops sending CHANNEL REQUEST messages, switches to the assigned channels, sets the channel mode to signalling only and activates the assigned channels. It then establishes the main signalling link with an SABM containing an information field (see sub-clause 3.1.5).

An IMMEDIATE ASSIGNMENT or IMMEDIATE ASSIGNMENT EXTENDED message may indicate a frequency change in progress, with a starting time and possibly alternative channel descriptions.

In the case of the reception of an IMMEDIATE ASSIGNMENT EXTENDED message, or of an IMMEDIATE ASSIGNMENT message which contains only the description of a channel to be used after the starting time, the mobile station shall wait up to the starting time before accessing the channel. If the starting time has already elapsed, the mobile shall access the channel as an immediate reaction to the reception of the message (see 3GPP TS 05.10 for the timing constraints).

If the message contains both the description of a channel to be used after the indicated time and of a channel to be used before, the mobile station accesses a channel as an immediate reaction to the reception of the message. If the moment the mobile station is ready to access is before the indicated time, the mobile station accesses the channels described for before the starting time. The mobile station then changes to the channel described for after the starting time at the indicated time. New parameters can be frequency list and MAIO. Other parameters describing the channel to be used before the starting time are taken from the description of the channel defined for use after the starting time. If the moment the mobile station is ready to access is after the starting time, the mobile station accesses the channel described for after the starting time.

If frequency hopping is applied, the mobile station uses the last CA received on the BCCH.

###### 3.3.1.1.3.2 Assignment rejection

If no channel is available for assignment, the network may send to the mobile station an IMMEDIATE ASSIGNMENT REJECT message in unacknowledged mode on the same CCCH timeslot on which the channel request message was received. There is no further restriction on what part of the downlink CCCH timeslot an IMMEDIATE ASSIGNMENT REJECT message can be sent. This message contains the request reference and a wait indication.

On receipt of an IMMEDIATE ASSIGNMENT REJECT message corresponding to one of its 3 last CHANNEL REQUEST messages, the mobile station, stops sending CHANNEL REQUEST messages, starts timer T3122 with the indicated value, ("wait indication" information element), starts T3126 if it has not already been started, and listens to the downlink CCCH until T3126 expires. During this time, additional IMMEDIATE ASSIGNMENT REJECT messages are ignored, but any immediate assignment corresponding to any other of its 3 last CHANNEL REQUEST messages make the mobile station follow the procedure in sub-clause 3.3.1.2. If no such immediate assignment is received, the mobile station returns to CCCH idle mode (listening to its paging channel).

As an option the mobile station may return to CCCH idle mode as soon as it has received responses from the network on all, or in case more than 3 were sent the last 3, of its CHANNEL REQUEST messages.

The mobile station is not allowed to make a new attempt to establish a non emergency RR connection in the same cell until T3122 expires. Provided that an IMMEDIATE ASSIGNMENT REJECT message has not been received for an emergency RR connection attempt, the mobile station may attempt to enter the dedicated mode for an emergency call in the same cell before T3122 has expired.

The Wait Indication IE (i.e. T3122) relates to the cell from which it was received.

The mobile station in packet idle mode (only applicable to mobile station supporting GPRS) may initiate packet access in the same cell before T3122 has expired, see 3GPP TS 04.60 and sub-clause 3.5.2.1.3.4.

After T3122 expiry, no CHANNEL REQUEST message shall be sent as a response to a page until a PAGING REQUEST message for the mobile station is received.

##### 3.3.1.1.4 Assignment completion

The immediate assignment procedure is terminated on the network side when the main signalling link is established. Timer T3101 is stopped and the MM sublayer on the network side is informed that the RR entity has entered the dedicated mode.

On the mobile station side, the procedure is terminated when the establishment of the main signalling link is confirmed. The MM sublayer is informed that the RR entity has entered the dedicated mode.

###### 3.3.1.1.4.1 Early classmark sending

Early classmark sending consists in the mobile station sending as early as possible after access a CLASSMARK CHANGE message to provide the network with additional classmark information.

A mobile station which implements the "Controlled Early Classmark Sending" option shall perform the early classmark sending if and only if explicitly accepted by the network, as indicated in the last reception in the accessed cell of the SYSTEM INFORMATION TYPE 3 message.

A mobile station which implements one or more of the "multiple band support" options shall also implement the "Controlled Early Classmark Sending" option.

A mobile station which implements the "multislot capability" option shall also implement the "Controlled Early Classmark Sending" option.

A mobile station that implements some form of treatment of UCS2 alphabet (see TS 3GPP TS 03.38) encoded character string (e.g., in short message, or in USSD string) may indicate so in the classmark. (An example is a Mobile Equipment able to display UCS2 encoded character string.) In such a case, it should also implement the "Controlled Early Classmark Sending" option. It is the mobile station responsibility to provide the UCS2 support information in due time. If the network needs this information and the mobile station did not provide it, the network may assume that the Mobile Equipment does not support UCS2.

A mobile station which implements the R-GSM band (see 3GPP TS 05.05) shall also implement the "Controlled Early Classmark Sending" option.

A mobile station which implements the extended measurement function shall also implement the "Controlled Early Classmark Sending" option.

A mobile station which implements the "GPRS" option shall also implement the "Controlled Early Classmark Sending" option.

A mobile station which implements the "SoLSA" option shall also implement the "Controlled Early Classmark Sending" option.

A mobile station which implements the "LCS" option shall also implement the "Controlled Early Classmark Sending" option.

A mobile station which implements the "Controlled Early Classmark Sending" option shall indicate it in the classmark (ES IND bit).

###### 3.3.1.1.4.2 GPRS suspension procedure

This procedure enables the network to suspend GPRS services packet flow in the downlink direction.

The GPRS suspension procedure is initiated by the mobile station by sending a GPRS SUSPENSION REQUEST message. This can be done as early as possible after access but shall be done after sending a CLASSMARK CHANGE message. The RR sublayer of the mobile station shall indicate a RR GPRS suspend condition to the MM sublayer, see sub-clause 4.

When a mobile station which is IMSI attached for GPRS services (sub-clause 4) enters the dedicated mode, and when the mobile station limitations make it unable to handle both dedicated mode and either packet idle mode or packet transfer mode simultaneously, the mobile station shall perform the GPRS suspension procedure.

##### 3.3.1.1.5 Abnormal cases

If a lower layer failure occurs on the mobile station side on the new channel before the successful establishment of the main signalling link, the allocated channels are released; the subsequent behaviour of the mobile station depends on the type of failure and previous actions.

– If the failure is due to information field mismatch in the contention resolution procedure, see sub-clause 3.1.5, and no repetition as described in this paragraph has been performed, the immediate assignment procedure shall be repeated.

– If the failure is due to any other reason or if a repetition triggered by a contention resolution failure has been performed. The mobile station returns to idle mode (RR connection establishment failure), transactions in progress are aborted and cell reselection then may take place.

If the information available in the mobile station, after the reception of an IMMEDIATE ASSIGNMENT message does not satisfactorily define a channel, an RR connection establishment failure has occurred.

If the Mobile Allocation IE indexes frequencies in more than one frequency band then a RR connection establishment failure has occurred.

If an IMMEDIATE ASSIGNMENT message indicates (a) channel(s) in a different frequency band to which the CHANNEL REQUEST message was sent then, if the frequency band is supported by the mobile station, the mobile station shall access the indicated channel(s) with the same power control level as used for the CHANNEL REQUEST message.

If an IMMEDIATE ASSIGNMENT message indicates a channel in non-supported frequency band then a RR connection establishment failure has occurred.

On the network side, if timer T3101 elapses before the main signalling link is established, the newly allocated channels are released and the request is forgotten. Note that the network has no means to distinguish repeated attempts from initial attempts from a mobile station.

#### 3.3.1.2 Entering the group transmit mode: uplink access procedure

Only applicable for mobile stations supporting "VGCS transmit".

The purpose of the uplink control procedure is to establish an RR connection on a VGCS channel between a mobile station which is in group receive mode on that channel and the network.

The mobile station enters the group transmit mode when a successful establishment of the RR connection is indicated. The channel mode assumed by the mobile station is the one derived from the channel description.

##### 3.3.1.2.1 Mobile station side

The mobile station in group receive mode shall consider the uplink as free if the last message indicating the uplink as being free was received less than 480 ms ago and if no UPLINK BUSY message has been received since the last message indicating the uplink as free.

On receipt of a request from the upper layer to access the uplink and if the uplink is not free, the mobile station starts the timer T3128.

If the uplink is free or becomes free before expiry of timer T3128, then the uplink investigation procedure is terminated, the mobile station shall stop T3128, and start the uplink access procedure.

NOTE: The start of the uplink access procedure is not subject to the access class of the mobile station.

If the uplink is not indicated free before the timer expires, the mobile station shall remain in the group receive mode and indicate a reject of the uplink request to the upper layer.

The mobile station shall send UPLINK ACCESS messages on the voice group call channel with the appropriate establishment cause. The first UPLINK ACCESS message shall be transmitted by the mobile station with a random delay between 0 and 20ms. The UPLINK ACCESS messages shall be repeated after a further period of 100ms plus a random delay between 0 and 20ms.

If an uplink identity code (UIC) of the current cell has been provided by the network in the UPLINK FREE message, the mobile station shall use this UIC IE for the coding of the UPLINK ACCESS messages (see 3GPP TS 05.03). If no UIC is provided, the mobile station shall use the BSIC received from the current cell, for instance from the initial synchronization.

Having sent the first UPLINK ACCESS message, the mobile station starts timer T3130. At expiry of timer T3130, the mobile station shall repeat the same procedure if the uplink is free. A maximum of three attempts is allowed and after that a rejection of the uplink request is indicated to the upper layers.

If no VGCS UPLINK GRANT or UPLINK BUSY message is received by the mobile station 480 ms after having sent the first UPLINK ACCESS message, the mobile station shall stop sending UPLINK ACCESS messages and wait in order to receive a VGCS UPLINK GRANT or UPLINK BUSY message.

On receipt of an VGCS UPLINK GRANT message corresponding to one of its UPLINK ACCESS messages, the mobile station stops T3130, stops sending UPLINK ACCESS messages, and establishes the main signalling link with an SABM containing the TALKER INDICATION message in the information field. Early classmark sending shall be performed if applicable. If a UA is received containing the message sent, the mobile station enters the group transmit mode and indicates the successful seizure of the uplink to the upper layer. If a UA is received with a message different from the message sent, the mobile station shall remain in the group receive mode and indicate the rejection of the uplink request to the upper layers.

When receiving an UPLINK BUSY message or a VGCS UPLINK GRANT message aimed to another mobile station (i.e., not corresponding to one of its UPLINK ACCESS messages), the mobile station stops T3130 and stops sending UPLINK ACCESS messages. The mobile shall remain in the group receive mode and shall indicate a rejection of the uplink request to the upper layers.

##### 3.3.1.2.2 Network side

After the data link layer is established, the RR entity of the network shall analyse the TALKER INDICATION message received from the mobile station, adapt the RR procedures to the new classmark if necessary and provide the mobile subscriber identity to the upper layer.

##### 3.3.1.2.3 Abnormal cases

If a lower link failure has occurred or an indication of the release of the data link layer was provided by the lower layer and no RR release request was previously received from the upper layer, the network shall provide an UPLINK FREE message on the main signalling channel and wait for a new UPLINK ACCESS message.

#### 3.3.1.3 Dedicated mode and GPRS

A mobile station whose Channel Request message contained a packet access establishment cause may receive an Immediate Assignment message to a Channel which is to be used in dedicated mode. A mobile station supporting the <<GPRS>> option shall obey this command. When establishing the main signalling link the information field in the SABM shall contain an RR INITIALISATION REQUEST message.

This message contains:

– TLLI;

– MS Classmark type 2;

– Ciphering Key Sequence Number;

– MAC Mode and Channel Coding Requested;

– Channel Request Description.

Following a successful contention resolution procedure, the mobile station shall implement the Early Classmark Sending option. Then, the upper layers in the mobile station shall wait for commands from the network, eg for the allocation of a GPRS resource.

While on the dedicated channel the mobile station shall obey the RR management procedures of 04.08, in particular the mobile station shall send measurement reports on the SACCH.

### 3.3.2 Paging procedure for RR connection establishment

The network can initiate the establishment of an RR connection by the paging procedure for RR connection establishment. Such a procedure can only be initiated by the network.

#### 3.3.2.1 Paging initiation by the network

The network initiates the paging procedure to trigger RR connection establishment by broadcasting a paging request message on the appropriate paging subchannel on CCCH or PCCCH, and starts timer T3113. The paging subchannels on CCCH and PCCCH are specified in 3GPP TS 05.02 and 3GPP TS 03.13.

The network may also send paging related information on PACCH to a mobile station in packet transfer mode, see sub-clause 3.3.2.1.3.

The network may also broadcast paging related information on any voice broadcast or voice group call channel downlink.

##### 3.3.2.1.1 Paging initiation using paging subchannel on CCCH

Paging initiation using the paging subchannel on CCCH is used when sending paging information to a mobile station in idle mode. It is also used when sending paging information to a mobile station in packet idle mode, if PCCCH is not present in the cell.

NOTE 1: There are 3 types of paging messages which may be used on CCCH:

– PAGING REQUEST TYPE 1;

– PAGING REQUEST TYPE 2; and

– PAGING REQUEST TYPE 3.

In a PAGING REQUEST message on CCCH to trigger RR connection establishment, the mobile station shall be identified by the TMSI (non-GPRS TMSI) or its IMSI. If the mobile station is identified by the TMSI, it shall proceed as specified in sub-clause 3.3.2.2.

If the mobile station in packet idle mode is identified by its IMSI, it shall parse the message for a corresponding Packet Page Indication field:

– if the Packet Page Indication field indicates a paging procedure for RR connection establishment, or the field is not present in the message, the mobile station shall proceed as specified in sub-clause 3.3.2.2;

– if the Packet Page Indication field indicates a packet paging procedure, the mobile station shall proceed as specified in sub-clause 3.5.1.2.

A PAGING REQUEST message on CCCH includes for each mobile station that is paged to trigger RR connection establishment an indication which defines how mobiles of different capabilities shall code the establishment cause field in the CHANNEL REQUEST message. The information received in the CHANNEL REQUEST can be used by the network to assign a suitable channel.

A PAGING REQUEST message on CCCH may include more than one mobile station identification.

A PAGING REQUEST TYPE 1 message on CCCH may have additionally a notification message coded in the P1 rest octets information element.

A PAGING REQUEST message on CCCH may also include priority levels related to the mobile station identifications. A mobile station in group receive mode supporting eMLPP shall take into account this information to decide whether to respond to this PAGING REQUEST and, if the call is answered, the mobile station shall store the priority level for the duration of the call. A mobile station not supporting eMLPP shall ignore this information element when received in a PAGING REQUEST message.

NOTE 2: A mobile station not supporting VGCS or VBS may ignore this information element when received in a PAGING REQUEST message, since the priority level is also provided in the SETUP message.

If VGCS or VBS is supported by the network and the network supports reduced NCH monitoring, messages sent on the PCH may also include an indication of the change of the information sent on the NCH (see sub-clause 3.3.3.2).

The choice of the message type depends on the number of mobile stations to be paged and of the types of identities that are used. The maximum number of paged mobile stations per message is 4 when using only TMSIs for identification of the mobile stations.

The mobile station in idle mode is required to receive and analyse the paging messages and immediate assignment messages sent on the paging subchannel corresponding to its paging subgroup, as specified in 3GPP TS 05.02.

NOTE 3: The possible immediate assignment messages are: the IMMEDIATE ASSIGNMENT, the IMMEDIATE ASSIGNMENT EXTENDED and the IMMEDIATE ASSIGNMENT REJECT messages.

The paging and immediate assignment type messages contain a page mode information element. This information element controls possible additional requirements on mobile stations belonging to the paging subgroup corresponding to the paging subchannel the message was sent on. This implies that a given mobile station shall take into account the page mode information element of any message sent on its own paging subchannel whatever the nature of this message (paging messages or immediate assignment messages). This further implies that the mobile station does not take into account page mode information element of messages sent on paging subchannels other than its own paging subchannel. The requirements yielded by the page mode information element are as follows:

a) normal paging: no additional requirements;

b) extended paging: the mobile station is required in addition to receive and analyse the next but one message on the PCH;

c) paging reorganization: The mobile station shall receive all messages on the CCCH regardless of the BS-AG-BLKS-RES setting. It is required to receive all BCCH messages. When the mobile station receives the next message to its (possibly new) paging subgroup the subsequent action is defined in the page mode information element in that message.

d) same as before: No change of page mode from the previous page mode.

Note that a mobile station takes into account the page mode information only in messages of its own paging subchannel whatever the currently applied requirements (a, b, c or d).

When the mobile station selects a new PCH, the initial page mode in the mobile station shall be set to paging reorganization. If a message in the paging subchannel is not received correctly, the message is ignored and the previous page mode is assumed.

##### 3.3.2.1.2 Paging initiation using paging subchannel on PCCCH

Paging initiation using a paging subchannel on PCCCH, see 3GPP TS 04.60, applies when sending paging information to a mobile station in packet idle mode and PCCCH is provided in the cell.

The paging initiation procedure and the paging request message used on PCCCH are specified in 3GPP TS 04.60.

##### 3.3.2.1.3 Paging initiation using PACCH

Paging initiation using PACCH, see 3GPP TS 04.60, applies to a mobile station in packet transfer mode.

The paging initiation procedure and the message used to carry paging related information on PACCH are specified in 3GPP TS 04.60.

#### 3.3.2.2 Paging response

Upon receipt of a paging request message, or other message containing information to trigger the establishment of a RR connection, and if access to the network is allowed, the addressed mobile station shall, when camped on a cell as specified in 3GPP TS 03.22, initiate the immediate assignment procedure as specified in 3.3.1. The establishment of the main signalling link is then initiated by use of an SABM with information field containing the PAGING RESPONSE message (see sub-clause 3.1.5). The MM sublayer in the mobile station is informed that the RR entity has entered the dedicated mode.

Upon receipt of the PAGING RESPONSE message the network stops timer T3113. The MM sublayer in the network is informed that an RR connection exists.

#### 3.3.2.3 Abnormal cases

Lower layer failure occurring during the immediate assignment procedure is treated as specified for that procedure.

If timer T3113 expires and a PAGING RESPONSE message has not been received, the network may repeat the paging request message and start timer T3113 again. The number of successive paging attempts is a network dependent choice.

mobile station network

PAGING REQUEST

<————————- Start T3113

RANDOM ACCESS

————————->

IMM ASSIGN

<————————- Start T3101

SABM (PAGING RESPONSE)

————————-> Stop T3101,

T3113

Figure 3.2/3GPP TS 04.08: Paging sequence

The network informs the mobile station of starting or on-going voice broadcast calls and voice group calls with the notification procedure.

In cases where the mobile station has initiated a VGCS call, if the channel mode modify procedure is applied to turn the dedicated channel into a VGCS channel and ciphering may be applied for that call, in this case the network should suspend transmission of notification messages until ciphering with the group cipher key has started on the dedicated channel.

#### 3.3.3.1 Notification of a call

The mobile station may receive a notification that a voice broadcast call or a voice group call is established. Notifications may be sent on the NCH, on the PCH, or on the FACCH when in dedicated mode or group receive mode. The presence of an NCH is indicated on the PCH in the Pi Rest Octets IE. A notification contains the group call reference and possibly other related information. This notification may be contained:

– in a NOTIFICATION/NCH message sent on the NCH to notify mobile stations of VBS or VGCS calls in the current cell, possibly together with a description of the related VBS or VGCS channel;

– in a NOTIFICATION/FACCH message sent in unacknowledged mode on the main DCCH to notify mobile stations in dedicated mode or on the main DCCH of a VGCS or VBS channel, of other VBS or VGCS calls in the current cell, possibly together with a description of the related VBS or VGCS channel;

– in the rest octets part of a PAGING REQUEST TYPE 1 message.

A mobile station supporting neither VGCS listening nor VBS listening may ignore the notifications sent on the NCH or PCH. It may also ignore the notifications sent on the main DCCH except that a RR-STATUS message shall be sent to the network with cause #97, "message not existent or not implemented".

Upon receipt of every notification message a mobile station supporting VGCS listening or VBS listening shall give an indication containing the notified group call reference(s) to upper layers in the mobile station which may then decide:

– not to react on the notification; or

– join the voice broadcast call or the voice group call, if needed after having stopped on going activities.

#### 3.3.3.2 Joining a VGCS or VBS call

In order to join a VGCS or a VBS call the following procedures apply.

In this sub-clause, the term notification refers to the notification which has triggered the decision to join a VGCS or VBS call.

If the notification on the main DCCH concerns a VBS or VGCS in the current cell and does not contain a description of the VGCS or VBS channel, the mobile station shall read the corresponding notification on the NCH.

If the description of the VGCS or VBS channel was included in the notification for the current cell, RR connection establishment shall not be initiated, instead, the mobile station shall enter the group receive mode.

If no description for the VGCS or VBS channel is included in the notification, the mobile station shall establish a RR connection in dedicated mode in order to initiate the notification response procedure.

#### 3.3.3.3 Reduced NCH monitoring mechanism

This sub-clause applies to mobile stations which read the NCH in idle mode in order to receive the notification messages for the voice broadcast call and the voice group call, which read the PCH to receive pagings and which aim at reducing the reception load.

A reduced NCH monitoring mechanism may be used on the NCH. When the mobile station in idle mode enters a cell and deduces from the BCCH that an NCH is present, it shall read the NCH until it has received at least two messages on the NCH indicating NLN, with the two last received NLN being identical. Then it may stop reading the NCH until it receives on the PCH an NLN(PCH) different from the last previously received NLN or on the SACCH an NLN(SACCH) different from the last previously received NLN.

A mobile is able to determine the reduced NCH monitoring is active in the network if it receives an NLN in any message. Once received, the mobile shall assume that NCH monitoring is active for a certain period of time which is not specified.

For this, parameters are provided:

The NLN is a modulo 4 counter which is changed every time a notification for a new VGCS or VBS call is started on the NCH. If the reduced NCH monitoring is indicated, the NLN provides information on new notifications provided on the NCH.

– NLN status:
The NLN status is a single bit field which indicates the status of the content of the NOTIFICATION/NCH messages for a particular NLN value. A change of the NLN status field indicates a change of information on the NCH which is not related to new calls (e.g. There may have been a release of a previous notified call or change of priority, etc …).

If the reduced NCH monitoring is active in the network, the network has to provide both NLN and NLN status parameters.

These parameters may be provided on the NCH, PCH and SACCH:

NLN status(PCH): NLN status (received on the PCH).

NLN status(SACCH): NLN status (received on the SACCH).

A mobile station supporting neither VGCS listening nor VBS listening shall ignore the NLN(NCH),NLN(PCH), NLN(SACCH) and NLN status fields.

If a mobile station (supporting VGCS listening and/or VBS listening) receives a NLN parameters on the NLN(PCH) or NLN(SACCH) field different from the last received NLN value it shall read the NCH until it has received at least two messages on the NCH indicating NLN with the two last received NLN being identical.

If a message in the paging subchannel is not received correctly, or if a paging message does not contain the information on the notification status, the mobile station shall read the NCH until it has received at least two messages on the NCH indicating NLN, with the two last received NLN being identical.

In order to initiate the notification response procedure, if access to the network is allowed, the mobile station shall, when camped on a cell as specified in 3GPP TS 03.22, initiate the immediate assignment procedure as specified in 3.3.1. The establishment of the main signalling link is then initiated by use of an SABM with information field containing the NOTIFICATION RESPONSE message (see sub-clause 3.1.5). The MM sublayer in the mobile station is informed that the RR entity has entered the dedicated mode.

Upon receipt of the NOTIFICATION RESPONSE message the network stops timer T3101. The MM sublayer in the network may be informed that an RR connection exists; in this case, the MM sublayer may initiate MM common procedures.

## 3.4 Procedures in dedicated mode and in group transmit mode

Procedures described in this sub-clause apply to the dedicated mode and/or the group transmit mode.

Those procedures which are specific for group transmit mode or refer to transitions to the group transmit mode are only applicable for mobile stations supporting VGCS talking.

Direct transition between dedicated mode and group transmit mode is possible in both directions by use of the following procedures:

– Channel assignment procedure;

– Handover procedure;

– Channel mode modify procedure.

### 3.4.1 SACCH procedures

#### 3.4.1.1 General

In dedicated mode and group transmit mode, the SACCH is used in signalling layer at least for measurement results transmission from the mobile station.

The SACCH has the particularity that continuous transmission must occur in both directions at least on the channel carrying the main signalling link. For that purpose, in the mobile station to network direction, measurement result messages are sent at each possible occasion when nothing else has to be sent (see sub-clause 3.4.1.2). Similarly, SYSTEM INFORMATION TYPE 5, 6 and optionally 5bis and 5ter messages are sent in the network to mobile station direction in UI frames when nothing else has to be sent.

In a multislot configuration the SYSTEM INFORMATION TYPE 5, 6 and optionally 5bis and 5ter messages shall be sent on the SACCH associated with the channel carrying the main signalling link.

In a multislot configuration the mobile station shall ignore all messages received on the SACCH(s) that are not associated with the channel carrying the main signalling link.

On a VGCS channel, the network may send additional or alternative system information messages for both mobile stations in group transmit mode and those in group receive mode (see sub-clause 3.4.15.2.1).

A mobile station with extended measurement capabilities which receives EXTENDED MEASUREMENT ORDER (EMO) messages on the SACCH, shall perform and report extended measurements, see sub-clause 3.4.1.3.

The SYSTEM INFORMATION TYPE 5bis message shall be sent if and only if the EXT IND bit in the Neighbour Cell Description information element in both the SYSTEM INFORMATION TYPE 5 and TYPE 5bis messages indicates that each information element only carries part of the BA.

A GSM 900 mobile station which only supports the primary GSM band P-GSM 900 (cf. 3GPP TS 05.05) may consider the EXT-IND bit in the Neighbour Cells Description IE in the SYSTEM INFORMATION TYPE 5 message bit as a spare bit, assume that the information element carries the complete BA, and ignore any SYSTEM INFORMATION TYPE 5bis messages.

NOTE: The network should take into account limitations of certain mobile stations to understand SYSTEM INFORMATION TYPE 5ter and TYPE 5bis messages, the EXT-IND bit in the Neighbour Cells Description, and formats used in the Neighbour Cells Description information element and Cell Channel Description information element used in SYSTEM INFORMATION messages, see sub-clause 10.5.2.1b, and sub-clause 10.5.2.22.

As specified in 3GPP TS 05.08, problems occurring in the reception of SACCH frames are interpreted as a loss of communication means and appropriate procedures are then triggered as specified in sub-clause 3.4.13.

#### 3.4.1.2 Measurement report

When in dedicated mode or group transmit mode, the mobile station regularly sends MEASUREMENT REPORT messages to the network. These messages contain measurement results about reception characteristics from the current cell and from neighbour cells. The BA (list) which is the basis for the measurements is derived from information received on the BCCH in System Information 2 and optionally 2bis and/or 2ter and on the SACCH in System Information 5 and optionally 5bis and/or 5ter.

When the information is received in more than one message the mobile station shall only combine information from messages received on the same channel and indicating the same value of the BCCH allocation sequence number without any message indicating a different value of the BCCH allocation sequence number received in between. If neighbouring cell information for the serving cell is not available, the mobile station indicates this in the MEASUREMENT REPORT message. These measurement results are obtained as specified in 3GPP TS 05.08.

These messages are sent on the slow ACCH, in unacknowledged mode.

If no other message is scheduled on the SACCH at the instant when a layer 2 frame is due to be sent, then the mobile station shall send a MEASUREMENT REPORT message or an extended measurement report message (see sub-clause 3.4.1.3) in that frame. The interval between two successive layer 2 frames containing measurement report messages shall not exceed one layer 2 frame.

#### 3.4.1.3 Extended measurement report $(MAFA)$

Only applicable to mobile stations which support extended measurement.

When in dedicated mode or group transmit mode, a mobile station may receive an EXTENDED MEASUREMENT ORDER (EMO) message, from the network. The mobile station shall then, as defined in 3GPP TS 05.08, for one reporting period perform measurements on the frequencies specified by this EMO message. The mobile station shall thereafter send an EXTENDED MEASUREMENT REPORT message. This message contains the measurement results as defined in 3GPP TS 05.08.

If the mobile station has not started to send its EXTENDED MEASUREMENT REPORT within 10 seconds after the reception of the EMO message, no EXTENDED MEASUREMENT REPORT shall be sent. The mobile station shall after a successful channel change abort any pending measurements or reporting related to an EMO message received on the old channel.

If a mobile station receives an EMO message indicating the same value of the sequence code as an EMO message received earlier on the same channel without having received any EMO message indicating a different value of the sequence code in between, that EMO message shall be ignored. If the mobile station, before the reporting related to an EMO message has started, receives a new EMO message with a different value of the sequence code, any pending measurements or reporting related to the earlier EMO message shall be aborted and the new message treated.

The EMO message and the EXTENDED MEASUREMENT REPORT message are sent on the SACCH, in unacknowledged mode.

### 3.4.2 Transfer of messages and link layer service provision

When in dedicated mode or in group transmit mode, upper layers can send messages in multiframe or unacknowledged mode on SAPI 0.

Moreover, but only when in dedicated mode, upper layers have access to the full link layer services for SAPIs other than 0, with the exception of the error indication and local end release that are directly treated by the RR sublayer, as specified in particular places of sub-clause 3.

### 3.4.3 Channel assignment procedure

In dedicated mode or in group transmit mode, an intracell change of channel can be requested by upper layers for changing the channel type, or decided by the RR sublayer, e.g. for an internal handover. This change may be performed through the dedicated channel assignment procedure.

The purpose of the channel assignment procedure is to completely modify the physical channel configuration of the mobile station without frequency redefinition or change in synchronization while staying in the same cell.

This procedure shall not be used for changing between dependent configurations, i.e. those sharing Radio Resource for the main signalling link. An example of dependent channels is a full rate channel and one of the corresponding half rate channels. In multislot operation however, it is allowed to use the same timeslots before and after the assignment, as long as the main signalling link has been changed. The only procedures provided for changing between dependent configurations for the main signalling link are the additional assignment and the partial release procedures.

The channel assignment procedure happens only in dedicated mode and in group transmit mode. This procedure cannot be used in the idle mode; in this case the immediate assignment procedure is used.

The channel assignment procedure includes:

– the suspension of normal operation except for RR management (layer 3).

– the release of the main signalling link, and of the other data links as defined in sub-clause 3.1.4, and the disconnection of TCHs if any.

– the deactivation of previously assigned channels (layer 1).

– the activation of the new channels and their connection if applicable.

– The triggering of the establishment of the data link connections for SAPI = 0.

The channel assignment procedure is always initiated by the network.

#### 3.4.3.1 Channel assignment initiation

The network initiates the channel assignment procedure by sending an ASSIGNMENT COMMAND message to the mobile station on the main signalling link. It then starts timer T3107.

NOTE: The network should take into account limitations of certain mobile stations to understand formats used in the Frequency List IE and Cell Channel Description IE used in the ASSIGNMENT COMMAND message, see sub-clause 10.5.2.13 and sub-clause 10.5.2.1b.

When sending this message on the network side, and when receiving it on the mobile station side, all transmission of signalling layer messages except for those RR messages needed for this procedure and for abnormal cases is suspended until resumption is indicated. These RR messages can be deduced from sub-clauses 3.4.3 and 8.8 Radio Resource management.

Upon receipt of the ASSIGNMENT COMMAND message, the mobile station initiates a local end release of link layer connections, disconnects the physical channels, commands the switching to the assigned channels and initiates the establishment of lower layer connections (this includes the activation of the channels, their connection and the establishment of the main signalling links).

The ASSIGNMENT COMMAND message contains the description of the new configuration, including for the multislot configuration and the TCH/H + TCH/H + ACCHs configuration, the exact ACCHs to be used and a power command. The power level defined in this power command shall be used by the mobile station for the initial power on the new channel(s). It shall not affect the power used on the old channel(s). The message may also contain definitions of the channel mode to be applied for one or several channel sets. If a previously undefined channel set is defined by the ASSIGNMENT COMMAND message, a definition of the channel mode for the new channel set shall be included in the message.

If the channel mode to be applied corresponds to an initial assignment of a multi-rate speech codec, the ASSIGNMENT COMMAND message shall contain the MultiRate Configuration IE, which defines the set of codec modes and related information to use on the new channel.

If the assignment is related to an intra-cell handover from a multi-rate speech codec to a multi-rate speech codec, the MultiRate Configuration IE shall be included in the case of full rate to half rate. If not included in this case, the mobile station shall behave as if the MultiRate Configuration IE was inconsistent. If not included in other cases, the MS shall use on the new channel the AMR configuration it was using on the old channel when it received the ASSIGNMENT COMMAND message.

An ASSIGNMENT COMMAND message may indicate a frequency change in progress, with a starting time and possibly alternative channel descriptions.

In the case of the reception of an ASSIGNMENT COMMAND message which contains only the description of a channel to be used after the starting time, the mobile station shall wait up to the starting time before accessing the channel. If the starting time has already elapsed, the mobile shall access the channel as an immediate reaction to the reception of the message (see 3GPP TS 05.10 for the timing constraints).

If the message contains both the description of a channel to be used after the indicated time and of a channel to be used before, the mobile station accesses a channel as an immediate reaction to the reception of the message. If the moment the mobile station is ready to access is before the indicated time, the mobile station accesses the channels described for before the starting time. The mobile station then changes to the channel described for after the starting time at the indicated time. New parameters can be frequency list, MAIO and HSN. Other parameters describing the allocated channels must be identical to the parameters described for before the starting time. If the moment the mobile station is ready to access is after the starting time, the mobile station accesses the channel described for after the starting time.

If frequency hopping is applied, the cell allocation if present in the message is used to decode the mobile allocation. If the cell allocation is not included, the mobile station uses its current cell allocation, the current CA is the last CA received on the BCCH. Afterward, the current CA may be changed by some messages sent on the main signalling link containing a CA (the possible messages are: ASSIGNMENT COMMAND, HANDOVER COMMAND and FREQUENCY REDEFINITION). Note that there are cases in which the current CA is undefined, see sub-clause 3.4.3.3.

The ASSIGNMENT COMMAND message may contain a cipher mode setting IE. In that case, this ciphering mode has to be applied on the new channel. If no such information is present, the ciphering mode is the same as on the previous channel. In either case the ciphering key shall not be changed. The ASSIGNMENT COMMAND message shall not contain a cipher mode setting IE that indicates "start ciphering" unless a CIPHERING MODE COMMAND message has been transmitted earlier in the RR connection: if such an ASSIGNMENT COMMAND message is received it shall be regarded as erroneous, an ASSIGNMENT FAILURE with cause "Protocol error unspecified" message shall be returned immediately, and no further action taken.

In a voice group call, the ASSIGNMENT COMMAND message may contain a VGCS target mode information element defining which RR mode is to be used on the new channel (i.e. dedicated mode or group transmit mode). If this information element is not present, the mode shall be assumed to be the same as on the previous channel. The VGCS target mode information element shall also indicate the group cipher key number for the group cipher key to be used on the new channel or if the new channel is non ciphered. If the information element is not present, the ciphering mode and group cipher key shall be the same as on the previous channel. Mobile stations not supporting VGCS talking shall ignore the ASSIGNMENT COMMAND message if the VGCS target mode information element is included in the message and shall send an RR STATUS message to the network with cause #96. If a VGCS target mode information element and a cipher mode setting information element is included in the same message, then a mobile station supporting VGCS talking mobile shall regard the ASSIGNMENT COMMAND message as erroneous, an ASSIGNMENT FAILURE message with cause "Protocol error unspecified" shall be returned immediately, and no further action taken.

#### 3.4.3.2 Assignment completion

After the main signalling link is successfully established, the mobile station returns an ASSIGNMENT COMPLETE message, specifying cause "normal event", to the network on the main DCCH.

The sending of this message on the mobile station side and its receipt on the network side allow the resumption of the transmission of signalling layer messages other than those belonging to RR management.

At the receipt of the ASSIGNMENT COMPLETE message, the network releases the previously allocated resources and stops timer T3107.

#### 3.4.3.3 Abnormal cases

If the mobile station has no current CA and if it needs a CA to analyse the ASSIGNMENT COMMAND message, it stays on the current channel(s) and sends an ASSIGNMENT FAILURE message with cause "no cell allocation available".

If the ASSIGNMENT COMMAND message instructs the mobile station to use a Channel Description or Mode that it does not support, or if the Channel Mode to use is not defined for all channel sets, then the mobile station shall return an ASSIGNMENT FAILURE message with cause "channel mode unacceptable", and the mobile station shall remain on the current channel(s) and uses the old Channel Description or Channel Mode(s).

If the mobile station receives an ASSIGNMENT COMMAND message containing an inconsistent MultiRate Configuration IE, then the mobile station shall return an ASSIGNMENT FAILURE message with cause "channel mode unacceptable", and the mobile station shall remain on the current channel(s) and uses the old Channel Description or Channel Mode(s).

The MultiRate Configuration IE shall be considered as inconsistent by the MS if:

– the active set does not include any codec mode or the active set includes more than four codec modes; or

– one or more codec modes of the active codec set are not supported by the assigned channel; or

– the threshold and hysteresis values are not set according to requirements given in 3GPP TS 05.09.

If during the initial assignment of the multirate speech the mobile station receives an ASSIGNMENT COMMAND message and the MultiRate Configuration IE is not present, then the mobile station shall return an ASSIGNMENT FAILURE message with cause "channel mode unacceptable", and the mobile station shall remain on the current channel(s) and uses the old Channel Description or Channel Mode(s).

If the ASSIGNMENT COMMAND message instructs the mobile station to use a frequency that it is not capable of, then the mobile station shall return an ASSIGNMENT FAILURE message with cause "frequency not implemented", and the mobile station shall remain on the current channel(s).

If the mobile station receives an ASSIGNMENT COMMAND message with a Frequency List IE indicating frequencies that are not all in one band, then the mobile station shall stay on the current channel(s) and send an ASSIGNMENT FAILURE message with cause "frequency not implemented". If the mobile station receives an ASSIGNMENT COMMAND message with a Mobile Allocation IE indexing frequencies that are not all in one band, then the mobile station shall stay on the current channel(s) and send an ASSIGNMENT FAILURE message with cause "frequency not implemented".

NOTE: An ASSIGNMENT COMMAND message sent to a multi band mobile station shall not be considered invalid because it indicates frequencies that are all in a different frequency band to that of the current channel.

On the mobile station side, if a lower layer failure happens on the new channel before the ASSIGNMENT COMPLETE message has been sent, the mobile station deactivates the new channels, reactivates the old channels, reconnects the TCHs if any and triggers the establishment of the main signalling link. It then sends a ASSIGNMENT FAILURE message, cause "protocol error unspecified" on the main DCCH and resumes the normal operation, as if no assignment attempt had occurred. The operational parameters (e.g. ciphering mode) when returning on the old channel are those applied before the procedure.

When receiving the ASSIGNMENT FAILURE message, the network stops T3107.

If a lower layer failure happens while attempting to connect back to the old channels, the radio link failure procedure is applied (see sub-clause 3.4.13.2 for dedicated mode and sub-clause 3.4.13.5 for group transmit mode).

On the network side, if timer T3107 elapses before either the ASSIGNMENT COMPLETE message has been received on the new channels or an ASSIGNMENT FAILURE message is received on the old channels, the old channels and the new channels are released if they both were dedicated channels and, unless the mobile station has re-established the call, all contexts related to the connections with that mobile station are cleared. If one of the channels was a VGCS channel, it shall be maintained and the uplink shall be set free. If both channels were VGCS channels, the network shall maintain one of the channels and the uplink shall be set free.

On the network side, lower layer failure occurring on the old channels after the sending of the ASSIGNMENT COMMAND message are ignored. Lower layer failures occurring after the receipt of the SABM Frame on the new main signalling link are treated following the general rules (cf. sub-clause 3.5.2).

### 3.4.4 Handover procedure

In dedicated mode or group transmit mode, an intercell or intracell change of channel(s) can be requested by the network RR sublayer. This change may be performed through the handover procedure.

NOTE: The decision to do a handover and the choice of the new cell is out of the scope of the present document.

The purpose of the handover procedure is to completely modify the channels allocated to the mobile station e.g. when the cell is changed. A change in the channel configuration nature is possible. This procedure is used only while in dedicated mode or group transmit mode.

The handover procedure is also used by Location Services as described in 3GPP TS 03.71.

The handover procedure shall not be used for changing between dependent configurations (see sub-clause 3.4.3). An exception to this is when the handover procedure is used by Location Services. In this case the mobile may be commanded to attempt a handover to the same channel as currently assigned to the MS. The MS shall attempt to perform a handover to this unchanged channel, which includes the transmission of access bursts.

The handover procedure includes:

– The suspension of normal operation except for RR management (layer 3).

– The disconnection of the main signalling link, and of the other links via local end release (layer 2), and the disconnection of the TCH(s) if any.

– The disconnection and the deactivation of previously assigned channels and their release (layer 1).

– The activation of the new channels, and their connection if applicable.

– The triggering of the establishment of data link connection for SAPI = 0 on the new channels.

The handover procedure is always initiated by the network.

#### 3.4.4.1 Handover initiation

The network initiates the handover procedure by sending a HANDOVER COMMAND message to the mobile station on the main DCCH. It then starts timer T3103.

NOTE: The network should take into account limitations of certain mobile stations to understand formats used in the Frequency List IE, Frequency Short List IE, and Cell Channel Description IE used in the HANDOVER COMMAND message, see sub-clause 10.5.2.13, sub-clause 10.5.2.14, and sub-clause 10.5.2.1b.

When sending this message on the network side, and when receiving it on the mobile station side, all transmission of signalling layer messages except for those RR messages needed for this procedure and for abnormal cases, is suspended until resuming is indicated. These RR messages can be deduced from sub-clause 3.4.3 and 8.5.1 "Radio Resource management".

Upon receipt of the HANDOVER COMMAND message, the mobile station initiates, as described in sub-clause 3.1.4, the release of link layer connections, disconnects the physical channels, commands the switching to the assigned channels and initiates the establishment of lower layer connections (this includes the activation of the channels, their connection and the establishment of the data links).

The HANDOVER COMMAND message contains:

– The characteristics of the new channels, including for the multislot configuration and the TCH/H + TCH/H + ACCHs configuration the exact ACCHs to be used. The message may also contain definitions of the channel mode to be applied for one or several channel sets. If a previously undefined channel set is defined by the HANDOVER COMMAND message, a definition of the channel mode for the new channel set shall be included in the message.

– The characteristics of the new cell that are necessary to successfully communicate (e.g. frequency list in the case of slow frequency hopping), including the data that allows the mobile station to use the pre-knowledge about synchronization it acquires by the measurement process (i.e. BSIC + BCCH frequency).

– A power command (cf. 3GPP TS 05.08). The power level defined in this power command shall be used by the mobile station for the initial power on the new channel(s). It shall not affect the power used on the old channel(s).

– An indication of the physical channel establishment procedure to be used.

– A handover reference, used as specified in the following sub-clause. The choice of the handover reference by the network is out of the scope of the present document and left to the manufacturers.

– Optionally a timing advance to be used on the new cell.

– Optionally a cipher mode setting. In that case, this ciphering mode has to be applied on the new channel. If no such information is present, the ciphering mode is the same as on the previous channel. In either case the ciphering key shall not be changed. The HANDOVER COMMAND message shall not contain a cipher mode setting IE that indicates "start ciphering" unless a CIPHERING MODE COMMAND message has been transmitted previously in this instance of the dedicated mode: if such a HANDOVER COMMAND message is received it shall be regarded as erroneous, a HANDOVER FAILURE message with cause "Protocol error unspecified" shall be returned immediately, and no further action taken.

– Optionally, in a voice group call, a VGCS target mode information element defining which RR mode is to be used on the new channel (i.e. dedicated mode or group transmit mode). If this information element is not present, the mode shall be assumed to be the same as on the previous channel. The VGCS target mode information element shall also indicate the group cipher key number for the group cipher key to be used on the new channel or if the new channel is non ciphered. If the information element is not present, the ciphering mode and ciphering key shall be the same as on the previous channel. Mobile stations not supporting VGCS talking shall ignore the HANDOVER COMMAND message if the VGCS target mode information element is included in the message and shall send an RR STATUS message to the network with cause #96. If a VGCS target mode information element and a cipher mode setting information element is included in the same message, then a mobile station supporting VGCS talking shall regard the HANDOVER COMMAND message as erroneous, an HANDOVER FAILURE message with cause "Protocol error unspecified" shall be returned immediately, and no further action taken.

– Optionally, when the channel mode indicates that a multi-rate speech codec must be applied, the MultiRateconfiguration to be used in the new cell. The MultiRate Configuration IE defines the set of codec mode and related information to use after the handover. When accessing the new channel, the mobile station shall use for the Initial Codec Mode the mode specified in the MultiRate Configuration IE, if present, or apply by default the implicit rule defined in 3GPP TS 05.09.

In addition, a HANDOVER COMMAND message may indicate a frequency change in progress, with a starting time and possibly alternative channel descriptions.

In the case of the reception of a HANDOVER COMMAND message which contains only the description of a channel to be used after the starting time, the mobile station shall wait up to the starting time before accessing the channel. If the starting time has already elapsed, the mobile shall access the channel as an immediate reaction to the reception of the message (see 3GPP TS 05.10 for the timing constraints).

If the message contains both the description of a channel to be used after the indicated time and of a channel to be used before, the mobile station accesses a channel as an immediate reaction to the reception of the message. If the moment the mobile station is ready to access is before the indicated time, the mobile station accesses the channels described for before the starting time. The mobile station then changes to the channel described for after the starting time at the indicated time. New parameters can be frequency list, MAIO and HSN. Other parameters describing the allocated channels must be identical to the parameters described for before the starting time. If the moment the mobile station is ready to access is after the starting time, the mobile station accesses the channel described for after the starting time.

If the channel mode indicates that a multi-rate speech codec must be applied, and the MultiRateConfiguration IE is not included in the HANDOVER COMMAND message, then the mobile station shall use on the new channel the AMR configuration it was using on the old channel when it received the HANDOVER COMMAND message. The MultiRate Configuration IE shall be included in the case of full rate channel to half rate channel handover. If not included in this case, the mobile station shall behave as if the MultiRate Configuration IE was inconsistent.

#### 3.4.4.2 Physical channel establishment

Four procedures are defined. The support of three of them is mandatory in the mobile station. The pseudo-synchronization case is optional in the mobile station. A pseudo-synchronized handover can be commanded only to a mobile station that can support it, as indicated in the classmark.

##### 3.4.4.2.1 Finely synchronized cell case

If the mobile station knows that the timing advance with the new cell is not out of range, i.e. smaller than or equal to the maximum timing advance that can be coded as specified in 3GPP TS 04.04, or if the new cell does accept out of range timing advance as indicated in the HANDOVER COMMAND message, the mobile station proceeds as follows.

After having switched to the assigned channels, the mobile station sends four times the HANDOVER ACCESS message in four successive layer 1 frames on the main DCCH. This message is sent in an access burst. Its content is reduced to the handover reference information element. The transmission of these four messages is optional if so indicated by the network in the HANDOVER COMMAND message.

Before completion of the 4 access bursts on the DCCH, additional access bursts may also be sent on the SACCH.

It then activates the channels in sending and receiving mode and connects the channels if need be.

If applicable, ciphering is immediately started . The access bursts are not ciphered.

##### 3.4.4.2.2 Non synchronized cell case

After having switched to the assigned channels, the mobile station starts repeating the HANDOVER ACCESS message in successive layer 1 frames on the main DCCH and optionally on the SACCH. This message is sent in an access burst. Its content is reduced to the handover reference information element. The mobile station starts timer T3124 at the start point of the timeslot in which the HANDOVER ACCESS message is sent the first time on the main DCCH.

The mobile station then activates the channels in receiving mode and connects the channels if need be (only for reception).

If applicable, deciphering is then immediately started . The access bursts are not ciphered.

When the network has the RF characteristics that are necessary, it sends in unacknowledged mode a PHYSICAL INFORMATION message to the mobile station on the main DCCH. If applicable, ciphering and deciphering is immediately started (i.e., before even the reception of a correct access burst), and the message is sent enciphered.

The PHYSICAL INFORMATION message contains various physical layer related information, allowing a proper transmission by the mobile station.

When sending the PHYSICAL INFORMATION message, the network starts timer T3105. If this timer times out before the reception of a correctly decoded layer 2 frame in format A or B (see 3GPP TS 04.06), or a correctly decoded TCH frame from the mobile station, the network repeats the PHYSICAL INFORMATION message and restarts timer T3105. The maximum number of repetitions is Ny1.

The correct decoding of a frame means that the decoding algorithm and the error detection tests, if any, indicate no error.

When the mobile station receives a PHYSICAL INFORMATION message, it stops timer T3124, stops sending access bursts, activates the physical channels in sending and receiving mode and connects the channels if need be. If the allocated channel is an SDCCH (+ SACCH), performance of the mobile station must enable the mobile station to accept a correct PHYSICAL INFORMATION message sent by the network in any block while T3124 is running.

##### 3.4.4.2.3 Pseudo-synchronized cell case

The details of the use of this procedure are described in 3GPP TS 05.10. The mobile station computes the timing advance to be used with the new cell from the real time difference value given in the HANDOVER COMMAND message. If the mobile station knows that the timing advance with the new cell is not out of range , i.e. smaller or equal to the maximum timing advance that can be coded as specified in 3GPP TS 04.04, or if the new cell accepts an out of range timing advance as indicated in the HANDOVER COMMAND message, the mobile station switches to the new channel and proceeds as follows.

After having switched to the assigned channels, the mobile station sends in four successive slots on the main DCCH a HANDOVER ACCESS message. This message is sent in random mode and thus does not follow the basic format. Its content is reduced to the handover reference information element. The transmission of these four messages is optional if so indicated by the network in the HANDOVER COMMAND message.

Before completion of the 4 access bursts on the DCCH, additional access bursts may also be sent on the SACCH.

The mobile station then activates the channels in sending and receiving mode and connects the channels if need be. The mobile station may activate the channels in receiving mode and connect the channels while sending access bursts.

If applicable, ciphering is then immediately started. The access bursts are not ciphered.

##### 3.4.4.2.4 Pre-synchronized cell case

The details of the use of this procedure are described in 3GPP TS 05.10. The mobile station switches to the new channel and proceeds as follows.

After having switched to the assigned channels, the mobile station sends in four successive slots on the main DCCH a HANDOVER ACCESS message. This message is sent in an access burst and thus does not follow the basic format. Its content is reduced to the handover reference information element. The transmission of these four messages is optional if so indicated by the network in the HANDOVER COMMAND message.

Before completion of the 4 access bursts on the DCCH, additional access bursts may also be sent on the SACCH.

The mobile station then activates the channel in sending and receiving mode and connects the channels if need be. The timing advance value to be used with the new cell is:

– either the value contained in the HANDOVER COMMAND message if the timing advance information element is present;

– or the default value for pre-synchronized handover as defined in 3GPP TS 05.10, if the timing advance information element is not included in the HANDOVER COMMAND message. The MS may activate the channels in receiving mode and connect the channels while sending access bursts.

If applicable, ciphering is immediately started. The access bursts are not ciphered.

#### 3.4.4.3 Handover completion

After lower layer connections are successfully established, the mobile station returns a HANDOVER COMPLETE message, specifying cause "normal event", to the network on the main DCCH.

The sending of this message on the mobile station side and its receipt on the network side allow the resumption of the transmission of signalling layer messages other than those for RR management.

When receiving the HANDOVER COMPLETE message, the network stops timer T3103 and releases the old channels.

If requested to do so in the HANDOVER COMMAND message, the mobile station includes the observed time difference it has measured when performing the handover, corrected by half the timing advance, in the HANDOVER COMPLETE message (detailed specifications are given in 3GPP TS 05.10).

#### 3.4.4.4 Abnormal cases

In the case of a synchronous or pseudo-synchronous handover, if the mobile station knows that the timing advance with the new cell is out of range, i.e. is bigger than the maximum timing advance that can be coded as specified in 3GPP TS 04.04, and if the new cell does not accept out of range timing advance as indicated in the HANDOVER COMMAND message, the mobile station sends a HANDOVER FAILURE message, cause "handover impossible, timing advance out of range", on the main signalling link and does not attempt that handover.

If the HANDOVER COMMAND message instructs the mobile station to use a Channel Description or Mode that it does not support, or if the Channel Mode to use is not defined for all channel sets, then the MS shall return a HANDOVER FAILURE message with cause "channel mode unacceptable", and the MS shall remain on the current channel(s) and uses the old Channel Description or Mode(s).

If the mobile station receives a HANDOVER COMMAND message containing an inconsistent MultiRateConfiguration IE, then the mobile station shall return a HANDOVER FAILURE message with cause "channel mode unacceptable", and the mobile station shall remain on the current channel(s) and uses the old Channel Description or Mode(s).

The MultiRate Configuration IE shall be considered as inconsistent by the MS if:

– the active set does not include any codec mode or the active set includes more than four codec modes; or

– one or more codec modes of the active codec set are not supported by the assigned channel; or

– the threshold and hysteresis values are not set according to requirements given in 3GPP TS 05.09.

If the HANDOVER COMMAND message instructs the mobile station to use a frequency that it is not capable of, then the mobile station shall return a HANDOVER FAILURE message with cause "frequency not implemented", and the mobile station shall remain on the current channel(s).

If the mobile station receives a HANDOVER COMMAND message with a Frequency List IE or Frequency Short List IE indicating frequencies that are not all in one band, then the mobile station shall stay on the current channel(s) and send a HANDOVER FAILURE message with cause "frequency not implemented". If the mobile station receives a HANDOVER COMMAND message with a Mobile Allocation IE indexing frequencies that are not all in one band, then the mobile station shall stay on the current channel(s) and send a HANDOVER FAILURE message with cause "frequency not implemented".

NOTE: A HANDOVER COMMAND message sent to a multi band mobile station shall not be considered invalid because it indicates target channel frequencies that are all in a different frequency band to that of the ARFCN in the Cell Description IE.

On the mobile station side, if timer T3124 times out (only in the non- synchronized case) or if a lower layer failure happens on the new channel before the HANDOVER COMPLETE message has been sent, the mobile station deactivates the new channels, reactivates the old channels, reconnects the TCHs if any and triggers the establishment of the main signalling link. It then sends a HANDOVER FAILURE message on the main signalling link and resumes normal operation as if no handover attempt had occurred. The operational parameters (e.g. ciphering mode) when returning on the old channel are those applied before the HANDOVER COMMAND message was received.

When the HANDOVER FAILURE message has been received, the network releases the new channels if they were dedicated channels and stops timers T3105 and stops T3103 in the non-synchronized case. If the new channels were VGCS channels, they shall be maintained.

If a lower layer failure happens while attempting to connect back to the old channels, the standard rules are applied (cf. sub-clause 3.4.13.2 for dedicated mode and 3.4.13.5 for group transmit mode).

On the network side, if timer T3103 elapses before either the HANDOVER COMPLETE message is received on the new channels, or a HANDOVER FAILURE message is received on the old channels, or the mobile station has re-established the call, the old channels are released if they were dedicated channels and all contexts related to the connections with that mobile station are cleared. If the old channel was a VGCS channel, it shall be maintained and the uplink shall be set free.

On the network side, if neither a correctly layer 2 frame in format A or B nor a correctly TCH frame have been received from the mobile station on the new channel, the newly allocated channels are released if they were dedicated channels. If the new channels were VGCS channels, they shall be maintained and the uplink shall be set free..

On the network side, lower layer failures occurring on the old channels after the sending of the HANDOVER COMMAND message are ignored. Lower layer failures occurring after the receipt of the SABM frame on the new main signalling link are treated following a general scheme (cf. sub-clause 3.4.13.2 for dedicated mode and sub-clause 3.4.13.5 for group transmit mode).

### 3.4.5 Frequency redefinition procedure

In dedicated mode and group transmit mode, this procedure is used by the network to change the frequencies and hopping sequences of the allocated channels. This is meaningful only in the case of frequency hopping.

The network sends to the mobile station a FREQUENCY REDEFINITION message containing the new parameters together with a starting time indication.

NOTE: The network should take into account limitations of certain mobile stations to understand formats used in the Cell Channel Description IE used in the FREQUENCY REDEFINITION message, see sub-clause 10.5.2.13.

When receiving such a message, the mobile station modifies the frequencies/hopping sequences it uses at the exact indicated time slot, i.e. the indicated time slot is the first with new parameters. All other functions are not disturbed by this change. New parameters can be the cell channel description, the mobile allocation and the MAIO. In case of multislot configuration, the Channel Description IE shall describe the channel carrying the main signalling link, the new parameters however, shall be used for all assigned timeslots. Other parameters describing the allocated channels must be identical to the current parameters.

#### 3.4.5.1 Abnormal cases

If the mobile station receives a FREQUENCY REDEFINITION message with a Mobile Allocation IE indexing frequencies that are not all in one band and a Starting Time IE indicating a time that has not elapsed, then the mobile station shall stay on the current channel(s) and send a RR STATUS message with cause "frequency not implemented".

If the mobile station receives a FREQUENCY REDEFINITION message with a Mobile Allocation IE indexing frequencies that are not all in one band and a Starting Time IE indicating a time that has elapsed, then the mobile station shall locally abort the radio connection and, if permitted, attempt Call Re-establishment.

If the mobile station receives a FREQUENCY REDEFENITION message on a channel for which it has a pending redefinition (defined by the immediate assignment, assignment or handover procedure or a previous frequency redefinition procedure) the frequencies, hopping and starting time parameters defined by the new frequency redefinition procedure supersedes those of the pending one.

NOTE: A FREQUENCY REDEFINITION message sent to a multi band mobile station shall not be considered invalid because it indicates new frequencies that are all in a different frequency band to that of the ARFCN of the serving cell.

### 3.4.6 Channel mode modify procedure

In dedicated mode or group transmit mode, higher layers can request the setting of the channel mode.

The channel mode modify procedure allows the network to request the mobile station to set the channel mode for one channel or one channel set. The procedure shall not be used if the multislot configuration contains more than one channel set. The channel mode covers the coding, decoding and transcoding mode used on the indicated channel.

This procedure is always initiated by the network.

NOTE: Direct transitions between full rate speech coder version 1 and full rate speech coder version 2 (and vice versa) may cause unpleasant audio bursts.

#### 3.4.6.1 Normal channel mode modify procedure

##### 3.4.6.1.1 Initiation of the channel mode modify procedure

The network initiates the procedure by sending a CHANNEL MODE MODIFY message to the mobile station. This message contains:

– a channel description of the channel(s) on which the mode in the CHANNEL MODE MODIFY message shall be applied; and

– the mode to be used on that channel, or on all the channels of a channel set in a multislot configuration;

– Optionally, when the channel mode indicates that a multi-rate speech codec must be applied, the MultiRateconfiguration to be used. The MultiRateConfiguration IE defines the set of codec mode and related information to use after the mode modify procedure.

If the channel mode is changed from a non multi-rate speech codec to a multi-rate speech codec, the CHANNEL MODE MODIFY message shall contain the MultiRate Configuration IE, which defines the set of codec modes and related information to use as a new mode.

If the old channel mode and the new channel mode are both multi-rate speech codec, the MultiRate Configuration IE may not be present. If not present, the MS shall go on with the current multi-rate speech configuration.

##### 3.4.6.1.2 Completion of channel mode modify procedure

When it has received the CHANNEL MODE MODIFY message, the mobile station sets the mode for the indicated channel, and if that is in a multislot configuration, the whole channel set and then replies by a CHANNEL MODE MODIFY ACKNOWLEDGE message indicating the ordered channel mode.

This applies whether the mode commanded by the CHANNEL MODE MODIFY is different from the one used by the mobile station or whether it is already in use.

##### 3.4.6.1.3 Abnormal cases

If the new mode is multi-rate speech codec and if the MultiRate Configuration IE is inconsistent, the MS shall ignore the CHANNEL MODE MODIFY message and shall not send CHANNEL MODE MODIFY ACKNOWLEDGE message to the network.

No other specific action for a lower layer failure is specified in this sub-clause. If the mobile station does not support the indicated mode, it shall retain the old mode and return the associated channel mode information in the CHANNEL MODE MODIFY ACKNOWLEDGE message.

#### 3.4.6.2 Channel mode modify procedure for a voice group call talker

##### 3.4.6.2.1 Initiation of the channel mode modify procedure

The network initiates the procedure by sending a CHANNEL MODE MODIFY message to the mobile station. This message contains:

– a channel description of the channel on which the CHANNEL MODE MODIFY message is sent; and

– the new channel mode to be used on the channel; and

– optionally, the VGCS target mode information element defining which RR mode is to be used with the new channel mode (i.e. dedicated mode or group transmit mode). If this information element is not present, the RR mode shall be assumed to be the same as with the previous channel mode. The VGCS target mode information element shall also indicate the group cipher key number for the group cipher key to be used on the new channel or if the new channel is non ciphered. If the information element is not present, the ciphering mode and ciphering key shall be the same as with the previous channel mode. Mobile stations not supporting VGCS talking shall ignore the CHANNEL MODE MODIFY message if the VGCS target mode information element is included in the message and shall send an RR STATUS message to the network with cause #96.

The start of ciphering with a group cipher key with the new channel mode is only possible when the mode on the old channel was not ciphered.

If a VGCS target mode information element indicating a group cipher key number is included in the message and the previous mode is not non ciphered and the group cipher key number is different to the previous cipher key number, the mobile station shall behave as if it would not support the indicated channel mode.

##### 3.4.6.2.2 Completion of mode change procedure

When it has received the CHANNEL MODE MODIFY message, the mobile station changes the mode for the indicated channel and then replies by a CHANNEL MODE MODIFY ACKNOWLEDGE message indicating the new channel mode.

##### 3.4.6.2.3 Abnormal cases

No specific action for a lower layer failure is specified in this sub-clause. If the mobile station does not support the indicated mode, it shall retain the old mode and return the associated channel mode information in the CHANNEL MODE MODIFY ACKNOWLEDGE message.

### 3.4.7 Ciphering mode setting procedure

In dedicated mode, the ciphering mode setting procedure is used by the network to set the ciphering mode, i.e. whether or not the transmission is ciphered, and if so which algorithm to use. The procedure shall only be used to change from "not ciphered" mode to "ciphered" mode, or vice-versa, or to pass a CIPHERING MODE COMMAND message to the mobile station while remaining in the "not ciphered" mode. The ciphering mode setting procedure is always triggered by the network and it only applies to dedicated resources.

The cipher mode setting procedure shall not be applied in group transmit mode.

#### 3.4.7.1 Ciphering mode setting initiation

The network initiates the ciphering mode setting procedure by sending a CIPHERING MODE COMMAND message to the mobile station on the main signalling link, indicating whether ciphering shall be used or not, and if yes which algorithm to use.

Additionally, the network may, by the use of the cipher response information element, request the mobile station to include its IMEISV in the CIPHERING MODE COMPLETE message.

The new mode is applied for reception on the network side after the message has been sent.

#### 3.4.7.2 Ciphering mode setting completion

Whenever the mobile station receives a valid CIPHERING MODE COMMAND message, it shall, if a SIM is present and considered valid by the ME and the ciphering key sequence number stored on the SIM indicates that a ciphering key is available, load the ciphering key stored on the SIM into the ME. A valid CIPHERING MODE COMMAND message is defined to be one of the following:

– one that indicates "start ciphering" and is received by the mobile station in the "not ciphered" mode;

– one that indicates "no ciphering" and is received by the MS in the "not ciphered" mode; or

– one that indicates "no ciphering" and is received by the mobile station in the "ciphered" mode.

Other CIPHERING MODE COMMAND messages shall be regarded as erroneous, an RR STATUS message with cause "Protocol error unspecified" shall be returned, and no further action taken.

Upon receipt of the CIPHERING MODE COMMAND message indicating ciphering, the mobile station shall start transmission and reception in the indicated mode.

When the appropriate action on the CIPHERING MODE COMMAND has been taken, the mobile station sends back a CIPHERING MODE COMPLETE message. If the "cipher response" field of the cipher response information element in the CIPHERING MODE COMMAND message specified "IMEI must be included" the mobile station shall include its IMEISV in the CIPHERING MODE COMPLETE message.

Upon receipt of the CIPHERING MODE COMPLETE message or any other correct layer 2 frame which was sent in the new mode, the network starts transmission in the new mode.

mobile station network

CIPH MOD CMD

<————————–

<—— start reception

start —> in new mode

transmission and ß

reception in new mode ß

CIPH MOD COM

————————–>

<—— start trans-

mission in new mode

Figure 3.3/3GPP TS 04.08: Ciphering mode setting sequence

### 3.4.8 Additional channel assignment procedure

NOTE: In the present state of 3GPP TS 04.03, this procedure is only possible for the TCH/H + ACCHs to TCH/H + TCH/H + ACCHs transition. As a consequence it is not needed for simple mobile stations. The description of the procedure is in general terms to cope with possible evolution.

In dedicated mode, a change of channel configuration to include an additional channel can be requested by upper layers.

The additional channel assignment procedure shall not be applied in group transmit mode.

The purpose of the additional assignment procedure is to allocate an additional dedicated channel to a mobile station while keeping the previously allocated channels. In particular the main DCCH and the SACCH are not modified, and signalling exchanges are not interrupted.

The additional assignment procedure may happen only in dedicated mode. It is used for instance for the transition from the TCH/H + ACCHs configuration to the TCH/H + TCH/H + ACCHs configuration.

The additional assignment procedure is always initiated by the network.

#### 3.4.8.1 Additional assignment procedure initiation

The network initiates the procedure by sending an ADDITIONAL ASSIGNMENT message to the mobile station on the main DCCH. The ADDITIONAL ASSIGNMENT message contains the description of the newly assigned channel.

On receipt of the message, the mobile station activates the new channel.

#### 3.4.8.2 Additional assignment procedure completion

The mobile station sends an ASSIGNMENT COMPLETE message to the network on the channel, on which it receives the ADDITIONAL ASSIGNMENT message.

#### 3.4.8.3 Abnormal cases

A lower layer failure occurring during the procedure is treated according to the general case (see sub-clause 3.4.13.2).

The network considers the channel as allocated from the sending of the ADDITIONAL ASSIGNMENT message. As a consequence, if a re-establishment occurs, the network will consider the context as if the mobile station has received the message, and the new configuration allocated after the re‑establishment may differ from the one the mobile station had before the re-establishment.

### 3.4.9 Partial channel release procedure

In dedicated mode, a change of channel configuration to release one channel can be requested by upper layers.

The partial channel release procedure shall not be applied in group transmit mode.

The purpose of this procedure is to deactivate part of the dedicated channels in use. The channel configuration remains dedicated.

NOTE: In the present state of 3GPP TS 04.03, this procedure is only possible for the TCH/H + TCH/H + ACCHs to TCH/H + ACCHs transition. As a consequence it is not needed for simple mobile stations.

The partial release procedure is always initiated by the network.

#### 3.4.9.1 Partial release procedure initiation

The network initiates the partial release by sending a PARTIAL RELEASE message to the mobile station on the main DCCH.

On receipt of the PARTIAL RELEASE message the mobile station:

– Initiates the disconnection of all the link layer connections carried by the channel to be released;

– Simultaneously initiates the connection on remaining channels of the data link layer connections that have been released;

– Deactivates the physical channels to be released.

– Sends a PARTIAL RELEASE COMPLETE to the network on the (possibly new) main signalling link.

#### 3.4.9.2 Abnormal cases

A lower layer failure is treated following the general rules as specified in sub-clause 3.4.13.2.

Moreover, on the network side, the channel configuration nature is set from the sending of the PARTIAL RELEASE message onward. As a consequence, any new assignment after a re‑establishment may concern a different channel configuration nature from the one known by the mobile station before the re‑establishment.

### 3.4.10 Classmark change procedure

In dedicated mode or in group transmit mode, this procedure allows the mobile station to indicate to the network a change of characteristics reflected in the classmark (e.g. due to addition of power amplification). Furthermore, a mobile station which implements the "controlled early classmark sending " option may also send a CLASSMARK CHANGE message as described in sub-clause 3.3.1.1.4, even if no change of characteristics has occurred.

The mobile station sends a CLASSMARK CHANGE message to the network. This message contains the new mobile station classmark 2 information element. It may also contain a Classmark 3 Information Element. There is no acknowledgement from the network at layer 3.

### 3.4.11 Classmark interrogation procedure

This procedure allows the network to request additional classmark information from the mobile station (e.g. if the information initially sent by the mobile station is not sufficient for network decisions).

#### 3.4.11.1 Classmark interrogation initiation

The network initiates the classmark interrogation procedure by sending a CLASSMARK ENQUIRY message to the mobile station on the main DCCH.

#### 3.4.11.2 Classmark interrogation completion

On receipt of the CLASSMARK ENQUIRY message the mobile station sends a CLASSMARK CHANGE message to the network on the main DCCH. This message contains the mobile station classmark 2 information element. It may also contain a Classmark 3 Information Element.

### 3.4.12 Indication of notifications and paging information

Only applicable for mobile stations supporting VGCS listening or VBS listening:

In dedicated mode or in group transmit mode, the RR entity shall provide indications to the upper layer on all received notifications for voice group calls or voice broadcast calls according to the VGCS or VBS subscription data stored in the mobile station. The indication shall include the notified group or broadcast call reference and possibly the related priority, if provided.

In group transmit mode, if the mobile station has received a paging message with the own mobile station identity on the PCH or on the voice group call channel downlink, the RR entity shall provide an indication to the upper layers, together with the related priority, if applicable.

In group transmit mode, if the RR entity receives information on the voice group call channel of the existence of a paging message in its paging subgroup of the PCH, the RR entity shall pass this information to the upper layers together with the related priority if provided (see also sub-clauses 3.3.2 and 3.3.3).

### 3.4.13 RR connection release procedure

#### 3.4.13.1 Normal release procedure

The release of the RR connection can be requested by upper layers.

The purpose of this procedure is to deactivate all the dedicated channels in use. When the channels are released, the mobile station returns to the CCCH configuration, idle mode. The channel release procedure can be used in a variety of cases, including TCH release after a call release, and DCCH release when a dedicated channel allocated for signalling is released.

In dedicated mode and group transmit mode, the channel release procedure is always initiated by the network.

If the mobile station is IMSI attached for GPRS services (sub-clause 4) at release of the RR connection, the mobile station shall return to packet idle mode, or if a temporary block flow is established, continue in packet transfer mode.

##### 3.4.13.1.1 Channel release procedure initiation in dedicated mode and in group transmit mode

The network initiates the channel release by sending a CHANNEL RELEASE message to the mobile station on the main DCCH, starts timer T3109 and deactivates the SACCH.

On receipt of a CHANNEL RELEASE message the mobile station starts timer T3110 and disconnects the main signalling link. When T3110 times out, or when the disconnection is confirmed, the mobile station deactivates all channels, considers the RR connection as released, and returns to CCCH idle mode.

NOTE 1: Data Links other than the main signalling link are disconnected by local end link release.

If case of dedicated mode, on the network side, when the main signalling link is disconnected, the network stops timer T3109 and starts timer T3111. When timer T3111 times out, the network deactivates the channels, they are then free to be allocated to another connection.

NOTE 2: The sole purpose of timer T3111 is to let some time to acknowledge the disconnection and to protect the channel in case of loss of the acknowledge frame.

If timer T3109 times out, the network deactivates the channels; they are then free to be allocated to another connection.

The CHANNEL RELEASE message will include an RR cause indication as follows:

#0 if it is a normal release, e.g. at the end of a call or at normal release of a DCCH.

#1 to indicate an unspecified abnormal release.

#2, #3 or #4 to indicate a specific release event.

#5 if the channel is to be assigned for servicing a higher priority call (e.g. an emergency call).

#65 if e.g. a handover procedure is stopped because the call has been cleared.

The CHANNEL RELEASE message may include the information element BA Range which may be used by a mobile station in its selection algorithm (see 3GPP TS 05.08 and 3GPP TS 03.22).

Mobile stations not supporting VGCS or VBS listening shall consider Group Channel Description and Group Cipher Key Number information elements as unnecessary in the message and perform the channel release procedure as normal.

For mobile stations supporting VGCS listening, the following procedures apply:

The CHANNEL RELEASE message may include the information element Group Channel Description. In this case, the mobile station shall release the layer 2 link, enter the group receive mode and give an indication to the upper layer. If a CHANNEL RELEASE message with no Group Channel Description is received, the normal behaviour applies.

If ciphering is applied on the VGCS or VBS channel, the network shall provide in the CHANNEL RELEASE message with the Group Cipher Key Number information element for the group cipher key to be used by the mobile station for reception of the VGCS or VBS channel. If this information element is not included, no ciphering is applied on the VGCS or VBS channel.

A mobile station not supporting the "GPRS " option shall consider the GPRS Resumption information element as an information element unknown in the message and continue the channel release procedure as normal.

For a mobile station supporting the "GPRS " option, the following additional procedures also apply:

The CHANNEL RELEASE message may include the information element GPRS Resumption. If the GPRS Resumption information element indicates that the network has resumed GPRS services, the RR sublayer of the mobile station shall indicate a RR GPRS resumption complete to the MM sublayer, see clause 4. If the GPRS Resumption information element indicates that the network has not successfully resumed GPRS services, the RR sublayer of the mobile station shall indicate a RR GPRS resumption failure to the MM sublayer, see sub-clause 4.

If the mobile station has performed the GPRS suspension procedure (sub-clause 3.3.1.1.4.2) and the GPRS Resumption information element is not included in the message, the RR sublayer of the mobile station shall indicate a RR GPRS resumption failure to the MM sublayer, see sub-clause 4.

If the mobile station has not performed the GPRS suspension procedure and the GPRS Resumption information element is not included in the message, the mobile station shall continue the channel release procedure as normal.

##### 3.4.13.1.2 Abnormal cases

Abnormal cases are taken into account in the main part of the description of the procedure.

The main part of these procedures concerns the "normal" cases, i.e. those without any occurrence of loss of communication means. A separate paragraph at the end of the description of each procedure treats the cases of loss of communication, called a radio link failure. In dedicated mode, in most of the cases the reaction of the mobile station or the network is the same. Those reactions are described in this sub-clause to avoid repetitions.

1) By analysis of reception at layer 1, as specified in 3GPP TS 05.08 and sub-clause 3.4.1.1.

2) By a data link layer failure as specified in 3GPP TS 04.06, on the main signalling link. A data link failure on any other data link shall not be considered as a radio link failure.

3) When a lower layer failure happens while the mobile station attempts to connect back to the old channels in a channel assignment procedure, handover procedure, PDCH assignment procedure or RR-cell change order procedure.

4) In some cases where timers are started to detect the lack of answer from the other party, as described in sub-clause 3.

The two first cases are known by the term "lower layer failure".

##### 3.4.13.2.1 Mobile side

‑ the MS shall perform a local end release on all signalling links unless otherwise specified;

‑ the mobile station shall deactivate all channels;

‑ the RR sublayer of the mobile station shall indicate an RR connection failure to the MM sublayer unless otherwise specified.

NOTE: Upper layers may decide on a re-establishment (cf. sub-clause 5.5.4).

When a mobile station which has performed the GPRS suspension procedure (sub-clause 3.3.1.1.4.2) detects a radio link failure, the RR sublayer of the mobile station shall indicate a RR GPRS resumption failure to the MM sublayer, see sub-clause 4.

##### 3.4.13.2.2 Network side

In dedicated mode, the reaction of the network to a lower layer failure depends on the context. Except when otherwise specified, it is to release the connection either with the channel release procedure as specified in sub-clause 3.5.1, or with the following procedure. The network starts timer T3109 and deactivates the SACCH (and hence to stop transmission on the SACCH).

When a radio link failure has been detected, an indication is passed to the upper Mobility Management sublayer on the network side.

When timer T3109 expires, the network can regard the channels as released and free for allocation.

This procedure relies on the fact that if a mobile station does not receive the SACCH for some time, it completely releases the channels (cf. 3GPP TS 05.08).

NOTE: The network should maintain for a while the transaction context in order to allow call re-establishment. The length of timer is for further study.

When a mobile station which has performed the GPRS suspension procedure (sub-clause 3.3.1.1.4.2) detects a radio link failure, the RR sublayer of the mobile station shall indicate a RR GPRS resumption failure to the MM sublayer, see sub-clause 4.

#### 3.4.13.3 RR connection abortion in dedicated mode

The mobile station aborts the RR connection by initiating a normal release of the main signalling link, performing local end releases on all other signalling links and disconnecting all traffic channels, if any.

When a mobile station which has performed the GPRS suspension procedure (sub-clause 3.3.1.1.4.2) aborts the RR connection, the RR sublayer of the mobile station shall indicate a RR GPRS resumption failure to the MM sublayer, see sub-clause 4.

#### 3.4.13.4 Uplink release procedure in group transmit mode

If the uplink release is requested by the upper layer the mobile station shall send an UPLINK RELEASE message on the voice group call channel uplink, perform a release of the main signalling link and go back to the group receive mode.

If the UPLINK RELEASE message is received from the network on the voice group call channel downlink, the MS shall perform a release of the main signalling link and go back to the group receive mode.

The main part of these procedures concerns the "normal" cases, i.e. those without any occurrence of loss of communication means. A separate paragraph at the end of the description of each procedure treats the cases of loss of communication, called a radio link failure. In group transmit mode, in most of the cases the reaction of the mobile station or the network is the same. Those reactions are described in this sub-clause to avoid repetitions.

1) By analysis of reception at layer 1, as specified in 3GPP TS 05.08 and sub-clause 3.4.1.1.

2) By a data link layer failure as specified in 3GPP TS 04.06, on the main signalling link. A data link failure on any other data link shall not be considered as a radio link failure.

3) When a lower layer failure happens while the mobile station attempts to connect back to the old channels in a channel assignment procedure or handover procedure.

4) In some cases where timers are started to detect the lack of answer from the other party, as described in sub-clause 3.

The two first cases are known by the term "lower layer failure".

##### 3.4.13.5.1 Mobile side

‑ the MS shall perform a local end release on all signalling links;

‑ the mobile station shall go back to idle mode and, when possible, to group receive mode;

‑ the RR sublayer of the mobile station shall indicate an RR connection failure to the MM sublayer unless otherwise specified.

##### 3.4.13.5.2 Network side

When the uplink has been allocated and the network detects a lower layer failure, the network shall set the uplink free and provide an UPLINK FREE message on the main signalling channel, when appropriate.

When a radio link failure has been detected, an indication is passed to the upper Mobility Management sublayer on the network side.

### 3.4.14 Receiving a RR STATUS message by a RR entity

If the RR entity of the mobile station receives a RR STATUS message no transition and no specific action shall be taken as seen from the radio interface, i.e. local actions are possible.

The actions to be taken on receiving a RR STATUS message in the network are an implementation dependent option see also sub-clause 8.

### 3.4.15 Group receive mode procedures

Only applicable for support of VGCS listening or VBS listening.

#### 3.4.15.1 Mobile station side

##### 3.4.15.1.1 Reception of the VGCS or VBS channel

In group receive mode, the mobile station receives the downlink of the voice broadcast channel or voice group call channel for which the channel description was provided within the notification message or in the related command message. The mobile station should also listen to the CCCH of the serving cell. Moreover, it measures the received levels on the serving cell and on the neighbour cells to assess the need for a cell reselection as specified in 3GPP TS 05.08. The general cell reselection procedure for the mobile station in group receive mode is described in 3GPP TS 03.22.

Information on neighbour cells used for cell reselection and reception of the VGCS or VBS channel in the neighbour cells may be provided on the downlink messages (see sub-clause 3.4.15.1.2). If no such information is provided or information is missing, the mobile station shall try to read this information on the BCCH and NCH of the neighbour cells.

##### 3.4.15.1.2 Monitoring of downlink messages and related procedures

Mobile stations in group receive mode shall monitor messages related to the following procedures on the VGCS or VBS channel downlink and act appropriately in order to be able to keep receiving the VGCS or VBS channel downlink.

All messages for mobile stations in group receive mode shall be sent in UI format on the VGCS or VBS channel downlink. Mobile stations in group receive mode shall ignore all messages which are not sent in UI format or which are not related to the following mentioned procedures.

The mobile should also monitor messages on the PCH or NCH of the current cell.

###### 3.4.15.1.2.3 Channel mode modify procedure

The mobile station shall receive CHANNEL MODE MODIFY messages. The mobile station shall use the new channel mode but shall not transmit any response to the network.

###### 3.4.15.1.2.4 Notification and paging information

The mobile station shall monitor messages related to notification and paging procedures.

The RR entity shall provide indications on all received notifications for voice group calls or voice broadcast calls to the upper layer. The indication shall include the notified group or broadcast call reference and, if provided, and if the mobile station supports eMLPP the related priority.

On request by the upper layer to join another voice broadcast call or voice group call for which a corresponding notification has been received on the VGCS or VBS channel downlink, the RR entity shall read the corresponding notification on the NCH.

If the mobile station has received a paging message with its own mobile station identity on the PCH or on the voice broadcast channel or voice group call channel downlink, the RR entity shall provide an indication to the upper layers, together with the related priority, if applicable.

3.4.15.1.2.4.1 Use of Reduced NCH monitoring

This sub-clause applies to mobile stations which are in group receive mode or group transmit mode of dedicated mode and which in addition want to receive notification messages for other voice broadcast calls or voice group calls and which aim at reducing the reception load.

If the reduced NCH monitoring mechanism is used on the NCH as defined in sub-clause 3.3.3.3, when the MS in group receive mode or group transmit mode enters a cell, it should read the NCH until it has received at least two messages on the NCH indicating NLN, with the two last received NLN being identical. Then it should stop reading the NCH until it receives on the SACCH an NLN(SACCH) different from the last previously received NLN.

For this, a parameter is provided on the SACCH in the SYSTEM INFORMATION TYPE 6 message:

If a mobile station receives on the SACCH an NLN(SACCH) different from the last received NLN it may read the NCH until it has received at least two messages on the NCH indicating NLN with the two last received NLN being identical.

If a message in the SACCH is not received correctly the MS may read the NCH until it has received at least two messages on the NCH indicating NLN, with the two last received NLN being identical.

NOTE: If the NLN(SACCH) is not provided on the SACCH, the mobile station, depending on its particular implementation, may either read the NCH while being in group receive mode or group transmit mode or may not be able to receive notifications for other voice group calls or voice broadcast calls other than those notifications provided on the FACCH.

Mobile stations supporting VGCS talking shall monitor the VGCS uplink control related messages UPLINK FREE and UPLINK BUSY.

###### 3.4.15.1.2.6 Channel release message

The mobile station shall receive CHANNEL RELEASE messages. On receipt of a CHANNEL RELEASE message, the RR entity shall go to idle mode and give an indication to the upper layer. (See also sub-clause 3.4.15.1.4.1, 4th paragraph.)

###### 3.4.15.1.2.7 Information on paging channel restructuring

On receipt of a SYSTEM INFORMATION TYPE 6 message indicating that paging channel restructuring has taken place, if the mobile station wants to be able to read its paging subchannel while in group receive mode or group transmit mode, the mobile station should read the related messages on the BCCH to know the position of its paging group.

Only applicable for mobile stations supporting "VGCS talking".

On receipt of an UPLINK FREE message with an uplink access request indication from the network on the voice group call channel downlink, the mobile station shall send two UPLINK ACCESS messages on the voice group call channel with establishment cause "Reply on uplink access request" and then stop immediately transmitting on the uplink.

The first UPLINK ACCESS message shall be transmitted by the mobile station with a random delay between 0 and 20 ms. The second UPLINK ACCESS messages shall be repeated after a further period of 100 ms plus a random delay between 0 and 20 ms.

If an uplink identity code (UIC) of the current cell has been provided by the network in the UPLINK FREE message, the mobile station shall use this UIC for the coding of the UPLINK ACCESS messages. If no UIC is provided, the mobile station shall use the BSIC received of the serving cell, for instance as received from the initial synchronization.

##### 3.4.15.1.4 Leaving the group receive mode

3.4.15.1.4.1 Returning to idle mode

If the mobile station enters a new cell in which:

‑ notifications for the current group or broadcast call are sent; but

‑ no VGCS or VBS channel description for the current group or broadcast call is provided;

– the mobile station shall go to idle mode and give an indication to the upper (sub-)layers.

NOTE: Upper (sub-)layers then can request the establishment of an RR connection in order to be informed about the channel description by the network.

If the mobile station enters a cell in which notifications for the current group or broadcast call are not sent, the mobile station shall disconnect locally the TCH, go to idle mode and give an indication to the upper (sub-)layers.

On request by the upper layer in order to respond to a paging message the RR entity shall go to the idle mode in order to establish a dedicated RR connection.

On receipt of a CHANNEL RELEASE message in UI format from the network the RR entity shall go to idle mode and give an indication to the upper layer.

If the upper layer requests to abort the group receive mode, the mobile station shall go back to idle mode.

3.4.15.1.4.2 Going to group transmit mode

Only applicable for mobile stations supporting VGCS talking.

If the upper layer requests an uplink access, the mobile station shall perform the uplink investigation procedure as defined in sub-clause 3.3.1.2.1.1.

If the uplink investigation procedure is not successful, the mobile station shall give an indication to the upper layers and remain in group receive mode.

If the uplink investigation procedure is successful, the uplink access procedure is initiated as defined in sub-clause 3.3.1.2.1.2.

If the uplink access procedure is successful, the mobile station shall give an indication to the upper layers and enter the group transmit mode.

If the uplink access procedure is not successful, the mobile station shall give an indication to the upper layers and remain in group receive mode.

#### 3.4.15.2 Network side

##### 3.4.15.2.1 Provision of messages on the VGCS or VBS channel downlink

3.4.15.2.1.1 General

The network shall provide all messages directed to mobile stations in group receive mode (see sub-clause 3.4.15.1.2) in unacknowledged mode. Those messages which are also sent to the mobile station in group transmit mode in acknowledged mode have therefore to be repeated in addition as UI messages on the VGCS channel downlink if they shall also be received by mobile stations in group receive mode.

3.4.15.2.1.2 Provision of general information messages

In the case where the group call area exceeds one cell, the network should provide the SYSTEM INFORMATION TYPE 6 message on the SACCH related to the voice broadcast channel or voice group call channel.

In addition, if the group call area exceeds one cell, the network should provide SYSTEM INFORMATION TYPE 5 (possibly together with TYPE 5bis and 5ter) on the SACCH related to the voice broadcast channel or voice group call channel.

– The SYSTEM INFORMATION TYPE 5, TYPE 5bis and TYPE 5ter messages provide information on the BCCH frequency of the neighbour cells.

– The SYSTEM INFORMATION TYPE 6 message provides information on the location area of the current cell, possibly the status of the NCH, and an indication of whether paging channel restructuring has taken place.

– $(ASCI)$ Optional messages of the SYSTEM INFORMATION TYPE 10 message type provide information improving cell re-selection in group receive mode.

The network may also provide layer 3 messages for notification on the VGCS or VBS channel downlink FACCH.

3.4.15.2.1.3 Provision of messages related to the voice group call uplink channel

Only applicable for the support of VGCS talking.

The network shall provide UPLINK FREE messages on the main signalling link of all voice group call channels when the uplink is set free. The provision of UPLINK FREE messages shall be repeated as long as no uplink is granted to a mobile station.

The network shall provide an UPLINK BUSY message on the main signalling link of all voice group call when the uplink has been granted to a mobile station.

The network may send UPLINK FREE messages containing an uplink access request on the main signalling channel of the VGCS channels in order to obtain knowledge on whether any listening mobile is present in a cell or not. If there is no mobile station responding to the uplink access request, the network may decide to clear the VGCS channel in that cell.

##### 3.4.15.2.2 Release of the VGCS or VBS Channels

If a release request for a voice group call is received from the upper layer, the network, after having released the RR connection with the mobile station in group transmit mode, shall stop the notification procedures for that voice group call and clear all related voice group call channels.

If a release request for a voice broadcast call is received from the upper layer, the network shall stop the notification procedures for that voice broadcast call and locally disconnect any channel related to the voice broadcast call.

#### 3.4.15.3 Failure cases

If the mobile station looses the voice group call channel or voice broadcast channel, the mobile station shall search all possible channel positions on the current cell and the neighbour cells for which a channel description is known for that call.

### 3.4.16 Configuration change procedure

This is only applicable for multislot configuration.

The configuration change procedure is used by the network to change the number of timeslots used in a multislot configuration. The procedure can also be used to change the channel mode of one or several channels and change their allocation. The main signalling link however, cannot be changed by the configuration change procedure. If a change of the main signalling link is needed, the assignment or handover procedures shall be used.

The network shall not initiate a new configuration change procedure before a response to the previous CONFIGURATION CHANGE COMMAND message has been received from the mobile station.

#### 3.4.16.1 Configuration change initiation

The procedure starts when the network sends a CONFIGURATION CHANGE COMMAND to the mobile station on the main DCCH. The message indicates:

– which timeslots to use in uplink;

– which timeslots to use in downlink; and

– which channel set each timeslot belongs to.

The message may also contain definitions of the channel mode to be applied for one or several channel sets. If a previously undefined channel set is defined by the CONFIGURATION CHANGE COMMAND a definition of the channel mode for the new channel set shall be included in the message.

#### 3.4.16.2 Configuration change completion

When the mobile station receives the CONFIGURATION CHANGE COMMAND it changes its configuration in accordance with the message contents and returns a CONFIGURATION CHANGE ACKNOWLEDGE on the same channel as the command message was received, confirming the new channel configuration. This applies irrespective of whether the new configuration is different from the one already in use by the mobile station or if it is the same.

#### 3.4.16.3 Abnormal cases

If the CONFIGURATION CHANGE COMMAND message instructs the mobile station to use a Channel Configuration or Mode(s) that it does not support, or if the channel mode to use is not defined for all channel sets, the mobile station shall return a CONFIGURATION CHANGE REJECT message with cause ‘channel mode unacceptable’, and the mobile station shall remain on the current channel(s) and use the old Channel Configuration and Channel Mode(s).

### 3.4.17 Mapping of user data substreams onto timeslots in a multislot configuration

For multislot configurations the following rules for mapping of the user data substreams onto timeslots shall apply for each channel set:

– at initial assignment (using assignment procedure), the lowest numbered user data substream shall be mapped to the lowest numbered timeslot etc. in ascending order (the user data substreams are numbered 0 to (n-1), where n is the number of substreams).

– at channel changes using handover procedure or assignment procedure (where none of the timeslots are present in both the old and the new configuration), the lowest numbered user data substream shall be mapped to the lowest numbered timeslot etc. in ascending order (the user data substreams are numbered 0 to (n-1), where n is the number of substreams).

– at channel changes using assignment procedure (where at least one of the timeslots is the same in both the old and the new configuration) or configuration change procedure:

– user data substream(s) mapped to timeslot(s) that are present in both the old and the new configuration shall continue to be mapped to the same timeslot(s) as before the channel change; and

– possibly added timeslot(s) shall carry the lowest numbered available user data substream so that the lowest numbered data substream among the added is mapped to the lowest numbered added timeslot and so on in ascending order.

NOTE: The user data substream number is a number that need not be the same as the inband number used for transparent services. The user data substream number is only used as a point of reference to a specific user data substream.

### 3.4.18 Handling of classmark information at band change

The coding of some fields in the Mobile Station Classmark 1 and in the Mobile Station Classmark 2 information elements depends on the band in use as described in sub-clause 10.5.1.5 and sub-clause 10.5.1.6. When a command to change the frequency band (GSM 900, DCS 1800) has been received (by, e.g., an IMMEDIATE ASSIGNMENT message, an ASSIGNMENT COMMAND message, a HANDOVER COMMAND message or a FREQUENCY REDEFINITION message) the following applies:

‑ When an IMMEDIATE ASSIGNMENT message is received, "the band used" for the purpose of coding the classmark information in the service request message, see sub-clause 3.1.5, shall be understood as the band used for the CHANNEL REQUEST message or (one of) the band(s) indicated by the IMMEDIATE ASSIGNMENT message.

‑ For other cases "the band used" for the purpose of coding the classmark information shall be understood as one of the bands used or attempted to be used within the 2 seconds preceding the passing of the layer 3 message containing the classmark information to the layer 2 send queue as described in 3GPP TS 04.06.

NOTE: This definition means that when a band change is being done the network must take appropriate actions to handle possible ambiguities in the frequency band related information in the classmark.

### 3.4.19 Assignment to a Packet Data channel

This sub-clause is only applicable to mobile stations supporting the "GPRS" option.

When in dedicated mode or in group transmit mode, the network may wish to change the resources used by a mobile station that supports the "GPRS option". This change may be performed through the assignment to a Packet Data Channel procedure.

The purpose of the assignment to PDCH channel procedure is to completely modify the physical channel configuration of the mobile station without frequency redefinition or change in synchronization while staying in the same cell.

The assignment to PDCH procedure only commences in dedicated mode or in group transmit mode. This procedure cannot be used in the idle mode.

The assignment to PDCH procedure includes:

– the suspension of normal operation.

– the release of the main signalling link, and of the other data links as defined in sub-clause 3.1.4, and the disconnection of TCHs if any.

– the deactivation of previously assigned channels (layer 1)

– the triggering of the establishment of a Temporary Block Flow.

The assignment to PDCH procedure is always initiated by the network.

#### 3.4.19.1 Assignment to PDCH initiation

The network initiates the assignment to PDCH procedure by sending a PDCH ASSIGNMENT COMMAND message to the mobile station on the main signalling link. It then starts timer T3117.

NOTE: The network should take into account limitations of certain mobile stations to understand formats used in the Frequency List IE and Cell Channel Description IE used in the PDCH ASSIGNMENT COMMAND message, see sub-clause 10.5.2.13 and sub-clause 10.5.2.1b.

When sending this message on the network side, and when receiving it on the mobile station side, all transmission of signalling layer messages except for those RR messages needed for this procedure and for abnormal cases is suspended until resumption is indicated. These RR messages can be deduced from sub-clauses 3.4.3 and 8.8 Radio Resource management.

Upon receipt of the PDCH ASSIGNMENT COMMAND message, the mobile station initiates a local end release of dedicated mode link layer connections, disconnects the physical channels, commands the switching to the identified channels and obeys the procedures relevant to the establishment of the Temporary Block Flow. The mobile station starts timer T3190.

The PDCH ASSIGNMENT COMMAND message contains the description of either the uplink TBF or the downlink TBF.

The information on the power to be used on the target TBF shall not affect the power used on the old channel(s).

A PDCH ASSIGNMENT COMMAND message may indicate a frequency change in progress, with a starting time and possibly alternative channel descriptions.

In the case of the reception of a PDCH ASSIGNMENT COMMAND message which contains only the description of a TBF to be used after the starting time, the mobile station shall wait up to the starting time before using the TBF. If the starting time has already elapsed, the mobile shall use the TBF as an immediate reaction to the reception of the message (see 3GPP TS 05.10 for the timing constraints).

If the message contains both the description of a TBF to be used after the indicated time and of a TBF to be used before, the mobile station uses the TBF as an immediate reaction to the reception of the message. If the moment the mobile station is ready to access is before the indicated time, the mobile station uses the TBF described for before the starting time. The mobile station then changes to the TBF described for after the starting time at the indicated time. New parameters can be frequency list, MAIO and HSN. Other parameters describing the allocated channels shall be identical to the parameters described for before the starting time. If the moment the mobile station is ready to access is after the starting time, the mobile station uses the TBF described for after the starting time.

If frequency hopping is applied, the cell allocation if present in the message is used to decode the mobile allocation. If the cell allocation is not included, the mobile station uses its current cell allocation, the current CA is the last CA received on the BCCH. Afterward, the current CA may be changed by some messages sent on the main signalling link containing a CA (the possible messages are: ASSIGNMENT COMMAND, HANDOVER COMMAND and FREQUENCY REDEFINITION). Note that there are cases in which the current CA is undefined, see sub-clause 3.4.3.3.

The PDCH ASSIGNMENT COMMAND does not contain a cipher mode setting IE. Any RR layer ciphering that may have been applied in dedicated mode shall not be applied to the target TBF.

#### 3.4.19.2 Completion of the Assignment to PDCH procedure

The network regards the procedure as successfully completed when RLC/MAC blocks are received from the mobile station on the target TBF. The network then stops timer T3117.

The mobile station regards the procedure as successfully completed when RLC/MAC blocks with any TFI are received on the new PDCH.

#### 3.4.19.3 Abnormal cases

If the mobile station has no current CA and if it needs a CA to analyse the PDCH ASSIGNMENT COMMAND message, it stays on the current channel(s) and sends an ASSIGNMENT FAILURE message with cause "no cell allocation available".

If the PDCH ASSIGNMENT COMMAND message instructs the mobile station to use a Coding Scheme that it does not support then the mobile station shall return an ASSIGNMENT FAILURE message with cause "channel mode unacceptable", and the mobile station shall remain on the current channel(s) and uses the old Channel Description or Channel Mode(s).

If the PDCH ASSIGNMENT COMMAND message instructs the mobile station to use a frequency that it is not capable of, then the mobile station shall return an ASSIGNMENT FAILURE message with cause "frequency not implemented", and the mobile station shall remain on the current channel(s).

If the mobile station receives a PDCH ASSIGNMENT COMMAND message with a Frequency List IE indicating frequencies that are not all in one band, then the mobile station shall stay on the current channel(s) and send an ASSIGNMENT FAILURE message with cause "frequency not implemented". If the mobile station receives a PDCH ASSIGNMENT COMMAND message with a Mobile Allocation IE indexing frequencies that are not all in one band, then the mobile station shall stay on the current channel(s) and send an ASSIGNMENT FAILURE message with cause "frequency not implemented".

NOTE: A PDCH ASSIGNMENT COMMAND message sent to a multi band mobile station shall not be considered invalid because it indicates frequencies that are all in a different frequency band to that of the current channel.

On the mobile station side, if RLC/MAC blocks are not successfully received within T3190 seconds, the mobile station reactivates the old channels, reconnects the TCHs if any and triggers the establishment of the main signalling link. It then sends an ASSIGNMENT FAILURE message, cause "protocol error unspecified" on the main DCCH and resumes the normal operation, as if no assignment attempt had occurred. The operational parameters (e.g. ciphering mode) when returning on the old channel are those applied before the procedure.

When receiving the ASSIGNMENT FAILURE message, the network stops T3117.

If a lower layer failure happens while attempting to connect back to the old channels, the radio link failure procedure is applied (see sub-clause 3.4.13.2).

On the network side, if timer T3117 elapses before either the network receives an RLC/MAC block from the mobile station on the new channel, or, an ASSIGNMENT FAILURE message is received on the old channels, then the old channels and the new resources are released, except that, if the old channel was a VGCS channel, the old channel shall be maintained and the uplink shall be set free.

On the network side, lower layer failure occurring on the old channels after the sending of the PDCH ASSIGNMENT COMMAND message are ignored.

### 3.4.20 RR-Network Commanded Cell Change Order

This sub-clause is only applicable to mobiles supporting the <<GPRS>> option.

In dedicated mode or in group transmit mode, intracell or intercell change of channel(s) can be requested by the network RR sublayer. This change may be performed through the RR-network commanded cell change order procedure.

The purpose of the RR-network commanded cell change order procedure is to permit the complete modification of the channels allocated to the mobile station e.g. when the cell is changed. This procedure only commences while in dedicated mode or in group transmit mode.

The RR-network commanded cell change order procedure includes:

– The suspension of normal operation except for RR management (layer 3).

– The disconnection of the main signalling link, and of the other links via local end release (layer 2), and the disconnection of the TCH(s) if any.

– The disconnection and the deactivation of previously assigned channels and their release (layer 1).

The complete acquisition of BCCH or PBCCH messages of the target cell.

– The triggering of the establishment of a Temporary Block Flow.

The RR-network controlled cell change order procedure is always initiated by the network.

#### 3.4.20.1 RR-network commanded cell change order initiation

The network initiates the RR-network controlled cell change order procedure by sending a RR-CELL CHANGE ORDER message to the mobile station on the main DCCH. The network then starts timer T3119.

When a handover has taken place during dedicated connection, the network shall send a RR-CELL CHANGE ORDER message to the mobile station in order to establish TBF. In this case the target cell is equal to the old cell.

When sending this message on the network side, and when receiving it on the mobile station side, all transmission of signalling layer messages except for those RR messages needed for this procedure and for abnormal cases, is suspended until resuming is indicated. These RR messages can be deduced from sub-clauses 3.4.3 and 8.5.1 "Radio Resource management".

Upon receipt of the RR-CELL CHANGE ORDER message, the mobile station starts timer T3134, and initiates, as described in sub-clause 3.1.4, the release of link layer connections, disconnects the physical channels, commands the switching to the identified cell, performs a complete acquisition of BCCH or PBCCH messages (see 3GPP TS 04.60), and obeys the procedures relevant to the establishment of the Temporary Block Flow. The mobile station shall obey the RR-CELL CHANGE ORDER irrespective of whether or not the mobile station has any knowledge of the relative synchronisation of the target cell to the serving cell.

The RR-CELL CHANGE ORDER message contains:

– The characteristics of the new cell that are necessary to identify it (i.e. BSIC + BCCH frequency).

– the NC mode to be initially applied on the new cell.

The RR-CELL CHANGE ORDER does not contain a cipher mode setting IE. Any RR layer ciphering that may have been applied in dedicated mode shall not be applied to the target TBF or with the target cell.

#### 3.4.20.2 Network controlled cell reselection completion

The network regards the procedure as successfully completed when it knows that communication has been established with that mobile station via the new cell (e.g. the network has received a RLC/MAC Block containing the mobile station’s identity). The network then stops timer T3119.

The mobile station regards the procedure as successfully completed when it has received a response to a (PACKET) CHANNEL REQUEST message on the new cell which allocates it a resource on the new cell.

#### 3.4.20.3 Abnormal cases

If the RR-CELL CHANGE ORDER message instructs the mobile station to use a frequency that it is not capable of, then the mobile station shall return a HANDOVER FAILURE message with cause "frequency not implemented", and the mobile station shall remain on the current channel(s).

On the mobile station side, if timer T3134 times out before a response to the (PACKET) CHANNEL REQUEST message has been received, or, if an IMMEDIATE ASSIGNMENT REJECT message or a PACKET ACCESS REJECT is received from the new cell, or, if the contention resolution procedure fails on the new cell then the mobile station shall reactivate the old channels, reconnect the TCHs if any and trigger the establishment of the main signalling link. It then sends a HANDOVER FAILURE message on the main signalling link and resumes normal operation as if no handover attempt had occurred. The operational parameters (e.g. ciphering mode) when returning on the old channel are those applied before the RR-CELL CHANGE ORDER message was received.

When the HANDOVER FAILURE message has been received, the network stops T3119.

If a lower layer failure happens while attempting to connect back to the old channels, the standard rules are applied (cf. sub-clause 3.4.13.2).

On the network side, if timer T3119 elapses before either the mobile station has been recognised on the new cell, or a HANDOVER FAILURE message is received on the old channels, then the old channels are released, except that, if the old channel was a VGCS channel, the old channel shall be maintained and the uplink shall be set free.

On the network side, lower layer failures occurring on the old channels after the sending of the RR-CELL CHANGE ORDER message are ignored.

### 3.4.21 Application Procedures

#### 3.4.21.1 General

While in dedicated mode, the following applications associated with the Radio Resource management layer may be supported in the network and MS:

Location Services (LCS).

Common procedures are defined in the Radio Resource management layer to assist these applications.

#### 3.4.21.2 Application Information Transfer

The Application Information Transfer procedure enables an Application on the network side and a peer application in the MS to exchange Application Protocol Data Units (APDUs).

##### 3.4.21.2.1 Normal Procedure without Segmentation

The maximum size of an APPLICATION INFORMATION message is 251 octets as defined in 3GPP TS 04.06. Segmentation shall not be used when an APDU fits into a single APPLICATION INFORMATION message of maximum or smaller size.

Mobile Station Network

APPLICATION INFORMATION [APDU, C/R ]

<————————–

APPLICATION INFORMATION [APDU, C/R]

————————–>

Figure 3.4/3GPP TS 04.08: Application Information Transfer without segmentation

Either the network or MS may send an APPLICATION INFORMATION message once the MS is in dedicated mode. The APDU Data in the APPLICATION INFORMATION message shall contain a complete APDU according to the protocol in use. The APDU ID IE identifies the protocol and associated application. The APDU Flags IE indicates "First or Only Segment", "Last or Only Segment" and conveys a C/R flag transparently between the communicating applications. The C/R Flag may be used to distinguish a command from other messages and a final response from a non-final response. The use of the C/R flag is defined with respect to each application. On receiving an APPLICATION INFORMATION message, the receiving layer 3 entity shall deliver the message contents to the identified local application.

##### 3.4.21.2.2 Normal Procedure with Segmentation

Segmentation is applicable when an APDU is too large to fit into a single APPLICATION INFORMATION message. The procedure is applicable for either direction of transfer.

Mobile Station or Network Network or Mobile Station

APPLICATION INFORMATION [APDU segment, First Segment, not Last Segment]

<————————–

APPLICATION INFORMATION [APDU segment, not First Segment, not Last Segment]

<————————–

APPLICATION INFORMATION [APDU segment, not First Segment, Last Segment, C/R]

<————————–

Figure 3.5/3GPP TS 04.08: Application Information Transfer with segmentation

The sending layer 3 entity shall segment an APDU by dividing it into one or more segments exactly fitting into maximum sized APPLICATION INFORMATION messages plus a final segment fitting into an APPLICATION INFORMATION message of maximum size or smaller. Once segmented, the resulting APPLICATION INFORMATION messages shall be transferred in sequence to the data link layer for transmission, without being intersperced by other level 3 messages. The first APPLICATION INFORMATION message in the sequence shall indicate "First Segment" and "Not Last Segment". Subsequent APPLICATION INFORMATION messages except for the last shall indicate "Not First Segment" and "Not Last Segment". The last APPLICATION INFORMATION message shall indicate "Not First Segment" and "Last Segment" and shall include a C/R flag as provided by the sending application.

The receiving layer 3 entity shall reassemble any segmented APDU before transfer to the local application. The receiver may employ a timer to detect possible loss of APDU segments. If employed, the timer shall be started when the first APDU segment is received and cancelled after the last segment is received.

##### 3.4.21.2.3 Abnormal Cases

APPLICATION INFORMATION messages are sent using "low" priority at the data link layer. This can lead to message loss or truncation when preempted by other "high" priority messages. A receiving layer 3 entity shall detect APDU truncation if an APPLICATION INFORMATION message is received carrying an APDU or APDU segment that is shorter than indicated by the length indicator for the APDU Data IE. This test is reliable because preemption in the data link layer guarantees that at least the first 2*N201 octets of any truncated message will be reliably transferred.

An APPLICATION INFORMATION transfer error shall be detected due to any of the following:

1. Receipt of a truncated APDU or APDU segment;
2. While performing APDU reassembly:

– receipt of any other layer 3 message defined to use SAPI 0 on the main DCCH;

– receipt of an APDU or APDU segment indicating "First or Only Segment";

– expiration of the reassembly timer (if supported);

1. While not performing APDU reassembly, receipt of an APDU segment indicating "not First or only segment";
2. Detection of any other error for a received message as defined in sub-clause 8.

If APDU reassembly was in process when the error occurred, the receiving layer 3 entity shall discard the partially reassembled APDU and reprocess any received APDU or APDU segment that caused the error provided not an error defined in clause 8. In all other cases, any received APDU or APDU segment shall be discarded.

## 3.5 RR procedures on CCCH related to temporary block flow establishment

The establishment of a temporary block flow (TBF) on a packet data physical channel is supported by procedures on CCCH when PCCCH is not provided in the cell. The procedures for temporary block flow establishment using CCCH are only applicable to a mobile station supporting GPRS. The procedures are optional for the network.

These procedures constitute a complement to the corresponding procedures for temporary block flow establishment using PCCCH, defined in 3GPP TS 04.60, and include the procedures using CCCH for packet paging (sub-clause 3.5.1), packet access (sub-clause 3.5.2) and packet downlink assignment (sub-clause 3.5.3).

### 3.5.1 Packet paging procedure using CCCH

The network can initiate the packet paging procedure in order to cause upper layers in the mobile station to respond, see clause 4. The packet paging procedure can only be initiated by the network.

#### 3.5.1.1 Packet paging initiation by the network

The packet paging procedure is initiated by the RR entity of the network side. It is triggered by a page request from the MM sublayer, see 3GPP TS 04.07.

The network initiates the paging procedure by sending a paging request message on an appropriate paging subchannel on CCCH or PCCCH. Paging initiation using a paging subchannel on CCCH is used when sending paging information to a mobile station and PCCCH is not present in the cell.

NOTE 1: There are three types of paging request messages that are applicable:

– PAGING REQUEST TYPE 1;

– PAGING REQUEST TYPE 2; and

– PAGING REQUEST TYPE 3.

In a PAGING REQUEST message used for the packet paging procedure, the mobile station shall be identified by the P-TMSI (GPRS TMSI) or its IMSI. If the mobile station is identified by the P-TMSI, it shall proceed as specified in sub-clause 3.5.1.2.

If the mobile station identified by its IMSI, it shall parse the message for a corresponding Packet Page Indication field:

– if the Packet Page Indication field indicates a paging procedure for RR connection establishment, or the field is not present in the message, the mobile station shall proceed as specified in sub-clause 3.3.2.2;

– if the Packet Page Indication field indicates a packet paging procedure, the mobile station shall proceed as specified in sub-clause 3.5.1.2.

A PAGING REQUEST message may include more than one mobile station identification.

The mobile station in packet idle mode is required to receive and analyse the paging messages and immediate assignment messages sent on the paging subchannels on CCCH corresponding to the paging groups determined for it in packet idle mode, as specified in 3GPP TS 05.02. These messages contain a page mode information element.

NOTE 2: The possible immediate assignment messages are: the IMMEDIATE ASSIGNMENT, the IMMEDIATE ASSIGNMENT EXTENDED and the IMMEDIATE ASSIGNMENT REJECT messages.

The treatment of page mode information, including the procedure when the mobile station selects a new PCH, and the procedure if a message in a paging subchannel is not received correctly are defined in sub-clause 3.3.2.1.1.

#### 3.5.1.2 On receipt of a packet paging request

On the receipt of a paging request message, the RR sublayer of addressed mobile station indicates the receipt of a paging request to the MM sublayer, see 3GPP TS 04.07.

### 3.5.2 Packet access procedure using CCCH

The packet access procedure using CCCH may be used to establish a temporary block flow to support the transfer of LLC PDUs in the direction from the mobile station to the network. Establishment using one phase and two phase packet access, see 3GPP TS 04.60, are supported. The two phase packet access is supported by means of the single block packet access option in this procedure, allowing the transfer of a PACKET RESOURCE REQUEST message to the network.

The single block packet access option in this procedure may also be used by a mobile station in packet idle mode to transfer an RLC/MAC control message other than the PACKET RESOURCE REQUEST message to the network, see sub-clause 3.5.2.2.

#### 3.5.2.1 Entering the packet transfer mode: packet access procedure

The establishment of an uplink temporary block flow may be initiated by the RR entity of the mobile station using the packet access procedure. The procedure is triggered by a request from upper layers to transfer a LLC PDU, see 3GPP TS 04.07. The request from upper layers specifies radio priority and an RLC mode associated with the packet transfer or it indicates that the packet to be transferred contains signalling.

Upon such a request:

– if access to the network is allowed (sub-clause 3.5.2.1.1), the RR entity of the mobile station initiates the packet access procedure as defined in sub-clause 3.5.2.1.2;

– otherwise, it rejects the request.

If the request from upper layers indicates signalling, the highest radio priority level shall be used at determination if access to the network is allowed, and the acknowledged RLC mode shall be used.

##### 3.5.2.1.1 Permission to access the network

– if the mobile station is a member of at least one authorized access class or special access class as defined in sub-clause 3.3.1.1.1, and

– if packet access is allowed in the cell for the radio priority level associated with the packet transfer, as indicated by the PRIORITY_ACCESS_THR parameter broadcast in SI 13 message;

– if the cell belongs to one of the allowed LSAs for the mobile station, as indicated on the SIM, in the case where the mobile station is a LSA only access subscriber.

##### 3.5.2.1.2 Initiation of the packet access procedure: channel request

The mobile station initiates the packet access procedure by scheduling the sending of CHANNEL REQUEST messages on RACH and leaving the packet idle mode. In particular, the mobile station shall ignore PAGING REQUEST messages indicating a packet paging procedure.

A mobile station belonging to GPRS MS class A or B shall continue to monitor its paging subchannel on CCCH for PAGING REQUEST messages indicating an establishment of RR connection. A mobile station belonging to GPRS MS class B may abort the packet access procedure at the receipt of a PAGING REQUEST messages indicating an establishment of RR connection.

The mobile station schedules CHANNEL REQUEST messages on RACH as defined in sub-clause 3.3.1.1.2.

The CHANNEL REQUEST messages are sent on RACH and contain the parameters:

– an establishment cause which indicates packet access, and as applicable, a request for one phase packet access or single block packet access (sub-clause 9.1.8);

– a random reference which is drawn randomly from an uniform probability distribution for every new transmission.

If the requested RLC mode is unacknowledged mode, the mobile station shall request a single block packet access and attempt a two phase packet access.

If the purpose of the packet access procedure is to send a Page Response, Cell update, for a GPRS Mobility Management or a GPRS Session Management procedure, (i.e. the access is for Layer 3 signalling only, and not for a Layer 3 data transfer), the mobile station shall request a one phase packet access.

After sending the first CHANNEL REQUEST message, the mobile station shall start listening to the BCCH; it shall also listen to the full downlink CCCH timeslot corresponding to its CCCH group.

Having sent the maximum number of CHANNEL REQUEST messages, the mobile station starts timer T3146. At expiry of timer T3146, the packet access procedure is aborted and a packet access failure is indicated to upper layers.

If the mobile station receives an IMMEDIATE ASSIGNMENT message during the packet access procedure indicating a packet downlink assignment procedure, the mobile station shall abort the packet access procedure and respond to the IMMEDIATE ASSIGNMENT message as specified in sub-clause 3.5.3.1.2. The mobile station shall then attempt an establishment of uplink TBF, using the procedure specified in 3GPP TS 04.60 which is applicable in packet transfer mode.

##### 3.5.2.1.3 Packet immediate assignment

3.5.2.1.3.1 On receipt of a CHANNEL REQUEST message

On receipt of a CHANNEL REQUEST message indicating a packet access, the network may allocate a temporary flow identity and assign a packet uplink resource comprising one PDCH for an uplink temporary block flow.

If the establishment cause in the CHANNEL REQUEST message indicates a request for a single block packet access, the network shall grant only the single block period on the assigned packet uplink resource if the network allocates resource for the mobile station.

If the establishment cause in the CHANNEL REQUEST message indicates a request for one phase packet access, the network may grant either a one phase packet access or a single block packet access for the mobile station. If a single block packet access is granted, it forces the mobile station to perform a two phase packet access.

The packet uplink resource is assigned to the mobile station in an IMMEDIATE ASSIGNMENT message sent in unacknowledged mode on the same CCCH timeslot on which the network has received the CHANNEL REQUEST message. There is no further restriction on what part of the downlink CCCH timeslot the IMMEDIATE ASSIGNMENT message can be sent. Timer T3141 is started on the network side.

The IMMEDIATE ASSIGNMENT message contains:

– the information field of the CHANNEL REQUEST message and the frame number of the frame in which the CHANNEL REQUEST message was received;

– the packet channel description;

– the packet uplink assignment construction.

If frequency hopping is applied, the network may use the indirect encoding or the direct encoding of the frequency configuration in the Packet Channel Description information element. If the indirect encoding is used, the mobile station uses information received in system information or stored from a previous assignment to determine the frequency parameters, see 3GPP TS 04.60. If the direct encoding is used, the mobile station uses the cell allocation defined for the cell to decode the mobile allocation.

If the indirect encoding is used, the IMMEDIATE ASSIGNMENT message may contain a CHANGE_MARK_1 field. If that is present, the mobile station shall verify the validity of the SI13_CHANGE_MARK associated with the GPRS mobile allocation to which the message refers, see 3GPP TS 04.60. If the CHANGE_MARK_1 field and the SI13_CHANGE_MARK do not match, the message does not satisfactorily define a PDCH.

If the mobile station receives an IMMEDIATE ASSIGNMENT message and the Dedicated mode or TBF information element indicates that this is the first message in a two-message assignment, the mobile station shall continue to listen to the full CCCH. The network may send a second IMMEDIATE ASSIGNMENT message to the mobile station within two multiframe periods following the first IMMEDIATE ASSIGNMENT message, specifying the packet channel description and, if required, a mobile allocation for the assignment. The two IMMEDIATE ASSIGNMENT messages in a two-message assignment shall have the same contents of the Request Reference information elements.

If the mobile station does not receive the second IMMEDIATE ASSIGNMENT messages in a two-message assignment within two multiframe periods following the first message, the mobile station shall discard the first IMMEDIATE ASSIGNMENT message received.

On receipt of an IMMEDIATE ASSIGNMENT message or, in case of a two-message assignment, a matching pair of IMMEDIATE ASSIGNMENT messages corresponding to one of its 3 last CHANNEL REQUEST messages, the mobile station stops T3146 (if running), stops sending CHANNEL REQUEST messages, and switches to the assigned PDCH.

The content of the packet uplink assignment construction indicates which type of packet access is granted: one phase packet access or single block packet access

3.5.2.1.3.2 One phase packet access

In the case the one phase packet access is granted, the packet uplink assignment construction contains:

– the temporary flow identity;

– the USF value, if the medium access method is dynamic allocation;or

– the fixed allocation bitmap, if the medium access method is fixed allocation;

– the channel coding scheme for RLC data blocks;

– the power control parameters;

– the polling bit ;

– optionally, the timing advance index (see 3GPP TS 05.10);

– optionally, the TBF starting time (note: TBF starting time is mandatory if medium access method is fixed allocation).

The medium access method is dynamic allocation or fixed allocation and the RLC mode is acknowledged mode, see 3GPP TS 04.60.

The mobile station shall start timer T3164 and proceed with the contention resolution at one phase access defined in 3GPP TS 04.60.

If the medium access method is fixed allocation, and the number of blocks allocated in the ALLOCATION_BITMAP is not sufficient to transfer all the RLC/MAC blocks that the MS has to transmit at the time the packet uplink assignment construction is received, the MS shall request additional resources by sending a PACKET RESOURCE REQUEST on one of the allocated blocks.

If the timing advance index (TAI) is included in the packet uplink assignment construction, the mobile station shall use the continuous update timing advance mechanism, see 3GPP TS 05.10, using PTCCH in the same timeslot as the assigned PDCH. If a timing advance index (TAI) field is not included, the continuous update timing advance mechanism shall not be used.

In case the packet uplink assignment construction contains a TBF starting time and the mobile station receives the message before the TBF starting time has expired, it shall wait until the frame number indicated by the TBF starting time before accessing the channel. If the mobile station receives the message after the TBF starting time has expired, it shall ignore the TBF starting time and may immediately access the channel.

If the Polling bit is set to 1, MS shall send a PACKET CONTROL ACKNOWLEDGEMENT message (see 04.60) on the assigned PDCH, in the uplink block specified by the TBF Starting Time. In this case the TBF Starting Time is used both to indicate when the assigned PDCH becomes valid and to specify the uplink block. If the TBF Starting Time is not present or has expired, the MS shall ignore the polling request.

3.5.2.1.3.3 Single block packet access

In the case the single block packet access is granted, the packet uplink resource description contains:

– the power control parameter setting;

– the TBF starting time.

If the mobile station receives the IMMEDIATE ASSIGNMENT message before the TBF starting time has expired, it shall wait until the block period indicated by the TBF starting time. The network shall use the TBF starting time to indicate the first frame number belonging to the single block period granted for packet access. The mobile station may either use the assigned block period to send a PACKET RESOURCE REQUEST message to initiate the two phase packet access procedure defined in 3GPP TS 04.60, or to send an RLC/MAC control message other than the PACKET RESOURCE REQUEST message to the network, see sub-clause 3.5.2.2.

If the mobile station receives the IMMEDIATE ASSIGNMENT message after the TBF starting time has expired, a failure has occurred.

If a failure occurs and the packet access attempt was due to a request from upper layers to transfer a LLC PDU, a TBF establishment failure has occurred and the mobile station proceeds as specified in sub-clause 3.5.2.1.5. If a failure occurs and the packet access attempt was due to the sending of an RLC/MAC control message, the packet access is aborted, the mobile station returns to packet idle mode.

3.5.2.1.3.4 Packet access rejection

The network may send to the mobile station an IMMEDIATE ASSIGNMENT REJECT message in unacknowledged mode on the same CCCH timeslot on which the channel request message was received. There is no further restriction on what part of the downlink CCCH timeslot an IMMEDIATE ASSIGNMENT REJECT message can be sent. This message contains the request reference and a wait indication.

On receipt of an IMMEDIATE ASSIGNMENT REJECT message corresponding to one of its 3 last CHANNEL REQUEST messages, the mobile station stops sending CHANNEL REQUEST messages, starts timer T3142 with the indicated value, ("wait indication" information element), starts T3146 if it has not already been started, and listens to the downlink CCCH until T3146 expires. During this time, additional IMMEDIATE ASSIGNMENT REJECT messages are ignored, but any immediate assignment corresponding to any other of its 3 last CHANNEL REQUEST messages make the mobile station follow the procedure in sub-clause 3.5.2.1.3.1. If no such immediate assignment is received, the mobile station returns to packet idle mode and notify higher layers (TBF establishment failure).

If the mobile station has received responses from the network on all, or in case more than 3 were sent the last 3, of its CHANNEL REQUEST messages, it shall immediately return to packet idle mode and notify higher layers.

The mobile station is not allowed to make a new attempt for packet access in the same cell until T3142 expires, but may attempt packet access in an other cell after successful cell reselection for radio conditions reasons (see 3GPP TS 05.08). The value of the wait indication (i.e. T3142) relates to the cell from which it was received.

The mobile station may initiate RR connection establishment in the same cell before T3142 has expired, see sub-clause 3.3.1.1.3.2.

##### 3.5.2.1.4 Packet access completion

The one phase packet access procedure is completed at a successful contention resolution. The mobile station has entered the packet transfer mode. Timer T3141 is stopped on the network side. Timer T3164 is stopped on the mobile station side.

##### 3.5.2.1.5 Abnormal cases

If a failure occurs on the mobile station side before a successful contention resolution procedure is completed, the allocated temporary block flow is released; the mobile station returns to packet idle mode, upper layers are notified (TBF establishment failure), transactions in progress are aborted:

– If a TLLI mismatch has occurred during the contention resolution procedure, and the repetition of the packet access has been repeated the maximum number of times as defined in 3GPP TS 04.60, a TBF establishment failure has occurred.

– If the information available in the mobile station, after the reception of an IMMEDIATE ASSIGNMENT message or the second IMMEDIATE ASSIGNMENT message of a two-message assignment, does not satisfactorily define a PDCH, a TBF establishment failure has occurred.

– If the mobile allocation indexes frequencies in more than one frequency band then a TBF establishment failure has occurred.

– If an IMMEDIATE ASSIGNMENT message indicates a PDCH in a non-supported frequency band then a TBF establishment failure has occurred.

On the network side, if timer T3141 elapses before a successful contention resolution procedure is completed, the newly allocated temporary block flow is released as specified in 3GPP TS 04.60 and the packet access is forgotten.

#### 3.5.2.2 Sending an RLC/MAC control message: single block packet access procedure

The sending of an RLC/MAC control message other than the PACKET RESOURCE REQUEST message from a mobile station in packet idle mode to the network may be initiated by the RR entity on the mobile station side using the packet access procedure. If access to the network is allowed (sub-clause 3.5.2.1.1), the packet access is done according to the procedures defined in sub-clauses 3.5.2.1.2 and 3.5.2.1.3, using the single block packet access option defined in sub-clause 3.5.2.1.3.3.

Further action depends on the RLC/MAC control message sent by the mobile station, see 3GPP TS 04.60. Unless otherwise indicated by the RLC/MAC control message, the mobile station remains in packet idle mode.

### 3.5.3 Packet downlink assignment procedure using CCCH

The packet downlink assignment procedure using CCCH may be used to establish a temporary block flow to support the transfer of LLC PDUs in the direction from the network to the mobile station.

This procedure may also be used to assign a single downlink block on a PDCH to support the transfer of an RLC/MAC control message from the network to a mobile station in packet idle mode, see sub-clause 3.5.3.2.

#### 3.5.3.1 Entering the packet transfer mode: packet downlink assignment procedure

The establishment of a downlink temporary block flow may be initiated by the RR entity on the network side using the packet downlink assignment procedure. The procedure is triggered by a request from upper layers to transfer a LLC PDU, see 3GPP TS 04.07. The request from upper layers specifies an optional Priority level, a QoS profile including the requested RLC mode, optional DRX parameters, an optional IMSI and an optional MS Radio Access Capability associated with the packet transfer.

Upon such a request, the network shall determine whether the mobile station is in packet idle mode or packet transfer mode. The packet downlink assignment procedure using CCCH is applicable when the mobile station is in packet idle mode and when there is no PCCCH present in the cell.

The network may allocate a temporary flow identity and assign a packet downlink resource comprising one PDCH for a downlink temporary block flow.

##### 3.5.3.1.2 Initiation of the packet downlink assignment procedure

The network initiates the packet downlink assignment procedure by sending an IMMEDIATE ASSIGNMENT message in unacknowledged mode on the CCCH timeslot corresponding to CCCH group the mobile station belongs to. The appropriate CCCH group is calculated from the IMSI, see 05.02. The behaviour of the network when the RR entity does not receive the IMSI from the upper layers is implementation dependent for the calculation of the CCCH group where the IMMEDIATE ASSIGNMENT message has to be sent. If the mobile station is in non-DRX mode or if the RR entity does not receive the IMSI or the DRX parameters from the upper layers, there is no further restriction on what part of the downlink CCCH timeslot the IMMEDIATE ASSIGNMENT message, or the first part of the IMMEDIATE ASSIGNMENT message (in the case of a two-message assignment), can be sent. If the mobile station applies DRX, the IMMEDIATE ASSIGNMENT message, or the first part of the IMMEDIATE ASSIGNMENT message (in the case of a two-message assignment), shall be sent in a CCCH block corresponding to a paging group determined for the mobile station in packet idle mode, see 3GPP TS 05.02.

The IMMEDIATE ASSIGNMENT message contains:

– the packet channel description;

– the packet downlink assignment construction.

The contents of the packet downlink assignment construction determines the further action. At the establishment of a downlink temporary block flow, the packet downlink assignment construction shall contain:

– the TLLI;

– the temporary flow identity;

– the RLC mode;

– the power control parameters;

– the polling bit;

– the initial timing advance validity flag;

– optionally, the timing advance index (see 3GPP TS 05.10);

– optionally, the TBF starting time.

If frequency hopping is applied, the network may use the indirect encoding or the direct encoding of the frequency configuration in the Packet Channel Description information element. If the indirect encoding is used, the mobile station uses information received in system information or stored from a previous assignment to determine the frequency parameters, see 3GPP TS 04.60. If the direct encoding is used, the mobile station uses the cell allocation defined for the cell to decode the mobile allocation.

If the indirect encoding is used, the IMMEDIATE ASSIGNMENT message may contain a CHANGE_MARK_1 field. If that is present, the mobile station shall verify the validity of the SI change mark associated with the GPRS mobile allocation to which the message refers, see 3GPP TS 04.60. If the CHANGE_MARK_1 field and the SI change mark do not match, the message does not satisfactorily define a PDCH.

If the mobile station receives an IMMEDIATE ASSIGNMENT message and the Dedicated mode or TBF information element indicates that this is the first message in a two-message assignment, the mobile station shall start listen to the full CCCH. The network may send a second IMMEDIATE ASSIGNMENT message to the mobile station within two multiframe periods following the first IMMEDIATE ASSIGNMENT message, specifying the packet channel description and, if required, a mobile allocation for the assignment. The two IMMEDIATE ASSIGNMENT messages in a two-message assignment shall have the same contents of the Request Reference information elements.

If the mobile station was operating in DRX mode when it received the first message of a two-message assignment, the network shall not send the second IMMEDIATE ASSIGNMENT message within the two block periods immediately following the first message.

If the mobile station does not receive the second IMMEDIATE ASSIGNMENT messages in a two-message assignment within two multiframe periods following the first message, the mobile station shall discard the first IMMEDIATE ASSIGNMENT message received. After the two multiframe periods following the first message, the mobile station may resume to DRX mode.

On receipt of an IMMEDIATE ASSIGNMENT message or, in case of a two-message assignment, a matching pair of IMMEDIATE ASSIGNMENT messages, the mobile station stops monitoring downlink CCCH and switches to the assigned PDCH and starts listening for downlink RLC/MAC blocks identified by the assigned TFI; it starts timer T3190.

The IMMEDIATE ASSIGNMENT message may indicate a TBF starting time. If the mobile station receives the message before the TBF starting time has expired, it shall wait until the frame number indicated by the TBF starting time, start timer T3190 and switch to the assigned PDCH. If the mobile station receives the message after the TBF starting time has expired, it shall ignore the indicated TBF starting time, immediately start timer T3190 and switch to the assigned PDCH.

If the Polling bit is set to 1, MS shall send a PACKET CONTROL ACKNOWLEDGEMENT message (see 04.60) on the assigned PDCH, in the uplink block specified by the TBF Starting Time. In this case the TBF Starting Time is used both to indicate when the assigned PDCH becomes valid and to specify the uplink block. If the TBF Starting Time is not present or has expired, the MS shall ignore the polling request.

An IMMEDIATE ASSIGNMENT message may indicate a timing advance index (TAI) in the packet timing advance IE. The mobile station shall then use the continuous update timing advance mechanism, see 3GPP TS 05.10, using PTCCH in the same timeslot as the assigned PDCH. If there is no indication of a timing advance index, the continuous update timing advance mechanism shall not be used.

The TA_VALID flag indicates if the value of the Timing Advance IE is valid or not.

If the network does not have a valid timing advance value for the mobile station to include in the IMMEDIATE ASSIGNMENT message, the network shall use the procedures defined in 3GPP TS 04.60 on the assigned TBF, or the polling mechanism defined in the above paragraph if the PACKET CONTROL ACKNOWLEDGEMENT format is set to four access bursts, to obtain a timing advance value and to update the initially assigned timing advance value before the mobile station is required to transmit other than access burst on the newly assigned channel.

##### 3.5.3.1.3 Packet downlink assignment completion

After having sent the packet downlink assignment, the network starts sending downlink RLC/MAC blocks on the assigned packet downlink resource and the packet downlink assignment procedure is completed at the network side.

On the mobile station side, the procedure is completed when the mobile station receives an RLC/MAC block identified by the assigned temporary flow identity. The mobile station stops timer T3190. The mobile station has entered packet transfer mode.

##### 3.5.3.1.4 Abnormal cases

If a failure occurs on the mobile station side before the packet downlink assignment procedure is completed (TBF establishment failure), the temporary block flow is released; the mobile station returns to packet idle mode:

– If the mobile station does not receive a RLC/MAC block on the assigned PDCHs before timer T3190 expires, then a TBF establishment failure has occurred.

– If the information available in the mobile station, after the reception of an IMMEDIATE ASSIGNMENT message or the second IMMEDIATE ASSIGNMENT message of a two-message assignment, does not satisfactorily define a PDCH, then a TBF establishment failure has occurred.

– If the mobile allocation in the frequency parameters indexes frequencies in more than one frequency band, then a TBF establishment failure has occurred.

If an IMMEDIATE ASSIGNMENT message indicates a PDCH in a non-supported frequency band, then a TBF establishment failure has occurred.

#### 3.5.3.2 Sending an RLC/MAC control message: single block packet downlink assignment procedure

The sending of an RLC/MAC control message to a mobile station in packet idle mode may be initiated by the RR entity on network side using the packet downlink assignment procedure. The procedure is used to assign a single downlink block on a PDCH for the transfer of the RLC/MAC control message.

The single downlink block assignment is done according to the procedure defined in 3.5.3.1.2, with the following exceptions:

The packet downlink assignment construction in the IMMEDIATE ASSIGNMENT message shall contain only:

– the TLLI; and

– the TBF starting time.

If the mobile station receives the IMMEDIATE ASSIGNMENT message before the TBF starting time has expired, it shall wait until the frame number indicated by the TBF starting time. The network shall use the TBF starting time to indicate the first frame number belonging to the single block period assigned to the mobile station. The mobile station shall switch to the assigned PDCH and attempt to decode an RLC/MAC control message in the assigned downlink block. Further action depends on the RLC/MAC control message sent by the network, see 3GPP TS 04.60. Unless otherwise indicated by the RLC/MAC control message, the mobile station remains in packet idle mode. If the mobile station remains in packet idle mode, it shall continue to monitor downlink CCCH once the block period indicated by the TBF starting time has passed.

If the mobile station fails to decode or does not receive an RLC/MAC control message in the assigned downlink block, it shall remain in packet idle mode and continue to monitor downlink CCCH once the block period indicated by the TBF starting time has passed.

If the mobile station receives the IMMEDIATE ASSIGNMENT message after the TBF starting time has expired, it shall ignore the assignment.

If a failure occurs on the mobile station side due to any other reason, the mobile station shall ignore the assignment.