7 Medium Access Control (MAC) procedures on PCCCH

3GPP44.060General Packet Radio Service (GPRS)Mobile Station (MS) - Base Station System (BSS) interfaceRadio Link Control / Medium Access Control (RLC/MAC) protocolRelease 17TS

Tools: ARFCN - Frequency Conversion for 5G NR/LTE/UMTS/GSM

7.0 General

The establishment of a Temporary Block Flow (TBF) can be initiated by either the mobile station or the network.

The request for establishment of a TBF on PCCCH, if allocated in the cell, is described in this sub-clause. If no PCCCH is allocated in the cell, the establishment of a TBF occurs on CCCH as described in 3GPP TS 44.018. The establishment of an EC TBF, for a mobile station that has enabled EC operation, occurs on the EC-CCCH or on the CCCH as described in sub-clause 7a and in 3GPP TS 44.018.

For mobile stations in packet idle mode on PCCCH, measurement reports messages are sent on temporary fixed allocations without the establishment of an uplink TBF (see sub-clause 7.3).

7.0a Support of multiple TBF procedures

If the mobile station supports multiple TBF procedures, the mobile station shall indicate its support in the Multiple TBF Capability field in the MS Radio Access Capability 2 IE. If the network supports multiple TBF procedures, the network shall indicate its support in the Multiple TBF Capability field in the GPRS Cell Options IE.

If both the network and the mobile station support multiple TBF procedures, and if more than one request is received from upper layers to transfer upper layer PDUs for more than one PFC before the packet access procedure can be initiated by the mobile station, then the mobile station may initiate a packet access procedure requesting multiple TBFs.

During multiple TBF procedures in sub-clause 7:

– The mobile station shall support the PACKET RESOURCE REQUEST message to request a single uplink TBF;

– The mobile station may send the PACKET RESOURCE REQUEST message to request multiple uplink TBFs in the second phase of a two-phase access;

– The network shall support the PACKET UPLINK ASSIGNMENT message to assign a single uplink TBF;

– The network may send the MULTIPLE TBF UPLINK ASSIGNMENT message to assign one or more uplink TBFs to a mobile station that requested multiple TBFs in the PACKET RESOURCE REQUEST message. In this sub-clause this message shall only be sent in response to a multiple uplink resource request in the second part of a two-phase access.

7.0b (void)

7.1 TBF establishment initiated by the mobile station on PCCCH

The purpose of the packet access procedure is to establish a TBF to support the transfer of upper-layer PDUs in the direction from the mobile station to the network. Packet access shall be done on PCCCH, as defined in this sub-clause, if a PCCCH exists. Otherwise, packet access shall be done on CCCH, as defined in 3GPP TS 44.018. The packet access can be done in either one phase (sub-clause 7.1.2) or in two phases (sub-clauses 7.1.2 and 7.1.3).

TBF establishment can also be done on PACCH if a TBF for transfer of upper-layer PDUs in the direction from the network to the mobile station is already established (see sub-clause 8.1.2.5). TBF establishment can also be done on PACCH if the mobile station is releasing a TBF for transfer of upper-layer PDUs in the direction from the mobile station to the network and TBF for transfer of upper-layer PDUs in the direction from the network to the mobile station is not established (see sub-clause 9.3.2.4 and sub-clause 9.3.3.3).

If the mobile station is in dedicated mode and both the network and the mobile station support DTM, the establishment of a TBF shall be performed by the DTM assignment procedures on the main DCCH, as defined in 3GPP TS 44.018.

The packet access procedure is initiated by the mobile station. Initiation is triggered by a request from upper layers to transfer an upper-layer PDU. The request from upper layers specifies throughput, RLC mode, an optional PFI, and a Radio Priority to be associated with the packet transfer or indicates that the packet to be transferred contains signalling. If both the network and the mobile station support the extended uplink TBF mode, the request from upper layers may also specify that the upper-layer PDU is meant to pre-allocate an uplink TBF (early TBF establishment). In this case, the mobile station shall use the two phase access procedure, setting the EARLY_TBF_ESTABLISHMENT field in the PACKET RESOURCE REQUEST message to indicate pre-allocation is required (as described in sub-clause 7.1.3).

A mobile station indicates its support of RLC non-persistent mode in the RLC non-persistent mode capability bit of the MS Radio Access Capability information element (see 3GPP TS 24.008).

A packet access procedure requesting multiple TBFs may be initiated by the mobile station if multiple TBF procedures are supported in the network and the mobile station (see sub-clause 7.0). Initiation is triggered when the mobile station receives more than one request from upper layers to transfer upper-layer PDUs before the packet access procedure can be initiated. Each request from upper layers specifies a PFI, RLC mode, Radio Priority and optionally an LLC mode to be associated with the packet transfer or indicates that the packet to be transferred contains signalling.

Upon such a request:

– if access to the network is allowed (sub-clause 7.1.1), the mobile station shall initiate the packet access procedure as defined in sub-clause 7.1.2.1;

– otherwise, the RR sublayer in the mobile station shall reject the request.

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

If both the mobile station and the BSS support multiple TBF procedures, or if the mobile station supports RLC non-persistent mode, the BSS may order its preferred RLC mode when establishing uplink TBF(s), independently of the RLC mode requested by the mobile station. In particular, if the mobile station supports RLC non-persistent mode the network may allocate an EGPRS TBF that uses this RLC mode.

7.1.1 Permission to access the network

The network broadcasts on PBCCH and PCCCH the list of authorised access classes and authorised special access classes in the ACC_CONTR_CLASS parameter.

Access to the network is allowed if the mobile station is a member of at least one authorised access class or special access class as defined in 3GPP TS 22.011.

7.1.2 Initiation of a TBF establishment

7.1.2.1 Initiation of the packet access procedure

The mobile station shall initiate the packet access procedure by scheduling the sending of PACKET CHANNEL REQUEST messages on the PRACH corresponding to its PCCCH_GROUP and simultaneously leaving the packet idle mode. The mobile station shall use the last access parameters received on PBCCH. At sending of the first PACKET CHANNEL REQUEST message, the mobile station shall store the value for the Retry (R) bit to be transmitted in all the subsequent MAC headers as ‘MS sent channel request message once’. If a second PACKET CHANNEL REQUEST message is sent, the mobile station shall change the value for the Retry (R) bit to ‘MS sent channel request message twice or more’.

While waiting for a response to the PACKET CHANNEL REQUEST message, the mobile station shall monitor the full PCCCH corresponding to its PCCCH_GROUP. The mobile station shall perform signal strength measurements as they are defined for packet idle mode, see 3GPP TS 45.008.

While monitoring the full PCCCH, the mobile station shall decode any occurrence of the PERSISTENCE_LEVEL parameter included in a message received on PCCCH. When the mobile station receives the PERSISTENCE_LEVEL parameter, the value of the PERSISTENCE_LEVEL parameter shall be taken into account at the next PACKET CHANNEL REQUEST attempt that follows.

A mobile station that is IMSI attached (GPRS class A or B mode of operation) shall respond to a PACKET PAGING REQUEST message indicating an RR connection establishment. For that purpose, the mobile station may abort the packet access procedure, according to the conditions stated in sub-clause 6.1.4. The mobile station shall not respond to a PACKET PAGING REQUEST message indicating TBF establishment.

A mobile station that is not IMSI attached (GPRS class C mode of operation) shall not respond to any type of PACKET PAGING REQUEST messages during the packet access procedure, it shall only decode the PERSISTENCE_LEVEL parameter, if that is included in the message.

The PACKET CHANNEL REQUEST messages are sent on PRACH and contain an indication of the type of access and parameters required to indicate the mobile station’s demand of radio resource.

There are two formats of the PACKET CHANNEL REQUEST message containing either 8 bits or 11 bits of information. The format to be applied on PRACH is controlled by the parameter ACCESS_BURST_TYPE which is broadcast on PBCCH. The access type to be used in the PACKET CHANNEL REQUEST message for a non-EGPRS TBF mode capable MS or an EGPRS TBF mode capable MS in a non-EGPRS capable cell depends on the purpose of the packet access procedure as follows:

– If the purpose of the packet access procedure is to request multiple TBFs, the mobile station shall indicate ‘Two phase access’ in the PACKET CHANNEL REQUEST message;

– If the purpose of the packet access procedure is to request a single TBF, the mobile station shall indicate one of the following access causes:

– If the mobile station intends to use the TBF to send user data, it shall request two phase access if the requested RLC mode is unacknowledged mode. If the requested RLC mode is acknowledged mode, the mobile station shall request either one phase access or two phase access. In case of two phase access, if both the mobile station and the BSS support multiple TBF procedures, the BSS may order its preferred RLC mode when establishing an uplink TBF, overriding the mobile station request;

– If the purpose of the packet access procedure is to send a Page Response, the mobile station shall indicate ‘Page Response’ in the PACKET CHANNEL REQUEST message;

– If the purpose of the packet access procedure is to send a Cell update (the mobile station was in GMM READY state before the cell reselection) the mobile station shall indicate ‘Cell Update’ in the PACKET CHANNEL REQUEST message;

– If the purpose of the packet access procedure is for any other Mobility Management procedure, the mobile station shall indicate ‘MM Procedure’ in the PACKET CHANNEL REQUEST message;

– If the purpose of the packet access procedure is to send a Measurement Report, the mobile station shall indicate ‘Single block without TBF establishment’ in the PACKET CHANNEL REQUEST message;

– If the purpose of the packet access procedure is to send a PACKET PAUSE message, the mobile station shall indicate ‘Single block without TBF establishment’ in the PACKET CHANNEL REQUEST message. Upon the first attempt to send a PACKET CHANNEL REQUEST message the mobile station shall start timer T3204. If the mobile station receives a PACKET DOWNLINK ASSIGNMENT message before expiry of timer T3204, the mobile station shall ignore the message;

– If the purpose of the packet access procedure is to send an MBMS SERVICE REQUEST message to the network, the mobile station shall indicate ‘Single block MBMS access’ in the PACKET CHANNEL REQUEST message.

EGPRS TBF mode capable mobile stations shall monitor the GPRS Cell Options IE on the PBCCH (PSI1/PSI13) for the cell’s EGPRS capability and, if the mobile station is also Reduced Latency capable, the cell’s Reduced Latency Access capability. In the GPRS Cell Options IE it is also indicated if the EGPRS PACKET CHANNEL REQUEST message is supported in the cell and if Reduced Latency Access is supported in the cell. If the mobile station supports the IMMEDIATE PACKET ASSIGNMENT message, the mobile station shall monitor cell’s capability for IMMEDIATE PACKET ASSIGNMENT message within paging messages received on its own paging sub-channel. The following table specifies which message and which access type shall be used by an EGPRS mobile station when accessing an EGPRS capable cell depending on the purpose of the packet access procedure, and mobile station’s and cell’s capabilities; this table covers the case where PBCCH is present in the cell (see 3GPP TS 44.018 for the case where PBCCH is not present in the cell). The network shall not indicate Reduced Latency Access is supported if the EGPRS PACKET CHANNEL REQUEST message is not indicated as supported. The network shall not indicate IMMEDIATE PACKET ASSIGNMENT message is supported if the EGPRS PACKET CHANNEL REQUEST message is not indicated as supported.

Table 7.1.2.1.1: EGPRS PACKET CHANNEL REQUEST support

Purpose of the packet access procedure	EGPRS PACKET CHANNEL REQUEST supported in the cell	EGPRS PACKET CHANNEL REQUEST not supported in the cell
User data transfer – requested RLC mode = unacknowledged	EGPRS PACKET CHANNEL REQUEST with access type = ‘Two Phase Access Request’	PACKET CHANNEL REQUEST with access type = ‘Two Phase Access Request’ (NOTE 1)
User data transfer – requested RLC mode = acknowledged	EGPRS PACKET CHANNEL REQUEST with access type = ‘One Phase Access Request’ or ‘Two Phase Access Request’	PACKET CHANNEL REQUEST with access type = ‘Two Phase Access Request’ (NOTE 1)
User data transfer – requested RLC mode = acknowledged (Reduced Latency supported by MS)	EGPRS PACKET CHANNEL REQUEST with access type = ‘One Phase Access Request by Reduced Latency MS’ (NOTE 3)	PACKET CHANNEL REQUEST with access type = ‘Two Phase Access Request’ (NOTE 1)
Upper layer signalling transfer (e.g. page response, cell update, MM signalling, etc)	EGPRS PACKET CHANNEL REQUEST with access type = ‘Signalling’	PACKET CHANNEL REQUEST with access type = ‘Two Phase Access Request’
Sending of a measurement report or of a PACKET CELL CHANGE FAILURE	PACKET CHANNEL REQUEST with access type = ‘Single block without TBF establishment’ (NOTE 1)
Sending of a PACKET PAUSE message	PACKET CHANNEL REQUEST with access type = ‘Single block without TBF establishment’ (NOTE 1) (NOTE 2)
Sending of an MBMS Service Request message	PACKET CHANNEL REQUEST with access type = ‘Single block MBMS access’ (NOTE 1)
NOTE 1: The format to be used for the PACKET CHANNEL REQUEST message is defined by the parameter ACCESS_BURST_TYPE. NOTE 2: Upon the first attempt to send a PACKET CHANNEL REQUEST message the mobile station shall start timer T3204. If the mobile station receives a PACKET DOWNLINK ASSIGNMENT message before expiry of timer T3204, the mobile station shall ignore the message. NOTE 3: The ‘One phase Access Request by Reduced Latency MS’ shall be used by the mobile station supporting reduced latency if Reduced Latency Access is supported by the network.

7.1.2.1.1 Access persistence control on PRACH

The mobile station shall make maximally M + 1 attempts to send a PACKET CHANNEL REQUEST (respectively EGPRS PACKET CHANNEL REQUEST) message.

After sending each PACKET CHANNEL REQUEST (respectively EGPRS PACKET CHANNEL REQUEST) message, the mobile station shall listen to the full PCCCH corresponding to its PCCCH_GROUP.

The PRACH Control Parameters IE contains the access persistence control parameters and shall be broadcast on PBCCH and PCCCH. The parameters included in the PRACH Control Parameters IE are:

