82 GAN CS Domain Procedures

3GPP51.010-1Mobile Station (MS) conformance specificationPart 1: Conformance specificationTS

82.1 GA-CSR connection establishment

82.1.1 GA-CSR connection establishment / successful case

82.1.1.1 GA-CSR connection establishment, Upper Layer Message Transmission and GA-CRS connection release by GANC

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

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.

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

82.1.2 GA-CSR connection establishment / negative cases

82.1.2.1 GA-CSR REQUEST rejected

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

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.

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

82.1.2.2 MS receives GA-CSR REQUEST ACCEPT message after TU3908 expiry

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

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.

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

82.2 Upper layer message transmission

82.2.1 Upper layer message transmission / successful cases

82.2.1.1 Void

82.2.2 Upper layer message transmission / negative cases

82.2.2.1 MS receives GA-CSR DOWNLINK DIRECT TRANSFER message when not in GA-CSR-DEDICATED state

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

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.

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>’

82.3 Paging for CS domain

82.3.1 Paging for CS domain / successful case

82.3.1.1 Paging for CS domain

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

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.

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

82.3.2 Paging for CS domain / negative cases

82.3.2.1 Void

82.3.2.2 MS receives GA-CSR PAGING REQUEST when TU3908 is active

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

82.3.2.2.2 Test purpose

To verify that MS discards the received GA-CSR PAGING REQUEST message if timer TU3908 is active.

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

82.3.2.3 MS receives GA-CSR PAGING REQUEST when in GA-CSR DEDICATED state

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

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.

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

82.3.2.4 MS receives GA-CSR PAGING REQUEST when in GA-RC REGISTERED state

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

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.

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

82.4 Traffic Channel assignment

82.4.1 Traffic Channel assignment / successful cases

82.4.1.1 Traffic Channel assignment

82.4.1.1 Traffic Channel assignment and Release

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

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.

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

82.4.2 Traffic Channel assignment / negative cases

82.4.2.1 MS fails to establish the traffic channel

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

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.

82.4.2.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 corrupted GA-CSR ACTIVATE CHANNEL to the MS. In the corrupted GA-CSR ACTIVATE CHANNEL message “Sample Size” octet 3 is set to “1” (1ms), which is a undefined value.

MS fails to establish the traffic channel and transmits a GA-CSR ACTIVATE CHANNEL FAILURE and acts as if the GA-CSR ACTIVATE CHANNEL was not received.

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

This message has non-supportive configuration, with a “Sample Size” octet 3 set to “1”

3

MS

MS fails to establish the traffic channel

4

GA-CSR ACTIVATE CHANNEL FAILURE

IE ‘FAILURE message identity’

5

GA-CSR RELEASE

IE ‘RR cause’ indicates #0

6

GA-CSR RELEASE COMPLETE

MS enters GA-CSR-IDLE state

82.5 Release of GA-CSR

82.5.1 Release of GA-CSR

82.5.1.1 Void

82.5.1.2 Void

82.6 Classmark Indication

82.6.1 Classmark Indication Procedure

82.6.1.1 Classmark Indication, Initiation of Classmark Interrogation by MS

82.6.1.1.1 Conformance requirement

On receipt of the GA-CSR CLASSMARK ENQUIRY message or in case of "early classmark sending" procedure based on the system information indication received in GA-RC REGISTER ACCEPT message, the mobile station sends a GA-CSR CLASSMARK CHANGE message to the GANC.

The MS shall include the IE "Mobile Classmark 2" in the GA-CSR CLASSMARK CHANGE. It may also contain a IE "Mobile Classmark 3" depending on the MS capabilities.

In addition a MS supporting UTRAN sends a GA-CSR UTRAN CLASSMARK CHANGE message.

The Classmark Enquiry Mask information element in the GA-CSR CLASSMARK ENQUIRY message indicates the type of request. If the Classmark Enquiry Mask information element is not included in the GA-CSR CLASSMARK ENQUIRY message, this indicates a request for GA-CSR CLASSMARK CHANGE message.

Reference(s)

3GPP TS 44.318 sub-clause 7.6.2

82.6.1.1.2 Test purpose

To verify that the MS replies the GA-CSR CLASSMARK ENQUIRY correctly.

82.6.1.1.3 Method of test

Initial conditions

System Simulator:

– 1 GAN cell, default parameter

Mobile Station:

– MS in state GA-CSR-DEDICATED

Foreseen final state of the MS

MS in GA-CSR- IDLE state.

Test procedure

The SS sends the GA-CSR CLASSMARK ENQUIRY message. The MS replies with the GA-CSR CLASMARK CHANGE message.

Specific Test Parameters

Maximum duration of test

1 min.

Reference(s)Expected sequence

Step

Direction

Message

Comment

MS

SS

1

GA-CSR CLASSMARK ENQUIRY

The Classmark Enquiry Mask information element is not included

2

GA-CSR CLASSMARK CHANGE

 

3

GA-CSR RELEASE

IE ‘RR cause’ indicates #0

4

GA-CSR RELEASE COMPLETE

MS enters GA-CSR-IDLE state

82.7 Handover to GAN

82.7.1 Handover to GAN / successful cases

82.7.1.1 Handover from GERAN to GAN

82.7.1.1.1 Conformance requirement

3GPP TS 44.318 subclause 7.7.1:

The procedure is initiated when the source radio access technology (e.g. GERAN) orders the MS to make handover to GAN.

The procedure is applicable in GA-RC REGISTERED state provided the conditions described in Annex C: "(Source-RAT) Measurement Report for Handover and Cell Change Order to GAN" are met.

The handover order in the source radio access technology mode is sent via the (RR) HANDOVER COMMAND message. If the ARFCN and BSIC parameters included in the Cell Description IE in the (RR) HANDOVER COMMAND message (specified in [12]) match those of the GAN cell, the MS shall:

– send a GA-CSR HANDOVER ACCESS message to the network including the complete (RR) HANDOVER COMMAND message in the Handover To GAN Command IE and enter GA-CSR-DEDICATED state;

NOTE: sending the complete (RR) HANDOVER COMMAND message in the Handover To GAN Command IE instead of the Handover Reference IE allows for more than 256 concurrent handover requests

