13.5 Access Control

36.523-13GPPEvolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Packet Core (EPC)Part 1: Protocol conformance specificationRelease 16TSUser Equipment (UE) conformance specification

13.5.1 MTSI MO speech call / SSAC / 0% access probability for MTSI MO speech call

13.5.1.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_IDLE state having received a SysteminformationBlockType2 message including a ssac-BarringForMMTEL-Voice-r9 set to 0% accessibility }

ensure that {
when { the user initiates a MTSI MO voice call }

then { the UE does not establish RRC connection }

}

(2)

with { UE in E-UTRA RRC_IDLE state having received a SysteminformationBlockType2 message including a ssac-BarringForMMTEL-Voice-r9 set to 0% accessibility and including back-off timer Ty and having failed to initiate a voice call }

ensure that {
when { the user initiates a MTSI MO voice call during back-off timer Ty is running }

then { the UE does not establish RRC connection }

}

13.5.1.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 24.173 clause J.2.1.2 and TS 36.331 clause 5.3.3.10. Unless otherwise stated these are Rel-9 requirements.

[TS 24.173, clause J.2.1.1]:

The following information is provided by lower layer:

– BarringFactorForMMTEL-Voice: barring rate for MMTEL voice;

– BarringTimeForMMTEL-Voice: barring timer for MMTEL voice;

Upon request from a user to establish a multimedia telephony communication session as described in subclause 5.2, the UE shall:

1) if the multimedia telephony communication session to be established is an emergency session, then skip the rest of steps below and continue with session establishment as described in subclause 5.2;

2) retrieve SSAC related information mentioned above from lower layers;

3) if video is offered in the multimedia telephony communication session:

4) if audio is offered in the multimedia telephony communication session:

A) if back-off timer Ty is running, reject the multimedia telephony communication session establishment and skip the rest of steps below; or

B) else, then;

I) draw a new random number "rand3" that is uniformly distributed in the range 0 ≤ rand3 < 1; and

II) if the random number "rand3" is lower than BarringFactorForMMTEL-Voice, then skip the rest of steps below and continue with session establishment as described in subclause 5.2;

III) else, then;

i) draw a new random number "rand4" that is uniformly distributed in the range 0 ≤ rand4 < 1; and

ii) start timer Ty with the timer value calculated using the formula:

Ty = (0,7 + 0,6*rand4) * BarringTimeForMMTEL-Voice; and

iii) reject the multimedia telephony communication session establishment;

[TS 36.331 clause 5.3.3.10]:

Upon request from the upper layers, the UE shall:

1> set the local variables BarringFactorForMMTEL-Voice and BarringTimeForMMTEL-Voice as follows:

2> if ssac-BarringForMMTEL-Voice is present:

3> if the UE has one or more Access Classes, as stored on the USIM, with a value in the range 11..15, which is valid for the UE to use according to TS 22.011 [10] and TS 23.122 [11], and

NOTE: ACs 12, 13, 14 are only valid for use in the home country and ACs 11, 15 are only valid for use in the HPLMN/ EHPLMN.

3> if, for at least one of these Access Classes, the corresponding bit in the ac-BarringForSpecialAC contained in ssac-BarringForMMTEL-Voice is set to zero:

4> set BarringFactorForMMTEL-Voice to one and BarringTimeForMMTEL-Voice to zero;

3> else:

4> set BarringFactorForMMTEL-Voice and BarringTimeForMMTEL-Voice to the value of ac-BarringFactor and ac-BarringTime included in ssac-BarringForMMTEL-Voice, respectively;

2> else set BarringFactorForMMTEL-Voice to one and BarringTimeForMMTEL-Voice to zero;

1> set the local variables BarringFactorForMMTEL-Video and BarringTimeForMMTEL-Video as follows:

2> if ssac-BarringForMMTEL-Video is present:

3> if the UE has one or more Access Classes, as stored on the USIM, with a value in the range 11..15, which is valid for the UE to use according to TS 22.011 [10] and TS 23.122 [11], and

3> if, for at least one of these Access Classes, the corresponding bit in the ac-BarringForSpecialAC contained in ssac-BarringForMMTEL-Video is set to zero:

4> set BarringFactorForMMTEL-Video to one and BarringTimeForMMTEL-Video to zero;

3> else:

4> set BarringFactorForMMTEL-Video and BarringTimeForMMTEL-Video to the value of ac-BarringFactor and ac-BarringTime included in ssac-BarringForMMTEL-Video, respectively;

2> else set BarringFactorForMMTEL-Video to one and BarringTimeForMMTEL-Video to zero;

1> forward the variables BarringFactorForMMTEL-Voice, BarringTimeForMMTEL-Voice, BarringFactorForMMTEL-Video and BarringTimeForMMTEL-Video to the upper layers;

13.5.1.3 Test description

13.5.1.3.1 Pre-test conditions

System Simulator:

– Cell 1.

UE:

None.

Preamble:

– The UE is in state Registered, Idle mode (state 2) according to [18].

13.5.1.3.2 Test procedure sequence

Table 13.5.1.3.2-1: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

Make the UE attempt an MTSI MO Speech call

2

Check: Does the UE transmit a RRCConnectionRequest message within 10 s?.

–>

RRCConnectionRequest

1

F

3

SS changes SIB2 according to TS 36.508, table 4.4.3.3-1 and transmits a Paging message including systemInfoModification. The systemInfoValueTag in the SystemInformationBlockType1 is increased.

<–

Paging

4

Wait for 15 s (Note 1) to allow the new system information to take effect.

5

Make the UE attempt an MTSI MO Speech call

6

Check: Does the UE transmit an RRCConnectionRequest message with in 10s?

–>

RRCConnectionRequest

2

F

7

Wait for 49 s (Note 2) to make the timer Ty expire.

8-21

Steps 1 to 14 of the generic test procedure for MTSI MO Speech call establishment in EUTRA: Normal Service (TS 36.508 4.5A.6.3-1).

Note 1: The wait time of 15 s in step 3 is to allow for the network to page the system information change during the next modification period, and update the system information at the subsequent modification period. UE should acquire the updated system information within 100ms of the start of modification period.

Note 2: The UE starts timer Ty in step2. Maximum time of timer Ty is 83.2 sec ((0.7 + 0.6 * 1) * s64). At the end of step 7, 35 sec elapses from step 2. Therefore 49 sec (84s – 35s) is enough to wait timer Ty expiry.

13.5.1.3.3 Specific message contents

Table 13.5.1.3.3-1: SystemInformationBlockType2 for Cell 1 (preamble and step 1, Table 13.5.1.3.2-1)

Derivation Path: 36.508, Table 4.4.3.3-1

Information Element

Value/remark

Comment

Condition

SystemInformationBlockType2 ::= SEQUENCE {

ssac-BarringForMMTEL-Voice-r9 SEQUENCE {

ac-BarringFactor

p00

ac-BarringTime

s64

ac-BarringForSpecialAC

‘11111’B

}

}

Table 13.5.1.3.3-2: Paging (step3, Table 13.5.1.3.2-1)

Derivation Path: 36.508 Table 4.6.1-7

Information Element

Value/remark

Comment

Condition

Paging ::= SEQUENCE {

pagingRecordList

Not present

systemInfoModification

TRUE

}

13.5.1a MTSI MO speech call / SSAC in Connected mode / 0% access probability for MTSI MO speech call

13.5.1a.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_CONNECTED state having received a SysteminformationBlockType2 message including a ssac-BarringForMMTEL-Voice-r9 set to 0% accessibility }

ensure that {
when { the user initiates a MTSI MO voice call }

then { the UE does not initiate a MTSI MO voice call }

}

(2)

with { UE in E-UTRA RRC_CONNECTED state having received a SysteminformationBlockType2 message including a ssac-BarringForMMTEL-Voice-r9 with back-off timer Ty and having failed to initiate a voice call }

ensure that {
when { ssac-BarringForMMTEL-Voice-r9 is removed and the user initiates a MTSI MO voice call during back-off timer Ty is running }

then { the UE does not initiate a MTSI MO voice call }

}

(3)

with { UE in E-UTRA RRC_CONNECTED state having received a SysteminformationBlockType2 message including a ssac-BarringForMMTEL-Voice-r9 with back-off timer Ty and having failed to initiate a voice call }

ensure that {
when { the user initiates a MTSI MO voice call afar expiring back-off timer Ty }

then { the UE initiates a MTSI MO voice call }

}

13.5.1a.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 24.173 clause J.2.1.2 and TS 36.331 clause 5.3.3.10. Unless otherwise stated these are Rel-12 requirements.

[TS 24.173, clause J.2.1.2]:

The following information is provided by lower layer:

– BarringFactorForMMTEL-Voice: barring rate for MMTEL voice;

– BarringTimeForMMTEL-Voice: barring timer for MMTEL voice;

Upon request from a user to establish a multimedia telephony communication session as described in subclause 5.2, the UE shall:

1) if the multimedia telephony communication session to be established is an emergency session, then skip the rest of steps below and continue with session establishment as described in subclause 5.2;

2) retrieve SSAC related information mentioned above from lower layers;

3) if video is offered in the multimedia telephony communication session:

4) if audio is offered in the multimedia telephony communication session:

A) if back-off timer Ty is running, reject the multimedia telephony communication session establishment and skip the rest of steps below; or

B) else, then;

I) draw a new random number "rand3" that is uniformly distributed in the range 0 ≤ rand3 < 1; and

II) if the random number "rand3" is lower than BarringFactorForMMTEL-Voice, then skip the rest of steps below and continue with session establishment as described in subclause 5.2;

