84 GAN Iu Mode Procedures

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

84.1 Macros for GAN Iu mode

84.2 GA-RRC connection establishment

84.2.1 GA-RRC connection establishment / successful case

84.2.1.1 GA-RRC connection establishment, Upper Layer Message Transmission and GA-RRC connection release by GANC (CS domain)

84.2.1.1.1 Conformance requirement

The GAN Iu mode GA-RRC CS and PS connections are logical connections between the MS and the GANC. As described in 3GPP TS 43.318, the GA-RRC sub-layer in the MS contains two entities, the CS domain GA-RRC sublayer entity and the PS domain GA-RRC sublayer entity. These entities operate independently and in parallel; e.g., two GA-RRC connections are established in the case of simultaneous CS and PS services, one GA-RRC connection for each domain. Each GA-RRC sub-layer entity in the MS can be in one of two states, GA-RRC-IDLE or GA-RRC-CONNECTED.

A GA-RRC connection is established when the upper layers in the MS request the establishment of a signalling connection for either CS or PS domain and the GA-RRC sub-layer entity in the MS is in the GA-RRC-IDLE state for that domain; i.e., no GA-RRC connection exists. When a successful response is received from the network, GA-RRC replies to the upper layer that the GA-RRC sub-layer entity in the MS has entered the RRC connected mode (i.e., the GA-RRC-CONNECTED state). The upper layers then have the possibility to request transmission of NAS messages to the network.

The GA-RRC INITIAL DIRECT TRANSFER message is used to transfer the "initial" upper layer message for the domain (i.e., the first NAS message after GA-RRC connection establishment for the domain) from the MS to the GANC. Receipt of the GA-RRC INITIAL DIRECT TRANSFER message by the GANC triggers the establishment of the signalling connection to the indicated CN domain for the MS. The GA-RRC UPLINK DIRECT TRANSFER message is used to transfer all subsequent upper layer messages for the signalling connection from the MS to the GANC.

The GA-RRC DOWNLINK DIRECT TRANSFER message is used to transfer upper layer messages from the GANC to the MS.

The GANC initiates the GA-RRC connection release procedure to command the MS to release the GA-RRC connection and any user plane resources for a particular domain and instruct the GA-RRC sub-layer entity of the MS to leave the GA-RRC-CONNECTED state and return to the GA-RRC-IDLE state for the domain. The GANC normally initiates this procedure when it receives the Iu Release Command from the CN; however, the GANC may also initiate this procedure under certain failure conditions.

The GA-RRC RELEASE message includes the IE "GA-RRC Cause". The GA-RRC Cause value should be one of the following:

#83: normal release; e.g., at the end of a call

#115: unspecified failure

Other values, if received, should be treated as "unspecified failure".

When the GA-RRC sublayer entity in the MS receives the GA-RRC RELEASE message, it shall:

– send a GA-RRC RELEASE COMPLETE message to the GANC,

– release the GA-RRC connection and any user plane resources for the indicated domain,

– stop timer TU5002 for the domain (if running),

– stop timer TU5909 for the domain (if running), and

– enter the GA-RRC-IDLE state for the domain.

Reference(s)

3GPP TS 44.318 subclause 8a.1 / 8a.2 / 8a.5.3 / 8a.5.4

84.2.1.1.2 Test purpose

To verify all of the following for the CS domain.

To verify that MS is able to initiate GA-RRC connection establishment between the MS and GANC and to verify that MS is able to communicate with the CN by encapsulating NAS messages in the GA-RRC INITIAL DIRECT TRANSFER message (first NAS message after GA-RRC connection establishment) and GA-RRC UPLINK DIRECT TRANSFER message and able to receive upper layer messages within GA-RRC DOWNLINK DIRECT TRANSFER message.

To verify that MS is able to release the GA-RRC connection, able to move into GA-RRC-IDLE state and release all GA-RRC and any traffic channel resources, when the MS receives the GA-RRC RELEASE message from SS.

84.2.1.1.3 Method of test

Initial Conditions

System Simulator:

– 1 GAN cell, default parameters

Mobile Station:

– MS in GA-RRC-IDLE state for CS domain in service of GAN cell

Foreseen Final State of the MS

MS in GA-RRC-IDLE state for CS domain.

Test Procedure

The MS is made to initiate a GA-RRC connection establishment for CS domain. The MS moves into GA-RRC-CONNECTED state when the MS receives the GA-RRC REQUEST ACCEPT message from the SS within timer TU5908 (5 sec.) from sending GA-RRC REQUEST message. SS verifies that MS sends GA-RRC INITIAL DIRECT TRANSFER message within 10s from GA-RRC REQUEST ACCEPT message. The SS answers by sending upper layer message within GA-RRC DOWNLINK DIRECT TRANSFER container message.

The SS sends GA-RRC RELEASE message. The MS enters GA-RRC-IDLE state and transmits a GA-RRC RELEASE COMPLETE to the SS and releases all GA-RRC and any traffic channel resources.

Specific test parameters

Maximum Duration of Test

1 min.

Expected Sequence

Step

Direction

Message

Comment

MS

SS

1

MS

MS is made to initiate GA-RRC connection

2

MS

MS checks for access permission based on Access Control Class bits

3

GA-RRC REQUEST

IE ‘CN Domain Identity’ indicates CS domain

4

GA-RRC REQUEST ACCEPT

IE ‘CN Domain Identity’ indicates CS domain

5

MS

MS in GA-RRC-CONNECTED state for CS domain

6

GA-RRC INITIAL DIRECT TRANSFER

Within 10s from GA-RRC REQUEST ACCEPT message

Containing NAS message

IE ‘CN Domain Identity’ indicates CS domain

7

GA-RRC DOWNLINK DIRECT TRANSFER

Containing NAS message

IE ‘CN Domain Identity’ indicates CS domain

8

GA-RRC RELEASE

IE ‘GA-RRC Cause’ indicates #83

IE ‘CN Domain Identity’ indicates CS domain

9

GA-RRC RELEASE COMPLETE

MS enters GA-RRC-IDLE state

IE ‘CN Domain Identity’ indicates CS domain

84.2.1.2 GA-RRC connection establishment, Upper Layer Message Transmission and GA-RRC connection release by GANC (PS domain)

84.2.1.2.1 Conformance requirement

The GAN Iu mode GA-RRC CS and PS connections are logical connections between the MS and the GANC. As described in 3GPP TS 43.318, the GA-RRC sub-layer in the MS contains two entities, the CS domain GA-RRC sublayer entity and the PS domain GA-RRC sublayer entity. These entities operate independently and in parallel; e.g., two GA-RRC connections are established in the case of simultaneous CS and PS services, one GA-RRC connection for each domain. Each GA-RRC sub-layer entity in the MS can be in one of two states, GA-RRC-IDLE or GA-RRC-CONNECTED.

A GA-RRC connection is established when the upper layers in the MS request the establishment of a signalling connection for either CS or PS domain and the GA-RRC sub-layer entity in the MS is in the GA-RRC-IDLE state for that domain; i.e., no GA-RRC connection exists. When a successful response is received from the network, GA-RRC replies to the upper layer that the GA-RRC sub-layer entity in the MS has entered the RRC connected mode (i.e., the GA-RRC-CONNECTED state). The upper layers then have the possibility to request transmission of NAS messages to the network.

The GA-RRC INITIAL DIRECT TRANSFER message is used to transfer the "initial" upper layer message for the domain (i.e., the first NAS message after GA-RRC connection establishment for the domain) from the MS to the GANC. Receipt of the GA-RRC INITIAL DIRECT TRANSFER message by the GANC triggers the establishment of the signalling connection to the indicated CN domain for the MS. The GA-RRC UPLINK DIRECT TRANSFER message is used to transfer all subsequent upper layer messages for the signalling connection from the MS to the GANC.

The GA-RRC DOWNLINK DIRECT TRANSFER message is used to transfer upper layer messages from the GANC to the MS.

The GANC initiates the GA-RRC connection release procedure to command the MS to release the GA-RRC connection and any user plane resources for a particular domain and instruct the GA-RRC sub-layer entity of the MS to leave the GA-RRC-CONNECTED state and return to the GA-RRC-IDLE state for the domain. The GANC normally initiates this procedure when it receives the Iu Release Command from the CN; however, the GANC may also initiate this procedure under certain failure conditions.

The GA-RRC RELEASE message includes the IE "GA-RRC Cause". The GA-RRC Cause value should be one of the following:

#83: normal release; e.g., at the end of a call

#115: unspecified failure

Other values, if received, should be treated as "unspecified failure".

When the GA-RRC sublayer entity in the MS receives the GA-RRC RELEASE message, it shall:

– send a GA-RRC RELEASE COMPLETE message to the GANC,

– release the GA-RRC connection and any user plane resources for the indicated domain,

– stop timer TU5002 for the domain (if running),

– stop timer TU5909 for the domain (if running), and

– enter the GA-RRC-IDLE state for the domain.

Reference(s)

3GPP TS 44.318 subclause 8a.1 / 8a.2 / 8a.5.3 / 8a.5.4

84.2.1.2.2 Test purpose

To verify all of the following for the PS domain.

To verify that MS is able to initiate GA-RRC connection establishment between the MS and GANC and to verify that MS is able to communicate with the CN by encapsulating NAS messages in the GA-RRC INITIAL DIRECT TRANSFER message (first NAS message after GA-RRC connection establishment) and GA-RRC UPLINK DIRECT TRANSFER message and able to receive upper layer messages within GA-RRC DOWNLINK DIRECT TRANSFER message.

To verify that MS is able to release the GA-RRC connection, able to move into GA-RRC-IDLE state and release all GA-RRC and any traffic channel resources, when the MS receives the GA-RRC RELEASE message from SS.

84.2.1.2.3 Method of test

Initial Conditions

System Simulator:

– 1 GAN cell, default parameters

Mobile Station:

– MS in GA-RRC-IDLE state for PS domain in service of GAN cell

Foreseen Final State of the MS

MS in GA-RRC-IDLE state for PS domain.

Test Procedure

The MS is made to initiate a GA-RRC connection establishment for PS domain. The MS moves into GA-RRC-CONNECTED state when the MS receives the GA-RRC REQUEST ACCEPT message from the SS within timer TU5908 (5 sec.) from sending GA-RRC REQUEST message. SS verifies that MS sends GA-RRC INITIAL DIRECT TRANSFER message within 10s from GA-RRC REQUEST ACCEPT message. The SS answers by sending upper layer message within GA-RRC DOWNLINK DIRECT TRANSFER container message.

The SS sends GA-RRC RELEASE message. The MS enters GA-RRC-IDLE state and transmits a GA-RRC RELEASE COMPLETE to the SS and releases all GA-RRC and any traffic channel resources.

Specific test parameters

Maximum Duration of Test

1 min.

Expected Sequence

Step

Direction

Message

Comment

MS

SS

1

MS

MS is made to initiate GA-RRC connection

2

MS

MS checks for access permission based on Access Control Class bits

3

GA-RRC REQUEST

IE ‘CN Domain Identity’ indicates PS domain

4

GA-RRC REQUEST ACCEPT

IE ‘CN Domain Identity’ indicates PS domain

5

MS

MS in GA-RRC-CONNECTED state for PS domain

6

GA-RRC INITIAL DIRECT TRANSFER

Within 10s from GA-RRC REQUEST ACCEPT message

Containing NAS message

IE ‘CN Domain Identity’ indicates PS domain

7

GA-RRC DOWNLINK DIRECT TRANSFER

Containing NAS message

IE ‘CN Domain Identity’ indicates PS domain

8

GA-RRC RELEASE

IE ‘GA-RRC Cause’ indicates #83

IE ‘CN Domain Identity’ indicates PS domain

9

GA-RRC RELEASE COMPLETE

MS enters GA-RRC-IDLE state

IE ‘CN Domain Identity’ indicates PS domain

84.2.2 GA-RRC connection establishment / negative cases

84.2.2.1 GA-RRC REQUEST rejected (CS domain)

84.2.2.1.1 Conformance requirement

3GPP TS 44.318 subclause 8a.1.2.2:

If the GANC rejects the GA-RRC connection establishment request, it shall send the GA-RRC REQUEST REJECT message to the MS including the IE "CN Domain Identity".

3GPP TS 44.318 subclause 8a.1.3.2:

When the MS receives the GA-RRC REQUEST REJECT message, it shall:

– if timer TU5908 is active for the domain indicated by the IE "CN Domain Identity":

– stop timer TU5908 for that domain,

– remain in the GA-RRC-IDLE state for that domain, and

– indicate to upper layers that GA-RRC was not able to enter the connected state for that domain;

– if timer TU5908 is not active for the domain indicated by the IE "CN Domain Identity":

– ignore the GA-RRC REQUEST REJECT message, and

– continue with the procedure as if the GA-RRC REQUEST REJECT message was not received.

3GPP TS 44.318 subclause 8a.3.2:

If the mobile identity in the GA-RRC PAGING REQUEST message matches any of the valid identities of the MS and the GA-RRC sub-layer entity in the MS is in the GA-RRC-IDLE state for the indicated domain, the MS shall:

– if timer TU5908 is not active for the domain and access to the network is allowed:

– indicate reception of paging to upper layers, and

– forward the IE "CN Domain Identity", the IE "Mobile Identity" and the IE "Paging Cause" (if received) to the upper layers;

– Note: The upper layers will request the establishment of a signalling connection and the transmission of the paging response in the initial NAS message. This results in the implicit establishment of the GA-RRC connection (i.e., the GA-RRC sub-layer entity in the MS enters the GA-RRC CONNECTED state) and the transmission of the paging response from the MS to the GANC in the GA-RRC INITIAL DIRECT TRANSFER message, as shown in Figure 8a.3.1.

– if timer TU5908 is active for the domain:

– ignore the GA-RRC PAGING REQUEST message, and

– continue with the ongoing procedure as if the GA-RRC PAGING REQUEST was not received.

Reference(s)

3GPP TS 44.318 subclauses 8a.1.2.2 / 8a.1.3.2 / 8a.3.2

84.2.2.1.2 Test purpose

To verify that MS will remain in GA-RRC-IDLE state (CS domain) when MS receives the GA-RRC REQUEST REJECT message (CS domain).

84.2.2.1.3 Method of test

Initial Conditions

System Simulator:

– 1 GAN cell, default parameters

Mobile Station:

– MS in GA-RRC-IDLE state for CS domain in service of GAN cell

Foreseen Final State of the MS

MS in GA-RRC- IDLE state for CS domain.

Test Procedure

The MS is made to initiate a GA-RRC connection establishment for CS domain. SS sends the GA-RRC REQUEST REJECT message to the MS. MS is not able to enter GA-RRC-CONNECTED state. The SS sends GA-RRC PAGING REQUEST to verify that MS in GA-RRC-IDLE state. MS answers by sending GA-RRC INITIAL DIRECT TRANSFER message containing paging response.

Specific test parameters

Maximum Duration of Test

1 min.

Expected Sequence

Step

Direction

Message

Comment

MS

SS

1

MS

MS is made to initiate GA-RRC connection

2

MS

MS checks for access permission based on Access Control Class bits

3

GA-RRC REQUEST

IE ‘CN Domain Identity’ indicates CS domain

TU5908 is started

4

GA-RRC REQUEST REJECT

The SS sends GA-RRC REQUEST REJECT before the expiry of TU5908.

IE ‘CN Domain Identity’ indicates CS domain

5

MS

MS in GA-RRC-IDLE state for CS domain

6

GA-RRC PAGING REQUEST

Valid identity of the MS (‘TMSI’/’IMSI’)

IE ‘CN Domain Identity’ indicates CS domain

7

GA-RRC INITIAL DIRECT TRANSFER

IE ‘L3 Message’ contains Paging Response

IE ‘CN Domain Identity’ indicates CS domain

MS enters GA-RRC-CONNECTED state for CS domain

8

GA-RRC RELEASE

IE ‘RR cause’ indicates #83

IE ‘CN Domain Identity’ indicates CS domain

9

GA-RRC RELEASE COMPLETE

IE ‘CN Domain Identity’ indicates CS domain

MS enters GA-RRC-IDLE state for CS domain

84.2.2.2 MS receives GA-RRC REQUEST ACCEPT message after TU5908 expiry (CS domain)