– MAX_RETRANS, for each radio priority i (i = 1, 2, 3, 4);

– PERSISTENCE_LEVEL, which consists of the PERSISTENCE_LEVEL P(i) for each radio priority i (i = 1, 2, 3, 4); where P(i) Î {0, 1, …14, 16}. If the PRACH Control Parameters IE does not contain the PERSISTENCE_LEVEL parameter, this shall be interpreted as if P(i) = 0 for all radio priorities;

– S;

– TX_INT.

The mobile station shall start timer T3186 at the beginning of the packet access procedure. At expiry of timer T3186, the packet access procedure shall be aborted, and:

– if at least one PACKET CHANNEL REQUEST (respectively EGPRS PACKET CHANNEL REQUEST) message was transmitted by the mobile station, a random access failure shall be indicated to upper layers and the mobile station shall perform autonomous cell re-selection according to 3GPP TS 43.022;

– otherwise, a packet access failure shall be indicated to upper layers and the mobile station shall return to packet idle mode or MAC-Idle state.

The first attempt to send a PACKET CHANNEL REQUEST (respectively EGPRS PACKET CHANNEL REQUEST) message, may be initiated at the first available PRACH block on the PDCH defined by the PCCCH_GROUP for the mobile station (see 3GPP TS 45.002). The mobile station shall choose one of the four TDMA frames within the selected PRACH block randomly with a uniform probability distribution.

For each attempt, the mobile station shall draw a random value R with uniform probability distribution in the set {0, 1, …, 15}. The mobile station is allowed to transmit a PACKET CHANNEL REQUEST (respectively EGPRS PACKET CHANNEL REQUEST) message if P(i), where i is the radio priority of the TBF being established, is less than or equal to R.

After each attempt, the S and T parameters are used to determine the next TDMA frame in which it may be allowed to make a successive attempt. The number of TDMA frames belonging to the PRACH on the PDCH defined by the PCCCH_GROUP for the mobile station between two successive attempts to send a PACKET CHANNEL REQUEST (respectively EGPRS PACKET CHANNEL REQUEST) message excluding the TDMA frames potentially containing the messages themselves is a random value drawn for each transmission with uniform probability distribution in the set {S, S + 1, …, S + T ‑ 1}.

Here:

M is the value of the parameter MAX_RETRANS, belonging to the Radio Priority of the access;

T is the value of the parameter TX_INT;

S is the value of the parameter S.

Having made M + 1 attempts to send a PACKET CHANNEL REQUEST (respectively EGPRS PACKET CHANNEL REQUEST) message, the mobile station shall stop timer T3186 and start timer T3170 if at least one PACKET CHANNEL REQUEST (respectively EGPRS PACKET CHANNEL REQUEST) message was transmitted by the mobile station. In this case, at expiry of timer T3170, the packet access procedure shall be aborted, a random access failure shall be indicated to upper layers and the mobile station shall perform autonomous cell re-selection according to 3GPP TS 43.022. Otherwise, the packet access procedure shall be aborted, a packet access failure shall be indicated to upper layers and the mobile station shall return to packet idle mode or MAC-Idle state.

If the mobile station receives a PACKET DOWNLINK ASSIGNMENT message while it is waiting for a response to a PACKET CHANNEL REQUEST (respectively EGPRS PACKET CHANNEL REQUEST) message, it shall abort the packet access procedure and respond to the PACKET DOWNLINK ASSIGNMENT message (see sub-clause 7.2.1). The mobile station shall then attempt establishment of an uplink TBF using the procedures defined in sub-clause 8.1.2.5.

7.1.2.2 Packet assignment procedure

7.1.2.2.1 On receipt of a PACKET CHANNEL REQUEST or EGPRS PACKET CHANNEL REQUEST message

On receipt of a PACKET CHANNEL REQUEST message, the network may assign a radio resource on one or more PDCHs to be used by the mobile station for the TBF in GPRS TBF mode. On receipt of an EGPRS PACKET CHANNEL REQUEST message, the network may assign a radio resource on one or more PDCHs to be used by the mobile station for the TBF in EGPRS TBF mode or GPRS TBF mode.

The allocated PDTCH and PACCH resource is assigned to the mobile station in a PACKET UPLINK ASSIGNMENT message, sent on any PAGCH block on the same PCCCH on which the network has received the PACKET CHANNEL REQUEST or EGPRS PACKET CHANNEL REQUEST message. The Packet Request Reference information element shall be used to address the mobile station and frequency parameters shall be included.

A mobile station supporting Downlink Dual Carrier may be sent a PACKET UPLINK ASSIGNMENT message to assign radio resources on two different radio frequency channels for a given uplink TBF. In such a configuration, uplink radio blocks shall not be allocated on both radio frequency channels during any given radio block period.

The mobile station may use information received on PBCCH, BCCH or a previous assignment message to decode the frequency parameters contained in the assignment message. If the mobile station detects an invalid Frequency Parameters information element or an invalid Dual Carrier Frequency Parameters information element in the assignment message, it shall abort the procedure, if required initiate a partial acquisition of PBCCH or BCCH information, and may then re-initiate this procedure.

If the dynamic allocation medium access mode is commanded, the network shall include the USF values allocated for PDCHs in the PACKET UPLINK ASSIGNMENT message.

Unless the mobile station has indicated a "Single Block Without TBF Establishment" or "Single block MBMS access" in a PACKET CHANNEL REQUEST message, the mobile station shall perform a two phase access if the PACKET UPLINK ASSIGNMENT message includes a Single Block Allocation struct or a Multi Block Allocation struct.

If the PACKET UPLINK ASSIGNMENT message includes Dynamic Allocation struct and the MS has not requested ‘Single Block Without TBF Establishment’, ‘Two phase access’ , or ‘Single Block MBMS access’, the mobile station shall perform a one phase access.

In case the MS requested two phase access, the procedures in sub-clause 7.1.3 shall apply.

A mobile station that has indicated "Single Block Without TBF Establishment" in the PACKET CHANNEL REQUEST message for the purpose of sending a measurement report shall send a measurement report according to sub-clause 7.3.1.

A mobile station that has indicated "Single Block Without TBF Establishment" in the PACKET CHANNEL REQUEST message for the purpose of sending a PACKET CELL CHANGE FAILURE message shall send that message according to sub-clause 8.4.2.

On receipt of a PACKET UPLINK ASSIGNMENT message corresponding to one of its 3 last PACKET CHANNEL REQUEST or EGPRS PACKET CHANNEL REQUEST messages the mobile station shall stop timers T3186 and T3170 if running and stop sending PACKET CHANNEL REQUEST or EGPRS PACKET CHANNEL REQUEST messages.

If the PACKET UPLINK ASSIGNMENT message does not specify a TBF starting time, the mobile station shall switch to the assigned PDCHs, start timer T3164 if dynamic or extended dynamic allocation is assigned and proceed with contention resolution of the one phase packet access procedure according to sub-clause 7.1.2.3 (A/Gb mode) or in case of EGPRS, sub-clause 7.1.2.3a (A/Gb mode).

Unless assigning resources for RTTI, dual carrier, BTTI with FANR activated or EGPRS2 configurations, a PACKET UPLINK ASSIGNMENT message may indicate an assignment starting time in the TBF Starting Time parameter. The mobile station shall monitor the full PCCCH until the point in time denoted by the TBF Starting Time. Thereafter it shall switch to the assigned PDCHs. If dynamic or extended dynamic allocation is assigned, the mobile station shall start timer T3164. Regardless of which allocation mode is used, the mobile station shall proceed with the contention resolution defined in sub-clause 7.1.2.3 (A/Gb mode) or in case of EGPRS, sub-clause 7.1.2.3a (A/Gb mode). If the mobile station receives more than one PACKET UPLINK ASSIGNMENT message, it shall act upon the most recently received message and shall ignore the previous message.

When the mobile station switches to the assigned PDCHs, it shall take the power control parameters received in the PACKET UPLINK ASSIGNMENT message into account, perform signal strength measurements and apply output power control procedures as they are defined for packet transfer mode or MAC-Shared state (see 3GPP TS 45.008).

On receipt of a PACKET CHANNEL REQUEST message with establishment cause indicating "Two Phase Access Request" , "Single block without TBF establishment" or "Single block MBMS access", the network may allocate a single radio block on an uplink PDCH. In order to force the mobile station to make a two phase access, the network may allocate a single radio block on an uplink PDCH on receipt of a PACKET CHANNEL REQUEST message with any of the other access types.

On receipt of an EGPRS PACKET CHANNEL REQUEST message with establishment cause indicating "Two Phase Access Request", the network may allocate a Multi Block allocation on an uplink PDCH. In order to force the mobile station to make a two phase access, the network may allocate a Multi Block allocation on an uplink PDCH on receipt of a EGPRS PACKET CHANNEL REQUEST message with any of the other access types.

If the mobile station has been allocated a single block (respectively a Multi Block allocation) in the PACKET UPLINK ASSIGNMENT message and the mobile station has not indicated "Single block without TBF establishment" (respectively "Two phase access") in the PACKET CHANNEL REQUEST (respectively EGPRS PACKET CHANNEL REQUEST) message or "Single block MBMS access" in the PACKET CHANNEL REQUEST message, the mobile station shall proceed with the two phase packet access procedure according to sub-clause 7.1.3 (A/Gb mode).

If the mobile station has been allocated a single block in the PACKET UPLINK ASSIGNMENT message and the purpose of the packet access procedure is to send a Measurement Report message and the mobile station has indicated "Single block without TBF establishment" in the PACKET CHANNEL REQUEST message, the mobile station shall proceed according to sub-clause 7.3.1.

If the mobile station has been allocated a single block in the PACKET UPLINK ASSIGNMENT message and the purpose of the packet access procedure is to send a PACKET PAUSE message and the mobile station has indicated "Single block without TBF establishment" in the PACKET CHANNEL REQUEST message, the mobile station shall proceed according to sub-clause 7.6.

If the mobile station has been allocated a single block in the PACKET UPLINK ASSIGNMENT message and the purpose of the packet access procedure is to send an MBMS SERVICE REQUEST message and the mobile station has indicated "Single block MBMS access" in the PACKET CHANNEL REQUEST message, the mobile station shall proceed according to sub-clause 7.7.1.2.2.

7.1.2.2.1a Acquisition of MS Radio Access Capability information within EGPRS TBF establishment procedure

When assigning an EGPRS TBF, the network may request information about radio access capabilities of the mobile station on one or several frequency bands within the PACKET UPLINK ASSIGNMENT message; the list of frequency bands is ordered by the network starting with the most important and ending with the least important one. The mobile station shall provide the network with its radio access capabilities for the frequency bands it supports, in the same priority order as the one specified by the network, by sending a PACKET RESOURCE REQUEST message, and an ADDITIONAL MS RADIO ACCESS CAPABILITIES message if all the requested information does not fit in the PACKET RESOURCE REQUEST. If the mobile station does not support any frequency band requested by the network, it shall report its radio access capabilities for the BCCH frequency band. The mobile station shall indicate in the PACKET RESOURCE REQUEST if it will send more information about its radio access capabilities in the ADDITIONAL MS RADIO ACCESS CAPABILITIES message. The PACKET RESOURCE REQUEST and the ADDITIONAL MS RADIO ACCESS CAPABILITIES messages shall be sent within the one or two first radio blocks allocated for the mobile station on the assigned PDCH. The mobile station shall include the TLLI in these two messages until contention resolution. After that, the mobile station may use either the uplink TFI or the TLLI when these messages are repeated.

When constructing the PACKET RESOURCE REQUEST and ADDITIONAL MS RADIO ACCESS CAPABILITIES messages the mobile station shall take care that these messages fit in one UL radio block each. See sub-clause 12.30 for additional restrictions regarding how information for a given access technology type is to be provided using these messages.

The network may request a retransmission of the PACKET RESOURCE REQUEST and the ADDITIONAL MS RADIO ACCESS CAPABILITIES messages. A request for retransmission of one or both of these messages shall be indicated in the PACKET UPLINK ACK/NACK or the PACKET UPLINK ASSIGNMENT message. The mobile station has to indicate within the PACKET RESOURCE REQUEST message if the message is a retransmitted one. For the case of message retransmission the most recently sent instance of these messages shall be retransmitted. If these messages have not already been sent by the MS during the establishment (two phase access) or after the establishment (one phase access) of the corresponding uplink TBF then the request shall be ignored.

7.1.2.2.2 Packet access queuing notification procedure

The network may send to the mobile station a PACKET QUEUING NOTIFICATION message. The PACKET QUEUING NOTIFICATION message shall be sent on the same PCCCH on which the network has received the PACKET CHANNEL REQUEST or EGPRS PACKET CHANNEL REQUEST message. It contains a Temporary Queuing Identity which is later used to identify the mobile station (either when polling or sending an assignment).

On receipt of a PACKET QUEUING NOTIFICATION message corresponding to one of its 3 last PACKET CHANNEL REQUEST or EGPRS PACKET CHANNEL REQUEST messages, the mobile station shall stop timers T3170 and T3186 if running, start timer T3162, and stop sending PACKET CHANNEL REQUEST or EGPRS PACKET CHANNEL REQUEST messages. It shall continue to listen to the full PCCCH corresponding to its PCCCH_GROUP. If the mobile station receives a PACKET QUEUING NOTIFICATION message while waiting for the TBF Starting Time of a valid PACKET UPLINK ASSIGNMENT message, the mobile station shall ignore the PACKET QUEUING NOTIFICATION message.

The network may send to the mobile station a PACKET UPLINK ASSIGNMENT message following a PACKET QUEUING NOTIFICATION message. In this case, the reference address to the mobile station shall be the Temporary Queuing Identity received in the PACKET QUEUING NOTIFICATION message.

On receipt of a PACKET UPLINK ASSIGNMENT message following a PACKET QUEUING NOTIFICATION message, the mobile station shall stop timer T3162 and follow the procedures defined in sub-clause 7.1.2.2.1.

