hash
stringlengths 32
32
| doc_id
stringlengths 5
12
| section
stringlengths 4
1.47k
| content
stringlengths 0
6.67M
|
|---|---|---|---|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
81.2.6.10.1 Conformance requirement
|
When the MS receives the GA-RC DEREGISTER message, it shall:
- if the MS is in the process of PLMN selection;
- ignore the received Register Reject Cause Information Element, and
- proceed as defined in sub-clause 6.2.4.5.
- else extract the Reject Cause information element and act as following depending on the value of the Reject Cause IE:
- 'Network Congestion'
- release all local GAN resources (e.g. MS is in active call over GAN)
- release the TCP connection towards the current GANC and
- release the secure connection towards the GANC-SEGW, as defined in sub-clause 4.5
- create a random value between zero and the received value in IE ‘TU3907 Timer’ and
- add this value to the received value in IE ‘TU3907 Timer’, and use this as the new value for TU3907
- start timer TU3907 according to the new calculated value
Reference(s)
3GPP TS 44.318 sub-clause 6.4.4
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
81.2.6.10.2 Test purpose
|
To verify that the MS changes state to GA-RC DEREGISTERED and starts to try to register again after receiving GA-RC DEREGISTER with cause ‘Network Congestion’.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
81.3 Lower Layer Faults
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
81.3.1 TCP Reset
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
81.3.1.1 TCP Reset, Successful Re-establishment, MS in State GA-CSR DEDICATED
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
81.3.1.1.1 Conformance requirement
|
When MS receives TCP RST after TCP connection failure, it shall attempt to re-establish TCP connection once. After successfully re-establishing TCP connection, the MS shall send GA-RC SYNCHRONIZATION INFORMATION to the GANC to synchronize the state information. If unsuccessful, the MS shall release the related local GA-CSR or GA-PSR resources, and continue as per section 9.5.
Reference(s)
3GPP TS 44.318 sub-clause 6.6.1.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
81.3.1.1.2 Test purpose
|
To verify that the MS ca re-establish the TCP connection after receiving a TCP Reset.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
81.3.1.1.3 Method of test
|
Initial conditions
System Simulator:
- 1 GAN cell, default parameter
Mobile Station:
- MS in state GA-CSR DEDICATED
- The MS has the IP address or the FQDN for the serving GANC
Foreseen final state of the MS
The MS will stay in GA-CSR DEDICATED.
Test procedure
The MS starts in GA-CSR DEDICATED.
The SS sends a TCP RST and the MS re-establish the TCP connection and send the GA-RC SYNCHRONISATION INFORMATION message.
Specific Test Parameters
-
Maximum duration of test
1 min.
Expected sequence
Step
Direction
Message
Comment
MS
SS
1
MS
MS starts in GA-CSR DEDICATED
2
SS
The SS sends TCP RST
3
MS
The MS re-establish the TCP connection
4
GA-RC SYNCHRONIZATION INFORMATION
To serving GANC
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
81.3.1.2 TCP Reset, Unsuccessful Re-establishment, MS in State GA-CSR IDLE
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
81.3.1.2.1 Conformance requirement
|
When MS receives TCP RST after TCP connection failure, it shall attempt to re-establish TCP connection once. After successfully re-establishing TCP connection, the MS shall send GA-RC SYNCHRONIZATION INFORMATION to the GANC to synchronize the state information. If unsuccessful, the MS shall release the related local GA-RC or GA-PSR resources, and continue as per section 9.5.
Reference(s)
3GPP TS 44.318 sub-clause 6.6.1.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
81.3.1.2.2 Test purpose
|
To verify that the MS can re-establish the TCP connection after receiving a TCP Reset.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
81.3.1.2.3 Method of test
|
Initial conditions
System Simulator:
- 1 GAN cell, default parameter
Mobile Station:
- MS in state GA-CSR IDLE
- The MS has the IP address or the FQDN for the serving GANC
Foreseen final state of the MS
The MS will change to GA-RC DEREGISTERED.
Test procedure
The MS starts in GA-CSR IDLE.
The SS sends a TCP RST and the MS tries to re-establish the TCP connection. When that fails it start timer TU3905 and tries to register again when the timer expires.
Specific Test Parameters
-
Maximum duration of test
1 min.
Expected sequence
Step
Direction
Message
Comment
MS
SS
1
MS
MS starts in GA-CSR IDLE
2
SS
The SS sends TCP RST
3
MS
The MS tries to re-establish the TCP connection, the SS doesn’t reply. MS starts timer TU3905
4
MS
Wait for 10 seconds
5
MS
MS sets up secure connection to the SEGW and establishes a TCP connection to the serving GANC using either IP address or FQDN
6
GA-RC REGISTER REQUEST
To serving GANC
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
81.3.1.3 TCP Reset, Successful Re-establishment, MS in State GA-RRC-CONNECTED (CS domain)
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
81.3.1.3.1 Conformance requirement
|
When MS receives TCP RST after TCP connection failure, it shall attempt to re-establish TCP connection once. After successfully re-establishing TCP connection, the MS shall send GA-RC SYNCHRONIZATION INFORMATION to the GANC to synchronize the state information. If unsuccessful, the MS shall release the related local GA-RRC resources, and continue as per section 9.5.
Reference(s)
3GPP TS 44.318 sub-clause 6.6.1.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
81.3.1.3.2 Test purpose
|
To verify that the MS can re-establish the TCP connection after receiving a TCP Reset.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
81.3.1.3.3 Method of test
|
Initial conditions
System Simulator:
- 1 GAN cell, default parameter
Mobile Station:
- MS in state GA-RRC-CONNECTED (CS domain)
- The MS has the IP address or the FQDN for the serving GANC
Foreseen final state of the MS
The MS will stay in GA-RRC-CONNECTED (CS domain).
Test procedure
The MS starts in GA-RRC-CONNECTED (CS domain).
The SS sends a TCP RST and the MS re-establish the TCP connection and send the GA-RC SYNCHRONISATION INFORMATION message.
Specific Test Parameters
-
Maximum duration of test
1 min.
Expected sequence
Step
Direction
Message
Comment
MS
SS
1
MS
MS starts in GA-RRC-CONNECTED (CS domain)
2
SS
The SS sends TCP RST
3
MS
The MS re-establish the TCP connection
4
GA-RC SYNCHRONIZATION INFORMATION
To serving GANC
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
81.3.1.4 TCP Reset, Successful Re-establishment, MS in State GA-RRC-CONNECTED (PS domain)
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
81.3.1.4.1 Conformance requirement
|
When MS receives TCP RST after TCP connection failure, it shall attempt to re-establish TCP connection once. After successfully re-establishing TCP connection, the MS shall send GA-RC SYNCHRONIZATION INFORMATION to the GANC to synchronize the state information. If unsuccessful, the MS shall release the related local GA-RRC resources, and continue as per section 9.5.
Reference(s)
3GPP TS 44.318 sub-clause 6.6.1.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
81.3.1.4.2 Test purpose
|
To verify that the MS can re-establish the TCP connection after receiving a TCP Reset.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
81.3.1.4.3 Method of test
|
Initial conditions
System Simulator:
- 1 GAN cell, default parameter
Mobile Station:
- MS in state GA-RRC-CONNECTED (PS domain)
- The MS has the IP address or the FQDN for the serving GANC
Foreseen final state of the MS
The MS will stay in GA-RRC-CONNECTED (PS domain).
Test procedure
The MS starts in GA-RRC-CONNECTED (PS domain).
The SS sends a TCP RST and the MS re-establish the TCP connection and send the GA-RC SYNCHRONISATION INFORMATION message.
Specific Test Parameters
-
Maximum duration of test
1 min.
Expected sequence
Step
Direction
Message
Comment
MS
SS
1
MS
MS starts in GA-RRC-CONNECTED (PS domain)
2
SS
The SS sends TCP RST
3
MS
The MS re-establish the TCP connection
4
GA-RC SYNCHRONIZATION INFORMATION
To serving GANC
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
81.3.1.5 TCP Reset, Unsuccessful Re-establishment, MS in State GA-RRC-IDLE (CS and PS domains)
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
81.3.1.5.1 Conformance requirement
|
When MS receives TCP RST after TCP connection failure, it shall attempt to re-establish TCP connection once. After successfully re-establishing TCP connection, the MS shall send GA-RC SYNCHRONIZATION INFORMATION to the GANC to synchronize the state information. If unsuccessful, the MS shall release the related local GA-RC or GA-RRC resources, and continue as per section 9.5.
Reference(s)
3GPP TS 44.318 sub-clause 6.6.1.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
81.3.1.5.2 Test purpose
|
To verify that the MS can re-establish the TCP connection after receiving a TCP Reset.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
81.3.1.5.3 Method of test
|
Initial conditions
System Simulator:
- 1 GAN cell, default parameter
Mobile Station:
- MS in state GA-RRC-IDLE (CS and PS domains)
- The MS has the IP address or the FQDN for the serving GANC
Foreseen final state of the MS
The MS will change to GA-RC DEREGISTERED.
Test procedure
The MS starts in GA-RRC-IDLE (CS and PS domains).
The SS sends a TCP RST and the MS tries to re-establish the TCP connection. When that fails it start timer TU3905 and tries to register again when the timer expires.
Specific Test Parameters
-
Maximum duration of test
1 min.
Expected sequence
Step
Direction
Message
Comment
MS
SS
1
MS
MS starts in GA-RRC-IDLE (CS and PS domains)
2
SS
The SS sends TCP RST
3
MS
The MS tries to re-establish the TCP connection, the SS doesn’t reply. MS starts timer TU3905
4
MS
Wait for 10 seconds
5
MS
MS sets up secure connection to the SEGW and establishes a TCP connection to the serving GANC using either IP address or FQDN
6
GA-RC REGISTER REQUEST
To serving GANC
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
81.3.2 Lower Layer Faults, MS is Registered
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
81.3.2.1 IPSec Tunnel Failure, MS in State GA-CSR IDLE
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
81.3.2.1.1 Conformance requirement
|
The handling of lower layer failures in the MS while in the GA-RC-DEREGISTERED state is described in sub-clauses 5.6.2 and 6.2.4.2.
The handling of lower layer failures in the MS while not in the GA-RC-DEREGISTERED state is described below:
For all lower layer failures in the MS (for example related to DNS, IPsec or TCP failures other than RST) except the TCP connection failure specified in section 6.6, the MS shall:
- release the TCP connection towards the current GANC, if established,
- stop timer TU3906,
- release the secure connection towards SEGW of the current GANC, if established, as defined in sub-clause 4.5,
- start timer TU3905, and
- enter GA-RC-DEREGISTERED state.
Reference(s)
3GPP TS 44.318 sub-clause 9.5.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
81.3.2.1.2 Test purpose
|
To verify that the MS tries to register again after a lower layer fault when in state GA-CSR IDLE.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
81.3.2.1.3 Method of test
|
Initial conditions
System Simulator:
- 1 GAN cell, default parameter
Mobile Station:
- MS in state GA-CSR IDLE
- The MS has the IP address or the FQDN for the serving GANC
Foreseen final state of the MS
The MS will change to GA-RC DEREGISTERED.
Test procedure
The MS starts in GA-CSR IDLE.
The SS removes the Ipsec tunnel. When that happens the MS starts timer TU3905 and tries to register again when the timer expires.
Specific Test Parameters
-
Maximum duration of test
1 min.
Expected sequence
Step
Direction
Message
Comment
MS
SS
1
MS
MS starts in GA-CSR IDLE
2
SS
The SS removes the Ipsec tunnel
3
MS
MS starts timer TU3905
4
MS
Wait for 10 seconds
5
MS
MS sets up secure connection to the SEGW and establishes a TCP connection to the serving GANC using either IP address or FQDN
6
GA-RC REGISTER REQUEST
To serving GANC
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
81.3.2.2 TCP Failure, MS in State GA-CSR DEDICATED
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
81.3.2.2.1 Conformance requirement
|
The handling of lower layer failures in the MS while in the GA-RC-DEREGISTERED state is described in sub-clauses 5.6.2 and 6.2.4.2.
The handling of lower layer failures in the MS while not in the GA-RC-DEREGISTERED state is described below:
For all lower layer failures in the MS (for example related to DNS, IPsec or TCP failures other than RST) except the TCP connection failure specified in section 6.6, the MS shall:
- release the TCP connection towards the current GANC, if established,
- stop timer TU3906,
- release the secure connection towards SEGW of the current GANC, if established, as defined in sub-clause 4.5,
- start timer TU3905, and
- enter GA-RC-DEREGISTERED state.
Reference(s)
3GPP TS 44.318 sub-clause 9.5
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
81.3.2.2.2 Test purpose
|
To verify that the MS tries to register again after a lower layer fault when in state GA-CSR DEDICATED.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
81.3.2.2.3 Method of test
|
Initial conditions
System Simulator:
- 1 GAN cell, default parameter
Mobile Station:
- MS in state GA-CSR DEDICATED
- The MS has the IP address or the FQDN for the serving GANC
Foreseen final state of the MS
The MS will change to GA-RC DEREGISTERED.
Test procedure
The MS starts in GA-CSR DEDICATED.
The SS removes the Ipsec tunnel. When that happens the MS starts timer TU3905 and tries to register again when the timer expires.
Specific Test Parameters
-
Maximum duration of test
1 min.
Expected sequence
Step
Direction
Message
Comment
MS
SS
1
MS
MS starts in GA-CSR DEDICATED
2
SS
The SS removes the Ipsec tunnel
3
MS
MS starts timer TU3905
4
MS
Wait for 10 seconds
5
MS
MS sets up secure connection to the SEGW and establishes a TCP connection to the serving GANC using either IP address or FQDN
6
GA-RC REGISTER REQUEST
To serving GANC
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
81.3.2.3 IPSec Tunnel Failure, MS in State GA-RRC-IDLE (CS and PS domains)
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
81.3.2.3.1 Conformance requirement
|
The handling of lower layer failures in the MS while in the GA-RC-DEREGISTERED state is described in sub-clauses 5.6.2 and 6.2.4.2.
The handling of lower layer failures in the MS while not in the GA-RC-DEREGISTERED state is described below:
For all lower layer failures in the MS (for example related to DNS, IPsec or TCP failures other than RST) except the TCP connection failure specified in section 6.6, the MS shall:
- release the TCP connection towards the current GANC, if established,
- stop timer TU3906,
- release the secure connection towards SEGW of the current GANC, if established, as defined in sub-clause 4.5,
- start timer TU3905, and
- enter GA-RC-DEREGISTERED state.
Reference(s)
3GPP TS 44.318 sub-clause 9.5.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
81.3.2.3.2 Test purpose
|
To verify that the MS tries to register again after a lower layer fault when in state GA-RRC-IDLE.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
81.3.2.3.3 Method of test
|
Initial conditions
System Simulator:
- 1 GAN cell, default parameter
Mobile Station:
- MS in state GA-RRC-IDLE (CS and PS domains)
- The MS has the IP address or the FQDN for the serving GANC
Foreseen final state of the MS
The MS will change to GA-RC DEREGISTERED.
Test procedure
The MS starts in GA-RRC-IDLE (CS and PS domains).
The SS removes the IPSec tunnel. When that happens the MS starts timer TU3905 and tries to register again when the timer expires.
Specific Test Parameters
-
Maximum duration of test
1 min.
Expected sequence
Step
Direction
Message
Comment
MS
SS
1
MS
MS starts in GA-RRC-IDLE (CS and PS domains)
2
SS
The SS removes the IPSec tunnel
3
MS
MS starts timer TU3905
4
MS
Wait for 10 seconds
5
MS
MS sets up secure connection to the SEGW and establishes a TCP connection to the serving GANC using either IP address or FQDN
6
GA-RC REGISTER REQUEST
To serving GANC
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
81.3.2.4 TCP Failure, MS in State GA-RRC-CONNECTED (CS domain)
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
81.3.2.4.1 Conformance requirement
|
The handling of lower layer failures in the MS while in the GA-RC-DEREGISTERED state is described in sub-clauses 5.6.2 and 6.2.4.2.
The handling of lower layer failures in the MS while not in the GA-RC-DEREGISTERED state is described below:
For all lower layer failures in the MS (for example related to DNS, IPsec or TCP failures other than RST) except the TCP connection failure specified in section 6.6, the MS shall:
- release the TCP connection towards the current GANC, if established,
- stop timer TU3906,
- release the secure connection towards SEGW of the current GANC, if established, as defined in sub-clause 4.5,
- start timer TU3905, and
- enter GA-RC-DEREGISTERED state.
Reference(s)
3GPP TS 44.318 sub-clause 9.5
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
81.3.2.4.2 Test purpose
|
To verify that the MS tries to register again after a lower layer fault when in state GA-RRC-CONNECTED (CS domain).
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
81.3.2.4.3 Method of test
|
Initial conditions
System Simulator:
- 1 GAN cell, default parameter
Mobile Station:
- MS in state GA-RRC-CONNECTED (CS domain)
- The MS has the IP address or the FQDN for the serving GANC
Foreseen final state of the MS
The MS will change to GA-RC DEREGISTERED.
Test procedure
The MS starts in GA-RRC-CONNECTED (CS domain).
The SS removes the Ipsec tunnel. When that happens the MS starts timer TU3905 and tries to register again when the timer expires.
Specific Test Parameters
-
Maximum duration of test
1 min.
Expected sequence
Step
Direction
Message
Comment
MS
SS
1
MS
MS starts in GA-RRC-CONNECTED (CS domain)
2
SS
The SS removes the IPSec tunnel
3
MS
MS starts timer TU3905
4
MS
Wait for 10 seconds
5
MS
MS sets up secure connection to the SEGW and establishes a TCP connection to the serving GANC using either IP address or FQDN
6
GA-RC REGISTER REQUEST
To serving GANC
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
81.3.2.5 TCP Failure, MS in State GA-RRC-CONNECTED (PS domain)
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
81.3.2.5.1 Conformance requirement
|
The handling of lower layer failures in the MS while in the GA-RC-DEREGISTERED state is described in sub-clauses 5.6.2 and 6.2.4.2.
The handling of lower layer failures in the MS while not in the GA-RC-DEREGISTERED state is described below:
For all lower layer failures in the MS (for example related to DNS, IPsec or TCP failures other than RST) except the TCP connection failure specified in section 6.6, the MS shall:
- release the TCP connection towards the current GANC, if established,
- stop timer TU3906,
- release the secure connection towards SEGW of the current GANC, if established, as defined in sub-clause 4.5,
- start timer TU3905, and
- enter GA-RC-DEREGISTERED state.
Reference(s)
3GPP TS 44.318 sub-clause 9.5
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
81.3.2.5.2 Test purpose
|
To verify that the MS tries to register again after a lower layer fault when in state GA-RRC-CONNECTED (PS domain).
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
81.3.2.5.3 Method of test
|
Initial conditions
System Simulator:
- 1 GAN cell, default parameter
Mobile Station:
- MS in state GA-RRC-CONNECTED (PS domain)
- The MS has the IP address or the FQDN for the serving GANC
Foreseen final state of the MS
The MS will change to GA-RC DEREGISTERED.
Test procedure
The MS starts in GA-RRC-CONNECTED (PS domain).
The SS removes the Ipsec tunnel. When that happens the MS starts timer TU3905 and tries to register again when the timer expires.
Specific Test Parameters
-
Maximum duration of test
1 min.
Expected sequence
Step
Direction
Message
Comment
MS
SS
1
MS
MS starts in GA-RRC-CONNECTED (PS domain)
2
SS
The SS removes the IPSec tunnel
3
MS
MS starts timer TU3905
4
MS
Wait for 10 seconds
5
MS
MS sets up secure connection to the SEGW and establishes a TCP connection to the serving GANC using either IP address or FQDN
6
GA-RC REGISTER REQUEST
To serving GANC
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
82 GAN CS Domain Procedures
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
82.1 GA-CSR connection establishment
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
82.1.1 GA-CSR connection establishment / successful case
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
82.1.1.1 GA-CSR connection establishment, Upper Layer Message Transmission and GA-CRS connection release by GANC
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
82.1.1.1.1 Conformance requirement
|
The GA-CSR connection is a logical connection between the MS and the GANC. It is established when the upper layers in the MS request GA-CSR to enter dedicated mode. The MS initiates GA-CSR connection establishment by sending the GA-CSR REQUEST message to the network. When a successful response is received from the network, GA-CSR replies to the upper layer that it has entered dedicated mode. The upper layers have then the possibility to request transmission of messages to the network. These messages are sent to the network using GA-CSR UPLINK DIRECT TRANSFER messages as defined in sub-clause 7.2.1.
The GA-CSR UPLINK DIRECT TRANSFER message is used for the transfer of upper layer messages from the MS to the GANC while the GA-CSR DOWNLINK DIRECT TRANSFER message is used for the transfer of upper layer messages from the GANC to the MS. The first GA-CSR UPLINK DIRECT TRANSFER message received by the GANC triggers the establishment of the signalling connection to the CN for that MS.
The GANC initiates this procedure to command the MS to release the GA-CSR and any traffic channel resources and instruct the MS to leave GA-CSR-DEDICATED state.
The GA-CSR RELEASE message will include an RR cause indication as follows:
#0: normal release, e.g. at the end of a call.
- #1: unspecified abnormal release.
- #65: if e.g. a handover procedure is stopped because the call has been cleared.
When the MS receives the GA-CSR RELEASE message, it shall:
- transmit a GA-CSR RELEASE COMPLETE message to the GANC and release all GA-CSR and any traffic channel resources,
- Enter GA-CSR-IDLE state.
Reference(s)
3GPP TS 44.318 subclause 7.1 / 7.2 / 7.5.3 / 7.5.4
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
82.1.1.1.2 Test purpose
|
To verify that MS is able to initiate GA-CSR connection establishment between the MS and GANCand to verify that MS is able to communicate with the CN by encapsulating upper layer messages (CC/MM/SS/SMS messages) to GA-CSR UPLINK DIRECT TRANSFER container message and able to receive upper layer messages within GA-CSR DOWNLINK DIRECT TRANSFER container message.
To verify that MS is able to release the GA-CSR connection, able to move into GA-CSR-IDLE state and release all GA-CSR and any traffic channel resources, when the MS receives the GA-CSR RELEASE message from SS.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
82.1.1.1.3 Method of test
|
Initial Conditions
System Simulator:
- 1 GAN cell, default parameters
Mobile Station:
- MS in GA-CSR-IDLE state in service of GAN cell
Foreseen Final State of the MS
MS in GA-CSR-IDLE state.
Test Procedure
The MS is made to initiate a GA-CSR connection establishment. The MS moves into GA-CSR-DEDICATED state when the MS receives the GA-CSR REQUEST ACCEPT message from the SS within timer TU3908 (5 sec.) from sending GA-CSR REQUEST message. SS verifies that MS sends GA-CSR UPLINK DIRECT TRANSFER message within 10s from GA-CSR REQUEST ACCEPT message. The SS answers by sending upper layer message within GA-CSR DOWNLINK DIRECT TRANSFER container message.
The SS sends GA-CSR RELEASE message. The MS enters GA-CSR-IDLE state and transmits a GA-CSR RELEASE COMPLETE to the SS and releases all GA-CSR 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-CSR connection
2
MS
MS checks for access permission based on Access Control Class bits
3
GA-CSR REQUEST
4
GA-CSR REQUEST ACCEPT
5
MS
MS in GA-CSR-DEDICATED state
6
GA-CSR UPLINK DIRECT TRANSFER
Within 10s from GA-CSR REQUEST ACCEPT message
Containing (UL) CC/MM/SS/SMS message
7
GA-CSR DOWNLINK DIRECT TRANSFER
Containing (DL) CC/MM/SS/SMS message
8
GA-CSR RELEASE
IE ‘RR cause’ indicates #0
9
GA-CSR RELEASE COMPLETE
MS enters GA-CSR-IDLE state
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
82.1.2 GA-CSR connection establishment / negative cases
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
82.1.2.1 GA-CSR REQUEST rejected
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
82.1.2.1.1 Conformance requirement
|
3GPP TS 44.318 subclause 7.1.2.2:
If the GANC rejects the GA-CSR connection establishment request, it shall send the GA-CSR REQUEST REJECT message to the MS.
3GPP TS 44.318 subclause 7.1.3.2:
When the MS receives the GA-CSR REQUEST REJECT message, it shall:
- if timer TU3908 is active:
- stop timer TU3908,
- remain in GA-CSR-IDLE state and
- indicate to upper layers that GA-CSR was not able to enter dedicated state
3GPP TS 44.318 subclause 7.3.2:
If the mobile identity in the GA-CSR PAGING REQUEST message matches any of the valid identities of the MS and the MS is in GA-CSR-IDLE state, the MS shall:
- if timer TU3908 is not active and access to the network is allowed;
- send a GA-CSR PAGING RESPONSE message to the GANC and
- enter GA-CSR-DEDICATED state.
Reference(s)
3GPP TS 44.318 subclauses 7.1.2.2 / 7.1.3.2 / 7.3.2
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
82.1.2.1.2 Test purpose
|
To verify that MS will remain in GA-CSR-IDLE state when MS receives the GA-CSR REQUEST REJECT message.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
82.1.2.1.3 Method of test
|
Initial Conditions
System Simulator:
- 1 GAN cell, default parameters
Mobile Station:
- MS in GA-CSR-IDLE state in service of GAN cell
Foreseen Final State of the MS
MS in GA-CSR- IDLE state.
Test Procedure
The MS is made to initiate a GA-CSR connection establishment. SS sends the GA-CSR REQUEST REJECT message to the MS. MS is not able to enter GA-CSR-DEDICATED state. The SS sends GA-CSR PAGING REQUEST to verify that MS in GA-CSR-IDLE state. MS answers by sending GA-CSR 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-CSR connection
2
MS
MS checks for access permission based on Access Control Class bits
3
GA-CSR REQUEST
TU3908 is started
4
GA-CSR REQUEST REJECT
The SS sends GA-CSR REQUEST REJECT before the expiry of TU3908.
5
MS
MS in GA-CSR-IDLE state
6
GA-CSR PAGING REQUEST
Valid identity of the MS (‘TMSI’/’IMSI’)
7
GA-CSR PAGING RESPONSE
MS enters GA-CSR-DEDICATED state
8
GA-CSR RELEASE
IE ‘RR cause’ indicates #0
9
GA-CSR RELEASE COMPLETE
MS enters GA-CSR-IDLE state
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
82.1.2.2 MS receives GA-CSR REQUEST ACCEPT message after TU3908 expiry
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
82.1.2.2.1 Conformance requirement
|
If the GANC accepts the GA-CSR connection establishment request, it shall send the GA-CSR REQUEST ACCEPT message to the MS.
When the MS receives the GA-CSR REQUEST ACCEPT message, it shall:
- if timer TU3908 is active:
- stop timer TU3908,
- move into GA-CSR-DEDICATED state,
- indicate to upper layers that GA-CSR has entered dedicated state and
- send the initial GA-CSR UPLINK DIRECT TRANSFER message to the network
- if timer TU3908 is not active:
- ignore the GA-CSR REQUEST ACCEPT message and
- continue with any ongoing procedure as if the GA-CSR REQUEST ACCEPT message was not received
- If timer TU3908 expires in the MS, the MS shall remain in GA-CSR-IDLE state and indicate to upper layers that GA-CSR was not able to enter dedicated state
If the mobile identity in the GA-CSR PAGING REQUEST message matches any of the valid identities of the MS and the MS is in GA-CSR-IDLE state, the MS shall:
- if timer TU3908 is not active and access to the network is allowed;
- send a GA-CSR PAGING RESPONSE message to the GANC and
- enter GA-CSR-DEDICATED state.
- if timer TU3908 is active;
- discard the received GA-CSR PAGING REQUEST message.
Reference(s)
3GPP TS 44.318 subclauses 7.1.2.1 / 7.1.3.1 / 7.1.4.1 / 7.3.2
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
82.1.2.2.2 Test purpose
|
To verify that MS will remain in GA-CSR IDLE state if TU3908 expires before MS receives the GA-CSR REQUEST ACCEPT message.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
82.1.2.2.3 Method of test
|
Initial Conditions
System Simulator:
- 1 GAN cell, default parameters
Mobile Station:
- MS in GA-CSR-IDLE state in service of GAN cell
Foreseen Final State of the MS
MS in GA-CSR- IDLE state.
Test Procedure
The MS is made to initiate a GA-CSR connection establishment. MS receives the GA-CSR REQUEST ACCEPT message from the SS after timer TU3908 (5 sec.) expires. MS remains in GA-CSR IDLE state. The MS may send GA-CSR-REQUEST message due to upper layer requesting to restart the higher layer procedure which verifies that MS has been in GA-CSR-IDLE state. If GA-CSR-REQUEST message is not received, the SS sends GA-CSR PAGING REQUEST to verify that MS in GA-CSR-IDLE state. MS answers by sending GA-CSR 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-CSR connection
2
MS
MS checks for access permission based on Access Control Class bits
3
GA-CSR REQUEST
4
SS
SS waits 5 seconds after SS has received the GA-CSR REQUEST message
5
MS
TU3908 expires
6
GA-CSR REQUEST ACCEPT
7
MS
MS ignores the GA-CSR REQUEST ACCEPT message and remains in GA-CSR-IDLE state
7a (optional)
GA-CSR REQUEST
MS may send GA-CSR-REQUEST message due to upper layer restarting the higher layer procedure. This verifies that the MS has been in GA-CSR-IDLE state.
8 (conditional)
GA-CSR PAGING REQUEST
Valid identity of the MS (‘TMSI’/’IMSI’)
9 (conditional)
GA-CSR PAGING RESPONSE
MS enters GA-CSR DEDICATED state
10 (conditional)
GA-CSR RELEASE
IE ‘RR cause’ indicates #0
11 (conditional)
GA-CSR RELEASE COMPLETE
MS enters GA-CSR-IDLE state
NOTE: Steps 8-11 are not applicable If GA-CSR-REQUEST message is received in step 7a
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
82.2 Upper layer message transmission
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
82.2.1 Upper layer message transmission / successful cases
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
82.2.1.1 Void
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
82.2.2 Upper layer message transmission / negative cases
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
82.2.2.1 MS receives GA-CSR DOWNLINK DIRECT TRANSFER message when not in GA-CSR-DEDICATED state
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
82.2.2.1.1 Conformance requirement
|
If the MS receives a GA-CSR DOWNLINK DIRECT TRANSFER message and MS is not in GA-CSR-DEDICATED state, the MS shall:
- ignore the contents of the GA-CSR DOWNLINK DIRECT TRANSFER message;
- transmit a GA-CSR STATUS message as follows:
- set the IE "RR 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-CSR DOWNLINK DIRECT TRANSFER message was not received.
Reference(s)
3GPP TS 44.318 subclause 7.2.4.1
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
82.2.2.1.2 Test purpose
|
To verify that MS ignores the contents of the GA-CSR DOWNLINK DIRECT TRANSFER message if MS is not in GA-CSR-DEDICATED state and to be able to send GA-CSR STATUS message to the SS.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
82.2.2.1.3 Method of test
|
Initial Conditions
System Simulator:
- 1 GAN cell, default parameters
Mobile Station:
- MS in GA-CSR-IDLE state in service of GAN cell
Foreseen Final State of the MS
MS in GA-CSR-IDLE state in service of GAN cell
Test Procedure
MS is in GA-CSR-IDLE state in service of GAN cell. SS sends GA-CSR DOWNLINK DIRECT TRANSFER message containing upper layer message. MS ignores the contents of the message and sends GA-CSR STATUS message to the SS with IE ‘RR 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-CSR-IDLE state
2
GA-CSR DOWNLINK DIRECT TRANSFER
Containing (DL) CC/MM/SS/SMS message
3
GA-CSR STATUS
RR Cause: ‘Message type not compatible with protocol state’
PDU in Error: ‘<received (DL) message>’
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
82.3 Paging for CS domain
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
82.3.1 Paging for CS domain / successful case
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
82.3.1.1 Paging for CS domain
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
82.3.1.1.1 Conformance requirement
|
3GPP TS 44.318 subclause 7.3.1:
The GANC initiates this procedure when it receives a PAGING REQUEST message over the A-interface or a Paging CS over the Gb-interface. The MS to be paged is identified by the identity received in the request from the CN. If the request includes the TMSI then the GANC should include the TMSI as the mobile identity else it should include the IMSI received in the request.
3GPP TS 44.318 subclause 7.3.2:
If the mobile identity in the GA-CSR PAGING REQUEST message matches any of the valid identities of the MS and the MS is in GA-CSR-IDLE state, the MS shall:
- if timer TU3908 is not active and access to the network is allowed;
- send a GA-CSR PAGING RESPONSE to the GANC and
- enter GA-CSR-DEDICATED state.
3GPP TS 44.318 subclause 7.3.4:
If the MS receives a GA-CSR 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-CSR PAGING REQUEST message
- continue with any ongoing procedure as if the GA-CSR PAGING REQUEST message was not received.
Reference(s)
3GPP TS 44.318 subclauses 7.3.1 / 7.3.2 / 7.3.4
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
82.3.1.1.2 Test purpose
|
To verify that MS ignores the GA-CSR PAGING REQUEST and continues with any ongoing procedure, if received GA-CSR PAGING REQUEST doesn’t contain valid identity.
To verify that MS is able send a GA-CSR PAGING RESPONSE to the SS and enter GA-CSR-DEDICATED state when MS receives GA-CSR PAGING REQUEST with valid identities of the MS.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
82.3.1.1.3 Method of test
|
Initial Conditions
System Simulator:
- 1 GAN cell, default parameters
Mobile Station:
- MS in GA-CSR-IDLE state in service of GAN cell
Foreseen Final State of the MS
MS in GA-CSR-IDLE state in service of GAN cell Test Procedure
The SS initiates paging procedure by sending GA-CSR PAGING REQUEST message with not matching identity to the MS. MS ignores the GA-CSR PAGING REQUEST and continues with any ongoing procedure as if the GA-CSR PAGING REQUEST was not received. After 10s the SS sends GA-CSR PAGING REQUEST to verify that MS in GA-CSR-IDLE state. MS answers by sending GA-CSR PAGING RESPONSE.
Specific test parameters
-
Maximum Duration of Test
1 min.
Expected Sequence
Step
Direction
Message
Comment
MS
SS
1
GA-CSR PAGING REQUEST
With not matching identity
2
MS
MS ignores GA-CSR PAGING REQUEST message
3
SS
SS waits 10s for response
4
GA-CSR PAGING REQUEST
Valid identity of the MS (‘TMSI’/’IMSI’)
5
GA-CSR PAGING RESPONSE
MS enters GA-CSR-DEDICATED state
6
GA-CSR RELEASE
IE ‘RR cause’ = #0
7
GA-CSR RELEASE COMPLETE
MS enters GA-CSR-IDLE state
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
82.3.2 Paging for CS domain / negative cases
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
82.3.2.1 Void
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
82.3.2.2 MS receives GA-CSR PAGING REQUEST when TU3908 is active
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
82.3.2.2.1 Conformance requirement
|
If the mobile identity in the GA-CSR PAGING REQUEST message matches any of the valid identities of the MS and the MS is in GA-CSR-IDLE state, the MS shall:
- if timer TU3908 is not active and access to the network is allowed;
- send a GA-CSR PAGING RESPONSE message to the GANC and
- enter GA-CSR-DEDICATED state.
- if timer TU3908 is active;
- discard the received GA-CSR PAGING REQUEST message
Reference(s)
3GPP TS 44.318 subclause 7.3.2
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
82.3.2.2.2 Test purpose
|
To verify that MS discards the received GA-CSR PAGING REQUEST message if timer TU3908 is active.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
82.3.2.2.3 Method of test
|
Initial Conditions
System Simulator:
- 1 GAN cell, default parameters
Mobile Station:
- MS in GA-CSR-IDLE state in service of GAN cell
Foreseen Final State of the MS
MS in GA-CSR- IDLE state.
Test Procedure
MS is made to initiate GA-CSR connection. MS sends GA-CSR REQUEST message and activates timer TU3908. The SS initiates paging procedure by sending GA-CSR PAGING REQUEST message to the MS when TU3908 is active in MS. MS discards the received GA-CSR PAGING REQUEST message. After TU3908 expiry the SS sends GA-CSR PAGING REQUEST to verify that MS in GA-CSR-IDLE state. MS may answer by sending GA-CSR PAGING RESPONSE or re-establish the GA-CSR connection by re-sending GA-CSR 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-CSR connection
2
GA-CSR REQUEST
MS activates TU3908
3
GA-CSR PAGING REQUEST
Valid identity of the MS (‘TMSI’/’IMSI’), sent before TU3908 expiry
4
MS
MS discards GA-CSR PAGING REQUEST message
5
SS
SS waits for TU3908 to expire. The MS may resend GA-CSR REQUEST after the expiry of TU3908.
The following steps are executed only if no GA-CSR REQUEST is received from the MS.
6
GA-CSR PAGING REQUEST
Valid identity of the MS (‘TMSI’/’IMSI’)
7
GA-CSR PAGING RESPONSE
MS enters GA-CSR-DEDICATED state
8
GA-CSR RELEASE
IE ‘RR cause’ indicates #0
9
GA-CSR RELEASE COMPLETE
MS enters GA-CSR-IDLE state
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
82.3.2.3 MS receives GA-CSR PAGING REQUEST when in GA-CSR DEDICATED state
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
82.3.2.3.1 Conformance requirement
|
If the MS receives a GA-CSR PAGING REQUEST message and MS is in GA-CSR-DEDICATED state or GA-RC-REGISTERED state, the MS shall:
- ignore the GA-CSR PAGING REQUEST message
- continue with any ongoing procedure as if the GA-CSR PAGING REQUEST was not received.
Reference(s)
3GPP TS 44.318 subclause 7.3.4
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
82.3.2.3.2 Test purpose
|
To verify that MS ignores the GA-CSR PAGING REQUEST and continues with any ongoing procedure as if the GA-CSR PAGING REQUEST was not received, if MS receives GA-CSR PAGING REQUEST when MS is in GA-CSR-DEDICATED state.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
82.3.2.3.3 Method of test
|
Initial Conditions
System Simulator:
- 1 GAN cell, default parameters
Mobile Station:
- MS in GA-CSR-DEDICATED state in service of GAN cell.
Foreseen Final State of the MS
MS in GA-CSR-IDLE state in service of GAN cell.
Test Procedure
The MS is in GA-CSR-DEDICATED state in service of GAN cell. The SS initiates paging procedure by sending GA-CSR PAGING REQUEST message to the MS. The MS ignores the GA-CSR PAGING REQUEST and continues with any ongoing procedure as if the GA-CSR PAGING REQUEST was not received. After 10s the SS sends GA-CSR RELEASE to verify that MS in GA-CSR-DEDICATED state. MS answers by sending GA-CSR RELEASE COMPLETE.
Specific test parameters
-
Maximum Duration of Test
1 min.
Expected Sequence
Step
Direction
Message
Comment
MS
SS
1
MS
MS in GA-CSR-DEDICATED state with ongoing procedure
2
GA-CSR PAGING REQUEST
Valid identity of the MS (‘TMSI’/’IMSI’)
3
MS
MS ignores the GA-CSR PAGING REQUEST and continues with ongoing procedure
4
SS
SS waits 10s for response
5
GA-CSR RELEASE
IE ‘RR cause’
6
GA-CSR RELEASE COMPLETE
MS enters GA-CSR-IDLE state
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
82.3.2.4 MS receives GA-CSR PAGING REQUEST when in GA-RC REGISTERED state
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
82.3.2.4.1 Conformance requirement
|
If the MS receives a GA-CSR PAGING REQUEST message and MS is in GA-CSR-DEDICATED state or GA-RC-REGISTERED state, the MS shall:
- ignore the GA-CSR PAGING REQUEST message
- continue with any ongoing procedure as if the GA-CSR PAGING REQUEST was not received.
Reference(s)
3GPP TS 44.318 subclause 7.3.4
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
82.3.2.4.2 Test purpose
|
To verify that MS ignores the GA-CSR PAGING REQUEST and continues with any ongoing procedure as if the GA-CSR PAGING REQUEST was not received, if MS receives GA-CSR PAGING REQUEST when MS is in GA-RC-REGISTERED state.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
82.3.2.4.3 Method of test
|
Initial Conditions
System Simulator:
- 2 cells: GERAN cell & GAN cell
- 1 GERAN cell, default parameters
- 1 GAN cell, default parameters
Mobile Station:
- MS in GERAN mode camped on a GERAN cell, voice call activated and in GA-RC-REGISTERED state
Foreseen Final State of the MS
MS in GA-CSR- IDLE state.
Test Procedure
MS is camped on a GERAN cell, voice call activated and in GA-RC-REGISTERED state. The SS initiates paging procedure by sending GA-CSR PAGING REQUEST message to the MS. The MS ignores the GA-CSR PAGING REQUEST and continues with any ongoing procedure as if the GA-CSR PAGING REQUEST was not received. After 10s, the voice call is deactivated to switch the serving RR entity to GA-CSR. The SS waits 30 seconds to ensure that the MS enters the GA-CSR-IDLE state and sends GA-CSR PAGING REQUEST to verify that MS in GA-CSR-IDLE state. MS answers by sending GA-CSR PAGING RESPONSE.
Specific test parameters
-
Maximum Duration of Test
1 min.
Expected Sequence
Step
Direction
Message
Comment
MS
SS
1
MS
MS is camped on a GERAN cell, voice call activated and in GA-RC-REGISTERED state
2
GA-CSR PAGING REQUEST
Valid identity of the MS (‘TMSI’/’IMSI’)
3
MS
MS ignores the GA-CSR PAGING REQUEST and continues with ongoing procedure
4
SS
SS waits 10s for response
5
MS
The voice call is deactivated to switch the serving RR entity to GA-CSR-IDLE state.
6
SS
Wait 30 seconds to ensure that the MS enters GA-CSR-IDLE state.
67
GA-CSR PAGING REQUEST
Valid identity of the MS (‘TMSI’/’IMSI’)
78
GA-CSR PAGING RESPONSE
MS enters GA-CSR-DEDICATED state
89
GA-CSR RELEASE
IE ‘RR cause’ indicates #0
910
GA-CSR RELEASE COMPLETE
MS enters GA-CSR-IDLE state
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
82.4 Traffic Channel assignment
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
82.4.1 Traffic Channel assignment / successful cases
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
82.4.1.1 Traffic Channel assignment
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
82.4.1.1 Traffic Channel assignment and Release
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
82.4.1.1.1 Conformance requirement
|
3GPP TS 44.318 subclause 7.4.2:
The MS shall act on the received GA-CSR ACTIVATE CHANNEL message when in GA-CSR-DEDICATED state as follows:
- Code and decode the CS payload samples according to the IE "Channel Mode";
- Use the value indicated by the IE "Sample Size" as the minimum sampling size for the coding and decoding of the CS payload samples, if the MS is not able to use the indicated value. If AMR is used with FEC by sending redundant frames, the sample size is defined as the size of the new speech sample in each RTP packet, not including any redundant speech sample.
- Configure the uplink CS payload stream to be transmitted to the UDP port identified by the IE "UDP Port";
- Configure the uplink CS payload stream to be transmitted to the IP address identified by the IE "IP address";
- If received, use the configuration included in the IE ‘Multi-rate Configuration’ for the CS payload stream;
- If received, use the configuration included in the IE "RTP Redundancy Configuration" for the CS payload stream. The redundancy policy is defined for each of the AMR modes to use. The level of redundancy can span from no redundancy to double redundancy. In the same active codec set, a lower codec mode shall not be associated with a lower redundancy level then a higher codec mode. For example, the highest mode in the set is used with no redundancy, the next lower with single redundancy and rest of the modes with double redundancy;
- If received, use the Payload Type included in the IE ‘Payload Type’ for the PT field in the RTP header for the CS downlink and uplink payload streams;
- On successful activation of the channel, the MS shall:
- Transmit a GA-CSR ACTIVATE CHANNEL ACK message and include the UDP port number in the IE ‘UDP Port" for the downlink CS payload stream to be used by the GANC.
- Include the selected RTP sample size, to be used uplink and downlink, in the IE Sample Size.
- if the IE ‘RTCP UDP Port’ was received in the GA-CSR ACTIVATE CHANNEL message and the MS is capable of supporting RTCP, activate the uplink RTCP stream and include the IE ‘RTCP UDP Port’ for the downlink RTCP stream to be used by the GANC.
3GPP TS 44.318 subclause 7.4.4:
The RTP channel is available for use by upper layers. To enable uplink quality measurements in the GANC, the MS shall send at least one RTP frame each 480 ms. The AMR payload Table of Contents shall indicate NO_DATA if there is no speech or SID frames to send.
3GPP TS 44.318 subclause 7.5.1:
If the MS needs to release the GA-CSR connection and signalling connection to the core network, it shall send the GA-CSR CLEAR REQUEST message to the GANC. The MS shall include the ‘RR Cause’ IE.
Reference(s)
3GPP TS 44.318 subclauses 7.4.2 / 7.4.4/ 7.5.1
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
82.4.1.1.2 Test purpose
|
To verify that MS is able to establish a GAN traffic channel.
The MS initiates the release the GA-CSR connection by sending GA-CSR CLEAR REQUEST to the SS. The MS enters GA-CSR-IDLE state and releases all GA-CSR and any traffic channel resources.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
82.4.1.1.3 Method of test
|
Initial Conditions
System Simulator:
- 1 GAN cell, default parameters
Mobile Station:
- MS in GA-CSR-DEDICATED state in service of GAN cell and a voice call is ongoing.
Foreseen Final State of the MS
MS in GA-CSR-IDLE state in service of GAN cell.
Test Procedure
A voice call is ongoing.The SS configures a traffic channel by transmitting GA-CSR ACTIVATE CHANNEL to the MS. MS responses by transmitting a GA-CSR ACTIVATE CHANNEL ACK with the IE ‘UDP Port’. Then the SS configures itself for transmission of RTP packets to the MS to the indicated UDP port and transmits a GA-CSR ACTIVATE CHANNEL COMPLETE message to the MS. MS and SS sends at least one RTP frame each 480 ms. The SS releases the call by sending GA-CSR DL DIRECT TRANSFER message (Release) and receiving GA-CSR UL DIRECT TRANSFER (Release Complete) message. Therefore, the MS will send GA-CSR CLEAR REQUEST to release CSR connection.
Specific test parameters
-
Maximum Duration of Test
1 min.
Expected Sequence
Step
Direction
Message
Comment
MS
SS
1
MS
MS in GA-CSR-DEDICATED state, voice call is ongoing.
2
GA-CSR ACTIVATE CHANNEL
IE ‘Channel Mode’, IE ‘Sample Size’, IE ‘UDP Port’, IE ‘IP address’, optional IE ‘Multi-rate Configuration’, optional IE ‘RTP Redundancy Configuration ‘, optional IE ‘Payload Type’.
3
GA-CSR ACTIVATE CHANNEL ACK
IE ‘UDP Port’, optional IE ‘RTCP UDP Port’
4
GA-CSR ACTIVATE CHANNEL COMPLETE
5
Verify that the MS sends at least one RTP frame
6
GA-CSR DL DIRECT TRANSFER (Release)
7
GA-CSR UL DIRECT TRANSFER (Release Complete)
Eventual CC L3 messages are ignored.
8
GA-CSR CLEAR REQUEST
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
82.4.2 Traffic Channel assignment / negative cases
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
82.4.2.1 MS fails to establish the traffic channel
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
82.4.2.1.1 Conformance requirement
|
If the MS fails to establish the channel indicated in the GA-CSR ACTIVATE CHANNEL the MS shall:
- transmit a GA-CSR ACTIVATE CHANNEL FAILURE message
- act as if the GA-CSR ACTIVATE CHANNEL message was not received.
Reference(s)
3GPP TS 44.318 subclause 7.4.5
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
82.4.2.1.2 Test purpose
|
To verify that if MS fails to establish the traffic channel, it transmits a GA-CSR ACTIVATE CHANNEL FAILURE and act as if the GA-CSR ACTIVATE CHANNEL was not received.
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.