5 Introduction to the Medium Access Control (MAC) procedures
3GPP44.160General Packet Radio Service (GPRS)Mobile Station (MS) - Base Station System (BSS) interfaceRadio Link Control / Medium Access Control (RLC/MAC) protocol Iu modeRelease 16TS
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) and dedicated transmission resources (e.g. the multiplexing of logical channels onto DBPSCHs).
The Medium Access Control procedures support the provision of Temporary Block Flows that allow the point-to-point transfer of signalling and user data within a cell between the network and a mobile station.
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 TBF is a logical connection used by two MAC entities to support the unidirectional transfer of upper-layer PDUs on basic physical sub-channels. A mobile station shall support eight TBFs in each direction (uplink and downlink) . The network shall not assign more than eight TBFs to a mobile station. The total amount of TBFs assigned to a mobile station in a given direction shall always be lower than or equal to eight.
The TBF is allocated radio resources on one or more BPSCHs of the same type (i.e. either SBPSCH(s) or DBPSCH(s)) and may only be mapped on one logical channel type at a time. A TBF shall not be mapped on more than one DBPSCH/S. The TBF comprises a number of RLC/MAC blocks carrying one or more upper-layer PDUs.
A TBF mapped on PDTCH(s) may operate in either GPRS TBF mode or EGPRS TBF mode. If this TBF is operating on SBPSCH(s), the network sets the TBF mode in the PACKET UPLINK ASSIGNMENT message, MULTIPE TBF UPLINK ASSIGNMENT message, PACKET DOWNLINK ASSIGNMENT message, MUTLIPLE TBF DOWNLINK ASSIGNMENT message, PACKET TIMESLOT RECONFIGURE message, MULTIPLE TBF TIMESLOT RECONFIGURE message. If this TBF is operating on DBPSCH(s), the network sets the TBF mode using RRC procedures (see 3GPP TS 44.118). The EGPRS TBF mode is only supported by EGPRS capable MSs.
A TBF mapped on FACCH, SACCH or SDCCH operates implicitly in DCCH TBF mode.
A TBF mapped on TCH operates implicitly in TCH TBF mode.
A TBF mapped on UDCH(s) operates in UDCH TBF mode. UDCH TBF mode is applicable only when FLO is used.
A TBF mapped on CDCH(s) operates in CDCH TBF mode. CDCH TBF mode is applicable only when FLO is used.
A TBF associated with a URB may operate in either GPRS TBF mode, EGPRS TBF mode, DCCH TBF mode, TCH TBF mode or UDCH TBF mode.
A TBF associated with a SRB may operate in either GPRS TBF mode (CS-1 coding only), DCCH TBF mode or CDCH TBF mode. It shall not operate in EGPRS TBF mode.
5.2.2 Temporary Flow Identity
5.2.2.1 Temporary Flow Identity for SBPSCH
See 3GPP TS 44.060 sub-clause 5.2.2.
Global_TFI is used in an uplink or a downlink RLC/MAC control message to unambiguously identify the mobile station or one of its TBFs on SBPSCH. If present, the Global TFI addresses the mobile station using either an uplink TFI or a downlink TFI. The TFI used shall obey the rules below:
– If the TFI is used to identify the mobile station, any TFI may be used provided:
– The timeslot number (TN) of the SBPSCH on which the RLC/MAC control message is sent corresponds to a timeslot assigned to the TBF in the direction of the TBF.
– If the TFI is used to identify a TBF, the TFI of this TBF shall be used. Additionally if the RLC/MAC control message is sent in uplink, and the TBF is a downlink TBF:
– If the timeslot number (TN) of the SBPSCH on which the RLC/MAC control message is sent is different from the TN of each of the timeslots assigned to the TBF in the direction of the TBF, the TN of the TBF shall be included in the RLC/MAC control message to uniquely identify this TBF.
5.2.2.2 Temporary Flow Identity for DBPSCH
A TBF mapped on DBPSCH(s) may operate in either GPRS, EGPRS, DCCH, TCH, CDCH or UDCH TBF mode. A TBF mapped on DBPSCH/S shall operate in DCCH TBF mode.
A TBF in either GPRS TBF mode, EGPRS TBF mode or UDCH TBF mode (NT-RLC) is implicitly assigned a TFI that equals the identity (RBid) of the radio bearer it carries. An RLC/MAC block associated with such TBF shall contain a TFI. The TBF to which a RLC data block belongs is identified by the TFI and the direction (uplink or downlink) in which this RLC data block is sent. The TBF to which a RLC/MAC control message belongs is identified by the TFI, the direction in which this RLC/MAC control message is sent and the message type.
A TBF in TCH TBF mode is not assigned a TFI. This TBF is in its direction the only user of the TCH on which it is mapped, as described in sub-clause 9.2.2.
A TBF in UDCH TBF mode running in T-RLC is not assigned a TFI.
A TBF in DCCH TBF mode is implicitly assigned a Reduced Radio Bearer identity (RRBid) that provides a one-to-one mapping with the RBid of the radio bearer it carries. In case this radio bearer is a User-plane Radio Bearer (URB), the mapping between RRBid and RBid is given at radio bearer set-up of this URB by means of primitive exchange between RRC and MAC (CMAC-CONFIG). An RLC/MAC block associated with a DCCH TBF mode shall contain a RRBid. The TBF to which a RLC data block belongs is identified by the RRBid and the direction (uplink or downlink) in which this RLC data block is sent. The TBF to which a RLC/MAC control message belongs is identified by the RRBid, the direction in which this RLC/MAC control message is sent and the message type.
A TBF in CDCH TBF mode is implicitly assigned a Reduced Radio Bearer identity (RRBid) that provides a one-to-one mapping with the RBid of the signalling radio bearer it carries. An RLC/MAC block associated with a CDCH TBF mode shall contain a RRBid. The TBF to which a RLC data block belongs is identified by the RRBid and the direction (uplink or downlink) in which this RLC data block is sent. The TBF to which a RLC/MAC control message belongs is identified by the TFI or RRBid, the direction in which this RLC/MAC control message is sent and the message type.
5.2.3 Uplink State Flag
See 3GPP TS 44.060 sub-clause 5.2.3.
5.2.4 Medium Access modes
5.2.4.1 Medium Access modes for SBPSCH
See 3GPP TS 44.060 sub-clause 5.2.4.
5.2.4.2 Medium Access modes for DBPSCH
The dedicated allocation is applicable exclusively on a dedicated channel (i.e. mapped onto a DBPSCH). No other MAC mode may apply on DBPSCH. If the mobile station is assigned a DBPSCH (e.g. PACKET DBPSCH ASSIGNMENT), dedicated allocation shall be used in both uplink and downlink directions on this DBPSCH.
5.2.5 Multiplexing of GPRS and EGPRS TBF mode capable mobile stations
See 3GPP TS 44.060 sub-clause 5.2.4a.
5.3 MAC States
5.3.1 MAC-Idle state
5.3.1.1 General
In MAC-Idle state no TBF exists and the mobile station monitors relevant paging subchannels on the PCCCH. The mobile station may use DRX for monitoring the PCCCH.
5.3.1.2 Establishment of a SBPSCH
In MAC-Idle state, upper layers may require the transfer of an upper-layer PDU, which may trigger the establishment of a TBF on SBPSCH(s) and the transition to MAC-Shared state.
5.3.1.3 Establishment of a DBPSCH
In MAC-Idle state upper layers may require the transfer of an upper-layer PDU, which may trigger the establishment of a TBF on DBPSCH(s) either through RRC procedures (see 3GPP TS 44.118) or RLC/MAC procedures, in which case the mobile station leaves MAC-Idle state and enters the MAC-Dedicated state immediately after assignment of the DBPSCH(s). A mobile station shall not be assigned more than one DBPSCH/S.
5.3.2 MAC-Shared state
5.3.2.1 General
In MAC-Shared state, the mobile station is allocated radio resources providing a TBF for a point-to-point connection on one or more SBPSCHs. The TBF is used for the unidirectional transfer of upper-layer PDUs between the network and the mobile station. In MAC-Shared state the following services are offered:
– transfer of upper-layer PDUs in RLC acknowledged mode;
– transfer of upper-layer PDUs in RLC unacknowledged mode.
5.3.2.2 Release of all SBPSCHs
In MAC-Shared state, when all TBFs have been released in the downlink and uplink direction, the mobile station returns to MAC-Idle state.
5.3.2.3 Establishment of a DBPSCH
In MAC-Shared state upper layers may require the transfer of an upper-layer PDU, which may trigger the establishment of a TBF on a DBPSCH through RRC procedures (see 3GPP TS 44.118), in which case the mobile station leaves MAC‑Shared state and enters the MAC-DTM state.
5.3.2.4 Radio bearer reconfiguration
Upon reconfiguration of all Radio Bearers from SBPSCH(s) to DBPSCH(s), the mobile station shall leave the MAC‑Shared state and enter the MAC-Dedicated state after release of all TBFs on SBPSCH(s) and set-up of the first DBPSCH. See 3GPP TS 44.118.
5.3.3 MAC-DTM state
5.3.3.1 General
In MAC-DTM state a mobile station has been allocated radio resources providing one or more DBPSCHs and one or more SBPSCHs. A mobile station shall not be allocated radio resources providing a DBPSCH/S with any other BPSCH(s). The allocation of radio resources is co-ordinated by the network, in agreement with the capabilities of the mobile station.
The transfer of upper-layer PDUs in RLC acknowledged, RLC unacknowledged mode or RLC transparent mode is provided.
5.3.3.2 Release of all SBPSCHs
In MAC-DTM state, when all TBFs on SBPSCHs have been released, in downlink and uplink directions, the mobile station enters MAC-Dedicated state.
5.3.3.3 Release of all DBPSCHs
In MAC-DTM state, upon release of all DBPSCHs, the mobile station enters the MAC-Shared state.
5.3.3.4 Release of all SBPSCHs and DBPSCHs
In MAC-DTM state, upon release of all SBPSCHs and DBPSCHs, the mobile station enters the MAC-Idle state.
5.3.4 MAC-Dedicated state
5.3.4.1 General
In MAC-Dedicated state a mobile station has been allocated radio resources providing one or more DBPSCHs. A mobile station shall not be allocated more than one DBPSCH/S. The allocation of radio resources is co-ordinated by the network, in agreement with the capabilities of the mobile station.
The transfer of upper-layer PDUs in RLC acknowledged, RLC unacknowledged mode or RLC transparent mode is provided.
5.3.4.2 Release of all DBPSCHs
In MAC-Dedicated state, upon release of all DBPSCHs, the mobile station shall enter the MAC-Idle state.
5.3.4.3 Radio bearer reconfiguration
Upon reconfiguration of all Radio Bearers from DBPSCH(s) to SBPSCH(s), the mobile station shall leave the MAC‑Dedicated state and enter the MAC-Shared state after release of all DBPSCH(s) and set-up of the first TBF on SBPSCH(s) (see 3GPP TS 44.118).
5.3.5 MAC state machine
Figure 5.3.5.1 represents the state machine of the MAC sublayer.
Figure 5.3.5.1: MAC state machine
5.4 General MAC procedures in MAC-Idle state and MAC-Shared state
5.4.1 Mobile station side
5.4.1.1 General
A mobile station in MAC-Idle state or MAC-Shared state shall monitor the system information broadcast in the cell.
In MAC-Idle state, the mobile station shall monitor the radio blocks on PCCCH as defined in sub-clauses 5.4.1.8 and 5.4.1.9. The determination of the paging group for the mobile station is defined in 3GPP TS 45.002.
5.4.1.2 Cell reselection
Cell reselection in MAC-Idle state and MAC-Shared state is specified in 3GPP TS 45.008. The MAC entity on the mobile station side indicates to the RRC layer the availability of a cell and a cell change when decided by the MAC sublayer. RRC is advised of system information broadcast in the cell when a new cell has been selected or when a relevant part of this information changes.
If the new cell supports Iu mode the mobile station shall operate in Iu mode unless ordered to operate in A/Gb mode by the network. If the new cell does not support Iu mode, a mobile station which supports A/Gb mode shall operate in A/Gb mode as described in 3GPP TS 44.060. If operating in Iu mode, the mobile station shall perform packet access in Iu mode otherwise the mobile station shall perform packet access in A/Gb mode.
When a cell reselection is determined by the mobile station or ordered by the network, the mobile station may continue its operation in MAC-Idle state or MAC-Shared state in the old serving cell, while acquiring certain system information for the target cell.
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).
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.4.1.5) the mobile station may re-establish and continue its operation in the old cell, until the next occurrence of PSI1 in block B0.
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, in order to receive necessary information on BCCH in the target cell. Such suspension may be required in MAC-Idle state and MAC-Shared state. 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 any TBF 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, follow the procedures for Network Assisted Cell Change as specified in 3GPP TS 44.060 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 seconds after a cell reselection has been determined.
5.4.1.3 Network Assisted Cell Change
See 3GPP TS 44.060 sub-clause 5.5.1.1a.
5.4.1.4 Release of DBPSCHs
5.4.1.4.1 General
The mobile station shall acquire system information broadcast in the serving cell when in MAC-Idle state, after the release of all DBPSCHs if the mobile station had been unable to monitor the system information broadcast on PBCCH while one or more DBPSCHs were allocated:
– The acquisition of system information shall be performed according to the requirements in sub-clause 5.4.1.5.
– The mobile station shall not attempt a packet access or accept a packet downlink assignment before these requirements are fulfilled.
The following exceptions, stated in sub-clauses 5.4.1.4.2 and 5.4.1.4.3, may apply.
5.4.1.4.2 Continuation of PBCCH information
At the allocation of a DBPSCH, the mobile station may keep the PSI messages received on PBCCH before the allocation of the DBPSCH. If all DBPSCHs are released in the same serving cell within 30 s after the PSI1 message was last received, the mobile station may resume the supervision of PBCCH_CHANGE_MARK and update of PBCCH information, defined in 3GPP TS 44.060 sub-clause 5.5.1.2.1, and need not initiate a complete acquisition of PBCCH information, as specified in sub-clause 5.4.1.5.
5.4.1.4.3 Receipt of PSI14 message in MAC-DTM state
In MAC-DTM state, the mobile station may receive the PSI14 message on PACCH in the serving cell. If all DBPSCHs are 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 or SI13-Alt message after the release of all DBPSCHs, until either the SI13 or SI13-Alt 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 all of DBPSCHs, the mobile station shall perform a complete acquisition of PBCCH information, as defined in sub-clause 5.4.1.5.
5.4.1.5 System information on PBCCH
See 3GPP TS 44.060 sub-clause 5.5.1.2.
5.4.1.6 System information on BCCH
5.4.1.6.1 General
The support of Iu mode shall be indicated in SI3 message sent on BCCH. In addition, the support of Iu mode shall be indicated in either SI4 or SI7 and 8 messages. The SI3, SI4, SI7 and SI8 messages contain the CBQ3 parameter that indicates if Iu mode is supported in the cell (see 3GPP TS 44.018).
If CBQ3 parameter sent on BCCH indicates that Iu mode is supported in the cell then a mobile station shall acquire a PBCCH description from either SI13 or SI13-Alt and shall operate in Iu mode (see 3GPP TS 44.118).
If CBQ3 indicates that Iu mode is not supported in the cell then a mobile station may operate in A/Gb mode as described in 3GPP TS 44.060.
When a new cell has been selected where PBCCH is not present, the mobile station shall operate as described in 3GPP TS 44.060.
5.4.1.6.2 Establishment of PBCCH
The mobile station may receive an SI13, SI13-Alt 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.4.1.7).
5.4.1.6.3 (void)
5.4.1.7 (void)
5.4.1.8 Discontinuous reception (DRX)
A mobile station in MAC-Idle state may use Discontinuous Reception (DRX) to reduce its power consumption.
In DRX mode, the MAC layer receives the paging group relevant for the mobile station from the RRC layer via the CMAC-CONFIG primitive. The computation of the paging group is defined in 3GPP TS 44.118. The mobile station shall only monitor the blocks corresponding to its paging group. The GERAN shall initiate paging procedures for this mobile station on the blocks corresponding to its paging group.
In non-DRX mode, the mobile station shall monitor all paging blocks on the monitored PCCCH (see 3GPP TS 45.002).
There are three cases when the mobile station enters a non-DRX mode period:
1) When entering the MAC-Idle state, the mobile station shall enter the non-DRX mode period.
The duration of the non-DRX mode period is determined by the value of the DRX_TIMER_MAX parameter broadcast in the cell.
If the mobile station receives a new value of the DRX_TIMER_MAX parameter during the non-DRX mode period, the mobile station may wait to apply the new value until the next time the non-DRX mode period is entered.
2) When the network operates in NC2 mode and the MS sends a NC measurement report, both the MS and the network shall enter the NC2 non-DRX mode period. The duration of this period is defined by the NC_NON_DRX_PERIOD parameter.
3) 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.
The non-DRX mode periods defined above run independent of each other and may overlap. In RRC-Idle mode, the mobile station shall be in non-DRX mode during any of the non-DRX mode periods.
5.4.1.9 Page mode procedures on PCCCH
See 3GPP TS 44.060 sub-clause 5.5.1.6.
5.4.1.10 Frequency Parameters
See 3GPP TS 44.060 sub-clause 5.5.1.7.
5.4.1.11 G-RNTI Management
G-RNTI is used to identify a mobile station during contention resolution and is allocated by RRC in the GERAN. If a mobile station does not possess a GERAN allocated G-RNTI when making a contention access it shall use a Random G-RNTI. Upon receiving a G-RNTI allocation from the GERAN a mobile station shall use it for subsequent contention accesses for as long as it remains valid.
5.4.2 Network side
5.4.2.1 System Information broadcasting
5.4.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, 3bis and PSI16 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, a 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 3GPP TS 44.060 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 PSI16 message shall be broadcast on the PBCCH to provide mobile stations with additional information required for Iu mode operation.
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 MAC-Shared state.
The network indicates the support of the PACKET PSI STATUS and EGPRS PACKET CHANNEL REQUEST messages in the PSI1 message.
5.4.2.1.2 System information on BCCH
In addition to the requirements in 3GPP TS 44.018, a SYSTEM INFORMATION TYPE 13 (SI13) message or a SYSTEM INFORMATION TYPE 13 Alt (SI13-Alt) message is regularly broadcast by the network on the BCCH to support Iu mode. Note that either the SI13 message or the SI13-Alt message is required on BCCH to support Iu mode.
5.4.2.1.3 System information on PACCH (and other logical channels)
See 3GPP TS 44.060 sub-clause 5.5.2.1.3.
5.4.2.1.4 Consistent sets of system information messages
Certain types of PSI messages are sent on PBCCH in a multiple number of instances. If such a PSI message type is sent on (P)BCCH, a mobile station shall receive a consistent set of that type of PSI message. In some cases, more than one type of PSI messages may be joined into one consistent set, see table 5.4.2.1.4.1.
Table 5.4.2.1.4.1: Consistent sets of system information messages
|
Consistent set / |
Broadcast |
Number of instances |
PSI change mark |
PSI index |
PSI count |
|
PSI2 |
PBCCH |
1 – 8 |
PSI2_CHANGE_MARK |
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 |
|
PSI16 |
PBCCH |
0 – 8 |
PSI16_CHANGE_MARK |
PSI16 _INDEX |
PSI16_COUNT |
A consistent set of system information messages is identified by a PSI 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 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 index parameter.
The PSI 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 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 index parameter.
5.4.2.2 Paging
See 3GPP TS 44.060 sub-clause 5.5.2.2.
5.4.2.3 Network Assisted Cell Change
See 3GPP TS 44.060 sub-clause 5.5.2.3.
5.5 Measurement reports
5.5.1 General
See 3GPP TS 44.060 sub-clause 5.6.0.
5.5.2 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, SI13-Alt 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. 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 MAC-Idle state or the NC_REPORTING_PERIOD_T when in MAC-Shared state. The measurement results shall be sent to the network using the procedures specified in sub-clause 7.4 for MAC Idle state, and in sub-clause 8.4 for MAC-Shared state.
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 3GPP TS 44.060 sub-clause 11.2.23, sub-clause 11.2.4 and sub-clause 11.2.9b and also 3GPP TS 44.018 sub-clause 10.5.2.33b.
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 MAC-Shared state to MAC-Idle state, 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 MAC-Shared state. Otherwise the timer T3158 shall continue to run.
When changing from MAC-Idle state to MAC-Shared state, 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 in Iu mode leaves RRC-Cell Shared state and enters RRC-GRA_PCH state or RRC-Idle mode, 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 MEASUREMENT ORDER or PACKET CELL CHANGE ORDER message); or
– received in a broadcast PSI5, SI13, SI13-Alt, 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 or use the default parameter values.
The default frequency list to be applied in the new cell shall be the BA(GPRS) list of that cell until a new PACKET MEASUREMENT ORDER message is received. 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) measurement 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 multi-RAT mobile station, reports on 3G cells may also be included in the reporting. For report with the PACKET MEASUREMENT REPORT message, reporting is performed on two separate lists: the BA(GPRS) and the 3G Neighbour Cell List (for a multi-RAT MS). For report with the PACKET ENHANCED MEASUREMENT REPORT message, reporting is performed on the Neighbour Cell List (defined in 3GPP TS 44.060 sub-clause 5.6.3.3).
A mobile station that has been allocated one or more DBPSCHs, shall not send Network Control measurement reports to the network during that period. The mobile station shall return to the previous reporting mode when all the DBPSCHs have been released.
5.5.3 (void)
5.5.4 Additional measurement and reporting parameters
See 3GPP TS 44.060 sub-clause 5.6.4.
5.6 Mapping of Signalling Radio Bearers (SRB) onto logical channels / transport channels
5.6.1 Downlink
In downlink direction, the mapping of SRBs onto logical channels or, in case of FLO, transport channels is left up to network implementation. The rules defined in sub-clause 5.6.2 should be used. The MS shall be able to receive SRB data on any of the following logical channels if available: SDCCH, SACCH, FACCH, PDTCH and SFACCH. Additionaly, a MS supporting FLO shall be able to receive SRB data on CDCH.
5.6.2 Uplink
5.6.2.1 MAC-Dedicated State
Table 5.6.2.1.1 represents the alternatives for mapping a given SRB onto a given logical channel or, in case of FLO, transport channel when the MS is in MAC‑Dedicated state. The MS shall obey the rules given in this table. Only the logical channels or transport channels available for SRBs are listed.
In case more than one DBPSCHs are assigned, with a mixed allocation of TCH(s) and PDTCH(s) (e.g. TCH on one DBPSCH, and PDTCH on the other DBPSCH), any ongoing transfer of a given SRB shall continue in the same TBF mode.
Table 5.6.2.1.1: Mapping of SRBs onto logical channels or transport channels in MAC-Dedicated State
|
MAC-Dedicated State |
||||
|
SDCCH + SACCH |
FACCH + SACCH |
PDTCH + SACCH |
CDCH + SACCH |
|
|
SRB1 |
SACCH |
SACCH |
SACCH |
SACCH |
|
SRB2 |
SDCCH |
FACCH |
PDTCH |
CDCH |
|
SRB3 |
SDCCH |
FACCH |
PDTCH |
CDCH |
|
SRB4 |
SDCCH |
SACCH |
PDTCH |
SACCH |
5.6.2.2 MAC-Shared State
Table 5.6.2.2.1 represents the alternatives for mapping a given SRB onto a given logical channel when the MS is in MAC‑Shared state. The MS shall obey the rules given in this table. Only the logical channels available for SRBs are listed.
Table 5.6.2.2.1: Mapping of SRBs onto logical channels in MAC-Shared State
|
MAC-Shared State |
|
|
PDTCH + SFACCH |
|
|
SRB1 |
PDTCH xor SFACCH (i) |
|
SRB2 |
PDTCH xor SFACCH (i) |
|
SRB3 |
PDTCH xor SFACCH (i) |
|
SRB4 |
PDTCH xor SFACCH (i) |
|
Rule i: PDTCH shall be used if and only if the corresponding TBF is established or a TBF establishment request is ongoing for this SRB, otherwise SFACCH shall be used. |
|
5.6.2.3 MAC-DTM State
Table 5.6.2.3.1 represents the alternatives for mapping a given SRB onto a given logical channel or, in case of FLO, transport channel when the MS is in MAC‑DTM state. The MS shall obey the rules given in this table. Only the logical channels or transport channel available for SRBs are listed.
Table 5.6.2.3.1: Mapping of SRBs onto logical channels or transport channels in MAC-DTM State
|
MAC-DTM State |
|
|
(FACCH/H + SACCH/H) + (PDTCH/H (see note) + SFACCH/H) |
|
|
SRB1 |
SACCH/H |
|
SRB2 |
PDTCH/H xor FACCH/H (ii) |
|
SRB3 |
PDTCH/H xor SFACCH/H (i) |
|
SRB4 |
PDTCH/H xor SFACCH/H (i) |
|
MAC-DTM State |
|
|
(CDCH + SACCH/H) + (PDTCH/H (see note) + SFACCH/H) |
|
|
SRB1 |
SACCH/H |
|
SRB2 |
PDTCH/H xor CDCH (iv) |
|
SRB3 |
PDTCH/H xor SFACCH/H (i) |
|
SRB4 |
PDTCH/H xor SFACCH/H (i) |
|
MAC-DTM State |
|
|
(FACCH/F + SACCH/F) + (PDTCH/F + SFACCH/F) |
|
|
SRB1 |
SACCH/F |
|
SRB2 |
FACCH/F xor PDTCH/F (ii) |
|
SRB3 |
PDTCH/F xor SFACCH/F (i) |
|
SRB4 |
PDTCH/F xor SFACCH/F (i) |
|
MAC-DTM State |
|
|
(CDCH + SACCH/F) + (PDTCH/F + SFACCH/F) |
|
|
SRB1 |
SACCH/F |
|
SRB2 |
CDCH xor PDTCH/F (iv) |
|
SRB3 |
PDTCH/F xor SFACCH/F (i) |
|
SRB4 |
PDTCH/F xor SFACCH/F (i) |
|
MAC-DTM State |
|
|
(PDTCH + SACCH) + (PDTCH + SFACCH) |
|
|
SRB1 |
SACCH |
|
SRB2 |
PDTCH (iii) |
|
SRB3 |
PDTCH xor SFACCH (i) |
|
SRB4 |
PDTCH xor SFACCH (i) |
|
Rule i: PDTCH shall be used if and only if the corresponding TBF is established or a TBF establishment request is ongoing for this SRB, otherwise SFACCH shall be used. Rule ii: PDTCH shall be used if and only if the corresponding TBF is established or a TBF establishment request is ongoing for SRB2, else FACCH shall be used. In case more than one DBPSCHs are assigned, with a mixed allocation of TCH(s) and PDTCH(s) (e.g. TCH on one DBPSCH, and PDTCH on the other DBPSCH), any ongoing SRB2 transfer shall continue in the same TBF mode. Rule iii: PDTCH on SBPSCH shall be used if and only if the corresponding TBF is established or a TBF establishment request is ongoing for SRB2, else PDTCH on DBPSCH shall be used. Rule iv: PDTCH shall be used if and only if the corresponding TBF is established or a TBF establishment request is ongoing for SRB2, else CDCH shall be used. NOTE: Single-slot operation with exclusive allocation. |
|
5.7 Multiplexing principles with Flexible Layer One
5.7.1 General
The Flexible Layer One may only be used on DBPSCH in MAC-Dedicated and MAC-DTM states. The allowed channel combinations are defined in 3GPP TS 45.002.
Multiplexing of TBFs in UDCH TBF mode or CDCH TBF mode with TBFs in GPRS TBF mode, EGPRS TBF mode, TCH TBF mode or DCCH TBF mode on the same DBPSCH is not allowed with the exceptions of TBFs on SACCH and half-rate configurations.
A mobile station may have up to four simultaneous active transport channels in the same TTI on a DBPSCH (see 3GPP TS 45.002)
5.7.2 Mutliplexing between user-plane and control-plane
The figure below illustrates the multiplexing between user-plane and control-plane onto transport channels.
A TBF may send data onto one transport channel at a time per TTI per DBPSCH, following the rules below:
– RLC/MAC blocks for data transfer associated with an SRB shall be sent on CDCH.
– RLC/MAC blocks for data transfer associated with a URB shall be sent on UDCH.
– RLC/MAC blocks for control message transfer shall be sent on ADCH.
There may be up to four simultaneous UDCHs active during the same TTI on a DBPSCH, allowing for transfer of data from four different TBFs during the same TTI.
On a DBPSCH, when either CDCH or ADCH is active during a TTI, no other transport channel may be active at the same time.
NOTE: User-plane and control-plane data are effectively multiplexed on the same DBPSCH on a TTI-basis.
Figure 5.7.2.1: Control-plane and user-plane multiplexing on transport channels