At expiry of timer T3162, the packet access procedure shall be aborted and a packet access failure shall be indicated to the upper layer and the mobile station shall return to packet idle mode or MAC-Idle state.

If the mobile station receives a PACKET DOWNLINK ASSIGNMENT message, it shall abort the packet access queuing notification procedure and respond to the PACKET DOWNLINK ASSIGNMENT message (see sub-clause 7.2.1). The mobile station shall then attempt establishment of an uplink TBF using the procedures defined in sub-clause 8.1.2.5.

7.1.2.2.3 Packet polling procedure

The network may send to the mobile station a PACKET POLLING REQUEST message after having sent a PACKET QUEUING NOTIFICATION message. The PACKET POLLING REQUEST message shall be sent on the same PDCH on which the network has received the PACKET CHANNEL REQUEST or EGPRS PACKET CHANNEL REQUEST message. The mobile station shall be addressed by the Temporary Queuing Identity.

On receipt of a PACKET POLLING REQUEST message, the mobile station shall respond to the network with the PACKET CONTROL ACKNOWLEDGEMENT message in the reserved uplink radio block specified by the RRBP field. The reserved block is considered as a one block PACCH allocation.

7.1.2.2.4 Packet access reject procedure

The network may, as response to a PACKET CHANNEL REQUEST or EGPRS PACKET CHANNEL REQUEST message, send to the mobile station a PACKET ACCESS REJECT message on any PAGCH block on the same PCCCH on which the channel request message was received. This message contains the request reference with time of reception of the PACKET CHANNEL REQUEST or EGPRS PACKET CHANNEL REQUEST message and optionally a WAIT_INDICATION field in the Reject structure of the PACKET ACCESS REJECT message.

On receipt of a PACKET ACCESS REJECT message containing a Reject structure addressed to the mobile station, where the Packet Request Reference in the Reject structure corresponds to one of its 3 last PACKET CHANNEL REQUEST or EGPRS PACKET CHANNEL REQUEST messages:

– The mobile station shall stop timer T3186, stop sending PACKET CHANNEL REQUEST or EGPRS PACKET CHANNEL REQUEST messages, start timer T3172 with the value indicated in the WAIT_INDICATION field, start timer T3170 if it has not already been started and listen to the downlink PCCCH until timer T3170 expires. During this time, the mobile station shall ignore additional PACKET ACCESS REJECT messages, but on reception of any PACKET UPLINK ASSIGNMENT message corresponding to any other of its 3 last PACKET CHANNEL REQUEST or EGPRS PACKET CHANNEL REQUEST messages the mobile station shall stop timers T3170 and T3172 if running, and follow the procedure defined in sub-clause 7.1.2.2.1;

– If no PACKET UPLINK ASSIGNMENT message is received before expiration of timer T3170, the mobile station shall indicate a packet access failure to upper layer and return to packet idle mode (listening to its paging channel). As an option the mobile station may stop timer T3170, indicate a packet access failure to upper layer and return to packet 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 PACKET CHANNEL REQUEST or EGPRS PACKET CHANNEL REQUEST messages;

– If an erroneous PACKET UPLINK ASSIGNMENT message (e.g. the mobile station has been assigned more PDCHs than it supports according to the relevant multislot configuration as defined in 3GPP TS 45.002) addressed to the mobile station is received before expiration of timer T3170, the mobile station shall stop T3170 and act as stated in sub-clause 7.1.4;

– If the mobile station receives a PACKET DOWNLINK ASSIGNMENT message, it shall stop timer T3170 if running and respond to the PACKET DOWNLINK ASSIGNMENT message (see sub-clause 7.2.1);

– The mobile station is not allowed to make a new attempt for packet access in the same cell until timer T3172 expires, but may attempt packet access in another cell after successful cell reselection for radio conditions reasons (see 3GPP TS 45.008). In A/Gb mode, a mobile station that is IMSI attached (GPRS class A or B mode of operation) may attempt to enter the dedicated mode in the same cell before timer T3172 has expired. During the time T3172 is running, the mobile station shall ignore all received PACKET PAGING REQUEST messages except paging requests sent to trigger RR connection establishment and paging requests sent to trigger the acquisition of an ETWS Primary Notification message;

– The value of the WAIT_INDICATION field (i.e. timer T3172) relates to the cell from which it was received.

7.1.2.3 Contention resolution at one phase access

The TLLI is used to uniquely identify the mobile station when sending on uplink. Every RLC data block that is sent on the TBF shall include the TLLI of the mobile station, until the contention resolution is completed on the mobile station side. If MCS-7, MCS-8 or MCS-9 is used for the transmission of the TLLI in EGPRS TBF mode (i.e. the RLC/MAC block is carrying two RLC data blocks), the TLLI shall be inserted in both RLC data blocks. The TLLI shall also be included in the PACKET RESOURCE REQUEST and the ADDITIONAL MS RADIO ACCESS CAPABILITIES messages, if those are sent during the contention resolution.

The retransmission of an RLC data block shall include the TLLI (or the TLLI and the PFI field), if the RLC data block was originally transmitted including these fields, also if the retransmission occurs after the completion of the contention resolution.

At sending of the first RLC data block, the mobile station shall stop timer T3164, set counter N3104 to 1, and start timer T3166. The counter N3104 shall be stepped each time the mobile station sends an RLC/MAC block for data transfer.

The network shall respond by including the TLLI in the PACKET UPLINK ACK/NACK message after the first correctly received RLC data block that comprises the TLLI. In EGPRS TBF mode, the network may instead respond by addressing the mobile station with the TFI of the assigned TBF and including the TLLI (in the CONTENTION_RESOLUTION_TLLI field) in a PACKET UPLINK ASSIGNMENT message, if the resources allocated for the TBF need to be reallocated (see sub-clause 8.1.1.1.2).

The contention resolution is completed on the network side when the network receives an RLC data block that comprises the TLLI value that identifies the mobile station and the TFI value associated with the TBF.

The contention resolution is successfully completed on the mobile station side when the mobile station receives a PACKET UPLINK ACK/NACK message addressing the mobile station with the TFI value associated with the uplink TBF and including the same TLLI value that the mobile station has included in the RLC header of the first RLC data blocks, or alternatively, in EGPRS TBF mode, a PACKET UPLINK ASSIGNMENT message addressing the mobile station with the TFI value associated with the uplink TBF and including the same TLLI value that the mobile station included in the RLC header of the first RLC data blocks. The mobile shall then stop timer T3166 and counter N3104.

The contention resolution has failed on the mobile station side when the counter N3104 reaches its maximum value, or timer T3166 expires. The contention resolution also fails, if the mobile station receives a PACKET UPLINK ACK/NACK message or in EGPRS TBF mode alternatively a PACKET UPLINK ASSIGNMENT message addressing the mobile station with the TFI associated with the uplink TBF and including a TLLI value other than that the mobile station included in the RLC header of the first RLC data blocks; in such a case, the mobile station shall not transmit a PACKET CONTROL ACKNOWLEDGEMENT in the uplink radio block specified if a valid RRBP field is received as part of the PACKET UPLINK ACK/NACK message or in EGPRS TBF mode alternatively as part of the PACKET UPLINK ASSIGNMENT message.

In case of a contention resolution failure on the mobile station side, the mobile station shall reset the counter N3104 and stop timer T3166, if not expired. The mobile station shall stop transmitting on the TBF and reinitiate the packet access procedure, unless the packet access procedure has already been attempted four times. In that case, a TBF failure has occurred, see sub-clause 7.1.4.

7.1.2.3a RLC/MAC procedures during contention resolution

During the contention resolution, the mobile station may receive a non-distribution RLC/MAC control message addressing the mobile station by TLLI, or the TFI value associated with the uplink TBF. The mobile station shall act on that message using the procedure defined for the message when it is received in packet transfer mode during operation on an uplink TBF (see clause 8), with the following restrictions:

– The mobile station shall not accept a PACKET MEASUREMENT ORDER message, a PACKET CELL CHANGE ORDER message and a PACKET POWER CONTROL/TIMING ADVANCE message addressing the mobile station with the TFI value associated with the uplink TBF;

– The mobile station shall not accept a PACKET DOWNLINK ASSIGNMENT or a PACKET TIMESLOT RECONFIGURE message.

If a valid RRBP field is received as part of the RLC/MAC control block, the mobile station shall transmit a PACKET CONTROL ACKNOWLEDGEMENT message in the uplink radio block specified (see sub-clause 10.4.5) if it acts on the message; the mobile station may transmit a PACKET CONTROL ACKNOWLEDGEMENT message in the uplink radio block specified if it does not act on the message.

If during the contention resolution, upper layers request the transfer of another upper layer PDU with a different PFI, a different Radio Priority, a different peak throughput class or a different RLC mode than the one which is in transfer, then the procedures as described in packet transfer mode (see sub-clause 8.1.1.1.2) shall be applied by the mobile station.

In either case, the mobile station shall continue with the contention resolution on the uplink TBF, till it either completes successfully or fails, or that the uplink TBF is released as a result of the procedure defined for the message that is received.

7.1.2.4 One phase packet access completion

The one phase packet access procedure is completed upon a successful contention resolution. The mobile station has entered the packet transfer mode or MAC-Shared state.

7.1.2.5 Timing Advance

Initial timing advance may be provided in the PACKET UPLINK ASSIGNMENT in the TIMING_ADVANCE_VALUE field.

Thereafter either the timing advance is updated with a PACKET POWER CONTROL/TIMING ADVANCE message or a continuous timing advance procedure is used. If a Timing Advance Index is included in the assignment message, the mobile station shall use the continuous timing advance procedure, using its allocation on PTCCH (see 3GPP TS 45.010). Otherwise, the continuous timing advance procedure shall not be used. For the case where a TIMING_ADVANCE_VALUE field is not provided in the assignment message, the mobile station is not allowed to send normal bursts on the uplink until it receives a valid timing advance either through the continuous timing advance procedure or in a PACKET POWER CONTROL/TIMING ADVANCE message.

In the case of a mobile station with a Downlink Dual Carrier configuration where the continuous timing advance procedure is used there is no explicit indication of the carrier on which the PTCCH is allocated, and the mobile station shall consider the PTCCH allocation to be on carrier 1 (see sub-clause 5.5.1.7). If a mobile station with a Downlink Dual Carrier configuration subsequently receives an assignment message which results in the mobile station no longer being in a Downlink Dual Carrier configuration (but still in packet transfer mode), the mobile station shall consider the PTCCH allocation to be on the carrier on which packet resources are assigned.

In the case of a mobile station in a DLMC configuration where the continuous timing advance procedure is used the assignment message indicates the carrier on which the PTCCH is allocated. If a mobile station in a DLMC configuration subsequently receives an assignment message that results in the mobile station no longer being in a DLMC configuration (but still in packet transfer mode), the mobile station shall consider the PTCCH allocation to be on the carrier on which packet resources are assigned.

7.1.2.6 PFC procedure at one phase access

If the PFC_FEATURE_MODE field indicates that the network supports PFC procedures in the system information and if a PFC exists for the LLC data to be transferred then the PFI shall be transmitted along with the TLLI of the mobile station in the RLC extended header during contention resolution. If the PFC_FEATURE_MODE field indicates that the network does not support PFC procedures, the mobile station shall not indicate a PFI value. If no valid PFI is assigned, the default mapping defined in sub-clause 5.5.1.9 shall be used. The PFI is not used for contention resolution but is included to indicate to the network which PFC shall initially be associated with the uplink TBF.

7.1.3 TBF establishment using two phase access

The two phase access procedure defined in this sub-clause, is applicable also in the case when no PCCCH is provided in the cell. For that case, the first phase is defined in 3GPP TS 44.018.

7.1.3.1 Initiation of the Packet resource request procedure

In the first phase of a two phase access in a cell provided with a PCCCH, the same procedures as for one phase access are used until the network sends a PACKET UPLINK ASSIGNMENT message including a Single Block Allocation struct or Multi Block Allocation struct, denoting two phase access to the mobile station. The Multi Block Allocation struct may be used only if the mobile station has EGPRS capability (i.e. the network received an EGPRS PACKET CHANNEL REQUEST message from the mobile station). In the PACKET UPLINK ASSIGNMENT message, the network reserves a limited resource on one PDCH to the mobile station where the mobile station may transmit a PACKET RESOURCE REQUEST message and optionally an ADDITIONAL MS RADIO ACCESS CAPABILITIES message.

If PCCCH is provided in the cell, a two phase access can be initiated:

– by the network by ordering the mobile station to send a PACKET RESOURCE REQUEST message. The order is sent implicitly to the mobile station in the PACKET UPLINK ASSIGNMENT message by including either the Single Block Allocation struct or Multi Block Allocation struct;

– by a mobile station, by requiring a two phase access in the PACKET CHANNEL REQUEST or EGPRS PACKET CHANNEL REQUEST message. In this case, if access is granted, the network shall order the mobile station to send a PACKET RESOURCE REQUEST message. The order is sent implicitly to the mobile station in the PACKET UPLINK ASSIGNMENT message by including the Single Block Allocation struct or Multi Block Allocation struct.

If no PCCCH is provided in the cell, a two phase access can be initiated by the network or by a mobile station, as defined in 3GPP TS 44.018.

When the mobile station has received the PACKET UPLINK ASSIGNMENT message it shall respond with a PACKET RESOURCE REQUEST message in the first allocated radio block.

A mobile station supporting EGPRS shall indicate the EGPRS capability in the MS Radio Access Capability 2 IE of the PACKET RESOURCE REQUEST message.

A mobile station supporting multiple TBF procedures shall set the Multiple TBF Capability flag in the MS Radio Access Capability 2 IE of the PACKET RESOURCE REQUEST message.

A mobile station attempting a packet access for the purpose of NAS signalling low priority (see 3GPP TS 24.008) shall set the Low Access Priority Signalling field to "1" in the PACKET RESOURCE REQUEST message (see sub-clause 11.2.16). The Low Access Priority Signalling field shall be set to "0" if the PACKET RESOUCE REQUEST message is sent for any other reason and includes the Low Access Priority Signalling field.

