04.083GPPMobile radio interface Layer 3 specificationRelease 1998TS

Table 9.1/3GPP TS 04.08 summarizes the messages for Radio Resources management.

Table 9.1/3GPP TS 04.08: Messages for Radio Resources management

9.1.1 Additional assignment

This message is sent on the main DCCH by the network to the mobile station to allocate an additional dedicated channel while keeping the previously allocated channels. See table 9.2/3GPP TS 04.08.

Message type: ADDITIONAL ASSIGNMENT

Significance: dual

Direction: network to mobile station

Table 9.2/3GPP TS 04.08: ADDITIONAL ASSIGNMENT message content

9.1.1.1 Mobile Allocation

This information element shall appear if the Channel Description information element indicates frequency hopping.

If the Channel Description IE does not indicate frequency hopping and the information element is present it shall be considered as an IE unnecessary in the message.

9.1.1.2 Starting Time

This information element appears in particular if e.g., a change of frequency is planned.

9.1.2 Assignment command

This message is sent on the main DCCH by the network to the mobile station to change the channel configuration to another independent dedicated channel configuration, when no timing adjustment is needed. See table 9.3/3GPP TS 04.08

Message type: ASSIGNMENT COMMAND

Significance: dual

Direction: network to mobile station

Table 9.3/3GPP TS 04.08: ASSIGNMENT COMMAND message content

9.1.2.1 Mode of the First Channel (Channel Set 1) and Mode of Channel Set "X" (2=<X=<8)

If this information element is not present the channel mode of the previously allocated channel or channels for Channel Set "X" (1=<X<=8) shall be assumed.

If Channel Set "X" is not defined for the configuration, the Mode of Channel Set "X" IE shall be considered as an IE unnecessary in the message.

NOTE: Sub-clause 3.4.3.1 defines cases when one or several Mode of Channel Set "X" IEs shall be included in the message.

9.1.2.2 Description of the Second Channel

These information elements appear in the case of an assignment occurring if the mobile station carries two connections (on two dedicated channels, for the TCH/H + TCH/H configuration).

The connection using the channel previously defined in the Description of the First Channel IEs of an ASSIGNMENT COMMAND or HANDOVER COMMAND message shall use the channel defined in the Description of the First Channel IEs of the ASSIGNMENT COMMAND message defining the new configuration.

The channel described in the Description of the First Channel IEs carries the main DCCH. The SACCH used is the one associated with that channel.

9.1.2.3 Mode of the Second Channel

If no Description of the Second Channel IE is present but the information element is present it shall be considered as an IE unnecessary in the message.

This information element appears at least when the channel mode is changed for the channel defined in the second channel description information elements.

9.1.2.4 Mobile Allocation and Frequency List, after the starting time

If at least one of the channel descriptions for the starting time indicates frequency hopping, one and only one of the following information elements shall be present and apply to all assigned channels:

– Mobile Allocation, after time;

– Frequency List, after time.

If neither of the Channel Description IEs for after time indicate frequency hopping, if decoding of Channel Description IEs for before time does not require a frequency list for after time (see next sub-clause), and one or both of the two information elements are present they shall be considered as IEs unnecessary in the message.

9.1.2.5 Starting Time

The starting time information element is included when the network wants the mobile station to change the frequency parameters of the channels more or less at the moment a change of channel occurs. In this case a number of information elements may be included to give the frequency parameters to be used before the starting time.

If the starting time information element is present and none of the information elements referring to before the starting time are present, the mobile station waits and accesses the channels at the indicated time.

If the starting time information element is present and at least one of the information elements referring to before the starting time is present, the mobile station does not wait for the indicated time and accesses the channel using the frequency parameters for before the starting time.

If the starting time information element is not present and at some of the information elements referring to before the starting time is present, these information elements shall be considered as IEs unnecessary in the message.

If the description of the first channel, before time IE is not present, the channel description to apply for before the time, if needed, is given by the description of the first channel, after time IE.

If the description of the second channel, after time IE is present, the description of the second channel, before time IE not present, and a description of the configuration for before the time needed, the channel configuration before the starting time is nevertheless of two traffic channels, and the channel description to apply to the second channel before the starting time is given by the description of the second channel, after time IE.

If the starting time IE is present and at least one of the channel descriptions for before the starting time indicates frequency hopping, one and only one of the following information elements may be present and applies before the starting time to all assigned channels

– Mobile Allocation, before time IE;

– Frequency list, before time IE;

– Frequency channel sequence, before time IE.

If the starting time IE is present and at least one of the channel descriptions for before the starting time indicates frequency hopping, and none of the above mentioned IE is present, a frequency list for after the starting time must be present (see sub-clause 9.1.2.4), and this list applies also for the channels before the starting time.

9.1.2.6 Reference cell frequency list

If any of the mobile allocation information elements is present, then the network must ensure that either the mobile station has received in a previous message the proper reference cell frequency list (CA), or that the cell channel description IE is present.

If the cell channel description IE is present, it is used to decode the mobile allocation IEs in the message, as well as in later messages until reception of a new reference cell frequency list or the cell is left.

9.1.2.7 Cell Channel Description

If present, this information element shall be used to decode the Mobile Allocation IE in the same message and in subsequent messages.

9.1.2.8 Cipher Mode Setting

If this information element is omitted, the mode of ciphering is not changed after the mobile station has switched to the assigned channel.

9.1.2.9 VGCS target mode Indication

This information element is identified as "comprehension required". Only mobile stations supporting "VGCS talking " are required to accept the presence of the element. The presence of the element shall trigger an exception handling if received by a mobile station not supporting "VGCS talking".

This IE indicates which mode is to be used on the new channel (i.e. dedicated mode or group transmit mode). If this information element is not present, the mode shall be the same as on the previous channel.

The IE also indicates the group cipher key number for the group cipher key to be used on the new channel or if the new channel is non ciphered. If the information element is not present, the ciphering mode shall be the same as on the previous channel.

NOTE: A mobile station supporting VGCS talking shall not consider a syntactical error when this IE is present and the channel mode is not speech.

9.1.2.10 Description of the multislot allocation

This information element is included if so indicated by the channel type and TDMA offset field in the Channel Description information element and is used to assign channels that do not carry a main signalling link in a multislot configuration. It indicates how the used timeslots are divided into separate channel sets.

If the Channel Description IE does not require the presence of the information element the Description of the multislot allocation IE shall be considered as an IE unnecessary in the message.

