| 1 — Additions for REL-5

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

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

{ 0 | 1 < Uplink Control Timeslot : bit (3) > }

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

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

| 1 — Additions for REL-6

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

{ 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 >

{ 0

| 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) >

{ 0 | 1 — Secondary DL TSC Value assigned

< Secondary DL TSC Set : bit (1) >

< Secondary DL TSC Value : bit (3) > }

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

| 1 — Additions for Rel-14

{ 0 | 1 < Multilateration Information Request : bit (1) > } }

< padding bits > } } } } } } } }// — truncation at end of message allowed, bits ‘0’ assumed

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

| 1 — message escape for dual carrier, multi carrier, RTTI, BTTI with FANR activated, EGPRS2

{ 00 — downlink dual carrier, RTTI, BTTI with FANR activated, EGPRS2

{ < RLC_MODE : bit (1) >

< CONTROL_ACK : bit (1) >

< Assignment Info : < Assignment Info struct > >

{ 0 — BTTI mode

< TIMESLOT_ALLOCATION_C1: bit (8) >

{ 0 | 1 < TIMESLOT_ALLOCATION_C2: bit (8) > }

| 1 — RTTI mode

{ 0 — Single Carrier Assignment

{ 00 — Default PDCH pair configuration

| 01 — Unchanged

| 10 — Explicit PDCH pair configuration

< DOWNLINK_PDCH_PAIRS_C1 : bit (8) >

< UPLINK_PDCH_PAIRS_C1 : bit (8) >

! < PDCH pairs configuration error : { 1 1 } bit (*) = < no string > > — reserved

}

< RTTI_DOWNLINK_PDCH_PAIR_ASSIGNMENT_SC : bit (4) >

| 1 — Dual Carrier Assignment

{ 00 — Default PDCH pair configuration

| 01 — Unchanged

| 10 — Explicit PDCH pair configuration

< DOWNLINK_PDCH_PAIRS_C1 : bit (8) >

< DOWNLINK_PDCH_PAIRS_C2 : bit (8) >

< UPLINK_PDCH_PAIRS_C1 : bit (8) >

< UPLINK_PDCH_PAIRS_C2 : bit (8) >

! < PDCH pairs configuration error : { 1 1 } bit (*) = < no string > > — reserved

}

< RTTI_DOWNLINK_PDCH_PAIR_ASSIGNMENT_DC : bit (8) >

}

}

< Packet Timing Advance : < Packet Timing Advance 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 < P0_C1 : bit (4) >

< PR_MODE_C1 : bit (1) >

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

< PR_MODE_C2 : bit (1) > } }

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

{ 0 | 1 < Power Control Parameters C1 : < Power Control Parameters IE > > }

{ 0 | 1 < Power Control Parameters C2 : < Power Control Parameters IE > > }

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

< LINK_QUALITY_MEASUREMENT_MODE : bit (2) >

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

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

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

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

{ 0 | 1 — ‘1′ indicates Fast Ack/Nack Reporting is activated

< EVENT_BASED_FANR: bit (1) > }

<Downlink EGPRS Level: < EGPRS Level 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 >

{ 0

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

{ 0

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

}

{ 0 | 1 MTTI_DOWNLINK_ASSIGNMENT_C1 : bit (1) }

{ 0 | 1 MTTI_DOWNLINK_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-11

< EGPRS Packet Downlink Ack/Nack Type 3 Support : bit(1) >

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

| 1 — Additions for Rel-12

< Primary TSC Set : bit (1) >

{ 0 | 1 — Secondary DL TSC Value assigned

< Secondary DL TSC Set : bit (1) >

< Secondary DL TSC Value : bit (3) > }

< padding bits > } } } }// — truncation at end of message allowed, bits ‘0’ assumed

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

| 01 — downlink multi carrier, RTTI, BTTI with FANR activated, EGPRS2