III) else, then;

i) draw a new random number "rand4" that is uniformly distributed in the range 0 ≤ rand4 < 1; and

ii) start timer Ty with the timer value calculated using the formula:

Ty = (0,7 + 0,6*rand4) * BarringTimeForMMTEL-Voice; and

iii) reject the multimedia telephony communication session establishment;

[TS 36.331 clause 5.3.3.10]:

Upon request from the upper layers, the UE shall:

1> set the local variables BarringFactorForMMTEL-Voice and BarringTimeForMMTEL-Voice as follows:

2> if ssac-BarringForMMTEL-Voice is present:

3> if the UE has one or more Access Classes, as stored on the USIM, with a value in the range 11..15, which is valid for the UE to use according to TS 22.011 [10] and TS 23.122 [11], and

NOTE: ACs 12, 13, 14 are only valid for use in the home country and ACs 11, 15 are only valid for use in the HPLMN/ EHPLMN.

3> if, for at least one of these Access Classes, the corresponding bit in the ac-BarringForSpecialAC contained in ssac-BarringForMMTEL-Voice is set to zero:

4> set BarringFactorForMMTEL-Voice to one and BarringTimeForMMTEL-Voice to zero;

3> else:

4> set BarringFactorForMMTEL-Voice and BarringTimeForMMTEL-Voice to the value of ac-BarringFactor and ac-BarringTime included in ssac-BarringForMMTEL-Voice, respectively;

2> else set BarringFactorForMMTEL-Voice to one and BarringTimeForMMTEL-Voice to zero;

1> set the local variables BarringFactorForMMTEL-Video and BarringTimeForMMTEL-Video as follows:

2> if ssac-BarringForMMTEL-Video is present:

3> if the UE has one or more Access Classes, as stored on the USIM, with a value in the range 11..15, which is valid for the UE to use according to TS 22.011 [10] and TS 23.122 [11], and

3> if, for at least one of these Access Classes, the corresponding bit in the ac-BarringForSpecialAC contained in ssac-BarringForMMTEL-Video is set to zero:

4> set BarringFactorForMMTEL-Video to one and BarringTimeForMMTEL-Video to zero;

3> else:

4> set BarringFactorForMMTEL-Video and BarringTimeForMMTEL-Video to the value of ac-BarringFactor and ac-BarringTime included in ssac-BarringForMMTEL-Video, respectively;

2> else set BarringFactorForMMTEL-Video to one and BarringTimeForMMTEL-Video to zero;

1> forward the variables BarringFactorForMMTEL-Voice, BarringTimeForMMTEL-Voice, BarringFactorForMMTEL-Video and BarringTimeForMMTEL-Video to the upper layers;

13.5.1a.3 Test description

13.5.1a.3.1 Pre-test conditions

System Simulator:

– Cell 1.

UE:

None.

Preamble:

– The UE is in state Generic RB Established (state 3) on Cell 1 according to [18].

13.5.1a.3.2 Test procedure sequence

Table 13.5.1a.3.2-1: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1-4

Void

5

Make the UE attempt a MTSI MO Speech call

6

Check: Does the UE transmit an INVITE message with in 10s?

–>

INVITE

1

F

6AA

SS changes SIB2 according to TS 36.508, table 4.4.3.3-1 and transmits a Paging message including systemInfoModification. The systemInfoValueTag in the SystemInformationBlockType1 is increased.

<–

Paging

6AB

Wait for 15 s (Note 1) to allow the new system information to take effect.

6A

Make the UE attempt a MTSI MO Speech call

6B

Check: Does the UE transmit an INVITE message during back-off timer Ty is running and within 10s?

–>

INVITE

2

F

7

Wait for 49 s (Note 2) to make the timer Ty expire.

8

Make the UE attempt a MTSI MO Speech call

9

Check: Does the UE transmit an INVITE message within 10 s?

INVITE

3

P

10-12

Steps 3 to 4 of the generic procedure for MTSI MO speech call establishment (TS 34.229-1 C.21)

13-15

Steps 12 to 14 of the generic procedure for MTSI MO speech call establishment (TS 36.508 table 4.5A.6.3-1).

Note 1: The wait time of 15 s in step 3 is to allow for the network to page the system information change during the next modification period, and update the system information at the subsequent modification period. UE should acquire the updated system information within 100ms of the start of modification period.

Note 2: The UE starts timer Ty in step 6. Maximum time of timer Ty is 83.2 sec ((0.7 + 0.6 * 1) * s64). At the end of step 6B, 20 sec elapses from the beginning of step 6. Therefore 64 sec (84s – 20s) is enough to wait timer Ty expiry.

13.5.1a.3.3 Specific message contents

Table 13.5.1a.3.3-1: SystemInformationBlockType2 for Cell 1 (preamble,)

Derivation Path: 36.508, Table 4.4.3.3-1

Information Element

Value/remark

Comment

Condition

SystemInformationBlockType2 ::= SEQUENCE {

ssac-BarringForMMTEL-Voice-r9 SEQUENCE {

ac-BarringFactor

p00

ac-BarringTime

s64

ac-BarringForSpecialAC

‘11111’B

}

}

Table 13.5.1a.3.3-2: Void

13.5.1b Void

13.5.2 MTSI MO video call / SSAC / 0% access probability for MTSI MO video call

13.5.2.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_IDLE state having received a SysteminformationBlockType2 message including a ssac-BarringForMMTEL-Video-r9 set to 0% accessibility }

ensure that {
when { the user initiates a MTSI MO video call }

then { the UE does not establish RRC connection }

}

(2)

with { UE in E-UTRA RRC_IDLE state having received a SysteminformationBlockType2 message including a ssac-BarringForMMTEL-Video-r9 set to 0% accessibility and including back-off timer Ty and having failed to initiate a voice call }

ensure that {
when { the user initiates a MTSI MO video call during back-off timer Ty is running }

then { the UE does not establish RRC connection }

}

13.5.2.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 24.173 clause J.2.1.2 and TS 36.331 clause 5.3.3.10. Unless otherwise stated these are Rel-9 requirements.

[TS 24.173, clause J.2.1.1]:

The following information is provided by lower layer:

– BarringFactorForMMTEL-Video: barring rate for MMTEL video; and

– BarringTimeForMMTEL-Video: barring timer for MMTEL video.

Upon request from a user to establish a multimedia telephony communication session as described in subclause 5.2, the UE shall:

1) if the multimedia telephony communication session to be established is an emergency session, then skip the rest of steps below and continue with session establishment as described in subclause 5.2;

2) retrieve SSAC related information mentioned above from lower layers;

3) if video is offered in the multimedia telephony communication session:

A) if back-off timer Tx is running, reject the multimedia telephony communication session establishment and skip the rest of steps below; or

B) else, then:

I) draw a new random number "rand1" that is uniformly distributed in the range 0 ≤ rand1 < 1; and

II) if the random number "rand1" is lower than BarringFactorForMMTEL-Video, then skip the rest of steps below and continue with session establishment as described in subclause 5.2;

III) else, then;

i) draw a new random number "rand2" that is uniformly distributed in the range 0 ≤ rand2 < 1; and

ii) start back-off timer Tx with the timer value calculated using the formula:

Tx = (0,7 + 0,6*rand2) * BarringTimeForMMTEL-Video; and

iii) reject the multimedia telephony communication session establishment and skip the rest of steps below;

[TS 36.331 clause 5.3.3.10]:

Upon request from the upper layers, the UE shall:

1> set the local variables BarringFactorForMMTEL-Voice and BarringTimeForMMTEL-Voice as follows:

2> if ssac-BarringForMMTEL-Voice is present:

3> if the UE has one or more Access Classes, as stored on the USIM, with a value in the range 11..15, which is valid for the UE to use according to TS 22.011 [10] and TS 23.122 [11], and

NOTE: ACs 12, 13, 14 are only valid for use in the home country and ACs 11, 15 are only valid for use in the HPLMN/ EHPLMN.

3> if, for at least one of these Access Classes, the corresponding bit in the ac-BarringForSpecialAC contained in ssac-BarringForMMTEL-Voice is set to zero:

4> set BarringFactorForMMTEL-Voice to one and BarringTimeForMMTEL-Voice to zero;

3> else:

4> set BarringFactorForMMTEL-Voice and BarringTimeForMMTEL-Voice to the value of ac-BarringFactor and ac-BarringTime included in ssac-BarringForMMTEL-Voice, respectively;

2> else set BarringFactorForMMTEL-Voice to one and BarringTimeForMMTEL-Voice to zero;

1> set the local variables BarringFactorForMMTEL-Video and BarringTimeForMMTEL-Video as follows:

2> if ssac-BarringForMMTEL-Video is present:

3> if the UE has one or more Access Classes, as stored on the USIM, with a value in the range 11..15, which is valid for the UE to use according to TS 22.011 [10] and TS 23.122 [11], and

3> if, for at least one of these Access Classes, the corresponding bit in the ac-BarringForSpecialAC contained in ssac-BarringForMMTEL-Video is set to zero:

4> set BarringFactorForMMTEL-Video to one and BarringTimeForMMTEL-Video to zero;

3> else:

4> set BarringFactorForMMTEL-Video and BarringTimeForMMTEL-Video to the value of ac-BarringFactor and ac-BarringTime included in ssac-BarringForMMTEL-Video, respectively;

2> else set BarringFactorForMMTEL-Video to one and BarringTimeForMMTEL-Video to zero;

