5 Introduction to the Medium Access Control (MAC) procedures

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

5.1 General

The Medium Access Control procedures include the functions related to the management of the shared transmission resources, e.g. the packet data physical channels and the radio link connections on packet data physical channels.

The Medium Access Control procedures support the provision of Temporary Block Flows (TBFs) that allow the point-to-point transfer of signalling and user data within a cell between the network and a mobile station. The MAC procedures also support the provision of MBMS radio bearers that allow the point-to-multipoint transfer of signalling and user data within a cell between the network and one (or more) mobile station(s).

Moreover, the Medium Access Control procedures include the procedures for reception of PBCCH and PCCCH, which permits autonomous cell reselection performed by the mobile station (see 3GPP TS 45.008).

5.2 Multiplexing principles

5.2.1 Temporary Block Flow

A Temporary Block Flow (TBF) is a physical connection used by the two RR entities to support the unidirectional transfer of upper layer PDUs on packet data physical channels.

The TBF is allocated radio resources on one or more assigned PDCHs and comprises a number of RLC/MAC blocks carrying one or more upper layer PDUs. If Downlink Dual Carrier is supported by both the mobile station and the network, the assigned PDCHs for a given TBF may be on one or two radio frequency channels. If Downlink Multi Carrier is supported by both the mobile station and the network and a DLMC configuration is used, the assigned PDCHs for the downlink TBF shall be on two or more radio frequency channels and the assigned PDCHs for the uplink TBF (if assigned) may be on one or more radio frequency channels. The maximum number of radio frequency channels the PDCHs can be assigned on is indicated by the maximum number of downlink carriers a DLMC capable MS supports, see 3GPP TS 24.008. A TBF is temporary and is maintained only for the duration of the data transfer (i.e. until there are no more RLC/MAC blocks to be transmitted and, in RLC acknowledged mode, all of the transmitted RLC/MAC blocks have been successfully acknowledged by the receiving entity).

A TBF may operate in either GPRS TBF mode, EGPRS TBF mode or EC TBF mode. For Downlink Dual Carrier and DLMC configurations TBFs shall operate in EGPRS TBF mode. A TBF assigned in IMMEDIATE PACKET ASSIGNMENT message shall operate in EGPRS TBF mode. The network sets the TBF mode in the PACKET UPLINK ASSIGNMENT, MULTIPLE TBF UPLINK ASSIGNMENT, PACKET DOWNLINK ASSIGNMENT, MULTIPLE TBF DOWNLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE, MULTIPLE TBF TIMESLOT RECONFIGURE, IMMEDIATE ASSIGNMENT or PACKET CS RELEASE INDICATION message, unless the TBF is assigned in EC TBF mode. The EGPRS TBF mode is only supported by EGPRS capable MSs. A TBF in EC TBF mode is assigned in an EC IMMEDIATE ASSIGNMENT, EC PACKET UPLINK ASSIGNMENT or EC PACKET DOWNLINK ASSIGNMENT message.

If a mobile station is assigned concurrent TBFs, these shall be in the same TBF mode. Concurrent TBFs either in same direction or opposite direction are not supported in EC operation.

A TBF in EGPRS mode operates using one of four groups of modulation and coding schemes:

– EGPRS-GMSK only (applicable to uplink TBFs only): this comprises MCS-1 to MCS-4

– EGPRS: this comprises MCS-1 to MCS-9

– EGPRS2-A: for uplink TBFs, this comprises MCS-1 to MCS-6 and UAS-7 to UAS-11; for downlink TBFs, this comprises MCS-1 to MCS-4, MCS-6 (only for retransmissions of blocks originally transmitted using EGPRS), MCS-7, MCS-8 and DAS-5 to DAS-12

– EGPRS2-B: for uplink TBFs, this comprises MCS-1 to MCS-4 and UBS-5 to UBS-12; for downlink TBFs, this comprises MCS-1 to MCS-4, MCS-6 to MCS-9, DAS-5, DAS-6, DAS-8, DAS-9, DAS-11 and DBS-5 to DBS-12.

The group of modulation and coding schemes to be used on a PDTCH associated with a TBF is indicated in the assignment message. The EGPRS-GMSK only group applies if the aggregate timeslot allocation is not within the indicated EGPRS multislot class, but is within the indicated GPRS multislot class.

The use of the EGPRS2-A group for uplink or downlink is only supported by MSs which are capable of EGPRS2-A or EGPRS2-B in that direction. The EGPRS2-B group is only supported by MSs which are capable of EGPRS2-B in that direction. If a mobile station supports EGPRS2, the same group of modulation and coding schemes shall be used for all TBFs in a given direction.

A TBF in EC TBF mode operates using one of two groups of modulation and coding schemes (both applicable to both uplink and downlink TBFs):

– EGPRS-GMSK only: this comprises MCS-1 to MCS-4

– EGPRS: this comprises MCS-1 to MCS-9

If a mobile station indicates support of Reduced Latency (see 3GPP TS 24.008), it may be assigned TBFs with FANR activated (see sub-clause 9.1.14), either in BTTI configuration, RTTI configuration or (if the mobile additionally supports MTTI configurations) MTTI configuration. If a mobile station indicates support of FANR (see 3GPP TS 24.008), it may be assigned TBFs with FANR activated (see sub-clause 9.1.14) in BTTI configuration only. The network shall ensure that, if a mobile station is assigned a TBF with FANR activated, FANR shall be activated for all concurrent TBFs assigned to that mobile station.

For the case where a mobile station supports multiple TBF procedures the maximum number of TBFs it can support concurrently is not specified. Mobile station implementations are expected to ensure that the mobile station can support a sufficient number of TBFs to operate all the PDP contexts it has activated. As such, a mobile station may choose to release, modify or activate one or more PDP contexts when prioritizing the services it wants to operate concurrently. The network is not required to consider any potential complexity limitations regarding the number of concurrent TBFs when establishing an uplink or downlink TBF for a mobile station that supports multiple TBF procedures.

The following messages are used only if both the mobile station and the network support multiple TBF procedures:

– MULTIPLE TBF UPLINK ASSIGNMENT

– MULTIPLE TBF DOWNLINK ASSIGNMENT

– MULTIPLE TBF TIMESLOT RECONFIGURE.

5.2.2 Temporary Flow Identity

Each TBF is assigned a Temporary Flow Identity (TFI) by the network. The mobile station shall assume that the TFI value is unique among concurrent TBFs in the same direction (uplink or downlink) on all PDCHs used for the TBF. In (E)GPRS, the same TFI value may be used concurrently for TBFs on other PDCHs in the same direction and for TBFs in the opposite direction. In EC-GSM-IoT the same TFI value may be used for EC TBFs on different PDCHs in the same direction and for EC TBFs in opposite direction. In EC operation a mobile station shall only support one ongoing EC TBF. For a TBF with FANR activated, the TFI value shall be unique among concurrent TBFs assigned to one mobile station in the same direction (uplink or downlink). If Enhanced Multiplexing for Single TBF (EMST) is used, the network shall assign, according to the rules above, a unique TFI value to each RLC entity multiplexed on the TBF. If Enhanced Multiplexing for Single RLC Entity (EMSR) is supported by a mobile station the network may allocate multiple PFCs on a common RLC entity where at least two of these PFCs are allocated a unique TFI value (see sub-clause 5.12). The downlink TBF of a mobile station in a DLMC configuration may be assigned an eTFI if the maximum number of downlink timeslots the mobile supports is greater than 20. The eTFI supplements the TFI so that combined they uniquely identify the downlink TBF on all of the PDCH resources allocated for that TBF on a given downlink carrier. The TBF may be assigned different eTFI – TFI combinations for each downlink carrier used in a given DLMC configuration. If a mobile station receives an RLC/MAC control block which includes a downlink TFI equal to a TFI supported by a downlink TBF assigned to the mobile station, which is received on a timeslot or PDCH-pair which is not a timeslot or PDCH-pair which is assigned to the mobile station as part of that TBF, the mobile station shall consider that message as not addressed to it. If a mobile station receives an RLC/MAC control block which includes an uplink TFI equal to a TFI supported by an uplink TBF assigned to the mobile station, which is received on a timeslot or PDCH-pair which does not correspond to a timeslot or PDCH-pair which is assigned to the mobile station as part of that TBF, the mobile station shall consider that message as not addressed to it.

NOTE: The behaviour of the mobile station in case it receives a control block not addressed to it is specified in sub-clause 10.4.10

An RLC/MAC block associated with a certain TBF shall comprise a TFI. The TBF is identified by the TFI together with, in case of a RLC data block, the direction (uplink or downlink) in which the RLC data block is sent; and in case of a RLC/MAC control message, the direction in which the RLC/MAC control message is sent and the message type. In the case of a DLMC configuration where a downlink TBF is assigned an eTFI on a specific downlink carrier, an RLC/MAC block associated with that TBF on that downlink carrier shall comprise a TFI and an eTFI (see sub-clause 10.0a.2).

Global_TFI is used to unambiguously identify the mobile station in packet transfer mode, MAC-Shared state, dual transfer mode or MAC-DTM state within an uplink or downlink RLC/MAC control message. In the case of a DLMC configuration and a mobile station supporting eTFI, Global_TFI and eTFI may be used to unambiguously identify the mobile station in packet transfer mode within a downlink RLC/MAC control message. If present, the Global TFI addresses the MS using either:

– an uplink TFI identifying an uplink TBF assigned to the MS such that the timeslot or PDCH-pair on which the Global TFI is sent corresponds to a timeslot or PDCH-pair assigned to that TBF, or

– a downlink TFI identifying a downlink TBF assigned to the MS such that the timeslot or PDCH-pair on which the Global TFI is sent is a timeslot or PDCH-pair assigned to that TBF.

If there is a choice of TFI to use, which TFI is used is at the discretion of the sender except where explicitly defined by procedure. For the mobile station in broadcast/multicast receive mode, the Global TFI includes the MBMS Bearer Identity of the MBMS radio bearer the RLC/MAC control message relates to (in the most significant bit(s) of the DOWNLINK_TFI field) and, where explicitly defined by procedure, the current MS_ID of the mobile station the message relates to (in the remaining least significant bit(s) of the DOWNLINK_TFI field).

5.2.3 Uplink State Flag

An Uplink State Flag (USF) is included in the header of each RLC/MAC block on a downlink PDCH, as specified in clause 10. It may be used by the network to control the multiplexing of different mobile stations and TBFs on an uplink PDCH. The use of USF is further specified in 3GPP TS 45.002.

5.2.4 Medium Access modes

Four medium access modes are supported:

– Dynamic Allocation, characterised by that the mobile station detecting an assigned USF value for each assigned uplink PDCH when operating in BTTI configuration or each assigned uplink PDCH-pair when operating in RTTI configuration and block or group of four blocks that it is allowed to transmit on that PDCH/PDCH-pair (see sub-clause 8.1.1.1);

– Extended Dynamic Allocation is characterised by the mobile station detecting an assigned USF value for any assigned uplink PDCH when operating in BTTI configuration or any assigned uplink PDCH-pair when operating in RTTI configuration, allowing the mobile station to transmit on that PDCH/PDCH-pair and all higher numbered assigned PDCHs/PDCH-pairs in the same block or group of four blocks (see sub-clause 8.1.1.2);

– Exclusive Allocation, characterised by the mobile station being granted the exclusive right to transmit on the assigned PDCH/H for the duration of an uplink TBF (see sub-clause 8.1.1.3a). Exclusive allocation is applicable only in dual transfer mode. When using exclusive allocation, only one TBF shall be established in the uplink.

– Fixed Uplink Allocation, characterised by the mobile station being allocated uplink resources in an (EC-)AGCH assignment message or in an RLC/MAC control message (see sub-clause 8.1.1.3b). Fixed uplink allocation is applicable only in EC TBF mode. The uplink resources are allocated according to the uplink Coverage Class that the mobile station is assigned.

Dynamic Allocation medium access mode shall be supported by all networks that support GPRS. The support of Extended Dynamic Allocation is optional for the network.

Dynamic Allocation shall be supported in all mobile stations, except if the mobile station only supports EC operation in which case only Fixed Uplink Allocation needs to be supported. The support of Extended Dynamic Allocation is mandatory for mobile stations of multislot classes 22, 24, 25 and 27, for multislot class type 1 mobile stations that can transmit on three or more timeslots (either PDCH or TCH), and for mobile stations supporting Flexible Timeslot Assignment (see 3GPP TS 24.008). The support of Extended Dynamic Allocation for other mobile stations is optional and shall be indicated in the MS Radio Access Capability.

NOTE: Flexible Timeslot Assignment is applicable only when Extended Dynamic Allocation is used, or as explicitly indicated for certain RTTI configurations in 3GPP TS 45.002.

The exclusive allocation shall be used in dual transfer mode during uplink operation with a half-rate PDCH.

The network shall ensure that the medium access mode and the resource allocation used for a mobile station are compatible with the permitted multislot configurations (see 3GPP TS 45.002).

5.2.4a Multiplexing of GPRS, EGPRS and EGPRS2 capable mobile stations

GPRS, EGPRS, EGPRS2 and EC GSM-IoT capable mobile stations can be multiplexed dynamically on the same PDCH.

If dynamic or extended dynamic allocation is used, a mobile station shall be able to decode the USF that allocates the uplink to that mobile station as follows,

– For a mobile station supporting only GPRS the network shall use GMSK modulation, i.e. either CS-1 to CS-4 or ,MCS-0, MCS-1 to MCS-4, in those blocks. The other blocks may use other modulations.

– For a mobile station supporting EGPRS, the network may use either GMSK modulation or 8-PSK modulation, i.e. CS-1 to CS-4, MCS-0, MCS-1 to MCS-4, MCS-5 to MCS-9 or DAS-5 to DAS-7 in those blocks.

– For a mobile station supporting EGPRS2-A in the downlink, the network may use either GMSK, 8-PSK, 16-QAM or 32-QAM modulation with normal symbol rate, i.e. CS-1 to CS-4, MCS-0, MCS-1 to MCS-9 or DAS-5 to DAS-12 in those blocks.

– For a mobile station supporting EGPRS2-B in the downlink, the network may use GMSK, 8-PSK, 16-QAM and 32-QAM modulations with normal symbol rate, or QPSK, 16-QAM or 32-QAM modulations with higher symbol rate in those blocks, i.e. CS-1 to CS-4, MCS-0, MCS-1 to MCS-9, DAS-5 to DAS-12 or DBS-5 to DBS-12.

– For a mobile station supporting eTFI, the network may use CS-1 for RLC/MAC control blocks irrespective of whether or not the RLC/MAC control blocks are associated with a TBF assigned an eTFI (see sub-clause 5.2.2, 8.1.1.1.1 and 8.1.1.2.2).

One exception to the list above is for mobile stations not supporting eTFI where the network shall not use RLC/MAC control blocks associated with a TBF assigned an eTFI.

If Fixed Uplink Allocation is used, the mobile station does not decode any USF for uplink allocation. The USF shall however be included in downlink RLC blocks sent to a mobile station in EC operation in case another mobile station using dynamic or extended dynamic allocation is monitoring the same downlink channel.

A mobile station assigned an uplink TBF using FANR shall be able to decode the PAN in a downlink block. If the PAN is addressed to a mobile station other than the one to which the data in the RLC/MAC block is addressed, then the network may use in this block any of the modulation and coding schemes allowed for USF transmission to that mobile station. One exception applies for a mobile station not supporting eTFI in which case the network shall not address the PAN to that mobile station if the RLC/MAC block is associated with a TBF assigned an eTFI (see sub-clause 8.1.2.1) unless the assigned eTFI field equals ‘000’. For a mobile station supporting eTFI (see sub-clause 5.2.2) the network may address the PAN to that mobile station irrespective of whether or not the RLC/MAC block is associated with a TBF assigned an eTFI.

NOTE 1: The stealing bits in the EGPRS GMSK blocks are set to indicate CS-4. The coding and interleaving of the USF is done as defined for CS-4. That leads to:

1) A GPRS mobile station is able to detect the USF in EGPRS GMSK blocks. The risk that the rest of the block will be misinterpreted as valid information is low;

2) An EGPRS mobile station cannot differentiate CS-4 blocks from EGPRS GMSK blocks by decoding the stealing bits only. However, an EGPRS mobile station in EGPRS TBF mode needs only to decode GMSK blocks assuming either of MCS-1 to MCS-4, in order to determine if they were aimed for it.

NOTE 2: Due to mobile station synchronisation reasons, special requirements apply for the scheduling, the modulation and coding scheme and the output power of blocks that are transmitted to a mobile station with an active uplink or downlink TBF, see 3GPP TS 45.008.

A mobile station shall only attempt to decode USF or PAN in a downlink radio block transmitted using a TSC it has been assigned. A mobile station that supports the extended TSC sets (see 3GPP TS 45.002 [32]) can have up to two TSCs assigned for a given PDCH and shall attempt to decode USF or PAN in a downlink radio block it receives on that PDCH using its assigned TSC(s).

5.3 Packet idle mode

In packet idle mode no temporary block flow (TBF) exists.

In packet idle mode, the mobile station monitors the relevant paging subchannels on PCCCH, if such is present in the cell. If a PCCCH is not present in the cell, the mobile station monitors the relevant paging subchannels on CCCH or, if the mobile station has enabled EC operation, on EC-CCCH.

In packet idle mode, upper layers may require the transfer of an upper layer PDU, which implicitly triggers the establishment of a TBF and the transition to packet transfer mode.

In packet idle mode, upper layers may require the establishment of an RR connection. When the mobile station enters dedicated mode (see 3GPP TS 44.018), it may leave the packet idle mode, if the mobile station limitations make it unable to handle the RR connection and the procedures in packet idle mode simultaneously. A mobile station that has enabled PEO may use mobile originated RR connection establishment for GSM services (see 3GPP TS 23.060 [19]) while in packet idle mode. If it establishes a RR connection then it shall leave the packet idle mode and shall only re-enter packet idle mode when the RR connection is released.

In packet idle mode, if a mobile station starts listening to an MBMS radio bearer, it shall enter broadcast/multicast receive mode (see sub-clause 5.3.1).

5.3.1 Broadcast/multicast receive mode

In broadcast/multicast receive mode, the mobile station listens to an MBMS radio bearer.

Broadcast/multicast receive mode can only be entered by a mobile station when in packet idle mode; when leaving broadcast/multicast receive mode, the mobile station shall return to packet idle mode.

Whenever a mobile station leaves broadcast/multicast receive mode to enter packet transfer mode, upon returning to packet idle mode it may re-enter broadcast/multicast receive mode to resume the reception of the ongoing MBMS session(s).

The mobile station receives the system information and paging messages on the (P)BCCH and (P)CCCH as specified for packet idle mode or on the PACCH/D associated with the MBMS radio bearer, depending on the value of the MBMS In-band Signalling Indicator information element included in the MBMS ASSIGNMENT and MBMS NEIGHBOURING CELL INFORMATION messages.

If the use of in-band signalling has been indicated (by the MBMS In-band Signalling Indicator), only mobile stations that have an MS_ID on the MBMS radio bearer shall be addressed with paging messages on the PACCH/D of that MBMS radio bearer. Mobile stations without an MS_ID shall continue monitoring their paging groups on the paging channel(s) on the (P)CCCH and skip the reception of the radio blocks of the MBMS radio bearer that prevent the monitoring of their paging groups, if needed. In this specification, requirements for mobile stations in packet idle mode apply also to mobile stations in broadcast/multicast receive mode unless stated otherwise.

5.4 Packet transfer mode

In packet transfer mode, the mobile station is allocated radio resources providing one or more TBFs for physical point-to-point connection(s) on one or more packet data physical channels for the unidirectional transfer of upper layer PDUs between the network and the mobile station. Successive transfer of one or more upper layer PDUs is possible. Concurrent TBFs may be established in opposite directions, unless the mobile station is in EC operation. The RR sublayer provides the following services:

– transfer of upper layer PDUs in RLC acknowledged mode;

– transfer of upper layer PDUs in RLC unacknowledged mode;

– transfer of upper layer PDUs in RLC non-persistent mode.

Only RLC acknowledged mode is supported for an EC TBF.

When a transfer of upper layer PDUs terminates, in either downlink or uplink direction, the corresponding TBF is released. In packet transfer mode, when all TBFs have been released, in downlink and uplink direction, the mobile station returns to packet idle mode.

In packet transfer mode, upper layers may require the establishment of an RR connection. When the mobile station enters dedicated mode (see 3GPP TS 44.018), it may abort all ongoing TBFs and leave the packet transfer mode, if the mobile station limitations make it unable to handle the RR connection and the procedures in packet transfer mode simultaneously. A MS that has enabled PEO may use mobile originated RR connection establishment for GSM services (see 3GPP TS 23.060 [19]) while in packet transfer mode in which case it shall abort the ongoing TBFs, leave packet transfer mode and enter packet idle mode when the RR connection is released.

In packet transfer mode, a mobile station that supports PS handover may be ordered to move to a new cell through the use of a PS HANDOVER COMMAND message that provides resources to be used for one or more of its ongoing TBFs in the new cell (e.g. TBF resources in the new cell that have been pre-allocated by the target BSS). A mobile station indicates that it supports PS handover in the PS Handover Capability field/GAN PS Handover Capability field in the MS Radio Access Capability IE (see 3GPP TS 24.008). An E-UTRAN capable mobile station indicates that it supports PS handover to E-UTRAN in the "GERAN to E-UTRAN support in GERAN packet transfer mode" field of the MS Radio Access Capability IE (see 3GPP TS 24.008). The network may initiate the PS handover procedure as a result of various trigger conditions as described in sub-clause 8.10.3.1. The PS handover procedure is described in sub-clause 8.10.

5.4a Dual transfer mode

In dual transfer mode, the mobile station is allocated radio resources providing an RR connection on a dedicated traffic channel and one or more TBFs on one or more packet data physical channels. The allocation of radio resources for the RR connection and the TBFs is co-ordinated by the network, in agreement with the capabilities of the mobile station in dual transfer mode.

If a mobile station that supports multiple TBF procedures has entered dual transfer mode where an uplink TBF is operating in exclusive allocation mode then no additional uplink TBFs may be requested. If exclusive allocation is not used a mobile station in dual transfer mode that supports multiple TBF procedures may request the establishment of one or more additional uplink TBFs by sending a Packet Resource Request message on the PACCH. If this occurs and the network determines that re-allocation of the RR connection is required before it can satisfy the requested TBFs it sends the mobile station a DTM ASSIGNMENT COMMAND message to reallocate the RR connection and a combination of one or more ongoing uplink and downlink TBFs as specified in 3GPP TS 44.018.

Successive transfer of one or more upper layer PDUs is possible. Concurrent TBFs may be established in opposite directions. Mobile stations supporting multiple TBF procedures may have multiple concurrent TBFs established in opposite directions. The transfer of upper layer PDUs in RLC acknowledged or RLC unacknowledged mode is provided.

When a transfer of upper layer PDUs terminates, in either downlink or uplink direction, the corresponding TBF is released. In dual transfer mode, when all TBFs have been released, in downlink and uplink directions, the mobile station enters dedicated mode.

In dual transfer mode, at the release of the RR connection, the mobile station may abort all ongoing TBFs and enter packet idle mode. If the mobile station and the network support enhanced DTM CS release procedure the mobile station may continue in packet transfer mode without entering packet idle mode, after the release of the RR connection.

5.5 General procedures in packet idle and packet transfer modes

Unless explicitly stated, the requirements in this sub-clause (and sub-clauses) apply only in packet idle mode and in packet transfer mode, neither in dedicated mode nor in dual transfer mode.

5.5.1 Mobile station side

The mobile station in either packet idle or packet transfer modes shall monitor the system information broadcast in the cell. A MS that has enabled PEO shall monitor system information as described in 3GPP TS 44.018 [11] while in packet idle mode and is not required to monitor system information while in packet transfer mode. A mobile station in EC operation shall not monitor the system information broadcast in the cell when in packet transfer mode.

In packet idle mode, the mobile station shall monitor the radio blocks on PCCCH, CCCH or EC-CCCH, as defined in sub-clauses 5.5.1.5 and 5.5.1.6. The determination of the paging group for the mobile station is defined in 3GPP TS 45.002.

5.5.0.1 Indication of a selected PLMN using PLMN Index

A mobile station supporting network sharing shall indicate the selected PLMN to the network when sending an upper layer PDU using a foreign TLLI or a random TLLI (see 3GPP TS 23.003) address for this transmission. The mobile station shall set the value of the Selected PLMN Index field in the first RLC data block used to transfer the PDU (see sub-clauses 10.4.14 and 10.4.14a.) to whichever of the following was the most recently received:

– the corresponding PLMN ID index of the selected PLMN, if the selected PLMN is acquired from the system information when the SI22IND field contained in the Control Channel Description IE in the SYSTEM INFORMATION TYPE 3 message (see 3GPP TS 44.018) indicates that network sharing is used; or

– the Selected PLMN Index received in the PS HANDOVER COMMAND message; or

– the Selected PLMN index as indicated by the PLMN Index IE received in the CS HANDOVER COMMAND or DTM HANDOVER COMMAND (see 3GPP TS 44.018); or

– for a mobile station in EC operation, the corresponding PLMN ID index of the selected PLMN, if the selected PLMN is acquired from the EC SYSTEM INFORMATION TYPE 4 message (see 3GPP TS 44.018).

5.5.0.2 Indication of DCN-ID

A mobile station supporting MS assisted Dedicated Core Network selection shall indicate the DCN-ID (corresponding to its selected PLMN) to a network supporting MS assisted Dedicated Core Network selection when sending an upper layer PDU using a foreign TLLI or a random TLLI (see 3GPP TS 23.003) address for this transmission. The mobile station shall set the value of the DCN-ID in the first RLC data block used to transfer the PDU (see sub-clauses 10.4.14 and 10.4.14a.) according to the DCN-ID value indicated by upper layers (see 3GPP TS 23.401 [54] and 3GPP TS 24.008 [51]).

5.5.1.1 Cell reselection

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

When the mobile station reselects a new (target) cell, the support of GPRS in the target cell is indicated in system information sent on BCCH, see 3GPP TS 44.018. If the mobile station has received a PBCCH description for the target cell, it shall assume that GPRS is supported, without further receiving system information on BCCH. The support for EC GSM-IoT in the target cell is indicated by the presence of the EC-SCH.

NOTE: A PBCCH description for the target cell may be received in the packet system information (neighbour cell information in PSI3 and 3bis) and/or in the MBMS NEIGHBOURING CELL INFORMATION message (for a mobile station in broadcast/multicast receive mode) in the old serving cell, or in a BCCH message (SI13) in the target cell.

If a cell supports GPRS, the mobile station may perform packet access. If a cell does not support GPRS, the mobile station is not allowed to perform packet access.

If a cell supports EC-GSM-IoT, a mobile station that is EC-GSM-IoT capable may enable EC operation and perform packet access to request a TBF in EC TBF mode. If a cell does not support EC-GSM-IoT, the mobile station may not enable EC operation in that cell and it may not perform packet access to request a TBF in EC TBF mode.

When a cell reselection is determined by the mobile station or ordered by the network, the mobile station may continue its operation in packet idle or in packet transfer mode in the old serving cell, while acquiring certain system information for the target cell.

When a cell reselection is determined by the mobile station in broadcast/multicast receive mode shall leave the old serving cell immediately if the distribution of MBMS NEIGHBOURING CELL INFORMATION messages is not supported in the old serving cell (see sub-clause 7.7.3). If the distribution of MBMS NEIGHBOURING CELL INFORMATION messages is supported in the old serving cell, the mobile station shall continue its operation in broadcast/multicast receive mode in the old serving cell as follows:

– if the mobile station has received for the target cell the MBMS bearer description for each session it is acquiring it shall leave the cell immediately after it receives an MBMS NEIGHBOURING CELL INFORMATION message for that target cell with the same MBMS_PTM_CHANGE_MARK as the last one received (see note), or after 1s after cell reselection is determined, whichever occurs first;

– otherwise the mobile station shall leave the cell immediately after 1s after cell reselection is determined.

NOTE 1: An MBMS_PTM_CHANGE_MARK is one received in an MBMS NEIGHBOURING CELL INFORMATION message for a session the mobile station is acquiring.

NOTE 2: The behaviour of the mobile station after leaving the old serving cell is described in sub-clause 8.1.6.

If the old cell does not support CCN, the operation in the old cell shall be aborted when one of the following conditions are met:

– the mobile station starts to receive information on PBCCH in the target cell;

– the mobile station has received the SI13 message (see 3GPP TS 44.018) and there is no PBCCH present in the target cell; or

– the criteria for camping on the old cell are no longer fulfilled (see 3GPP TS 45.008).

For a mobile station that has enabled EC operation, the operation in the old cell shall be aborted when one of the following conditions are met:

– the mobile station starts to receive information on BCCH or EC-BCCH in the target cell; or

– the criteria for camping on the old cell are no longer fulfilled (see 3GPP TS 45.008).

If PBCCH is present in the target cell, the mobile station shall delay the start of receiving information on PBCCH until the first occurrence of PSI1 in block B0. If the reception of PSI1 or PSI2 messages fails (see sub-clause 5.5.1.2) the mobile station may re-establish and continue its operation in the old cell, until the next occurrence of PSI1 in block B0, unless the mobile station is in broadcast/multicast receive mode and performs fast reception resumption (see sub-clause 8.1.6.2) of at least one MBMS session in the target cell.

While the operation is maintained in the old cell, the mobile station may suspend its TBF(s) or suspend the monitoring of radio blocks on PCCCH and CCCH, in order to receive necessary information on BCCH in the target cell. Such suspension may be required in both packet idle and packet transfer modes, but shall not apply in broadcast/multicast receive mode. It is performed without notification to the network.

Suspension of the operation in the old cell for this purpose is allowed during the time required, for each message and according to the mobile station’s multislot class, to receive the required messages on BCCH in the target cell. The allowable suspension of an uplink TBF may be extended with one block period, in case of dynamic or extended dynamic allocation, if the mobile station is unable to receive the corresponding USF due to the suspension of downlink operation.

When the conditions are fulfilled to switch to the new cell, the mobile station shall abort all TBFs in progress by immediately ceasing to decode the downlink, ceasing to transmit on the uplink, stopping all RLC/MAC timers except for timers related to measurement reporting. The mobile station shall then switch to the identified specified new cell and shall obey the relevant RLC/MAC procedures on this new cell.

If the old cell supports CCN, a mobile station shall, when the cell reselection has been determined for other reason than path loss criterion parameter C1 becomes negative, follow the procedures for Network Assisted Cell Change as specified in sub-clauses 5.5.1.1a.2 and 8.8.2.

If the old cell supports CCN, a mobile station may, when the cell reselection has been determined because the path loss criterion parameter C1 has become negative, follow the procedures for Network Assisted Cell Change as specified in sub-clauses 5.5.1.1a.2 and 8.8.2.

Under no circumstances and independent of whether CCN mode is supported, operations in the old cell shall be continued more than 5 s after a cell reselection has been determined.

5.5.1.1a Network Assisted Cell Change

The mobile station shall support the Network Assisted Cell Change procedures. The Network Assisted Cell Change consists of two independent procedures:

– One procedure that can assist a mobile station in packet transfer mode or MAC-Shared state with neighbour cell system information for a GSM neighbouring cell required for initial packet access after a cell change;

– one procedure in which the mobile station notifies the network when it has determined to reselect to another GSM, to a 3G, or to an E-UTRAN cell and delays the cell re-selection (CCN mode procedures) to let the network e.g. in the case of reselection to a GSM cell, respond with neighbour cell system information.

The Network Assisted Cell Change procedures are part of the GERAN Feature Package 1. A mobile station indicating support of the GERAN Feature Package 1 in the Mobile Station Classmark 3 IE, the MS Radio Access Capability IE and the MS Radio Access Capability 2 IE supports the Network Assisted Cell Change procedures (see 3GPP TS 24.008).

5.5.1.1a.1 Neighbour Cell System Information Distribution

The network may send GSM neighbour cell system information to a mobile station in packet transfer mode or MAC-Shared state. A mobile station, which receives this information, shall store the information for 30 seconds and during that period the information can be used for initial access in the neighbour cell (see sub-clause 8.8.1).

5.5.1.1a.2 CCN Mode

A mobile station, which has CCN Enabled, can enter CCN Mode.

The mobile station shall enable CCN when the following criteria are fulfilled:

– the mobile station is camping on a cell (see 3GPP TS 45.008); and

– the network indicates CCN ACTIVE/3G CCN ACTIVE/E-UTRAN CCN ACTIVE either in system information to all mobile stations in the cell or in an individual order to a certain mobile station; and

– the mobile station is neither in dedicated mode nor Dual Transfer Mode; and

– the mobile station is in NC0 or in NC1 mode; and

– the mobile station is in Packet Transfer mode.

The CCN procedures and the criteria for entering and leaving CCN mode are specified in sub-clauses 8.8.2 and 8.8.3.

5.5.1.1b Release of RR connection

5.5.1.1b.1 General

After the release of an RR connection (see 3GPP TS 44.018, Normal release procedure and Abnormal cases), if the mobile station during the RR connection is unable to monitor the system information broadcast on BCCH or PBCCH (i.e. GPRS class B or GPRS class A mode of operation using DTM), the mobile station shall acquire the system information broadcast in the serving cell. The acquisition of system information shall be performed according to the requirements in sub-clause 5.5.1.2 (PBCCH present in the cell) or sub-clause 5.5.1.3 (PBCCH not present in the cell). The mobile station shall not attempt a packet access or accept a packet downlink assignment before those requirements are fulfilled.

The following exceptions, stated in sub-clauses 5.5.1.1b.2 to 5.5.1.1b. 5, may apply.

5.5.1.1b.2 Continuation of PBCCH information

At the establishment of an RR connection and if PBCCH is present in the cell, the mobile station may keep the PSI messages received on PBCCH before the RR connection establishment.

If the RR connection is established, maintained and released in the same serving cell and the MS has received PSI14 messages or received and acted upon PSI1 messages during dual transfer mode at least every 30 seconds such that

– for PSI1, the value of the PBCCH_CHANGE_MARK has indicated no change in the PSI messages (see sub-clause 5.5.1.2.1), and

– for PSI14, all instances of the PSI14 messages indicate no change in the contents of PSI messages,

the mobile station may resume the supervision of PBCCH_CHANGE_MARK and update of PBCCH information, defined in sub-clause 5.5.1.2.1, and need not initiate a complete acquisition of PBCCH information, as specified in sub-clause 5.5.1.2.

5.5.1.1b.3 Continuation of BCCH information

At the establishment of an RR connection and if PBCCH is not present in the cell, the mobile station may keep the SI messages received on BCCH before the RR connection establishment.

If the RR connection is established, maintained and released in the same serving cell and the MS has received PSI14 messages or received and acted upon PSI13/SI13 messages during dual transfer mode at least every 30 seconds such that the value of the BCCH_CHANGE_MARK has indicated no change in the SI messages (see sub-clause 5.5.1.3.1), the mobile station may resume the supervision of BCCH_CHANGE_MARK and update of BCCH information, defined in sub-clause 5.5.1.3.1, and need not initiate a complete acquisition of BCCH information, as specified in sub-clause 5.5.1.3.

5.5.1.1b.4 Receipt of PSI14 message in dual transfer mode

In dual transfer mode, the mobile station may receive the PSI14 message on PACCH in the serving cell. If the RR connection is released in the same serving cell within 30 s after the PSI14 message was last received, the mobile station may use the PSI14 message as a substitute for the SI13 message after the release of the RR connection, until the SI13 message has been received or the mobile station starts to receive information on PBCCH.

The presence of a PBCCH in the cell is indicated by a PBCCH description in the PSI14 message. If the message does not contain the PBCCH description, the mobile station shall assume that PBCCH is not present in the cell.

After the release of the RR connection and if PBCCH is present in the cell, the mobile station shall perform a complete acquisition of PBCCH information, as defined in sub-clause 5.5.1.2.

After the release of the RR connection and if PBCCH is not present in the cell, the mobile station shall perform a complete acquisition of BCCH information, as defined in sub-clause 5.5.1.3. The mobile station shall attempt to receive the SI13 (or PSI13) message within 30 s after the last receipt of the PSI14 message.

5.5.1.1b.5 Acquisition of system information for enhanced DTM CS release procedure in dual transfer mode

If the mobile station and the network support enhanced DTM CS release procedure, the network may delay the release of the RR connection until the mobile station has received the needed system information, in order to maintain the radio resources on the PDCH(s) after the release of the RR connection.

The network initiates enhanced DTM CS release by sending the PACKET CS RELEASE INDICATION message on PACCH with the ENHANCED_DTM_CS_RELEASE_INDICATION parameter set to indicate that the RR connection is to be released (i.e. upon subsequent transmission of the CHANNEL RELEASE message to the mobile station) and starts timer T3197.

On receipt of PACKET CS RELEASE INDICATION message with the ENHANCED_DTM_CS_RELEASE_INDICATION parameter set to indicate that the RR connection is to be released, the mobile station shall send the PACKET SI STATUS (respectively PACKET PSI STATUS if the PBCCH is present) message on PACCH to indicate which system information messages were stored while in the dual transfer mode by the mobile station. The following system information (respectively packet system information) messages are required to maintain radio resources and enter packet transfer mode after the release of the RR connection:

– PSI1, PSI2 and PSI14 in the Received PSI Message List; or respectively

– SI13, SI3 and SI1, if present, in the Received SI Message List.

The PSI (respectively SI) messages listed above shall be indicated as the first PSI (respectively SI) messages indicated in the PACKET PSI STATUS (respectively PACKET SI STATUS) messages. If other PSI (respectively SI) messages are indicated in the PACKET PSI STATUS (respectively PACKET SI STATUS) message, the priority order defined in Table 5.5.1.4.3.1 shall apply.

In case the mobile station has no information available to determine whether PBCCH is allocated in the cell or not, the mobile station shall transmit the PACKET SI STATUS message where an empty Received SI Message List is indicated. Upon reception of such message, the network shall determine that the mobile station has no knowledge whether PBCCH is present in the cell. In this case the network shall start transmitting the PSI messages if PBCCH is present in the cell or, otherwise, SI messages.

The mobile station may request the release of the RR connection and packet resources (e.g. if combined RAU procedure shall be performed after the release of the RR connection) with PS_REL_REQ field sent in the PACKET SI STATUS (respectively PACKET PSI STATUS) message.

On receipt of the PACKET SI STATUS (respectively PACKET PSI STATUS) message the network shall send the missing system information messages by using the PACKET SERVING CELL SI message or it shall send respectively the corresponding packet system information messages.

The mobile station is allowed to send the PACKET SI STATUS (respectively PACKET PSI STATUS) message twice and the second sending occurrence of this message shall take place at the first suitable opportunity at least one second after the first transmission of that message. Whenever the mobile station has received all required system information (respectively packet system information) messages, it shall send the PACKET SI STATUS (respectively PACKET PSI STATUS) message at the first suitable opportunity, even if it has already sent the PACKET SI STATUS (respectively PACKET PSI STATUS) twice.