When the mobile station switches to the assigned PDCH, it shall take the power control parameters received in the PACKET UPLINK ASSIGNMENT message into account, perform signal strength measurements and apply output power control procedures as they are defined for packet transfer mode (see 3GPP TS 45.008).

At sending of the PACKET RESOURCE REQUEST message requesting a single uplink TBF, the mobile station shall start timer T3168. At sending of the PACKET RESOURCE REQUEST message requesting multiple TBFs, the mobile station shall start contention resolution timer T3188 and additionally one instance of T3168 for each of the resource requests for the transfer of upper layer PDUs. Furthermore, the mobile station shall not respond to PACKET DOWNLINK ASSIGNMENT or MULTIPLE TBF DOWNLINK ASSIGNMENT messages before contention resolution is completed on the mobile station side – but may acknowledge such messages if they contain a valid RRBP field.

The mobile station may indicate in the PACKET RESOURCE REQUEST message the number of octets of user data it has to transfer.

7.1.3.2 Packet resource assignment for uplink procedure

When assigning a Multi Block Allocation, the network may request information about radio access capabilities of the mobile station on one or several frequency bands within the PACKET UPLINK ASSIGNMENT message and allocate one or two radio blocks for uplink control messages accordingly; the list of frequency bands is ordered by the network starting with the most important and ending with the least important one. The mobile station shall provide the network with its radio access capabilities for the frequency bands it supports, in the same order of priority as specified by the network, by sending a PACKET RESOURCE REQUEST message in the first radio block on the assigned PDCH and an ADDITIONAL MS RADIO ACCESS CAPABILITIES message in the next radio block on the assigned PDCH, if the requested information does not fit in the PACKET RESOURCE REQUEST and two radio blocks have been allocated by the network. If the network does not provide an Access Technologies Request in the PACKET UPLINK ASSIGNMENT message or the mobile station does not support any frequency band requested by the network, it shall report its radio access capabilities for the frequency band of the BCCH carrier in the PACKET RESOURCE REQUEST message.

The mobile station shall indicate in the PACKET RESOURCE REQUEST message, by setting the ADDITIONAL MS RAC INFORMATION AVAILABLE bit, if it will send more information about its radio access capabilities in the ADDITIONAL MS RADIO ACCESS CAPABILITIES message if it has been allocated two radio blocks, or if it would have sent more information but has been allocated only one radio block. If the mobile station has been allocated two radio blocks and the requested information fit in the PACKET RESOURCE REQUEST message, no ADDITIONAL MS RADIO ACCESS CAPABILITIES message shall be sent. Instead, some uplink control block (e.g. packet measurement report, packet uplink dummy control block) may be sent by the mobile station.

The network may indicate in the next PACKET UPLINK ASSIGNMENT or MULTIPLE TBF UPLINK ASSIGNMENT message a request for retransmission of the ADDITIONAL MS RADIO ACCESS CAPABILITIES message (see sub-clause 7.1.3.2.1).

When constructing the PACKET RESOURCE REQUEST and ADDITIONAL MS RADIO ACCESS CAPABILITIES messages the mobile station shall take care that these messages fit in one uplink radio block each (see sub-clause 7.1.2.2.1a).

If the network indicates that it supports packet flow procedures via the PFC_FEATURE_MODE in the system information, then the mobile station supporting PFC procedures shall indicate the initial PFI to be associated with the TBF in the PACKET RESOURCE REQUEST message. If the PFC_FEATURE_MODE field indicates that the network does not support PFC procedures, the mobile station shall not indicate a PFI value. If no valid PFI is assigned, the default mapping defined in sub-clause 5.5.1.9 shall be used. If the mobile station requests multiple TBFs in the PACKET RESOURCE REQUEST message, it shall indicate the PFI to be associated with each TBF.

Whenever the mobile station wants to pre-allocate an uplink TBF, it shall send a PACKET RESOURCE REQUEST message with the EARLY_TBF_ESTABLISHMENT field set to indicate pre-allocation is required.

7.1.3.2.1 On receipt of a PACKET RESOURCE REQUEST message

On receipt of a PACKET RESOURCE REQUEST message requesting a single uplink TBF scheduled with a Single Block or a Multi Block allocation, the network shall respond by sending a PACKET UPLINK ASSIGNMENT message (radio resources assignment on one or more PDCHs to be used by the mobile station for the TBF in EGPRS or GPRS TBF mode) or a PACKET ACCESS REJECT message to the mobile station on PACCH on the same PDCH on which the mobile station has sent the PACKET RESOURCE REQUEST message. If the mobile station supports RLC non-persistent mode the network may allocate an EGPRS TBF that uses this RLC mode.

On receipt of a PACKET RESOURCE REQUEST message requesting multiple uplink TBFs, the network shall respond by sending either a MULTIPLE TBF UPLINK ASSIGNMENT message or a PACKET ACCESS REJECT message to the mobile station on PACCH on the same PDCH on which the mobile station has sent the PACKET RESOURCE REQUEST message. These messages shall address (assign or reject) some or all of the resource requests in the PACKET RESOURCE REQUEST message. For the resource requests that have not been addressed by the first assignment or reject message, additional MULTIPLE TBF UPLINK ASSIGNMENT or PACKET ACCESS REJECT messages may be sent to the mobile station on the PACCH to which the mobile station has been assigned. If the mobile station supports RLC non-persistent mode the network may allocate one or more EGPRS TBFs that use this RLC mode.

If the received PACKET RESOURCE REQUEST message is indicating additional MS Radio Access Capabilities information available, the following additional requirements apply:

– If the PACKET RESOURCE REQUEST message was scheduled with a Multi Block allocation of two blocks, the network shall respond by sending a PACKET UPLINK ASSIGNMENT or MULTIPLE TBF UPLINK ASSIGNMENT message after reception of the ADDITIONAL MS RADIO ACCESS CAPABILITIES message;

– If the PACKET RESOURCE REQUEST message was scheduled with a Single Block allocation or with a Multi Block allocation of only one block, the network shall respond upon receipt by sending a PACKET UPLINK ASSIGNMENT or MULTIPLE TBF UPLINK ASSIGNMENT message. When assigning one or more EGPRS TBFs, the network may request additional information about radio access capabilities of the mobile station on one or several frequency bands within the PACKET UPLINK ASSIGNMENT or MULTIPLE TBF UPLINK ASSIGNMENT message; the list of frequency bands is ordered by the network starting with the most important and ending with the least important one. The mobile station shall provide the network with its radio access capabilities for the frequency bands it supports, in the same priority order as the one specified by the network, by sending an ADDITIONAL MS RADIO ACCESS CAPABILITIES message within the first radio block allocated to the mobile station on the assigned PDCH(s). When constructing the ADDITIONAL MS RADIO ACCESS CAPABILITIES message, the mobile station shall take care that this message fits in one uplink radio block (see sub-clause 7.1.2.2.1a). If the mobile station does not support any frequency band requested by the network, it shall report its radio access capabilities for the BCCH frequency band.

In case the ADDITIONAL MS RADIO ACCESS CAPABILITIES message is not received correctly, the network may either:

– send a PACKET UPLINK ASSIGNMENT or MULTIPLE TBF UPLINK ASSIGNMENT message assigning radio resources on one or more PDCHs to be used by the mobile station for the TBF(s) in EGPRS or GPRS TBF mode, based on the information the network has got, or let unchanged the already assigned PDCH(s);

– send a PACKET UPLINK ASSIGNMENT message assigning (or reassigning) radio resources on one or more PDCHs to be used by the mobile station for the TBF(s) in EGPRS TBF mode and request a retransmission of the ADDITIONAL MS RADIO ACCESS CAPABILITIES message.

In addition, in case the ADDITIONAL MS RADIO ACCESS CAPABILITIES message scheduled with a Multi Block allocation of two blocks is not received correctly, the network may either:

– send a PACKET UPLINK ASSIGNMENT or MULTIPLE TBF UPLINK ASSIGNMENT message including a Multi Block allocation struct (allocating only one block) requesting a retransmission of the ADDITIONAL MS RADIO ACCESS CAPABILITIES message;

– send a PACKET ACCESS REJECT message to the mobile station.

On receipt of a PACKET UPLINK ASSIGNMENT or MULTIPLE TBF UPLINK ASSIGNMENT message where no TBF starting time is specified, the mobile station shall switch to the assigned PDCHs, stop T3168 for each resource request that is assigned a TBF in the PACKET UPLINK ASSIGNMENT or Multiple TBF Uplink Assignment message, and start timer T3164 for each allocated TBF if dynamic or extended dynamic allocation is assigned. If a TBF starting time is specified the mobile station shall stop T3168 for each resource request assigned a TBF and wait until the indicated TBF starting time before switching to the assigned PDCHs and starting T3164 for each allocated TBF.

At sending of the first RLC data block on a TBF, the mobile station shall stop timer T3164 for that TBF.

The mobile station may use information received on PBCCH, BCCH or a previous assignment message to decode the frequency parameters contained in the assignment message. If the mobile station detects an invalid Frequency Parameters information element in the assignment message, it shall abort the procedure, if required initiate a partial acquisition of PBCCH or BCCH information, and may then re-initiate the access on the PRACH.

On receipt of a PACKET ACCESS REJECT message that contains a Reject structure addressed to the mobile station, the mobile station shall stop timer T3168 and indicate a packet access failure to upper layer for each resource request which is rejected in the Reject structure.

If the PACKET ACCESS REJECT message contains a WAIT_INDICATION field in a Reject structure addressed to the mobile station, the mobile station shall start timer T3172 with the indicated value (Wait Indication). The mobile station is not allowed to make a new attempt for packet access in the same cell until timer T3172 expires, but may attempt packet access in another cell after successful cell reselection.

When the network receives a Packet Flow Identifier (PFI) from the mobile then the network should handle the uplink transfer according the associated aggregate BSS QoS profile (ABQP). The Peak Throughput specified in the associated ABQP, available in the network, supersedes the Peak Throughput specified by the Channel Request Description IE.

When an uplink TBF is established in response to a PACKET RESOURCE REQUEST message with the EARLY_TBF_ESTABLISHMENT field set to indicate pre-allocation is required, a network supporting early TBF establishment should keep the uplink TBF open by means of the extended uplink TBF mode operation (see sub-clause 9.3.1b.2).

7.1.3.3 Contention resolution at two phase access

The contention resolution is completed on the network side when the network receives a TLLI value identifying the mobile station, as part of the contention resolution procedure on the TBF.

The contention resolution is completed on the mobile station side when the mobile station receives a PACKET UPLINK ASSIGNMENT , Multiple TBF UPLINK ASSIGNMENT or PACKET ACCESS REJECT message with the same TLLI as the mobile station has included in the PACKET RESOURCE REQUEST and ADDITIONAL MS RADIO ACCESS CAPABILITIES messages that addresses at least one TBF for which resources were requested in the PACKET RESOURCE REQUEST message.

– If the mobile station receives an assignment for its single uplink TBF request, it shall then stop timer T3168. It does not include its TLLI in any RLC data block;

– If the mobile station receives an assignment for at least one TBF of a multiple uplink TBF request, it shall then stop timer T3188 and the instance of T3168 which was started for the assigned TBF. It does not include its TLLI in any RLC data block.

After contention resolution is successfully completed on the mobile station side, if the mobile station requested multiple uplink TBFs and an instance of timer T3168 expires, TBF establishment for the corresponding upper layer PDU has failed. The mobile station shall reinitiate a resource request for that upper layer PDU using the procedures described in sub-clauses 8.1.1.1.2a and 8.1.1.1.2b.

The contention resolution has failed on the mobile station side when the mobile station does not receive a PACKET UPLINK ASSIGNMENT or Multiple TBF UPLINK ASSIGNMENT message with its TLLI assigning at least one TBF for which resources were requested before expiry of timer T3168 (single uplink TBF requested) or T3188 (multiple uplink TBFs requested). The mobile station shall then reinitiate the packet access procedure unless the packet access procedure has already been attempted four times. In that case, TBF failure has occurred and an RLC/MAC error should be reported to the higher layer for each of the TBFs for which resources were requested.

7.1.3.4 Two phase packet access completion

The two phase packet access procedure is completed upon a successful contention resolution. The mobile station has entered the packet transfer mode or MAC-Shared state.

7.1.3.5 Timing Advance

If a Timing Advance Index is included in the PACKET UPLINK ASSIGNMENT message, the mobile station shall use the continuous timing advance procedure, using its allocation on PTCCH (see 3GPP TS 45.010). Otherwise, the continuous timing advance procedure shall not be used.

For the case where a TIMING_ADVANCE_VALUE field is not provided in the assignment message, the mobile station shall use its previous timing advance (either assigned in the previous IMMEDIATE ASSIGNMENT or IMMEDIATE PACKET ASSIGNMENT message received on AGCH or in the previous PACKET UPLINK ASSIGNMENT message received on PAGCH or got through the continuous timing advance procedure).

Otherwise, the mobile station is not allowed to send normal bursts on the uplink until it receives a valid timing advance either through the continuous timing advance procedure or in a PACKET POWER CONTROL/TIMING ADVANCE message.

In the case of a mobile station with a Dual Carrier configuration where the continuous timing advance procedure is used there is no explicit indication of the carrier on which the PTCCH is allocated, and the mobile station shall consider the PTCCH allocation to be on carrier 1 (see sub-clause 5.5.1.7). If a mobile station with a Dual Carrier configuration subsequently receives an assignment message which results in the mobile station no longer being in a Dual Carrier configuration (but still in packet transfer mode), the mobile station shall consider the PTCCH allocation to be on the carrier on which packet resources are assigned.

7.1.3.6 RTTI Assignments

If assigned resources are for an RTTI configuration, then the assignment message (e.g. PACKET DOWNLINK ASSIGNMENT, PACKET UPLINK ASSIGNMENT, etc.) specifies a set of PDCH pairs for both the uplink and downlink.