– if non-signalling mode is indicated in Channel Mode IE, the MS shall:

– start timer TU3920;

3GPP TS 44.318 subclause 7.7.3:

– If the traffic channel assignment was successfully completed within timer TU3920, the MS shall:

– stop timer TU3920;

– send a GA-CSR HANDOVER COMPLETE message to the network;

– switch to GAN mode i.e. attach the GA-RR entity to the RR-SAP;

In addition the MS shall send upper layer messages for which LAPDm has not yet received acknowledgement from the network to the network using the GA-RR entity.

Reference(s)

3GPP TS 44.318 subclause 7.7.1 / 7.7.3

82.7.1.1.2 Test purpose

To verify that MS completes the handover procedure from GERAN to GAN successfully.

82.7.1.1.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 in service of 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

The MS is in GERAN mode in service of GERAN cell, voice call activated. MS sends MEASUREMENT REPORT with GAN-ARFCN within cell info list to GERAN cell and MS has not detected GSM neighbour cell matching the {GAN-ARFCN, GAN-BSIC}couple. SS sends (RR) HANDOVER COMMAND with ARFCN and BSIC in ‘Cell Description’ IE matched of the GAN cell. MS sends a GA-CSR HANDOVER ACCESS message to the GAN network with the complete (RR) HANDOVER COMMAND message in the ‘Handover To GAN Command’ IE and enters GA-CSR-DEDICATED state. MS establishes GAN traffic channel with SS and MS sends GA-CSR HANDOVER COMPLETE message to the SS.

Specific test parameters

Maximum Duration of Test

1 min.

Expected Sequence

Step

Direction

Message

Comment

MS

SS

1

MS in service voice call activated on GERAN cell

2

MEASUREMENT REPORT

Sent to GERAN cell with GAN-ARCFN within cell info list

3

RR HANDOVER COMMAND

Sent on GERAN cell with GAN cell ARFCN and BSIC and Channel Mode indicating speech.

4

GA-CSR HANDOVER ACCESS

Sent to GAN cell, with IE ‘Handover To GAN Command’, MS enters GA-CSR-DEDICATED state

5

GAN Traffic Channel assignment procedure (steps 5-10)

6

GA-CSR ACTIVATE CHANNEL

IE ‘Channel Mode’, IE ‘Sample Size’, IE ‘UDP Port’, IE ‘IP address’, optional IE ‘Multi-rate Configuration’, optional IE ‘Payload Type’.

7

GA-CSR ACTIVATE CHANNEL ACK

IE ‘UDP Port’

8

GA-CSR ACTIVATE CHANNEL COMPLETE

Optional IE ‘RTCP UDP Port’

9

RTP frame each 480 ms

To enable quality measurements

10

GAN Traffic Channel assignment procedure ready

11

GA-CSR HANDOVER COMPLETE

Sent to GAN cell, voice call ongoing on GAN cell

12

GA-CSR RELEASE

IE ‘RR cause’ indicates #0

13

GA-CSR RELEASE COMPLETE

MS enters GA-CSR-IDLE state

82.7.1.2 Handover from GERAN to GAN signalling case

82.7.1.2.1 Conformance requirement

The procedure is initiated when the source radio access technology (e.g. GERAN) orders the MS to make handover to GAN.

The procedure is applicable in GA-RC REGISTERED state provided the conditions described in Annex C: "(Source-RAT) Measurement Report for Handover and Cell Change Order to GAN" are met.

The handover order in the source radio access technology mode is sent via the (RR) HANDOVER COMMAND message. If the ARFCN and BSIC parameters included in the Cell Description IE in the (RR) HANDOVER COMMAND message (specified in [12]) match those of the GAN cell, the MS shall:

– send a GA-CSR HANDOVER ACCESS message to the network including the complete (RR) HANDOVER COMMAND message in the Handover To GAN Command IE and enter GA-CSR-DEDICATED state;

NOTE: sending the complete (RR) HANDOVER COMMAND message in the Handover To GAN Command IE instead of the Handover Reference IE allows for more than 256 concurrent handover requests

– if non-signalling mode is indicated in Channel Mode IE, the MS shall:

– start timer TU3920;

– otherwise, the MS shall:

– immediately send a GA-CSR HANDOVER COMPLETE message to the network;

– switch to GAN mode i.e. attach the GA-RR entity to the RR-SAP;.

Reference(s)

3GPP TS 44.318 subclauses 7.7.1

82.7.1.2.2 Test purpose

To verify that MS completes the handover signalling procedure from GERAN to GAN successfully.

82.7.1.2.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 in service of GERAN cell, in GA-CSR-REGISTERED state

Foreseen Final State of the MS

MS in GA-CSR-IDLE state.Test Procedure

The MS is in GERAN mode in service of GERAN cell. MS sends MEASUREMENT REPORT with GAN-ARFCN within cell info list to GERAN cell and MS has not detected GSM neighbour cell matching the {GAN-ARFCN, GAN-BSIC} couple. SS sends (RR) HANDOVER COMMAND with ARFCN and BSIC in ‘Cell Description’ IE matched of the GAN cell. MS sends a GA-CSR HANDOVER ACCESS message to the GAN network with the complete (RR) HANDOVER COMMAND message in the ‘Handover To GAN Command’ IE and enters GA-CSR DEDICATED state. MS immediately sends GA-CSR HANDOVER COMPLETE message to the SS and switches to GAN mode i.e. attaches the GAN-RR entity to the RR-SAP.

Specific test parameters

Maximum Duration of Test

1 min.

Expected Sequence

Step

Direction

Message

Comment

MS

SS

1

MS in service on GERAN cell

2

MEASUREMENT REPORT

Sent to GERAN cell with GAN-ARCFN within cell info list

3

RR HANDOVER COMMAND

Sent on GERAN cell with GAN cell ARFCN and BSIC and Channel Mode indicating signalling only.

4

GA-CSR HANDOVER ACCESS

Sent to GAN cell, with IE ‘Handover To GAN Command’, MS enters GA-CSR DEDICATED state

5

GA-CSR HANDOVER COMPLETE

Immediately sent to GAN cell, MS switches to GAN mode

6

GA-CSR RELEASE

IE ‘RR cause’ indicates #0

