58b.2.1a Concurrent Downlink Multi Carrier TBF/ Reconfigure Frequency Parameters
3GPP51.010-1Mobile Station (MS) conformance specificationPart 1: Conformance specificationTS
58b.2.1a.1 Conformance requirement
Frequency parameters may be included in the packet assignment messages (i.e., PACKET DOWNLINK ASSIGNMENT, MULTIPLE TBF DOWNLINK ASSIGNMENT, PACKET UPLINK ASSIGNMENT, MULTIPLE TBF UPLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE, MULTIPLE TBF TIMESLOT RECONFIGURE or PACKET CS RELEASE INDICATION messages) or in the PS HANDOVER COMMAND message and define the training sequence codes(s) (TSC) and the radio frequency channels or set of radio frequency channels the mobile station is to use during the assigned TBF(s). The first packet assignment message, sent to the mobile station when it enters packet transfer mode or MAC-Shared state, shall include the frequency parameters. Subsequent packet assignment messages, sent to the mobile station during packet transfer mode or MAC-Shared state, may omit the frequency parameters. If a mobile station receives a subsequent packet assignment message, during packet transfer mode or MAC-Shared state, without the frequency parameters, the mobile station shall continue to use the previously assigned frequency parameters.
A packet assignment message, when sent to a mobile station in dual transfer mode or MAC-DTM state, shall not include the frequency parameters for the carrier supporting the dedicated resources in a Downlink Dual Carrier configuration. If the network intends to change the frequency allocation of the carrier supporting the dedicated resources for a mobile station in dual transfer mode or MAC-DTM state, the network may use the DTM assignment procedure defined in 3GPP TS 44.018.
If the network and mobile station both support Downlink Dual Carrier, the network may send a packet assignment message or a PS HANDOVER COMMAND message to a mobile station specifying packet resources for one or more TBFs on two carriers (referred to as carrier 1 and carrier 2) and thereby establish a Downlink Dual Carrier configuration. If the packet assignment message is sent to a mobile station in packet idle mode, this message shall include frequency parameters for both carriers. If this message is sent to a mobile station which is in packet transfer mode (and is not in a Downlink Dual Carrier configuration) the assignment message shall either:
– provide new frequency parameters for both carriers, or
– provide frequency parameters for only one carrier (carrier 2) in which case the frequency parameters for carrier 1 remain unchanged.
If the network and mobile station both support Downlink Multi Carrier, the network may send a packet assignment message (i.e. PACKET DOWNLINK ASSIGNMENT or PACKET TIMESLOT RECONFIGURE messages) or a PS HANDOVER COMMAND message to a mobile station specifying packet resources that establish a DLMC configuration. The PS HANDOVER COMMAND message shall always provide new frequency parameters for use in the new cell whereas the packet assignment message may:
– provide new frequency parameters for all newly assigned and existing carriers, or
– provide new frequency parameters for all newly assigned carriers, modify the frequency parameters for a subset of the existing carriers and leave the frequency parameters for the remaining existing carriers unchanged.
When a mobile station has resources assigned on only one carrier then, for the purposes of subsequent packet assignment messages, that carrier shall be considered carrier 1. A subsequent packet assignment message may assign resources on a second carrier, thereby establishing a Downlink Dual Carrier configuration; in this case, the packet assignment message shall provide frequency parameters for a second carrier (carrier 2) for use in a Downlink Dual Carrier configuration. Similarly, a subsequent packet assignment message may assign resources on one or more additional carriers, thereby establishing a DLMC configuration; in this case, the packet assignment message shall provide DLMC frequency parameters as required for use in a DLMC configuration.
A packet assignment message sent to a mobile station in packet transfer mode may specify frequency parameters for one or (in the case of a mobile station with a downlink dual carrier configuration) both carriers which are different from those currently in effect for that mobile station only in the following cases:
a) the assignment message is a PACKET TIMESLOT RECONFIGURE or MULTIPLE TBF TIMESLOT RECONFIGURE message.
b) the assignment message is a PACKET DOWNLINK ASSIGNMENT message (respectively PACKET UPLINK ASSIGNMENT message) being sent to a mobile station which has no ongoing uplink (respectively downlink) TBF(s).
c) the assignment message is a MULTIPLE TBF DOWNLINK ASSIGNMENT message (respectively MULTIPLE TBF UPLINK ASSIGNMENT message) being sent to a mobile station which is or, after this assignment, will be in a downlink dual carrier configuration and has no ongoing uplink (respectively downlink) TBF(s); in this case, the ongoing downlink (respectively uplink) TBFs are implicitly reassigned on the new frequency parameters with all other parameters for those TBFs unchanged.
d) the assignment message is a PACKET DOWNLINK ASSIGNMENT message (respectively PACKET UPLINK ASSIGNMENT message) sent to a mobile station with a downlink dual carrier configuration, where the frequency parameters for only one carrier are changed, and where no ongoing uplink (respectively downlink) TBF(s) had resources assigned on that carrier.
In cases c) and d) above, a format of the message which includes the Carrier ID field shall be used.
When assigning resources on one carrier to a mobile station which is currently in a Downlink Dual Carrier configuration using a format of the message which does not include the Carrier ID field, the network shall always include frequency parameters; if one or more TBFs which are ongoing are not explicitly addressed in the packet assignment message and will remain ongoing after the new assignment, the included frequency parameters shall be those in use for either carrier 1 or carrier 2.
A packet assignment message sent to a mobile station in packet transfer mode with a DLMC configuration may specify frequency parameters for one or more carriers which are different from those currently in effect for that mobile station only in the following cases:
a) the assignment message is a PACKET TIMESLOT RECONFIGURE message.
b) the assignment message is a PACKET DOWNLINK ASSIGNMENT message sent to a mobile station which has no ongoing uplink TBF.
c) the assignment message is a PACKET DOWNLINK ASSIGNMENT message sent to a mobile station which has an ongoing uplink TBF, subject to the restriction that all existing carriers on which USF is monitored remain assigned.
d) the assignment message is a PACKET UPLINK ASSIGNMENT message for the case where the ongoing downlink TBF is not modified.
The Frequency Parameters information element is defined in sub-clause 12.8 and the Dual Carrier Frequency Parameters information element is defined in sub-clause 12.8.2 and the DLMC Frequency Parameters information element is defined in sub-clause 12.8.4. The frequency parameters may use an ARFCN defining a non-hopping radio frequency channel, or use the indirect encoding, direct encoding 1 or direct encoding 2 defining a hopping radio frequency channel.
References
3GPP TS 44.060; subclause 5.5.1.7
58b.2.1a.2 Test purpose
To verify that the MS is able to change and operate concurrent downlink dual carrier TBF on different frequency resources.
58b.2.1a.3 Method of test
Initial Conditions
System Simulator:
1 cell, EGPRS supported, Downlink Multi Carrier supported.
Mobile Station:
Support for Downlink Multi Carrier indicated in MS Radio Access Capabilities IE.
The MS is in the state "idle, GMM-registered" with a P-TMSI allocated, SPLIT PG CYCLE negotiated, and PDP context 2 activated.
Specific PICS Statements
PIXIT Statements
–
Test Procedure
The EGPRS capable MS is made to transmit uplink RLC data blocks in EGPRS TBF RLC acknowledged mode. Then MS receives a PACKET DOWNLINK ASSIGNMENT message on its PACCH, instructing a Multi Carrier Downlink configuration, the existing UL carrier corresponds to downlink carrier 1. The SS sends RLC data blocks on Carrier 1 and Carrier 2 simultaneously. MS when polled acknowledges all data blocks send by SS and sends uplink data block when it receives USF on Carrier 1. This is to setup Concurrent Downlink Multi Carrier TBF.
Then the SS sends a PACKET TIMESLOT RECONFIGURE message on the PACCH, instructing a modification of existing assignment for Carrier 1. A new frequency parameter is specified for Carrier 1. The SS then sends RLC data blocks on Carrier 1 and Carrier 2 simultaneously. MS when polled acknowledges all data blocks send by the SS and sends uplink data block when it receives USF on Carrier 1.
Next the SS sends a PACKET TIMESLOT RECONFIGURE message on the PACCH, instructing a modification of existing assignment for Carrier 2. A new frequency parameter is specified for Carrier 2. The SS then sends RLC data blocks on Carrier 1 and Carrier 2 simultaneously. MS when polled acknowledges all data blocks send by the SS and sends uplink data block when it receives USF on Carrier 1.
Next the SS sends a PACKET TIMESLOT RECONFIGURE message on the PACCH, instructing a Multi Carrier Assignment for both Carrier 1 and Carrier 2 using legacy IEs. New frequency parameters are specified for Carrier 1 and Carrier 2. The SS then sends RLC data blocks on Carrier 1 and Carrier 2 simultaneously. MS when polled acknowledges all data blocks send by the SS and sends uplink data block when it receives USF on Carrier 1.
Then the SS sends a PACKET TIMESLOT RECONFIGURE message on the PACCH, instructing a Multi Carrier Assignment for both Carrier 1 and Carrier 2 using multi carrier frequency parameters. New frequency parameters are specified for Carrier 1 and Carrier 2. The SS then sends RLC data blocks on Carrier 1 and Carrier 2 simultaneously. MS when polled acknowledges all data blocks send by the SS and sends uplink data block when it receives USF on Carrier 1.
Finally the SS sends a PACKET TIMESLOT RECONFIGURE message on the PACCH, instructing a Multi Carrier Assignment for both Carrier 1 only using legacy IEs. New frequency parameters are specified for Carrier 1. The SS then sends RLC data blocks on Carrier 1 and Carrier 2 simultaneously. MS when polled acknowledges all data blocks send by the SS and sends uplink data block when it receives USF on Carrier 1.
Maximum Duration of Test
10 minutes.
Expected Sequence
|
Step |
Direction |
Message |
Comments |
|
1 |
{Uplink dynamic allocation two phase access} |
N = 1000 octets USF_GRANULARITY = 1 block EGPRS Channel Coding Command: MCS-1 |
|
|
2 |
SS -> MS |
PACKET DOWNLINK DUMMY CONTROL BLOCK |
Sent on the PACCH of the PDCH assigned, containing USF assigned to the MS. |
|
3 |
MS -> SS |
EGPRS UPLINK RLC DATA BLOCK |
Received on the assigned PDTCH SS verifies that the BSN starts from 0, and the correct MCS is used. |
|
4 |
SS -> MS |
PACKET UPLINK ACK/NACK |
SS acknowledges RLC data block received. |
|
5 |
SS -> MS |
PACKET DOWNLINK ASSIGNMENT |
Sent on PACCH of the PDTCH assigned in Step 1. Addressing the MS using the UL TFI assigned in Step 1. Two Carriers Assigned. See specific message contents |
|
6 |
SS |
Wait for at least 3 block periods |
|
|
7 |
SS -> MS |
EGPRS DOWNLINK RLC DATA BLOCK |
On carrier 1 with next in sequence BSN (Start with BSN 0). USF Assigned. MCS-1. |
|
8 |
SS -> MS |
EGPRS DOWNLINK RLC DATA BLOCK |
On carrier 2 with next in sequence BSN Send on same Radio Block as Data Block Send on Carrier 1. MCS-1.Valid RRBP field |
|
9 |
MS -> SS |
EGPRS UPLINK RLC DATA BLOCK |
Received on the assigned PDTCH on carrier1 SS verifies that the correct BSN is received and the correct MCS is used. |
|
10 |
MS -> SS |
EGPRS PACKET DOWNLINK ACK/NACK |
Received on Carrier 2 In the uplink block specified by the RRBP field .Concurrent TBF established. |
|
11 |
SS -> MS |
PACKET TIMESLOT RECONFIGURE |
Sent on PACCH of the PDTCH assigned in Step 1. New Frequency Parameters specified for carrier1. See specific message contents |
|
12 |
SS |
Wait for at least 3 block periods |
|
|
13 |
Repeat step 7 to 10 |
||
|
14 |
SS -> MS |
PACKET TIMESLOT RECONFIGURE |
Sent on PACCH of the PDTCH assigned in Step 1. New Frequency Parameters specified for carrier2. See specific message contents |
|
15 |
SS |
Wait for at least 3 block periods |
|
|
16 |
Repeat step 7 to 10 |
||
|
17 |
SS -> MS |
PACKET TIMESLOT RECONFIGURE |
Sent on PACCH of the PDTCH assigned in Step 1. New Frequency Parameters specified for carrier1 and carrier2 using legacy IEs. See specific message contents |
|
18 |
SS |
Wait for at least 3 block periods |
|
|
19 |
Repeat step 7 to 10 |
||
|
20 |
SS -> MS |
PACKET TIMESLOT RECONFIGURE |
Sent on PACCH of the PDTCH assigned in Step 1. New Frequency Parameters specified for carrier1 and carrier2 using dual carrier assignment IEs. See specific message contents |
|
21 |
SS |
Wait for at least 3 block periods |
|
|
22 |
Repeat step 7 to 10 |
||
|
23 |
SS -> MS |
PACKET TIMESLOT RECONFIGURE |
Sent on PACCH of the PDTCH assigned in Step 1. New Frequency Parameters specified for carrier1 only using legacy IEs. See specific message contents |
|
24 |
SS |
Wait for at least 3 block periods |
|
|
25 |
SS -> MS |
EGPRS DOWNLINK RLC DATA BLOCK |
On carrier 1 with next in sequence BSN (Start with BSN 0). USF Assigned. MCS-1. |
|
26 |
SS -> MS |
EGPRS DOWNLINK RLC DATA BLOCK |
On carrier 2 with next in sequence BSN Send on same Radio Block as Data Block Send on Carrier 1. MCS-1.Valid RRBP field. FBI=1 |
|
27 |
MS -> SS |
EGPRS UPLINK RLC DATA BLOCK |
Received on the assigned PDTCH on carrier1 SS verifies that the correct BSN is received and the correct MCS is used. |
|
28 |
MS -> SS |
EGPRS PACKET DOWNLINK ACK/NACK |
Received on Carrier 2 In the uplink block specified by the RRBP field FAI is set to 1. |
|
29 |
{ Completion of uplink RLC data block transfer} |
Specific Message Contents
PACKET DOWNLINK ASSIGNMENT message in step 5:
|
Information Element |
value/ remark |
|
MESSAGE_TYPE |
000010 |
|
PAGE_MODE |
00 Normal Paging |
|
Persistence Level |
0 (no Persistence Level Present) |
|
Referenced Address |
Referenced by UL TFI |
|
1 |
Message Escape Sequence for DLMC… |
|
01 |
|
|
RLC_MODE |
0 Acknowledged mode |
|
CONTROL_ACK |
0 |
|
1 < UFPS : < UFPS struct > |
1st UFPS struct |
|
| 10 |
Existing UFPS changed/new UFPS provided |
|
| 1 < DLMC Frequency Para |
< 1st DLMC Frequency Parameters IE > (Present), ARFCN=F1 (see note below) based on existing UL carrier 1 |
|
{ 1 < CARRIER_SPECIFIC_INFO |
< 1st Carrier Specific Info struct > |
|
| 10 |
Existing carrier changed/new carrier provided |
|
0 |
BTTI mode |
|
1 TIMESLOT_ALLOCATION |
arbitrarily chosen (default timeslot 4) |
|
0 |
MAIO |
|
1 < P0 |
0000 0dB |
|
1 PR_MODE |
0 PR mode A |
|
1 |
DOWNLINK_TFI_ASSIGNMENT assign |
|
00001 |
downlink tfi assigned value |
|
1 |
<Power Control Parameters>} |
|
1 (Power Control Parameters present for Carrier1) |
|
|
– ALPHA |
0.5 |
|
– GAMMA for allocated timeslots |
For DCS 1800 and PCS 1900: +6 dBm. For all other bands: +8 dBm (default timeslot 4) |
|
0 |
EMST is not used on this carrier |
|
0 |
EMSR is not used on this carrier |
|
1 < UFPS : < UFPS struct > |
2nd UFPS struct |
|
| 10 |
Existing UFPS changed/new UFPS provided |
|
| 1 < DLMC Frequency Para |
< 2nd DLMC Frequency Parameters IE > (Present), ARFCN=F2 (see note below) |
|
{ 1 < CARRIER_SPECIFIC_INFO |
< 2nd Carrier Specific Info struct > |
|
| 10 |
Existing carrier changed/new carrier provided |
|
0 |
BTTI mode |
|
0 |
same timeslots as the lowest numbered carrier |
|
0 |
MAIO |
|
0 |
same P0 and PR_MODE as the lowest numbered carrier |
|
0 |
same DOWNLINK_TFI_ASSIGNMENT as the lowest numbered carrier |
|
0 |
same Power Control Parameters as the lowest numbered carrier |
|
0 |
EMST is not used on this carrier |
|
0 |
EMSR is not used on this carrier |
|
0 |
End of CARRIER_SPECIFIC_INFO |
|
0 |
End of UFPS struct |
|
DLMC Measurement Type |
0 |
|
< LINK_QUALITY_MEASUREMENT_MODE |
00 |
|
0 |
Carrier for Interference Measurements |
|
Packet Timing Advance |
|
|
1 |
1 (timing advance value) |
|
100000} |
32 bit periods indicated |
|
0 |
0 (no timing advance index or timing advance timeslot number) |
|
0 |
< Packet Extended Timing Advance |
|
0 |
< PTCCH_CARRIER |
|
0 |
< PDAN Coding > |
|
0 |
< Extended SNS > |
|
0 |
< BEP_PERIOD2 |
|
0 |
< PFI |
|
0 |
< NPM Transfer Time |
|
0 |
Fast Ack/Nack Reporting |
|
00 |
< Downlink EGPRS Level |
|
0 |
< Indication of Upper Layer PDU Start for RLC UM |
|
0 |
< EGPRS Packet Downlink Ack/Nack Type 3 Support |
|
Spare padding |
Spare Padding |
PACKET TIMESLOT RECONFIGURE in Step 11
|
Information Element |
value/ remark |
|
|
MESSAGE_TYPE |
0 00111 |
|
|
PAGE_MODE |
00 Normal Paging |
|
|
GLOBAL_TFI |
UL_TFI assigned in Step 1 |
|
|
10 |
escape for Downlink Multi Carrier, BTTI using FANR, EGPRS2, RTTI |
|
|
DOWNLINK_RLC_MODE |
0 |
|
|
CONTROL_ACK |
0 |
|
|
1 < UFPS : < UFPS struct > |
1st UFPS struct |
|
|
| 10 |
Existing UFPS changed/new UFPS provided ARFCN=F3 (see note below) |
|
|
1 < UFPS : < UFPS struct > |
2st UFPS struct |
|
|
| 01 |
Existing UFPS remains unchanged (no information provided) |
|
|
DLMC Measurement Type |
0 |
|
|
< LINK_QUALITY_MEASUREMENT_MODE |
00 |
|
|
Carrier for Interference Measurements |
0 |
|
|
Global Packet Timing advance |
||
|
– {0|1 <TIMING_ADVANCE_VALUE>} |
1 (timing advance value) |
|
|
– TIMING_ADVANCE_VALUE |
30 bit periods |
|
|
Packet Extended Timing Advance |
0 |
|
|
PTCCH_CARRIER |
0 |
|
|
CONTROL_ACK |
0 |
|
|
PDAN Coding |
0 |
|
|
Extended SNS |
0 |
|
|
BEP_PERIOD2 |
0 |
|
|
PFI of downlink TBF |
0 |
|
|
Downlink NPM Transfer Time |
0 |
|
|
indicates Fast Ack/Nack Reporting is activated for downlink TBF |
0 |
|
|
Downlink EGPRS Level |
No change |
|
|
Indication of Upper Layer PDU Start for RLC UM |
0 |
|
|
EGPRS Packet Downlink Ack/Nack Type 3 Support |
0 |
|
|
EGPRS Channel Coding Command |
0 MCS1 |
|
|
RESEGMENT |
0 |
|
|
1 < DLMC UL Carrier struct > |
1st DLMC UL struct |
|
|
| 10 |
value’s for DL Carrier 1 chosen |
|
|
UPLINK EGPRS Window Size |
0 |
|
|
UPLINK_TFI_ASSIGNMENT |
||
|
PFI of uplink TBF |
0 |
|
|
UPLINK_RLC_MODE |
0 |
|
|
Uplink NPM Transfer Time |
0 |
|
|
indicates that FANR is activated |
0 |
|
|
Uplink EGPRS Level |
default |
|
|
Pulse Format |
0 |
|
|
Enhanced Flexible Timeslot Assignment |
0 |
|
|
Uplink Control Timeslot |
0 |
|
PACKET TIMESLOT RECONFIGURE in Step 14
Based on message at step 11 with below deviation.
|
Information Element |
value/ remark |
||
|
1 < UFPS : < UFPS struct > |
1st UFPS struct |
||
|
| 01 |
Existing UFPS remains unchanged (no information provided) |
||
|
1 < UFPS : < UFPS struct > |
2st UFPS struct |
||
|
| 10 |
Existing UFPS changed/new UFPS provided, ARFCN=F4 (see note below) |
||
|
< DLMC UL Carrier Info > |
DLMC UL Carrier Info struct |
||
|
01 |
Carrier remains unchanged (no information provided |
||
PACKET TIMESLOT RECONFIGURE in Step 17
Based on message at step 11 with below deviation.
|
Information Element |
value/ remark |
||
|
1 < UFPS : < UFPS struct > |
1st UFPS struct |
||
|
| 10 |
Existing UFPS changed/new UFPS provided, ARFCN=F5 (see note below) |
||
|
1 < UFPS : < UFPS struct > |
2st UFPS struct |
||
|
| 10 |
Existing UFPS changed/new UFPS provided, ARFCN=F6 (see note below) |
||
|
< DLMC UL Carrier Info > |
DLMC UL Carrier Info struct |
||
|
10 |
value’s for DL Carrier 1 chosen |
||
PACKET TIMESLOT RECONFIGURE in Step 20
Based on message at step 11 with below deviation.
|
Information Element |
value/ remark |
||
|
1 < UFPS : < UFPS struct > |
1st UFPS struct |
||
|
| 10 |
Existing UFPS changed/new UFPS provided, ARFCN=F7 (see note below) |
||
|
1 < UFPS : < UFPS struct > |
2st UFPS struct |
||
|
| 10 |
Existing UFPS changed/new UFPS provided, ARFCN=F8 (see note below) |
||
|
< DLMC UL Carrier Info > |
DLMC UL Carrier Info struct |
||
|
10 |
value’s for DL Carrier 1 chosen |
||
PACKET TIMESLOT RECONFIGURE in Step 23
Based on message at step 11 with below deviation.
|
Information Element |
value/ remark |
||
|
1 < UFPS : < UFPS struct > |
1st UFPS struct |
||
|
| 10 |
Existing UFPS changed/new UFPS provided, ARFCN=F9 (see note below) |
||
|
1 < UFPS : < UFPS struct > |
2st UFPS struct |
||
|
| 01 |
Existing UFPS remains unchanged (no information provided) |
||
|
< DLMC UL Carrier Info > |
DLMC UL Carrier Info struct |
||
|
10 |
value’s for DL Carrier 1 chosen |
||
NOTE: F1, F2, F3, F4, F5, F6, F7, F8 and F9 are nine different downlink ARFCNs in the same frequency band.