84.2.2.2.1 Conformance requirement

If the GANC accepts the GA-RRC connection establishment request, it shall send the GA-RRC REQUEST ACCEPT message to the MS including the IE "CN Domain Identity".

When the MS receives the GA-RRC REQUEST ACCEPT message, it shall:

– if timer TU5908 is active for the domain indicated by the IE "CN Domain Identity":

– stop timer TU5908 for that domain,

– move into the GA-RRC-CONNECTED state for that domain,

– indicate to upper layers that GA-RRC has entered the connected state for that domain, and

– send the GA-RRC INITIAL DIRECT TRANSFER message to the network;

– if timer TU5908 is not active for the domain indicated by the IE "CN Domain Identity":

– ignore the GA-RRC REQUEST ACCEPT message, and

– continue with the procedure as if the GA-RRC REQUEST ACCEPT message was not received.

If timer TU5908 expires in the MS, the GA-RRC sub-layer entity in the MS shall remain in the GA-RRC-IDLE state and indicate to upper layers that GA-RRC was not able to enter the connected state for the domain.

If the mobile identity in the GA-RRC PAGING REQUEST message matches any of the valid identities of the MS and the GA-RRC sub-layer entity in the MS is in the GA-RRC-IDLE state for the indicated domain, the MS shall:

– if timer TU5908 is not active for the domain and access to the network is allowed:

– indicate reception of paging to upper layers, and

– forward the IE "CN Domain Identity", the IE "Mobile Identity" and the IE "Paging Cause" (if received) to the upper layers;

– Note: The upper layers will request the establishment of a signalling connection and the transmission of the paging response in the initial NAS message. This results in the implicit establishment of the GA-RRC connection (i.e., the GA-RRC sub-layer entity in the MS enters the GA-RRC CONNECTED state) and the transmission of the paging response from the MS to the GANC in the GA-RRC INITIAL DIRECT TRANSFER message, as shown in Figure 8a.3.1.

– if timer TU5908 is active for the domain:

– ignore the GA-RRC PAGING REQUEST message, and

– continue with the ongoing procedure as if the GA-RRC PAGING REQUEST was not received.

Reference(s)

3GPP TS 44.318 subclauses 8a.1.2.1 / 8a.1.3.1 / 8a.1.4.1 / 8a.3.2

84.2.2.2.2 Test purpose

To verify that MS will remain in GA-RRC IDLE state (CS domain) if TU5908 expires before MS receives the GA-RRC REQUEST ACCEPT message (CS domain).

84.2.2.2.3 Method of test

Initial Conditions

System Simulator:

– 1 GAN cell, default parameters

Mobile Station:

– MS in GA-RRC-IDLE state for CS domain in service of GAN cell

Foreseen Final State of the MS

MS in GA-RRC- IDLE state for CS domain.

Test Procedure

The MS is made to initiate a GA-RRC connection establishment for CS domain. MS receives the GA-RRC REQUEST ACCEPT message from the SS after timer TU5908 (5 sec.) expires. MS remains in GA-RRC IDLE state. The MS may send GA-RRC-REQUEST message due to upper layer requesting to restart the higher layer procedure which verifies that MS has been in GA-RRC-IDLE state. If GA-RRC-REQUEST message is not received, the SS sends GA-RRC PAGING REQUEST to verify that MS in GA-RRC-IDLE state. MS answers by sending GA-RRC INITIAL DIRECT TRANSFER message containing paging response.

Specific test parameters

Maximum Duration of Test

1 min.

Expected Sequence

Step

Direction

Message

Comment

MS

SS

1

MS

MS is made to initiate GA-RRC connection

2

MS

MS checks for access permission based on Access Control Class bits

3

GA-RRC REQUEST

IE ‘CN Domain Identity’ indicates CS domain

4

SS

SS waits 5 seconds after SS has received the GA-RRC REQUEST message

5

MS

TU5908 expires

6

GA-RRC REQUEST ACCEPT

IE ‘CN Domain Identity’ indicates CS domain

7

MS

MS ignores the GA-RRC REQUEST ACCEPT message and remains in GA-RRC-IDLE state for CS domain

7a (optional)

GA-RRC REQUEST

MS may send GA-RRC-REQUEST message due to upper layer restarting the higher layer procedure. This verifies that the MS has been in GA-RRC-IDLE state.

IE ‘CN Domain Identity’ indicates CS domain

8 (conditional)

GA-RRC PAGING REQUEST

Valid identity of the MS (‘TMSI’/’IMSI’)

IE ‘CN Domain Identity’ indicates CS domain

9 (conditional)

GA-RRC INITIAL DIRECT TRANSFER

IE ‘L3 Message’ contains Paging Response

IE ‘CN Domain Identity’ indicates CS domain

MS enters GA-RRC-CONNECTED state for CS domain

10 (conditional)

GA-RRC RELEASE

IE ‘GA-RRC Cause’ indicates #83

IE ‘CN Domain Identity’ indicates CS domain

11 (conditional)

GA-RRC RELEASE COMPLETE

IE ‘CN Domain Identity’ indicates CS domain

MS enters GA-RRC-IDLE state for CS domain

NOTE: Steps 8-11 are not applicable If GA-RRC-REQUEST message is received in step 7a

84.2.2.3 GA-RRC REQUEST rejected (PS domain)

84.2.2.3.1 Conformance requirement

3GPP TS 44.318 subclause 8a.1.2.2:

If the GANC rejects the GA-RRC connection establishment request, it shall send the GA-RRC REQUEST REJECT message to the MS including the IE "CN Domain Identity".

3GPP TS 44.318 subclause 8a.1.3.2:

When the MS receives the GA-RRC REQUEST REJECT message, it shall:

– if timer TU5908 is active for the domain indicated by the IE "CN Domain Identity":

– stop timer TU5908 for that domain,

– remain in the GA-RRC-IDLE state for that domain, and

– indicate to upper layers that GA-RRC was not able to enter the connected state for that domain;

– if timer TU5908 is not active for the domain indicated by the IE "CN Domain Identity":

– ignore the GA-RRC REQUEST REJECT message, and

– continue with the procedure as if the GA-RRC REQUEST REJECT message was not received.

3GPP TS 44.318 subclause 8a.3.2:

If the mobile identity in the GA-RRC PAGING REQUEST message matches any of the valid identities of the MS and the GA-RRC sub-layer entity in the MS is in the GA-RRC-IDLE state for the indicated domain, the MS shall:

– if timer TU5908 is not active for the domain and access to the network is allowed:

– indicate reception of paging to upper layers, and

– forward the IE "CN Domain Identity", the IE "Mobile Identity" and the IE "Paging Cause" (if received) to the upper layers;

– Note: The upper layers will request the establishment of a signalling connection and the transmission of the paging response in the initial NAS message. This results in the implicit establishment of the GA-RRC connection (i.e., the GA-RRC sub-layer entity in the MS enters the GA-RRC CONNECTED state) and the transmission of the paging response from the MS to the GANC in the GA-RRC INITIAL DIRECT TRANSFER message, as shown in Figure 8a.3.1.

– if timer TU5908 is active for the domain:

– ignore the GA-RRC PAGING REQUEST message, and

– continue with the ongoing procedure as if the GA-RRC PAGING REQUEST was not received.

Reference(s)

3GPP TS 44.318 subclauses 8a.1.2.2 / 8a.1.3.2 / 8a.3.2

84.2.2.3.2 Test purpose

To verify that MS will remain in GA-RRC-IDLE state (PS domain) when MS receives the GA-RRC REQUEST REJECT message (PS domain).

84.2.2.3.3 Method of test

Initial Conditions

System Simulator:

– 1 GAN cell, default parameters

Mobile Station:

– MS in GA-RRC-IDLE state for PS domain in service of GAN cell

Foreseen Final State of the MS

MS in GA-RRC- IDLE state for PS domain.

Test Procedure

The MS is made to initiate a GA-RRC connection establishment for PS domain. SS sends the GA-RRC REQUEST REJECT message to the MS. MS is not able to enter GA-RRC-CONNECTED state. The SS sends GA-RRC PAGING REQUEST to verify that MS in GA-RRC-IDLE state. MS answers by sending GA-RRC INITIAL DIRECT TRANSFER message containing paging response.

Specific test parameters

Maximum Duration of Test

1 min.

Expected Sequence

Step

Direction

Message

Comment

MS

SS

1

MS

MS is made to initiate GA-RRC connection

2

MS

MS checks for access permission based on Access Control Class bits

3

GA-RRC REQUEST

IE ‘CN Domain Identity’ indicates PS domain

TU5908 is started

4

GA-RRC REQUEST REJECT

The SS sends GA-RRC REQUEST REJECT before the expiry of TU5908.

IE ‘CN Domain Identity’ indicates PS domain

5

MS

MS in GA-RRC-IDLE state for PS domain

6

GA-RRC PAGING REQUEST

Valid identity of the MS (‘TMSI’/’IMSI’)

IE ‘CN Domain Identity’ indicates PS domain

7

GA-RRC INITIAL DIRECT TRANSFER

IE ‘L3 Message’ contains Paging Response

IE ‘CN Domain Identity’ indicates PS domain

MS enters GA-RRC-CONNECTED state for PS domain

8

GA-RRC RELEASE

IE ‘RR cause’ indicates #83

IE ‘CN Domain Identity’ indicates PS domain

9

GA-RRC RELEASE COMPLETE

IE ‘CN Domain Identity’ indicates PS domain

MS enters GA-RRC-IDLE state for PS domain

84.2.2.4 MS receives GA-RRC REQUEST ACCEPT message after TU5908 expiry (PS domain)

84.2.2.4.1 Conformance requirement

If the GANC accepts the GA-RRC connection establishment request, it shall send the GA-RRC REQUEST ACCEPT message to the MS including the IE "CN Domain Identity".

When the MS receives the GA-RRC REQUEST ACCEPT message, it shall:

– if timer TU5908 is active for the domain indicated by the IE "CN Domain Identity":

– stop timer TU5908 for that domain,

– move into the GA-RRC-CONNECTED state for that domain,

– indicate to upper layers that GA-RRC has entered the connected state for that domain, and

– send the GA-RRC INITIAL DIRECT TRANSFER message to the network;

– if timer TU5908 is not active for the domain indicated by the IE "CN Domain Identity":

– ignore the GA-RRC REQUEST ACCEPT message, and

– continue with the procedure as if the GA-RRC REQUEST ACCEPT message was not received.

If timer TU5908 expires in the MS, the GA-RRC sub-layer entity in the MS shall remain in the GA-RRC-IDLE state and indicate to upper layers that GA-RRC was not able to enter the connected state for the domain.

If the mobile identity in the GA-RRC PAGING REQUEST message matches any of the valid identities of the MS and the GA-RRC sub-layer entity in the MS is in the GA-RRC-IDLE state for the indicated domain, the MS shall:

– if timer TU5908 is not active for the domain and access to the network is allowed:

– indicate reception of paging to upper layers, and

– forward the IE "CN Domain Identity", the IE "Mobile Identity" and the IE "Paging Cause" (if received) to the upper layers;

– Note: The upper layers will request the establishment of a signalling connection and the transmission of the paging response in the initial NAS message. This results in the implicit establishment of the GA-RRC connection (i.e., the GA-RRC sub-layer entity in the MS enters the GA-RRC CONNECTED state) and the transmission of the paging response from the MS to the GANC in the GA-RRC INITIAL DIRECT TRANSFER message, as shown in Figure 8a.3.1.

– if timer TU5908 is active for the domain:

– ignore the GA-RRC PAGING REQUEST message, and

– continue with the ongoing procedure as if the GA-RRC PAGING REQUEST was not received.

Reference(s)

3GPP TS 44.318 subclauses 8a.1.2.1 / 8a.1.3.1 / 8a.1.4.1 / 8a.3.2

84.2.2.4.2 Test purpose

To verify that MS will remain in GA-RRC IDLE state (PS domain) if TU5908 expires before MS receives the GA-RRC REQUEST ACCEPT message (PS domain).

84.2.2.4.3 Method of test

Initial Conditions

System Simulator:

– 1 GAN cell, default parameters

Mobile Station:

– MS in GA-RRC-IDLE state for PS domain in service of GAN cell

Foreseen Final State of the MS

MS in GA-RRC- IDLE state for PS domain.

Test Procedure

The MS is made to initiate a GA-RRC connection establishment for PS domain. MS receives the GA-RRC REQUEST ACCEPT message from the SS after timer TU5908 (5 sec.) expires. MS remains in GA-RRC IDLE state. The MS may send GA-RRC-REQUEST message due to upper layer requesting to restart the higher layer procedure which verifies that MS has been in GA-RRC-IDLE state. If GA-RRC-REQUEST message is not received, the SS sends GA-RRC PAGING REQUEST to verify that MS in GA-RRC-IDLE state. MS answers by sending GA-RRC INITIAL DIRECT TRANSFER message containing paging response.

Specific test parameters

Maximum Duration of Test

1 min.

Expected Sequence

Step

Direction

Message

Comment

MS

SS

1

MS

MS is made to initiate GA-RRC connection

2

MS

MS checks for access permission based on Access Control Class bits

3

GA-RRC REQUEST

IE ‘CN Domain Identity’ indicates PS domain

4

SS

SS waits 5 seconds after SS has received the GA-RRC REQUEST message

5

MS

TU5908 expires

6

GA-RRC REQUEST ACCEPT

IE ‘CN Domain Identity’ indicates PS domain

7

MS

MS ignores the GA-RRC REQUEST ACCEPT message and remains in GA-RRC-IDLE state for PS domain

7a (optional)

GA-RRC REQUEST

MS may send GA-RRC-REQUEST message due to upper layer restarting the higher layer procedure. This verifies that the MS has been in GA-RRC-IDLE state.

IE ‘CN Domain Identity’ indicates PS domain

8 (conditional)

GA-RRC PAGING REQUEST

Valid identity of the MS (‘TMSI’/’IMSI’)

IE ‘CN Domain Identity’ indicates PS domain

9 (conditional)

GA-RRC INITIAL DIRECT TRANSFER

IE ‘L3 Message’ contains Paging Response

IE ‘CN Domain Identity’ indicates PS domain

MS enters GA-RRC-CONNECTED state for PS domain

10 (conditional)

GA-RRC RELEASE

IE ‘GA-RRC Cause’ indicates #83

IE ‘CN Domain Identity’ indicates PS domain

11 (conditional)

GA-RRC RELEASE COMPLETE

IE ‘CN Domain Identity’ indicates PS domain

MS enters GA-RRC-IDLE state for PS domain

NOTE: Steps 8-11 are not applicable If GA-RRC-REQUEST message is received in step 7a

84.3 Upper layer message transmission

84.3.1 Upper layer message transmission / successful cases

84.3.1.1 Void

84.3.2 Upper layer message transmission / negative cases

84.3.2.1 MS receives GA-RRC DOWNLINK DIRECT TRANSFER message when not in GA-RRC-CONNECTED state (CS domain)

84.3.2.1.1 Conformance requirement

If the MS receives a GA-RRC DOWNLINK DIRECT TRANSFER message and GA-RRC sub-layer entity in the MS is not in GA-RRC-CONNECTED state for the indicated domain, the MS shall:

– ignore the contents of the GA-RRC DOWNLINK DIRECT TRANSFER message;

– transmit a GA-RRC STATUS message to the GANC as follows:

– set the IE "GA-RRC Cause" to "Message type not compatible with protocol state"

– include the received message contents in the IE "PDU in Error"

– continue with any ongoing procedure and act as if the GA-RRC DOWNLINK DIRECT TRANSFER message was not received.

Reference(s)

3GPP TS 44.318 subclause 8a.2.6.1

84.3.2.1.2 Test purpose

To verify that MS ignores the contents of the GA-RRC DOWNLINK DIRECT TRANSFER message (CS domain) if MS is not in GA-RRC-CONNECTED state (CS domain) and to be able to send GA-RRC STATUS message to the SS.

84.3.2.1.3 Method of test

Initial Conditions

System Simulator:

– 1 GAN cell, default parameters

Mobile Station:

– MS in GA-RRC-IDLE state for CS domain in service of GAN cell

Foreseen Final State of the MS

MS in GA-RRC-IDLE state for CS domain in service of GAN cell

Test Procedure