7

GA-CSR RELEASE COMPLETE

MS enters GA-CSR-IDLE state

82.7.1.3 Handover from UTRAN to GAN

82.7.1.3.1 Conformance requirement

The procedure is initiated when the source radio access technology (e.g. GERAN) orders the MS to make handover to GAN.

The procedure is applicable in GA-RC-REGISTERED state provided the conditions described in Annex C: "(Source-RAT) Measurement Report for Handover and Cell Change Order to GAN" are met.

The handover order in the source radio access technology mode is sent via the (RR) HANDOVER COMMAND message. If the ARFCN and BSIC parameters included in the Cell Description IE in the (RR) HANDOVER COMMAND message (specified in [12]) match those of the GAN cell, the MS shall:

– send a GA-CSR HANDOVER ACCESS message to the network including the complete (RR) HANDOVER COMMAND message in the Handover To GAN Command IE and enter GA-CSR-DEDICATED state;

NOTE: sending the complete (RR) HANDOVER COMMAND message in the Handover To GAN Command IE instead of the Handover Reference IE allows for more than 256 concurrent handover requests

– if non-signalling mode is indicated in Channel Mode IE, the MS shall:

– start timer TU3920;

– otherwise, the MS shall:

– immediately send a GA-CSR HANDOVER COMPLETE message to the network;

– switch to GAN mode i.e. attach the GA-RR entity to the RR-SAP;

If the traffic channel assignment was successfully completed within timer TU3920, the MS shall:

– stop timer TU3920;

– send a GA-CSR HANDOVER COMPLETE message to the network;

– switch to GAN mode i.e. attach the GA-RR entity to the RR-SAP;

In addition the MS shall send upper layer messages for which LAPDm has not yet received acknowledgement from the network to the network using the GA-RR entity.

Reference(s)

3GPP TS 44.318 subclause 7.7.1 / 7.7.3

82.7.1.3.2 Test purpose

To verify that MS completes the handover procedure from UTRAN to GAN successfully.

82.7.1.3.3 Method of test

Initial Conditions

System Simulator:

– 2 cells – Cell 1 is UTRAN (3GPP TS 34.108, subclause 6.1 shall be referenced for default parameters), Cell 2 is GAN (GAN default parameters)

Mobile Station:

– MS in UTRAN mode in service of UTRAN cell, voice call activated and in GA-RC-REGISTERED state

Foreseen Final State of the MS

MS in GA-CSR-IDLE state.

Test Procedure

The MS is in UTRAN mode in service of UTRAN cell, voice call activated. After measurement reporting procedure in UTRAN cell with successful reporting of the GAN cell, SS sends (RR) HANDOVER COMMAND with ARFCN and BSIC in ‘Cell Description’ IE of the GAN cell. MS sends a GA-CSR HANDOVER ACCESS message to the GAN network with the complete (RR) HANDOVER COMMAND message in the ‘Handover To GAN Command’ IE and enters GA-CSR-DEDICATED state. MS establishes GAN traffic channel with SS and MS sends GA-CSR HANDOVER COMPLETE message to the SS.

Specific test parameters

Maximum Duration of Test

2 min.

Expected Sequence

Step

Direction

Message

Comment

MS

SS

1

MS in service voice call activated on UTRAN cell

2

MEASUREMENT CONTROL

SS configures event 3a in the UE.

3

MEASUREMENT REPORT

UE sends a MEASUREMENT REPORT to SS triggered by event 3a.

Measurement results for GAN cell are included with best possible receiving level (GSM carrier RSSI = 63).

4

HANDOVER FROM UTRAN COMMAND-GSM

Sent on cell 1 (UTRAN cell)

GAN-ARFCN is assigned in (RR) HANDOVER COMMAND part of the message

5

GA-CSR HANDOVER ACCESS

Sent to GAN cell, with IE ‘Handover To GAN Command’, MS enters GA-CSR-DEDICATED state

6

GAN Traffic Channel assignment procedure (steps 5-10)

7

GA-CSR ACTIVATE CHANNEL

IE ‘Channel Mode’, IE ‘Sample Size’, IE ‘UDP Port’, IE ‘IP address’, optional IE ‘Multi-rate Configuration’, optional IE ‘Payload Type’.

8

GA-CSR ACTIVATE CHANNEL ACK

IE ‘UDP Port’

9

GA-CSR ACTIVATE CHANNEL COMPLETE

Optional IE ‘RTCP UDP Port’

10

RTP frame each 480 ms

To enable quality measurements

11

GAN Traffic Channel assignment procedure ready

12

GA-CSR HANDOVER COMPLETE

Sent to GAN cell, voice call ongoing on GAN cell

13

GA-CSR RELEASE

IE ‘RR cause’ indicates #0

14

GA-CSR RELEASE COMPLETE

MS enters GA-CSR-IDLE state

Specific Message Contents:

Default settings for measurement control from 3GPP TS 34.108 are used.

Following specific settings are applied:

MEASUREMENT CONTROL (Step 2)

Information Element

Value/remark

Measurement Identity

3

Measurement Command

Default

Measurement Reporting Mode

– Measurement Reporting Transfer Mode

Default

– Periodic Reporting / Event Trigger Reporting Mode

Event triggered

Additional measurements list

Default

CHOICE measurement type

– inter-RAT measurement

– inter-RAT measurement object list

CHOICE Inter-RAT Cell Removal

Remove all inter-RAT cells

-Remove all inter-RAT cells

(No Data)

New inter-RAT cells (1 to <MaxCellMeas>)

– inter-RAT cell id

0

CHOICE Radio Access Technology

GSM

– Cell individual offset

0

– Cell selection and re-selection info

Not present

– BSIC

BSIC of GAN (cell 2)

– Band indicator

Default

– BCCH ARFCN

ARFCN not corresponding to a channel from any frequency band defined in 45.005

– Cell for measurement

Not present

– inter-RAT measurement quantity

– Measurement quantity for UTRAN quality estimate

– Intra-frequency measurement quantity

– Filter coefficient

0

– CHOICE mode

FDD

– Measurement quantity

CPICH RSCP

CHOICE system

GSM

– Measurement quantity

GSM carrier RSSI

– Filter coefficient