If the default single carrier PDCH pair configuration is indicated, then the assignment is for resources on a subset of the PDCH pairs consisting of the ordered sequence of timeslots pairs 0 and 1 (pair 1), 2 and 3 (pair 2), 4 and 5 (pair 3), and 6 and 7 (pair 4) in both the uplink and on the downlink. If the default dual carrier PDCH pair configuration is indicated, then the assignment is for resources on a subset of the PDCH pairs consisting of the ordered sequence of timeslots pairs 0 and 1, 2 and 3, 4 and 5, and 6 and 7 on both carriers (respectively numbered as pairs 1 to 4 on the first carrier and pairs 5 to 8 on the second carrier) in both the uplink and on the downlink. Otherwise, the assignment is for resources on a subset of the PDCH pairs as specified in the DOWNLINK_PDCH_PAIRS_C1, DOWNLINK_PDCH_PAIRS_C2, UPLINK_PDCH_PAIRS_C1 and UPLINK_PDCH_PAIRS_C2 bitmaps.

If the mobile station is currently in packet transfer mode with one or more ongoing TBFs operating in RTTI configuration, then the network may indicate in the assignment message that the PDCH pair configuration is ‘Unchanged’. In this case, the PDCH pair configuration described in the most recently received assignment message (for this mobile station) previous to this message applies.

The Uplink Assignment PDCH Pairs Description IE shall be included in a PACKET CS RELEASE INDICATION, PS HANDOVER COMMAND or DTM HANDOVER COMMAND message assigning an RTTI configuration for uplink TBF(s) if and only if no RTTI configuration description for downlink TBF(s) is provided in these messages.

For the purposes of interpreting the RTTI_DOWNLINK_PDCH_PAIR_ASSIGNMENT_SC and RTTI_DOWNLINK_PDCH_PAIR_ASSIGNMENT_DC bitmaps and the repeated USF structures in the Dynamic Allocation 2 struct and Uplink TBF Assignment 2 struct, PDCH pairs are ordered starting with the PDCH pair on carrier 1 using the lowest numbered timeslots, followed by the PDCH pair on carrier 1 using the next lowest numbered timeslots and so on, followed by the PDCH pair on carrier 2 using the lowest numbered timeslots (if present), etc.

For an uplink PDCH pair using timeslots i and j, where j > i , the corresponding downlink PDCH pair is:

– the one using timeslots i and j; else, if no such PDCH pair is specified

– the one using timeslots i-1 and i; else, if no such PDCH pair is specified

– the one using timeslots i-2 and i; else, if no such PDCH pair is specified

– the one using timeslots i-3 and i if such a PDCH pair exists.

NOTE: It may be the case that there is no downlink PDCH pair which corresponds to a given uplink PDCH pair.

For a downlink PDCH pair, the corresponding uplink PDCH pair is the uplink PDCH pair (if it exists) for which the downlink PDCH pair is the corresponding downlink PDCH pair.

NOTE: It may be the case that there is no uplink PDCH pair which corresponds to a given downlink PDCH pair.

The network shall activate FANR for any assigned TBF which uses an RTTI configuration (see sub-clause 9.1.14).

7.1.3.7 MTTI Configurations

If the mobile station supports MTTI configurations, the network may assign a mobile station a TBF comprising a combination of both RTTI and BTTI resources (i.e. MTTI resources). In this case the assigned MTTI resources consist of one PDCH and one or more PDCH-pairs where the PDCH is always assigned the timeslot adjacent to either the lowest or highest numbered timeslot of the assigned PDCH-pairs on that carrier. In a downlink dual carrier configuration, a TBF operating in MTTI configuration shall be assigned MTTI resources on one or both carriers. If MTTI resources are only assigned on one carrier then the remaining carrier may be assigned either BTTI or RTTI resources.

NOTE: Examples of valid and invalid MTTI configurations are illustrated in Annex M.

The specification of the following MAC procedures includes aspects which are specific to MTTI configurations:

– Selection of RLC data blocks for transmission on RTTI and BTTI resources (see sub-clause 8.1.1);

– Uplink transfer and PACCH operation when using Extended Dynamic Allocation (see sub-clauses 8.1.1.2.1 and 8.1.1.2.2).

Other MAC procedures applicable to the RTTI and BTTI resources assigned as part of an MTTI configuration apply as if they were separate TBFs, and therefore references to a "TBF operating in RTTI configuration" (respectively "TBF operating in BTTI configuration") shall also refer to "resources operating in RTTI configuration within an MTTI configuration" (respectively "resources operating in BTTI configuration within an MTTI configuration"),.

The specification of the following RLC procedures includes aspects which are specific to MTTI configurations:

– Encoding and interpretation of Piggy-backed Ack/Nack fields encoded using Time-based encoding (see sub-clauses 9.1.15 and 11.2.29);

– Countdown procedure: definition of MTS parameter (see sub-clause 9.3.1.1).

The network shall activate FANR for any assigned TBF which uses an MTTI configuration.

Reaction times applicable to TBFs operating in MTTI configurations shall be those specified for TBFs operating in RTTI configurations (see 3GPP TS 45.010)

7.1.4 Abnormal cases

If a failure occurs on the mobile station side of the new TBF before mobile station has successfully entered the packet transfer mode, the newly reserved resources are released; the subsequent behaviour of the mobile station depends on the type of failure and previous actions.

– If the failure is due to a TLLI mismatch, or to the expiry of timers T3166 or T3168, or to the fact that the counter N3104 reaches its maximum value in the contention resolution procedure, and repetition as described in sub-clauses 7.1.2.3, 7.1.3.2.1 or 7.1.3.3 has been performed, the mobile station shall remain in packet idle mode, notify higher layer (TBF establishment failure), transactions in progress shall be aborted and cell reselection continued, unless the failure takes place during a RR-cell change order procedure, in which case the mobile behaviour shall be as described in the Abnormal cases of the RR-Network Commanded Cell Change Order Procedure in 3GPP TS 44.018;

– If the mobile station has been assigned more PDCHs than it supports according to the relevant multislot configuration as defined in 3GPP TS 45.002, the mobile station shall reinitiate the packet access procedure unless the packet access procedure has already been attempted four times. In that case, TBF failure has occurred;

– If the information in the PACKET UPLINK ASSIGNMENT message does not properly specify an uplink PDCH or specifies a multislot configuration that the mobile station does not support (see 3GPP TS 45.002), the mobile station shall reinitiate the packet access procedure unless the packet access procedure has already been attempted four times. In that case, TBF failure has occurred;

– If the information in the MULTIPLE TBF UPLINK ASSIGNMENT message does not properly specify an uplink PDCH or specifies a multislot configuration that the mobile station does not support (see 3GPP TS 45.002), the mobile station shall reinitiate the packet access procedure for each of the TBFs for which there is an error unless the procedure has already been attempted 4 times for the TBF. In that case, TBF failure has occurred;

– If the MULTIPLE TBF UPLINK ASSIGNMENT message contains assignments including PFI values for which no TBF was requested, the mobile station shall not act upon these assignments. The mobile station shall act upon the valid assignments contained in the received message;

– If the MULTIPLE TBF UPLINK ASSIGNMENT message contains assignments such that more than one PFI value has been assigned to the same TFI, then TBF failure has occurred for the requests containing each of those PFI values;

– If the PACKET UPLINK ASSIGNMENT message contains an assignment including a PFI value for which no resources were requested, the mobile station shall not act upon the assignment. The mobile station shall reinitiate the packet access procedure unless the packet access procedure has already been attempted four times. In that case, TBF failure has occurred;

– If the PACKET ACCESS REJECT message incorrectly specifies a Reject structure and A/Gb mode Reject structure for this mobile station, or contains one or more PFIs in the A/Gb mode Reject structure for which no TBF was requested, the mobile station shall ignore this message;

– If the mobile station has been assigned a TBF in EGPRS mode and the MS does not support EGPRS, or has been assigned an MCS (e.g. 8-PSK in the Uplink) that the MS does not support, the MS shall return to packet idle mode and notify higher layers (TBF establishment failure);

– On expiry of timer T3164, the mobile station shall reinitiate the packet access procedure for the corresponding TBF unless the packet access procedure has already been attempted four times for this TBF, in which case the mobile station shall notify higher layers of TBF establishment failure. If the mobile station has no remaining TBFs allocated it shall return to packet idle mode and notify higher layers (TBF establishment failure);

– If the failure is due to any other reason, the mobile station shall return to packet idle mode, notify higher layer (TBF establishment failure), transactions in progress shall be aborted and cell reselection continues.

7.2 TBF establishment initiated by the network on PCCCH

The purpose of network initiated TBF establishment is to establish a TBF to support the transfer of upper layer PDUs in the direction from the network to the mobile station. The procedure may be entered when the mobile station is in packet idle mode. Network initiated TBF establishment can also be done on PACCH if a TBF for transfer of upper layer PDUs in the direction from the mobile station to the network is already established (sub-clause 8.1.1.1.3).

7.2.1 Entering the packet transfer mode

The procedure is triggered by a request from upper layers on the network side to transfer an upper layer PDU to a mobile station in packet idle mode. 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, multislot class and mobile classmark to be associated with the packet transfer. The request is implicit when receiving an upper layer PDU to a mobile station not already having any assigned radio resources. Upon such a request, the network shall initiate a packet downlink assignment procedure as defined in sub-clause 7.2.1.1. The BSS may order its preferred RLC mode when establishing a downlink TBF, independently of the RLC mode signalled from upper layers. If the mobile station supports RLC non-persistent mode the network may allocate a downlink EGPRS TBF that uses this RLC mode.

7.2.1.1 Packet downlink assignment procedure

The network may assign a radio resource on one or more PDCHs to be used for the TBF. The amount of radio resource to be reserved is a network dependent choice. If the network and mobile station both support Downlink Dual Carrier, the network may assign radio resources on one or more PDCHs on two different radio frequency channels to be used for the TBF.

The allocated radio resource is assigned to the mobile station in a PACKET DOWNLINK ASSIGNMENT message to the mobile station. The PACKET DOWNLINK ASSIGNMENT message is transmitted on the PCCCH timeslot corresponding to the PCCCH group the mobile station belongs to. The appropriate PCCCH group is calculated from the IMSI (see 3GPP TS 45.002). The behaviour of the network when the IMSI is not provided by the upper layers is implementation dependent for the calculation of the PCCCH group where the PACKET DOWNLINK ASSIGNMENT message has to be sent. If the mobile station is in non-DRX mode or if the IMSI or the DRX parameters are not provided by the upper layers, there is no further restriction on what part of the downlink PCCCH timeslot this PACKET DOWNLINK ASSIGNMENT message can be sent, provided that this part corresponds to one or more blocks where paging may appear. If the mobile station applies DRX, this message shall be sent in one or more PCCCH block(s) corresponding to a paging group determined for the mobile station in packet idle mode or MAC-Idle state (see 3GPP TS 45.002). The multislot capabilities of the mobile station shall be considered.

Initial timing advance can be provided in the PACKET DOWNLINK ASSIGNMENT message as Timing Advance Value field. In case valid timing advance for the mobile station is not available, the network may use one of the following two methods to trigger the mobile station to transmit a PACKET CONTROL ACKNOWLEDGEMENT message:

– if the PACKET DOWNLINK ASSIGNMENT message is not segmented and the CONTROL_ACK_TYPE parameter in the System Information indicates acknowledgement is access bursts, the network may set the poll bit in the PACKET DOWNLINK ASSIGNMENT message.

– if the PACKET DOWNLINK ASSIGNMENT message is segmented or the CONTROL_ACK_TYPE parameter in the System Information does not indicate acknowledgement is access bursts, the network may send PACKET POLLING REQUEST message with TYPE_OF_ACK parameter set to access bursts (see sub-clause 11.2.12).

The mobile station shall then send the PACKET CONTROL ACKNOWLEDGEMENT message as four access bursts in the reserved uplink radio block specified by the RRBP field as defined in sub-clause 10.4.5.The reserved block is considered as a one block PACCH allocation. The PACKET CONTROL ACKNOWLEDGEMENT message is used to derive the timing advance.

Thereafter, either the timing advance in the mobile station is updated with a PACKET POWER CONTROL /TIMING ADVANCE message or a continuous timing advance procedure is used. If a Timing Advance Index is included in the assignment message, the mobile station shall use the continuous timing advance procedure, using its allocation on PTCCH (see 3GPP TS 45.010). Otherwise the continuous timing advance procedure shall not be used. For the case where Timing Advance Value is not provided in the assignment message, the mobile station is not allowed to send normal bursts (e.g. PACKET DOWNLINK ACK/NACK message) on the uplink until it receives a valid timing advance either through the continuous timing advance procedure or in a PACKET POWER CONTROL /TIMING ADVANCE message.

In the case of a mobile station with a Downlink Dual Carrier configuration where the continuous timing advance procedure is used there is no explicit indication of the carrier on which the PTCCH is allocated, and the mobile station shall consider the PTCCH allocation to be on carrier 1 (see sub-clause 5.5.1.7). If a mobile station with a Downlink Dual Carrier configuration receives an assignment message which results in the mobile station no longer being in a Downlink Dual Carrier configuration (but still in packet transfer mode), the mobile station shall consider the PTCCH allocation to be on the carrier on which packet resources are assigned.

The mobile station shall use information received on the PBCCH to decode the channel descriptions contained in the assignment. If frequency hopping is applied, the mobile station shall use the last CA received on PBCCH to decode the Mobile Allocation. Alternatively, the network may provide a Mobile Allocation in the assignment. The radio resource is assigned to the mobile station in a PACKET DOWNLINK ASSIGNMENT message. On receipt of a PACKET DOWNLINK ASSIGNMENT message, the mobile station shall switch to the assigned PDCHs.

A PACKET DOWNLINK ASSIGNMENT message may indicate an assignment starting time in the TBF Starting Time parameter. The mobile station shall monitor PCCCH until the point in time denoted by the TBF Starting Time. If the mobile station receives more than one PACKET DOWNLINK ASSIGNMENT message while it monitors the PCCCH, it shall act upon the most recently received message and shall ignore the previous message.

