hash
stringlengths 32
32
| doc_id
stringlengths 5
12
| section
stringlengths 4
595
| content
stringlengths 0
6.67M
|
|---|---|---|---|
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 83.1.5.7.1 Conformance requirements | When the GANC decides to deactivate GA-PSR TC channel, it shall send GA-PSR-DEACTIVATE-UTC-REQ message to the MS to request the deactivation.
If the MS receives an unexpected GA-PSR-DEACTIVATE-UTC-ACK message response while the GA-PSR is in GA-PSR-ACTIVE state, the MS GA-PSR shall stop TU4001 timer, and release the GA-PSR TC. In parallel, the MS GA-PSR shall transition to GA-PSR-STANDBY state.
References
3GPP TS 44.318, subclauses 8.5.1 & 8.4.4.5 |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 83.1.7.1.2 Test purpose | To verify that upon receiving a GA-PSR-DEACTIVATE-UTC-REQ message from the GANC, the MS releases the GA-PSR TC, sends the GA-PSR-DEACTIVATE-UTC-ACK message to the GANC indicating successful deactivation and MS GA-PSR enters the GA-PSR-STANDBY state. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 83.1.7.1.3 Method of test | Initial Conditions
System Simulator:
- 1 GAN cell, default parameters
Mobile Station:
- MS GA-PSR is in the GA-PSR-STANDBY state. PDP context 1 is activated.
Foreseen Final State of the MS
MS in GA-PSR-STANDBY state in service of GAN cell
Test Procedure
The SS initiates active state. The MS responds with GA-PSR-ACTIVATE-UTC-ACK. The SS initiates deactivation of the TC and sends GA-PSR-DEACTIVATE-UTC-ACK. The MS responds with GA-PSR-DEACTIVATE-UTC-ACK and enters the GA-PSR-STANDBY state. To confirm that the MS is in the GA-PSR-STANDBY state, the MS is triggered to send user data. Therefore, GA-PSR-ACTIVATE-UTC-REQ is expected to be sent from the MS. The SS sends GA-PSR-ACTIVATE-UTC-ACK message and waits for GA-PSR-UNITDATA.
Maximum Duration of Test
1 min.
Expected Sequence
Step
Direction
Message
Comments
MS
SS
1
GA-PSR-ACTIVATE-UTC-REQ
SS initiated GA-PSR-ACTIVE state
2
GA-PSR-ACTIVATE-UTC-ACK
3
GA-PSR-UNITDATA
4
GA-PSR-DEACTIVATE-UTC-REQ
SS initiates the deactivation
5
GA-PSR-DEACTIVATE-UTC-ACK
MS response on deactivation
6
Trigger MS to send user data
7
GA-PSR-ACTIVATE-UTC-REQ
SS verifies that MS was in GA-PSR-STANDBY state in step 5.
8
GA-PSR-ACTIVATE-UTC-ACK
8a
GA-PSR-UNITDATA
9
GA-PSR-DEACTIVATE-UTC-REQ
SS initiates the deactivation
10
GA-PSR-DEACTIVATE-UTC-ACK
MS response on deactivation
Specific Message Contents
- |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 83.1.8 Void | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 83.2 GA-PSR GPRS User Data Transport | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 83.2.1 GA-PSR GPRS User Data Transport , Normal Cases | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 83.2.1.1 MS Initiates Uplink GPRS User Data Transfer | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 83.2.1.1.1 Conformance requirements | The GPRS user data packets are tunnelled using UDP transport as specified for GA-PSR Transport Channel. Each packet is assigned a sequence number in the range of 0 to 65535 sequentially. The sequence number is set to 0 after reaching the maximum – 65535.
Assuming that the GA-PSR TC has been already activated as specified in sub-clauses 8.2 or 8.3, the MS GA-PSR is able to immediately forward any uplink GPRS user data packets to the GANC. Upon the request from the LLC to transfer an uplink LLC PDU with GPRS user data identified with LLC SAPI 3, 5, 9 or 11, the MS GA-PSR shall restart TU4001 timer and encapsulate the complete LLC PDU within a GA-PSR UNITDATA message.
Subsequently, the MS shall send the GA-PSR UNITDATA message to the GANC using the existing GA-PSR TC; i.e. using the corresponding GANC IP address and UDP port number.
The MS shall increment the uplink packet sequence number for each GA-PSR-UNITDATA message sent to the GANC.
References
3GPP TS 44.318, subclauses 8.7 & 8.7.1. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 83.2.1.1.2 Test purpose | To verify that MS:
1) Uses corresponding GANC IP address and UDP port number,
2) Transmits at least 65537 packets, and that each packet is assigned a sequence number in the range of 0 to 65535 sequentially.
3) Assigns sequence number to 0 after reaching the maximum – 65535 |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 83.2.1.1.3 Method of test | Initial Conditions
System Simulator:
- 1 GAN cell, default parameters
Mobile Station:
- MS GA-PSR is in the GA-PSR-STANDBY state. PDP context 1 is activated
Foreseen Final State of the MS
MS in GA-PSR-STANDBY state in service of GAN cell.
Test Procedure
The MS activates the GA-PSR TC with the corresponding GANC IP address and UDP port number and immediately forwards uplink GPRS user data, which consist of 65537 of packets, being requested from the MS LLC, to the GANC. The MS tunnels the GPRS data packets using UDP transport, assigning number to the packets in range from 0 to 65535 sequentially. The MS increments the uplink packet sequence number for each GA-PSR-UNITDATA message, being sent to the GANC, and assigns the number 0 after reaching the 65535.
SS verifies that MS:
1) Uses corresponding GANC IP address and UDP port number,
2) Transmits at least 65537 packets, and that each packet is assigned a sequence number in the range of 0 to 65535 sequentially.
3) Assigns sequence number to 0 after reaching the maximum – 65535
Maximum Duration of Test
30 min.
Expected Sequence
Step
Direction
Message
Comments
MS
SS
1
GA-PSR-ACTIVATE-UTC-REQ
SS initiated GA-PSR-ACTIVE state
2
GA-PSR-ACTIVATE-UTC-ACK
SS sends IP address and UDP port number
3
GA-PSR-UNITDATA
MS sends at least 65537 packets, SS verified that the sequence number is set to 0 after reaching the maximum – 65535
4
GA-PSR-DEACTIVATE-UTC-REQ
Sent after TU4001 expires
5
GS-PSR DEACTIVATE-UTC-ACK
Specific Message Contents
- |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 83.2.2 GA-PSR GPRS User Data Transport , Abnormal Cases | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 83.2.2.1 Void | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 83.2.2.2 Void | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 83.2.2.3 MS Receives a Downlink Message to Initiate Uplink GPRS User Data Transfer while the GA-PSR TC activation Procedure is in progress | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 83.2.2.3.1 Conformance requirements | Upon receiving a downlink message while the GA-PSR TC activation procedure is in progress (TU4002 timer is still running), the MS GA-PSR shall process the request as if the transport channel was active. The MS shall not initiate uplink GPRS user data transfer until the GA-PSR TC activation procedure is successfully completed (as specified in the subclause 8.2). The MS shall use the IP address and UDP port number received in the GA-PSR ACTIVATE UTC ACK message for sending uplink GPRS user data packets to the GANC on that transport channel.
References
3GPP TS 44.318, subclause 8.7.5.4 |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 83.2.2.3.2 Test purpose | To verify that MS GA-PSR shall only use IP address and UDP port number received in the GA-PSR ACTIVATE UTC ACK message to send uplink GPRS user data packets to the SS |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 83.2.2.3.3 Method of test | Initial Conditions
System Simulator:
- 1 GAN cell, default parameters
Mobile Station:
- MS GA-PSR is in the GA-PSR-STANDBY state. PDP context 1 is activated
Foreseen Final State of the MS
MS in GA-PSR-ACTIVE state in service of GAN cell.
Test Procedure
The MS receives a downlink message GA-PSR UNITDATA while Transport Channel activation is in progress. The MS activates the GA-PSR TC with the GANC IP address and UDP port number given in the GA-PSR ACTIVATE UTC ACK message and sends uplink GPRS user data.
SS verifies that MS:
1) GA-PSR shall only use IP address and UDP port number received in the GA-PSR ACTIVATE UTC ACK message to send uplink GPRS user data packets to the SS
Maximum Duration of Test
5 min.
Expected Sequence
Step
Direction
Message
Comments
MS
SS
1
MS
MS in GA-PSR-STANDBY state
2
GA-PSR-ACTIVATE-UTC-REQ
MS initiates GA-PSR TC activation
3
GA-PSR-UNITDATA
SS initiates a GPRS user data transfer by sending GA_PSR UNIT DATA message with IP address and UDP port address
4
SS
Waiting for 2 sec to check MS does not send any data
5
GA-PSR-ACTIVATE-UTC-ACK
SS sends a different IP address and UDP port number than source IP address and UDP port number in step 3
6
MS
MS in GA-PSR-ACTIVE state
7
GA-PSR-UNITDATA
MS completes data transfer using new IP address and UDP port given in GA-PSR-ACTIVATE-UTC-ACK
Specific Message Contents
- |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 83.3 Packet paging for packet service | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 83.3.1 PS Paging Request Processed by the MS, Normal Case | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 83.3.1.1 PS Paging Request Processed by the MS | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 83.3.1.1.1 Conformance requirements | Upon receiving a GA-PSR-PS-PAGE message from the GANC, the MS GA-PSR shall forward the indication to the GMM layer using the GMMRR SAP as per standard GPRS. Subsequently, the MS shall send an uplink LLC PDU as a page response per standard GPRS. The MS may either send GA-PSR-DATA or GA-PSR-UNITDATA message as described in sub-clauses 8.7 and 8.8.
References
3GPP TS 44.318, subclauses 8.9.2 |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 83.3.1.1.2 Test purpose | To verify that the MS responds with GA-PSR-DATA message upon receiving a GA-PSR-PS-PAGE message from the GANC. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 83.3.1.1.3 Method of test | Initial Conditions
System Simulator:
- 1 GAN cell, default parameters
Mobile Station:
- MS GA-PSR is in the GA-PSR-STANDBY state. PDP context 1 is activated.
Forseen Final State of the MS
MS in Idle state
Test Procedure
The SS sends the GA-PSR-PS-PAGE, paging the MS. The MS responds with GA-PSR-DATA. The SS checks the received data is the paging response.
Maximum Duration of Test
1 min.
Expected Sequence
Step
Direction
Message
Comments
1
x
MS is in GA-PSR-STANDBY state
2
GA-PSR-PS-PAGE
MS is made to initiate GA-PSR TC
3
GA-PSR-DATA
SS verifies that the MS sends the GA-PSR-DATA
Check that the received data is the paging reponse (Empty LLC PDU)
Specific Message Contents
- |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 83.4 GPRS Suspend Procedure | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 83.4.1 GPRS Suspension Initiation by the MS, normal Case | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 83.4.1.1 GPRS Suspension Initiation by the MS | 83.4.1.1.1 Conformance requirements
While transitioning to dedicated mode and if unable to support simultaneous CS and PS services, the MS shall request the suspension of the downlink GPRS data transfer by sending a GA-CSR GPRS SUSPENSION REQUEST message to the GANC
Upon receiving a GA-CSR GPRS SUSPENSION REQUEST message from the MS, the GANC completes the GPRS suspend procedure via the Gb interface as defined in [3GPP 48.018].
References
3GPP TS 44.318, subclauses 8.10.1 & 8.10.2 |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 83.4.1.1.2 Test purpose | To verify that the MS requests the suspension of the downlink GPRS data transfer by sending a GA-CSR GPRS SUSPENSION REQUEST message to the GANC, while the MS is transitioning to dedicated mode and if the MS unable to support simultaneous CS and PS services. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 83.4.1.1.3 Method of test | Initial Conditions
System Simulator:
- 1 GAN cell, default parameters
Mobile Station:
- MS GA-PSR is in the GA-PSR-STANDBY state. PDP context 1 is activated.
Foreseen Final State of the MS
MS in GA-PSR-STANDBY state in service of GAN cell
Test Procedure
The SS initiates GA-PSR TC, sending the GA-PSR-ACTIVATE-UTC-REQ. The MS responds with GA-PSR-ACTIVATE-UTC-ACK. The SS sends data, sending GA-PSR-UNITDATA. The SS sends GA-CSR PAGING REQUEST, requesting transitioning of the MS to dedicated mode. MS sends GA-CSR GPRS SUSPENSION REQUEST. The SS verifies that the MS requests GPRS suspension.
Maximum Duration of Test
1 min.
Expected Sequence
Step
Direction
Message
Comments
MS
SS
1
MS
MS is in GA-PSR-STANDBY state
2
GA-PSR-ACTIVATE-UTC-REQ
SS initiates GA-PSR TC
3
GA-PSR-ACTIVATE-UTC-ACK
4
GA-PSR-UNITDATA
5
GA-CSR PAGING REQUEST
6
GA-CSR GPRS SUSPENSION REQUEST
SS verifies that the MS sends the GA-PSR-DATA message
7
GA-PSR-DEACTIVATE-UTC-REQ
SS deactivates
8
GS-PSR DEACTIVATE-UTC-ACK
Specific Message Contents
- |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 83.5 Downlink Flow Control | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 83.5.1 Initiation of the Downlink Flow Control and Processing of the TU4003 Timer Expiry by the MS, Normal Case | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 83.5.1.1 Initiation of the Downlink Flow Control and Processing of the TU4003 Timer Expiry by the MS | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 83.5.1.1.1 Conformance requirements | Upon detecting the downlink flow control condition, the MS shall initiate a downlink flow control procedure by sending a GA-PSR-DFC-REQ message to the GANC via the existing GA-PSR TC. The message includes new estimated data rate that can be supported. At the same time the MS shall start timer TU4003 to continue monitoring the flow control condition. The timer TU4003 is specified in sub-clause 12.
When the TU4003 timer expires, the MS shall re-evaluate the flow control condition and perform the following based on the outcome of the evaluation:
- If the flow control condition still exists (e.g. downlink buffer utilization is still above the low watermark level), the MS shall calculate a new data rate that can be supported and forward the corresponding GA-PSR-DFC-REQ to the GANC via the existing GA-PSR TC. Simultaneously, the MS shall start timer TU4003 to continue monitoring the downlink data transfer.
- If the flow condition has been resolved (e.g. buffer utilization is below the low mark level), the MS shall not restart the TU4003 timer and shall stop sending flow control requests to the GANC.
References
3GPP TS 44.318, subclauses 8.11.1 & 8.11.3 |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 83.5.1.1.2 Test purpose | To verify that:
1) If the flow control condition exists the MS calculates a new data rate that can be supported and forwards the corresponding GA-PSR-DFC-REQ to the GANC via the existing GA-PSR TC.
2) If the timer expires, the MS checks the downlink flow control condition, and if it continues to exist, the MS restarts the timer TU4003, and optionally sends another GA-PSR-DFC-REQ message to the GANC.
3) If the flow condition has been resolved (e.g. buffer utilization is below the low mark level), the MS not restarts the TU4003 timer and stops sending flow control requests to the GANC. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 83.5.1.1.3 Method of test | Initial Conditions
System Simulator:
- 1 GAN cell, default parameters
Mobile Station:
- MS GA-PSR is in the GA-PSR-STANDBY state. PDP context 1 is activated.
Forseen Final State of the MS
MS in GA-PSR-STANDBY state in service of GAN cell
Test Procedure
SS initiates the activation procedure and starts to transmit data. The MS detects flow control condition, sends the GA-PSR-DFC-REQ message and starts the TU4003 timer. SS reduces the data rate and continues to send the data. The SS verifies that the MS does not send GA-PSR-DFC-REQ message.
Maximum Duration of Test
1 min.
Expected Sequence
Step
Direction
Message
Comment
MS
SS
1
MS
MS is in GA-PSR-STANDBY state
2
GA-PSR-ACTIVATE-UTC-REQ
SS initiates GA-PSR TC
3
GA-PSR-ACTIVATE-UTC-ACK
4
GA-PSR-UNITDATA
SS sends data, with very high data rate to overflow the MS
5
GA-PSR-DFC-REQ
MS request DL Flow Control and starts TU4003
6
GA-PSR-UNITDATA
SS sends data, with normal data rate
7
SS
SS verifies that MS does not sends GA-PSR-DFC-REQ for the time exceeding TU4003
8
GA-PSR-DEACTIVATE-UTC-REQ
SS deactivates
9
GS-PSR DEACTIVATE-UTC-ACK
Specific Message Contents
- |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 83.6 Uplink Flow Control | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 83.6.1 Processing of the Uplink Flow Control Request by the MS, Normal Case | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 83.6.1.1 Processing of the Uplink Flow Control Request by the MS | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 83.6.1.1.1 Conformance requirements | Upon detecting the uplink flow control condition, the GANC initiates an uplink flow control procedure by sending a GA-PSR-UFC-REQUEST message to the MS via the existing GA-PSR TC. The request is PFC based if the packet flow management procedures are supported.
Upon receiving the GA-PSR-UFC-REQUEST message from the GANC, the MS adjusts the uplink data rate accordingly.
References
3GPP TS 44.318, subclauses 8.12.1 & 8.12.2 |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 83.6.1.1.2 Test purpose | To verify that the MS adjusts the uplink data rate accordingly with GA-PSR-UFC-REQUEST message received from the GANC. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 83.6.1.1.3 Method of test | Initial Conditions
System Simulator:
- 1 GAN cell, default parameters
Mobile Station:
- MS GA-PSR is in the GA-PSR-STANDBY state. PDP context 1 is activated.
Forseen Final State of the MS
MS in Idle state
Test Procedure
The MS activates GA-PSR TC and starts to send lowest data rate to the SS. SS requests UL Flow Control sending the GA-PSR-UFC-REQ. The MS sends the data with rate adjusted according to GA-PSR-UFC-REQ.
The SS verifies whether the MS sends the data with adjusted data rate.
Maximum Duration of Test
1 min.
Expected Sequence
Step
Direction
Message
Comment
MS
SS
1
MS
MS is in GA-PSR-STANDBY state
2
GA-PSR-ACTIVATE-UTC-REQ
SS is made to activate GA-PSR TC
3
GA-PSR-ACTIVATE-UTC-ACK
4
GA-PSR-UNITDATA
MS sends data
5
GA-PSR-UFC-REQ
SS request UL Flow Control of 100 bits/s.
6
GA-PSR-UNITDATA
MS sends data with the adjusted data rate (100 bits/s), according with GA-PSR-UFC-REQ
7
SS
SS verifies whether the MS have adjusted data rate
8
GA-PSR-DEACTIVATE-UTC-REQ
SS initiates the deactivation
9
GA-PSR-DEACTIVATE-UTC-ACK
MS response on deactivation
Specific Message Contents
- |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 83.6.2 Processing of the Uplink Flow Control Request by the MS, Abnormal Cases | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 83.6.2.1 GA-PSR TC in not Active | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 83.6.2.1.1 Conformance requirements | If the MS receives a GA-PSR-UFC-REQUEST message while the GA-PSR TC deactivation is in progress, the MS shall ignore the flow control request.
References
3GPP TS 44.318, subclauses 8.12.4.1. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 83.6.2.1.2 Test purpose | To verify whether the MS ignores a flow control request received while the GA-PSR TC deactivation is in progress. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 83.6.2.1.3 Method of test | Initial Conditions
System Simulator:
- 1 GAN cell, default parameters
Mobile Station:
- MS GA-PSR is in the GA-PSR-STANDBY state. PDP context 1 is activated.
Foreseen Final State of the MS
MS in GA-PSR-STANDBY state in service of GAN cell
Test Procedure
The MS is in GA-PSR STANDBY state. MS is made to activate GA-PSR TC .SS sends the GA-PSR-UFC-REQ after the MS has initiated deactivation procedure. The MS ignores the flow control request and does not abort deactivation procedure. This is checked by verifying that when asked to send data after expiration of TU4002, the MS sends GA-PSR-ACTIVATE-UTC-REQ..
Maximum Duration of Test
1 min.
Expected Sequence
Step
Direction
Message
Comments
MS
SS
1
MS
MS is in GA-PSR STANDBY state
2
-->
GA-PSR-ACTIVATE-UTC-REQ
MS is made to activate GA-PSR TC, by triggering UL data
3
<--
GA-PSR-ACTIVATE-UTC-ACK
4
-->
GA PSR UNITDATA
MS sends data
5
-->
GA-PSR-DEACTIVATE-UTC-REQ
Sent after TU4001 expires
6
<--
GA-PSR-UFC-REQ
SS request UL Flow Control. Sent before TU4002 expires
7
SS
Wait 5s to allow TU4002 to expire
8
Trigger MS to initiate a data transfer
9
-->
GA-PSR-ACTIVATE-UTC-REQ
MS sends activation request
10
SS
SS verifies that MS sends activation request
Specific Message Contents
- |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 84 GAN Iu Mode Procedures | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 84.1 Macros for GAN Iu mode | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 84.2 GA-RRC connection establishment | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 84.2.1 GA-RRC connection establishment / successful case | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 84.2.1.1 GA-RRC connection establishment, Upper Layer Message Transmission and GA-RRC connection release by GANC (CS domain) | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 84.2.1.1.1 Conformance requirement | The GAN Iu mode GA-RRC CS and PS connections are logical connections between the MS and the GANC. As described in 3GPP TS 43.318, the GA-RRC sub-layer in the MS contains two entities, the CS domain GA-RRC sublayer entity and the PS domain GA-RRC sublayer entity. These entities operate independently and in parallel; e.g., two GA-RRC connections are established in the case of simultaneous CS and PS services, one GA-RRC connection for each domain. Each GA-RRC sub-layer entity in the MS can be in one of two states, GA-RRC-IDLE or GA-RRC-CONNECTED.
A GA-RRC connection is established when the upper layers in the MS request the establishment of a signalling connection for either CS or PS domain and the GA-RRC sub-layer entity in the MS is in the GA-RRC-IDLE state for that domain; i.e., no GA-RRC connection exists. When a successful response is received from the network, GA-RRC replies to the upper layer that the GA-RRC sub-layer entity in the MS has entered the RRC connected mode (i.e., the GA-RRC-CONNECTED state). The upper layers then have the possibility to request transmission of NAS messages to the network.
The GA-RRC INITIAL DIRECT TRANSFER message is used to transfer the "initial" upper layer message for the domain (i.e., the first NAS message after GA-RRC connection establishment for the domain) from the MS to the GANC. Receipt of the GA-RRC INITIAL DIRECT TRANSFER message by the GANC triggers the establishment of the signalling connection to the indicated CN domain for the MS. The GA-RRC UPLINK DIRECT TRANSFER message is used to transfer all subsequent upper layer messages for the signalling connection from the MS to the GANC.
The GA-RRC DOWNLINK DIRECT TRANSFER message is used to transfer upper layer messages from the GANC to the MS.
The GANC initiates the GA-RRC connection release procedure to command the MS to release the GA-RRC connection and any user plane resources for a particular domain and instruct the GA-RRC sub-layer entity of the MS to leave the GA-RRC-CONNECTED state and return to the GA-RRC-IDLE state for the domain. The GANC normally initiates this procedure when it receives the Iu Release Command from the CN; however, the GANC may also initiate this procedure under certain failure conditions.
The GA-RRC RELEASE message includes the IE "GA-RRC Cause". The GA-RRC Cause value should be one of the following:
#83: normal release; e.g., at the end of a call
#115: unspecified failure
Other values, if received, should be treated as "unspecified failure".
When the GA-RRC sublayer entity in the MS receives the GA-RRC RELEASE message, it shall:
- send a GA-RRC RELEASE COMPLETE message to the GANC,
- release the GA-RRC connection and any user plane resources for the indicated domain,
- stop timer TU5002 for the domain (if running),
- stop timer TU5909 for the domain (if running), and
- enter the GA-RRC-IDLE state for the domain.
Reference(s)
3GPP TS 44.318 subclause 8a.1 / 8a.2 / 8a.5.3 / 8a.5.4 |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 84.2.1.1.2 Test purpose | To verify all of the following for the CS domain.
To verify that MS is able to initiate GA-RRC connection establishment between the MS and GANC and to verify that MS is able to communicate with the CN by encapsulating NAS messages in the GA-RRC INITIAL DIRECT TRANSFER message (first NAS message after GA-RRC connection establishment) and GA-RRC UPLINK DIRECT TRANSFER message and able to receive upper layer messages within GA-RRC DOWNLINK DIRECT TRANSFER message.
To verify that MS is able to release the GA-RRC connection, able to move into GA-RRC-IDLE state and release all GA-RRC and any traffic channel resources, when the MS receives the GA-RRC RELEASE message from SS. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 84.2.1.1.3 Method of test | Initial Conditions
System Simulator:
- 1 GAN cell, default parameters
Mobile Station:
- MS in GA-RRC-IDLE state for CS domain in service of GAN cell
Foreseen Final State of the MS
MS in GA-RRC-IDLE state for CS domain.
Test Procedure
The MS is made to initiate a GA-RRC connection establishment for CS domain. The MS moves into GA-RRC-CONNECTED state when the MS receives the GA-RRC REQUEST ACCEPT message from the SS within timer TU5908 (5 sec.) from sending GA-RRC REQUEST message. SS verifies that MS sends GA-RRC INITIAL DIRECT TRANSFER message within 10s from GA-RRC REQUEST ACCEPT message. The SS answers by sending upper layer message within GA-RRC DOWNLINK DIRECT TRANSFER container message.
The SS sends GA-RRC RELEASE message. The MS enters GA-RRC-IDLE state and transmits a GA-RRC RELEASE COMPLETE to the SS and releases all GA-RRC and any traffic channel resources.
Specific test parameters
-
Maximum Duration of Test
1 min.
Expected Sequence
Step
Direction
Message
Comment
MS
SS
1
MS
MS is made to initiate GA-RRC connection
2
MS
MS checks for access permission based on Access Control Class bits
3
GA-RRC REQUEST
IE 'CN Domain Identity' indicates CS domain
4
GA-RRC REQUEST ACCEPT
IE 'CN Domain Identity' indicates CS domain
5
MS
MS in GA-RRC-CONNECTED state for CS domain
6
GA-RRC INITIAL DIRECT TRANSFER
Within 10s from GA-RRC REQUEST ACCEPT message
Containing NAS message
IE 'CN Domain Identity' indicates CS domain
7
GA-RRC DOWNLINK DIRECT TRANSFER
Containing NAS message
IE 'CN Domain Identity' indicates CS domain
8
GA-RRC RELEASE
IE ‘GA-RRC Cause’ indicates #83
IE 'CN Domain Identity' indicates CS domain
9
GA-RRC RELEASE COMPLETE
MS enters GA-RRC-IDLE state
IE 'CN Domain Identity' indicates CS domain |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 84.2.1.2 GA-RRC connection establishment, Upper Layer Message Transmission and GA-RRC connection release by GANC (PS domain) | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 84.2.1.2.1 Conformance requirement | The GAN Iu mode GA-RRC CS and PS connections are logical connections between the MS and the GANC. As described in 3GPP TS 43.318, the GA-RRC sub-layer in the MS contains two entities, the CS domain GA-RRC sublayer entity and the PS domain GA-RRC sublayer entity. These entities operate independently and in parallel; e.g., two GA-RRC connections are established in the case of simultaneous CS and PS services, one GA-RRC connection for each domain. Each GA-RRC sub-layer entity in the MS can be in one of two states, GA-RRC-IDLE or GA-RRC-CONNECTED.
A GA-RRC connection is established when the upper layers in the MS request the establishment of a signalling connection for either CS or PS domain and the GA-RRC sub-layer entity in the MS is in the GA-RRC-IDLE state for that domain; i.e., no GA-RRC connection exists. When a successful response is received from the network, GA-RRC replies to the upper layer that the GA-RRC sub-layer entity in the MS has entered the RRC connected mode (i.e., the GA-RRC-CONNECTED state). The upper layers then have the possibility to request transmission of NAS messages to the network.
The GA-RRC INITIAL DIRECT TRANSFER message is used to transfer the "initial" upper layer message for the domain (i.e., the first NAS message after GA-RRC connection establishment for the domain) from the MS to the GANC. Receipt of the GA-RRC INITIAL DIRECT TRANSFER message by the GANC triggers the establishment of the signalling connection to the indicated CN domain for the MS. The GA-RRC UPLINK DIRECT TRANSFER message is used to transfer all subsequent upper layer messages for the signalling connection from the MS to the GANC.
The GA-RRC DOWNLINK DIRECT TRANSFER message is used to transfer upper layer messages from the GANC to the MS.
The GANC initiates the GA-RRC connection release procedure to command the MS to release the GA-RRC connection and any user plane resources for a particular domain and instruct the GA-RRC sub-layer entity of the MS to leave the GA-RRC-CONNECTED state and return to the GA-RRC-IDLE state for the domain. The GANC normally initiates this procedure when it receives the Iu Release Command from the CN; however, the GANC may also initiate this procedure under certain failure conditions.
The GA-RRC RELEASE message includes the IE "GA-RRC Cause". The GA-RRC Cause value should be one of the following:
#83: normal release; e.g., at the end of a call
#115: unspecified failure
Other values, if received, should be treated as "unspecified failure".
When the GA-RRC sublayer entity in the MS receives the GA-RRC RELEASE message, it shall:
- send a GA-RRC RELEASE COMPLETE message to the GANC,
- release the GA-RRC connection and any user plane resources for the indicated domain,
- stop timer TU5002 for the domain (if running),
- stop timer TU5909 for the domain (if running), and
- enter the GA-RRC-IDLE state for the domain.
Reference(s)
3GPP TS 44.318 subclause 8a.1 / 8a.2 / 8a.5.3 / 8a.5.4 |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 84.2.1.2.2 Test purpose | To verify all of the following for the PS domain.
To verify that MS is able to initiate GA-RRC connection establishment between the MS and GANC and to verify that MS is able to communicate with the CN by encapsulating NAS messages in the GA-RRC INITIAL DIRECT TRANSFER message (first NAS message after GA-RRC connection establishment) and GA-RRC UPLINK DIRECT TRANSFER message and able to receive upper layer messages within GA-RRC DOWNLINK DIRECT TRANSFER message.
To verify that MS is able to release the GA-RRC connection, able to move into GA-RRC-IDLE state and release all GA-RRC and any traffic channel resources, when the MS receives the GA-RRC RELEASE message from SS. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 84.2.1.2.3 Method of test | Initial Conditions
System Simulator:
- 1 GAN cell, default parameters
Mobile Station:
- MS in GA-RRC-IDLE state for PS domain in service of GAN cell
Foreseen Final State of the MS
MS in GA-RRC-IDLE state for PS domain.
Test Procedure
The MS is made to initiate a GA-RRC connection establishment for PS domain. The MS moves into GA-RRC-CONNECTED state when the MS receives the GA-RRC REQUEST ACCEPT message from the SS within timer TU5908 (5 sec.) from sending GA-RRC REQUEST message. SS verifies that MS sends GA-RRC INITIAL DIRECT TRANSFER message within 10s from GA-RRC REQUEST ACCEPT message. The SS answers by sending upper layer message within GA-RRC DOWNLINK DIRECT TRANSFER container message.
The SS sends GA-RRC RELEASE message. The MS enters GA-RRC-IDLE state and transmits a GA-RRC RELEASE COMPLETE to the SS and releases all GA-RRC and any traffic channel resources.
Specific test parameters
-
Maximum Duration of Test
1 min.
Expected Sequence
Step
Direction
Message
Comment
MS
SS
1
MS
MS is made to initiate GA-RRC connection
2
MS
MS checks for access permission based on Access Control Class bits
3
GA-RRC REQUEST
IE 'CN Domain Identity' indicates PS domain
4
GA-RRC REQUEST ACCEPT
IE 'CN Domain Identity' indicates PS domain
5
MS
MS in GA-RRC-CONNECTED state for PS domain
6
GA-RRC INITIAL DIRECT TRANSFER
Within 10s from GA-RRC REQUEST ACCEPT message
Containing NAS message
IE 'CN Domain Identity' indicates PS domain
7
GA-RRC DOWNLINK DIRECT TRANSFER
Containing NAS message
IE 'CN Domain Identity' indicates PS domain
8
GA-RRC RELEASE
IE ‘GA-RRC Cause’ indicates #83
IE 'CN Domain Identity' indicates PS domain
9
GA-RRC RELEASE COMPLETE
MS enters GA-RRC-IDLE state
IE 'CN Domain Identity' indicates PS domain |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 84.2.2 GA-RRC connection establishment / negative cases | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 84.2.2.1 GA-RRC REQUEST rejected (CS domain) | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 84.2.2.1.1 Conformance requirement | 3GPP TS 44.318 subclause 8a.1.2.2:
If the GANC rejects the GA-RRC connection establishment request, it shall send the GA-RRC REQUEST REJECT message to the MS including the IE "CN Domain Identity".
3GPP TS 44.318 subclause 8a.1.3.2:
When the MS receives the GA-RRC REQUEST REJECT message, it shall:
- if timer TU5908 is active for the domain indicated by the IE "CN Domain Identity":
- stop timer TU5908 for that domain,
- remain in the GA-RRC-IDLE state for that domain, and
- indicate to upper layers that GA-RRC was not able to enter the connected state for that domain;
- if timer TU5908 is not active for the domain indicated by the IE "CN Domain Identity":
- ignore the GA-RRC REQUEST REJECT message, and
- continue with the procedure as if the GA-RRC REQUEST REJECT message was not received.
3GPP TS 44.318 subclause 8a.3.2:
If the mobile identity in the GA-RRC PAGING REQUEST message matches any of the valid identities of the MS and the GA-RRC sub-layer entity in the MS is in the GA-RRC-IDLE state for the indicated domain, the MS shall:
- if timer TU5908 is not active for the domain and access to the network is allowed:
- indicate reception of paging to upper layers, and
- forward the IE "CN Domain Identity", the IE "Mobile Identity" and the IE "Paging Cause" (if received) to the upper layers;
- Note: The upper layers will request the establishment of a signalling connection and the transmission of the paging response in the initial NAS message. This results in the implicit establishment of the GA-RRC connection (i.e., the GA-RRC sub-layer entity in the MS enters the GA-RRC CONNECTED state) and the transmission of the paging response from the MS to the GANC in the GA-RRC INITIAL DIRECT TRANSFER message, as shown in Figure 8a.3.1.
- if timer TU5908 is active for the domain:
- ignore the GA-RRC PAGING REQUEST message, and
- continue with the ongoing procedure as if the GA-RRC PAGING REQUEST was not received.
Reference(s)
3GPP TS 44.318 subclauses 8a.1.2.2 / 8a.1.3.2 / 8a.3.2 |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 84.2.2.1.2 Test purpose | To verify that MS will remain in GA-RRC-IDLE state (CS domain) when MS receives the GA-RRC REQUEST REJECT message (CS domain). |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 84.2.2.1.3 Method of test | Initial Conditions
System Simulator:
- 1 GAN cell, default parameters
Mobile Station:
- MS in GA-RRC-IDLE state for CS domain in service of GAN cell
Foreseen Final State of the MS
MS in GA-RRC- IDLE state for CS domain.
Test Procedure
The MS is made to initiate a GA-RRC connection establishment for CS domain. SS sends the GA-RRC REQUEST REJECT message to the MS. MS is not able to enter GA-RRC-CONNECTED state. The SS sends GA-RRC PAGING REQUEST to verify that MS in GA-RRC-IDLE state. MS answers by sending GA-RRC INITIAL DIRECT TRANSFER message containing paging response.
Specific test parameters
-
Maximum Duration of Test
1 min.
Expected Sequence
Step
Direction
Message
Comment
MS
SS
1
MS
MS is made to initiate GA-RRC connection
2
MS
MS checks for access permission based on Access Control Class bits
3
GA-RRC REQUEST
IE 'CN Domain Identity' indicates CS domain
TU5908 is started
4
GA-RRC REQUEST REJECT
The SS sends GA-RRC REQUEST REJECT before the expiry of TU5908.
IE 'CN Domain Identity' indicates CS domain
5
MS
MS in GA-RRC-IDLE state for CS domain
6
GA-RRC PAGING REQUEST
Valid identity of the MS (‘TMSI’/’IMSI’)
IE 'CN Domain Identity' indicates CS domain
7
GA-RRC INITIAL DIRECT TRANSFER
IE 'L3 Message' contains Paging Response
IE 'CN Domain Identity' indicates CS domain
MS enters GA-RRC-CONNECTED state for CS domain
8
GA-RRC RELEASE
IE ‘RR cause’ indicates #83
IE 'CN Domain Identity' indicates CS domain
9
GA-RRC RELEASE COMPLETE
IE 'CN Domain Identity' indicates CS domain
MS enters GA-RRC-IDLE state for CS domain |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 84.2.2.2 MS receives GA-RRC REQUEST ACCEPT message after TU5908 expiry (CS domain) | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 84.2.2.2.1 Conformance requirement | If the GANC accepts the GA-RRC connection establishment request, it shall send the GA-RRC REQUEST ACCEPT message to the MS including the IE "CN Domain Identity".
When the MS receives the GA-RRC REQUEST ACCEPT message, it shall:
- if timer TU5908 is active for the domain indicated by the IE "CN Domain Identity":
- stop timer TU5908 for that domain,
- move into the GA-RRC-CONNECTED state for that domain,
- indicate to upper layers that GA-RRC has entered the connected state for that domain, and
- send the GA-RRC INITIAL DIRECT TRANSFER message to the network;
- if timer TU5908 is not active for the domain indicated by the IE "CN Domain Identity":
- ignore the GA-RRC REQUEST ACCEPT message, and
- continue with the procedure as if the GA-RRC REQUEST ACCEPT message was not received.
If timer TU5908 expires in the MS, the GA-RRC sub-layer entity in the MS shall remain in the GA-RRC-IDLE state and indicate to upper layers that GA-RRC was not able to enter the connected state for the domain.
If the mobile identity in the GA-RRC PAGING REQUEST message matches any of the valid identities of the MS and the GA-RRC sub-layer entity in the MS is in the GA-RRC-IDLE state for the indicated domain, the MS shall:
- if timer TU5908 is not active for the domain and access to the network is allowed:
- indicate reception of paging to upper layers, and
- forward the IE "CN Domain Identity", the IE "Mobile Identity" and the IE "Paging Cause" (if received) to the upper layers;
- Note: The upper layers will request the establishment of a signalling connection and the transmission of the paging response in the initial NAS message. This results in the implicit establishment of the GA-RRC connection (i.e., the GA-RRC sub-layer entity in the MS enters the GA-RRC CONNECTED state) and the transmission of the paging response from the MS to the GANC in the GA-RRC INITIAL DIRECT TRANSFER message, as shown in Figure 8a.3.1.
- if timer TU5908 is active for the domain:
- ignore the GA-RRC PAGING REQUEST message, and
- continue with the ongoing procedure as if the GA-RRC PAGING REQUEST was not received.
Reference(s)
3GPP TS 44.318 subclauses 8a.1.2.1 / 8a.1.3.1 / 8a.1.4.1 / 8a.3.2 |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 84.2.2.2.2 Test purpose | To verify that MS will remain in GA-RRC IDLE state (CS domain) if TU5908 expires before MS receives the GA-RRC REQUEST ACCEPT message (CS domain). |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 84.2.2.2.3 Method of test | Initial Conditions
System Simulator:
- 1 GAN cell, default parameters
Mobile Station:
- MS in GA-RRC-IDLE state for CS domain in service of GAN cell
Foreseen Final State of the MS
MS in GA-RRC- IDLE state for CS domain.
Test Procedure
The MS is made to initiate a GA-RRC connection establishment for CS domain. MS receives the GA-RRC REQUEST ACCEPT message from the SS after timer TU5908 (5 sec.) expires. MS remains in GA-RRC IDLE state. The MS may send GA-RRC-REQUEST message due to upper layer requesting to restart the higher layer procedure which verifies that MS has been in GA-RRC-IDLE state. If GA-RRC-REQUEST message is not received, the SS sends GA-RRC PAGING REQUEST to verify that MS in GA-RRC-IDLE state. MS answers by sending GA-RRC INITIAL DIRECT TRANSFER message containing paging response.
Specific test parameters
-
Maximum Duration of Test
1 min.
Expected Sequence
Step
Direction
Message
Comment
MS
SS
1
MS
MS is made to initiate GA-RRC connection
2
MS
MS checks for access permission based on Access Control Class bits
3
GA-RRC REQUEST
IE 'CN Domain Identity' indicates CS domain
4
SS
SS waits 5 seconds after SS has received the GA-RRC REQUEST message
5
MS
TU5908 expires
6
GA-RRC REQUEST ACCEPT
IE 'CN Domain Identity' indicates CS domain
7
MS
MS ignores the GA-RRC REQUEST ACCEPT message and remains in GA-RRC-IDLE state for CS domain
7a (optional)
GA-RRC REQUEST
MS may send GA-RRC-REQUEST message due to upper layer restarting the higher layer procedure. This verifies that the MS has been in GA-RRC-IDLE state.
IE 'CN Domain Identity' indicates CS domain
8 (conditional)
GA-RRC PAGING REQUEST
Valid identity of the MS (‘TMSI’/’IMSI’)
IE 'CN Domain Identity' indicates CS domain
9 (conditional)
GA-RRC INITIAL DIRECT TRANSFER
IE 'L3 Message' contains Paging Response
IE 'CN Domain Identity' indicates CS domain
MS enters GA-RRC-CONNECTED state for CS domain
10 (conditional)
GA-RRC RELEASE
IE ‘GA-RRC Cause’ indicates #83
IE 'CN Domain Identity' indicates CS domain
11 (conditional)
GA-RRC RELEASE COMPLETE
IE 'CN Domain Identity' indicates CS domain
MS enters GA-RRC-IDLE state for CS domain
NOTE: Steps 8-11 are not applicable If GA-RRC-REQUEST message is received in step 7a |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 84.2.2.3 GA-RRC REQUEST rejected (PS domain) | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 84.2.2.3.1 Conformance requirement | 3GPP TS 44.318 subclause 8a.1.2.2:
If the GANC rejects the GA-RRC connection establishment request, it shall send the GA-RRC REQUEST REJECT message to the MS including the IE "CN Domain Identity".
3GPP TS 44.318 subclause 8a.1.3.2:
When the MS receives the GA-RRC REQUEST REJECT message, it shall:
- if timer TU5908 is active for the domain indicated by the IE "CN Domain Identity":
- stop timer TU5908 for that domain,
- remain in the GA-RRC-IDLE state for that domain, and
- indicate to upper layers that GA-RRC was not able to enter the connected state for that domain;
- if timer TU5908 is not active for the domain indicated by the IE "CN Domain Identity":
- ignore the GA-RRC REQUEST REJECT message, and
- continue with the procedure as if the GA-RRC REQUEST REJECT message was not received.
3GPP TS 44.318 subclause 8a.3.2:
If the mobile identity in the GA-RRC PAGING REQUEST message matches any of the valid identities of the MS and the GA-RRC sub-layer entity in the MS is in the GA-RRC-IDLE state for the indicated domain, the MS shall:
- if timer TU5908 is not active for the domain and access to the network is allowed:
- indicate reception of paging to upper layers, and
- forward the IE "CN Domain Identity", the IE "Mobile Identity" and the IE "Paging Cause" (if received) to the upper layers;
- Note: The upper layers will request the establishment of a signalling connection and the transmission of the paging response in the initial NAS message. This results in the implicit establishment of the GA-RRC connection (i.e., the GA-RRC sub-layer entity in the MS enters the GA-RRC CONNECTED state) and the transmission of the paging response from the MS to the GANC in the GA-RRC INITIAL DIRECT TRANSFER message, as shown in Figure 8a.3.1.
- if timer TU5908 is active for the domain:
- ignore the GA-RRC PAGING REQUEST message, and
- continue with the ongoing procedure as if the GA-RRC PAGING REQUEST was not received.
Reference(s)
3GPP TS 44.318 subclauses 8a.1.2.2 / 8a.1.3.2 / 8a.3.2 |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 84.2.2.3.2 Test purpose | To verify that MS will remain in GA-RRC-IDLE state (PS domain) when MS receives the GA-RRC REQUEST REJECT message (PS domain). |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 84.2.2.3.3 Method of test | Initial Conditions
System Simulator:
- 1 GAN cell, default parameters
Mobile Station:
- MS in GA-RRC-IDLE state for PS domain in service of GAN cell
Foreseen Final State of the MS
MS in GA-RRC- IDLE state for PS domain.
Test Procedure
The MS is made to initiate a GA-RRC connection establishment for PS domain. SS sends the GA-RRC REQUEST REJECT message to the MS. MS is not able to enter GA-RRC-CONNECTED state. The SS sends GA-RRC PAGING REQUEST to verify that MS in GA-RRC-IDLE state. MS answers by sending GA-RRC INITIAL DIRECT TRANSFER message containing paging response.
Specific test parameters
-
Maximum Duration of Test
1 min.
Expected Sequence
Step
Direction
Message
Comment
MS
SS
1
MS
MS is made to initiate GA-RRC connection
2
MS
MS checks for access permission based on Access Control Class bits
3
GA-RRC REQUEST
IE 'CN Domain Identity' indicates PS domain
TU5908 is started
4
GA-RRC REQUEST REJECT
The SS sends GA-RRC REQUEST REJECT before the expiry of TU5908.
IE 'CN Domain Identity' indicates PS domain
5
MS
MS in GA-RRC-IDLE state for PS domain
6
GA-RRC PAGING REQUEST
Valid identity of the MS (‘TMSI’/’IMSI’)
IE 'CN Domain Identity' indicates PS domain
7
GA-RRC INITIAL DIRECT TRANSFER
IE 'L3 Message' contains Paging Response
IE 'CN Domain Identity' indicates PS domain
MS enters GA-RRC-CONNECTED state for PS domain
8
GA-RRC RELEASE
IE ‘RR cause’ indicates #83
IE 'CN Domain Identity' indicates PS domain
9
GA-RRC RELEASE COMPLETE
IE 'CN Domain Identity' indicates PS domain
MS enters GA-RRC-IDLE state for PS domain |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 84.2.2.4 MS receives GA-RRC REQUEST ACCEPT message after TU5908 expiry (PS domain) | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 84.2.2.4.1 Conformance requirement | If the GANC accepts the GA-RRC connection establishment request, it shall send the GA-RRC REQUEST ACCEPT message to the MS including the IE "CN Domain Identity".
When the MS receives the GA-RRC REQUEST ACCEPT message, it shall:
- if timer TU5908 is active for the domain indicated by the IE "CN Domain Identity":
- stop timer TU5908 for that domain,
- move into the GA-RRC-CONNECTED state for that domain,
- indicate to upper layers that GA-RRC has entered the connected state for that domain, and
- send the GA-RRC INITIAL DIRECT TRANSFER message to the network;
- if timer TU5908 is not active for the domain indicated by the IE "CN Domain Identity":
- ignore the GA-RRC REQUEST ACCEPT message, and
- continue with the procedure as if the GA-RRC REQUEST ACCEPT message was not received.
If timer TU5908 expires in the MS, the GA-RRC sub-layer entity in the MS shall remain in the GA-RRC-IDLE state and indicate to upper layers that GA-RRC was not able to enter the connected state for the domain.
If the mobile identity in the GA-RRC PAGING REQUEST message matches any of the valid identities of the MS and the GA-RRC sub-layer entity in the MS is in the GA-RRC-IDLE state for the indicated domain, the MS shall:
- if timer TU5908 is not active for the domain and access to the network is allowed:
- indicate reception of paging to upper layers, and
- forward the IE "CN Domain Identity", the IE "Mobile Identity" and the IE "Paging Cause" (if received) to the upper layers;
- Note: The upper layers will request the establishment of a signalling connection and the transmission of the paging response in the initial NAS message. This results in the implicit establishment of the GA-RRC connection (i.e., the GA-RRC sub-layer entity in the MS enters the GA-RRC CONNECTED state) and the transmission of the paging response from the MS to the GANC in the GA-RRC INITIAL DIRECT TRANSFER message, as shown in Figure 8a.3.1.
- if timer TU5908 is active for the domain:
- ignore the GA-RRC PAGING REQUEST message, and
- continue with the ongoing procedure as if the GA-RRC PAGING REQUEST was not received.
Reference(s)
3GPP TS 44.318 subclauses 8a.1.2.1 / 8a.1.3.1 / 8a.1.4.1 / 8a.3.2 |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 84.2.2.4.2 Test purpose | To verify that MS will remain in GA-RRC IDLE state (PS domain) if TU5908 expires before MS receives the GA-RRC REQUEST ACCEPT message (PS domain). |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 84.2.2.4.3 Method of test | Initial Conditions
System Simulator:
- 1 GAN cell, default parameters
Mobile Station:
- MS in GA-RRC-IDLE state for PS domain in service of GAN cell
Foreseen Final State of the MS
MS in GA-RRC- IDLE state for PS domain.
Test Procedure
The MS is made to initiate a GA-RRC connection establishment for PS domain. MS receives the GA-RRC REQUEST ACCEPT message from the SS after timer TU5908 (5 sec.) expires. MS remains in GA-RRC IDLE state. The MS may send GA-RRC-REQUEST message due to upper layer requesting to restart the higher layer procedure which verifies that MS has been in GA-RRC-IDLE state. If GA-RRC-REQUEST message is not received, the SS sends GA-RRC PAGING REQUEST to verify that MS in GA-RRC-IDLE state. MS answers by sending GA-RRC INITIAL DIRECT TRANSFER message containing paging response.
Specific test parameters
-
Maximum Duration of Test
1 min.
Expected Sequence
Step
Direction
Message
Comment
MS
SS
1
MS
MS is made to initiate GA-RRC connection
2
MS
MS checks for access permission based on Access Control Class bits
3
GA-RRC REQUEST
IE 'CN Domain Identity' indicates PS domain
4
SS
SS waits 5 seconds after SS has received the GA-RRC REQUEST message
5
MS
TU5908 expires
6
GA-RRC REQUEST ACCEPT
IE 'CN Domain Identity' indicates PS domain
7
MS
MS ignores the GA-RRC REQUEST ACCEPT message and remains in GA-RRC-IDLE state for PS domain
7a (optional)
GA-RRC REQUEST
MS may send GA-RRC-REQUEST message due to upper layer restarting the higher layer procedure. This verifies that the MS has been in GA-RRC-IDLE state.
IE 'CN Domain Identity' indicates PS domain
8 (conditional)
GA-RRC PAGING REQUEST
Valid identity of the MS (‘TMSI’/’IMSI’)
IE 'CN Domain Identity' indicates PS domain
9 (conditional)
GA-RRC INITIAL DIRECT TRANSFER
IE 'L3 Message' contains Paging Response
IE 'CN Domain Identity' indicates PS domain
MS enters GA-RRC-CONNECTED state for PS domain
10 (conditional)
GA-RRC RELEASE
IE ‘GA-RRC Cause’ indicates #83
IE 'CN Domain Identity' indicates PS domain
11 (conditional)
GA-RRC RELEASE COMPLETE
IE 'CN Domain Identity' indicates PS domain
MS enters GA-RRC-IDLE state for PS domain
NOTE: Steps 8-11 are not applicable If GA-RRC-REQUEST message is received in step 7a |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 84.3 Upper layer message transmission | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 84.3.1 Upper layer message transmission / successful cases | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 84.3.1.1 Void | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 84.3.2 Upper layer message transmission / negative cases | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 84.3.2.1 MS receives GA-RRC DOWNLINK DIRECT TRANSFER message when not in GA-RRC-CONNECTED state (CS domain) | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 84.3.2.1.1 Conformance requirement | If the MS receives a GA-RRC DOWNLINK DIRECT TRANSFER message and GA-RRC sub-layer entity in the MS is not in GA-RRC-CONNECTED state for the indicated domain, the MS shall:
- ignore the contents of the GA-RRC DOWNLINK DIRECT TRANSFER message;
- transmit a GA-RRC STATUS message to the GANC as follows:
- set the IE "GA-RRC Cause" to "Message type not compatible with protocol state"
- include the received message contents in the IE "PDU in Error"
- continue with any ongoing procedure and act as if the GA-RRC DOWNLINK DIRECT TRANSFER message was not received.
Reference(s)
3GPP TS 44.318 subclause 8a.2.6.1 |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 84.3.2.1.2 Test purpose | To verify that MS ignores the contents of the GA-RRC DOWNLINK DIRECT TRANSFER message (CS domain) if MS is not in GA-RRC-CONNECTED state (CS domain) and to be able to send GA-RRC STATUS message to the SS. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 84.3.2.1.3 Method of test | Initial Conditions
System Simulator:
- 1 GAN cell, default parameters
Mobile Station:
- MS in GA-RRC-IDLE state for CS domain in service of GAN cell
Foreseen Final State of the MS
MS in GA-RRC-IDLE state for CS domain in service of GAN cell
Test Procedure
MS is in GA-RRC-IDLE state for CS domain in service of GAN cell. SS sends GA-RRC DOWNLINK DIRECT TRANSFER message containing upper layer message. MS ignores the contents of the message and sends GA-RRC STATUS message to the SS with IE ‘GA-RRC Cause’: ‘Message type not compatible with protocol state’. MS includes the received message contents in the IE ‘PDU in error’.
Specific test parameters
-
Maximum Duration of Test
1 min.
Expected Sequence
Step
Direction
Message
Comment
MS
SS
1
MS
MS in GA-RRC-IDLE state for CS domain
2
GA-RRC DOWNLINK DIRECT TRANSFER
Containing (DL) CC/MM/SS/SMS message
IE 'CN Domain Identity' indicates CS domain
3
GA-RRC STATUS
IE 'CN Domain Identity' indicates CS domain
IE 'GA-RRC Cause' indicates #99
IE PDU in Error: ‘<received (DL) message>’ |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 84.3.2.2 MS receives GA-RRC DOWNLINK DIRECT TRANSFER message when not in GA-RRC-CONNECTED state (PS domain) | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 84.3.2.2.1 Conformance requirement | If the MS receives a GA-RRC DOWNLINK DIRECT TRANSFER message and GA-RRC sub-layer entity in the MS is not in GA-RRC-CONNECTED state for the indicated domain, the MS shall:
- ignore the contents of the GA-RRC DOWNLINK DIRECT TRANSFER message;
- transmit a GA-RRC STATUS message to the GANC as follows:
- set the IE "GA-RRC Cause" to "Message type not compatible with protocol state"
- include the received message contents in the IE "PDU in Error"
- continue with any ongoing procedure and act as if the GA-RRC DOWNLINK DIRECT TRANSFER message was not received.
Reference(s)
3GPP TS 44.318 subclause 8a.2.6.1 |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 84.3.2.2.2 Test purpose | To verify that MS ignores the contents of the GA-RRC DOWNLINK DIRECT TRANSFER message (PS domain) if MS is not in GA-RRC-CONNECTED state (PS domain) and to be able to send GA-RRC STATUS message to the SS. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 84.3.2.2.3 Method of test | Initial Conditions
System Simulator:
- 1 GAN cell, default parameters
Mobile Station:
- MS in GA-RRC-IDLE state for PS domain in service of GAN cell
Foreseen Final State of the MS
MS in GA-RRC-IDLE state for PS domain in service of GAN cell
Test Procedure
MS is in GA-RRC-IDLE state for PS domain in service of GAN cell. SS sends GA-RRC DOWNLINK DIRECT TRANSFER message containing upper layer message. MS ignores the contents of the message and sends GA-RRC STATUS message to the SS with IE ‘GA-RRC Cause’: ‘Message type not compatible with protocol state’. MS includes the received message contents in the IE ‘PDU in error’.
Specific test parameters
-
Maximum Duration of Test
1 min.
Expected Sequence
Step
Direction
Message
Comment
MS
SS
1
MS
MS in GA-RRC-IDLE state for PS domain
2
GA-RRC DOWNLINK DIRECT TRANSFER
Containing (DL) CC/MM/SS/SMS message
IE 'CN Domain Identity' indicates PS domain
3
GA-RRC STATUS
IE 'CN Domain Identity' indicates PS domain
IE 'GA-RRC Cause' indicates #99
IE PDU in Error: ‘<received (DL) message>’ |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 84.4 Paging | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 84.4.1 Paging for CS domain / successful cases | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 84.4.1.1 Paging for CS domain | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 84.4.1.1.1 Conformance requirement | 3GPP TS 44.318 subclause 8a.3.1:
The GANC sends the GA-RRC PAGING REQUEST message to the MS when the GANC receives a PAGING message over the Iu interface from a CN domain. The IMSI of the MS to be paged is identified by the IE "Permanent NAS UE Identity" received in the request from the CN. If the request also includes the (P-)TMSI then the GANC shall include the (P-)TMSI in the IE "Mobile Identity"; else the GANC shall include the IMSI in the IE "Mobile Identity". The GANC also includes the IE "CN Domain Identity" and the IE "GA-RRC Paging Cause", if a cause is received from the CN.
3GPP TS 44.318 subclause 8a.3.2:
If the mobile identity in the GA-RRC PAGING REQUEST message matches any of the valid identities of the MS and the GA-RRC sub-layer entity in the MS is in the GA-RRC-IDLE state for the indicated domain, the MS shall:
- if timer TU5908 is not active for the domain and access to the network is allowed:
- indicate reception of paging to upper layers, and
- forward the IE "CN Domain Identity", the IE "Mobile Identity" and the IE "Paging Cause" (if received) to the upper layers;
- Note: The upper layers will request the establishment of a signalling connection and the transmission of the paging response in the initial NAS message. This results in the implicit establishment of the GA-RRC connection (i.e., the GA-RRC sub-layer entity in the MS enters the GA-RRC CONNECTED state) and the transmission of the paging response from the MS to the GANC in the GA-RRC INITIAL DIRECT TRANSFER message, as shown in Figure 8a.3.1.
- if timer TU5908 is active for the domain:
- ignore the GA-RRC PAGING REQUEST message, and
- continue with the ongoing procedure as if the GA-RRC PAGING REQUEST was not received.
3GPP TS 44.318 subclause 8a.3.3:
If the MS receives a GA-RRC PAGING REQUEST and the mobile identity included in the message does not match any of the valid identities assigned to the MS, the MS shall:
- ignore the GA-RRC PAGING REQUEST message, and
- continue with any ongoing procedure as if the GA-RRC PAGING REQUEST message was not received.
Reference(s)
3GPP TS 44.318 subclauses 8a.3.1 / 8a.3.2 / 8a.3.3 |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 84.4.1.1.2 Test purpose | To verify all of the following for the CS domain.
To verify that MS ignores the GA-RRC PAGING REQUEST and continues with any ongoing procedure, if received GA-RRC PAGING REQUEST doesn’t contain valid identity.
To verify that MS is able send a GA-RRC INITIAL DIRECT TRANSFER containing a page response to the SS and enter GA-RRC-CONNECTED state when MS receives GA-RRC PAGING REQUEST with valid identities of the MS. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 84.4.1.1.3 Method of test | Initial Conditions
System Simulator:
- 1 GAN cell, default parameters
Mobile Station:
- MS in GA-RRC-IDLE state for CS domain in service of GAN cell
Foreseen Final State of the MS
MS in GA-RRC-IDLE state for CS domain in service of GAN cell
Test Procedure
The SS initiates paging procedure by sending GA-RRC PAGING REQUEST message with not matching identity to the MS. MS ignores the GA-RRC PAGING REQUEST and continues with any ongoing procedure as if the GA-RRC PAGING REQUEST was not received. After 10s the SS sends GA-RRC PAGING REQUEST to verify that MS in GA-RRC-IDLE state. MS answers by sending GA-RRC INITIAL DIRECT TRANSFER message containg page response.
Specific test parameters
-
Maximum Duration of Test
1 min.
Expected Sequence
Step
Direction
Message
Comment
MS
SS
1
GA-RRC PAGING REQUEST
With not matching identity
IE 'CN Domain Identity' indicates CS domain
2
MS
MS ignores GA-RRC PAGING REQUEST message
3
SS
SS waits 10s for response
4
GA-RRC PAGING REQUEST
Valid identity of the MS (‘TMSI’/’IMSI’)
IE 'CN Domain Identity' indicates CS domain
5
GA-RRC INITIAL DIRECT TRANSFER
IE 'L3 Message' contains Paging Response
IE 'CN Domain Identity' indicates CS domain
MS enters GA-RRC-CONNECTED state for CS domain
6
GA-RRC RELEASE
IE ‘GA-RRC Cause’ = #83
IE 'CN Domain Identity' indicates CS domain
7
GA-RRC RELEASE COMPLETE
IE 'CN Domain Identity' indicates CS domain
MS enters GA-RRC-IDLE state for CS domain |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 84.4.2 Paging for CS domain / negative cases | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 84.4.2.1 Void | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 84.4.2.2 Paging for CS domain / negative cases / MS receives GA-RRC PAGING REQUEST when TU5908 is active | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 84.4.2.2.1 Conformance requirement | If the mobile identity in the GA-RRC PAGING REQUEST message matches any of the valid identities of the MS and the GA-RRC sub-layer entity in the MS is in the GA-RRC-IDLE state for the indicated domain, the MS shall:
- if timer TU5908 is not active for the domain and access to the network is allowed:
- indicate reception of paging to upper layers, and
- forward the IE "CN Domain Identity", the IE "Mobile Identity" and the IE "Paging Cause" (if received) to the upper layers;
- Note: The upper layers will request the establishment of a signalling connection and the transmission of the paging response in the initial NAS message. This results in the implicit establishment of the GA-RRC connection (i.e., the GA-RRC sub-layer entity in the MS enters the GA-RRC CONNECTED state) and the transmission of the paging response from the MS to the GANC in the GA-RRC INITIAL DIRECT TRANSFER message, as shown in Figure 8a.3.1.
- if timer TU5908 is active for the domain:
- ignore the GA-RRC PAGING REQUEST message, and
- continue with the ongoing procedure as if the GA-RRC PAGING REQUEST was not received.
Reference(s)
3GPP TS 44.318 subclause 8a.3.2 |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 84.4.2.2.2 Test purpose | To verify that MS discards the received GA-RRC PAGING REQUEST message (indicating CS domain page) if timer TU5908 is active for the CS domain. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 84.4.2.2.3 Method of test | Initial Conditions
System Simulator:
- 1 GAN cell, default parameters
Mobile Station:
- MS in GA-RRC-IDLE state for CS domain in service of GAN cell
Foreseen Final State of the MS
MS in GA-RRC- IDLE state for CS domain.
Test Procedure
MS is made to initiate GA-RRC connection for CS domain. MS sends GA-RRC REQUEST message and activates timer TU5908. The SS initiates paging procedure by sending GA-RRC PAGING REQUEST message to the MS when TU5908 is active in MS. MS discards the received GA-RRC PAGING REQUEST message. After TU5908 expiry the SS sends GA-RRC PAGING REQUEST to verify that MS in GA-RRC-IDLE state. MS may answer by sending GA-RRC INITIAL DIRECT TRANSFER or re-establish the GA-RRC connection by re-sending GA-RRC REQUEST message.
Specific test parameters
-
Maximum Duration of Test
1 min.
Expected Sequence
Step
Direction
Message
Comment
MS
SS
1
MS
MS is made to initiate GA-RRC connection for CS domain
2
GA-RRC REQUEST
IE 'CN Domain Identity' indicates CS domain
MS activates TU5908 for CS domain
3
GA-RRC PAGING REQUEST
Valid identity of the MS (‘TMSI’/’IMSI’), sent before TU5908 expiry
IE 'CN Domain Identity' indicates CS domain
4
MS
MS discards GA-RRC PAGING REQUEST message
5
SS
SS waits for TU5908 to expire. The MS may resend GA-RRC REQUEST after the expiry of TU5908.
The following steps are executed only if no GA-RRC REQUEST is received from the MS.
6
GA-RRC PAGING REQUEST
Valid identity of the MS (‘TMSI’/’IMSI’)
IE 'CN Domain Identity' indicates CS domain
7
GA-RRC INITIAL DIRECT TRANSFER
IE 'L3 Message' contains Paging Response
IE 'CN Domain Identity' indicates CS domain
MS enters GA-RRC-CONNECTED state for CS domain
8
GA-RRC RELEASE
IE ‘GA-RRC Cause’ = #83
IE 'CN Domain Identity' indicates CS domain
9
GA-RRC RELEASE COMPLETE
IE 'CN Domain Identity' indicates CS domain
MS enters GA-RRC-IDLE state for CS domain |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 84.4.2.3 Paging for CS domain / negative cases / MS receives GA-RRC PAGING REQUEST when in GA-RRC-CONNECTED state | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 84.4.2.3.1 Conformance requirement | If the MS receives a GA-RRC PAGING REQUEST message and the GA-RRC sublayer entity in the MS is in GA-RRC-CONNECTED state for the indicated domain or the MS is in the GA-RC-REGISTERED state but in GERAN/UTRAN mode, the MS shall:
- ignore the GA-RRC PAGING REQUEST message, and
- continue with any ongoing procedure as if the GA-RRC PAGING REQUEST was not received.
Reference(s)
3GPP TS 44.318 subclause 8a.3.3 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.