hash
stringlengths 32
32
| doc_id
stringlengths 5
12
| section
stringlengths 4
595
| content
stringlengths 0
6.67M
|
|---|---|---|---|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
58b.3.5 DLMC Assignment abnormal case single carrier fallback
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
58b.3.5.1 Conformance requirement
|
For a mobile in DLMC configuration, fallback to reception of a single carrier, irrespective of the number of assigned carriers, is performed with regular periodicity. The periodicity is based on BS_PA_MFRMS, which indicates the number of 52-multiframes between two fallback periods. A mobile belongs to a particular single carrier fallback group which identifies a specific basic radio block period.
A mobile station in DLMC configuration where the continuous timing advance procedure is used shall fall back to single carrier configuration for PTCCH reception during each PTCCH frame occurring on the corresponding radio frequency channel (see sub-clause 7.1.2.5). In addition, the mobile station shall fall back to single carrier configuration for radio block reception according to a regular pre-determined interval (see 3GPP TS 45.002 [13]) using the radio frequency channel of its assigned PTCCH or using the radio frequency channel of the lowest numbered carrier (see sub-clause 8.1.1.1.3) if it has not been assigned a PTCCH.
References
3GPP TS 45.002, subclause 6.5.1, and 6.5.8.
3GPP TS 45.060 subclause 5.13.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
58b.3.5.2 Test purpose
|
To verify the MS report lost blocks if transmitted from NW using a non-fallback carrier during the single carrier fallback.radio block period. Verify that a poll sent using a non-fallback carrier during the single carrier fallback radio block.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
58b.3.5.3 Method of test
|
Initial Conditions
System Simulator:
1 cell, EGPRS supported, Downlink Multi Carrier supported.
DLMC Bandwidth: 5MHz.
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 3 activated.
Specific PICS Statements
-
PIXIT Statements
-
Test Procedure
The EGPRS capable MS is made to transmit uplink RLC data blocks in EGPRS TBF RLC unacknowledged mode. The SS sends a PACKET TIMESLOT RECONFIGURE message, instructing a Downlink Multi Carrier configuration with 4 carriers and 16Ts.Send Downlink data on all 4 carriers at the single fallback period, PDAN shall only include Acked blocks for single carrier 1.
Poll for a PDAN on carrier 2 at the single fallback period, the PDAN shall arrive on lowest Carrier 1.
Maximum Duration of Test
5 minutes.
Expected Sequence
Step
Direction
Message
Comments
1
{Uplink dynamic allocation two phase access}
n = 440 octets, without starting time,
USF_GRANULARITY = 1 block,
RLC_DATA_BLOCKS_GRANTED = open-end
TLLI_BLOCK_CHANNEL_CODING: MCS1
EGPRS CHANNEL CODING COMMAND: MCS1
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 TIMESLOT RECONFIGURE
Sent on PACCH of the PDTCH assigned in Step 1.
Addressing the MS using the UL TFI assigned in Step 1.
4 Carriers Assigned.
5
SS
Wait for at least 3 block periods
6
SS -> MS
EGPRS DOWNLINK RLC DATA BLOCK
On carrier 1 with next in sequence BSN (Start with BSN 0). USF Assigned. MCS-1. Valid RRBP field Sent on the single fallback period according to 45.002 subclause 6.5.8
7
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. Sent on the single fallback period according to 45.002 subclause 6.5.8
8
SS -> MS
EGPRS DOWNLINK RLC DATA BLOCK
On carrier 3 with next in sequence BSN
Send on same Radio Block as Data Block Send on Carrier 1. MCS-1. Sent on the single fallback period according to 45.002 subclause 6.5.8
9
SS -> MS
EGPRS DOWNLINK RLC DATA BLOCK
On carrier 4 with next in sequence BSN
Send on same Radio Block as Data Block Send on Carrier 1. MCS-1. Sent on the single fallback period according to 45.002 subclause 6.5.8
10
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.
11
MS -> SS
EGPRS PACKET DOWNLINK ACK/NACK
Received on Carrier 1 In the uplink block specified by the RRBP field .Concurrent TBF established. Radioblock on carrier 1 shall be Acked, radioblock on carrier 2,3,4 shall be Nacked.
12
SS -> MS
EGPRS DOWNLINK RLC DATA BLOCK
On carrier 1 with next in sequence BSN. USF Assigned. MCS-1.
13
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 Sent, polling to be scheduled on the single fallback period according to 45.002 subclause 6.5.8
14
SS -> MS
EGPRS DOWNLINK RLC DATA BLOCK
On carrier 3 with next in sequence BSN
Send on same Radio Block as Data Block Send on Carrier 1. MCS-1.
15
SS -> MS
EGPRS DOWNLINK RLC DATA BLOCK
On carrier 4 with next in sequence BSN
Send on same Radio Block as Data Block Send on Carrier 1. MCS-1.
16
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.
17
MS -> SS
EGPRS PACKET DOWNLINK ACK/NACK
Received on Carrier 1 In the uplink block specified by the RRBP field FAI is set to 1, instead of carrier 2 during single fallback period.
18
{Completion of uplink RLC data block transfer}
Specific Message Contents
PACKET TIMESLOT RECONFIGURE message in step 4:
Information Element
value/ remark
PAGE_MODE
00 Normal Paging
{ 0 < GLOBAL_TFI : < Global TFI IE > >
uplink TFI, same value as assigned in step 1
| 10 -- escape for Downlink Multi Carrier, BTTI using FANR, EGPRS2, RTTI
10 Message Escape Sequence for DLMC
DOWNLINK_RLC_MODE
0 Acknowledged mode
CONTROL_ACK
Does not establish new downlink TBF while T3192 running
1 < UFPS : < UFPS struct >
1st UFPS struct
| 10
Existing UFPS changed/new UFPS provided
| 1 < DLMC Frequency Para
< 1st DLMC Frequency Parameters IE > Present
{ 1 < CARRIER_SPECIFIC_INFO
< 1st Carrier Specific Info struct >
| 10
Existing carrier changed/new carrier provided
0
BTTI mode
1 TIMESLOT_ALLOCATION
assign 4 timeslots 0-6
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 >
2,3,4nd UFPS struct
| 10
Existing UFPS changed/new UFPS provided
| 1 < DLMC Frequency Para
< 2,3,4nd DLMC Frequency Parameters IE > Present
{ 1 < CARRIER_SPECIFIC_INFO
< 2,3,4nd Carrier Specific Info struct >
| 10
Existing carrier changed/new carrier provided
0
BTTI mode
0-5
Assign timeslots 0-5 as supported by multislotclass but higher than DLMC - Maximum Number of Downlink Timeslots
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
1
1 (present timing advance index or timing advance timeslot number)
0010
2 timing advance index
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
MCS-1
< EGPRS Channel Coding Command
0
< RESEGMENT
0
{ 1 < < DLMC UL Carrier Info : < DLMC UL Carrier Info struct > > }
192
{ 0 | 1 < UPLINK EGPRS Window Size : < EGPRS Window Size IE > > }
same value as assigned in step 1
< UPLINK_TFI_ASSIGNMENT
0
{ 0 | 1 < PFI of uplink TBF
0
{ 0 | 1 < UPLINK_RLC_MODE
0
{ 0 | 1 < Uplink NPM Transfer Time
0
{ 0 | 1 -- '1' indicates that FANR is activated
EGPRS
< Uplink EGPRS Level
0
{ 0 | 1 < Pulse Format: < Pulse Format IE > >
0
< Enhanced Flexible Timeslot Assignment
0
{ 0 | 1 < Uplink Control Timeslot :
Spare padding
Spare Padding
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
58c EGPRS2
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
58c.1 Concurrent EGPRS2 TBF
|
58c.1.1a Concurrent EGPRS2A TBF using RTTI Latency reduction
58c.1.1a.1 Conformance Requirement
If a mobile station is assigned concurrent TBFs, these shall be in the same TBF mode.
A TBF in EGPRS mode operates using one of four groups of modulation and coding schemes:
- EGPRS-GMSK only (applicable to uplink TBFs only): this comprises MCS-1 to MCS-4
- EGPRS: this comprises MCS-1 to MCS-9
- EGPRS2-A: for uplink TBFs, this comprises MCS-1 to MCS-6 and UAS-7 to UAS-11; for downlink TBFs, this comprises MCS-1 to MCS-4, MCS-6 (only for retransmissions of blocks originally transmitted using EGPRS), MCS-7, MCS-8 and DAS-5 to DAS-12
- EGPRS2-B: for uplink TBFs, this comprises MCS-1 to MCS-4 and UBS-5 to UBS-12; for downlink TBFs, this comprises MCS-1 to MCS-4, MCS-6 to MCS-9, DAS-5, DAS-6, DAS-8, DAS-9, DAS-11 and DBS-5 to DBS-12.
The group of modulation and coding schemes to be used on a PDTCH associated with a TBF is indicated in the assignment message.
The use of the EGPRS2-A group for uplink or downlink is only supported by MSs which are capable of EGPRS2-A or EGPRS2-B in that direction.
If a mobile station indicates support of Reduced Latency (see 3GPP TS 24.008), it may be assigned TBFs with FANR activated (see sub-clause 9.1.14), either in BTTI configuration or in RTTI configuration. The network shall ensure that, if a mobile station is assigned a TBF with FANR activated, FANR shall be activated for all concurrent TBFs assigned to that mobile station.
References
3GPP TS 44.060, subclauses 5.2.1
GPRS, EGPRS and EGPRS2 capable mobile stations can be multiplexed dynamically on the same PDCH.
- For a mobile station supporting EGPRS2-A in the downlink, the network may use either GMSK, 8-PSK, 16-QAM or 32-QAM modulation with normal symbol rate, i.e. CS-1 to CS-4, MCS-0, MCS-1 to MCS-9 or DAS-5 to DAS-12 in those blocks.
References
3GPP TS 44.060, subclauses 5.2.4a
58c.1.1a.2 Test Purposes
To verify that the MS
- can operate concurrent uplink and downlink EGPRS2-A TBFs
- can operate with EGPRS2A TBF using RTTI
58c.1.1a.3 Method of Test
Initial Conditions
System Simulator:
1 cell with EGPRS support, default setting,
Mobile Station:
The MS is EGPRS updated with a P-TMSI allocated, SPLIT_PG_CYCLE negotiated and the test PDP Context 2 activated.
Specific PICS Statements
PIXIT Statements
-
Test Procedure
An EGPRS2A MS receives a PACKET DOWNLINK ASSIGNMENT message on its PACCH allocating resources for carrier 1. SS transmits downlink RLC data blocks. MS responds by sending a PACKET DOWNLINK ACK/NACK. MS then triggered to perform uplink data transfer in EGPRS2A to establish a concurrent uplink TBF. MS sends uplink data blocks and SS acknowledges. SS then send a PACKET TIMSLOT RECONFIGURE message to MS and to change the TTI configuration to RTTI in RTTI USF mode. A new EGPRS2A channel coding scheme is chosen for downlink. MS sends and receives data in new RTTI configuration. The uplink data transfer is completed.
Maximum Duration of Test
5 minutes
Expected Sequence
Step
Direction
Message
Comments
1
SS -> MS
PACKET DOWNLINK ASSIGNMENT
Sent on PACCH triggers the MS to assigned PDTCH.
2
SS -> MS
EGPRS DOWNLINK RLC DATA BLOCK
Sent on assigned PDCH with DAS-5 assigned to the MS.
A valid RRBP is indicated.
3
MS -> SS
EGPRS PACKET DOWNLINK ACK/NACK
In the uplink block specified by the RRBP field, MS acknowledges the previously received RLC data blocks.
4
{Uplink dynamic allocation two phase access}
n = 2000 octets,
USF_GRANULARITY = 1 block
EGPRS2 Channel Coding Command: UAS-11
5
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
Sent on the PACCH of the PDCH assigned, containing USF assigned to the MS.
6
MS -> SS
EGPRS UPLINK RLC DATA BLOCK
Received on the assigned PDTCH
7
SS -> MS
PACKET UPLINK ACK/NACK
SS acknowledges receiving all RLC data blocks.
8
SS -> MS
PACKET TIMESLOT RECONFIGURE
Sent on downlink PACCH.
RTTI Configuration (Changing TTI configuration from BTTI to RTTI)
Assigns a single uplink PDTCH pair. The corresponding downlink PDTCH pair uses the same timeslots as the assigned uplink pair.
USF Mode = RTTI USF Mode.
USF Granularity = 1 block
EGPRS2 uplink channel coding command arbitrarily chosen between UAS 7 to UAS-11.
Assigns a single downlink PDTCH pair.
EGPRS2 downlink channel coding chosen to be DAS-12.
9
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
Sent on downlink PACCH of the corresponding downlink PDCH pair of the uplink Ink PDCH assigned at Step 8
USF assigned to the MS.
10
MS -> SS
EGPRS UPLINK DATA BLOCK
Received on uplink PDTCH pair assigned in Step 8
UAS as specified in Step 8
11
SS -> MS
EGPRS DOWNLINK DATA BLOCK
Sent on downlink PDTCH pair assigned in Step 8.
Contains the PAN field which acknowledges the radio block received in Step 10.
CES/P = 011
12
MS -> SS
EGPRS UPLINK DATA BLOCK
Received on uplink PDTCH pair assigned in Step 8
13
MS-> SS
EGPRS PACKET DOWNLINK ACK/NACK
Received on the uplink PDCH pair corresponding to the downlink PDTCH pair assigned at Step 8.
14
SS-> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
Sent on corresponding downlink PDCH pair of the uplink PDCH pair assigned at Step 8.
USF assigned to the MS
15
MS-> SS
EGPRS UPLINK DATA BLOCK
Received on the uplink PDTCH pair assigned in Step 8.
16
{Completion of uplink RLC data block transfer}
Specific Message Contents
None.
58c.2.1a Acknowledged Mode/ Uplink TBF/ Countdown Value, in EGPRS2A
58c.2.1a.1 Conformance requirements
1. The mobile station shall send the Countdown Value (CV) in each uplink RLC data block to indicate to the network the absolute BSN (BSN') of the last RLC data block that will be sent in the uplink TBF.
2. When a radio block for EGPRS2-A data transfer consists of two RLC data blocks, the CV value of the RLC/MAC header refers to the second RLC data block.
References
3GPP TS 44.060, subclause 9.3.1.
58.2.1a.2 Test purpose
1. To verify that when a radio block for EGPRS2-A data transfer consists of two RLC data blocks, the CV value is calculated based on BSN of the second RLC data block.
58.2.1a.3 Method of test
Initial Conditions
System Simulator:
1 cell with EGPRS2-A support, default setting, PBCCH not present, BS_CV_MAX = 15.
Mobile Station:
The MS is EGPRS2-A updated with a P-TMSI allocated, SPLIT PG CYCLE negotiated and the test PDP context2 activated.
Specific PICS Statements
Support of QAM in uplink (TSPC_Type_EGPRS_16QAM_uplink)
PIXIT Statements
-
Test Procedure
The MS is made to transmit uplink RLC data blocks in an acknowledged mode uplink EGPRS2-A TBF to transmit N octets to calculate TBC value. Uplink RLC data block transfer is completed.
The MS is made to transmit uplink RLC data blocks in an acknowledged mode uplink EGPRS2-A TBF to transmit TBC uplink RLC data blocks. EGPRS2-A Channel Coding Scheme is UAS-7. N is less than Window Size.
The SS assigns resources for the mobile station to transmit data blocks. Each time one radio block is assigned.
The SS observes the CV value in the uplink blocks. BSN' = Absolute BSN of the second RLC data block is calculated upon each radio block is received.
The SS verifies that when x=round((TBC-BSN'-1)/NTS*2) is greater than BS_CV_MAX, CV equals to 15, otherwise, CV=x.
UAS-8, UAS9, UAS10 and UAS-11 shall be applied.
Maximum Duration of Test
50 minutes.
Expected Sequence
Step
Direction
Message
Comments
1
{Uplink dynamic allocation two phase access}
N = 56*60 octets
K=2
USF_GRANULARITY = 1 block
EGPRS2-A Channel Coding Scheme: UAS-7
(Suppose timeslot capability is 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
EGPRS2-A UPLINK RLC DATA BLOCK
Received on the assigned PDTCH
4
SS
-
Repeat steps 2 and 3 until CV=14
When CV=14, Calculate BSN' = BSN of the second RLC block, Calculate TBC= CV * NTS*K+BSN’
5
{Completion of uplink RLC data block transfer}
6
{Uplink dynamic allocation two phase access}
N = 56*60 octets
K=2
USF_GRANULARITY = 1 block
EGPRS2-A Channel Coding Scheme: UAS-7
(Suppose timeslot capability is 1)
7
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
Sent on the PACCH of the PDCH assigned, containing USF assigned to the MS.
8
MS -> SS
EGPRS2-A UPLINK RLC DATA BLOCK
Received on the assigned PDTCH
9
SS
-
Repeat steps 7 and 8 for TBC/2 times.
Calculate BSN' = BSN of the second RLC bock.
Calculate x=round( (TBC-BSN'-1)/NTS*K ).
Verify that when x is greater than BS_CV_MAX: CV = 15. Otherwise: CV=x
10
{Completion of uplink RLC data block transfer}
11
Repeat the procedure from step 1 to 10 for:
UAS-8, N=64*60 octets, K=2
UAS-9, N=74*60 octets, K=2
UAS-10, N=56*60 octets, K=3
UAS-11, N=64*60 octets, K=3
58c.2.2a Acknowledged Mode/ Uplink TBF/ Retransmission/ Split RLC Data Block, in EGPRS2-A
58c.2.2a.1 Conformance requirements
1. In RLC acknowledged mode, each RLC endpoint transmitter shall have an associated acknowledge state array (V(B)).
2. The transmitter shall transmit the oldest RLC data block whose corresponding element in V(B) indexed relative to V(A) has the value NACKED. As each RLC data block is transmitted the corresponding element in V(B) is set to the value PENDING_ACK.
3. In EGPRS2-A uplink, depending on the modulation and coding one to three RLC data blocks are contained in one RLC/MAC block as follows:
- One RLC data block per RLC/MAC block: MCS-1, MCS-2, MCS-3, MCS-4, MCS-5 and MCS-6.
- Two RLC data blocks per RLC/MAC block: UAS-7, UAS-8 and UAS-9.
- Three RLC data blocks per RLC/MAC block: UAS-10 and UAS-11.
4. A re-segment bit is included within each PACKET UPLINK ACK/NACK, PACKET UPLINK ASSIGNMENT and PACKET TIMESLOT RECONFIGURE message. For initial transmissions of new RLC blocks the channel coding commanded is applied. The re-segment bit is used to set the ARQ mode to type I or type II (incremental redundancy) for uplink TBFs.
5. For retransmissions, setting the re-segment bit to 1 (type I ARQ) requires the mobile station to use an MCS within the same family as the initial transmission and the payload may be split.
6. If the RLC data block to be transmitted is split over two radio blocks, both radio blocks shall be transmitted
7. RLC data blocks initially transmitted with MCS4, MCS-5, MCS-6, UAS-7, UAS-8, UAS-9, UAS-10 or UAS-11, can optionally be retransmitted with MCS-1, MCS-2 and MCS-3 respectively, using two radio blocks. In this case, the split block field in the header shall be set to indicate that the RLC data block is split, and the order of the two parts.
References
3GPP TS 44.060, subclauses 8.1.1, 9.1.2, 9.1.3, 9.1.8, 9.1.3.2, 9.3.2.1, 10.0a.2, 10.3a.4, 10.4.1, 10.4.8b and 12.10e.
3GPP TS 44.004.
3GPP TS 45.003.
58c.2.2a.2 Test purpose
1. To verify that if the RLC data block to be transmitted is split over two radio blocks, both radio blocks shall be transmitted.
2. To verify the correct setting of the Split Block field in the block header.
3. To verify that the order of the retransmitted two parts of the data block is correct.
58c.2.2a.3 Method of test
Initial Conditions
System Simulator:
1 cell with EGPRS2-A support, default setting, PBCCH not present.
Mobile Station:
The MS is EGPRS2-A updated with a P-TMSI allocated, SPLIT PG CYCLE negotiated and the test PDP context2 activated.
Specific PICS Statements
-
PIXIT Statements
-
Test Procedure
The EGPRS2-A capable MS is made to transmit uplink RLC data blocks in EGPRS2-A TBF RLC acknowledged mode. The EGPRS2-A Channel Coding Command IE indicates UAS-7 in the Packet Uplink Assignment message.
After BS_CV_MAX block periods the SS sends a Packet Uplink Ack/Nack message to negatively acknowledge some RLC data blocks. In the message EGPRS2-A Channel Coding Command IE is set to MCS-1 and Re-segment IE should be set to '1'B.
The MS shall retransmit the NACKED RLC data blocks using MCS-1 in spitted radio blocks. Observe the uplink RLC data block header. Both of split blocks shall be received, the first one shall contain a SPB field equals to '10'B while the second shall be '11'B.
Maximum Duration of Test
8 minutes
Expected Sequence
Step
Direction
Message
Comments
1
{Uplink dynamic allocation two phase access}
N = 1500 octets
USF_GRANULARITY = 1 block
EGPRS2-A Channel Coding Command: UAS-7
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
EGPRS2-A UPLINK RLC DATA BLOCK
Received on the assigned PDTCH
SS verifies that the BSN starts from 0, and verifies the correct MCS is used.
4
-
Repeat steps 2 and 3 until the RLC data Block with BSN=8 is received.
5
-
Wait for BS_CV_MAX block periods.
6
SS -> MS
PACKET UPLINK ACK/NACK
SS acknowledges RLC data blocks from BSN 0 to 7 and negatively acknowledges last RLC data block (BSN = 8).
USF not assigned to the MS
EGPRS2-A Channel Coding Command is set to MCS-1.
Resegment IE is set to '1'B.
7
-
Wait for 1 block period with no USF
8
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
Sent on the PACCH of the PDCH assigned, containing USF assigned to the MS.
A9 (optional step)
MS -> SS
EGPRS2-A UPLINK RLC DATA BLOCK
MS may transmit new data block if it has already been scheduled while Packet Uplink Ack/Nack is being processed.
B9(optional step)
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
USF assigned to the MS,
9
MS -> SS
EGPRS2-A UPLINK RLC DATA BLOCK
Received on the assigned PDTCH.
BSN = 8, SPB = '10'B.
SS verifies that the NACKED RLC data blocks are received and that the correct MCS is used.
10
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
Sent on the PACCH of the PDCH assigned, containing USF assigned to the MS.
11
MS -> SS
EGPRS2-A UPLINK RLC DATA BLOCK
Received on the assigned PDTCH.
BSN = 8, SPB = '11'B.
SS verifies that the NACKED RLC data blocks are received and that the correct MCS is used.
12
{Completion of uplink RLC data block transfer}
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
58c.2 Uplink EGPRS2 TBF
|
58c.2.1 to 58c.2.4 Void
58c.2.4a Acknowledged Mode/ Uplink TBF/ Verification of new coding schemes for EGPRS2A
58c.2.4a.1 Conformance requirements
A TBF in EGPRS mode operates using one of four groups of modulation and coding schemes:
- EGPRS-GMSK only (applicable to uplink TBFs only): this comprises MCS-1 to MCS-4
- EGPRS: this comprises MCS-1 to MCS-9
- EGPRS2-A: for uplink TBFs, this comprises MCS-1 to MCS-6 and UAS-7 to UAS-11; for downlink TBFs, this comprises MCS-1 to MCS-4, MCS-6 (only for retransmissions of blocks originally transmitted using EGPRS), MCS-7, MCS-8 and DAS-5 to DAS-12
- EGPRS2-B: for uplink TBFs, this comprises MCS-1 to MCS-4 and UBS-5 to UBS-12; for downlink TBFs, this comprises MCS-1 to MCS-4, MCS-6 to MCS-9, DAS-5, DAS-6, DAS-8, DAS-9, DAS-11 and DBS-5 to DBS-12.
A RESEGMENT bit is included within each PACKET UPLINK ACK/NACK, PACKET UPLINK ASSIGNMENT, MULTIPLE TBF UPLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE, MULTIPLE TBF TIMESLOT RECONFIGURE or PACKET CS RELEASE INDICATION messages. For initial transmissions of new RLC blocks the channel coding commanded is applied. The RESEGMENT bit is used to set the ARQ mode to type I or type II (incremental redundancy) for uplink TBFs. For retransmissions, setting the RESEGMENT bit to '1' (type I ARQ) requires the mobile station to use an MCS within the same family as the initial transmission and the payload may be split (refer to table 8.1.1.1). For retransmissions, setting the RESEGMENT bit to '0' (type II ARQ) requires the mobile station to use an MCS within the same family as the initial transmission without splitting the payload even if the network has commanded it to use MCS‑1, MCS‑2 or MCS‑3 for subsequent RLC blocks (refer to table 8.1.1.2), see note. In RLC unacknowledged mode, RESEGMENT bit shall be ignored and default value 0 should be used.
References
3GPP TS 44.060, subclause 5.2.1 and 8.1.1
58c.2.4a.2 Test purpose
1. To verify that the mobile station uses the correct channel coding commanded by the Network for initial transmission.
2. To verify that correct channel coding command is used for retransmission.
58c.2.4a.3 Method of test
Initial Conditions
System Simulator:
1 cell with EGPRS support, default setting, PBCCH not present.
Mobile Station:
The MS is EGPRS updated with a P-TMSI allocated, SPLIT PG CYCLE negotiated and the test PDP context2 activated.
Specific PICS Statements
- Support of PSK in uplink (TSPC_Type_EGPRS_8PSK_uplink)
- Support of QAM in uplink (TSPC_Type_EGPRS_16QAM_uplink)
PIXIT Statements
-
Test Procedure
The EGPRS capable MS is made to transmit uplink RLC data blocks in EGPRS TBF RLC acknowledged mode. The EGPRS Channel Coding Command IE is commanded in the Packet Uplink Assignment message. The resegment IE is set to 1.
The SS checks that the Uplink RLC Data Blocks are transmitted by the mobile using the channel coding scheme commanded by the SS.
The SS negatively acknowledges the received data blocks. The Coding scheme to be used by the mobile is commanded in the EGPRS Channel Coding Command IE.
The SS checks that the Uplink RLC data blocks are retransmitted using the channel coding scheme commanded by the SS.
Maximum Duration of Test
5 minutes.
Expected Sequence
MS supporting ‘EGPRS capable of 8PSK and 16 QAM in Uplink, of all Multislot classes’ should run the test for k=0, k=1, k=2, k=3, k=4.
Expected Sequence
Step
Direction
Message
Comments
For K=0
MCS-A = UAS-11
MCS-B = MCS-6
MCS-C = MCS-3
For K=1
MCS-A = UAS-10
MCS-B = MCS-5
MCS-C = MCS-2
For K=2
MCS-A = UAS-9
MCS-B = MCS-6
MCS-C = MCS-3
For K=3
MCS-A = UAS-8
MCS-B = MCS-6
MCS-C = MCS-3
For K=4
MCS-A = UAS-7
MCS-B = MCS-5
MCS-C = MCS-2
1
{Uplink dynamic allocation two phase access}
N = 1000 octets
USF_GRANULARITY = 1 block
Resegment IE=1
EGPRS Channel Coding Command: MCS-A
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 correct MCS MCS-A is used.
4
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
Sent on the PACCH of the PDCH assigned, containing USF assigned to the MS.
5
MS -> SS
EGPRS UPLINK RLC DATA BLOCK
Received on the assigned PDTCH
SS verifies that the correct MCS MCS-A is used.
6
SS -> MS
PACKET UPLINK ACK/NACK
Wait for BS_CV_MAX block periods before sending this message.
SS acknowledges first RLC data block, and negatively acknowledges second RLC data block.
USF not assigned to the MS
Resegment IE=1
EGPRS Channel Coding Command: MCS-B
7
Wait for 6 blocks with no USF
8
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
Sent on the PACCH of the PDCH assigned, containing USF assigned to the MS.
9a
(optional)
MS -> SS
EGPRS UPLINK RLC DATA BLOCK
Received on the assigned PDTCH. The MS may send a new data block already in the transmit buffer using MCS-A
9b
(optional)
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
If optional step 9a was received.
Sent on the PACCH of the PDCH assigned, containing USF assigned to the MS.
9
MS -> SS
EGPRS UPLINK RLC DATA BLOCK
Received on the assigned PDTCH
SS verifies that the correct MCS MCS-B is used.
10
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
Sent on the PACCH of the PDCH assigned, containing USF assigned to the MS.
11
MS -> SS
EGPRS UPLINK RLC DATA BLOCK
Received on the assigned PDTCH
SS verifies that the correct MCS MCS-B is used.
12
SS -> MS
PACKET UPLINK ACK/NACK
Wait for BS_CV_MAX block periods before sending this message.
SS negatively acknowledges the retransmitted RLC data block.
EGPRS Channel Coding Command: MCS-C
USF not assigned to the MS
Resegment IE=1
Wait for 6 blocks with no USF
13
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
Sent on the PACCH of the PDCH assigned, containing USF assigned to the MS.
14a
(optional)
MS -> SS
EGPRS UPLINK RLC DATA BLOCK
Received on the assigned PDTCH. The MS may send a new data block already in the transmit buffer using MCS-B
14b
(optional)
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
If optional step 14a was received.
Sent on the PACCH of the PDCH assigned, containing USF assigned to the MS.
15
MS -> SS
EGPRS UPLINK RLC DATA BLOCK
Received on the assigned PDTCH
SS verifies that the correct MCS MCS-C is used.
16
{Completion of uplink RLC data block transfer}
58c.2.5a Acknowledged Mode/ Uplink TBF/ Recalculation of CV on MCS change for EGPRS2A
58c.2.5a.1 Conformance requirements
1. The mobile station shall send the Countdown Value (CV) in each uplink RLC data block to indicate the current number of remaining RLC data blocks for the uplink TBF. The CV shall be calculated as follows:
where:
TBC = total number of RLC data blocks currently to be transmitted in the TBF.
BSN' = absolute block sequence number of the RLC data block, with range from 0 to (TBC - 1).
NTS = number of timeslots assigned to the uplink TBF in the assignment message, with range 1 to 8 when operating in BTTI configuration. In RTTI configuration this parameter shall be equal to the number of assigned uplink PDCH pairs, with the range 1 to 4.
K =2 when commanded MCS is MCS-7, MCS-8, MCS-9, UAS-7, UAS-8, UAS-9, UBS-7 or UBS-8
3 when commanded UAS-10, UAS-11, UBS-9 or UBS-10
4 when commanded UBS-11 or UBS-12 otherwise K=1
the function round() rounds upwards to the nearest integer.
BS_CV_MAX is a parameter broadcast in the system information,
the division operation is non-integer and results in zero only for (TBC - BSN' - 1) = 0.
The countdown procedure starts when RLC data blocks include CV values different from '15'. When the mobile station transmits the last RLC data block currently in the send buffer for the TBF (i.e. the RLC data block with BSN' = TBC - 1), the RLC data block shall have CV set to the value '0'.
When an EGPRS or EGPRS2 RLC/MAC block for data transfer consists of two or more RLC data blocks, a CV value is calculated for each block and the CV of the RLC/MAC header refers to the last RLC data block.
2. If the mobile station receives a change in the Channel Coding Command in a PACKET UPLINK ACK/NACK message during the countdown procedure, the mobile station shall act upon the new Channel Coding Command. The mobile station shall then recalculate the CV for any untransmitted RLC data block using the new RLC data block size.
In EGPRS TBF mode, a MS may choose an alternate MCS than the one commanded, for the initial transmission of the last RLC data blocks of the TBF under the following conditions:
- the alternate MCS is more robust than the commanded MCS;
- the alternate MCS has already been commanded by the network during the TBF or was available for selection by the MS during the TBF according to the MCS selection rules for retransmissions; and
- the TBF requires no more radio blocks for initial transmission of the RLC data blocks using the alternate MCS than would be required when using the commanded MCS.
References
3GPP TS 44.060, subclause 8.1.1, 9.3.1 and clause F.3.
58c.2.5a.2 Test purpose
To verify that the mobile station correctly recalculates the CV values when the MCS is changed during countdown procedure.
58c.2.5a.3 Method of test
Initial Conditions
System Simulator:
1 cell with EGPRS support, default setting, PBCCH not present, BS_CV_MAX = 15.
Mobile Station:
The MS is EGPRS updated with a P-TMSI allocated, SPLIT PG CYCLE negotiated and the test PDP context2 activated.
Specific PICS Statements
- Support of PSK in uplink (TSPC_Type_EGPRS_8PSK_uplink)
- Support of 16QAM in uplink (TSPC_Type_EGPRS_16QAM_uplink)
PIXIT Statements
-
Test Procedure
The EGPRS capable MS is made to transmit uplink RLC data blocks in EGPRS TBF RLC acknowledged mode. UAS-10 is commanded. Total number of Data Blocks is taken to be a minimum of 20 blocks.
SS acknowledges all the Data Blocks upon reception.
SS monitors the CV of the data blocks sent.
SS sends a PACKET UL ACK/NACK message acknowledging the RLC data block with CV =14 or CV =13 and ordering a change of MCS to MCS-5.
The Mobile might send a new Data Block with UAS-10 which could have been stored in the Transmit buffer.
SS notes the BSN of the last RLC data block, received with UAS-10 as BSN2. SS verifies that CV=15 till BSN=BSN2+3*CV1-15, BSN2+3*CV1-16 or BSN=BSN2+3*CV1-17 (MS can select alternate MCS)
where CV1 = CV in the last radio block received with UAS-10
SS verifies that CV decreases progressively in further blocks.
Maximum Duration of Test
5 minutes.
Expected Sequence
Step
Direction
Message
Comments
1
{Uplink dynamic allocation two phase access}
N chosen to transmit minimum 20 blocks
USF_GRANULARITY = 1 block
EGPRS Channel Coding Command: UAS-10
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
Wait for BS_CV_MAX block periods before sending this message.
SS Acknowledges the UL RLC Data Block
USF assigned to the MS.
5
MS -> SS
EGPRS UPLINK RLC DATA BLOCK
Received on the assigned PDTCH.
SS verifies that the BSN values are in sequence, and the correct MCS is used.
6
-
Repeat steps 4 and 5 until CV = 14 or CV = 13. SS notes the BSN of the last RLC data block as BSN2, and the CV as CV1.
7
SS -> MS
PACKET UPLINK ACK/NACK
Wait for BS_CV_MAX block periods before sending this message.
SS Acknowledges the UL RLC Data Block
EGPRS CHANNEL CODING COMMAND: MCS-5
8
-
Wait for 6 blocks with no USF
9
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
Sent on the PACCH of the PDCH assigned, containing USF assigned to the MS.
Optional
Step 10a
MS -> SS
EGPRS UPLINK RLC DATA BLOCK
The MS may send a data block already in the buffer using coding scheme UAS-10.
If received, the value of CV1 and BSN2 shall be updated by this radio block according to the rule in step 6, for further calculation.
Optional Step 10b
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
Sent on the PACCH of the PDCH assigned, containing USF assigned to the MS.
10
MS -> SS
EGPRS UPLINK RLC DATA BLOCK
Received on the assigned PDTCH.
SS verifies that coding scheme MCS-5 is used;
BSN=BSN2+1
and CV = 15.
11
SS-> MS
PACKET UPLINK ACK/NACK
Wait for BS_CV_MAX block periods before sending this message.
SS Acknowledges the UL RLC Data Block
USF assigned to the MS.
12
-
Repeat steps 10 and 11 until
BSN= BSN2+ 2*CV1 – 15; SS verifies that CV remains 15 until BSN= BSN2+ 3*CV1 – 17
CV may be 14 for BSN= BSN2+ 3*CV1 – 15, or CV may be 13 for BSN= BSN2+ 3*CV1 – 15, in case MS have 3*CV1-1 RLC data blocks, or 3*CV1-2 RLC data blocks, respectively, after sending the RLC data block of BSN2, or in case MS choose to use an alternate coding scheme to transmit the last block of the TBF.
Else
CV=15 for BSN= BSN2+ 3*CV1 – 15
13
MS -> SS
EGPRS UPLINK RLC DATA BLOCK
Received on the assigned PDCH. SS verifies that the
BSN = BSN2+ 3*CV1 – 14
In case CV=14 was received for BSN= BSN2+ 3*CV1 – 15, CV=13 in the received Data block.
In case CV=13 was received for BSN= BSN2+ 3*CV1 – 15, CV=12 in the received Data block.
else CV=14 in the received Data Block.
14
SS-> MS
PACKET UPLINK ACK/NACK
Wait for BS_CV_MAX block periods before sending this message.
SS Acknowledges the UL RLC Data Block
USF assigned to the MS.
15
MS->SS
EGPRS UPLINK RLC DATA BLOCK
Received on the assigned PDCH. SS verifies that BSN is incremented by 1 and CV is decremented by 1
16
[Completion of RLC Data Block Transfer]
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
58c.2.6 Void
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
58c.2.7 Void
|
58c.2.7a EGPRS Acknowledged mode / Uplink TBF / Retransmission/ UAS or MCS Selection with Re-segmentation, in EGPRS2A
58c.2.7a.1 Conformance requirements
In EGPRS TBF mode, RLC data blocks that are transmitted for the first time shall be transmitted with the commanded MCS, except if the commanded mode is MCS-5-7, in which case the data block shall be transmitted with MCS‑5, or if the commanded mode is MCS-6-9, in which case the data block shall be transmitted with MCS-6. In the case of a Downlink Dual Carrier configuration the commanded MCS shall apply to both of the carriers. In EGPRS TBF mode, a MS may choose an alternate MCS than the one commanded, for the initial transmission of the last RLC data blocks of the TBF under the following conditions:
- the alternate MCS is more robust than the commanded MCS;
- the alternate MCS has already been commanded by the network during the TBF or was available for selection by the MS during the TBF according to the MCS selection rules for retransmissions; and
- the TBF requires no more radio blocks for initial transmission of the RLC data blocks using the alternate MCS than would be required when using the commanded MCS.
For a TBF with FANR activated, if the commanded MCS is MCS-9 (respectively MCS-4), the initial transmission of the RLC data block(s) shall be done with MCS-8 (respectively MCS-3) if a PAN field is included in the radio block.
When EMST is used, the commanded MCS shall apply to the RLC entity on the TBF identified by the TFI included in the header of the RLC/MAC block.
A RESEGMENT bit is included within each PACKET UPLINK ACK/NACK, PACKET UPLINK ASSIGNMENT, MULTIPLE TBF UPLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE, MULTIPLE TBF TIMESLOT RECONFIGURE or PACKET CS RELEASE INDICATION messages. For initial transmissions of new RLC blocks the channel coding commanded is applied. The RESEGMENT bit is used to set the ARQ mode to type I or type II (incremental redundancy) for uplink TBFs. For retransmissions, setting the RESEGMENT bit to '1' (type I ARQ) requires the mobile station to use an MCS within the same family as the initial transmission and the payload may be split (refer to table 8.1.1.1). For retransmissions, setting the RESEGMENT bit to '0' (type II ARQ) requires the mobile station to use an MCS within the same family as the initial transmission without splitting the payload even if the network has commanded it to use MCS‑1, MCS‑2 or MCS‑3 for subsequent RLC blocks (refer to table 8.1.1.2), see note. In RLC unacknowledged mode, RESEGMENT bit shall be ignored and default value 0 should be used.
NOTE: This bit is particularly useful for networks with uplink IR capability since it allows combining on retransmissions.
Table 8.1.1.3: Choice of modulation and coding scheme for retransmissions with re-segmentation (EGPRS2-A)
Scheme used for Initial transmission
Scheme to use for retransmissions after switching to a different modulation and coding scheme (MCS or UAS)
UAS-11 Commanded
UAS-10 Commanded
UAS-9 Commanded
UAS-8 Commanded
UAS-7 Commanded
MCS-6 Commanded
MCS-5 Commanded
MCS-4 Commanded
MCS-3 Commanded
MCS-2 Commanded
MCS-1 Commanded
UAS-11
UAS-11
UAS-8
UAS-8
UAS-8
MCS-6
(pad)
MCS-6
(pad)
MCS-3
(pad)
MCS-3
(pad)
MCS-3
(pad)
MCS-3
(pad)
MCS-3
(pad)
UAS-10
UAS-10
UAS-10
UAS-7
UAS-7
UAS-7
MCS-5
MCS-5
MCS-2
MCS-2
MCS-2
MCS-2
UAS-9
UAS-9
UAS-9
UAS-9
MCS-6
MCS-6
MCS-6
MCS-3
MCS-3
MCS-3
MCS-3
MCS-3
UAS-8
UAS-11
UAS-8
UAS-8
UAS-8
MCS-6
(pad)
MCS-6
(pad)
MCS-3
(pad)
MCS-3
(pad)
MCS-3
(pad)
MCS-3
(pad)
MCS-3
(pad)
UAS-7
UAS-10
UAS-10
UAS-7
UAS-7
UAS-7
MCS-5
MCS-5
MCS-2
MCS-2
MCS-2
MCS-2
MCS-6
UAS-9
UAS-9
UAS-9
MCS-6
MCS-6
MCS-6
MCS-3
MCS-3
MCS-3
MCS-3
MCS-3
MCS-5
UAS-10
UAS-10
UAS-7
UAS-7
UAS-7
MCS-5
MCS-5
MCS-2
MCS-2
MCS-2
MCS-2
MCS-4
MCS-4
MCS-4
MCS-4
MCS-4
MCS-4
MCS-4
MCS-4
MCS-4
MCS-1
MCS-1
MCS-1
MCS-3
MCS-3
MCS-3
MCS-3
MCS-3
MCS-3
MCS-3
MCS-3
MCS-3
MCS-3
MCS-3
MCS-3
MCS-2
MCS-2
MCS-2
MCS-2
MCS-2
MCS-2
MCS-2
MCS-2
MCS-2
MCS-2
MCS-2
MCS-2
MCS-1
MCS-1
MCS-1
MCS-1
MCS-1
MCS-1
MCS-1
MCS-1
MCS-1
MCS-1
MCS-1
MCS-1
In EGPRS2, if these rules require a transmission (either original transmission or retransmission) in a modulation and coding scheme where there are fewer than the maximum number of RLC blocks that can be transmitted, the mobile station shall use the modulation and coding scheme specified in tables 8.1.1.7 and 8.1.1.8.
Table 8.1.1.7: Retransmissions with fewer RLC blocks (EGPRS2-A)
Modulation and Coding Scheme specified
Modulation/Coding scheme to be used (only 1 block can be transmitted)
Modulation/Coding scheme to be used (only 2 blocks can be transmitted)
UAS-7
MCS-5
n/a
UAS-8
MCS-6 (with padding)
n/a
UAS-9
MCS-6
n/a
UAS-10
MCS-5
UAS-7
UAS-11
MCS-6 (with padding)
UAS-8
References
3GPP TS 44.060, subclause 8.1.1.
3GPP TS 44.060, subclause 9.3.2.1.
3GPP TS 45.010, subclause 6.11.1.
58c.2.7a.2 Test purpose
1. To verify that the mobile station retransmits Nacked data blocks with the UAS or MCS commanded and according to TS 44.060 table 8.1.1.3.
58c.2.7a.3 Method of test
Initial Conditions
System Simulator:
1 cell with EGPRS2A support, default setting,
Mobile Station:
The MS is EGPRS2A updated with a P-TMSI allocated and the test PDP context2 activated.
Specific PICS Statements
-
PIXIT Statements
-
Test Procedure
The EGPRS2A capable MS is made to transmit uplink RLC data blocks in EGPRS TBF RLC acknowledged mode. The EGPRS Channel Coding Command IE in the Packet Uplink Assignment message is set according to the execution counter K described as below.
After BS_CV_MAX block periods the SS sends a Packet Uplink Ack/Nack message to negatively acknowledge some RLC data blocks. In the message EGPRS Channel Coding Command IE is set to a different UAS or MCS and Resegment IE should be set to '0'.
The MS shall then retransmit the negatively acknowledged RLC data blocks using the UAS or MCS specified in table 8.1.1.3, 3GPP TS 44.060.
Test procedure is repeated for K = 1 to 7 with:
K = 1: UAS-11 to be used at step 1,
K = 2: UAS-10 to be used at step 1,
K = 3: UAS-9 to be used at step 1,
K = 4: UAS-8 to be used at step 1,
K = 5: UAS-7 to be used at step 1,
K = 6: MCS-6 to be used at step 1,
K = 7: MCS-5 to be used at step 1,
Maximum Duration of Test
30 minutes.
Expected Sequence
Step
Direction
Message
Comments
1
{Uplink dynamic allocation two phase access}
N = for K = 1: 4600 octets.
(K = 2: 4250, K = 3: 3500, K = 4: 3000, K = 5: 2500, K = 6: 3500, K = 7: 2500.).
USF_GRANULARITY = 1 block.
Resegment bit = 1.
EGPRS2A Channel Coding Command is set according to execution counter K (e.g., K = 1: UAS-11).
2
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
Sent on the PACCH of the PDCH assigned, USF assigned to the MS.
3
MS -> SS
EGPRS2A UPLINK RLC DATA BLOCK
Received on the assigned PDTCH.
4
Repeat steps 2 and 3 until received data block BSN = 30
5
SS -> MS
PACKET UPLINK ACK/NACK
Wait for BS_CV_MAX block periods before sending this message.
SS acknowledges RLC data blocks with BSN 10 to 30 if K = 3, K = 4 ,K = 5, BSN 10 to 31 if K = 1, K = 2, K = 6, K =7. RBB set to 1 and negatively acknowledges the rest with RBB set to 0.
USF not assigned to the MS.
EGPRS CHANNEL_CODING_COMMAND: UAS-11.
6
Wait for 6 blocks with no USF.
7
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
Sent on the PACCH of the PDCH assigned, USF assigned to the MS.
A8(optional step)
MS -> SS
EGPRS2A UPLINK RLC DATA BLOCK
MS may transmit new in-sequence data block if it has already been scheduled while Packet Uplink Ack/Nack is being processed.
B8 (optional step)
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
USF assigned to the MS,
8
MS -> SS
EGPRS2A UPLINK RLC DATA BLOCK
Received on the assigned PDTCH.
BSN = 0...9.
The SS verifies that the NACKED data blocks are received using the correct MCS or UAS according to tables 8.1.1.3 and 8.1.1.7, 3GPP TS 44.060.
9
SS
Repeat steps 7 & 8 nine times.
10
SS -> MS
PACKET UPLINK ACK/NACK
Wait for BS_CV_MAX block periods before sending this message.
SS acknowledges retransmitted RLC data blocks with BSN 0,
RBB set to 1 and negatively acknowledges the rest with RBB set to 0USF not assigned to the MS.
EGPRS CHANNEL_CODING_COMMAND: UAS-10.
11
Wait for 6 blocks with no USF.
12
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
Sent on the PACCH of the PDCH, containing USF assigned to the MS.
A13(optional step)
MS -> SS
EGPRS2A UPLINK RLC DATA BLOCK
MS may transmit new in-sequence data block if it has already been scheduled while Packet Uplink Ack/Nack is being processed.
B13 (optional step)
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
USF assigned to the MS.
13
MS -> SS
EGPRS2A UPLINK RLC DATA BLOCK
Received on the assigned PDTCH.
BSN = 1...9.
The SS verifies that the NACKED data blocks are received using the correct MCS or UAS according to tables 8.1.1.3 and 8.1.1.7, 3GPP TS 44.060.
14
Repeat steps 12 & 13 eight times.
15
SS -> MS
PACKET UPLINK ACK/NACK
Wait for BS_CV_MAX block periods before sending this message.
SS acknowledges retransmitted RLC data blocks with BSN = 1,
RBB set to 1 and negatively acknowledges the rest with RBB set to 0.
USF not assigned to the MS.
EGPRS CHANNEL_CODING_COMMAND: UAS-9.
16
Wait for 6 blocks with no USF.
17
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
Sent on the PACCH of the PDCH, containing USF assigned to the MS.
A18(optional step)
MS -> SS
EGPRS2A UPLINK RLC DATA BLOCK
MS may transmit new in-sequence data block if it has already been scheduled while Packet Uplink Ack/Nack is being processed.
B18 (optional step)
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
USF assigned to the MS.
18
MS -> SS
EGPRS2A UPLINK RLC DATA BLOCK
Received on the assigned PDTCH.
BSN = 2...9.
The SS verifies that the NACKED data blocks are received using the correct MCS or UAS according to tables 8.1.1.3 and 8.1.1.7, 3GPP TS 44.060.
BSN = 2 and BSN = 3 are received in the same radio block.
19
Repeat steps 17 & 18 seven times.
20
SS -> MS
PACKET UPLINK ACK/NACK
Wait for BS_CV_MAX block periods before sending this message.
SS acknowledges retransmitted RLC data blocks with BSN 2,
RBB set to 1 and negatively acknowledges the rest with RBB set to 0.
USF not assigned to the MS.
EGPRS CHANNEL_CODING_COMMAND: UAS-8.
21
Wait for 6 blocks with no USF.
22
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
Sent on the PACCH of the PDCH, containing USF assigned to the MS.
A23(optional step)
MS -> SS
EGPRS2A UPLINK RLC DATA BLOCK
MS may transmit new in-sequence data block if it has already been scheduled while Packet Uplink Ack/Nack is being processed.
B23 (optional step)
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
USF assigned to the MS.
23
MS -> SS
EGPRS2A UPLINK RLC DATA BLOCK
Received on the assigned PDTCH
BSN = 3...9.
The SS verifies that the NACKED data blocks are received using the correct MCS or UAS according to tables 8.1.1.3 and 8.1.1.7, 3GPP TS 44.060.
24
Repeat steps 22 & 23 six times.
25
SS -> MS
PACKET UPLINK ACK/NACK
Wait for BS_CV_MAX block periods before sending this message.
SS acknowledges retransmitted RLC data blocks with BSN 3,
RBB set to 1 and negatively acknowledges the rest with RBB set to 0.
USF not assigned to the MS
EGPRS CHANNEL_CODING_COMMAND: UAS-7.
26
Wait for 6 blocks with no USF.
27
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
Sent on the PACCH of the PDCH, containing USF assigned to the MS.
A28(optional step)
MS -> SS
EGPRS2A UPLINK RLC DATA BLOCK
MS may transmit new in-sequence data block if it has already been scheduled while Packet Uplink Ack/Nack is being processed.
B28 (optional step)
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
USF assigned to the MS.
28
MS -> SS
EGPRS2A UPLINK RLC DATA BLOCK
Received on the assigned PDTCH
BSN = 4...9.The SS verifies that the NACKED data blocks are received using the correct MCS or UAS according to tables 8.1.1.3 and 8.1.1.7, 3GPP TS 44.060.
29
Repeat steps 27 & 28 five times.
30
SS -> MS
PACKET UPLINK ACK/NACK
Wait for BS_CV_MAX block periods before sending this message.
SS acknowledges retransmitted RLC data blocks with BSN 4,
RBB set to 1 and negatively acknowledges the rest with RBB set to 0.
USF not assigned to the MS.
EGPRS CHANNEL_CODING_COMMAND: MCS-6.
31
Wait for 6 blocks with no USF.
32
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
Sent on the PACCH of the PDCH, containing USF assigned to the MS.
A33(optional step)
MS -> SS
EGPRS2A UPLINK RLC DATA BLOCK
MS may transmit new in-sequence data block if it has already been scheduled while Packet Uplink Ack/Nack is being processed.
B33 (optional step)
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
USF assigned to the MS.
33
MS -> SS
EGPRS2A UPLINK RLC DATA BLOCK
Received on the assigned PDTCH
BSN = 5...9.
The SS verifies that the NACKED data blocks are received using the correct MCS or UAS according to tables 8.1.1.3 and 8.1.1.7, 3GPP TS 44.060.
34
Repeat steps 32 & 33 four times.
35
SS -> MS
PACKET UPLINK ACK/NACK
Wait for BS_CV_MAX block periods before sending this message.
SS acknowledges retransmitted RLC data blocks with BSN 5,
RBB set to 1 and negatively acknowledges the rest with RBB set to 0.
USF not assigned to the MS.
EGPRS CHANNEL_CODING_COMMAND: MCS-5
36
Wait for 6 blocks with no USF.
37
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
Sent on the PACCH of the PDCH, containing USF assigned to the MS.
A38(optional step)
MS -> SS
EGPRS2A UPLINK RLC DATA BLOCK
MS may transmit new in-sequence data block if it has already been scheduled while Packet Uplink Ack/Nack is being processed.
B38 (optional step)
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
USF assigned to the MS.
38
MS -> SS
EGPRS2A UPLINK RLC DATA BLOCK
Received on the assigned PDTCH
BSN = 6...9.
The SS verifies that the NACKED data blocks are received using the correct MCS or UAS according to tables 8.1.1.3 and 8.1.1.7, 3GPP TS 44.060.
39
Repeat steps 37 & 38 three times.
40
SS -> MS
PACKET UPLINK ACK/NACK
Wait for BS_CV_MAX block periods before sending this message.
SS acknowledges retransmitted RLC data blocks with BSN 6,
RBB set to 1 and negatively acknowledges the rest with RBB set to 0.
USF not assigned to the MS.
41
{ Completion of uplink RLC data block transfer}
-
Repeat the above procedure with K = 2...7.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
58c.2.8 Void
|
58c.2.8a Acknowledged Mode/ Uplink TBF/ Link Adaptation Procedure for Initial Transmission in EGPRS2A
58c.2.8a.1 Conformance requirements
1. In EGPRS TBF mode, RLC data blocks that are transmitted for the first time shall be transmitted with the MCS commanded, except if the commanded mode is MCS-5-7, in which case the data block shall be transmitted with MCS-5, or if the commanded mode is MCS-6-9, in which case the data block shall be transmitted with MCS-6.
2. In EGPRS2, if these rules require a transmission (either original transmission or retransmission) in a modulation and coding scheme where there are fewer than the maximum number of RLC blocks that can be transmitted, the mobile station shall use the modulation and coding scheme specified in tables 8.1.1.7 and 8.1.1.8.
Table 8.1.1.7: Retransmissions with fewer RLC blocks (EGPRS2-A)
Modulation and Coding Scheme specified
Modulation/Coding scheme to be used (only 1 block can be transmitted)
Modulation/Coding scheme to be used (only 2 blocks can be transmitted)
UAS-7
MCS-5
n/a
UAS-8
MCS-6 (with padding)
n/a
UAS-9
MCS-6
n/a
UAS-10
MCS-5
UAS-7
UAS-11
MCS-6 (with padding)
UAS-8
References
3GPP TS 44.060, subclause 8.1.1
3GPP TS 44.060, subclause 9.3.2.1
3GPP TS 44.060, subclause 6.11.1
58c.2.8a.2 Test purpose
To verify the mobile station transmits data blocks with the correct MCS value in initial transmission.
58c.2.8a.3 Method of test
Initial Conditions
System Simulator:
1 cell with EGPRS support, default setting, PBCCH not present.
Mobile Station:
The MS is EGPRS updated with a P-TMSI allocated, SPLIT PG CYCLE negotiated and the test PDP context2 activated.
Specific PICS Statements
- Support of PSK in uplink (TSPC_Type_EGPRS_8PSK_uplink)
- Support of QAM in uplink (TSPC_Type_EGPRS_16QAM_uplink)
PIXIT Statements
-
Test Procedure
The EGPRS capable MS is made to transmit uplink RLC data blocks in EGPRS TBF RLC acknowledged mode. The SS acknowledges the RLC data blocks transmitted by the MS and verifies that the correct MCS is used, as mentioned below.
Execution counter
k
Number of octets
n
Commanded MCS to
be used in step 1
Expected MCS to be
used in step 4
1
1000
UAS-11
UAS-11
2
1000
UAS-10
UAS-10
3
1000
UAS-9
UAS-9
4
1000
UAS-8
UAS-8
5
1000
UAS-7
UAS-7
6
1000
MCS-6
MCS-6
7
1000
MCS-5
MCS-5
8
1000
MCS-4
MCS-4
9
1000
MCS-3
MCS-3
10
1000
MCS-2
MCS-2
11
1000
MCS-1
MCS-1
12
64<x≤ 128
UAS-11
UAS-8
13
56<x≤ 112
UAS-10
UAS-7
14
5 (max 64)
UAS-11
MCS-6
15
5 (max 56)
UAS-10
MCS-5
16
5 (max 74)
UAS-9
MCS-6
17
5 (max 64)
UAS-8
MCS-6
18
5 (max 56)
UAS-7
MCS-5
NOTE: Note: For k = 12, 13 the number of octets of data at the RLC Layer, x, must lie within the specified range. For k =14-18 the number of octets of data at the RLC Layer must not exceed the specified value.
Maximum Duration of Test
5 minutes.
Expected Sequence
Step
Direction
Message
Comments
1
{ Uplink dynamic allocation two phase access}
n = number of octets according to execution counter k (e.g. k = 1: n = 1000)
USF_GRANULARITY = 1 block
Resegment bit = 1
EGPRS CHANNEL_CODING_COMMAND: according to execution counter k (e.g. k = 1: UAS-11)
UPLINK EGPRS LEVEL = 01
Window size = 96
2
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
Sent on the PACCH of the PDCH assigned, USF assigned to the MS.
3
MS -> SS
UPLINK RLC DATA BLOCK
Received on the assigned PDTCH
4
SS -> MS
PACKET UPLINK ACK/NACK
Wait for BS_CV_MAX block periods before sending this message.
SS acknowledges the first RLC data block,
RBB set to 1.
SS verifies that the expected modulation and coding scheme is used according to execution counter k (e.g. k=1: UAS-11) (Skip step 5-8 for k=12-18)
5
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
Sent on the PACCH of the PDCH assigned, USF assigned to the MS.
6
MS -> SS
UPLINK RLC DATA BLOCK
Received on the assigned PDTCH
7
Repeat steps 5 and 6 until all data blocks has been received
8
SS -> MS
PACKET UPLINK ACK/NACK
Wait for BS_CV_MAX block periods before sending this message.
SS acknowledges all RLC data blocks,
RBB set to 1.
9
{Completion of uplink RLC data block transfer}
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
58c.2.9 Void
|
58c.2.9a Acknowledged Mode/ Uplink TBF/ Retransmission/ MCS or UAS Selection without Re-segmentation, in EGPRS2A
58c.2.9a.1 Conformance requirements
In EGPRS TBF mode, RLC data blocks that are transmitted for the first time shall be transmitted with the commanded MCS, except if the commanded mode is MCS-5-7, in which case the data block shall be transmitted with MCS‑5, or if the commanded mode is MCS-6-9, in which case the data block shall be transmitted with MCS-6. In the case of a Downlink Dual Carrier configuration the commanded MCS shall apply to both of the carriers. In EGPRS TBF mode, a MS may choose an alternate MCS than the one commanded, for the initial transmission of the last RLC data blocks of the TBF under the following conditions:
- the alternate MCS is more robust than the commanded MCS;
- the alternate MCS has already been commanded by the network during the TBF or was available for selection by the MS during the TBF according to the MCS selection rules for retransmissions; and
- the TBF requires no more radio blocks for initial transmission of the RLC data blocks using the alternate MCS than would be required when using the commanded MCS.
For a TBF with FANR activated, if the commanded MCS is MCS-9 (respectively MCS-4), the initial transmission of the RLC data block(s) shall be done with MCS-8 (respectively MCS-3) if a PAN field is included in the radio block.
When EMST is used, the commanded MCS shall apply to the RLC entity on the TBF identified by the TFI included in the header of the RLC/MAC block.
A RESEGMENT bit is included within each PACKET UPLINK ACK/NACK, PACKET UPLINK ASSIGNMENT, MULTIPLE TBF UPLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE, MULTIPLE TBF TIMESLOT RECONFIGURE or PACKET CS RELEASE INDICATION messages. For initial transmissions of new RLC blocks the channel coding commanded is applied. The RESEGMENT bit is used to set the ARQ mode to type I or type II (incremental redundancy) for uplink TBFs. For retransmissions, setting the RESEGMENT bit to '1' (type I ARQ) requires the mobile station to use an MCS within the same family as the initial transmission and the payload may be split (refer to table 8.1.1.1). For retransmissions, setting the RESEGMENT bit to '0' (type II ARQ) requires the mobile station to use an MCS within the same family as the initial transmission without splitting the payload even if the network has commanded it to use MCS‑1, MCS‑2 or MCS‑3 for subsequent RLC blocks (refer to table 8.1.1.2), see note. In RLC unacknowledged mode, RESEGMENT bit shall be ignored and default value 0 should be used.
NOTE: This bit is particularly useful for networks with uplink IR capability since it allows combining on retransmissions.
Table 8.1.1.4: Choice of modulation and coding scheme for retransmissions without re-segmentation (EGPRS2-A)
Scheme used for Initial transmission
Scheme to use for retransmissions after switching to a different modulation and coding scheme (MCS or UAS)
UAS-11 Commanded
UAS-10 Commanded
UAS-9 Commanded
UAS-8 Commanded
UAS-7 Commanded
MCS-6 Commanded
MCS-5 Commanded
MCS-4 Commanded
MCS-3 Commanded
MCS-2 Commanded
MCS-1 Commanded
UAS-11
UAS-11
UAS-8
UAS-8
UAS-8
MCS-6
(pad)
MCS-6
(pad)
MCS-6
(pad)
MCS-6
(pad)
MCS-6
(pad)
MCS-6
(pad)
MCS-6
(pad)
UAS-10
UAS-10
UAS-10
UAS-7
UAS-7
UAS-7
MCS-5
MCS-5
MCS-5
MCS-5
MCS-5
MCS-5
UAS-9
UAS-9
UAS-9
UAS-9
MCS-6
MCS-6
MCS-6
MCS-6
MCS-6
MCS-6
MCS-6
MCS-6
UAS-8
UAS-11
UAS-8
UAS-8
UAS-8
MCS-6
(pad)
MCS-6
(pad)
MCS-6
(pad)
MCS-6
(pad)
MCS-6
(pad)
MCS-6
(pad)
MCS-6
(pad)
UAS-7
UAS-10
UAS-10
UAS-7
UAS-7
UAS-7
MCS-5
MCS-5
MCS-5
MCS-5
MCS-5
MCS-5
MCS-6
UAS-9
UAS-9
UAS-9
MCS-6
MCS-6
MCS-6
MCS-6
MCS-6
MCS-6
MCS-6
MCS-6
MCS-5
UAS-10
UAS-10
UAS-7
UAS-7
UAS-7
MCS-5
MCS-5
MCS-5
MCS-5
MCS-5
MCS-5
MCS-4
MCS-4
MCS-4
MCS-4
MCS-4
MCS-4
MCS-4
MCS-4
MCS-4
MCS-4
MCS-4
MCS-4
MCS-3
MCS-3
MCS-3
MCS-3
MCS-3
MCS-3
MCS-3
MCS-3
MCS-3
MCS-3
MCS-3
MCS-3
MCS-2
MCS-2
MCS-2
MCS-2
MCS-2
MCS-2
MCS-2
MCS-2
MCS-2
MCS-2
MCS-2
MCS-2
MCS-1
MCS-1
MCS-1
MCS-1
MCS-1
MCS-1
MCS-1
MCS-1
MCS-1
MCS-1
MCS-1
MCS-1
Table 8.1.1.7: Retransmissions with fewer RLC blocks (EGPRS2-A)
Modulation and Coding Scheme specified
Modulation/Coding scheme to be used (only 1 block can be transmitted)
Modulation/Coding scheme to be used (only 2 blocks can be transmitted)
UAS-7
MCS-5
n/a
UAS-8
MCS-6 (with padding)
n/a
UAS-9
MCS-6
n/a
UAS-10
MCS-5
UAS-7
UAS-11
MCS-6 (with padding)
UAS-8
References
3GPP TS 44.060, subclause 8.1.1.
58c.2.9a.2 Test purpose
1. To verify that if the re-segment bit is not set, the mobile station shall use a MCS or UAS within the same family as the initial MCS or UAS without splitting the payload for retransmission in accordance with subclause 8.1.1 table 8.1.1.4, 3GPP TS 44.060.
58c.2.9a.3 Method of test
Initial Conditions
System Simulator:
1 cell with EGPRS2A support, default settings
Mobile Station:
The MS is EGPRS2A updated with a P-TMSI allocated and the test PDP context2 activated.
Specific PICS Statements
-
PIXIT Statements
-
Test Procedure
The EGPRS2A capable MS is made to transmit uplink RLC data blocks in EGPRS TBF RLC acknowledged mode. The EGPRS Channel Coding Command IE in the Packet Uplink Assignment message is set according to the execution counter K described as below.
After BS_CV_MAX block periods the SS sends a Packet Uplink Ack/Nack message to negatively acknowledge some RLC data blocks. In the message EGPRS Channel Coding Command IE is set to a different MCS or UAS and Resegment IE should be set to '0'.
The MS shall then retransmit the negatively acknowledged RLC data blocks using the MCS or UAS specified in table 8.1.1.4, 3GPP TS 44.060.
Test procedure is repeated for K = 1 to 7 with:
K = 1: UAS-11 to be used at step 1,
K = 2: UAS-10 to be used at step 1,
K = 3: UAS-9 to be used at step 1,
K = 4: UAS-8 to be used at step 1,
K = 5: UAS-7 to be used at step 1,
K = 6: MCS-6 to be used at step 1,
K = 7: MCS-5 to be used at step 1,
Maximum Duration of Test
30 minutes.
Expected Sequence
Step
Direction
Message
Comments
1
{Uplink dynamic allocation two phase access}
N = for K = 1: 4600 octets.
(K = 2: 4250, K = 3: 3500, K = 4: 3000, K = 5: 2500, K = 6: 3500, K = 7: 2500.)
USF_GRANULARITY = 1 block.
EGPRS Channel Coding Command is set according to execution counter K (e.g., K=1: UAS-11).
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
EGPRS2A UPLINK RLC DATA BLOCK
Received on the assigned PDTCH.
The SS verifies that the BSN starts from 0, and verifies the correct MCS or UAS is used.
4
-
Repeat steps 2 and 3 until RLC data block BSN = 31.
5
-
Wait for BS_CV_MAX block periods relative to the last received RLC data block.
6
SS -> MS
PACKET UPLINK ACK/NACK
The SS acknowledges RLC data blocks from BSN 10 to 31 with RBB set to 1 and negatively acknowledges RLC data blocks from BSN 1 to 9 with RBB set to 0, SSN = 1 (Note: This is NACK for BSN = 0).
USF not assigned to the MS.
EGPRS Channel Coding Command is set to UAS-11.
Resegment IE is set to '0'.
7
-
Wait for 6 blocks with no USF.
8
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
Sent on the PACCH of the PDCH assigned, containing USF assigned to the MS.
A9
(optional step)
MS -> SS
EGPRS2A UPLINK RLC DATA BLOCK
MS may transmit new data block if it has already been scheduled while Packet Uplink Ack/Nack is being processed.
B9
(optional step)
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
USF assigned to the MS.
9
MS -> SS
EGPRS2A UPLINK RLC DATA BLOCK
Received on the assigned PDTCH.
BSN = 0...9.
The SS verifies that the NACKED data blocks are received using the correct MCS or UAS according to tables 8.1.1.4 and 8.1.1.7, 3GPP TS 44.060.
If K = 1, 2, 4, 5 or 7 BSN = 0 and BSN = 1 are received in the same radio block.
If K = 3 or 6 then BSN = 2 is also received in the same radio block.
10
-
Repeat steps 8 & 9 three times if K = 1, 2, 4, 5 or 7 and four times if K = 3 or 6.
11
SS -> MS
PACKET UPLINK ACK/NACK
Wait for BS_CV_MAX block periods before sending this message.
The SS acknowledges RLC data block BSN = 0 with SSN = 2 and negatively acknowledges RLC data blocks from BSN 2 to 9 with RBB set to 0. For BSN > 9 RBB is set to 1.
USF not assigned to the MS.
EGPRS Channel Coding Command is set to UAS-10.
Resegment IE is set to '0'.
12
-
Wait for 6 blocks with no USF.
13
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
Sent on the PACCH of the PDCH assigned, containing USF assigned to the MS.
A14
(optional step)
MS -> SS
EGPRS2A UPLINK RLC DATA BLOCK
MS may transmit new data block if it has already been scheduled while Packet Uplink Ack/Nack is being processed.
B14
(optional step)
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
USF assigned to the MS,
14
MS -> SS
EGPRS2A UPLINK RLC DATA BLOCK
Received on the assigned PDTCH.
If K = 1, 3, 4 or 6 BSN = 1...8.
For K = 2, 5 or 7 BSN = 1...9.
The SS verifies that the NACKED data blocks are received using the correct MCS or UAS according to tables 8.1.1.4 and 8.1.1.7, 3GPP TS 44.060.
If K = 1, 3, 4 or 6 BSN = 1 and BSN = 2 are received in the same radio block.
If K = 2, 5 or 7 then BSN = 3 is also received in the same radio block.
15
-
Repeat steps 13 & 14 two times if K = 2, 5 or 7 and three times if K = 1, 3, 4 or 6.
16
SS -> MS
PACKET UPLINK ACK/NACK
Wait for BS_CV_MAX block periods before sending this message.
The SS acknowledges RLC data block BSN = 1 with SSN = 3 and negatively acknowledges RLC data blocks from BSN 3 to 9 with RBB set to 0. For BSN > 9 RBB is set to 1.
USF not assigned to the MS.
EGPRS Channel Coding Command is set to UAS-9.
Resegment IE is set to '0'.
17
-
Wait for 6 blocks with no USF.
18
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
Sent on the PACCH of the PDCH assigned, containing USF assigned to the MS.
A19
(optional step)
MS -> SS
EGPRS2A UPLINK RLC DATA BLOCK
For K = 1, 3, 4 or 6 the MS may retransmit a RLC data block with BSN = 9.
For K = 2, 5 or 7 MS may transmit new data block if it has already been scheduled while Packet Uplink Ack/Nack is being processed.
B19
(optional step)
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
USF assigned to the MS.
19
MS -> SS
EGPRS2A UPLINK RLC DATA BLOCK
Received on the assigned PDTCH.
If K = 1, 3, 4 or 6 BSN = 2...7.
If K = 2, 5 or 7 BSN = 2...9.
The SS verifies that the NACKED data blocks are received using the correct MCS or UAS according to tables 8.1.1.4 and 8.1.1.7, 3GPP TS 44.060.
BSN = 2 and BSN = 3 are received in the same radio block.
20
-
Repeat steps 18 & 19 two times if K = 1, 3, 4 or 6 and three times if K = 2, 5 or 7.
21
SS -> MS
PACKET UPLINK ACK/NACK
Wait for BS_CV_MAX block periods before sending this message.
The SS acknowledges RLC data block BSN 2 with SSN = 4 and negatively acknowledges RLC data blocks from BSN 3 to 9 with RBB set to 0. For BSN > 9 RBB is set to 1.
USF not assigned to the MS.
EGPRS Channel Coding Command is set to UAS-8.
Resegment IE is set to '0'.
22
-
Wait for 6 blocks with no USF
23
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
Sent on the PACCH of the PDCH assigned, containing USF assigned to the MS.
A24
(optional step)
MS -> SS
EGPRS2A UPLINK RLC DATA BLOCK
For K = 1, 3, 4 or 6 the MS may retransmit a data block with BSN = 8.
For K = 2, 5 or 7 the MS may transmit new data block if it has already been scheduled while Packet Uplink Ack/Nack is being processed.
B24
(optional step)
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
USF assigned to the MS,
24
MS -> SS
EGPRS2A UPLINK RLC DATA BLOCK
Received on the assigned PDTCH.
If K = 1, 3, 4 or 6 and step A24 was performed, BSN = 3...7 and 9 will be received.
If K = 2, 5 or 7 BSN = 3...9 will be received.
The SS verifies that the NACKED data blocks are received using the correct MCS or UAS according to tables 8.1.1.4 and 8.1.1.7, 3GPP TS 44.060.
25
-
Repeat steps 23 & 24 two times if K = 1 or 4 and
three times if K = 2, 5, or 7
and five times if K = 3 or 6.
26
SS -> MS
PACKET UPLINK ACK/NACK
Wait for BS_CV_MAX block periods before sending this message.
The SS acknowledges RLC data block BSN 3 with SSN = 5 and negatively acknowledges RLC data blocks from BSN 4 to 9 with RBB set to 0. For BSN > 9 RBB is set to 1.
USF not assigned to the MS.
EGPRS Channel Coding Command is set to UAS-7.
Resegment IE is set to '0'.
27
-
Wait for 6 blocks with no USF.
28
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
Sent on the PACCH of the PDCH assigned, containing USF assigned to the MS.
A29
(optional step)
MS -> SS
EGPRS2A UPLINK RLC DATA BLOCK
MS may transmit new data block if it has already been scheduled while Packet Uplink Ack/Nack is being processed.
B29
(optional step)
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
USF assigned to the MS.
29
MS -> SS
EGPRS2A UPLINK RLC DATA BLOCK
Received on the assigned PDTCH.
BSN = 4...9.
The SS verifies that the NACKED data blocks are received using the correct MCS or UAS according to tables 8.1.1.4 and 8.1.1.7, 3GPP TS 44.060.
30
-
Repeat steps 28 & 29 two times if K = 2, 5 or 7 and five times if K = 1, 3, 4 or 6.
31
SS -> MS
PACKET UPLINK ACK/NACK
Wait for BS_CV_MAX block periods before sending this message.
The SS acknowledges RLC data block BSN 4 with SSN = 6 and negatively acknowledges RLC data blocks from BSN 5 to 9 with RBB set to 0. For BSN > 9 RBB is set to 1.
USF not assigned to the MS.
EGPRS Channel Coding Command is set to MCS-6.
Resegment IE is set to '0'.
32
-
Wait for 6 blocks with no USF.
33
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
Sent on the PACCH of the PDCH assigned, containing USF assigned to the MS.
A34
(optional step)
MS -> SS
EGPRS2A UPLINK RLC DATA BLOCK
MS may transmit new data block if it has already been scheduled while Packet Uplink Ack/Nack is being processed.
B34
(optional step)
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
USF assigned to the MS.
34
MS -> SS
EGPRS2A UPLINK RLC DATA BLOCK
Received on the assigned PDTCH.
BSN = 5...9.
The SS verifies that the NACKED data blocks are received using the correct MCS or UAS according to tables 8.1.1.4 and 8.1.1.7, 3GPP TS 44.060.
35
-
Repeat steps 33 & 34 four times.
36
SS -> MS
PACKET UPLINK ACK/NACK
Wait for BS_CV_MAX block periods before sending this message.
The SS acknowledges RLC data block BSN 5 with SSN = 7 and negatively acknowledges RLC data blocks from BSN 6 to 9 with RBB set to 0. For BSN > 9 RBB is set to 1.
USF not assigned to the MS.
EGPRS Channel Coding Command is set to MCS-5.
Resegment IE is set to '0'.
37
-
Wait for 6 blocks with no USF.
38
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
Sent on the PACCH of the PDCH assigned, containing USF assigned to the MS.
A39
(optional step)
MS -> SS
EGPRS2A UPLINK RLC DATA BLOCK
MS may transmit new data block if it has already been scheduled while Packet Uplink Ack/Nack is being processed.
B39
(optional step)
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
USF assigned to the MS.
39
MS -> SS
EGPRS2A UPLINK RLC DATA BLOCK
Received on the assigned PDTCH.
BSN = 6...9.
The SS verifies that the NACKED data blocks are received using the correct MCS or UAS according to tables 8.1.1.4 and 8.1.1.7, 3GPP TS 44.060.
40
-
Repeat steps 38 & 39 three times.
41
SS -> MS
PACKET UPLINK ACK/NACK
Wait for BS_CV_MAX block periods before sending this message.
The SS acknowledges RLC data block BSN 6 with SSN = 8 and negatively acknowledges RLC data blocks from BSN 7 to 9 with RBB set to 0. For BSN > 9 RBB is set to 1.
USF not assigned to the MS.
42
{Completion of uplink RLC data block transfer}
-
Repeat the above procedure with K = 2...7.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
58c.2.10 Void
|
58c.2.10a Acknowledged Mode/ Uplink TBF/ Initial Puncturing Scheme After MCS Switching, in EGPRS2A
58c.2.10a.1 Conformance requirements
1. RLC data blocks which are retransmitted using a new MCS shall at the first transmission after the MCS switch be sent with the puncturing scheme indicated in table 9.3.2.1.1, 3GPP TS 44.060 subclause 9.3.2.1.
2. The choice of modulation and coding scheme for retransmissions in EGPRS2-A with/without re-segmentation shall follow table 8.1.1.3 and table 8.1.1.4, 3GPP TS 44.060 subclause 8.1.1
References
3GPP TS 44.060, subclause 8.1.1, 9.3.2.1.
3GPP TS 45.005.
3GPP TS 45.009.
58c.2.10a.2 Test purpose
1. To verify the correct selection of PS scheme after MCS switch.
58c.2.10a.3 Method of test
Initial Conditions
System Simulator:
1 cell with EGPRS support, default setting
Mobile Station:
The MS is EGPRS updated with a P-TMSI allocated, SPLIT PG CYCLE negotiated and the test PDP context2 activated.
Specific PICS Statements
-
PIXIT Statements
-
Test Procedure
The MS is made to transmit uplink RLC data blocks in an acknowledged mode uplink EGPRS TBF. EGPRS Coding Command is set to indicate UAS-11.
The SS sends a PACKET UPLINK ACK/NACK message and NACK all blocks received. UAS-7 is commanded in the message.
The SS checks that the retransmitted blocks are received in MCS-6, PS1.
Repeat the above steps with different allowed MCS and PS combinations.
Maximum Duration of Test
5 minutes.
Expected Sequence
Step
Direction
Message
Comments
1
{Uplink dynamic allocation two phase access}
n = 2000 octets,
USF_GRANULARITY = 1 block
EGPRS Channel Coding Command: UAS-11
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 correct Puncturing Scheme is received.
4
SS
-
Repeat steps 2-3 until RLC data block with BSN=5 is received.
5
SS -> MS
PACKET UPLINK ACK/NACK
Wait for BS_CV_MAX block periods before sending this message.
SS negatively acknowledges all RLC data blocks.
MCS Command is UAS-7,
USF not assigned to the MS.
Wait for 6 blocks with no USF
6
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
Sent on the PACCH of the PDCH assigned, containing USF assigned to the MS.
A7 (optional step)
MS -> SS
EGPRS UPLINK RLC DATA BLOCK
MS may transmit new data block if it has already been scheduled while Packet Uplink Ack/Nack is being processed.
B7 (optional step)
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
USF assigned to the MS
7
MS -> SS
EGPRS UPLINK RLC DATA BLOCK
Received on the assigned PDTCH
SS verifies that modulation and coding scheme is MCS-6 (pad) and Puncturing Scheme is PS1 is received.
BSN=0
8
SS
Repeat steps 9-10 until RLC data block with BSN=5 is received.
9
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
Sent on the PACCH of the PDCH assigned, containing USF assigned to the MS.
10
MS -> SS
EGPRS UPLINK RLC DATA BLOCK
Received on the assigned PDTCH
SS verifies that modulation and coding scheme is MCS-6 and Puncturing Scheme is PS1 is received.
11
{Completion of uplink RLC data block transfer}
12
-
The above steps 1-11 are repeated for different MCS and PS combinations as per table 8.1.1.3, 8.1.1.4 of Subclause 8.1.1, table 9.3.2.1.1 of Subclause 9.3, 3GPP TS 44.060, i.e.
UAS-10 switching to UAS-8, SS verifies MCS is UAS-7 in step 7 and step 10
UAS-9 switching to UAS-8, SS verifies MCS is MCS-6 in step 7 and step 10
UAS-7 switching to UAS-11, SS verifies MCS is UAS-10 in step 7 and step 10
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
58c.3 Downlink EGPRS2 TBF
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
58c.3.1 Void
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
58c.3.2 Void
|
58c.3.2a Acknowledged Mode/ Downlink TBF/ Split RLC Data Block, in EGPRS2A
58.3.2a.1 Conformance requirements
1. Each RLC endpoint receiver shall have an associated receive state array V(N). V(N) is an array of SNS elements indicating the receive status of WS RLC data blocks that are supposed to follow the block BSN=V(Q)-1. The array is indexed relative to the receive window state variable V(Q) modulo SNS. When an RLC data block is received with BSN within the receive window, the corresponding element in V(N) is set to the value RECEIVE
2. If the RLC data block is split over two radio blocks, the element shall be set to the value RECEIVED if and only if both radio blocks have been received.
3. The elements in V(N) shall be set to the value INVALID at the beginning of each TBF. During the TBF, an element in V(N) that falls outside the receive window, shall be set to the value INVALID.
References
3GPP TS 44.060, subclause 9.1.7
58.3.2a.2 Test purpose
To verify that in case an RLC data block is split over two radio blocks:
1. When an RLC data block is received with BSN within the active window i.e. such that [V(Q) <=BSN < V(Q) + WS] modulo SNS, the corresponding element in V(N) is set to the value RECEIVED (the RLC data block has passed FCS).
2. The corresponding V(N) element shall not be marked as RECEIVED if any of the two radio blocks is not received.
3. The corresponding V(N) element shall be marked as RECEIVED if both of the radio blocks are received.
58.3.2a.3 Method of test
Initial Conditions
System Simulator:
1 cell with EGPRS support, default setting,
Mobile Station:
The MS is EGPRS updated with a P-TMSI allocated, SPLIT PG CYCLE negotiated and the test PDP Context2 activated.
Specific PICS Statements
-
PIXIT Statements
-
Test Procedure
The SS establishes a downlink EGPRS TBF.
The SS sends a RLC data block n > N, n<WS using DAS-10. The SS sends the first part of a spitted RLC data block using DAS-7, with BSN=N (N< window size), SPB='10'B, and polls for the EGPRS PACKET DOWNLINK ACK/NACK message from the MS. The MS shall respond with an EGPRS PACKET DOWNLINK ACK/NACK message indicating the block BSN=N is not received.
The SS then sends the second part of the spitted RLC block with the same BSN=N (N<WS), SPB='11' using DAS-7, and polls for the EGPRS PACKET DOWNLIK ACK/NACK message from the MS. The MS shall respond with an EGPRS PACKET DOWNLINK ACK/NACK message with the BSN=N acknowledged.
Maximum Duration of Test
30 minutes.
Expected Sequence
Step
Direction
Message
Comments
1
{Downlink TBF establishment}
Acknowledged Mode
EGPRS2 Window Size: arbitrarily chosen
2
SS -> MS
EGPRS DOWNLINK RLC DATA BLOCK
With DAS-10, BSN=6, RRBP = '00'B
3
MS -> SS
EGPRS PACKET DOWNLINK ACK/NACK
The SS verifies that RBB is set to 0 for RLC data blocks with BSN = 0, 1, 2, 3, 4 and 5 and RBB is set to 1 for BSN=6.
4
SS -> MS
EGPRS DOWNLINK RLC DATA BLOCK
With DAS-7, BSN starts from 0
ES/P = '00'B, SPB='10'B
5
Repeat step 4 until BSN = 3
6
SS -> MS
EGPRS DOWNLINK RLC DATA BLOCK
With DAS-7
BSN = 5, ES/P = '01'B, RRBP = '00'B,SPB='11'B
7
MS -> SS
EGPRS PACKET DOWNLINK ACK/NACK
The SS verifies that the bits in RBB for BSN=0, 1, 2, 3, 4, 5 are set to '0'B.
8
SS -> MS
EGPRS DOWNLINK RLC DATA BLOCK
With DAS-7
BSN = 4, SPB = '10'B, ES/P = '01'B, RRBP = '00'B
9
MS -> SS
EGPRS PACKET DOWNLINK ACK/NACK
The SS verifies that the bit for BSN=4 in RBB is set to '0'B.
10
SS -> MS
EGPRS DOWNLINK RLC DATA BLOCK
With DAS-7
BSN = 4, SPB = '11'B, ES/P = '01'B, RRBP = '00'B
11
MS -> SS
EGPRS PACKET DOWNLINK ACK/NACK
The SS verifies that the bit for BSN=4 in RBB is set to '1'B.
{Completion of downlink data transfer}
58c.3.3a Acknowledged Mode / Downlink TBF / Decoding of Coding Schemes, in EGPRS2-A
58c.3.3a.1 Conformance requirements
1. In EGPRS TBF mode, the transfer of RLC Data Blocks in the acknowledged RLC/MAC mode can be controlled by a selective type I ARQ mechanism, or by type II hybrid ARQ (Incremental Redundancy: IR) mechanism, coupled with the numbering of the RLC Data Blocks within one Temporary Block Flow.
2. According to the link quality, an initial Modulation and Coding Scheme (MCS) is selected for an RLC block (see note). For the retransmissions, the same or another MCS from the same family of MCSs can be selected.
3. The selection of MCS is controlled by the network.
4. In EGPRS header, the Coding and Puncturing Scheme indicator field is used to indicate the kind of channel coding and puncturing used for data blocks.(see 3GPP TS 05.03)
References
3GPP TS 44.060, subclauses 9.3.2.1 and 10.4.8.a.
58c.3.3a.2 Test purpose
To verify that the mobile station correctly decode RLC data blocks sent using different coding schemes (DAS-5 to DAS-12).
58c.3.3a.3 Method of test
Initial Conditions
System Simulator:
1 cell with EGPRS support, default setting,
Mobile Station:
The MS is EGPRS updated with a P-TMSI allocated, SPLIT PG CYCLE negotiated and the test PDP Context2 activated.
Specific PICS Statements
-
PIXIT Statements
-
Test Procedure
The SS establishes a downlink EGPRS2-A TBF setting EGPRS window size to 256, FANR disabled and in BTTI mode.
The SS establishes a Downlink EGPRS TBF.
The send SS sends a few RLC data blocks in different coding schemes and asks for an acknowledgement from the MS.
The MS shall correctly acknowledge all the received data blocks.
Maximum Duration of Test
10 minutes.
Expected Sequence
Step
Direction
Message
Comments
1
{Downlink TBF establishment}
Acknowledged Mode
EGPRS Window Size: 256. BTTI configuration Mode, FANR disabled, EGPRS Level set to EGPRS2-A, EGPRS Window Size: arbitrarily chosen
2
SS -> MS
EGPRS DOWNLINK RLC DATA BLOCK
With DAS-5, BSN=0, CES/P = '000’B
3
Repeat step 2 using DAS-6 till DAS-7. The BSNs of the data blocks shall be sequential.
Repeat step 2 using DAS-8 till DAS-10. The BSNs of the data blocks shall be sequential.
Repeat step 2 using DAS-11 till DAS-12. The BSNs of the data blocks shall be sequential.
The last block transmitted should be DAS-12 with BSN=12, 13, and 14 for the last block transmitted.
CES/P = '001'B and RRBP='00'B is set in the header of last RLC Data Block sent with BSN=12, 13, and 14.
4
MS -> SS
EGPRS PACKET DOWNLINK ACK/NACK
Received on the corresponding PACCH.
The SS verifies that the MS acknowledges all the received RLC data blocks.
SSN shall be equal to 16
Specific message contents
None.
58c.3.4a Acknowledged Mode / Downlink TBF / Retransmission / Padding in EGPRS2-A
58c.3.4a.1 Conformance requirements
According to the link quality, an initial Modulation and Coding Scheme (MCS) is selected for an RLC block (see note). For the retransmissions, the same or another MCS from the same family of MCSs may be selected. E.g. if MCS-7 is selected for the first transmission of an RLC block, any MCS of the family B may be used for the retransmissions. Further, RLC data blocks initially transmitted with MCS-4, MCS-5, MCS-6, MCS-7, MCS-8 or MCS-9, may be retransmitted with MCS-1, MCS-2 or MCS-3 as appropriate, by sending the different parts of the RLC data block in different radio blocks. In this case, the split block field in the header shall be set to indicate that the RLC data block is split, and the order of the two parts. For blocks initially transmitted with MCS-8 which are retransmitted using MCS-6 or MCS-3, padding of the first six octets shall be applied before each RLC data block, and the CPS field shall be set to indicate that this has been done (see an informative example in annex J).
References
3GPP TS 44.060, subclause 9.3.2.1
58c.3.4a.2 Test purpose
To verify that the MS correctly decodes the CPS field of EGPRS Downlink RLC Data Block header.
To verify that the MS correctly decodes a retransmitted data block this contains first six octets of padding.
58c.3.4a.3 Method of test
Initial Conditions
System Simulator:
1 cell with EGPRS support, default setting,
Mobile Station:
The MS is EGPRS updated with a P-TMSI allocated, SPLIT PG CYCLE negotiated and the test PDP context2 activated.
Specific PICS Statements
- EGPRS Multislotclass (TSPC_Type_EGPRS_Multislot_ClassX where X = 1...45)
PIXIT Statements
-
Test Procedure
The SS initiates the establishment of a downlink EGPRS2-A TBF, setting window size to the largest value WS corresponding the number of timeslots assigned to TBF.
The SS sends two EGPRS2-A RLC radio blocks with BSN=0 BSN=1 and BSN=4 BSN=5 using DAS-9. In the last block FBI is set to 1 and the MS is polled for Acknowledgement.
The MS shall send a EGPRS Packet Downlink Ack/Nack type 2 message acknowledging BSNs 0,1,4 and 5 and negatively acknowledging BSN=2 and BSN=3. SS verifies that FAI is set to 0.
The SS sends EGPRS RLC data block with BSN=2 using DAS-6, setting first 6 octets of the data block to padding, and setting CPS field to indicate the same and polls the MS for acknowledgement.
The MS shall send EGPRS Packet Downlink Ack/Nack type 2 message acknowledging BSNs 0,1,2,4 and 5 and negatively acknowledging BSN=3. SS verifies that FAI is set to 0.
The SS sends first part of BSN=3 using MCS-3 with first six octets of the data block set to padding and polls the MS for acknowledgement. CPS is set correctly in the data block header to indicate that the block is first part of split block and that the data block is padded.
The MS shall send EGPRS Packet Downlink Ack/Nack message acknowledging BSNs 0,1,2,4 and 5 and negatively acknowledging BSN=3. SS verifies that FAI is set to 0.
The SS sends second part of BSN=3 using MCS-3 and polls the MS for acknowledgement. CPS is set correctly in the data block header to indicate that the block is second part of split block and that the data block is not padded.
The MS shall send EGPRS Packet Downlink Ack/Nack Type 2 message acknowledging BSNs 0 to 5. SS verifies that FAI is set to 1.
Maximum Duration of Test
5 minutes.
Expected Sequence
Step
Direction
Message
Comments
1
{Downlink TBF establishment}
Acknowledged Mode, EGPRS level = 01
EGPRS Window Size = Maximum for the MS according to the number of timeslots assigned to TBF.
2
SS -> MS
EGPRS DOWNLINK RLC DATA BLOCK
Using DAS-9
Sent on the assigned PDTCH, with BSN = 0 and BSN=1.
3
SS -> MS
EGPRS DOWNLINK RLC DATA BLOCK
Using DAS-9
Sent on the assigned PDTCH, with BSN = 4 and BSN=5.
FBI is set to 1.
MS is polled for FPB
4
MS -> SS
EGPRS PACKET DOWNLINK ACK/NACK TYPE2
Received on PACCH of the assigned PDTCH.
SS verifies that BSN 0, 1, 4 and 5 are acknowledged, BSN 2 and 3 are not acknowledged and FAI=0
5
SS -> MS
EGPRS DOWNLINK RLC DATA BLOCK
Using DAS-6
Sent on the assigned PDTCH, with BSN = 2. First six octets of the data block shall be padding octets. CPS field shall indicate the same. MS is polled for FPB.
6
MS -> SS
EGPRS PACKET DOWNLINK ACK/NACK TYPE2
Received on PACCH of the assigned PDTCH.
SS verifies that BSN 0, 1, 2, 4 and 5 are acknowledged, BSN 3 is not acknowledged and FAI=0
7
SS -> MS
EGPRS DOWNLINK RLC DATA BLOCK
Using MCS-3
Sent on the assigned PDTCH, with BSN = 3. First 6 octets of the data block shall be padding octets.
CPS field shall indicate that the data block is first part of split block and the data block is padded.
MS is polled for FPB.
8
MS -> SS
EGPRS PACKET DOWNLINK ACK/NACK TYPE2
Received on PACCH of the assigned PDTCH.
SS verifies that BSN 0, 1, 2, 4 and 5 are acknowledged , BSN 3 is not acknowledged and FAI=0
9
SS -> MS
EGPRS DOWNLINK RLC DATA BLOCK
Using MCS-3
Sent on the assigned PDTCH, with BSN = 3.
CPS field shall indicate that the data block is second part of split block and the data block is not padded.
MS is polled for FPB.
10
MS -> SS
EGPRS PACKET DOWNLINK ACK/NACK TYPE2
Received on PACCH of the assigned PDTCH.
SS verifies that BSN 0, 1, 2, 3, 4 and 5 are acknowledged and FAI=1
Specific message contents
None.
58c.3.5a Acknowledged Mode / Downlink TBF / First Partial Bitmap and Next Partial Bitmap in EGPRS2-A
58c.3.5a.1 Conformance requirements
1. In EGPRS downlink TBFs, an additional poll bit is added to the S/P field in every downlink RLC block so that the network can request the following:
- First Partial Bitmap (FPB) segment with SSN = (V(Q) + 1) mod 2048 where SSN denotes the Starting Sequence Number.
- Next Partial Bitmap (NPB) segment with SSN = (PBSN + 1) mod 2048 where PBSN denotes a Partial Bitmap Sequence Number variable stored at the receiver.
2. SSN is determined by the receiver as a function of ES/P, V(Q) and PBSN. The FPB and NPB are specific instances of the EGPRS Ack/Nack Description Information Element within the EGPRS PACKET DOWNLINK ACK/NACK message, EGPRS PACKET DOWNLINK ACK/NACK TYPE 2 message. The mobile station shall respond to ES/P field according to table 9.1.8.2.1.1 (non-MBMS). For a mobile station with one or more downlink TBFs using EGPRS2, the mobile station shall send the EGPRS PACKET DOWNLINK ACK/NACK TYPE 2 message. Otherwise, the mobile station shall send the EGPRS PACKET DOWNLINK ACK/NACK message.
3. Based on PBSN, V(Q) and the ES/P field set by the network, SSN and PBSN shall be determined according to table 9.1.8.2.2.1. For EGPRS2, SSN and PBSN shall be determined based on PBSN, V(Q) and CES/P fields according to table 9.1.8.2.2.2. For EGPRS2 the Combined EGPRS Supplementary/Polling field describes the feedback request and specifies a single uplink block in which the mobile station shall transmit a PACKET CONTROL ACKNOWLEDGEMENT message, a PACCH block see table 9.1.8.2.1.3. The single uplink block is defined by a delay relative to the first TDMA frame (N) of the downlink block containing the CES/P value. If ordered to send a EGPRS PACKET DOWNLINK ACK/NACK message or EGPRS PACKET DOWNLINK ACK/NACK TYPE 2 message, a mobile station with one or more downlink TBFs using EGPRS2 shall send the EGPRS PACKET DOWNLINK ACK/NACK TYPE 2 message. Otherwise, the mobile station shall send the EGPRS PACKET DOWNLINK ACK/NACK message.
References
3GPP TS 44.060, sub clause 9.1.8.2.
58c.3.5a.2 Test purpose
To verify the correct generation of SSN and RB in the First Partial Bitmap.
To verify the correct generation of SSN and RB in the Next Partial Bitmap.
58c.3.5a.3 Method of test
Initial Conditions
System Simulator:
1 cell with EGPRS support, default setting,
Mobile Station:
The MS is EGPRS updated with a P-TMSI allocated, SPLIT PG CYCLE negotiated and the test PDP Context2 activated.
Specific PICS Statements
-
PIXIT Statements
-
Test Procedure
The SS establishes a downlink EGPRS2-A TBF setting EGPRS window size to 256, FANR disabled and in BTTI mode.
The SS sends a series of RLC data blocks with BSN=0, 1...5, CES/P = '000'B using DAS-7 coding scheme.
The SS sends a RLC data block with BSN=21, CES/P = '001'B and using DAS7. MS responds back with EGPRS PACKET DOWNLINK ACK/NACK TYPE2 message with CQR and FPB within radio period (N+8 or N+9) mode 2715648.
The SS sends a RLC data block with BSN=32, CES/P = '010'B and using DAS-5. MS responds back with EGPRS PACKET DOWNLINK ACK/NACK TYPE2 message with CQR and FPB within radio period (N+13) mode 2715648.
The SS sends a RLC data block with BSN=22, CES/P = '011'B and using DAS-6. MS doesn’t responds back with EGPRS PACKET DOWNLINK ACK/NACK TYPE2 message.
The SS sends a RLC data block with BSN=24, CES/P = '100'B and using DAS-5. MS doesn’t responds back with EGPRS PACKET DOWNLINK ACK/NACK TYPE2 message.
The SS sends a RLC data block with BSN=26, CES/P = '101'B and using DAS-7. MS responds back with EGPRS PACKET DOWNLINK ACK/NACK TYPE2 message with CQR and NPB within radio period (N+8 or N+9) mode 2715648.
The SS sends a RLC data block with BSN=29, CES/P = '110'B and using DAS-5. MS responds back with EGPRS PACKET DOWNLINK ACK/NACK TYPE2 message with CQR and NPB within radio period (N+13) mode 2715648.
The SS sends a RLC data block with BSN=31, CES/P = '111'B and using DAS-5. MS responds back with EGPRS PACKET DOWNLINK ACK/NACK TYPE2 message with CQR and NPB within radio period (N+8 or N+9) mode 2715648.
The SS sends RLC data blocks with BSN=256, 116,241. CES/P = '000'B using DAS-5 coding scheme
The SS sends a RLC data block with BSN=237, CES/P = '111'B and using DAS-5. MS responds back with EGPRS PACKET DOWNLINK ACK/NACK TYPE2 message with no channel quality report and NPB within radio period (N+8 or N+9) mode 2715648.
Maximum Duration of Test
10 minutes.
Expected Sequence
Step
Direction
Message
Comments
1
{Downlink TBF establishment}
Acknowledged Mode
EGPRS Window Size: 256. BTTI configuration Mode, FANR disabled, EGPRS Level set to EGPRS2-A,
2
SS -> MS
EGPRS DOWNLINK RLC DATA BLOCK
With DAS-7,BSN = N, CES/P = '000’B
3
Repeat step 2 with N = 0..5
4
SS -> MS
EGPRS DOWNLINK RLC DATA BLOCK
With DAS7,BSN = 21, CES/P = '001'B
5
MS -> SS
EGPRS PACKET DOWNLINK ACK/NACK TYPE2
The SS verifies that the EGPRS Ack/Nack description IE contains the correct SSN and RB in the message.
Verify that BOW is set EGPRS PACKET DOWNLINK ACK/NACK TYPE 2 message contains Channel Quality Report(s) and if there is enough room left in RLC/MAC block, FPB within the radio period (N+8 or N+9) mode 2715648.
6
SS -> MS
EGPRS DOWNLINK RLC DATA BLOCK
With DAS-5, BSN = 32, CES/P = '010'B using TFI allocated in step 1.
7
MS -> SS
EGPRS PACKET DOWNLINK ACK/NACK TYPE2
The SS verifies that the EGPRS Ack/Nack description IE contains the correct SSN and RB in the message indicating all the unacknowledged blocks.
Verify that BOW is set EGPRS PACKET DOWNLINK ACK/NACK TYPE 2 message contains Channel Quality Report(s) and if there is enough room left in RLC/MAC block, FPB within the radio period (N+13) mode 2715648.
8
SS -> MS
EGPRS DOWNLINK RLC DATA BLOCK
With DAS-6, BSN = 22, CES/P = '011'B, using TFI allocated in step 1.
9
SS
The SS verifies that MS does not send any EGPRS PACKET DOWNLINK ACK/NACk TYPE2 message.
10
SS -> MS
EGPRS DOWNLINK RLC DATA BLOCK
With DAS-5, BSN = 24, CES/P = '100'B, using TFI allocated in step 1.
11
SS
The SS verifies that MS does not send any EGPRS PACKET DOWNLINK ACK/NACK TYPE2 message.
12
SS -> MS
EGPRS DOWNLINK RLC DATA BLOCK
With DAS-7, BSN = 26, CES/P = '101'B, using TFI allocated in step 1.
13
MS -> SS
EGPRS PACKET DOWNLINK ACK/NACK TYPE2
The SS verifies that the EGPRS Ack/Nack description IE contains the correct SSN and RB in the message indicating all the unacknowledged blocks.
Verify that BOW is set EGPRS PACKET DOWNLINK ACK/NACK TYPE 2 message contains Channel Quality Report(s) and if there is enough room left in RLC/MAC block, NPB within the radio period (N+8 or N+9) mode 2715648.
13
SS -> MS
EGPRS DOWNLINK RLC DATA BLOCK
With DAS-5
BSN = 29, CES/P = '110'B, using TFI allocated in step 1.
14
MS -> SS
EGPRS PACKET DOWNLINK ACK/NACK TYPE2
The SS verifies that the EGPRS Ack/Nack description IE contains the correct SSN and RB in the message indicating all the unacknowledged blocks.
Verify that BOW is set. EGPRS PACKET DOWNLINK ACK/NACK TYPE 2 message contains Channel Quality Report(s) and if there is enough room left in RLC/MAC block NPB within the radio period (N+13) mode 2715648.
15
SS -> MS
EGPRS DOWNLINK RLC DATA BLOCK
With DAS-5
BSN = 31, CES/P = '111'B, using TFI allocated in step 1.
16
MS -> SS
EGPRS PACKET DOWNLINK ACK/NACK TYPE2
The SS verifies that the EGPRS Ack/Nack description IE contains the correct SSN and RB in the message indicating all the unacknowledged blocks.
Verify that BOW is set. EGPRS PACKET DOWNLINK ACK/NACK TYPE 2 message contains Channel Quality Report(s) and if there is enough room left in RLC/MAC block NPB within the radio period (N+8 or N+9) mode 2715648.
17
SS -> MS
EGPRS DOWNLINK RLC DATA BLOCK
With DAS-5
BSN = 256, CES/P = '000'B, using TFI allocated in step 1.
18
SS -> MS
EGPRS DOWNLINK RLC DATA BLOCK
With DAS-5
BSN = 116, CES/P = '000'B, using TFI allocated in step 1.
19
SS -> MS
EGPRS DOWNLINK RLC DATA BLOCK
With DAS-5
BSN = 241, CES/P = '000'B, using TFI allocated in step 1.
21
SS -> MS
EGPRS DOWNLINK RLC DATA BLOCK
With DAS-5
BSN = 237, CES/P = '111'B, using TFI allocated in step 1.
22
MS -> SS
EGPRS PACKET DOWNLINK ACK/NACK TYPE2
The SS verifies that the EGPRS Ack/Nack description IE contains the correct SSN and RB in the message indicating all the unacknowledged blocks.
Verify that BOW is set. EGPRS PACKET DOWNLINK ACK/NACK TYPE 2 message does not contains Channel Quality Report(s) NPB within the radio period (N+8 or N+9) mode 2715648.
Specific message contents
None.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
58d EFTA
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
58d.1 Concurrent EFTA TBF
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
58d.1.1 EFTA / Extended Dynamic Allocation/Concurrent TBF
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
58d.1.1.1 Conformance Requirement
|
For a mobile station with an uplink TBF for which EFTA is used transmissions shall be performed on the uplink PDCHs or PDCH-pairs allocated by the USF as specified in Annex N. In case the mobile station also has one or more concurrent downlink TBF(s), but does not have enough RLC/MAC blocks ready for transmission to fully utilize the total number of allocated resources for uplink radio block transmission during the corresponding radio block period(s), then it shall immediately begin monitoring its assigned downlink PDCHs or PDCH-pairs after transmitting its last available RLC/MAC block taking into account the switching requirements of its multislot class (see 3GPP TS 45.002).
References
3GPP TS 44.060, subclause 8.1.1.2.1
A mobile station with an uplink TBF operating in BTTI configuration for which EFTA is used shall perform transmissions on a subset of the uplink PDCHs allocated by the USF. If the mobile station has P RLC/MAC blocks ready for transmission, then this subset is defined as the first P number of the allocated uplink PDCHs arranged according to the specific timeslot numbers order as specified in Table N.1 below. Tra or Trb, whichever is applicable, is the switching time from transmission to reception (see 3GPP TS 45.002).
Table N.1: Uplink timeslots transmission order for EFTA
Lowest Numbered Downlink Timeslot the MS Needs to Monitor
Tra or Trb, whichever is applicable
0
1
2
TN0
4,3,2,1,0,5,6,7
3,2,1,0,4,5,6,7
2,1,0,3,4,5,6,7
TN1
5,4,3,2,1,0,6,7
4,3,2,1,0,5,6,7
3,2,1,0,4,5,6,7
TN2
6,5,4,3,2,1,0,7
5,4,3,2,1,0,6,7
4,3,2,1,0,5,6,7
TN3
7,6,5,4,3,2,1,0
6,5,4,3,2,1,0,7
5,4,3,2,1,0,6,7
TN4
7,6,5,4,3,2,1,0
7,6,5,4,3,2,1,0
6,5,4,3,2,1,0,7
TN5
7,6,5,4,3,2,1,0
7,6,5,4,3,2,1,0
7,6,5,4,3,2,1,0
TN6
7,6,5,4,3,2,1,0
7,6,5,4,3,2,1,0
7,6,5,4,3,2,1,0
TN7
7,6,5,4,3,2,1,0
7,6,5,4,3,2,1,0
7,6,5,4,3,2,1,0
A mobile station with an uplink TBF operating in RTTI configuration for which EFTA is used shall perform transmissions on a subset of the uplink PDCH-pairs allocated by the USF in the same manner as specified above. For this case the specific timeslot number order shall be seen as indicating the lowest numbered timeslot of the uplink PDCH-pair.
NOTE: The above described rule determine the subset of the allocated uplink PDCHs or PDCH-pairs on which uplink transmissions shall be performed when EFTA is used. This procedure however, does not define which uplink PDCHs or PDCH-pairs that shall be allocated by the USF. Nor does the procedure define the individual ordering of any transmitted RLC/MAC blocks on these resources, which shall remain the same as for the case when EFTA is not used.
A mobile station with an uplink TBF for which EFTA is used shall perform the transmission of any uplink PACCH message allocated via the polling mechanism (see sub-clauses 10.4.4b and 10.4.5) on the first of the assigned uplink PDCHs or PDCH-pairs arranged according to the specific timeslot number order as described by Table N.1 above, regardless of which resources are allocated by the USF. The switching time Tra or Trb shall be interpreted according to its value at the time the poll was received.
References
3GPP TS 44.060, Annex N
References
3GPP TS 45.002, Annex B.1 and B.5
3GPP TS 45.002 Table 6.4.2.2.1
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
58d.1.1.2 Test Purposes
|
The test purpose is to verify that the EFTA capable MS indicating support for an Alternative EFTA Multislot Class supports as many downlink timeslots per TDMA frame as indicated with the multislot classes. Especially it’s verified that the Sum parameter is not used in the conditions where Sum is not applicable according to TS 45.002 Annex B.5.
1. Ttb, the minimum number of slots allowed between the end of the previous transmit or receive TS and the next transmit TS when measurement is to be performed for type 1 MS.
2. Tra, the minimum number of slots allowed between the previous transmit or receive TS and the next receive TS when measurement is to be performed for type 1 MS.
3. The maximum number of Rx and Tx supported.
4. Check that MS transmit according to 44.060 Table N.1.
5. MS shall if uplink data is ongoing then for these overlapping instances prioritize uplink radio block transmission over attempting to read downlink radio blocks.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
58d.1.1.3 Method of Test
|
Initial Conditions
System Simulator:
1 cell with EGPRS support, default setting,
Mobile Station:
The MS is EGPRS updated with a P-TMSI allocated, PDP Context 2 activated.
Specific PICS Statements
-
PIXIT Statements
-
Test Procedure
Establish a concurrent uplink downlink TBF using max number of Tx and Rx timeslot according to multislot class and alternative EFTA multislot class, EDA used, USF_GRANULARITY=4 blocks, MCS-5.
Transmit on all downlink timeslots and check that all data is Ack’d correctly.
Transmit on all uplink timeslots while downlink transmission on all timeslot also is ongoing, check that the uplink always gets transmitted correctly and that only overlapping downlink data is Nacked.
Send 2 RLC blocks on uplink assign USF on lowest TN, while downlink transmission on all timeslots also is ongoing, check that uplink is transmitted according to 44.060 Table N.1.
Maximum Duration of Test
5 minutes
Expected Sequence
Step
Direction
Message
Comments
1
SS -> MS
{Downlink TBF establishment}
Acknowledged Mode. SS Commands MS to use mobile coding scheme MCS-5.
Max number of timeslots are assigned according to MS multislot class (TS 45.002 Annex B.1) and Alternative EFTA multislot class (TS 45.002 Annex B.5):
- TN1 to TNx.
2
SS -> MS
30 RLC data blocks
SS sends data, last block is polling.
3
MS -> SS
EGPRS PACKET DOWNLINK ACK/NACK
Sent on PACCH. Check all blocks Acked ok.
4
SS -> MS
PACKET UPLINK ASSIGNMENT
Sent on downlink PACCH.
The uplink TBF is assigned.
MCS-5, EDA used, USF_GRANULARITY=4.
Max number of timeslots are assigned according to MS multislot class (TS 45.002 Annex B.1) and Alternative EFTA multislot class (TS 45.002 Annex B.5):
- TN1 to TNx.
5
SS -> MS
30 RLC data blocks
SS sends data, last block is polling.
6
MS -> SS
EGPRS PACKET DOWNLINK ACK/NACK
Sent on PACCH.
SS checks that all data blocks are Acked.
7
SS <-> MS
{Downlink data transfer},{Uplink data transfer}
2000 octets of data in downlink and SS checks that Acked/Nack is according to EFTA requirements:
• Downlink packets are Nacked if simultaneous as uplink.
• Downlink packets are Nacked related to Ttb and Tra.
1000 octets of data in uplink and SS checks that all data blocks are Acked.
Downlink and uplink data transfers are simultaneous.
8
SS -> MS
30 RLC data blocks
SS sends data, last block is polling.
9
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
Assigned USF on PACCH on lowest TN.
10
MS -> SS
2 RLC data blocks
Trigger 2 UL data blocks while SS sends data on all assigned downlink timeslots in step 9.
SS checks that MS send the data according to TS 44.060 Table N.1.
11
MS -> SS
EGPRS PACKET DOWNLINK ACK/NACK
Sent on PACCH.
12
SS -> MS
PACKET UPLINK ACK/NACK
SS acknowledges receiving all RLC data blocks.
Final Ack Indicator = '1' containing valid RRBP. Sent on the PACCH of the assigned PDCH.
13
MS -> SS
PACKET CONTROL ACKNOWLEDGEMENT
Received on the block specified by RRBP on PACCH of the assigned PDCH.
Specific Message Contents
None.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
58d.1.2 EFTA / Acknowledge mode/ Concurrent TBF/ pre-emptive retransmission
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
58d.1.2.1 Conformance Requirement
|
When Enhanced Flexible Timeslot Assignment, EFTA, is used, and the applicable conditions for pre-emptive retransmission are true, the mobile station shall not prioritize uplink radio block transmission over attempting to read downlink radio blocks.
References
3GPP TS 44.060 subclause 9.1.3.2.1
For a mobile station with an uplink TBF for which EFTA is used transmissions shall be performed on the uplink PDCHs or PDCH-pairs allocated by the USF as specified in Annex N. In case the mobile station also has one or more concurrent downlink TBF(s), but does not have enough RLC/MAC blocks ready for transmission to fully utilize the total number of allocated resources for uplink radio block transmission during the corresponding radio block period(s), then it shall immediately begin monitoring its assigned downlink PDCHs or PDCH-pairs after transmitting its last available RLC/MAC block taking into account the switching requirements of its multislot class (see 3GPP TS 45.002).
References
3GPP TS 44.060, subclause 8.1.1.2.1
References
3GPP TS 45.002, Annex B.1 and B.5
3GPP TS 45.002 Table 6.4.2.2.1
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
58d.1.2.2 Test Purposes
|
The test purpose is to verify that the EFTA capable MS:
1. When the pre-emptive retransmission bit is set to ‘1’, is not retransmitting RLC data blocks whose corresponding element in V(B) is set to PENDING_ACK if not able to transmit one UL radio block and read all assigned DL timeslots in the same TTI.;
2. When the pre-emptive retransmission bit is set to ‘1’, is retransmitting RLC data blocks whose corresponding element in V(B) is set to PENDING_ACK if able to transmit one UL radio block and read all assigned DL timeslots in the same TTI.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
58d.1.2.3 Method of Test
|
Initial Conditions
System Simulator:
1 cell with EGPRS support, default setting,
Mobile Station:
The MS is EGPRS updated with a P-TMSI allocated, PDP Context 2 activated.
Specific PICS Statements
TSPC_Type_EGPRS_Multislot_ClassX (where X = 40..45)
TSPC_EFTA_Alt_Multislot_Class_X (where X= 1..3)
PIXIT Statements
-
Test Procedure
Establish a concurrent uplink downlink TBF using max number of Tx and Rx allowed timeslots according to multislot class and alternative EFTA multislot class for K=1 (DL with minimum 6 TS) and for K=2 (5 DL TS should be used), EDA used, USF_GRANULARITY=1 blocks, MCS-5.
Transmit on all downlink timeslots.
Send 30 RLC block on uplink while downlink transmission on all timeslot also is ongoing.15 RLC blocks neither acked nor nacked by SS.
Check if K=1 that MS not tries to resend RLC blocks while downlink ongoing.
Check if K=2 that MS resend RLC blocks while downlink ongoing.
Maximum Duration of Test
5 minutes
Expected Sequence
The test sequence is repeated for K = 1: DL using max number of TS allowed, minimum 6 TS, K=2: DL using 5 TS.
Step
Direction
Message
Comments
1
SS -> MS
{Downlink TBF establishment}
Acknowledged Mode. SS Commands MS to use mobile coding scheme MCS-5.
timeslots are assigned for K=1:
according to MS multislot class (TS 45.002 Annex B.1) and Alternative EFTA multislot class (TS 45.002 Annex B.5)
for K=2:
5 TS is assigned:
- TN1 to TNx
2
SS -> MS
PACKET UPLINK ASSIGNMENT
Sent on downlink PACCH.
The uplink TBF is assigned.
MCS-5, EDA used, USF_GRANULARITY=1
Max number of timeslots are assigned according to MS multislot class (TS 45.002 Annex B.1) and Alternative EFTA multislot class (TS 45.002 Annex B.5) :
- TN1 to TNx
3
SS -> MS
{Downlink data transfer}
2000 octets of data in downlink. Downlink data transfer are simultaneous with steps 4 to step 6
4
MS -> SS
30 RLC data blocks
Trigger 30 UL data blocks while SS sends data on all assigned downlink timeslots in step 3.
.
5
SS -> MS
PACKET UPLINK ACK/NACK
SS acknowledges 15 RLC data blocks, the other 15 RLC data blocks SS neither Ack nor Nack.
PRE_EMPTIVE_TRANSMISSION bit in PUAN message set to ‘1’.
6a
SS
For K=1:
SS checks that MS does not try to resend RLC blocks while downlink data transfer ongoing.
Downlink transfer ends
6b
MS -> SS
15 RLC data blocks
For K=2
SS checks that MS resends outstanding Pending Ack blocks while downlink data transfer ongoing.
Downlink transfer ends
7
SS -> MS
PACKET UPLINK ACK/NACK
SS sets Final Ack Indicator = '1' containing valid RRBP. Sent on the PACCH of the assigned PDCH.
8
MS -> SS
PACKET CONTROL ACKNOWLEDGEMENT
Received on the block specified by RRBP on PACCH of the assigned PDCH.
Specific Message Contents
None.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
58d.1.3 EFTA / Concurrent TBF / PAN Polling
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
58d.1.3.1 Conformance Requirement
|
In case EFTA is used at the time the CES/P field is received, the mobile station shall transmit the uplink radio block according to the uplink radio block transmission order as described in Annex N regardless of the timeslot or PDCH pair where the block containing the CES/P field was received
References
3GPP TS 44.060, subclause 10.4.4b
A mobile station with an uplink TBF operating in BTTI configuration for which EFTA is used shall perform transmissions on a subset of the uplink PDCHs allocated by the USF. If the mobile station has P RLC/MAC blocks ready for transmission, then this subset is defined as the first P number of the allocated uplink PDCHs arranged according to the specific timeslot numbers order as specified in Table N.1 below. Tra or Trb, whichever is applicable, is the switching time from transmission to reception (see 3GPP TS 45.002).
Table N.1: Uplink timeslots transmission order for EFTA
Lowest Numbered Downlink Timeslot the MS Needs to Monitor
Tra or Trb, whichever is applicable
0
1
2
TN0
4,3,2,1,0,5,6,7
3,2,1,0,4,5,6,7
2,1,0,3,4,5,6,7
TN1
5,4,3,2,1,0,6,7
4,3,2,1,0,5,6,7
3,2,1,0,4,5,6,7
TN2
6,5,4,3,2,1,0,7
5,4,3,2,1,0,6,7
4,3,2,1,0,5,6,7
TN3
7,6,5,4,3,2,1,0
6,5,4,3,2,1,0,7
5,4,3,2,1,0,6,7
TN4
7,6,5,4,3,2,1,0
7,6,5,4,3,2,1,0
6,5,4,3,2,1,0,7
TN5
7,6,5,4,3,2,1,0
7,6,5,4,3,2,1,0
7,6,5,4,3,2,1,0
TN6
7,6,5,4,3,2,1,0
7,6,5,4,3,2,1,0
7,6,5,4,3,2,1,0
TN7
7,6,5,4,3,2,1,0
7,6,5,4,3,2,1,0
7,6,5,4,3,2,1,0
A mobile station with an uplink TBF operating in RTTI configuration for which EFTA is used shall perform transmissions on a subset of the uplink PDCH-pairs allocated by the USF in the same manner as specified above. For this case the specific timeslot number order shall be seen as indicating the lowest numbered timeslot of the uplink PDCH-pair.
NOTE: The above described rule determine the subset of the allocated uplink PDCHs or PDCH-pairs on which uplink transmissions shall be performed when EFTA is used. This procedure however, does not define which uplink PDCHs or PDCH-pairs that shall be allocated by the USF. Nor does the procedure define the individual ordering of any transmitted RLC/MAC blocks on these resources, which shall remain the same as for the case when EFTA is not used.
A mobile station with an uplink TBF for which EFTA is used shall perform the transmission of any uplink PACCH message allocated via the polling mechanism (see sub-clauses 10.4.4b and 10.4.5) on the first of the assigned uplink PDCHs or PDCH-pairs arranged according to the specific timeslot number order as described by Table N.1 above, regardless of which resources are allocated by the USF. The switching time Tra or Trb shall be interpreted according to its value at the time the poll was received.
References
3GPP TS 44.060, Annex N
For a mobile station with an uplink TBF for which EFTA is used transmissions shall be performed on the uplink PDCHs or PDCH-pairs allocated by the USF as specified in Annex N. In case the mobile station also has one or more concurrent downlink TBF(s), but does not have enough RLC/MAC blocks ready for transmission to fully utilize the total number of allocated resources for uplink radio block transmission during the corresponding radio block period(s), then it shall immediately begin monitoring its assigned downlink PDCHs or PDCH-pairs after transmitting its last available RLC/MAC block taking into account the switching requirements of its multislot class (see 3GPP TS 45.002).
References
3GPP TS 44.060, subclause 8.1.1.2.1
References
3GPP TS 45.002, Annex B.1 and B.5
3GPP TS 45.002 Table 6.4.2.2.1
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
58d.1.3.2 Test Purposes
|
The test purpose is to verify that the EFTA capable MS indicating support for an Alternative EFTA Multislot Class supports as many uplink and downlink timeslots per TDMA frame as indicated with the multislot classes. Especially it’s verified that the Sum parameter is not used in the conditions where Sum is not applicable according to TS 45.002 Annex B.5.
1. The maximum number of Rx and Tx supported.
2. MS is polled for a Piggy-back Ack/Nack with CES/P field. Check that MS transmit response according to 44.060 Table N.1.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
58d.1.3.3 Method of Test
|
Initial Conditions
System Simulator:
1 cell with EGPRS support, default setting,
Mobile Station:
The MS is EGPRS updated with a P-TMSI allocated, PDP Context 2 activated.
Specific PICS Statements
-
PIXIT Statements
-
Test Procedure
Establish a concurrent uplink downlink TBF using max number of Tx and Rx timeslot according to multislot class and alternative EFTA multislot class, EDA used, USF_GRANULARITY=4 blocks, MCS-5, RTTI and FANR configuration used.
Transmit on all uplink timeslots while downlink transmission on all timeslot also is ongoing, check that the uplink always gets transmitted correctly and that only overlapping downlink data is Nacked.
MS is polled for a Piggy-back Ack/nack on lowest TN, while downlink transmission on all timeslot also is ongoing, check that uplink response is transmitted according to 44.060 Table N.1.
Maximum Duration of Test
5 minutes
Expected Sequence
Step
Direction
Message
Comments
1
SS -> MS
{Downlink TBF establishment}
Acknowledged Mode. SS Commands MS to use mobile coding scheme MCS-5.
Max number of timeslots are assigned according to MS multislot class (TS 45.002 Annex B.1) and Alternative EFTA multislot class (TS 45.002 Annex B.5):
- TN1 to TNx:
RTTI and FANR activated.
2
SS -> MS
PACKET UPLINK ASSIGNMENT
Sent on downlink PACCH.
The uplink TBF is assigned.
MCS-5, EDA used, USF_GRANULARITY=1
Max number of timeslots are assigned according to MS multislot class (TS 45.002 Annex B.1) and Alternative EFTA multislot class (TS 45.002 Annex B.5) :
- TN1 to TNx
RTTI and FANR activated. BTTI USF.
3
SS <-> MS
{Downlink data transfer},{Uplink data transfer}
2000 octets of data in downlink and SS checks that Acked/Nack is according to EFTA requirements:
• Downlink packets are Nacked if simultaneous as uplink.
• Downlink packets are Nacked related to Ttb and Tra.
1000 octets of data in uplink and SS checks that all data blocks are Acked.
Downlink and uplink data transfers are simultaneous and also simultaneous with steps 4 to step 7.
4
SS -> MS
EGPRS DOWNLINK DATA BLOCK
Sent on assigned PDTCH on lowest TN.
TFI assigned to the MS.
CES/P = 011
Does not contain PAN field.
5
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
Assigned USF on PACCH on lowest TN.
6
MS -> SS
EGPRS UPLINK DATA BLOCK
Received on assigned PDTCH.
Received in reserved block allocated by CES/P at Step 4.
Contains PAN field
7
SS
SS checks MS sends the block including the PAN response according to TS 44.060 Table N.1.
Downlink and uplink transfer ends
8
SS -> MS
PACKET UPLINK ACK/NACK
SS sets Final Ack Indicator = '1' containing valid RRBP. Sent on the PACCH of the assigned PDCH.
9
MS -> SS
PACKET CONTROL ACKNOWLEDGEMENT
Received on the block specified by RRBP on PACCH of the assigned PDCH.
Specific Message Contents
None.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
58d.1.4 EFTA / Concurrent TBF / Polling
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
58d.1.4.1 Conformance Requirement
|
In case of a BTTI or an RTTI configuration when EFTA is used at the time the RRBP field is received, the mobile station shall transmit the uplink radio block according to the uplink radio block transmission order as described in Annex N regardless of the timeslot or PDCH-pair where the block containing the RRBP was received.
References
3GPP TS 44.060, subclause 10.4.5
A mobile station with an uplink TBF operating in BTTI configuration for which EFTA is used shall perform transmissions on a subset of the uplink PDCHs allocated by the USF. If the mobile station has P RLC/MAC blocks ready for transmission, then this subset is defined as the first P number of the allocated uplink PDCHs arranged according to the specific timeslot numbers order as specified in Table N.1 below. Tra or Trb, whichever is applicable, is the switching time from transmission to reception (see 3GPP TS 45.002).
Table N.1: Uplink timeslots transmission order for EFTA
Lowest Numbered Downlink Timeslot the MS Needs to Monitor
Tra or Trb, whichever is applicable
0
1
2
TN0
4,3,2,1,0,5,6,7
3,2,1,0,4,5,6,7
2,1,0,3,4,5,6,7
TN1
5,4,3,2,1,0,6,7
4,3,2,1,0,5,6,7
3,2,1,0,4,5,6,7
TN2
6,5,4,3,2,1,0,7
5,4,3,2,1,0,6,7
4,3,2,1,0,5,6,7
TN3
7,6,5,4,3,2,1,0
6,5,4,3,2,1,0,7
5,4,3,2,1,0,6,7
TN4
7,6,5,4,3,2,1,0
7,6,5,4,3,2,1,0
6,5,4,3,2,1,0,7
TN5
7,6,5,4,3,2,1,0
7,6,5,4,3,2,1,0
7,6,5,4,3,2,1,0
TN6
7,6,5,4,3,2,1,0
7,6,5,4,3,2,1,0
7,6,5,4,3,2,1,0
TN7
7,6,5,4,3,2,1,0
7,6,5,4,3,2,1,0
7,6,5,4,3,2,1,0
A mobile station with an uplink TBF operating in RTTI configuration for which EFTA is used shall perform transmissions on a subset of the uplink PDCH-pairs allocated by the USF in the same manner as specified above. For this case the specific timeslot number order shall be seen as indicating the lowest numbered timeslot of the uplink PDCH-pair.
NOTE: The above described rule determine the subset of the allocated uplink PDCHs or PDCH-pairs on which uplink transmissions shall be performed when EFTA is used. This procedure however, does not define which uplink PDCHs or PDCH-pairs that shall be allocated by the USF. Nor does the procedure define the individual ordering of any transmitted RLC/MAC blocks on these resources, which shall remain the same as for the case when EFTA is not used.
A mobile station with an uplink TBF for which EFTA is used shall perform the transmission of any uplink PACCH message allocated via the polling mechanism (see sub-clauses 10.4.4b and 10.4.5) on the first of the assigned uplink PDCHs or PDCH-pairs arranged according to the specific timeslot number order as described by Table N.1 above, regardless of which resources are allocated by the USF. The switching time Tra or Trb shall be interpreted according to its value at the time the poll was received.
References
3GPP TS 44.060, Annex N
References
3GPP TS 45.002, Annex B.1 and B.5
3GPP TS 45.002 Table 6.4.2.2.1
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
58d.1.4.2 Test Purposes
|
The test purpose is to verify that the EFTA capable MS:
1. Is not transmitting an EGPRS PACKET DOWNLINK ACK/NACK on the timeslot where the RRBP was received but instead according to the uplink radio block transmission order as described in TS 44.060 Annex N.
2. Is not transmitting a PACKET CONTROL ACKNOWLEDGEMENT on the timeslot where the RRBP was received but instead according to the uplink radio block transmission order as described in TS 44.060 Annex N.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
58d.1.4.3 Method of Test
|
Initial Conditions
System Simulator:
1 cell with EGPRS support, default setting,
Mobile Station:
The MS is EGPRS updated with a P-TMSI allocated, PDP Context 2 activated.
Specific PICS Statements
-
PIXIT Statements
-
Test Procedure
Establish a concurrent uplink downlink TBF using max number of Tx (max 4 Ts) and Rx timeslot according to multislot class and alternative EFTA multislot class minus 1 timeslot, EDA used, USF_GRANULARITY=4 blocks, MCS-5.
Transmit on downlink timeslots and check that polled Ack’d is transmitted according to TS 44.060 Annex N.
Transmit uplink timeslots SS sets FAI containing valid RRBP check that Packet Control Ack is transmitted according to TS 44.060 Annex N
Maximum Duration of Test
5 minutes
Expected Sequence
Step
Direction
Message
Comments
1
SS -> MS
{Downlink TBF establishment}
Acknowledged Mode. SS Commands MS to use mobile coding scheme MCS-5.
Max number of timeslots minus 1 are assigned according to MS multislot class (TS 45.002 Annex B.1) and Alternative EFTA multislot class (TS 45.002 Annex B.5):
- TN1 to TNx.
2
SS -> MS
PACKET UPLINK ASSIGNMENT
Sent on downlink PACCH.
The uplink TBF is assigned.
MCS-5, EDA used, USF_GRANULARITY=1
Max number of timeslots are assigned according to MS multislot class (TS 45.002 Annex B.1) and Alternative EFTA multislot class (TS 45.002 Annex B.5) (limited to max 4 timeslots to use):
- TN1 to TNx
3
SS -> MS
30 RLC data blocks
SS sends data, last block is polling. SS make sure the polling is done on a timeslot that will not be used in step 4
4
MS -> SS
EGPRS PACKET DOWNLINK ACK/NACK
Sent on PACCH.
SS checks that message sent according to TS44.060 Table N.1.
5
MS -> SS
30 RLC data blocks
Trigger 30 UL data blocks.
6
SS -> MS
PACKET UPLINK ACK/NACK
SS sets Final Ack Indicator = '1' containing valid RRBP. Sent on the PACCH of the assigned PDCH. SS make sure RRBP is sent on a timeslot that will not be used in step 7
7
MS -> SS
PACKET CONTROL ACKNOWLEDGEMENT
Received on the block specified by RRBP on PACCH according to TS44.060 Table N.1.
Specific Message Contents
None.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
58d.1.5 EFTA/Downlink TBF/8 TS
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
58d.1.5.1 Conformance Requirement
|
For a mobile station with an uplink TBF for which EFTA is used transmissions shall be performed on the uplink PDCHs or PDCH-pairs allocated by the USF as specified in Annex N. In case the mobile station also has one or more concurrent downlink TBF(s), but does not have enough RLC/MAC blocks ready for transmission to fully utilize the total number of allocated resources for uplink radio block transmission during the corresponding radio block period(s), then it shall immediately begin monitoring its assigned downlink PDCHs or PDCH-pairs after transmitting its last available RLC/MAC block taking into account the switching requirements of its multislot class (see 3GPP TS 45.002).
References
3GPP TS 44.060, subclause 8.1.1.1
A mobile station with an uplink TBF operating in BTTI configuration for which EFTA is used shall perform transmissions on a subset of the uplink PDCHs allocated by the USF. If the mobile station has P RLC/MAC blocks ready for transmission, then this subset is defined as the first P number of the allocated uplink PDCHs arranged according to the specific timeslot numbers order as specified in Table N.1 below. Tra or Trb, whichever is applicable, is the switching time from transmission to reception (see 3GPP TS 45.002).
Table N.1: Uplink timeslots transmission order for EFTA
Lowest Numbered Downlink Timeslot the MS Needs to Monitor
Tra or Trb, whichever is applicable
0
1
2
TN0
4,3,2,1,0,5,6,7
3,2,1,0,4,5,6,7
2,1,0,3,4,5,6,7
TN1
5,4,3,2,1,0,6,7
4,3,2,1,0,5,6,7
3,2,1,0,4,5,6,7
TN2
6,5,4,3,2,1,0,7
5,4,3,2,1,0,6,7
4,3,2,1,0,5,6,7
TN3
7,6,5,4,3,2,1,0
6,5,4,3,2,1,0,7
5,4,3,2,1,0,6,7
TN4
7,6,5,4,3,2,1,0
7,6,5,4,3,2,1,0
6,5,4,3,2,1,0,7
TN5
7,6,5,4,3,2,1,0
7,6,5,4,3,2,1,0
7,6,5,4,3,2,1,0
TN6
7,6,5,4,3,2,1,0
7,6,5,4,3,2,1,0
7,6,5,4,3,2,1,0
TN7
7,6,5,4,3,2,1,0
7,6,5,4,3,2,1,0
7,6,5,4,3,2,1,0
A mobile station with an uplink TBF operating in RTTI configuration for which EFTA is used shall perform transmissions on a subset of the uplink PDCH-pairs allocated by the USF in the same manner as specified above. For this case the specific timeslot number order shall be seen as indicating the lowest numbered timeslot of the uplink PDCH-pair.
NOTE: The above described rule determine the subset of the allocated uplink PDCHs or PDCH-pairs on which uplink transmissions shall be performed when EFTA is used. This procedure however, does not define which uplink PDCHs or PDCH-pairs that shall be allocated by the USF. Nor does the procedure define the individual ordering of any transmitted RLC/MAC blocks on these resources, which shall remain the same as for the case when EFTA is not used.
A mobile station with an uplink TBF for which EFTA is used shall perform the transmission of any uplink PACCH message allocated via the polling mechanism (see sub-clauses 10.4.4b and 10.4.5) on the first of the assigned uplink PDCHs or PDCH-pairs arranged according to the specific timeslot number order as described by Table N.1 above, regardless of which resources are allocated by the USF. The switching time Tra or Trb shall be interpreted according to its value at the time the poll was received.
References
3GPP TS 44.060, Annex N
References
3GPP TS 45.002, Annex B.1 and B.5
3GPP TS 45.002 Table 6.4.2.2.1
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
58d.1.5.2 Test Purposes
|
The test purpose is to verify that an EFTA capable MS indicating the support for alternative EFTA multislot class 3:
1. Is capable to receive and acknowledge correctly on a maximum of 8 timeslots while no frequency hopping is used.
2. Is capable to receive and acknowledge correctly on a maximum of 7 timeslots (if PICS TSPC_Fast_Downlink_Freq_Switch_Cap is supported then a maximum of 8 timeslots should be used instead) while frequency hopping is used.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
58d.1.5.3 Method of Test
|
Initial Conditions
System Simulator:
1 cell with EGPRS support, default setting,
Mobile Station:
The MS is EGPRS updated with a P-TMSI allocated, PDP Context 2 activated.
Specific PICS Statements
TSPC_Fast_Downlink_Freq_Switch_Cap
PIXIT Statements
-
Test Procedure
Establish a downlink TBF using:
- K=1: 8 timeslots should be assigned for downlink using no frequency hopping
- K=2: 7 timeslots should be assigned for downlink using frequency hopping and TSPC_Fast_Downlink_Freq_Switch_Cap not supported
- K=3: 8 timeslots should be assigned for downlink using frequency hopping and TSPC_Fast_Downlink_Freq_Switch_Cap supported
Transmit on all downlink timeslots and check that all data is Ack’d correctly.
Maximum Duration of Test
5 minutes
Expected Sequence
The test sequence is repeated for K = 1, 2 and 3
Step
Direction
Message
Comments
1
SS -> MS
{Downlink TBF establishment}
Acknowledged Mode. SS Commands MS to use mobile coding scheme MCS-5.
K=1: 8 timeslots assigned with no frequency hopping
K=2: 7 timeslots assigned with frequency hopping
K=3: 8 timeslots assigned with frequency hopping
- TN1 to TNx
SS -> MS
{Downlink data transfer}
2000 octets of data in downlink. and SS checks that Acked correctly.
Specific Message Contents
None.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
58e DTR
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
58e.1 DTR with Uplink TBF / PACKET UPLINK ACK/NACK message with DTR information / Resumption to normal operation
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
58e.1.1 Conformance requirements
|
[3GPP TS 44.060, 8.1.8.2]
During an uplink TBF, the network may transmit the DTR information within a PACKET UPLINK ACK/NACK message. If DTR information is received in a PACKET UPLINK ACK/NACK message and an RLC data block in the same block period, the mobile station shall ignore the DTR information received in the RLC data block.
A mobile station not already in DTR mode shall enter DTR mode and start monitoring only the indicated PDCH or PDCH-pair (and if applicable, carrier) within the reaction time specified in 3GPP TS 45.010, when:
- DTR information was included in whichever of the following was the most recently received:
i) any PACKET UPLINK ACK/NACK message (applicable if the mobile station has an ongoing uplink TBF) and
[3GPP TS 44.060, 8.1.8.3]
The mobile station shall exit DTR mode within the reaction time specified in 3GPP TS 45.010:
- when an RLC data block with BSN equal to V(S) is transmitted and the medium access mode is Dynamic Allocation;
References
3GPP TS 44.060, subclause 8.1.8
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
58e.1.2 Test purpose
|
1. To verify that MS enters DTR mode when PACKET UPLINK ACK/NACK message with DTR information is received during an uplink TBF.
2. To verify that MS resumes the RLC data block transfer on all the timeslots configured when a new LLC PDU is received from upper layers, after exiting the DTR mode.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
58e.3 Method of test
|
Initial Conditions
System Simulator:
1 cell, NW_EXT_UTBF = 1, EXT_UTBF_NODATA = 1, BS_CV_MAX = 15
Mobile Station:
MS is in Packet Idle mode, GPRS attached with support of GERAN Feature Package 1 indicated in MS Radio Access Capabilities, and PDP context 2 established.
Specific PICS Statements
- DTR Supported (TSPC_DTR)
PIXIT Statements
-
Test Procedure
The MS is triggered to transfer user data. A TBF of dynamic allocation in acknowledged mode is assigned. SS assigns an USF to MS until MS has sent CV = 0. SS acknowledges all received data with Final Ack Indicator bit set to ‘0’. SS continues to assigns USF to MS. As the EXT_UTBF_NODATA = 1, MS refrains from transmitting the Packet Uplink Dummy Control Blocks. SS transmits PACKET UPLINK ACK/NACK message with DTR information. SS transmits PACKET POLLING REQUEST on PACCH on TN2. Verify that MS does not respond with PACKET CONTROL ACK, as the MS is in DTR mode and it shall not monitor TN2. Then MS is triggered to send more data. Verify that MS shall send data blocks with a recalculated CV on both TN1 and TN2. Then the uplink TBF is continued and completed.
Expected Sequence
Step
Direction
Message
Comments
1
{Uplink dynamic allocation two phase access}
n = 400 octets, without starting time,
USF_GRANULARITY = 1 block,
EGPRS channel coding command: MCS 1,
RLC acknowledged mode (PDP context2),
Two slots, USF1 on TN1 and USF2 on TN2 are assigned.
2
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
The USF1 assigned to the MS. Sent in TN1 on PACCH of PDCH assigned in step 1.
3
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
The USF2 assigned to the MS. Sent in TN2 on PACCH of PDCH assigned in step 1.
4
MS -> SS
EGPRS UPLINK RLC DATA BLOCK
Received on TN1 on the PDTCH assigned in step 1.
5
MS -> SS
EGPRS UPLINK RLC DATA BLOCK
Received on TN2 on the PDTCH assigned in step 1.
6
Repeat step 2 and 3 until CV=0
7
SS -> MS
PACKET UPLINK ACK/NACK
Final Ack Indication = 0. Sent on PACCH of the assigned PDCH. Acknowledge all data blocks received.
8
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
Received on TN1 on the PDTCH assigned in step 1.
9
SS
Verify that MS does not transmit any data as EXT_UTBF_NODATA = 1
10
SS -> MS
PACKET UPLINK ACK/NACK
Sent on TN1 of the uplink PDTCH, with DTR information.
11
SS -> MS
PACKET POLLING REQUEST
Sent on TN2 of the uplink PDTCH, with a valid RRBP=N+13
12
SS
Verify that there is no PACKET CONTROL ACKNOWLEDGEMENT received, as the DTR is active for TN2.
13
MS
Trigger the MS to send 400 octets of data. Verify that UPLINK RLC DATA BLOCK is transmitted by the MS on both TN0 and TN1 and has recalculated the CV.
14
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
The USF1 assigned to the MS. Sent in TN1 on PACCH of PDCH assigned in step 1.
15
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
The USF2 assigned to the MS. Sent in TN2 on PACCH of PDCH assigned in step 1.
16
MS -> SS
EGPRS UPLINK RLC DATA BLOCK
Received on TN1 on the PDTCH assigned in step 1.
17
MS -> SS
EGPRS UPLINK RLC DATA BLOCK
Received on TN2 on the PDTCH assigned in step 1.
18
Repeat step 12 and 13 until CV=0
19
SS -> MS
PACKET UPLINK ACK/NACK
Final Ack Indication = 1 containing valid RRBP. Sent on PACCH of the assigned PDCH. Acknowledge all data blocks received.
20
MS -> SS
PACKET CONTROL ACKNOWLEDGEMENT
Received on the block specified by RRBP on PACCH of the assigned PDCH.
Specific Message Contents
PACKET UPLINK ACK/NACK (step 8):
Additions for Rel-10
1
- DTR Information
1
CI_DTR
0
TN_PDCH_pair_DTR
001
DTR Blks
00
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
58e.2 DTR with Downlink TBF / RLC data block with DTR information / Resumption to normal operation
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
58e.2.1 Conformance requirements
|
[3GPP TS 44.060, 8.1.8.2]
During a downlink TBF, the network may transmit the DTR information within downlink RLC data blocks of the TBF (see sub-clause10.3a.1).
A mobile station not already in DTR mode shall enter DTR mode and start monitoring only the indicated PDCH or PDCH-pair (and if applicable, carrier) within the reaction time specified in 3GPP TS 45.010, when:
- DTR information was included in whichever of the following was the most recently received:
ii) the RLC data block with BSN equal to V(Q) - 1 modulo SNS (applicable if the mobile station has an ongoing downlink TBF) and
[3GPP TS 44.060, 8.1.8.3]
The mobile station shall exit DTR mode within the reaction time specified in 3GPP TS 45.010:
- when an EGPRS RLC/MAC block for data transfer including BSN higher than V(R) modulo SNS is received;
References
3GPP TS 44.060, subclause 8.1.8
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
58e.2.2 Test purpose
|
1. To verify that MS enters DTR mode when RLC data block with LLC UI dummy command is received during a downlink TBF.
2. To verify that MS resumes the RLC data block transfer on all the configured timeslots, when an EGPRS RLC/MAC block for data transfer including BSN higher than V(R) modulo SNS is received.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
58e.2.3 Method of test
|
Initial Conditions
System Simulator:
1 cell, NW_EXT_UTBF = 1, EXT_UTBF_NODATA = 1, BS_CV_MAX = 15
Mobile Station:
MS is in Packet Idle mode, GPRS attached with support of GERAN Feature Package 1 indicated in MS Radio Access Capabilities, and PDP context 2 established.
Specific PICS Statements
- DTR Supported (TSPC_DTR)
PIXIT Statements
-
Test Procedure
A downlink TBF is established and in progress. SS continues the downlink TBF when the supply of downlink data is exhausted, the RLC entity on the network side shall transmit a RLC data block with LLC UI dummy command with DTR information (as in specific message content). SS transmits PACKET POLLING REQUEST on PACCH on TN2. Verify that MS does not respond with PACKET CONTROL ACK, as the MS is in DTR mode and it shall not monitor TN2. EGPRS RLC/MAC block for data transfer including BSN higher than V(R) modulo SNS is transmitted by the SS. SS transmits PACKET POLLING REQUEST on PACCH on TN2. Verify that UE responds with PACKET CONTROL ACK and has exit the DTR mode. Then the downlink TBF is continued and completed.
Expected Sequence
Step
Direction
Message
Comments
1
{Downlink TBF establishment}
RLC mode: acknowledged, without starting time.
Assigning the timeslots TN1 and TN2.
2
SS -> MS
EGPRS DOWNLINK RLC DATA BLOCK
Sent on TN1 of the downlink PDTCH.FBI=0. First RLC data block, is sent on the third block after the last radio block containing the downlink assignment.
3
SS -> MS
EGPRS DOWNLINK RLC DATA BLOCK
Sent on TN2 of the downlink PDTCH.FBI=0, ES/P field set to 01 and a valid RRBP.
4
MS -> SS
EGPRS PACKET DOWNLINK ACK/NACK
Received on the specified RRBP of downlink PACCH.
5
Repeat step 2 and 3 - 5 times
6
SS -> MS
EGPRS DOWNLINK RLC DATA BLOCK
Sent on TN1 of the downlink PDTCH.LLC UI dummy command, with DTR information
7
SS -> MS
PACKET POLLING REQUEST
Sent on TN2 of the downlink PDTCH, with a valid RRBP=N+13.
8
SS
Verify that there is no PACKET CONTROL ACKNOWLEDGEMENT received, as the DTR is active for TN2.
9
SS -> MS
EGPRS DOWNLINK RLC DATA BLOCK
Sent on TN1 of the downlink PDTCH.FBI=0. Including BSN higher than V(R) modulo SNS
10
SS -> MS
PACKET POLLING REQUEST
Sent on TN2 of the downlink PDTCH, with a valid RRBP=N+13
11
MS -> SS
PACKET CONTROL ACKNOWLEDGEMENT
Verify that PACKET CONTROL ACKNOWLEDGEMENT is received, as the MS has exit the DTR mode.
12
SS
{Completion of downlink RLC data block transfer}
Macro
Specific Message Contents
EGPRS DOWNLINK RLC DATA BLOCK (step 6):
Information Element
value/ remark
DTR Blks
00
CI
0
TN_PDCH_pair_DTR
001
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
58e.3 DTR with Concurrent TBF / RLC data block with DTR information / Resumption to normal operation
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
58e.3.1 Conformance requirements
|
[3GPP TS 44.060, 8.1.8.2]
During a downlink TBF, the network may transmit the DTR information within downlink RLC data blocks of the TBF (see sub-clause10.3a.1). During an uplink TBF, the network may transmit the DTR information within a PACKET UPLINK ACK/NACK message. If DTR information is received in a PACKET UPLINK ACK/NACK message and an RLC data block in the same block period, the mobile station shall ignore the DTR information received in the RLC data block.
A mobile station not already in DTR mode shall enter DTR mode and start monitoring only the indicated PDCH or PDCH-pair (and if applicable, carrier) within the reaction time specified in 3GPP TS 45.010, when:
- DTR information was included in whichever of the following was the most recently received:
ii) the RLC data block with BSN equal to V(Q) - 1 modulo SNS (applicable if the mobile station has an ongoing downlink TBF) and
- V(R) = V(Q), if the mobile station has an ongoing downlink TBF, and
- if the mobile station has an ongoing uplink TBF, the RLC data block with BSN = V(S) is not available and either:
- V(A) = V(S), or
- V(A) < V(S) mod SNS, the most recently received pre-emptive transmission bit is set to '0', and no element of V(B) has the value NACKED (for RLC acknowledged mode).
[3GPP TS 44.060, 8.1.8.3]
The mobile station shall exit DTR mode within the reaction time specified in 3GPP TS 45.010:
- when an RLC data block with BSN equal to V(S) is transmitted and the medium access mode is Dynamic Allocation;
References
3GPP TS 44.060, subclause 8.1.8
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
58e.3.2 Test purpose
|
1. To verify that MS enters DTR mode when RLC data block with LLC UI dummy command is received during a concurrent TBF.
2. To verify that MS resumes the RLC data block transfer on all the timeslots configured when a new LLC PDU is received from upper layers, after exiting the DTR mode.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
58e.3.3 Method of test
|
Initial Conditions
System Simulator:
1 cell, NW_EXT_UTBF = 1, EXT_UTBF_NODATA = 1, BS_CV_MAX = 15
Mobile Station:
MS is in Packet Idle mode, GPRS attached with support of GERAN Feature Package 1 indicated in MS Radio Access Capabilities, and PDP context 2 established.
Specific PICS Statements
- DTR Supported (TSPC_DTR)
PIXIT Statements
-
Test Procedure
An uplink TBF is established and in progress. After the MS sends an uplink data block the SS assigns a downlink TBF on the same timeslot as the uplink TBF. Uplink and downlink data transfer are in progress until CV = 0. SS transmits a RLC data block with LLC UI dummy command with DTR information. SS transmits PACKET POLLING REQUEST on PACCH on TN2. Verify that MS does not respond with PACKET CONTROL ACK, as DTR is active for TN2.Then MS is triggered to send more data. Verify that MS shall send data blocks with a recalculated CV on both TN1 and TN2. Then the uplink TBF is continued and completed.
Expected Sequence
Step
Direction
Message
Comments
1
{Uplink dynamic allocation two phase access}
n = 440 octets, without starting time,
USF_GRANULARITY = 1 block,
TLLI_BLOCK_CHANNEL_CODING: MCS1
EGPRS CHANNEL CODING COMMAND: MCS1
Two uplink timeslots TN1 and TN2 assigned.
2
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
The USF1 assigned to the MS. Sent in TN1 on PACCH of PDCH assigned in step 1.
3
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
The USF2 assigned to the MS. Sent in TN2 on the same radio block as step 2, on PACCH of PDCH assigned in step 1.
4
MS -> SS
EGPRS UPLINK RLC DATA BLOCK
Received on TN1 on the PDTCH assigned in step 1.
5
MS -> SS
EGPRS UPLINK RLC DATA BLOCK
Received on TN2, on the same radio block as step 4, on PDTCH assigned in step 1.
6
SS -> MS
PACKET DOWNLINK ASSIGNMENT
Sent on PACCH of PDCH assigned in step 1. Assign a downlink TBF, MAC mode = dynamic allocation, RLC mode = acknowledged mode, TFId, no starting time, assigning the timeslots TN1 and TN2.
7
SS -> MS
EGPRS DOWNLINK RLC DATA BLOCK
Sent on TN1 of the downlink PDTCH, RRBP invalid, the assigned USF1 addressing the MS.
8
SS -> MS
EGPRS DOWNLINK RLC DATA BLOCK
Sent on TN2 of the downlink PDTCH, RRBP invalid, the assigned USF2 addressing the MS.
9
MS -> SS
EGPRS UPLINK RLC DATA BLOCK
Received on TN1 on the next radio block from step 7.
10
MS -> SS
EGPRS UPLINK RLC DATA BLOCK
Received on TN2 on the next radio block from step 8.
11
SS -> MS
EGPRS DOWNLINK RLC DATA BLOCK
Sent on TN1 of the downlink PDTCH, RRBP invalid, the assigned USF1 addressing the MS.
12
SS -> MS
EGPRS DOWNLINK RLC DATA BLOCK
Sent on TN2 of the downlink PDTCH, with FBI= 0, ES/P set to 01 and a valid RRBP. Sent on downlink PDTCH.
13
MS -> SS
EGPRS UPLINK RLC DATA BLOCK
Received on TN1.
14
MS -> SS
EGPRS PACKET DOWNLINK ACK/NACK
Received on the specified RRBP of the downlink PACCH.
15
Repeat step 7 to 14, until CV=0 in step 9, 10 or 13.
16
SS -> MS
PACKET UPLINK ACK/NACK
Final Ack Indication = 0. Sent on PACCH of the assigned PDCH. Acknowledge all data blocks received.
17
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
USF assigned to the MS
18
SS
Verify that MS does not transmit any data as EXT_UTBF_NODATA = 1
19
SS -> MS
EGPRS DOWNLINK RLC DATA BLOCK
LLC UI dummy command, with DTR information
20
SS -> MS
PACKET POLLING REQUEST
Sent on TN2 of the uplink PDTCH, with a valid RRBP=N+13
21
SS
Verify that there is no PACKET CONTROL ACKNOWLEDGEMENT received, as the DTR is active for TN2.
23
MS
The MS is triggered to send 440 octets of user data.
Verify that UPLINK RLC DATA BLOCK is transmitted by the MS on both TN1 and TN2 and has recalculated the CV.
24
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
The USF assigned to the MS. Sent in TN1 on PACCH of PDCH assigned in step 1.
25
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
The USF assigned to the MS. Sent in TN2 on PACCH of PDCH assigned in step 1.(NOTE 1)
26
MS -> SS
EGPRS UPLINK RLC DATA BLOCK
Received on TN1.
27
MS -> SS
EGPRS UPLINK RLC DATA BLOCK
Received on TN2.
28
Repeat step 24 to 27 until CV=0
29
SS -> MS
PACKET UPLINK ACK/NACK
Final Ack Indication = 1 containing valid RRBP. Sent on PACCH of the assigned PDCH. Acknowledge all data blocks received.
30
MS -> SS
PACKET CONTROL ACKNOWLEDGEMENT
Received on the block specified by RRBP on PACCH of the assigned PDCH.
NOTE 1: The mobile stations shall be ready to receive on TN2 in step 25 in TDMA frame (N+9) mod 2715648 where N is the last TDMA frame of block sent in step 24 (3GPP TS 45.010).
Specific Message Contents
EGPRS DOWNLINK RLC DATA BLOCK (step 19):
Information Element
value/ remark
DTR Blks
00
CI
0
TN_PDCH_pair_DTR
001
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
59 Void
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
60 Inter-system hard handover from GSM to UTRAN
|
Clause 60 contains test procedures to be used for executing Inter-system Handover from GSM to UTRAN tests. Table 60‑1 contains a summary of the different combinations of parameters being tested, together with a reference to the appropriate generic test procedure. If a test uses a parameter which the MS under test does not support, the test shall be skipped. Test cases in this clause are applicable only to the MS supporting both UTRAN and GSM. The test USIM shall support service 27 to carry out these test cases.
Table 60-1
From
To
State
of call
Ref. subclause
Exec counter
Remark
GSM FR
UTRAN AMR
(conversational/speech/
UL:12.2 DL:12.2 kbps/CS RAB +
UL:3.4 DL3.4 kbps SRBS)
U10
60.1
1
call active state
GSM EFR
UTRAN AMR
(conversational/speech/
UL:12.2 DL:12.2 kbps/CS RAB +
UL:3.4 DL3.4 kbps SRBS)
U10
60.1
2
call active state
GSM AMR
UTRAN AMR
(conversational/speech/
UL:12.2 DL:12.2 kbps/CS RAB +
UL:3.4 DL3.4 kbps SRBS)
U10
60.1
3
call active state
GSM HR
UTRAN AMR
(conversational/speech/
UL:12.2 DL:12.2 kbps/CS RAB +
UL:3.4 DL3.4 kbps SRBS)
U10
60.1
4
call active state
GSM FR
UTRAN (TDD 1.28 Mcps) AMR
(conversational/speech/
UL:12.2 DL:12.2 kbps/CS RAB +
UL:3.4 DL3.4 kbps SRBS)
U10
60.1
5
call active state
GSM EFR
UTRAN (TDD 1.28 Mcps) AMR
(conversational/speech/
UL:12.2 DL:12.2 kbps/CS RAB +
UL:3.4 DL3.4 kbps SRBS)
U10
60.1
6
call active state
GSM AMR
UTRAN (TDD 1.28 Mcps) AMR
(conversational/speech/
UL:12.2 DL:12.2 kbps/CS RAB +
UL:3.4 DL3.4 kbps SRBS)
U10
60.1
7
call active state
GSM HR
UTRAN (TDD 1.28 Mcps) AMR
(conversational/speech/
UL:12.2 DL:12.2 kbps/CS RAB +
UL:3.4 DL3.4 kbps SRBS)
U10
60.1
8
call active state
GSM FR
UTRAN AMR
(conversational/speech/
UL:12.2 DL:12.2 kbps/CS RAB +
UL:3.4 DL3.4 kbps SRBS)
U10
60.1a
1
call active state;
A5/3 applied in GSM, UEA2/UIA2 in UTRAN
GSM EFR
UTRAN AMR
(conversational/speech/
UL:12.2 DL:12.2 kbps/CS RAB +
UL:3.4 DL3.4 kbps SRBS)
U10
60.1a
2
call active state;
A5/3 applied in GSM, UEA2/UIA2 in UTRAN
GSM AMR
UTRAN AMR
(conversational/speech/
UL:12.2 DL:12.2 kbps/CS RAB +
UL:3.4 DL3.4 kbps SRBS)
U10
60.1a
3
call active state;
A5/3 applied in GSM, UEA2/UIA2 in UTRAN
GSM HR
UTRAN AMR
(conversational/speech/
UL:12.2 DL:12.2 kbps/CS RAB +
UL:3.4 DL3.4 kbps SRBS)
U10
60.1a
4
call active state;
A5/3 applied in GSM, UEA2/UIA2 in UTRAN
GSM FR
UTRAN AMR
(conversational/speech/
UL:12.2 DL:12.2 kbps/CS RAB +
UL:3.4 DL3.4 kbps SRBS)
U10
60.1b
1
call active state;
A5/4 applied in GSM, UEA2/UIA2 in UTRAN
GSM EFR
UTRAN AMR
(conversational/speech/
UL:12.2 DL:12.2 kbps/CS RAB +
UL:3.4 DL3.4 kbps SRBS)
U10
60.1b
2
call active state;
A5/4 applied in GSM, UEA2/UIA2 in UTRAN
GSM AMR
UTRAN AMR
(conversational/speech/
UL:12.2 DL:12.2 kbps/CS RAB +
UL:3.4 DL3.4 kbps SRBS)
U10
60.1b
3
call active state;
A5/4 applied in GSM, UEA2/UIA2 in UTRAN
GSM HR
UTRAN AMR
(conversational/speech/
UL:12.2 DL:12.2 kbps/CS RAB +
UL:3.4 DL3.4 kbps SRBS)
U10
60.1b
4
call active state;
A5/4 applied in GSM, UEA2/UIA2 in UTRAN
GSM
14.4 kbps CS data
UTRAN
(Streaming/unknown/
UL:14.4 DL:14.4 kbps/CS RAB +
UL:3.4 DL:3.4 kbps SRBS)
U10
60.2a
1
same data rate
GSM
14.4 kbps CS data
UTRAN (TDD 1.28 Mcps)
(Streaming/unknown/
UL:14.4 DL:14.4 kbps/CS RAB +
UL:3.4 DL:3.4 kbps SRBS)
U10
60.2a
2
same data rate
GSM
14.4 kbps HSCSD
UTRAN
(Streaming/unknown/
UL:14.4 DL:14.4 kbps/CS RAB +
UL:3.4 DL:3.4 kbps SRBS)
U10
60.2b
1
Same data rate
GSM
28.8 kbps CS data
UTRAN
(Streaming/unknown/
UL:28.8 DL:28.8 kbps/CS RAB +
UL:3.4 DL:3.4 kbps SRBS)
U10
60.2b
2
same data rate
GSM
57.6 kbps CS data
UTRAN
(Streaming/unknown/
UL:57.6 DL:57.6 kbps/CS RAB +
UL:3.4 DL:3.4 kbps SRBS)
U10
60.2 b
3
same data rate
GSM
14.4 kbps CS data
UTRAN
(Streaming/unknown/
UL:28.8 DL:28.8 kbps/CS RAB +
UL:3.4 DL:3.4 kbps SRBS)
U10
60.3a
1
data rate upgrading
GSM
14.4 kbps CS data
UTRAN
(Streaming/unknown/
UL:57.6 DL:57.6 kbps/CS RAB +
UL:3.4 DL:3.4 kbps SRBS)
U10
60.3a
2
data rate upgrading
GSM
14.4 kbps HSCSD
UTRAN
(Streaming/unknown/
UL:28.8 DL:28.8 kbps/CS RAB +
UL:3.4 DL:3.4 kbps SRBS)
U10
60.3b
1
Data rate upgrading
GSM
14.4 kbps HSCSD
UTRAN
(Streaming/unknown/
UL:57.6 DL:57.6 kbps/CS RAB +
UL:3.4 DL:3.4 kbps SRBS)
U10
60.3b
2
Data rate upgrading
GSM
28.8 kbps CS data
UTRAN
(Streaming/unknown/
UL:57.6 DL:57.6 kbps/CS RAB +
UL:3.4 DL:3.4 kbps SRBS)
U10
60.3b
3
data rate upgrading
GSM SDCCH
UTRAN
(SDCCH/
UL:13.6 DL:13.6 kbps SRBS)
U1
60.4
1
during call establishment
GSM SDCCH
UTRAN (TDD 1.28 Mcps)
(SDCCH/
UL:13.6 DL:13.6 kbps SRBS)
U1
60.4
2
during call establishment
GSM FR
UTRAN AMR
(conversational/speech/
UL:12.2 DL:12.2 kbps/CS RAB +
UL:3.4 DL3.4 kbps SRBS)
U10
60.5
1
blind handover
GSM FR
UTRAN AMR
(conversational/speech/
UL:12.2 DL:12.2 kbps/CS RAB +
UL:3.4 DL3.4 kbps SRBS)
U10
60.6
1
failure case
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
60.1 Inter system handover to UTRAN/From GSM/Speech/Success
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
60.1.1 Definition
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
60.1.2 Conformance requirement
|
The MS shall be able to receive a INTERSYSTEM TO UTRAN HANDOVER COMMAND message from GSM and perform an inter-system handover.
If the MS succeeds to establish the connection to UTRAN, it shall transmit a HANDOVER TO UTRAN COMPLETE message on the uplink DCCH.
Reference(s)
3GPP TS 25.331 subclause 8.3.6.
3GPP TS 04.18 subclause 3.4.4a.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
60.1.3 Test purpose
|
To test that MS supporting both GSM and UTRAN hands over to the indicated channel in the UTRAN target cell when it is in the speech call active state in the GSM serving cell and receives a INTERSYSTEM TO UTRAN HANDOVER COMMAND. It is also verified that the MS performs measurements on the target UTRAN cell before the handover.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
60.1.4 Method of test
|
Initial conditions
System Simulator:
2 cells - Cell 1 is GPRS, Cell 2 is UTRAN (cell selection conditions in favour of the GPRS cell).
The present document subclause 40 shall be referenced for the default parameters of cell 1, and subclause 26.6.5.1 shall be referenced for cell allocation.
3GPP TS 34.108, subclause 6.1 shall be referenced for default parameters of Cell 2.
MS:
"idle, updated", channel released mode with TMSI allocated.
For MS supporting GPRS:
The MS is GPRS attached with a P-TMSI allocated, SPLIT PG CYCLE negotiated.
Specific PICS statements
- MS supports GSM FR (TSPC_AddInfo_Full_rate_version_1).
- MS supports GSM AMR (TSPC_AddInfo_Full_rate_version_3).
- MS supports GSM EFR (TSPC_AddInfo_Full_rate_version_2).
- MS supports GSM HR (TSPC_AddInfo_Half_rate_version_1).
- Support of UTRAN FDD (TSPC_Type_UTRAN FDD)
- Support of UTRAN TDD (TSPC_Type_UTRAN TDD)
PIXIT statements
-
Foreseen final state of the MS
The MS is in CC state U10 on cell 2.
Test Procedure
The SS brings the MS into the call active state (CC state U10) according to settings for execution counter M (with FR speech call for execution counter M = 1). The SS configures the UTRAN dedicated channel corresponding to the UTRAN FDD/TDD mode to default configuration 3. The SS sends a MEASUREMENT INFORMATION to trigger the MS to perform measurements on the UTRAN cell. The SS verifies that the MS includes the UTRAN cell in the MEASUREMENT REPORT and then sends INTERSYSTEM TO UTRAN HANDOVER COMMAND indicating the dedicated channel of the target cell to the MS through the GSM serving cell. After the MS receives the command it shall configure itself accordingly and switch to the dedicated channel of UTRAN cell. The SS checks whether the handover is performed by checking that the MS transmits HANDOVER TO UTRAN COMPLETE to the SS through DCCH of the UTRAN cell.
Depending on the PIXIT parameters, the above procedure is executed each time for different initial conditions:
For MS following procedures are executed:
- if the MS supports GSM FR, the procedure is executed for execution counter M = 1 (UTRAN_FDD);
- if the MS supports GSM EFR, the procedure is executed for execution counter M = 2 (UTRAN_FDD);
- if the MS supports GSM AMR, the procedure is executed for execution counter M = 3 (UTRAN_FDD);
- if the MS supports GSM HR, the procedure is executed for execution counter M = 4 (UTRAN_FDD);
- if the MS supports GSM FR, the procedure is executed for execution counter M = 5 (UTRAN_TDD);
- if the MS supports GSM EFR, the procedure is executed for execution counter M = 6 (UTRAN_TDD);
- if the MS supports GSM AMR, the procedure is executed for execution counter M = 7 (UTRAN_TDD);
- if the MS supports GSM HR, the procedure is executed for execution counter M = 8 (UTRAN_TDD).
Expected sequence
This sequence is performed for a maximum execution counter M = 1, 2, 3, 4, 5, 6, 7, 8 depending on the PIXIT parameters.
Step
Direction
Message
Comments
MS
SS
1
MS
The SS bring the MS into GSM U10 state in cell 1 and
for M = 1 and 5: the MS is in GSM FR speech call;
for M = 2 and 6: the MS is in GSM EFR speech call;
for M = 3 and 7: the MS is in GSM AMR speech call;
for M = 4 and 8: the MS is in GSM HR speech call.
on a hopping traffic channel
2
SS
The SS configures the dedicated channel with the configuration: conversational/speech/UL:12.2 DL:12.2 kbps/CS RAB + UL:3.4 DL3.4 kbps SRBs in UTRAN cell.
3
MEASUREMENT INFORMATION
4
MEASUREMENT REPORT
Including Measurement Results on the UTRAN cell in Step 4
5
INTERSYSTEM TO UTRAN HANDOVER COMMAND
Send on cell 1 (GSM cell)
6
MS
The MS accepts the handover command and configures its lower layers using the parameters contained in the INTERSYSTEM TO UTRAN HANDOVER COMMAND
7
SS
The SS waits for uplink physical channel in synchronization
8
HANDOVER TO UTRAN COMPLETE
The SS receives this message on DCCH of cell 2 (UTRAN cell). It implies that the down link physical channel has synchronised with UTRAN.
Specific message contents
MEASUREMENT INFORMATION (for M = 1,2,3,4)
Information Element
Value/remark
< RR short PD : bit >
0
< Message type : bit (5) >
‘00101’B
< Short layer 2 header : bit (2) >
‘00’B
< BA_IND : bit >
0
< 3G_BA_IND : bit >
0
< MP_CHANGE_MARK : bit >
0
< MI_INDEX : bit (4) >
‘0000’B
< MI_COUNT : bit (4) >
‘0000’B
< PWRC : bit >
0
< REPORT_TYPE : bit >
1 (Measurement Reporting shall be used)
< REPORTING_RATE : bit >
0 (SACCH rate reporting)
< INVALID_BSIC_REPORTING : bit >
0 (Report on cells with invalid BSIC not allowed)
0 | 1 < Real Time Difference Description >
0
0 | 1 < BSIC Description >
0
0 | 1 < REPORT PRIORITY Description >
0
0 | 1 < MEASUREMENT Parameters Description >
0
0 | 1 < extension length >
0
0 | 1 < 3G Neighbour Cell Description >
1
0 | 1 < 3G_Wait : bit (3) >
0
0 | 1 < Index_Start_3G : bit (7) >
0
0 | 1 < Absolute_Index_Start_EMR : bit (7) >
0
0 | 1 < UTRAN FDD Description >
1
0 | 1 < Bandwidth_FDD : bit (3) >
0
1 < Repeated UTRAN FDD Neighbour Cells > ** 0
1
0 < FDD-ARFCN : bit (14) >
0 See TS 34.108, clause 6.1.5, table 6.1.1
< FDD_Indic0 : bit >
0
< NR_OF_FDD_CELLS : bit (5) >
‘00001’B
< FDD_CELL_INFORMATION Field >
10 bits
Scrambling code according to TS 34.108, clause 6.1.4, Default settings for cell No.1
1 < Repeated UTRAN FDD Neighbour Cells > ** 0
0
0 | 1 < UTRAN TDD Description >
0
0 | 1 < CDMA2000 Description >
0
0 | 1 < 3G MEASUREMENT Parameters Description >
< Qsearch_C : bit (4) >
‘0111’B (Always)
< 3G_SEARCH_PRIO: bit (1) >
1
< FDD_REP_QUANT : bit (1) >
1 (Ec/No)
0 | 1 < FDD_MULTIRAT_REPORTING : bit (2) >
‘1 01’B (Report on 1 UTRAN cell)
0 | 1 < FDD_REPORTING_OFFSET : bit (3) >
0
0 | 1 < TDD_MULTIRAT_REPORTING : bit (2) >
0
0 | 1 < TDD_REPORTING_OFFSET : bit (3) >
0
0 | 1 < CDMA2000_MULTIRAT_REPORTING : bit (2) >
0
0 | 1 < CDMA2000_REPORTING_OFFSET : bit (3) >
0
MEASUREMENT INFORMATION (for M = 5,6,7,8)
Information Element
Value/remark
< RR short PD : bit >
0
< Message type : bit (5) >
‘00101’B
< Short layer 2 header : bit (2) >
‘00’B
< BA_IND : bit >
0
< 3G_BA_IND : bit >
0
< MP_CHANGE_MARK : bit >
0
< MI_INDEX : bit (4) >
‘0000’B
< MI_COUNT : bit (4) >
‘0000’B
< PWRC : bit >
0
< REPORT_TYPE : bit >
1 (Measurement Reporting shall be used)
< REPORTING_RATE : bit >
0 (SACCH rate reporting)
< INVALID_BSIC_REPORTING : bit >
0 (Report on cells with invalid BSIC not allowed)
0 | 1 < Real Time Difference Description >
0
0 | 1 < BSIC Description >
0
0 | 1 < REPORT PRIORITY Description >
0
0 | 1 < MEASUREMENT Parameters Description >
0
0 | 1 < extension length >
0
0 | 1 < 3G Neighbour Cell Description >
1
0 | 1 < 3G_Wait : bit (3) >
0
0 | 1 < Index_Start_3G : bit (7) >
0
0 | 1 < Absolute_Index_Start_EMR : bit (7) >
0
0 | 1 < UTRAN FDD Description >
0
0 | 1 < UTRAN TDD Description >
1
0 | 1 < Bandwidth_TDD : bit (3) >
1 ‘001’B
1 < Repeated UTRAN TDD Neighbour Cells > ** 0
1
0 < TDD-ARFCN : bit (14) >
0 See TS 34.108, clause 6.1.6, table 6.1.6a
< TDD_Indic0 : bit >
1
< NR_OF_TDD_CELLS : bit (5) >
‘00001’B
< TDD_CELL_INFORMATION Field >
9 bits
Scrambling code according to TS 34.108, clause 6.1.4, Default settings for cell No.1
1 < Repeated UTRAN TDD Neighbour Cells > ** 0
0
0 | 1 < CDMA2000 Description >
0
0 | 1 < 3G MEASUREMENT Parameters Description >
< Qsearch_C : bit (4) >
‘0111’B (Always)
< 3G_SEARCH_PRIO: bit (1) >
1
< FDD_REP_QUANT : bit (1) >
1 (Ec/No)
0 | 1 < FDD_MULTIRAT_REPORTING : bit (2) >
0
0 | 1 < FDD_REPORTING_OFFSET : bit (3) >
0
0 | 1 < TDD_MULTIRAT_REPORTING : bit (2) >
1 ’01’B (Report on 1 UTRAN cell)
0 | 1 < TDD_REPORTING_OFFSET : bit (3) >
0
0 | 1 < CDMA2000_MULTIRAT_REPORTING : bit (2) >
0
0 | 1 < CDMA2000_REPORTING_OFFSET : bit (3) >
0
INTERSYSTEM TO UTRAN HANDOVER COMMAND
Information Element
Value/remark
RR management Protocol Discriminator
‘0110'B
Skip Indicator
‘0000'B
Inter System to UTRAN Handover Command Message Type
‘01100011'B
Length of Handover to UTRAN Command contents
Octet length of the "Handover to UTRAN Command value part"
Handover to UTRAN Command value part
PER encoded ASN.1 value of type "HandoverToUTRANCommand-r3-IEs", the content is presented in the next table.
Content of "HandoverToUTRANCommand-r3-IEs" (in tabular format) (for M = 1,2,3,4)
Information Element
Value/remark
New U-RNTI
- SRNC Identity
‘000000000001'B
- S-RNTI-2
Set to arbitrary value corresponding to DPCH Offset value currently stored in SS
Ciphering algorithm
The presence of this IE is dependent on PIXIT statements in TS 34.123-2. If ciphering is indicated to be active, use UEA1. Else, this IE is omitted.
CHOICE specification mode
Preconfiguration
CHOICE preconfiguration mode
Default configuration
- Default configuration mode
FDD
- Default configuration identity
3 (12.2 kbps speech + 3.4 kbps signalling)
- RAB Info
- RAB identity
- RAB identity (GSM-MAP)
‘00000001'B
- CN domain identity
CS domain
- NAS Synchronisation Indicator
Not Present
- Uplink DPCH info
- Uplink DPCH power control info
- CHOICE mode
FDD
- DPCCH power offset
-78 dB ( i.e. ASN.1 IE value of -20 ( 2 + ( IE Value * 4) ) )
- PC Preamble
1 frame
- SRB delay
7 frames
- CHOICE mode
FDD
- Scrambling code type
long
- Reduced scrambling code number
0
- Spreading factor
64
- Downlink information common for all radio links
- Downlink DPCH info common for all RL
- Downlink DPCH power control information
- CHOICE Mode
FDD
- DPC mode
Single TPC
- Downlink information per radio link list
1
- Downlink information for each radio link
- CHOICE mode
FDD
- Primary CPICH info
- Primary scrambling code
See TS 34.108, clause titled "Default settings for cell No.1 (FDD)” in clause 6.1
- Downlink DPCH info for each radio link
- CHOICE mode
FDD
- CHOICE mode
FDD
- Primary CPICH usage for channel
May be used
- Secondary scrambling code
1
- CHOICE Spreading factor
128
- Code number
0
- Scrambling code change
No code change
- TPC combination index
0
- Frequency info
- UARFCN uplink(Nu)
Not Present
Absence of this IE is equivalent to apply the default duplex distance defined for the operating frequency according to TS 25.101
- UARFCN downlink(Nd)
See TS 34.108, clause 6.1.5, table 6.1.1
Maximum allowed UL TX power
See TS 34.108, clause 6.1.5, table 6.1.1
Content of "HandoverToUTRANCommand-r4-IEs" (in tabular format) (for M = 5,6,7,8)
Information Element
Value/remark
New U-RNTI
- SRNC Identity
‘000000000001'B
- S-RNTI-2
Set to arbitrary value corresponding to DPCH Offset value currently stored in SS
Ciphering algorithm
The presence of this IE is dependent on PIXIT statements in TS 34.123-2. If ciphering is indicated to be active, use UEA1. Else, this IE is omitted.
CHOICE specification mode
Preconfiguration
CHOICE preconfiguration mode
Default configuration
- Default configuration mode
TDD
- Default configuration identity
3 (12.2 kbps speech + 3.4 kbps signalling)
- RAB Info
- RAB identity
- RAB identity (GSM-MAP)
‘00000001'B
- CN domain identity
CS domain
- NAS Synchronisation Indicator
Not Present
- Choice TDD128
- Uplink DPCH info
- Uplink DPCH power control info
- Uplink TargetSIR
20 ( real value : (IE value * 0.5) – 11 )
- UplinkTimingAdvanceControl
-CHOICE enabled
- Uplink SynchronisationParameters
_- stepsize
1
- frequency
1
- SynchronisationParameters
- Sync Uplink Code
01010101
- FPACH Info
FPACH Configuration Information
- Timeslot Number
0
- Channelisation Code
16/15
- Midamble shift and burst type
- Choice default Midamble
- Midamble Configuration
4 (MidambleK = 8)
- wt
4
- prxUpPCHdes
-80 (-120~-58 by step 1)
- SYNC Uplink Procedure
- max SYNC ULTransmissions
2
- powerRampStep
2
- UplinkTimeslotsCodes
- dynamicSFusage
No
- IndividualTimeslotInfo
- TimeslotNum
TS1,TS2 or TS3
- tfci Existence
TRUE
- MidambleShiftAndBurstType
- Choice default Midamble
- midamble Configuration
4 (MidambleK = 8)
- modulation
QPSK
- SS TPC symbols
1
- additional SS-TPC symbols
Not present
- UL-TS-ChannelisationCodeList
SF8 code*1 or SF16 code*2 34.108 Clause6
-CHOICE nomoreTimeslot
- Downlink information common for all radio links
- Downlink DPCH info common for all RL
- Downlink DPCH power control information
- CHOICE Mode
TDD
- TPC StepSizeTDD
- Downlink information per radio link list
1
- Downlink information for each radio link
- CHOICE mode
TDD
- Primary CPICH info
- tstd-Indicator
FALSE
- CellParametersID
CellParamterID of cell 2
- sctd-Indicator
FALSE
- Downlink DPCH info for each radio link
- IndividualTimeslotInfo
- TimeslotNum
TS4, TS5 or TS6
- tfci-Existence
TRUE
- MidambleShiftAndBurstType
- Choice default Midamble
- Midamble Configuration
4 (MidambleK = 8)
- modulation
QPSK
- SS TPC Symbols
1
- additional SS TPC Symbols
Not present
- Downlink Timeslot ChannelisationCode
- Choice bitmap
SF16 code*2 34.108 Clause6
- Choice nomoreTimeslot
- Frequency info
- UARFCN
UARFCN of cell 2
- PrimaryCCPCH TX Power
20 (6~43, ref TS34.108, clause 6.1.6, table6.1.6a)
Maximum allowed UL TX power
33dbm (ref TS34.108, clause 6.1.6, table6.1.6a)
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
60.1.5 Test requirement
|
At step 4 the MEASUREMENT REPORT should include details of the UTRAN cell. At step 8 a HANDOVER TO UTRAN COMPLETE command should be received on DCCH of the UTRAN cell.
60.1a Inter system handover to UTRAN/From GSM/Speech/Success with A5/3 and UEA2/UIA2 ciphering
60.1a.1 Definition
The A5/3 ciphering algorithm is applied in the GERAN cell. UEA2/UIA2 algorithms are applied in the UTRAN cell.
60.1a.2 Conformance requirement
Identical to 60.1.2
60.1a.3 Test purpose
Identical to 60.1.3 but the ciphering /integrity algorithms are defined in 60.1.1.
60.1a.4 Method of test
Identical to 60.1.4
Specific message contents
Similar to the specific message contents in 60.1 except the Rel-7 IE are used and the MS/UE capability to support A5/3 and UEA2/UIA2 is checked, instead.
60.1a.5 Test requirement
Identical to 60.1.5
60.1b Inter system handover to UTRAN/From GSM/Speech/Success with A5/4 and UEA2/UIA2 ciphering
60.1b.1 Definition
The A5/4 ciphering algorithm is applied in the GERAN cell. UEA2/UIA2 algorithms are applied in the UTRAN cell.
60.1b.2 Conformance requirement
Identical to 60.1.2
60.1b.3 Test purpose
Identical to 60.1.3 but the ciphering /integrity algorithms are defined in table 60-1.
60.1b.4 Method of test
Identical to 60.1.4
Specific message contents
Similar to the specific message contents in 60.1 except the Rel-9 IE are used and the MS/UE capability to support A5/4 and UEA2/UIA2 is checked, instead.
60.1b.5 Test requirement
Identical to 60.1.5
60.2a Inter system handover to UTRAN/From GSM/Data/Same data rate/Success
60.2a.1 Definition
60.2a.2 Conformance requirement
The MS shall be able to receive a INTER SYSTEM TO UTRAN HANDOVER COMMAND message from GSM and perform an inter-system handover.
If the MS succeeds to establish the connection to UTRAN, it shall transmit a HANDOVER TO UTRAN COMPLETE message on the uplink DCCH.
Reference(s)
3GPP TS 25.331 subclause 8.3.6.
3GPP TS 04.18 subclause 3.4.4a.
60.2a.3 Test purpose
To test that the MS hands over to the indicated UTRAN target cell and the data rate of the target channel is the same as the old channel when it is in the data call active state in the GSM serving cell and receives a INTER SYSTEM TO UTRAN HANDOVER COMMAND. It is also verified that the MS performs measurements on the target UTRAN cell before the handover.
60.2a.4 Method of test
Initial conditions
System Simulator:
2 cells - Cell 1 is GPRS, Cell 2 is UTRAN (cell selection conditions in favour of the GPRS cell).
The present document subclause 40 shall be referenced for the default parameters of Cell 1, and subclause 26.6.5.1 shall be referenced for cell allocation.
3GPP TS 34.108, subclause 6.1 shall be referenced for default parameters of Cell 2.
MS:
"idle, updated", channel released mode with TMSI allocated.
For MS supporting GPRS:
The MS is GPRS attached with a P-TMSI allocated, SPLIT PG CYCLE negotiated.
Specific PICS statements
- Support of UTRAN FDD (TSPC_Type_UTRAN FDD)
- Support of UTRAN TDD (TSPC_Type_UTRAN TDD)
PIXIT statements
-
Foreseen final state of the MS
The MS is in CC state U10 on cell 2.
Test Procedure
The SS brings the MS into the call active state (CC state U10) with a 14.4 kbps CS data call. The SS configures a dedicated channel corresponding to the UTRAN FDD/TDD mode (default configuration 7 -streaming/unknown/UL:14.4 DL:14.4 kbps/CS RAB + UL:3.4 DL3.4 kbps SRBS ) in the UTRAN cell. The SS sends a MEASUREMENT INFORMATION to trigger the MS to perform measurements on the UTRAN cell. The SS verifies that the MS include the UTRAN cell in the MEASUREMENT REPORT and then sends INTER SYSTEM TO UTRAN HANDOVER COMMAND indicating the dedicated channel of the target cell to the MS through the GSM serving cell. After the MS receives the command it shall configure itself accordingly and switch to the dedicated channel of the UTRAN cell. The SS checks whether the handover is performed by checking that the MS transmits HANDOVER TO UTRAN COMPLETE to the SS through DCCH of the UTRAN cell.
For MS following procedures are executed:
- if the MS supports UTRAN_FDD the procedure is executed for execution counter M = 1;
- if the MS supports UTRAN_TDD the procedure is executed for execution counter M = 2.
Expected sequence
This sequence is performed for a maximum execution counter M = 1, 2 depending on the PIXIT parameters.
Step
Direction
Message
Comments
MS
SS
1
MS
The SS bring the MS into GSM U10 state in cell 1 - GSM 14.4 kbps CS data call on a hopping traffic channel.
2
SS
The SS configures a dedicated channel in the UTRAN cell with the configuration:
streaming/unknown/UL:14.4 DL:14.4 kbps/CS RAB + UL:3.4 DL3.4 kbps SRBs.
3
MEASUREMENT INFORMATION
4
MEASUREMENT REPORT
Including Measurement Results on the UTRAN cell in Step 4.
5
INTER SYSTEM TO UTRAN HANDOVER COMMAND
Send on cell 1 (GSM cell)
6
MS
The MS accepts the handover command and configures its lower layers using the parameters contained in the INTER SYSTEM TO UTRAN HANDOVER COMMAND
7
SS
The SS waits for uplink physical channel in synchronization
8
HANDOVER TO UTRAN COMPLETE
The SS receives this message on DCCH of cell 2 (UTRAN cell). It implies that the down link physical channel has synchronised with UTRAN.
Specific message contents
MEASUREMENT INFORMATION
Same as in 60.1 according UTRAN FDD/TDD mode.
INTER SYSTEM TO UTRAN HANDOVER COMMAND
For M = 1:
Same content as in 60.1 (UTRAN FDD mode) with the following exceptions in the content of the "HandoverToUTRANCommand-r3-IEs":
Information Element
Value/remark
CHOICE specification mode
Preconfiguration
CHOICE preconfiguration mode
Default configuration
- Default configuration identity
7 (14.4 kbps streaming CS data + 3.4 kbps signalling)
For M = 2:
Same content as in 60.1 (according to UTRAN TDD mode) with the following exceptions in the content of the "HandoverToUTRANCommand-r4-IEs" for the configuration “Streaming / unknown / UL:14.4/DL:14.4 kbps / CS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH” defined in TS 34.108 [149] clause 6.11.5.4.1.15:
Information Element
Value/remark
New U-RNTI
- SRNC Identity
‘000000000001'B
- S-RNTI-2
Set to arbitrary value corresponding to DPCH Offset value currently stored in SS
Ciphering algorithm
The presence of this IE is dependent on PIXIT statements in TS 34.123-2. If ciphering is indicated to be active, use UEA1. Else, this IE is omitted.
CHOICE specification mode
Complete specification
CHOICE complete specification
Default configuration
RB information elements
Signalling RB information to setup list
- Signalling RB information to setup
(UM DCCH for RRC)
- RB identity
Not Present
- CHOICE RLC info type
- RLC info
- CHOICE Uplink RLC mode
UM RLC
- Transmission RLC discard
Not Present
- CHOICE Downlink RLC mode
UM RLC
- RB mapping info
- Information for each multiplexing option
1 RBMuxOption
- RLC logical channel mapping indicator
Not Present
- Number of RLC logical channels
1
- Uplink transport channel type
DCH
- UL Transport channel identity
5
- Logical channel identity
1
- CHOICE RLC size list
Configured
- MAC logical channel priority
1
- Downlink RLC logical channel info
- Number of RLC logical channels
1
- Downlink transport channel type
DCH
- DL DCH Transport channel identity
10
- DL DSCH Transport channel identity
Not Present
- Logical channel identity
1
- Signalling RB information to setup
(AM DCCH for RRC)
- RB identity
Not Present
- CHOICE RLC info type
- RLC info
- CHOICE Uplink RLC mode
AM RLC
- Transmission RLC discard
- SDU discard mode
No Discard
- MAX_DAT
15
- Transmission window size
128
- Timer_RST
500
- Max_RST
1
- Polling info
- Timer_poll_prohibit
200
- Timer_poll
200
- Poll_PDU
Not present
- Poll_SDU
1
- Last transmission PDU poll
TRUE
- Last retransmission PDU poll
TRUE
- Poll_Window
99
- Timer_poll_periodic
Not Present
- CHOICE Downlink RLC mode
AM RLC
- In-sequence delivery
TRUE
- Receiving window size
128
- Downlink RLC status info
- Timer_status_prohibit
200
- Timer_EPC
Not Present
- Missing PDU indicator
TRUE
- Timer_STATUS_periodic
Not Present
- RB mapping info
- Information for each multiplexing option
1 RBMuxOption
- RLC logical channel mapping indicator
Not Present
- Number of RLC logical channels
1
- Uplink transport channel type
DCH
- UL Transport channel identity
5
- Logical channel identity
2
- CHOICE RLC size list
Configure
- MAC logical channel priority
2
- Downlink RLC logical channel info
- Number of RLC logical channels
1
- Downlink transport channel type
DCH
- DL DCH Transport channel identity
10
- DL DSCH Transport channel identity
Not Present
- Logical channel identity
2
Signalling RB information to setup
(AM DCCH for NAS_DT High priority)
- RB identity
Not Present
- CHOICE RLC info type
- RLC info
- CHOICE Uplink RLC mode
AM RLC
- Transmission RLC discard
- SDU discard mode
No Discard
- MAX_DAT
15
- Transmission window size
128
- Timer_RST
500
- Max_RST
1
- Polling info
- Timer_poll_prohibit
200
- Timer_poll
200
- Poll_PDU
Not present
- Poll_SDU
1
- Last transmission PDU poll
TRUE
- Last retransmission PDU poll
TRUE
- Poll_Windows
99
- Timer_poll_periodic
Not Present
- CHOICE Downlink RLC mode
AM RLC
- In-sequence delivery
TRUE
- Receiving window size
128
- Downlink RLC status info
- Timer_status_prohibit
200
- Timer_EPC
Not Present
- Missing PDU indicator
TRUE
- Timer_STATUS_periodic
Not Present
- RB mapping info
- Information for each multiplexing option
1 RBMuxOption
- RLC logical channel mapping indicator
Not Present
- Number of RLC logical channels
1
- Uplink transport channel type
DCH
- UL Transport channel identity
5
- Logical channel identity
3
- CHOICE RLC size list
Configured
- MAC logical channel priority
3
- Downlink RLC logical channel info
- Number of RLC logical channels
1
- Downlink transport channel type
DCH
- DL DCH Transport channel identity
10
- DL DSCH Transport channel identity
Not Present
- Logical channel identity
3
- Signalling RB information to setup
(AM DCCH for NAS_DT Low priority)
- RB identity
Not Present
- CHOICE RLC info type
- RLC info
- CHOICE Uplink RLC mode
AM RLC
- Transmission RLC discard
- SDU discard mode
No discard
- MAX_DAT
15
- Transmission window size
128
- Timer_RST
500
- Max_RST
1
- Polling info
- Timer_poll_prohibit
200
- Timer_poll
200
- Poll_PDU
Not present
- Poll_SDU
1
- Last transmission PDU poll
TRUE
- Last retransmission PDU poll
TRUE
- Poll_Windows
99
- Timer_poll_periodic
Not Present
- CHOICE Downlink RLC mode
AM RLC
- In-sequence delivery
TRUE
- Receiving window size
128
- Downlink RLC status info
- Timer_status_prohibit
200
- Timer_EPC
Not Present
- Missing PDU indicator
TRUE
- Timer_STATUS_periodic
Not Present
- RB mapping info
- Information for each multiplexing option
1 RBMuxOptions
- RLC logical channel mapping indicator
Not Present
- Number of RLC logical channels
1
- Uplink transport channel type
DCH
- UL Transport channel identity
5
- Logical channel identity
4
- CHOICE RLC size list
Configured
- MAC logical channel priority
4
- Downlink RLC logical channel info
- Number of RLC logical channels
1
- Downlink transport channel type
DCH
- DL DCH Transport channel identity
10
- DL DSCH Transport channel identity
Not Present
- Logical channel identity
4
RAB information to setup list
- RAB info
- RAB identity
- CHOICE RAB identity type
RAB identity (GSM-MAP)
- RAB identity
0000 0001B
The first/ leftmost bit of the bit string contains the most significant bit of the RAB identity.
- CN domain identity
CS domain
- NAS Synchronization Indicator
Not Present
- Re-establishment timer
useT314
- RB information to setup list
- RB information to setup
- RB identity
10
- PDCP info
Not Present
- CHOICE RLC info type
RLC info
- CHOICE Uplink RLC mode
TM RLC
- Transmission RLC discard
Not Present
- Segmentation indication
FALSE
- CHOICE Downlink RLC mode
TM RLC
- Segmentation indication
FALSE
- RB mapping info
- Information for each multiplexing option
- RLC logical channel mapping indicator
Not Present
- Number of uplink RLC logical channels
1
- Uplink transport channel type
DCH
- UL Transport channel identity
1
- Logical channel identity
Not Present
- CHOICE RLC size list
Configured
- MAC logical channel priority
8
- Downlink RLC logical channel info
- Number of downlink RLC logical channels
1
- Downlink transport channel type
DCH
- DL DCH Transport channel identity
6
- DL DSCH Transport channel identity
Not Present
- Logical channel identity
Not Present
Uplink transport channels
UL Transport channel information common for all transport channels
- PRACH TFCS
Not Present
- CHOICE mode
TDD128
- Individual UL CCTrCH information
- UL TFCS Identity
- TFCS ID
1
- Shared Channel Indicator
FALSE
- UL TFCS
- CHOICE TFCI signalling
Normal
- TFCI Field 1 Information
- CHOICE TFCS representation
Complete reconfiguration
- TFCS complete reconfiguration information
- CHOICE CTFC Size
Number of bits used must be enough to cover all combinations of CTFC from clause 6.11.5.4 Parameter Set.
- CTFC information
This IE is repeated for TFC numbers and reference to clause 6.11.5.4 Parameter Set
- CTFC
Reference to clause 6.11.5.4 Parameter Set
- Power offset information
- CHOICE Gain Factors
Computed Gain Factors(The last TFC is set to Signalled Gain Factors)
- Reference TFC ID
0 Integer(0.. 3)
- CHOICE Gain Factors
Signalled Gain Factors(Not Present if the CHOICE Gain Factors is set to ComputedGain Factors)
- CHOICE mode
TDD
- Gain Factor d
15
- Reference TFC ID
0 Integer(0.. 3)
- CHOICE mode
TDD
- TFC subset
- CHOICE Subset representation
Full transport format combination set
- TFC subset list
Not Present
Added or Reconfigured UL TrCH information
- Uplink transport channel type
DCH
- UL Transport channel identity
5
- TFS
- CHOICE Transport channel type
Dedicated transport channels
- Dynamic Transport format information
- RLC Size
Reference to clause 6.11 Parameter Set
- Number of TBs and TTI List
(This IE is repeated for TF number.)
- Transmission Time Interval
Not Present
- Number of Transport blocks
Reference to clause 6.11 Parameter Set
- CHOICE Logical channel list
All
- Semi-static Transport Format information
- Transmission time interval
Reference to clause 6.11 Parameter Set
- Type of channel coding
Reference to clause 6.11 Parameter Set
- Coding Rate
Reference to clause 6.11 Parameter Set
- Rate matching attribute
Reference to clause 6.11 Parameter Set
- CRC size
Reference to clause 6.11 Parameter Set
- Uplink transport channel type
DCH
- UL Transport channel identity
1
- TFS
- CHOICE Transport channel type
Dedicated transport channels
- Dynamic Transport format information
- RLC Size
Reference to clause 6.11 Parameter Set
- Number of TBs and TTI List
(This IE is repeated for TF number.)
- Transmission Time Interval
Not Present
- Number of Transport blocks
Reference to clause 6.11 Parameter Set
- CHOICE Logical channel list
All
- Semi-static Transport Format information
- Transmission time interval
Reference to clause 6.11 Parameter Set
- Type of channel coding
Reference to clause 6.11 Parameter Set
- Coding Rate
Reference to clause 6.11 Parameter Set
- Rate matching attribute
Reference to clause 6.11 Parameter Set
- CRC size
Reference to clause 6.11 Parameter Set
Downlink transport channels
DL Transport channel information common for all transport channel
- SCCPCH TFCS
Not Present
- CHOICE mode
TDD
- Individual DL CCTrCH information
- DL TFCS Identity
- TFCS ID
2
- Shared Channel Indicator
FALSE
- CHOICE DL parameters
SameAsUL
- UL DCH TFCS Identity
- TFCS ID
1
- Shared Channel Indicator
FALSE
Added or Reconfigured TrCH information
- Added or Reconfigured DL TrCH information
- Downlink transport channel type
DCH
- DL Transport channel identity
10
- CHOICE DL parameters
Same as UL
- Uplink transport channel type
DCH
- UL TrCH identity
5
- DCH quality target
- BLER Quality value
-20 (-2.0)
- Downlink transport channel type
DCH
- DL Transport channel identity
6
- CHOICE DL parameters
Same as UL
- Uplink transport channel type
DCH
- UL TrCH identity
1
- DCH quality target
- BLER Quality value
-20 (-2.0)
Uplink radio resources
Uplink DPCH info
- Uplink DPCH power control info
- CHOICE mode
TDD
- CHOICE TDD option
1.28 Mcps TDD
- PRXPDPCHdes
Integer (-120…-58 by step of 1)
- CHOICE UL OL PC info
- Broadcast UL OL PC info
Null
- Uplink Timing Advance Control
Not Present
-CHOICE enabled
- Uplink SynchronisationParameters
_- stepsize
1
- frequency
1
- SynchronisationParameters
- Sync Uplink Code
01010101
- FPACH Info
FPACH Configuration Information
- Timeslot Number
0
- Channelisation Code
16/15
- Midamble shift and burst type
- Choice default Midamble
- Midamble Configuration
4 (MidambleK = 8)
- wt
4
- prxUpPCHdes
-80 (-120~-58 by step 1)
- SYNC Uplink Procedure
- max SYNC ULTransmissions
2
- powerRampStep
2
- UL CCTrCH List
- TFCS ID
1
- UL Target SIR
20 ( real value : (IE value * 0.5) – 11 )
- Time info
- Activation time
(256+CFN-(CFN MOD 8 + 8))MOD 256
- Duration
Infinite
- Common timeslot info
- 2nd interleaving mode
Default value is "Frame"
- TFCI coding
Reference to clause 6 Parameter set
- Puncturing limit
Reference to clause 6 Parameter set
- Repetition period
1
- Repetition length
- Uplink DPCH timeslots and code
- UplinkTimeslotsCodes
- dynamicSFusage
No
- IndividualTimeslotInfo
- TimeslotNum
TS1,TS2 or TS3
- tfci Existence
TRUE
- MidambleShiftAndBurstType
- Choice default Midamble
- midamble Configuration
4 (MidambleK = 8)
- modulation
QPSK
- SS TPC symbols
1
- additional SS-TPC symbols
Not present
- UL-TS-ChannelisationCodeList
SF8 code*1 or SF16 code*2 34.108 Clause6
-CHOICE nomoreTimeslot
- First timeslot Code List
Repeated (1,2) for each channelisation code assigned in the slot to meet the needs of clause 6 Parameter Set.
- channelisation codes
(SF/ i) where i denotes an unassigned code matching the SF specified in clause 6 Parameter Set.
- CHOICE more timeslots
No more timeslots
- UL CCTrCH List to Remove
Not present
Downlink radio resources
Downlink information common for all radio links
- Downlink information common for all radio links
- Downlink DPCH info common for all RL
- Downlink DPCH power control information
- CHOICE Mode
TDD
- TPC StepSizeTDD
- Downlink information per radio link list
1
- Downlink information for each radio link
- CHOICE mode
TDD
- Primary CPICH info
- tstd-Indicator
FALSE
- CellParametersID
CellParamterID of cell 2
- sctd-Indicator
FALSE
Downlink DPCH info for each radio link
- IndividualTimeslotInfo
- TimeslotNum
TS4, TS5 or TS6
- tfci-Existence
TRUE
- MidambleShiftAndBurstType
- Choice default Midamble
- Midamble Configuration
4 (MidambleK = 8)
- modulation
QPSK
- SS TPC Symbols
1
- additional SS TPC Symbols
Not present
- Downlink Timeslot ChannelisationCode
- Choice bitmap
SF16 code*2 34.108 Clause6
- Choice nomoreTimeslot
- Frequency info
- UARFCN
UARFCN of cell 2
- PrimaryCCPCH TX Power
20 (6~43, ref TS34.108, clause 6.1.6, table6.1.6a)
Frequency info
- UARFCN uplink(Nu)
Not Present
Absence of this IE is equivalent to apply the default duplex distance defined for the operating frequency according to TS 25.101
- UARFCN downlink(Nd)
See TS 34.108, clause 6.1.5, table 6.1.1
Maximum allowed UL TX power
33dbm (ref TS34.108, clause 6.1.6, table6.1.6a)
60.2a.5 Test requirement
At step 4 the MEASUREMENT REPORT should include details of the UTRAN cell. At step 8 a HANDOVER TO UTRAN COMPLETE command should be received on DCCH of the UTRAN cell.
60.2b Inter system handover to UTRAN/From GSM/Data/Same data rate/Extended Rates/Success
60.2b.1 Definition
60.2b.2 Conformance requirement
The MS shall be able to receive a INTER SYSTEM TO UTRAN HANDOVER COMMAND message from GSM and perform an inter-system handover.
If the MS succeeds to establish the connection to UTRAN, it shall transmit a HANDOVER TO UTRAN COMPLETE message on the uplink DCCH.
Reference(s)
3GPP TS 25.331 subclause 8.3.6.
3GPP TS 04.18 subclause 3.4.4a.
60.2b.3 Test purpose
To test that the MS hands over to the indicated UTRAN target cell and the data rate of the target channel is the same as the old channel when it is in the data call active state in the GSM serving cell and receives a INTER SYSTEM TO UTRAN HANDOVER COMMAND. It is also verified that the MS performs measurements on the target UTRAN cell before the handover.
60.2b.4 Method of test
Initial conditions
System Simulator:
2 cells - Cell 1 is GSM, Cell 2 is UTRAN (cell selection conditions in favour of the GSM cell).
The present document subclause 26.6.5.1 or subclause 26.13.1.3 (for HSCSD) shall be referenced for the default parameters of Cell 1.
3GPP TS 34.108, subclause 6.1 shall be referenced for default parameters of Cell 2.
MS:
"idle, updated", channel released mode with TMSI allocated.
Specific PICS statements
- MS supports UTRAN Streaming/unknown/UL:14.4 DL:14,4 kbps/CS RAB + UL:3.4 DL:3,4 kbps SRBs.
- MS supports UTRAN Streaming/unknown/UL:28.8 DL:28,8 kbps/CS RAB + UL:3.4 DL:3,4 kbps SRBs.
- MS supports UTRAN Streaming/unknown/UL:57.6 DL:57,6 kbps/CS RAB + UL:3.4 DL:3,4 kbps SRBs.
PIXIT statements
-
Foreseen final state of the MS
The MS is in CC state U10 on cell 2.
Test Procedure
The SS brings the MS into the call active state (CC state U10) with a CS data call (14.4 kbps HSCSD for execution counter M = 1). The SS configures an appropriate dedicated channel(default configuration 7 -streaming/unknown/UL:14.4 DL:14.4 kbps/CS RAB + UL:3.4 DL3.4 kbps SRBS for M = 1) in the UTRAN cell. The SS sends a MEASUREMENT INFORMATION to trigger the MS to perform measurements on the UTRAN cell. The SS verifies that the MS include the UTRAN cell in the MEASUREMENT REPORT and then sends INTER SYSTEM TO UTRAN HANDOVER COMMAND indicating the dedicated channel of the target cell to the MS through the GSM serving cell. After the MS receives the command it shall configure itself accordingly and switch to the dedicated channel of the UTRAN cell. The SS checks whether the handover is performed by checking that the MS transmits HANDOVER TO UTRAN COMPLETE to the SS through DCCH of the UTRAN cell.
Depending on the PIXIT parameters, the above procedure is executed maximum three times, each time for different initial conditions:
- if the MS supports GSM 14.4 kbps HSCSD and UTRAN streaming/unknown/UL:14.4 DL:14.4 kbps/CS RAB + UL:3.4 DL3.4 kbps SRBs, the procedure is executed for execution counter M = 1, using Default configuration 7;
- if the MS supports GSM 28.8 kbps CS data and UTRAN streaming/unknown/UL:28.8 DL:28.8 kbps/CS RAB + UL:3.4 DL3.4 kbps SRBs, the procedure is executed for execution counter M = 2, using Default configuration 8;
- if the MS supports GSM 57.6 kbps CS data and UTRAN streaming/unknown/UL:57.6 DL:57.6 kbps/CS RAB + UL:3.4 DL3.4 kbps SRBs, the procedure is executed for execution counter M = 3, using Default configuration 9.
Expected sequence
This sequence is performed for a maximum execution counter M = 1, 2, 3, depending on the PIXIT parameters.
Step
Direction
Message
Comments
MS
SS
1
MS
The SS bring the MS into GSM U10 state in cell 1 and
for M = 1: the MS is in GSM 14.4 kbps HSCSD call;
for M = 2: the MS is in GSM 28.8 kbps CS data call;
for M = 3: the MS is in GSM 57.6 kbps CS data call;
2
SS
The SS configures a dedicated channel in the UTRAN cell with the configuration:
For M = 1: (streaming/unknown/UL:14.4 DL:14.4 kbps/CS RAB + UL:3.4 DL3.4 kbps SRBs);
For M = 2: (streaming/unknown/UL:28.8 DL:28.8 kbps/CS RAB + UL:3.4 DL3.4 kbps SRBs);
For M = 3: (streaming/unknown/UL:57.6 DL:57.6 kbps/CS RAB + UL:3.4 DL3.4 kbps SRBs)
3
MEASUREMENT INFORMATION
4
MEASUREMENT REPORT
Including Measurement Results on the UTRAN cell in Step 4
Received within 5 sec + 10% from Step 4.
5
INTER SYSTEM TO UTRAN HANDOVER COMMAND
Send on cell 1 (GSM cell)
6
MS
The MS accepts the handover command and configures its lower layers using the parameters contained in the INTER SYSTEM TO UTRAN HANDOVER COMMAND
7
SS
The SS waits for uplink physical channel in synchronization
8
HANDOVER TO UTRAN COMPLETE
The SS receives this message on DCCH of cell 2 (UTRAN cell). It implies that the down link physical channel has synchronised with UTRAN.
Specific message contents
MEASUREMENT INFORMATION
Same as in 60.1
For execution1 (M = 1):
INTER SYSTEM TO UTRAN HANDOVER COMMAND for FDD
Same content as in 60.1 with the following exceptions in the content of the "HandoverToUTRANCommand-r3-IEs":
Information Element
Value/remark
CHOICE specification mode
Preconfiguration
CHOICE preconfiguration mode
Default configuration
- Default configuration identity
7 (14.4 kbps streaming CS data + 3.4 kbps signalling)
INTER SYSTEM TO UTRAN HANDOVER COMMAND for TDD
Same content as in 60.2a M=2
For execution2 (M = 2):
INTER SYSTEM TO UTRAN HANDOVER COMMAND
Same content as in 60.1 with the following exceptions in the content of the "HandoverToUTRANCommand-r3-IEs":
Information Element
Value/remark
CHOICE specification mode
Preconfiguration
CHOICE preconfiguration mode
Default configuration
- Default configuration identity
8 (28.8 kbps streaming CS data + 3.4 kbps signalling)
- RAB Info
Same content as in 60.1
- Uplink DPCH info
Same content as in 60.1 except for:
- Spreading factor
32
- Downlink information per radio link
Same content as in 60.1 except for:
- Downlink information for each radio link
- Downlink DPCH info for each RL
- CHOICE Spreading factor
64
For execution3 (M = 3):
INTER SYSTEM TO UTRAN HANDOVER COMMAND
Same content as in 60.1 with the following exceptions in the content of the "HandoverToUTRANCommand-r3-IEs":
Information Element
Value/remark
CHOICE specification mode
Preconfiguration
CHOICE preconfiguration mode
Default configuration
- Default configuration identity
9 (57.6 kbps streaming CS data + 3.4 kbps signalling)
- RAB Info
Same content as in 60.1
- Uplink DPCH info
Same content as in 60.1 except for:
- Spreading factor
16
- Downlink information per radio link
Same content as in 60.1 except for:
- Downlink information for each radio link
- Downlink DPCH info for each RL
- CHOICE Spreading factor
32
60.2b.5 Test requirement
At step 5 the MEASUREMENT REPORT should include details of the UTRAN cell. At step 9 a HANDOVER TO UTRAN COMPLETE command should be received on DCCH of the UTRAN cell.
60.3a Inter system handover to UTRAN/From GSM/Data/Data rate upgrading/Success
60.3a.1 Definition
60.3a.2 Conformance requirement
The MS shall be able to receive a INTER SYSTEM TO UTRAN HANDOVER COMMAND message from GSM and perform an inter-system handover.
If the MS succeeds to establish the connection to UTRAN, it shall transmit a HANDOVER TO UTRAN COMPLETE message on the uplink DCCH.
Reference(s)
3GPP TS 25.331 subclause 8.3.6.
3GPP TS 04.18 subclause 3.4.4a.
60.3a.3 Test purpose
To test that the MS being in the data call active state hands over from the GSM serving cell to the indicated channel of a higher data rate in the UTRAN target cell after it receives a INTER SYSTEM TO UTRAN HANDOVER COMMAND. It is also verified that the MS performs measurements on the target UTRAN cell before the handover.
60.3a.4 Method of test
Initial conditions
System Simulator:
2 cells - Cell 1 is GPRS, Cell 2 is UTRAN (cell selection conditions in favour of the GPRS cell).
The present document subclause 40 shall be referenced for the default parameters of cell 1, and subclause 26.6.5.1 shall be referenced for cell allocation.
3GPP TS 34.108 subclause 6.1 shall be referenced for default parameters of Cell 2.
MS:
"idle, updated", channel released mode with TMSI allocated.
For MS supporting GPRS:
The MS is GPRS attached with a P-TMSI allocated, SPLIT PG CYCLE negotiated.
Specific PICS statements
- MS supports UTRAN Streaming/unknown/UL:28.8 DL:28.8 kbps/CS RAB + UL:3.4 DL:3.4 kbps SRBs.
- MS supports UTRAN Streaming/unknown/UL:57.6 DL:57.6 kbps/CS RAB + UL:3.4 DL:3.4 kbps SRBs.
PIXIT statements
-
Foreseen final state of the MS
The MS is in CC state U10 on cell 2.
Test Procedure
Then the SS brings the MS into the call active state (CC state U10) with a 14.4 kbps CS data call . The SS configures an appropriate dedicated channel in the UTRAN cell ( default configuration 8 streaming/unknown/UL:28.8 DL:28.8 kbps/CS RAB + UL:3.4 DL3.4 kbps SRBS for M = 1). The SS sends a MEASUREMENT INFORMATION to trigger the MS to perform measurements on the UTRAN cell. The SS verifies that the MS include the UTRAN cell in the MEASUREMENT REPORTs and then sends INTER SYSTEM TO UTRAN HANDOVER COMMAND indicating the dedicated channel of the target cell to the MS through the GSM serving cell. After the MS receives the command it shall configure itself accordingly and switch to the new channel of the UTRAN cell. The SS checks whether the handover is performed by checking that the MS transmits HANDOVER TO UTRAN COMPLETE to the SS through DCCH of the UTRAN cell.
Depending on the PIXIT parameters, the above procedure is executed maximum two times, each time for different conditions:
- if the MS supports GSM 14.4 kbps CS data and UTRAN streaming/unknown/UL:28.8 DL:28.8 kbps/CS RAB + UL:3.4 DL3.4 kbps SRBs, the procedure is executed for execution counter M = 1, using Default configuration 8;
- if the MS supports GSM 14.4 kbps CS data and UTRAN streaming/unknown/UL:57.6 DL:57.6 kbps/CS RAB + UL:3.4 DL3.4 kbps SRBs, the procedure is executed for execution counter M = 2, using Default configuration 9;
Expected sequence
This sequence is performed for a maximum execution counter M = 1, 2 depending on the PIXIT parameters.
Step
Direction
Message
Comments
MS
SS
1
MS
The SS bring the MS into GSM U10 state in cell 1 and the MS is in GSM 14.4 kbps CS data call on a hopping traffic channel
2
SS
The SS configures a dedicated channel in the UTRAN cell with the configuration:
For M = 1: (streaming/unknown/UL:28.8 DL:28.8 kbps/CS RAB + UL:3.4 DL3.4 kbps SRBs);
For M = 2: (streaming/unknown/UL:57.6 DL:57.6 kbps/CS RAB + UL:3.4 DL3.4 kbps SRBs);
3
MEASUREMENT INFORMATION
4
MEASUREMENT REPORT
Including Measurement Results on the UTRAN cell in Step 4
5
INTER SYSTEM TO UTRAN HANDOVER COMMAND
Send on cell 1 (GSM cell)
6
MS
The MS accepts the handover command and configures its lower layers using the parameters contained in the INTER SYSTEM TO UTRAN HANDOVER COMMAND
7
SS
The SS waits for uplink physical channel in synchronization
8
HANDOVER TO UTRAN COMPLETE
The SS receives this message on DCCH of cell 2 (UTRAN cell). It implies that the down link physical channel has synchronised with UTRAN.
Specific message contents
For execution1 (M = 1):
Same as the default message contents in subclause 60.2b for M = 2.
For execution2 (M = 2):
Same as the default message contents in subclause 60.2b for M = 3.
60.3a.5 Test requirement
At step 4 the MEASUREMENT REPORT should include details of the UTRAN cell. At step 8 a HANDOVER TO UTRAN COMPLETE command should be received on DCCH of the UTRAN cell.
60.3b Inter system handover to UTRAN/From GSM/Data/Data rate upgrading/Extended Rates/Success
60.3b.1 Definition
60.3b.2 Conformance requirement
The MS shall be able to receive a INTER SYSTEM TO UTRAN HANDOVER COMMAND message from GSM and perform an inter-system handover.
If the MS succeeds to establish the connection to UTRAN, it shall transmit a HANDOVER TO UTRAN COMPLETE message on the uplink DCCH.
Reference(s)
3GPP TS 25.331 subclause 8.3.6.
3GPP TS 04.18 subclause 3.4.4a.
60.3b.3 Test purpose
To test that the MS being in the data call active state hands over from the GSM serving cell to the indicated channel of a higher data rate in the UTRAN target cell after it receives a INTER SYSTEM TO UTRAN HANDOVER COMMAND. It is also verified that the MS performs measurements on the target UTRAN cell before the handover.
60.3b.4 Method of test
Initial conditions
System Simulator:
2 cells - Cell 1 is GSM, Cell 2 is UTRAN (cell selection conditions in favour of the GSM cell).
The present document subclause 26.6.5.1 or subclause 26.13.1.3 (for HSCSD) shall be referenced for the default parameters of cell 1.
3GPP TS 34.108 subclause 6.1 shall be referenced for default parameters of Cell 2.
MS:
"idle, updated", channel released mode with TMSI allocated.
Specific PICS statements
- MS supports UTRAN Streaming/unknown/UL:28.8 DL:28.8 kbps/CS RAB + UL:3.4 DL:3.4 kbps SRBs.
- MS supports UTRAN Streaming/unknown/UL:57.6 DL:57.6 kbps/CS RAB + UL:3.4 DL:3.4 kbps SRBs.
PIXIT statements
-
Foreseen final state of the MS
The MS is in CC state U10 on cell 2.
Test Procedure
Then the SS brings the MS into the call active state (CC state U10) with a CS data call (14.4 kbps HSCSD for execution counter M = 1). The SS configures an appropriate dedicated channel in the UTRAN cell ( default configuration 4 streaming/unknown/UL:28.8 DL:28.8 kbps/CS RAB + UL:3.4 DL3.4 kbps SRBS for M = 1). The SS sends a MEASUREMENT INFORMATION to trigger the MS to perform measurements on the UTRAN cell. The SS verifies that the MS include the UTRAN cell in the MEASUREMENT REPORTs and then sends INTER SYSTEM TO UTRAN HANDOVER COMMAND indicating the dedicated channel of the target cell to the MS through the GSM serving cell. After the MS receives the command it shall configure itself accordingly and switch to the new channel of the UTRAN cell. The SS checks whether the handover is performed by checking that the MS transmits HANDOVER TO UTRAN COMPLETE to the SS through DCCH of the UTRAN cell.
Depending on the PIXIT parameters, the above procedure is executed maximum three times, each time for different conditions:
- if the MS supports GSM 14.4 kbps HSCSD and UTRAN streaming/unknown/UL:28.8 DL:28.8 kbps/CS RAB + UL:3.4 DL3.4 kbps SRBs, the procedure is executed for execution counter M = 1, using Default configuration 8;
- if the MS supports GSM 14.4 kbps HSCSD and UTRAN streaming/unknown/UL:57.6 DL:57.6 kbps/CS RAB + UL:3.4 DL3.4 kbps SRBs, the procedure is executed for execution counter M = 2, using Default configuration 9;
- if the MS supports GSM 28.8 kbps CS data and UTRAN streaming/unknown/UL:57.6 DL:57.6 kbps/CS RAB + UL:3.4 DL3.4 kbps SRBs, the procedure is executed for execution counter M = 3, using Default configuration 9.
Expected sequence
This sequence is performed for a maximum execution counter M = 1, 2, 3, depending on the PIXIT parameters.
Step
Direction
Message
Comments
MS
SS
1
MS
The SS bring the MS into GSM U10 state in cell 1 and
for M = 1: the MS is in GSM 14.4 kbps HSCSD call;
for M = 2: the MS is in GSM 14.4 kbps HSCSD call;
for M = 3: the MS is in GSM 28.8 kbps CS data call;
2
SS
The SS configures a dedicated channel in the UTRAN cell with the configuration:
For M = 1: (streaming/unknown/UL:28.8 DL:28.8 kbps/CS RAB + UL:3.4 DL3.4 kbps SRBs);
For M = 2: (streaming/unknown/UL:57.6 DL:57.6 kbps/CS RAB + UL:3.4 DL3.4 kbps SRBs);
For M = 3: (streaming/unknown/UL:57.6 DL:57.6 kbps/CS RAB + UL:3.4 DL3.4 kbps SRBs)
3
MEASUREMENT INFORMATION
4
MEASUREMENT REPORT
Including Measurement Results on the UTRAN cell in Step 4
Received within 5 sec + 10% from Step 4.
5
INTER SYSTEM TO UTRAN HANDOVER COMMAND
Send on cell 1 (GSM cell)
6
MS
The MS accepts the handover command and configures its lower layers using the parameters contained in the INTER SYSTEM TO UTRAN HANDOVER COMMAND
7
SS
The SS waits for uplink physical channel in synchronization
8
HANDOVER TO UTRAN COMPLETE
The SS receives this message on DCCH of cell 2 (UTRAN cell). It implies that the down link physical channel has synchronised with UTRAN.
Specific message contents
For execution1 (M = 1):
Same as the default message contents in subclause 60.2b for M = 2.
For execution2 (M = 2):
Same as the default message contents in subclause 60.2b for M = 3.
For execution3 (M = 3):
Same as the default message contents in subclause 60.2b for M = 3.
60.3b.5 Test requirement
At step 5 the MEASUREMENT REPORT should include details of the UTRAN cell. At step 9 a HANDOVER TO UTRAN COMPLETE command should be received on DCCH of the UTRAN cell.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
60.4 Inter system handover to UTRAN/From GSM/SDCCH/CC Establishment/Success
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
60.4.1 Definition
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
60.4.2 Conformance requirement
|
The MS shall be able to receive a INTER SYSTEM TO UTRAN HANDOVER COMMAND message from GSM and perform an inter-system handover.
If the MS succeeds to establish the connection to UTRAN, it shall transmit a HANDOVER TO UTRAN COMPLETE message on the uplink DCCH.
Reference(s)
3GPP TS 25.331 subclause 8.3.6.
3GPP TS 04.18 subclause 3.4.4a.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
60.4.3 Test purpose
|
To test that the MS supporting both GSM and UTRAN handovers from the GSM serving cell to the indicated channel in UTRAN target cell when the MS is on SDCCH during call establishment phase and receives an INTER SYSTEM TO UTRAN HANDOVER COMMAND. It is also verified that the MS performs measurements on the target UTRAN cell before the handover.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
60.4.4 Method of test
|
Initial conditions
System Simulator:
2 cells - Cell 1 is GPRS, Cell 2 is UTRAN (cell selection conditions in favour of the GPRS cell).
The present document subclause 40 shall be referenced for the default parameters of cell 1. Except for SI3 indicating SI2quater on BCCH norm, and SI2quater is broadcasted on BCCH of Cell 1, and subclause 26.6.5.1 shall be referenced for cell allocation..
3GPP TS 34.108, subclause 6.2 shall be referred to default parameters of Cell 2.
MS:
"idle, updated", channel released mode with TMSI allocated.
For MS supporting GPRS:
The MS is GPRS attached with a P-TMSI allocated, SPLIT PG CYCLE negotiated.
Specific PICS statements
- Support of UTRAN FDD (TSPC_Type_UTRAN FDD)
- Support of UTRAN TDD (TSPC_Type_UTRAN TDD)
PIXIT statements
-
Foreseen final state of the MS
The MS is in CC state U1 on cell 2.
Test Procedure
The UTRAN cell is set up corresponding to the UTRAN FDD/TDD mode. The MS reads SI2quater indicating presence of the UTRAN cell. The MS is triggered to make an MO speech call. After the SS received SETUP message it configures a dedicated channel corresponding to the default configuration 1 (UL:13.6 DL13.6 kbps SRBs) corresponding to the UTRAN FDD/TDD mode and then the SS sends INTER SYSTEM TO UTRAN HANDOVER COMMAND indicating the dedicated channel to the MS through the GSM serving cell. After the MS receives the command and it shall configure itself accordingly and switch to the new channel of UTRAN cell. The SS checks whether the handover is performed by checking that the MS transmits HANDOVER TO UTRAN COMPLETE to the SS through DCCH of the UTRAN cell.
For MS following procedures are executed:
- if the MS supports UTRAN_FDD the procedure is executed for execution counter M = 1;
- if the MS supports UTRAN_TDD the procedure is executed for execution counter M = 2.
Expected sequence
This sequence is performed for a maximum execution counter M = 1, 2 depending on the PIXIT parameters.
Step
Direction
Message
Comments
MS
SS
1
SS
The MS reads SI2quater indicating presence of the UTRAN cell.
3
SETUP
The SS brings the MS to GSM U1 state in Cell 1
4
SS
The SS configures a dedicated channel with the default configuration 1: UL:13.6 DL13.6 kbps SRBs in UTRAN cell.
5
MEASUREMENT REPORT
6
Step 5 is repeated until the MEASUREMENT REPORT contains the measurement result on the UTRAN cell
7
INTER SYSTEM TO UTRAN HANDOVER COMMAND
Send on cell 1 (GSM cell)
8
MS
The MS accepts the handover command and configures its lower layers using the parameters contained in the INTER SYSTEM TO UTRAN HANDOVER COMMAND
9
SS
The SS waits for uplink physical channel in synchronization
10
HANDOVER TO UTRAN COMPLETE
The SS receives this message on DCCH of cell 2 (UTRAN cell). It implies that the down link physical channel has synchronised with UTRAN.
Specific message contents
SYSTEM INFORMATION TYPE 2QUATER (M = 1)
Information Element
Value/remark
< RR management Protocol Discriminator bit (4) >
‘0110'B
< Skip Indicator : bit (4) >
‘0000'B
< Message type : bit (8) >
‘0000 0111’B
< SI2 quarter Rest Octets >
< BA_IND : bit >
0
< 3G_BA_IND : bit >
0
< MP_CHANGE_MARK : bit >
0
< SI2quater _INDEX : bit (4) >
‘0000’B
< SI2quater_COUNT : bit (4) >
‘0000’B
0 | 1 < Measurement_Parameters Description >
0
0 | 1 < GPRS_Real Time Difference Description >
0
0 | 1 < GPSR_BSIC Description >
0
0 | 1 < GPRS_REPORT PRIORITY Description >
0
0 | 1 < GPRS_Measurement_Parameters Description >
0
0 | 1 < NC Measurement Parameters >
0
0 | 1 < extension length >
0
0 | 1 < 3G Neighbour Cell Description >
1
0 | 1 < Index_Start_3G : bit (7) >
0
0 | 1 < Absolute_Index_Start_EMR : bit (7) >
0
0 | 1 < UTRAN FDD Description >
1
0 | 1 < Bandwidth_FDD : bit (3) >
0
1 < Repeated UTRAN FDD Neighbour Cells > ** 0
1
0 < FDD-ARFCN : bit (14) >
0 See TS 34.108, clause 6.1.5, table 6.1.1
< FDD_Indic0 : bit >
0
< NR_OF_FDD_CELLS : bit (5) >
‘00001’B
< FDD_CELL_INFORMATION Field >
10 bits
Scrambling code according to TS 34.108, clause 6.1.4, Default settings for cell No.1
1 < Repeated UTRAN FDD Neighbour Cells > ** 0
0
0 | 1 < UTRAN TDD Description >
0
0 | 1 < 3G MEASUREMENT Parameters Description >
< Qsearch_I : bit (4) >
‘0111’B (Always)
< Qsearch_C_Initial : bit (1) >
0
0 | 1 < FDD_Qoffset : bit (4) >
0
0 | 1 < FDD_MULTIRAT_REPORTING : bit (2) >
‘1 01’B (Report on 1 UTRAN cell)
0 | 1 < FDD_REPORTING_OFFSET : bit (3) >
0
0 | 1 < TDD_MULTIRAT_REPORTING : bit (2) >
0
0 | 1 < TDD_REPORTING_OFFSET : bit (3) >
0
0 | 1 < CDMA2000_MULTIRAT_REPORTING : bit (2) >
0
0 | 1 < CDMA2000_REPORTING_OFFSET : bit (3) >
0
0 | 1 < GPRS_3G_MEASUREMENT Parameters Description >
0
SYSTEM INFORMATION TYPE 2QUATER (M = 2)
Information Element
Value/remark
< RR management Protocol Discriminator bit (4) >
‘0110'B
< Skip Indicator : bit (4) >
‘0000'B
< Message type : bit (8) >
‘0000 0111’B
< SI2 quater Rest Octets >
< BA_IND : bit >
0
< 3G_BA_IND : bit >
0
< MP_CHANGE_MARK : bit >
0
< SI2quater _INDEX : bit (4) >
‘0000’B
< SI2quater_COUNT : bit (4) >
‘0000’B
0 | 1 < Measurement_Parameters Description >
0
0 | 1 < GPRS_Real Time Difference Description >
0
0 | 1 < GPSR_BSIC Description >
0
0 | 1 < GPRS_REPORT PRIORITY Description >
0
0 | 1 < GPRS_Measurement_Parameters Description >
0
0 | 1 < NC Measurement Parameters >
0
0 | 1 < extension length >
0
0 | 1 < 3G Neighbour Cell Description >
1
0 | 1 < Index_Start_3G : bit (7) >
0
0 | 1 < Absolute_Index_Start_EMR : bit (7) >
0
0 | 1 < UTRAN FDD Description >
0
0 | 1 < UTRAN TDD Description >
1
0 | 1 < Bandwidth_TDD : bit (3) >
1 ‘001’B
1 < Repeated UTRAN TDD Neighbour Cells > ** 0
1
0 < TDD-ARFCN : bit (14) >
0 See TS 34.108, clause 6.1.6, Table 6.1.6a
< TDD_Indic0 : bit >
1
< NR_OF_TDD_CELLS : bit (5) >
‘00001’B
< TDD_CELL_INFORMATION Field >
9 bits
Scrambling code according to TS 34.108, clause 6.1.4, Default settings for TDD cell No.1
1 < Repeated UTRAN TDD Neighbour Cells > ** 0
0
0 | 1 < 3G MEASUREMENT Parameters Description >
1
< Qsearch_I : bit (4) >
‘0111’B (Always)
< Qsearch_C_Initial : bit (1) >
0
0 | 1 < FDD_Qoffset : bit (4) >
0
0 | 1 < TDD_Qoffset : bit (4) >
1 ‘ 1111’B (Reselect UTRAN TDD cell when above 60dB)
< TDD_MULTIRAT_REPORTING : bit (2) >
’01’B (Report on 1 UTRAN cell)
0 | 1 < GPRS_3G_MEASUREMENT Parameters Description >
0
INTER SYSTEM TO UTRAN HANDOVER COMMAND
For M = 1:
Same as the default message contents in subclause 60.1 for M = 1 with the following exceptions:
Information Element
Value/remark
CHOICE specification mode
Preconfiguration
CHOICE preconfiguration mode
Default configuration
- Default configuration identity
1 (13.6 kbps signalling)
RAB information list
Not Present
For M = 2:
Same as the default message contents in subclause 60.2a for M = 2 using the configuration defined in TS 34.108 [149] clause 6.10.2.4.1.2:
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
60.4.5 Test requirement
|
At step 5 the MEASUREMENT REPORT should include details of the UTRAN cell. At step 10 a HANDOVER TO UTRAN COMPLETE command should be received on DCCH of the UTRAN cell.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
60.5 Inter system handover to UTRAN/From GSM/Speech/Blind HO/Success
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
60.5.1 Definition
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
60.5.2 Conformance requirement
|
The MS shall be able to receive a INTER SYSTEM TO UTRAN HANDOVER COMMAND message from GSM and perform an inter-system handover, even if no prior MS measurements have been performed on the target UTRAN cell and/or frequency.
If the MS succeeds to establish the connection to UTRAN, it shall transmit a HANDOVER TO UTRAN COMPLETE message on the uplink DCCH.
Reference(s)
3GPP TS 25.331 subclause 8.3.6.
3GPP TS 04.18 subclause 3.4.4a.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
60.5.3 Test purpose
|
To test that the MS handovers from the GSM serving cell to the indicated channel of UTRAN target cell when it is in the speech call active state without any knowledge of the target system (blind handover) and receives an INTER SYSTEM TO UTRAN HANDOVER COMMAND.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
60.5.4 Method of test
|
Initial conditions
2 cells - Cell 1 is GPRS, Cell 2 is UTRAN (cell conditions favour the GPRS cell).
The present document subclause 40 shall be referenced for the default parameters of cell 1, and subclause 26.6.5.1 shall be referenced for cell allocation.
3GPP TS 34.108 subclause 6.1 shall be referred to for default parameters of Cell 2.
MS:
"idle, updated", channel released mode with TMSI allocated.
For MS supporting GPRS:
The MS is GPRS attached with a P-TMSI allocated, SPLIT PG CYCLE negotiated.
Specific PICS statements
-
PIXIT statements
-
Foreseen final state of the MS
The MS is in CC state U10 on cell 2.
Test Procedure
No SYSTEM INFORMATION TYPE 2quarter or MEASUREMENT INFORMATION indicating presence of the UTRAN cell are broadcasted in the GSM cell. The SS brings the MS into the call active state (CC state U10) with FR speech. The SS configures a dedicated channel (conversationa/speech/UL:12.2 DL:12.2 kbps/CS RAB + UL:3.4 DL3.4 kbps SRBS), then sends INTER SYSTEM TO UTRAN HANDOVER COMMAND indicating the dedicated channel of the target cell to the MS through the GSM serving cell. After the MS receives the command it shall configure itself accordingly and switch to the dedicated channel of UTRAN cell. The SS checks whether the handover is performed by checking that the MS transmits HANDOVER TO UTRAN COMPLETE to the SS through DCCH of the UTRAN cell.
Expected sequence
Step
Direction
Message
Comments
MS
SS
1
MS
The SS bring the MS into GSM U10 state in cell 1, on a hopping traffic channel, and the MS has no pre-configuration information stored or received any information of presence of the UTRAN cell.
2
SS
The SS configures dedicated channel with the configuration: conversational/speech/UL:12.2 DL:12.2 kbps/CS RAB + UL:3.4 DL3.4 kbps SRBs in UTRAN cell.
3
INTER SYSTEM TO UTRAN HANDOVER COMMAND
Send on cell 1 (GSM cell)
4
MS
The MS accepts the handover command and configures its lower layers using the parameters contained in the INTER SYSTEM TO UTRAN HANDOVER COMMAND
5
SS
The SS waits for uplink physical channel in synchronization
6
HANDOVER TO UTRAN COMPLETE
The SS receives this message on DCCH of cell 2 (UTRAN cell). It implies that the down link physical channel has synchronised with UTRAN.
Specific message contents
INTER SYSTEM TO UTRAN HANDOVER COMMAND
Same as the specific message contents in subclause 60.1 for M = 1.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
60.5.5 Test requirement
|
At step 6 the HANDOVER TO UTRAN COMPLETE shall be received on UTRAN cell.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
60.6 Inter system handover to UTRAN/From GSM/Speech/Failure
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
60.6.1 Definition
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
60.6.2 Conformance requirement
|
The MS shall be able to receive a INTER SYSTEM TO UTRAN HANDOVER COMMAND message from GSM and perform an inter-system handover.
If the MS can not establish the connection to UTRAN, it shall reactivate the old channel and transmit a HANDOVER FAILURE message on the old channel.
Reference(s)
3GPP TS 25.331 subclause 8.3.6.
3GPP TS 04.18 subclause 3.4.4a.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
60.6.3 Test purpose
|
To test that the MS reactivates the old channel and transmits HANDOVER FAILURE message to the network on the old channel in the GSM cell when it received INTER SYSTEM TO UTRAN HANDOVER COMMAND towards a non-existing UTRAN cell.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
60.6.4 Method of test
|
Initial conditions
System Simulator:
2 cells - Cell 1 is GPRS, Cell 2 is UTRAN (cell selection conditions in favour of the GPRS cell).
The present document subclause 40 shall be referenced for the default parameters of cell 1, and subclause 26.6.5.1 shall be referenced for cell allocation.
3GPP TS 34.108, subclause 6.1 will be referenced for the default parameters of Cell 2.
MS:
"idle, updated", channel released mode with TMSI allocated.
For MS supporting GPRS:
The MS is GPRS attached with a P-TMSI allocated, SPLIT PG CYCLE negotiated.
Specific PICS statements
-
PIXIT statements
-
Foreseen final state of the MS
The MS is in CC state U10 on cell 1.
Test Procedure
The SS brings the MS into the call active state (CC state U10) with FR speech call. The SS does not configure a dedicated channel corresponding to the default configuration 3. The SS sends a MEASUREMENT INFORMATION to trigger the MS to perform measurements on the UTRAN cell. The SS verifies that the MS include the UTRAN cell in the MEASUREMENT REPORT and, then sends INTER SYSTEM TO UTRAN HANDOVER COMMAND indicating the dedicated channel of the target cell to the MS through the GSM serving cell. The MS will not be able to establish the connection to UTRAN dedicated channel. The SS checks that the handover is failed by checking that the MS returns to the old channel and transmits HANDOVER FAILURE to the SS through the old channel.
Expected sequence
Step
Direction
Message
Comments
MS
SS
1
MS
The SS brings the MS into GSM U10 state in cell 1 on a hopping traffic channel
2
SS
The SS configures the Physical channel of the UTRAN cell but here is no dedicated channel with the configuration: conversational/speech/UL:12.2 DL:12.2 kbps/CS RAB + UL:3.4 DL3.4 kbps SRBs in UTRAN cell.
3
MEASUREMENT INFORMATION
4
MEASUREMENT REPORT
Including Measurement Results on the UTRAN cell in Step 4
5
INTER SYSTEM TO UTRAN HANDOVER COMMAND
Send on cell 1 (GSM cell)
6
MS
The MS accepts the handover command and configures its lower layers using the parameters contained in the INTER SYSTEM TO UTRAN HANDOVER COMMAND
7
MS
The MS fails to configure to the indicated RAB in Step 6 and fails to establish a connection to UTRAN cell
8
HANDOVER FAILURE
The SS receives this message on DCCH of cell 1 (old channel in GSM cell)
Specific message contents
Same as the specific message contents in subclause 60.1 for M = 1.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
60.6.5 Test requirement
|
At step 8 the HANDOVER FAILURE shall be received on GSM cell.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
60.7 Inter system handover to UTRAN/From GSM/Failure/Cause: Frequency not implemented
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
60.7.1 Definition
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
60.7.2 Conformance requirement
|
The MS shall be able to receive a HANDOVER TO UTRAN COMMAND message from GSM and perform an inter‑system handover, even if no prior MS measurements have been performed on the target UTRAN cell and/or frequency.
The HANDOVER TO UTRAN COMMAND message instructs the mobile station to use frequency that it is not capable of, and then the MS shall return a HANDOVER FAILURE message with cause "frequency not implemented" (Reference 3GPP TS 04.18 subclause 3.4.4a.3).
Reference(s)
3GPP TS 25.331 subclause 8.3.6.
3GPP TS 04.18 subclause 3.4.4a.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
60.7.3 Test purpose
|
To test that the MS reactivates the old channel and transmits HANDOVER FAILURE message to the network on the old channel in the GSM cell when it received HANDOVER TO UTRAN COMMAND and the handover to UTRAN failed because of frequency not implemented.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
60.7.4 Method of test
|
Initial conditions
System Simulator:
2 cells - Cell 1 is GSM, Cell 2 is UTRAN. TS 51.010-1 subclause 26.6.5.1 shall be referenced for the default parameters of Cell 1.
MS:
CC State U10 in cell 1.
Specific PICS statements
-
PIXIT statements
-
Foreseen final state of the MS
The MS is in CC state U10 on cell 1.
Test Procedure:
The SS starts the GSM cell and UTRAN cell with the cell selection condition in favour of GSM cell. The MS selects the GSM cell.
SS brings the MS into the call active state (CC state U10) with FR speech call. The SS configures the dedicated channel corresponding to the default configuration (conversational/speech/uplink: 12.2 DL: 12.2 kbps/CS RAB + uplink: 3.4 DL3.4 kbps SRBS), then sends HANDOVER TO UTRAN COMMAND the MS through the GSM serving cell. The HANDOVER TO UTRAN COMMAND message instructs the mobile station to use frequency that it is not capable of, and then the MS shall return a HANDOVER FAILURE message with cause "frequency not implemented" (Reference 3GPP TS 04.18 subclause 3.4.4a.3) and continue the voice call on the old channel.
Expected sequence
Step
Direction
Message
Comments
MS
SS
1
SS
The SS starts GSM and UTRAN cells; the UTRAN cell broadcasts SIB16 containing pre-configuration information. MS camps on GSM cell and received SIB 16 from UTRAN cell.
2
MS
The SS brings the MS into GSM U10 state in cell 1.
3
SS
The SS configures dedicated channel with the configuration: conversational/speech/uplink:12.2 DL:12.2 kbps/CS RAB + uplink:3.4 DL3.4 kbps SRBs in UTRAN cell.
4
HANDOVER TO UTRAN COMMAND
Handover message is sent on cell 1 (GSM cell) with unsupported frequency.
5
MS
The MS fails to establish a connection to UTRAN cell
6
HANDOVER FAILURE
The SS receives this message on DCCH of cell 1 (old channel in GSM cell) with RR Cause "frequency not implemented".
Specific message contents
Same as the specific message contents in subclause 60.1 for M = 1 except that the INTER SYSTEM TO UTRAN HANDOVER COMMAND indicates a frequency not supported by the MS.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
60.7.5 Test requirement
|
At step 7 the HANDOVER FAILURE shall be received on GSM cell.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
60.8 Inter system handover to UTRAN/From GSM/Failure/Cause: UTRAN configuration unknown
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
60.8.1 Definition
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
60.8.2 Conformance requirement
|
The MS shall be able to receive a HANDOVER TO UTRAN COMMAND message from GSM and perform an inter-system handover, even if no prior MS measurements have been performed on the target UTRAN cell and/or frequency. The HANDOVER TO UTRAN COMMAND message instructs the mobile station to use preconfiguration that the mobile station has not read or instruct to use default reconfiguration not implemented by MS, then the MS shall return a HANDOVER FAILURE message with cause "UTRAN configuration unknown" (3GPP TS 04.18 subclause 3.4.4a.3).
Reference(s)
3GPP TS 25.331 subclause 8.3.6.
3GPP TS 04.18 subclause 3.4.4a.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
60.8.3 Test purpose
|
To test that the MS reactivates the old channel and transmits HANDOVER FAILURE message to the network on the old channel in the GSM cell when it receives HANDOVER TO UTRAN COMMAND and the handover to UTRAN failed because of UTRAN configuration unknown.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
60.8.4 Method of test
|
Initial conditions
System Simulator:
2 cells - Cell 1 is GSM, Cell 2 is UTRAN. TS 51.010-1section 26.6.5.1 shall be referenced for the default parameters of cell 1.
MS:
CC State U10 in cell.
Specific PICS statements
-
PIXIT statements
-
Foreseen final state of the MS
The MS is in CC state U10 on cell 1.
Test Procedure
The SS starts the GSM cell and UTRAN cell with the cell selection condition in favour of GSM cell, SIB16 is not broadcast in UTRAN cell and MS has no predefined configuration stored.
The MS selects the GSM cell. SS brings the MS into the call active state (CC state U10) with FR speech call. The SS configures a dedicated channel (conversational/speech/uplink: 12.2 DL: 12.2 kbps/CS RAB + uplink: 3.4 DL3.4 kbps SRBS). The SS sends a HANDOVER TO UTRAN COMMAND message through the GSM cell that instructs the MS to use a preconfiguration that the mobile station has not read or instructed to use default configuration not implemented by MS. The MS shall return a HANDOVER FAILURE message with cause "UTRAN preconfiguration unknown" and continue the voice call on the old cell.
Expected sequence
Step
Direction
Message
Comments
MS
SS
1
SS
The SS starts GSM and UTRAN cells; SIB16 is not broadcast in the UTRAN cell.
2
MS
The SS brings the MS into GSM U10 state in cell 1and MS has not any pre-configuration stored.
3
SS
The SS configures dedicated channel with the configuration: conversational/speech/uplink:12.2 DL:12.2 kbps/CS RAB + uplink:3.4 DL3.4 kbps SRBs in UTRAN cell.
4
HANDOVER TO UTRAN COMMAND
Handover message is sent on cell 1 (GSM cell) with unknown preconfiguration.
5
MS
The MS fails to establish a connection to UTRAN cell
6
HANDOVER FAILURE
The SS receives this message on DCCH of cell 1 (old channel in GSM cell) with RR Cause "UTRAN configuration unknown".
Specific message contents
INTER SYSTEM TO UTRAN HANDOVER COMMAND
Information Element
Value/remark
RR management Protocol Discriminator
‘0110'B
Skip Indicator
‘0000'B
Inter System to UTRAN Handover Command Message Type
‘01100011'B
Handover to UTRAN Command IEI
TBD
Length of Handover to UTRAN Command contents
Octet length of the "Handover to UTRAN Command value part"
Handover to UTRAN Command value part
PER encoded ASN.1 value of type "HandoverToUTRANCommand-v1-IEs", content is presented in the next table.
Content of "HandoverToUTRANCommand-r3-IEs"
Information Element
Value/remark
New U-RNTI
- SRNC Identity
‘000000000001'B
- S-RNTI-2
1
Activation time
now
Ciphering algorithm
Standard UMTS Encryption Algorithm UEA1
CHOICE Specification mode
Preconfiguration
- Predefined configuration identity
1
- RAB Info
- RAB identity
- GSM-MAP RAB identity
‘00000001'B
- CN domain identity
CS domain
- CHOICE Mode specific info
FDD
- uplink DPCH info
- uplink DPCH power control info
- DPCCH power offset
-6dB
- PC Preamble
1 frame
- SRB delay
7 frames
- Scrambling code type
long
- Reduced scrambling code number
0
- Spreading factor
16
- DL common information post
- DL DPCH info common
- DL DPCH power control info
- CHOICE Mode specific info
FDD
- DPC mode
Single TPC
- DL information perRL list
- Primary CPICH info
- Primary scrambling code
100
- DL DPCH info perRL
- pCPICH usage for channelEst
May be used
- DL channelization code
- Secondary scrambling code
1
- SF and code number
SF = 32, code number = 31
- Scrambling code change
No code change
- TPC combination index
0
- Frequency info
- UARFCN uplink(Nu)
See PIXIT
- UARFCN downlink(Nd)
See PIXIT
Maximum allowed uplink TX power
33dBm
HANDOVER FAILURE message content
Information element
Value/remark
RR management Protocol Discriminator
‘0110'B
Skip Indicator
‘0000'B
Handover Failure Message Type
‘00101000'B
RR Cause
RR Cause (Refer : table 10.5.2.31.1/3GPP TS 04.18: RR Cause information element)
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
60.8.5 Test requirement
|
At step 7 the HANDOVER FAILURE shall be received on GSM cell.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
60.9 Inter system handover to UTRAN/From GSM/Failure/Cause: Protocol Error
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
60.9.1 Definition
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
60.9.2 Conformance requirement
|
The MS shall be able to receive a HANDOVER TO UTRAN COMMAND message from GSM and perform an inter‑system handover, even if no prior MS measurements have been performed on the target UTRAN cell and/or frequency. The HANDOVER TO UTRAN COMMAND message, which contains a protocol error causing the variable PROTOCOL_ERROR_REJECT to be set TRUE according to subclause 9 of 3GPP TS 25.331.
3GPP TS 04.18 subclause 8.5
When on receipt of a message,
- an "imperative message part" error; or
- a "missing mandatory IE" error
is diagnosed or when a message containing:
- a syntactically incorrect mandatory IE; or
- an IE unknown in the message, but encoded as "comprehension required" (see clause 3GPP TS 24.007); or
- an out of sequence IE encoded as "comprehension required" (see clause 3GPP TS 24.007)
is received,
- the mobile station shall proceed as follows:
If the message is not one of the messages listed in clauses 8.5.1, 8.5.2, 8.5.3 the mobile station shall ignore the message except for the fact that, if an RR connection exists, it shall return a status message (RR STATUS) with cause # 96 "Invalid mandatory information".
Reference(s)
3GPP TS 25.331 subclause 8.3.6 and 9.
3GPP TS 04.18 subclause 3.4.4a and 8.5.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
60.9.3 Test purpose
|
To test that the MS reactivates the old channel and transmits RR Status message to the network on the old channel in the GSM cell when it receives HANDOVER TO UTRAN COMMAND and the handover to UTRAN failed because of protocol error.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
60.9.4 Method of test
|
Initial conditions
System Simulator:
2 cells - Cell 1 is GSM, Cell 2 is UTRAN. TS 51.010-1 section 26.6.5.1 shall be referenced for the default parameters of cell 1.
MS:
CC State U10 in cell 1.
Specific PICS statements
-
PIXIT statements
-
Foreseen final state of the MS
The MS is in CC state U10 on cell 1.
Test Procedure
The SS starts the GSM cell and UTRAN cell with the cell selection condition in favour of GSM cell. The MS selects the GSM cell. SS brings the MS into the call active state (CC state U10) with FR speech call. The SS configures the dedicated channel corresponding to the default configuration 3 (conversational/speech/uplink: 12.2 DL: 12.2 kbps/CS RAB + uplink: 3.4 DL3.4 kbps SRBS), then sends HANDOVER TO UTRAN COMMAND indicating the dedicated channel of the target cell to the MS through the GSM serving cell.
The SS sends a HANDOVER TO UTRAN COMMAND message, that contains a protocol error causing the variable PROTOCOL_ERROR_REJECT to be set TRUE according to 3GPP TS 25.331 subclause 9. Then the MS shall return an RR STATUS message on DCCH of cell 1 (old channel in GSM cell) with RR cause #96 “Invalid mandatory information”.
Expected sequence
Step
Direction
Message
Comments
MS
SS
1
SS
The SS starts GSM and UTRAN cells; The MS camps on GSM cell
2
MS
The SS brings the MS into GSM U10 state in cell 1
3
SS
The SS configures dedicated channel with the configuration: conversational/speech/uplink:12.2 DL:12.2 kbps/CS RAB + uplink:3.4 DL3.4 kbps SRBs in UTRAN cell.
4
HANDOVER TO UTRAN COMMAND
Handover message is sent on cell 1 (GSM cell) with missing mandatory IE.
5
RR STATUS
The SS receives this message on DCCH of cell 1 (old channel in GSM cell) with RR cause #96 "Invalid mandatory information".
Specific message contents
Same as the specific message contents in subclause 60.1 for M = 1 except that in the INTER SYSTEM TO UTRAN HANDOVER COMMAND a mandatory IE is missing causing a protocol error.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
60.9.5 Test requirement
|
At step 5 the RR STATUS shall be received on GSM cell.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
60.10 Inter system handover to UTRAN/From GSM/Integrity Protection Activation
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
60.10.1 Definition
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
60.10.2 Conformance requirement
|
The MS shall include the Security START values in INTER RAT HANDOVER INFO in the RR message UTRAN CLASSMARK CHANGE -definition and in the RRC message HANDOVER TO UTRAN COMPLETE.
If the MS succeeds to establish the connection to UTRAN after reception of an INTERSYSTEM TO UTRAN HANDOVER COMMAND, the NW may start Integrity protection using the previously received CS START value by sending a SECURITY MODE COMMAND message to the MS.
Reference(s)
3GPP TS 25.331 subclause 8.1.12 and 8.3.6.
3GPP TS 04.18 subclause 3.4.4a and 3.4.11.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
60.10.3 Test purpose
|
To test that MS supporting both GSM and UTRAN applies the correct CS Security START value after a successful handover from GSM to UTRAN when Integrity protection is activated by the NW.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
60.10.4 Method of test
|
Initial conditions
System Simulator:
2 cells - Cell 1 is GSM, Cell 2 is UTRAN.
The present document subclause 40 shall be referenced for the default parameters of cell 1, and subclause 26.6.5.1 shall be referenced for cell allocation.
3GPP TS 34.108, subclause 6.1 shall be referenced for default parameters of Cell 2.
Mobile Station:
"idle, updated", channel released mode with TMSI allocated.
For MS supporting GPRS:
The MS is GPRS attached with a P-TMSI allocated, SPLIT PG CYCLE negotiated.
Specific PICS statements
-
PIXIT statements
-
Foreseen final state of the MS
The MS is in CC state U10 on cell 2.
Test Procedure
The SS brings the MS into the call active state (CC state U10) with FR speech call.
The SS starts the UTRAN cell, configures the UTRAN dedicated channel corresponding to default handover configuration 3 and sends a MEASUREMENT INFORMATION to trigger the MS to perform measurements on the UTRAN cell.
The SS verifies that the MS includes the UTRAN cell in the MEASUREMENT REPORT. The SS then sends a CLASSMARK ENQUIRY requesting an UTRAN CLASSMARK CHANGE from the MS. The MS responds with a UTRAN CLASSMARK CHANGE and the SS verifies that the INTER RAT HANDOVER INFO includes a START value for the CS domain.
The SS sends an INTERSYSTEM TO UTRAN HANDOVER COMMAND indicating the dedicated channel of the target cell to the MS. After the MS receives the command, it shall switch to the dedicated channel of the UTRAN cell. The SS checks whether the handover is performed by checking that the MS transmits HANDOVER TO UTRAN COMPLETE to the SS through DCCH of the UTRAN cell. It is also verified that the START value for the CS domain in the HANDOVER TO UTRAN COMPLETE message is the same as the START value received in the INTER RAT HANDOVER INFO.
The SS attempts to activate Integrity protection by sending an Integrity protected SECURITY MODE COMMAND on the DCCH with an incorrect IE “Integrity check info”. It is verified that the MS does not respond with a SECURITY MODE COMPLETE message.
The SS retransmits the SECURITY MODE COMMAND on the DCCH with a correct IE Integrity Check Info and the MS responds with an Integrity protected SECURITY MODE COMPLETE. Both SS and MS shall use the START value for the CS domain for Integrity protection that the MS has indicated in UTRAN CLASSMARK CHANGE and HANDOVER TO UTRAN COMPLETE.
Expected sequence
Step
Direction
Message
Comments
MS
SS
1
MS – SS
The SS brings the MS into GSM U10 state in cell 1 on a hopping traffic channel
2
SS
The SS configures the UTRAN cell with a dedicated channel configuration: conversational/speech/UL:12.2 DL:12.2 kbps/CS RAB + UL:3.4 DL3.4 kbps SRBs in UTRAN cell (default handover configuration 3).
The following messages are sent and received on the GSM cell
3
MEASUREMENT INFORMATION
4
MEASUREMENT REPORT
Including Measurement Results on the UTRAN cell in Step 4.
5
CLASSMARK ENQUIRY
6
UTRAN CLASSMARK CHANGE
Verify that the ue-SecurityInformation is present.
7
INTERSYSTEM TO UTRAN HANDOVER COMMAND
8
MS
The MS accepts the handover command and configures its lower layers using the parameters contained in the INTERSYSTEM TO UTRAN HANDOVER COMMAND
9
SS
The SS waits for uplink physical channel in synchronization
The following messages are sent and received on the UTRAN cell.
10
HANDOVER TO UTRAN COMPLETE
Received on DCCH of the UTRAN cell.
Verify that the same CS-domain START-Value is indicated as in step 6.
11
SECURITY MODE COMMAND
Integrity protected with a different CS-domain START value than the indicated in step 6 is applied.
12
SS
Verify that no SECURITY MODE COMPLETE is sent by the MS for 5 sec.
13
SECURITY MODE COMMAND
Integrity protected with the CS-domain START value indicated in step 6 is applied.
14
SECURITY MODE COMPLETE
Verify that Integrity protection is applied using the CS-domain START value indicated in step 6.
Specific message contents
MEASUREMENT INFORMATION in Step 3
Same as in 60.1
CLASSMARK ENQUIRY message in Step 5
Information Element
Value/remark
Protocol Discriminator
RR management
Skip Indicator
‘0000’B
Message Type
Classmark Enquiry
Classmark Enquiry Mask
Classmark Enquiry Mask IEI
‘00010000’B
Length of Classmark Enquiry Mask contents
‘00000001’B
Classmark Enquiry Mask value part
‘10001000’B Note
Note CLASSMARK CHANGE message is not requested;
UTRAN CLASSMARK CHANGE message is requested;
CDMA2000 CLASSMARK CHANGE message is not requested
UTRAN CLASSMARK CHANGE message in step 6
Information Element
Value/remark
Protocol Discriminator
RR management
Skip Indicator
‘0000’B
Message Type
UTRAN ‘Classmark Change
UTRAN Classmark
Length of UTRAN Classmark
Length of INTER RAT HANDOVER INFO
UTRAN Classmark value part
INTER RAT HANDOVER INFO
InterRATHandoverInfo
RR management
PredefinedConfigurationStatusList
(Optional) Not checked
ue-SecurityInformation
Checked that the IE is present
start-CS
20 bits
…
Rest of message not checked
INTER SYSTEM TO UTRAN HANDOVER COMMAND message in Step 7
Same content as in 60.1
HANDOVER TO UTRAN COMPLETE message in step 10
Information Element
Value/remark
UL-DCCH-Message
IntegrityCheckInfo
Not defined
Message
handoverToUTRANComplete
HandoverToUTRANComplete
StartList
[0]
cn-DomainIdentity
cs –domain Checked that IE is present
start-Value
20 bits
[1]
cn-DomainIdentity
ps-domain Not checked
start-Value
20 bits
…
-
SECURITY MODE COMMAND message AM, in step 11
Information Element
Value/remark
Message Type
RRC transaction identifier
Arbitrarily selects an integer between 0 and 3
Integrity check info
- Message authentication code
Set to MAC-I value computed by the SS using a different START value for the CS domain from the indicated in the INTER RAT HANDOVER INFO. The first/ leftmost bit of the bit string contains the most significant bit of the MAC-I.
UE system specific security capability
- Inter-RAT UE security capability
- CHOICE system
GSM
- GSM security capability
The indicated algorithms must be the same as the algorithms supported by the UE as indicated in the IE " Mobile station classmark 2 " in the LOCATION UPDATING REQUEST message.
SECURITY MODE COMMAND message AM, in step 13
Information Element
Value/remark
Message Type
RRC transaction identifier
Arbitrarily selects an integer between 0 and 3
Integrity check info
- Message authentication code
Set to MAC-I value computed by the SS using the indicated START value for the CS domain from the INTER RAT HANDOVER INFO. The first/ leftmost bit of the bit string contains the most significant bit of the MAC-I.
UE system specific security capability
- Inter-RAT UE security capability
- CHOICE system
GSM
- GSM security capability
The indicated algorithms must be the same as the algorithms supported by the UE as indicated in the IE " Mobile station classmark 2 " in the LOCATION UPDATING REQUEST message.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
60.10.5 Test requirement
|
After step 14, the ongoing call shall continue on UTRAN cell with Integrity protection using the CS Security START value indicated in the UTRAN CLASSMARK CHANGE.
61-69 Void
70 Location Services
This sub clause contains test cases for Location Services (LCS).
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.