When the PACKET DOWNLINK ASSIGNMENT message is received and after awaiting the point in time denoted by the TBF Starting Time, if such is indicated, the mobile station shall switch to the assigned PDCHs and start timer T3190. The timer T3190 is restarted when receiving the first valid RLC data block addressed to the mobile station. In EGPRS TBF mode T3190 is also restarted when receiving an erroneous RLC data block for which the header is correctly received and which addresses the mobile station.

When the mobile station switches to the assigned PDCHs, it shall take the power control parameters received in the PACKET DOWNLINK ASSIGNMENT message into account, perform signal strength measurements and apply output power control procedures as they are defined for packet transfer mode or MAC-Shared state (see 3GPP TS 45.008). In the case of a mobile station with a Downlink Dual Carrier configuration, the power control parameters may be different for each of the two carriers.

On expiry of timer T3190, the mobile station shall abort the procedure and return to packet idle mode or MAC-Idle state.

7.2.1.2 Packet downlink assignment procedure completion

The packet downlink assignment procedure is completed when the mobile station receives a valid RLC/MAC block. The mobile station has entered the packet transfer mode or MAC-Shared state.

7.2.1.3 Packet polling procedure

The network may send to the mobile station a PACKET POLLING REQUEST message. If the MS has received a PACKET DOWNLINK ASSIGNMENT message with no starting time or with a starting time that has already elapsed, the PACKET POLLING REQUEST message shall be sent on PACCH. Otherwise the PACKET POLLING REQUEST message shall be sent on PAGCH. The mobile station shall be addressed by its TLLI (A/Gb mode), G-RNTI (Iu mode) or TFI.

On receipt of a PACKET POLLING REQUEST message, the mobile station shall respond to the network with the PACKET CONTROL ACKNOWLEDGEMENT message in the reserved uplink radio block specified by the RRBP field as defined in sub-clause 10.4.5. The reserved block is considered as a one block PACCH allocation.

7.2.2 Abnormal cases

If a failure occurs on the mobile station side of the new TBF before mobile station has successfully entered the packet transfer mode or MAC-Shared state, the newly reserved resources are released; the subsequent behaviour of the mobile station depends on the type of failure and previous actions.

– If the mobile station has been assigned more PDCHs than it supports according to the relevant multislot configuration as defined in 3GPP TS 45.002, the mobile station shall return to packet idle mode or MAC-Idle state;

– If the mobile station has been assigned a TBF in EGPRS TBF mode and the MS does not support EGPRS, the MS shall return to packet idle mode or MAC-Idle state and notify higher layers (TBF establishment failure);

– On expiry of timer T3190, the mobile station shall return to packet idle mode or MAC-Idle state;

– If the failure is due to any other reason, the mobile station shall return to packet idle mode or MAC-Idle state and cell reselection continues.

7.3 Procedure for measurement report sending in packet idle mode

The procedure for measurement report sending shall be initiated by the mobile station at expiry of the NC measurement report interval timer T3158. At expiry of the timer T3158 the mobile station shall restart the expired timer T3158, perform the measurements and initiate the packet access.

The procedure for measurement report sending is initiated by the mobile station either on PCCCH (sub-clause 7.3.1) or, if a packet control channel not exists, on CCCH (sub-clause 7.3.2).

If the mobile station initiates the establishment of an RR connection, the timer T3158 shall be stopped and no measurement reports shall be sent. When the RR connection is released and if the mobile station has not changed cell, the measurement reporting procedure shall be restarted.

If a cell change has occurred during the RR connection, the measurements shall be cancelled until new NC orders have been received (see sub-clause 5.6).

7.3.1 Measurement report sending procedure initiated on PCCCH

The packet access procedure is initiated by the RR entity in the mobile station as specified in sub-clauses 7.1.2.1 and 7.1.2.2 but with access type "Single block without TBF establishment" indicated in the PACKET CHANNEL REQUEST message. In the following sub-clauses the procedure is only briefly summarised and special requirements are indicated.

7.3.1.1 On receipt of a PACKET CHANNEL REQUEST message

On receipt of a PACKET CHANNEL REQUEST message with access type indicating ‘Single block without TBF establishment’, the network may allocate one radio block on an uplink PDCH.

If uplink resources are not available, the network may reject the access request by sending a PACKET ACCESS REJECT message (see sub-clause 7.3.1.3). The network shall not respond to a packet access for measurement reporting by sending a PACKET QUEUING NOTIFICATION message.

The radio resource is assigned to the mobile station in a PACKET UPLINK ASSIGNMENT message sent on any PAGCH on the same PCCCH on which the network has received the PACKET CHANNEL REQUEST message. The PACKET UPLINK ASSIGNMENT message shall include the following optional parameters:

– Power Control Parameters with timeslot allocation;

– Frequency parameters;

– TBF_STARTING_TIME indicating the frame number of the allocated block;

– TIMING_ADVANCE_VALUE;

– Packet Request Reference.

7.3.1.2 On receipt of a PACKET UPLINK ASSIGNMENT message

When receiving a PACKET UPLINK ASSIGNMENT message the mobile station shall send either the PACKET MEASUREMENT REPORT message or the PACKET ENHANCED MEASUREMENT REPORT message in the allocated radio block on the assigned PDCH and immediately switch back to the PCCCH in non-DRX mode (see sub-clause 5.5.1.5). No TBF is established and the network shall not acknowledge the reception of the PACKET MEASUREMENT REPORT message or the PACKET ENHANCED MEASUREMENT REPORT message.

The PACKET MEASUREMENT REPORT message shall contain the NC Measurement Report struct.

If timer T3170 expires before a PACKET UPLINK ASSIGNMENT message is received, the packet access procedure is aborted, the transmission of the measurement report for that measurement period is cancelled, and the mobile station shall indicate a random access failure to upper layer and perform autonomous cell re-selection.

7.3.1.3 On receipt of a PACKET ACCESS REJECT message

The network may send to the mobile station a PACKET ACCESS REJECT message.

The mobile station shall react to this as described in sub-clause 7.1.2.2.4 with the exception of the actions taken when either of the timers T3172 or T3162 expires. In this case, the measurement report initiating the packet access shall be discarded and the mobile station shall return to packet idle mode or MAC-Idle state.

If the measurement report interval timer T3158 expires before any of the timers T3172 or T3162 expires, no new measurement shall be initiated but the timer T3158 shall be restarted.

7.3.1.4 Abnormal cases

If the PACKET UPLINK ASSIGNMENT message contains faulty parameters, the mobile station shall abort the packet access procedure and return to packet idle mode or MAC-Idle state. The measurement report initiating the packet access shall be discarded.

If the mobile station receives either a PACKET QUEUING NOTIFICATION message or a PACKET POLLING REQUEST message, the mobile station shall abort the packet access procedure and return to packet idle mode or MAC-Idle state. The measurement report initiating the packet access shall be discarded.

7.3.2 Measurement report sending procedure initiated on CCCH

For detailed description of the procedures following in this sub-clause, see 3GPP TS 44.018. The procedure is here only briefly summarised and special requirements are indicated.

The packet access procedure is initiated by the RR entity in the mobile station. The mobile station sends a CHANNEL REQUEST message indicating ‘Single block packet access’ on RACH. The network shall then respond with either an IMMEDIATE ASSIGNMENT message granting a "single block access" on a PDCH or an IMMEDIATE ASSIGNMENT REJECT message (see 3GPP TS 44.018).

If a PDCH block is assigned, the mobile station shall send either the PACKET MEASUREMENT REPORT message or the PACKET ENHANCED MEASUREMENT REPORT message in the allocated radio block on the assigned PDCH and then immediately switch back to the CCCH in non-DRX mode (see sub-clause 5.5.1.5). No TBF is established and the network shall not acknowledge the reception of the PACKET MEASUREMENT REPORT message or the PACKET ENHANCED MEASUREMENT REPORT message.

The PACKET MEASUREMENT REPORT message shall contain the NC Measurement Report struct.

On receipt of an IMMEDIATE ASSIGNMENT REJECT message the mobile station shall follow the procedure specified in 3GPP TS 44.018 sub-clause ‘Packet access rejection’ with the exception of the actions taken when either of the 3GPP TS 44.018 timers T3142 or T3146 expires. In this case, the measurement report initiating the packet access shall be discarded and the mobile station shall return to packet idle mode.

If the measurement report interval timer T3158 expires before any of the 3GPP TS 44.018 timers T3142 or T3146 expires, no new measurement shall be initiated but the timer T3158 shall be restarted.

7.4 Cell Change Order procedures in Packet Idle mode

For an individual mobile station in packet idle mode, the network may initiate the cell change order procedure either on PCCCH or, if a packet control channel does not exist, on CCCH.

7.4.1 Cell Change Order procedure initiated on PCCCH

The network may initiate the cell change order procedure by sending a PACKET CELL CHANGE ORDER message in a PCCCH block monitored by the mobile station. No TBF shall be established.

The PACKET CELL CHANGE ORDER message contains:

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

– The NC measurement parameters valid for the mobile station in the new cell (NETWORK_CONTROL_ORDER and optionally: NC_NON_DRX_PERIOD, NC_REPORTING_PERIOD_I and NC_REPORTING_PERIOD_T).

For a multi-RAT mobile station supporting UTRAN, the PACKET CELL CHANGE ORDER message may contain information on a UTRAN target cell; in this case, the establishment of channel(s) and subsequent measurement reporting are defined in 3GPP TS 25.331.

For a multi-RAT mobile station supporting "CCN towards E-UTRAN, E-UTRAN Neighbour Cell measurement reporting and Network controlled cell reselection to E-UTRAN", the PACKET CELL CHANGE ORDER message may contain information on an E-UTRAN target cell; in this case, the establishment of channel(s) and subsequent measurement reporting are defined in 3GPP TS 36.331.

If the mobile station is not involved in an RR connection, upon receipt of the PACKET CELL CHANGE ORDER message, the mobile station shall stop all relevant RLC/MAC timers except for timers related to measurement reporting and start timer T3174. The mobile station shall then switch to the specified new cell and obey the relevant RLC/MAC procedures on this new cell. If a valid RRBP field was received in the PACKET CELL CHANGE ORDER message then the MS shall send a PACKET CONTROL ACKNOWLEDMENT message in the reserved uplink radio block specified by the RRBP field before switching to the new cell. If the timers related to measurement reporting expire while the reselection procedure has not yet been completed, these timers shall be restarted so that the mobile station resumes the measurement reporting procedures once camped on the new cell. A UTRAN capable mobile station ordered to a UTRAN cell shall obey the PACKET CELL CHANGE ORDER message irrespective of whether the target cell is known or not known (see 3GPP TS 25.133 and 3GPP TS 25.123); an E-UTRAN capable mobile station ordered to an E-UTRAN cell shall obey the PACKET CELL CHANGE ORDER message irrespective of whether the target cell is known or not known (see 3GPP TS 36.133).

If the mobile station is involved in an RR connection, the mobile station shall ignore the PACKET CELL CHANGE ORDER message.

The procedure for completion of the cell change order is defined in sub-clause 8.4.1 and abnormal procedures are defined in sub-clause 8.4.2.

7.4.2 Cell Change Order procedure initiated on CCCH

The network may initiate the cell change order procedure by sending an IMMEDIATE ASSIGNMENT message for single block assignment in a CCCH block monitored by the mobile station. No TBF shall be established. The single block assignment procedure is specified in 3GPP TS 44.018.

The network shall then send the PACKET CELL CHANGE ORDER message in the assigned downlink block to the mobile station. The PACKET CELL CHANGE ORDER message contains:

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

– the NC measurement parameters valid for the mobile station in the new cell (NETWORK_CONTROL_ORDER and optionally: NC_NON_DRX_PERIOD, NC_REPORTING_PERIOD_I and NC_REPORTING_PERIOD_T).

Upon receipt of the PACKET CELL CHANGE ORDER message, the mobile station shall stop all relevant RLC/MAC timers except for timers related to measurement reporting and start timer T3174. The mobile station shall then switch to the specified new cell and obey the relevant RLC/MAC procedures on this new cell. If a valid RRBP field was received in the PACKET CELL CHANGE ORDER message then the MS shall send a PACKET CONTROL ACKNOWLEDMENT message in the reserved uplink radio block specified by the RRBP field before switching to the new cell. If the timers related to measurement reporting expire while the reselection procedure has not yet been completed, these timers shall be restarted so that the mobile station resumes the measurement reporting procedures once camped on the new cell. A UTRAN capable mobile station ordered to a UTRAN cell shall obey the PACKET CELL CHANGE ORDER message irrespective of whether or not the target cell is known (see 3GPP TS 25.133 and 3GPP TS 25.123); an E-UTRAN capable mobile station ordered to an E-UTRAN cell shall obey the PACKET CELL CHANGE ORDER message irrespective of whether the target cell is known or not known (see 3GPP TS 36.133).

The procedure for completion of the cell change order is defined in sub-clause 8.4.1 and abnormal procedures are defined in sub-clause 8.4.2.

7.5 Measurement Order procedures in Packet Idle mode

To send the NC Measurement order to an individual mobile station in packet idle mode, the network may establish a connection either on PCCCH or, if a packet control channel does not exist, on CCCH.

7.5.1 Measurement Order procedures initiated on PCCCH

The network may initiate the measurement order procedure by sending a PACKET MEASUREMENT ORDER message in a PCCCH block monitored by the mobile station. The PACKET MEASUREMENT ORDER message overrides a broadcast PSI5 message. If the PACKET MEASUREMENT ORDER message contains multiple instances, the network shall send all instances to the mobile station.

The PACKET MEASUREMENT ORDER message may contain the following optional Measurement order parameters:- TLLI (shall be included in A/Gb mode);

– G-RNTI (shall be included in Iu mode);

– Enhanced measurement parameters.

Upon receipt of the PACKET MEASUREMENT ORDER message, the mobile station shall store the Measurement order parameters . The mobile station shall obey the NETWORK_CONTROL_ORDER as specified in 3GPP TS 45.008 and in sub-clause 5.6.

7.5.2 Measurement Order procedures initiated on CCCH

The network may initiate the measurement order procedure by allocating a single block in an IMMEDIATE ASSIGNMENT message sent to the mobile station on a CCCH block in the same way as specified in sub-clause 7.4.2.