{ < RLC_MODE : bit (1) >

< CONTROL_ACK : bit (1) >

{ 1 < UFPS : < UFPS struct > > } ** 0

DLMC Measurement Type : bit (1)

< LINK_QUALITY_MEASUREMENT_MODE : bit (2) >

{ 0 | 1 < Carrier for Interference Measurements : bit (4) > }

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

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

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

< PDAN Coding : bit (1) >

< Extended SNS : bit (1) >

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

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

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

{ 0 | 1 — ‘1′ indicates Fast Ack/Nack Reporting is activated

< EVENT_BASED_FANR: bit (1) > }

< Downlink EGPRS Level: < EGPRS Level IE > >

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

< EGPRS Packet Downlink Ack/Nack Type 3 Support : bit(1) >

< padding bits > // — truncation at end of message allowed, bits ‘0’ assumed

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

}

! < Message escape : { 10 | 11 } bit (*) = < no string > > }

}

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

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

< Assignment Info struct > ::=

< Assignment Type : bit (2) >

< Carrier ID : bit (1) >;

< RLC Entity Struct > ::=

< DOWNLINK_TFI_ASSIGNMENT : bit (5) >

< RLC_MODE : bit (1) >

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

< PFI : bit (7) >;

< Additional PFCs struct > ::=

< DOWNLINK_TFI_ASSIGNMENT : bit (5) >

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

< PFI : bit (7) >;

< UFPS struct > ::=

{ 00 — Existing UFPS released

| 01 — Existing UFPS remains unchanged (no information provided)

| 10 — Existing UFPS changed/new UFPS provided

{ 0 — Existing DLMC Frequency Parameters unchanged

| 1 < DLMC Frequency Parameters : < DLMC Frequency Parameters IE > > }

{ 1 < CARRIER_SPECIFIC_INFO : < Carrier Specific Info struct > > } ** 0

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

};

< Carrier Specific Info struct > ::=