When the network receives the PACKET SI STATUS (respectively PACKET PSI STATUS) message indicating that all required system information (respectively packet system information) messages have been received by the mobile station it shall stop timer T3197, start timer T3109 (see 3GPP TS 44.018) and send the CHANNEL RELEASE message on the main DCCH indicating that the mobile station is allowed to continue in packet transfer mode after the release of the RR connection (see 3GPP TS 44.018). Upon reception of the CHANNEL RELEASE message the mobile station shall release the RR connection, continue in packet transfer mode and re-configure the packet resources (if provided by the PACKET CS RELEASE INDICATION message).

If continuous timing advance parameters are provided to the mobile station in the PACKET CS RELEASE INDICATION message, the mobile station shall start the continuous timing advance procedure upon entering packet transfer mode. The mobile station shall use the last timing advance value received whilst in dual transfer mode until a new value of the timing advance is provided to the mobile station according to the procedures defined for packet transfer mode.

If timer T3197 expires before the network receives the PACKET SI STATUS (respectively PACKET PSI STATUS) message indicating that all required system information (respectively packet system information) messages have been received by the mobile station, the network shall release the RR connection by sending the CHANNEL RELEASE message on the main DCCH indicating that the mobile station is not allowed to continue in packet transfer mode after the release of the RR connection (see 3GPP TS 44.018).

5.5.1.1c Inter-RAT cell re-selection based on priority information

5.5.1.1c.1 General

The network may provide priority information to enable priority-based cell reselection (see 3GPP TS 45.008). Inter-RAT cell reselection based on priority information applies only in case of autonomous cell reselection.

Two sets of priorities are defined for inter-RAT cell re-selection based on priority information: common priorities (see sub-clause 5.5.1.1c.2) and individual priorities (see sub-clause 5.5.1.1c.3). The mobile station shall delete all priorities when switched off.

While providing common or individual priorities, the network shall ensure that the GERAN priority value is different from all E-UTRAN priority values and from all UTRAN priority values, and that all UTRAN priority values are different from all E-UTRAN priority values. In addition, if for some E-UTRAN frequencies THRESH_E-UTRAN_high_Q is provided in the Enhanced Cell Reselection Parameters Description IE in the PACKET MEASUREMENT ORDER message, the network shall ensure that the priority value for any frequency for which THRESH_E-UTRAN_high_Q is provided is different from the priority value for all frequencies for which THRESH_E-UTRAN_high_Q is not provided.

The mobile station shall determine each set, considering only individual priorities (respectively common priorities) when building the set of individual (respectively common) priorities. The mobile station shall perform the following steps, in the specified order:

– If the same priority value is assigned to GERAN and to one or more UTRAN or E-UTRAN frequencies then all such UTRAN and E-UTRAN priority values are considered as not in the set of priorities.

– If the same priority value is assigned to one or more UTRAN frequencies and one or more E-UTRAN frequencies, then all such priority values are considered as not in the set of priorities.

– If the same priority value is assigned to one or more E-UTRAN frequencies for which THRESH_E-UTRAN_high_Q is provided and one or more E-UTRAN frequencies for which THRESH_E-UTRAN_high_Q is not provided then all such priority values are considered as not in the set of priorities.

NOTE 1: These steps mean that if, for example, there are two UTRAN priority values, one E-UTRAN priority value (for a frequency for which THRESH_E-UTRAN_high_Q is provided) and one E-UTRAN priority value (for a frequency for which THRESH_E-UTRAN_high_Q is not provided) that are all the same, then all four priority values are considered as not in the set of priorities.

A set of individual priorities is valid if it contains at least one priority.

A set of common priorities is valid if both of the following conditions are met:

– The set of priorities includes a priority for GERAN;

– The mobile station does not have a valid set of individual priorities.

If the mobile station has a valid set of priorities, the priorities in this set shall be used for priority-based reselection as specified in 3GPP TS 45.008.

NOTE 2: It is possible that individual priorities inherited from UTRAN or E-UTRAN (see sub-clause 5.5.1.1c.3) do not contain a priority for GERAN.

5.5.1.1c.2 Common priorities information

The mobile station may receive common priorities information as specified in 3GPP TS 44.018.

In addition, a mobile station may receive common priorities information in the PACKET MEASUREMENT ORDER message in the Priority and E-UTRAN Parameters Description IE, or for a mobile station supporting extended EARFCNs, in the E-UTRAN NC with extended EARFCNs IE.

5.5.1.1c.3 Provision of individual priorities information

The provision of individual priorities information is described in 3GPP TS 44.018.

5.5.1.1d (void)

5.5.1.2 System information on PBCCH

If PBCCH is present in the serving cell, the mobile station shall receive the PACKET SYSTEM INFORMATION (PSI) messages broadcast on PBCCH. The parameters determining the schedule of PSI messages on PBCCH are provided in the PSI1 message.

When a new cell has been selected where PBCCH is present, the mobile station shall perform a complete acquisition of PBCCH messages (see 5.5.1.4). The mobile station shall not perform packet access in the selected cell, or enter the packet transfer mode or the MAC-Shared state, until it has:

– acquired the PACKET SYSTEM INFORMATION TYPE 1 (PSI1) message;

– acquired a consistent set of PSI2 messages; and

– made at least one attempt to receive the complete set of PSI messages on PBCCH.

If the network supports the PACKET PSI STATUS message, the mobile station may perform packet access or maintain its radio resources (PDCH(s)) when the RR connection is released while in dual transfer mode, and enter packet transfer mode or the MAC-Shared state, as soon as the PSI1 message and a consistent set of PSI2 messages have been received. In this case, the mobile station shall implement the request for acquisition of system information (see 5.5.1.4.3).

When the PSI1 message has been received, the mobile station shall supervise the PBCCH_CHANGE_MARK and perform update of PBCCH information as specified in sub-clause 5.5.1.2.1. In addition, while camping on a cell, the mobile station shall take into account any PSI message that may be received on PCCCH and PACCH.

Once that the mobile station starts to acquire the information on PBCCH, the information sent to a mobile station in RLC/MAC control messages shall be independent of the information provided on the BCCH. If the mobile station receives information in an RLC/MAC control message that depends on the BCCH information, the behaviour of the mobile station is not specified.

5.5.1.2.1 Supervision of PBCCH_CHANGE_MARK and update of PBCCH information

While camping on a cell where PBCCH is present, the mobile station shall attempt to receive the PSI1 message at least every 30 seconds. The mobile station shall then take into account any occurrence of the PSI1 message that may be received on PACCH during packet transfer mode or MAC-Shared state. The mobile station shall also take into account any occurrence of the PSI1 message that may be received on PCCCH during periods in packet idle mode or MAC-Idle state. If the PSI1 message is not received, the mobile station shall attempt to receive this message on PBCCH during periods in packet idle mode or MAC-Idle state.

If the mobile station has not received the PSI1 message within the last 30 seconds, it shall attempt to receive the PSI1 message each time it is scheduled on PBCCH. Such attempts shall be made during packet idle mode, packet transfer mode, MAC-Idle state and MAC Shared state. A mobile station in packet transfer mode or MAC-Shared state may suspend its TBF(s) for this purpose (see 5.5.1.4.2).

The PSI1 message contains the PBCCH_CHANGE_MARK and PSI_CHANGE_FIELD parameters. The mobile station shall store the value of the last PBCCH_CHANGE_MARK received.

If the mobile station receives a PBCCH_CHANGE_MARK and detects that the value has been incremented by one unit, compared to the previous value, the mobile station shall perform a partial acquisition of PBCCH information. The information that shall be received is determined by the PSI_CHANGE_FIELD parameter:

– If the PSI_CHANGE_FIELD parameter indicates an update of a specific type or specific types of PSI messages, the mobile station shall receive at least one instance of each of the indicated type(s) of PSI messages.

– If the PSI_CHANGE_FIELD parameter indicates an update of an unspecified type or types of PSI messages, the mobile station shall receive at least one message instance within each consistent set of PSI messages on PBCCH. It shall also receive all PSI messages on PBCCH not belonging to a consistent set.

– If the PSI_CHANGE_FIELD parameter indicates an update of an unknown type of PSI message, the mobile station is not required to receive any PBCCH information.

When a PSI message is received, the mobile station shall consider the PSI change mark value, if such is received in the message and take appropriate action (see sub-clause 5.5.1.4.1).

Whenever the mobile station receives a PBCCH_CHANGE_MARK and detects that the value has been incremented by more than one unit, compared to the previous value, the mobile station shall perform a complete acquisition of PBCCH messages (see sub-clause 5.5.1.4).

5.5.1.2.2 Replacement of PBCCH

The mobile station may receive a PSI1 message indicating that PBCCH is being deactivated in the cell. Moreover, the mobile station may receive a PSI13 message on PACCH or PCCCH providing a different PBCCH description than the one currently being used, or a PSI13 message indicating that PBCCH is not present in the cell.

If the mobile station detects that PBCCH is being deactivated in the cell, or receives an indication that PBCCH is no longer present in the cell, it shall attempt to receive the SI13 message on BCCH. For this purpose, the mobile station may suspend its operation in packet idle mode, packet transfer mode, MAC-Idle state and MAC-Shared state (see 5.5.1.4.2). When the SI13 has been received, further action depends on the contents of the SI13 message:

– If the SI13 message contains a PBCCH description, the mobile station shall perform a complete acquisition of PBCCH messages using the indicated PBCCH (see sub-clause 5.5.1.4).

– If the SI13 message does not contain a PBCCH description, the mobile station shall perform a complete acquisition of BCCH messages.

– If the mobile station receives a PSI13 message with a PBCCH description different from that currently being used, the mobile station shall perform a complete acquisition of PBCCH messages using the new PBCCH.

5.5.1.2.3 PSI1 reception failure

If the mobile station has not received the PSI1 message within the last 60 s, a PSI1 reception failure has occurred. A PSI1 reception failure shall result in a cell reselection.

5.5.1.3 System information on BCCH

The presence of a PBCCH in the cell is indicated by a PBCCH description in the SI13 message on BCCH. If the mobile station receives an SI13 message without a PBCCH description, it shall assume that PBCCH is not present in the cell. If PBCCH is not present in the serving cell, the mobile station shall receive the SYSTEM INFORMATION (SI) messages broadcast on BCCH.

When a new cell has been selected where PBCCH is not present, the mobile station shall perform a complete acquisition of BCCH messages (see sub-clause 5.5.1.4). The mobile station shall not perform packet access in the selected cell, or enter the packet transfer mode, until it has:

– acquired the SYSTEM INFORMATION TYPE 3 (SI3), SI13 and, if present, SI1 messages;

– made at least one attempt to receive other SI messages that may be scheduled within one TC cycle on BCCH (see 3GPP TS 45.002).

If the network supports the PACKET SI STATUS message, the mobile station may perform packet access or maintain its radio resources (PDCH(s)) when the RR connection is released while in dual transfer mode, and enter packet transfer mode, as soon as the SI3, SI13 and, if present, SI1 messages have been received. In this case, the mobile station shall implement the request for acquisition of system information (see sub-clause 5.5.1.4.3).

When the SI13 message has been received, the mobile station shall supervise the BCCH_CHANGE_MARK and perform update of BCCH information.

5.5.1.3.1 Supervision of BCCH_CHANGE_MARK and update of BCCH information

While camping on a cell where PBCCH is not present, the mobile station shall attempt to receive the SI13 or the PSI13 message at least every 30 s. The mobile station shall then take into account any occurrence of the PSI13 message that may be received on PACCH during packet transfer mode. If PSI13 is not received, the mobile station shall attempt to receive the SI13 message on BCCH during periods in packet idle mode.

If the mobile station has received neither the SI13 nor the PSI13 message within the last 30 s, it shall attempt to receive the SI13 message each time it is scheduled on BCCH. Such attempts shall be made during both packet idle and packet transfer modes. A mobile station in packet transfer mode may suspend its TBF(s) for this purpose (see sub-clause 5.5.1.4.2).

An exception case is where a mobile station has enabled PEO in which case the mobile station shall monitor system information as described in 3GPP TS 44.018 [11] while in packet idle mode but shall not monitor system information while in packet transfer mode.

The SI13 and PSI13 messages contain the BCCH_CHANGE_MARK and SI_CHANGE_FIELD parameters. When camped on a cell where PBCCH is not present, the mobile station shall store the value of the last BCCH_CHANGE_MARK received. In that case, if the mobile station detects that the value has been incremented by one unit, compared to the previous value, the mobile station shall perform a partial acquisition of BCCH information. The information that shall be received is determined by the SI_CHANGE_FIELD parameter:

– If the SI_CHANGE_FIELD parameter indicates an update of a specific type or specific types of SI messages, the mobile station shall receive at least one instance of each of the indicated type(s) of SI messages.

– If the SI_CHANGE_FIELD parameter indicates an update of an unspecified type or types of SI messages, the mobile station shall receive at least one message instance within each consistent set of SI messages on BCCH. It shall also receive all SI messages on BCCH not belonging to a consistent set.

– If the SI_CHANGE_FIELD parameter indicates an update of an unknown type of SI message, the mobile station is not required to update any BCCH information.

When an SI message is received, the mobile station shall consider a SI change mark value, if such is received in the message and take appropriate action (see sub-clause 5.5.1.4.1).

If the mobile station detects that the BCCH_CHANGE_MARK value has been incremented by more than one unit, compared to the previous value, the mobile station shall perform a complete acquisition of BCCH messages (see sub-clause 5.5.1.4).

5.5.1.3.2 Establishment of PBCCH

The mobile station may receive an SI13 or PSI13 message providing a PBCCH description indicating that PBCCH is present in the cell. The mobile station shall then perform a complete acquisition of PBCCH messages using the indicated PBCCH (see sub-clause 5.5.1.4).

5.5.1.3.3 SI13 reception failure

If the mobile station has not received the SI13 or the PSI13 message within the last 60 s, a SI13 reception failure has occurred. An SI13 reception failure shall result in a cell reselection.

5.5.1.3a System information on EC-BCCH

A mobile station that has enabled EC operation in a cell shall receive the EC SYSTEM INFORMATION messages broadcast on EC-BCCH (EC SI). The EC-BCCH shall be present in a cell that supports EC-GSM-IoT.

When a mobile station that is EC-GSM-IoT capable has selected a new cell that supports EC-GSM-IoT, the mobile station shall perform a complete acquisition of EC-BCCH messages, see 3GPP TS 44.018. The mobile station shall not perform packet access in the selected cell, or enter the packet transfer mode, until it has acquired the full set of system information messages scheduled on the EC-BCCH.

5.5.1.4 Acquisition of system information on the broadcast channel

This procedure shall be used by a mobile station that supports GPRS (in A/Gb mode) or Iu mode in order to perform a complete or partial acquisition of either PBCCH or BCCH information. As part of this procedure, the mobile station may implement the request for acquisition of system information as specified in sub-clause 5.5.1.4.3.

The procedure to be used by a mobile station that has enabled EC operation, is described in 3GPP TS 44.018.

When PBCCH is not present in a cell this procedure starts:

– when the mobile station is camped on BCCH and receives a BCCH_CHANGE_MARK or SI change mark value indicating that system information is changed.

When PBCCH is present in a cell this procedure starts:

– when the mobile station is camped on PBCCH and receives a PBCCH_CHANGE_MARK or PSI change mark value indicating that packet system information is changed.

Moreover, the procedure shall start at any other indication, which may be received by the mobile station, that the stored system information for the serving cell is no longer valid.

At cell selection or cell reselection, in case PBCCH is present in the target cell, this procedure starts when the mobile station starts to receive the information on PBCCH. In case PBCCH is not present in the target cell, the procedure starts when the mobile station has received the SI13 message.

In a complete acquisition of either PBCCH or BCCH information, the mobile station shall receive all PSI or SI messages that are scheduled on the respective broadcast channel. The mobile station shall delete any PSI or SI change mark value that was stored before the acquisition of PBCCH or BCCH information started.

In a partial acquisition of either PBCCH or BCCH information, only a certain subset of the PSI or SI messages that are scheduled on the respective broadcast channel shall be received. The mobile station may consider the state of the PSI or SI change mark values, without restriction, to reduce the total number of messages to receive.

When the mobile station acquires a set of PSI or SI messages on the respective broadcast channels, it may receive these messages during packet idle mode, packet transfer mode, MAC-Idle state, MAC-Shared state and broadcast/multicast receive mode. While the mobile station is in packet idle mode or MAC-Idle state or broadcast/multicast receive mode if the network has indicated that the system information is not sent on the PACCH, an attempt to receive a required message shall be made each time the message is scheduled on the broadcast channel, until the message is received. While the mobile station is in packet transfer mode, MAC-Shared state or broadcast/multicast receive mode if the nework has indicated that the system information is sent on the PACCH, it shall receive any PSI message that is sent by the network on PACCH. While the mobile station is in dual transfer mode or MAC-DTM state, it may disregard any PSI message except PSI14 message that is sent by the network on PACCH.

If the mobile station has not received the required messages within 10 seconds after the start of this procedure, an attempt to receive a missing message shall be made each time the message is scheduled on the broadcast channel. These attempts shall then be performed during packet idle mode, packet transfer mode, MAC-Idle state, MAC-Shared state and broadcast/multicast receive mode. A mobile station in packet transfer mode or MAC-Shared state may suspend its TBF(s) for this purpose, as specified in 5.5.1.4.2. A mobile station in broadcast/multicast receive mode may skip the reception of radio blocks of the MBMS radio bearer for the same purpose, as specified in 5.5.1.4.2.

A second acquisition of either PBCCH or BCCH information may be initiated (e.g. when the mobile station receives a PSI or SI change mark value) before a previous acquisition is completed. In this case, the mobile station shall discard and immediately begin re-acquiring all the system information messages of the particular type to which the changemark value refers.

To allow future extension of PSI message types, the mobile station may disregard a message in a position within the schedule of PSI messages on PBCCH, where it receives a valid RLC/MAC control block, but diagnoses an unknown or unexpected (non-PSI) message type. When this condition is detected, the mobile station needs not to receive the PBCCH block in this position again, until a change in the schedule of PBCCH messages is detected or a complete acquisition of PBCCH information is required.

5.5.1.4.1 Consistent sets of system information messages

A mobile station, receiving a PSI or SI message belonging to a consistent set of system information messages, shall store the last PSI or SI change mark value received for the set of messages (see table 5.5.2.1.4.1). A mobile station lacking all non-GSM capabilities defined for PSI6, PSI7, SI 18 or SI 20 shall consider those message as irrelevant when making a determination of whether or not a consistent set of system information messages has been received.

A mobile station that does not support UTRAN shall consider a PSI3quater message as irrelevant when making a determination of whether or not a consistent set of system information messages has been received.

Whenever mobile station receives a PSI or SI change mark value, which is not equal to the previously stored value for the set of messages, the mobile station shall perform a partial acquisition of either PBCCH or BCCH information. It shall then receive all instances of the PSI or SI messages belonging to the consistent set of system information messages.

If a mobile station detects an inconsistency amongst the PSI or SI count and index parameters within a consistent set of system information messages or any other inconsistency making the information that is contained invalid, the mobile station shall discard the messages received so far and delete the stored PSI or SI change mark value. The mobile station may then restart the acquisition of the affected system information messages.

5.5.1.4.2 Suspension of operation to receive system information

During certain conditions, the mobile station in packet transfer mode or MAC-Shared state is allowed to suspend its TBF(s) to receive certain information on PBCCH or BCCH. A mobile station in broadcast/multicast receive mode may suspend the reception of radio blocks of the MBMS radio bearer for the same purpose. Such suspension is made without notification to the network. A mobile station in EC operation shall not suspend its TBF for reception of EC system information.

Suspension of its TBF(s) or suspension of the reception of radio blocks of the MBMS radio bearer for this purpose is allowed during the time required, for each message and according to the mobile station’s multislot class, to receive the required messages on PBCCH or BCCH. The allowable suspension of an uplink TBF may be extended with one block period, in case of dynamic or extended dynamic allocation, if the mobile station is unable to receive the corresponding USF due to the suspension of downlink operation. In case it conflicts with the transmission of a polling response, priority shall be given to the acquisition of blocks on the PBCCH or BCCH channel.

