11.2.29 Packet Uplink Assignment

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

This message is sent on the PCCCH or PACCH by the network to the mobile station to assign uplink resources. If the mobile station supports Downlink Dual Carrier or Downlink Multi Carrier, this message may be sent using extended RLC/MAC control message segmentation (see sub-clause 9.1.12a). The mobile station may be addressed by TFI, TQI, or Packet Request Reference depending upon the procedure used. A mobile allocation or reference frequency list received as part of this assignment message shall be valid until new assignment is received or each TBF of the MS are terminated.

Message type: PACKET UPLINK ASSIGNMENT

Direction: network to mobile station

Classification: non-distribution message

Table 11.2.29.1: Packet UPlink ASSIGNMENT information elements

< Packet Uplink Assignment message content > ::=

< PAGE_MODE : bit (2) >

{ 0 | 1 <PERSISTENCE_LEVEL : bit (4) > * 4 }

{ { 0 < Global TFI : < Global TFI IE > >

| 10 < TLLI / G-RNTI : bit (32) >

| 110 < TQI : bit (16) >

| 111 < Packet Request Reference : < Packet Request Reference IE > > }

{ 0 — Message escape

{ < CHANNEL_CODING_COMMAND : bit (2) >

< TLLI_BLOCK_CHANNEL_CODING : bit (1) >

< Packet Timing Advance : < Packet Timing Advance IE > >

{ 0 | 1 < Frequency Parameters : < Frequency Parameters IE > > }

{ 01 < Dynamic Allocation : < Dynamic Allocation struct > >

| 10 < Single Block Allocation : < Single Block Allocation struct > >

| 00 < extension >

} — The value ’11’ was allocated in an earlier version of the protocol and shall not be used.

{ null | 0 bit** = < no string > — Receiver backward compatible with earlier version

| 1 — Additions for R99

{ 0 | 1 < Packet Extended Timing Advance : bit (2) > }

{ null | 0 bit** = <no string> — Receiver backward compatible with earlier version

| 1 — Additions for Rel-5

{ 0 | 1 < G-RNTI extension : bit (4) > }

{ 0 | 1 < RB Id : bit (5) > }

{ null | 0 bit** = <no string> — Receiver backward compatible with earlier version

| 1 — Additions for Rel-6

{ 0 | 1 < PFI : bit (7) > }

{ 0 | 1 < RLC_MODE : bit (1) > }

{ null | 0 bit** = < no string > — Receiver backward compatible with earlier version

| 1 — Additions for Rel-12

< Primary TSC Set : bit (1) >

< padding bits > } } } }

! < Non-distribution part error : bit (*) = < no string > > }

| 1 — Message escape bit used to define EGPRS message contents

{ 00 { { 0 | 1 < CONTENTION_RESOLUTION_TLLI : bit(32) > }

{ 0 | 1 < COMPACT reduced MA : < COMPACT reduced MA IE >> }

< EGPRS Channel Coding Command : < EGPRS Modulation and Coding Scheme IE >>

< RESEGMENT : bit (1) >

< EGPRS Window Size : < EGPRS Window Size IE > >

{ 0 | 1 < Access Technologies Request : Access Technologies Request struct >}

< ARAC RETRANSMISSION REQUEST : bit (1) >

< TLLI_BLOCK_CHANNEL_CODING : bit (1) >

{ 0 | 1 < BEP_PERIOD2 : bit (4) > }

< Packet Timing Advance : < Packet Timing Advance IE > >

{ 0 | 1 < Packet Extended Timing Advance : bit (2) > }

{ 0 | 1 < Frequency Parameters : < Frequency Parameters IE > > }

{ 01 < Dynamic Allocation : < Dynamic Allocation struct > >

| 10 < Multi Block Allocation : < Multi Block Allocation struct > >

| 00 < extension >

} — The value ’11’ was allocated in an earlier version of the protocol and shall not be used.

{ null | 0 bit** = <no string> — Receiver backward compatible with earlier version

| 1 — Additions for Rel-5

{ 0 | 1 < G-RNTI extension : bit (4) > }

{ 0 | 1 < RB Id : bit (5) > }

{ null | 0 bit** = <no string> — Receiver backward compatible with earlier version

| 1 — Additions for Rel-6

{ 0 | 1 < PFI : bit (7) > }

{ 0 | 1 < RLC_MODE : bit (1) > }

{ null | 0 bit** = < no string > — Receiver backward compatible with earlier version

| 1 — Additions for Rel-7

{ 0 | 1 < NPM Transfer Time : bit (5) > }

{ null | 0 bit** = < no string > — Receiver backward compatible with earlier version

| 1 — Additions for Rel-9

< Indication of Upper Layer PDU Start for RLC UM: bit >

< Enhanced Flexible Timeslot Assignment : bit >

{ 0 < EMST_NW_Capability : bit (1) > — EMST is not used

| 1 < RLC Entity 2 : < RLC Entity Struct > > — EMST is used

{ 0

| 1 < RLC Entity 3 : < RLC Entity Struct > > }

}

{ null | 0 bit** = < no string > — Receiver backward compatible with earlier version

| 1 — Additions for Rel-10

{ 1 < EMSR Additional PFCs 1 : < Additional PFCs struct > > } ** 0

{ 1 < EMSR Additional PFCs 2 : < Additional PFCs struct > > } ** 0

{ 1 < EMSR Additional PFCs 3 : < Additional PFCs struct > > } ** 0

{ null | 0 bit** = < no string > — Receiver backward compatible with earlier version

| 1 — Additions for Rel-12

< Primary TSC Set : bit (1) >

< padding bits > } } } } } }

! < Non-distribution part error : bit (*) = < no string > > }

| 01 — Message escape for dual carrier, RTTI, BTTI with FANR activated, EGPRS2

{ { 0 | 1 < CONTENTION_RESOLUTION_TLLI : bit(32) > }

< RESEGMENT : bit (1) >

< Assignment Info : Assignment Info struct >

< EGPRS Window Size : < EGPRS Window Size IE > >

{ 0 | 1 < Access Technologies Request : Access Technologies Request struct > }

< ARAC RETRANSMISSION REQUEST : bit (1) >

< TLLI_BLOCK_CHANNEL_CODING : bit (1) >

{ 0 | 1 < BEP_PERIOD2 : bit (4) > }

< Packet Timing Advance : < Packet Timing Advance IE > >

{ 0 | 1 < Packet Extended Timing Advance : bit (2) > }

{ 0 — BTTI mode

| 1 — RTTI mode

< RTTI_USF_MODE : bit (1) >

< PDCH Pairs Description : < PDCH Pairs Description IE > > }

< Dynamic Allocation 2: < Dynamic Allocation 2 struct > >

< EGPRS Channel Coding Command : < EGPRS Modulation and Coding Scheme IE >>

{ 00 — No frequency parameters included

| 01 — Legacy IEs used

{ 0 | 1 < Frequency Parameters C1 : < Frequency Parameters IE > > }

{ 0 | 1 < Frequency Parameters C2 : < Frequency Parameters IE > > }

| 10 — Optimized Dual Carrier frequency parameters used

< Dual Carrier Frequency Parameters : < Dual Carrier Frequency Parameters IE > >

! < Frequency Parameters error: { 11 } bit(*) = < no string> > — reserved for future used

}

{ 0 | 1 < PFI : bit (7) > }

{ 0 | 1 < RLC_MODE : bit (1) > }

{ 0 | 1 < NPM Transfer Time : bit (5) > }

{ 0 | 1 — ‘1’ indicates that FANR is activated

{ 0 — SSN-based encoding is selected

| 1 — Time-based encoding is selected

< REPORTED TIMESLOTS C1 : bit (8) > — carrier 1 in Downlink Dual Carrier

–configuration

{ 0 | 1 < REPORTED TIMESLOTS C2 : bit (8) > } — carrier 2 in Downlink Dual Carrier

configuration

< TSH : bit (2) > } }

< Uplink EGPRS Level: < EGPRS Level IE > >

{ 0 | 1 < Pulse Format: < Pulse Format IE > > }

{ null | 0 bit** = < no string > — Receiver backward compatible with earlier version

| 1 — Additions for Rel-9

< Indication of Upper Layer PDU Start for RLC UM: bit >

< Enhanced Flexible Timeslot Assignment : bit >

{ 0 < EMST_NW_Capability : bit (1) > — EMST is not used

| 1 < RLC Entity 2 : < RLC Entity Struct > > — EMST is used

{ 0

| 1 < RLC Entity 3 : < RLC Entity Struct > > }

}

{ 0 | 1 MTTI_UPLINK_ASSIGNMENT_C1 : bit (1) }

{ 0 | 1 MTTI_UPLINK_ASSIGNMENT_C2 : bit (1) }

{ null | 0 bit** = < no string > — Receiver backward compatible with earlier version

| 1 — Additions for Rel-10

{ 1 < EMSR Additional PFCs 1 : < Additional PFCs struct > > } ** 0

{ 1 < EMSR Additional PFCs 2 : < Additional PFCs struct > > } ** 0

{ 1 < EMSR Additional PFCs 3 : < Additional PFCs struct > > } ** 0

{ null | 0 bit** = < no string > — Receiver backward compatible with earlier version

| 1 — Additions for Rel-12

< Primary TSC Set : bit (1) >

< padding bits > } } }

! < Non-distribution part error : bit (*) = < no string > > }

| 10 — Message escape for downlink multi carrier, RTTI, BTTI with FANR activated, EGPRS2

{ < RESEGMENT : bit (1) >

{ 1 < < DLMC UL Carrier Info: < DLMC UL Carrier Info struct > > } ** 0

< EGPRS Window Size : < EGPRS Window Size IE > >

< UPLINK_TFI_ASSIGNMENT : bit (5) >

< Packet Timing Advance : < Packet Timing Advance IE > >

{ 0 | 1 < Packet Extended Timing Advance : bit (2) > }

{ 0 | 1 < BEP_PERIOD2 : bit (4) > }

{ 0 | 1 < PFI : bit (7) > }

{ 0 | 1 < RLC_MODE : bit (1) > }

{ 0 | 1 < NPM Transfer Time : bit (5) > }

{ 0 | 1 — ‘1’ indicates that FANR is activated

{ 0 — SSN-based encoding is selected

| 1 — Time-based encoding is selected

< REPORTED TIMESLOTS : bit (8) >

< TSH : bit (2) > } }

< Uplink EGPRS Level: < EGPRS Level IE > >

{ 0 | 1 < Pulse Format: < Pulse Format IE > > }

< Indication of Upper Layer PDU Start for RLC UM: bit >

< Enhanced Flexible Timeslot Assignment : bit >

< EGPRS Channel Coding Command : < EGPRS Modulation and Coding Scheme IE >>

< padding bits > // — truncation at end of message allowed, bits ‘0’ assumed ! < Non-distribution part error : bit (*) = < no string > > }

! < Message escape : { 11 } bit (*) = <no string> > } } – Extended for future changes

! < Address information part error : bit (*) = < no string > > }

! < Distribution part error : bit (*) = < no string > > ;

<extension> ::= — Future extension can be done by modifying this structure

null ;

<Dynamic Allocation struct > ::=

< EXTENDED_DYNAMIC_ALLOCATION : bit (1) >

{ 0 | 1 < P0 : bit (4) >

< PR_MODE : bit (1) > }

< USF_GRANULARITY : bit (1) >

{ 0 | 1 < UPLINK_TFI_ASSIGNMENT : bit (5) > }

0 The value ‘1’ was allocated in an earlier version of the protocol and shall not be used.

{ 0 | 1 < TBF Starting Time : < Starting Frame Number Description IE > > }

{ 0 — Timeslot Allocation

{ 0 | 1 < USF_TN0 : bit (3) > }

{ 0 | 1 < USF_TN1 : bit (3) > }

{ 0 | 1 < USF_TN2 : bit (3) > }

{ 0 | 1 < USF_TN3 : bit (3) > }

{ 0 | 1 < USF_TN4 : bit (3) > }

{ 0 | 1 < USF_TN5 : bit (3) > }

{ 0 | 1 < USF_TN6 : bit (3) > }

{ 0 | 1 < USF_TN7 : bit (3) > }

| 1 — Timeslot Allocation with Power Control Parameters

< ALPHA : bit (4) >

{ 0 | 1 < USF_TN0 : bit (3) >

< GAMMA_TN0 : bit (5) > }

{ 0 | 1 < USF_TN1 : bit (3) >

< GAMMA_TN1 : bit (5) > }

{ 0 | 1 < USF_TN2 : bit (3) >

< GAMMA_TN2 : bit (5) > }

{ 0 | 1 < USF_TN3 : bit (3) >

< GAMMA_TN3 : bit (5) > }

{ 0 | 1 < USF_TN4 : bit (3) >

< GAMMA_TN4 : bit (5) > }

{ 0 | 1 < USF_TN5 : bit (3) >

< GAMMA_TN5 : bit (5) > }

{ 0 | 1 < USF_TN6 : bit (3) >

< GAMMA_TN6 : bit (5) > }

{ 0 | 1 < USF_TN7 : bit (3) >

< GAMMA_TN7 : bit (5) > } } ;

<Single Block Allocation struct > ::=

< TIMESLOT_NUMBER : bit (3) >

{ 0 | 1 < ALPHA : bit (4) >

< GAMMA_TN : bit (5) >}

{ 0 | 1 < P0 : bit (4) >

0 — The value ‘1’ was allocated in an earlier version of the protocol and shall not be used.

< PR_MODE : bit (1) > }

< TBF Starting Time : < Starting Frame Number Description IE > > ;

< Multi Block Allocation struct > ::=

< TIMESLOT_NUMBER : bit (3) >

{ 0 | 1 < ALPHA : bit (4) >

< GAMMA_TN : bit (5) >}

{ 0 | 1 < P0 : bit (4) >

0 — The value ‘1’ was allocated in an earlier version of the protocol and shall not be used.

< PR_MODE : bit (1) > }

< TBF Starting Time : < Starting Frame Number Description IE > >

< NUMBER OF RADIO BLOCKS ALLOCATED: bit (2) > ;

< Access Technologies Request struct > ::= — recursive structure allows any combination of Access technologies

<Access Technology Type : bit (4) >

{ 0 | 1 < Access Technologies Request struct > } ;

< Assignment Info struct > ::=

< Assignment Type : bit (2) >

< Carrier ID : bit (1) >;

< Dynamic Allocation 2 struct > ::=

< EXTENDED_DYNAMIC_ALLOCATION : bit (1) >

{ 0 | 1 < P0_C1 : bit (4) >

< PR_MODE_C1 : bit (1) >

{ 0 | 1 < P0_C2 : bit (4) >

< PR_MODE_C2 : bit (1) > } }

< USF_GRANULARITY : bit (1) >

{ 0 | 1 < UPLINK_TFI_ASSIGNMENT : bit (5) > }

{ 0 — Allocation without Power Control Parameters

< N_USF : bit (4) >

{ 0 | 1 < USF : bit (3) > } *( val(N_USF) + 1)

| 1 — Allocation with Power Control Parameters

< ALPHA_C1: bit (4) >

{ 0 | 1 < ALPHA_C2: bit (4) > }

{ 0 — BTTI mode

< N_TS : bit (4) >

{ 0 | 1

< USF : bit (3) >

< GAMMA: bit (5) >

} * ( val(N_TS) + 1)

| 1 — RTTI mode

< N_PAIRS : bit (3) >

{ 0 | 1

< USF : bit (3) >

< GAMMA : bit (5) >

} * (val(N_PAIRS) + 1)

{ 0 — RTTI USF

| 1 — BTTI USF

{ 0 | 1

< USF_2 : bit (3) >

{ 0 | 1 < GAMMA : bit (5) > }

} * (val(N_PAIRS) + 1)

}

}

} ;

< RLC Entity Struct > ::=

< UPLINK_TFI_ASSIGNMENT : bit (5) >

< RLC_MODE : bit (1) >

{ 0 | 1 < EGPRS Window Size : < EGPRS Window Size IE > > }

PFI : bit (7) >;

< Additional PFCs struct > ::=

< UPLINK TFI_ASSIGNMENT : bit (5) >

{ 0 | 1 < NPM Transfer Time : bit (5) > }

< PFI : bit (7) >;

< DLMC UL Carrier Info struct > ::=

{ 00 — Assigned carrier released

| 01 — Carrier remains unchanged (no information provided)

| 10 — Assigned carrier modified or new carrier assigned

{ 0 — BTTI mode

{ 0 | 1 < UPLINK_TIMESLOT_ALLOCATION : bit (8) > } — assigned PDCH

| 1 — RTTI mode

{ 0 | 1 < UPLINK_PDCH_PAIRS_DLMC : bit (8) > } — assigned PDCH-pairs

}

< Dynamic Allocation 3 : < Dynamic Allocation 3 IE > >

{ 0 — EMST is not used on this carrier

| 1 — EMST is used on this carrier

< Uplink RLC Entity 2 : < RLC Entity Struct >

{ 0 | 1 < Uplink RLC Entity 3 : < RLC Entity Struct > } }

{ 0 — EMSR is not used on this carrier

| 1 — EMSR is used on this carrier

{ 1 < EMSR Additional PFCs 1 : < Additional PFCs struct > > } ** 0

{ 1 < EMSR Additional PFCs 2 : < Additional PFCs struct > > } ** 0

{ 1 < EMSR Additional PFCs 3 : < Additional PFCs struct > > } ** 0

}

< Primary TSC Set : bit (1) >

| 11 bit (*) = < no string > — reserved

} ;

Table 11.2.29.2: Packet UPlink ASSIGNMENT information element details

PAGE_MODE (2 bit field)
This field is defined in sub-clause 12.20.

PERSISTENCE_LEVEL (4 bit field for each Radio Priority 1…4)
This field is defined in sub-clause 12.14, PRACH Control Parameters.

Global TFI
This information element identifies the uplink TFI, if available, or the downlink TFI, to which this message applies. This field is defined in sub-clause 12.10.

TLLI / G-RNTI
This information element is defined in sub-clause 12.16.

TQI (16 bit field)
This field is defined in sub-clause 12.17.

Packet Request Reference
This information element is defined in sub-clause 12.11.

CHANNEL_CODING_COMMAND (2 bit field)
The Channel Coding Indicator field indicates the channel coding scheme that the mobile station shall use when transmitting data on the uplink.

bit
2 1
0 0 CS-1
0 1 CS-2
1 0 CS-3
1 1 CS-4

CONTENTION_RESOLUTION_TLLI (32 bit field)
The CONTENTION_RESOLUTION_TLLI field is present only if the network has decoded one of the uplink blocks containing the TLLI or G-RNTI during the EGPRS one phase access. The mobile station shall perform the contention resolution function if this field is present. This field contains a TLLI or G-RNTI, which is defined in sub-clause 12.16. See sub-clause 7.1.2.3a.

COMPACT reduced MA
This information element is defined in sub-clause 12.29.

EGPRS Modulation and Coding Scheme

The EGPRS Modulation and Coding Scheme information element is defined in sub-clause 12.10d.

If this field is included in a Dual Carrier assignment, it shall specify the initial EGPRS Modulation and Coding Scheme to be used on both carriers.

RESEGMENT (1 bit field)

This field is defined in sub-clause 12.10e.

EGPRS Window Size

This information element is defined in sub-clause 12.5.2.

TLLI_BLOCK_CHANNEL_CODING (1 bit field)
This field indicates the channel coding command that the mobile station shall use for any RLC data block containing a TLLI field in the RLC data block header. This field is coded as shown:

0 the mobile station shall use CS-1 in GPRS TBF mode and MCS-1 in EGPRS TBF mode.

1 the mobile station shall use the value commanded in the CHANNEL_CODING_COMMAND or EGPRS_CHANNEL_CODING_COMMAND field.

BEP_PERIOD2 (4 bit field)
This field contains a constant which is used for filtering channel quality measurements in EGPRS. BEP_PERIOD2 when present, or if not, when received in a previous message of the same TBF session, shall be used instead of BEP_PERIOD. For details see 3GPP TS 45.008.

Range: 0 to 15

UPLINK_TFI_ASSIGNMENT (5 bit field)
This information element, if present, assigns the contained TFI to the mobile station to identify the uplink TBF described by this message. This field is coded the same as the TFI field defined in sub-clause 12.15. If EMST is used, each TFI identifies an RLC entity allocated on the uplink TBF. If EMSR is supported, each TFI identifies a Packet Flow Context supported by a specific RLC entity allocated on the uplink TBF.

Packet Timing Advance
This information element is defined in sub-clause 12.12.

Frequency Parameters
This information element, if present, assigns frequency parameters to the uplink TBF. If this information element is not present the mobile station shall use its previously assigned frequency parameters. This information element is defined in sub-clause 12.8.

Frequency Parameters C1, Frequency Parameters C2
These information elements are coded as defined in sub-clause 12.8. See sub-clause 11.2.7 for the usage of these information elements.

Dual Carrier Frequency Parameters
This information element, if present, assigns frequency parameters to the uplink TBF for both carriers in a dual carrier configuration. This information element is defined in sub-clause 12.8.2.

Dynamic Allocation struct
This information element contains parameters necessary to define the radio resources of a dynamic allocation or an extended dynamic allocation.

In case of a timeslot allocation without power control parameters, the values of the power control parameters for assigned timeslots shall be the default values as specified in 3GPP TS 45.008. However, in case some of the timeslots assigned by this message are already used by the mobile station, the mobile station shall continue to use the current power control parameters for these timeslots.

Dynamic Allocation 2 struct
This information element contains parameters necessary to define the radio resources of a dynamic allocation or an extended dynamic allocation in a dual carrier, RTTI, BTTI with FANR activated, or EGPRS2 configuration.

In case of a timeslot allocation without power control parameters, the values of the power control parameters for assigned timeslots shall be the default values as specified in 3GPP TS 45.008. However, in case some of the timeslots assigned by this message are already used by the mobile station, the mobile station shall continue to use the current power control parameters for these timeslots.

EXTENDED_DYNAMIC_ALLOCATION (1 bit field)
This information field indicates the medium access mode to be used during the TBF.
0 Dynamic Allocation
1 Extended Dynamic Allocation

TBF Starting Time
The TBF Starting Time field contains a starting time that indicates the frame number during which the assigned TBF may start.

In case of dynamic allocation, if no uplink TBF is in progress, the MS need not monitor the USF field until the TDMA frame number occurs. When the indicated TDMA frame number occurs, the mobile station shall immediately begin to monitor the USF field and use the new assigned uplink TBF parameters when its USF has occurred. If an uplink TBF is already in progress, the MS shall continue to use the parameters of the existing TBF until the TDMA frame number occurs. When the indicated TDMA frame number occurs, the mobile station shall immediately begin to monitor the USF field and use the new assigned uplink TBF parameters when its USF has occurred.

In case of single block allocation, the mobile station shall use the assigned timeslot during the RLC/MAC block whose first TDMA burst occurs in the indicated TDMA frame number.

This information element is encoded as the Starting Frame Number Description IE. See sub-clause 12.21.

USF_TN0 (3 bit field)
USF_TN1 (3 bit field)
USF_TN2 (3 bit field)
USF_TN3 (3 bit field)
USF_TN4 (3 bit field)
USF_TN5 (3 bit field)
USF_TN6 (3 bit field)
USF_TN7 (3 bit field)

These fields indicate the USF value assigned to the MS for assigned timeslots (range 0 to 7). These fields are encoded as a binary presentation of the USF value as defined in sub-clause 10.4.1.

USF_GRANULARITY (1 bit field)
This information field indicates the USF granularity to be applied by the mobile station when it is assigned a TBF using Dynamic Allocation or Extended Dynamic Allocation.

0 the mobile station shall transmit one RLC/MAC block
1 the mobile station shall transmit four consecutive RLC/MAC blocks

Single Block Allocation struct
This information element contains parameters necessary to define the radio resources of a Single Block allocation. For example for sending of a PACKET RESOURCE REQUEST message in a two phase access or a Measurement report.

TIMESLOT_NUMBER (3 bit field)
This field indicates the timeslot assigned for transfer of a single RLC/MAC block on the uplink. This field is coded as the binary representation of the timeslot number as defined in 3GPP TS 45.010.
Range 0 to 7

ALPHA (4 bit field)
For encoding and description see the Global Power Control Parameters IE.

ALPHA_C1, ALPHA_C2 (4 bit field)
If the Assignment Type field is included and indicates ‘Assignment on single carrier only’ or ‘Modification of existing assignment’, then ALPHA_C1 (if present) shall apply to the carrier specified in the Carrier ID field.

If the Assignment Type field is included and indicates ‘Dual Carrier assignment’, ALPHA_C1 and ALPHA_C2 indicate the value of the parameter alpha to be applied in power control on carrier 1 and carrier 2 respectively. For encoding and description see the Global Power Control Parameters IE. If ALPHA_C1 is present and ALPHA_C2 is absent, then ALPHA_C1 shall apply to carrier 2.

GAMMA, GAMMA_TN (5 bit field)
This field is the binary representation of the parameter GCH for MS output power control in units of 2 dB, see 3GPP TS 45.008. The field is coded according to the following table:

bit
5 4 3 2 1
0 0 0 0 0 GCH = 0 dB
0 0 0 0 1 GCH = 2 dB
: : : :
1 1 1 1 0 GCH = 60 dB
1 1 1 1 1 GCH = 62 dB

In the case of RTTI mode with BTTI USF, exactly one GAMMA field shall be included for each PDCH pair for which either one or two USF values are assigned.

P0, P0_C1, P0_C2 (4 bit field)
These fields are optional downlink power control parameters.

If the Assignment Type field is present and indicates ‘Dual Carrier assignment’, P0_C1 and P0_C2 apply to carrier 1 and carrier 2, respectively. The presence of these parameters indicates that downlink power control is used for the indicated carrier; otherwise, downlink power control is not used for the indicated carrier. If the P0_C1 IE is present but the P0_C2 IE is absent, then the P0_C1 IE shall apply also to carrier 2.

If the Assignment Type field is included and indicates ‘Assignment on single carrier only’ or ‘Modification of existing assignment’, then P0_C1 shall apply to the carrier specified in the Carrier ID field.

These fields are encoded as follows:

bit
4 3 2 1
0 0 0 0 P0 = 0 dB
0 0 0 1 P0 = 2 dB
0 0 1 0 P0 = 4 dB
:
1 1 1 1 P0 = 30 dB

PR_MODE, PR_MODE_C1, PR_MODE_C2 (1 bit field)
These fields indicate the PR Management mode, as defined in 3GPP TS 45.008.

If the Assignment Type field is included and indicates ‘Assignment on single carrier only’ or ‘Modification of existing assignment’, then PR_MODE_C1 shall apply to the carrier specified in the Carrier ID field. Otherwise, PR_MODE_C1 and PR_MODE_C2 shall apply to carrier 1 and carrier 2 respectively. If the Assignment Type field indicates ‘Dual Carrier assignment and the PR_MODE_C1 IE is present but the PR_MODE_C2 IE is absent, then the PR_MODE_C1 IE shall apply also to carrier 2. It is encoded as follows:
0 PR mode A: for one addressed MS
1 PR mode B: for all MS

Packet Extended Timing Advance (2 bit field)
This field is defined in sub-clause 12.12b.

Multi Block Allocation struct
This information element contains parameters necessary to define the radio resources of a Multi Block allocation.

NUMBER OF RADIO BLOCKS ALLOCATED (2 bit field)

Bits
1 0
0 0 1 radio block reserved for uplink transmission
0 1 2 radio blocks reserved for uplink transmission
1 0 reserved for future use
1 1 reserved for future use

ACCESS TECHNOLOGY TYPE

This field indicates the access technology that is requested from the mobile station. The field is coded according to the definition in 3GPP TS 24.008. The access technology types requested from the MS in the Access Technologies Request structure shall be classified by priority, the most important first. The MS shall reply using the same order.
Among the three GSM 900 access technology types GSM P, GSM E and GSM R only one shall be requested by the network.

ARAC RETRANSMISSION REQUEST (1 bit field)

0 indicates that retransmission of an ADDITIONAL MS RADIO ACCESS CAPABILITIES message is not requested
1 indicates that retransmission of an ADDITIONAL MS RADIO ACCESS CAPABILITIES message is requested (see sub-clause 7.1.2.2.1a)

G-RNTI extension (4 bit field)

This field contains the extra 4 bits of the G-RNTI not included in the TLLI / G-RNTI field which are necessary to provide a unique identifier for contention resolution in Iu-mode. This field may also be included when an assigned G-RNTI is used in the CONTENTION_RESOLUTION_TLLI field during the contention resolution procedure.

RB Id (5 bit field)

This field is included in Iu mode when a TBF is assigned in MAC-Shared state. It contains the radio bearer identifier for the radio bearer using the assigned TBF.

PFI (7 bit field)

This field contains the PFI parameter identifying the Packet Flow Context related to the TBF identified in the UPLINK_TFI_ASSIGMENT field. The PFI parameter is encoded as the contents of the PFI information element defined in 3GPP TS 44.018. If EMST is used, this field contains the PFI parameter identifying the Packet Flow Context related to the RLC entity. If EMSR is supported, this field contains the PFI parameter identifying a Packet Flow Context supported by a specific RLC entity.

RLC_MODE (1 bit field)
This field contains the RLC mode to be used for the assigned TBF.

0 RLC acknowledged mode

1 RLC unacknowledged mode. For the case of an EGPRS TBF an MS that supports RLC non-persistent mode shall respond to this indication of RLC mode as described in the EGPRS Window Size IE (see sub-clause 12.5.2).

NPM Transfer Time (5 bit field)

This field contains the NPM Transfer Time limitation for TBF or RLC entity assigned to operate in RLC non-persistent mode. If EMSR is supported this field contains the NPM Transfer Time limitation for a specific Packet Flow Context configured to use RLC non-persistent mode.

ASSIGNMENT TYPE (2 bit field)

This indicates the type of assignment. The coding of this field is as specified in sub-clause 11.2.7.

Carrier ID (1 bit field)
This identifies the carrier to which the description refers.

0 Carrier 1
1 Carrier 2

REPORTED TIMESLOTS (8 bit field)

The field indicates the timeslots for which feedback is provided by a time-based encoded PAN field and is encoded as the TIMESLOT_ALLOCATION IE defined in sub-clause 12.18.

PDCH Pairs Description

This information element is defined in sub-clause 12.5.5.

RTTI_USF_MODE (1 bit field)
This field identifies whether RTTI or BTTI USF Mode is enabled for this uplink RTTI TBF.

0 BTTI USF Mode is enabled
1 RTTI USF Mode is enabled

TSH (2 bit field)

This field indicates the time-shift between the most recent radio block period for which feedback information is provided and the radio block period when the bitmap is sent:
bit
2 1
0 0 4 TDMA frames (for a basic TTI configuration) or 2 TDMA frames (for a reduced TTI or MTTI configuration)
0 1 8 TDMA frames (for a basic TTI configuration) or 4 TDMA frames (for a reduced TTI or MTTI configuration)
1 0 12 TDMA frames (for a basic TTI configuration) or 6 TDMA frames (for a reduced TTI or MTTI configuration)
1 1 16 TDMA frames (for a basic TTI configuration) or 8 TDMA frames (for a reduced TTI or MTTI configuration)

Uplink EGPRS Level (2 bit field)

This field specifies the group of modulation and coding schemes applicable to the TBF. This information element is defined in sub-clause 12.10f.

Pulse Format (N bit field)

This information element, if assigned, specified on which radio frequency channel the mobile station shall transmit using the narrow-band pulse option. The information element is defined in sub-clause 12.8.3.

N_USF, N_TS (4 bit field)

N_PAIRS (3 bit field)

These fields indicate the number USF allocations signalled. The number of USFs is given as the binary value of the corresponding field plus one.

See Annex K for details of the coding of these fields.

USF, USF_2 (3 bit field)

These fields indicate the USF values assigned to the MS for the assigned timeslot or PDCH pair.

In the case of RTTI mode with BTTI USF, the USF value specified in the USF field (respectively USF_2 field) applies to the first two (respectively second two) TDMA frames of the following basic radio block period (see sub-clauses 8.1.1.1, 8.1.1.2.1).

These fields are encoded as a binary representation of the USF value as defined in sub-clause 10.4.1.

The order in which USF assignments are encoded and the meaning when the number of repetitions of the USF is lower than the maximum is described in Annex K.

Indication of Upper Layer PDU Start for RLC UM (1 bit field)

This field is defined in section 11.2.7.

Enhanced Flexible Timeslot Assignment (1 bit field)

This field indicates whether Enhanced Flexible Timeslot Assignment, EFTA, shall be used for the assigned uplink TBF. This field is coded as follows:

0 Enhanced Flexible Timeslot Assignment, EFTA shall not be used for the assigned uplink TBF.
1 Enhanced Flexible Timeslot Assignment, EFTA shall be used for the assigned uplink TBF.

EMST_NW_Capability (1 bit field)

This information element indicates the network’s support of EMST

0 The network does not support EMST

1 The network supports EMST

MTTI_UPLINK_ASSIGNMENT_C1 (1 bit field)

MTTI_UPLINK_ASSIGNMENT_C2 (1 bit field)

These fields indicate whether the assigned uplink TBF operates in MTTI configuration. If present, a PDCH is assigned on the respective carrier in addition to any assigned PDCH-pairs. If set to ‘1’ (respectively ‘0’), the assigned PDCH uses the timeslot immediately adjacent to and lower than (respectively higher than) the lower (respectively higher) timeslot used by the lowest numbered (respectively highest numbered) PDCH-pair assigned on that carrier. If no PDCH-pairs are assigned on one carrier, then the assigned PDCH for that carrier is on the same timeslot as the assigned PDCH on the other carrier, regardless of the value of the field.

EMSR Additional PFCs 1

EMSR Additional PFCs 2

EMSR Additional PFCs 3

These IEs are defined in section 11.2.7.

DLMC UL Carrier Info

This information element is used to describe the uplink carriers applicable to an uplink TBF assigned for a DLMC configuration. It provides information for one or more of the uplink carriers corresponding to the downlink carriers (see sub-clause 8.1.1.2.1 and 8.1.2.5) where the uplink carriers are referenced in ascending order starting with the uplink carrier corresponding to downlink carrier C1, followed by the uplink carrier corresponding to downlink carrier C2 and so on (see sub-clause 8.1.1.1.3 for the numbering of downlink carriers in a DLMC configuration). The assignment message allows for releasing an existing carrier, keeping an existing carrier unchanged, modifying an existing carrier or adding a new carrier.

UPLINK_TIMESLOT_ALLOCATION (8 bit field)
This field is defined in sub-clause 12.18.

UPLINK_PDCH_PAIR_DLMC

This field is defined in sub-clause 11.2.31

Dynamic Allocation 3

This information element provides information for an uplink carrier corresponding to a downlink carrier assigned for a DLMC configuration. It shall always include information for the lowest numbered PDCH/PDCH-pair assigned on the referenced uplink carrier. If information is excluded for any additional PDCH/PDCH-pair assigned for the referenced uplink carrier then the MS shall apply the information provided for the lowest numbered PDCH/PDCH-pair assigned for that carrier. This information element is defined in sub-clause 12.65.

Primary TSC Set (1 bit field)

If a mobile station supports the extended TSC sets (see 3GPP TS 45.002 [32]) then it shall use this field to identify the TSC set associated with the TSC value indicated by the Frequency Parameters IE, Dual Carrier Frequency Parameters IE or DLMC Frequency Parameters IE for use on the assigned uplink PS resources. This field is coded as follows:

0 TSC set 1

1 Indicates TSC set 2 for 8PSK, 16QAM and 32QAM modulation. For GMSK modulation it indicates TSC set 3 (which is identical to TSC set 3 used for the CS domain).

11.2.29.1 Special requirements in dual transfer mode for uplink TBF

Special requirements apply when an uplink TBF is assigned to a mobile station in dual transfer mode or about to enter dual transfer mode.

If the mobile station has an RR connection to the network on a half-rate TCH, the network may assign an uplink TBF using the other sub-channel of the same timeslot for a half-rate PDCH (see 3GPP TS 45.002). In this case, the uplink assignment message shall be encoded with a timeslot allocation including the timeslot number for the half-rate TCH and the half-rate PDCH, and only that timeslot number. The mobile station shall interpret this allocation as an allocation of a half-rate PDCH.

In dual transfer mode, the mobile station may be assigned an uplink TBF using exclusive allocation. The exclusive allocation shall be applied according to the conditions specified in sub-clause 8.1.0. When the exclusive allocation is applied, the mobile station shall ignore the USF values assigned in the uplink assignment message.