If multislot configuration is indicated by the Channel Description IE but the Multislot Allocation IE is not present, all channels in the configuration belong to one channel set, "Channel Set 1".

NOTE: As a change of timeslot number cannot occur for the channel described after the starting time, the Multislot Allocation IE does not have to be included more than once.

9.1.2.11 Multi Rate configuration

This information element appears if the Mode of the First Channel indicates a multi-rate speech codec, and if the assigned configuration is new, i.e. it is different from the MultiRateconfiguration of a previously allocated channel in the cell.

9.1.3 Assignment complete

This message is sent on the main DCCH from the mobile station to the network to indicate that the mobile station has established the main signalling link successfully. See table 9.4/3GPP TS 04.08.

Message type: ASSIGNMENT COMPLETE

Significance: dual

Direction: mobile station to network

Table 9.4/3GPP TS 04.08: ASSIGNMENT COMPLETE message content

9.1.4 Assignment failure

This message is sent on the main DCCH on the old channel from the mobile station to the network to indicate that the mobile station has failed to seize the new channel. See table 9.5/3GPP TS 04.08.

Message type: ASSIGNMENT FAILURE

Significance: dual

Direction: mobile station to network

Table 9.5/3GPP TS 04.08: ASSIGNMENT FAILURE message content

9.1.5 Channel mode modify

This message is sent on the main DCCH by the network to the mobile station to request the setting of the mode for the indicated channel(s). The message can be used to change the channel mode of a Multislot Configuration which only contains one channel set. See table 9.6/3GPP TS 04.08.

Message type: CHANNEL MODE MODIFY

Significance: local

Direction: network to mobile station

Table 9.6/3GPP TS 04.08: CHANNEL MODE MODIFY message content

9.1.5.1 Channel Description

This is sufficient to identify the channel in the case of a TCH/H + TCH/H configuration. If used for a multislot configuration, the IE shall describe the present channel configuration with TN indicating the main channel. The IE shall not indicate a new channel configuration when included in the Channel Mode Modify message.

9.1.5.2 VGCS target mode Indication

This information element is identified as "comprehension required". Only mobile stations supporting "VGCS talking " are required to accept the presence of the element. The presence of the element shall trigger an exception handling if received by a mobile station not supporting "VGCS talking".

This IE indicates which RR mode is to be used with the new channel mode (i.e. dedicated mode or group transmit mode). If this information element is not present, the RR mode shall be the same as with the previous channel mode.

The IE also indicates the group cipher key number for the group cipher key to be used on the new channel or if the new channel is non ciphered. If the information element is not present, the ciphering mode shall be the same as with the previous channel mode.

NOTE: A mobile station supporting VGCS Talking shall not consider a syntactical error if this IE is present and the channel mode is not speech.

9.1.5.3 Multi Rate configuration

This information element appears if the Channel Mode IE indicates a multi-rate speech codec.

9.1.6 Channel mode modify acknowledge

This message is sent on the main DCCH by the mobile station to the network to indicate the successful or unsuccessful execution of a channel mode modify request. See table 9.7/3GPP TS 04.08.

Message type: CHANNEL MODE MODIFY ACKNOWLEDGE

Significance: local

Direction: mobile station to network

Table 9.7/3GPP TS 04.08: CHANNEL MODE MODIFY ACKNOWLEDGE message content

9.1.7 Channel release

This message is sent on the main DCCH from the network to the mobile station to initiate deactivation of the dedicated channel used. See table 9.8/3GPP TS 04.08

Message type: CHANNEL RELEASE

Significance: dual

Direction: network to mobile station

Table 9.8/3GPP TS 04.08: CHANNEL RELEASE message content

9.1.7.1 Channel description and mobile allocation

If a CHANNEL RELEASE is send to a mobile station which is in dedicated mode and which is involved in a voice group call or has responded to a notification to a voice group call or voice broadcast call, a group channel description may be included, describing the voice group call channel or voice broadcast channel to which the mobile station shall go after the channel release procedure.

Mobile stations not supporting VGCS listening or VBS listening shall consider this information element as unnecessary.

9.1.7.2 Group Cipher Key Number

This IE may be present only if the Group channel description IE is provided. The presence of this IE indicates that the mobile station shall use the Group Cipher Key indicated by the Group Cipher Key Number IE for deciphering on the VGCS or VBS channel. If this IE is not present, no ciphering is applied on the VGCS or VBS channel.

Mobile stations not supporting VGCS listening or VBS listening shall ignore this information element.

9.1.8 Channel request

This message is sent in random mode on the RACH. It does not follow the basic format. The possible formats are presented directly below, without reference to information fields. The order of bit transmission is defined in 3GPP TS 04.04.

The message is only one octet long, coded as shown in figure 9.1/GSM 4.08 and table 9.9/3GPP TS 04.08.

8 7 6 5 4 3 2 1

+———————————————–+

│ ESTABLISHMENT │ RANDOM │

│ + – – – – – – – – + │octet 1

│ CAUSE │ REFERENCE │

+———————————————–+

Figure 9.1/3GPP TS 04.08: CHANNEL REQUEST message content

ESTABLISHMENT CAUSE (octet 1)

This information field indicates the reason for requesting the establishment of a connection. This field has a variable length (from 3 bits up to 6 bits).

RANDOM REFERENCE (octet 1)

This is an unformatted field with variable length (from 5 bits down to 2 bits).

The Channel Request message is coded as follows:

(Random Reference field is filled with "x").

Table 9.9/3GPP TS 04.08: CHANNEL REQUEST message content

MS codes According to Establishment cause:
bits
8 …. 1

101xxxxx Emergency call

110xxxxx Call re-establishment; TCH/F was in use, or
TCH/H was in use but the network does not
set NECI bit to 1

011010xx Call re-establishment; TCH/H was in use and the
network sets NECI bit to 1

011011xx Call re-establishment; TCH/H + TCH/H was in use
and the network sets NECI bit to 1

100xxxxx Answer to paging
0010xxxx 0011xxxx See table 9.9a/3GPP TS 04.08
0001xxxx

111xxxxx Originating call and TCH/F is needed, or originating call
and the network does not set NECI bit to 1, or
procedures that can be completed with a SDCCH and the
network does not set NECI bit to 1. note 1

0100xxxx Originating speech call from dual‑rate mobile station when TCH/H
is sufficient and supported by the MS for speech calls and the network sets NECI bit to 1 note 5