MS is in GA-RRC-IDLE state for CS domain in service of GAN cell. SS sends GA-RRC DOWNLINK DIRECT TRANSFER message containing upper layer message. MS ignores the contents of the message and sends GA-RRC STATUS message to the SS with IE ‘GA-RRC Cause’: ‘Message type not compatible with protocol state’. MS includes the received message contents in the IE ‘PDU in error’.

Specific test parameters

Maximum Duration of Test

1 min.

Expected Sequence

Step

Direction

Message

Comment

MS

SS

1

MS

MS in GA-RRC-IDLE state for CS domain

2

GA-RRC DOWNLINK DIRECT TRANSFER

Containing (DL) CC/MM/SS/SMS message

IE ‘CN Domain Identity’ indicates CS domain

3

GA-RRC STATUS

IE ‘CN Domain Identity’ indicates CS domain

IE ‘GA-RRC Cause’ indicates #99

IE PDU in Error: ‘<received (DL) message>’

84.3.2.2 MS receives GA-RRC DOWNLINK DIRECT TRANSFER message when not in GA-RRC-CONNECTED state (PS domain)

84.3.2.2.1 Conformance requirement

If the MS receives a GA-RRC DOWNLINK DIRECT TRANSFER message and GA-RRC sub-layer entity in the MS is not in GA-RRC-CONNECTED state for the indicated domain, the MS shall:

– ignore the contents of the GA-RRC DOWNLINK DIRECT TRANSFER message;

– transmit a GA-RRC STATUS message to the GANC as follows:

– set the IE "GA-RRC Cause" to "Message type not compatible with protocol state"

– include the received message contents in the IE "PDU in Error"

– continue with any ongoing procedure and act as if the GA-RRC DOWNLINK DIRECT TRANSFER message was not received.

Reference(s)

3GPP TS 44.318 subclause 8a.2.6.1

84.3.2.2.2 Test purpose

To verify that MS ignores the contents of the GA-RRC DOWNLINK DIRECT TRANSFER message (PS domain) if MS is not in GA-RRC-CONNECTED state (PS domain) and to be able to send GA-RRC STATUS message to the SS.

84.3.2.2.3 Method of test

Initial Conditions

System Simulator:

– 1 GAN cell, default parameters

Mobile Station:

– MS in GA-RRC-IDLE state for PS domain in service of GAN cell

Foreseen Final State of the MS

MS in GA-RRC-IDLE state for PS domain in service of GAN cell

Test Procedure

MS is in GA-RRC-IDLE state for PS domain in service of GAN cell. SS sends GA-RRC DOWNLINK DIRECT TRANSFER message containing upper layer message. MS ignores the contents of the message and sends GA-RRC STATUS message to the SS with IE ‘GA-RRC Cause’: ‘Message type not compatible with protocol state’. MS includes the received message contents in the IE ‘PDU in error’.

Specific test parameters

Maximum Duration of Test

1 min.

Expected Sequence

Step

Direction

Message

Comment

MS

SS

1

MS

MS in GA-RRC-IDLE state for PS domain

2

GA-RRC DOWNLINK DIRECT TRANSFER

Containing (DL) CC/MM/SS/SMS message

IE ‘CN Domain Identity’ indicates PS domain

3

GA-RRC STATUS

IE ‘CN Domain Identity’ indicates PS domain

IE ‘GA-RRC Cause’ indicates #99

IE PDU in Error: ‘<received (DL) message>’

84.4 Paging

84.4.1 Paging for CS domain / successful cases

84.4.1.1 Paging for CS domain

84.4.1.1.1 Conformance requirement

3GPP TS 44.318 subclause 8a.3.1:

The GANC sends the GA-RRC PAGING REQUEST message to the MS when the GANC receives a PAGING message over the Iu interface from a CN domain. The IMSI of the MS to be paged is identified by the IE "Permanent NAS UE Identity" received in the request from the CN. If the request also includes the (P-)TMSI then the GANC shall include the (P-)TMSI in the IE "Mobile Identity"; else the GANC shall include the IMSI in the IE "Mobile Identity". The GANC also includes the IE "CN Domain Identity" and the IE "GA-RRC Paging Cause", if a cause is received from the CN.

3GPP TS 44.318 subclause 8a.3.2:

If the mobile identity in the GA-RRC PAGING REQUEST message matches any of the valid identities of the MS and the GA-RRC sub-layer entity in the MS is in the GA-RRC-IDLE state for the indicated domain, the MS shall:

– if timer TU5908 is not active for the domain and access to the network is allowed:

– indicate reception of paging to upper layers, and

– forward the IE "CN Domain Identity", the IE "Mobile Identity" and the IE "Paging Cause" (if received) to the upper layers;

– Note: The upper layers will request the establishment of a signalling connection and the transmission of the paging response in the initial NAS message. This results in the implicit establishment of the GA-RRC connection (i.e., the GA-RRC sub-layer entity in the MS enters the GA-RRC CONNECTED state) and the transmission of the paging response from the MS to the GANC in the GA-RRC INITIAL DIRECT TRANSFER message, as shown in Figure 8a.3.1.

– if timer TU5908 is active for the domain:

– ignore the GA-RRC PAGING REQUEST message, and

– continue with the ongoing procedure as if the GA-RRC PAGING REQUEST was not received.

3GPP TS 44.318 subclause 8a.3.3:

If the MS receives a GA-RRC PAGING REQUEST and the mobile identity included in the message does not match any of the valid identities assigned to the MS, the MS shall:

– ignore the GA-RRC PAGING REQUEST message, and

– continue with any ongoing procedure as if the GA-RRC PAGING REQUEST message was not received.

Reference(s)

3GPP TS 44.318 subclauses 8a.3.1 / 8a.3.2 / 8a.3.3

84.4.1.1.2 Test purpose

To verify all of the following for the CS domain.

To verify that MS ignores the GA-RRC PAGING REQUEST and continues with any ongoing procedure, if received GA-RRC PAGING REQUEST doesn’t contain valid identity.

To verify that MS is able send a GA-RRC INITIAL DIRECT TRANSFER containing a page response to the SS and enter GA-RRC-CONNECTED state when MS receives GA-RRC PAGING REQUEST with valid identities of the MS.

84.4.1.1.3 Method of test

Initial Conditions

System Simulator:

– 1 GAN cell, default parameters

Mobile Station:

– MS in GA-RRC-IDLE state for CS domain in service of GAN cell

Foreseen Final State of the MS

MS in GA-RRC-IDLE state for CS domain in service of GAN cell

Test Procedure

The SS initiates paging procedure by sending GA-RRC PAGING REQUEST message with not matching identity to the MS. MS ignores the GA-RRC PAGING REQUEST and continues with any ongoing procedure as if the GA-RRC PAGING REQUEST was not received. After 10s the SS sends GA-RRC PAGING REQUEST to verify that MS in GA-RRC-IDLE state. MS answers by sending GA-RRC INITIAL DIRECT TRANSFER message containg page response.

Specific test parameters

Maximum Duration of Test

1 min.

Expected Sequence

Step

Direction

Message

Comment

MS

SS

1

GA-RRC PAGING REQUEST

With not matching identity

IE ‘CN Domain Identity’ indicates CS domain

2

MS

MS ignores GA-RRC PAGING REQUEST message

3

SS

SS waits 10s for response

4

GA-RRC PAGING REQUEST

Valid identity of the MS (‘TMSI’/’IMSI’)

IE ‘CN Domain Identity’ indicates CS domain

5

GA-RRC INITIAL DIRECT TRANSFER

IE ‘L3 Message’ contains Paging Response

IE ‘CN Domain Identity’ indicates CS domain

MS enters GA-RRC-CONNECTED state for CS domain

6

GA-RRC RELEASE

IE ‘GA-RRC Cause’ = #83

IE ‘CN Domain Identity’ indicates CS domain

7

GA-RRC RELEASE COMPLETE

IE ‘CN Domain Identity’ indicates CS domain

MS enters GA-RRC-IDLE state for CS domain

84.4.2 Paging for CS domain / negative cases

84.4.2.1 Void

84.4.2.2 Paging for CS domain / negative cases / MS receives GA-RRC PAGING REQUEST when TU5908 is active

84.4.2.2.1 Conformance requirement

If the mobile identity in the GA-RRC PAGING REQUEST message matches any of the valid identities of the MS and the GA-RRC sub-layer entity in the MS is in the GA-RRC-IDLE state for the indicated domain, the MS shall:

– if timer TU5908 is not active for the domain and access to the network is allowed:

– indicate reception of paging to upper layers, and

– forward the IE "CN Domain Identity", the IE "Mobile Identity" and the IE "Paging Cause" (if received) to the upper layers;

– Note: The upper layers will request the establishment of a signalling connection and the transmission of the paging response in the initial NAS message. This results in the implicit establishment of the GA-RRC connection (i.e., the GA-RRC sub-layer entity in the MS enters the GA-RRC CONNECTED state) and the transmission of the paging response from the MS to the GANC in the GA-RRC INITIAL DIRECT TRANSFER message, as shown in Figure 8a.3.1.

– if timer TU5908 is active for the domain:

– ignore the GA-RRC PAGING REQUEST message, and

– continue with the ongoing procedure as if the GA-RRC PAGING REQUEST was not received.

Reference(s)

3GPP TS 44.318 subclause 8a.3.2

84.4.2.2.2 Test purpose

To verify that MS discards the received GA-RRC PAGING REQUEST message (indicating CS domain page) if timer TU5908 is active for the CS domain.

84.4.2.2.3 Method of test

Initial Conditions

System Simulator:

– 1 GAN cell, default parameters

Mobile Station:

– MS in GA-RRC-IDLE state for CS domain in service of GAN cell

Foreseen Final State of the MS

MS in GA-RRC- IDLE state for CS domain.

Test Procedure

MS is made to initiate GA-RRC connection for CS domain. MS sends GA-RRC REQUEST message and activates timer TU5908. The SS initiates paging procedure by sending GA-RRC PAGING REQUEST message to the MS when TU5908 is active in MS. MS discards the received GA-RRC PAGING REQUEST message. After TU5908 expiry the SS sends GA-RRC PAGING REQUEST to verify that MS in GA-RRC-IDLE state. MS may answer by sending GA-RRC INITIAL DIRECT TRANSFER or re-establish the GA-RRC connection by re-sending GA-RRC REQUEST message.

Specific test parameters

Maximum Duration of Test

1 min.

Expected Sequence

Step

Direction

Message

Comment

MS

SS

1

MS

MS is made to initiate GA-RRC connection for CS domain

2

GA-RRC REQUEST

IE ‘CN Domain Identity’ indicates CS domain

MS activates TU5908 for CS domain

3

GA-RRC PAGING REQUEST

Valid identity of the MS (‘TMSI’/’IMSI’), sent before TU5908 expiry

IE ‘CN Domain Identity’ indicates CS domain

4

MS

MS discards GA-RRC PAGING REQUEST message

5

SS

SS waits for TU5908 to expire. The MS may resend GA-RRC REQUEST after the expiry of TU5908.

The following steps are executed only if no GA-RRC REQUEST is received from the MS.

6

GA-RRC PAGING REQUEST

Valid identity of the MS (‘TMSI’/’IMSI’)

IE ‘CN Domain Identity’ indicates CS domain

7

GA-RRC INITIAL DIRECT TRANSFER

IE ‘L3 Message’ contains Paging Response

IE ‘CN Domain Identity’ indicates CS domain

MS enters GA-RRC-CONNECTED state for CS domain

8

GA-RRC RELEASE

IE ‘GA-RRC Cause’ = #83

IE ‘CN Domain Identity’ indicates CS domain

9

GA-RRC RELEASE COMPLETE

IE ‘CN Domain Identity’ indicates CS domain

MS enters GA-RRC-IDLE state for CS domain

84.4.2.3 Paging for CS domain / negative cases / MS receives GA-RRC PAGING REQUEST when in GA-RRC-CONNECTED state

84.4.2.3.1 Conformance requirement

If the MS receives a GA-RRC PAGING REQUEST message and the GA-RRC sublayer entity in the MS is in GA-RRC-CONNECTED state for the indicated domain or the MS is in the GA-RC-REGISTERED state but in GERAN/UTRAN mode, the MS shall:

– ignore the GA-RRC PAGING REQUEST message, and

– continue with any ongoing procedure as if the GA-RRC PAGING REQUEST was not received.

Reference(s)

3GPP TS 44.318 subclause 8a.3.3

84.4.2.3.2 Test purpose

To verify that MS ignores the GA-RRC PAGING REQUEST and continues with any ongoing procedure as if the GA-RRC PAGING REQUEST was not received, if MS receives GA-RRC PAGING REQUEST indicating CS domain when MS is in GA-RRC-CONNECTED state for the CS domain.

84.4.2.3.3 Method of test

Initial Conditions

System Simulator:

– 1 GAN cell, default parameters

Mobile Station:

– MS in GA-RRC-CONNECTED state for CS domain in service of GAN cell.

Foreseen Final State of the MS

MS in GA-RRC-IDLE state for CS domain in service of GAN cell.

Test Procedure

The MS is in GA-RRC-CONNECTED state for CS domain in service of GAN cell. The SS initiates paging procedure by sending GA-RRC PAGING REQUEST message to the MS. The MS ignores the GA-RRC PAGING REQUEST and continues with any ongoing procedure as if the GA-RRC PAGING REQUEST was not received. After 10s the SS sends GA-RRC RELEASE to verify that MS in GA-RRC-CONNECTED state. MS answers by sending GA-RRC RELEASE COMPLETE.

Specific test parameters

Maximum Duration of Test

1 min.

Expected Sequence

Step

Direction

Message

Comment

MS

SS

1

MS

MS in GA-RRC-CONNECTED state for CS domain with ongoing procedure

2

GA-RRC PAGING REQUEST

Valid identity of the MS (‘TMSI’/’IMSI’)

IE ‘CN Domain Identity’ indicates CS domain

3

MS

MS ignores the GA-RRC PAGING REQUEST and continues with ongoing procedure

4

SS

SS waits 10s for response

5

GA-RRC RELEASE

IE ‘GA-RRC Cause’

IE ‘CN Domain Identity’ indicates CS domain

6

GA-RRC RELEASE COMPLETE

IE ‘CN Domain Identity’ indicates CS domain

MS enters GA-RRC-IDLE state for CS domain

84.4.2.4 Paging for CS domain / negative cases / MS receives GA-RRC PAGING REQUEST when in GA-RC REGISTERED state

84.4.2.4.1 Conformance requirement

If the MS receives a GA-RRC PAGING REQUEST message and the GA-RRC sublayer entity in the MS is in GA-RRC-CONNECTED state for the indicated domain or the MS is in the GA-RC-REGISTERED state but in GERAN/UTRAN mode, the MS shall:

– ignore the GA-RRC PAGING REQUEST message, and

– continue with any ongoing procedure as if the GA-RRC PAGING REQUEST was not received.

Reference(s)

3GPP TS 44.318 subclause 8a.3.3

84.4.2.4.2 Test purpose

To verify that MS ignores the GA-RRC PAGING REQUEST and continues with any ongoing procedure as if the GA-RRC PAGING REQUEST was not received, if MS receives GA-RRC PAGING REQUEST when MS is in GA-RC-REGISTERED state but in GERAN/UTRAN mode.

84.4.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-RRC-IDLE state for the CS domain.

Test Procedure

MS is camped on a GERAN cell, voice call activated and in GA-RC-REGISTERED state. The SS initiates CS domain paging procedure by sending GA-RRC PAGING REQUEST message to the MS. The MS ignores the GA-RRC PAGING REQUEST and continues with any ongoing procedure as if the GA-RRC PAGING REQUEST was not received. After 10s, the voice call is deactivated to switch the serving RR entity to GA-RRC. The SS waits 30 seconds to ensure that the MS enters the GA-RRC-IDLE state (CS domain) and sends GA-RRC PAGING REQUEST (CS domain) to verify that MS in GA-RRC-IDLE state. MS answers by sending GA-RRC INITIAL DIRECT TRANSFER (CS domain) message containing the page 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-RRC PAGING REQUEST

Valid identity of the MS (‘TMSI’/’IMSI’)

IE ‘CN Domain Identity’ indicates CS domain

3

MS