The network shall then send the PACKET MEASUREMENT ORDER message in the assigned downlink block to the mobile station. The PACKET MEASUREMENT ORDER message overrides a broadcast PSI5 message. If the PACKET MEASUREMENT ORDER message contains multiple instances, the network has to repeat the complete procedure with new assignment for each instance of the message.

The PACKET MEASUREMENT ORDER message may contain the following optional Measurement order parameters:

– TLLI (shall be included);

– NC Measurement Parameters (NETWORK_CONTROL_ORDER; NC_NON_DRX_PERIOD; NC_REPORTING_PERIOD_I; NC_REPORTING_PERIOD_T; NC_FREQUENCY_LIST);

– Enhanced measurement parameters.

7.6 Packet Pause procedure

This procedure enables the network to pause GPRS services packet flow for a mobile station with non-GSM capabilities in the downlink direction. The procedure is initiated by the mobile station either on a PCCCH (sub-clause 7.6.1) or, if a packet control channel does not exist, on a CCCH (sub-clause 7.6.2).

7.6.1 Packet pause procedure initiated on PCCCH

The packet access procedure is initiated by the RR entity in the mobile station as specified in sub-clauses 7.1.2.1 and 7.1.2.2 but with access type ‘Single block without TBF establishment’ indicated in the PACKET CHANNEL REQUEST message.

7.6.1.1 On receipt of a PACKET CHANNEL REQUEST message

On receipt of a PACKET CHANNEL REQUEST message with access type indicating "Single block without TBF establishment", the network may allocate one radio block on an uplink PDCH.

If uplink resources are not available, the network may reject the access request by sending a PACKET ACCESS REJECT message (see sub-clause 7.6.1.3). The network shall not respond by sending a PACKET QUEUING NOTIFICATION message.

– Power Control Parameters with timeslot allocation;

– Frequency parameters;

– TBF_STARTING_TIME indicating the frame number of the allocated block;

– TIMING_ADVANCE_VALUE;

– Packet Request Reference.

7.6.1.2 On receipt of a PACKET UPLINK ASSIGNMENT message

When receiving a PACKET UPLINK ASSIGNMENT message the mobile station shall send PACKET PAUSE in the allocated radio block on the assigned PDCH. The mobile station shall stop timer T3204. No TBF is established and the network shall not acknowledge the reception of the PACKET PAUSE message.

If timer T3204 expires before a PACKET UPLINK ASSIGNMENT message is received, the packet pause procedure is aborted.

7.6.1.3 On receipt of a PACKET ACCESS REJECT message

The network may send to the mobile station a PACKET ACCESS REJECT message. The mobile station shall react by aborting the packet pause procedure and stopping timer T3204.

7.6.1.4 Abnormal cases

If on the mobile station side timer T3204 expires indicating unsuccessful channel request procedure or if the PACKET UPLINK ASSIGNMENT message contains faulty parameters, the mobile station shall abort the packet pause procedure.

If the mobile station receives either a PACKET QUEUING NOTIFICATION message or a PACKET POLLING REQUEST message, the mobile station shall abort the packet pause procedure.

7.6.2 Packet pause procedure initiated on CCCH

For a description of the procedure, see 3GPP TS 44.018.

7.7 MBMS packet access and establishment procedures

7.7.1 MBMS packet access procedure

7.7.1.1 General

This procedure enables the network to count the number of mobile stations in a cell that want to receive an MBMS session. If the procedure is initiated by the mobile station as a response to an MBMS notification, which contains uplink resource description for an MPRACH, or after cell reselection during an ongoing MBMS session, if the mobile station is in DRX mode (e.g. it is not involved in a routeing area update procedure) and has received in the old serving cell the indication that in the new cell an MPRACH is allocated for that MBMS session, the procedure shall be initiated on that MPRACH (sub-clause 7.7.1.4). Otherwise the procedure is initiated by the mobile station either on a PCCCH (sub-clause 7.7.1.2) or, if a packet control channel is not allocated in the cell, on a CCCH (sub-clause 7.7.1.3).

The procedure may be initiated by the mobile station either:

– as a response to an MBMS notification where counting is requested; or

– in the new cell after cell reselection during an ongoing MBMS session, if MBMS is supported by the network in the new cell; or

– when a request is received from upper layer in the mobile station, if MBMS is supported by the network in the cell; or

– after timeout when waiting for an RLC block for this session.

NOTE: The mobile station shall not initiate an MBMS packet access procedure in a new cell after cell reselection if the mobile station already has information about the location and identifier of the MBMS radio bearer relevant to the ongoing MBMS session in that new cell and it contains no uplink feedback channel.

A mobile station that is IMSI attached (GPRS class A or B mode of operation) shall respond to a PACKET PAGING REQUEST message indicating an RR connection establishment or TBF establishment. For that purpose, the mobile station shall abort the MBMS packet access procedure, according to the conditions stated in sub-clause 6.1.4.

If the mobile station receives a PACKET DOWNLINK ASSIGNMENT message, it shall abort the MBMS packet access procedure and respond to the PACKET DOWNLINK ASSIGNMENT message (see sub-clause 7.2.1)

7.7.1.2 MBMS packet access procedure on PCCCH

7.7.1.2.0 Initiation of the MBMS packet access procedure

The packet access procedure for an MBMS session is initiated by the mobile station on PCCCH, as specified in sub-clauses 7.1.2.1 with access type "Single block MBMS access" indicated in the PACKET CHANNEL REQUEST message.

7.7.1.2.1 On receipt of a PACKET CHANNEL REQUEST message

On receipt of a PACKET CHANNEL REQUEST message with access type indicating "Single block MBMS access", the network may either allocate one radio block on an uplink PDCH, as specified in sub-clause 7.1.2.1 or, if uplink resources are not available, reject the access request by sending a PACKET ACCESS REJECT message (see sub-clause 7.7.1.2.3).

– Power Control Parameters with timeslot allocation;

– Frequency parameters;

– TBF_STARTING_TIME indicating the frame number of the allocated block;

– TIMING_ADVANCE_VALUE;

– Packet Request Reference.

7.7.1.2.2 On receipt of a PACKET UPLINK ASSIGNMENT message

When receiving a PACKET UPLINK ASSIGNMENT message, corresponding to one of its 3 last PACKET CHANNEL REQUEST messages, the mobile station shall send the MBMS SERVICE REQUEST message in the allocated radio block on the assigned PDCH and then start timer T3214.While timer T3214 is running the mobile station shall accept reception of repeated PACKET UPLINK ASSIGNMENT messages, on any PAGCH on the same PCCCH on which the mobile station has sent the PACKET CHANNEL REQUEST message, and re-send the MBMS SERVICE REQUEST in the allocated block on the assigned PDCH and restart the timer T3214.

At expiry of timer T3214, a mobile station in packet idle mode or MAC-Idle state shall return to DRX mode. No radio bearer will be established in the cell for the concerned MBMS session. A mobile station in broadcast/multicast receive mode shall remain in broadcast/multicast receive mode.

7.7.1.2.3 On receipt of a PACKET ACCESS REJECT message

The network may send a PACKET ACCESS REJECT message to the mobile station in response to a PACKET CHANNEL REQUEST message. The mobile station shall then react as described in sub-clause 7.1.2.2.4.

7.7.1.2.4 On receipt of an MBMS ASSIGNMENT message

When the mobile station receives an MBMS ASSIGNMENT message for an MBMS session, it shall stop any ongoing packet access procedure for that MBMS session and proceed according to sub-clause 7.7.2.2.

7.7.1.2.5 Abnormal cases

If the mobile station receives a PACKET UPLINK ASSIGNMENT message that contains faulty parameters, the mobile station shall abort the MBMS packet access procedure.

7.7.1.3 MBMS packet access procedure on CCCH

For a description of the procedure, see 3GPP TS 44.018.

7.7.1.4 MBMS packet access procedure on MPRACH

7.7.1.4.1 Initiation of the MBMS packet access procedure on MPRACH

The mobile station initiates the MBMS packet access procedure on MPRACH by sending an MPRACH PACKET CHANNEL REQUEST message (see sub-clause 11.2.5c) with access type "Single block MBMS access" on the MPRACH.

The mobile station shall determine the control parameters from the MPRACH control parameters included in the MBMS notification or in the MBMS NEIGHBOURING CELL INFORMATION message transmitted in the old serving cell, if present. If an MPRACH control parameter is not available, the last received corresponding control parameter for the PRACH, if PCCCH is present, shall be used; otherwise the last received corresponding control parameter for the RACH shall be used.

At sending of the first MPRACH PACKET CHANNEL REQUEST message, the mobile station shall store the value for the Retry (R) bit to be transmitted in all the subsequent MAC headers as ‘MS sent channel request message once’. If a second MPRACH PACKET CHANNEL REQUEST message is sent, the mobile station shall change the value for the Retry (R) bit to ‘MS sent channel request message twice or more’.

While waiting for a response to the MPRACH PACKET CHANNEL REQUEST message the mobile station shall continue to monitor the CCCH/PCCCH (whichever is applicable) corresponding to its CCCH_GROUP/PCCCH_GROUP. The mobile station shall perform signal strength measurements as they are defined for packet idle mode, see 3GPP TS 45.008.

7.7.1.4.1.1 Access persistence control on MPRACH

The mobile station shall make maximally M + 1 attempts to send an MPRACH PACKET CHANNEL REQUEST message.

The mobile station shall use the control parameters determined by the procedure described in sub-clause 7.7.1.4.1:

– MAX_RETRANS;

– PERSISTENCE_LEVEL, which consists of the PERSISTENCE_LEVEL P Î {0, 1, …14, 16}. If the control parameters do not contain the PERSISTENCE_LEVEL parameter, this shall be interpreted as if P = 0;

– S;

– TX_INT.

The mobile station shall start timer T3186 at the beginning of the MPRACH packet access procedure. At expiry of timer T3186, the MPRACH packet access procedure shall be aborted, and:

– if at least one MPRACH PACKET CHANNEL REQUEST message was transmitted by the mobile station, a random access failure shall be indicated to upper layers and the mobile station shall perform autonomous cell re-selection according to 3GPP TS 43.022;

– otherwise, a packet access failure shall be indicated to upper layers and the mobile station shall return to packet idle mode or MAC-Idle state.

The first attempt to send an MPRACH PACKET CHANNEL REQUEST message may be initiated at the first available MPRACH block on the indicated PDCH. The mobile station shall choose one of the four TDMA frames within the selected MPRACH block randomly with a uniform probability distribution.

For each attempt, the mobile station shall draw a random value R with uniform probability distribution in the set {0, 1, …, 15}. The mobile station is allowed to transmit an MPRACH PACKET CHANNEL REQUEST message if P is less than or equal to R.

After each attempt, the S and T parameters are used to determine the next TDMA frame in which it may be allowed to make a successive attempt. The number of TDMA frames, belonging to the MPRACH on the indicated PDCH, between two successive attempts to send an MPRACH PACKET CHANNEL REQUEST message, excluding the TDMA frames potentially containing the messages themselves, is a random value drawn for each transmission, with uniform probability distribution, in the set {S, S + 1, …, S + T ‑ 1};

Here:

M is the value of the parameter MAX_RETRANS;

T is the value of the parameter TX_INT;

S is the value of the parameter S.

Having made M + 1 attempts to send an MPRACH PACKET CHANNEL REQUEST message, the mobile station shall stop timer T3186 and start timer T3170 if at least one MPRACH PACKET CHANNEL REQUEST message was transmitted by the mobile station. In this case, at expiry of timer T3170, the packet access procedure shall be aborted, a random access failure shall be indicated to upper layers and the mobile station shall perform autonomous cell re-selection according to 3GPP TS 43.022. Otherwise, the packet access procedure shall be aborted, a packet access failure shall be indicated to upper layers and the mobile station shall return to packet idle mode or MAC-Idle state.

If the mobile station receives a PACKET DOWNLINK ASSIGNMENT message while it is waiting for a response to an MPRACH PACKET CHANNEL REQUEST message, it shall abort the MBMS packet access procedure on MPRACH and respond to the PACKET DOWNLINK ASSIGNMENT message (see sub-clause 7.2.1).

7.7.1.4.2 On receipt of an MPRACH PACKET CHANNEL REQUEST

On receipt of an MPRACH PACKET CHANNEL REQUEST message with access type indicating "Single block MBMS access", the network shall either allocate one radio block on an uplink PDCH by sending a PACKET UPLINK ASSIGNMENT message on the downlink PDCH corresponding to the uplink PDCH where the MPRACH is allocated or, if uplink resources are not available, reject the access request by sending a PACKET ACCESS REJECT message on the same downlink PDCH (see sub-clause 7.7.1.4.3).

The PACKET UPLINK ASSIGNMENT message shall include the optional parameters:

– Power Control Parameters with timeslot allocation;

– Frequency parameters;

– TBF_STARTING_TIME indicating the frame number of the allocated block;

– TIMING_ADVANCE_VALUE;

– Packet Request Reference.

7.7.1.4.3 On receipt of a PACKET ACCESS REJECT message

The network may, as response to an MPRACH PACKET CHANNEL REQUEST message, send to the mobile station a PACKET ACCESS REJECT message on the downlink PDCH corresponding to the uplink PDCH where the MPRACH is allocated. This message contains the request reference with time of reception of the MPRACH PACKET CHANNEL REQUEST message and optionally a WAIT_INDICATION field in the Reject structure of the PACKET ACCESS REJECT message.

– The mobile station shall stop timer T3186, stop sending MPRACH PACKET CHANNEL REQUEST messages, start timer T3172 with the value indicated in the WAIT_INDICATION field, start timer T3170 if it has not already been started and listen to the downlink PCCCH until timer T3170 expires. During this time, the mobile station shall ignore additional PACKET ACCESS REJECT messages. During this time, on reception of any PACKET UPLINK ASSIGNMENT message corresponding to any other of its 3 last MPRACH PACKET CHANNEL REQUEST messages, the mobile station shall stop timers T3170 and T3172 if running, and follow the procedure defined in sub-clause 7.1.2.2.1b;