0101xxxx Originating data call from dual‑rate mobile station when TCH/H
is sufficient and supported by the MS for data calls and the network sets NECI bit to 1 note 5

000xxxxx Location updating and the network does not set NECI bit to 1

0000xxxx Location updating and the network sets NECI bit to 1

0001xxxx Other procedures which can be completed with note 1
an SDCCH and the network sets NECI bit to 1

011110xx One phase packet access with request for single timeslot uplink
01111x0x transmission; one PDCH is needed.
01111xx0

01110xxx Single block packet access; one block period on a PDCH is needed for
two phase packet access or other RR signalling purpose.

01100111 LMU establishment note 2

01100xx0 Reserved for future use
01100×01 01100011 note 2a

01111111 Reserved for future use. note 2b

NOTE 1: Examples of these procedures are: IMSI detach, Short Message Service (SMS), Supplementary Service management, Location Services.

NOTE 2: If such messages are received by a network, an SDCCH shall be allocated.

NOTE 2a: If such messages are received by a network, an SDCCH may be allocated.

NOTE 2b: This value shall not be used by the mobile station on RACH. If such message is received by the network, it may be ignored.

Table 9.9a/3GPP TS 04.08: CHANNEL REQUEST message
(when answering to paging for RR connection establishment)

+——————————————————-+

++ MS Capability │ │ │ │

│+——-+ │ Full rate │ Dual │ SDCCH │

│ Paging +——+│ only │ rate │ only │

│ Indication 3) +│ │ (note 5) │ │

+—————-+————+————+————│

│ Any channel │ 100xxxxx │ 100xxxxx │ 100xxxxx │

+—————-+————+————+————│

│ SDCCH │ 0001xxxx │ 0001xxxx │ 0001xxxx │

+—————-+————+————+————│

│ TCH/F │ 100xxxxx │ 0010xxxx │ 0001xxxx │

+—————-+————+————+————│

│ TCH/H or TCH/F │ 100xxxxx │ 0011xxxx │ 0001xxxx │

+——————————————————-+

NOTE 3: The Paging Indication is provided by the Channel Needed IE (or the Channel Needed field) associated with the page which triggered the sending of the CHANNEL REQUEST message.