0

– BSIC verification required

required

– inter-RAT reporting quantity

CHOICE system

GSM

– Observed time difference to to GSM cell reporting indicator

FALSE

– GSM carrier RSSI reporting indicator

TRUE

CHOICE report criteria

– Inter-RAT measurements reporting criteria

– Parameters required for each event

(1 to<maxMeasEvent>)

– Inter-RAT event identity

3a

– Threshold own system

Default

– W

Default

– Threshold other system

Default

– Hysteresis

Default

– Time to Trigger

640 ms

– Reporting cell status

Report cells within active set or within virtual active set or of the other RAT

– Maximum number of reported cells

1 cells

82.7.2 Handover to GAN / negative cases

82.7.2.1 Void

82.7.2.2 TU3920 expires during handover procedure

82.7.2.2.1 Conformance requirement

If the traffic channel assignment procedure fails or the timer TU3920 expires before traffic channel assignment is completed, the MS shall:

– terminate the procedure including release of the associated GA-CSR resources;

– resume the connection in the source radio access technology used before the handover;

– indicate the failure to the source radio access technology.

Reference(s)

3GPP TS 44.318 subclause 7.7.5

82.7.2.2.2 Test purpose

To verify that MS is able to terminate the handover procedure and resume the connection in the source radio access technology used before the handover, if timer TU3920 expires during handover procedure.

82.7.2.2.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 in service of GERAN cell, voice call activated and in GA-RC-REGISTERED state

Foreseen Final State of the MS

MS in GERAN mode in service of GERAN cell, voice call activated

Test Procedure

The MS is in GERAN mode in service of GERAN cell, voice call activated. MS sends MEASUREMENT REPORT with GAN-ARFCN within cell info list to GERAN cell and MS has not detected GSM neighbour cell matching the {GAN-ARFCN, GAN-BSIC} couple. SS sends RR HANDOVER COMMAND with ARFCN and BSIC in ‘Cell Description’ IE matched of the GAN cell. MS sends a GA-CSR HANDOVER ACCESS message to the GAN network with the complete (RR) HANDOVER COMMAND message in the ‘Handover To GAN Command’ IE and enters GA-CSR-DEDICATED state. TU3920 expires during handover procedure. MS terminates the handover procedure and resumes the connection in the source radio access technology used before the handover. MS returns HANDOVER FAILURE message to GERAN cell.

Specific test parameters

Maximum Duration of Test

1 min.

Expected Sequence

Step

Direction

Message

Comment

MS

SS

1

MS in service voice call activated on GERAN cell

2

MEASUREMENT REPORT

Sent to GERAN cell with GAN-ARCFN within cell info list

3

RR HANDOVER COMMAND

Sent on GERAN cell with GAN cell ARFCN and BSIC and Channel Mode indicating speech.

4

GA-CSR HANDOVER ACCESS

Sent to GAN cell, with IE ‘Handover To GAN Command’, MS enters GA-CSR-DEDICATED state

5

GA-CSR ACTIVATE CHANNEL

IE ‘Channel Mode’, IE ‘Sample Size’, IE ‘UDP Port’, IE ‘IP address’, optional IE ‘Multi-rate Configuration’, optional IE ‘Payload Type’.

6

GA-CSR ACTIVATE CHANNEL ACK

IE ‘UDP Port’

7

SS doesn’t send GA-CSR ACTIVATE CHANNEL COMPLETE, TU3920 expires during GAN Traffic Channel assignment procedure

8

MS

MS terminates handover procedure and resumes connection on GERAN cell

9

HANDOVER FAILURE

Sent on GERAN cell

82.8 Handover from GAN

82.8.1 Handover from GAN / successful cases

82.8.1.1 Handover from GAN to GERAN

82.8.1.1.1 Conformance requirement

3GPP TS 44.318 subclause 7.8.1:

The purpose of this procedure is to transfer, upon request from the MS (and under the control of the GAN), a connection between MS and GAN to another radio access technology (e.g. GERAN).

The procedure is applicable in GA-CSR-DEDICATED state.

The procedure may be initiated by the MS based on:

– local measurements of GAN coverage signal quality;

– reception of a GA-CSR UPLINK QUALITY INDICATION message indicating poor uplink quality in the UL Quality Indication IE; If the UL Quality Indication IE indicates "Network problem" a handover out to GERAN or UTRAN should be attempted. In case the UL Quality Indication information element shows "Radio problem" or "Undetermined problem" a search for a new access point should be done before the handover out is initiated;

– reception of RTCP packets indicating poor uplink quality;

– excessive loss or delay in the received RTP packets.

When the MS decides to trigger the handover from GAN, it shall:

– send a GA-CSR HANDOVER INFORMATION message to the network including a list of candidate/ target cell identifiers ranked in order of preference which is the most recent list available from the other radio access technology (e.g. GSM RR) and including the received signal strength for each identified GERAN or UTRAN cell. The MS may include GERAN cells, UTRAN cells or both.

3GPP TS 44.318 subclause 7.8.3:

The MS shall:

– suspend all NAS layer signalling transmissions;

– start the connection establishment to the target radio access technology (e.g. GERAN) by using the contents of the Handover From GAN Command IE. This message carries information about the candidate/ target cell identifier and radio parameters relevant for the target radio access technology;

A MS that is simultaneously operating in GPRS and CS modes over GAN shall follow the procedure as outlined in 3GPP TS 43.055 when it switches to target cell.

NOTE: The requirements concerning the establishment of the radio connection towards the target radio access technology (e.g. GERAN) and the signalling procedure are outside of the scope of this specification.

3GPP TS 44.318 subclause 7.8.4:

Upon successfully completing the handover, the GANC should:

– release all radio resources associated with the GAN connection.

Upon successfully completing the handover, the MS shall:

– switch to target radio access technology (e.g. GERAN) mode i.e. detach the GA-RR entity from the RR-SAP;

– enter GA- RC -REGISTERED state.

NOTE: The release of the GAN radio resources is initiated from the target RAT. The MS may deregister from the GANC (as defined in sub-clause 6.4) after successfully completing the handover. If the MS chooses to deregister from the GANC, it may do so either immediately after successfully completing the handover or after sending the GA-CSR RELEASE COMPLETE message to the GANC in response to the GA-CSR RELEASE message from the GANC.