5.5.1.4.3 Request for acquisition of system information

As an option, the mobile station may implement the request for acquisition of system information. If the network supports the PACKET PSI STATUS message or the PACKET SI STATUS message, the mobile station shall then send the PACKET PSI STATUS message to the network, each time an acquisition of PBCCH information is initiated or the PACKET SI STATUS message to the network, each time an acquisition of BCCH information is initiated.

A mobile station supporting the Network Assisted Cell Change or enhanced DTM CS release procedures shall implement the request for acquisition of system information (see sub-clauses 5.5.1.1a and 5.5.1.1b.5).

The PACKET SI STATUS message shall always contain the PSCSI_SUPPORT field.

The PACKET PSI STATUS (respectively PACKET SI STATUS) message shall indicate the present status of PSI (respectively SI) messages stored in or requested but not received by the mobile station. The mobile station shall include as many PSI (respectively SI) message types that fit into the Received PSI Message List (respectively Received SI Message List) construction in the PACKET PSI STATUS (respectively PACKET SI STATUS) message and that meet the following criteria:

– The PSI (respectively SI) message type is relevant for the mobile station, based on the features the mobile station supports (e.g. non-GSM and multi-RAT capabilities); and

– In case of optional PSI (respectively SI) messages types, the PSI (respectively SI) message type shall be indicated by the network as present on PBCCH (respectively BCCH).

If the presence of an optional PSI (respectively SI) message type cannot be determined, based on the information received, the mobile station shall assume that the optional PSI (respectively SI) message type is present.

NOTE 1: On PBCCH, the presence of optional PSI messages is indicated in PSI1 and PSI2.

NOTE 2: On BCCH, SI2, SI3, SI4 and, if present, SI9 indicate the presence of optional SI messages, except SI1. The presence of SI1 can be determined by reading the BCCH Norm block at TC = 0.

The "ADDITIONAL_MSG_TYPE" information should reflect whether all PSI (respectively SI) message types that satisfy the criteria given above fit into a given PACKET PSI STATUS (respectively PACKET SI STATUS) message or not.

The message type value for these PSI (respectively SI) messages shall be included in the Received PSI Message List (respectively Received SI Message List) in the PACKET PSI STATUS (respectively PACKET SI STATUS) message. The message types that may be indicated are given in table 5.5.1.4.3.1. The message types shall be indicated in descending order of priority. The network may use this information to determine which PSI (respectively SI) message types the mobile station is able to receive and the present status of the PSI (respectively SI) messages stored in the mobile station.

Table 5.5.1.4.3.1: Message types that may be indicated at a request for acquisition of system information during packet transfer mode

Type of status message	PSI (respectively SI) message types, descending order of priority
PACKET PSI STATUS message	PSI2 (highest priority), PSI3, PSI3bis, PSI5, PSI3ter, PSI3quater, PSI6, PSI7, and PSI8 (lowest priority)
PACKET SI STATUS message	SI1 (highest priority), SI3, SI2, SI2bis, SI2ter, SI2quater, SI4, SI2n, SI7, SI8, SI9, SI15, SI16, SI17, SI18, SI20 and SI19 (lowest priority)

During a partial acquisition of PSI (respectively SI) messages, see sub-clause 5.5.1.4, the mobile station may need to obtain the current PSI (respectively SI) change mark value for certain types of PSI (respectively SI) messages. In that case, the mobile station may use this procedure and indicate the present status for that PSI (respectively SI) message type in the PACKET PSI STATUS (respectively PACKET SI STATUS) message, except that the message instance corresponding to the PSI (respectively SI) index parameter = 0 shall be indicated as not received.

The PACKET PSI STATUS (respectively PACKET SI STATUS) message may also be used to indicate the message type of a PSI (respectively SI) message that is required but has not been received by the mobile station.

The PACKET PSI STATUS (respectively PACKET SI STATUS) message is sent on PACCH when the mobile station is in packet transfer mode or MAC-Shared state. The first sending of this message during the acquisition of PBCCH (respectively BCCH) information shall take place at the first suitable opportunity after the acquisition is initiated. This is also allowed during the contention resolution.

During the acquisition of PBCCH (respectively BCCH) information, up to four PACKET PSI STATUS (respectively PACKET SI STATUS) messages may be sent to the network. The second sending occurrence of this message shall take place at the first suitable opportunity at least one second after that the message is sent the first time. Further sending occurrences shall take place at the first suitable opportunity at least two seconds after that the message was sent the previous time. At each sending occurrence, this message shall be updated according to the present status of PSI (respectively SI) messages in the mobile station.

The PACKET PSI STATUS (respectively PACKET SI STATUS) message shall not be sent when the mobile station has started to suspend its TBF(s) in order to receive the required PSI (respectively SI) messages on PBCCH (respectively BCCH). The PACKET PSI STATUS (respectively PACKET SI STATUS) message shall not be sent when the mobile station has acquired the complete set of PSI (respectively SI) messages on PBCCH (respectively BCCH), unless a new partial or full acquisition of system information is required.

5.5.1.5 Discontinuous reception (DRX)

A mobile station in packet idle mode shall monitor the CCCH, PCCCH or EC-CCCH as defined in 3GPP TS 45.002.

In the GPRS attach procedure, defined in 3GPP TS 24.008, the mobile station requests values for the SPLIT_PG_CYCLE and NON_DRX_TIMER parameters to be applied on CCCH or PCCCH.

NOTE: The support of the SPLIT_PG_CYCLE parameter is optional on CCCH, see 3GPP TS 45.002.

The SPLIT_PG_CYCLE and NON_DRX_TIMER parameters control:

– the occurrence of paging blocks on CCCH or PCCCH belonging to the mobile station (SPLIT_PG_CYCLE parameter, see 3GPP TS 45.002) in DRX mode (see 3GPP TS 43.064); and

– the duration of the non-DRX mode period to be applied by the mobile station when it has left the packet transfer mode or the dual transfer mode and then enters the packet idle mode.

There are five cases when the mobile station shall enter a non-DRX mode period.

1) At the transition from the packet transfer mode to the packet idle mode, the mobile station shall enter the Transfer non-DRX mode period.

2) At the transition from the dual transfer mode to the dedicated mode or packet idle mode, the mobile station shall enter the Transfer non-DRX mode period.

In both cases, the duration of the Transfer non-DRX mode period is determined by value of the NON_DRX_TIMER parameter, requested in the GPRS attach procedure, and the value of the DRX_TIMER_MAX parameter broadcast in the cell. The mobile station may use the minimum value of these two parameters.

If the mobile station receives a new value of the DRX_TIMER_MAX parameter during the Transfer non-DRX mode period, the mobile station may wait to apply the new value until the next time the Transfer non-DRX mode period is entered.

3) A mobile station operating in NC2 mode shall enter the NC2 non-DRX mode period when it sends an NC measurement report. The duration of this period is defined by the NC_NON_DRX_PERIOD parameter.

4) When initiating the MM procedures for GPRS attach and routeing area update defined in 3GPP TS 24.008, the mobile station shall enter the MM non-DRX mode period. This period ends when either of the messages GPRS ATTACH ACCEPT, GPRS ATTACH REJECT, ROUTING AREA UPDATE ACCEPT or ROUTING AREA UPDATE REJECT is received by the mobile station. This period also ends after timeout when waiting for any of these messages.

5) The mobile station shall enter the MBMS non-DRX mode period when it receives a pre-notification for an MBMS service and MBMS session, and the MBMS service is a broadcast service or is a multicast service previously joined by the mobile station and the MBMS session has not yet been received by the mobile station. The mobile station shall also enter the MBMS non-DRX mode period, if not already in it, when the mobile station sends the MBMS SERVICE REQUEST message, unless the MBMS packet access procedure is performed on MPRACH during fast reception resumption. The mobile station shall also enter the MBMS non-DRX mode period, if not already in it, when it receives a notification for an MBMS service and MBMS session, and the MBMS service is a broadcast service or is a multicast service previously joined by the mobile station and the MBMS session has not yet been received by the mobile station, and the notification:

– indicates that no counting shall be performed and contains no MBMS p-t-m channel description;

– or, specifies an MBMS radio bearer starting time which has not yet elapsed.

The MBMS non-DRX mode period ends when a notification (containing an MBMS p-t-m channel description) or the MBMS ASSIGNMENT message, addressing the same MBMS session and not specifying an MBMS radio bearer starting time or specifying an MBMS radio bearer starting time already elapsed, is received by the mobile station. If the notification or the MBMS ASSIGNMENT message specifies an MBMS radio bearer starting time which has not yet elapsed, the period ends when the point in time denoted by the MBMS radio bearer starting time occurs, unless any subsequent notification or MBMS ASSIGNMENT message addressing the same MBMS session and received by the mobile station, before the point in time denoted by the MBMS radio bearer starting time, provides an up-to-date value of the MBMS radio bearer starting time or does not include an MBMS radio bearer starting time.

The MBMS non-DRX mode period also ends after timeout when waiting for the MBMS notification of the pre-notified MBMS service and MBMS session or after timeout when waiting for the MBMS ASSIGNMENT message.

The non-DRX mode periods defined above run independent of each other and may overlap. The non-DRX mode periods have effect only in packet idle mode. In packet idle mode, the mobile station shall be in non-DRX mode during any of the non-DRX mode periods. Otherwise, the mobile station in packet idle mode may be in DRX mode.

If the mobile station establishes an RR connection during any of the non-DRX mode periods, then that period shall continue to run.

An exception case is where a mobile station has enabled PEO or EC operation in which case it shall operate as follows:

– When initiating the MM procedures for GPRS attach and routing area update defined in 3GPP TS 24.008 [51], the mobile station shall enter a zero length MM non-DRX mode period.

– If eDRX has been negotiated (see 3GPP TS 24.008 [51]) then the mobile station shall not request values for the SPLIT_PG_CYCLE or the NON_DRX_TIMER parameter.

– At the transition from packet transfer mode to packet idle mode, the mobile station shall enter a zero-length Transfer non-DRX mode period.

– It may negotiate the use of eDRX or PSM with eDRX. If it has negotiated eDRX or PSM with eDRX then it shall consider eDRX to be supported in all cells in the corresponding Routing Area (i.e. eDRX is negotiated at the Routing Area level).

– If a mobile station that has enabled PEO enters extended uplink TBF mode (see sub-clauses 9.3.1a and 9.3.1b) then it monitors the downlink PACCH starting with the 2nd 52-multiframe following the 52-multiframe in which it received the PACKET UPLINK ACK/NACK message confirming reception of all uplink RLC data blocks. More specifically, when there is no ongoing downlink TBF it monitors radio block [(IMSI mod 1e7) mod 12] in that 52-multiframe and in each subsequent 52-multiframe for a matching PACCH message for as long as it remains in extended UL TBF mode or it receives a matching PACCH message assigning it a downlink TBF.

– If the mobile station in EC operation is indicated to continue monitoring the EC-PACCH in the EC PACKET UPLINK ACK/NACK with the Final Ack Indicator bit set to ‘1’, then it monitors the EC-PACCH, according to its allocated downlink Coverage Class of the TBF, after an initial waiting time as indicated in the EC PACKET UPLINK ACK/NACK message. The mobile station then monitors the EC-PACCH, using a monitoring pattern as indicated in the EC PACKET UPLINK ACK/NACK message, for as long as timer T3238 is running.

– A mobile station that has enabled EC operation and negotiated eDRX shall monitor the EC-CCCH according to the selected downlink Coverage Class and the negotiated eDRX value, see 3GPP TS 45.008. If no eDRX value has been negotiated, the mobile station shall monitor the EC-CCCH according to the selected downlink Coverage Class and the lowest eDRX value. While in packet idle mode with the Ready timer running a mobile station that has enabled EC operation shall always use the lowest eDRX cycle (see 3GPP TS 45.002 [13]).

– A mobile station that has enabled PEO uses the lowest eDRX cycle (see 3GPP TS 45.002 [13]) while the Ready timer is running. If eDRX has been negotiated then upon expiration of the Ready timer the mobile station enters the eDRX based power saving state and uses its negotiated eDRX (see 3GPP TS 45.002 [13]).

– If PSM has been negotiated (see 3GPP TS 24.008 [51]) it starts the active timer upon expiration of the ready timer. While the active timer is running it remains reachable using the eDRX value last negotiated with the network. If no eDRX value has been negotiated then it uses the DRX cycle applicable to the serving cell while the Active timer is running. When the active timer expires the mobile station enters the PSM based power saving state and will not be reachable until the next time it performs an uplink data transfer.

5.5.1.6 Page mode procedures on PCCCH

The network sends page mode information in all downlink message on PCCCH (and PACCH, see note). The page mode information controls possible additional requirements on a mobile station receiving the message.

NOTE: PCCCH, PDTCH and PACCH may be operated in frame stealing mode on the same PDCH. A mobile station in packet idle mode or MAC-Idle state shall consider any RLC/MAC control message received in such a radio block as belonging to PCCCH. A mobile station in packet transfer mode, dual transfer mode, MAC-Shared state or MAC-DTM state shall consider any RLC/MAC control message received as belonging to PACCH.

A mobile station in packet transfer mode, dual transfer mode, MAC-Shared state or MAC-DTM state shall not consider the page mode information received in any message that is received on a PDCH.

A mobile station in packet idle mode or MAC-Idle state shall take into account the page mode information in any message received in a radio block on PCCCH corresponding to its paging group. The mobile station shall not take into account the page mode information in a message received in any other radio block than those corresponding to its paging group. The requirements yielded by the page mode information are as follows:

– normal paging: no additional requirements;

– extended paging: the mobile station is required in addition to receive and analyse the possible message in the third block period on PCCCH where paging may occur (PPCH), following the block corresponding to MS’s paging group;

– paging reorganization: The mobile station shall receive all messages on the PCCCH regardless of the BS_PAG_BLKS_RES setting. It is required to receive all PBCCH messages. When the mobile station receives the next message to its (possibly new) paging group, subsequent action is defined by the page mode information in that message;

– same as before: no change of page mode from the previous page mode.

Note that a mobile station takes into account the page mode information only in packet idle mode or MAC-Idle state and only in messages received in a radio block corresponding to its paging group, whatever the currently applied requirements are (normal paging, extended paging or paging reorganization).

When the mobile station selects a new PPCH, the initial page mode in the mobile station shall be set to paging reorganization. If an RLC/MAC block in a paging sub-channel does not contain page mode information, or if it is not received correctly, the default page mode information is same as before.

5.5.1.7 Frequency Parameters

Frequency parameters may be included in the packet assignment messages (i.e., PACKET DOWNLINK ASSIGNMENT, MULTIPLE TBF DOWNLINK ASSIGNMENT, PACKET UPLINK ASSIGNMENT, MULTIPLE TBF UPLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE, MULTIPLE TBF TIMESLOT RECONFIGURE or PACKET CS RELEASE INDICATION messages) or in the PS HANDOVER COMMAND message and define the training sequence codes(s) (TSC) and the radio frequency channels or set of radio frequency channels the mobile station is to use during the assigned TBF(s). The first packet assignment message, sent to the mobile station when it enters packet transfer mode or MAC-Shared state, shall include the frequency parameters. Subsequent packet assignment messages, sent to the mobile station during packet transfer mode or MAC-Shared state, may omit the frequency parameters. If a mobile station receives a subsequent packet assignment message, during packet transfer mode or MAC-Shared state, without the frequency parameters, the mobile station shall continue to use the previously assigned frequency parameters.

A packet assignment message, when sent to a mobile station in dual transfer mode or MAC-DTM state, shall not include the frequency parameters for the carrier supporting the dedicated resources in a Downlink Dual Carrier configuration. If the network intends to change the frequency allocation of the carrier supporting the dedicated resources for a mobile station in dual transfer mode or MAC-DTM state, the network may use the DTM assignment procedure defined in 3GPP TS 44.018.

If the network and mobile station both support Downlink Dual Carrier, the network may send a packet assignment message or a PS HANDOVER COMMAND message to a mobile station specifying packet resources for one or more TBFs on two carriers (referred to as carrier 1 and carrier 2) and thereby establish a Downlink Dual Carrier configuration. If the packet assignment message is sent to a mobile station in packet idle mode, this message shall include frequency parameters for both carriers. If this message is sent to a mobile station which is in packet transfer mode (and is not in a Downlink Dual Carrier configuration) the assignment message shall either:

– provide new frequency parameters for both carriers, or

– provide frequency parameters for only one carrier (carrier 2) in which case the frequency parameters for carrier 1 remain unchanged.

Subsequent packet assignment messages sent to a mobile station in a Downlink Dual Carrier configuration may:

– include frequency parameters which correspond to the frequency parameters already in use for one or both carriers; or

– provide no new frequency parameters, in which case the existing parameters continue to apply; or

– provide new frequency parameters for both carriers; or

– provide new frequency parameters for only one carrier, in which case the frequency parameters for the other carrier remain unchanged.

If the network and mobile station both support Downlink Multi Carrier, the network may send a packet assignment message (i.e. PACKET DOWNLINK ASSIGNMENT or PACKET TIMESLOT RECONFIGURE messages) or a PS HANDOVER COMMAND message to a mobile station specifying packet resources that establish a DLMC configuration. The PS HANDOVER COMMAND message shall always provide new frequency parameters for use in the new cell whereas the packet assignment message may:

– provide new frequency parameters for all newly assigned and existing carriers, or

– provide new frequency parameters for all newly assigned carriers, modify the frequency parameters for a subset of the existing carriers and leave the frequency parameters for the remaining existing carriers unchanged.

When a mobile station has resources assigned on only one carrier then, for the purposes of subsequent packet assignment messages, that carrier shall be considered carrier 1. A subsequent packet assignment message may assign resources on a second carrier, thereby establishing a Downlink Dual Carrier configuration; in this case, the packet assignment message shall provide frequency parameters for a second carrier (carrier 2) for use in a Downlink Dual Carrier configuration. Similarly, a subsequent packet assignment message may assign resources on one or more additional carriers, thereby establishing a DLMC configuration; in this case, the packet assignment message shall provide DLMC frequency parameters as required for use in a DLMC configuration.

A packet assignment message sent to a mobile station in packet transfer mode may specify frequency parameters for one or (in the case of a mobile station with a downlink dual carrier configuration) both carriers which are different from those currently in effect for that mobile station only in the following cases:

a) the assignment message is a PACKET TIMESLOT RECONFIGURE or MULTIPLE TBF TIMESLOT RECONFIGURE message.

b) the assignment message is a PACKET DOWNLINK ASSIGNMENT message (respectively PACKET UPLINK ASSIGNMENT message) being sent to a mobile station which has no ongoing uplink (respectively downlink) TBF(s).

c) the assignment message is a MULTIPLE TBF DOWNLINK ASSIGNMENT message (respectively MULTIPLE TBF UPLINK ASSIGNMENT message) being sent to a mobile station which is or, after this assignment, will be in a downlink dual carrier configuration and has no ongoing uplink (respectively downlink) TBF(s); in this case, the ongoing downlink (respectively uplink) TBFs are implicitly reassigned on the new frequency parameters with all other parameters for those TBFs unchanged.

d) the assignment message is a PACKET DOWNLINK ASSIGNMENT message (respectively PACKET UPLINK ASSIGNMENT message) sent to a mobile station with a downlink dual carrier configuration, where the frequency parameters for only one carrier are changed, and where no ongoing uplink (respectively downlink) TBF(s) had resources assigned on that carrier.

In cases c) and d) above, a format of the message which includes the Carrier ID field shall be used.