– If no PACKET UPLINK ASSIGNMENT message is received before expiration of timer T3170, the mobile station shall indicate a packet access failure to upper layer and return to packet idle mode (listening to its paging channel). As an option the mobile station may stop timer T3170, indicate a packet access failure to upper layer and return to packet 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 MPRACH PACKET CHANNEL REQUEST messages. If the mobile station is already engaged in a parallel broadcast/multicast session the mobile station shall remain in broadcast/multicast receive mode;

– If the mobile station receives a PACKET DOWNLINK ASSIGNMENT message, it shall stop timer T3170 if running and respond to the PACKET DOWNLINK ASSIGNMENT message (see sub-clause 7.2.1);

– The value of the WAIT_INDICATION field (i.e. timer T3172) relates to the cell from which it was received.

7.7.1.4.4 On receipt of a PACKET UPLINK ASSIGNMENT message

On receipt of a PACKET UPLINK ASSIGNMENT message corresponding to one of its 3 last MPRACH PACKET CHANNEL REQUEST messages the mobile station shall stop timers T3186 and T3170 if running and stop sending MPRACH PACKET CHANNEL REQUEST messages. The mobile station shall send the MBMS SERVICE REQUEST message in the allocated radio block on the assigned PDCH and then start timer T3214. While timer T3214 is running the mobile station shall accept reception of repeated PACKET UPLINK ASSIGNMENT messages, on the downlink PDCH corresponding to the uplink PDCH where the MPRACH is allocated, and re-send the MBMS SERVICE REQUEST in the allocated block on the assigned PDCH and restart the timer T3214.

At expiry of timer T3214, a mobile station in packet idle mode or MAC-Idle state shall return to DRX mode and shall consider the MBMS radio bearer as not established in the cell for the concerned MBMS session. A mobile station in broadcast/multicast receive mode shall remain in broadcast/multicast receive mode.

7.7.1.4.5 On receipt of an MBMS ASSIGNMENT message

When the mobile station receives an MBMS ASSIGNMENT message for an MBMS session, it shall stop any ongoing packet access procedure for that MBMS session and proceed according to sub-clause 7.7.2.2.

7.7.2 Establishment of MBMS bearer

7.7.2.1 General

The network may send an MBMS ASSIGNMENT message to the mobile station(s) in order to inform about the establishment of a radio bearer for an MBMS session in the cell or to notify the mobile station(s) that a radio bearer for that MBMS session is not established in the cell. The decision of whether to establish a radio bearer for an MBMS session in a cell is a network dependent choice.

If the network sends the MBMS ASSIGNMENT message subsequent to an MBMS Notification for the same MBMS session, the MBMS ASSIGNMENT message shall be sent on any PAGCH on the same PCCCH on which the network has sent the MBMS Notification or, if a packet control channel does not exist, the IMMEDIATE ASSIGNMENT message including the Multiple Blocks Packet Downlink Assignment construction shall be sent on any AGCH on the same CCCH on which the network has sent the MBMS Notification, followed by the MBMS ASSIGNMENT message sent on the PDCH specified by the Packet Channel Description IE in the IMMEDIATE ASSIGNMENT message (see 3GPP TS 44.018).

In case the network sends the MBMS ASSIGNMENT message in response to an MBMS SERVICE REQUEST message which is not sent as a response to an MBMS Notification, the MBMS ASSIGNMENT message shall be sent either:

– on the PCCCH corresponding to the mobile station PCCCH_GROUP, if the mobile station initiated the MBMS packet access procedure on the MPRACH, or

– on any PAGCH on the same PCCCH on which the mobile station sent the PACKET CHANNEL REQUEST message with access type "Single block MBMS access" or,

– if a packet control channel does not exist, the IMMEDIATE ASSIGNMENT message including the Multiple Blocks Packet Downlink Assignment construction shall be sent on the CCCH corresponding to the mobile station CCCH_GROUP, if the mobile station initiated the MBMS packet access procedure on the MPRACH, or on any AGCH on the same CCCH on which the mobile station sent the CHANNEL REQUEST message with access type "Single block MBMS access", followed by the MBMS ASSIGNMENT message sent on the PDCH specified by the Packet Channel Description IE in the IMMEDIATE ASSIGNMENT message (see 3GPP TS 44.018).

7.7.2.2 On receipt of an MBMS ASSIGNMENT message

On reception of the MBMS ASSIGNMENT message the mobile station shall stop timer T3214 if running and enters broadcast/multicast receive mode.

If the MBMS ASSIGNMENT message indicates that a radio bearer is established for the MBMS session in the cell, and thus contains an MBMS bearer description, the mobile station shall set and start the session duration timer for this MBMS session with a value equal to the Estimated Session Duration and shall listen to downlink RLC blocks identified by the assigned MBMS Bearer Identity value on the defined PDCHs. The network may assign a radio resource on one or more PDCHs to be used for the radio bearer. The amount of radio resource to be reserved is a network dependent choice and shall not exceed the multislot capability of an MBMS capable mobile station (see 3GPP TS 45.002). The MBMS In-band Signalling Indicator information element included in the MBMS ASSIGNMENT message indicates whether or not the network shall send system information messages and (for mobile stations with an assigned MS_ID on that MBMS radio bearer) paging messages on the PACCH of the MBMS radio bearer.

The MBMS bearer description may indicate an MBMS radio bearer starting time. If the mobile station receives the MBMS ASSIGNMENT message before the MBMS radio bearer starting time has expired, it shall wait until the point in time denoted by the MBMS radio bearer starting time, leave non-DRX mode, switch to the assigned PDCHs and start timer T3190. If the mobile station receives the MBMS ASSIGNMENT message after the MBMS radio bearer starting time has expired, it shall ignore the indicated MBMS radio bearer starting time, leave non-DRX mode, immediately switch to the assigned PDCHs and start timer T3190. If the mobile station receives an MBMS ASSIGNMENT message including an MBMS bearer description without an MBMS radio bearer starting time, it shall leave non-DRX mode, immediately switch to the assigned PDCHs and start timer T3190. The timer T3190 is restarted when receiving the first valid RLC data block including the assigned MBMS Bearer Identity. On expiry of timer T3190, the mobile station shall abort the procedure and repeat the MBMS packet access procedure for the MBMS session.

If the mobile station receives more than one MBMS ASSIGNMENT message while it monitors the PCCCH or, if a packet control channel does not exist, the CCCH (see 3GPP TS 44.018), it shall act upon the most recently received message and shall ignore the previous message.

If the MBMS ASSIGNMENT message indicates that no radio bearer is established for the MBMS session in the cell, the mobile station shall act according to the indication in the Reject cause.

– If the cause value indicates that further MBMS packet accesses are allowed for this MBMS session in the same cell, as long as the session duration timer for this MBMS session in the mobile station is still running, the mobile station may perform more access attempts for the current MBMS session in this cell or in any other cell where MBMS is supported by the network;

– If the cause value indicates that no further MBMS packet accesses are allowed for this MBMS session in the same cell, the mobile station shall not perform any further access attempts for the current MBMS session in this cell. As long as the session duration timer for this MBMS session in the mobile station is still running, the mobile station may perform access attempts for the MBMS session in any other cell to which the mobile station has performed cell reselection, if MBMS is supported by the network in that cell;

– If the cause value indicates that no further MBMS packet accesses are allowed for this MBMS session in the same Routing Area, the mobile station shall not perform any further access attempts for the current MBMS session in this Routing Area. As long as the session duration timer for this MBMS session in the mobile station is still running, the mobile station may perform access attempts for the MBMS session in any other cell, in any other Routing Area, to which the mobile station has performed cell reselection, if MBMS is supported by the network in that cell;

– If the cause value indicates that no further MBMS packet accesses are allowed for this MBMS session in this PLMN, the mobile station shall not perform any further access attempts for the MBMS session.

When the session duration timer for the MBMS session in the mobile station expires, the mobile station shall no longer perform access attempts for that MBMS session in any cell and shall indicate to the upper layers the end of the MBMS session.

Independent on the Reject cause value received and on the expiry of the session duration timer for the MBMS session, the mobile station may always perform new MBMS packet accesses for the MBMS session if a new MBMS Notification addressing that MBMS session, and indicating that counting shall be performed, is received.

In case the network sends the MBMS ASSIGNMENT message in response to an MBMS SERVICE REQUEST message which is not sent as a response to an MBMS Notification, and the MBMS ASSIGNMENT message contains the MBMS bearer description and an uplink feedback channel is used, then the network may include the TLLI of the mobile station, the MS_ID and the timing advance parameters in the MBMS ASSIGNMENT message. If no MS_ID identifier is available on the network side, the network notifies the mobile station of the lack of an MS_ID identifier, preventing the mobile station from repeating the MBMS packet access procedure in this cell.

7.7.2.3 Abnormal cases

If on the mobile station side timer T3214 expires indicating that no MBMS bearer will be established for the specific MBMS session in the cell or if the MBMS ASSIGNMENT message contains faulty parameters, the mobile station shall abort the MBMS packet access procedure.

7.7.2.4 MBMS address assignment procedure

In case an uplink feedback channel is associated to an established MBMS radio bearer, then the network may assign an MS_ID to a given mobile station receiving this MBMS radio bearer by sending an MBMS MS_ID ASSIGNMENT message including the MS_ID and the timing advance parameters assigned to the mobile station. The mobile station shall be addressed by its TLLI. This message shall not be sent before the point in time denoted by the MBMS radio bearer starting time, if present in the previous MBMS ASSIGNMENT message.

On a given PDCH a mobile station having been assigned an MS_ID is identified with a TFI value including the MBMS Bearer Identity (in the most significant bit(s) of the TFI field) and the MS_ID (in the remaining least significant bit(s) of the TFI field).

The mobile station shall respond with a PACKET CONTROL ACKNOWLEDGEMENT message in the uplink radio block specified if a valid RRBP field is received as part of the MBMS MS_ID ASSIGNMENT message. The network shall reset counter N3109 for that MS_ID on that MBMS radio bearer when transmitting for the first time the MBMS MS_ID ASSIGNMENT message including a polling request. If the network does not receive the PACKET CONTROL ACKNOWLEDGEMENT message in the specified radio block, it shall increment counter N3109 for that MS_ID and may retransmit the MBMS MS_ID ASSIGNMENT message. If N3109 = N3109_MAX, the network shall start timer T3199 for that MS_ID. While T3199 is running for a given MS_ID and MBMS radio bearer, the network shall not use that MS_ID in any RLC/MAC block belonging to that MBMS radio bearer. When timer T3199 expires, the network may reuse the corresponding MS_ID value for that MBMS radio bearer.

An initial timing advance value may be provided in the MBMS ASSIGNMENT message or in the MBMS MS_ID ASSIGNMENT message in the Packet Timing Advance IE. Thereafter either the timing advance is updated with a PACKET POWER CONTROL/TIMING ADVANCE message or the continuous timing advance procedure is used. If timing advance timeslot number and index are provided in the MBMS ASSIGNMENT message or in the MBMS MS_ID ASSIGNMENT message, the mobile station shall use the continuous timing advance procedure, using its allocation on PTCCH (see 3GPP TS 45.010). Otherwise, the continuous timing advance procedure shall not be used. For the case where the timing advance value is not provided in the MBMS ASSIGNMENT message or in the MBMS MS_ID ASSIGNMENT message, the mobile station is not allowed to send normal bursts (e.g. (EGPRS) PACKET DOWNLINK ACK/NACK message) on the uplink until it has received a valid timing advance either through the continuous timing advance procedure or in a PACKET POWER CONTROL/TIMING ADVANCE message.

If the mobile station has been assigned an MS_ID in the MBMS ASSIGNMENT message before the point in time denoted by the MBMS radio bearer starting time, if present in the MBMS ASSIGNMENT message, the mobile station shall switch to the assigned PDCH(s) at the point in time denoted by the MBMS radio bearer starting time and start timers T3190 and T3290. If the MBMS radio bearer starting time has already expired or has not been included in the MBMS ASSIGNMENT message including the MS_ID, the mobile station shall switch to the assigned PDCH(s) within the reaction time defined in 3GPP TS 45.010 and start timers T3190 and T3290. If the mobile station is assigned an MS_ID in the MBMS MS_ID ASSIGNMENT message, the mobile station shall start timer T3290 within the reaction time defined in 3GPP TS 45.010. The mobile station shall restart timer T3190 whenever receiving an RLC/MAC block including the assigned MBMS Bearer Identity. In EGPRS TBF mode T3190 is also restarted when receiving an erroneous RLC data block for which the header is correctly received and which addresses the mobile station. The mobile station with an assigned MS_ID value shall restart timer T3290 whenever receiving an RLC/MAC block including the corresponding MBMS Bearer Identity and the MS_ID in the TFI field.

7.7.3 MBMS Neighbour Cell Information Distribution

The network shall indicate in GPRS Cell Options IE whether it supports the distribution of MBMS NEIGHBOURING CELL INFORMATION messages (see sub-clause 12.24).

The network may send MBMS neighbour cell information to a mobile station during MBMS reception using the MBMS NEIGHBOURING CELL INFORMATION message on the PACCH. A mobile station, which receives this information, shall store the MBMS data channel information until refreshing or until the end of the MBMS session. During that period the information can be used for fast resumption of the MBMS reception in the neighbour cell (see sub-clause 8.1.6.2).

The MS shall only combine information received in several instances of the MBMS NEIGHBOURING CELL INFORMATION messages that have the same value of the MBMS_PTM_CHANGE_MARK specified for a neighbouring cell.

In case the target cell has PBCCH allocated, this information shall be included in the MBMS NEIGHBOURING CELL INFORMATION message, if the PBCCH parameters can be encoded via the means provided in the message. If present, the MS shall use this information in order to avoid BCCH decoding, if not otherwise necessary unless the PBCCH location is known via PSI3 and PSI3bis messages, in the target cell.

In case in the target cell an MPRACH is allocated on the uplink feedback channel of an MBMS radio bearer, this information shall be included in the MBMS NEIGHBOURING CELL INFORMATION message.