Reference(s)

3GPP TS 44.318 subclause 7.8.1 / 7.8.3 / 7.8.4

82.8.1.1.2 Test purpose

To verify that MS is able to complete the handover procedure from GAN to GERAN successfully.

82.8.1.1.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 GA-CSR-DEDICATED state in service of GAN cell, voice call activated

Foreseen Final State of the MS

MS in GERAN mode in service of GERAN cell, voice call activated

Test Procedure

The MS is in GA-CSR-DEDICATED state in service of GAN cell, voice call activated. SS sends GA-CSR UPLINK QUALITY INDICATION to the MS indicating poor uplink quality. MS sends a GA-CSR HANDOVER INFORMATION with candidate lists. SS sends GA-CSR HANDOVER COMMAND message to the MS. MS starts the connection establishment to the GERAN cell, switches to GERAN mode, detaches the GAN-RR entity, releases all radio resources associated with the GAN connection and enters GA-RC-REGISTERED state. The MS may (optionally) immediately send the GA-RC DEREGISTER message to the GANC and enter the GA-RC-DEREGISTERED state.

Specific test parameters

Maximum Duration of Test

2 min.

Expected Sequence

Step

Direction

Message

Comment

MS

SS

1

MS in GA-CSR-DEDICATED state in service of GAN cell, voice call activated

2

GA-CSR UPLINK QUALITY INDICATION

IE ‘UL Quality Indication’

3

GA-CSR HANDOVER INFORMATION

IE ‘Cell Identifier List’

4

GA-CSR HANDOVER COMMAND

IE ‘Handover From GAN Command’. Indicates non-synchronized handover.

5

MS

MS establishes new connection to GERAN

6

HANDOVER ACCESS

Repeated on every burst of the uplink main DCCH until reception of PHYSICAL INFORMATION.

7

PHYSICAL INFORMATION

Sent after reception of n HANDOVER ACCESS message.

8

HANDOVER COMPLETE

Sent on GERAN cell

9

(optional)

GA-RC DEREGISTER

IE ‘Deregister cause’

Sent if MS chooses to immediately deregister after successful handover from GAN

10 (conditional)

GA-CSR RELEASE

IE ‘RR cause’

Sent if GANC does not receive GA-RC DEREGISTER from MS (step 9)

11 (conditional)

GA-CSR RELEASE COMPLETE

MS in GERAN mode in service of GERAN cell, voice call activated, MS in GA-CSR-REGISTERED state

Sent if MS does not send GA-RC DEREGISTER to GANC (step 9)

82.8.1.2 Handover from GAN to UTRAN

82.8.1.2.1 Conformance requirement

3GPP TS 44.318 subclause 7.8.1:

The purpose of this procedure is to transfer, upon request from the MS (and under the control of the GAN), a connection between MS and GAN to another radio access technology (e.g. GERAN).

The procedure is applicable in GA-CSR-DEDICATED state.

The procedure may be initiated by the MS based on:

– local measurements of GAN coverage signal quality;

– reception of a GA-CSR UPLINK QUALITY INDICATION message indicating poor uplink quality in the UL Quality Indication IE; If the UL Quality Indication IE indicates "Network problem" a handover out to GERAN or UTRAN should be attempted. In case the UL Quality Indication information element shows "Radio problem" or "Undetermined problem" a search for a new access point should be done before the handover out is initiated;

– reception of RTCP packets indicating poor uplink quality;

– excessive loss or delay in the received RTP packets.

When the MS decides to trigger the handover from GAN, it shall:

– send a GA-CSR HANDOVER INFORMATION message to the network including a list of candidate/ target cell identifiers ranked in order of preference which is the most recent list available from the other radio access technology (e.g. GSM RR) and including the received signal strength for each identified GERAN or UTRAN cell. The MS may include GERAN cells, UTRAN cells or both.

3GPP TS 44.318 subclause 7.8.3:

The MS shall:

– suspend all NAS layer signalling transmissions;

– start the connection establishment to the target radio access technology (e.g. GERAN) by using the contents of the Handover From GAN Command IE. This message carries information about the candidate/ target cell identifier and radio parameters relevant for the target radio access technology;

A MS that is simultaneously operating in GPRS and CS modes over GAN shall follow the procedure as outlined in 3GPP TS 43.055 when it switches to target cell.

NOTE: The requirements concerning the establishment of the radio connection towards the target radio access technology (e.g. GERAN) and the signalling procedure are outside of the scope of this specification.

3GPP TS 44.318 subclause 7.8.4:

Upon successfully completing the handover, the GANC should:

– release all radio resources associated with the GAN connection.

Upon successfully completing the handover, the MS shall:

– switch to target radio access technology (e.g. GERAN) mode i.e. detach the GA-RR entity from the RR-SAP;

– enter GA- RC -REGISTERED state.

NOTE: The release of the GAN radio resources is initiated from the target RAT. The MS may deregister from the GANC (as defined in sub-clause 6.4) after successfully completing the handover. If the MS chooses to deregister from the GANC, it may do so either immediately after successfully completing the handover or after sending the GA-CSR RELEASE COMPLETE message to the GANC in response to the GA-CSR RELEASE message from the GANC.

Reference(s)

3GPP TS 44.318 subclause 7.8.1 / 7.8.3 / 7.8.4

82.8.1.2.2 Test purpose

To verify that MS is able to complete the handover procedure from GAN to UTRAN successfully.

82.8.1.2.3 Method of test

Initial Conditions

System Simulator:

– 2 cells – Cell 1 is GAN (GAN default parameters), Cell 2 is UTRAN (3GPP TS 34.108, subclause 6.1 shall be referenced for default parameters)

Mobile Station:

– MS in GA-CSR-DEDICATED state in service of GAN cell, voice call activated

Foreseen Final State of the MS

MS in UTRAN mode in service of UTRAN cell, voice call activated

Test Procedure