When assigning resources on one carrier to a mobile station which is currently in a Downlink Dual Carrier configuration using a format of the message which does not include the Carrier ID field, the network shall always include frequency parameters; if one or more TBFs which are ongoing are not explicitly addressed in the packet assignment message and will remain ongoing after the new assignment, the included frequency parameters shall be those in use for either carrier 1 or carrier 2.

A packet assignment message sent to a mobile station in packet transfer mode with a DLMC configuration may specify frequency parameters for one or more carriers which are different from those currently in effect for that mobile station only in the following cases:

a) the assignment message is a PACKET TIMESLOT RECONFIGURE message.

b) the assignment message is a PACKET DOWNLINK ASSIGNMENT message sent to a mobile station which has no ongoing uplink TBF.

c) the assignment message is a PACKET DOWNLINK ASSIGNMENT message sent to a mobile station which has an ongoing uplink TBF, subject to the restriction that all existing carriers on which USF is monitored remain assigned.

d) the assignment message is a PACKET UPLINK ASSIGNMENT message for the case where the ongoing downlink TBF is not modified.

Frequency parameters used for EC TBFs are specified in the EC SYSTEM INFORMATION TYPE 1 message, sent on the EC-BCCH, see 3GPP TS 44.018. The frequency parameters are included in EC Mobile Allocation sets, each set consisting of:

– radio frequencies (ARFCNs), HSN and MAIO, for a hopping radio frequency channel; or

– a single ARFCN, for a non-hopping radio frequency channel.

The frequency parameters for a specific EC TBF are assigned in the packet assignment messages (i.e. EC IMMEDIATE ASSIGNMENT TYPE 1, EC IMMEDIATE ASSIGNMENT TYPE 2, EC DOWNLINK ASSIGNMENT, EC PACKET DOWNLINK ASSIGNMENT or EC PACKET UPLINK ASSIGNMENT message). The packet assignment messages then includes a reference to one of the EC Mobile Allocation sets in the EC SYSTEM INFORMATION TYPE 1 message and a definition of the training sequence code (TSC) to use for the EC TBF.

The Frequency Parameters information element is defined in sub-clause 12.8 and the Dual Carrier Frequency Parameters information element is defined in sub-clause 12.8.2 and the DLMC Frequency Parameters information element is defined in sub-clause 12.8.4. The frequency parameters may use an ARFCN defining a non-hopping radio frequency channel, or use the indirect encoding, direct encoding 1 or direct encoding 2 defining a hopping radio frequency channel.

The indirect encoding defines the assigned set of radio frequency channels by referencing information stored within the mobile station. Such information may be received on PBCCH or BCCH (see sub-clauses 5.5.2.1, 11.2.19, 12.8 and 12.10a), or be received in a previous assignment message using one of the direct encoding options. An MA_NUMBER identifies which of up to eight stored sets of frequency parameters is to be used. The MA_NUMBER shall use the following coding:

MA_NUMBER = 0-13 shall be used to reference a GPRS mobile allocation received in a PSI2 message;

MA_NUMBER = 14 shall be used to reference a GPRS mobile allocation received in a SI13 or PSI13 message;

MA_NUMBER = 15 shall be used to reference a GPRS mobile allocation received in a previous assignment message using the direct encoding.

When the indirect encoding is used, the network may include a CHANGE_MARK_1 and a CHANGE_MARK_2 in the Frequency Parameters information element. The mobile station shall then verify that it is using a set of PBCCH or BCCH information identified by a PSI or SI change mark corresponding to one of the CHANGE_MARK_1 or 2 parameters, for the decoding of the frequency information. If that is not the case, an abnormal condition occurs.

The direct encoding defines the assigned set of radio frequency channels by using information contained within the assignment message. The direct encoding 1 references the cell allocation or reference frequency lists received on PBCCH for the decoding of this information. The direct encoding 2 is self contained. When the direct encoding 1 or 2 is used, the mobile station shall store the received GPRS mobile allocation for possible later reference in an assignment message using the indirect encoding. Such reference shall be made using the MA_NUMBER = 15.

NOTE: If there is a GPRS mobile allocation associated with MA_NUMBER = 15, the association shall be kept unchanged if the mobile station receives a packet assignment using the indirect encoding (referencing any value of the MA_NUMBER), the frequency parameters are not included in the packet assignment (i.e., in packet transfer mode, dual transfer mode, MAC-Shared state or MAC-DTM state) or the mobile station establishes an RR connection (for A/Gb mode) or is allocated a DBPSCH (for Iu mode).

For the decoding of frequency parameters, the mobile station shall be able to store the following frequency information (see sub-clauses 11.2.19, 12.8 and 12.10a):

– four Reference Frequency Lists received in the PSI2 information and the corresponding RFL_NUMBERs for identification, each RFL having a contents length of up to 18 octets;

– a Cell Allocation received in the PSI2 information referencing up to four RFLs;

– seven GPRS Mobile Allocations received in the PSI2 or the SI13/PSI13 information and the corresponding MA_NUMBERs for identification, each GPRS Mobile Allocation information element having a length of up to 12 octets (96 bits); and

– one GPRS mobile allocation received in an assignment message using direct encoding 1 or 2, consisting of either a GPRS Mobile Allocation information element having a length of up to 12 octets (96 bits) or a MA Frequency List having a contents length of up to 18 octets.

The mobile station shall be able to store the frequency information for the PCCCH description corresponding to its own PCCCH_GROUP (see sub-clause 11.2.19).

If the mobile station supports SMSCB, it shall be able to store the frequency information for the CBCH to be used in packet idle mode or MAC-Idle state.

The frequency information that the mobile station has stored while camping on a cell shall be deleted when the mobile station reselects a new cell.

5.5.1.8 TLLI management

In case the mobile station receives a message assigning a new P-TMSI from the network during the contention resolution procedure, the mobile station shall continue to use the old TLLI until the contention resolution is completed.

After contention resolution the mobile station shall apply new TLLI in RLC/MAC control block if the mobile has received a new P-TMSI.

The BSS shall not include TLLI within RLC/MAC control messages it sends to a mobile station in packet transfer mode.

5.5.1.9 Packet Flow Context (PFC)

Packet Flow Context (PFC) procedures are described in 3GPP TS 23.060. A Packet Flow Identifier (PFI) is used to identify a PFC.

Mobile station support of packet flow context (PFC) procedures is indicated in the MS Network Capability IE (see 3GPP TS 24.008). Network support of packet flow context (PFC) procedures is indicated by the PFC_FEATURE_MODE parameter that is broadcast on either the BCCH or PBCCH. If the PFC_FEATURE_MODE field indicates that the network does not support PFC procedures then a mobile station shall not indicate a PFI value during uplink TBF establishment. If the PFC_FEATURE_MODE field indicates that the network supports PFC procedures then a mobile station may indicate a PFI value during uplink TBF establishment. The PFI value identifies the initial PFC used during the TBF.

If the network or the mobile station indicates it supports multiple TBF procedures (see sub-clause 7.0) then it shall also indicate support for PFC procedures. When the network and the mobile station both support multiple TBF procedures then the mobile station shall indicate the PFI value associated with each uplink TBF it attempts to establish and the network shall indicate the PFI value associated with each downlink TBF it attempts to establish.

If the network or the mobile station indicates it supports Enhanced Multiplexing for Single TBF (see sub-clause 5.10) then it shall also indicate support for PFC procedures. The mobile station supporting EMST shall indicate the PFI value associated with each RLC entity it requests to establish on an uplink TBF if the network indicates the support of PFC procedures. When EMST is used on a given TBF, the network shall always indicate the PFI value associated with each RLC entity it establishes on that TBF.

EMSR requires the support of PFC procedures in both the network and the mobile station (see sub-clause 5.10). A mobile station that supports EMSR shall always indicate the PFI value associated with each PFC for which it requests resources from a network that supports PFC procedures. A network that supports EMSR shall always indicate the PFI value associated with each PFC it establishes on a given RLC entity when sending an assignment message to a mobile station that supports EMSR (see sub-clause 5.2.2).

A network or mobile station that supports PS handover or DTM handover shall also support PFC procedures.

In case no valid PFI value is assigned for the LLC data to be transmitted, and the network indicates support for the PFC procedures, an MS supporting PFC procedures shall associate and indicate the following PFI values for the LLC data:

PFI=0 (Best Effort) for user data,

PFI=1 (Signalling) for GMM/SM signalling (LLC SAPI 1), or

PFI=2 (SMS) for Short Message Service (LLC SAPI 7), or

PFI=3 (TOM8) for LLC SAPI 8 data.

5.5.1.10 Acquisition of E-UTRAN Information on the PACCH

An MS that receives a full set of instances of the PACKET MEASUREMENT ORDER message that includes one or more IEs used to provide E-UTRAN related information shall proceed as follows:

– The information provided by all instances of the Repeated E-UTRAN Neighbour Cells IE (alternatively, for an MS supporting extended EARFCNs, all instances of the E-UTRAN NC with extended EARFCNs IE when applicable, see sub-clause 11.2.9b) shall be added to the E-UTRAN Neighbour Cell list built by the last received consistent set of SI2quater message instances, or the last received consistent set of SI23 message instances if SI23 is broadcast in the cell and for a mobile station supporting network sharing (see sub-clause 5.6.3.1a).

– The information provided by all instances of the Repeated E-UTRAN Not Allowed Cells IE for any given frequency shall be used to build a new E-UTRAN Not Allowed Cells list for that frequency.

– The information provided by all instances of the Repeated E-UTRAN PCID to TA mapping IE for any given frequency shall be used to build new E-UTRAN PCID to TA mapping for that frequency.

If an MS receives a full set of instances of the PACKET MEASUREMENT ORDER message that excludes an IE used to provide E-UTRAN related information that was provided within the last received consistent set of SI2quater (or alternatively SI23) message instances (e.g. the Priority and E-UTRAN Parameters Description struct provides a "0" for the E-UTRAN Parameters Description IE), the MS shall resort back to using the corresponding information provided by the last received SI2quater (or alternatively SI23) message (see NOTE 1 and NOTE 2).

If an MS receives a full set of instances of the PACKET MEASUREMENT ORDER message that includes an IE used to provide E-UTRAN related information that was provided within the last received consistent set of SI2quater (or alternatively SI23) message instances but none of the fields associated with the included IE provide any information, the MS shall resort back to using the corresponding information provided by the last received SI2quater (or alternatively SI23) message (see NOTE 1 and NOTE 2).

If an MS receives a full set of instances of the PACKET MEASUREMENT ORDER message that includes an IE used to provide E-UTRAN related information but only a subset of the fields associated with the included IE actually provide information, the MS shall use the fields that provide information to update their corresponding stored parameters and shall use values for the fields for which no information was provided as described in Table 11.2.9b.2 (see NOTE 2).

If an MS receives a full set of instances of the PACKET MEASUREMENT ORDER message that limits the information provided within the Repeated E-UTRAN Not Allowed Cells IE to only providing one or more E-UTRAN frequency indices (i.e. only the E-UTRAN_FREQUENCY_INDEX field contains information), the MS shall ignore this IE.

NOTE 1: If the last received consistent set of SI2quater (or alternatively SI23) message instances has not provided a value for any given E-UTRAN related parameter then the MS uses the default value for that parameter unless otherwise specified.

NOTE 2: An MS that supports extended EARFCNs shall build its E-UTRAN Neighbour Cell list from the E-UTRAN NC with extended EARFCNs IE when included in the PACKET MEASUREMENT ORDER message.

5.5.2 Network side

5.5.2.1 System Information broadcasting

5.5.2.1.1 System information on PBCCH

If PBCCH is present in the cell, the network regularly broadcasts PACKET SYSTEM INFORMATION TYPE (PSI) 1, 2, 3 and 3bis messages, and optionally PSI3ter, PSI3quater and some types of PSI messages on the PBCCH. The PSI 2, PSI 3bis, PSI3 ter, PSI3quater messages and some further types of PSI messages may be broadcast in multiple number of instances. Based on the information broadcast in PSI messages, the mobile station is able to decide whether and how it may gain access to the system via the current cell.

NOTE: The network should take into account the limitations of earlier version of mobile equipments to understand the 3-digit MNC format of the location area identification, see sub-clause 12.23 and 3GPP TS 44.018, table "Location Area Identification .information element".

Instances of the PSI 5 message are broadcast on PBCCH if the mobile stations camping on the cell shall perform measurement reporting, see 3GPP TS 45.008.

Instances of the PSI6 and PSI7 message may be broadcast on the PBCCH if non-GSM broadcast information is transmitted.

The PSI8 message may be broadcast on the PBCCH if additional information (i.e. CBCH configuration and dynamic ARFCN mapping) shall be provided to the mobile station camping on the cell.

The PSI1 message contains the PBCCH_CHANGE_MARK and PSI_CHANGE_FIELD parameters. The value of the PBCCH_CHANGE_MARK may be incremented by one, modulo 8, each time the network makes a change in the PBCCH information. Such change includes any addition, removal or replacement of PSI messages, contents of PSI messages, or change in the scheduling of PSI messages on PBCCH. A change in the contents of the PSI1 message alone shall not be reflected in the PBCCH_CHANGE_MARK. When the PBCCH_CHANGE_MARK is incremented, the PSI_CHANGE_FIELD parameter shall be set to an appropriate value to indicate the nature of the latest change in the PBCCH information.

The network may increment the PBCCH_CHANGE_MARK value by more than one, modulo 8, in order to enforce a complete acquisition of PBCCH information of all mobile stations.

In order to avoid extensive TBF suspensions following an increment of the PBCCH_CHANGE_MARK parameter, the network may send PSI messages on PACCH to mobile stations in packet transfer mode.

The network indicates the support of the PACKET PSI STATUS and EGPRS PACKET CHANNEL REQUEST messages in the PSI1 message.

5.5.2.1.2 System information on BCCH

In addition to the requirements in 3GPP TS 44.018, a SYSTEM INFORMATION TYPE 13 (SI13) message is regularly broadcast by the network on the BCCH to support GPRS. Optionally and if PBCCH is not present in the cell, additional types of SI messages may be broadcast on BCCH. Some of them may be broadcast in multiple number of instances. If PBCCH is present in the cell, only the SI13 message is required on BCCH to support GPRS.

Based on this information, the GPRS mobile station is able to decide whether and how it gains access to the system via the current cell when PBCCH is not present.

The SI13 message contains the BCCH_CHANGE_MARK and SI_CHANGE_FIELD parameters. If PBCCH is not present in the cell, the value of the BCCH_CHANGE_MARK may be incremented by one, modulo 8, each time the network makes a change in the BCCH information. Such change includes any addition, removal or replacement of SI messages, contents of SI messages, or change in the scheduling of SI messages on BCCH. Changes in the contents of the SI13 message shall not to be reflected in the BCCH_CHANGE_MARK. Changes of the contents of the RACH Control Parameters information element alone (see 3GPP TS 44.018) may optionally be reflected in the BCCH_CHANGE_MARK; if reflected, the SI_CHANGE_FIELD parameter may indicate only one of the SI message containing the RACH Control Parameters. When the BCCH_CHANGE_MARK is incremented, the SI_CHANGE_FIELD parameter shall be set to an appropriate value to indicate the nature of the latest change in the BCCH information.

When PBCCH is not present in the cell, the network may increment the BCCH_CHANGE_MARK value by more than one, modulo 8, in order to enforce a complete acquisition of BCCH information of all mobile stations.

If PBCCH is not present in the cell, instances of the SI 18 and SI 20 message may be broadcast on the BCCH if non-GSM broadcast information is transmitted.

The network indicates the support of the PACKET SI STATUS message in the SI13 message.

5.5.2.1.3 System information on PACCH (and other logical channels)

The network may broadcast PSI and SI messages on PACCH. In particular, if a mobile station is busy in packet transfer mode or MAC-Shared state and thus unable to receive the relevant blocks on the broadcast channels (PBCCH or BCCH) for a period longer than 15 seconds, the following requirements apply:

– If PBCCH is present in the cell, the network may broadcast the PSI1 message on PACCH such that the mobile station may receive the PSI1 message at least every 15 s.

– If PBCCH is not present in the cell, the network may broadcast the PSI13 message on PACCH such that the mobile station may receive the PSI13 messages at least every 15 s.

If the network has indicated the use of in-band signalling for a given MBMS radio bearer (with the MBMS In-band Signalling Indicator information element included in the MBMS ASSIGNMENT message in the serving cell and/or in the MBMS NEIGHBOURING CELL INFORMATION message in the old cell), it shall broadcast the full system information on PACCH of that MBMS radio bearer, as described in sub-clause 5.5.2.1.3b.

Furthermore, the network may broadcast PSI messages on PCCCH. In particular, the network may send the PSI1 and PSI13 messages on PCCCH to notify mobile stations in packet idle mode or MAC-Idle state about changes in the PBCCH information or changes of the PBCCH channel description.

If the network supports the PACKET PSI STATUS message and this message is received from a mobile station, the network may schedule the missing PSI messages for that mobile station on PACCH (sub-clause 5.5.1.4.3). Optionally, the missing PSI messages may be sent in one or more instances of the PACKET SERVING CELL DATA message for that mobile station on PACCH.

If the network supports the PACKET SI STATUS message and this message is received from a mobile station, the network may schedule the missing SI messages in one or more instances of the PACKET SERVING CELL DATA message for that mobile station on PACCH (sub-clause 5.5.1.4.3), or, in case the mobile station has indicated in the PACKET SI STATUS message that it supports the PACKET SERVING CELL SI message, the network should use the PACKET SERVING CELL SI messages instead of the PACKET SERVING CELL DATA messages.

If the network supports the SI2n message, it shall always use the PACKET SERVING CELL SI message when broadcasting the SI2n messages on PACCH.

NOTE: This is required due to the fact that the PACKET SERVING CELL SI is a distribution message making it possible for all mobile stations capable of decoding the SI2n message and listening to the PACCH to be able to receive the content.

The network may send the PSI14 message on PACCH to a mobile station in dual transfer mode or MAC-DTM state. The scheduling of the PSI14 message is determined by the network.

If PBCCH is present in the cell and the network changes the contents of any of the PSI messages, it shall set the PSI_CHANGED_IND to "1" in all the PSI14 messages it sends in the next 30 seconds. Otherwise, the PSI_CHANGED_IND shall be set to "0".

When a PSI or SI message is received on PACCH during dual transfer mode, no parameters except those relevant for monitoring possible changes in the contents of SI or PSI messages (e.g. PBCCH_CHANGE_MARK, BCCH_CHANGE_MARK, PSI_CHANGED_IND) shall be applied by the MS for operation in dual transfer mode.

The network may send neighbour cell PSI and SI messages on PACCH in one or more instances of the PACKET NEIGHBOUR CELL DATA message (see sub-clause 8.8.1).

5.5.2.1.3a Rules for (P)SI distribution within Packet Serving Cell Data messages

In order to ensure a consistent distribution and decoding of (P)SI messages contained in PACKET SERVING CELL DATA messages, the following rules shall apply:

– Whenever the network starts sending a set of PACKET SERVING CELL DATA message instances in response to any PACKET (P)SI STATUS message, the first PACKET SERVING CELL DATA message instance shall be started with CONTAINER_INDEX=0. If SI1 is broadcast in the serving cell and the MS has requested the SI1 message, the network shall include the SI1 message as the first SI message contained in the set of PACKET SERVING CELL DATA messages, starting from the message with CONTAINER_INDEX=0. If the MS is able to decode the first SI message contained in the set of PACKET SERVING CELL DATA messages but it was not the SI1 message, the MS shall conclude that SI1 is not broadcast in the serving cell.

– All subsequent instances of a PACKET SERVING CELL DATA message set shall be sent in ascending order of CONTAINER_INDEX value. It is allowed to send a PACKET SERVING CELL DATA message with the same CONTAINER_INDEX value more than once.