1> forward the variables BarringFactorForMMTEL-Voice, BarringTimeForMMTEL-Voice, BarringFactorForMMTEL-Video and BarringTimeForMMTEL-Video to the upper layers;

13.5.2.3 Test description

13.5.2.3.1 Pre-test conditions

System Simulator:

– Cell 1.

UE:

None.

Preamble:

– The UE is in state Registered, Idle mode (state 2) according to [18].

13.5.2.3.2 Test procedure sequence

Table 13.5.2.3.2-1: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

Make the UE attempt a MTSI MO Video call

2

Check: Does the UE transmit a RRCConnectionRequest message within 10 s?.

–>

RRCConnectionRequest

1

F

3

SS changes SIB2 according to TS 36.508, table 4.4.3.3-1 and transmits a Paging message including systemInfoModification. The systemInfoValueTag in the SystemInformationBlockType1 is increased.

<–

Paging

4

Wait for 15 s (Note 1) to allow the new system information to take effect.

5

Make the UE attempt a MTSI MO Video call

6

Check: Does the UE transmit an RRCConnectionRequest message with in 10s?

–>

RRCConnectionRequest

2

F

7

Wait for 49 s (Note 2) to make the timer Ty expire.

8-22

Steps 1 to 15 of the generic test procedure for MTSI MO Video call establishment in EUTRA: Normal Service (TS 36.508 4.5A.8.3-1).

Note 1: The wait time of 15 s in step 3 is to allow for the network to page the system information change during the next modification period, and update the system information at the subsequent modification period. UE should acquire the updated system information within 100ms of the start of modification period.

Note 2: The UE starts timer Ty in step2. Maximum time of timer Ty is 83.2 sec ((0.7 + 0.6 * 1) * s64). At the end of step 7, 35 sec elapses from step 2. Therefore 49 sec (84s – 35s) is enough to wait timer Ty expiry.

13.5.2.3.3 Specific message contents

Table 13.5.2.3.3-1: SystemInformationBlockType2 for Cell 1 (preamble and step 1, Table 13.5.2.3.2-1)

Derivation Path: 36.508, Table 4.4.3.3-1

Information Element

Value/remark

Comment

Condition

SystemInformationBlockType2 ::= SEQUENCE {

ssac-BarringForMMTEL-Video-r9 SEQUENCE {

ac-BarringFactor

p00

ac-BarringTime

s64

ac-BarringForSpecialAC

‘11111’B

}

}

Table 13.5.2.3.3-2: Paging (step3, Table 13.5.2.3.2-1)

Derivation Path: 36.508 Table 4.6.1-7

Information Element

Value/remark

Comment

Condition

Paging ::= SEQUENCE {

pagingRecordList

Not present

systemInfoModification

TRUE

}

13.5.2a MTSI MO video call / SSAC in Connected mode / 0% access probability for MTSI MO video call

13.5.2a.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_CONNECTED state having received a SysteminformationBlockType2 message including a ssac-BarringForMMTEL-Video-r9 set to 0% accessibility }

ensure that {
when { the user initiates a MTSI MO video call }

then { the UE does not initiate a MTSI MO video call }

}

(2)

with { UE in E-UTRA RRC_CONNECTED state having received a SysteminformationBlockType2 message including a ssac-BarringForMMTEL-Video-r9 with back-off timer Ty and having failed to initiate a voice call }

ensure that {
when { ssac-BarringForMMTEL-Video-r9 is removed and the user initiates a MTSI MO video call during back-off timer Ty is running }

then { the UE does not initiate a MTSI MO video call }

}

(3)

with { UE in E-UTRA RRC_CONNECTED state having received a SysteminformationBlockType2 message including a ssac-BarringForMMTEL-Video-r9 with back-off timer Ty and having failed to initiate a voice call }

ensure that {
when { the user initiates a MTSI MO video call afar expiring back-off timer Ty }

then { the UE initiates a MTSI MO video call }

}

13.5.2a.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 24.173 clause J.2.1.2 and TS 36.331 clause 5.3.3.10. Unless otherwise stated these are Rel-12 requirements.

[TS 24.173, clause J.2.1.2]:

The following information is provided by lower layer:

– BarringFactorForMMTEL-Voice: barring rate for MMTEL voice;

– BarringTimeForMMTEL-Voice: barring timer for MMTEL voice;

Upon request from a user to establish a multimedia telephony communication session as described in subclause 5.2, the UE shall:

1) if the multimedia telephony communication session to be established is an emergency session, then skip the rest of steps below and continue with session establishment as described in subclause 5.2;

2) retrieve SSAC related information mentioned above from lower layers;

3) if video is offered in the multimedia telephony communication session:

4) if audio is offered in the multimedia telephony communication session:

A) if back-off timer Ty is running, reject the multimedia telephony communication session establishment and skip the rest of steps below; or

B) else, then;

I) draw a new random number "rand3" that is uniformly distributed in the range 0 ≤ rand3 < 1; and

II) if the random number "rand3" is lower than BarringFactorForMMTEL-Voice, then skip the rest of steps below and continue with session establishment as described in subclause 5.2;

III) else, then;

i) draw a new random number "rand4" that is uniformly distributed in the range 0 ≤ rand4 < 1; and

ii) start timer Ty with the timer value calculated using the formula:

Ty = (0,7 + 0,6*rand4) * BarringTimeForMMTEL-Voice; and

iii) reject the multimedia telephony communication session establishment;

[TS 36.331 clause 5.3.3.10]:

Upon request from the upper layers, the UE shall:

1> set the local variables BarringFactorForMMTEL-Voice and BarringTimeForMMTEL-Voice as follows:

2> if ssac-BarringForMMTEL-Voice is present:

3> if the UE has one or more Access Classes, as stored on the USIM, with a value in the range 11..15, which is valid for the UE to use according to TS 22.011 [10] and TS 23.122 [11], and

NOTE: ACs 12, 13, 14 are only valid for use in the home country and ACs 11, 15 are only valid for use in the HPLMN/ EHPLMN.

3> if, for at least one of these Access Classes, the corresponding bit in the ac-BarringForSpecialAC contained in ssac-BarringForMMTEL-Voice is set to zero:

4> set BarringFactorForMMTEL-Voice to one and BarringTimeForMMTEL-Voice to zero;

3> else:

4> set BarringFactorForMMTEL-Voice and BarringTimeForMMTEL-Voice to the value of ac-BarringFactor and ac-BarringTime included in ssac-BarringForMMTEL-Voice, respectively;

2> else set BarringFactorForMMTEL-Voice to one and BarringTimeForMMTEL-Voice to zero;

1> set the local variables BarringFactorForMMTEL-Video and BarringTimeForMMTEL-Video as follows:

2> if ssac-BarringForMMTEL-Video is present:

3> if the UE has one or more Access Classes, as stored on the USIM, with a value in the range 11..15, which is valid for the UE to use according to TS 22.011 [10] and TS 23.122 [11], and

3> if, for at least one of these Access Classes, the corresponding bit in the ac-BarringForSpecialAC contained in ssac-BarringForMMTEL-Video is set to zero:

4> set BarringFactorForMMTEL-Video to one and BarringTimeForMMTEL-Video to zero;

3> else:

4> set BarringFactorForMMTEL-Video and BarringTimeForMMTEL-Video to the value of ac-BarringFactor and ac-BarringTime included in ssac-BarringForMMTEL-Video, respectively;

2> else set BarringFactorForMMTEL-Video to one and BarringTimeForMMTEL-Video to zero;

1> forward the variables BarringFactorForMMTEL-Voice, BarringTimeForMMTEL-Voice, BarringFactorForMMTEL-Video and BarringTimeForMMTEL-Video to the upper layers;

13.5.2a.3 Test description

13.5.2a.3.1 Pre-test conditions

System Simulator:

– Cell 1.

UE:

None.

Preamble:

– The UE is in state Generic RB Established (state 3) on Cell 1 according to [18].

13.5.2a.3.2 Test procedure sequence

Table 13.5.2a.3.2-1: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1-4

Void

5

Make the UE attempt a MTSI MO Video call

6

Check: Does the UE transmit an INVITE message with in 10s?

–>

INVITE

1

F

6AA

SS changes SIB2 according to TS 36.508, table 4.4.3.3-1 and transmits a Paging message including systemInfoModification. The systemInfoValueTag in the SystemInformationBlockType1 is increased.

<–

Paging

6AB

Wait for 15 s (Note 1) to allow the new system information to take effect.

6A

Make the UE attempt a MTSI MO Video call

6B

Check: Does the UE transmit an INVITE message during back-off timer Ty is running and within 10s?

–>

INVITE

2

F

7

Wait for 49 s (Note 2) to make the timer Ty expire.

8

Make the UE attempt a MTSI MO Video call

9

Check: Does the UE transmit an INVITE message within 10 s?

–>

INVITE

3

P

10-11

Steps 3 to 4 of the generic procedure for MTSI MO Video call establishment (TS 34.229-1 C.21)

12-14

Steps 12 to 14 of the generic procedure for MTSI MO Video call establishment (TS 36.508 table 4.5A.6.3-1).

Note 1: The wait time of 15 s in step 3 is to allow for the network to page the system information change during the next modification period, and update the system information at the subsequent modification period. UE should acquire the updated system information within 100ms of the start of modification period.

Note 2: The UE starts timer Ty in step 6. Maximum time of timer Ty is 83.2 sec ((0.7 + 0.6 * 1) * s64). At the end of step 6B , 20 sec elapses from the beginning of step 6. Therefore 64 sec (84s – 20s) is enough to wait timer Ty expiry.

