hash
stringlengths 32
32
| doc_id
stringlengths 5
12
| section
stringlengths 4
595
| content
stringlengths 0
6.67M
|
|---|---|---|---|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.5.5.2.1 Conformance Requirements
|
The network may at any time during uplink packet transfer initiate a change of resources by sending on the downlink PACCH monitored by the MS, an unsolicited uplink assignment message (e.g. PACKET UPLINK ASSIGNMENT, MULTIPLE TBF UPLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE, MULTIPLE TBF TIMESLOT RECONFIGURE or PACKET CS RELEASE INDICATION message) to the mobile station. During the reallocation, TFI is allowed to be changed.
References
3GPP TS 44.060, sub-clauses 8.1.1.1.2
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.5.5.2.2 Test Purpose
|
To verify that the MS continues to maintain an ongoing uplink TBF and downlink TBF throughout the Enhanced DTM CS Release procedure.
To verify that the MS correctly implements the reallocation of the PS resources, including a change of TFI, for an ongoing uplink TBF upon completion of the Enhanced DTM CS Release procedure.
To verify that the MS correctly implements the reallocation of the PS resources, including a change of TFI, for an ongoing downlink TBF upon completion of the Enhanced DTM CS Release procedure.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.5.5.2.3 Method of Test
|
Initial Conditions
System Simulator:
- 1 cell, Enhanced DTM supported.
Mobile Station:
- The MS is in the active state (U10) of a call on timeslot N.
- The MS is in packet idle mode, with a TMSI, P-TMSI allocated and PDP context 1 activated.
Specific PICS Statements
-
PIXIT Statements
-
Test Procedure
The MS, whilst in dedicated mode, is triggered to initiate packet uplink transfer data in RLC unacknowledged mode and sends a DTM REQUEST message. On receipt of the DTM REQUEST message, requesting uplink resources, the SS assigns the MS PS resource using a PACKET ASSIGNMENT message which also assigns a new downlink TBF. The active speech call is disconnected. The SS sends the PACKET CS RELEASE INDICATION message on PACCH to the MS indicating that the RR connection is going to end. The PACKET CS RELEASE INDICATION indicates that when the RR connection is released the downlink and/or uplink TBFs are reconfigured and reassigns the uplink and downlink TFIs as well as the allocated timeslots. Once any requested SI messages have been sent to the MS, the SS sends the CHANNEL RELEASE message on the main DCCH indicating in the Enhanced DTM Release Indication IE that the MS may continue in packet transfer mode. It is checked that the MS continues operating the uplink and downlink TBFs by sending RLC data blocks on the new PS resources.
Maximum Duration of Test
5 minutes
Expected Sequence
Step
Direction
Message
Comments
1
MS
Trigger the MS to initiate an uplink packet transfer
containing 1000 octets.
2
MS->SS
DTM REQUEST
Sent on main DCCH.
3
SS->MS
PACKET ASSIGNMENT
Sent on main DCCH.
See specific message contents.
4
SS<->MS
{ Uplink data }
Macro.
5
SS<->MS
{ Acknowledged Downlink Data }
Macro.
6
It is checked that the MS continues to transmit uplink and acknowledge downlink data during Steps 7 to 14 below.
7
SS->MS
DISCONNECT
Sent on main DCCH.
The active speech call is disconnected.
8
MS->SS
RELEASE
Sent on main DCCH.
9
SS->MS
RELEASE COMPLETE
Sent on main DCCH.
10
SS->MS
PACKET CS RELEASE INDICATION
Sent on PACCH.
See specific message contents.
11
MS->SS
PACKET SI STATUS
Sent on PACCH.
Indicates possible non receipt of SI messages.
Steps 12 and 13 are performed if the MS indicates non-receipt of required SI messages (SI1, SI3 and SI13) in Step 11.
12
SS->MS
PACKET SERVING CELL SI
Sent on PACCH.
Contains an SI message requested in Step 11.
13
Step 12 is repeated until all requested required SI messages (SI1, SI3 and SI13) have been sent to the MS.
14
SS->MS
CHANNEL RELEASE
Sent on main DCCH.
See specific message contents.
Steps 15 and 16 are performed concurrently.
15
SS<->MS
{ Uplink data transfer }
Macro.
16
SS<->MS
{ Downlink data transfer }
Macro.
Specific Message Contents
PACKET ASSIGNMENT (Step 3):
As default message contents except:
RR Packet Uplink Assignment IE
- TIMESLOT_ALLOCATION
(N + 1) MOD 8
RR Packet Downlink Assignment IE
- TIMESLOT_ALLOCATION
(N + 1) MOD 8
PACKET CS RELEASE INDICATION (Step 10):
Information Element
Value/remark
As default message contents, except:
- ENHANCED PACKET CS RELEASE INDICATION
1 (RR connection released)
The subsequent message encoding indicates that when the RR connection is released the downlink and/or uplink TBF(s) are reconfigured.
- Multiple Downlink Assignment
TFI is changed.
Timeslot allocation = (N -2) MOD 8
- Multiple Uplink Assignment
TFI is changed.
Timeslot allocation = (N - 2) MOD 8
CHANNEL RELEASE (Step 14):
Information Element
Value/remark
As default message contents, except:
Enhanced DTM CS Release Indication IE
1 (MS allowed to continue in packet transfer mode)
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.5.5.3 Change of LA in NW Mode II
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.5.5.3.1 Conformance Requirements
|
If the MS and the network in mode II or III support enhanced DTM CS release procedure and the location area of the MS has changed while in dual transfer mode, the MS may perform the enhanced DTM CS release procedure and, after the release of the RR connection, request CS resources via the enhanced DTM CS Establishment procedure for performing the Location Area Update procedure.
References
3GPP TS 43.055, sub-clauses 6.4.4.1
41.5.5.3.2 Test Purpose
To verify that the MS performs the enhanced DTM CS Release procedure when circuit switched resources are released by the NW following a change of location area whilst the MS was in dedicated mode in a network using network mode II.
To verify that following successful completion of the enhanced DTM CS Release procedure the MS performs the enhanced DTM CS Establishment procedure in order to perform the Location Update procedure following a change of location area whilst the MS was in dedicated mode in a network using network mode II.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.5.5.3.3 Method of Test
|
Initial Conditions
System Simulator:
- 2 cells, A and B operating in NW Mode II with different LAC, without PBCCHs, both supporting Enhanced DTM.
Mobile Station:
- The MS is in the active state (U10) of a call on Cell A on timeslot N.
- The MS is in packet idle mode, with a TMSI, P-TMSI allocated and PDP context 1 activated.
Specific PICS Statements
-
PIXIT Statements
-
Test Procedure
The MS, whilst in dedicated mode, is triggered to initiate packet uplink data transfer in RLC unacknowledged mode and sends a DTM REQUEST message. On receipt of the DTM REQUEST message, the SS assigns the MS packet switched resources using a PACKET ASSIGNMENT message. Before the MS has completed transmission of the uplink data, the SS orders a handover to Cell B. Following handover to Cell B the non-combined routing area update procedure is performed on the main DCCH. The MS resumes transmission of the uplink data. The active speech call is disconnected. The SS sends the PACKET CS RELEASE INDICATION message on PACCH to the MS indicating that the RR connection is going to end. The PACKET CS RELEASE INDICATION indicates that when the RR connection is released the MS may maintain it's uplink TBF. The packet switched resources are not re-allocated. The MS responds with the PACKET SI STATUS message on PACCH. The SS sends the MS any requested SI messages encapsulated within PACKET SERVING CELL SI messages on PACCH. The MS responds with the PACKET SI STATUS message indicating receipt of the required SI messages. The SS sends the CHANNEL RELEASE message on the main DCCH indicating in the Enhanced DTM Release Indication IE that the MS may continue in packet transfer mode. It is checked that the MS continues operating the uplink TBF by sending RLC data blocks on the PS resources. The MS requests circuit switched resources by sending the PACKET CS REQUEST on PACCH. The SS responds with the PACKET CS COMMAND on PACCH which encapsulates a DTM ASSIGNMENT COMMAND. The location update procedure is completed on the assigned circuit switched resources. Prior to sending the CHANNEL RELEASE message on the main DCCH, the SS sends the PACKET CS RELEASE INDICATION message on PACCH to the MS indicating that the RR connection is going to end. The PACKET CS RELEASE INDICATION indicates that when the RR connection is released the MS may maintain it's uplink TBF. The packet switched resources are not re-allocated. The MS responds with the PACKET SI STATUS message on PACCH. The SS sends the MS any requested SI messages encapsulated within PACKET SERVING CELL SI messages on PACCH. The MS responds with the PACKET SI STATUS message indicating receipt of the required SI messages. The SS then sends the CHANNEL RELEASE message on the main DCCH indicating in the Enhanced DTM Release Indication IE that the MS may continue in packet transfer mode. It is checked that the MS continues operating the uplink TBF by sending RLC data blocks on the PS resources.
Maximum Duration of Test
5 minutes
Expected Sequence
Step
Direction
Message
Comments
1
MS
Trigger the MS to initiate an uplink packet transfer
containing 1000 octets.
2
MS->SS
DTM REQUEST
Sent on main DCCH.
3
SS->MS
PACKET ASSIGNMENT
Sent on main DCCH.
See specific message contents.
4
SS<->MS
{ Uplink data }
Macro.
5
SS->MS
HANDOVER COMMAND
Sent on main DCCH.
See specific message contents.
The following messages are sent and received on Cell B.
6
MS->SS
HANDOVER ACCESS
Repeated on every burst of the uplink main DCCH (and optionally on the SACCH) until reception of PHYSICAL INFORMATION. Handover Reference as included in the HANDOVER COMMAND.
7
SS->MS
PHYSICAL INFORMATION
Sent on main DCCH.
8
MS->SS
HANDOVER COMPLETE
Sent on main DCCH.
9
SS->MS
DTM INFORMATION
Sent on main DCCH.
10
MS->SS
GPRS INFORMATION
Sent on main DCCH.
Contains a ROUTING AREA UPDATE REQUEST
message.
11
SS->MS
GPRS INFORMATION
Sent on main DCCH.
Contains a ROUTING AREA UPDATE ACCEPT message.
Does not allocate MS a new P-TMSI.
12
MS->SS
DTM REQUEST
Sent on main DCCH.
13
SS->MS
PACKET ASSIGNMENT
Sent on main DCCH.
See specific message contents.
14
SS<->MS
{ Uplink data }
Macro.
15
It is checked that the MS continues to transmit uplink data during Steps 16 to 39 below.
16
SS->MS
DISCONNECT
Sent on main DCCH.
The active speech call is disconnected.
17
MS->SS
RELEASE
Sent on main DCCH.
18
SS->MS
RELEASE COMPLETE
Sent on main DCCH.
19
SS->MS
PACKET CS RELEASE INDICATION
Sent on PACCH.
See specific message contents.
20
MS->SS
PACKET SI STATUS
Sent on PACCH.
Indicates possible non receipt of required SI messages.
Steps 21 to 23 are performed if the MS indicates non-receipt of required SI messages in Step 20.
21
SS->MS
PACKET SERVING CELL SI
Sent on PACCH.
Contains an SI message requested in Step 20.
22
Step 21 is repeated until all requested required SI messages have been sent to the MS.
23
MS->SS
PACKET SI STATUS
Sent on PACCH.
Indicates reception of SI13, SI3 and SI1.
24
SS->MS
CHANNEL RELEASE
Sent on main DCCH.
See specific message contents.
25
MS->SS
PACKET CS REQUEST
Sent on PACCH.
Establishment Cause = Location Updating
26
SS->MS
PACKET CS COMMAND
Sent on PACCH.
Encapsulates a DTM ASSIGNMENT COMMAND.
See specific message contents.
27
MS->SS
LOCATION UPDATE REQUEST
Sent on main DCCH.
Location Updating Type = normal
28
MS ->SS
CLASSMARK CHANGE
Sent on main DCCH.
29
SS ->MS
AUTHENTICATION REQUEST
Sent on main DCCH.
30
MS ->SS
AUTHENTICATION RESPONSE
Sent on main DCCH.
31
SS ->MS
CIPHERING MODE COMMAND
Sent on main DCCH.
Ciphering = on
32
MS ->SS
CIPHERING MODE COMPLETE
Sent on main DCCH.
33
SS ->MS
LOCATION UPDATE ACCEPT
Sent on main DCCH.
Does not allocate a new TMSI.
34
SS->MS
PACKET CS RELEASE INDICATION
Sent on PACCH.
See specific message contents.
35
MS->SS
PACKET SI STATUS
Sent on PACCH.
Indicates possible non receipt of required SI messages.
Steps 36 to 38 are performed if the MS indicates non-receipt of required SI messages in Step 35.
36
SS->MS
PACKET SERVING CELL SI
Sent on PACCH.
Contains an SI message requested in Step 35.
37
Step 36 is repeated until all requested required SI messages have been sent to the MS.
38
MS->SS
PACKET SI STATUS
Sent on PACCH.
Indicates reception of SI13, SI3 and SI1.
39
SS->MS
CHANNEL RELEASE
Sent on main DCCH.
See specific message contents.
40
SS<->MS
{ Uplink data transfer }
Macro - Completion of the 1kB of Data.
Specific Message Contents
PACKET ASSIGNMENT (Step 3 and Step 13):
Information Element
Value/remark
As default message contents except:
RR Packet Uplink Assignment IE
- TIMESLOT_ALLOCATION
(N 1) MOD 8
RR Packet Downlink Assignment IE
Not included
HANDOVER COMMAND (Step 5):
Information Element
Value/remark
As default message contents, except:
Channel Description
- Timeslot Number
N (chosen arbitrarily)
- Channel Type
TCH/F
Cell Description
Default values from Cell B
Synchronization Indication
- Report Observed Time Difference
Shall not be included.
- Synchronization Indication
"Non synchronized".
- Normal Cell Indication
Ignore out of range timing advance.
PACKET CS RELEASE INDICATION (Step 19 and Step 34):
Information Element
Value/remark
As default message contents, except:
- GLOBAL TFI
The TFI of the current uplink TBF.
- ENHANCED PACKET CS RELEASE INDICATION
1 (RR connection released)
The subsequent message encoding indicates that when the RR connection is released the MS maintains it's uplink TBF.
CHANNEL RELEASE (Step 24 and Step 39):
Information Element
Value/remark
As default message contents, except:
Enhanced DTM CS Release Indication IE
1 (MS allowed to continue in packet transfer mode)
DTM ASSIGNMENT COMMAND (Step 26):
Information Element
Value/remark
As default message contents except:
Channel Description IE
- TN
N
- Channel Type
TCH/F
Channel Mode IE
Full Rate Version 1
RR Packet Uplink Assignment IE
Not included.
RR Packet Downlink Assignment IE
Not included.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.5.5.4 Change of LA in NW Mode I
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.5.5.4.1 Conformance Requirements
|
If the MS and the network in mode I support enhanced DTM CS release procedure and the location area of the MS has changed while in dual transfer mode, the MS shall send an indication to the network that in this case the enhanced DTM CS release procedure shall not be used. This indication is sent in the PACKET SI STATUS or PACKET PSI STATUS message. After the receipt of the indication the network shall release the RR connection and PS resources. Upon receipt of a CHANNEL RELEASE message the MS shall initiate the Combined RA/LA Update procedure.
References
3GPP TS 43.055, sub-clauses 6.4.4.1
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.5.5.4.2 Test Purpose
|
To verify that in response to the NW initiating the Enhanced CS Release procedure the MS requests that the procedure shall not be used following a change of location area whilst the MS was in dedicated mode in a network using network mode I.
To verify that following the release of packet and circuit switched resources the MS performs the Combined Routing Are Update procedure following a change of location area whilst the MS was in dedicated mode in a network using network mode I.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.5.5.4.3 Method of Test
|
Initial Conditions
System Simulator:
- 2 cells, A and B operating in NW Mode I with different LAC, both supporting Enhanced DTM.
Mobile Station:
- The MS is in the active state (U10) of a call on Cell A on timeslot N.
- The MS is in packet idle mode, with a TMSI, P-TMSI allocated and PDP context 1 activated.
Specific PICS Statements
-
PIXIT Statements
-
Test Procedure
The MS, whilst in dedicated mode, is triggered to initiate packet uplink data transfer in RLC unacknowledged mode and sends a DTM REQUEST message. On receipt of the DTM REQUEST message, the SS assigns the MS packet switched resources using a PACKET ASSIGNMENT message. Before the MS has completed transmission of the uplink data, the SS orders a handover to Cell B. Following handover to Cell B the non-combined routing area update procedure is performed on the main DCCH. The MS resumes transmission of the uplink data. The active speech call is disconnected. The SS sends the PACKET CS RELEASE INDICATION message on PACCH to the MS indicating that the RR connection is going to end. The PACKET CS RELEASE INDICATION indicates that when the RR connection is released, the MS may maintain the uplink TBF. The packet switched resources are not re-allocated. The MS responds with the PACKET SI STATUS message on PACCH in which it requests the release of both packet and circuit switched resources. The SS responds with the CHANNEL RELEASE message which indicates that the MS may not continue in packet transfer mode. It is checked that the MS no longer transmits data on the previously assigned packet switched resources. The MS requests packet switched resources in order to perform the Combined Routing Area update procedure. Following completion of the Combined Routing Area Update procedure the MS requests packet switched resources in order to continue with the transfer of user data.
Maximum Duration of Test
5 minutes
Expected Sequence
Step
Direction
Message
Comments
1
MS
Trigger the MS to initiate an uplink packet transfer
containing 1000 octets.
2
MS->SS
DTM REQUEST
Sent on main DCCH.
3
SS->MS
PACKET ASSIGNMENT
Sent on main DCCH.
See specific message contents.
4
SS<->MS
{ Uplink data }
Macro.
5
SS->MS
HANDOVER COMMAND
Sent on main DCCH.
See specific message contents.
The following messages are sent and received on Cell B.
6
MS->SS
HANDOVER ACCESS
Repeated on every burst of the uplink main DCCH (and optionally on the SACCH) until reception of PHYSICAL INFORMATION. Handover Reference as included in the HANDOVER COMMAND.
7
SS->MS
PHYSICAL INFORMATION
Sent on main DCCH.
8
MS->SS
HANDOVER COMPLETE
Sent on main DCCH.
9
SS->MS
DTM INFORMATION
Sent on main DCCH.
10
MS->SS
GPRS INFORMATION
Sent on main DCCH.
Contains a ROUTING AREA UPDATE REQUEST
message.
11
SS->MS
GPRS INFORMATION
Sent on main DCCH.
Contains a ROUTING AREA UPDATE ACCEPT message.
Does not allocate MS a new P-TMSI.
12
MS->SS
DTM REQUEST
Sent on main DCCH.
13
SS->MS
PACKET ASSIGNMENT
Sent on main DCCH.
See specific message contents.
14
SS<->MS
{ Uplink data }
Macro.
15
It is checked that the MS continues to transmit uplink data during Steps 16 to 20 below.
16
SS->MS
DISCONNECT
Sent on main DCCH.
The active speech call is disconnected.
17
MS->SS
RELEASE
Sent on main DCCH.
18
SS->MS
RELEASE COMPLETE
Sent on main DCCH.
19
SS->MS
PACKET CS RELEASE INDICATION
Sent on PACCH.
See specific message contents.
20
MS->SS
PACKET SI STATUS
Sent on PACCH.
PS_REL_REQ = 1
The MS requests release of both packet and circuit switched resources.
21
SS->MS
CHANNEL RELEASE
Sent on main DCCH.
See specific message contents.
22
SS
It is checked that the MS no longer transmits data on the packet switched resources assigned at Step 13.
23
MS -> SS
CHANNEL REQUEST
Sent on RACH.
Access Type = MM Procedure
24
SS -> MS
IMMEDIATE ASSIGNMENT
Sent on AGCH.
Allocates uplink TBF on single timeslot.
25
SS<->MS
{ Uplink data block transfer }
Macro.
The received RLC data blocks contain :-
ROUTING AREA UPDATE REQUEST
Update type = 'Combined RA/LA updating'
26
SS -> MS
IMMEDIATE ASSIGNMENT
Sent on PCH.
Allocates downlink TBF on single timeslot.
27
SS<->MS
{ Downlink data transfer }
Macro.
The transmitted RLC data blocks contain :-
ROUTING AREA UPDATE ACCEPT
Update result = 'Combined RA/LA updated'
Does not assign a new P-TMSI.
28
MS -> SS
CHANNEL REQUEST
Sent on RACH
Access Type = Two Phase Access Request
29
SS -> MS
IMMEDIATEASSIGNMENT
Sent on AGCH.
Single block assignment, to order the MS to follow the two phase access procedure.
30
MS -> SS
PACKET RESOURCE REQUEST
Sent on PACCH.
31
SS -> MS
PACKET UPLINK ASSIGNMENT
Sent on PACCH.
uplink dynamic allocation, no starting time
32
SS<->MS
{ Uplink data transfer }
Macro - Completion of the 1kB of Data.
Specific Message Contents
PACKET ASSIGNMENT (Step 3 and Step 13):
As default message contents except:
RR Packet Uplink Assignment IE
- TIMESLOT_ALLOCATION
(N 1) MOD 8
RR Packet Downlink Assignment IE
Not included
HANDOVER COMMAND (Step 5):
Information Element
Value/remark
As default message contents, except:
Channel Description
- Timeslot Number
N (chosen arbitrarily)
- Channel Type
TCH/F
Cell Description
Default values from Cell B
Synchronization Indication
- Report Observed Time Difference
Shall not be included.
- Synchronization Indication
"Non synchronized".
- Normal Cell Indication
Ignore out of range timing advance.
PACKET CS RELEASE INDICATION (Step 19):
Information Element
Value/remark
As default message contents, except:
- GLOBAL TFI
The TFI of the current uplink TBF.
- ENHANCED PACKET CS RELEASE INDICATION
1 (RR connection released)
The subsequent message encoding indicates that when the RR connection is released the MS maintains it's uplink TBF.
CHANNEL RELEASE (Step 21):
Information Element
Value/remark
As default message contents, except:
Enhanced DTM CS Release Indication IE
0 (MS not allowed to continue in packet transfer mode)
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.6 Intra SGSN PS Handover
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.6.1 Intra SGSN PS Handover / Synchronized cell case
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.6.1.1 Intra SGSN PS Handover / Synchronized cell case / successful
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.6.1.1.1 Conformance requirements
|
The following synchronisation mechanisms are used for PS handover:
- Non-synchronised.
- Synchronised.
- Pre-Synchronised.
The synchronised and pre-synchronised cases are shown in figures 23 and 25 and have different mechanisms for the provision of the timing advance that are described in 3GPP TS 45.010 [26].
NOTE: The pseudo-synchronised case is not supported by the PS handover feature.
If the timing advance with the new cell calculated by the mobile station is not out of range, i.e. smaller than or equal to the maximum timing advance that can be coded as specified in 3GPP TS 44.004, or if the new cell does accept out of range timing advance as indicated in the PS HANDOVER COMMAND message, the mobile station acts on the message.
After having switched to the assigned channels, if the Handover Reference information is included within the PS HANDOVER COMMAND message the mobile station shall send four times the PS HANDOVER ACCESS message.
The mobile station activates the channels in sending and receiving mode. The MS may activate the channels in downlink while sending access bursts.
References
3GPP TS 43.129, subclasses 6.2.2
3GPP TS 44.060, subclasses 8.10.4.1 and 8.10.4.4.2.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.6.1.1.2 Test purposes
|
To verify that while in uplink acknowledged mode operation the MS performs successfully synchronized PS Handover from A/Gb to A/Gb.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.6.1.1.3 Method of test
|
Initial Conditions
System Simulator:
2 cells A and B, GPRS supported, NC 2 mode, PCCCH not present.
The RF level of cell A is –50 dBm and cell B – 60 dBm.
Mobile Station:
The MS is GPRS attached on cell A, a P-TMSI allocated and test PDP context2 activated.
Specific PICS Statements
-
PIXIT Statements
-
Test Procedure
The MS is triggered to initiate packet uplink transfer 2000 octets in the RLC acknowledged mode on cell A. After a successful uplink PDCH assignment the SS sends PACKET DOWNLINK DUMMY indicating the assigned USF assigned to the MS. The MS sends a RLC radio block. The SS allows the MS to transfer about 30 RLC blocks.
The SS provides the MS a minimum set of System Info Types in order to perform a A/Gb to A/Gb synchronized PS Handover by sending them in PACKET NEIGHBOUR CELL DATA message.
The SS sends PS HANDOVER COMMAND to assign a PDCH on cell B. The MS moves to cell B and resumes the uplink data transfer. The MS completes the uplink data transfer.
Maximum Duration of Test
5 minutes.
Expected Sequence
Step
Direction
Message
Comments
1
{Uplink dynamic allocation two phase access}
The following messages received on cell A.
n = 2000 octets in RLC acknowledged mode (Test PDP context2), without starting time,
USF_GRANULARITY = 1 block,
RLC_DATA_BLOCKS_GRANTED = open-end
TLLI_BLOCK_CHANNEL_CODING: cs1,
CHANNEL_CODING_COMMAND: cs1
2
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
USF assigned to the MS
3
MS -> SS
UPLINK RLC DATA BLOCK or PACKET MEASUREMENT REPORT
Received on the assigned PDTCH.
In case of Uplink data block check that the coding and the TFI are correct.
4
Repeat step 2 and 3 in total of 30 times.
5
SS -> MS
PACKET NEIGHBOUR CELL DATA
Sent on the PACCH of the assigned PDCH.
Containing : System Info Type 1, System Info Type 3 and
System Info Type 13.
USF assigned to the MS.
6
MS -> SS
UPLINK RLC DATA BLOCK or PACKET MEASUREMENT REPORT
Received on the assigned PDTCH.
7
SS -> MS
PS HANDOVER COMMAND
Sent on the PACCH of the assigned PDCH . USF not assigned to the MS.
The following messages are received on cell B.
8
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
120 ms (T_GSM_delay) after step 7. USF assigned to the MS.
9
MS -> SS
PACKET UPLINK DUMMY CONTROL BLOCK or UPLINK RLC DATA BLOCK or PACKET MEASUREMENT REPORT
Received on the assigned PDTCH.
Repeat steps 8 and 9 for maximum of 100 ms or until UPLINK RLC DATA BLOCK is received.
(Data block may contain empty LLC PDU for Cell Update. In that case the SS shall accept Packet Resource Request from MS and respond with Packet Uplink Assignment.)
NOTE: The empty LLC PDU may be accompanied by another low priority RLC data block (with Packet Resource Request and Packet Uplink Assignment as required), in order to ensure that the radio resources are used efficiently.
10
{Completion of uplink RLC data block transfer}
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.6.1.2 Intra SGSN PS Handover / Synchronized cell case / Abnormal Case / T3218 expiry
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.6.1.2.1 Conformance requirements
|
In case of initial access failure in the target cell, including the case where the MS fails to acquire time alignment information (for the unsynchronised network case), the MS is allowed to revert to the old cell. As is defined currently in 3GPP TS 44.060 [7], the MS shall return to the old cell and send a Packet Cell Change Failure message with the appropriate cause.
If the MS was in packet transfer mode (or MAC-shared state) before the attempted handover it will, when going back to the old cell, send a Packet Cell Change Failure message and resume TBFs which were ongoing in the old cell.
A mobile station operating in A/Gb mode shall consider the PS handover to A/Gb mode to have failed for the following reasons:
- Timer T3218 expires while in the new cell.
A mobile station operating in A/Gb mode when a PS handover to A/Gb mode fails shall proceed as follows:
- If timer T3218 expired it shall return to the cell on which the PS HANDOVER COMMAND message was received.
- Send a Packet Cell Change Failure message with the cause code set to "No response on target cell" if timer T3218 or T3216 expired, otherwise "PS Handover failure-others". The message shall be sent on PACCH .
- The transmission of a Packet Cell Change Failure message terminates the PS handover procedure in the mobile station and after the transmission of this message the mobile station is therefore allowed to request the establishment of additional uplink TBFs.
- After terminating the PS handover procedure the mobile station shall resume all uplink and downlink TBFs that were ongoing in the old cell prior to receiving the PS HANDOVER COMMAND message. Timers T3180 (uplink TBFs) and T3190 (downlink TBFs) corresponding to these TBFs shall be re-started.
- For each TBF that is resumed the corresponding RLC state machine shall reflect its state when the last RLC data block was transmitted for that TBF in the old cell (uplink TBFs) and the last RLC data block was received for that TBF in the old cell (downlink TBFs).
References
3GPP TS 43.129, subclasses 5.7.2.1
3GPP TS 44.060, subclasses 8.10.5.1
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.6.1.2.2 Test purposes
|
To verify that the MS, when PS handover failed due to T3218 expiry, returns to the cell on which PS HANDOVER COMMAND message was received, sends a PACKET CELL CHANGE FAILURE message with cause “No response on target cell” and resumes the TBFs that were ongoing in the old cell.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.6.1.2.3 Method of test
|
Initial Conditions
System Simulator:
2 cells A and B, GPRS supported, NC 2 mode, PCCCH not present.
The RF level of cell A is –50 dBm and cell B – 60 dBm.
Mobile Station:
The MS is GPRS attached on cell A, a P-TMSI allocated and test PDP context2 activated.
Specific PICS Statements
-
PIXIT Statements
-
Test Procedure
The MS is triggered to initiate packet uplink transfer 2000 octets in the RLC acknowledged mode on cell A. After a successful uplink PDCH assignment the SS sends PACKET DOWNLINK DUMMY indicating the USF assigned to the MS. The SS allows the MS to transfer about 30 RLC blocks.
The SS provides the MS a minimum set of System Info Types in order to perform a A/Gb to A/Gb synchronized PS Handover by sending them in PACKET NEIGHBOUR CELL DATA message.
The SS sends PS HANDOVER COMMAND to assign a PDCH on cell B. No USF is assigned to the MS on cell B for 1s (T3218). The SS assigns USF to the MS on the old cell A. MS send PACKET CELL CHANGE FAILURE with cause value “No response on target cell” and resumes the uplink data transfer.
Maximum Duration of Test
5 minutes.
Expected Sequence
Step
Direction
Message
Comments
1
{Uplink dynamic allocation two phase access}
The following messages received on cell A.
n = 400 octets in RLC acknowledged mode (Test PDP context2), without starting time,
USF_GRANULARITY = 1 block,
RLC_DATA_BLOCKS_GRANTED = open-end
TLLI_BLOCK_CHANNEL_CODING: cs1,
CHANNEL_CODING_COMMAND: cs1
2
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
USF assigned to the MS.
3
MS -> SS
UPLINK RLC DATA BLOCK or PACKET MEASUREMENT REPORT
Received on the assigned PDTCH. Check that the coding and the TFI are correct.
4
Repeat step 2 and 3 in total of 30 times.
5
SS -> MS
PACKET NEIGHBOUR CELL DATA
All instances are sent on the PACCH of the assigned PDCH.
Containing : System Info Type 1, System Info Type 3 and
System Info Type 13 of cell B.
USF assigned to the MS.
6
MS -> SS
UPLINK RLC DATA BLOCK or PACKET MEASUREMENT REPORT
Received on the assigned PDTCH.
7
SS -> MS
PS HANDOVER COMMAND
Sent on the PACCH of the assigned PDCH. USF not assigned to the MS.
The following messages are sent on cell B.
8
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
Sent on PACCH assigned in step 7. USF not addressing the MS.
9
SS
Check that no data block is transmitted by the MS in the next radio block.
Steps 8 and 9 are repeated for 1s (T3218).
The following messages are sent 200 ms after step 9 on cell A.
10
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
USF allocated in PACKET UPLINK ASSIGNMENT from step 1 assigned to the MS.
11
MS -> SS
PACKET CELL CHANGE FAILURE
Cause:"No response on target cell”
12
{Completion of uplink RLC data block transfer}
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.6.1.3 Intra SGSN PS Handover / Synchronized cell case / Abnormal Case / Minimum set of SI not available
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.6.1.3.1 Conformance requirements
|
In case of initial access failure in the target cell, including the case where the MS fails to acquire time alignment information (for the unsynchronised network case), the MS is allowed to revert to the old cell. As is defined currently in 3GPP TS 44.060 [7], the MS shall return to the old cell and send a Packet Cell Change Failure message with the appropriate cause.
If the MS was in packet transfer mode (or MAC-shared state) before the attempted handover it will, when going back to the old cell, send a Packet Cell Change Failure message and resume TBFs which were ongoing in the old cell.
A mobile station operating in A/Gb mode shall consider the PS handover to A/Gb mode to have failed for the following reasons:
- If it has not stored a valid minimum set of the following of PSI or SI messages (provided via PACKET NEIGHBOUR CELL DATA messages, see sub-clause 8.8.1) required for mobile station to operate in the new cell: PSI1, a consistent set of PSI2 messages and PSI14 (if PBCCH allocated in the new cell) or SI3, SI1 (if present in the new cell) and SI13 messages (if PBCCH not allocated in the new cell).
A mobile station operating in A/Gb mode when a PS handover to A/Gb mode fails shall proceed as follows:
- Send a Packet Cell Change Failure message with the cause code set to "No response on target cell" if timer T3218 or T3216 expired, otherwise "PS Handover failure-others". The message shall be sent on PACCH .PACCH.
- The transmission of a Packet Cell Change Failure message terminates the PS handover procedure in the mobile station and after the transmission of this message the mobile station is therefore allowed to request the establishment of additional uplink TBFs.
References
3GPP TS 43.129, subclasses 5.7.2.1
3GPP TS 44.060, subclasses 8.10.5.1
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.6.1.3.2 Test purposes
|
To verify that the MS, when PS handover failed due to a valid minimum set of SI messages for the new cell not stored, returns to the cell on which PS HANDOVER COMMAND message was received, sends a PACKET CELL CHANGE FAILURE message with cause “PS Handover failure-others” and resumes the TBFs that were ongoing in the old cell.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.6.1.3.3 Method of test
|
Initial Conditions
System Simulator:
2 cells A and B, GPRS supported, NC 2 mode, PCCCH not present.
The RF level of cell A is –50 dBm and cell B – 60 dBm.
Mobile Station:
The MS is GPRS attached on cell A, a P-TMSI allocated and test PDP context2 activated.
Specific PICS Statements
-
PIXIT Statements
-
Test Procedure
The MS is triggered to initiate packet uplink transfer 2000 octets in the RLC acknowledged mode on cell A. After a successful uplink PDCH assignment the SS sends PACKET DOWNLINK DUMMY indicating the USF assigned to the MS. The SS allows the MS to transfer about 30 RLC blocks.
The SS provides the MS a set of System Info Type 1 and 3 messages in PACKET NEIGHBOUR CELL DATA message but not System Info Type 13 for the new cell B.
The SS sends PS HANDOVER COMMAND to assign a PDCH on cell B. USF is assigned to the MS on cell B on the assigned PDCH and it is checked that the MS does not send RLC blocks on the new cell B.
The SS assigns USF to the MS on the old cell A. MS send PACKET CELL CHANGE FAILURE with cause value “PS Handover failure-others” and resumes the uplink data transfer.
Maximum Duration of Test
5 minutes.
Expected Sequence
Step
Direction
Message
Comments
1
{Uplink dynamic allocation two phase access}
The following messages received on cell A.
n = 400 octets in RLC acknowledged mode (Test PDP context2), without starting time,
USF_GRANULARITY = 1 block,
RLC_DATA_BLOCKS_GRANTED = open-end
TLLI_BLOCK_CHANNEL_CODING: cs1,
CHANNEL_CODING_COMMAND: cs1
2
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
USF assigned to the MS.
3
MS -> SS
UPLINK RLC DATA BLOCK or PACKET MEASUREMENT REPORT
Received on the assigned PDTCH. Check that the coding and the TFI are correct.
4
Repeat step 2 and 3 in total of 30 times.
5
SS -> MS
PACKET NEIGHBOUR CELL DATA
All instances are sent on the PACCH of the assigned PDCH.
Containing :Containing: System Info Type 1and System Info Type 3 of cell B.
USF assigned to the MS.
6
MS -> SS
UPLINK RLC DATA BLOCK or PACKET MEASUREMENT REPORT
Received on the assigned PDTCH.
7
SS -> MS
PS HANDOVER COMMAND
Sent on the PACCH of the assigned PDCH. USF not assigned to the MS.
The following messages are sent on cell B.
8
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
Sent on PACCH assigned in step 7. USF assigned to the MS.
9
SS
Check that no data block is transmitted by the MS in the next radio radio block.
The following messages are sent 200 ms after step 9 on cell A.
10
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
USF allocated in PACKET UPLINK ASSIGNMENT from step 1 assigned to the MS.
11
MS -> SS
PACKET CELL CHANGE FAILURE
Cause:" PS Handover failure-others”
12
{Completion of uplink RLC data block transfer}
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.6.2 Intra SGSN PS Handover / Pre-synchronized cell case
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.6.2.1 Intra SGSN PS Handover / Pre-synchronized cell case / successful / RLC reset
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.6.2.1.1 Conformance requirements
|
The following synchronisation mechanisms are used for PS handover:
• Non-synchronised.
• Synchronised.
• Pre-Synchronised.
The synchronised and pre-synchronised cases are shown in figures 23 and 25 and have different mechanisms for the provision of the timing advance that are described in 3GPP TS 45.010 [26].
NOTE: The pseudo-synchronised case is not supported by the PS handover feature.
In the case of pre-synchronised handover the MS may receive the timing advance information to use in uplink in the target cell in the PS Handover Command message (if no timing advance information is included, the mobile station uses a default timing advance in the target cell). In a pre-synchronised or synchronised handover, the Packet Physical information message is not sent in the target cell.
If the timing advance with the new cell calculated by the mobile station is not out of range, i.e. smaller than or equal to the maximum timing advance that can be coded as specified in 3GPP TS 44.004, or if the new cell does accept out of range timing advance as indicated in the PS HANDOVER COMMAND message, the mobile station acts on the message.
After having switched to the assigned channels, if the Handover Reference information is included within the PS HANDOVER COMMAND message the mobile station shall send four times the PS HANDOVER ACCESS message.
The mobile station activates the channels in sending and receiving mode. The MS may activate the channels in downlink while sending access bursts.
If the PS HANDOVER COMMAND indicates RLC reset for a TBF allocated in the new cell corresponding to a PFC receiving a PS handover, the target BSS shall initialize a new RLC entity to support that TBF. Otherwise, the TBF allocated in the new cell shall be supported using the same RLC entity used to support the TBF in the old cell corresponding to the same PFC (i.e. the RLC state machine is maintained across PS handover).
References
3GPP TS 43.129, subclasses 5.1.2 and 6.2.2
3GPP TS 44.060, subclasses 8.10.3.2; 8.10.4.1 and 8.10.4.4.2.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.6.2.1.2 Test purposes
|
To verify that while in uplink acknowledged mode operation the MS performs successfully pre-Synchronised PS Handover from A/Gb to A/Gb and that the RLC is not maintained over PS handover.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.6.2.1.3 Method of test
|
Initial Conditions
System Simulator:
2 cells A (RAI 1) and B (RAI 1), GPRS supported, NC 2 mode, PCCCH not present.
The RF level of cell A is –50 dBm and cell B – 60 dBm.
Mobile Station:
The MS is GPRS attached on cell A, a P-TMSI allocated and test PDP context2 activated.
Specific PICS Statements
-
PIXIT Statements
-
Test Procedure
The MS is triggered to initiate packet uplink transfer 2000 octets in the RLC acknowledged mode on cell A. After a successful uplink PDCH assignment the SS sends PACKET DOWNLINK DUMMY indicating the assigned USF assigned to the MS. The MS sends a RLC radio block. The SS allows the MS to transfer about 30 RLC blocks.
The SS provides the MS a minimum set of System Info Types in order to perform a A/Gb to A/Gb pre-synchronized PS Handover by sending them in PACKET NEIGHBOUR CELL DATA message.
The SS sends PS HANDOVER COMMAND to assign a PDCH on cell B, indicating RLC reset and containing a handover reference. The MS moves to cell B sends PS HANDOVER ACCESS resets the RLC entity and resends the unacknowledged RLC data blocks. The MS completes the uplink data transfer.
Maximum Duration of Test
5 minutes.
Expected Sequence
Step
Direction
Message
Comments
1
{Uplink dynamic allocation two phase access}
The following messages received on cell A.
n = 2000 octets in RLC acknowledged mode (Test PDP context2), without starting time,
USF_GRANULARITY = 1 block,
RLC_DATA_BLOCKS_GRANTED = open-end
TLLI_BLOCK_CHANNEL_CODING: cs1,
CHANNEL_CODING_COMMAND: cs1
2
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
USF assigned to the MS
3
MS -> SS
UPLINK RLC DATA BLOCK or PACKET MEASUREMENT REPORT
Received on the assigned PDTCH. Check that the coding BSN and the TFI are correct.
4
Repeat step 2 and 3 in total of 30 times.
5
SS -> MS
PACKET NEIGHBOUR CELL DATA
Sent on the PACCH of the assigned PDCH.
Containing : System Info Type 1, System Info Type 3 and System Info Type 13.
USF assigned to the MS.
6
MS -> SS
UPLINK RLC DATA BLOCK or PACKET MEASUREMENT REPORT
Received on the assigned PDTCH. Check that the coding BSN and the TFI are correct.
7
SS -> MS
PS HANDOVER COMMAND
Sent on the PACCH of the assigned PDCH . USF not assigned to the MS.
The following messages are received on cell B.
8
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
120 ms (T_GSM_delay) after step 7. USF assigned to the MS.
9
MS -> SS
PS HANDOVER ACCESS
As 4 access bursts. Check that handover reference is correct.
10
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
USF assigned to the MS.
11
MS -> SS
PACKET UPLINK DUMMY CONTROL BLOCK or
UPLINK RLC DATA BLOCK or PACKET MEASUREMENT REPORT
Repeat steps 10 and 11 for maximum of 100 ms or until UPLINK RLC DATA BLOCK is received.
Received on the assigned PDTCH.
(Data block may contain empty LLC PDU for Cell Update. In that case the SS shall accept Packet Resource Request from MS and respond with Packet Uplink Assignment.)
NOTE: The empty LLC PDU may be accompanied by another low priority RLC data block (with Packet Resource Request and Packet Uplink Assignment as required), in order to ensure that the radio resources are used efficiently.
Check that BSN = 0.
12
{Completion of uplink RLC data block transfer}
Specific Message Contents
PS HANDOVER COMMAND message in step 7:
As default message contents except
PS Handover Radio Resources IE
present
SI
10 Pre-synchronized
RLC_RESET
1
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.6.2.2 Intra SGSN PS Handover / Pre-synchronized cell case / Frequency parameters / successful
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.6.2.2.1 Conformance requirements
|
The following synchronisation mechanisms are used for PS handover:
• Non-synchronised.
• Synchronised.
• Pre-Synchronised.
The synchronised and pre-synchronised cases are shown in figures 23 and 25 and have different mechanisms for the provision of the timing advance that are described in 3GPP TS 45.010 [26].
NOTE: The pseudo-synchronised case is not supported by the PS handover feature.
In the case of pre-synchronised handover the MS may receive the timing advance information to use in uplink in the target cell in the PS Handover Command message (if no timing advance information is included, the mobile station uses a default timing advance in the target cell). In a pre-synchronised or synchronised handover, the Packet Physical information message is not sent in the target cell.
If the timing advance with the new cell calculated by the mobile station is not out of range, i.e. smaller than or equal to the maximum timing advance that can be coded as specified in 3GPP TS 44.004, or if the new cell does accept out of range timing advance as indicated in the PS HANDOVER COMMAND message, the mobile station acts on the message.
After having switched to the assigned channels, if the Handover Reference information is included within the PS HANDOVER COMMAND message the mobile station shall send four times the PS HANDOVER ACCESS message.
The mobile station activates the channels in sending and receiving mode. The MS may activate the channels in downlink while sending access bursts.
References
3GPP TS 43.129, subclasses 5.1.2 and 6.2.2
3GPP TS 44.060, subclasses 8.10.3.2; 8.10.4.1 and 8.10.4.4.2.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.6.2.2.2 Test purposes
|
To verify that while in uplink acknowledged mode operation the MS performs successfully pre-Synchronised PS Handover from A/Gb to A/Gb and applies frequency hopping settings on cell B correctly which are assigned by ‘Indirect Encoding’ and ‘Direct encoding 1’ method.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.6.2.2.3 Method of test
|
Initial Conditions
System Simulator:
2 cells A (RAI 1) and B (RAI 1), GPRS supported, NC 2 mode, PCCCH not present.
The RF level of cell A is –50 dBm and cell B – 60 dBm.
Mobile Station:
The MS is GPRS attached on cell A, a P-TMSI allocated and test PDP context2 activated.
Specific PICS Statements
-
PIXIT Statements
-
Test Procedure
The MS is triggered to initiate packet uplink transfer 2000 octets in the RLC acknowledged mode on cell A. After a successful uplink PDCH assignment the SS sends PACKET DOWNLINK DUMMY indicating the assigned USF assigned to the MS. The MS sends a RLC radio block. The SS allows the MS to transfer about 30 RLC blocks.
The SS provides the MS a set of System Info messages in order to perform a A/Gb to A/Gb pre-synchronized PS Handover by sending them in PACKET NEIGHBOUR CELL DATA message.
The SS sends PS HANDOVER COMMAND to assign a hopping PDCH on cell B. The MS moves to cell B sends PS HANDOVER ACCESS and resends the unacknowledged RLC data blocks. The MS completes the uplink data transfer.
The procedure is performed for execution counter M=1 and 2 using different methods for assigning the hopping frequencies.
Maximum Duration of Test
5 minutes.
Expected Sequence
Step
Direction
Message
Comments
1
{Uplink dynamic allocation two phase access}
The following messages received on cell A.
n = 2000 octets in RLC acknowledged mode (Test PDP context2), without starting time,
USF_GRANULARITY = 1 block,
RLC_DATA_BLOCKS_GRANTED = open-end
TLLI_BLOCK_CHANNEL_CODING: cs1,
CHANNEL_CODING_COMMAND: cs1
2
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
USF assigned to the MS.
3
MS -> SS
UPLINK RLC DATA BLOCK or PACKET MEASUREMENT REPORT
Received on the assigned PDTCH. Check that the coding BSN and the TFI are correct.
4
Repeat step 2 and 3 in total of 30 times.
5
SS -> MS
PACKET NEIGHBOUR CELL DATA
All instances are sent on the PACCH of the assigned PDCH.
Containing : System Info Type 1, System Info Type 3 and System Info Type 13 of cell B (see Specific Message Contents).
USF assigned to the MS.
6
MS -> SS
UPLINK RLC DATA BLOCK or PACKET MEASUREMENT REPORT
Received on the assigned PDTCH. Check that the coding BSN and the TFI are correct.
7
SS -> MS
PS HANDOVER COMMAND
Sent on the PACCH of the assigned PDCH . USF not assigned to the MS.
The following messages are received on cell B.
8
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
120 ms (T_GSM_delay) after step 7. USF assigned to the MS.
9
MS -> SS
PS HANDOVER ACCESS
As 4 access bursts. Check that handover reference is correct.
10
MS -> SS
PACKET UPLINK DUMMY CONTROL BLOCK or
UPLINK RLC DATA BLOCK or PACKET MEASUREMENT REPORT
Repeat steps 10 and 11 for maximum of 100 ms or until UPLINK RLC DATA BLOCK is received.
Received on the assigned PDTCH.
(Data block may contain empty LLC PDU for Cell Update. In that case the SS shall accept Packet Resource Request from MS and respond with Packet Uplink Assignment.)
NOTE: The empty LLC PDU may be accompanied by another low priority RLC data block (with Packet Resource Request and Packet Uplink Assignment as required), in order to ensure that the radio resources are used efficiently.
11
{Completion of uplink RLC data block transfer}
Specific Message Contents
SYSTEM INFORMATION TYPE 13 of cell B and included in PACKET NEIGHBOUR CELL DATA in step 5:
For M = 1:
As default message contents except
- GPRS Mobile Allocation
- HSN
1 Hopping sequence 1
- 0 <RFL number list>
not present
- 0
using MA BITMAP
- <MA_LENGTH>
000101 (for GSM 900)
000011 (for other bands)
- <MA_BITMAP>
000111 3 belonging (for GSM 900)
0111 3 belonging (for other bands)
PACKET SYSTEM INFORMATION TYPE 13 on PACCH of cell B:
{GPRS Mobile Allocation}
- HSN
1 Hopping sequence 1
- 0 <RFL number list>
not present
- 0
using MA BITMAP
- <MA_LENGTH>
000101 (for GSM 900)
000011 (for other bands)
- <MA_BITMAP>
000111 3 belonging (for GSM 900)
0111 3 belonging (for other bands)
For M = 2 default SI13 and PSI13 of cell B are used.
PS HANDOVER COMMAND message in step 7:
For M = 1:
As default message contents except
PS Handover Radio Resources IE
Present
SI
10 Pre-synchronized
1<Frequency Parameters>}
present
- TSC
‘101’, same as BCCH of cell B
- 01 (Indirect encoding)
Indirect encoding struct
- MAIO
5
- MA_NUMBER
14…GPRS mobile allocation received in SI13 message
- 0 <CHANGE_MARK_1>
not present
- 0 <CHANGE_MARK_2>
not present
For M = 2:
As default message contents except
PS Handover Radio Resources IE
Present
SI
10 Pre-synchronized
1<Frequency Parameters>}
present
- TSC
‘101’, same as BCCH of cell B
- 10 (Direct encoding 1)
Direct encoding 1 struct
- MAIO
5
- GPRS Mobile Allocation
- HSN
1 Hopping sequence 1
- 0 <RFL number list>
not present
- 0
using MA BITMAP
- <MA_LENGTH>
000101 (for GSM 900)
000011 (for other bands)
- <MA_BITMAP>
000111 3 belonging (for GSM 900)
0111 3 belonging (for other bands)
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.6.3 Intra SGSN PS Handover / Non synchronized cell case
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.6.3.1 Intra SGSN PS Handover / Non synchronized cell case / PS Handover Access (8-bit / 11-bit format) / successful
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.6.3.1.1 Conformance requirements
|
The following synchronisation mechanisms are used for PS handover:
- Non-synchronised.
- Synchronised.
- Pre-Synchronised.
The non-synchronised cases are shown in figures 22 and 24 and are characterised by the requirement for the MS to obtain a valid uplink timing advance before it can transmit normal bursts. The MS shall notify its presence in the target cell through the transmission of access bursts to the BSS, and the BSS shall respond with a valid timing advance which in turn enables the MS to send normal bursts in uplink.
After having switched to the assigned channels, the mobile station shall send four times the PS HANDOVER ACCESS message. The mobile station shall start timer T3216 at the start point of the timeslot in which the PS HANDOVER ACCESS message is sent the first time on the PACCH.
If the network requests the transmission of the PS HANDOVER ACCESS message it shall be sent with highest transmission priority using either the 8-bit or 11-bit access burst format on the PACCH associated with any uplink TBF allocated in the PS HANDOVER COMMAND message for which the mobile station detects an assigned USF value. Its content consists of the handover reference field. The burst format used shall be that specified by the ACCESS_BURST_TYPE in the system information for the target cell.
The mobile station then activates the channels in receiving mode.
Upon reception of the PS HANDOVER ACCESS message containing the expected Handover Reference value, once the network has the RF characteristics that are necessary, it sends a PACKET PHYSICAL INFORMATION message to the mobile station on the PACCH.
When the mobile station receives a PACKET PHYSICAL INFORMATION message, it stops timer T3216, stops sending access bursts and activates the channels in sending and receiving mode.
The MS sends uplink LLC PDUs, e.g. a Routing Area Update Request message or uplink user data packets to the SGSN immediately after receiving the Packet Physical Information message or, in a synchronised or pre-synchronised handover, immediately if the PS Handover Access message is not required to be sent (see Section 6.2).
References
3GPP TS 43.129, subclasses 6.2.2, 5.1.2.3
3GPP TS 44.060, subclasses 8.10.4.4.4.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.6.3.1.2 Test purpose
|
To verify that while in uplink Acknowledged mode MS performs successfully Non-Synchronised PS Handover from A/Gb to A/Gb.
To verify that MS uses correct access burst format for the PS HANDOVER ACCESS message.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.6.3.1.3 Method of test
|
Initial Conditions
System Simulator:
Two cells A (RAI1, SI13 indicates 8-bit access burst format) and Cell B (RAI 1, SI13 indicates 11-bit access burst format), NC2 mode, GPRS supported, PCCCH not present.
Mobile Station:
The MS is GPRS attached on cell A, a P-TMSI allocated and test PDP context2 activated.
Specific PICS Statements
-
PIXIT Statements
-
Test Procedure
The MS is triggered to initiate packet uplink transfer 2000 octets in the RLC acknowledged mode on cell A. After a successful uplink PDCH assignment the SS sends PACKET DOWNLINK DUMMY indicating the assigned USF to the MS. The MS sends a RLC radio block. The SS allows the MS to transfer about 30 RLC blocks.
The SS provides the MS a minimum set of System Info Types in order to perform a A/Gb to A/Gb Non-synchronized PS Handover to cell B by sending them in PACKET NEIGHBOUR CELL DATA message.
The SS sends PS HANDOVER COMMAND to assign a PDCH on cell B and containing a handover reference. The MS moves to cell B and sends PS HANDOVER ACCESS in 11-bit access burst format in Cell B. The SS sends PACKET PHYSICAL INFORMATION to the MS.
Following handover to Cell B MS continues with the data uplink data transfer in Cell B. The SS allows the MS to transfer about 30 RLC blocks.
The SS provides the MS a minimum set of System Info Types in order to perform a A/Gb to A/Gb Non-synchronized PS Handover to cell A by sending them in PACKET NEIGHBOUR CELL DATA message.
The SS sends PS HANDOVER COMMAND to assign a PDCH on cell A and containing a handover reference. The MS moves to cell A and sends PS HANDOVER ACCESS in 8-bit access burst format in Cell A. The SS sends PACKET PHYSICAL INFORMATION to the MS.
Following handover to cell A MS continues with the data uplink data transfer in Cell A.
Maximum Duration of Test
10 minutes.
Expected Sequence
Step
Direction
Message
Comments
1
{Uplink dynamic allocation two phase access}
The following messages received on cell A.
n = 2000 octets in RLC acknowledged mode (Test PDP context2), without starting time,
USF_GRANULARITY = 1 block,
RLC_DATA_BLOCKS_GRANTED = open-end
TLLI_BLOCK_CHANNEL_CODING: cs1,
CHANNEL_CODING_COMMAND: cs1
2
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
USF assigned to the MS.
3
MS -> SS
UPLINK RLC DATA BLOCK or PACKET MEASUREMENT REPORT
Received on the assigned PDTCH. Check that the coding BSN and the TFI are correct.
4
Repeat step 2 and 3 in total of 30 times.
5
SS -> MS
PACKET NEIGHBOUR CELL DATA
All instances are Sent on the PACCH of the assigned PDCH.
Containing: System Info Type 1, System Info Type 3 and System Info Type 13 of cell B.
USF assigned to the MS.
6
MS -> SS
UPLINK RLC DATA BLOCK or PACKET MEASUREMENT REPORT
Received on the assigned PDTCH. Check that the coding BSN and the TFI are correct.
7
SS -> MS
PS HANDOVER COMMAND
Sent on the PACCH of the assigned PDCH. USF not assigned to the MS.
The following messages are received on cell B.
8
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
Send 120 ms (T_GSM_delay) after step 7. USF assigned to the MS.
9
MS -> SS
PS HANDOVER ACCESS
As 4 access bursts. Check that handover reference and access burst format (11-bit) is correct.
10
SS->MS
PACKET PHYSICAL INFORMATION
11
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
USF assigned to the MS.
12
MS -> SS
PACKET UPLINK DUMMY CONTROL BLOCK or
UPLINK RLC DATA BLOCK or PACKET MEASUREMENT REPORT
Received on the assigned PDTCH.
Repeat steps 11 and 12 for maximum of 100 ms or until UPLINK RLC DATA BLOCK is received.
(Data block may contain empty LLC PDU for Cell Update. In that case the SS shall accept Packet Resource Request from MS and respond with Packet Uplink Assignment.)
13
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
USF assigned to the MS.
14
MS -> SS
UPLINK RLC DATA BLOCK or PACKET MEASUREMENT REPORT
Received on the assigned PDTCH. Check that the coding BSN and the TFI are correct.
15
Repeat step 13 and 14 in total of 30 times.
16
SS -> MS
PACKET NEIGHBOUR CELL DATA
All instances are Sent on the PACCH of the assigned PDCH.
Containing: System Info Type 1, System Info Type 3 and System Info Type 13 of cell A.
USF assigned to the MS.
17
MS -> SS
UPLINK RLC DATA BLOCK or PACKET MEASUREMENT REPORT
Received on the assigned PDTCH. Check that the coding BSN and the TFI are correct.
18
SS -> MS
PS HANDOVER COMMAND
Sent on the PACCH of the assigned PDCH. USF not assigned to the MS.
The following messages are received on cell A.
19
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
Send 120 ms (T_GSM_delay) after step 18. USF assigned to the MS.
20
MS -> SS
PS HANDOVER ACCESS
As 4 access bursts. Check that handover reference and access burst format (8-bit) is correct.
21
SS->MS
PACKET PHYSICAL INFORMATION
22
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
USF assigned to the MS.
23
MS -> SS
PACKET UPLINK DUMMY CONTROL BLOCK or
UPLINK RLC DATA BLOCK or PACKET MEASUREMENT REPORT
Received on the assigned PDTCH.
Repeat steps 11 and 12 for maximum of 100 ms or until UPLINK RLC DATA BLOCK is received.
(Data block may contain empty LLC PDU for Cell Update. In that case the SS shall accept Packet Resource Request from MS and respond with Packet Uplink Assignment.)
24
{Completion of uplink RLC data block transfer}
Specific Message Contents
PS HANDOVER COMMAND message in step 7:
As default message contents except
default
PS Handover Radio Resources IE
present
SI
00 Non-synchronized
RLC_RESET
1
PACKET PHYSICAL INFORMATION message in step 10:
PAGE_MODE
default
Global TFI
TFI of mobile station uplink TBF
TIMING ADVANCE VALUE
30 bit periods
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.6.3.2 Intra SGSN PS Handover / Non synchronized cell case / Different RA / successful
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.6.3.2.1 Conformance requirements
|
The following synchronisation mechanisms are used for PS handover:
• Non-synchronised.
• Synchronised.
• Pre-Synchronised.
The non-synchronised cases are shown in figures 22 and 24 and are characterised by the requirement for the MS to obtain a valid uplink timing advance before it can transmit normal bursts. The MS shall notify its presence in the target cell through the transmission of access bursts to the BSS, and the BSS shall respond with a valid timing advance which in turn enables the MS to send normal bursts in uplink.
After having switched to the assigned channels, the mobile station shall send four times the PS HANDOVER ACCESS message. The mobile station shall start timer T3216 at the start point of the timeslot in which the PS HANDOVER ACCESS message is sent the first time on the PACCH.
The mobile station then activates the channels in receiving mode.
Upon reception of the PS HANDOVER ACCESS message containing the expected Handover Reference value, once the network has the RF characteristics that are necessary, it sends a PACKET PHYSICAL INFORMATION message to the mobile station on the PACCH.
When the mobile station receives a PACKET PHYSICAL INFORMATION message, it stops timer T3216, stops sending access bursts and activates the channels in sending and receiving mode.
The MS sends uplink LLC PDUs, e.g. a Routing Area Update Request message or uplink user data packets to the SGSN immediately after receiving the Packet Physical Information message or, in a synchronised or pre-synchronised handover, immediately if the PS Handover Access message is not required to be sent (see Section 6.2).
References
3GPP TS 43.129, subclasses 6.2.2, 5.1.2.3
3GPP TS 44.060, subclasses 8.10.4.4.4.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.6.3.2.2 Test purpose
|
To verify that while in uplink Acknowledged mode MS performs successfully Non-Synchronised PS Handover from A/Gb to A/Gb.
To verify that MS triggers Routing Area update procedure after receiving the Packet Physical Information and during this procedure data transfer continues.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.6.3.2.3 Method of test
|
Initial Conditions
System Simulator:
Two cells A (RAI 1) and Cell B (RAI 2), NC2 mode, GPRS supported, PCCCH not present.
Mobile Station:
The MS is GPRS attached on cell A, a P-TMSI allocated and test PDP context2 activated.
Specific PICS Statements
-
PIXIT Statements
-
Test Procedure
The MS is triggered to initiate packet uplink transfer 2000 octets in the RLC acknowledged mode on cell A. After a successful uplink PDCH assignment the SS sends PACKET DOWNLINK DUMMY indicating the assigned USF to the MS. The MS sends a RLC radio block. The SS allows the MS to transfer about 30 RLC blocks.
The SS provides the MS a minimum set of System Info Types in order to perform a A/Gb to A/Gb Non-synchronized PS Handover by sending them in PACKET NEIGHBOUR CELL DATA message.
The SS sends PS HANDOVER COMMAND to assign a PDCH on cell B and containing a handover reference. The MS moves to cell B sends PS HANDOVER ACCESS. The SS sends PACKET PHYSICAL INFORMATION to the MS.
Following handover to Cell B MS may send PACKET RESOURCE REQUEST to trigger the ROUTING AREA UPDATE procedure. The Routing area procedure is completed and the MS continues with the data uplink data transfer in Cell B.
Maximum Duration of Test
5 minutes.
Expected Sequence
Step
Direction
Message
Comments
1
{Uplink dynamic allocation two phase access}
The following messages received on cell A.
n = 2000 octets in RLC acknowledged mode (Test PDP context2), without starting time,
USF_GRANULARITY = 1 block,
RLC_DATA_BLOCKS_GRANTED = open-end
TLLI_BLOCK_CHANNEL_CODING: cs1,
CHANNEL_CODING_COMMAND: cs1
2
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
USF assigned to the MS.
3
MS -> SS
UPLINK RLC DATA BLOCK or PACKET MEASUREMENT REPORT
Received on the assigned PDTCH. Check that the coding BSN and the TFI are correct.
4
Repeat step 2 and 3 in total of 30 times.
5
SS -> MS
PACKET NEIGHBOUR CELL DATA
All instances are Sent on the PACCH of the assigned PDCH.
Containing : System Info Type 1, System Info Type 3 and System Info Type 13 of cell B.
USF assigned to the MS.
6
MS -> SS
UPLINK RLC DATA BLOCK or PACKET MEASUREMENT REPORT
Received on the assigned PDTCH. Check that the coding BSN and the TFI are correct.
7
SS -> MS
PS HANDOVER COMMAND
Sent on the PACCH of the assigned PDCH. USF not assigned to the MS.
The following messages are received on cell B.
8
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
Send 120 ms (T_GSM_delay) after step 7. USF assigned to the MS.
9
MS -> SS
PS HANDOVER ACCESS
As 4 access bursts. Check that handover reference is correct.
10
SS->MS
PACKET PHYSICAL INFORMATION
11
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
USF assigned to the MS.
12
MS -> SS
PACKET UPLINK DUMMY CONTROL BLOCK or
UPLINK RLC DATA BLOCK or
PACKET RESOURCE REQUEST or
ROUTING AREA UPDATE REQUEST or PACKET MEASUREMENT REPORT
Repeat steps 11 and 12 for maximum of 100 ms
or PACKET RESOURCE REQUEST is received on PACCH then the optional steps 13 to 16 are performed or ROUTING AREA UPDATE REQUEST
Note: MS may complete the ongoing LLC PDU started before PS handover in step 11 and step 12 or
Ensure that the MS completes the transfer of the ROUTING AREA UPDATE REQUEST message
13
Optional step
SS->MS
PACKET UPLINK ASSIGNMENT
Sent on the PACCH of the assigned PDCH. USF not assigned to the MS.
14
Optional step
SS->MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
USF assigned to the MS.
15
Optional step
MS->SS
UPLINK RLC DATA BLOCK
(ROUTING AREA UPDATE REQUEST) or PACKET MEASUREMENT REPORT
Ensure that the MS completes the transfer of the ROUTING AREA UPDATE REQUEST message
16
Optional step
Repeat step 14 and 15 until the last block of the ROUTING AREA UPDATE REQUEST is received.
17
SS -> MS
PACKET UPLINK ACK/NACK
Sent on the PACCH of the PDCH assigned, acknowledge all received data, without setting FINAL_ACK_INDICATION.
18
SS -> MS
PACKET DOWNLINK ASSIGNMENT
Sent on PACCH of the PDCH assigned.
19
SS -> MS
DOWNLINK RLC DATA BLOCK
(ROUTING AREA UPDATE ACCEPT)
Transporting the ROUTING AREA UPDATE ACCEPT
Last RLC data block with valid RRBP field (polling).
20A
MS -> SS
PACKET DOWNLINK ACK/NACK
Including Channel Request Description.
21A
SS -> MS
PACKET UPLINK ASSIGNMENT
Sent on PACCH of the PDCH assigned. Continue with step 24.
20B
MS -> SS
PACKET DOWNLINK ACK/NACK
Not including Channel Request Description.
21B
SS->MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
USF assigned to the MS.
22B
MS -> SS
UPLINK RLC DATA BLOCK or PACKET RESOURCE REQUEST
23 B Optional step
SS -> MS
PACKET UPLINK ASSIGNMENT
Step is performed if MS send PACKET RESOURCE REQUEST in step 22B.
Sent on PACCH of the PDCH assigned.
24
{Completion of uplink RLC data block transfer}
Specific Message Contents
PS HANDOVER COMMAND message in step 7:
As default message contents except
default
PS Handover Radio Resources IE
present
SI
00 Non-synchronized
RLC_RESET
1
PACKET PHYSICAL INFORMATION message in step 10:
PAGE_MODE
default
Global TFI
TFI of mobile station uplink TBF
TIMING ADVANCE VALUE
30 bit periods
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.6.3.3 Intra SGSN PS Handover / Non synchronized cell case / Abnormal Case / T3216 expiry
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.6.3.3.1 Conformance requirements
|
In case of initial access failure in the target cell, including the case where the MS fails to acquire time alignment information (for the unsynchronised network case), the MS is allowed to revert to the old cell. As is defined currently in 3GPP TS 44.060 [7], the MS shall return to the old cell and send a Packet Cell Change Failure message with the appropriate cause.
If the MS was in packet transfer mode (or MAC-shared state) before the attempted handover it will, when going back to the old cell, send a Packet Cell Change Failure message and resume TBFs which were ongoing in the old cell.
A mobile station operating in A/Gb mode shall consider the PS handover to A/Gb mode to have failed for the following reasons:
- Timer T3216 expires while in the new cell.
A mobile station operating in A/Gb mode when a PS handover to A/Gb mode fails shall proceed as follows:
- If timer T3216 expired it shall return to the cell on which the PS HANDOVER COMMAND message was received.
- Send a Packet Cell Change Failure message with the cause code set to "No response on target cell" if timer T3218 or T3216 expired, otherwise "PS Handover failure-others". The message shall be sent on PACCH .
- The transmission of a Packet Cell Change Failure message terminates the PS handover procedure in the mobile station and after the transmission of this message the mobile station is therefore allowed to request the establishment of additional uplink TBFs.
- After terminating the PS handover procedure the mobile station shall resume all uplink and downlink TBFs that were ongoing in the old cell prior to receiving the PS HANDOVER COMMAND message. Timers T3180 (uplink TBFs) and T3190 (downlink TBFs) corresponding to these TBFs shall be re-started.
- For each TBF that is resumed the corresponding RLC state machine shall reflect its state when the last RLC data block was transmitted for that TBF in the old cell (uplink TBFs) and the last RLC data block was received for that TBF in the old cell (downlink TBFs).
References
3GPP TS 43.129, subclasses 5.7.2.1
3GPP TS 44.060, subclasses 8.10.5.1
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.6.3.3.2 Test purposes
|
To verify that the MS upon PS handover failure due to T3216 expiry, returns to the old cell and sends a PACKET CELL CHANGE FAILURE message with cause “No response on target cell” and resumes the TBFs that were ongoing in the old cell.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.6.3.3.3 Method of test
|
Initial Conditions
System Simulator:
2 cells A and B, GPRS supported, NC 2 mode, PCCCH not present.
The RF level of cell A is –50 dBm and cell B – 60 dBm.
Mobile Station:
The MS is GPRS attached on cell A, a P-TMSI allocated and test PDP context2 activated.
Specific PICS Statements
-
PIXIT Statements
-
Test Procedure
The MS is triggered to initiate packet uplink transfer 2000 octets in the RLC acknowledged mode on cell A. After a successful uplink PDCH assignment the SS sends PACKET DOWNLINK DUMMY indicating the USF assigned to the MS. The SS allows the MS to transfer about 30 RLC blocks.
The SS provides the MS a minimum set of System Info Types in order to perform a A/Gb to A/Gb non-synchronized PS Handover by sending them in PACKET NEIGHBOUR CELL DATA message.
The SS sends PS HANDOVER COMMAND to assign a PDCH on cell B.
MS will send 4 PS Handover Access messages. SS does not send Packet Physical information and
waits for timer T3216(1 s) expiry.
SS then assigns USF to the MS on the old cell A. MS send PACKET CELL CHANGE FAILURE with cause value “No response on target cell” and resumes the uplink data transfer.
Maximum Duration of Test
5 minutes.
Expected Sequence
Step
Direction
Message
Comments
1
{Uplink dynamic allocation two phase access}
The following messages received on cell A.
n = 2000 octets in RLC acknowledged mode (Test PDP context2), without starting time,
USF_GRANULARITY = 1 block,
RLC_DATA_BLOCKS_GRANTED = open-end
TLLI_BLOCK_CHANNEL_CODING: cs1,
CHANNEL_CODING_COMMAND: cs1
2
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
USF assigned to the MS.
3
MS -> SS
UPLINK RLC DATA BLOCK or PACKET MEASUREMENT REPORT
Received on the assigned PDTCH. Check that the coding and the TFI are correct.
4
Repeat step 2 and 3 in total of 30 times.
5
SS -> MS
PACKET NEIGHBOUR CELL DATA
USF assigned to the MS.
6
MS -> SS
UPLINK RLC DATA BLOCK or PACKET MEASUREMENT REPORT
Received on the assigned PDTCH.
7
Repeat step 5 and 6 until all instances are sent on the PACCH of the assigned PDCH.
Containing : System Info Type 1, System Info Type 3 and
System Info Type 13 of cell B.
8
SS -> MS
PS HANDOVER COMMAND
Sent on the PACCH of the assigned PDCH. USF not assigned to the MS.
9
The following messages are sent on cell B.
10
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
Sent on PACCH assigned in step 8. USF addressing the MS.
11
MS -> SS
PS HANDOVER ACCESS
As 4 access bursts. Check that handover reference is correct.
12
SS
SS does not send PACKET PHYSICAL INFORMATION.
SS waits until Timer T3216 expires (1 sec) + 0.1*T3216
13
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
USF allocated in PACKET UPLINK ASSIGNMENT from step 1 assigned to the MS.
14
MS -> SS
PACKET CELL CHANGE FAILURE
Cause:"No response on target cell”
15
SS<->MS
{ Uplink data transfer }
Macro - Completion of the 2kB of Data.
Specific Message Contents
PS HANDOVER COMMAND message in step 8:
As default message contents except
default
PS Handover Radio Resources IE
present
SI
00 Non-synchronized
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.7 PEO - Power Efficiency Operation
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.7.1 Macros and default message contents
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.7.1.1 Macros
|
In order to simplify the process of writing and coding test cases, macros are referenced in the expected signalling tables. These macros provide all additional signalling needed to complete the particular test but are not relevant to its purpose.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.7.1.2 GPRS Attach Procedure for PEO
|
The following table describes a signalling sequence performing the GPRS attach procedure for an MS that supports PEO and is performing NAS signalling in an attempt to enable a power saving feature (i.e. eDRX or PSM - see 3GPP TS 23.060 [19]) while in a cell that supports PEO.
The macros {Completion of GPRS attach for PEO} in the test cases refer to the table below starting at the step required for the particular sequence.
{GPRS attach procedure for PEO}
Step
Direction
Message
Comments
{ GPRS attach procedure for PEO }
Macro parameters:
Extended DRX value: If present, replace the value requested in Step3
T3324 Value: If present, replace the value requested in Step3
0
MS is triggered to initiate the GPRS attach procedure.
1
MS -> SS
CHANNEL REQUEST
Establishment Cause is 'one phase packet access'.
2
SS -> MS
IMMEDIATE ASSIGNMENT
For uplink TBF, one phase access, dynamic allocation.
3
MS -> SS
RLC data blocks
Transporting:
ATTACH REQUEST
It is Verified that eDRX and/or T3324 IE are included
At least one of the two IE must be present
4
SS -> MS
PACKET UPLINK ACK/NACK
Indicating correct reception of uplink blocks, including RRBP field set.
5
MS -> SS
PACKET CONTROL ACKNOWLEDGMENT
Sent on PACCH
6
SS -> MS
IMMEDIATE ASSIGNMENT
For downlink TBF, sent 1 s. after step 5 on AGCH.
7
SS -> MS
RLC data blocks
Transporting:
ATTACH ACCEPT.
Including the Extended DRX value and/or T3324 Value specified in the macro, if any, otherwise the values in step 3 must be used
(PSM - T3324 - included only if eDRX is not reused)
Last block containing a valid RRBP field and FBI set.
8A
MS -> SS
PACKET DOWNLINK ACK/NACK
Including Channel Request Description.
9A
SS -> MS
PACKET UPLINK ASSIGNMENT
Sent on PACH.
10A
MS -> SS
RLC data blocks
Transporting:
ATTACH COMPLETE
11A
SS -> MS
PACKET UPLINK ACK/NACK
Including valid RRBP field
12A
MS -> SS
PACKET CONTROL ACKNOWLEDGMENT
8B
MS -> SS
PACKET DOWNLINK ACK/NACK
Not including Channel Request Description.
9B
MS->SS
EGPRS PACKET CHANNEL REQUEST
Establishment Cause is 'PEO one phase packet access'.
10B
SS -> MS
IMMEDIATE ASSIGNMENT
For uplink TBF, single phase access, dynamic allocation.
11B
MS -> SS
RLC data blocks
Transporting:
ATTACH COMPLETE
12B
SS -> MS
PACKET UPLINK ACK/NACK
Indicating correct reception of uplink blocks, including RRBP field set.
13B
MS -> SS
PACKET CONTROL ACKNOWLEDGMENT
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.7.2 Paging
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.7.2.1 PEO Paging / Ready Timer Expiration
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.7.2.1.1 Conformance requirements
|
A PEO capable mobile station camping in a cell that supports PEO performs NAS signalling to negotiate the use of a power saving feature (i.e. eDRX or PSM – see 3GPP TS 23.060 [74]). A mobile station that has enabled PEO (see 3GPP TS 43.064 [109]) shall only transmit an EGPRS PACKET CHANNEL REQUEST message indicating ‘PEO One Phase Access Request’ (see Table 3.5.2.1.2.2 and 3GPP TS 44.060 [76]) when performing system access. A BSS that receives this message shall send a response that only assigns the MS packet resources in the frequency band corresponding to CCCH on which the EGPRS PACKET CHANNEL REQUEST message was received.
[...]
A MS that has enabled PEO where eDRX is used supports eDRX paging cycles that can range from multiple seconds to about 52 minutes (see 3GPP TS 45.002 [32]). In this case the mobile station supports reachability while in packet idle mode as follows:
• The mobile station uses the lowest eDRX cycle while the Ready timer (see 3GPP TS 24.008 [79]) is running.
• Upon expiration of the Ready timer or waking up and determining it has not been paged using its nominal paging group the mobile station re-enters the eDRX based power saving state for the time remaining until its next paging occasion.
Reference
3GPP TS 44.018 subclauses 3.9.1 & 3.9.2
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.7.2.1.2 Test purpose
|
1. To verify that a MS that has enabled PEO (eDRX) on a PEO capable cell will use an EGPRS PACKET CHANNEL REQUEST message indicating ‘PEO One Phase Access Request’.
2. To verify that the eDRX cycle negotiated is only applied once the Ready Timer expires. Before that the lowest eDRX cycle is used.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.7.2.1.3 Method of test
|
Initial conditions
System Simulator:
1 cell, PEO capable for eDRX.
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 a PEO (eDRX) capable Cell The SS verifies that the MS uses an EGPRS PACKET CHANNEL REQUEST message indicating ‘PEO One Phase Access Request’ for every packet access when the PEO is enabled (ATTACH_ACCEPT received). Only the eDRX value is sent by the SS.
Once the device is GPRS attached, in packet idle mode with the Ready Timer running, the SS pages the MS according to the second lowest eDRX cycle and reject the MS access. The MS is then pages according to the second lowest eDRX cycle, once the ready timer is expired. There should be no answer from the MS.
The MS is then paged according to its negotiated eDRX cycle and should answer the Paging Request.
Maximum duration of the test
6 minutes
Expected sequence
Step
Direction
Message
Comments
0
MS
The MS is turned on and triggered to initiate the GPRS attach procedure.
1
MS -> SS
CHANNEL REQUEST
Establishment Cause is 'one phase packet access'.
2
MS<->SS
Completion of macro {GPRS attach procedure for PEO}
SS allows MS to complete the attach procedure.
eDRX Value: 0110 (1.63 Min)
T3324 Value (PSM): not present
3
SS
Wait 20 seconds (starting after the last RLC data block)
4
SS -> MS
PAGING REQUEST TYPE 1
Packet page indication indicates packet paging procedure. Sent on PCH according to the lowest eDRX cycle.
5
MS -> SS
EGPRS PACKET CHANNEL REQUEST
Establishment Cause is 'PEO one phase packet access'.
6
SS -> MS
IMMEDIATE ASSIGNMENT REJECT
Request Reference = pertaining to the message received in step 5.
Sent on AGCH.
7
Wait for 30 seconds for Ready Timer to expire.
8
SS -> MS
PAGING REQUEST TYPE 1
Packet page indication indicates packet paging procedure. Sent on PCH according to the second eDRX cycle, but not on MS PCH.
9
There Should be no response from MS as the eDRX Cycle is now set to eDRX Value: 0110. This is verified for the duration of T3315
10
SS -> MS
PAGING REQUEST TYPE 1
Packet page indication indicates packet paging procedure. Sent on PCH according to the negotiated eDRX cycle.
11
MS -> SS
EGPRS PACKET CHANNEL REQUEST
Establishment Cause is 'PEO one phase packet access'.
12
SS -> MS
IMMEDIATE ASSIGNMENT REJECT
Request Reference = pertaining to the message received in step 11.
Sent on AGCH.
13
SS -> MS
PAGING REQUEST TYPE 1
Packet page indication indicates packet paging procedure. Sent on next PCH according to the negotiated eDRX cycle.
14
MS -> SS
EGPRS PACKET CHANNEL REQUEST
Establishment Cause is 'PEO one phase packet access'.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.7.2.2 PEO Paging / PSM and eDRX
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.7.2.2.1 Conformance requirements
|
A PEO capable mobile station camping in a cell that supports PEO performs NAS signalling to negotiate the use of a power saving feature. After successfully negotiating a power saving feature or while performing NAS signalling in an attempt to enable a power saving feature (i.e. eDRX or PSM – see 3GPP TS 23.060 [74]) while in a cell that supports PEO, the mobile station shall only transmit an EGPRS PACKET CHANNEL REQUEST message indicating ‘PEO One Phase Access Request’ (see Table 3.5.2.1.2.2 and 3GPP TS 44.060 [76]) when performing system access. A BSS that receives this message shall only assign the MS packet resources in the frequency band corresponding to CCCH on which the EGPRS PACKET CHANNEL REQUEST message was received.
If PSM has been negotiated (see 3GPP TS 24.008 [51]) it starts the active timer upon expiration of the ready timer. While the active timer is running it remains reachable using the eDRX value last negotiated with the network. If no eDRX value has been negotiated then it uses the DRX cycle applicable to the serving cell while the Active timer is running. When the active timer expires the mobile station enters the PSM based power saving state and will not be reachable until the next time it performs an uplink data transfer.
Reference
3GPP TS 44.018 subclause 3.9.1
3GPP TS 44.060 subclause 5.5.1.5
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.7.2.2.2 Test purpose
|
1. To verify that a MS that has enabled PEO on a PEO capable cell will use an EGPRS PACKET CHANNEL REQUEST message indicating ‘PEO One Phase Access Request’
2. To verify that a MS that has enabled PEO with both PSM and eDRX is reachable with the eDRX cycle negotiated during the PSM active timer.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.7.2.2.3 Method of test
|
Initial conditions
System Simulator:
- 1 cell, PEO capable for PSM and eDRX
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 a PEO (eDRX & PSM) capable Cell The SS verifies that the MS uses an EGPRS PACKET CHANNEL REQUEST message indicating ‘PEO One Phase Access Request’ for every packet access when the PEO is enabled (ATTACH_ACCEPT received). Both PSM and eDRX value are sent by the SS.
Once the device is GPRS attached, in packet idle mode with the Active Timer running, after the Ready Timer expires, the SS pages the MS according to the lowest eDRX cycle. There should be no answer from the MS.
The MS is then pages according to the negotiated eDRX cycle, on every occasion until the Active Timer expiry should answer the Paging Request.
The MS is then paged according to its negotiated eDRX cycle but after the Active Timer expires. There should be no answer from the MS.
Maximum duration of the test
13 minutes
Expected sequence
Step
Direction
Message
Comments
0
MS
The MS is turned on and triggered to initiate the GPRS attach procedure.
1
MS -> SS
CHANNEL REQUEST
Establishment Cause is 'one phase packet access'.
2
MS<->SS
Completion of macro {GPRS attach procedure for PEO}
SS allows MS to complete the attach procedure.
eDRX Value: 0111 (3.25 min)
T3324 Value (PSM): 8 minutes
3
SS
Wait 20 seconds (starting after the last RLC data block)
4
Wait for 1 minute for Ready Timer to expire.
5
SS -> MS
PAGING REQUEST TYPE 1
Packet page indication indicates packet paging procedure. Sent on PCH according to the lowest eDRX cycle, but not on the MS PCH.
6
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
7
SS -> MS
PAGING REQUEST TYPE 1
Packet page indication indicates packet paging procedure. Sent on MS PCH according to the negotiated eDRX cycle.
8
MS -> SS
EGPRS PACKET CHANNEL REQUEST
Establishment Cause is 'PEO one phase packet access'.
9
SS -> MS
IMMEDIATE ASSIGNMENT REJECT
Request Reference = pertaining to the message received in step 8
Sent on AGCH.
10
Steps 7 to 9 are repeated on every occasion during T3324 duration,
11
SS -> MS
PAGING REQUEST TYPE 1
Sent on PCH according to the negotiated eDRX cycle, on the next paging occasion after T3324 expiry.
12
There should be no response from MS, as it shall have entered PSM mode. This is verified for the duration of T3315.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.7.2.3 PEO Paging / PEO_BCCH_CHANGE_MARK
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.7.2.3.1 Conformance requirements
|
An MS that has enabled PEO and is using eDRX shall ignore the “Paging reorganization” condition indicated by the page mode information element if received in any message (i.e. this condition targets mobile stations not using eDRX).
[…]
A MS that has enabled PEO not accessing the network for the purpose of NAS signalling low priority shall also listen to the downlink CCCH until successfully decoding one of the RR messages listed in sub-clause 3.3.1.1.1a and read the PEO_BCCH_CHANGE_MARK field therein. If a change of PEO_BCCH_CHANGE_MARK is detected then it shall first read SI13 prior to performing the packet access.
Reference
3GPP TS 44.018 subclauses 3.5.1.1 & 3.5.2.1.2
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.7.2.3.2 Test purpose
|
1. To verify that a MS that has enabled PEO will not take into account the “paging Reorganisation” condition indicated by the page mode information.
2. To verify that a MS that has enabled PEO will read the SI13 prior to performing a packet access if a change of the PEO_BCCH_CHANGE_MARK is detected.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.7.2.3.3 Method of test
|
Initial conditions
System Simulator:
1 cell, PEO capable for eDRX
Mobile Station:
The MS is GPRS attached with a P-TMSI allocated and eDRX cycle negotiated. Specific PICS Statements
-
PIXIT Statements
-
Test procedure
The MS is paged according to its negotiated eDRX cycle. The access is rejected by SS and the Page mode is set to “Paging reorganisation”.
The MS is then paged on its CCCH (not on its paging subchannel), there should be no answer form the MS.
The PEO_BCCH_CHANGE_MARK is then updated on the next message sent on the MS PCH to identified the change of GPRS Mobile allocation
A downlink data transfer using the new GPRS Mobile allocation is then triggered.
Maximum duration of the test
4 minutes
Expected sequence
Step
Direction
Message
Comments
1
SS -> MS
PAGING REQUEST TYPE 1
Sent before the MS paging occasion.
2
MS -> SS
EGPRS PACKET CHANNEL REQUEST
Verify ‘PEO One Phase Access’ is requested
3
SS -> MS
IMMEDIATE ASSIGNMENT REJECT
Request Reference = pertaining to the message received in step 2.
Sent on AGCH.
Page Mode set to “paging Reorganisation”
4
SS -> MS
PAGING REQUEST TYPE 1
Sent before the MS's paging sub-channel re-occurs, but later than the next paging block of that CCCH.
5
SS -> MS
There should be no answer from the MS
6
SS
SS verifies for 10s. that the MS does not respond.
7
SS -> MS
IMMEDIATE ASSIGNMENT
Sent on MS PCH, not addressing the MS.
PEO_BCCH_CHANGE_MARK changed.
8
SS
Update the SI13_CHANGE_MARK to be used in SI 13
9
SS
Wait two SI13 repeat periods to allow for the new SI acquisition
10
SS -> MS
IMMEDIATE ASSIGNMENT
for downlink TBF on a PCH block corresponding to the MS, including a packet downlink assignment, using the newly defined GPRS Mobile Allocation
11
SS -> MS
RLC data blocks
SS sends data
12
MS -> SS
PACKET DOWNLINK ACK/NACK
indicating correct reception of data blocks
13
MS<->SS
Completion of macro {Downlink data transfer}
SS completes downlink transfer
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.7.3 Extended Uplink TBF
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.7.3.1 PEO / Extended UL TBF
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.7.3.1.1 Conformance requirements
|
An exception case is where a mobile station has enabled PEO or EC-EGPRS in which case it shall operate as follows:
[…]
- If a mobile station that has enabled PEO enters extended uplink TBF mode (see sub-clauses 9.3.1a and 9.3.1b) then it monitors the downlink PACCH starting with the 8th 52-multiframe following the 52-multiframe in which it received the PACKET UPLINK ACK/NACK message confirming reception of all uplink RLC data blocks. More specifically, it monitors radio block [(IMSI mod 1e7) mod 12] in that 52-multiframe and in each subsequent 52-multiframe for a matching PACCH message for as long as it remains in extended UL TBF mode or it receives a matching PACCH message.
Reference
3GPP TS 44.060 subclause 5.5.1.5
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.7.3.1.2 Test purpose
|
To verify that an MS that has enabled PEO (eDRX) and enters Extended uplink TBF mode will only monitors its assigned PACCH when all uplink RLC data blocks are received by the network
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.7.3.1.3 Method of test
|
Initial conditions
System Simulator:
1 cell, PEO capable for eDRX, NW_EXT_UTBF = 1.
Mobile Station:
MS is in Packet Idle mode, GPRS attached with support of GERAN Feature Package 1 indicated in MS Radio Access Capabilities, and PDP context 2 established. eDRX negotiated to 52 MF (~12.2 sec)
Specific PICS Statements
-
PIXIT Statements
-
Test Procedure
The MS is triggered to transfer user data. A TBF using dynamic allocation in acknowledged mode is assigned. The SS assigns an USF to MS. SS receives data blocks till CV=0 and acknowledges all the blocks with an UPLINK ACK/NACK setting FAI=0. Then SS checks that if a USF is matched to the MS it sends a UPLINK DUMMY CONTROL BLOCK. SS sends two PACKET TIMESLOT RECONFIGURE, reassigning the timeslot given for Uplink and initiating a downlink TBF on both new defined slot.
One PACKET TIMESLOT RECONFIGURE is sent out of the blocks defined by the Conformance Requirements. SS checks that the MS is not sending an UPLINK DUMMY CONTROL BLOCK on the new channels whenever the USF is matched. This is to verify that the PACKET TIMESLOT RECONFIGURE was not taken into account.
The other PACKET TIMESLOT RECONFIGURE is sent on the blocks defined by the Conformance Requirements. SS checks that the MS is sending an UPLINK DUMMY CONTROL BLOCK on the new channels whenever the USF is matched. This is to verify that the PACKET TIMESLOT RECONFIGURE was taken into account.
SS releases the downlink TBF.
Expected Sequence
Step
Direction
Message
Comments
1
{Uplink dynamic allocation two phase access}
n = 500 octets,
USF_GRANULARITY = 1 block,
CHANNEL_CODING_COMMAND: CS-2,
RLC acknowledged mode (PDP context2)
2
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
USF assigned to the MS.
3
MS -> SS
UPLINK RLC DATA BLOCK
4
Repeat step 2 and 3 until CV=0
5
SS -> MS
PACKET UPLINK ACK/NACK
Final Ack Indication = 0. Sent on PACCH of the assigned PDCH. Acknowledge all data blocks received.
6
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
USF assigned to the MS
A6 (optional step)
MS -> SS
UPLINK RLC DATA BLOCK
MS may retransmit the block with BSN=0 once if it has already been scheduled while Packet Uplink Ack/Nack is being processed. In this case go to step B6.
B6 (optional step)
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
USF assigned to the MS
7
MS -> SS
PACKET UPLINK DUMMY CONTROL BLOCK
8
Repeat step 6 and 7 one time.
9
SS -> MS
PACKET TIMESLOT RECONFIGURE
See Specific message content. Assigning different timeslot, starting a downlink TBF. Sent in the first available PACCH on the 5th 52-multiframe following the 52-multiframe in which it received the PACKET UPLINK ACK/NACK in step 5.
10
SS -> MS
PACKET TIMESLOT RECONFIGURE
See Specific message content. Assigning different timeslot, starting a downlink TBF. Sent in the first available PACCH on the 8th 52-multiframe following the 52-multiframe in which it received the PACKET UPLINK ACK/NACK - radio block [(IMSI mod 1e7) mod 12]
11
SS -> MS
DOWNLINK RLC DATA BLOCK
Containing RRBP= N+21 or +22 and USF assigned to the MS. FBI ='1'. Sent on the downlink PDTCH assigned on 3 blocks from the last radio block containing the TIMESLOT RECONFIGURE in step 9.
12
SS -> MS
DOWNLINK RLC DATA BLOCK
Containing RRBP= N+21 or +22 and USF assigned to the MS. FBI ='1'. Sent on the downlink PDTCH assigned on 3 blocks from the last radio block containing the TIMESLOT RECONFIGURE in step 10.
11
MS -> SS
PACKET UPLINK DUMMY CONTROL BLOCK
Received on the uplink PDTCH assigned in step 10.
12
SS
Checks that no PACKET UPLINK DUMMY CONTROL BLOCK is received on the PDTCH assigned in Step 9
12
MS -> SS
PACKET DOWNLINK ACK/NACK
Received on the block of frame number = N+21 or +22, N is the frame number of the first burst of the data block in step 10.
Specific Message Contents
PACKET TIMESLOT RECONFIGURE message in step 9:
PAGE_MODE
Normal
0, Global TFI as reference
- Global TFI
0, uplink TFI
same value as assigned in the uplink in step 1
CHANNEL_CODING_COMMAND
Arbitrarily chosen from valid values
Global packet Timing Advance
- {0|1<TIMING_ADVANCE_VALUE>}
1 (timing advance value)
- TIMING_ADVANCE_VALUE
30 bit periods
- {0|1<UPLINK_TIMING_ADVANCE_INDEX> <UPLINK_TIMING_ADVANCE_TIMESLOT_NUMBER>}
0 (no uplink timing advance index)
The MS stops the operation of the continuous timing advance procedure.
- {0|1<DOWNLINK_TIMING_ADVANCE_INDEX> <DOWNLINK_TIMING_ADVANCE_TIMESLOT_NUMBER>}
0 (no downlink timing advance index)
The MS stops the operation of the continuous timing advance procedure.
DOWNLINK_RLC_MODE
Acknowledged mode
CONTROL_ACK
0
{0|1<DOWNLINK_TFI_ASSIGNMENT>}
1
- GLOBAL_TFI_ASSIGNMENT
Arbitrarily chosen but different from the value for uplink TBF
{0|1<UPLINK_TFI_ASSIGNMENT>}
0
DOWNLINK_TIMESLOT_ALLOCATION
Timeslot 5 assigned
{0|1<Frequency parameters>}
0
Dynamic allocation
0
- Extended Dynamic Allocation
0 ( Dynamic allocation)
{0|1<P0>}
0
- USF GRANULARITY
0 (1 RLC block)
- {0|1<RLC_DATA_BLOCKS_GRANTED>}
0 (open-ended TBF)
- {0|1<TBF_STARTING_TIME>}
0 (no starting time)
-
1 (Timeslot Allocation with Power Control Parameters)
- ALPHA
0.5
- {0|1<USF_TNx><GAMMA_TNx>}
000001 (timeslot 5 assigned)
- USF_TN5
Arbitrarily chosen but different from current value
- GAMMA_TN5
For GSM 700, T-GSM 810, GSM 850 and GSM 900, +8 dBm
For DCS 1 800 and PCS 1 900, +6 dBm
00
PACKET TIMESLOT RECONFIGURE message in step 10:
PAGE_MODE
Normal
0, Global TFI as reference
- Global TFI
0, uplink TFI
same value as assigned in the uplink in step 1
CHANNEL_CODING_COMMAND
Arbitrarily chosen from valid values
Global packet Timing Advance
- {0|1<TIMING_ADVANCE_VALUE>}
1 (timing advance value)
- TIMING_ADVANCE_VALUE
30 bit periods
- {0|1<UPLINK_TIMING_ADVANCE_INDEX> <UPLINK_TIMING_ADVANCE_TIMESLOT_NUMBER>}
0 (no uplink timing advance index)
The MS stops the operation of the continuous timing advance procedure.
- {0|1<DOWNLINK_TIMING_ADVANCE_INDEX> <DOWNLINK_TIMING_ADVANCE_TIMESLOT_NUMBER>}
0 (no downlink timing advance index)
The MS stops the operation of the continuous timing advance procedure.
DOWNLINK_RLC_MODE
Acknowledged mode
CONTROL_ACK
0
{0|1<DOWNLINK_TFI_ASSIGNMENT>}
1
- GLOBAL_TFI_ASSIGNMENT
Arbitrarily chosen but different from the value for uplink TBF
{0|1<UPLINK_TFI_ASSIGNMENT>}
0
DOWNLINK_TIMESLOT_ALLOCATION
Timeslot 6 assigned
{0|1<Frequency parameters>}
0
Dynamic allocation
0
- Extended Dynamic Allocation
0 ( Dynamic allocation)
{0|1<P0>}
0
- USF GRANULARITY
0 (1 RLC block)
- {0|1<RLC_DATA_BLOCKS_GRANTED>}
0 (open-ended TBF)
- {0|1<TBF_STARTING_TIME>}
0 (no starting time)
-
1 (Timeslot Allocation with Power Control Parameters)
- ALPHA
0.5
- {0|1<USF_TNx><GAMMA_TNx>}
000001 (timeslot 5 assigned)
- USF_TN5
Arbitrarily chosen but different from current value
- GAMMA_TN5
For GSM 700, T-GSM 810, GSM 850 and GSM 900, +8 dBm
For DCS 1 800 and PCS 1 900, +6 dBm
00
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.8 EC-GSM-IoT procedures
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.8.1 EC-GSM-IoT / Packet Access
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.8.1.1 EC-GSM-IoT / Packet Access / EC-BCCH CHANGE MARK
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.8.1.1.1 Conformance requirements
|
A MS that has enabled EC operation shall have read a complete EC-SI message set no longer than 24 hours prior to attempting packet access. In addition, if the mobile station detects a change to the EC- BCCH CHANGE MARK field when reading the EC-SCH it shall re-acquire one ore more EC-SI (as determined by the EC SI_CHANGE_MARK field in the first received EC-SI message) before attempting packet access (see sub-clause 3.5.2a). [...]
Reference
3GPP TS 44.018 subclause 3.10.4
A mobile station that has enabled EC operation uses its currently estimated uplink coverage class to determine the number of blind physical layer transmissions to use when sending an EC PACKET CHANNEL REQUEST message (see sub-clause 3.5.2a) and includes an estimate of its downlink coverage class in the message (see sub-clause 9.1.65).
Reference
3GPP TS 44.018 subclause 3.10.5
On receipt of an EC-IMMEDIATE ASSIGNMENT TYPE 2 message corresponding to its last EC PACKET CHANNEL REQUEST message, the mobile station stops T3146 (if running), stops sending EC PACKET CHANNEL REQUEST messages, and switches to the assigned PDCH(s).
Reference
3GPP TS 44.018 subclause 3.5.2.1.3a.1
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.8.1.1.2 Test purpose
|
To verify that a change of EC-BCCH CHANGE MARK detected when initiating uplink packet access triggers an EC-System Information acquisition prior to performing the uplink packet access.
To verify that the EC-GSM-IoT capable mobile station uses the correct procedures for packet access.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.8.1.1.3 Method of test
|
Initial conditions
System Simulator:
1 cell EC-GSM-IoT supported
1TS EC-RACH Mapping used:
- Access Timeslots field in EC_SI2 set to ‘0’.
CC used: CC1 in downlink and uplink.
- CC1 used in the downlink: Signal level for FCCH and EC-SCH set-up such that the estimated received signal level parameter (C_VALUE) is greater than BT_Threshold_DL. BT_Threshold_DL is broadcast in EC_SI2 message. See 3GPP TS 45.008 §6.10.2.
- CC1 used in the uplink: Signal level for FCCH and EC-SCH set-up such that the estimated uplink received signal strength (BS_RX_PWR) is greater than BT_Threshold_UL. This requires proper setting of BT_Threshold_UL, MSPWR, MS_TXPWR_MAX_CCH, BSPWR. MS_TXPWR_MAX_CCH and BSPWR are broadcast in EC_SI2 message. See 3GPP TS 45.008 §6.10.3.
Mobile Station:
The MS is GPRS attached in packet idle mode. PDP context 2 has been established.
Specific PICS Statements
-
PIXIT Statements
-
Foreseen final state of the MS
-
Test procedure
The EC-BCCH CHANGE MARKfield is set updated to 001’ in EC-SCH. The parameter EC_MAX_RETRANS is changed to 2 retransmissions in EC-SI 2.
The MS is triggered to send uplink data (2 MCS-1 coded RLC data blocks using normal priority). The MS checks the EC-BCCH CHANGE MARK on EC-SCH, notices the change and re-acquires the EC System Information Type 2 message.
The MS then sends an EC PACKET CHANNEL REQUEST.
The SS ignores first EC PACKET CHANNEL REQUEST message and acts on the second EC PACKET CHANNEL REQUEST message (verifies that 2 retransmissions of the EC PACKET CHANNEL REQUEST are done)
Maximum duration of the test
-
Expected sequence
Step
Direction
Message
Comments
1
SS
EC-SCH update with EC-BCCH CHANGE MARK set to ‘1’,
EC_MAX_RETRANS set to 2 retransmission in EC-SI2, Access_Timeslots field in EC_SI2 set to ‘0’ and EC SI_CHANGE_MARK set to indicate that only EC-SI 2 has changed
2
MS
Trigger to UL data send data
3
MS ->SS
EC PACKET CHANNEL REQUEST
1TS-Mapping, sent on EC-RACH
EGPRS-Priority = ‘0’
EC-NumberOfBlocks = ‘01’
DL Coverage Class: a CC1 codepoint
4
SS
SS verifies that MS repeats the EC PACKET CHANNEL REQUEST transmission twice
5
SS
SS verifies than no more access is done for 5 s
Specific message contents:
-
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.8.1.2 EC-GSM-IoT / Packet Access / EC-GSM-IoT / RACH Access allowed / Packet Access on RACH
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.8.1.2.1 Conformance requirements
|
An EC-GSM-IoT capable mobile station in a cell that supports EC-GSM-IoT attempts packet access by:
- transmitting an EC PACKET CHANNEL REQUEST message using the RACH (see sub-clause 3.5.2.1.2); or
Reference
3GPP TS 44.018 subclause 3.10.1
RACH Access Control is a 1 bit field and is coded as follows:
0: A mobile station using CC1 in both the uplink and downlink shall not use timeslot 0
1: A mobile station using CC1 in both the uplink and downlink shall use timeslot 0
Reference
3GPP TS 44.018 subclause 9.1.30c.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.8.1.2.2 Test purpose
|
To verify that the EC-GSM-IoT capable mobile station attempts packet access using an EC PACKET CHANNEL REQUEST message on RACH when RACH access is allowed and it is using CC1 in both downlink and uplink.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.8.1.2.3 Method of test
|
Initial conditions
System Simulator:
1 cell EC-GSM-IoT supported
RACH Access to be used:
- RACH Access allowed (CC1)
- CC1 used in the downlink
- CC1 used in the uplink
Mobile Station:
The MS is GPRS attached and in EC mode.
Specific PICS Statements
-
PIXIT Statements
-
Foreseen final state of the MS
-
Test procedure
The MS determines CC1 is used in both uplink and downlink. The MS is triggered to send uplink data (Normal Report consisting of 2 MCS-1 coded RLC data blocks, neither NAS Signalling or Exception Report). The MS issues a EC PACKET CHANNEL REQUEST message on RACH. The SS verifies the EC PACKET CHANNEL REQUEST is received on RACH.
Maximum duration of the test
1 minute.
Expected sequence
Step
Direction
Message
Comments
1
SS
Access_Timeslots field sent in EC-SI2 = 0, RACH Access Control field in SCH set to ‘1’
2
MS
Trigger to UL data send data
3
MS -> SS
EC PACKET CHANNEL REQUEST
The MS sends EC PACKET CHANNEL REQUEST on RACH with:
TS3 or TS4 (depending on the MS 8PSK capability)
EC-NumberOfBlocks = ‘0 1 1’
EC Priority = ‘0’
Random Bits = 3 random bits
Signal Strength = any value according to the MS measurement
Specific message contents
-
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.8.1.3 EC-GSM-IoT / Packet Access / EC-GSM-IoT / 1TS EC-RACH Mapping / CC1
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.8.1.3.1 Conformance requirements
|
The RR entity of a mobile station initiates the packet access procedure by scheduling the sending of EC PACKET CHANNEL REQUEST messages (see Table 3.5.2.1.2a and sub-clause 9.1.65) as follows:
- Using the 1TS EC-RACH Mapping method if using CC1 on the uplink or if the Access Timeslots field sent in EC-SI2 = 0.
Reference
3GPP TS 44.018 subclause 3.5.2.5.2a.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.8.1.3.2 Test purpose
|
To verify that the EC-GSM-IoT capable mobile station attempts packet access using an EC PACKET CHANNEL REQUEST message with 1TS EC-RACH Mapping when RACH access is not allowed though using CC1 in both downlink and uplink.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.8.1.3.3 Method of test
|
Initial conditions
System Simulator:
1 cell EC-GSM-IoT supported.
RACH Access not allowed (CC1)
4 DL coverage classes are indicated as supported
1TS EC-RACH Mapping to be used:
- Access Timeslots field in EC_SI2 set to ‘1’.
- CC1 used in the downlink
- CC1 used in the uplink
Mobile Station:
The MS is GPRS attached and in EC mode.
Specific PICS Statements
-
PIXIT Statements
-
Foreseen final state of the MS
-
Test procedure
The MS determines CC1 in both uplink and downlink. The MS is triggered to send uplink data (Normal Report consisting of 2 MCS-1 coded RLC data blocks, neither NAS Signalling or Exception Report). The MS issues a EC PACKET CHANNEL REQUEST message using the 1TS EC-RACH mapping. The SS verifies the EC PACKET CHANNEL REQUEST received is using the 1TS EC-RACH mapping.
Maximum duration of the test
1 minute.
Expected sequence
Step
Direction
Message
Comments
1
MS
Trigger to send UL data
2
MS -> SS
EC PACKET CHANNEL REQUEST
The MS sends EC PACKET CHANNEL REQUEST on EC-RACH using 1TS Mapping with:
TS3 or TS4 (depending on the MS 8PSK capability)
EC-NumberOfBlocks = ‘0 1 1’
EC Priority = ‘0’
Random Bits = 3 random bits
Selected DL Coverage Class = any value in the range from ‘0 1 1’ to ‘1 1 1’ depending on the MS measurement
3
SS
SS verifies that the EC PACKET CHANNEL REQUEST message is received on EC-RACH, using 1TS Mapping, with the correct content (see above)
Specific message contents
-
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.8.1.4 EC-GSM-IoT / Packet Access / EC-GSM-IoT / 1TS EC-RACH Mapping / Access Timeslots field = 0
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.8.1.4.1 Conformance requirements
|
The RR entity of a mobile station initiates the packet access procedure by scheduling the sending of EC-EGPRS PACKET CHANNEL REQUEST messages (see Table 3.5.2.1.2a.1 and sub-clause 9.1.65) as follows:
- Using the 1TS EC-RACH Mapping method if using CC1 on the uplink or if the Access Timeslots field sent in EC-SI2 = 0.
The mapping of the EC-RACH (EC-CCCH/U) is defined in table 6a of clause 7 and illustrated in figure 16 and figure 17, where the possible blocks are indicated for each uplink Coverage Class. Furthermore, two different EC-RACH mappings exist. The mapping to be used is signalled on cell level in EC SI, see 3GPP TS 44.018. The EC-RACH is either mapped onto a single TS, or over 2 consecutive TS for CC2, CC3 and CC4. CC1 EC-RACH is always mapped onto 1 TS.
Reference
3GPP TS 44.018 subclause 3.5.2.5.2a.
3GPP TS 45.002 subclause 6.3.4.3.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.8.1.4.2 Test purpose
|
To verify that the GSM-IoT capable mobile station attempts packet access using an EC PACKET CHANNEL REQUEST message with 1TS EC-RACH Mapping when Access Timeslots field sent in EC-SI2 = 0.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.8.1.4.3 Method of test
|
Initial conditions
System Simulator:
1 cell EC-GSM-IoT supported.
RACH Access not allowed (CC1)
4 DL coverage classes are indicated as supported
1TS EC-RACH Mapping to be used:
- Access Timeslots field in EC_SI2 set to ‘0’
- CC1 not used in the uplink
Cell power: -90dBm (to ensure uplink CC2)
Mobile Station:
The MS is GPRS attached and in EC mode.
Specific PICS Statements
-
PIXIT Statements
-
Foreseen final state of the MS
-
Test procedure
The MS determines CC2, in UL. The MS is triggered to send uplink data (accessing the network for the purpose of NAS signalling low priority and is not sending an exception report). The MS issues an EC PACKET CHANNEL REQUEST message using the 1TS EC-RACH mapping. The SS verifies the EC PACKET CHANNEL REQUEST received is using the 1TS EC-RACH mapping.
Maximum duration of the test
1 minute.
Expected sequence
Step
Direction
Message
Comments
1
MS
Trigger to send UL data
2
MS -> SS
EC PACKET CHANNEL REQUEST
The MS sends EC PACKET CHANNEL REQUEST on EC-RACH using 1TS Mapping with:
TS5, TS6 or TS7 (depending whether the coverage class in uplink is CC2, CC3 or CC4, respectively)
EC-NumberOfBlocks = ‘0 1 1’
EC-EGPRS Priority = ‘0’
Random Bits = 3 random bits
Selected DL Coverage Class = any value depending on the MS measurement
3
SS
SS verifies that the EC PACKET CHANNEL REQUEST message is received on EC-RACH, using 1TS Mapping, with the correct content (see above)
Verified 4 identical bursts (CC2 Uplink), 0n TS1 on 4 consecutive frames
Specific message contents
-
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.8.1.5 EC-GSM-IoT / Packet Access / EC-GSM-IoT / 2TS EC-RACH Mapping
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.8.1.5.1 Conformance requirements
|
The RR entity of a mobile station initiates the packet access procedure by scheduling the sending of EC PACKET CHANNEL REQUEST messages (see Table 3.5.2.1.2a.1 and sub-clause 9.1.65) as follows:
- Using the 2TS EC-RACH Mapping method if using CC2, CC3 or CC4 on the uplink and the Access Timeslots field sent in EC-SI2 = 1.
- When the 2TS EC-RACH Mapping method is used the EC PACKET CHANNEL REQUEST messages sent across 2 timeslots on the EC-RACH shall be identical and shall use the same training sequence code (i.e. one of TS5, TS6 or TS7 is used according to the uplink CC).
Reference
3GPP TS 44.018 subclause 3.5.2.5.2a.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.8.1.5.2 Test purpose
|
To verify that the EC-GSM-IoT capable mobile station attempts packet access using an EC PACKET CHANNEL REQUEST message with 2TS EC-RACH Mapping when using CC2 in uplink and when Access Timeslots field sent in EC-SI2 = 1.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.8.1.5.3 Method of test
|
Initial conditions
System Simulator:
1 cell EC-GSM-IoT supported.
RACH Access not allowed (CC1)
4 DL coverage classes are indicated as supported
2TS EC RACH Mapping to be used:
- Access Timeslots field in EC_SI2 set to ‘1’ (i.e. 2TS EC-RACH mapping).
- UL coverage as CC2.
Cell power: -90dBm (to ensure uplink CC2)
Mobile Station:
The MS is GPRS attached and in EC mode.
Specific PICS Statements
-
PIXIT Statements
-
Foreseen final state of the MS
-
Test procedure
The MS determines CC2 in UL. The MS is triggered to send uplink data (accessing the network for the purpose of NAS signalling low priority and is not sending an exception report). The MS issues an EC PACKET CHANNEL REQUEST message using the 2TS EC-RACH mapping. The SS verifies the EC PACKET CHANNEL REQUEST messages received across 2 timeslots are identical and use the same TSC (according to the uplink CC).
Maximum duration of the test
1 minute.
Expected sequence
Step
Direction
Message
Comments
1
SS
Trigger to send UL data
2
MS -> SS
EC-EGPRS PACKET CHANNEL REQUEST
The MS sends EC PACKET CHANNEL REQUEST on EC-RACH using 2TS Mapping with:
TS5 (corresponding to CC2 in uplink)
EC-NumberOfBlocks = ‘0 1 0’
EC-EGPRS Priority = ‘0’
Random Bits = 3 random bits
Selected DL Coverage Class = any value depending on the MS measurement
3
SS
SS verifies that the EC PACKET CHANNEL REQUEST message is received on EC-RACH, using 2TS Mapping, same training sequence
Verify 2TS meaning
Verified 4 identical bursts (CC2 Uplink), TS 0 and TS1 on 2 consecutive frames
Specific message contents
-
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.8.1.6 EC-GSM-IoT / Packet Access / Implicit Reject
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.8.1.6.1 Conformance requirements
|
…
A mobile station that is accessing the network for the purpose of NAS signalling low priority (see 3GPP TS 24.008 [79]) and is not sending an exception report (see sub-clause 9.1.65), shall read the Implicit Reject Status (IRS) field, EC-BCCH CHANGE MARK field and RACH Access Control field sent in the EC-SCH INFORMATION message (see Figure 9.1.30c.1 and 3GPP TS 45.002) prior to accessing the network. If a change of EC-BCCH CHANGE MARK is detected it shall read one or more EC-SYSTEM INFORMATION messages as needed (see sub-clause3.10.4). The MS then proceeds as follows:
- If the IRS field indicates the access attempt is rejected the mobile station shall abort the packet access procedure and initiate the EC Implicit Reject procedure (see sub-clause 3.5.2a.2).
- If the IRS field indicates the access attempt is not rejected, the RACH Access Control field indicates that RACH usage on timeslot number 0 is not allowed it shall proceed with the packet access procedure as described in sub-clause 3.5.2.1.2a.
- If the IRS field indicates the access attempt is not rejected, the RACH Access Control field indicates that RACH usage on timeslot number 0 is allowed and the mobile station has selected CC1 in both uplink and downlink, see 3GPP TS 45.008 [34], it shall proceed with the packet access procedure as described in sub-clause 3.5.2.1.2.
- If the IRS field indicates the access attempt is not rejected and the mobile station has selected CC2, CC3 or CC4 in the uplink and/or downlink (see 3GPP TS 45.008 [34]) then it shall proceed with the packet access procedure as described in sub-clause 3.5.2.1.2a.
…
The EC-GSM-IoT preliminary access barring check shall indicate network access is barred for a MS that has enabled EC operation if any of the following conditions are satisfied:
• A MS that is a member of an Access Class in the range 0-9 is attempting to send a normal report (see sub-clause 9.1.65) and determines that the corresponding AC0 to AC9 bit in the EC_Access_Control_Class field sent in the EC SYSTEM INFORMATION TYPE 2 message (for the common PLMN) or in the EC SYSTEM INFORMATION TYPE 4 message (for the corresponding Additional PLMN when network sharing is in use in the cell) is not authorized.
• A MS that is a member of an Access Class in the range 0-9 is attempting to send an exception report (see sub-clause 9.1.65) and determines that the Exception_Report_Status field sent in the EC SYSTEM INFORMATION TYPE 2 message (for the common PLMN) or in the EC SYSTEM INFORMATION TYPE 4 message (for the corresponding Additional PLMN when network sharing is in use in the cell) is not authorized.
A MS that is a member of one or more of a special Access Class in the range 11-15 is attempting to send a normal report or an exception report and determines the AC11 to AC15 bit in the EC_Access_Control_Class field corresponding to its special Access Class sent in the EC SYSTEM INFORMATION TYPE 2 message (for the common PLMN) or in the EC SYSTEM INFORMATION TYPE 4 message (for the corresponding Additional PLMN when network sharing is in use in the cell) is not authorized. References
3GPP TS 44.018, subclauses 3.10.1, 3.5.2a and 3.5.2a.1
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.8.1.6.2 Test purpose
|
To verify that the EC-EGPRS capable mobile station, accessing the network for the purpose of NAS signalling low priority and is not sending an exception report, checks the Implicit Reject Status (IRS) field before attempting packet access.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.8.1.6.3 Method of test
|
Initial Conditions
System Simulator:
1 cell, EC-GSM-IoT supported, MS is in GPRS attached state. Routing area T3312=6min.
Mobile Station:
The MS is configured for “NAS signalling low access priority” and is configured for one of Access Class 0 to 9.
Specific PICS Statements
-
PIXIT Statements
-
Test Procedure
The MS attached to the EC-GSM-IoT cell is expected to trigger a Periodic Routing Area Procedure.
At least 1min before the Periodic Timer expiry, the Implicit Reject Status on EC-SCH is set to 11 (all MS barred) in order to give the MS enough time to identify the barred status.
The SS then checks that the MS shall not access the network for the Periodic Routing Area procedure until the EC-SCH Implicit Reject Status is unbarred. The MS access is then expected for the duration of T3236.
Maximum Duration of Test
8 minutes.
Expected Sequence
Step
Direction
Message
Comments
1
SS
EC-SCH updated with Implicit Reject Status set to: 11 (all MS are barred)
2
SS
Wait 1min to ensure barred.
3
MS
SS checks for 5 min (Periodic Routing Area Timer) that no access is done by the MS
4
SS
EC-SCH updated with Implicit Reject Status set to: 00 (No barring)
5
SS
EC-Packet channel request
SS verifies that the MS Periodic Routing area update is initiated by the MS.
Shall be sent within 200 seconds (maximum of T3236).
Specific Message Contents
-
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.8.1.7 EC-GSM-IoT / Packet Access / Legacy Implicit Reject
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.8.1.7.1 Conformance requirements
|
- transmitting an EC-EGPRS PACKET CHANNEL REQUEST message using the RACH (see sub-clause 3.5.2.1.2); or
- transmitting an EC-EGPRS PACKET CHANNEL REQUEST message using the 1TS EC-RACH Mapping method (see sub-clause 3.5.2.1.2a); or
- transmitting an EC-EGPRS PACKET CHANNEL REQUEST message using the 2TS EC-RACH Mapping method (see sub-clause 3.5.2.1.2a)
…
A mobile station accessing the network for the purpose of NAS signalling low priority (see 3GPP TS 24.008), when attempting to establish a PS connection, shall, while ignoring MS identities included within PAGING REQUEST messages, start listening to the downlink CCCH until successfully decoding one of the RR messages listed in sub-clause 3.3.1.1.1a. A MS that has enabled PEO shall read the PEO_BCCH_CHANGE_MARK field within the successfully decoded RR message. If a change of PEO BCCH CHANGE MARK is detected it shall first read SI13 before proceeding with the packet access procedure. If the RR message indicates an implicit reject for the PS domain (see sub-clause 3.3.1.1.1a) the mobile station shall abort the packet access procedure and initiate the implicit reject procedure (see sub-clause 3.3.1.1.3.2a). An exception case is where the mobile station has enabled EC-EGPRS operation and is sending an EC-EGPRS PACKET CHANNEL REQUEST message using the RACH (see sub-clause 3.5.2a) in which case it proceeds with the packet access without first checking the status of the PEO_BCCH_CHANGE_MARK field or implicit reject information sent in an RR message.
…
A mobile station that has enabled EC-EGPRS operation and is accessing the network for the purpose of NAS signalling low priority (see 3GPP TS 24.008) and is not sending an exception report, shall examine the Implicit Reject Status (IRS) field, EC-EGPRS BCCH CHANGE MARK field and RACH Access Control field sent as part of the 25 bit EC-SCH payload space (see Figure 9.1.30c.1 and 3GPP TS 45.002). If a change of EC-EGPRS BCCH CHANGE MARK is detected it shall first read one or more EC-SI messages (see sub-clause3.10.4) and then proceed as follows:
- If the IRS field indicates the access attempt is rejected the mobile station shall abort the packet access procedure and initiate the EC-EGPRS Implicit Reject procedure (see sub-clause 3.5.2.1.6).
- If the access attempt is not rejected and the RACH Access Control field indicates that RACH usage is not allowed it shall proceed with the packet access procedure as described in sub-clause 3.5.2.1.2a.
- If the access attempt is not rejected, the RACH Access Control field indicates that RACH usage is allowed and the mobile station is in normal coverage (i.e. it uses CC1 for both the uplink and downlink) it shall proceed with the packet access procedure as described in sub-clause 3.5.2.1.2.
…
The EC-EGPRS preliminary access barring check shall indicate network access is barred for a MS that has enabled EC-EGPRS operation if any of the following conditions are satisfied:
- A MS that is a member of an Access Class in the range 0-9 is attempting to send a normal report and determines that the Normal Access Barring field sent in EC-SI2 is not authorized.
- A MS that is a member of an Access Class in the range 0-9 is attempting to send an exception report and determines that the Exception Report Status field sent in EC-SI2 is not authorized.
- A MS that is a member of an Access Class in the range 0-9 and one or more of a special Access Class in the range 11-15 is attempting to send a normal report and determines the Special Access Barring field corresponding to its special Access Class sent in EC-SI2 is not authorized.
- A MS that is a member of an Access Class in the range 0-9 and one or more of a special Access Class in the range 11-15 is attempting to send an exception report and determines that the Special Access Barring field corresponding to its special Access Class is not authorized and the Exception Report Status field is not authorized.
References
3GPP TS 44.018, subclauses 3.10.1, 3.5.2, 3.5.2a and 3.5.2a.1
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.8.1.7.2 Test purpose
|
To verify that the EC-EGPRS capable mobile station, accessing the network for the purpose of NAS signalling low priority ignores the checks the Implicit Reject Status (IRS) field when sending an EC-EGPRS PACKET CHANNEL REQUEST message using the RACH.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.8.1.7.3 Method of test
|
Initial Conditions
System Simulator:
1 cell, EC-GSM-IoT supported, Implicit reject flag enabled and RACH Access Control = 1 in EC-SCH
Mobile Station:
The MS is configured for “NAS signalling low access priority”
The MS is GPRS attached and have acquired the EC-SI message
Specific PICS Statements
-
PIXIT Statements
-
Test Procedure
The MS, configured for low access priority, is triggered to initiate a “NAS signalling low priority” packet uplink data transfer on an EC-GSM-IoT capable Cell.
Before accessing the network, the MS reads the EC-SCH SYNCHRONIZATION CHANNEL INFORMATION, indicating that the Implicit Reject Status is set to 11 (all mobile stations barred) and that the RACH Access Control flag is set to 1.
The SS verifies that the MS ignore the Implicit Reject flag and send the EC PACKET CHANNEL REQUEST on RACH.
The MS transfers the NAS message to the SSMaximum Duration of Test
8 minutes.
Expected Sequence
Step
Direction
Message
Comments
2
MS
The MS is triggered to initiate “NAS signalling low priority” packet uplink data transfer
3
MS -> SS
EC PACKET CHANNEL REQUEST
Verify received on RACH
4
SS -> MS
EC IMMEDIATE ASSIGNMENT TYPE 1
CC1 to be used
5
MS -> SS
UPLINK RLC DATA BLOCKS
Transporting: NAS message send with low priority indication
6
SS -> MS
EC PACKET UPLINK ACK/NACK
acknowledge the received RLC data block, Final Ack Indicator = ‘1’, a valid RRBP
7
MS -> SS
EC PACKET CONTROL ACKNOWLEDGEMENT
acknowledge the RLC data
Specific Message Contents
-
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.8.2 EC-GSM-IoT / Paging
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.8.2.1 EC-GSM-IoT / Paging / normal paging
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.