– Whenever the MS receives a PACKET SERVING CELL DATA message instance with CONTAINER_INDEX=0 or with a CONTAINER_INDEX value that is less than the CONTAINER_INDEX value of the last received PACKET SERVING CELL DATA message instance, it shall delete any PACKET SERVING CELL DATA message instances it may have stored but it shall keep the already extracted PSI/SI message instances.

– Whenever the MS leaves packet transfer mode, it shall delete any PACKET SERVING CELL DATA message instances it may have stored but it shall keep the already extracted PSI/SI message instances.

NOTE : In order to increase the probability that the MS receives the PACKET SERVING CELL DATA message instances (especially the one with CONTAINER_INDEX =0), the network may poll the MS with a valid RRBP field in the RLC/MAC header of a PACKET SERVING CELL DATA message. Alternatively, the network may repeat the PACKET SERVING CELL DATA message instances one or more times.

5.5.2.1.3b Rules for (P)SI distribution on PACCH of an MBMS radio bearer

If the network has indicated the use of in-band signalling for a given MBMS radio bearer, it shall broadcast on the PACCH the full system information provided on the (P)BCCH:

– In case PBCCH is allocated in the cell, the network shall broadcast the consistent set of PSI messages (it broadcasts on PBCCH), on the PACCH/D of the MBMS radio bearer.

– In case PBCCH is not allocated in the cell, the network shall broadcast the consistent set of SI messages (it broadcasts on the BCCH), on the PACCH/D of the MBMS radio bearer using PACKET SERVING CELL SI messages.

5.5.2.1.4 Consistent sets of system information messages

Certain types of PSI and SI messages are sent on PBCCH and BCCH in a multiple number of instances. If such a PSI or SI message type is sent on (P)BCCH, the mobile station shall receive a consistent set of that type of PSI or SI message. In some cases, more than one type of PSI messages may be joined into one consistent set, see table 5.5.2.1.4.1.

Table 5.5.2.1.4.1: Consistent sets of system information messages

Consistent set / Message Type(s)	Broadcast Channel	Number of instances	PSI or SI change mark parameter	PSI or SI index parameter	PSI or SI count parameter
PSI2	PBCCH	1 – 8	PSI2_CHANGE_MARK (Note 3)	PSI2_INDEX	PSI2_COUNT
PSI3	PBCCH	1	PSI3_CHANGE_MARK
PSI3 bis	PBCCH	1 – 16	PSI3_CHANGE_MARK	PSI3bis_INDEX	PSI3bis_COUNT
PSI3 ter	PBCCH	0 – 16	PSI3_CHANGE_MARK	PSI3ter_INDEX	PSI3ter_COUNT
PSI3 quater	PBCCH	0 – 16	PSI3_CHANGE_MARK	PSI3quater_INDEX	PSI3quater_COUNT
PSI5	PBCCH	0 – 8	PSI5_CHANGE_MARK	PSI5_INDEX	PSI5_COUNT
PSI6	PBCCH	0 – 8	PSI6_CHANGE_MARK	PSI6_INDEX	PSI6_COUNT
PSI7	PBCCH	0 – 8	PSI7_CHANGE_MARK	PSI7_INDEX	PSI7_COUNT
PSI8	PBCCH	0 – 8	PSI8_CHANGE_MARK	PSI8_INDEX	PSI8_COUNT
SI13 (Notes1 and 2)	BCCH	1	SI13_CHANGE_MARK (Note 3)
SI2 ter	BCCH	0 – 8	SI2ter_MP_CHANGE_MARK and SI2ter_3G_ CHANGE_MARK	SI2ter_INDEX	SI2ter_COUNT
SI2 quater	BCCH	0 – 16	BA_IND, 3G_BA_IND and MP_CHANGE_MARK	SI2quater_INDEX	SI2quater_COUNT
SI2n	BCCH	0 – 16	SI2n_CHANGE_MARK	SI2n_INDEX	SI2n_COUNT
SI15	BCCH	0 – 4	DM_CHANGE_MARK	SI15_INDEX	SI15_COUNT
SI18	BCCH	0 – 8	SI18_CHANGE_MARK	SI18_INDEX	None (Note 4)
SI19	BCCH	0 – 8	SI19_CHANGE_MARK	SI19_INDEX	None (Note 4)
SI20	BCCH	0 – 8	SI20_CHANGE_MARK	SI20_INDEX	None (Note 4)
SI21	BCCH	0 – 8	SI21_CHANGE_MARK	SI21_INDEX	SI21_COUNT
SI22	BCCH	0 – 8	SI22_CHANGE_MARK	SI22_INDEX	SI22_COUNT
SI23	BCCH	0 – 8	SI23_CHANGE_MARK	SI23_INDEX	SI23_COUNT
NOTE 1: If the SI13 message provides a GPRS mobile allocation, it shall also provide an SI13_CHANGE_MARK. The SI13_CHANGE_MARK shall be used if the indirect encoding of the frequency information is applied in a packet assignment, referring to the GPRS mobile allocation provided in the SI13 message. There is only one instance of the SI13 message. NOTE 2: The PSI13 message may be received on PACCH. It provides the same information as SI13, including the SI13_CHANGE_MARK. NOTE 3: If PSI2 and SI13 change mark values need to be distinguished, e.g. during an activation or release of PBCCH, the network should assign appropriate values to these parameters. NOTE 4: For SI18, SI19 and SI20 messages, there is no count parameter (see 3GPP TS 44.018).

A consistent set of system information messages is identified by a PSI or SI change mark parameter included in each message in the set. All messages within a consistent set shall have the same value of this parameter.

The total number of system information messages of a certain type within a consistent set is indicated by a PSI or SI count parameter included in each message in the set. The position of a certain message instance within the consistent set of system information messages is indicated by a PSI or SI index parameter.

The PSI or SI count parameter shall have the value N-1, where N is the number of instances of the particular message type present in the consistent set. The PSI or SI index parameter shall have a range from zero to N-1. Different instances of a particular message type in a consistent set shall have different values of the PSI or SI index parameter.

5.5.2.2 Paging

The network is required to send valid RLC data blocks or RLC/MAC control blocks continuously on all subchannels on PCCCH where paging can appear.

NOTE: If RLC data blocks are sent in the blocks on PCCCH where paging may appear, the network uses the coding schemes CS-1 to CS-4, in order to avoid the expiry of the downlink signalling counter for non-EGPRS capable mobile stations (see 3GPP TS 45.002).

5.5.2.3 Network Assisted Cell Change

A cell that supports GPRS (in A/Gb mode) and/or Iu mode shall indicate if CCN is enabled. This shall be indicated on BCCH and on PBCCH in the parameter CCN_ACTIVE (see sub-clause 12.24). The network may also send a PACKET MEASUREMENT ORDER message with the parameter CCN_ACTIVE set to order an individual mobile station to apply the CCN procedures in the serving cell or a PACKET CELL CHANGE ORDER or a PS HANDOVER COMMAND message to order an individual mobile station to apply the CCN procedures in the new cell. This parameter controls the overall enabling of CCN. The network may also indicate in system information messages sent on BCCH and PBCCH and individually in the PACKET MEASUREMENT ORDER or PACKET CELL CHANGE ORDER or PS HANDOVER COMMAND messages whether CCN mode shall be entered towards a particular cell (see sub-clause 8.8.2). A GSM cell that supports PS handover to GAN mode shall ensure that CCN is enabled for all GAN neighbour cells.

The network may also send neighbour cell system information on PACCH to be used by the mobile station at initial access after cell re-selection (see sub-clause 8.8.1).

When the network receives a PACKET CELL CHANGE NOTIFICATION message from the mobile station, the network may respond by sending neighbour cell system information for the proposed cell or another cell and also complete the transmission of ongoing data packets before sending a PACKET CELL CHANGE CONTINUE message (to confirm the proposed cell) or a PACKET CELL CHANGE ORDER message. The neighbour cell information is sent in PACKET NEIGHBOUR CELL DATA messages.

The ARFCN for BCCH and the BSIC identifying a GSM neighbour cell shall be included in the PACKET CELL CHANGE CONTINUE message in case a set of PACKET NEIGHBOUR CELL DATA messages referred by the corresponding CONTAINER_ID value was sent for that cell without ARFCN and BSIC provided. If included by the network in the PACKET CELL CHANGE CONTINUE message, ARFCN and BSIC shall reflect the cell proposed in the PACKET CELL CHANGE NOTIFICATION message. Upon reception of the PACKET CELL CHANGE CONTINUE message the mobile station shall continue the cell reselection in NC0/NC1 mode irrespective of the cell indicated in the ARFCN and BSIC parameters.

5.5.2.4 Packet Switched Handover

Packet switched handover is applicable only in packet transfer mode.

If the network supports PS handover it may initiate the PS handover procedure for a mobile station that supports PS handover as a result of various trigger conditions such as, but not restricted to, the following:

– Upon reception of a PACKET CELL CHANGE NOTIFICATION message from a mobile station operating in NC0.

– Upon reception of a PACKET CELL CHANGE NOTIFICATION message or measurement reports from a mobile station operating in NC1.

– Upon reception of measurement reports from a mobile station operating in NC2.

– Upon determining that resource limitations exist for the serving cell.

– Upon receiving the Service UTRAN CCO IE from the SGSN indicating that a mobile station operating in A/Gb mode would be better served in a cell supporting a different RAT.

For PS handover to a GSM neighbour cell the NC mode applicable to the new cell shall be indicated by the PS HANDOVER COMMAND message sent to the mobile station in the old cell.

5.6 Measurement reports

5.6.0 General

The network may request measurement reports from the MS. The measurement reporting principles are specified in 3GPP TS 45.008. The measurement reports consists of

– Network Control (NC) measurement reports sent when the MS is in A/Gb mode and GMM Ready state (see 3GPP TS 24.008) or the MS is in Iu mode and in RRC-Cell_Shared state; this may be performed with either the PACKET MEASUREMENT REPORT message or the PACKET ENHANCED MEASUREMENT REPORT message.

5.6.1 Network Control (NC) measurement reporting

The behaviour of the mobile station is controlled by the parameter NETWORK_CONTROL_ORDER broadcast in the PSI5 message on PBCCH, in the SI13 and SI2quater messages on the BCCH and in the PSI13 message on PACCH. Alternatively, the network may send the NETWORK_CONTROL_ORDER parameters in a PACKET MEASUREMENT ORDER or in a PACKET CELL CHANGE ORDER message on PCCCH or PACCH to a particular mobile station or in a PS HANDOVER COMMAND message sent on PACCH to a particular mobile station. The parameter NETWORK_CONTROL_ORDER may have one of the values NC0, NC1, NC2 or RESET, see 3GPP TS 45.008.

When in mode NC1 or NC2, the mobile station shall perform the NC measurements as defined in 3GPP TS 45.008. The reporting periods are indicated in the NC_REPORTING_PERIOD_I and NC_REPORTING_PERIOD_T field of the PSI5, the SI2quater, the PACKET CELL CHANGE ORDER or the PACKET MEASUREMENT ORDER message. If NC_NON_DRX_PERIOD, NC_REPORTING_PERIOD_I or NC_REPORTING_PERIOD_T have not been received by the mobile station the default values shall be used. The mobile station shall apply to the timer T3158 either the NC_REPORTING_PERIOD_I when in packet idle mode or the NC_REPORTING_PERIOD_T when in packet transfer mode. The measurement results shall be sent to the network using the procedures specified in sub-clause 7.3 for packet idle mode, and in sub-clause 8.3 for packet transfer mode.

On expiry of timer T3158, the mobile station shall restart timer T3158 with the indicated reporting period, perform the measurements and send either the PACKET MEASUREMENT REPORT message or the PACKET ENHANCED MEASUREMENT REPORT to the network. The condition for sending the PACKET ENHANCED MEASUREMENT REPORT message instead of the PACKET MEASUREMENT REPORT message is based on the REPORT_TYPE parameter and if the MS has received BSIC information for all cells. For the detailed conditions see sub-clauses 11.2.23, 11.2.4 and 11.2.9b and also 3GPP TS 44.018 sub-clause 10.5.2.33b. A mobile station in packet idle mode (respectively packet transfer mode) in NC2 may transmit a PACKET CELL CHANGE NOTIFICATION message, instead of a PACKET MEASUREMENT REPORT message or PACKET ENHANCED MEASUREMENT REPORT message, if the conditions in sub-clause 5.6.3.9 are met, A mobile station shall send no more than one PACKET CELL CHANGE NOTIFICATION per ([4] x NC_REPORTING_PERIOD_I) seconds (respectively ([4] x NC_REPORTING_PERIOD_T) seconds).

A mobile station in mode NC1 or NC2 may receive a new indicated reporting period while timer T3158 is active. If the new indicated reporting period is less than the time to expiry of timer T3158, the mobile station shall immediately restart timer T3158 with the new indicated reporting period. Otherwise, the timer T3158 shall continue to run.

When changing from packet transfer mode to packet idle mode, a mobile station in mode NC1 or NC2 shall restart the timer T3158 with the reporting period determined by the NC_REPORTING_PERIOD_I parameter if at least one PACKET MEASUREMENT REPORT or PACKET ENHANCED MEASUREMENT REPORT message was sent in packet transfer mode. Otherwise the timer T3158 shall continue to run.

When changing from packet idle mode to packet transfer mode, a mobile station in mode NC1 or NC2 shall restart the timer T3158 with the reporting period determined by the NC_REPORTING_PERIOD_T parameter if the reporting period is less than the time to expiry of timer T3158. Otherwise the timer T3158 shall continue to run.

When a mobile station leaves the GMM Ready state, the timer T3158 shall be stopped and no more measurement reports shall be sent to the network.

A mobile station may reselect a new cell or may be ordered to reselect a new cell with mode NC1 or NC2 while timer T3158 is active. If time to expiry of timer T3158 is greater than the indicated reporting period for the new cell, the mobile station shall immediately restart timer T3158 with the indicated reporting period for the new cell. Otherwise, the timer T3158 shall continue to run.

At cell reselection the NC measurement parameters valid for the mobile station in the new cell (NETWORK_CONTROL_ORDER, NC_NON_DRX_PERIOD, NC_REPORTING_PERIOD_I and NC_REPORTING_PERIOD_T) are either:

– brought from the old cell if received in a PACKET CELL CHANGE ORDER message sent in the old cell; or

– received in a broadcast PSI5, SI13, PSI13 or SI2quater message in the new cell. If no parameters have been brought from the old cell, and until individual measurement parameters are received in the new cell, the mobile station shall use the broadcast measurement parameters from PSI5 if a PBCCH is allocated in the cell or SI2quater if a PBCCH is not allocated in the cell or use the default parameter values.

The default frequency list to be applied in the new cell following a cell reselection or the successful completion of the PS handover procedure shall be the BA(GPRS) list of that cell until a new PACKET MEASUREMENT ORDER message is received. For the case of cell reselection the BA(GPRS) list could also have been modified by frequency parameters received in a PACKET CELL CHANGE ORDER message in the old cell.

For (NC) measurements reporting, the Mobile Station shall use PACKET ENHANCED MEASUREMENT REPORT messages instead of PACKET MEASUREMENT REPORT messages if that is indicated by the parameter REPORT_TYPE and if at least one BSIC is allocated to each frequency in the BA(GPRS) list.

For a mobile station supporting UTRAN, reports on 3G cells may also be included in the reporting. For a mobile station supporting "E-UTRAN Neighbour Cell measurements and MS autonomous cell reselection to E-UTRAN", reports on E-UTRAN cells may also be included in the reporting. For report with the PACKET MEASUREMENT REPORT message, reporting is performed on three separate lists: the BA(GPRS), the 3G Neighbour Cell List (for a multi-RAT MS supporting UTRAN) and the E-UTRAN Neighbour Cell List (for a MS supporting "E-UTRAN Neighbour Cell measurements and MS autonomous cell reselection to E-UTRAN"). For report with the PACKET ENHANCED MEASUREMENT REPORT message, reporting is performed on the Neighbour Cell List (defined in sub-clause 5.6.3.3) and the E-UTRAN Neighbour Cell List (for a multi-RAT MS supporting "E-UTRAN Neighbour Cell measurements and MS autonomous cell reselection to E-UTRAN").

A multi-RAT MS supporting UTRAN and/or E-UTRAN with no CSG Whitelist or an empty CSG Whitelist shall not send any measurement reports for cells that are known to be UTRAN/E-UTRAN CSG cells. A multi-RAT MS supporting UTRAN and/or E-UTRAN which is a member of at least one Closed Subscriber Group (i.e. at least one CSG ID is included in its CSG Whitelist) but does not support CSG Cells Reporting shall not send any measurement reports for cells that are known to be UTRAN/E-UTRAN CSG cells other than in a PACKET CELL CHANGE NOTIFICATION message for a CSG cell which is the proposed target cell (see sub-clause 8.8.3).

The reporting of CSG cells and hybrid cells is specified in sub-clause 5.6.3.9.

A mobile station involved in an RR connection (in class A mode of operation), shall not send Network Control measurement reports to the network during that period. The mobile station shall return to the previous reporting mode when the RR connection is released.

5.6.2 (void)

5.6.3 Additional measurement and reporting parameters

Some parameters from the PACKET MEASUREMENT ORDER, PACKET CELL CHANGE ORDER, SI2quater, SI23, PSI3bis, PSI3ter, PSI3quater or PSI5 messages allow to build GPRS Measurement Parameters, GPRS 3G Measurement Parameters, GPRS E-UTRAN Measurement Parameters and neighbour cell lists which are used for Network Control (NC) measurement reporting.

5.6.3.1 Deriving the 3G Neighbour Cell list from the 3G Neighbour Cell description

In a cell without a PBCCH allocated, the 3G Neighbour Cell list is given by one or more instances of the SI2quater message with the same 3G_BA_IND value. If the SI23 message is broadcast in the cell, for a UTRAN capable mobile station supporting network sharing the 3G neighbour Cell list is given by one or more instances of the PACKET MEASUREMENT ORDER message with the same 3G_BA_IND value.

In a cell with a PBCCH allocated, the 3G Neighbour Cell list is given by one or more instances of the PSI3quater message with the same PSI3_CHANGE_MARK value.

The 3G Neighbour cell list may be modified by a PACKET CELL CHANGE ORDER message (in which case the reference list is given on the new cell) or by one or more instances of the PACKET MEASUREMENT ORDER message with the same 3G_BA_IND value as in the SI2quater message or PSI3_CHANGE_MARK value as in the PSI3quater message. A UTRAN capable mobile station supporting network sharing shall build its 3G Neighbour Cell list from the information received in the PACKET CELL CHANGE ORDER message (in which case the 3G Neighbour Cell list is only used in the new cell if the SI23 message is broadcast in the new cell).

The 3G Neighbour Cell list may contain up to 96 3G Neighbour Cells and/or UTRAN frequencies for RSSI reporting.

Each 3G Neighbour Cell Description received is added to the 3G Neighbour Cell list, starting with the index equal to the parameter Index_Start_3G. If this parameter is not present then the value 0 shall be used.

For each 3G Neighbour Cell Description received, the cells / UTRAN frequencies are indexed in the following order:

1: UTRAN FDD cells / UTRAN FDD frequencies: FDD UARFCNs are indexed in the order of occurrence in the 3G Neighbour Cell description. For each FDD UARFCN indicating UTRAN FDD cells, the cells are indexed in the order of increasing values of the decoded FDD_CELL_INFORMATION parameters.

2: UTRAN TDD cells / UTRAN TDD frequencies: TDD UARFCNs are indexed in the order of occurrence in the 3G Neighbour Cell description. For each TDD UARFCN indicating UTRAN TDD cells, the cells are indexed in the order of increasing values of the decoded TDD_CELL_INFORMATION parameters.