The MS is in GA-CSR-DEDICATED state in service of GAN cell, voice call activated. SS sends GA-RC UPLINK QUALITY INDICATION to the MS indicating poor uplink quality. MS sends a GA-CSR HANDOVER INFORMATION with candidate lists including cell 2 (UTRAN). SS sends GA-CSR HANDOVER COMMAND message to the MS. MS starts the connection establishment to the UTRAN cell, switches to UTRAN mode, detaches the GAN-RR entity, releases all radio resources associated with the GAN connection and enters GA-CSR-REGISTERED state. The MS may (optionally) immediately send the GA-RC DEREGISTER message to the GANC and enter the GA-RC-DEREGISTERED state.

Specific test parameters

Maximum Duration of Test

2 min.

Expected Sequence

Step

Direction

Message

Comment

MS

SS

1

MS in GA-CSR-DEDICATED state in service of GAN cell, voice call activated

2

SS

The SS configures the dedicated channel with the configuration: conversational/speech/UL:12.2 DL:12.2 kbps/CS RAB + UL:3.4 DL3.4 kbps SRBs in UTRAN cell.

3

GA-CSR UPLINK QUALITY INDICATION

IE ‘UL Quality Indication’

4

GA-CSR HANDOVER INFORMATION

IE ‘UTRAN Cell Identifier List’ and ‘UTRAN Received Signal Level List’ shall be present. UTRAN cell 2 shall be indicated.

5

GA-CSR HANDOVER COMMAND

Value part of IE ‘Handover From GAN Command’ includes INTERSYSTEM TO UTRAN HANDOVER COMMAND.

6

MS

The MS accepts the handover command and configures its lower layers using the parameters from INTERSYSTEM TO UTRAN HANDOVER COMMAND.

7

SS

The SS waits for uplink physical channel in synchronization.

8

HANDOVER TO UTRAN COMPLETE

The SS receives this message on DCCH of cell 2 (UTRAN cell). It implies that the down link physical channel has synchronised with UTRAN.

9

(optional)

GA-RC DEREGISTER

IE ‘Deregister cause’

Sent if MS chooses to immediately deregister after successful handover from GAN

10 (conditional)

GA-CSR RELEASE

IE ‘RR cause’

Sent if GANC does not receive GA-RC DEREGISTER from MS (step 9)

11 (conditional)

GA-CSR RELEASE COMPLETE

MS in UTRAN mode in service of UTRAN cell, voice call activated, MS in GA-CSR-REGISTERED state

Sent if MS does not send GA-RC DEREGISTER to GANC (step 9)

82.8.2 Handover from GAN / negative cases

82.8.2.1 Connection establishment fails on GERAN cell

82.8.2.1.1 Conformance requirement

If the MS does not succeed in establishing a connection to the target radio access technology, the MS shall:

– revert back to the GAN configuration;

– return a GA-CSR HANDOVER FAILURE message and resume normal operation as if the GA-CSR HANDOVER COMMAND message has not been received. The cause shall be set as specified in 3GPP TS 44.018.

Reference(s)

3GPP TS 44.318 subclause 7.8.5

82.8.2.1.2 Test purpose

To verify that if MS fails to complete requested handover to GERAN, MS reverts back to the GAN configuration.

82.8.2.1.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 GA-CSR-DEDICATED state in service of GAN cell, voice call activated

Foreseen Final State of the MS

MS in GA-CSR-IDLE state

Test Procedure

The MS is in GA-CSR-DEDICATED state in service of GAN cell, voice call activated. SS sends GA-CSR UPLINK QUALITY INDICATION to the MS indicating poor uplink quality. MS sends a GA-CSR HANDOVER INFORMATION with candidate lists. SS sends GA-CSR HANDOVER COMMAND message to the MS. MS starts the connection establishment to the GERAN cell. MS does not succeed in establishing a connection to the target GERAN cell. MS reverts back to the GAN configuration, sends a GA-CSR HANDOVER FAILURE message and resumes normal operation.

Specific test parameters

Maximum Duration of Test

2 min.

Expected Sequence

Step

Direction

Message

Comment

MS

SS

1

MS in GA-CSR-DEDICATED state in service of GAN cell, voice call activated

2

GA-CSR UPLINK QUALITY INDICATION

IE ‘UL Quality Indication’

3

GA-CSR HANDOVER INFORMATION

IE ‘Cell Identifier List’

4

GA-CSR HANDOVER COMMAND

IE ‘Handover From GAN Command’. Indicates non-synchronized handover.

5

HANDOVER ACCESS

Repeated until T3124 (TS 3GPP 44.018) expires.

6

GA-CSR HANDOVER FAILURE

IE ‘RR Cause’ as in test case 26.6.5.8.

7

GA-CSR RELEASE

IE ‘RR cause’ indicates #0

8

GA-CSR RELEASE COMPLETE

MS enters GA-CSR-IDLE state

82.8.2.2 Handover command with non-supported configuration

82.8.2.2.1 Conformance requirement

If the GA-CSR HANDOVER COMMAND message instructs the MS:

– to perform a non-supported scenario, or

– to use a non-supported configuration,

the MS shall return a GA-CSR HANDOVER FAILURE message with cause as defined in 3GPP TS 44.018 and resume normal operation as if the GA-CSR HANDOVER COMMAND message has not been received.

Reference(s)

3GPP TS 44.318 subclause 7.8.7

82.8.2.2.2 Test purpose

To verify that if the GA-CSR HANDOVER COMMAND message instructs the MS to use a non-supported configuration, MS resumes normal operation as if the GA-CSR HANDOVER COMMAND message has not been received.

82.8.2.2.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 GA-CSR-DEDICATED state in service of GAN cell, voice call activated

Foreseen Final State of the MS

MS in GA-CSR-IDLE state.

Test Procedure

The MS is in GA-CSR-DEDICATED state in service of GAN cell, voice call activated. SS sends GA-CSR UPLINK QUALITY INDICATION to the MS indicating poor uplink quality. MS sends a GA-CSR HANDOVER INFORMATION with candidate lists. SS sends GA-CSR HANDOVER COMMAND message to the MS. The GA-CSR HANDOVER COMMAND message instructs the MS to use a not supported frequency. MS sends a GA-CSR HANDOVER FAILURE message and resumes normal operation as if the GA-CSR HANDOVER COMMAND message has not been received.

Specific test parameters

Maximum Duration of Test

2 min.

Expected Sequence