NOTE 4: In some cases the established connection will be used only to allow a default rejection mechanism to take place (typically the mobile station will send a RELEASE COMPLETE message with cause #88 "incompatible destination" as an answer to the incoming SETUP message).

NOTE 5: In this sub-clause, "dual rate capability" means that the MS supports both full rate and half-rate channels at least for the signalling channel mode. In addition, it may support either speech channel mode, or data channel modes, or both on half-rate channels.

9.1.9 Ciphering mode command

This message is sent on the main DCCH from the network to the mobile station to indicate that the network has started deciphering and that enciphering and deciphering shall be started in the mobile station, or to indicate that ciphering will not be performed. See table 9.10/3GPP TS 04.08.

Message type: CIPHERING MODE COMMAND

Significance: dual

Direction: network to mobile station

Table 9.10/3GPP TS 04.08: CIPHERING MODE COMMAND message content

9.1.10 Ciphering mode complete

This message is sent on the main DCCH from the mobile station to the network to indicate that enciphering and deciphering has been started in the MS. See table 9.11/3GPP TS 04.08.

Message type: CIPHERING MODE COMPLETE

Significance: dual

Direction: mobile station to network

Table 9.11/3GPP TS 04.08: CIPHERING MODE COMPLETE message content

9.1.10.1 Mobile Equipment Identity

This information element is included if and only if the mobile station shall include its IMEISV (see sub-clause 3.4.7). This information element shall only refer to IMEISV.

9.1.11 Classmark change

This message is sent on the main DCCH by the mobile station to the network to indicate a classmark change or as a response to a classmark enquiry. See table 9.12/3GPP TS 04.08.

Message type: CLASSMARK CHANGE

Significance: dual

Direction: mobile station to network

Table 9.12/3GPP TS 04.08: CLASSMARK CHANGE message content

9.1.11.1 Additional Mobile Station Classmark Information

This IE shall be included if and only if the CM3 bit in the Mobile Station Classmark IE is set to 1.

9.1.11.2 Mobile Station Classmark

This IE shall include for multiband MS the Classmark 2 corresponding to the frequency band in use.

9.1.12 Classmark enquiry

This message is sent on the main DCCH by the network to the mobile station to request classmark information. See table 9.12a/3GPP TS 04.08.

Message type: CLASSMARK ENQUIRY

Significance: dual

Direction: network to mobile station

Table 9.12a/3GPP TS 04.08: CLASSMARK ENQUIRY message content

9.1.12a Spare

9.1.12b Configuration change command

This message is sent on the main DCCH from the network to the mobile station to change the channel configuration of a multislot configuration. See table 9.12b/3GPP TS 04.08.

Message type: CONFIGURATION CHANGE COMMAND

Significance: dual

Direction: network to mobile station

Table 9.12b/3GPP TS 04.08: CONFIGURATION CHANGE COMMAND message contents

9.1.12b.1 Description of the multislot allocation

This information element is used to assign channels that do not carry the main signalling link in a multislot configuration. It indicates if multiple channel sets are used.

9.1.12b.2 Mode of Channel Set "X" ( 1=<X<=8)

If this information element is not present the channel mode of the previously allocated channel or channels for Channel Set "X" shall be assumed.

If Channel Set "X" is not defined for the configuration, the Mode of Channel Set "X" IE shall be considered as an IE unnecessary in the message.

NOTE: Sub-clause 3.4.16.1 defines cases when one or several Mode of Channel Set "X" IEs shall be included in the message.

9.1.12c Configuration change acknowledge

This message is sent on the main DCCH from the mobile station to the network to indicate that the mobile station has changed to the ordered channel configuration successfully. See table 9.12c/3GPP TS 04.08.

Message type: CONFIGURATION CHANGE ACKNOWLEDGE

Significance: dual

Direction: mobile station to network

Table 9.12c/3GPP TS 04.08: CONFIGURATION CHANGE ACKNOWLEDGE message contents

9.1.12d Configuration change reject

This message is sent on the main DCCH from the mobile station to the network to indicate that the mobile station has not managed to switch to the channel configuration ordered by the configuration change command and is still using the previous configuration. See table 9.12d/3GPP TS 04.08.

Message type: CONFIGURATION CHANGE REJECT

Significance: dual

Direction: mobile station to network

Table 9.12d/3GPP TS 04.08: CONFIGURATION CHANGE REJECT message contents

9.1.13 Frequency redefinition

This message is sent on the main DCCH from the network to the MS to indicate that the frequencies and the hopping sequence of the allocated channels shall be changed. See table 9.13/3GPP TS 04.08

Message type: FREQUENCY REDEFINITION

Significance: dual

Direction: network to MS

Table 9.13/3GPP TS 04.08: FREQUENCY REDEFINITION message content

9.1.13.1 Cell Channel Description

If it does not appear, the cell channel description is assumed to be unchanged.

9.1.13a PDCH Assignment command

This message is sent on the main DCCH by the network to the mobile station to change the channel configuration to a PDCH, when no timing adjustment is needed. See table 9.13a/3GPP TS 04.08.

A mobile station that does not support the <<GRPS>> option shall regard this message as an unknown message.

Message type: PDCH ASSIGNMENT COMMAND

Significance: dual

Direction: network to mobile station

Table 9.13a/3GPP TS 04.08: PDCH ASSIGNMENT COMMAND message content

9.1.13a.1 Mobile Allocation and Frequency List, after the starting time

If the channel description for after the starting time indicates frequency hopping, one and only one of the following information elements shall be present

– Mobile Allocation, after time;

– Frequency List, after time.

If the Channel Description IE for after time does not indicate frequency hopping, if decoding of Channel Description IE for before time does not require a frequency list for after time (see next sub-clause), and one or both of the two information elements are present they shall be considered as IEs unnecessary in the message.

9.1.13a.2 Starting Time

The starting time information element is included when the network wants the mobile station to change the frequency parameters of the channels more or less at the moment the change to a TBF occurs. In this case a number of information elements may be included to give the frequency parameters to be used before the starting time.

If the starting time information element is present and none of the information elements referring to before the starting time are present, the mobile station waits and uses the TBFfrom the indicated time.

If the starting time information element is present and at least one of the information elements referring to before the starting time is present, the mobile station does not wait for the indicated time and uses the TBF using the frequency parameters for before the starting time.

If the starting time information element is not present and some of the information elements referring to before the starting time is present, these information elements shall be considered as IEs unnecessary in the message.

If the description of the channel, before time IE is not present, the channel description to apply for before the time, if needed, is given by the description of the channel, after time IE.

If the starting time IE is present and the channel description for before the starting time indicates frequency hopping, one and only one of the following information elements may be present and applies before the starting time:

– Mobile Allocation, before time IE;

– Frequency list, before time IE;

– Frequency channel sequence, before time IE.

If the starting time IE is present and the channel description for before the starting time indicates frequency hopping, and none of the above mentioned IE is present, a frequency list for after the starting time must be present (see sub-clause 9.1.2.4), and this list applies also for the TBF before the starting time.

9.1.13a.3 Reference cell frequency list

If any of the mobile allocation information elements are present, then the network shall ensure that either the mobile station has received in a previous message the proper reference cell frequency list (CA), or that the cell channel description IE is present.

If the cell channel description IE is present, it is used to decode the mobile allocation IEs in the message, as well as in later dedicated mode messages until reception of a new reference cell frequency list or the cell is left.

9.1.13a.4 Cell Channel Description

If present, this information element shall be used to decode the Mobile Allocation IE in the same message and in subsequent messages.

9.1.13a.5 Packet Assignment

One and only one of the following information elements shall be present:

– RR Packet Uplink Assignment;

– RR Packet Downlink Assignment.

9.1.13b GPRS suspension request

This message is sent on the main DCCH by the mobile station to the network to request a suspension of GPRS services. See table 9.13b/3GPP TS 04.08.

Message type: GPRS SUSPENSION REQUEST

Significance: dual

Direction: mobile station to network

Table 9.13b/3GPP TS 04.08: GPRS SUSPENSION REQUEST message content

9.1.14 Handover access

This message is sent in random mode on the main DCCH during a handover procedure. It does not follow the basic format. The format is presented directly below without reference to information elements. The order of bit transmission is defined in 3GPP TS 04.04.

This message is only one octet long, coded as shown in figure 9.2/3GPP TS 04.08 and table 9.14/3GPP TS 04.08.

8 7 6 5 4 3 2 1

+———————————————–+

│ handover reference │ octet 1

+———————————————–+

Figure 9.2/3GPP TS 04.08: HANDOVER ACCESS message content

Table 9.14/3GPP TS 04.08: HANDOVER ACCESS message content

+———————————————————-+

│ │

│ HANDOVER REFERENCE │

│ This is an unformatted 8 bit field. │

│ (also described in sub-clause 10.5.2.15) │

│ │

+———————————————————-+

9.1.15 Handover command

This message is sent on the main DCCH by the network to the mobile station to change the dedicated channel configuration, timing adjustment needed. See table 9.15/3GPP TS 04.08.

Message type: HANDOVER COMMAND

Significance: dual

Direction: network to mobile station

Table 9.15/3GPP TS 04.08: HANDOVER COMMAND message content

9.1.15.1 Synchronization Indication

If this information element does not appear, the assumed value is "non-synchronized".

9.1.15.2 Mode of the First Channel (Channel Set 1) and Mode of Channel Set "X" (2=<X<=8)

If this information element is not present the channel mode of the previously allocated channel or channels for Channel Set "X" (1=<X<=8) shall be assumed.

If Channel Set "X" is not defined for the configuration, the Mode of Channel Set "X" IE shall be considered as an IE unnecessary in the message.

NOTE: Sub-clause 3.4.4.1 defines cases when one or several Mode of Channel Set "X" IEs shall be included in the message.

9.1.15.3 Description of the Second Channel

These information element appear if the mobile station carries two connections (on two dedicated channels, for the TCH/H+TCH/H configuration).

The connection using the channel previously defined in the Description of the First Channel IE of an ASSIGNMENT COMMAND or HANDOVER COMMAND message shall use the channel defined in the first channel description IE of the HANDOVER COMMAND message defining the new configuration.

The channel described in the Description of the First Channel IE carries the main DCCH. The SACCH used is the one associated with that channel.

9.1.15.4 Mode of the Second Channel

If the Description of the Second Channel IE is not present and the information element is present it shall be considered as an IE unnecessary in the message.

This element appears at least when the channel mode is changed for the channel defined in the Description of the Second Channel information element.

9.1.15.5 Frequency Channel Sequence, Frequency List, Frequency short list and Mobile Allocation, after time

If at least one of the channel descriptions for after time indicates frequency hopping, one and only one of the following information elements shall be present:

– Frequency Channel Sequence, after time;

– Frequency list, after time;

– Frequency Short List, after time;

– Mobile Allocation, after time.

If neither of the Channel Description IEs indicate frequency hopping, if they are not required for the decoding of Channel Description IEs for before time, and if any of the four information elements are present they shall be considered as IEs unnecessary in the message.

The Frequency Channel Sequence information element shall not be used unless all the ARFCNs that it indicates are in the P-GSM band.

9.1.15.6 Starting Time

The starting time information element is included when the network wants the mobile station to change the frequency parameters of the channels more or less at the moment a change of channel occurs. In this case a number of information elements may be included to give the frequency parameters to be used before the starting time.

The starting time information element refers to the new cell time.

If the starting time information element is present and none of the information elements referring to before the starting time are present, the mobile station waits and accesses the channels at the indicated time.

If the starting time information element is present and at least one of the information elements referring to before the starting time is present, the mobile station does not wait for the indicated time and accesses the channel using the frequency parameters for before the starting time.

If the starting time information element is not present and some of the information elements referring to before the starting time is present, these information elements shall be considered as IEs unnecessary in the message.

If the description of the first channel, before time IE is not present, the channel description to apply for before the time, if needed, is given by the description of the first channel, after time IE.

If the description of the second channel, after time IE is present, the description of the second channel, before time IE not present, and a description of the configuration for before the time needed, the channel configuration before the starting time is nevertheless of two traffic channels, and the channel description to apply to the second channel before the starting time is given by the description of the second channel, after time IE.

If the starting time IE is present and at least one of the channel descriptions for before the starting time indicates frequency hopping, one and only one of the following information elements may be present and applies before the starting time to all assigned channels:

– Mobile Allocation, before time IE;

– Frequency Short list, before time IE;

– Frequency list, before time IE;

– Frequency channel sequence, before time IE.

If the starting time IE is present and at least one of the channel descriptions for before the starting time indicates frequency hopping, and none of the above mentioned IE is present, a frequency list for after the starting time must be present (see 9.1.2.4), and this list applies also for the channels before the starting time.

9.1.15.7 Reference cell frequency list

If any of the mobile allocation information elements is present, then the cell channel description IE must be present. It is used to decode the mobile allocation IEs in the message.

In addition, if no information elements pertaining to before the starting time is present in the message, the frequency list defined by the cell channel description IE is used to decode the mobile allocation IEs in later messages received in the new cell until reception of a new reference cell frequency list or the new cell is left.

9.1.15.8 Real Time Difference

This information element shall appear if the Synchronization Indication information element indicates a pseudo‑synchronous handover otherwise it shall be considered as an unnecessary information element.

9.1.15.9 Timing Advance

This information element shall appear if the "synchronization indication" element indicates a presynchronized handover. If not included for a presynchronized handover, then the default value as defined in 3GPP TS 05.10 shall be used. For other types of handover it shall be considered as an unnecessary information element.

9.1.15.10 Cipher Mode Setting

If this information element is omitted, the mode of ciphering is not changed after the mobile station has switched to the assigned channel.

Only applicable for mobile stations supporting VGCS talking:

The cipher mode setting IE shall not be included if a HANDOVER COMMAND message is sent on a VGCS channel or in a HANDOVER COMMAND message on a dedicated channel for a handover to a VGCS channel.

9.1.15.11 VGCS target mode indication

This information element is identified as "comprehension required". Only mobile stations supporting "VGCS talking " are required to accept the presence of the element. The presence of the element shall trigger an exception handling if received by a mobile station not supporting "VGCS talking ".

This IE indicates which mode is to be used on the new channel (i.e. dedicated mode or group transmit mode). If this information element is not present, the mode shall be the same as on the previous channel.

The IE also indicates the group cipher key number for the group cipher key to be used on the new channel or if the new channel is non ciphered. If the information element is not present, the ciphering mode shall be the same as on the previous channel.

NOTE: A mobile station supporting VGCS Talking shall not consider a syntactical error if this IE is present and the channel mode is not speech.

9.1.15.12 Description of the multislot allocation

This information element is included if so indicated by the channel type and TDMA offset field in the Channel Description information element and is used to assign channels that do not carry a main signalling link in a multislot configuration. It indicates how the used timeslots are divided into separate channel sets.

If the Channel Description IE does not require the presence the information element it shall be considered as an IE unnecessary in the message.

If multislot configuration is indicated by the Channel Description IE but the Multislot Allocation IE is not present, all channels in the configuration belong to one channel set, "Channel Set 1".

NOTE: As a change of timeslot number cannot occur for the channel described for after the starting time, the Multislot Allocation IE does not have to be included more than once.

9.1.15.13 MultiRateconfiguration

This information element appears if the Mode of the First Channel indicates a multi-rate speech codec, and if the assigned configuration is new, i.e. it is different from the MultiRateconfiguration used in the serving cell. If the Mode of the First Channel indicates a multi-rate speech codec, and this IE is not included, then the mobile station shall assume that the MultiRateconfiguration has not changed.

9.1.16 Handover complete

This message is sent on the main DCCH from the mobile station to the network to indicate that the mobile station has established the main signalling link successfully. See table 9.16/3GPP TS 04.08.

Message type: HANDOVER COMPLETE

Significance: dual

Direction: mobile station to network

Table 9.16/3GPP TS 04.08: HANDOVER COMPLETE message content

9.1.16.1 Mobile Observed Time Difference

This information element is included if and only if the Synchronization Indication IE in the HANDOVER COMMAND message requests it to be sent.

9.1.17 Handover failure

This message is sent on the main DCCH on the old channel from the mobile station to the network to indicate that the mobile station has failed to seize the new channel. See table 9.17/3GPP TS 04.08.

Message type: HANDOVER FAILURE

Significance: dual

Direction: mobile station to network

Table 9.17/3GPP TS 04.08: HANDOVER FAILURE message content

9.1.18 Immediate assignment

This message is sent on the CCCH by the network to the mobile station in idle mode to change the channel configuration to a dedicated configuration while staying in the same cell or to the mobile station in packet idle mode to change the channel configuration to either an uplink or a downlink packet data channel configuration in the cell. See table 9.18/3GPP TS 04.08.

The L2 pseudo length of this message is the sum of lengths of all information elements present in the message except the IA Rest Octets and L2 Pseudo Length information elements.

Message type: IMMEDIATE ASSIGNMENT

Significance: dual

Direction: network to mobile station

Table 9.18/3GPP TS 04.08: IMMEDIATE ASSIGNMENT message content

9.1.18.0a Dedicated mode or TBF

A mobile station not supporting GPRS may ignore the contents of this information element and regard it as an unnecessary IE. Such mobile station shall assume that this message assigns a dedicated mode resource.

9.1.18.0b Channel Description

If the Dedicated mode or TBF IE indicates that the message assigns a dedicated mode resource, the mobile station shall consider this information element present in the message.

9.1.18.0c Packet Channel Description

If the Dedicated mode or TBF IE indicates that the message assigns a Temporary Block Flow (TBF), the mobile station shall consider this information element present in the message. If the Dedicated mode or TBF IE indicates that this message is the first of two in a two-message assignment of an uplink or downlink TBF, the mobile station shall ignore the contents of this information element and regard it as an unnecessary IE.

9.1.18.0d Request Reference

If this message is used in an assignment of a downlink TBF, the network shall code this information element, e.g. by using a suitably offset frame number, such that the resource reference cannot be confused with any CHANNEL REQUEST message sent by a mobile station.

If the IA Rest Octets IE indicates that this message is the second message of a two-message assignment of an uplink or downlink TBF, this information element shall have the same contents as the first message of the assignment.

9.1.18.0e Timing Advance

If the IA Rest Octets IE indicates that this message is the second message of a two-message assignment of an uplink or downlink TBF, the mobile station shall ignore the contents of this information element and regard it as an unnecessary IE.

9.1.18.1 Mobile Allocation

If this message assigns a dedicated mode resource and the Channel Description IE does not indicate frequency hopping , the length indicator of this information element shall be set to zero, and the mobile station shall consider the IE as an unnecessary IE.

If this message assigns a TBF and the Packet Channel Description IE does not indicate frequency hopping or if it uses indirect encoding of a hopping RF channel configuration, the length indicator of this information element shall be set to zero, and the mobile station shall consider the IE as an unnecessary IE.

9.1.18.2 Starting Time

This information element appears if e.g. a frequency change is in progress.

If this message is used in an assignment of an uplink or downlink TBF, the mobile station shall ignore the contents of the Starting Time information element if included and consider it as an unnecessary IE.

9.1.18.3 IA Rest Octets (Frequency parameters, before time)

The sum of the length of this IE and the L2 Pseudo Length of the message equals 22.

If the starting time IE is present but not the frequency parameters, before time construction, the mobile stations must wait until the starting time before accessing the channel.

If the starting time IE is present and the Channel Description IE does not indicate frequency hopping the mobile station shall consider the frequency parameters, before time construction as unnecessary in the message and the mobile must wait until the starting time before accessing the channel.

If the starting time IE is not present, the mobile station shall consider the frequency parameters, before time construction as unnecessary in the message.

9.1.18.4 IA Rest Octets (assignment of uplink or downlink TBF)

If the Dedicated mode or TBF IE indicates that this message is used in an assignment of a TBF, this information element shall contain a Packet Uplink Assignment, Packet Downlink Assignment or Second Part Packet Assignment construction.

If the Dedicated mode or TBF IE indicates that this message assigns a dedicated mode resource, but not that the mobile station is identified in the IA Rest Octets IE information element, the mobile station shall consider the Packet Uplink Assignment, Packet Downlink Assignment and Second Part Packet Assignment constructions as unnecessary in the message.

9.1.19 Immediate assignment extended

This message is sent on the CCCH by the network to two mobile stations in idle mode to change their channel configurations to different dedicated configurations while they stay in the same cell. See table 9.19/3GPP TS 04.08

The L2 pseudo length of this message is the sum of lengths of all information elements present in the message except the IAX Rest Octets and L2 Pseudo Length information elements.

Message type: IMMEDIATE ASSIGNMENT EXTENDED

Significance: dual

Direction: network to mobile station

Table 9.19/3GPP TS 04.08: IMMEDIATE ASSIGNMENT EXTENDED message content

NOTE: Index 1 refers to the first mobile station, index 2 refers to the second mobile station.

9.1.19.1 Unnecessary IEs

A mobile station which reacts on the request reference 1 shall consider all information elements as unnecessary IEs except for Requests Reference 1, Channel Description 1, Timing advance 1, Starting Time and if Channel Description 1 IE indicates frequency hopping mobile allocation.

A mobile station which reacts on the request reference 2 shall consider all information elements as unnecessary IE except Requests Reference 2, Channel Description 2, Timing advance 2, Starting Time and if channel description 2 IE indicates frequency hopping mobile allocation.

A mobile station in idle mode shall consider all information elements as unnecessary IEs except for the Page Mode IE.

9.1.19.2 Mobile Allocation

If both channel description IE do not indicate frequency hopping, the length indicator shall be set to zero.

9.1.19.3 Starting Time

This information element appears if a frequency change is in progress. If included the starting time is common to the two referenced mobile stations.

9.1.19.4 Maximum message length

As the maximum length of the resulting layer 3 data cannot exceed 22 octets, it is not possible to use this message type if the total length of the value part of the Mobile Allocation plus, optionally, the length of the Starting Time IE exceeds 5 octets. In this case it is necessary to use the IMMEDIATE ASSIGNMENT message.

9.1.19.5 IAX Rest Octets

The sum of the length of this IE and the L2 Pseudo Length of the message equals 22.

9.1.20 Immediate assignment reject

This message is sent on the CCCH by the network to up to four mobile stations to indicate that no channel is available for assignment. See table 9.20/3GPP TS 04.08. This message has L2 pseudo length 19.

Message type: IMMEDIATE ASSIGNMENT REJECT

Significance: dual

Direction: network to mobile station

Table 9.20/3GPP TS 04.08: IMMEDIATE ASSIGNMENT REJECT message content

NOTE: Index 1 refers to the first mobile station, index 2 refers to the second MS and so on.

9.1.20.1 Use of the indexes

A request reference information element and the following wait indication information element refer to the same mobile station. So it is possible to reject up to four channel requests with this message.

9.1.20.2 Filling of the message

If necessary the request reference information element and the wait indication information element should be duplicated to fill the message.

9.1.20.3 Wait Indication

When IMMEDIATE ASSIGNMENT REJECT message is for RR connection establisment then this IE contains timeout value for T3122. If IMMEDIATE ASSIGNMENT REJECT message is for TBF establisment for GPRS MS then this IE contain timeout value for T3142.

9.1.20.4 IAR Rest Octets

The sum of the length of this IE and the L2 Pseudo Length of the message equals 22.

9.1.21 Measurement report

This message is sent on the SACCH by the mobile station to the network to report measurement results about the dedicated channel and about neighbour cells. See table 9.21/3GPP TS 04.08.

Message type: MEASUREMENT REPORT

Significance: dual

Direction: mobile station to network

Table 9.21/3GPP TS 04.08: MEASUREMENT REPORT message content

9.1.21a Notification/FACCH

The understanding of this message is only required for mobile stations supporting VGCS listening or VBS listening.

This message is sent on the main DCCH, in unacknowledged mode using the RR short protocol discriminator by the network to notify the mobile stations in dedicated mode or in on-going voice broadcast calls or voice group calls on other voice broadcast calls or voice group calls in that cell.

Notification/FACCH messages for VBS or VGCS calls are differentiated by a flag in the call reference.

The message shall not exceed a maximum length of 20 octets.

Mobile stations not supporting VGCS listening or VBS listening shall ignore this message.

See table 9.21a/3GPP TS 04.08.

Message type: NOTIFICATION/FACCH

Significance: dual

Direction: network to mobile station

Table 9.21a/3GPP TS 04.08: NOTIFICATION/FACCH message content

<NOTIFICATION FACCH> ::= <RR short PD : bit> — See 3GPP TS 04.07

<message type : bit(5)> — See 10.4

<short layer 2 header : bit(2)> — See 3GPP TS 04.06

{0 <Group Call information>

|1 <Paging Information>} 

<spare padding> ;

<Group Call information> ::= <Group Call Reference : bit(36)>

{0|1 <Group Channel Description>} ;

<Group Call Reference>

This field is syntactically and semantically equivalent to octets 2-5 and bits 5 to 8 of octet 6 of the Descriptive Group or Broadcast Call Reference information element.

The <Group Channel Description> field is optionally present. When present only the Channel description is provided in the case of non hopping channels. In the case where the channel is hopping then either a mobile allocation or a frequency short list is provided.

<Group Channel Description> : := <Channel Description : bit(24)>

{0 — Non hopping case

|1 {0 <Mobile Allocation : <bit string>>

|1 <Frequency Short List : bit(64)>}} ;

<bit string> ::= null | bit <bit string> ;

<Channel Description>

This field is syntactically and semantically equivalent to octets 2-4 of the Channel Description information element. See sub-clause 10.5.2.5

<Frequency Short List>

This field is syntactically and semantically equivalent to octets 1-8 of the Frequency Short List 2 information element. See sub-clause 10.5.2.14a

<Mobile Allocation>

This field is syntactically and semantically equivalent to octet 2 to n+2 of the Mobile Allocation information element. See sub-clause 10.5.2.21

The <Paging Information> field may be used to inform the mobile station in Group Receive or in Group Transmit mode that the corresponding mobile identity is paged in that cell.

<Paging Information> ::= <mobile identity : <bit string>>

<channel first: bit(2)>

{0|1 <eMLPP priority : bit(3)>} ;

<bit string> ::= null | bit <bit string> ;

<mobile identity>

This field is syntactically and semantically equivalent to octet 2-n of the Mobile Identity information element. See sub-clause 10.5.1.4.

<channel first>

This field is syntactically and semantically equivalent to bits 1 and 2 of the Channel Needed information element. See sub-clause 10.5.2.8.

<eMLPP priority>

This field is coded as the <Priority1> field in the P1 Rest Octets information element. See sub-clause 10.5.2.23

9.1.21a.1 Spare

9.1.21a.2 Spare

9.1.21a.3 Spare

9.1.21a.4 Spare

9.1.21b Notification/NCH

The understanding of this message is only required for mobile stations supporting VGCS listening or VBS listening.

This message is sent on the NCH by the network to notify mobile stations of VBS or VGCS calls in the current cell. The VBS or VGCS calls are identified by their broadcast call reference or group call reference, respectively. For each reference, the corresponding VBS or VGCS call channel may be indicated. See table 9.21b/3GPP TS 04.08.

Notification/NCH messages for VBS or VGCS calls are differentiated by a flag in the call reference.

The L2 pseudo length of this message has a value one

Mobile stations not supporting VGCS listening or VBS listening shall ignore this message.

Message type: NOTIFICATION/NCH

Significance: dual

Direction: network to mobile station

Table 9.21b/3GPP TS 04.08: NOTIFICATION/NCH message content

9.1.21b.1 Spare

9.1.21b.2 Spare

9.1.21d Notification response

This message is sent by the mobile station to the network to respond on a notification for a voice group call or voice broadcast call. See table 9.21d/3GPP TS 04.08.

Message type: NOTIFICATION RESPONSE

Significance: dual

Direction: mobile station to network

Table 9.21d/3GPP TS 04.08: NOTIFICATION RESPONSE message content

9.1.21e RR-Cell Change Order

This message is sent on the main DCCH by the network to the mobile station to order it to reselect a cell. See table 9.21e/3GPP TS 04.08.

A mobile station that does not support the <<GRPS>> option shall regard this message as an unknown message.

Message type: RR-CELL CHANGE ORDER

Significance: dual

Direction: network to mobile station

Table 9.21e/3GPP TS 04.08: RR-CELL CHANGE ORDER message content

9.1.22 Paging request type 1

This message is sent on the CCCH by the network to up to two mobile stations. It may be sent to a mobile station in idle mode to trigger channel access. It may be sent to a mobile station in packet idle mode to transfer MM information (i.e. trigger of cell update procedure). The mobile stations are identified by their TMSI/P-TMSI or IMSI. See table 9.22/3GPP TS 04.08.

The L2 pseudo length of this message is the sum of lengths of all information elements present in the message except the P1 Rest Octets and L2 Pseudo Length information elements.

Message type: PAGING REQUEST TYPE 1

Significance: dual

Direction: network to mobile station

Table 9.22/3GPP TS 04.08: PAGING REQUEST TYPE 1 message content

9.1.22.1 Unnecessary IE

A mobile station in idle mode shall consider all information elements as unnecessary IEs except for the Page Mode IE.

9.1.22.2 Channels needed for Mobiles 1 and 2

The first CHANNEL field of Channel Needed IE is associated with Mobile Identity 1. The second CHANNEL field of Channel Needed IE is associated with Mobile Identity 2.

If this message is used in the packet paging procedure, the Channel Needed IE associated with the corresponding Mobile Identity 1 or 2 shall be coded with the value 00 (any channel) by the network. The mobile station receiving a packet paging request shall treat this information element as unnecessary in the message.

9.1.22.3 Mobile Identities

The Mobile Identity 1 and 2 IEs shall not refer to IMEI.

9.1.22.4 P1 Rest Octets

The sum of the length of this IE and the L2 Pseudo Length of the message equals 22.

This IE may contain a notification list number field and/or, referring to each one of the Mobile Identity 1 and 2 IEs, a Priority 1 and 2 field and/or a Packet Page Indication 1 and 2 field.

9.1.23 Paging request type 2

This message is sent on the CCCH by the network to two or three mobile stations. It may be sent to a mobile station in idle mode to trigger channel access. It may be sent to a mobile station in packet idle mode to transfer MM information (i.e. trigger of cell update procedure). Two of the mobile stations are identified by their TMSI/P-TMSI while the third is identified by its TMSI/P-TMSI or IMSI. See table 9.23/3GPP TS 04.08.

The L2 pseudo length of this message is the sum of lengths of all information elements present in the message except the P2 Rest Octets and L2 Pseudo Length information elements.

Message type: PAGING REQUEST TYPE 2

Significance: dual

Direction: network to mobile station

Table 9.23/3GPP TS 04.08: PAGING REQUEST TYPE 2 message content

9.1.23.1 Channels needed for Mobiles 1 and 2

The first CHANNEL field of Channel Needed IE is associated with Mobile Identity 1. The second CHANNEL field of Channel Needed IE is associated with Mobile Identity 2.

If this message is used in the packet paging procedure, the Channel Needed IE associated with the corresponding Mobile Identity 1 or 2 shall be coded with the value 00 (any channel) by the network. The mobile station receiving a packet paging request shall treat this information element as unnecessary in the message.

9.1.23.2 Mobile Identity 3

The Mobile Identity 3 information element shall not refer to IMEI.

9.1.23.3 P2 Rest Octets

The sum of the length of this IE and the L2 Pseudo Length of the message equals 22.

This IE contains the channel needed indication related to the paging of Mobile Identity 3. The treatment of this indication in the case this message is used in a packet paging procedure is specified in sub-clause 9.1.23.1.

This IE may further contain a notification list number field and/or, referring to each one of the Mobile Identity 1, 2 and 3 IEs, a Priority 1, 2 and 3 field and/or, referring to the Mobile Identity 3 IE, a Packet Page Indication 3 field.

9.1.24 Paging request type 3

This message is sent on the CCCH by the network to four mobile stations. It may be sent to a mobile station in idle mode to trigger channel access. It may be sent to a mobile station in packet idle mode to transfer MM information (i.e. trigger of cell update procedure). The mobile stations are identified by their TMSIs/P-TMSIs. See table 9.24/3GPP TS 04.08.

This message has a L2 Pseudo Length of 19.

Message type: PAGING REQUEST TYPE 3

Significance: dual

Direction: network to mobile station

Table 9.24/3GPP TS 04.08: PAGING REQUEST TYPE 3 message content

9.1.24.1 Channels needed for Mobiles 1 and 2

The first CHANNEL field of Channel Needed IE is associated with Mobile Identity 1. The second CHANNEL field of Channel Needed IE is associated with Mobile Identity 2.

If this message is used in the packet paging procedure, the Channel Needed IE associated with the corresponding Mobile Identity 1 or 2 shall be coded with the value 00 (any channel) by the network. The mobile station receiving a packet paging request shall treat this information element as unnecessary in the message.

9.1.24.2 P3 Rest Octets

This IE contains the channel needed indication related to the paging of Mobile Identity 3 and 4. The treatment of these indications in the case this message is used in a packet paging procedure is specified in sub-clause 9.1.24.1.

This IE may further contain a notification list number field and/or, referring to each one of the Mobile Identity 1, 2, 3 and 4 IEs, a Priority 1, 2, 3 and 4 field.

9.1.25 Paging response

This message is sent on the main DCCH by the mobile station to the network in connection with establishment of the main signalling link as a response to the paging request message. See table 9.25/3GPP TS 04.08.

Message type: PAGING RESPONSE

Significance: dual

Direction: mobile station to network

Table 9.25/3GPP TS 04.08: PAGING RESPONSE message content

9.1.25.1 Mobile Station Classmark

This IE shall include for multiband mobile station the Classmark 2 corresponding to the frequency band in use.

9.1.26 Partial release

This message is sent on the main DCCH by the network to the mobile station to deactivate part of the dedicated channels in use. See table 9.26/3GPP TS 04.08.

Message type: PARTIAL RELEASE

Significance: dual

Direction: network to mobile station

Table 9.26/3GPP TS 04.08: PARTIAL RELEASE message content

9.1.26.1 Channel Description

This information element describes the channel to be released.

9.1.27 Partial release complete

This message is sent on the main DCCH by the mobile station to the network to indicate that a part of the dedicated channels has been deactivated. See table 9.27/3GPP TS 04.08.

Message type: PARTIAL RELEASE COMPLETE

Significance: dual

Direction: mobile station to network

Table 9.27/3GPP TS 04.08: PARTIAL RELEASE COMPLETE message content

9.1.28 Physical information

This message is sent on the main DCCH by the network to the mobile station to stop the sending of access bursts from the mobile station. See table 9.28/3GPP TS 04.08.

Message type: PHYSICAL INFORMATION

Significance: dual

Direction: network to mobile station

Table 9.28/3GPP TS 04.08: PHYSICAL INFORMATION message content

9.1.28.a RR Initialisation Request

This message is sent on the main DCCH by the mobile station to request establishment of dedicated mode.

Message type: RR Initialisation Request

Significance: local

Direction: mobile station to network

Table 9.28a/3GPP TS 04.08: RR Initialisation Request message content

9.1.29 RR Status

This message is sent by the mobile station or the network at any time to report certain error conditions as described in clause 8. See table 9.28a/3GPP TS 04.08.

Message type: RR STATUS

Significance: local

Direction: both

Table 9.28a/3GPP TS 04.08: RR STATUS message content