If more than one cell / UTRAN frequency with the same index in the 3G Neighbour Cell list are provided by different instances of 3G Neighbour Cell descriptions, the cell / UTRAN frequency from the message instance with the highest index shall be used. In case the same 3G Cell / UTRAN frequency occurs more than once in the resulting 3G Neighbour Cell list, each occurrence shall be assigned an index but only the cell / UTRAN frequency with the highest index in the 3G Neighbour Cell list shall be referred to in measurement reports.

The 3G Neighbour Cell Description may contain information on 3G Neighbour Cells / UTRAN frequencies to be removed (REMOVED_3GCELL_Description). The cells / UTRAN frequencies to be removed are identified by their indices in the 3G Neighbour Cell list. Removed cells / UTRAN frequencies shall keep their indices but no measurement shall be performed. If the index is higher than 95 or points to a 3G cell / UTRAN frequency that does not exist, this shall not be considered as an error.

In a cell without PBCCH allocated, the mobile station shall only combine 3G Neighbour cells / UTRAN frequencies from SI2quater (or PACKET MEASUREMENT ORDER, if the SI23 message is broadcast) message instances indicating the same value of the 3G_BA_IND without any message instance indicating a different value of the 3G_BA_IND received in between.

In a cell with a PBCCH allocated, the mobile station shall only combine 3G Neighbour cells / UTRAN frequencies from PSI3quater messages indicating the same PSI3_CHANGE_MARK value.

If a 3G Neighbour Cell Description includes non-supported frequencies or Radio Access Technologies or if the same cell / UTRAN frequency occurs more than once, this shall not be considered as an error; indices in the 3G neighbour Cell list shall be incremented accordingly. If a cell / UTRAN frequency is provided for an index higher than 95 in the 3G Neighbour Cell list, this shall not be considered as an error; the cell / UTRAN frequency shall not be included in the 3G Neighbour Cell list.

For a mobile station indicating support for UTRA Multiple Frequency Band Indicators (MFBI) in the MS Radio Access Capabilities IE (see 3GPP TS 24.008), the network may send different FDD ARFCN values corresponding to different frequency bands but designating the same physical UTRAN frequency in the PACKET CELL CHANGE ORDER message or in the PACKET MEASUREMENT ORDER message. The network may also broadcast different FDD ARFCN values corresponding to different frequency bands but designating the same physical UTRAN frequency in the SI2quater message; in such a case, a mobile station supporting UTRA Multiple Frequency Band Indicators (MFBI) shall consider a FDD ARFCN value belonging to frequency band it does not support as a non-supported frequency. When a PACKET CELL CHANGE ORDER message or a PACKET MEASUREMENT ORDER message or a SI2quater message is received by the MFBI capable MS, each occurrence of a FDD ARFCN corresponding to different frequency bands but designating the same physical UTRAN frequency shall be assigned an index in the 3G Neighbour Cell list. However, only the highest index in the list that corresponds to a supported frequency band shall be referred to in measurement reports.

The MS behaviour is not specified if the number of 3G frequencies or cells exceeds the MS monitoring capabilities as defined in 3GPP TS 45.008.

5.6.3.1a Deriving the E-UTRAN Neighbour Cell list from the Repeated E-UTRAN Neighbour Cell information

The E-UTRAN Neighbour Cell list is given by one or more instances of the SI2quater message with the same 3G_BA_IND value, or alternatively, if the SI23 message is broadcast in the cell and for a mobile station supporting network sharing, by one or more instances of the SI23 message with the same SI 23_BA_IND value, see 3GPP TS 44.018.

If the mobile station receives a full set of instances of the PACKET MEASUREMENT ORDER message (see sub-clause 11.2.9b) with the same 3G_BA_IND value as in the SI2quater message, each E-UTRAN Parameters Description IE received therein (alternatively, for a mobile station supporting extended EARFCNs, each E-UTRAN NC with extended EARFCNs IE received therein) shall be used to modify the E-UTRAN Neighbour Cell list received from SI2quater. When a mobile station supporting network sharing builds its E-UTRAN Neighbour Cell list from the information received in the SI23 message, this list shall only be modified if the mobile station receives a full set of instances of the PACKET MEASUREMENT ORDER message with the same 3G_BA_IND value as the SI 23_BA_IND value in the SI23 message, in which case each E-UTRAN Parameters Description IE (alternatively, each E-UTRAN NC with extended EARFCNs IE) received therein shall be used to modify the E-UTRAN Neighbour Cell list received from SI23.

If the mobile station supporting extended EARFCNs receives a PACKET MEASUREMENT ORDER message with both Repeated E-UTRAN Neighbour Cell IE and E-UTRAN NC with extended EARFCNs IE included therein, it shall ignore the message.

The E-UTRAN Neighbour Cell list may contain up to 8 E-UTRAN frequencies. Each frequency described by a Repeated E-UTRAN Neighbour Cell IE is added to the E-UTRAN Neighbour Cell list in the order in which they appear in the message. Different instances of the Repeated E-UTRAN Neighbour Cells IE shall be evaluated in ascending order of the PMO_INDEX of the PACKET MEASUREMENT ORDER message that they are received in.

In case the same E-UTRAN frequency occurs more than once in the resulting E-UTRAN Neighbour Cell list, each occurrence shall be assigned an index but only the E-UTRAN frequency with the highest index in the E-UTRAN Neighbour Cell list shall be referred to in measurement reports.

For a mobile station indicating support for E-UTRA Multiple Frequency Band Indicators (MFBI) in the MS Radio Access Capabilities IE (see 3GPP TS 24.008), the network may send different EARFCN values corresponding to different frequency bands but designating the same physical E-UTRAN frequency in the PACKET MEASUREMENT ORDER message. The network may also broadcast different EARFCN values corresponding to different frequency bands but designating the same physical E-UTRAN frequency in the SI2quater message or SI23 message; in such a case, a mobile station supporting E-UTRA Multiple Frequency Band Indicators (MFBI) shall consider an EARFCN value belonging to frequency band it does not support as a non-supported frequency. When a PACKET MEASUREMENT ORDER message or a SI2quater message or a SI23 message is received by the MFBI capable MS, each occurrence of an EARFCN corresponding to different frequency bands but designating the same physical E-UTRAN frequency shall be assigned an index in the E-UTRAN Neighbour Cell list. However, only the highest index in the list that corresponds to a supported frequency band shall be referred to in measurement reports.

The mobile station behaviour is not specified if the number of E-UTRAN frequencies exceeds the MS monitoring capabilities as defined in 3GPP TS 45.008.

NOTE 1: Multiple instances of a PACKET MEASUREMENT ORDER message may be received as described in sub-clause 11.2.9b.

5.6.3.2 Deriving BA(GPRS) and the GSM Neighbour Cell list

In a cell without a PBCCH allocated, BA(GPRS) is equal to the BA (list) from the SI2/SI2bis/SI2ter messages. BSICs from the GPRS BSIC Description from one or more instances of the SI2quater message (if broadcast) shall be associated with BA(GPRS) with the same BA_IND value to create the GSM Neighbour Cell list, as described in 3GPP TS 44.018 (sub-clause 3.4.1.2.1.2). When the mobile station has acquired the GSM Neighbour Cell list, the mobile station shall include in the measurement reports only cells present in that list. If GPRS BSIC Description is not broadcast, the GSM Neighbour Cell list is equal to BA(GPRS) (only a frequency list).

In a cell with a PBCCH allocated, BA(GPRS) is derived from the neighbour cell parameters sent in PSI3 and ascending order of PSI3bis on PBCCH with the same PSI3_CHANGE_MARK value (see sub-clause 11.2.20). Each neighbour cell listed in PSI3 and in one or more instances of PSI3bis is assigned an ascending index used for measurement reports. The first neighbour cell in PSI3 has the lowest index (= 0), and the last neighbour cell in the highest indexed PSI3bis message has the highest index. The GSM Neighbour Cell list is equal to BA(GPRS).

The GSM Neighbour Cell list may contain up to 96 GSM Neighbour Cells. The total number of frequencies to measure shall not exceed 32. If the list includes more than 32 frequencies, the MS shall only measure the 32 frequencies with the lowest indices.

The GSM Neighbour Cell list may be modified by "NC Frequency List" in a PACKET CELL CHANGE ORDER message (in which case the reference list is given on the new cell) or one or more instances of the PACKET MEASUREMENT ORDER message with the same BA_IND value or PSI3_CHANGE_MARK value.

The "NC Frequency List" may add cells to the GSM Neighbour Cell list (see sub-clauses 11.2.4 and 11.2.9b). These cells shall be added at the end of the GSM Neighbour Cell list and indexed in the order of occurrence within the PACKET CELL CHANGE ORDER message or ascending instances of the PACKET MEASUREMENT ORDER message. The list of added cells may contain GPRS and optionally Iu mode cell re-selection parameters. The "NC Frequency List" does not impact the serving cell parameters.

The "NC Iu Mode Only Capable Cell List" may add cells to the GSM Neighbour Cell list (see sub-clauses 11.2.4 and 11.2.9b). These Iu mode only capable cells shall be added at the end of the GSM Neighbour Cell list after A/Gb mode or both A/Gb and Iu mode capable cells and indexed in the order of occurrence within the PACKET CELL CHANGE ORDER message or ascending instances of the PACKET MEASUREMENT ORDER message. The list of added cells may contain Iu mode only cell re-selection parameters.

In case the same cell (ARFCN+BSIC) or the same ARFCN without BSIC occur more than once in the resulting GSM Neighbour Cell list, each occurrence shall be assigned an index but only the cell with the highest index shall be used for cell re-selection and referred to in measurement reports.

The "NC Frequency List" may delete frequencies from the BA(GPRS) list (see sub-clause 11.2.9b). The frequencies to be removed are identified by their indices in the BA(GPRS). In this case all cells associated with the removed frequencies shall be removed from the GSM Neighbour Cell list. Removed cells/frequencies shall keep their indices but no measurements or reporting shall be performed. If the index points to a cell that does not exist, this shall not be considered as an error.

If the mobile station receives a PACKET MEASUREMENT ORDER message (full set of instances) with changed PMO_IND parameter value, any old "NC frequency list" shall be deleted. If the last PACKET MEASUREMENT ORDER message (full set of instances) does not contain a "NC frequency list" (no added or deleted frequencies) the mobile station shall return to BA(GPRS).

In a cell without PBCCH allocated, if the BA_IND parameter is changed, the mobile station shall re-read and rebuild the GSM Neighbour Cell list.

In a cell with a PBCCH allocated, if PSI3_CHANGE_MARK is changed, the mobile station shall re-read and rebuild the GSM Neighbour Cell list.

5.6.3.3 Deriving the Neighbour Cell list from the GSM Neighbour Cell list and the 3G Neighbour Cell list

The Neighbour Cell list may contain up to 96 Neighbour Cells. For report with the PACKET ENHANCED MEASUREMENT REPORT message, the Neighbour Cell list is the concatenation of the GSM Neighbour Cell list and the 3G Neighbour Cell list (if any). In this concatenation the value of the parameter Absolute_Index_Start_EMR is added to the 3G Neighbour Cell list indices. If the same index occurs for a GSM Cell and a 3G Cell, the GSM Cell shall be used.

NOTE: For report with the PACKET MEASUREMENT REPORT message, the concatenated list is not used. Instead, the two lists are used separately, as defined in table 11.2.9.2 from sub-clause 11.2.9.

5.6.3.4 GPRS Real Time Differences

The GPRS Real Time Difference list may contain up to 96 Real Time Difference parameters.

In a cell without PBCCH allocated, GPRS Real Time Difference information may be received from the SI2quater message and associated with the BA (list) from the SI2/SI2bis/SI2ter messages with the same BA_IND value, see 3GPP TS 44.018. Each frequency in the BA (list) may be associated to 0, 1 or more Real Time Difference parameters. The Real Time Difference parameters may be received before the corresponding BA (list). The parameter BA_Index_Start_RTD in each structure indicates the index of the frequency in the BA (list) to be taken as a starting reference. A sub-structure is included for each frequency referenced. Each of those sub-structures indicates if 0, 1 or more RTD parameters are present for this frequency. If a frequency in the BA (list) is not provided with Real Time Difference information by any of the message instances with correct BA_IND value, it shall be assumed that no information is available for that frequency. If the MP_CHANGE_MARK parameter is changed, the mobile station shall re-read the Real Time Difference parameters.

In a cell with a PBCCH allocated, GPRS Real Time Difference information may be received from the PSI3ter messages and associated with the GSM Neighbour Cell list with the same PSI3_CHANGE_MARK value. In this case each cell may be associated to 0 or 1 Real Time Difference parameter. The Real Time Difference parameters may be received before the corresponding GSM Neighbour Cell list. The parameter Cell_Index_Start_RTD in each structure indicates the index of the cell in the GSM Neighbour Cell list to be taken as a starting reference. A sub-structure is included for each GSM Neighbour Cell referenced. Each of those sub-structures indicate if 0 or 1 RTD parameter is present for this GSM Neighbour Cell. If a cell in the GSM Neighbour Cell list is not provided with Real Time Difference information by any of the message instances with correct PSI3_CHANGE_MARK value, it shall be assumed that no information is available for that cell. If some Real Time Difference information are provided for a cell that does not exist, this shall not be considered as an error. See sub-clause 11.2.21.

5.6.3.5 GPRS Report Priority Descriptions

In a cell without PBCCH allocated, Report Priority information may be received from the SYSTEM INFORMATION TYPE 2 QUATER message and associated to the Neighbour Cell list with the same BA_IND value and 3G_BA_IND value, see 3GPP TS 44.018. If the parameter MP_CHANGE_MARK is changed, the mobile shall re-read the GPRS Report Priority information. Each REP_PRIORITY bit of this field relates to indices of the Neighbour Cell list starting with index 0.

In a cell with a PBCCH allocated, Report Priority information for GSM cells may be received from the PACKET SYSTEM INFORMATION TYPE 3 TER message and associated to the GSM Neighbour Cell list with the same PSI3_CHANGE_MARK value, see sub-clause 11.2.21a. Each REP_PRIORITY bit of this field relates to indices of the GSM Neighbour Cell list starting with index 0.

In a cell with a PBCCH allocated, Report Priority information for 3G cells may be received from the PACKET SYSTEM INFORMATION TYPE 3 QUATER message and associated to the 3G Neighbour Cell list with the same PSI3_CHANGE_MARK value, see sub-clause 11.2.21b. Each REP_PRIORITY bit of this field relates to indices of the 3G Neighbour Cell list starting with index 0.

If Report Priority information is received as part of a PACKET MEASUREMENT ORDER or PACKET CELL CHANGE ORDER message, it is associated to the Neighbour Cell list and may be received before the corresponding Neighbour Cell list. Each REP_PRIORITY bit of this field relates to indices of the Neighbour cell list, starting with index 0.

Indices exceeding the value 95 shall be ignored. If there are fewer indices than the number of Neighbour Cells, the value 0 shall be assumed for the missing bits.

5.6.3.6 GPRS Measurement Parameters and GPRS 3G Measurement Parameters

In a cell without a PBCCH allocated, GPRS Measurement Parameters, GPRS 3G Measurement Parameters and 3G Priority Parameters may be received from SI2quater message, see 3GPP TS 44.018. When the parameter MP_CHANGE_MARK is changed, the mobile station shall re-read GPRS Measurement Parameters and GPRS 3G Measurement Parameters and 3G Priority Parameters.

In a cell with a PBCCH allocated, GPRS Measurement Parameters and GPRS 3G Measurement Parameters may be received from PSI3quater and PSI5 messages, see sub-clauses 11.2.21b and 11.2.23. Additionally, 3G Priority Parameters may also be received from PSI3quater messages. When the PSI5_CHANGE_MARK parameter is changed, the MS shall re-read the corresponding Measurement Parameters and 3G Measurement Parameters. When the PSI3_CHANGE_MARK parameter is changed, the MS shall re-read the corresponding Measurement Parameters, 3G Priority Parameters and 3G Measurement Parameters.

If different values are received for the same parameter in different instances of a message, only the value in the instance with the highest index shall be used.

5.6.3.6a GPRS E-UTRAN Measurement Parameters

This sub-clause applies only to an E-UTRAN capable mobile station.

GPRS E-UTRAN Measurement Parameters may be received from SI2quater message, see 3GPP TS 44.018.

GPRS E-UTRAN Measurement Parameters may be modified by one or more instances of the PACKET MEASUREMENT ORDER message with the same 3G_BA_IND value as the SI2quater message.

If different values are received for the same parameter in different instances of the PACKET MEASUREMENT ORDER message, only the value in the instance with the highest index shall be used.

5.6.3.7 The GPRS 3G Cell Reselection list

This sub-clause applies only to a (3G) multi-RAT MS.

In a cell without a PBCCH allocated, the GPRS 3G Cell Reselection list is equal to the 3G Cell Reselection list that is defined in 3GPP TS 44.018.

In a cell with a PBCCH allocated, the GPRS 3G Cell Reselection list is the union of 3G Cells and/or 3G frequencies provided in one or more instances of the PSI3quater message. The GPRS 3G Cell Reselection list may contain up to 96 3G Cells. 3G Cells not provided explicitly in the PSI3quater message (frequencies on their own) are not included in these 96 cells. Up to 8 frequencies on their own can be added to these 96 cells.

The MS behaviour is not specified if the number of 3G frequencies or cells exceeds the MS monitoring capabilities as defined in 3GPP TS 45.008.

When the 3G Neighbour Cell list is modified by a PACKET CELL CHANGE ORDER message or by one or more instances of the PACKET MEASUREMENT ORDER message with the same 3G_BA_IND value as in the SI2quater message, the GPRS 3G Cell Reselection list shall be updated according to the modified 3G Neighbour Cell list. A UTRAN capable mobile station supporting network sharing shall build its 3G Cell Reselection list from the information received in the PACKET CELL CHANGE ORDER message (in which case the 3G Cell Reselection list is only used in the new cell if the SI23 message is broadcast in the new cell).If SI23 is broadcast in the cell and for a mobile station supporting network sharing, the 3G Cell Reselection list shall only be modified by one or more instances of the PACKET MEASUREMENT ORDER message with the same 3G_BA_IND value as the SI 23_BA_IND value broadcast in the SI23 message.

NOTE: Frequencies for which the parameter NR_OF_FDD_CELLS is set to 0 (and FDD_Indic0 is set to 0) or NR_OF_TDD_CELLS is set to 0 (and TDD_Indic0 is set to 0) are not added to the GPRS 3G Cell Reselection list. They are added to the 3G Neighbour Cell list and are only used for RSSI reporting (subject to the restrictions given in 3GPP TS 45.008). Frequencies for which NR_OF_FDD_CELLS is set to a value from 17 to 31 or NR_OF_TDD_CELLS is set to a value from 21 to 31 are not added to the 3G Cell Reselection list (see sub-clause 11.2.9b).

5.6.3.7a (void)

5.6.3.7b The 3G Frequency list

The 3G Frequency list consists of the set of UTRAN frequencies contained in the GPRS 3G Cell Reselection list or in the 3G Neighbour Cell list, depending on which list is being used by the mobile station. The 3G Frequency list is constructed as specified in 3GPP TS 44.018.

When the 3G Neighbour cell list is modified (e.g. by a PACKET CELL CHANGE ORDER message or by one or more instances of the PACKET MEASUREMENT ORDER message), the 3G Frequency list shall be updated.

5.6.3.8 Closed Subscriber Group Information

This applies only to a multi-RAT MS supporting UTRAN and/or E-UTRAN. One or more instances of the SI2quater or the PACKET MEASUREMENT ORDER message may provide the E-UTRAN CSG Description IE and/or the 3G CSG Description IE. An MS supporting cell reselection to UTRAN and/or E-UTRAN shall use this information as described in 3GPP TS 45.008.