MS ignores the GA-RRC 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-RRC-IDLE state.

6

SS

Wait 30 seconds to ensure that the MS enters GA-RRC-IDLE state.

7

GA-RRC PAGING REQUEST

Valid identity of the MS (‘TMSI’/’IMSI’)

IE ‘CN Domain Identity’ indicates CS domain

8

GA-RRC INITIAL DIRECT TRANSFER

IE ‘L3 Message’ contains Paging Response

IE ‘CN Domain Identity’ indicates CS domain

MS enters GA-RRC-CONNECTED state for CS domain

9

GA-RRC RELEASE

IE ‘CN Domain Identity’ indicates CS domain

IE ‘GA-RRC Cause’ indicates #83

10

GA-RRC RELEASE COMPLETE

IE ‘CN Domain Identity’ indicates CS domain

MS enters GA-RRC-IDLE state for CS domain

84.4.3 Paging for PS domain / successful cases

84.4.3.1 Paging for PS domain

84.4.3.1.1 Conformance requirement

3GPP TS 44.318 subclause 8a.3.1:

The GANC sends the GA-RRC PAGING REQUEST message to the MS when the GANC receives a PAGING message over the Iu interface from a CN domain. The IMSI of the MS to be paged is identified by the IE "Permanent NAS UE Identity" received in the request from the CN. If the request also includes the (P-)TMSI then the GANC shall include the (P-)TMSI in the IE "Mobile Identity"; else the GANC shall include the IMSI in the IE "Mobile Identity". The GANC also includes the IE "CN Domain Identity" and the IE "GA-RRC Paging Cause", if a cause is received from the CN.

3GPP TS 44.318 subclause 8a.3.2:

If the mobile identity in the GA-RRC PAGING REQUEST message matches any of the valid identities of the MS and the GA-RRC sub-layer entity in the MS is in the GA-RRC-IDLE state for the indicated domain, the MS shall:

– if timer TU5908 is not active for the domain and access to the network is allowed:

– indicate reception of paging to upper layers, and

– forward the IE "CN Domain Identity", the IE "Mobile Identity" and the IE "Paging Cause" (if received) to the upper layers;

– Note: The upper layers will request the establishment of a signalling connection and the transmission of the paging response in the initial NAS message. This results in the implicit establishment of the GA-RRC connection (i.e., the GA-RRC sub-layer entity in the MS enters the GA-RRC CONNECTED state) and the transmission of the paging response from the MS to the GANC in the GA-RRC INITIAL DIRECT TRANSFER message, as shown in Figure 8a.3.1.

– if timer TU5908 is active for the domain:

– ignore the GA-RRC PAGING REQUEST message, and

– continue with the ongoing procedure as if the GA-RRC PAGING REQUEST was not received.

3GPP TS 44.318 subclause 8a.3.3:

If the MS receives a GA-RRC PAGING REQUEST and the mobile identity included in the message does not match any of the valid identities assigned to the MS, the MS shall:

– ignore the GA-RRC PAGING REQUEST message, and

– continue with any ongoing procedure as if the GA-RRC PAGING REQUEST message was not received.

Reference(s)

3GPP TS 44.318 subclauses 8a.3.1 / 8a.3.2 / 8a.3.3

84.4.3.1.2 Test purpose

To verify all of the following for the PS domain.

To verify that MS ignores the GA-RRC PAGING REQUEST and continues with any ongoing procedure, if received GA-RRC PAGING REQUEST doesn’t contain valid identity.

To verify that MS is able send a GA-RRC INITIAL DIRECT TRANSFER containing a page response to the SS and enter GA-RRC-CONNECTED state when MS receives GA-RRC PAGING REQUEST with valid identities of the MS.

84.4.3.1.3 Method of test

Initial Conditions

System Simulator:

– 1 GAN cell, default parameters

Mobile Station:

– MS in GA-RRC-IDLE state for PS domain in service of GAN cell

Foreseen Final State of the MS

MS in GA-RRC-IDLE state for PS domain in service of GAN cell

Test Procedure

The SS initiates paging procedure by sending GA-RRC PAGING REQUEST message with not matching identity to the MS. MS ignores the GA-RRC PAGING REQUEST and continues with any ongoing procedure as if the GA-RRC PAGING REQUEST was not received. After 10s the SS sends GA-RRC PAGING REQUEST to verify that MS in GA-RRC-IDLE state. MS answers by sending GA-RRC INITIAL DIRECT TRANSFER message containg page response.

Specific test parameters

Maximum Duration of Test

1 min.

Expected Sequence

Step

Direction

Message

Comment

MS

SS

1

GA-RRC PAGING REQUEST

With not matching identity

IE ‘CN Domain Identity’ indicates PS domain

2

MS

MS ignores GA-RRC PAGING REQUEST message

3

SS

SS waits 10s for response

4

GA-RRC PAGING REQUEST

Valid identity of the MS (‘TMSI’/’IMSI’)

IE ‘CN Domain Identity’ indicates PS domain

5

GA-RRC INITIAL DIRECT TRANSFER

IE ‘L3 Message’ contains Paging Response

IE ‘CN Domain Identity’ indicates PS domain

MS enters GA-RRC-CONNECTED state for PS domain

6

GA-RRC RELEASE

IE ‘GA-RRC Cause’ = #83

IE ‘CN Domain Identity’ indicates PS domain

7

GA-RRC RELEASE COMPLETE

IE ‘CN Domain Identity’ indicates PS domain

MS enters GA-RRC-IDLE state for PS domain

84.4.4 Paging for PS domain / negative cases

84.4.4.1 Void

84.4.4.2 Paging for PS domain / negative cases / MS receives GA-RRC PAGING REQUEST when TU5908 is active

84.4.4.2.1 Conformance requirement

If the mobile identity in the GA-RRC PAGING REQUEST message matches any of the valid identities of the MS and the GA-RRC sub-layer entity in the MS is in the GA-RRC-IDLE state for the indicated domain, the MS shall:

– if timer TU5908 is not active for the domain and access to the network is allowed:

– indicate reception of paging to upper layers, and

– forward the IE "CN Domain Identity", the IE "Mobile Identity" and the IE "Paging Cause" (if received) to the upper layers;

– Note: The upper layers will request the establishment of a signalling connection and the transmission of the paging response in the initial NAS message. This results in the implicit establishment of the GA-RRC connection (i.e., the GA-RRC sub-layer entity in the MS enters the GA-RRC CONNECTED state) and the transmission of the paging response from the MS to the GANC in the GA-RRC INITIAL DIRECT TRANSFER message, as shown in Figure 8a.3.1.

– if timer TU5908 is active for the domain:

– ignore the GA-RRC PAGING REQUEST message, and

– continue with the ongoing procedure as if the GA-RRC PAGING REQUEST was not received.

Reference(s)

3GPP TS 44.318 subclause 8a.3.2

84.4.4.2.2 Test purpose

To verify that MS discards the received GA-RRC PAGING REQUEST message (indicating PS domain page) if timer TU5908 is active for the PS domain.

84.4.4.2.3 Method of test

Initial Conditions

System Simulator:

– 1 GAN cell, default parameters

Mobile Station:

– MS in GA-RRC-IDLE state for PS domain in service of GAN cell

Foreseen Final State of the MS

MS in GA-RRC- IDLE state for PS domain.

Test Procedure

MS is made to initiate GA-RRC connection for PS domain. MS sends GA-RRC REQUEST message and activates timer TU5908. The SS initiates paging procedure by sending GA-RRC PAGING REQUEST message to the MS when TU5908 is active in MS. MS discards the received GA-RRC PAGING REQUEST message. After TU5908 expiry the SS sends GA-RRC PAGING REQUEST to verify that MS in GA-RRC-IDLE state. MS may answer by sending GA-RRC INITIAL DIRECT TRANSFER or re-establish the GA-RRC connection by re-sending GA-RRC REQUEST message.

Specific test parameters

Maximum Duration of Test

1 min.

Expected Sequence

Step

Direction

Message

Comment

MS

SS

1

MS

MS is made to initiate GA-RRC connection for PS domain

2

GA-RRC REQUEST

IE ‘CN Domain Identity’ indicates PS domain

MS activates TU5908 for PS domain

3

GA-RRC PAGING REQUEST

Valid identity of the MS (‘TMSI’/’IMSI’), sent before TU5908 expiry

IE ‘CN Domain Identity’ indicates PS domain

4

MS

MS discards GA-RRC PAGING REQUEST message

5

SS

SS waits for TU5908 to expire. The MS may resend GA-RRC REQUEST after the expiry of TU5908.

The following steps are executed only if no GA-RRC REQUEST is received from the MS.

6

GA-RRC PAGING REQUEST

Valid identity of the MS (‘TMSI’/’IMSI’)

IE ‘CN Domain Identity’ indicates PS domain

7

GA-RRC INITIAL DIRECT TRANSFER

IE ‘L3 Message’ contains Paging Response

IE ‘CN Domain Identity’ indicates PS domain

MS enters GA-RRC-CONNECTED state for PS domain

8

GA-RRC RELEASE

IE ‘GA-RRC Cause’ = #83

IE ‘CN Domain Identity’ indicates PS domain

9

GA-RRC RELEASE COMPLETE

IE ‘CN Domain Identity’ indicates PS domain

MS enters GA-RRC-IDLE state for PS domain

84.4.4.3 Paging for PS domain / negative cases / MS receives GA-RRC PAGING REQUEST when in GA-RRC-CONNECTED state

84.4.4.3.1 Conformance requirement

If the MS receives a GA-RRC PAGING REQUEST message and the GA-RRC sublayer entity in the MS is in GA-RRC-CONNECTED state for the indicated domain or the MS is in the GA-RC-REGISTERED state but in GERAN/UTRAN mode, the MS shall:

– ignore the GA-RRC PAGING REQUEST message, and

– continue with any ongoing procedure as if the GA-RRC PAGING REQUEST was not received.

Reference(s)

3GPP TS 44.318 subclause 8a.3.3

84.4.4.3.2 Test purpose

To verify that MS ignores the GA-RRC PAGING REQUEST and continues with any ongoing procedure as if the GA-RRC PAGING REQUEST was not received, if MS receives GA-RRC PAGING REQUEST indicating PS domain when MS is in GA-RRC-CONNECTED state for the PS domain.

84.4.4.3.3 Method of test

Initial Conditions

System Simulator:

– 1 GAN cell, default parameters

Mobile Station:

– MS in GA-RRC-CONNECTED state for PS domain in service of GAN cell.

Foreseen Final State of the MS

MS in GA-RRC-IDLE state for PS domain in service of GAN cell.

Test Procedure

The MS is in GA-RRC-CONNECTED state for PS domain in service of GAN cell. The SS initiates paging procedure by sending GA-RRC PAGING REQUEST message to the MS. The MS ignores the GA-RRC PAGING REQUEST and continues with any ongoing procedure as if the GA-RRC PAGING REQUEST was not received. After 10s the SS sends GA-RRC RELEASE to verify that MS in GA-RRC-CONNECTED state. MS answers by sending GA-RRC RELEASE COMPLETE.

Specific test parameters

Maximum Duration of Test

1 min.

Expected Sequence

Step

Direction

Message

Comment

MS

SS

1

MS

MS in GA-RRC-CONNECTED state for PS domain with ongoing procedure

2

GA-RRC PAGING REQUEST

Valid identity of the MS (‘TMSI’/’IMSI’)

IE ‘CN Domain Identity’ indicates PS domain

3

MS

MS ignores the GA-RRC PAGING REQUEST and continues with ongoing procedure

4

SS

SS waits 10s for response

5

GA-RRC RELEASE

IE ‘GA-RRC Cause’ = #83

IE ‘CN Domain Identity’ indicates PS domain

6

GA-RRC RELEASE COMPLETE

IE ‘CN Domain Identity’ indicates PS domain

MS enters GA-RRC-IDLE state for PS domain

84.4.4.4 Paging for PS domain / negative cases / MS receives GA-RRC PAGING REQUEST when in GA-RC REGISTERED state

84.4.4.4.1 Conformance requirement

If the MS receives a GA-RRC PAGING REQUEST message and the GA-RRC sublayer entity in the MS is in GA-RRC-CONNECTED state for the indicated domain or the MS is in the GA-RC-REGISTERED state but in GERAN/UTRAN mode, the MS shall:

– ignore the GA-RRC PAGING REQUEST message, and

– continue with any ongoing procedure as if the GA-RRC PAGING REQUEST was not received.

Reference(s)

3GPP TS 44.318 subclause 8a.3.3

84.4.4.4.2 Test purpose

To verify that MS ignores the GA-RRC PAGING REQUEST and continues with any ongoing procedure as if the GA-RRC PAGING REQUEST was not received, if MS receives GA-RRC PAGING REQUEST when MS is in GA-RC-REGISTERED state but in GERAN/UTRAN mode.

84.4.4.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-RRC-IDLE state for the PS domain.

Test Procedure

MS is camped on a GERAN cell, voice call activated and in GA-RC-REGISTERED state. The SS initiates PS domain paging procedure by sending GA-RRC PAGING REQUEST message to the MS. The MS ignores the GA-RRC PAGING REQUEST and continues with any ongoing procedure as if the GA-RRC PAGING REQUEST was not received. After 10s, the voice call is deactivated to switch the serving RR entity to GA-RRC. The SS waits 30 seconds to ensure that the MS enters the GA-RRC-IDLE state (PS domain) and sends GA-RRC PAGING REQUEST (PS domain) to verify that MS in GA-RRC-IDLE state. MS answers by sending GA-RRC INITIAL DIRECT TRANSFER (PS domain) message containing the page 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-RRC PAGING REQUEST

Valid identity of the MS (‘TMSI’/’IMSI’)

IE ‘CN Domain Identity’ indicates PS domain

3

MS

MS ignores the GA-RRC 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-RRC-IDLE state.

6

SS

Wait 30 seconds to ensure that the MS enters GA-RRC-IDLE state.

7

GA-RRC PAGING REQUEST

Valid identity of the MS (‘TMSI’/’IMSI’)

IE ‘CN Domain Identity’ indicates PS domain

8

GA-RRC INITIAL DIRECT TRANSFER

IE ‘L3 Message’ contains Paging Response

IE ‘CN Domain Identity’ indicates PS domain

MS enters GA-RRC-CONNECTED state for PS domain

9

GA-RRC RELEASE

IE ‘GA-RRC Cause’ = #83

IE ‘CN Domain Identity’ indicates PS domain

10

GA-RRC RELEASE COMPLETE

IE ‘CN Domain Identity’ indicates PS domain

MS enters GA-RRC-IDLE state for PS domain

84.5 Traffic Channel assignment

84.5.1 CS Traffic Channel assignment / successful cases

84.5.1.1 CS Traffic Channel assignment and Release

84.5.1.1.1 Conformance requirement

3GPP TS 44.318 subclause 8a.4.1.2:

The MS shall act on the received GA-RRC ACTIVATE CHANNEL message indicating the CS domain as follows:

– for each CTC specified in the IE "CTC Activation List":

– store the RAB ID;

– if the IE "RAB Configuration" indicates that the CTC is for AMR or AMR-WB speech, use the format specified in Annex A.1 and Annex D to code and decode the RTP packets;

– if the IE "RAB Configuration" indicates that the CTC is for circuit switched data, use the format specified in Annex A.2 to code and decode the RTP packets;

– use the value indicated by the IE "Sample Size" as the minimum sample size for the coding and decoding of the RTP packets, if the MS is not able to use the indicated value. If the circuit transport channel is for AMR or AMR-WB speech with RTP redundancy, the sample size is defined as the size of the new speech sample in each RTP packet, not including any redundant speech samples;

– configure the uplink RTP packets to be transmitted to the UDP port and IP address identified by the IE "RTP UDP Port" and the IE "GANC IP address", respectively;

– use the Payload Type included in the IE "Payload Type" for the PT field in the RTP header for the RTP packets;

– if received, use the configuration included in the IE "Multi-rate Configuration 2" for the circuit transport channel that is for AMR or AMR-WB speech;

– if received, use the configuration included in the IE "RTP Redundancy Configuration" for the circuit transport channel that is for AMR or AMR-WB speech. The redundancy policy is defined for each of the AMR modes specified in the IE "Multi-rate Configuration 2". 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, pass the contents of the NAS Synchronisation Indicator to upper layers.