13.5.2a.3.3 Specific message contents

Table 13.5.2a.3.3-1: SystemInformationBlockType2 for Cell 1 (preamble)

Derivation Path: 36.508, Table 4.4.3.3-1

Information Element

Value/remark

Comment

Condition

SystemInformationBlockType2 ::= SEQUENCE {

ssac-BarringForMMTEL-Video-r9 SEQUENCE {

ac-BarringFactor

p00

ac-BarringTime

s64

ac-BarringForSpecialAC

‘11111’B

}

}

Table 13.5.2a.3.3-2: Void

13.5.2b Void

13.5.3 Emergency call / Success / SSAC / 0% access probability for MTSI MO speech call

13.5.3.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_IDLE state having received a SysteminformationBlockType2 message including a ssac-BarringForMMTEL-Voice-r9 set to 0% accessibility }

ensure that {
when { the user initiates a MTSI MO emergency voice call }

then { the UE initiates a MTSI MO emergency voice call }

}

13.5.3.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 24.173 clause 5.2 and J.2.1.2, and TS 24.229 clause 5.1.6.2 and TS 36.331 clause 5.3.3.10. Unless otherwise stated these are Rel-9 requirements.

[TS 24.173 clause 5.2]:

The IMS multimedia telephony communication service can support different types of media, including media types listed in 3GPP TS 22.173 [2]. The session control procedures for the different media types shall be in accordance with 3GPP TS 24.229 [13] and 3GPP TS 24.247 [14], with the following additions:

[TS 24.173 clause J.2.1.1]:

The following information is provided by lower layer:

– BarringFactorForMMTEL-Voice: barring rate for MMTEL voice;

– BarringTimeForMMTEL-Voice: barring timer for MMTEL voice;

– BarringFactorForMMTEL-Video: barring rate for MMTEL video; and

– BarringTimeForMMTEL-Video: barring timer for MMTEL video.

Upon request from a user to establish a multimedia telephony communication session as described in subclause 5.2, the UE shall:

1) if the multimedia telephony communication session to be established is an emergency session, then skip the rest of steps below and continue with session establishment as described in subclause 5.2;

[TS 24.229 clause 5.1.6.2]:

When the user initiates an emergency call, if emergency registration is needed (including cases described in subclause 5.1.6.2A), the UE shall perform an emergency registration prior to sending the SIP request related to the emergency call.

The UE shall have only one valid emergency registration at any given time. If the UE initiates a new emergency registration using different contact address, and the previous emergency registration has not expired, the UE shall consider the previous emergency registration as expired.

When a UE performs an initial emergency registration the UE shall perform the actions as specified in subclause 5.1.1.2 with the following additions and modifications:

a) the UE shall include a "sos" SIP URI parameter in the Contact header field as described in subclause 7.2A.13, indicating that indicates that this is an emergency registration and that the associated contact address is allowed only for emergency service; and

b) the UE shall populate the From and To header fields of the REGISTER request with:

– the first entry in the list of public user identities provisioned in the UE;

– the default public user identity obtained during the normal registration, if the UE is not provisioned with a list of public user identities, but the UE is currently registered to the IM CN subsystem; and

– the derived temporary public user identity, in all other cases.

[TS 36.331 clause 5.3.3.10]:

Upon request from the upper layers, the UE shall:

1> set the local variables BarringFactorForMMTEL-Voice and BarringTimeForMMTEL-Voice as follows:

2> if ssac-BarringForMMTEL-Voice is present:

3> if the UE has one or more Access Classes, as stored on the USIM, with a value in the range 11..15, which is valid for the UE to use according to TS 22.011 [10] and TS 23.122 [11], and

NOTE: ACs 12, 13, 14 are only valid for use in the home country and ACs 11, 15 are only valid for use in the HPLMN/ EHPLMN.

3> if, for at least one of these Access Classes, the corresponding bit in the ac-BarringForSpecialAC contained in ssac-BarringForMMTEL-Voice is set to zero:

4> set BarringFactorForMMTEL-Voice to one and BarringTimeForMMTEL-Voice to zero;

3> else:

4> set BarringFactorForMMTEL-Voice and BarringTimeForMMTEL-Voice to the value of ac-BarringFactor and ac-BarringTime included in ssac-BarringForMMTEL-Voice, respectively;

2> else set BarringFactorForMMTEL-Voice to one and BarringTimeForMMTEL-Voice to zero;

1> set the local variables BarringFactorForMMTEL-Video and BarringTimeForMMTEL-Video as follows:

2> if ssac-BarringForMMTEL-Video is present:

3> if the UE has one or more Access Classes, as stored on the USIM, with a value in the range 11..15, which is valid for the UE to use according to TS 22.011 [10] and TS 23.122 [11], and

3> if, for at least one of these Access Classes, the corresponding bit in the ac-BarringForSpecialAC contained in ssac-BarringForMMTEL-Video is set to zero:

4> set BarringFactorForMMTEL-Video to one and BarringTimeForMMTEL-Video to zero;

3> else:

4> set BarringFactorForMMTEL-Video and BarringTimeForMMTEL-Video to the value of ac-BarringFactor and ac-BarringTime included in ssac-BarringForMMTEL-Video, respectively;

2> else set BarringFactorForMMTEL-Video to one and BarringTimeForMMTEL-Video to zero;

1> forward the variables BarringFactorForMMTEL-Voice, BarringTimeForMMTEL-Voice, BarringFactorForMMTEL-Video and BarringTimeForMMTEL-Video to the upper layers;

13.5.3.3 Test description

13.5.3.3.1 Pre-test conditions

System Simulator:

– Cell 1.

UE:

None.

Preamble:

– The UE is in state Registered, Idle mode (state 2) according to [18].

13.5.3.3.2 Test procedure sequence

Table 13.5.3.3.2-1: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1-18

Void

18A

Check: does the test result in generic test procedure in TS 36.508 subclause 4.5A.4.3 indicate that the UE establishes an IMS emergency call?

1

P

19-23

Steps 1 to 5 of the generic procedure for IMS speech call release (TS 34.229-1 C.32).

13.5.3.3.3 Specific message contents

Table 13.5.3.3.3-1: SystemInformationBlockType2 for Cell 1 (preamble, Table 13.5.3.3.2-1)

Derivation Path: 36.508, Table 4.4.3.3-1

Information Element

Value/remark

Comment

Condition

SystemInformationBlockType2 ::= SEQUENCE {

ac-BarringForEmergency

FALSE

ac-BarringForMO-Signalling

Not present

ac-BarringForMO-Data

Not present

ssac-BarringForMMTEL-Voice-r9 SEQUENCE {

ac-BarringFactor

p00

ac-BarringTime

s4

ac-BarringForSpecialAC

‘11111’B

}

}

13.5.3a Emergency call / Success / SSAC in Connected mode / 0% access probability for MTSI MO speech call

13.5.3a.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_CONNECTED state having received a SysteminformationBlockType2 message including a ssac-BarringForMMTEL-Voice-r9 set to 0% accessibility }

ensure that {
when { the user initiates a MTSI MO emergency voice call }

then { the UE initiate a MTSI MO emergency voice call }

}

13.5.3a.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 24.173 clause5.2 and J.2.1.2, TS 24.229 clause 5.1.6.2 and TS 36.331 clause 5.3.3.10. Unless otherwise stated these are Rel-12 requirements.

[TS 24.173 clause 5.2]:

The IMS multimedia telephony communication service can support different types of media, including media types listed in 3GPP TS 22.173 [2]. The session control procedures for the different media types shall be in accordance with 3GPP TS 24.229 [13] and 3GPP TS 24.247 [14], with the following additions:

[TS 24.173 clause J.2.1.1]:

The following information is provided by lower layer:

– BarringFactorForMMTEL-Voice: barring rate for MMTEL voice;

– BarringTimeForMMTEL-Voice: barring timer for MMTEL voice;

– BarringFactorForMMTEL-Video: barring rate for MMTEL video; and

– BarringTimeForMMTEL-Video: barring timer for MMTEL video.

Upon request from a user to establish a multimedia telephony communication session as described in subclause 5.2, the UE shall:

1) if the multimedia telephony communication session to be established is an emergency session, then skip the rest of steps below and continue with session establishment as described in subclause 5.2;

[TS 24.229 clause 5.1.6.2]:

When the user initiates an emergency call, if emergency registration is needed (including cases described in subclause 5.1.6.2A), the UE shall perform an emergency registration prior to sending the SIP request related to the emergency call.

The UE shall have only one valid emergency registration at any given time. If the UE initiates a new emergency registration using different contact address, and the previous emergency registration has not expired, the UE shall consider the previous emergency registration as expired.

When a UE performs an initial emergency registration the UE shall perform the actions as specified in subclause 5.1.1.2 with the following additions and modifications:

a) the UE shall include a "sos" SIP URI parameter in the Contact header field as described in subclause 7.2A.13, indicating that indicates that this is an emergency registration and that the associated contact address is allowed only for emergency service; and

b) the UE shall populate the From and To header fields of the REGISTER request with:

– the first entry in the list of public user identities provisioned in the UE;

– the default public user identity obtained during the normal registration, if the UE is not provisioned with a list of public user identities, but the UE is currently registered to the IM CN subsystem; and

– the derived temporary public user identity, in all other cases.

[TS 36.331 clause 5.3.3.10]:

Upon request from the upper layers, the UE shall:

1> set the local variables BarringFactorForMMTEL-Voice and BarringTimeForMMTEL-Voice as follows:

2> if ssac-BarringForMMTEL-Voice is present:

3> if the UE has one or more Access Classes, as stored on the USIM, with a value in the range 11..15, which is valid for the UE to use according to TS 22.011 [10] and TS 23.122 [11], and

NOTE: ACs 12, 13, 14 are only valid for use in the home country and ACs 11, 15 are only valid for use in the HPLMN/ EHPLMN.

3> if, for at least one of these Access Classes, the corresponding bit in the ac-BarringForSpecialAC contained in ssac-BarringForMMTEL-Voice is set to zero:

4> set BarringFactorForMMTEL-Voice to one and BarringTimeForMMTEL-Voice to zero;

3> else:

4> set BarringFactorForMMTEL-Voice and BarringTimeForMMTEL-Voice to the value of ac-BarringFactor and ac-BarringTime included in ssac-BarringForMMTEL-Voice, respectively;

2> else set BarringFactorForMMTEL-Voice to one and BarringTimeForMMTEL-Voice to zero;

1> set the local variables BarringFactorForMMTEL-Video and BarringTimeForMMTEL-Video as follows:

2> if ssac-BarringForMMTEL-Video is present:

3> if the UE has one or more Access Classes, as stored on the USIM, with a value in the range 11..15, which is valid for the UE to use according to TS 22.011 [10] and TS 23.122 [11], and

3> if, for at least one of these Access Classes, the corresponding bit in the ac-BarringForSpecialAC contained in ssac-BarringForMMTEL-Video is set to zero:

4> set BarringFactorForMMTEL-Video to one and BarringTimeForMMTEL-Video to zero;

3> else:

4> set BarringFactorForMMTEL-Video and BarringTimeForMMTEL-Video to the value of ac-BarringFactor and ac-BarringTime included in ssac-BarringForMMTEL-Video, respectively;

2> else set BarringFactorForMMTEL-Video to one and BarringTimeForMMTEL-Video to zero;

1> forward the variables BarringFactorForMMTEL-Voice, BarringTimeForMMTEL-Voice, BarringFactorForMMTEL-Video and BarringTimeForMMTEL-Video to the upper layers;

13.5.3a.3 Test description

13.5.3a.3.1 Pre-test conditions

System Simulator:

– Cell 1.

UE:

None.

Preamble:

– The UE is in state Generic RB Established (state 3) on Cell 1 according to [18].

13.5.3a.3.2 Test procedure sequence

Table 13.5.3a.3.2-1: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

Make the UE attempt an IMS emergency call

2-25

Void

25A1-25A7

Check: does the test result in generic test procedure in TS 36.508 subclause 4.5A.4.3 steps 9 to 15 indicate that the UE establishes an IMS emergency call?

1

P

26-30

Steps 1 to 5 of the generic procedure for IMS speech call release (TS 34.229-1 C.32).

13.5.3a.3.3 Specific message contents

Table 13.5.3a.3.3-1: SystemInformationBlockType2 for Cell 1 (preamble, Table 13.5.3a.3.2-1)

Derivation Path: 36.508, Table 4.4.3.3-1

Information Element

Value/remark

Comment

Condition

SystemInformationBlockType2 ::= SEQUENCE {

ssac-BarringForMMTEL-Voice-r9 SEQUENCE {

ac-BarringFactor

p00

ac-BarringTime

s4

ac-BarringForSpecialAC

‘11111’B

}

}

Table 13.5.3a.3.3-2: Void

13.5.4 MTSI MO speech call / SCM / 0% access probability skip for MTSI MO speech call

13.5.4.1 Test Purpose (TP)

(1)

Void

(2)

with { UE in E-UTRA RRC_IDLE state having received a SystemInformationBlockType2 message including an ac-BarringForMO-data set to 0% accessibility and including ac-BarringSkipForMMTELVoice-r12 }

ensure that {
when { the user initiates an MTSI MO voice call}

then { UE establishes an RRC connection and an MTSI voice call }

}

13.5.4.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 24.173 clause J.2.1.2, TS 24.301 clause 5.6.1.6 and TS 36.331 clause 5.3.3.2, 5.3.3.10 and 5.3.3.11. Unless otherwise stated these are Rel-12 requirements.

[TS 24.173, clause J.2.1.2]

The following information is provided by lower layer:

– BarringFactorForMMTEL-Voice: barring rate for MMTEL voice;

– BarringTimeForMMTEL-Voice: barring timer for MMTEL voice;

– BarringFactorForMMTEL-Video: barring rate for MMTEL video; and

– BarringTimeForMMTEL-Video: barring timer for MMTEL video.

Upon request from a user to establish a multimedia telephony communication session as described in subclause 5.2, the UE shall:

1) if the multimedia telephony communication session to be established is an emergency session, then skip the rest of steps below and continue with session establishment as described in subclause 5.2;

2) retrieve SSAC related information mentioned above from lower layers;

3) if video is offered in the multimedia telephony communication session:

A) if back-off timer Tx is running, reject the multimedia telephony communication session establishment and skip the rest of steps below; or

B) else, then:

I) draw a new random number "rand1" that is uniformly distributed in the range 0 ≤ rand1 < 1; and

II) if the random number "rand1" is lower than BarringFactorForMMTEL-Video, then skip the rest of steps below and continue with session establishment as described in subclause 5.2;

III) else, then;

i) draw a new random number "rand2" that is uniformly distributed in the range 0 ≤ rand2 < 1; and

ii) start back-off timer Tx with the timer value calculated using the formula:

Tx = (0,7 + 0,6*rand2) * BarringTimeForMMTEL-Video; and

iii) reject the multimedia telephony communication session establishment and skip the rest of steps below;

4) if audio is offered in the multimedia telephony communication session:

A) if back-off timer Ty is running, reject the multimedia telephony communication session establishment and skip the rest of steps below; or

B) else, then;

I) draw a new random number "rand3" that is uniformly distributed in the range 0 ≤ rand3 < 1; and

II) if the random number "rand3" is lower than BarringFactorForMMTEL-Voice, then skip the rest of steps below and continue with session establishment as described in subclause 5.2;

III) else, then;

i) draw a new random number "rand4" that is uniformly distributed in the range 0 ≤ rand4 < 1; and

ii) start timer Ty with the timer value calculated using the formula:

Ty = (0,7 + 0,6*rand4) * BarringTimeForMMTEL-Voice; and

iii) reject the multimedia telephony communication session establishment;

NOTE: If the multimedia telephony communication implementation and the access stratum protocol implementation are located in separate physical entities, it is expected that the interconnecting protocol supports the transfer of information elements needed for the service specific access control enforcement.

Service Specific Access Control is not activated when the UE is in other radio accesses (e.g. UTRAN/GERAN). And when UE camping on E-UTRAN moves to other radio accesses (e.g. UTRAN/GERAN), back-off timer (Tx or Ty or both) shall be stopped if running.

[TS 24.173, clause J.2.1.2]

The following information is provided to the non-access stratum:

– MO-MMTEL-voice-started;

– MO-MMTEL-voice-ended.

– MO-MMTEL-video-started; and

– MO-MMTEL-video-ended;

Upon request from a user to establish an originating multimedia telephony communication session as described in subclause 5.2, and if the session establishment is continued after performing the Service Specific Access Control as specified in subclause J.2.1.1:

1) if only audio or only real-time text or only both audio and real-time text (see subclause 4.2 for 3GPP systems) are offered in the multimedia telephony communication session, and no other originating multimedia telephony communication session initiated with offering only audio or only real-time text or only both audio and real-time text exists, the UE sends the MO-MMTEL-voice-started indication to the non-access stratum and continue with session establishment as described in subclause 5.2;

2) if video is offered in the multimedia telephony communication session, and no other originating multimedia telephony communication session initiated with offering video exists, the UE sends the MO-MMTEL-video-started indication to the non-access stratum and continue with session establishment as described in subclause 5.2.

When an originating multimedia telephony communication session ends (i.e. a response to a BYE or a failure response to the initial INVITE request is transferred), the originating multimedia telephony communication session was initiated with offering only audio or only real-time text or only both audio and real-time text (i.e. in the SDP offer in the initial INVITE request), and no other originating multimedia telephony communication session initiated with offering only audio or only real-time text or only both audio and real-time text exists, the UE sends the MO-MMTEL-voice-ended to the non-access stratum.

When an originating multimedia telephony communication session ends (i.e. a response to a BYE or a failure response to the initial INVITE request is transferred), the originating multimedia telephony communication session was initiated with offering video (i.e. in the SDP offer in the initial INVITE request), and no other originating multimedia telephony communication session initiated with offering video exists, the UE sends the MO-MMTEL-video-ended indication to the non-access stratum.

NOTE 1: If the UE supports other 3GPP specific mechanisms for communicating with the non-access stratum protocol implementation, e.g. DHCP discovery via PCO, then the UE is expected to support the transfer of information elements needed for the smart congestion mitigation enforcement.

NOTE 2: Adding or removing media during the multimedia telephony communication session has no impact on the information relating to smart congestion mitigation.

[TS 24.301, clause 5.6.5.6]

The following abnormal cases can be identified:

a) Access barred because of access class barring or NAS signalling connection establishment rejected by the network without "Extended wait time" received from lower layers

If the service request procedure is started in response to a paging request from the network, access class barring is not applicable.

If the trigger for the service request procedure is the response to a paging request from the network and the NAS signalling connection establishment is rejected by the network, the service request procedure shall not be started. The UE stays in the current serving cell and applies normal cell reselection process. The service request procedure may be started if it is still necessary, i.e. when access for "terminating calls" is granted or because of a cell change.