If an MS receives a CSG_PSC_SPLIT IE and/or a CSG_PCI_SPLIT IE it shall store this information and shall consider it as being valid for the specified frequencies for a period of up to 24 hours or until a new CSG_PSC_SPLIT IE and/or a new CSG_PCI_SPLIT IE is received, whichever occurs first.

Any valid "CSG PSC Split Information" received from a UTRAN frequency and stored by the mobile station shall take precedence over the information received from the CSG_PSC_SPLIT IE for that frequency. Any valid "CSG PCI Split Information" received from an E-UTRAN frequency and stored by the mobile station shall take precedence over the information received from the CSG_PCI_SPLIT IE for that frequency.

5.6.3.9 Reporting of CSG Cells and Hybrid Cells

A multi-RAT mobile station in packet transfer mode may report a CSG cell or a detected hybrid cell in a PACKET MEASUREMENT REPORT or PACKET ENHANCED MEASUREMENT REPORT message (see sub-clause 5.6.1) if all of the following conditions are met:

– the mobile station supports "UTRA (respectively E-UTRA) CSG Cells Reporting";

– the CSG Whitelist (see 3GPP TS 23.122) of the mobile station is not empty;

– the UTRAN CSG Cells Reporting Description IE (respectively E-UTRAN CSG Cells Reporting Description IE) has been received from the network (see subclause 5.6.1);

– the mobile station has determined that it is allowed to access the cell, i.e. the CSG ID and the PLMN ID of the CSG cell matches one of the CSG IDs with their associated PLMN IDs stored in its CSG Whitelist and the PLMN ID of the CSG cell matches the PLMN ID in the RAI received during latest registration or registration update with PS domain or that of an equivalent PLMN;

– the reporting criteria specified in 3GPP TS 45.008 are met.

Under these conditions, the mobile station may report a E-UTRAN or UTRAN CSG cell or detected hybrid cell by including the E-UTRAN CSG Measurement Report IE or the UTRAN CSG Measurement Report IE in the PACKET MEASUREMENT REPORT or the PACKET ENHANCED MEASUREMENT REPORT message.

If one or more of these conditions are not met the multi-RAT mobile station in packet transfer mode may only report a UTRAN or E-UTRAN cell detected as a hybrid cell in a PACKET MEASUREMENT REPORT message or PACKET ENHANCED MEASUREMENT REPORT message using the procedures for non-CSG cells defined in subclause 5.6.

A multi-RAT mobile station in NC2 mode may send a PACKET CELL CHANGE NOTIFICATION message on PACCH in place of a PACKET MEASUREMENT REPORT message or PACKET ENHANCED MEASUREMENT REPORT message (see sub-clause 5.6.1), indicating a target cell which is a CSG cell or detected hybrid cell whose CSG ID is in the CSG whitelist of the MS if all of the following conditions are met:

– the CSG Whitelist of the mobile station is not empty; and

– for a UTRAN cell, either the MS does not support "UTRA CSG Cells Reporting" or the UTRAN CSG Cells Reporting Description IE has not been received from the network (or both); and

– for an E-UTRAN cell, either the MS does not support "E-UTRA CSG Cells Reporting" or the E-UTRAN CSG Cells Reporting Description IE has not been received from the network (or both); and

– the cell reselection criteria for autonomous reselection towards a CSG cell in NC0/NC1 mode (see 3GPP TS 45.008) have been met and;

– the NC2_CSG_PCCN_permitted field (see 3GPP TS 44.018) has been received in System Information Type 2quater and is equal to ‘1’.

NOTE: The sending of the PACKET CELL CHANGE NOTIFICATION message when these conditions are met is not conditional on the setting of 3G_CCN_ACTIVE or E-UTRAN_CCN_ACTIVE.

If these conditions are met and a mobile station sends a PACKET CELL CHANGE NOTIFICATION message, it shall indicate the CSG cell as the target cell in the PACKET CELL CHANGE NOTIFICATION message using the 3G Target Cell Struct or E-UTRAN Target Cell Struct (alternatively, if the mobile station and the network supports extended EARFCNs, the E-UTRAN Target Cell with extended EARFCN struct) and shall include the CSG Discriminator bit. The remaining contents of the PACKET CELL CHANGE NOTIFICATION message shall be as specified for the case of entering CCN mode (see sub-clause 8.8.3). The network may respond to the PACKET CELL CHANGE NOTIFICATION with a PACKET CELL CHANGE ORDER message. The mobile station shall not enter CCN mode and shall not perform a cell change unless a PACKET CELL CHANGE ORDER message is received.

NOTE: The use of PACKET CELL CHANGE NOTIFICATION message to report a CSG cell by a mobile station in packet transfer mode in NC0/NC1 mode (including the case where the MS supports CSG Cells Reporting and the CSG Cells Reporting Description IE has been received from the network) is specified in sub-clause 8.8.3.

The CSG Discriminator shall be incremented by one modulo 2 whenever the mobile station reports a different CSG cell having the same physical layer parameters as the previously reported CSG cell. The initial value of the CSG Discriminator is 0. The mobile station shall use individual sequences of CSG Discriminator for CSG cells with different physical layer parameters.

When the mobile station leaves NC2 mode or moves to a new cell, the mobile station shall delete all CSG Discriminator information.

5.6.4 Measurement reporting in broadcast/multicast receive mode

The mobile station in broadcast/multicast receive mode shall report neighbouring cell measurements when polled for an MBMS DOWNLINK ACK/NACK message according to the procedures specified in sub-clause 8.1.4.2. Measurement reporting in broadcast/multicast receive mode shall not affect the procedure for NC measurement reporting defined in sub-clause 5.6.1.

For reporting neighbouring cells in the MBMS Neighbouring Cell Report struct, the following rules apply:

– the neighbouring cells shall belong to the six strongest non-serving and allowed (see 3GPP TS 45.008) carriers

– the cells for which cell reselection parameters have been acquired, shall be reported in decreasing order of the corresponding cell re-selection ranking (see 3GPP TS 45.008), i.e. the highest ranked first.

– the neighbouring cells for which cell reselection parameters have not been acquired, shall be reported in decreasing order of the received signal level average (see 3GPP TS 45.008), i.e. the neighbouring cell with highest received signal average first.

– in case there are cells for which cell reselection parameters have and cells for which cell reselection parameters have not been acquired to be included in the MBMS Neighbouring Cell Report struct, the cells shall be reported in alternating order, starting with the highest ranked cell for which cell reselection parameters have been acquired.

– the MBMS Neighbouring Cell Report struct shall include as many cells as possible but shall not exceed 6 cells.

EXAMPLE: there is space to report 4 neighbouring cells in the MBMS DOWNLINK ACK/NACK message.

In this case, the neighbouring cells in the MBMS Neighbouring Cell Report stuct shall be reported in the following order :

y(1), n(1), y(2), y(3), cells y(4) and y(5) are not reported,

where

y(1) is the highest ranked cell for which cell reselection parameters have been acquired
y(2) is the 2^nd highest ranked cell for which cell reselection parameters have been acquired
y(3) is the 3^rd highest ranked cell for which cell reselection parameters have been acquired
y(4) is the 4^th highest ranked cell for which cell reselection parameters have been acquired
y(5) is the 5^th highest ranked cell for which cell reselection parameters have been acquired
n(1) is the highest ranked (and the only one within the 6 strongest) cell for which cell reselection parameters have not been acquired

If cell re-selection is triggered towards a neighbouring cell (see 3GPP TS 45.008), the mobile station shall indicate this to the network with the RESEL_CRITERIA_FULFILLED parameter when reporting measurement results for that cell. In this case, the mobile station shall not include any other measurement results for any other neighbouring cell in the MBMS Neighbouring Cell Report struct.

When reporting measurement results for a neighbouring cell, the mobile station shall indicate with the RESEL_PARAMS_ACQUIRED parameter whether it has acquired the reselection parameters for that cell. The mobile station shall also indicate whether it has received (as described in sub-clause 7.7.3) the MBMS bearer parameters in that cell for the MBMS session acknowledged in the MBMS DOWNLINK ACK/NACK message. If so the mobile station shall indicate the latest corresponding (i.e. for that cell and that session) MBMS_PTM_CHANGE_MARK parameter received. The network may use this information to schedule MBMS NEIGHBOURING CELL INFORMATION messages accordingly. If for a given session the network has received from a mobile station an indication that no MBMS bearer parameters for that session in a neighbouring cell have been received, the network may establish that session in that neighbouring cell, if not already established provided that that cell supports MBMS and belongs to the MBMS service area.

5.7 Dual transfer mode enhancements

The mobile station and the network may support enhanced DTM CS establishment and enhanced DTM CS release procedures, called DTM enhancements.

By using enhanced DTM CS establishment procedure, an RR connection can be initiated by either the mobile station or the network while the mobile station is in packet transfer mode. The procedure is specified in sub-clause 8.9.

By using enhanced DTM CS release, the network may delay the release of the RR connection until the mobile station in dual transfer mode has received the required system information, in order to maintain the radio resources (PDCH(s)) after the release of the RR connection while in dual transfer mode, as specified in sub-clause 5.5.1.1b.5.

The support of the DTM enhancements is optional for the mobile station and the network and is indicated in the Mobile Station Classmark 3 IE, the MS Radio Access Capability IE and the GPRS Cell Options IE. A mobile station supporting the DTM enhancements shall also support the extended RLC/MAC control message segmentation as defined in 9.1.12a. The DTM enhancements shall be used if the mobile station and the network support them.

5.8 DTM Handover

Mobile station and network support for DTM handover is optional. The mobile station shall indicate its support for DTM handover in the Mobile Station Classmark 3 IE and the MS Radio Access Capabilities IE (see 3GPP TS 24.008). A mobile station supporting DTM handover shall also support the extended RLC/MAC control message segmentation as defined in sub-clause 9.1.12a. The DTM handover procedure consists of the CS handover procedure (see 3GPP TS 44.018) and the PS handover procedure (see sub-clause 8.10) running in parallel with exceptions as outlined in 3GPP TS 48.008.

5.9 Downlink Dual Carrier

Mobile station and network support for Downlink Dual Carrier is optional. The mobile station shall indicate its support for Downlink Dual Carrier in the MS Radio Access Capabilities IE (see 3GPP TS 24.008). A mobile station and a network that support Downlink Dual Carrier shall also support EGPRS TBFs. A mobile station supporting Downlink Dual Carrier shall also support the extended RLC/MAC control message segmentation as defined in sub-clause 9.1.12a.

Downlink Dual Carrier enables downlink TBFs and uplink TBFs to use allocated resources on one or more assigned PDCHs on two different radio frequency channels. Uplink RLC/MAC blocks shall not be scheduled on both carriers of a downlink dual carrier configuration in the same radio block period. Downlink RLC/MAC blocks may be scheduled on both carriers of a downlink dual carrier configuration in the same radio block period.

If the network initially assigns a mobile station radio resources on only one carrier, it can extend this assignment to adownlink dual carrier configuration by sending a new single carrier assignment to the mobile station including assigned radio resources for the second carrier, without changing the resources already assigned for the initial carrier. Alternatively the network can include radio resources for two carriers in an initial or subsequent assignment message.

5.10 ETWS Primary Notification

Mobile station support for reception of Earthquake and Tsunami Warning System (ETWS) Primary Notification messages is optional. A mobile station supporting reception of ETWS Primary Notification shall also support the extended RLC/MAC control message segmentation as defined in sub-clause 9.1.12a.

5.11 Enhanced Multiplexing for Single TBF

Mobile station and network support for Enhanced Multiplexing for Single TBF (EMST) is optional. The mobile station shall indicate its support for EMST in the MS Radio Access Capability IE (see 3GPP TS 24.008). The mobile station supporting EMST and RLC non-persistent mode shall be able to operate up to three RLC entities on a single TBF concurrently. The mobile station supporting EMST and not supporting RLC non-persistent mode shall be able to operate up to two RLC entities on a single TBF concurrently. A mobile station and a network that support EMST shall also support EGPRS. A network supporting EMST shall also support the delayed release of downlink TBF and extended uplink TBF mode (see sub-clauses 9.3.1a and 9.3.1b).

EMST enables the allocation and multiplexing of one or more RLC entities on a single TBF. In the uplink, each RLC entity allocated on the TBF shall operate according to radio parameters (radio priority and peak throughput) of the PFC currently being served, however different RLC entities allocated on the same uplink TBF may operate according to different radio parameters. The RLC entities allocated on the TBF shall operate in different RLC modes. The TBF shall be maintained when packet transfer switches between RLC entities using different RLC modes and/or radio priorities. The network shall not assign more than one RLC entity operating in a give RLC mode to a single TBF.

NOTE: It is for further study, whether a specific PFC multiplexing shall apply if EMST is used.

Each RLC entity allocated on a TBF using EMST shall be assigned a unique TFI as specified in sub-clause 5.2.2.

An uplink TBF using EMST shall be assigned a unique USF as specified in sub-clause 5.2.3. The use of USF for an uplink TBF using EMST is the same as specified for an uplink TBF not using EMST.

On an uplink TBF using EMST, the mobile station shall use the same rules for multiplexing LLC PDUs as specified for a single RLC entity case, i.e. use peak throughput and radio priority to decide how data from different PFCs are multiplexed.

5.12 Enhanced Multiplexing for a Single RLC Entity

Mobile station and network support for Enhanced Multiplexing for a Single RLC Entity (EMSR) is optional. The mobile station shall indicate its support for EMSR in the MS Radio Access Capability IE (see 3GPP TS 24.008). A network that supports EMSR shall also support the delayed release of a downlink TBF and extended uplink TBF mode (see sub-clauses 9.3.1a and 9.3.1b). A mobile station that supports EMSR shall support extended uplink TBF mode.

EMSR is enabled for a given RLC entity when the network allocates multiple PFCs with at least two of them having unique TFI values within the context of that RLC entity. EMSR is disabled for a given RLC entity if that RLC entity is no longer allocated multiple PFCs with at least two of them having unique TFI values.

If EMSR is enabled for a given RLC entity then uplink resource reallocation/downlink resource reassignment is not performed whenever RLC data block transmission priority decisions made in the MS or in the BSS result in switching between PFCs assigned to the same RLC entity but having different TFI values. If EMSR is enabled and a new upper layer PDU becomes available but is not associated with a PFC for which the MS has already sent a PACKET RESOURCE REQUEST message (and received a corresponding assignment message), then the MS shall proceed as described in sub-clause 8.1.1.1.2 regarding how the transmission of the new LLC PDU is to be managed. Similarly, if EMSR is enabled and a new upper layer PDU becomes available but is not associated with a PFC for which the MS has already received a downlink assignment message then the BSS shall perform downlink resource reassignment and the MS shall proceed as described in sub-clause 8.1.2.4. An uplink TBF using EMSR shall be assigned a unique USF as specified in sub-clause 5.2.3.

If EMSR is enabled for a given RLC entity, the determination of the relative transmission priority of upper layer PDUs is implementation specific. The transmission of upper layer PDUs may be suspended or resumed depending on their relative priorities as specified in sub-clauses 9.1.11 and 9.1.12.

If EMSR is enabled for a given RLC entity, the network may send the mobile station an assignment message (e.g. PACKET TIMESLOT RECONFIGURE, PACKET UPLINK ASSIGNMENT or PACKET DOWNLINK ASSIGNMENT message) that excludes a subset of the PFCs previously allocated to that RLC entity without releasing the RLC entity. In this case:

– Upon reception of the assignment message, the mobile station may discard all upper layer PDUs corresponding to an excluded PFC for which transmission has not yet started.

– Upon determining that there are no outstanding upper layer PDUs corresponding to an excluded PFC, the mobile station shall consider that PFC as no longer allocated to the corresponding RLC entity. The mobile station shall also consider the TFI value associated with such a PFC as no longer allocated to the corresponding RLC entity if there are no remaining PFCs allocated to that RLC entity still associated with that TFI value.

– If the mobile station has more upper layer PDUs to send for an excluded PFC then it shall send a PACKET RESOURCE REQUEST message requesting resources for that PFC as described in this sub-clause.

5.13 Downlink Multi Carrier

Mobile station and network support for Downlink Multi Carrier is optional. The mobile station shall indicate its support for DLMC configuration in the MS Radio Access Capability IE (see 3GPP TS 24.008). A mobile station and a network that support DLMC configuration shall support:

– the assignment of only one EGPRS TBF on the downlink where multiple PDCHs may be assigned on two or more different radio frequency channels.

– extended RLC/MAC control message segmentation as defined in sub-clause 9.1.12a.

– the optional assignment of one EGPRS TBF on the uplink. If assigned, one or more PDCHs may be assigned on one or more uplink radio frequency channels where each uplink radio frequency channel corresponds to an assigned downlink radio frequency channel.

A mobile station that supports DLMC configuration shall, within the MS Radio Access Capability IE (see 3GPP TS 24.008), indicate the maximum number of downlink carriers it supports, the maximum number of downlink timeslots it supports, the maximum bandwidth it supports, and whether or not it support non-contiguous intra-band reception and/or inter-band reception.

A mobile station that supports DLMC configuration may be assigned one or more UFPS (see 3GPP TS 45.008 [15]) where the assigned UFPS(s) and their associated carriers are numbered as described in sub-clause 8.1.1.1.3. For the case where a UFPS is defined by a mobile allocation (see sub-clause 12.10a) a mobile station in DLMC configuration will perform carrier selection to determine the set of downlink carriers it can receive during any given radio block period as described in 3GPP TS 45.002 [13].

In DLMC configuration RLC/MAC blocks shall not be scheduled on multiple uplink carriers in the same radio block period whereas RLC/MAC blocks may be scheduled on one or more downlink carriers in the same radio block period.

If the maximum number of downlink timeslots a mobile station supports in a DLMC configuration is greater than 20 then it shall, in addition to supporting the EGPRS sequence number space (SNS) and window size, support an extended SNS of 8192, an extended window size (see sub-clause 9.0, 10.4.12 and 9.19), the assignment of eTFI values (see sub-clause 10.0a.2 and 10.0a.3) and CS-3 coding of EGPRS PACKET DOWNLINK ACK/NACK DLMC messages. The sequence number space to be used and the assigned eTFI values are indicated in the assignment message (see sub-clause 11.2.7).

In DLMC configuration where eTFI values are assigned, the mobile station uses eTFI in combination with TFI to determine if the message (PACCH, PAN or a RLC data block) is addressed to it. See sub-clause 8.1.1.1.1, 8.1.1.2.2 and 8.1.2.1 for the use of eTFI.

A mobile station in DLMC configuration where the continuous timing advance procedure is used shall fall back to single carrier configuration for PTCCH reception during each PTCCH frame occurring on the corresponding radio frequency channel (see sub-clause 7.1.2.5). In addition, the mobile station shall fall back to single carrier configuration for radio block reception according to a regular pre-determined interval (see 3GPP TS 45.002 [13]) using the radio frequency channel of its assigned PTCCH or using the radio frequency channel of the lowest numbered carrier (see sub-clause 8.1.1.1.3) if it has not been assigned a PTCCH. When inter-band reception is used in DLMC configuration (see 3GPP TS 45.005 and 3GPP TS 45.002), fall back to single carrier configuration only applies to the frequency band where the PTCCH is assigned or where the lowest numbered carrier is assigned (if a PTCCH has not been assigned).

If a mobile station is using the continuous timing advance procedure, it shall, upon receiving an assignment message that causes it to enter DLMC configuration, continue to use the current PTCCH information for as long as the corresponding downlink carrier remains assigned unless one of the following occurs:

– the current assignment message provides it with new PTCCH information.

– a subsequent assignment message or a Packet Power Control/Timing Advance message provides it with new PTCCH information.

– a subsequent assignment message results in the mobile station no longer being in a DLMC configuration (but still in packet transfer mode) in which case it shall consider the PTCCH allocation to be on the remaining carrier.