On completing the above procedure, the MS shall:

– start timer TU5911 for the CS domain;

– transmit a GA-RRC ACTIVATE CHANNEL ACK message including the IE "CN Domain Identity" and the IE "CTC Activation Ack List". For each CTC specified in the IE "CTC Activation Ack List":

– include the IE "RAB ID" for the CTC with the same value as received in the GA-RRC ACTIVATE CHANNEL message in the IE "RAB ID";

– include the IE "GA-RRC Cause" indicating either success (i.e., value ‘0’) or a failure cause value;

– for each CTC that is successfully configured (i.e., GA-RRC Cause value is ‘0’):

– include the allocated UDP port number in the IE "RTP UDP Port" for the downlink RTP packets to be sent from the GANC to the MS;

– include the selected RTP sample size, to be used for uplink and downlink RTP packets, in the IE "Sample Size";

– include the Payload Type in the IE "Payload Type";

– if the IE "RTCP UDP Port" was received in the GA-RRC 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 packets to be sent from the GANC to the MS.

3GPP TS 44.318 subclause 8a.4.1.4:

On reception of the GA-RRC ACTIVATE CHANNEL COMPLETE message indicating the CS domain, the MS shall stop timer TU5911 for the CS domain and consider the successfully activated CTC(s) to be 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 for each active CTC. During periods of discontinuous transmission (DTX), each RTP frame transmitted by the MS shall bear a format in the AMR/AMR-WB payload Table of Contents that either (a) omits all NO_DATA indications and contains only the next AMR speech or SID frame that is available, or (b) includes a single NO_DATA frame should no AMR speech or SID frame become available for 480 ms. The RTP timestamp shall indicate the time of that speech or SID or NO_DATA frame. See Section A.1.2 of Annex A for examples.

3GPP TS 44.318 subclause 8a.5.1:

If the MS needs to release the GA-RRC connection and signalling connection to a particular CN domain, it shall send the GA-RRC RELEASE REQUEST message to the GANC and start timer TU5909 for the domain. The MS shall include the IE "CN Domain Identity" and the IE "GA-RRC Cause". The GA-RRC Cause value shall be one of the following:

#40: UE generated signalling connection release

#115: unspecified failure

Reference(s)

3GPP TS 44.318 subclauses 8a.4.1.2 / 8a.4.1.4/ 8a.5.1

84.5.1.1.2 Test purpose

To verify that MS is able to establish a CS domain traffic channel.

The MS initiates the release the GA-RRC connection (CS domain) by sending GA-RRC CLEAR REQUEST to the SS. The MS enters GA-RRC-IDLE state and releases all GA-RRC and any traffic channel resources (CS domain).

84.5.1.1.3 Method of test

Initial Conditions

System Simulator:

– 1 GAN cell, default parameters

Mobile Station:

– MS in GA-RRC-CONNECTED state (CS domain) in service of GAN cell and a voice call is ongoing.

Foreseen Final State of the MS

MS in GA-RRC-IDLE state (CS domain) in service of GAN cell.

Test Procedure

A voice call is ongoing. The SS configures a CS traffic channel by transmitting GA-RRC ACTIVATE CHANNEL (CS domain) to the MS. MS responses by transmitting a GA-RRC ACTIVATE CHANNEL ACK including 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-RRC 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-RRC DL DIRECT TRANSFER message (Release) and receiving GA-RRC UL DIRECT TRANSFER (Release Complete) message. Therefore, the MS will send GA-RRC RELEASE REQUEST to release the CS domain connection.

Specific test parameters

Maximum Duration of Test

1 min.

Expected Sequence

Step

Direction

Message

Comment

MS

SS

1

MS

MS in GA-RRC-CONNECTED state (CS domain), voice call is ongoing.

2

GA-RRC ACTIVATE CHANNEL

For the (single) CTC specified in the IE ‘CTC Activation List’: IE ‘RAB ID’, IE ‘RAB Configuration’, IE ‘Sample Size’, IE ‘UDP Port’, IE ‘IP address’, IE ‘Payload Type’, IE ‘Multi-rate Configuration 2’, optional IE ‘RTP Redundancy Configuration ‘,optional IE ‘RTCP UDP Port’

3

GA-RRC ACTIVATE CHANNEL ACK