Step

Direction

Message

Comment

MS

SS

1

MS in GA-CSR-DEDICATED state in service of GAN cell, voice call activated

2

GA-CSR UPLINK QUALITY INDICATION

IE ‘UL Quality Indication’

3

GA-CSR HANDOVER INFORMATION

IE ‘Cell Identifier List’

4

GA-CSR HANDOVER COMMAND

Handover to frequency not supported by the MS.

5

GA-CSR HANDOVER FAILURE

With IE ‘RR Cause’ “frequency not implemented”, MS resumes normal operation on GAN cell

6

GA-CSR RELEASE

IE ‘RR cause’ indicates #0

7

GA-CSR RELEASE COMPLETE

MS enters GA-CSR-IDLE state

82.9 Ciphering Configuration Procedure

82.9.1 Ciphering Configuration Procedure, Normal cases

82.9.1.1 Ciphering Configuration Procedure

82.9.1.1.1 Conformance requirement

The network initiates the ciphering mode setting procedure by sending a GA-CSR CIPHERING MODE COMMAND message to the mobile station, indicating whether ciphering shall be used or not, and if yes which algorithm to use.

Additionally, the network may, by the use of the cipher response information element, request the mobile station to include its IMEISV in the GA-CSR CIPHERING MODE COMPLETE message.

Whenever the mobile station receives a valid GA-CSR CIPHERING MODE COMMAND message, it shall, if a SIM is present and considered valid and the ciphering key sequence number stored on the SIM indicates that a ciphering key is available, save information about the ciphering key to use if the MS is later performing Handover from GAN. A valid GA-CSR CIPHERING MODE COMMAND message is defined to be one of the following:

– one that indicates "start ciphering" and is received by the mobile station in the "not ciphered" mode;

– one that indicates "no ciphering" and is received by the MS in the "not ciphered" mode; or

– one that indicates "no ciphering" and is received by the mobile station in the "ciphered" mode.

Other GA-CSR CIPHERING MODE COMMAND messages shall be regarded as erroneous, and a GA-CSR STATUS message with cause "Protocol error unspecified" shall be returned, and no further action taken.

The MS shall also calculate a MAC (Message Authentication Code). The MAC shall be calculated over the following data:

RAND | IMSI

using "HMAC-SHA1-96" algorithm, as specified in [24] with Kc as authentication key.

In the formulas above, the "|" character denotes concatenation. RAND is the 16-octet random number received from the GANC in the GA-CSR CIPHERING MODE COMMAND message. IMSI is the MS IMSI, in the same format as defined for the Mobile Identity IE as defined in [8 / 3GPP TS 44.318 v.6.0.0] i.e. as a variable-length sequence of digits in BCD format (e.g. the IMSI "123456789098765" is encoded as the following octets (in hexadecimal): "21 43 65 87 09 89 67 F5"). Network byte order is used.

The Kc key is the Kc that has been derived during the last authentication. The length of the MAC is 12 octets.

When the appropriate action on the GA-CSR CIPHERING MODE COMMAND message has been taken, the mobile station sends back a GA-CSR CIPHERING MODE COMPLETE message. If the "cipher response" field of the cipher response information element in the GA-CSR CIPHERING MODE COMMAND message specified "IMEISV must be included" the mobile station shall include its IMEISV in the GA-CSR CIPHERING MODE COMPLETE message.

Reference(s)

3GPP TS 44.318 sub-clause 7.9.1 and 7.9.2

82.9.1.1.2 Test purpose

To verify that the MS can reply a GA-CSR CIPHERING MODE COMMAND message and return the correct Message Authentication Code (MAC).

82.9.1.1.3 Method of test

Initial conditions

System Simulator:

– 1 GAN cell, default parameter

Mobile Station:

– MS in state GA-CSR-DEDICATED

– MS in not ciphered mode

Foreseen final state of the MS

MS in GA-CSR IDLE state.Test procedure

The SS sends the GA-CSR CIPHERING MODE message. The Cipher Response IE should indicate that IMEISV should not be included. The MS replies with the GA-CSR CIPHERING MODE COMPLETE message. SS checks that the IMEISV is not included and that the MAC is correct. The SS sends another GA-CSR CIPHERING MODE COMMAND message with SC in Cipher Mode Setting IE set to “No ciphering”. The MS replies with the GA-CSR CIPHERING MODE COMPLETE message. The SS sends new GA-CSR CIPHERING MODE message. The Cipher Response IE should indicate that IMEISV should be included. The MS replies with the GA-CSR CIPHERING MODE COMPLETE message. SS checks that the IMEISV is included and that the MAC is correct.

Specific Test Parameters

Maximum duration of test

1 min.

Reference(s)Expected sequence

Step

Direction

Message

Comment

MS

SS

1

GA-CSR CIPHERING MODE COMMAND

Indicate that IMEISV should not be included

2

GA-CSR CIPHERING MODE COMPLETE

SS checks that the IMEISV is not included and that the MAC is correct

3

GA-CSR CIPHERING MODE COMMAND

SC indicating “No Ciphering”

4

GA-CSR CIPHERING MODE COMPLETE

5

GA-CSR CIPHERING MODE COMMAND

Indicate that IMEISV should be included

6

GA-CSR CIPHERING MODE COMPLETE

SS checks that the IMEISV is included and that the MAC is correct

7

GA-CSR RELEASE

IE ‘RR cause’ #0

8

GA-CSR RELEASE COMPLETE

MS enters GA-CSR-IDLE state

82.9.1.2 Void

82.9.2 Ciphering Configuration Procedure, Abnormal cases

82.9.2.1 Ciphering Configuration Procedure, Invalid Ciphering Mode Command

82.9.2.1.1 Conformance requirement

Whenever the mobile station receives a valid GA-CSR CIPHERING MODE COMMAND message, it shall, if a SIM is present and considered valid and the ciphering key sequence number stored on the SIM indicates that a ciphering key is available, save information about the ciphering key to use if the MS is later performing Handover from GAN. A valid GA-CSR CIPHERING MODE COMMAND message is defined to be one of the following:

– one that indicates "start ciphering" and is received by the mobile station in the "not ciphered" mode;

– one that indicates "no ciphering" and is received by the MS in the "not ciphered" mode; or

