hash
stringlengths 32
32
| doc_id
stringlengths 5
12
| section
stringlengths 4
595
| content
stringlengths 0
6.67M
|
|---|---|---|---|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.8.2.1.1 Conformance requirements
|
The MS can request the use of power saving mode (PSM) during an attach or routing area updating procedures (see 3GPP TS 23.682 [133A] and 3GPP TS 23.060 [74]). The MS shall not request the use of PSM during:
- an attach for emergency bearer services procedure;
- a routing area updating procedure for initiating a PDN connection for emergency bearer services; or
- a routing area updating procedure when the MS has a PDN connection established for emergency bearer services.
…
The MS can request the use of extended idle mode DRX cycle (eDRX) during an attach or routing area updating procedure by including the extended DRX parameters IE (see 3GPP TS 23.682 [11A] and 3GPP TS 23.060 [74]). The MS shall not request the use of eDRX during:
- an attach for emergency bearer services procedure;
- a routing area updating procedure for initiating a PDN connection for emergency bearer services; or
- a routing area updating procedure when the MS has a PDN connection established for emergency bearer services.
…
The mobile station in packet idle mode is required to receive and analyse the paging messages and immediate assignment messages sent on the paging subchannels on EC-CCCH corresponding to the paging groups determined for it in packet idle mode, as specified in 3GPP TS 45.002. The messages sent on EC-CCCH may contain an EC-GSM-IoT Page Extension field.
….
A mobile station that has enabled EC operation where eDRX is used wakes up to read its nominal paging group according to its negotiated eDRX cycle (see 3GPP TS 45.002) when in Idle mode and the Ready timer is not running or supports reachability while the Ready timer is running using the lowest eDRX. If it receives a matching paging message therein it shall act on it as described in sub-clause 3.5.1.2. Otherwise, if it receives any other message and the EC-EGPRS Page Extension field is included therein (sub-clause 9.1.60), it shall proceed as follows:
…
A MS that has enabled EC operation where PSM with eDRX is used supports reachability while in packet idle mode when the Ready timer or Active timer is running as described in sub-clause 3.9.2 for the case of a mobile station that uses PEO with PSM and eDRX A MS that has enabled EC operation where PSM without eDRX is used supports reachability while the Active timer is running using the lowest eDRX cycle.
References
3GPP TS 24.008, subclauses 4.7.2.9 and 4.7.2.10
3GPP TS 44.018, subclauses 3.5.1a, 3.5.1a.1, 3.5.2.1.2, 3.10.1, 3.10.2
3GPP TS 45.002, subclause 6.5.6a.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.8.2.1.2 Test purpose
|
1. To verify that the mobile station in packet idle mode can receive and analyse the paging messages sent on the paging subchannels on EC-CCCH
2. To verify that the mobile station can activate both PSM and eDRX when in EC operation.
3. To verify that the mobile station that has enabled EC operation with both PSM and eDRX is reachable with the eDRX cycle negotiated during the PSM active timer.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.8.2.1.3 Method of test
|
Initial Conditions
System Simulator:
- 1 cell, EC-GSM-IoT, PSM and eDRX supported
Mobile Station:
- The MS is switched off.
Specific PICS Statements
-
PIXIT Statements
-
Test Procedure
The MS is triggered to initiate the GPRS attach procedure on an EC-GSM-IoT capable Cell but does not include eDRX or PSM related parameters in the GPRS Attach Request. The SS checks that the MS does not indicate any value for eDRX.
Once the device is GPRS attached, in packet idle mode with Ready Timer expired the SS pages the MS according to the lowest eDRX cycle. There should be no answer from the MS as the MS has not negotiated the use of an eDRX cycle (i.e. the MS is unreachable when the neither the Ready timer nor Active timer is running).
The MS is then paged according to the lowest eDRX cycle and should answer the Paging Request. The Paging request contains the EC-GSM-IoT Page Extension IE set to CC1. The SS reject the MS access.
The MS is then paged according to the second lowest eDRX cycle and should answer the Paging Request.
Expected Sequence
Step
Direction
Message
Comments
1
MS
The MS is turned on and triggered to initiate the GPRS attach procedure
2
MS -> SS
EC PACKET CHANNEL REQUEST
DL Coverage Class: CC1
3
SS -> MS
EC IMMEDIATE ASSIGNMENT TYPE 2
Request Reference = pertaining to the message received in step 2. Fixed link assignment, sent on EC-AGCH
4
MS -> SS
UPLINK RLC DATA BLOCKS
Transporting: ATTACH REQUEST
5
SS -> MS
EC PACKET UPLINK ACK/NACK
acknowledge the received RLC data block, Final Ack Indicator = ‘1’ , a valid RRBP. Sent on EC-PACCH
6
MS -> SS
EC PACKET CONTROL ACKNOWLEDGEMENT
acknowledge the RLC data. Received on EC-PACCH
7
SS -> MS
EC IMMEDIATE ASSIGNMENT TYPE 2
For downlink TBF, sent 1 s. after step 6 on EC-AGCH
8
SS -> MS
DOWNLINK RLC DATA BLOCKS
Transporting:
ATTACH ACCEPT.
Last block containing a valid RRBP field and FBI set.
9
MS -> SS
EC PACKET DOWNLINK ACK/NACK
Not including Channel Request Description
10
MS -> SS
EC PACKET CHANNEL REQUEST
Received on EC-RACH
11
SS -> MS
EC IMMEDIATE ASSIGNMENT TYPE 2
Request Reference = pertaining to the message received in step 10. Fixed link assignment, sent on EC-AGCH
11
MS -> SS
UPLINK RLC DATA BLOCKS
Transporting:
ATTACH COMPLETE
12
SS -> MS
PACKET UPLINK ACK/NACK
Including valid RRBP field
13
MS -> SS
PACKET CONTROL ACKNOWLEDGMENT
14
Wait for 1 minute for Ready Timer to expire
15
SS -> MS
EC PAGING REQUEST
Packet page indication indicates packet paging procedure. Sent on EC-PCH according to the second lowest eDRX cycle
16
There Should be no response from MS as the eDRX Cycle is set to the lowest eDRX cycle. This is verified for the duration of T3315
17
SS -> MS
EC PAGING REQUEST
Packet page indication indicates packet paging procedure. Sent on EC-PCH according to the lowest eDRX cycle
Including the EC-EGPRS Page Extension IE set to '1 X X X'
18
MS -> SS
EC PACKET CHANNEL REQUEST
received on EC-RACH
19
SS -> MS
EC IMMEDIATE ASSIGNMENT REJECT
Request Reference = pertaining to the message received in step 18.
Sent on EC-AGCH.
20
SS -> MS
EC PAGING REQUEST
Packet page indication indicates packet paging procedure. Sent on EC-PCH according to the second lowest eDRX cycle
21
MS -> SS
EC PACKET CHANNEL REQUEST
received on EC-RACH
Specific Message Contents
-
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.8.2.2 EC-GSM-IoT / Paging / normal paging / with eDRX or eDRX and PSM
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.8.2.2.1 Conformance requirements
|
The MS can request the use of power saving mode (PSM) during an attach or routing area updating procedures (see 3GPP TS 23.682 [133A] and 3GPP TS 23.060 [74]). The MS shall not request the use of PSM during:
- an attach for emergency bearer services procedure;
- a routing area updating procedure for initiating a PDN connection for emergency bearer services; or
- a routing area updating procedure when the MS has a PDN connection established for emergency bearer services.
…
The MS can request the use of extended idle mode DRX cycle (eDRX) during an attach or routing area updating procedure by including the extended DRX parameters IE (see 3GPP TS 23.682 [11A] and 3GPP TS 23.060 [74]). The MS shall not request the use of eDRX during:
- an attach for emergency bearer services procedure;
- a routing area updating procedure for initiating a PDN connection for emergency bearer services; or
- a routing area updating procedure when the MS has a PDN connection established for emergency bearer services.
…
The mobile station in packet idle mode is required to receive and analyse the paging messages and immediate assignment messages sent on the paging subchannels on EC-CCCH corresponding to the paging groups determined for it in packet idle mode, as specified in 3GPP TS 45.002. The messages sent on EC-CCCH may contain an EC-EGPRS Page Extension field.
….
A mobile station that has enabled EC operation where eDRX is used wakes up to read its nominal paging group according to its negotiated eDRX cycle (see 3GPP TS 45.002) or the lowest eDRX cycle if it has not negotiated the use of PSM or eDRX. If it receives a matching paging message therein it shall act on it as described in sub-clause 3.5.1.2. Otherwise, if it receives any other message and the EC-EGPRS Page Extension field is included therein (sub-clause 9.1.60), it shall proceed as follows:
…
A MS that has enabled EC operation where PSM with eDRX is used supports reachability while in packet idle mode when the Ready timer or Active timer is running as described in sub-clause 3.9.2 for the case of a mobile station that uses PEO with PSM and eDRX except that the MS always uses the lowest eDRX cycle when the Ready timer is running.
References
3GPP TS 24.008, subclauses 4.7.2.9 and 4.7.2.10
3GPP TS 44.018, subclauses 3.5.1a, 3.5.1a.1, 3.5.2.1.2, 3.10.1, 3.10.2
3GPP TS 45.002, subclause 6.5.6a.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.8.2.2.3 Method of test
|
Initial Conditions
System Simulator:
- 1 cell, EC-GSM-IoT, PSM and eDRX supported
Mobile Station:
- The MS is switched off.
Specific PICS Statements
• Support of PSM (TSPC_PSM)
PIXIT Statements
-
Test Procedure
The MS is triggered to initiate the GPRS attach procedure on an EC-GSM-IoT (eDRX & PSM) capable Cell. The MS send either eDRX only or both PSM and eDRX values in the ATTACH REQUEST.
Either eDRX or both PSM and eDRX values are sent by the SS, depending on what the MS sent in the ATTACH REQUEST, as well as the DL CC received by the SS during the GPRS attach procedure (i.e. EC operation is enabled). The eDRX value shall not be the lowest eDRX value but shall be selected so that only one eDRX cycle fits within the time period determined by the Active timer (T3324).
Once the device is GPRS attached, in packet idle mode with Ready Timer expired the SS pages the MS according to the lowest eDRX cycle. There should be no answer from the MS as the eDRX cycle negotiated is higher.
The MS is then paged according to its negotiated eDRX cycle and should answer the Paging Request. The SS reject the MS access.
When the T3324 timer expire the MS is paged according to its negotiated eDRX cycle. If the MS indicated that PSM is supported there should be no answer from the MS.
Maximum Duration of Test
13 minutes.
Expected Sequence
Step
Direction
Message
Comments
1
MS
The MS is turned on and triggered to initiate the GPRS attach procedure
2
MS -> SS
EC PACKET CHANNEL REQUEST
DL Coverage Class: CC1
3
SS -> MS
EC IMMEDIATE ASSIGNMENT TYPE 2
Request Reference = pertaining to the message received in step 2. Fixed link assignment, sent on EC-AGCH
4
If the MS only supports eDRX, step 4a shall be performed.
If the MS supports both eDRX and PSM, step 4b shall be performed
4a
MS -> SS
UPLINK RLC DATA BLOCKS
Transporting: ATTACH REQUEST
It is Verified that eDRX IE is included
4b
MS -> SS
UPLINK RLC DATA BLOCKS
Transporting: ATTACH REQUEST
It is Verified that eDRX and T3324 IE are included.
5
SS -> MS
EC PACKET UPLINK ACK/NACK
acknowledge the received RLC data block, Final Ack Indicator = ‘1’ , a valid RRBP. Sent on EC-PACCH
6
MS -> SS
EC PACKET CONTROL ACKNOWLEDGEMENT
acknowledge the RLC data. Received on EC-PACCH
7
SS -> MS
EC IMMEDIATE ASSIGNMENT TYPE 2
For downlink TBF, sent 1 s. after step 6 on EC-AGCH
8
SS -> MS
DOWNLINK RLC DATA BLOCKS
Transporting:
ATTACH ACCEPT.
Including the Extended DRX value and T3324 Value set to:
eDRX Value: 0111 (3.25 min)
T3324 Value (PSM): 8 minutes
Last block containing a valid RRBP field and FBI set.
9
MS -> SS
EC PACKET DOWNLINK ACK/NACK
Not including Channel Request Description
10
MS -> SS
EC PACKET CHANNEL REQUEST
TS3 or TS4, received on EC-RACH
11
SS -> MS
EC IMMEDIATE ASSIGNMENT TYPE 2
Request Reference = pertaining to the message received in step 10. Fixed link assignment, sent on EC-AGCH
11
MS -> SS
UPLINK RLC DATA BLOCKS
Transporting:
ATTACH COMPLETE
12
SS -> MS
PACKET UPLINK ACK/NACK
Including valid RRBP field
13
MS -> SS
PACKET CONTROL ACKNOWLEDGMENT
14
Wait for 1 minute for Ready Timer to expire
15
SS -> MS
EC PAGING REQUEST
Packet page indication indicates packet paging procedure. Sent on EC-PCH according to the lowest eDRX cycle
16
There Should be no response from MS as the eDRX Cycle is now set to eDRX Value: 0111. This is verified for the duration of T3315
17
SS -> MS
EC PAGING REQUEST
Packet page indication indicates packet paging procedure. Sent on EC-PCH according to the negotiated eDRX cycle
18
MS -> SS
EC PACKET CHANNEL REQUEST
received on EC-RACH
19
SS -> MS
EC IMMEDIATE ASSIGNMENT REJECT
Request Reference = pertaining to the message received in step 18.
Sent on EC-AGCH.
20
SS -> MS
EC PAGING REQUEST
Sent on EC-PCH according to the negotiated eDRX cycle, on the next paging occasion after T3324 expiry
21
If the MS only supports eDRX, step 21a shall be performed.
If the MS supports both eDRX and PSM, step 21b shall be performed
21a
MS -> SS
EC PACKET CHANNEL REQUEST
received on EC-RACH
21b
There should be no response from MS, as it shall have entered PSM mode. This is verified for the duration of T3315
Specific Message Contents
-
41.8.3
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.8.4 EC-GSM-IoT / Coverage Class
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.8.4.0 EC-GSM-IoT / Coverage Class / Default Conditions
|
All default conditions, message contents and macros are defined in section 40, except for the parameters as described in this subclause. These parameters are applicable to the whole section 41.8, they shall be transmitted by the system simulator and are required to be received by the MS under test.
By default, DL_CC_Selection is set to RLA_EC based coverage class selection unless otherwise stated.
For RLA_EC based coverage class selection, the RxLev of the serving cell is adjusted in relation to EC_RXLEV_ACCESS_MIN, BT_Threshold_DL and CCx_Range_DL in order to select the expected coverage class.
For SLA based coverage class selection (tests 41.8.4.4 and 41.8.4.6), as per TS 45.008 subclause 6.9.4, the following radio conditions are used for test purposes:
BT_Threshold_DL = 18 (8 dB), CC2_Range_DL = 5 (6 dB), CC3_Range_DL = 5 (6 dB). Serving GSM cell at RXLEV= -70 dBm with two non-serving cells at -84 dBm, at -78 dBm, at -72 dBm, and at -66 dBm, for the MS to select CC1, CC2, CC3 and CC4, respectively.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.8.4.1 EC-GSM-IoT / Coverage Class / Paging Extension
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.8.4.1.1 Conformance requirement
|
A mobile station that has enabled EC operation and has successfully negotiated eDRXdeterminess its nominal paging group as defined for EC operation (see 3GPP TS 45.002) according to its negotiated eDRX cycle and selected downlink coverage class . A mobile station that has enabled EC operation but has not negotiated eDRX determines its nominal paging group as defined for EC operation according to the lowest eDRX cycle, its IMSI and its selected downlink CC (see 3GPP TS 45.002). If it receives a matching paging message therein it shall act on it as described in sub-clause 3.5.1.2. Otherwise, if it receives any other message on the EC-PCH and the EC Page Extension field is included therein it shall proceed as follows:
- If the EC Page Extension field indicates paging extension is enabled for its downlink coverage class it shall attempt to read one additional paging message using a paging group determined according to its coverage class as shown in Table 3.5.1a.1.
- If it finds a matching paging message therein it shall act on that message as described in sub-clause 3.5.1.2.
- If paging extension is not enabled or it does not find a matching paging message when attempting to read one additional paging message it sets its eDRX cycle to the negotiated eDRX cycle, remains in packet idle mode and waits for the next instance of its nominal paging group.
- A mobile station that has enabled EC operation and has successfully negotiated eDRX shall, upon re-selecting to a cell in the same Routing Area that does not support EC operation, determine its nominal paging group as defined for PEO (see 3GPP TS 45.002 [32]) using its negotiated eDRX cycle length.
Table 3.5.1a.1: Page Extension Using Fixed Offset
Downlink Coverage Class of Ongoing Transmission
CC1
CC2
CC3
CC4
Downlink CC of MS Requiring Page Extension
CC1
PG1 + 2
PG1 + 4
PG1 + 8
PG1 + 8
CC2
-
PG1 + 4
PG1 + 4
PG1 + (2 or 6)2
CC3
-
-
PG1 + 2
PG1 + (1 or 3)3
CC4
-
-
-
PG1 + 2
Note 1: PG (Paging Group) represents the start of the coverage class specific EC-PCH block corresponding to the nominal paging group of an MS (see 3GPP TS 45.002 [32]). The start of the coverage class specific EC-PCH block used for page extension is expressed as an offset relative to PG (where the value of the offset indicates the number of coverage class specific EC-PCH blocks comprising the offset).
Note 2: Page Extension is determined using PG + 2 when a CC2 MS reading its nominal paging group in TDMA frames 35 to 42 (CC2 B2) or in TDMA frames 43 to 50 (CC2 B3) in MF N/N+1 determines that a CC4 page is ongoing from TDMA frames 35 to 50 in MF N/N+1/N+2/N+3. Page Extension is determined using Paging Group PG + 6 when a CC2 MS reading its nominal paging group in TDMA frames 19 to 26 (CC2 B0) or in TDMA frames 27 to 34 (CC2 B1) in MF N/N+1 determines that a CC4 page is ongoing from TDMA frames 19 to 34 in MF N/N+1/N+2/N+3.
Note 3: Page Extension is determined using Paging Group PG + 1 when a CC3 MS reading its nominal paging group in TDMA frames 35 to 50 (CC3 B1) in MF N/N+1 determines that a CC4 page is ongoing from TDMA frames 35 to 50 in MF N/N+1/N+2/N+3. Page Extension is determined using Paging Group PG + 3 when a CC3 MS reading its nominal paging group in TDMA frames 19 to 34 (CC3 B0) in MF N/N+1 determines that a CC4 page is ongoing from TDMA frames 19 to 34 in MF N/N+1/N+2/N+3.
Reference
3GPP TS 44.018 subclause 3.5.1a.1
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.8.4.1.2 Test purpose
|
To verify that in EC operation, an MS will correctly consider the EC Paging extension field acquired when reading a message sent within its nominal paging group:
- If the EC Page Extension field indicates paging extension is enabled for its downlink coverage class, one additional paging group shall be considered,
- If the EC Page Extension field indicates paging extension is enabled for another downlink coverage class than the MS Coverage class, no additional paging group is considered by the MS.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.8.4.1.3 Method of test
|
Initial conditions
System Simulator:
1 cell EC-GSM-IoT supported
DL_CC_Selection = 0 (RLA_EC based coverage class selection)
BT_Threshold_DL = 0 (-87 dBm)
BT_Threshold_UL = 20 (-110 dBm)
CC2_Range_DL = CC3_Range_DL = 5 (6 dB)
Mobile Station:
The MS is GPRS attached in packet idle mode. eDRX cycle negotiated to 0100 (~ 24.5 sec)
Specific PICS Statements
-
PIXIT Statements
-
Foreseen final state of the MS
-
Test procedure
An immediate assignment, not addressing the MS, is sent on the MS paging group with the EC Page Extension field enabled for the selected DL Coverage class of the MS. The MS is then paged on the fixed offset paging block according to its selected DL coverage class and shall answer the paging.
At the next paging occurrence, a new Paging request not addressing the MS is sent with the EC Page Extension field enabled for a coverage class different than the MS one. The SS verified that it is not taken into account by the MS with a new Paging request addressing the MS on the fixed offset paging block according to its selected DL coverage class,.
The procedure is repeated for all the DL coverage class (k= 1 to 4).
Maximum duration of the test
-
Expected sequence
The test sequence is repeated for k = 1 … 4.
Step
Direction
Message
Comments
1
SS
The test is run with the following kx configurations:
k=1: -80 dBm, RxLev of the serving cell to ensure CC1 as DL coverage class
k=2: -90 dBm, RxLev of the serving cell to ensure CC2 as DL coverage class
k=3: -96, dBm RxLev of the serving cell to ensure CC3 as DL coverage class
k=4: -102 dBm RxLev of the serving cell to ensure CC4 as DL coverage class
2
MS
The MS is attached on Cell A
3
SS -> MS
EC IMMEDIATE ASSIGNMENT Type 2
On the MS paging group but not addressing the MS
EC Page Extension set to the MS Coverage class according to k configuration defined in Step 1
3a
SS -> MS
EC PAGING REQUEST
Sent on the additional EC-PCH block, according to Table 3.5.1a.1 of TS 44.018 (i.e. PG1 + 2 for CC1 / CC3 and CC4, and PG1 + 4 for CC2)
4
MS -> SS
EC PACKET CHANNEL REQUEST
Received on EC-RACH.
DL Coverage class indicated by the MS shall match k configuration.
5
SS -> MS
EC IMMEDIATE ASSIGNMENT REJECT
Request Reference = pertaining to the message received in step 4.
Sent on EC-AGCH.
6
SS -> MS
EC PAGING REQUEST
Sent on next EC-PCH according to the negotiated eDRX cycle (i.e. ~ 24.5 seconds after step 3) but not addressing the MS
EC Page Extension set to a different coverage class than the MS Coverage class according to k configuration defined in Step 1
6a
SS -> MS
EC PAGING REQUEST
Sent on the additional EC-PCH block, addressing the MS, according to Table 3.5.1a.1 of TS 44.018 (i.e. PG1 + 2 for CC1 / CC3 and CC4, and PG1 + 4 for CC2)
7
SS
SS checks that no response form the MS is sent.
8
SS -> MS
EC PAGING REQUEST
Sent on next EC-PCH according to the negotiated eDRX cycle (i.e. ~ 24.5 seconds after step 6)
9
MS -> SS
EC PACKET CHANNEL REQUEST
Received on EC-RACH.
Coverage class indicated by the MS shall match k configuration.
Specific message contents:
-
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.8.4.2 EC-GSM-IoT / Coverage Class / UL Coverage Class selection
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.8.4.2.1 Conformance requirement
|
The MS shall select the uplink CC to use on (EC-)RACH according to table 6.10.3-1, based on the uplink received signal strength, estimated as
BS_RX_PWR = RLA_EC + min(MSPWR, MS_TXPWR_MAX_CCH) – BSPWR.
MSPWR is the nominal maximum output power of the MS. MS_TXPWR_MAX_CCH is the maximum TX power level an MS is allowed to use when accessing the system. BSPWR is the output power of the BTS used on FCCH and EC-SCH. MS_TXPWR_MAX_CCH and BSPWR are broadcast in EC SI 2 (see 3GPP TS 44.018 [17]).
Table 6.10.3-1: Uplink CC selection
Uplink CC
Upper limit of BS_RX_PWR
Lower limit of BS_RX_PWR
1
-
BT_Threshold_UL
2
BT_Threshold_UL
BT_Threshold_UL +
CC2_Range_UL
3
BT_Threshold_UL +
CC2_Range_UL
BT_Threshold_UL +
CC2_Range_UL +
CC3_Range_UL
4
BT_Threshold_UL +
CC2_Range_UL +
CC3_Range_UL
(see note)
NOTE: There is no explicit lower limit for selection of uplink CC4 but the C1 criterion (see subclause 6.4.1) will trigger a cell re-selection.
BT_Threshold_UL indicates the BS_RX_PWR (in dBm) below which blind physical layer transmissions are used on EC-RACH. CC2_Range_UL and CC3_Range_UL indicate the BS_RX_PWR range (in dB) of uplink CC 2 and 3, respectively. BT_Threshold_UL is broadcast in EC SI 2 while CC2_Range_UL and CC3_Range_UL are optionally broadcast in EC SI 2 (see 3GPP TS 44.018 [17]). If either of CC2_Range_UL and CC3_Range_UL is not present, its value shall be set to 0 and the corresponding uplink CC not used. If BS_RX_PWR is on the limit between two CC, the MS shall select the higher CC.
Reference
3GPP TS 45.008 subclause 6.10.3
This message may be sent by an EC capable mobile station attempting system access using the EC-RACH (see sub-clause 3.5.2.1.2a) in which the message format is as shown in Tables 9.1.65.1 and 9.1.65.2.
Table 9.1.65.1: EC PACKET CHANNEL REQUEST message content (EC-RACH)
Training sequence (see 3GPP TS 45.002)
bits
11…...1
Packet Channel Access
TS3
< EC PACKET CHANNEL REQUEST message content >
Uplink CC1 MS - GMSK and 8PSK capability in uplink and downlink
TS4
< EC PACKET CHANNEL REQUEST message content >
Uplink CC1 MS - Only GMSK capability in uplink and downlink
TS5
< EC PACKET CHANNEL REQUEST message content >
Uplink CC2 MS
TS6
< EC PACKET CHANNEL REQUEST message content >
Uplink CC3 MS
TS7
< EC PACKET CHANNEL REQUEST message content >
Uplink CC4 MS
Reference
3GPP TS 44.008 9.1.65
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.8.4.2.2 Test purpose
|
To verify that an MS making an EC packet channel request will select the uplink CC to use on (EC-)RACH based on the uplink received signal strength, and the associated parameters.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.8.4.2.3 Method of test
|
Initial conditions
System Simulator:
1 cell EC-GSM-IoT supported
RLA_EC based coverage class selection.
BT_Threshold_UL = 0 (-90 dBm)
BT_Threshold_DL = 18 (-105 dBm)
CC2_Range_UL = CC3_Range_UL = 3 (4 dB)
Access_Timeslots = 0 to use 1TS EC_RACH Mapping
EC_Max_Retrans = 0 (1 retransmission)
CC_Access_Adaptation = 0
Mobile Station:
The MS is off.
Specific PICS Statements
-
PIXIT Statements
-
Foreseen final state of the MS
-
Test procedure
The MS is turned on with the cell at different power level. The EC-RACH access should be done according to the estimated Uplink Coverage Class.
The procedure is repeated for all the UL coverage class (k= 1 to 4).
Maximum duration of the test
-
Expected sequence
The test sequence is repeated for k = 1 … 4.
Step
Direction
Message
Comments
1
SS
The test is run with the following kx configurations:
k=1: -80 dBm RxLev of the serving cell to ensure CC1 as UL coverage class
k=2: -92 dBm RxLev of the serving cell to ensure CC2 as UL coverage class
k=3: -96 dBm RxLev of the serving cell to ensure CC3 as UL coverage class
k=4: -101 dBm RxLev of the serving cell to ensure CC4 as UL coverage class (not lower than -105 dBm)
2
MS
The MS is powered on
3
MS -> SS
EC PACKET CHANNEL REQUEST
Received on EC-RACH.
UL coverage class (i.e. Training Sequence used) indicated by the MS shall match kx configuration.
Selected DL coverage Class shall be CC1
4
SS
It is verified that the EC PACKET CHANNEL REQUESTED is properly repeated for the blind repetition cases k=2, 3 or 4 (i.e. UL CC > CC1) according to TS 45.002
5
MS -> SS
EC PACKET CHANNEL REQUEST
Received on EC-RACH. Sent as EC_Max_Retrans=0
UL coverage class (i.e. Training Sequence used) indicated by the MS shall match kx configuration.
DL coverage Class shall be CC1
6
SS
It is verified that the EC PACKET CHANNEL REQUESTED is properly repeated for the blind repetition cases k=2, 3 or 4 (i.e. UL CC > CC1) according to TS 45.002
7
SS
Check for 10 sec that no more EC-RACH access are done
Specific message contents:
-
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.8.4.3 EC-GSM-IoT / Coverage Class / DL Coverage Class selection / RLA_EC
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.8.4.3.1 Conformance requirement
|
The MS shall select the downlink CC based on either RLA_EC or SLA, as indicated by the DL_CC_Selection parameter sent in EC SI 2 (see 3GPP TS 44.018 [17]), according to table 6.10.2-1 and indicate it to the network in the EC Packet Channel Request message (see 3GPP TS 44.018 [17]). The network shall apply the indicated downlink CC on EC-AGCH.
Table 6.10.2-1: Downlink CC selection
Downlink CC
Upper limit of RLA_EC or SLA
Lower limit of RLA_EC or SLA
CC1
-
BT_Threshold_DL
CC2
BT_Threshold_DL
BT_Threshold_DL -
CC2_Range_DL
CC3
BT_Threshold_DL -
CC2_Range_DL
BT_Threshold_DL -
CC2_Range_DL -
CC3_Range_DL
CC4
BT_Threshold_DL -
CC2_Range_DL -
CC3_Range_DL
(see note)
NOTE: There is no explicit lower limit for selection of downlink CC4 but the C1 criterion (see subclause 6.4.1) will trigger a cell re-selection if RLA_EC ≤ EC_RXLEV_ACCESS_MIN + Max(MS_TXPWR_MAX_CCH – MSPWR,0), which implicitly sets a lower limit if CC selection is based on RLA_EC.
BT_Threshold_DL indicates the RLA_EC (in dBm) or SLA (in dB) below which blind physical layer transmissions are used on EC-AGCH. CC2_Range_DL and CC3_Range_DL indicate the RLA_EC range (in dB) of downlink CC2 and CC3, respectively.
BT_Threshold_DL and EC_RXLEV_ACCESS_MIN are broadcast in EC SI 2 (see 3GPP TS 44.018 [17]).
CC2_Range_DL and CC3_Range_DL are optionally broadcast in EC SI 2. If either of CC2_Range_DL and CC3_Range_DL is not broadcast, its value shall be set to 0 and the corresponding downlink CC is not supported by the network.
If RLA_EC or SLA (whichever is applicable) is on the limit between two CC, the MS shall select the higher CC.
In case downlink CC1 is selected, the MS shall further indicate in the EC Packet Channel Request message (see 3GPP TS 44.018 [17]) the margin of the measured RLA_EC (or SLA) relative to BT_Threshold_DL. The parameter DL_Signal_Strength_Step_Size broadcast in EC SI 2 (see 3GPP TS 44.018 [17]) is used to quantize the margin to report in the EC Packet Channel Request message. The maximum margin that can be reported is dependent on the number of Coverage Classes supported in the cell, and whether or not the access is initiated on RACH or EC-RACH, see 3GPP TS 44.018 [17].
NOTE: When TX diversity (antenna hopping) is active a MS may underestimate RLA_EC. This can be compensated for by the NW in an adjustment of the BT_Threshold_DL.
Reference
3GPP TS 45.008 subclause 6.10.2
[…]
Table 3.5.2.1.2a.2: Values of parameters Scc and Tcc
Scc
Tcc
CC1
Sm
Tm
CC2
Sm
Tm
CC3
2*Sm
2*Tm
CC4
4*Sm
2*(Tm+1)
The value for Sm is sent in the EC SYSTEM INFORMATION TYPE 2 message and is used for determining the Scc value applicable for monitoring the EC-AGCH according to the selected downlink coverage class of the mobile station
[…]
After sending the first EC PACKET CHANNEL REQUEST message or a subsequent retransmission, the mobile station shall start reading the EC-AGCH (according to the downlink coverage class indicated within the corresponding EC PACKET CHANNEL REQUEST message) in an attempt to find a response matching its last transmission.
- A MS that has selected downlink CC1 shall begin looking for a matching response starting within downlink 51-multiframe N (i.e. N = TDMA FN div 51) if it used uplink 51-multiframe N to send the last blind physical layer transmission of the EC PACKET CHANNEL REQUEST message and there is at least one remaining valid CC1 reception opportunity in downlink 51-multiframe N. If a matching response is not found or there are no remaining valid CC1 reception opportunities within downlink 51-multiframe N it shall start reading 51-multiframe N+1in an attempt to find a matching response. The total number of downlink 51-multiframes it reads (excluding downlink 51-multiframe N) in an attempt to find a matching response is determined by Scc (see Table 3.5.2.1.2a.2).
- A MS that has selected downlink CC2 shall begin looking for a matching response starting within downlink 51-multiframe N if it used uplink 51-multiframe N to send the last blind physical layer transmission of the EC PACKET CHANNEL REQUEST message, N mod 2 = 0 and there is at least one remaining valid CC2 reception opportunity that starts in downlink 51-multiframe N. If a matching response is not found using downlink 51-multiframes N and N+1 or there are no remaining valid CC2 reception opportunities that start within downlink 51-multiframe N it shall start reading downlink 51-multiframe N+1 (respectively N+2) if N mod 2 = 1 (respectively N mod 2 = 0). The total number of downlink 51-multiframes it reads (excluding downlink 51-multiframe N) in an attempt to find a matching response is determined by Scc (see Table 3.5.2.1.2a.2).
- A MS that has selected downlink CC3 shall begin looking for a matching response starting with downlink 51-multiframe N+1 (respectively N+2) when it used uplink 51-multiframe N to send the last blind physical layer transmission of the EC PACKET CHANNEL REQUEST message where N mod 2 = 1 (respectively N mod 2 = 0). The total number of downlink 51-multiframes it reads in an attempt to find a matching response is determined by Scc (see Table 3.5.2.1.2a.2).
- A MS that has selected downlink CC4 shall begin looking for a matching response starting with downlink 51-multiframe N+1 (respectively N+2, N+3, N+4) when it used uplink 51-multiframe N to send the last blind physical layer transmission of the EC PACKET CHANNEL REQUEST message where N mod 4 = 3 (respectively N mod 4 = 2, 1, 0). The total number of downlink 51-multiframes it reads in an attempt to find a matching response is determined by Scc (see Table 3.5.2.1.2a.2).
Reference
- 3GPP TS 44.018 subclause 3.5.2.1.2a
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.8.4.3.2 Test purpose
|
To verify that an MS make an EC operation access request shall select the downlink CC to use on EC-RACH, based on the downlink received signal strength and the associated parameters if the DL_CC_Selection indicates the RLA_EC based method.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.8.4.3.3 Method of test
|
Initial conditions
System Simulator:
1 Serving cell, EC-GSM-IoT supported
DL_CC_Selection = 0 (RLA_EC based coverage class selection)
BT_Threshold_DL = 0 (-87 dBm)
BT_Threshold_UL = 20 (-110 dBm)
CC2_Range_DL = CC3_Range_DL = 3 (4 dB)
Access_Timeslots = 0 to use 1TS EC_RACH Mapping
EC_Max_Retrans = 0 (1 retransmission)
DL_Signal_Strength_Step_Size = 0 (2dB)
Mobile Station:
The MS is off.
Specific PICS Statements
-
PIXIT Statements
-
Foreseen final state of the MS
-
Test procedure
The MS is turned on with the cell at different power level. The EC-RACH access should indicate the proper DL coverage class or the proper margin if CC1 is indicated.
The Assignment message sent, once only, randomly on one of the EC-AGCH blocks according to the requested DL Coverage Class. The reception level being good enough for a one time only decoding, without blind physical layer transmissions, the MS shall then continue its GPRS attach procedure.
The procedure is repeated for all the DL coverage class. (k= 1 to 5).
Maximum duration of the test
-
Expected sequence
The test sequence is repeated for k = 1 … 5.
Step
Direction
Message
Comments
1
SS
The test is run with the following kx configurations:
k=1: -70 dBm RxLev of the serving cell to ensure CC1 as DL coverage class
k=2: -80 dBm RxLev of the serving cell to ensure CC1 as DL coverage class
k=3: -89 dBm RxLev of the serving cell to ensure CC2 as DL coverage class
k=4: -93 dBm RxLev of the serving cell to ensure CC3 as DL coverage class
k=5: -100 dBm RxLev of the serving cell to ensure CC4 as DL coverage class (not lower than -105 dBm)
2
MS
The MS is powered on
3
MS -> SS
EC PACKET CHANNEL REQUEST
Received on EC-RACH.
UL coverage class (i.e. Training Sequence used) indicated by the MS shall be CC1
Selected DL coverage Class shall be set according to k configuration
For k=1 and 2, two different margins, at least 2 steps apart shall be reported
For k= 3 to 5, CC2, CC3 and CC4 shall be reported respectively
4
SS -> MS
EC IMMEDIATE ASSIGNMENT Type 2
Sent on EC-AGCH, once only, randomly on one of the blocks scheduled for the initial transmission or a potential blind repetition
5
MS -> SS
UPLINK RLC DATA BLOCKS
Transporting: ATTACH REQUEST
Specific message contents:
-
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.8.4.4 EC-GSM-IoT / Coverage Class / DL Coverage Class selection / SLA
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.8.4.4.1 Conformance requirement
|
The MS shall select the downlink CC based on either RLA_EC or SLA, as indicated by the DL_CC_Selection parameter sent in EC SI 2 (see 3GPP TS 44.018 [17]), according to table 6.10.2-1 and indicate it to the network in the EC Packet Channel Request message (see 3GPP TS 44.018 [17]). The network shall apply the indicated downlink CC on EC-AGCH.
Table 6.10.2-1: Downlink CC selection
Downlink CC
Upper limit of RLA_EC or SLA
Lower limit of RLA_EC or SLA
CC1
-
BT_Threshold_DL
CC2
BT_Threshold_DL
BT_Threshold_DL -
CC2_Range_DL
CC3
BT_Threshold_DL -
CC2_Range_DL
BT_Threshold_DL -
CC2_Range_DL -
CC3_Range_DL
CC4
BT_Threshold_DL -
CC2_Range_DL -
CC3_Range_DL
- (see note)
NOTE: There is no explicit lower limit for selection of downlink CC4 but the C1 criterion (see subclause 6.4.1) will trigger a cell re-selection if RLA_EC ≤ EC_RXLEV_ACCESS_MIN + Max(MS_TXPWR_MAX_CCH – MSPWR,0), which implicitly sets a lower limit if CC selection is based on RLA_EC.
BT_Threshold_DL indicates the RLA_EC (in dBm) or SLA (in dB) below which blind physical layer transmissions are used on EC-AGCH. CC2_Range_DL and CC3_Range_DL indicate the RLA_EC range (in dB) of downlink CC2 and CC3, respectively.
BT_Threshold_DL and EC_RXLEV_ACCESS_MIN are broadcast in EC SI 2 (see 3GPP TS 44.018 [17]).
CC2_Range_DL and CC3_Range_DL are optionally broadcast in EC SI 2. If either of CC2_Range_DL and CC3_Range_DL is not broadcast, its value shall be set to 0 and the corresponding downlink CC is not supported by the network.
If RLA_EC or SLA (whichever is applicable) is on the limit between two CC, the MS shall select the higher CC.
In case downlink CC1 is selected, the MS shall further indicate in the EC Packet Channel Request message (see 3GPP TS 44.018 [17]) the margin of the measured RLA_EC (or SLA) relative to BT_Threshold_DL. The parameter DL_Signal_Strength_Step_Size broadcast in EC SI 2 (see 3GPP TS 44.018 [17]) is used to quantize the margin to report in the EC Packet Channel Request message. The maximum margin that can be reported is dependent on the number of Coverage Classes supported in the cell, and whether or not the access is initiated on RACH or EC-RACH, see 3GPP TS 44.018 [17].
NOTE: When TX diversity (antenna hopping) is active a MS may underestimate RLA_EC. This can be compensated for by the NW in an adjustment of the BT_Threshold_DL.
Reference
3GPP TS 45.008 subclause 6.10.2
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.8.4.4.2 Test purpose
|
To verify that an MS make an EC operation access request shall select the downlink CC to use on EC-RACH, based on the SINR and the associated parameters if the DL_CC_Selection indicates the SLA based method.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.8.4.4.3 Method of test
|
Initial conditions
System Simulator:
1 Serving cell EC-GSM-IoT supported, RxLev -70dBm
2 non-serving cells (same ARFCN than the serving Cell), with RxLev set as per test configuration.
DL_CC_Selection = 1 (SLA based coverage class selection)
BT_Threshold_DL = 18 (8 dB)
BT_Threshold_UL = 20 (-110 dBm)
CC2_Range_DL = CC3_Range_DL = 5 (6 dB)
Access_Timeslots = 0 to use 1TS EC_RACH Mapping
EC_Max_Retrans = 0 (1 retransmission)
DL_Signal_Strength_Step_Size = 0 (2dB)
Mobile Station:
The MS is off.
Specific PICS Statements
-
PIXIT Statements
-
Foreseen final state of the MS
-
Test procedure
The MS is turned on with the non-serving cell at different power level to modify the SINR. The EC-RACH access should indicate the proper DL coverage class or the proper margin if CC1 is indicated.
The procedure is repeated for all the DL coverage class. (k= 1 to 5)
Maximum duration of the test
-
Expected sequence
The test sequence is repeated for k = 1 … 5.
Step
Direction
Message
Comments
1
SS
The test is run with the following kx configurations:
k=1: -90 dBm RxLev of the non-serving cells to ensure CC1 as DL coverage class
k=2: -84 dBm RxLev of the non-serving cells to ensure CC1 as DL coverage class
k=3: -78 dBm RxLev of the non-serving cells to ensure CC2 as DL coverage class
k=4: -72 dBm RxLev of the non-serving cells to ensure l ensure CC3 as DL coverage class
k=5: -66 dBm RxLev of the non-serving cells to ensure CC4 as DL coverage class
2
MS
The MS is powered on
3
MS -> SS
EC PACKET CHANNEL REQUEST
Received on EC-RACH.
UL coverage class (i.e. Training Sequence used) indicated by the MS shall be CC1
Selected DL coverage Class shall be set according to k configuration
For k=1 and 2, two different margins, at least 2 steps apart shall be reported
For k= 3 to 5, CC2, CC3 and CC4 shall be reported respectively
Specific message contents:
-
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.8.4.5 EC-GSM-IoT / Coverage Class / UL Coverage Class Adaptation
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.8.4.5.1 Conformance requirement
|
If CC adaptation on EC-RACH and EC-AGCH is allowed (as indicated by the CC_Access_Adaptation parameter broadcast in EC-SI2), the MS shall gradually increase its CC as described in 3GPP TS 44.018 and use it as its selected uplink or downlink CC.
Reference
3GPP TS 45.008 subclause 6.10.4
A mobile station accessing the network for the purpose of NAS signalling low priority (see 3GPP TS 24.008) that has sent one or more EC PACKET CHANNEL REQUEST messages shall proceed as follows:
[…]
- When scheduling another EC PACKET CHANNEL REQUEST message the MS uses the “CC_Access_Adaptation” parameter (broadcast in EC SYSTEM INFORMATION TYPE 2 message) to determine if it is allowed to increment both its uplink CC and downlink CC to the next CC supported by the network (unless it is already using CC4).
- Upon incrementing its uplink/downlink CC the number of subsequent EC PACKET CHANNEL REQUEST message transmission attempts that may occur before it is allowed to increment its uplink/downlink CC once again is the same as when sending the first EC PACKET CHANNEL REQUEST message (i.e. determined by the “EC_Max_Retrans” parameter).
- When sending up to M + 1 EC PACKET CHANNEL REQUEST messages the MS may increment its uplink CC and downlink CC a maximum of 2 times if CC adaptations are allowed according to the “CC_Access_Adaptation” parameter.
Reference
- 3GPP TS 44.018 subclause 3.5.2.1.2a
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.8.4.5.2 Test purpose
|
To verify that an MS make an access for NAS low priority may gradually increment its coverage class if it is allowed by the network (based on CC_Access_Adaptation), it cannot be done more than 2 times
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.8.4.5.3 Method of test
|
Initial conditions
System Simulator:
1 cell EC-GSM-IoT supported
RLA_EC based coverage class selection.
BT_Threshold_UL = 0 (-90 dBm)
BT_Threshold_DL = 18 (-105 dBm)
CC2_Range_UL = CC3_Range_UL = 3 (4 dB)
Access_Timeslots = 0 to use 1TS EC_RACH Mapping
EC_Max_Retrans = 11 (7 retransmissions)
CC_Access_Adaptation = 1
Mobile Station:
The MS is off, configured for Low Priority.
Specific PICS Statements
-
PIXIT Statements
-
Foreseen final state of the MS
-
Test procedure
The MS is turned on and shall trigger an access for NAS signalling low priority.
Maximum duration of the test
-
Expected sequence
Step
Direction
Message
Comments
1
SS
The test is run with the following kx configurations:
k=1: -80 dBm RxLev of the serving cell to ensure CC1 as UL coverage class
2
MS
The MS is powered on
3
MS -> SS
EC PACKET CHANNEL REQUEST
Received on EC-RACH.
UL coverage class (i.e. Training Sequence used) indicated by the MS shall match CC1 configuration.
Selected DL coverage Class shall be CC1
4
SS
No response from the network
5
MS -> SS
EC PACKET CHANNEL REQUEST
Received on EC-RACH as retransmissions are allowed
UL coverage class (i.e. Training Sequence used) indicated by the MS shall match the previous request or be one coverage class higher.
DL coverage Class shall match the previous configuration or a be one coverage class higher.
Both or none of the coverage classes shall be incremented.
6
SS
Step 5 is repeated 6 times (7 retransmissions).
It is check that no more than 2 increases are requested.
If CC2 or higher is requested, it is checked that the blind physical layers transmissions are properly sent according to TS 45.002.
6A
If the MS does not increase any Coverage Class request, the test case is considered as not applicable
Specific message contents:
-
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.8.4.6 EC-GSM-IoT / Coverage Class / DL Coverage Class Update
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.8.4.6.1 Conformance requirement
|
An EC capable MS whose last uplink transmission was in a cell that does not support EC-GSM-IoT may choose to enable EC operation upon reselection to a cell that supports EC-GSM-IoT. In this case it shall perform an uplink transmission (e.g. a cell update) to update the network (i.e. addition of Coverage Class information) and therefore be reachable for pages on the EC-PCH.
Reference
- 3GPP TS 44.018 subclause 3.5.1a.1
For the purpose of paging block monitoring on EC-PCH, the MS shall keep the network informed about the selected downlink CC (see subclause 6.10.2). The MS shall indicate the selected downlink CC using the DL Coverage Class field in the EC Packet Channel Request message. This shall be done in advance of the next occurrence of the paging group of the MS, and at least if any of the following conditions are fulfilled:
- the selected downlink CC is higher than the last downlink CC communicated to the network;
- the selected downlink CC is CC1 and the last downlink CC communicated to the network is CC4; or
- the MS has completed an uplink data transfer in a cell not supporting EC-GSM-IoT since the last time it communicated a downlink CC to the network.
The MS shall consider the network to be informed about the selected downlink CC at the completion of the uplink data transfer.
The network shall apply the indicated downlink CC on EC-PCH messages sent to that MS.
Reference
- 3GPP TS 45.005 subclause 6.10.5
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.8.4.6.2 Test purpose
|
To verify that an MS updates the network appropriately if the selected downlink coverage class is modified.
For EC Capable MS supporting GPRS, it is verified that the MS will inform the network, of its DL coverage class when the last uplink transmission was done in a cell not supporting EC-GSM-IoT.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.8.4.6.3 Method of test
|
Initial conditions
System Simulator:
1 Serving cell EC-GSM-IoT supported, RxLev -70dBm
1 GPRS Cell, turned Off
2 non-serving cells (same ARFCN than the serving Cell), with RxLev set at -78dBm to ensure DL CC2 is used.
DL_CC_Selection = 1 (SLA based coverage class selection)
BT_Threshold_DL = 18 (8 dB)
BT_Threshold_UL = 20 (-110 dBm)
CC2_Range_DL = CC3_Range_DL = 7 (6 dB)
Access_Timeslots = 0 to use 1TS EC_RACH Mapping
EC_Max_Retrans = 0 (1 retransmission)
DL_Signal_Strength_Step_Size = 0 (2dB)
Mobile Station:
The MS is GPRS attached in packet idle mode. eDRX cycle negotiated to 0101 (~ 49 sec)
Specific PICS Statements
- GPRS Supported (TSPC_GPRS)
PIXIT Statements
-
Foreseen final state of the MS
-
Test procedure
The MS is attached to the EC-GSM-IoT cell with DL coverage class CC2 conditions.
The SINR is decreased in order to trigger DL CC4 conditions. Before its next paging occasion, the MS should inform the network about the new DL CC.
The network conditions are then enhanced for CC1 to be selected as DL coverage Class. Before its next paging occasion, the MS should inform the network about the new DL CC.
If the MS support also GPRS, the MS is forced to move to a GPRS Cell and answer a paging. The MS is then moved again the EC-GSM-IoT cell and should inform the network of its coverage class.
Maximum duration of the test
-
Expected sequence
Step
Direction
Message
Comments
1
The MS is GPRS and the DL coverage Class CC2 was used during the Attach procedure.
2
SS -> MS
EC PAGING REQUEST
Sent on the MS EC-PCH block, according to TS 45.002 (CC2)
3
MS -> SS
EC PACKET CHANNEL REQUEST
Received on EC-RACH.
DL Coverage class indicated by the MS shall be CC2
4
SS -> MS
EC IMMEDIATE ASSIGNMENT REJECT
Request Reference = pertaining to the message received in step 3
Sent on EC-AGCH according to TS 45.002
5
The RxLev of the non-serving cells is increased to -66 dBm to ensure CC4 as DL coverage class.
6
MS -> SS
EC PACKET CHANNEL REQUEST
Received on EC-RACH.
Payload: “Cell Update”
UL coverage class (i.e. Training Sequence used) indicated by the MS shall be CC1
Selected DL coverage Class shall be CC4
This message should be sent within one eDRX cycle (49 sec) of step 1.
6a
SS -> MS
EC IMMEDIATE ASSIGNMENT REJECT
Request Reference = pertaining to the message received in step 6
Sent on EC-AGCH according to TS 45.002 (with blind repetitions as CC4 is used)
7
SS -> MS
EC PAGING REQUEST
Sent on the MS EC-PCH block, according to TS 45.002 (CC4)
8
MS -> SS
EC PACKET CHANNEL REQUEST
Received on EC-RACH.
DL Coverage class indicated by the MS shall be CC4
9
SS -> MS
EC IMMEDIATE ASSIGNMENT REJECT
Request Reference = pertaining to the message received in step 8
Sent on EC-AGCH according to TS 45.002 (with blind repetitions as CC4 is used)
10
The RxLev of the non-serving cells is decreased to -84 dBm to ensure CC1 as DL coverage class.
11
MS -> SS
EC PACKET CHANNEL REQUEST
Received on EC-RACH.
Payload: “Cell Update”
UL coverage class (i.e. Training Sequence used) indicated by the MS shall be CC1
Selected DL coverage Class shall be CC1
This message should be sent within one eDRX cycle (49 sec) of step 7.
11a
SS -> MS
EC IMMEDIATE ASSIGNMENT REJECT
Request Reference = pertaining to the message received in step 11
Sent on EC-AGCH according to TS 45.002 (no Blind repetition as CC1 is used)
12
SS -> MS
EC PAGING REQUEST
Sent on the MS EC-PCH block, according to TS 45.002 (CC1)
13
MS -> SS
EC PACKET CHANNEL REQUEST
Received on EC-RACH.
DL Coverage class indicated by the MS shall be CC1
14
SS -> MS
EC IMMEDIATE ASSIGNMENT REJECT
Request Reference = pertaining to the message received in step 13
Sent on EC-AGCH according to TS 45.002 (no Blind repetition as CC1 is used)
Next step are only applicable for EC Capable MS supporting GPRS (TSPC_GPRS)
15
The EC-GSM-IoT cell is turned Off and the GPRS cell is turned on (RxLev = -80dBm)
16
Wait for 30 sec.
17
SS -> MS
PAGING REQUEST Type 1
1st Mobile Identity contains IMSI of the MS, second Mobile Identity not present. Packet page indication indicates packet paging procedure. Sent on PCH.
18
MS -> SS
CHANNEL REQUEST
Establishment Cause = = "one phase packet access". Received on RACH.
19
SS -> MS
IMMEDIATE ASSIGNMENT REJECT
Request Reference = pertaining to the message received in step 18
Sent on AGCH
20
The EC-GSM-IoT cell is turned on (RxLev = -70dBm) and the GPRS cell is turned off
21
MS -> SS
EC PACKET CHANNEL REQUEST
Received on EC-RACH.
Payload: “Cell Update”
UL coverage class (i.e. Training Sequence used) indicated by the MS shall be CC1
Selected DL coverage Class shall be CC1
This message should be sent within before next paging opportunity
21a
SS -> MS
EC IMMEDIATE ASSIGNMENT REJECT
Request Reference = pertaining to the message received in step 21
Sent on EC-AGCH according to TS 45.002 (no Blind repetition as CC1 is used)
22
SS -> MS
EC PAGING REQUEST
Sent on the MS EC-PCH block, according to TS 45.002 (CC1)
23
MS -> SS
EC PACKET CHANNEL REQUEST
Received on EC-RACH.
DL Coverage class indicated by the MS shall be CC1
Specific message contents:
-
42 Test of Medium Access Control (MAC) protocol
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
42.1 Test of Medium Access Control (MAC) Procedures
|
Default conditions
The SS default conditions simulate one cell with default settings as defined in the GPRS general default section.
The MS default initial condition is GPRS attached. Unless otherwise stated, no PDP context is required.
The default message contents and signalling macro not specified in the end of this subclause shall be set as in "GPRS default conditions" clause 40. Specific message contents for a test case is specified in each test case.
Conditions or message contents specified in a test case have the highest precedence. In addition, the default message contents described in the end of this subclause override those specified in "GPRS default conditions".
In case the test case not expected "short access" as access type for Packet Channel Request the amount of RLC data specified in the comments in expected sequence is not necessary to be exactly the specified amount of data. It only has to be more than the limit for short access. If the test case need a specific amount of data this is specified in the test case.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
42.1.1 Void
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
42.1.2 Packet Uplink/Downlink Assignment
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
42.1.2.1 Packet uplink assignment procedure
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
42.1.2.1.1 Void
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
42.1.2.1.2 Void
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
42.1.2.1.3 Void
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
42.1.2.1.4 Void
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
42.1.2.1.5 Void
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
42.1.2.1.6 Void
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
42.1.2.1.7 Void
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
42.1.2.1.8 Void
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
42.1.2.1.9 Packet Uplink Assignment / Two phase access
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
42.1.2.1.9.1 Void
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
42.1.2.1.9.2 Packet Uplink Assignment / Two phase access / Contention resolution
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
42.1.2.1.9.2.1 Packet Uplink Assignment / Two phase access / Contention resolution / Expiry of timer T3168
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
42.1.2.1.9.2.1.1 Conformance requirements
|
The contention resolution has failed on the mobile station side when the mobile station does not receive a PACKET UPLINK ASSIGNMENT message with its TLLI before expiry of timer T3168. The mobile station shall then reinitiate the packet access procedure unless it has already been repeated 4 times. In that case, TBF failure has occurred.
Reference
3GPP TS 04.60 subclause 7.1.3.3.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
42.1.2.1.9.2.1.2 Test purpose
|
To verify that the mobile station reinitiates the packet access procedure after a time equal to timer T3168 and the procedure shall be attempted a total of 4 or 5 times.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
42.1.2.1.9.2.1.3 Method of test
|
Initial conditions
System Simulator:
1 cell supporting GPRS, CCCH combined with SDCCH,SI13 GPRS Cell Options, T3168 = 7.
Mobile Station:
The MS is GPRS attached and in packet idle mode. PDP context 1 has been established.
Specific PICS Statements
- Release of GPRS supported (TSPC_MS_GPRS_RELEASE)
PIXIT Statements
-
Test procedure
The MS is triggered to initiate unacknowledged uplink data transfer. The SS sends IMMEDIATE ASSIGNMENT message including Single Block Allocation struct information to order the MS to send PACKET RESOURCE REQUEST message. The MS shall perform a two-phase access i.e. the MS shall transmit a PACKET RESOURCE REQUEST message on the allocated uplink resource. The SS wait for a time greater than timer T3168 so the MS shall reinitiate packet access procedure. This procedure shall be attempted 4 or 5 times.
Maximum duration of the test
2 minutes.
Expected sequence
Step
Direction
Message
Comments
1
MS
The MS is triggered to initiate packet uplink transfer of an LLC PDU consisting of 200 octets data.
2
MS -> SS
CHANNEL REQUEST
3
SS -> MS
IMMEDIATE ASSIGNMENT
Single Block Allocation struct. Sent on AGCH.
4
MS -> SS
PACKET RESOURCE REQUEST
ACCESS_TYPE = "Two Phase Access Request". Received on the single block assigned in step 3.
5
SS
The SS waits T3168 expiry.
6
The SS verifies that the MS attempts packet access procedure (steps 2-5 are repeated) in total:
Four or five times if PICS ‘Release of GPRS supported’ is Release 97, 98, 99 or 4.
Four times if PICS ‘Release of GPRS supported’ is Release 5 or later.
NOTE: After step 6 the MS may reinitiate a packet access procedure, since higher layers may request to restart the access procedure.
Specific message contents
None.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
42.1.2.1.9.2.2 Packet Uplink Assignment / Two phase access / Contention resolution / TLLI mismatch
|
The contention resolution is completed on the mobile station side when the mobile station receives a PACKET UPLINK ASSIGNMENT message with the same TLLI as the mobile station has included in the PACKET RESOURCE REQUEST message.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
42.1.2.1.9.2.2.1 Conformance requirements
|
If the failure is due to a TLLI mismatch, or to the expiry of timers T3166 or T3168, or to the fact that the counter N3104 reached its maximum value in the contention resolution procedure, and repetition as described in subclause 7.1.3.3 has been performed, the mobile station shall remain in packet idle mode, notify higher layer (TBF establishment failure), transactions in progress shall be aborted and cell reselection continued.
Reference
3GPP TS 04.60 subclauses 7.1.4 and 7.1.3.3.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
42.1.2.1.9.2.2.2 Test purpose
|
To verify that the MS reinitiates packet access procedure with failure due to a TLLI mismatch in the contention resolution procedure, unless it has already been attempted 4 or 5 times. In that case, TBF failure has occurred.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
42.1.2.1.9.2.2.3 Method of test
|
Initial conditions
System Simulator:
1 cell supporting GPRS, CCCH combined with SDCCH, GPRS cell options ACCESS_BURST_TYPE indicates 8 bit access.
Mobile Station:
The MS is GPRS attached and in packet idle mode. PDP context 1 has been established.
Specific PICS Statements
- Release of GPRS supported (TSPC_MS_GPRS_RELEASE)
PIXIT Statements
-
Test procedure
The MS is triggered to initiate unacknowledged uplink data transfer. The SS responds with IMMEDIATE ASSIGNMENT message that request two phase access. The MS shall then send PACKET RESOURCE REQUEST message. The SS responds with PACKET UPLINK ASSIGNMENT message with a TLLI different to that the MS has sent in PACKET RESOURCE REQUEST message. The MS shall reinitiate the packet access procedure.
This procedure shall be attempted 4 or 5 times.
Maximum duration of the test
2 minutes.
Expected sequence
Step
Direction
Message
Comments
1
MS
The MS is triggered to initiate packet uplink transfer of an LLC PDU consisting of 200 octets data.
2
MS -> SS
CHANNEL REQUEST
Received on RACH.
3
SS -> MS
IMMEDIATE ASSIGNMENT
Single Block Allocation struct. Sent on AGCH.
4
MS -> SS
PACKET RESOURCE REQUEST
ACCESS_TYPE = "Two Phase Access Request". Include TLLI. Received on the single block assigned in step 3.
5
SS -> MS
PACKET UPLINK ASSIGNMENT
Include incorrect TLLI according to step 4. Sent on the PACCH of the assigned PDCH.
6
The SS verifies that the MS attempts packet access procedure (steps 2-5 are repeated) in total:
Four or five times if PICS ‘Release of GPRS supported’ is Release 97, 98, 99 or 4.
Four times if PICS ‘Release of GPRS supported’ is Release 5 or later.
Note: After step 6 the MS may reinitiate a packet access procedure, since higher layers may request to restart the access procedure.
Specific message contents
None.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
42.1.2.1.9.3 Packet Uplink Assignment / Two phase access / Packet Resource Request / No respond to Packet Downlink Assignment
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
42.1.2.1.9.3.1 Conformance requirements
|
At sending of the PACKET RESOURCE REQUEST message, the mobile station shall start timer T3168. Further more, the mobile station shall not respond to PACKET DOWNLINK ASSIGNMENT messages while timer T3168 is running.
Reference
3GPP TS 04.60 subclause 7.1.3.1.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
42.1.2.1.9.3.2 Test purpose
|
To verify that the mobile station does not respond to PACKET DOWNLINK ASSIGNMENT messages while timer T3168 is running after sending of the PACKET RESOURCE REQUEST message.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
42.1.2.1.9.3.3 Method of test
|
Initial conditions
System Simulator:
1 cell supporting GPRS, CCCH combined with SDCCH, T3168 indicates value 7 in GPRS Cell Options.
Mobile Station:
The MS is GPRS attached and in packet idle mode. PDP context 2 has been established.
Specific PICS Statements
-
PIXIT Statements
-
Test procedure
The MS is triggered to initiate uplink data transfer. The SS shall send IMMEDIATE ASSIGNMENT message including Single Block Allocation struct information to instruct the MS to send PACKET RESOURCE REQUEST. The MS should perform a two-phase access i.e. the MS shall transmit a PACKET RESOURCE REQUEST message on the allocated uplink resource.
While timer T3168 is running the SS send PACKET DOWNLINK ASSIGNMENT message and starts to send data on the allocated downlink before the timer expires. The MS shall not respond to the Downlink data transfer.
The SS should then send PACKET UPLINK ASSIGNMENT message before the timer T3168 expires and the MS should then begin transmitting RLC data blocks on the allocated uplink resources. The SS allows the MS to complete the sending of the data.
Maximum duration of the test
2 minutes.
Expected sequence
Step
Direction
Message
Comments
1
MS
The MS is triggered to initiate packet uplink transfer of an LLC PDU containing 400 octets of data.
2
MS -> SS
CHANNEL REQUEST
Received on RACH.
3
SS -> MS
IMMEDIATE ASSIGNMENT
Single block allocation struct. Sent on AGCH.
4
MS -> SS
PACKET RESOURCE REQUEST
Received on the single block assigned in step 3.
5
SS -> MS
PACKET DOWNLINK ASSIGNMENT
Sent on PACCH.
6
SS -> MS
DOWNLINK RLC DATA BLOCK
Sent on the assigned PDTCH with poll bit set to 1.
SS
Verify no response from the MS.
7
SS -> MS
PACKET UPLINK ASSIGNMENT
Dynamic allocation struct. Sent on the PACCH of the assigned PDCH 0,9* T3168.
8
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
Assigning USF to the MS. Sent at least 3 block periods from the assignment in step 7.
9
{Uplink data transfer}
Macro. Completion of the TBF procedure.
Specific message contents
None.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
42.1.2.1.10 Packet Uplink Assignment / Abnormal cases
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
42.1.2.1.10.1 Packet Uplink Assignment / Abnormal cases / Incorrect PDCH assignment
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
42.1.2.1.10.1.1 Conformance requirements
|
If the mobile station has been assigned more PDCHs than it supports according to its MS multislot class, the mobile station shall reinitiate the packet access procedure unless it has already been repeated 4 times. In that case, TBF failure has occurred.
Reference
3GPP TS 04.60 subclause 7.1.4.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
42.1.2.1.10.1.2 Test purpose
|
To verify that the mobile station reinitiates the packet access procedure when the mobile station has been assigned more PDCHs than it supports and after 4 or 5 attempts of the packet access procedure the mobile station shall initiate TBF failure.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
42.1.2.1.10.1.3 Method of test
|
Initial conditions
System Simulator:
1 cell supporting GPRS, CCCH combined with SDCCH.
Mobile Station:
The MS is switched off. The SIM is updated to the test cell.
Specific PICS Statements
- Release of GPRS supported (TSPC_MS_GPRS_RELEASE)
- GPRS Multislotclass (TSPC_Type_GPRS_Multislot_ClassX where X = 1..45)
PIXIT Statements
-
Test procedure
Convert the MS GPRS Multislot Class to number of uplink timeslot supported.
The MS is powered up or switched on and triggered to perform a GPRS attach. An uplink TBF is established and after PACKET RESOURCE REQUEST the SS sends PACKET UPLINK ASSIGNMENT message containing more assigned PDCHs than the MS supports according to its GPRS multislot class. The MS shall reinitiate packet access procedure; this procedure shall be attempted 4 or 5 times.
Maximum duration of the test
2 minutes.
Expected sequence
Step
Direction
Message
Comments
1
MS
The MS is powered up or switched on and triggered to perform a GPRS attach.
2
MS -> SS
CHANNEL REQUEST
Received on RACH.
3
SS -> MS
IMMEDIATE ASSIGNMENT
Single block allocation struct. Sent on AGCH.
4
MS -> SS
PACKET RESOURCE REQUEST
Received on the single block assigned in step 3.
5
SS -> MS
PACKET UPLINK ASSIGNMENT
Assign one more Tx than the MS supported. Sent on PACCH.
6
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
Sent on the third block from the message sent in step 35 Assigning USF to the MS
7
The SS verifies that the MS does not send UPLINK RLC DATA BLOCKS and instead attempts packet access procedure (steps 2-6 are repeated) in total:
Four or five times if PICS ‘Release of GPRS supported’ is Release 97, 98, 99 or 4.
Four times if PICS ‘Release of GPRS supported’ is Release 5 or later
NOTE: After step 7 the MS may reinitiate a packet access procedure, since higher layers may request to restart the access procedure.
Specific message contents
None.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
42.1.2.1.10.2 Packet Uplink Assignment / Abnormal cases / Expiry of timer T3164
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
42.1.2.1.10.2.1 Conformance requirements
|
On expiry of timer T3164, the mobile station shall reinitiate the packet access procedure unless it has already been reinitiated 3 times, in which case the mobile station shall return to packet idle mode and notify higher layers.
Reference
3GPP TS 04.60 subclause 7.1.4.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
42.1.2.1.10.2.2 Test purpose
|
To verify that the mobile station reinitiate the packet access procedure when the network have sent a PACKET UPLINK ASSIGNMENT message but the MS has not sent the first block within the time equal to the timer T3164. This packet access procedure shall be reinitiated 3 times.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
42.1.2.1.10.2.3 Method of test
|
Initial conditions
System Simulator:
1 cell supporting GPRS, CCCH combined with SDCCH.
Mobile Station:
The MS is GPRS attached and in packet idle mode. PDP context 2 has been established.
Specific PICS Statements
-
PIXIT Statements
-
Test procedure
The MS is triggered to initiate uplink data transfer. The SS sends IMMEDIATE ASSIGNMENT message with a USF assigned to the MS. The SS shall send PACKET DOWNLINK DUMMY CONTROL BLOCK messages with USF not assigned to the MS. T3164 expires. The SS send a PACKET DOWNLINK DUMMY CONTROL BLOCK containing the assigned USF. The SS verifies that the MS does not send a RLC data block. The SS verifies that the MS reinitiate the packet access procedure within 5 seconds of T3164 expiry; this shall be repeated 3 times.
Maximum duration of the test
1 minute.
Expected sequence
Step
Direction
Message
Comments
1
MS
The MS is triggered to initiate packet uplink transfer of an LLC PDU consisting of 200 octets of data.
2
MS -> SS
CHANNEL REQUEST
Received on RACH.
3
SS -> MS
IMMEDIATE ASSIGNMENT
Single block assignment, to order the MS to follow the two phase access procedure. Sent on AGCH
4
MS -> SS
PACKET RESOURCE REQUEST
Received on the single block assigned in step 3.
5
SS -> MS
PACKET UPLINK ASSIGNMENT
Allocate a USF for the MS. Sent on PACCH.
6
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCKs
Don't contain the assigned USF in step 5. Repeat step 6 for a maximum of 5.5 seconds (1.1*T3164). The MS may send a CHANNEL REQUEST at any time after 0.9*T3164, in this case go to step 9.
7
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCKs
Containing the assigned USF in step 5.
8
SS
Verify the MS does not transmit an RLC data block
9
SS
The SS verifies that the packet access procedure (steps 2-6) is reinitiated three times.
The CHANNEL REQUEST for reinitiation (in step 2) shall be sent within 5 sec of T3164 expiry (to cater for T3168 - the maximum duration of a packet access procedure).
NOTE: After step 9 the MS may reinitiate a packet access procedure, since higher layers may request to restart the access procedure.
Specific message contents
None.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
42.1.2.2 Packet Downlink Assignment
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
42.1.2.2.1 Packet Downlink Assignment / Response to poll bit
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
42.1.2.2.1.1 Conformance requirements
|
In case valid timing advance for the mobile station is not available, the network may use one of the following two methods to trigger the mobile station to transmit a PACKET CONTROL ACKNOWLEDGEMENT:
- if the PACKET DOWNLINK ASSIGNMENT message is not segmented and the CONTROL_ACK_TYPE parameter in the System Information indicates acknowledgement is access bursts, the network may set the poll bit in the PACKET DOWNLINK ASSIGNMENT message.
- if the PACKET DOWNLINK ASSIGNMENT message is segmented or the CONTROL_ACK_TYPE parameter in the System Information does not indicate acknowledgement is access bursts, the network may send PACKET POLLING REQUEST with TYPE_OF_ACK parameter set to access bursts (see subclause 11.2.12).
The mobile station shall always transmit the uplink radio block on the same timeslot as the block where the RRBP was received. After receiving an RLC/MAC block containing a valid RRBP field the mobile station need not monitor the USF in the associated downlink RLC/MAC block appearing just before the uplink block it shall transmit.
Reference
3GPP TS 04.60 subclause 7.2.1.1 and 10.4.5.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
42.1.2.2.1.2 Test purpose
|
To verify that the mobile station sends PACKET CONTROL ACKNOWLEDGEMENT as four access bursts if the network sets the poll bit in the PACKET DOWNLINK ASSIGNMENT message when CONTROL_ACK_TYPE is set to four access bursts.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
42.1.2.2.1.3 Method of test
|
Initial conditions
System Simulator:
1 cell supporting GPRS, CCCH combined with SDCCH. CONTROL_ACK_TYPE is set to indicate PACKET CONTROL ACKNOWLEGEMENT format as four access bursts and the ACCESS_BURST_TYPE indicates 11 bit access.
Mobile Station:
The MS is GPRS attached and in packet idle mode and Ready state.
Specific PICS Statements
-
PIXIT Statements
-
Test procedure
The SS initiate a downlink data transfer by sending IMMEDIATE ASSIGNMENT on PCH. The SS sends PACKET DOWNLINK ASSIGNMENT message. The poll bit in the MAC header of the PACKET DOWNLINK ASSIGNMENT message will be set to indicate RRBP field is valid. The MS may delay the establishment of the downlink channels in order to answer the poll request on the common control channel. The SS verifies that the MS sends PACKET CONTROL ACKNOWLEDGEMENT as four access bursts on the timeslot on which it received the polling command.
Maximum duration of the test
2 minutes.
Expected sequence
Step
Direction
Message
Comments
1
SS
The SS initiate a downlink transfer of 200 octets data.
2a
SS -> MS
IMMEDIATE ASSIGNMENT
For downlink TBF. Sent on PCH
2b
SS -> MS
PACKET DOWNLINK ASSIGNMENT
Poll bit in the MAC header is set to indicate a valid RRBP = 1. Sent on PACCH.
3
MS -> SS
PACKET CONTROL ACKNOWLEDGEMENT
As four access bursts. Received on PACCH.
4
SS
The SS verifies that the MS sends the PACKET CONTROL ACKNOWLEDGEMENT as four access bursts, one per TDMA frame of the uplink radio block.
Specific message contents
None.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
42.1.2.2.2 Void
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
42.1.2.2.3 Void
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
42.1.2.2.4 Packet Downlink Assignment / Response to Packet Polling
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
42.1.2.2.4.1 Conformance requirements
|
In case valid timing advance for the mobile station is not available, the network may use one of the following two methods to trigger the mobile station to transmit a PACKET CONTROL ACKNOWLEDGEMENT:
- if the PACKET DOWNLINK ASSIGNMENT message is not segmented and the CONTROL_ACK_TYPE parameter in the System Information indicates acknowledgement is access bursts, the network may set the poll bit in the PACKET DOWNLINK ASSIGNMENT message.
- if the PACKET DOWNLINK ASSIGNMENT message is segmented or the CONTROL_ACK_TYPE parameter in the System Information does not indicate acknowledgement is access bursts, the network may send PACKET POLLING REQUEST with TYPE_OF_ACK parameter set to access bursts (see subclause 11.2.12).
On receipt of a PACKET POLLING REQUEST message, the mobile station shall respond to the network with the PACKET CONTROL ACKNOWLEDGEMENT message in the block period specified by the RRBP field. If the MS has received a PACKET DOWNLINK ASSIGNMENT message with no starting time or with a starting time that has already elapsed, the PACKET POLLING REQUEST message shall be sent on PACCH. Otherwise the PACKET POLLING REQUEST message shall be sent on PAGCH.
Reference
3GPP TS 04.60 subclauses 7.2.1.3 and 7.2.1.1.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
42.1.2.2.4.2 Test purpose
|
To verify that on receipt of a PACKET POLLING REQUEST message, the mobile station responds with PACKET CONTROL ACKNOWLEDGEMENT message in the block period specified by the RRBP field.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
42.1.2.2.4.3 Method of test
|
Initial conditions
System Simulator:
1 cell supporting GPRS, CCCH combined with SDCCH. CONTROL_ACK_TYPE is set to not indicate acknowledgement as four access bursts and ACCESS_BURST_TYPE indicate 8 bit access.
Mobile Station:
The MS is GPRS attached and in packet idle mode and Ready state.
Specific PICS Statements
-
PIXIT Statements
-
Test procedure
The SS initiate a downlink data transfer by sending IMMEDIATE ASSIGNMENT on PCH. The SS sends PACKET DOWNLINK ASSIGNMENT message to the MS with a TBF starting time. The SS sends a PACKET POLLING REQUEST message containing a valid RRBP field. The SS verifies that the MS sends a PACKET CONTROL ACKNOWLEDGEMENT message in the block period specified by the RRBP field. The SS sends PACKET PDCH RELEASE message to the MS. The SS initiate a downlink data transfer by sending IMMEDIATE ASSIGNMENT on PCH. The SS sends PACKET DOWNLINK ASSIGNMENT message to the MS without TBF starting time. The SS sends a PACKET POLLING REQUEST message containing a valid RRBP field. The SS verifies that the MS sends a PACKET CONTROL ACKNOWLEDGEMENT message in the block period specified by the RRBP field.
Maximum duration of the test
5 minutes.
Expected sequence
Step
Direction
Message
Comments
1
SS
The SS initiate a downlink transfer of 200 octets data.
2a
SS -> MS
IMMEDIATE ASSIGNMENT
For downlink TBF. Sent on PCH
2b
SS -> MS
PACKET DOWNLINK ASSIGNMENT
See specific message contents. Sent on PACCH.
3
SS -> MS
PACKET POLLING REQUEST
Sent on PACCH after TBF starting time in step 2 has elapsed. See specific message contents.
4
MS -> SS
PACKET CONTROL ACKNOWLEDGEMENT
The SS verifies that the MS send this message in the block period specified by the RRBP field as four access bursts. Received on PACCH.
5
SS -> MS
PACKET PDCH RELEASE
Sent on PACCH.
6
SS
Wait 20 s.
7
SS
The SS initiate a downlink transfer of 200 octets data.
8a
SS -> MS
IMMEDIATE ASSIGNMENT
For downlink TBF. Sent on PCH
8b
SS -> MS
PACKET DOWNLINK ASSIGNMENT
See specific message contents. Sent on PACCH.
9
SS -> MS
PACKET POLLING REQUEST
Sent on PACCH. See specific message contents.
10
MS -> SS
PACKET CONTROL ACKNOWLEDGEMENT
The SS verifies that the MS send this message in the block period specified by the RRBP field as four access bursts. Received on PACCH.
Specific message contents
As default messages contents, except:
PACKET DOWNLINK ASSIGNMENT in step 2b
Information element
Value/remark
< TIMESLOT_ALLOCATION >
00000100, allocate timeslot 5.
{0|1< TBF Starting Time >
1
-TBF_STARTING_TIME}
arbitrarily chosen
PACKET DOWNLINK ASSIGNMENT in step 8b
Information element
Value/remark
< TIMESLOT_ALLOCATION >
00000001, allocate timeslot 7.
{0|1< TBF Starting Time >}
0 (No TBF starting time)
PACKET POLLING REQUEST in step 3 and 9
Information element
Value/remark
RRBP in MAC header
Set to 1
S/P in MAC header
Set to 1 : RRBP field is valid
< MESSAGE_TYPE >
000100
< PAGE_MODE
Normal Paging
{ 0 < Global TFI >
| 10 < TLLI >
0 (Global TFI)
| 110 < TQI >}
1
DOWNLINK TFI
DOWNLINK TFI Present
As allocated in the PACKET DOWNLINK ASSIGNMENT message in Step 2 and Step 8 respectively
< TYPE_OF_ACK >
0 as four access bursts
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
42.1.2.2.5 Void
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
42.1.2.2.6 Packet Downlink Assignment Timing Advance / TA value field not provided
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
42.1.2.2.6.1 Conformance requirements
|
For the case where a TIMING_ADVANCE_VALUE field is not provided in the assignment message, the mobile station is not allowed to send normal bursts on the uplink until it receives a valid timing advance either through the continuous timing advance procedure or in a PACKET TIMING ADVANCE/POWER CONTROL message.
Reference
3GPP TS 04.60 subclause 7.1.2.5.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
42.1.2.2.6.2 Test purpose
|
To verify that the mobile station does not send normal bursts on the uplink until it receives a valid timing advance in a PACKET POWER CONTROL/TIMING ADVANCE message if Timing Advance Value field is not provided in the PACKET DOWNLINK ASSIGNMENT message.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
42.1.2.2.6.3 Method of test
|
Initial conditions
System Simulator:
1 cell supporting GPRS, CCCH combined with SDCCH.
Mobile Station:
The MS is GPRS attached and in packet idle mode. PDP context 2 has been established.
Specific PICS Statements
-
PIXIT Statements
-
Test procedure
The SS initiates downlink data transfer by sending IMMEDIATE ASSIGNMENT on PCH. The SS sends PACKET DOWNLINK ASSIGNMENT message. The SS does not include Timing Advance in the PACKET DOWNLINK ASSIGNMENT. The SS poll MS by sending an RLC DATA BLOCK. SS verifies for 2 seconds that MS did not answer to poll and then send a PACKET POWER CONTROL/TIMING ADVANCE message with a valid timing advance information. The SS verifies that the MS does not send any normal burst on the uplink until the SS sends a valid timing advance.
Maximum duration of the test
2 minutes.
Expected sequence
Step
Direction
Message
Comments
1
MS
The SS initiate a downlink transfer of 200 octets data.
2a
SS -> MS
IMMEDIATE ASSIGNMENT
For downlink TBF. Sent on PCH
2b
SS->MS
PACKET DOWNLINK ASSIGNMENT
Send on PACCH. No Timing Advance Value
3
SS -> MS
DOWNLINK RLC DATA BLOCK
Sent on assigned PDTCHs with a valid RRBP field.
Final Block Indicator is set to 0.
4
SS
SS verifies that the MS does not send any normal burst on the uplink.
5
SS -> MS
PACKET POWER CONTROL/TIMING ADVANCE
Include a valid Timing Advance information. Sent on PACCH.
6
SS->MS
DOWNLINK RLC DATA BLOCK
Sent on assigned PDTCHs with a valid RRBP field.
Final Block Indicator is set to 0.
7
MS->SS
PACKET DOWNLINK ACK/NACK
The SS verifies that the MS indicating correct reception of downlink data blocks. Received on PACCH.
Specific message contents
None.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
42.2 Void
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
42.3 Dynamic Allocation in Packet Transfer Mode
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
42.3.1 Dynamic Allocation / Uplink Transfer
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
42.3.1.1 Dynamic Allocation / Uplink Transfer / Normal
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
42.3.1.1.1 Dynamic Allocation / Uplink Transfer / Normal / Successful
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
42.3.1.1.1.1 Conformance requirements
|
1. The mobile station shall set the TFI field of each uplink RLC data block to the TFI value assigned to the mobile station in the PACKET UPLINK ASSIGNMENT or PACKET TIMESLOT RECONFIGURE message.
2. Whenever the mobile station detects an assigned USF value on an assigned PDCH, the mobile station shall transmit either a single RLC/MAC block or a sequence of four RLC/MAC blocks on the same PDCH in the next block period(s). The time relation between an uplink block, which the mobile station shall use for transmission, and the occurrence of the USF value is defined in 3GPP TS 05.02. The number of RLC/MAC blocks to transmit is controlled by the USF_GRANULARITY parameter characterising the uplink TBF.
3. At two-phase access the mobile station does not include its TLLI in any RLC data block.
References
3GPP TS 04.60, subclauses 8.1.1, 8.1.1.1 and 7.1.3.3.
3GPP TS 05.02, subclause 6.3.2.2.1.
42.3.1.1.1.2 Test purposes
To verify that the MS:
1. depending on the parameter USF_GRANULARITY, transmits one or a sequence of four RLC/MAC data block(s) in the next block period(s) on the PDCH on which it has detected its corresponding assigned USF.
2. includes the assigned TFI in each uplink RLC data blocks.
3. does not include its TLLI in any RLC data block at two phase access.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
42.3.1.1.1.3 Method of test
|
Initial Conditions
System Simulator:
1 cell, default setting, .
Mobile Station:
The MS is GPRS attached with a P-TMSI allocated and the test PDP context3 activated.
Specific PICS Statements
-
PIXIT Statements
-
Test Procedure
The MS is triggered to initiate packet uplink transfer data in RLC unacknowledged mode. The SS orders the MS to have two-phase access, in PACKET UPLINK ASSIGNMENT message the USF_GRANURALITY is set to 4 blocks. The SS sends the assigned USF assigned to the MS and checks that a sequence of four RLC/MAC data blocks in the next radio block period is received, and that each data block contains the correct TFI, but without TLLI. The SS assigns the USF assigned to the MS again. The check is repeated. The procedure is going on until the MS completes the packet data transfer.
The above test procedure is repeated once for USF_GRANURALITY set to one block.
Maximum Duration of Test
5 minutes.
Expected Sequence
Step
Direction
Message
Comments
1
{Uplink dynamic allocation two phase access}
n =600 octets, without starting time,
USF_GRANULARITY = 4 blocks,
RLC_DATA_BLOCKS_GRANTED = open-end
CHANNEL_CODING_COMMAND: arbitrarily chosen.
2
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
Sent on the PACCH, the USF assigned to the MS, on 3 blocks from the last radio block containing the uplink assignment.
3
MS -> SS
UPLINK RLC DATA BLOCK
Received on the assigned PDTCH.
Check that the coding as specified by CHANNEL_CODING_COMMAND, the TFI is correct and the block does not contain TLLI.
4
MS -> SS
UPLINK RLC DATA BLOCK
Received on the assigned PDTCH in the next radio block to step 3. Check that the coding as specified by CHANNEL_CODING_COMMAND, the TFI is correct and the block does not contain TLLI.
5
MS -> SS
UPLINK RLC DATA BLOCK
Received on the assigned PDTCH in the next radio block to step 4. Check that the coding is the scheme specified by CHANNEL_CODING_COMMAND, the TFI is correct and the block does not contain TLLI.
6
MS -> SS
UPLINK RLC DATA BLOCK
Received on the assigned PDTCH in the next radio block to step 5. Check that the coding as specified by CHANNEL_CODING_COMMAND, the TFI is correct and the block does not contain TLLI.
7
SS -> MS
PACKET UPLINK ACK/NACK
Sent on the PACCH of the PDCH, the USF not addressing the MS.
8
SS
Check that no RLC data blocks are transmitted from the MS in the next radio block to step 7.
9
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
The USF assigned to the MS.
10
MS -> SS
UPLINK RLC DATA BLOCK
Received on the assigned PDTCH.
11
MS -> SS
UPLINK RLC DATA BLOCK
Received on the assigned PDTCH in the next radio block to step 10. Check that the TFI is correct.
12
MS -> SS
UPLINK RLC DATA BLOCK
Received on the assigned PDTCH in the next radio block to step 11. Check that the TFI is correct.
13
MS -> SS
UPLINK RLC DATA BLOCK
Received on the assigned PDTCH in the next radio block to step 12. Check that the TFI is correct.
14
{Completion of uplink RLC data block transfer}
USF_GRANULARITY = 4 blocks
15
{Uplink dynamic allocation two phase access}
Similar parameter values to step 1
Except USF_GRANULARITY = 1 blocks
16
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
Sent on the PACCH of the PDCH, the USF assigned to the MS on 3 blocks from the last radio block containing the uplink assignment.
17
MS -> SS
UPLINK RLC DATA BLOCK
Received on the assigned PDTCH. Check that the coding as specified in CHANNEL_CODING_COMMAND, the TFI is correct and the block does not contain TLLI.
18
SS -> MS
PACKET UPLINK ACK/NACK
Sent on the PACCH, the USF not addressing the MS.
19
SS
Check that no RLC data blocks are transmitted from the MS in the next radio block to step 18.
20
SS -> MS
PACKET UPLINK ACK/NACK
Sent on a PDCH with any different time slot as the assigned PDCH, the USF assigned to the MS.
21
SS
Check that no RLC data block is transmitted from the MS on the next radio block to step 20.
22
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
Sent on the PACCH of the PDCH, the USF assigned to the MS.
23
MS -> SS
UPLINK RLC DATA BLOCK
Received on the assigned PDTCH. Check that the coding as specified in CHANNEL_CODING_COMMAND, the TFI is correct and the block does not contain TLLI.
24
{Completion of uplink RLC data block transfer}
USF_GRANULARITY = 1 block
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
42.3.1.1.2 Void
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
42.3.1.1.3 Dynamic Allocation / Uplink Transfer / Normal / Starting frame number encoding
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
42.3.1.1.3.1 Conformance requirements
|
1. In case of dynamic allocation, if no uplink TBF is in progress, the MS needs not monitor the USF field until the TDMA frame number occurs. When the indicated TDMA frame number occurs, the mobile station shall immediately begin to monitor the USF field and use the new assigned uplink TBF parameters when its USF occurs.
2. If an uplink TBF is already in progress, the MS shall continue to use the parameters of the existing TBF until the TDMA frame number occurs. When the indicated TDMA frame number occurs, the mobile station shall immediately begin to monitor the USF field and use the new assigned uplink TBF parameters when its USF occurs.
3. In case of single block allocation, the mobile station shall use the assigned timeslot during the RLC/MAC block whose first TDMA burst occurs in the indicated TDMA frame number.
4. If the mobile station is in packet transfer mode during the block immediately before the starting time and the lowest numbered PDCH assigned to the MS is different immediately before and after the starting time then the mobile station shall be ready to receive or transmit no later than one radio block from the starting time
5 If the Starting FN (in absolute frame number encoding) is not aligned to the start of a block period and the mobile station is in packet transfer mode during the TDMA immediately before the Starting FN, then the mobile station shall align the starting time to the next block boundary and continue to use the currently assigned allocation up to the next block boundary.
References
3GPP TS 04.60, subclauses 11.2.29, 12.21 and 12.21.1.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
42.3.1.1.3.2 Test purposes
|
To verify that the MS, in transfer mode:
1. correctly uses the starting frame number description in PACKET UPLINK ASSIGNMENT, and in all subsequent RLC/MAC control messages which are sent on the uplink TBF;
2. is ready to receive or transmit no later than one radio block from the starting time;
3. is able to align the starting time to the next block boundary and continue to use the currently assigned allocation up to the next block boundary.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
42.3.1.1.3.3 Method of test
|
Initial Conditions
System Simulator:
1 cell, default setting,.
Mobile Station:
The MS is GPRS attached with a P-TMSI allocated and the test PDP context3 activated.
Specific PICS Statements
-
PIXIT Statements
-
Test Procedure
The MS is triggered to initiate packet uplink transfer 440 octets in the RLC unacknowledged mode. The IMMEDIATE ASSIGNMENT message contains a starting time for the single block allocation. It is checked that the MS uses the time slot at the assigned frame number. In the two-phase access a starting time is included in PACKET UPLINK ASSIGNMENT. The assigned USF is on a radio block before the starting time. The MS does not react upon that. The assigned USF is on one block after the starting time. The MS sends a RLC data block.
The test procedure is repeated once. The starting time is encoded in relative frame number format.
Maximum Duration of Test
5 minutes.
Expected Sequence
The expected sequence is repeated once. In the 2nd execution the starting frame numbers in the specific message contents are encoded in the relative format.
Step
Direction
Message
Comments
1
{Uplink dynamic allocation two phase access}
n = 440 octets,
USF_GRANULARITY = 1 block,
RLC_DATA_BLOCKS_GRANTED = open-end
TLLI_BLOCK_CHANNEL_CODING: same as channel coding
CHANNEL_CODING_COMMAND: cs-3
The IMMEDIATE ASSIGNMENT contains starting time current frame + 1001.
It is checked that PACKET RESOURCE REQUEST in the macro is sent at the starting time.
The PACKET UPLINK ASSIGNMENT contains starting time specified in absolute frame number encoding, current frame + 91,
The timeslot TN7 assigned.
2
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
The USF assigned to the MS, Sent on one radio block before the starting time.
3
SS
Check that there is no RLC data block sent by the MS on the assigned PDTCH.
4
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
The USF assigned to the MS. Sent on one block after the starting time.
5
MS -> SS
UPLINK RLC DATA BLOCK
Received on the assigned PDTCH. Check that the coding is the scheme specified by CHANNEL_CODING_COMMAND in step 1, and TFI is correct.
6
{Completion of uplink RLC data block transfer}
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
42.3.1.1.4 Dynamic Allocation / Uplink Transfer / Normal / Starting time
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
42.3.1.1.4.1 Conformance requirements
|
1 If a TBF starting time information element is present and no uplink TBF is in progress, but a downlink TBF is in progress, the mobile station shall wait until the starting time before beginning to monitor the USFs. While waiting for the starting time, the mobile station shall monitor the assigned PDCHs.
2 If an uplink TBF is already in progress, the mobile station shall continue to use the assigned parameters of the uplink TBF until the TDMA frame number indicated by the TBF starting time occurs. At that time the mobile station shall immediately begin to use the newly assigned uplink TBF parameters.
3 While waiting for the frame number indicated by the TBF starting time if the mobile station receives another uplink assignment, the mobile station shall act upon the most recently received uplink assignment and shall ignore the previous uplink assignment.
4 An MS shall be ready to transmit and receive using a new assignment no later than the next occurrence of block B((x+3) mod 12) where block B(x) is the last radio block containing the assignment message. This applies also for the reception of the first USF for dynamic uplink assignment.
References
3GPP TS 04.60, subclause 8.1.1.1, 3GPP TS 45.010 subclause 6.11.1.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
42.3.1.1.4.2 Test purposes
|
To verify that after the MS receives an uplink assignment with starting time:
1. if a downlink TBF is in progress and no uplink TBF is in progress it monitors the assigned PDCHs while waiting for the starting time. If another uplink assignment received while waiting, the mobile station acts upon that and ignores the previous uplink assignment.
2. if an uplink TBF is already in progress, it continues to use the assigned parameters of the uplink TBF until the TDMA frame number indicated by the TBF starting time occurs. While waiting for the frame number indicated by the TBF starting time the mobile station receives another uplink assignment, the mobile station acts upon that and ignores the previous uplink assignment. As soon as the starting time occurs the MS immediately begins to use the newly assigned uplink TBF parameters.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
42.3.1.1.4.3 Method of test
|
Initial Conditions
System Simulator:
1 cell, default setting,.
Mobile Station:
The MS is GPRS attached with a P-TMSI allocated and the test PDP context2 activated.
Specific PICS Statements
-
PIXIT Statements
-
Test Procedure
A downlink TBF is established and in progress. An uplink TBF is established with a starting time which does not yet elapse. The SS sends two downlink data blocks before the starting time to the MS and signals the assigned TBF addressing the MS for uplink transfer. It is checked that no uplink RLC data blocks are sent by the MS. The SS sends PACKET TIMESLOT RECONFIGURE on three radio blocks before the starting time, assigning a new starting time. Two downlink data blocks are then sent to the MS before the new starting time occurs. Each data block contains one of the assigned USFs addressing the MS. It is checked that no uplink data blocks are sent from the MS. After the new starting time elapses the SS sends a downlink data block containing the USF assigned to the MS. The MS sends an uplink data block. The MS is brought to Idle mode.
Subsequently an uplink TBF is established. The SS sends PACKET UPLINK ASSIGNMENT assigning a reconfigured PDCH with a starting time and a new USF associated. Before the starting time the SS signals the USF of the ongoing TBF addressing the MS. The SS receives an uplink data block from the MS. The SS sends UPLINK ASSIGNMENT on three radio blocks before the starting time, assigning a new reconfigured PDCH with a starting time and a different USF associated. The later assignment overwrites the earlier one.. While waiting for the frame number of the newly assigned starting time the SS signals the USF of the previous assignment on both the ongoing PDCH and on the previous assigned PDCH. The MS ignores it. The SS signals the USF of the ongoing TBF addressing the MS. An uplink data block can be received. On one radio block before the starting time the SS signals the later assigned USF assigned to the MS on the later assigned PDCH. No uplink data block is received. On one radio block after the starting time the SS signals the just expired USF. No uplink data block is received. Then the SS signals the valid USF assigned to the MS. An uplink data block is received.
Maximum Duration of Test
5 minutes.
Expected Sequence
Step
Direction
Message
Comments
1
{Downlink TBF establishment}
RLC mode: acknowledged, without starting time
2
SS -> MS
DOWNLINK RLC DATA BLOCK
The data block contains FBI=0 and a valid RRBP, sent on the third block after the last radio block containing the downlink assignment.
3
MS -> SS
PACKET DOWNLINK ACK/NACK
Received on the specified RRBP of downlink PACCH.
4
MS
The MS is triggered to send 440 octets of user data.
5
SS -> MS
DOWNLINK RLC DATA BLOCK
The data block contains FBI=0 and a valid RRBP.
6
MS -> SS
PACKET DOWNLINK ACK/NACK
Received on the specified RRBP of downlink PACCH.
Contains Channel Request Description IE.
Note : If the triggering of the uplink access involves a manual operation taking more than 5s to complete, steps 5 and 6 are repeated (until the MS does include the Channel Request Description IE) at least once every 5s in order to keep the downlink transfer active.
7
SS -> MS
PACKET UPLINK ASSIGNMENT
USF_GRANULARITY = 1 block,
RLC_DATA_BLOCKS_GRANTED = open-end
CHANNEL_CODING_COMMAND: arbitrarily chosen.
TBF Starting Time : starting time1, the current frame + 104 frames, encoded in absolute frame number.
The uplink TBF is assigned on the same timeslot as the downlink TBF.
8
SS -> MS
DOWNLINK RLC DATA BLOCK
FBI=0, the assigned USF1 to the MS. Sent on downlink PDTCH, 12 data blocks (52 TDMA frames) before the starting time1.
9
SS -> MS
DOWNLINK RLC DATA BLOCK
FBI=0, the assigned USF1 to the MS. Sent on downlink PDTCH, 5 blocks before the starting time1, a valid RRBP = N+13.
10
MS -> SS
PACKET DOWNLINK ACK/NACK
Received on the specified RRBP on downlink PACCH.
11
SS -> MS
PACKET TIMESLOT RECONFIGURE
Assigned USF1 addressing the MS, sent on three blocks before the starting time1. Assigned a new USF2 on the same timeslot, with starting time2, current frame + 104 frames in relative frame number encoding.
12
SS -> MS
DOWNLINK RLC DATA BLOCK
On 4 blocks from the last radio block containing the uplink assignment in step 11, with FBI=0, the assigned previous USF1 addressing the MS. Sent on downlink PDTCH.
13
SS -> MS
DOWNLINK RLC DATA BLOCK
One data block with FBI=0, the assigned USF2 addressing the MS. Sent on downlink PDTCH, one radio block before the starting time2.
14
SS
Check that from the step 4 onwards till the starting time2, there is no RLC data block sent by the MS on the assigned uplink PDTCH.
15
SS -> MS
DOWNLINK RLC DATA BLOCK
One data block with FBI=0, a valid RRBP, the assigned USF2 addressing the MS. Sent on downlink PDTCH, on the frame number specified in the starting time2.
16
MS -> SS
UPLINK RLC DATA BLOCK
Received on the assigned uplink PDTCH.
17
MS -> SS
PACKET DOWNLINK ACK/NACK
Received on the specified RRBP of downlink PACCH.
18
SS -> MS
DOWNLINK RLC DATA BLOCK
One data block with FBI=1 and a valid RRBP. Sent on downlink PDTCH.
19
MS -> SS
PACKET DOWNLINK ACK/NACK
Received on the specified RRBP of the downlink PACCH.
20
{Completion of uplink RLC data block transfer}
21
{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: arbitrarily chosen
CHANNEL_CODING_COMMAND: cs-1
The timeslot TN3 assigned
22
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
Assigned USF1 addressing the MS, sent on 3 blocks from the last radio block containing the uplink assignment in step 21.
23
MS -> SS
UPLINK RLC DATA BLOCK
Check that the coding is cs1, the TFI is correct.
24
SS -> MS
PACKET UPLINK ACK/NACK
Assigned USF1 addressing the MS.
25
MS -> SS
UPLINK RLC DATA BLOCK
Received on the assigned PDTCH.
26
PACKET UPLINK ASSIGNMENT
Assign an uplink TBF on the timeslot TN2, containing new TFI2, USF2, starting time3, current frame + 117 in relative encoding. Sent on PACCH assigned.
27
PACKET UPLINK ACK/NACK
USF1 addressing the MS, sent on 5 radio blocks before the starting time3, on PACCH assigned in step 21.
28
UPLINK RLC DATA BLOCK
Check that the coding is cs1, the TFI is correct.
29
SS -> MS
PACKET UPLINK ASSIGNMENT
Assign a TBF on the timeslot TN1, containing new TFI3, USF3, cs-3 coding, starting time4, current frame + 325 in relative encoding. Sent on three radio blocks before the starting time3, on PACCH assigned in step 21.
30
SS -> MS
PACKET UPLINK ACK/NACK
USF2 addressing the MS, sent on 4 blocks from the last radio block containing the uplink assignment in step 29 on the PACCH assigned in step 26.
31
SS
Check that no data block is sent from the MS on the assigned radio block on the PDTCH assigned in step 26.
32
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
USF1 addressing the MS, sent on 5 radio blocks before the starting time4, on PACCH assigned in step 21.
33
MS -> SS
UPLINK RLC DATA BLOCK
Check that the coding is cs1, the TFI is correct.
34
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
The USF3 addressing the MS, sent on one radio block before the starting time4, on PACCH assigned in step 26.
35
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
The USF1 addressing the MS, sent on one radio block after the starting time4, on PACCH assigned in step 21.
36
SS
Check that no data blocks are sent from the MS on the radio blocks assigned in steps 34 and 35, or any intermediate radio blocks, on any of the three PDTCHs assigned
37
SS -> MS
PACKET UPLINK ACK/NACK
Containing USF3. Sent on PACCH of PDCH assigned in step 29.
38
(optional step)
MS -> SS
UPLINK RLC DATA BLOCK
Received on the PDTCH assigned in step 29.
Use coding cs-1.
If step 38 is performed, then step 39 must be performed.
39(optional step)
SS -> MS
PACKET UPLINK ACK/NACK
Only performed if step 38 is performed
Containing USF3. Sent on PACCH of PDCH assigned in step 29.
40
MS -> SS
UPLINK RLC DATA BLOCK
Received on the PDTCH assigned in step 29. Check that the coding cs-3 and TFI3 are correct.
41
{Completion of uplink RLC data block transfer}
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.