For the (single) CTC specified in the IE ‘CTC Activation Ack List’: IE ‘RAB ID’, IE ‘GA-RRC Cause’ (indicating value #0), IE ‘UDP Port’, IE ‘Sample Size’, IE ‘Payload Type’, optional IE ‘RTCP UDP Port’

4

GA-RRC ACTIVATE CHANNEL COMPLETE

5

Verify that the MS sends at least one RTP frame

6

GA-RRC DL DIRECT TRANSFER (Release)

7

GA-RRC UL DIRECT TRANSFER (Release Complete)

Eventual CC L3 messages are ignored.

8

GA-RRC RELEASE REQUEST

IE ‘CN Domain Identity’ indicates CS domain

IE ‘GA-RRC Cause’ indicates #40

84.5.2 CS Traffic Channel assignment / negative cases

84.5.2.1 MS fails to establish the CS traffic channel

84.5.2.1.1 Conformance requirement

3GPP TS 44.318 subclause 8a.4.1.2:

The MS shall act on the received GA-RRC ACTIVATE CHANNEL message indicating the CS domain as follows:

– for each CTC specified in the IE "CTC Activation List":

– store the RAB ID;

– if the IE "RAB Configuration" indicates that the CTC is for AMR or AMR-WB speech, use the format specified in Annex A.1 and Annex D to code and decode the RTP packets;

– if the IE "RAB Configuration" indicates that the CTC is for circuit switched data, use the format specified in Annex A.2 to code and decode the RTP packets;

– use the value indicated by the IE "Sample Size" as the minimum sample size for the coding and decoding of the RTP packets, if the MS is not able to use the indicated value. If the circuit transport channel is for AMR or AMR-WB speech with RTP redundancy, the sample size is defined as the size of the new speech sample in each RTP packet, not including any redundant speech samples;

– configure the uplink RTP packets to be transmitted to the UDP port and IP address identified by the IE "RTP UDP Port" and the IE "GANC IP address", respectively;

– use the Payload Type included in the IE "Payload Type" for the PT field in the RTP header for the RTP packets;

– if received, use the configuration included in the IE "Multi-rate Configuration 2" for the circuit transport channel that is for AMR or AMR-WB speech;

– if received, use the configuration included in the IE "RTP Redundancy Configuration" for the circuit transport channel that is for AMR or AMR-WB speech. The redundancy policy is defined for each of the AMR modes specified in the IE "Multi-rate Configuration 2". 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, pass the contents of the NAS Synchronisation Indicator to upper layers.

On completing the above procedure, the MS shall:

– start timer TU5911 for the CS domain;

– transmit a GA-RRC ACTIVATE CHANNEL ACK message including the IE "CN Domain Identity" and the IE "CTC Activation Ack List". For each CTC specified in the IE "CTC Activation Ack List":

– include the IE "RAB ID" for the CTC with the same value as received in the GA-RRC ACTIVATE CHANNEL message in the IE "RAB ID";

– include the IE "GA-RRC Cause" indicating either success (i.e., value ‘0’) or a failure cause value;

– for each CTC that is successfully configured (i.e., GA-RRC Cause value is ‘0’):

– include the allocated UDP port number in the IE "RTP UDP Port" for the downlink RTP packets to be sent from the GANC to the MS;

– include the selected RTP sample size, to be used for uplink and downlink RTP packets, in the IE "Sample Size";

– include the Payload Type in the IE "Payload Type";

– if the IE "RTCP UDP Port" was received in the GA-RRC 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 packets to be sent from the GANC to the MS.

Reference(s)

3GPP TS 44.318 subclauses 8a.4.1.2

84.5.2.1.2 Test purpose

To verify that if MS fails to establish the traffic channel, it transmits a GA-RRC ACTIVATE CHANNEL ACK message including the reason for the failure.

84.5.2.1.3 Method of test

Initial Conditions

System Simulator:

– 1 GAN cell, default parameters

Mobile Station:

– MS in GA-RRC-CONNECTED state (CS domain) in service of GAN cell and a voice call is ongoing.

Foreseen Final State of the MS

MS in GA-RRC-IDLE state (CS domain) in service of GAN cell.

Test Procedure

A CS domain voice call is ongoing. The SS configures a traffic channel by transmitting corrupted GA-RRC ACTIVATE CHANNEL to the MS. In the corrupted GA-RRC ACTIVATE CHANNEL message “Sample Size” octet 3 is set to “1” (1ms), which is an undefined value.

MS fails to establish the traffic channel and transmits a GA-RRC ACTIVATE CHANNEL ACK message including the reason for the failure.

Specific test parameters

Maximum Duration of Test

1 min.

Expected Sequence

Step

Direction

Message

Comment

MS

SS

1

MS

MS in GA-RRC-CONNECTED state (CS domain), voice call is ongoing

2

GA-RRC 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-RRC ACTIVATE CHANNEL ACK

For the (single) CTC specified in the IE ‘CTC Activation Ack List’: IE ‘RAB ID’, IE ‘GA-RRC Cause’ indicates a value other than #0 (e.g., ‘Invalid RAB Parameters Value’ #19).

5

GA-RRC RELEASE

IE ‘GA-RRC Cause’ = #83

IE ‘CN Domain Identity’ indicates CS domain

6

GA-RRC RELEASE COMPLETE

IE ‘CN Domain Identity’ indicates CS domain

MS enters GA-RRC-IDLE state for CS domain

84.5.3 PS Traffic Channel assignment / successful cases

84.5.3.1 PS Traffic Channel assignment and Release

84.5.3.1.1 Conformance requirement

3GPP TS 44.318 subclause 8a.4.2.2:

The MS shall act on the received GA-RRC ACTIVATE CHANNEL message indicating the PS domain as follows:

– for each PTC specified in the IE "PTC Activation List":

– store the RAB ID;

– allocate local PTC resources based on the values in the IE "RAB Configuration";

– use the TEID value included in the IE "GANC TEID" for the TEID field in the GA-RRC PDU messages to be sent to the GANC;

– use the TEID value included in the IE "MS TEID" to verify the TEID field in the GA-RRC PDU messages to be received from the GANC;

– configure the uplink GA-RRC PDU messages to be transmitted to the UDP port and IP address identified by the IE "GANC UDP Port" and the IE "GANC IP address", respectively.

On completing the above procedure, the MS shall:

– start timer TU5911 for the PS domain;

– transmit a GA-RRC ACTIVATE CHANNEL ACK message including the IE "CN Domain Identity" and the IE "PTC Activation Ack List". For each PTC specified in the IE "PTC Activation Ack List":

– include the IE "RAB ID" for the PTC with the same value as received in the GA-RRC ACTIVATE CHANNEL message in the IE "RAB ID";

– include the IE "GA-RRC Cause" indicating either success (i.e., value ‘0’) or a failure cause value;

– for each PTC that is successfully configured (i.e., GA-RRC Cause value is ‘0’):

– include the allocated UDP port number in the IE "MS UDP Port" for the downlink GA-RRC PDU messages to be sent from the GANC to the MS.

3GPP TS 44.318 subclause 8a.4.2.4:

On reception of the GA-RRC ACTIVATE CHANNEL COMPLETE message indicating the PS domain, the MS shall stop timer TU5911 for the PS domain, and start timer TU4001 for each of the successfully activated PTC(s) which are now available for use by upper layers.

3GPP TS 44.318 subclause 8a.5.1:

If the MS needs to release the GA-RRC connection and signalling connection to a particular CN domain, it shall send the GA-RRC RELEASE REQUEST message to the GANC and start timer TU5909 for the domain. The MS shall include the IE "CN Domain Identity" and the IE "GA-RRC Cause". The GA-RRC Cause value shall be one of the following:

#40: UE generated signalling connection release

#115: unspecified failure

Reference(s)

3GPP TS 44.318 subclauses 8a.4.2.2 / 8a.4.2.4/ 8a.5.1

84.5.3.1.2 Test purpose

To verify that MS is able to establish a PS domain traffic channel.

The MS initiates the release the GA-RRC connection (PS domain) by sending GA-RRC RELEASE REQUEST to the SS. The MS enters GA-RRC-IDLE state and releases all GA-RRC and any traffic channel resources (PS domain).

84.5.3.1.3 Method of test

Initial Conditions

System Simulator:

– 1 GAN cell, default parameters

Mobile Station:

– MS in GA-RRC-CONNECTED state (PS domain) in service of GAN cell.

Foreseen Final State of the MS

MS in GA-RRC-IDLE state (PS domain) in service of GAN cell.

Test Procedure

A PS session is ongoing. The SS configures a PS traffic channel by transmitting GA-RRC ACTIVATE CHANNEL (PS domain) to the MS. MS responses by transmitting a GA-RRC ACTIVATE CHANNEL ACK and configures the uplink GA-RRC PDU messages to be transmitted to the UDP port and IP address identified by the IE "GANC UDP Port" and the IE "GANC IP address", respectively. Then the SS configures itself for transmission of downlink GA-RRC PDU messages to be transmitted to the UDP port identified by the IE "MS UDP Port" and the IE "GANC IP address", and transmits a GA-RRC ACTIVATE CHANNEL COMPLETE message to the MS. The SS releases the PS session by sending GA-RRC DL DIRECT TRANSFER message (Deactivate PDP Context Request) and receiving GA-RRC UL DIRECT TRANSFER (Deactivate PDP Context Accept) message. Therefore, the MS will send GA-RRC RELEASE REQUEST to release the PS domain connection.

Specific test parameters

Maximum Duration of Test

1 min.

Expected Sequence

Step

Direction

Message

Comment

MS

SS

1

MS

MS in GA-RRC-CONNECTED state (PS domain).

2

GA-RRC ACTIVATE CHANNEL

For the (single) PTC specified in the IE ‘PTC Activation List’: IE ‘RAB ID’, IE ‘RAB Configuration’, IE ‘GANC TEID’, IE ‘MS TEID’, IE ‘GANC UDP Port’, IE ‘GANC IP address’.

3

GA-RRC ACTIVATE CHANNEL ACK

For the (single) PTC specified in the IE ‘PTC Activation Ack List’: IE ‘RAB ID’, IE ‘GA-RRC Cause’ (indicating value #0), IE ‘MS UDP Port’.

4

GA-RRC ACTIVATE CHANNEL COMPLETE

5

Verify that the MS sends at least one GA-RRC PDU message

6

GA-RRC DL DIRECT TRANSFER (Deactivate PDP Context Request)

7

GA-RRC UL DIRECT TRANSFER (Deactivate PDP Context Accept)

8

GA-RRC RELEASE REQUEST

IE ‘CN Domain Identity’ indicates PS domain

IE ‘GA-RRC Cause’ indicates #40

84.5.4 PS Traffic Channel assignment / negative cases

84.5.4.1 MS fails to establish the PS traffic channel

84.5.4.1.1 Conformance requirement

3GPP TS 44.318 subclause 8a.4.2.2:

The MS shall act on the received GA-RRC ACTIVATE CHANNEL message indicating the PS domain as follows:

– for each PTC specified in the IE "PTC Activation List":

– store the RAB ID;

– allocate local PTC resources based on the values in the IE "RAB Configuration";

– use the TEID value included in the IE "GANC TEID" for the TEID field in the GA-RRC PDU messages to be sent to the GANC;

– use the TEID value included in the IE "MS TEID" to verify the TEID field in the GA-RRC PDU messages to be received from the GANC;

– configure the uplink GA-RRC PDU messages to be transmitted to the UDP port and IP address identified by the IE "GANC UDP Port" and the IE "GANC IP address", respectively.

On completing the above procedure, the MS shall:

– start timer TU5911 for the PS domain;

– transmit a GA-RRC ACTIVATE CHANNEL ACK message including the IE "CN Domain Identity" and the IE "PTC Activation Ack List". For each PTC specified in the IE "PTC Activation Ack List":

– include the IE "RAB ID" for the PTC with the same value as received in the GA-RRC ACTIVATE CHANNEL message in the IE "RAB ID";

– include the IE "GA-RRC Cause" indicating either success (i.e., value ‘0’) or a failure cause value;

– for each PTC that is successfully configured (i.e., GA-RRC Cause value is ‘0’):

– include the allocated UDP port number in the IE "MS UDP Port" for the downlink GA-RRC PDU messages to be sent from the GANC to the MS.

3GPP TS 44.318 subclause 8a.4.2.4:

On reception of the GA-RRC ACTIVATE CHANNEL COMPLETE message indicating the PS domain, the MS shall stop timer TU5911 for the PS domain, and start timer TU4001 for each of the successfully activated PTC(s) which are now available for use by upper layers.

3GPP TS 44.318 subclause 8a.5.1:

If the MS needs to release the GA-RRC connection and signalling connection to a particular CN domain, it shall send the GA-RRC RELEASE REQUEST message to the GANC and start timer TU5909 for the domain. The MS shall include the IE "CN Domain Identity" and the IE "GA-RRC Cause". The GA-RRC Cause value shall be one of the following:

#40: UE generated signalling connection release

#115: unspecified failure

Reference(s)

3GPP TS 44.318 subclauses 8a.4.2.2 / 8a.4.2.4/ 8a.5.1

84.5.4.1.2 Test purpose

To verify that if MS fails to establish the PTC, it transmits a GA-RRC ACTIVATE CHANNEL ACK message including the reason for the failure.

84.5.4.1.3 Method of test

Initial Conditions

System Simulator:

– 1 GAN cell, default parameters

Mobile Station:

– MS in GA-RRC-CONNECTED state (PS domain) in service of GAN cell.

Foreseen Final State of the MS

MS in GA-RRC-IDLE state (PS domain) in service of GAN cell.

Test Procedure

A PS domain voice call is ongoing. The SS configures a PTC by transmitting corrupted GA-RRC ACTIVATE CHANNEL to the MS. In the corrupted GA-RRC ACTIVATE CHANNEL message the “RAB Configuration” IE indicates Interactive traffic class and the Guaranteed DL Bit Rate and Guaranteed UL Bit Rate fields are populated (which is not a valid combination according to TS 44.318, sub-clause 11.2.103).

MS fails to establish the traffic channel and transmits a GA-RRC ACTIVATE CHANNEL ACK message including the reason for the failure.

Specific test parameters

Maximum Duration of Test

1 min.

Expected Sequence

Step

Direction

Message

Comment

MS

SS

1

MS

MS in GA-RRC-CONNECTED state (PS domain).

2

GA-RRC ACTIVATE CHANNEL

For the (single) PTC specified in the IE ‘PTC Activation List’: IE ‘RAB ID’, IE ‘RAB Configuration’, IE ‘GANC TEID’, IE ‘MS TEID’, IE ‘GANC UDP Port’, IE ‘GANC IP address’. IE ‘RAB Configuration’ is misconfigured.

3

GA-RRC ACTIVATE CHANNEL ACK

For the (single) PTC specified in the IE ‘PTC Activation Ack List’: IE ‘RAB ID’, IE ‘GA-RRC Cause’ (indicating value other than #0; e.g., ‘Invalid RAB Parameters Value’ #19).

4

GA-RRC DL DIRECT TRANSFER (Deactivate PDP Context Request)

5

GA-RRC UL DIRECT TRANSFER (Deactivate PDP Context Accept)

6

GA-RRC RELEASE REQUEST

IE ‘CN Domain Identity’ indicates PS domain

IE ‘GA-RRC Cause’ indicates #40

84.6 Release of GA-RRC

FFS

84.7 Void

84.8 Void

84.9 Security Mode Control Procedure

84.9.1 Security Mode Control Procedure / successful cases

84.9.1.1 Security Mode Control Procedure (CS domain)

84.9.1.1.1 Conformance requirement

3GPP TS 44.318 subclause 8a.6.1:

The GANC initiates the security mode control procedure by sending a GA-RRC SECURITY MODE COMMAND message to the MS. This message includes the IE "Selected Integrity Protection Algorithm", the IE "Selected Encryption Algorithm" (optional), and the IE "Random Number". The GANC selects the algorithms based on the permitted algorithms received from the CN and the MS security capabilities indicated in the IE "3G Security Capability" received from the MS in the GA-RC REGISTER REQUEST message.

3GPP TS 44.318 subclause 8a.6.2:

Whenever the MS receives a valid GA-RRC SECURITY MODE COMMAND message, it shall, if a (U)SIM is present and considered valid and the key set identifier (KSI) stored on the (U)SIM indicates that an integrity key and cipher key are available for the domain indicated in the IE "CN Domain Identity", store the selected integrity protection algorithm and (if received) the selected encryption algorithm for possible future use after a handover from GAN Iu mode to UTRAN during the same upper layer transaction. If handover from GAN Iu mode to UTRAN occurs, encryption is enabled if the IE “Selected Encryption Algorithm” is present in the message and disabled otherwise.

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 the integrity key (IK) for the domain indicated in the IE "CN Domain Identity" used as the authentication key.

In the formulas above, the "|" character denotes concatenation. RAND is the 16-octet random number received from the GANC in the GA-RRC SECURITY MODE COMMAND message. IMSI is the MS IMSI, in the same format as defined for the Mobile Identity IE as defined in [8]; 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 IK key is the IK that has been derived during the last authentication for the domain indicated in the IE "CN Domain Identity". The length of the MAC is 12 octets.

When the appropriate action on the GA-RRC SECURITY MODE COMMAND message has been taken, the MS sends a GA-RRC SECURITY MODE COMPLETE message to the GANC. The MS includes the calculated MAC value in the IE "Ciphering Command MAC".

Reference(s)

3GPP TS 44.318 sub-clause 8a.6.1 and 8a.6.2.

84.9.1.1.2 Test purpose

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

84.9.1.1.3 Method of test

Initial conditions

System Simulator:

– 1 GAN cell, default parameter

Mobile Station:

– MS in state GA-RRC-CONNECTED (CS domain)

Foreseen final state of the MS

– MS in GA-RRC IDLE state.

Test procedure

The SS sends the GA-RRC SECURITY MODE COMMAND message indicating the CS domain. The MS replies with the GA-RRC SECURITY MODE COMPLETE message indicating the CS domain. SS checks 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-RRC SECURITY MODE COMMAND

IE ‘CN Domain Identity’ indicates CS domain

2

GA-RRC SECURITY MODE COMPLETE

IE ‘CN Domain Identity’ indicates CS domain

SS checks that the MAC is correct

3

GA-RRC RELEASE

IE ‘GA-RRC Cause’ = #83

IE ‘CN Domain Identity’ indicates CS domain

4

GA-RRC RELEASE COMPLETE

IE ‘CN Domain Identity’ indicates CS domain

MS enters GA-RRC-IDLE state for CS domain

84.9.1.2 Security Mode Control Procedure (PS domain)

84.9.1.2.1 Conformance requirement

3GPP TS 44.318 subclause 8a.6.1:

The GANC initiates the security mode control procedure by sending a GA-RRC SECURITY MODE COMMAND message to the MS. This message includes the IE "Selected Integrity Protection Algorithm", the IE "Selected Encryption Algorithm" (optional), and the IE "Random Number". The GANC selects the algorithms based on the permitted algorithms received from the CN and the MS security capabilities indicated in the IE "3G Security Capability" received from the MS in the GA-RC REGISTER REQUEST message.

3GPP TS 44.318 subclause 8a.6.2:

Whenever the MS receives a valid GA-RRC SECURITY MODE COMMAND message, it shall, if a (U)SIM is present and considered valid and the key set identifier (KSI) stored on the (U)SIM indicates that an integrity key and cipher key are available for the domain indicated in the IE "CN Domain Identity", store the selected integrity protection algorithm and (if received) the selected encryption algorithm for possible future use after a handover from GAN Iu mode to UTRAN during the same upper layer transaction. If handover from GAN Iu mode to UTRAN occurs, encryption is enabled if the IE “Selected Encryption Algorithm” is present in the message and disabled otherwise.

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 the integrity key (IK) for the domain indicated in the IE "CN Domain Identity" used as the authentication key.

In the formulas above, the "|" character denotes concatenation. RAND is the 16-octet random number received from the GANC in the GA-RRC SECURITY MODE COMMAND message. IMSI is the MS IMSI, in the same format as defined for the Mobile Identity IE as defined in [8]; 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 IK key is the IK that has been derived during the last authentication for the domain indicated in the IE "CN Domain Identity". The length of the MAC is 12 octets.

When the appropriate action on the GA-RRC SECURITY MODE COMMAND message has been taken, the MS sends a GA-RRC SECURITY MODE COMPLETE message to the GANC. The MS includes the calculated MAC value in the IE "Ciphering Command MAC".

Reference(s)

3GPP TS 44.318 sub-clause 8a.6.1 and 8a.6.2.

84.9.1.2.2 Test purpose

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

84.9.1.2.3 Method of test

Initial conditions

System Simulator:

– 1 GAN cell, default parameter

Mobile Station:

– MS in state GA-RRC-CONNECTED (PS domain)

Foreseen final state of the MS

– MS in GA-RRC IDLE state (PS domain)

Test procedure

The SS sends the GA-RRC SECURITY MODE COMMAND message indicating the PS domain. The MS replies with the GA-RRC SECURITY MODE COMPLETE message indicating the PS domain. SS checks 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-RRC SECURITY MODE COMMAND

IE ‘CN Domain Identity’ indicates PS domain

2

GA-RRC SECURITY MODE COMPLETE

IE ‘CN Domain Identity’ indicates PS domain

SS checks that the MAC is correct

3

GA-RRC RELEASE

IE ‘CN Domain Identity’ indicates PS domain

IE ‘RR cause’ #0

4

GA-RRC RELEASE COMPLETE

IE ‘CN Domain Identity’ indicates PS domain

MS enters GA-RRC-IDLE state (PS domain)

84.10 Channel modify procedure

84.10.1 CS channel modify procedure / successful cases

84.10.1.1 CS channel modify / successful case

84.10.1.1.1 Conformance requirement

3GPP TS 44.318 subclause 8a.7.1.1:

The GANC initiates the circuit transport channel (CTC) modification procedure when it determines that one or more active CTCs require modification; e.g., based on information received from the MSC in the RAB Assignment Request message or based on local GANC logic.

The following CTC parameters may be modified:

– RAB Configuration

– Sample Size

– GANC RTP UDP Port

– GANC IP Address

– Multi-rate Configuration 2

– RTP Redundancy Configuration

– GANC RTCP UDP Port

– NAS Synchronisation Indicator

The GANC only includes the IEs which specify modifications to the existing CTC parameters.

One or more CTCs may be modified using a single instance of the channel modification procedure; however, it is not possible to modify both circuit and packet transport channels using a single instance of the channel modification procedure.

The GANC begins the modification of the CTC(s) by transmitting the GA-RRC MODIFY CHANNEL message to the MS. The message contains the IE "CN Domain Identity" (indicating CS domain) and IE "CTC Modification List" which includes the parameters necessary to describe the modifications to each circuit transport channel.

3GPP TS 44.318 subclause 8a.7.1.2:

On receipt of the GA-RRC MODIFY CHANNEL message indicating the CS domain, the MS shall process the specified CTC modifications.

On completion of the modification of the CTC(s), the MS shall:

– transmit a GA-RRC MODIFY CHANNEL ACK message including the IE "CN Domain Identity" and the IE "CTC Modification Ack List". For each CTC specified in the IE "CTC Modification Ack List":

– include the IE "RAB ID" for the CTC with the same value as received in the GA-RRC MODIFY CHANNEL message in the IE "RAB ID";

– include the IE "GA-RRC Cause" indicating either success (i.e., value ‘0’) or a failure cause value;

– for each CTC that is successfully modified (i.e., GA-RRC Cause value is ‘0’):

– include the modified parameter values currently used by the MS.

When the MS has sent the GA-RRC MODIFY CHANNEL ACK message, it shall start transmitting RTP packets based on the successful parameter modifications. The MS shall be able to receive RTP packets with the old parameters until the MS determines that the first RTP packet using the new parameters has been received.

Reference(s)

3GPP TS 44.318 subclauses 8a.7.1.1, 8a.7.1.2

84.10.1.1.2 Test purpose

To verify that MS is able to change active CTC parameters if requested.

84.10.1.1.3 Method of test

Initial Conditions

System Simulator:

– 1 GAN cell, default parameters

Mobile Station:

– MS in GA-RRC-CONNECTED state (CS domain) in service of GAN cell, voice call activated

Foreseen Final State of the MS

MS in GA-RRC-IDLE state (CS domain)

Test Procedure

The MS is in GA-RRC-CONNECTED state (CS domain) in service of GAN cell, voice call activated. SS sends GA-RRC MODIFY CHANNEL message to change the active sample size for the CTC. The MS sets the sample size for the active CTC and then replies by a GA-RRC MODIFY CHANNEL ACK message indicating the modified parameter.

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-RRC MODIFY CHANNEL

IE ‘CN Domain Identity’ indicates CS domain. For the (single) CTC specified in the IE ‘CTC Modification List’: IE ‘RAB ID’, IE ‘Sample Size’ with new sample size value

3

MS

MS sets the different sample size

4

GA-RRC MODIFY CHANNEL ACK

IE ‘CN Domain Identity’ indicates CS domain. For the (single) CTC specified in the IE ‘CTC Modification Ack List’: IE ‘RAB ID’, IE ‘GA-RRC Cause’ (indicating value #0), IE ‘Sample Size’ with new sample size value

5

MS

MS in service voice call activated on GAN cell with different sample size

6

GA-RRC RELEASE

IE ‘GA-RRC Cause’ = #83

IE ‘CN Domain Identity’ indicates CS domain

7

GA-RRC RELEASE COMPLETE

IE ‘CN Domain Identity’ indicates CS domain

MS enters GA-RRC-IDLE state for CS domain

84.10.2 CS channel modify procedure / negative cases

84.10.2.1 CS channel modify requests illegal change to parameter

84.10.2.1.1 Conformance requirement

3GPP TS 44.318 subclause 8a.7.1.1:

The GANC initiates the circuit transport channel (CTC) modification procedure when it determines that one or more active CTCs require modification; e.g., based on information received from the MSC in the RAB Assignment Request message or based on local GANC logic.

The following CTC parameters may be modified:

– RAB Configuration

– Sample Size

– GANC RTP UDP Port

– GANC IP Address

– Multi-rate Configuration 2

– RTP Redundancy Configuration

– GANC RTCP UDP Port

– NAS Synchronisation Indicator

The GANC only includes the IEs which specify modifications to the existing CTC parameters.

One or more CTCs may be modified using a single instance of the channel modification procedure; however, it is not possible to modify both circuit and packet transport channels using a single instance of the channel modification procedure.

The GANC begins the modification of the CTC(s) by transmitting the GA-RRC MODIFY CHANNEL message to the MS. The message contains the IE "CN Domain Identity" (indicating CS domain) and IE "CTC Modification List" which includes the parameters necessary to describe the modifications to each circuit transport channel.

3GPP TS 44.318 subclause 8a.7.1.2:

On receipt of the GA-RRC MODIFY CHANNEL message indicating the CS domain, the MS shall process the specified CTC modifications.

On completion of the modification of the CTC(s), the MS shall:

– transmit a GA-RRC MODIFY CHANNEL ACK message including the IE "CN Domain Identity" and the IE "CTC Modification Ack List". For each CTC specified in the IE "CTC Modification Ack List":

– include the IE "RAB ID" for the CTC with the same value as received in the GA-RRC MODIFY CHANNEL message in the IE "RAB ID";

– include the IE "GA-RRC Cause" indicating either success (i.e., value ‘0’) or a failure cause value;

– for each CTC that is successfully modified (i.e., GA-RRC Cause value is ‘0’):

– include the modified parameter values currently used by the MS.

When the MS has sent the GA-RRC MODIFY CHANNEL ACK message, it shall start transmitting RTP packets based on the successful parameter modifications. The MS shall be able to receive RTP packets with the old parameters until the MS determines that the first RTP packet using the new parameters has been received.

Reference(s)

3GPP TS 44.318 subclauses 8a.7.1.1, 8a.7.1.2

84.10.2.1.2 Test purpose

To verify that the MS does not change the CTC parameters if requested to make an illegal change to a parameter (i.e., to change the Payload Type value).

84.10.2.1.3 Method of test

Initial Conditions

System Simulator:

– 1 GAN cell, default parameters

Mobile Station:

– MS in GA-RRC-CONNECTED state (CS domain) in service of GAN cell, voice call activated

Foreseen Final State of the MS

MS in GA-RRC-IDLE state (CS domain)

Test Procedure

The MS is in GA-RRC-CONNECTED state (CS domain) in service of GAN cell, voice call activated. SS sends GA-RRC MODIFY CHANNEL message to change the Payload Type value. The requested change is not allowed. MS retains the old Payload Type value for the active CTC and then replies by a GA-RRC MODIFY CHANNEL ACK message with a failure indication.

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-RRC MODIFY CHANNEL

IE ‘CN Domain Identity’ indicates CS domain. For the (single) CTC specified in the IE ‘CTC Modification List’: IE ‘RAB ID’, IE ‘Payload Type’ with new value

3

MS

MS retains the old Payload Type value

4

GA-RRC MODIFY CHANNEL ACK

IE ‘CN Domain Identity’ indicates CS domain. For the (single) CTC specified in the IE ‘CTC Modification Ack List’: IE ‘RAB ID’, IE ‘GA-RRC Cause’ (indicating other than value #0; e.g., value #19 indicating invalid RAB parameters value)

5

MS

MS in service voice call activated on GAN cell with old Payload Type value

6

GA-RRC RELEASE

IE ‘GA-RRC Cause’ = #83

IE ‘CN Domain Identity’ indicates CS domain

7

GA-RRC RELEASE COMPLETE

IE ‘CN Domain Identity’ indicates CS domain

MS enters GA-RRC-IDLE state for CS domain

84.10.3 PS channel modify procedure / successful cases

84.10.3.1 PS channel modify / successful case

84.10.3.1.1 Conformance requirement

3GPP TS 44.318 subclause 8a.7.2.1:

The GANC initiates the packet transport channel (PTC) modification procedure when it determines that one or more active PTCs require modification; e.g., based on information received from the SGSN in the RAB Assignment Request message or based on local GANC logic.

The following PTC parameters may be modified:

– RAB Configuration

– GANC UDP Port

– GANC IP Address

The GANC only includes the IEs which specify modifications to the existing PTC parameters.

One or more PTCs may be modified using a single instance of the channel modification procedure; however, it is not possible to modify both circuit and packet transport channels using a single instance of the channel modification procedure.

The GANC begins the modification of the PTC(s) by transmitting the GA-RRC MODIFY CHANNEL message to the MS. The message contains the IE "CN Domain Identity" (indicating PS domain) and IE "PTC Modification List" which includes the parameters necessary to describe the modifications to each packet transport channel.

3GPP TS 44.318 subclause 8a.7.2.2:

On receipt of the GA-RRC MODIFY CHANNEL message indicating the PS domain, the MS shall process the specified PTC modifications.

On completion of the modification of the PTC(s), the MS shall:

– transmit a GA-RRC MODIFY CHANNEL ACK message including the IE "CN Domain Identity" and the IE "PTC Modification Ack List". For each PTC specified in the IE "PTC Modification Ack List":

– include the IE "RAB ID" for the PTC with the same value as received in the GA-RRC MODIFY CHANNEL message in the IE "RAB ID";

– include the IE "GA-RRC Cause" indicating either success (i.e., value ‘0’) or a failure cause value;

– for each PTC that is successfully modified (i.e., GA-RRC Cause value is ‘0’):

– include the modified parameter values currently used by the MS.

When the MS has sent the GA-RRC MODIFY CHANNEL ACK message, it shall start transmitting GA-RRC PDU messages based on the successful parameter modifications. The MS shall be able to receive GA-RRC PDU messages with the old parameters until the MS determines that the first GA-RRC PDU message using the new parameters has been received.

Reference(s)

3GPP TS 44.318 subclauses 8a.7.2.1, 8a.7.2.2

84.10.3.1.2 Test purpose

To verify that MS is able to change active PTC parameters if requested.

84.10.3.1.3 Method of test

Initial Conditions

System Simulator:

– 1 GAN cell, default parameters

Mobile Station:

– MS in GA-RRC-CONNECTED state (PS domain) in service of GAN cell, with active PTC

Foreseen Final State of the MS

MS in GA-RRC-IDLE state (PS domain)

Test Procedure

The MS is in GA-RRC-CONNECTED state (PS domain) in service of GAN cell, with an active PTC. SS sends GA-RRC MODIFY CHANNEL message to change the RAB Configuration. The MS modifies the RAB Configuration for the active PTC and then replies by a GA-RRC MODIFY CHANNEL ACK message indicating the modified parameter.

Specific test parameters

Maximum Duration of Test

1 min.

Expected Sequence

Step

Direction

Message

Comment

MS

SS

1

MS

MS in service with PTC activated on GAN cell

2

GA-RRC MODIFY CHANNEL

IE ‘CN Domain Identity’ indicates PS domain. For the (single) PTC specified in the IE ‘PTC Modification List’: IE ‘RAB ID’, IE ‘RAB Configuration’ with new value

3

MS

MS sets the new RAB Configuration value

4

GA-RRC MODIFY CHANNEL ACK

IE ‘CN Domain Identity’ indicates PS domain. For the (single) PTC specified in the IE ‘PTC Modification Ack List’: IE ‘RAB ID’, IE ‘GA-RRC Cause’ (indicating value #0), IE ‘RAB Configuration’ with new value

5

MS

MS in service with active PTC on GAN cell with new RAB Configuration value

6

GA-RRC RELEASE

IE ‘GA-RRC Cause’ = #83

IE ‘CN Domain Identity’ indicates PS domain

7

GA-RRC RELEASE COMPLETE

IE ‘CN Domain Identity’ indicates PS domain

MS enters GA-RRC-IDLE state for PS domain

84.10.4 PS channel modify procedure / negative cases

84.10.4.1 PS channel modify requests illegal change to parameter

84.10.4.1.1 Conformance requirement

3GPP TS 44.318 subclause 8a.7.2.1:

The GANC initiates the packet transport channel (PTC) modification procedure when it determines that one or more active PTCs require modification; e.g., based on information received from the SGSN in the RAB Assignment Request message or based on local GANC logic.

The following PTC parameters may be modified:

– RAB Configuration

– GANC UDP Port

– GANC IP Address

The GANC only includes the IEs which specify modifications to the existing PTC parameters.

One or more PTCs may be modified using a single instance of the channel modification procedure; however, it is not possible to modify both circuit and packet transport channels using a single instance of the channel modification procedure.

The GANC begins the modification of the PTC(s) by transmitting the GA-RRC MODIFY CHANNEL message to the MS. The message contains the IE "CN Domain Identity" (indicating PS domain) and IE "PTC Modification List" which includes the parameters necessary to describe the modifications to each packet transport channel.

3GPP TS 44.318 subclause 8a.7.2.2:

On receipt of the GA-RRC MODIFY CHANNEL message indicating the PS domain, the MS shall process the specified PTC modifications.

On completion of the modification of the PTC(s), the MS shall:

– transmit a GA-RRC MODIFY CHANNEL ACK message including the IE "CN Domain Identity" and the IE "PTC Modification Ack List". For each PTC specified in the IE "PTC Modification Ack List":

– include the IE "RAB ID" for the PTC with the same value as received in the GA-RRC MODIFY CHANNEL message in the IE "RAB ID";

– include the IE "GA-RRC Cause" indicating either success (i.e., value ‘0’) or a failure cause value;

– for each PTC that is successfully modified (i.e., GA-RRC Cause value is ‘0’):

– include the modified parameter values currently used by the MS.

When the MS has sent the GA-RRC MODIFY CHANNEL ACK message, it shall start transmitting GA-RRC PDU messages based on the successful parameter modifications. The MS shall be able to receive GA-RRC PDU messages with the old parameters until the MS determines that the first GA-RRC PDU message using the new parameters has been received.

Reference(s)

3GPP TS 44.318 subclauses 8a.7.2.1, 8a.7.2.2

84.10.4.1.2 Test purpose

To verify that the MS does not change the PTC parameters if requested to make an illegal change to a parameter (i.e., to change the MS TEID value).

84.10.4.1.3 Method of test

Initial Conditions

System Simulator:

– 1 GAN cell, default parameters

Mobile Station:

– MS in GA-RRC-CONNECTED state (PS domain) in service of GAN cell, with active PTC

Foreseen Final State of the MS

MS in GA-RRC-IDLE state (PS domain)

Test Procedure

The MS is in GA-RRC-CONNECTED state (PS domain) in service of GAN cell, with an active PTC. SS sends GA-RRC MODIFY CHANNEL message to change the MS TEID value. The requested change is not allowed. MS retains the old MS TEID value for the active PTC and then replies by a GA-RRC MODIFY CHANNEL ACK message with a failure indication.

Specific test parameters

Maximum Duration of Test

1 min.

Expected Sequence

Step

Direction

Message

Comment

MS

SS

1

MS

MS in service with PTC activated on GAN cell

2

GA-RRC MODIFY CHANNEL

IE ‘CN Domain Identity’ indicates PS domain. For the (single) PTC specified in the IE ‘PTC Modification List’: IE ‘RAB ID’, IE ‘MS TEID’ with new value

3

MS

MS retains the old MS TEID value

4

GA-RRC MODIFY CHANNEL ACK

IE ‘CN Domain Identity’ indicates PS domain. For the (single) PTC specified in the IE ‘PTC Modification Ack List’: IE ‘RAB ID’, IE ‘GA-RRC Cause’ (indicating other than value #0; e.g., value #19 indicating invalid RAB parameters value)

5

MS

MS in service with active PTC on GAN cell with old MS TEID value

6

GA-RRC RELEASE

IE ‘GA-RRC Cause’ = #83

IE ‘CN Domain Identity’ indicates PS domain

7

GA-RRC RELEASE COMPLETE

IE ‘CN Domain Identity’ indicates PS domain

MS enters GA-RRC-IDLE state for PS domain

84.11 Deactivate channel procedure

84.11.1 CS deactivate channel procedure / successful cases

84.11.1.1 CS deactivate channel request from GANC

84.11.1.1.1 Conformance requirement

3GPP TS 44.318 subclause 8a.8.3:

The GANC normally initiates this procedure when it receives the RAB Assignment message from the CN indicating RAB release; however, the GANC may also initiate this procedure under certain failure conditions.

One or more circuit or packet transport channels may be deactivated using a single instance of the channel deactivation procedure; however, it is not possible to deactivate both circuit and packet transport channels using a single instance of the channel deactivation procedure.

The GA-RRC DEACTIVATE CHANNEL message includes the IE "GA-RRC Cause" with value as follows:

#0: normal event, e.g. deactivate due to RAB release request from CN

#115: unspecified failure

#10: relocation cancelled (e.g., the handover procedure is stopped because the call has been cleared)

3GPP TS 44.318 subclause 8a.8.4:

When the MS receives the GA-RRC DEACTIVATE CHANNEL message, it shall:

– deactivate the CTC(s) or PTC(s) identified in the IE "RAB ID List";

– send a GA-RRC DEACTIVATE CHANNEL COMPLETE message to the GANC.

3GPP TS 44.318 subclause 8a.8.5:

If timer TU5002 expires in the MS, the MS shall release the associated transport channel(s).

Reference(s)

3GPP TS 44.318 subclauses 8a.8.3, 8a.8.4, 8a.8.5

84.11.1.1.2 Test purpose

To verify that MS is able to deactivate a CTC if requested.

84.11.1.1.3 Method of test

Initial Conditions

System Simulator:

– 1 GAN cell, default parameters

Mobile Station:

– MS in GA-RRC-CONNECTED state (CS domain) in service of GAN cell, one CTC active

Foreseen Final State of the MS

MS in GA-RRC-IDLE state (CS domain)

Test Procedure

The MS is in GA-RRC-CONNECTED state (CS domain) in service of GAN cell, with one CTC active. SS sends GA-RRC DEACTIVATE CHANNEL message to deactivate the CTC. The MS deactivates the CTC and then replies by a GA-RRC DEACTIVATE CHANNEL COMPLETE message.

Specific test parameters

Maximum Duration of Test

1 min.

Expected Sequence

Step

Direction

Message

Comment

MS

SS

1

MS

MS in service with one CTC active on GAN cell

2

GA-RRC DEACTIVATE CHANNEL

IE ‘CN Domain Identity’ indicates CS domain. For the (single) CTC specified in the IE ‘RAB ID List’: IE ‘RAB ID’

3

MS

MS deactivates the CTC

4

GA-RRC DEACTIVATE CHANNEL COMPLETE

IE ‘CN Domain Identity’ indicates CS domain.

5

MS

MS with GA-RRC connection (CS domain) but no active CTC

6

GA-RRC RELEASE

IE ‘GA-RRC Cause’ = #83

IE ‘CN Domain Identity’ indicates CS domain

7

GA-RRC RELEASE COMPLETE

IE ‘CN Domain Identity’ indicates CS domain

MS enters GA-RRC-IDLE state for CS domain

84.11.1.2 CS deactivate channel request from MS

84.11.1.2.1 Conformance requirement

3GPP TS 44.318 subclause 8a.8.1:

If the MS needs to deactivate one or more transport channels for a particular domain, it shall send the GA-RRC DEACTIVATE CHANNEL REQUEST message to the GANC and start timer TU5002 for the domain. The MS shall include the IE "CN Domain Identity" and the IE "GA-RRC Cause". The GA-RRC Cause value shall be one of the following:

#0: normal release (e.g., due to inactivity timer timeout)

#115: unspecified failure

3GPP TS 44.318 subclause 8a.8.2:

When the GANC receives the GA-RRC DEACTIVATE CHANNEL REQUEST message, it shall request the selected CN domain to release the identified RABs associated with the MS. The GANC selects the CN domain based on the value of the received IE "CN Domain Identity". Note that the GANC may also request the selected CN domain to release the Iu connection for the MS in this case, based on local policy settings.

3GPP TS 44.318 subclause 8a.8.3:

The GANC normally initiates this procedure when it receives the RAB Assignment message from the CN indicating RAB release; however, the GANC may also initiate this procedure under certain failure conditions.

One or more circuit or packet transport channels may be deactivated using a single instance of the channel deactivation procedure; however, it is not possible to deactivate both circuit and packet transport channels using a single instance of the channel deactivation procedure.

The GA-RRC DEACTIVATE CHANNEL message includes the IE "GA-RRC Cause" with value as follows:

#0: normal event, e.g. deactivate due to RAB release request from CN

#115: unspecified failure

#10: relocation cancelled (e.g., the handover procedure is stopped because the call has been cleared)

3GPP TS 44.318 subclause 8a.8.4:

When the MS receives the GA-RRC DEACTIVATE CHANNEL message, it shall:

– deactivate the CTC(s) or PTC(s) identified in the IE "RAB ID List";

– send a GA-RRC DEACTIVATE CHANNEL COMPLETE message to the GANC.

3GPP TS 44.318 subclause 8a.8.5:

If timer TU5002 expires in the MS, the MS shall release the associated transport channel(s).

Reference(s)

3GPP TS 44.318 subclauses 8a.8.1, 8a.8.2, 8a.8.3, 8a.8.4, 8a.8.5

84.11.1.2.2 Test purpose

To verify that MS is able to request deactivation of a CTC.

84.11.1.2.3 Method of test

Initial Conditions

System Simulator:

– 1 GAN cell, default parameters

Mobile Station:

– MS in GA-RRC-CONNECTED state (CS domain) in service of GAN cell, one CTC active

Foreseen Final State of the MS

MS in GA-RRC-IDLE state (CS domain)

Test Procedure

The MS is in GA-RRC-CONNECTED state (CS domain) in service of GAN cell, with one CTC active. MS sends GA-RRC DEACTIVATE CHANNEL REQUEST message to request deactivation of the CTC. SS sends GA-RRC DEACTIVATE CHANNEL message to deactivate the CTC. The MS deactivates the CTC and then replies by a GA-RRC DEACTIVATE CHANNEL COMPLETE message.

Specific test parameters

Maximum Duration of Test

1 min.

Expected Sequence

Step

Direction

Message

Comment

MS

SS

1

MS

MS in service with one CTC active on GAN cell

2

GA-RRC DEACTIVATE CHANNEL REQUEST

IE ‘CN Domain Identity’ indicates CS domain, IE ‘GA-RRC Cause’ = #115. For the (single) CTC specified in the IE ‘RAB ID List’: IE ‘RAB ID’.

3

GA-RRC DEACTIVATE CHANNEL

IE ‘CN Domain Identity’ indicates CS domain, For the (single) CTC specified in the IE ‘RAB ID List’: IE ‘RAB ID’

4

MS

MS deactivates the CTC

5

GA-RRC DEACTIVATE CHANNEL COMPLETE

IE ‘CN Domain Identity’ indicates CS domain.

6

MS

MS with GA-RRC connection (CS domain) but no active CTC

7

GA-RRC RELEASE

IE ‘GA-RRC Cause’ = #83

IE ‘CN Domain Identity’ indicates CS domain

8

GA-RRC RELEASE COMPLETE

IE ‘CN Domain Identity’ indicates CS domain

MS enters GA-RRC-IDLE state for CS domain

84.11.2 CS deactivate channel procedure / negative cases

84.11.2.1 TU5002 timer expires

84.11.2.1.1 Conformance requirement

3GPP TS 44.318 subclause 8a.8.1:

If the MS needs to deactivate one or more transport channels for a particular domain, it shall send the GA-RRC DEACTIVATE CHANNEL REQUEST message to the GANC and start timer TU5002 for the domain. The MS shall include the IE "CN Domain Identity" and the IE "GA-RRC Cause". The GA-RRC Cause value shall be one of the following:

#0: normal release (e.g., due to inactivity timer timeout)

#115: unspecified failure

3GPP TS 44.318 subclause 8a.8.2:

When the GANC receives the GA-RRC DEACTIVATE CHANNEL REQUEST message, it shall request the selected CN domain to release the identified RABs associated with the MS. The GANC selects the CN domain based on the value of the received IE "CN Domain Identity". Note that the GANC may also request the selected CN domain to release the Iu connection for the MS in this case, based on local policy settings.

3GPP TS 44.318 subclause 8a.8.3:

The GANC normally initiates this procedure when it receives the RAB Assignment message from the CN indicating RAB release; however, the GANC may also initiate this procedure under certain failure conditions.

One or more circuit or packet transport channels may be deactivated using a single instance of the channel deactivation procedure; however, it is not possible to deactivate both circuit and packet transport channels using a single instance of the channel deactivation procedure.

The GA-RRC DEACTIVATE CHANNEL message includes the IE "GA-RRC Cause" with value as follows:

#0: normal event, e.g. deactivate due to RAB release request from CN

#115: unspecified failure

#10: relocation cancelled (e.g., the handover procedure is stopped because the call has been cleared)

3GPP TS 44.318 subclause 8a.8.4:

When the MS receives the GA-RRC DEACTIVATE CHANNEL message, it shall:

– deactivate the CTC(s) or PTC(s) identified in the IE "RAB ID List";

– send a GA-RRC DEACTIVATE CHANNEL COMPLETE message to the GANC.

3GPP TS 44.318 subclause 8a.8.5:

If timer TU5002 expires in the MS, the MS shall release the associated transport channel(s).

Reference(s)

3GPP TS 44.318 subclauses 8a.8.1, 8a.8.2, 8a.8.3, 8a.8.4, 8a.8.5

84.11.2.1.2 Test purpose

To verify that the MS releases the CTC when the TU5002 timer (CS domain) expires.

84.11.2.1.3 Method of test

Initial Conditions

System Simulator:

– 1 GAN cell, default parameters

Mobile Station:

– MS in GA-RRC-CONNECTED state (CS domain) in service of GAN cell, one CTC active

Foreseen Final State of the MS

MS in GA-RRC-IDLE state (CS domain)

Test Procedure

The MS is in GA-RRC-CONNECTED state (CS domain) in service of GAN cell, with one CTC active. MS sends GA-RRC DEACTIVATE CHANNEL REQUEST message to request deactivation of the CTC and starts timer TU5002 (CS domain). SS does not respond and timer TU5002 (CS domain) expires. MS deactivates the CTC.

Specific test parameters

Maximum Duration of Test

1 min.

Expected Sequence

Step

Direction

Message

Comment

MS

SS

1

MS

MS in service with one CTC active on GAN cell

2

GA-RRC DEACTIVATE CHANNEL REQUEST

IE ‘CN Domain Identity’ indicates CS domain, IE ‘GA-RRC Cause’ = #115. For the (single) CTC specified in the IE ‘RAB ID List’: IE ‘RAB ID’. MS starts TU5002 (CS domain)

3

SS

SS waits for period longer than TU5002

4

MS

TU5002 (CS domain) expires. MS releases the CTC resources

5

MS

MS with GA-RRC connection (CS domain) but no active CTC

6

GA-RRC RELEASE

IE ‘GA-RRC Cause’ = #83

IE ‘CN Domain Identity’ indicates CS domain

7

GA-RRC RELEASE COMPLETE

IE ‘CN Domain Identity’ indicates CS domain

MS enters GA-RRC-IDLE state for CS domain

84.11.3 PS deactivate channel procedure / successful cases

84.11.3.1 PS deactivate channel request from GANC

84.11.1.3.1 Conformance requirement

3GPP TS 44.318 subclause 8a.8.3:

The GANC normally initiates this procedure when it receives the RAB Assignment message from the CN indicating RAB release; however, the GANC may also initiate this procedure under certain failure conditions.

One or more circuit or packet transport channels may be deactivated using a single instance of the channel deactivation procedure; however, it is not possible to deactivate both circuit and packet transport channels using a single instance of the channel deactivation procedure.

The GA-RRC DEACTIVATE CHANNEL message includes the IE "GA-RRC Cause" with value as follows:

#0: normal event, e.g. deactivate due to RAB release request from CN

#115: unspecified failure

#10: relocation cancelled (e.g., the handover procedure is stopped because the call has been cleared)

3GPP TS 44.318 subclause 8a.8.4:

When the MS receives the GA-RRC DEACTIVATE CHANNEL message, it shall:

– deactivate the CTC(s) or PTC(s) identified in the IE "RAB ID List";

– send a GA-RRC DEACTIVATE CHANNEL COMPLETE message to the GANC.

3GPP TS 44.318 subclause 8a.8.5:

If timer TU5002 expires in the MS, the MS shall release the associated transport channel(s).

Reference(s)

3GPP TS 44.318 subclauses 8a.8.3, 8a.8.4, 8a.8.5

84.11.1.3.2 Test purpose

To verify that MS is able to deactivate a PTC if requested.

84.11.1.3.3 Method of test

Initial Conditions

System Simulator:

– 1 GAN cell, default parameters

Mobile Station:

– MS in GA-RRC-CONNECTED state (PS domain) in service of GAN cell, one PTC active

Foreseen Final State of the MS

MS in GA-RRC-IDLE state (PS domain)

Test Procedure

The MS is in GA-RRC-CONNECTED state (PS domain) in service of GAN cell, with one PTC active. SS sends GA-RRC DEACTIVATE CHANNEL message to deactivate the PTC. The MS deactivates the PTC and then replies by a GA-RRC DEACTIVATE CHANNEL COMPLETE message.

Specific test parameters

Maximum Duration of Test

1 min.

Expected Sequence

Step

Direction

Message

Comment

MS

SS

1

MS

MS in service with PTC active on GAN cell

2

GA-RRC DEACTIVATE CHANNEL

IE ‘CN Domain Identity’ indicates PS domain. For the (single) PTC specified in the IE ‘RAB ID List’: IE ‘RAB ID’

3

MS

MS deactivates the PTC

4

GA-RRC DEACTIVATE CHANNEL COMPLETE

IE ‘CN Domain Identity’ indicates PS domain.

5

MS

MS with GA-RRC connection (PS domain) but no active PTC

6

GA-RRC RELEASE

IE ‘GA-RRC Cause’ = #83

IE ‘CN Domain Identity’ indicates PS domain

7

GA-RRC RELEASE COMPLETE

IE ‘CN Domain Identity’ indicates PS domain

MS enters GA-RRC-IDLE state for PS domain

84.11.3.2 PS deactivate channel request from MS

84.11.3.2.1 Conformance requirement

3GPP TS 44.318 subclause 8a.8.1:

If the MS needs to deactivate one or more transport channels for a particular domain, it shall send the GA-RRC DEACTIVATE CHANNEL REQUEST message to the GANC and start timer TU5002 for the domain. The MS shall include the IE "CN Domain Identity" and the IE "GA-RRC Cause". The GA-RRC Cause value shall be one of the following:

#0: normal release (e.g., due to inactivity timer timeout)

#115: unspecified failure

3GPP TS 44.318 subclause 8a.8.2:

When the GANC receives the GA-RRC DEACTIVATE CHANNEL REQUEST message, it shall request the selected CN domain to release the identified RABs associated with the MS. The GANC selects the CN domain based on the value of the received IE "CN Domain Identity". Note that the GANC may also request the selected CN domain to release the Iu connection for the MS in this case, based on local policy settings.

3GPP TS 44.318 subclause 8a.8.3:

The GANC normally initiates this procedure when it receives the RAB Assignment message from the CN indicating RAB release; however, the GANC may also initiate this procedure under certain failure conditions.

One or more circuit or packet transport channels may be deactivated using a single instance of the channel deactivation procedure; however, it is not possible to deactivate both circuit and packet transport channels using a single instance of the channel deactivation procedure.

The GA-RRC DEACTIVATE CHANNEL message includes the IE "GA-RRC Cause" with value as follows:

#0: normal event, e.g. deactivate due to RAB release request from CN

#115: unspecified failure

#10: relocation cancelled (e.g., the handover procedure is stopped because the call has been cleared)

3GPP TS 44.318 subclause 8a.8.4:

When the MS receives the GA-RRC DEACTIVATE CHANNEL message, it shall:

– deactivate the CTC(s) or PTC(s) identified in the IE "RAB ID List";

– send a GA-RRC DEACTIVATE CHANNEL COMPLETE message to the GANC.

3GPP TS 44.318 subclause 8a.8.5:

If timer TU5002 expires in the MS, the MS shall release the associated transport channel(s).

Reference(s)

3GPP TS 44.318 subclauses 8a.8.1, 8a.8.2, 8a.8.3, 8a.8.4, 8a.8.5

84.11.3.2.2 Test purpose

To verify that MS is able to request deactivation of a PTC.

84.11.3.2.3 Method of test

Initial Conditions

System Simulator:

– 1 GAN cell, default parameters

Mobile Station:

– MS in GA-RRC-CONNECTED state (PS domain) in service of GAN cell, one PTC active

Foreseen Final State of the MS

MS in GA-RRC-IDLE state (PS domain)

Test Procedure

The MS is in GA-RRC-CONNECTED state (PS domain) in service of GAN cell, with one PTC active. MS sends GA-RRC DEACTIVATE CHANNEL REQUEST message to request deactivation of the PTC. SS sends GA-RRC DEACTIVATE CHANNEL message to deactivate the PTC. The MS deactivates the PTC and then replies by a GA-RRC DEACTIVATE CHANNEL COMPLETE message.

Specific test parameters

Maximum Duration of Test

1 min.

Expected Sequence

Step

Direction

Message

Comment

MS

SS

1

MS

MS in service with one PTC active on GAN cell

2

GA-RRC DEACTIVATE CHANNEL REQUEST

IE ‘CN Domain Identity’ indicates PS domain, IE ‘GA-RRC Cause’ = #0. For the (single) PTC specified in the IE ‘RAB ID List’: IE ‘RAB ID’.

3

GA-RRC DEACTIVATE CHANNEL

IE ‘CN Domain Identity’ indicates PS domain, For the (single) PTC specified in the IE ‘RAB ID List’: IE ‘RAB ID’

4

MS

MS deactivates the PTC

5

GA-RRC DEACTIVATE CHANNEL COMPLETE

IE ‘CN Domain Identity’ indicates PS domain.

6

MS

MS with GA-RRC connection (PS domain) but no active PTC

7

GA-RRC RELEASE

IE ‘GA-RRC Cause’ = #83

IE ‘CN Domain Identity’ indicates PS domain

8

GA-RRC RELEASE COMPLETE

IE ‘CN Domain Identity’ indicates PS domain

MS enters GA-RRC-IDLE state for PS domain

84.11.4 PS deactivate channel procedure / negative cases

84.11.4.1 TU5002 timer expires

84.11.4.1.1 Conformance requirement

3GPP TS 44.318 subclause 8a.8.1:

If the MS needs to deactivate one or more transport channels for a particular domain, it shall send the GA-RRC DEACTIVATE CHANNEL REQUEST message to the GANC and start timer TU5002 for the domain. The MS shall include the IE "CN Domain Identity" and the IE "GA-RRC Cause". The GA-RRC Cause value shall be one of the following:

#0: normal release (e.g., due to inactivity timer timeout)

#115: unspecified failure

3GPP TS 44.318 subclause 8a.8.2:

When the GANC receives the GA-RRC DEACTIVATE CHANNEL REQUEST message, it shall request the selected CN domain to release the identified RABs associated with the MS. The GANC selects the CN domain based on the value of the received IE "CN Domain Identity". Note that the GANC may also request the selected CN domain to release the Iu connection for the MS in this case, based on local policy settings.

3GPP TS 44.318 subclause 8a.8.3:

The GANC normally initiates this procedure when it receives the RAB Assignment message from the CN indicating RAB release; however, the GANC may also initiate this procedure under certain failure conditions.

One or more circuit or packet transport channels may be deactivated using a single instance of the channel deactivation procedure; however, it is not possible to deactivate both circuit and packet transport channels using a single instance of the channel deactivation procedure.

The GA-RRC DEACTIVATE CHANNEL message includes the IE "GA-RRC Cause" with value as follows:

#0: normal event, e.g. deactivate due to RAB release request from CN

#115: unspecified failure

#10: relocation cancelled (e.g., the handover procedure is stopped because the call has been cleared)

3GPP TS 44.318 subclause 8a.8.4:

When the MS receives the GA-RRC DEACTIVATE CHANNEL message, it shall:

– deactivate the PTC(s) or PTC(s) identified in the IE "RAB ID List";

– send a GA-RRC DEACTIVATE CHANNEL COMPLETE message to the GANC.

3GPP TS 44.318 subclause 8a.8.5:

If timer TU5002 expires in the MS, the MS shall release the associated transport channel(s).

Reference(s)

3GPP TS 44.318 subclauses 8a.8.1, 8a.8.2, 8a.8.3, 8a.8.4, 8a.8.5

84.11.4.1.2 Test purpose

To verify that the MS releases the PTC when the TU5002 timer (PS domain) expires.

84.11.4.1.3 Method of test

Initial Conditions

System Simulator:

– 1 GAN cell, default parameters

Mobile Station:

– MS in GA-RRC-CONNECTED state (PS domain) in service of GAN cell, one PTC active

Foreseen Final State of the MS

MS in GA-RRC-IDLE state (PS domain)

Test Procedure

The MS is in GA-RRC-CONNECTED state (PS domain) in service of GAN cell, with one PTC active. MS sends GA-RRC DEACTIVATE CHANNEL REQUEST message to request deactivation of the PTC and starts timer TU5002 (PS domain). SS does not respond and timer TU5002 (PS domain) expires. MS deactivates the PTC.

Specific test parameters

Maximum Duration of Test

1 min.

Expected Sequence

Step

Direction

Message

Comment

MS

SS

1

MS

MS in service with one PTC active on GAN cell

2

GA-RRC DEACTIVATE CHANNEL REQUEST

IE ‘CN Domain Identity’ indicates PS domain, IE ‘GA-RRC Cause’ = #0. For the (single) PTC specified in the IE ‘RAB ID List’: IE ‘RAB ID’. MS starts TU5002 (PS domain)

3

SS

SS waits for period longer than TU5002

4

MS

TU5002 (PS domain) expires. MS releases the PTC resources

5

MS

MS with GA-RRC connection (PS domain) but no active PTC

6

GA-RRC RELEASE

IE ‘GA-RRC Cause’ = #83

IE ‘CN Domain Identity’ indicates PS domain

7

GA-RRC RELEASE COMPLETE

IE ‘CN Domain Identity’ indicates PS domain

MS enters GA-RRC-IDLE state for PS domain