If the service request was initiated for CS fallback and the access is barred for "mobile originating CS fallback" (see 3GPP TS 36.331 [22]) and the lower layer indicates "the barring is due to CSFB specific access barring information", the service request procedure shall not be started. The UE stays in the current serving cell and applies normal cell reselection process. The service request procedure may be started if it is still necessary, i.e. when access for "mobile originating CS fallback" is granted or because of a cell change.

If the service request was initiated for CS fallback and a CS fallback cancellation request was not received and the access is barred for "mobile originating CS fallback" (see 3GPP TS 36.331 [22]) and the lower layer does not indicate "the barring is due to CSFB specific access barring information", the UE shall attempt to select GERAN or UTRAN radio access technology. If the UE finds a suitable GERAN or UTRAN cell, it then proceeds with the appropriate MM and CC specific procedures and the EMM sublayer shall not indicate the abort of the service request procedure to the MM sublayer. Otherwise the EMM sublayer shall indicate the abort of the service request procedure to the MM sublayer.

If the service request was initiated for 1xCS fallback and the access is barred for "originating calls" (see 3GPP TS 36.331 [22]), the UE shall select cdma2000® 1x radio access technology. The UE then proceeds with appropriate cdma2000® 1x CS procedures.

If the lower layer indicated the access was barred for "originating calls" (see 3GPP TS 36.331 [22]) and if:

– the service request is initiated due to a request from upper layers for user plane radio resources, and the MO MMTEL voice call is started, the MO MMTEL video call is started or the MO SMSoIP is started; or

– the service request is initiated due to a mobile originated SMS over NAS or SMS over S102;

then the service request procedure shall be started. The call type used shall be per annex D of this document.

NOTE 1: If more than one of MO MMTEL voice call is started, MO MMTEL video call is started or MO SMSoIP is started conditions are satisfied, it is left to UE implementation to determine the call type based on annex D of this document.

Otherwise, if access is barred for "originating calls" (see 3GPP TS 36.331 [22]), the service request procedure shall not be started. The UE stays in the current serving cell and applies normal cell reselection process. The service request procedure may be started if it is still necessary, i.e. when access for "originating calls" is granted or because of a cell change.

[TS 36.331, clause 5.3.3.2]

The UE initiates the procedure when upper layers request establishment of an RRC connection while the UE is in RRC_IDLE.

Upon initiation of the procedure, the UE shall:

1> if SystemInformationBlockType2 includes ac-BarringPerPLMN-List and the ac-BarringPerPLMN-List contains an AC-BarringPerPLMN entry with the plmn-IdentityIndex corresponding to the PLMN selected by upper layers (see TS 23.122 [11], TS 24.301 [35]):

2> select the AC-BarringPerPLMN entry with the plmn-IdentityIndex corresponding to the PLMN selected by upper layers;

2> in the remainder of this procedure, use the selected AC-BarringPerPLMN entry (i.e. presence or absence of access barring parameters in this entry) irrespective of the common access barring parameters included in SystemInformationBlockType2;

1> else

2> in the remainder of this procedure use the common access barring parameters (i.e. presence or absence of these parameters) included in SystemInformationBlockType2;

1> if upper layers indicate that the RRC connection is subject to EAB (see TS 24.301 [35]):

2> if the result of the EAB check, as specified in 5.3.3.12, is that access to the cell is barred:

3> inform upper layers about the failure to establish the RRC connection and that EAB is applicable, upon which the procedure ends;

1> if the UE is establishing the RRC connection for mobile terminating calls:

2> if timer T302 is running:

3> inform upper layers about the failure to establish the RRC connection and that access barring for mobile terminating calls is applicable, upon which the procedure ends;

1> else if the UE is establishing the RRC connection for mobile originating MMTEL voice, mobile originating MMTEL video, mobile originating SMSoIP or mobile originating SMS:

2> if the UE is establishing the RRC connection for mobile originating MMTEL voice and SystemInformationBlockType2 includes ac-BarringSkipForMMTELVoice; or

2> if the UE is establishing the RRC connection for mobile originating MMTEL video and SystemInformationBlockType2 includes ac-BarringSkipForMMTELVideo; or

2> if the UE is establishing the RRC connection for mobile originating SMSoIP or SMS and SystemInformationBlockType2 includes ac-BarringSkipForSMS:

3> consider access to the cell as not barred;

2> else:

3> if establishmentCause is set to mo-Signalling:

4> perform access barring check as specified in 5.3.3.11, using T305 as "Tbarring" and ac-BarringForMO-Signalling as "AC barring parameter";

4> if access to the cell is barred:

5> inform upper layers about the failure to establish the RRC connection and that access barring for mobile originating signalling is applicable, upon which the procedure ends;

3> if establishmentCause is set to mo-Data:

4> perform access barring check as specified in 5.3.3.11, using T303 as "Tbarring" and ac-BarringForMO-Data as "AC barring parameter";

4> if access to the cell is barred:

5> if SystemInformationBlockType2 includes ac-BarringForCSFB or the UE does not support CS fallback:

6> inform upper layers about the failure to establish the RRC connection and that access barring for mobile originating calls is applicable, upon which the procedure ends;

5> else (SystemInformationBlockType2 does not include ac-BarringForCSFB and the UE supports CS fallback):

6> if timer T306 is not running, start T306 with the timer value of T303;

6> inform upper layers about the failure to establish the RRC connection and that access barring for mobile originating calls and mobile originating CS fallback is applicable, upon which the procedure ends;

1> apply the default physical channel configuration as specified in 9.2.4;

1> apply the default semi-persistent scheduling configuration as specified in 9.2.3;

1> apply the default MAC main configuration as specified in 9.2.2;

1> apply the CCCH configuration as specified in 9.1.1.2;

1> apply the timeAlignmentTimerCommon included in SystemInformationBlockType2;

1> start timer T300;

1> initiate transmission of the RRCConnectionRequest message in accordance with 5.3.3.3;

[TS 36.331, clause 5.3.3.10]

Upon request from the upper layers, the UE shall:

1> if SystemInformationBlockType2 includes ac-BarringPerPLMN-List and the ac-BarringPerPLMN-List contains an AC-BarringPerPLMN entry with the plmn-IdentityIndex corresponding to the PLMN selected by upper layers (see TS 23.122 [11], TS 24.301 [35]):

2> select the AC-BarringPerPLMN entry with the plmn-IdentityIndex corresponding to the PLMN selected by upper layers;

2> in the remainder of this procedure, use the selected AC-BarringPerPLMN entry (i.e. presence or absence of access barring parameters in this entry) irrespective of the common access barring parameters included in SystemInformationBlockType2;

1> else:

2> in the remainder of this procedure use the common access barring parameters (i.e. presence or absence of these parameters) included in SystemInformationBlockType2;

1> set the local variables BarringFactorForMMTEL-Voice and BarringTimeForMMTEL-Voice as follows:

2> if ssac-BarringForMMTEL-Voice is present:

3> if the UE has one or more Access Classes, as stored on the USIM, with a value in the range 11..15, which is valid for the UE to use according to TS 22.011 [10] and TS 23.122 [11], and

NOTE: ACs 12, 13, 14 are only valid for use in the home country and ACs 11, 15 are only valid for use in the HPLMN/ EHPLMN.

3> if, for at least one of these Access Classes, the corresponding bit in the ac-BarringForSpecialAC contained in ssac-BarringForMMTEL-Voice is set to zero:

4> set BarringFactorForMMTEL-Voice to one and BarringTimeForMMTEL-Voice to zero;

3> else:

4> set BarringFactorForMMTEL-Voice and BarringTimeForMMTEL-Voice to the value of ac-BarringFactor and ac-BarringTime included in ssac-BarringForMMTEL-Voice, respectively;

2> else set BarringFactorForMMTEL-Voice to one and BarringTimeForMMTEL-Voice to zero;

1> set the local variables BarringFactorForMMTEL-Video and BarringTimeForMMTEL-Video as follows:

2> if ssac-BarringForMMTEL-Video is present:

3> if the UE has one or more Access Classes, as stored on the USIM, with a value in the range 11..15, which is valid for the UE to use according to TS 22.011 [10] and TS 23.122 [11], and

3> if, for at least one of these Access Classes, the corresponding bit in the ac-BarringForSpecialAC contained in ssac-BarringForMMTEL-Video is set to zero:

4> set BarringFactorForMMTEL-Video to one and BarringTimeForMMTEL-Video to zero;

3> else:

4> set BarringFactorForMMTEL-Video and BarringTimeForMMTEL-Video to the value of ac-BarringFactor and ac-BarringTime included in ssac-BarringForMMTEL-Video, respectively;

2> else set BarringFactorForMMTEL-Video to one and BarringTimeForMMTEL-Video to zero;

1> forward the variables BarringFactorForMMTEL-Voice, BarringTimeForMMTEL-Voice, BarringFactorForMMTEL-Video and BarringTimeForMMTEL-Video to the upper layers;

[TS 36.331, clause 5.3.3.10]

1> if timer T302 or "Tbarring" is running:

2> consider access to the cell as barred;

1> else if SystemInformationBlockType2 includes "AC barring parameter":

2> if the UE has one or more Access Classes, as stored on the USIM, with a value in the range 11..15, which is valid for the UE to use according to TS 22.011 [10] and TS 23.122 [11], and