– one that indicates "no ciphering" and is received by the mobile station in the "ciphered" mode.

Other GA-CSR CIPHERING MODE COMMAND messages shall be regarded as erroneous, and a GA-CSR STATUS message with cause "Protocol error unspecified" shall be returned, and no further action taken.

Reference(s)

3GPP TS 44.318 sub-clause 7.9.2

82.9.2.1.2 Test purpose

To verify that the MS can reject a GA-CSR CIPHERING MODE COMMAND in the wrong ciphering mode by returning the GA-CSR STATUS message with cause "Protocol error unspecified".

82.9.2.1.3 Method of test

Initial conditions

System Simulator:

– 1 GAN cell, default parameter

Mobile Station:

– MS in state GA-CSR-DEDICATED

– MS in not ciphered mode

Foreseen final state of the MS

MS in GA-CSR IDLE state.Test procedure

The SS sends the GA-CSR CIPHERING MODE message. The MS replies with the GA-CSR CIPHERING MODE COMPLETE message and changes to ciphered mode. The SS sends another GA-CSR CIPHERING MODE message. The MS responds with an GA-CSR STATUS message with cause "Protocol error unspecified".

Specific Test Parameters

Maximum duration of test

1 min.

Expected sequence

Step

Direction

Message

Comment

MS

SS

1

GA-CSR CIPHERING MODE COMMAND

Indicating “start ciphering”

2

GA-CSR CIPHERING MODE COMPLETE

3

GA-CSR CIPHERING MODE COMMAND

Indicating “start ciphering”

4

GA-CSR STATUS

Cause: Protocol error unspecified.

5

GA-CSR RELEASE

IE ‘RR cause’ #0

6

GA-CSR RELEASE COMPLETE

MS enters GA-CSR-IDLE state

82.10 Channel mode modify procedure

82.10.1 Channel mode modify procedure / successful cases

82.10.1.1 Channel mode modify / successful case

82.10.1.1.1 Conformance requirement

In dedicated mode, the GANC can request a modification of the channel mode, multi-rate configuration, RTP redundancy configuration, sample size, GANC IP address, GANC RTP UDP port and GANC RTCP UDP port used for an active traffic channel.

The channel mode modify procedure allows the network to request the mobile station to modify configuration used for an active channel. The channel mode covers the coding, decoding and transcoding mode as well as the redundancy policy used on the active channel.

This procedure is always initiated by the network.

The network initiates the procedure by sending a GA-CSR CHANNEL MODE MODIFY message to the mobile station.

When the MS has received the GA-CSR CHANNEL MODE MODIFY message, the mobile station modifies the configuration, sets the mode and/or the RTP redundancy configuration for the active channel and then replies by a GA-CSR CHANNEL MODE MODIFY ACKNOWLEDGE message indicating the ordered channel mode.

Reference(s)

3GPP TS 44.318 subclauses 7.10 / 7.10.1.1 / 7.10.1.2

82.10.1.1.2 Test purpose

To verify that MS is able to change active channel mode if requested when it is different from the one used by the

mobile station or whether it is already in use.

82.10.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, voice call activated

Foreseen Final State of the MS

MS in GA-CSR-IDLE state

Test Procedure

The MS is in GA-CSR-DEDICATED state in service of GAN cell, voice call activated. SS sends GA-CSR CHANNEL MODE MODIFY message to change active channel mode. The mode is different from the one used by the mobile station. MS sets the mode for the active channel and then replies by a GA-CSR CHANNEL MODE MODIFY ACKNOWLEDGE message indicating the ordered channel mode.

Specific test parameters

Maximum Duration of Test

1 min.

Expected Sequence

Step

Direction

Message

Comment

MS

SS

1

MS

MS in service voice call activated on GAN cell

2

GA-CSR CHANNEL MODE MODIFY

IE ‘Channel Mode’

3

MS

MS sets the different mode

4

GA-CSR CHANNEL MODE MODIFY ACKNOWLEDGE

5

MS

MS in service voice call activated on GAN cell with different channel mode

6

GA-CSR RELEASE

IE ‘RR cause’ indicates #0

7

GA-CSR RELEASE COMPLETE

MS enters GA-CSR-IDLE state

82.10.2 Channel mode modify procedure / negative cases

82.10.2.1 Channel mode modify indicates non-supported mode

82.10.2.1.1 Conformance requirement

If the GA-CSR CHANNEL MODE MODIFY message includes IE "RTP Redundancy Configuration" and MS has indicated that it does not support RTP Redundancy through the GAN Classmark, it shall ignore the IE "RTP Redundancy Configuration".

If the mobile station does not support the indicated channel mode or sample size modifications, it shall retain the old mode and return the used configuration in the GA-CSR CHANNEL MODE MODIFY ACKNOWLEDGE message.

Reference(s)

3GPP TS 44.318 subclause 7.10.1.3

82.10.2.1.2 Test purpose

To verify that MS is able to retain the old channel mode, if GA-CSR CHANNEL MODE MODIFY is requested with non-supported mode.

82.10.2.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, voice call activated

Foreseen Final State of the MS

MS in GA-CSR-IDLE state

Test Procedure

The MS is in GA-CSR-DEDICATED state in service of GAN cell, voice call activated. SS sends GA-CSR CHANNEL MODE MODIFY message to change active channel mode. The requested mode is not supported by the mobile station. MS retains the old mode for the active channel and then replies by a GA-CSR CHANNEL MODE MODIFY ACKNOWLEDGE message with associated channel mode.

Specific test parameters

Maximum Duration of Test

1 min.

Expected Sequence

Step

Direction

Message

Comment

MS

SS

1

MS

MS in service voice call activated on GAN cell

2

GA-CSR CHANNEL MODE MODIFY

IE Channel Mode, requested mode is not supported by the MS

3

MS

MS retains the old mode

4

GA-CSR CHANNEL MODE MODIFY ACKNOWLEDGE

Associated with old channel mode

5

MS

MS in service voice call activated on GAN cell with old channel mode

6

GA-CSR RELEASE

IE ‘RR cause’ indicates #0

7

GA-CSR RELEASE COMPLETE

MS enters GA-CSR-IDLE state