{ 00 — Existing carrier released

| 01 — Existing carrier remains unchanged (no information provided)

| 10 — Existing carrier changed/new carrier provided

{ 0 — BTTI mode

{ 0 — same timeslots as the lowest numbered carrier

| 1 < TIMESLOT_ALLOCATION : bit (8) > }

| 1 — RTTI mode

{ 0 — same PDCH-pairs as the lowest numbered carrier

| 1 < DOWNLINK_PDCH_PAIRS_DLMC : bit (8) >

< RTTI_DOWNLINK_PDCH_PAIR_ASSIGNMENT_DLMC : bit (4) > }

}

{ 0 | 1 < MAIO : bit (6) > }

{ 0 — same P0 and PR_MODE as the lowest numbered carrier

| 1 < P0 : bit (4) >

< PR_MODE : bit (1) > }

{ 0 — same DOWNLINK_TFI_ASSIGNMENT as the lowest numbered carrier

| 1 < DOWNLINK_TFI_ASSIGNMENT : bit (5) >

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

{ 0 — same Power Control Parameters as the lowest numbered carrier

| 1 < Power Control Parameters : < Power Control Parameters IE > > }

{ 0 — EMST is not used on this carrier

| 1 — EMST is used on this carrier

< RLC Entity 2 : < RLC Entity Struct > >

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

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

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

{ 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 < DOWNLINK_eTFI_ASSIGNMENT : bit (3) > } } ** 0

{ 1 < EMSR Additional PFCs 2 : < Additional PFCs struct > >

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

{ 1 < EMSR Additional PFCs 3 : < Additional PFCs struct > >

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

}

< Primary TSC Set : bit (1) >

{ 0 | 1 — Secondary DL TSC Value assigned

< Secondary DL SC Set : bit (1) >

< Secondary DL TSC Value : bit (3) > }

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

};

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 contains the TFI of one of the mobile station’s downlink TBFs or uplink TBFs. This field is defined in sub-clause 12.10.

TLLI/ G-RNTI (32 bit field)
This field is defined in sub-clause 12.16.

MAC_MODE (2 bit field)
This information field was used in an earlier version of the protocol to indicate the medium access method to be used during an uplink TBF. For backward compatibility reasons, if there is an ongoing uplink TBF using the extended dynamic allocation, the network shall set the value of this field to ‘extended dynamic allocation’. Otherwise, the value shall be set to ‘dynamic allocation’. The mobile station shall ignore this field.

bit

2 1

0 0 Dynamic Allocation

0 1 Extended Dynamic Allocation

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

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

RLC_MODE (1 bit field)
This field indicates the RLC mode of the requested TBF. If EMST is used, this field indicates the RLC mode of the RLC entity..

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).

CONTROL_ACK (1 bit field)
In A/Gb mode, this field shall be set to ‘1’ if the network establishes a new downlink TBF for the mobile station whose timer T3192 is running. Otherwise this field shall be set to ‘0’.

In Iu mode, this field shall be set to ‘1’ if the network wishes to instruct the mobile station to release a given TBF for which timer T3192 is running. The TBF to be released is identified by the TFI given in the DOWNLINK_TFI_ASSIGNMENT field and has to be valid on the PACCH on which this message was sent. Otherwise this field shall be set to ‘0’.

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

TIMESLOT_ALLOCATION_C1, TIMESLOT_ALLOCATION_C2 (8 bit field)
These information fields indicate the timeslots assigned for use during the TBF. If the Assignment Type field is included and indicates ‘Assignment on single carrier only’ or ‘Modification of existing assignment’, then TIMESLOT_ALLOCATION_C1 shall apply to the carrier indicated by the Carrier ID field. Otherwise, TIMESLOT_ALLOCATION_C1 and TIMESLOT_ALLOCATION_C2 shall apply on carrier 1 and carrier 2 respectively of a dual carrier configuration. These fields are defined in sub-clause 12.18.

If TIMESLOT_ALLOCATION_C1 is present and TIMESLOT_ALLOCATION_C2 is not present and the Assignment Type field indicates ‘Dual Carrier assignment’, then the timeslots specified in TIMESLOT_ALLOCATION_C1 apply also to carrier 2.

For the case of a downlink carrier assigned for a DLMC configuration the assignment message shall provide the TIMESLOT_ALLOCATION IE for at least the first carrier in the corresponding UFPS. If this IE is absent for any remaining carriers, the TIMESLOT_ALLOCATION IE for the lowest numbered carrier (see sub-clause 8.1.1.1.3) shall apply.

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

P0, P0_C1, P0_C2 (4 bit field)
For description and encoding, see the Packet Uplink Assignment message. 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 indicated by the Carrier ID field. Otherwise, P0_C1and P0_C2 shall apply to carrier 1 and carrier 2 respectively. If the P0_C1 IE is present but the P0_C2 IE is absent and the Assignment Type field indicates ‘Dual Carrier assignment’, then the P0_C1 IE shall apply also to carrier 2.

For the case of a downlink carrier assigned for a DLMC configuration the assignment message shall provide the P0 IE for at least the first carrier in the corresponding UFPS. If this IE is absent for any remaining carriers, the P0 IE for the lowest numbered carrier (see sub-clause 8.1.1.1.3) shall apply.

PR_MODE, PR_MODE_C1, PR_MODE_C2 (1 bit field)
For description and encoding, see the Packet Uplink Assignment message. 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.

For the case of a downlink carrier assigned for a DLMC configuration the assignment message shall provide the PR_MODE IE for at least the first carrier in the corresponding UFPS. If this IE is absent for any remaining carriers, the PR_MODE IE for the lowest numbered carrier (see sub-clause 8.1.1.1.3) shall apply.

Power Control Parameters, Power Control Parameters C1, Power Control Parameters C2
These information elements are coded as defined in sub-clause 12.13.

If the Assignment Type field is included and indicates ‘Assignment on single carrier only’ or ‘Modification of existing assignment’, then the Power Control Parameters C1 IE shall apply to the carrier specified in the Carrier ID field. If, in this case, the Power Control Parameters C1 IE is absent, then the previous parameters for that carrier shall apply.

If the Assignment Type field is included and indicates ‘Dual Carrier assignment’ and the Power Control Parameters C1 IE is present but the Power Control Parameters C2 IE is absent, then the Power Control Parameters C1 IE shall apply also to carrier 2. Otherwise, if either Power Control Parameters C1 IE or Power Control Parameters C2 IE is absent, the previous parameters for the respective carrier(s) shall apply.

For the case of a downlink carrier assigned for a DLMC configuration the assignment message shall provide the Power Control Parameters IE for at least the first carrier in the corresponding UFPS. If this IE is absent for any remaining carriers, the Power Control Parameters IE for the lowest numbered carrier (see sub-clause 8.1.1.1.3) shall apply.

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.

If the Assignment Type field is included and indicates ‘Assignment on single carrier only’ or ‘Modification of existing assignment’, then Frequency Parameters 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’, Frequency Parameters C1 and Frequency Parameters C2 (if present) assign frequency parameters for carrier 1 and carrier 2, respectively.

Dual Carrier Frequency Parameters
This information element is defined in sub-clause 12.8.2.

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

If a DLMC configuration is established, the assignment message shall provide the DOWNLINK_TFI_ASSIGNMENT IE for at least the first carrier in the corresponding UFPS. If this IE is absent for any remaining carriers, the DOWNLINK_TFI_ASSIGNMENT IE for the first carrier in the first UFPS shall apply.

TBF Starting Time
The TBF Starting Time field contains a starting time that indicates the TDMA frame number during which the assigned TBF may start. If no downlink TBF is in progress, the mobile station need not monitor the TFI field of downlink RLC data blocks until the indicated TDMA frame number. After the indicated TDMA frame number, the mobile station shall operate as during a downlink TBF. If a downlink TBF is already in progress, the mobile station 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 use the new parameters assigned. This information element is defined in sub-clause 12.21.

EGPRS Window Size
This information element is defined in sub-clause 12.5.2.

LINK_QUALITY_MEASUREMENT_MODE (2 bit field)

This field determines the measurements to be included within the EGPRS Timeslot Link Quality Measurements IE or EGPRS Timeslot Link Quality Measurements Type 2 IE. In case the assignment results in a dual carrier configuration, the value of the LINK_QUALITY_MEASUREMENT_MODE field shall apply to both carriers. In case the assignment results in a DLMC configuration, the value of the LINK_QUALITY_MEASUREMENT_MODE field shall apply to all carriers.

bit

2 1

0 0 The mobile station shall not report either interference measurements ( values) or per slot (slot pair in RTTI configuration) mean BEP measurements.

0 1 The mobile station shall report available interference measurements ( values) for timeslots 0 through 7. The  value is defined in 3GPP TS 45.008. No per slot (slot pair in RTTI configuration) mean BEP measurements shall be reported.

For a mobile station in a DLMC configuration, available interference measurements shall be reported for timeslots 0 through 7 for the carrier indicated by the assignment message or the lowest numbered downlink carrier if carrier information for interference measurements is not provided by the assignment message (see sub-clause 12.66 for additional reporting rules).

1 0 The mobile station shall report the mean BEP on each assigned time slot (slot pair in RTTI configuration) as specified in 3GPP TS 45.008. No interference measurements ( values) shall be reported. For a mobile station in a DLMC configuration where measurement information is to be reported on a per carrier basis (see sub-clause 11.2.7), the mean BEP (as specified in 3GPP TS 45.008) shall only be reported for the assigned timeslots on the carrier on which it was polled (see sub-clause 12.66). A mobile station in a DLMC configuration where measurement information is to be reported on a per UFPS basis (see sub-clause 9.1.8.2.1) shall treat this code point as the ‘00’ code point.

1 1 The mobile station shall report the mean BEP on each assigned time slot (slot pair in RTTI configuration) as specified in 3GPP TS 45.008. In addition to mean BEP, the mobile station shall report interference measurements ( values) for no more than four time slots for a given carrier within a single reporting message instance. If the MS has interference measurements for more than four timeslots to report for a given carrier, the selection of timeslots for which interference measurements are included in each message instance is implementation specific, subject to the requirement that a measurement for each time slot on each carrier, unless not available (see 3GPP TS 45.008), is included in at least every other report.

For a mobile station in a DLMC configuration, available interference measurements shall be reported for timeslots 0 through 7 for the carrier indicated by the assignment message or the lowest numbered downlink carrier if carrier information for interference measurements is not provided by the assignment message (see sub-clause 12.66 for additional reporting rules). If measurement information is to be reported on a per carrier basis (see sub-clause 11.2.7), the mean BEP (as specified in 3GPP TS 45.008) shall only be reported for the assigned timeslots on the carrier on which it was polled (see sub-clause 12.66). A mobile station in a DLMC configuration where measurement information is to be reported on a per UFPS basis (see sub-clause 9.1.8.2.1) shall treat this code point as the ‘01’ code point.

In addition, for a mobile station assigned a Downlink Dual Carrier configuration, if not all the required interference measurements can be included within a reporting message instance after all the required per slot mean BEP values for both carriers have been included, the mobile station shall include as many interference measurements (if any) as can fit in this message instance. The selection of timeslots for which interference measurements are included in each message instance is implementation specific. See sub-clause 9.1.8.2.1 for how a mobile station in a DLMC configuration can report information for more than one UFPS/carrier.

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

COMPACT reduced MA

This information element is defined in sub-clause 12.29.

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

RB Id (5 bit field)

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

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.

Uplink Control Timeslot (3 bit field)

This field contains the timeslot number of the timeslot where the PACCH for the MS is located. It is encoded as the binary representation of the timeslot number as defined in 3GPP TS 45.002.

HFN_LSB (1 bit field)

This field contains the least significant bit of the downlink HFN of the radio bearer for which the TBF is assigned. It is used in Iu mode only.

PFI (7 bit field)

This field contains the PFI parameter identifying the Packet Flow Context related to the TBF identified in the DOWNLINK_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.

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:

bit

2 1

0 0 Assignment on single carrier only

0 1 Modification of existing assignment

1 0 Dual Carrier assignment

1 1 Reserved for future use

If the Assignment Type indicates an Assignment on a single carrier only the resources specified in this message are assigned for this TBF on the carrier identified by the Carrier ID field. If the assignment is sent to a mobile station that does not currently have a dual carrier configuration, the Carrier ID field shall indicate Carrier 1 and all resources specified in the message shall relate to Carrier 1.

If the Assignment Type indicates Modification of an existing assignment resources specified in this message replace any existing allocation for this TBF on the carrier indicated by the Carrier ID field. If this type of assignment is used to place a mobile station which currently has resources assigned on only one carrier in a dual carrier configuration the Carrier ID shall indicate Carrier 2.

If the Assignment Type indicates a Dual Carrier assignment the Carrier ID field shall be ignored by the mobile station.

The meaning of the different types of assignment is specified in sub-clause 8.1.1.1.3.

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

0 Carrier 1
1 Carrier 2

EVENT_BASED_FANR (1 bit field)

This field indicates whether the event-based FANR shall be used for the assigned TBF. This field shall be included if the assignment is for a RTTI or MTTI configuration.

0 The MS shall not use event-based FANR
1 The MS shall use event-based FANR

DOWNLINK_PDCH_PAIRS_C1

DOWNLINK_PDCH_PAIRS_C2

UPLINK_PDCH_PAIRS_C1

UPLINK_PDCH_PAIRS_C2

RTTI_DOWNLINK_PDCH_PAIR_ASSIGNMENT_SC

RTTI_DOWNLINK_PDCH_PAIR_ASSIGNMENT_DC

DOWNLINK_PDCH_PAIRS_DLMC

UPLINK_PDCH_PAIRS_DLMC

RTTI_DOWNLINK_PDCH_PAIR_ASSIGNMENT_DLMC

These fields are defined in sub-clause 11.2.31

Downlink EGPRS Level (2 bit field)

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

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

This field indicates whether "Indication of Upper Layer PDU Start for RLC UM" as described in sub-clause 10.4.14a is used for the assigned TBF. It is applicable only when the assigned TBF is operating in RLC unacknowledged mode.

0 "Indication of Upper Layer PDU Start for RLC UM" is not used for the assigned TBF.
1 "Indication of Upper Layer PDU Start for RLC UM" is used for the assigned TBF.

MTTI_DOWNLINK_ASSIGNMENT_C1 (1 bit field)

MTTI_DOWNLINK_ASSIGNMENT_C2 (1 bit field)

If either of these fields is present, it indicates that the assigned downlink TBF operates in an 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

If EMSR is supported one or more of these information elements may be included for allocating multiple PFCs to their corresponding RLC entity:

– if EMST is not used, EMSR Additional PFCs 1 corresponds to the single RLC entity of the TBF; EMSR Additional PFCs 2 and EMSR Additional PFCs 3, if present, shall be ignored.

– if EMST is used, EMSR Additional PFCs 1, EMSR Additional PFCs 2 and EMSR Additional PFCs 3 correspond to the first, the second and the third RLC entity, respectively, assigned to the TBF. EMSR Additional PFCs 2 corresponds to the RLC entity assigned using the RLC Entity 2 IE and EMSR Additional PFCs 3 correspond to the RLC entity assigned using the RLC Entity 3 IE if these RLC entities have been assigned; EMSR Additional PFCs 2¸ respectively EMSR Additional PFCs 3, if present, shall be ignored if the corresponding RLC entity has not been assigned.

EGPRS Packet Downlink Ack/Nack Type 3 Support (1 bit field)

This field indicates whether or not the network supports the EGPRS PACKET DOWNLINK ACK/NACK TYPE 3 message (see sub-clause 11.2.6f):

0 The network does not support the EGPRS PACKET DOWNLINK ACK/NACK TYPE 3 message.
1 The network supports the EGPRS PACKET DOWNLINK ACK/NACK TYPE 3 message.

If this field is not present, the value ‘0’ (EGPRS PACKET DOWNLINK ACK/NACK TYPE 3 message not supported) shall be assumed by the mobile station.

UFPS

This information element is used to identify the set of resources corresponding to each UFPS within the set of UFPS assigned for a DLMC configuration. Each UFPS in the set of UFPS is numbered according to the scheme described in sub-clause 8.1.1.1.3. The assignment message allows for releasing an existing UFPS, keeping an existing UFPS unchanged, modifying an existing UFPS or adding a new UFPS.

For the case where a UFPS is defined by a MA the first frequency indicated for the UFPS (i.e. by the CARRIER_SPECIFIC_INFO IE) is that corresponding to highest numbered element of the MA_BITMAP for which a ‘1’ is indicated, the second frequency indicated is that corresponding to 2^nd highest numbered element of the MA_BITMAP for which a ‘1’ is indicated, and so on where the last frequency indicated is that corresponding to lowest numbered element of the MA_BITMAP for which a ‘1’ is indicated. See sub-clause 12.10a for a description of the MA_BITMAP field.

DLMC Measurement Type

This field indicates the type of measurement reporting to be used by a mobile station in a DLMC configuration.

bit

0 BEP Link Quality is reported on a per UFPS basis using a representative value averaged over all carriers in the reported UFPS (see 3GPP TS 45.008 [15]).

1 BEP Link Quality is reported on a per carrier basis.

Carrier for Interference Measurements (4 bit field)

This field indicates the carrier to be used for making interference measurements. If the LINK_QUALITY_MEASUREMENT_MODE field indicates interference measurements are requested and this field is absent the MS shall make interference measurements using the lowest numbered carrier (see sub-clause 8.1.1.1.3).

bit

4 3 2 1

0 0 0 0 Use the 1^st carrier

0 0 0 1 Use the 2^nd carrier

0 0 1 0 Use the 3^rd carrier

…

1 1 1 0 Use the 15^th carrier

1 1 1 1 Use the 16^th carrier

CARRIER_SPECIFIC_INFO

This information element is used to describe the downlink carriers corresponding to a given UFPS applicable to the downlink TBF assigned for a DLMC configuration (see sub-clause 8.1.1.1.3 for the numbering of downlink carriers in a DLMC configuration).

DLMC Frequency Parameters
This information element provides frequency parameters for a UFPS and is described in sub-clause 12.8.4. For the case where a UFPS is defined by an MA this information element indicates the corresponding mobile allocation and TSC applicable to all carriers in that UFPS.

MAIO (6 bit field)
This field is the binary representation of the mobile allocation index offset (MAIO), see 3GPP TS 45.002. Range 0 to 63.

PTCCH_CARRIER (4 bit field)
This field is included if the continuous timing advance procedure is used and identifies the carrier that serves as the PTCCH carrier.

PDAN Coding (1 bit field)
This information field indicates the channel coding rate to be used when a mobile station in a DLMC configuration sends a Packet Downlink Ack/Nack message and is coded as follows:

0 CS-1 channel coding is used

1 CS-3 channel coding is used

DOWNLINK_eTFI_ASSIGNMENT (3 bit field)
This field, if present, assigns an extended TFI (eTFI) used by a mobile station in a DLMC configuration that along with the TFI uniquely identifies a downlink Temporary Block Flow (TBF) on a given carrier (see sub-clause 5.13). This information element is encoded as defined in sub-clause 12.67. When this field is present, the assignment message shall provide it for at least the first carrier in the corresponding UFPS. If this field is absent for any remaining carriers, the DOWNLINK_eTFI_ASSIGNMENT IE for the lowest numbered carrier (see sub-clause 8.1.1.1.3) shall apply

Extended SNS (1 bit field)

This field indicates whether or not the Extended Sequence Number Space of 8192 shall be used in a DLMC configuration. A mobile station shall ignore this field if the maximum number of downlink timeslots it supports in a DLMC configuration is 20 or less.

0 Extended SNS is disabled

1 Extended SNS is enabled

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 provided by the Frequency Parameters IE, Dual Carrier Frequency Parameters IE or DLMC Frequency Parameters IE for use on the assigned downlink PS resources.

Secondary DL 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 Secondary DL TSC Value field.

The Primary TSC Set and Secondary DL TSC Set fields are 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).

Secondary DL TSC Value (3 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 secondary TSC value to be used on the assigned downlink PS resources. It is coded as the binary representation of the Training Sequence code as defined in 3GPP TS 45.002. Range: 0 to 7.

Multilateration Information Request (1 bit field)

This field indicates whether or not a MS is to include “MS Transmission Offset” and “MS Sync Accuracy” parameters when sending an EGPRS Packet Downlink Ack/Nack Type 2 message (see sub-clause11.2.6e) or an EGPRS Packet Downlink Ack/Nack Type 3 message (see sub-clause 11.2.6f) during a downlink TBF. This field can be included when establishing a downlink TBF to deliver a downlink LLC PDU for which the corresponding DL-UNITDATA PDU indicates timing advance information is needed (see 3GPP TS 48.018). This field is coded as follows:

0 Do not include “MS Transmission Offset” and “MS Sync Accuracy” parameters

1 Include “MS Transmission Offset” and “MS Sync Accuracy” parameters