NOTE: ACs 12, 13, 14 are only valid for use in the home country and ACs 11, 15 are only valid for use in the HPLMN/ EHPLMN.

2> for at least one of these valid Access Classes the corresponding bit in the ac-BarringForSpecialAC contained in "AC barring parameter" is set to zero:

3> consider access to the cell as not barred;

2> else:

3> draw a random number ‘rand‘ uniformly distributed in the range: 0 ≤ rand < 1;

3> if ‘rand‘ is lower than the value indicated by ac-BarringFactor included in "AC barring parameter":

4> consider access to the cell as not barred;

3> else:

4> consider access to the cell as barred;

1> else:

2> consider access to the cell as not barred;

1> if access to the cell is barred and both timers T302 and "Tbarring" are not running:

2> draw a random number ‘rand‘ that is uniformly distributed in the range 0 ≤ rand < 1;

2> start timer "Tbarring" with the timer value calculated as follows, using the ac-BarringTime included in "AC barring parameter":

"Tbarring" = (0.7+ 0.6 * rand) * ac-BarringTime.

13.5.4.3 Test description

13.5.4.3.1 Pre-test conditions

System Simulator:

– Cell 1.

UE:

None.

Preamble:

– The UE is in state Registered, Idle mode (state 2) according to [18].

13.5.4.3.2 Test procedure sequence

Table 13.5.4.3.2-1: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

Void

2

Void

3

SS changes SIB2 according to table 13.5.4.3.3-2 and transmits a Paging message including systemInfoModification. The systemInfoValueTag in the SystemInformationBlockType1 is increased.

<–

Paging

3A

Wait for 13 s (Note 1) to allow the new system information to take effect.

4

Make the UE attempt an MTSI MO Speech call.

5

Check: Does the UE transmit an RRCConnectionRequest message?

–>

RRCConnectionRequest

2

P

6-18

Steps 3 to 15 of the generic test procedure for IMS MO Speech call establishment in EUTRA: Normal Service (TS 36.508 4.5A.6.3-1).

19

Check: Does the test result of generic test procedure in TS 36.508 subclause 6.4.2.3 indicate that the UE is in E-UTRA RRC_CONNECTED state on Cell 1?

Note 1: The wait time of 13 s in step 3A is to allow for the network to page the system information change during the next modification period, and update the system information at the subsequent modification period. UE should acquire the updated system information within 100ms of the start of modification period.

13.5.4.3.3 Specific message contents

Table 13.5.4.3.3-1: Void

Table 13.5.4.3.3-2: SystemInformationBlockType2 for Cell 1 (step 3, Table 13.5.4.3.2-1)

Derivation Path: 36.508, Table 4.4.3.3-1

Information Element

Value/remark

Comment

Condition

SystemInformationBlockType2 ::= SEQUENCE {

ac-BarringInfo SEQUENCE {

ac-BarringForEmergency

FALSE

ac-BarringForMO-Data SEQUENCE {

ac-BarringFactor

p0

ac-BarringTime

s512

ac-BarringForSpecialAC

‘11111’B

}

}

ac-BarringSkipForMMTELVoice-r12

TRUE

}

13.5.5 MTSI MO video call / SCM / 0% access probability skip for MTSI MO video call

13.5.5.1 Test Purpose (TP)

(1)

Void

(2)

with { UE in E-UTRA RRC_IDLE state having received a SystemInformationBlockType2 indicating 0% access probability for MO calls and including ac-BarringSkipForMMTELVideo-r12}

ensure that {
when { the user initiates an MTSI MO video call }

then { UE establishes an RRC connection and an MTSI video call }

}

13.5.5.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 36.331, clause 5.3.3.2, 5.3.3.10 and 5.3.3.11.

[TS 36.331, clause 5.3.3.2]

The UE initiates the procedure when upper layers request establishment of an RRC connection while the UE is in RRC_IDLE.

Upon initiation of the procedure, the UE shall:

1> else if the UE is establishing the RRC connection for mobile originating MMTEL voice, mobile originating MMTEL video, mobile originating SMSoIP or mobile originating SMS:

2> if the UE is establishing the RRC connection for mobile originating MMTEL voice and SystemInformationBlockType2 includes ac-BarringSkipForMMTELVoice; or

2> if the UE is establishing the RRC connection for mobile originating MMTEL video and SystemInformationBlockType2 includes ac-BarringSkipForMMTELVideo; or

2> if the UE is establishing the RRC connection for mobile originating SMSoIP or SMS and SystemInformationBlockType2 includes ac-BarringSkipForSMS:

3> consider access to the cell as not barred;

2> else:

3> if establishmentCause is set to mo-Signalling:

4> perform access barring check as specified in 5.3.3.11, using T305 as "Tbarring" and ac-BarringForMO-Signalling as "AC barring parameter";

4> if access to the cell is barred:

5> inform upper layers about the failure to establish the RRC connection and that access barring for mobile originating signalling is applicable, upon which the procedure ends;

3> if establishmentCause is set to mo-Data:

4> perform access barring check as specified in 5.3.3.11, using T303 as "Tbarring" and ac-BarringForMO-Data as "AC barring parameter";

4> if access to the cell is barred:

5> if SystemInformationBlockType2 includes ac-BarringForCSFB or the UE does not support CS fallback:

6> inform upper layers about the failure to establish the RRC connection and that access barring for mobile originating calls is applicable, upon which the procedure ends;

5> else (SystemInformationBlockType2 does not include ac-BarringForCSFB and the UE supports CS fallback):

6> if timer T306 is not running, start T306 with the timer value of T303;

6> inform upper layers about the failure to establish the RRC connection and that access barring for mobile originating calls and mobile originating CS fallback is applicable, upon which the procedure ends;

1> apply the default physical channel configuration as specified in 9.2.4;

1> apply the default semi-persistent scheduling configuration as specified in 9.2.3;

1> apply the default MAC main configuration as specified in 9.2.2;

1> apply the CCCH configuration as specified in 9.1.1.2;

1> apply the timeAlignmentTimerCommon included in SystemInformationBlockType2;

1> start timer T300;

1> initiate transmission of the RRCConnectionRequest message in accordance with 5.3.3.3;

[TS 36.331, clause 5.3.3.10]

Upon request from the upper layers, the UE shall:

1> if SystemInformationBlockType2 includes ac-BarringPerPLMNList and the ac-BarringPerPLMNList contains an AC-BarringPerPLMN entry with the plmn-IdentityIndex corresponding to the PLMN selected by upper layers (see TS 23.122 [11], TS 24.301 [35]):

2> select the AC-BarringPerPLMN entry with the plmn-IdentityIndex corresponding to the PLMN selected by upper layers;

2> for the remainder of this procedure use the present/absent access barring parameters in the selected AC-BarringPerPLMN entry when determining whether the access to the cell is barred, irrespective of the common access barring parameters included in SystemInformationBlockType2;

1> else

2> for the remainder of this procedure use the present/absent common access barring parameters included in SystemInformationBlockType2;

1> set the local variables BarringFactorForMMTEL-Voice and BarringTimeForMMTEL-Voice as follows:

2> if ssac-BarringForMMTEL-Voice is present:

3> if the UE has one or more Access Classes, as stored on the USIM, with a value in the range 11..15, which is valid for the UE to use according to TS 22.011 [10] and TS 23.122 [11], and

NOTE: ACs 12, 13, 14 are only valid for use in the home country and ACs 11, 15 are only valid for use in the HPLMN/ EHPLMN.

3> if, for at least one of these Access Classes, the corresponding bit in the ac-BarringForSpecialAC contained in ssac-BarringForMMTEL-Voice is set to zero:

4> set BarringFactorForMMTEL-Voice to one and BarringTimeForMMTEL-Voice to zero;

3> else:

4> set BarringFactorForMMTEL-Voice and BarringTimeForMMTEL-Voice to the value of ac-BarringFactor and ac-BarringTime included in ssac-BarringForMMTEL-Voice, respectively;

2> else set BarringFactorForMMTEL-Voice to one and BarringTimeForMMTEL-Voice to zero;

1> set the local variables BarringFactorForMMTEL-Video and BarringTimeForMMTEL-Video as follows:

2> if ssac-BarringForMMTEL-Video is present:

3> if the UE has one or more Access Classes, as stored on the USIM, with a value in the range 11..15, which is valid for the UE to use according to TS 22.011 [10] and TS 23.122 [11], and

3> if, for at least one of these Access Classes, the corresponding bit in the ac-BarringForSpecialAC contained in ssac-BarringForMMTEL-Video is set to zero:

4> set BarringFactorForMMTEL-Video to one and BarringTimeForMMTEL-Video to zero;

3> else:

4> set BarringFactorForMMTEL-Video and BarringTimeForMMTEL-Video to the value of ac-BarringFactor and ac-BarringTime included in ssac-BarringForMMTEL-Video, respectively;

2> else set BarringFactorForMMTEL-Video to one and BarringTimeForMMTEL-Video to zero;

1> forward the variables BarringFactorForMMTEL-Voice, BarringTimeForMMTEL-Voice, BarringFactorForMMTEL-Video and BarringTimeForMMTEL-Video to the upper layers;

[TS 36.331, clause 5.3.3.11]

1> if timer T302 or "Tbarring" is running:

2> consider access to the cell as barred;

1> else if SystemInformationBlockType2 includes "AC barring parameter":

2> if the UE has one or more Access Classes, as stored on the USIM, with a value in the range 11..15, which is valid for the UE to use according to TS 22.011 [10] and TS 23.122 [11], and

NOTE: ACs 12, 13, 14 are only valid for use in the home country and ACs 11, 15 are only valid for use in the HPLMN/ EHPLMN.

2> for at least one of these valid Access Classes the corresponding bit in the ac-BarringForSpecialAC contained in "AC barring parameter" is set to zero:

3> consider access to the cell as not barred;

2> else:

3> draw a random number ‘rand‘ uniformly distributed in the range: 0 ≤ rand < 1;

3> if ‘rand‘ is lower than the value indicated by ac-BarringFactor included in "AC barring parameter":

4> consider access to the cell as not barred;

3> else:

4> consider access to the cell as barred;

1> else:

2> consider access to the cell as not barred;

1> if access to the cell is barred and both timers T302 and "Tbarring" are not running:

2> draw a random number ‘rand‘ that is uniformly distributed in the range 0 ≤ rand < 1;

2> start timer "Tbarring" with the timer value calculated as follows, using the ac-BarringTime included in "AC barring parameter":

"Tbarring" = (0.7+ 0.6 * rand) * ac-BarringTime.

13.5.5.3 Test description

13.5.5.3.1 Pre-test conditions

System Simulator:

– Cell 1.

UE:

None.

Preamble:

– The UE is in state Registered, Idle mode (state 2) according to [18].

13.5.5.3.2 Test procedure sequence

Table 13.5.5.3.2-1: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

Void

2

Void

3

SS changes SIB2 IE ac-BarringSkipForMMTELVideo-r12 according to table 13.5.5.3.3-2 and transmits a Paging message including systemInfoModification. The systemInfoValueTag in the SystemInformationBlockType1 is increased.

<–

Paging

3A

Wait for 13 s (Note 1) to allow the new system information to take effect.

4

Make the UE attempt an MTSI MO Video call

5

Check: Does the UE transmit an RRCConnectionRequest message?

–>

RRCConnectionRequest

2

P

6-18

Steps 3 to 15 of the generic test procedure for IMS MO Video call establishment in EUTRA: Normal Service (TS 36.508 4.5A.8.3-1).

19

Check: Does the test result of generic test procedure in TS 36.508 subclause 6.4.2.3 indicate that the UE is in E-UTRA RRC_CONNECTED state on Cell 1?

Note 1: The wait time of 13 s in step 3A is to allow for the network to page the system information change during the next modification period, and update the system information at the subsequent modification period. UE should acquire the updated system information within 100ms of the start of modification period.

13.5.5.3.3 Specific message contents

Table 13.5.5.3.3-1: Void

Table 13.5.5.3.3-2: SystemInformationBlockType2 for Cell 1 (step 3, Table 13.5.5.3.2-1)

Derivation Path: 36.508, Table 4.4.3.3-1

Information Element

Value/remark

Comment

Condition

SystemInformationBlockType2 ::= SEQUENCE {

ac-BarringInfo SEQUENCE {

ac-BarringForEmergency

FALSE

ac-BarringForMO-Data SEQUENCE {

ac-BarringFactor

p0

ac-BarringTime

s512

ac-BarringForSpecialAC

‘11111’B

}

}

ac-BarringSkipForMMTELVideo-r12

TRUE

}

13.5.6 MTSI MO SMS / SCM / 0% access probability skip for MTSI MO SMS over IP

13.5.6.1 Test Purpose (TP)

(1)

Void

(2)

with { UE in E-UTRA RRC_IDLE state having received a SystemInformationBlockType2 message including an ac-BarringForMO-data set to 0% accessibility and including ac-BarringSkipForSMS-r12 }

ensure that {
when { the user initiates a SMS over IP }

then { the UE establishes an RRC connection and SMS over IP transfer }

}

13.5.6.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 24.173 clause J.2.1.2, TS 24.301 clause 5.6.1.6 and TS 36.331 clause 5.3.3.2, 5.3.3.10 and 5.3.3.11. Unless otherwise stated these are Rel-12 requirements.

[TS 36.331, clause 5.3.3.2]

The UE initiates the procedure when upper layers request establishment of an RRC connection while the UE is in RRC_IDLE.

Upon initiation of the procedure, the UE shall:

1> else if the UE is establishing the RRC connection for mobile originating MMTEL voice, mobile originating MMTEL video, mobile originating SMSoIP or mobile originating SMS:

2> if the UE is establishing the RRC connection for mobile originating MMTEL voice and SystemInformationBlockType2 includes ac-BarringSkipForMMTELVoice; or

2> if the UE is establishing the RRC connection for mobile originating MMTEL video and SystemInformationBlockType2 includes ac-BarringSkipForMMTELVideo; or

2> if the UE is establishing the RRC connection for mobile originating SMSoIP or SMS and SystemInformationBlockType2 includes ac-BarringSkipForSMS:

3> consider access to the cell as not barred;

2> else:

3> if establishmentCause is set to mo-Data:

4> perform access barring check as specified in 5.3.3.11, using T303 as "Tbarring" and ac-BarringForMO-Data as "AC barring parameter";

4> if access to the cell is barred:

5> if SystemInformationBlockType2 includes ac-BarringForCSFB or the UE does not support CS fallback:

6> inform upper layers about the failure to establish the RRC connection and that access barring for mobile originating calls is applicable, upon which the procedure ends;

5> else (SystemInformationBlockType2 does not include ac-BarringForCSFB and the UE supports CS fallback):

6> if timer T306 is not running, start T306 with the timer value of T303;

6> inform upper layers about the failure to establish the RRC connection and that access barring for mobile originating calls and mobile originating CS fallback is applicable, upon which the procedure ends;

1> apply the default physical channel configuration as specified in 9.2.4;

1> apply the default semi-persistent scheduling configuration as specified in 9.2.3;

1> apply the default MAC main configuration as specified in 9.2.2;

1> apply the CCCH configuration as specified in 9.1.1.2;

1> apply the timeAlignmentTimerCommon included in SystemInformationBlockType2;

1> start timer T300;

1> initiate transmission of the RRCConnectionRequest message in accordance with 5.3.3.3;

[TS 36.331, clause 5.3.3.11]

1> if timer T302 or "Tbarring" is running:

2> consider access to the cell as barred;

1> else if SystemInformationBlockType2 includes "AC barring parameter":

2> if the UE has one or more Access Classes, as stored on the USIM, with a value in the range 11..15, which is valid for the UE to use according to TS 22.011 [10] and TS 23.122 [11], and

NOTE: ACs 12, 13, 14 are only valid for use in the home country and ACs 11, 15 are only valid for use in the HPLMN/ EHPLMN.

2> for at least one of these valid Access Classes the corresponding bit in the ac-BarringForSpecialAC contained in "AC barring parameter" is set to zero:

3> consider access to the cell as not barred;

2> else:

3> draw a random number ‘rand‘ uniformly distributed in the range: 0 ≤ rand < 1;

3> if ‘rand‘ is lower than the value indicated by ac-BarringFactor included in "AC barring parameter":

4> consider access to the cell as not barred;

3> else:

4> consider access to the cell as barred;

1> else:

2> consider access to the cell as not barred;

1> if access to the cell is barred and both timers T302 and "Tbarring" are not running:

2> draw a random number ‘rand‘ that is uniformly distributed in the range 0 ≤ rand < 1;

2> start timer "Tbarring" with the timer value calculated as follows, using the ac-BarringTime included in "AC barring parameter":

"Tbarring" = (0.7+ 0.6 * rand) * ac-BarringTime.

13.5.6.3 Test description

13.5.6.3.1 Pre-test conditions

System Simulator:

– Cell 1.

UE:

None.

Preamble:

– The UE is in state Registered, Idle mode (state 2) according to [18].

13.5.6.3.2 Test procedure sequence

Table 13.5.6.3.2-1: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

Void

2

Void

3

SS changes SIB2 IE ac-BarringSkipForSMS-r12 according to table 13.5.6.3.3-1 and transmits a Paging message including systemInfoModification. The systemInfoValueTag in the SystemInformationBlockType1 is increased.

4

Wait for 13 s (Note 1) to allow the new system information to take effect.

5

Make the UE attempt a SMS over IP.

6

Check: Does the UE transmit an RRCConnectionRequest message?

–>

RRCConnectionRequest

2

P

7-11

Steps 3 to 7 of the generic test procedure TS 36.508 4.5A.6.3 are performed.

EXCEPTION: In parallel to the events described in step 12 below, steps 1 to 8 from test procedure for Mobile Originating SMS as described in 34.229-1 section 18.1.4 take place.

12

Step 8 of the generic test procedure TS 36.508 4.5A.6.3 is performed.

2

P

13-18

Void

Note 1: The wait time of 13 s is to allow for the network to page the system information change during the next modification period, and update the system information at the subsequent modification period. UE should acquire the updated system information within 100ms of the start of modification period.

13.5.6.3.3 Specific message contents

Table 13.5.6.3.3-1: Void

Table 13.5.6.3.3-2: SystemInformationBlockType2 for Cell 1 (step 3, Table 13.5.6.3.2-1)

Derivation Path: 36.508, Table 4.4.3.3-1

Information Element

Value/remark

Comment

Condition

SystemInformationBlockType2 ::= SEQUENCE {

ac-BarringInfo SEQUENCE {

ac-BarringForEmergency

FALSE

ac-BarringForMO-Signalling

Not present

ac-BarringForMO-Data SEQUENCE {

ac-BarringFactor

p00

ac-BarringTime

s512

ac-BarringForSpecialAC

‘11111’B

}

ac-BarringSkipForSMS-r12

true

}

}