31.8 Call restriction supplementary services

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

The following abbreviations are used:

BO: Barring of Outgoing calls.

BAOC: Barring of All Outgoing Calls.

BOIC: Barring of Outgoing International Calls.

BOICExHC: Barring of Outgoing International Call EXcept those directed to the Home PLMN country.

BI: Barring of Incoming calls.

BAIC: Barring of All Incoming calls.

BICRoam: Barring of Incoming when Roaming outside the home PLMN country.

B: Barring (common name for BAOC, BOIC, BOICExHC, BAIC and BICRoam).

These abbreviations are also used to represent the corresponding SS-Code; e.g. B is the SS-Code for all barring services.

NOTE: The password(s) to be used during tests of this subclause 31.8 may be randomly chosen – unless otherwise stated – in accordance with 3GPP TS 02.04 subclause 5.2.

31.8.1 Registration of a password

31.8.1.1 Registration accepted

31.8.1.1.1 Conformance requirements

1) For registration of a password for all barring services, the MS shall transmit successively:

1.1) a CHANNEL REQUEST with establishment cause set to "other services requested by the mobile user";

1.2) a CM SERVICE REQUEST with CM service type indicating "supplementary service activation";

1.3) and then the REGISTER message containing a facility IE that includes an invoke of the RegisterPassword operation with parameter values according to the user’s request (MMI action).

2) When the mobile subscriber wants to register a new password, the old password, the new password and the repeat of the new password shall be entered into the MS. Then the MS sends to the network an invoke component of the operation "register password".

3) The MS shall be able to send a password by sending a FACILITY message in accordance to the user request (MMI actions).

4) Upon receipt of the result of the procedure, contained in RELEASE COMPLETE or FACILITY message, the MS shall provide the appropriate user indication (which is to be described by the manufacturer).

References

1.1) 3GPP TS 04.08 / 3GPP TS 44.018 subclauses 3.3.1.1.2 and 9.1.9.

1.2) 3GPP TS 04.08 / 3GPP TS 24.008 subclauses 4.5.1.1, 9.2.9 and 10.5.3.3.

1.3) 3GPP TS 04.88, 3GPP TS 04.80 subclauses 2.3 and 3.6.

2) 3GPP TS 04.10 subclause 4.2.

3) 3GPP TS 04.80.

4) 3GPP TS 02.30.

31.8.1.1.2 Test purpose

1) To check that the MS correctly requests a supplementary service transaction for registration of a password for all barring services in CHANNEL REQUEST message.

2) To check that the MS correctly requests a supplementary service transaction for registration of a password for all barring services in the subsequent CM SERVICE REQUEST.

3) To check that the MS sends a REGISTER message containing the invoke of the RegisterPassword operation with the expected parameter values for registration of a password for all barring services.

4) To check that when the mobile subscriber wants to register a new password, the old password, the new password and the repeat of the new password shall be entered into the MS before the MS sends to the network a CHANNEL REQUEST.

5) To check that the MS is able to send a password by sending a FACILITY message in accordance to the user request (MMI actions).

6) To check that upon receipt of the result of the procedure, contained in RELEASE COMPLETE or FACILITY message, the MS provides the appropriate user indication (as described by the manufacturer).

These checks are done for:

– All barring services, the result of the operation being sent in a RELEASE COMPLETE message.

31.8.1.1.3 Method of test

Initial conditions

System Simulator:

1 cell, default parameters.

Mobile Station:

The MS is "idle updated".

Specific PICS Statements

PIXIT Statements

– Description of the user’s commands and of display of the answers from the network for call barring.

Foreseen final state of the MS

The MS is "idle updated".

Test procedure

By means of appropriate MMI functions (using either 3GPP TS 02.30 or manufacturer defined MMI), the user requests registration of a new password for all barring services by entering the old password, new password and a repeat of the old password.

Upon receipt of the operation (in a REGISTER message), the system simulator answers with the FACILITY message with the Facility information element containing an invoke of the GetPassword operation requiring the old password.

Upon receipt of the FACILITY message, the system simulator answers with the FACILITY message with the Facility information element containing an invoke of the GetPassword operation requiring a new password.

Upon receipt of the FACILITY message, the system simulator answers with the FACILITY message with the Facility information element containing an invoke of the GetPassword operation requiring again the new password.

Upon receipt of the FACILITY message, the system simulator answers with the RELEASE COMPLETE message with the Facility information element containing the return result of the RegisterPassword operation.

Maximum duration of test

3 minutes.

Expected sequence

Step

Direction

Message

Comments

1

MS

The MS is made to initiate a registration of a password for all call barring services. The old password, the new password and a repeat of the new password are entered.

2

MS -> SS

CHANNEL REQUEST

with establishment cause "Other procedures which can be completed with an SDCCH"

3

SS -> MS

IMMEDIATE ASSIGNMENT

4

MS -> SS

CM SERVICE REQUEST

cause: "supplementary service activation"

5

SS -> MS

CM SERVICE ACCEPT

6

MS -> SS

REGISTER

7

SS -> MS

FACILITY

Invoke = GetPassword (password)

8

MS -> SS

FACILITY

GetPassword operation ReturnResult

9

SS -> MS

FACILITY

Invoke = GetPassword (new password)

10

MS -> SS

FACILITY

GetPassword operation ReturnResult

11

SS -> MS

FACILITY

Invoke = GetPassword (new password again)

12

MS -> SS

FACILITY

GetPassword operation ReturnResult

13

SS -> MS

RELEASE COMPLETE

RegisterPassword operation ReturnResult

14

SS -> MS

CHANNEL RELEASE

Specific message content

step 6 –

– protocol discriminator: non call related SS message.

– message type: REGISTER.

– facility:

invoke = RegisterPassword:

Supplementary service code = B.

steps 7, 9, and 11 –

– protocol discriminator: non call related SS message.

– message type: FACILITY.

– facility:

invoke = GetPassword:

Guidance info: Password (step 7), new password (step 9), new password again (step 11).

The linked ID must be the same as the invoke ID in the invoke of the RegisterPassword operation.

31.8.1.2 Registration rejected

31.8.1.2.1 Rejection after invoke of the RegisterPassword operation

31.8.1.2.1.1 Conformance requirements

1) A transaction of any kind being already established, for registration of a password for all call restriction services, the MS shall establish a parallel MM transaction, sending a CM SERVICE REQUEST with CM service type indicating "supplementary service activation",

2) Then the MS shall send a REGISTER message related to the present SS transaction containing a facility IE that includes an invoke of the RegisterPassword operation with parameter values according to the user’s request (MMI action).

3) Upon receipt of the RELEASE COMPLETE message related to the present SS transaction, the SS transaction shall be released but the first transaction shall remain unaffected.

4) Upon receipt of the RELEASE COMPLETE message, the MS shall provide the appropriate user indication (which is to be described by the Manufacturer).

References

1) 3GPP TS 04.08 / 3GPP TS 44.018 subclauses 3.3.1.1.2 and 9.1.9.

2) 3GPP TS 04.08 / 3GPP TS 24.008 subclauses 4.5.1.1, 9.2.9 and 10.5.3.3.

3) 3GPP TS 04.88,
3GPP TS 04.80 subclauses 2.3 and 3.6.

4) 3GPP TS 02.30 subclause 4.5.

31.8.1.2.1.2 Test purpose

1) To check that, when a call transaction is already established, the MS correctly requests the establishment of a parallel MM transaction for supplementary service transaction of registration of a password for all call restriction services, sending a CM SERVICE REQUEST.

2) To check that the MS sends a REGISTER message containing the invoke of the RegisterPassword operation with the expected parameter values for registration of a password for all call restriction services.

3) To check that upon receipt of the RELEASE COMPLETE message related to the present SS transaction, the first transaction remains unaffected.

4) To check that upon receipt of the RELEASE COMPLETE message, the MS provides the appropriate user indication (as described by the Manufacturer).

Those checks are performed with a call transaction already established for:

– all call restriction services, the RELEASE COMPLETE message being sent at the beginning of the procedure with a facility IE containing a return_error(error) where error is "SS subscription violation".

31.8.1.2.1.3 Method of test

Initial conditions

System Simulator:

1 cell, default parameters.

Mobile Station:

The MS is in CC state U10.

Specific PICS Statements

PIXIT Statements

– Description of the user’s commands and of display of the answers from the network for call barring.

Foreseen final state of the MS

The MS is in CC state U10.

Test procedure

By means of appropriate MMI functions (using either 3GPP TS 02.30 or manufacturer defined MMI), the user requests registration of a new password for all call restriction services by entering the old password, the new password and a repeat of the new password.

Upon receipt of the operation (in a REGISTER message), the system simulator answers with the RELEASE COMPLETE (PD and TI of the SS transaction) message with the Facility information element containing a Return_error(error: SS subscription violation) of the RegisterPassword operation.

Upon receipt of the FACILITY message, the system simulator sends STATUS ENQUIRY, the MS responds with STATUS message indicating CC state U10.

Maximum duration of test

2 minutes.

Expected sequence

Step

Direction

Message

Comments

1

MS

The MS is made to initiate a registration of a new password for all call restriction services. The old password, the new password and a repeat of the new password are entered.

2

MS -> SS

CM SERVICE REQUEST

cause: "supplementary service activation"

3

SS -> MS

CM SERVICE ACCEPT

4

MS -> SS

REGISTER

5

SS -> MS

RELEASE COMPLETE

RegisterPassword operation Return_error

6

MS

provide correct MMI user indication

7

SS -> MS

STATUS ENQUIRY

8

MS -> SS

STATUS

CC staTE U10

Specific message content

step 4 –

– protocol discriminator: non call related SS message.

– message type: REGISTER.

– facility:

invoke = RegisterPassword:

Supplementary service code = all call restrictions.

step 5 –

– protocol discriminator: non call related SS message.

– transaction identifier: same TI as previous REGISTER message.

– message type: RELEASE COMPLETE.

– facility:

return error code: SS subscription violation.

For the return error the invoke ID must be the same as in the invoke of the RegisterPassword operation.

31.8.1.2.2 Rejection after password check with negative result

31.8.1.2.2.1 Conformance requirements

1) A transaction of any kind being already established, for registration of a password for all call restriction services, the MS shall establish a parallel MM transaction, sending a CM SERVICE REQUEST with CM service type indicating "supplementary service activation".

2) Then the MS shall send a REGISTER message related to the present SS transaction containing a facility IE that includes an invoke of the RegisterPassword operation with parameter values according to the user’s request (MMI action).

3) Upon receipt of the RELEASE COMPLETE message related to the present SS transaction, the SS transaction shall be released but the first transaction shall remain unaffected.

4) Upon receipt of the RELEASE COMPLETE message, the MS shall provide the appropriate user indication (which is to be described by the Manufacturer).

References

1) 3GPP TS 04.08 / 3GPP TS 44.018 subclauses 3.3.1.1.2 and 9.1.9.

2) 3GPP TS 04.08 / 3GPP TS 24.008 subclauses 4.5.1.1, 9.2.9 and 10.5.3.3.

3) 3GPP TS 04.88,
3GPP TS 04.80 subclauses 2.3 and 3.6,
3GPP TS 04.10 subclause 4.2.2,
3GPP TS 03.11 clause 3.

4) 3GPP TS 02.30 subclause 4.5.

31.8.1.2.2.2 Test purpose

1) To check that, when a call transaction is already established, the MS correctly requests the establishment of a parallel MM transaction for supplementary service transaction of registration of a password for all call restriction services, sending a CM SERVICE REQUEST.

2) To check that the MS sends a REGISTER message containing the invoke of the RegisterPassword operation with the expected parameter values for registration of a password for all call restriction services.

3) To check that upon receipt of the RELEASE COMPLETE message related to the present SS transaction, the first transaction remains unaffected.

4) To check that upon receipt of the RELEASE COMPLETE message, the MS provides the appropriate user indication (as described by the Manufacturer).

Those checks are performed with a call transaction already established for:

– all call restriction services, the RELEASE COMPLETE message being sent at the end of the procedure with a facility IE containing a return_error(error) where error is "NegativePasswordCheck".

31.8.1.2.2.3 Method of test

Initial conditions

System Simulator:

1 cell, default parameters.

WPA > 3.

Mobile Station:

The MS is in CC state U10.

Specific PICS Statements

PIXIT Statements

– Description of the user’s commands and of display of the answers from the network for call barring.

Foreseen final state of the MS

The MS is in CC state U10.

Test procedure

By means of appropriate MMI functions (using either 3GPP TS 02.30 or manufacturer defined MMI), the user requests registration of a new password for all call restriction services. By means of appropriate MMI functions the user enters the old and new passwords.

Upon receipt of the REGISTER message, the system simulator answers with the FACILITY message with the Facility information element containing an invoke of the GetPassword operation requiring the old password.

Upon receipt of the FACILITY message, the system simulator answers with the RELEASE COMPLETE message (PD and TI of the SS transaction) with the Facility information element containing a Return_error(error: NegativePasswordCheck) of the RegisterPassword operation.

The system simulator sends STATUS ENQUIRY, the MS responds with STATUS message indicating CC state U10.

Maximum duration of test

5 minutes.

Expected sequence

Step

Direction

Message

Comments

1

MS

The MS is made to initiate a registration of a new password for all call restriction services. The old and new passwords are entered.

2

MS -> SS

CM SERVICE REQUEST

cause: "supplementary service activation"

3

SS -> MS

CM SERVICE ACCEPT

4

MS -> SS

REGISTER

5

SS -> MS

FACILITY

Invoke = GetPassword (password)

6

SS -> MS

RELEASE COMPLETE

Register Password operation ReturnError

7

MS

provide correct MMI user indication

8

SS -> MS

STATUS ENQUIRY

9

MS -> SS

STATUS

CC staTE U10

Specific message content

step 4 –

– protocol discriminator: non call related SS message.

– message type: REGISTER.

– facility:

invoke = RegisterPassword:

Supplementary service code = B.

step 6 –

– protocol discriminator: non call related SS message.

– transaction identifier: same TI as previous REGISTER message.

– message type: RELEASE COMPLETE.

– facility:

error code: NegativePasswordCheck.

For the reject the invoke ID must be the same as in the invoke of the Registerpassword operation.

step 5 –

– protocol discriminator: non call related SS message.

– transaction identifier: in FACILITY same as previous REGISTER message.

– message type: FACILITY.

– facility:

invoke = GetPassword:

Guidance info: Password (step 1).

31.8.1.2.3 Rejection after new password mismatch

31.8.1.2.3.1 Conformance requirements

1) A transaction of any kind being already established, for registration of a password for all call restriction services, the MS shall establish a parallel MM transaction, sending a CM SERVICE REQUEST with CM service type indicating "supplementary service activation".

2) Then the MS shall send a REGISTER message related to the present SS transaction containing a facility IE that includes an invoke of the RegisterPassword operation with parameter values according to the user’s request (MMI action).

3) Upon receipt of the RELEASE COMPLETE message related to the present SS transaction, the SS transaction shall be released but the first transaction shall remain unaffected.

4) Upon receipt of the RELEASE COMPLETE message, the MS shall provide the appropriate user indication (which is to be described by the Manufacturer).

References

1) 3GPP TS 04.08 / 3GPP TS 44.018 subclauses 3.3.1.1.2 and 9.1.9.

2) 3GPP TS 04.08 / 3GPP TS 24.008 subclauses 4.5.1.1, 9.2.9 and 10.5.3.3.

3) 3GPP TS 04.88,
3GPP TS 04.80 subclauses 2.3 and 3.6.

4) 3GPP TS 02.30 subclause 4.5.

5) 3GPP TS 04.10 subclause 4.2.

31.8.1.2.3.2 Test purpose

1) To check that, when a call transaction is already established, the MS correctly requests the establishment of a parallel MM transaction for supplementary service transaction of registration of a password for all call restriction services, sending a CM SERVICE REQUEST.

2) To check that the MS sends a REGISTER message containing the invoke of the RegisterPassword operation with the expected parameter values for registration of a password for all call restriction services.

3) To check that upon receipt of the RELEASE COMPLETE message related to the present SS transaction, the first transaction remains unaffected.

4) To check that upon receipt of the RELEASE COMPLETE message, the MS provides the appropriate user indication (as described by the Manufacturer).

Those checks are performed with a call transaction already established for:

– all call restriction services, the RELEASE COMPLETE message being sent at the end of the procedure with a facility IE containing a return_error(error) where error is "PasswordRegistrationFailure" with diagnostic "new password mismatch".

31.8.1.2.3.3 Method of test

Initial conditions

System Simulator:

1 cell, default parameters.

Mobile Station:

The MS is in CC state U10.

Specific PICS Statements

PIXIT Statements

– Description of the user’s commands and of display of the answers from the network for call barring.

Foreseen final state of the MS

The MS is in CC state U10.

Test procedure

By means of appropriate MMI functions (using either 3GPP TS 02.30 or manufacturer defined MMI), the user requests registration of a new password for all call restriction services by entering the old password, the new password and a repeat of the new password.

Upon receipt of the REGISTER message, the system simulator answers with the FACILITY message with the Facility information element containing an invoke of the GetPassword operation requiring the old password.

Upon receipt of the FACILITY message, the system simulator answers with the FACILITY message with the Facility information element containing an invoke of the GetPassword operation requiring the new password.

Upon receipt of the FACILITY message, the system simulator answers with the FACILITY message with the Facility information element containing an invoke of the GetPassword operation requiring again the new password.

Upon receipt of the FACILITY message, the system simulator answers with the RELEASE COMPLETE message (PD and TI of the SS transaction) with the Facility information element containing a Return_error(error: PasswordRegistrationFailure, parameter: NewPasswordMismatch) of the RegisterPassword operation.

The system simulator sends STATUS ENQUIRY, the MS responds with STATUS message indicating CC state U10.

Maximum duration of test

3 minutes.

Expected sequence

Step

Direction

Message

Comments

1

MS

The MS is made to initiate a registration of a new password for all call restriction services. The old password, new password and a repeat of the new password are entered.

2

MS -> SS

CM SERVICE REQUEST

cause: "supplementary service activation"

3

SS -> MS

CM SERVICE ACCEPT

4

MS -> SS

REGISTER

5

SS -> MS

FACILITY

Invoke = GetPassword (password)

6

MS -> SS

FACILITY

GetPassword operation ReturnResult

7

SS -> MS

FACILITY

Invoke = GetPassword (new password)

8

MS -> SS

FACILITY

GetPassword operation ReturnResult

9

SS -> MS

FACILITY

Invoke = GetPassword (new password again)

10

MS -> SS

FACILITY

GetPassword operation ReturnResult

11

SS -> MS

RELEASE COMPLETE

Register Password operation ReturnError

12

MS

provide correct MMI user indication

13

SS -> MS

STATUS ENQUIRY

14

MS -> SS

STATUS

CC staTE U10

Specific message content

step 4 –

– protocol discriminator: non call related SS message.

– message type: REGISTER.

– facility:

invoke = RegisterPassword:

Supplementary service code = B.

step 11 –

– protocol discriminator: non call related SS message.

– transaction identifier: same TI as previous REGISTER message.

– message type: RELEASE COMPLETE.

– facility:

error code: PasswordRegistrationFailure.

parameter: NewPasswordMismatch.

For the reject the invoke ID must be the same as in the invoke of the Registerpassword operation.

steps 5, 7, and 8 –

– protocol discriminator: non call related SS message.

– transaction identifier: in FACILITY same as previous REGISTER message.

– message type: FACILITY.

– facility:

invoke = GetPassword:

Supplementary service code = B.

Guidance info: Password (step 5), new password (step 7), new password again (step 8).

31.8.2 Erasure

Not applicable.

31.8.3 Activation

31.8.3.1 Activation accepted

31.8.3.1.1 Conformance requirements

1) For activation of any specific call restriction service with any parameters, the MS shall transmit successively

1.1) a CHANNEL REQUEST with establishment cause set to "other services requested by the mobile user";

1.2) a CM SERVICE REQUEST with CM service type indicating "supplementary service activation";

1.3) and then the REGISTER message containing a facility IE that includes an invoke of the ActivateSS operation with parameter values according to the user’s request (MMI action).

2) Upon receipt of FACILITY message requiring the password, the MS shall be able to send a password by sending a FACILITY message.

3) Upon receipt of the RELEASE COMPLETE message, the MS shall provide the appropriate user indication (which is to be described by the manufacturer).

References

1) 3GPP TS 04.08 / 3GPP TS 44.018 subclauses 3.3.1.1.2 and 9.2.9.

2) 3GPP TS 04.88,
3GPP TS 04.80 subclauses 2.3 and 3.6.

3) 3GPP TS 02.30 subclause 4.5.

31.8.3.1.2 Test purpose

1) To check that the MS correctly requests a supplementary service transaction for activation of a specific call restriction service in CHANNEL REQUEST message.

2) To check that the MS correctly requests a supplementary service transaction for activation of call restriction service in the subsequent CM SERVICE REQUEST.

3) To check that the MS sends a REGISTER message containing the invoke of the ActivateSS operation with the expected parameter values for activation of a specific call restriction service.

4) To check that upon receipt of FACILITY message requiring the password, the MS is able to send a password by sending a FACILITY.

5) To check that upon receipt of the RELEASE COMPLETE message, the MS provides the appropriate user indication (which is to be described by the manufacturer).

These checks are done for:

a) BAOC, for basic service group "all synchronous services".

b) BICRoam, for all basic service groups.

31.8.3.1.3 Method of test

Initial conditions

System Simulator:

1 cell, default parameters.

Mobile Station:

The MS is "idle updated".

Specific PICS Statements

PIXIT Statements

– Description of the user’s commands and of display of the answers from the network for call barring.

Foreseen final state of the MS

The MS is "idle updated".

Test procedure

By means of appropriate MMI functions (using either 3GPP TS 02.30 or manufacturer defined MMI), the user requests activation of BAOC, for basic service group "all synchronous services".

Upon receipt of the operation (in a REGISTER message), the system simulator answers with the FACILITY message with the Facility information element containing an invoke of the GetPassword operation requiring the current password.

If the manufacturer defined MMI has been used to request the activation of BAOC, then the MS may, by means of appropriate manufacturer defined MMI functions, prompt the user to give a password, depending on the implementation of the manufacturer defined MMI functions.

Upon receipt of the FACILITY message, the system simulator answers with a RELEASE COMPLETE message with the Facility information element containing the Return_result of the ActivateSS operation.

The SS transaction and the dedicated channel are released.

Then again, by means of appropriate MMI functions, the user requests activation of BICRoam, for all basic service groups.

Upon receipt of the operation (in a REGISTER message), the system simulator answers with the FACILITY message with the Facility information element containing an invoke of the GetPassword operation requiring the current password.

If the manufacturer defined MMI has been used to request the activation of BICRoam, then the MS may, by means of appropriate manufacturer defined MMI functions, prompt the user to give a password, depending on the implementation of the manufacturer defined MMI functions.

Upon receipt of the FACILITY message, the system simulator answers with a RELEASE COMPLETE message with the Facility information element containing the Return_result of the ActivateSS operation.

The dedicated channel is released.

Maximum duration of test

3 minutes.

Expected sequence

Step

Direction

Message

Comments

1

MS

The MS is made to initiate a activation of BAOC(all synchronous services)

2

MS -> SS

CHANNEL REQUEST

with establishment cause "Other procedures which can be completed with an SDCCH"

3

SS -> MS

IMMEDIATE ASSIGNMENT

4

MS -> SS

CM SERVICE REQUEST

cause: "supplementary service activation"

5

SS -> MS

CM SERVICE ACCEPT

6

MS -> SS

REGISTER

7

SS -> MS

FACILITY

GetPassword

8

MS -> SS

FACILITY

Getpassword operation Return Result

9

SS -> MS

RELEASE COMPLETE

ActivateSS operation Return_result

10

SS -> MS

CHANNEL RELEASE

11

MS

Provide correct MMI user indication after step 9

12

MS

The MS is made to initiate an activation of BICRoam(all basic service groups),

13

MS -> SS

CHANNEL REQUEST

with establishment cause "Other procedures which can be completed with an SDCCH"

14

SS -> MS

IMMEDIATE ASSIGNMENT

15

MS -> SS

CM SERVICE REQUEST

cause: "supplementary service activation"

16

SS -> MS

CM SERVICE ACCEPT

17

MS -> SS

REGISTER

18

SS -> MS

FACILITY

GetPassword

19

MS -> SS

FACILITY

Getpassword operation Return Result

20

SS -> MS

RELEASE COMPLETE

ActivateSS operation Return result

21

SS -> MS

CHANNEL RELEASE

22

MS

Provide correct MMI user indication after step 20

Specific message contents

step 6 – BAOC

– protocol discriminator: non call related SS message.

– message type: REGISTER.

– facility:

invoke = Activation:

Supplementary service code = BAOC.

Basic service code: Bearer Service (all synchronous services), no teleservice present.

step 17 – BICRoam

– protocol discriminator: non call related SS message.

– message type: REGISTER.

– facility:

invoke = Activation:

Supplementary service code = BICRoam.

Basic service code: no bearer service present, no teleservice present.

steps 7, 18 –

– protocol discriminator: non call related SS message.

– transaction identifier: in FACILITY same as previous REGISTER message.

– message type: FACILITY.

– facility:

invoke = GetPassword:

Guidance info: Password.

31.8.3.2 Activation rejected

31.8.3.2.1 Rejection after invoke of ActivateSS operation

31.8.3.2.1.1 Conformance requirements

1) A transaction of any kind being already established, for activation of one specific barring services, the MS shall establish a parallel MM transaction, sending a CM SERVICE REQUEST with CM service type indicating "supplementary service activation".

2) Then the MS shall send a REGISTER message related to the present SS transaction containing a facility IE that includes an invoke of the ActivateSS operation with parameter values according to the user’s request (MMI action).

3) Upon receipt of the RELEASE COMPLETE message related to the present SS transaction, the SS transaction shall be released but the first transaction shall remain unaffected.

4) Upon receipt of the RELEASE COMPLETE message, the MS shall provide the appropriate user indication (which is to be described by the Manufacturer).

References

1) 3GPP TS 04.08 / 3GPP TS 44.018 subclauses 3.3.1.1.2 and 9.1.9.

2) 3GPP TS 04.08 / 3GPP TS 24.008 subclauses 4.5.1.1, 9.2.9 and 10.5.3.3.

3) 3GPP TS 04.88,
3GPP TS 04.80 subclauses 2.3 and 3.6.

4) 3GPP TS 02.30 subclause 4.5.

31.8.3.2.1.2 Test purpose

1) To check that, when a call transaction is already established, the MS correctly requests the establishment of a parallel MM transaction for supplementary service transaction of specific call barring service, sending a CM SERVICE REQUEST.

2) To check that the MS sends a REGISTER message containing the invoke of the ActivateSS operation with the expected parameter values for specific call barring service.

3) To check that upon receipt of the RELEASE COMPLETE message related to the present SS transaction, the first transaction remains unaffected.

4) To check that upon receipt of the RELEASE COMPLETE message, the MS provides the appropriate user indication (as described by the Manufacturer).

Those checks are performed with a call transaction already established for:

– BOIC, the RELEASE COMPLETE message being sent at the beginning of the procedure with a facility IE containing a return_error(error) where error is "SS subscription violation".

31.8.3.2.1.3 Method of test

Initial conditions

System Simulator:

1 cell, default parameters.

Mobile Station:

The MS is in CC state U10.

Specific PICS Statements

PIXIT Statements

– Description of the user’s commands and of display of the answers from the network for call barring.

Foreseen final state of the MS

The MS is in CC state U10.

Test procedure

By means of appropriate MMI functions (using either 3GPP TS 02.30 or manufacturer defined MMI), the user requests activation of BOIC.

Upon receipt of the operation (in a REGISTER message), the system simulator answers with the RELEASE COMPLETE (PD and TI of the SS transaction) message with the Facility information element containing a Return_error(error: SS subscription violation) of the ActivateSS operation.

The system simulator then sends STATUS ENQUIRY, and the MS responds with STATUS message indicating CC state U10.

Maximum duration of test

2 minutes.

Expected sequence

Step

Direction

Message

Comments

1

MS

The MS is made to initiate an activation of BOIC

2

MS -> SS

CM SERVICE REQUEST

cause: "supplementary service activation"

3

SS -> MS

CM SERVICE ACCEPT

4

MS -> SS

REGISTER

5

SS -> MS

RELEASE COMPLETE

RegisterPassword operation Return_error

6

MS

provide correct MMI user indication

7

SS -> MS

STATUS ENQUIRY

8

MS -> SS

STATUS

CC state U10

Specific message content

step 4 –

– protocol discriminator: non call related SS message.

– message type: REGISTER.

– facility:

invoke = ActivateSS:

Supplementary service code = BOIC.

step 5 –

– protocol discriminator: non call related SS message.

– transaction identifier: same TI as previous REGISTER message.

– message type: RELEASE COMPLETE.

– facility:

return error code: SS subscription violation.

For the return error the invoke ID must be the same as in the invoke of the ActivateSS operation.

31.8.3.2.2 Rejection after use of password procedure

31.8.3.2.2.1 Conformance requirements

1) A transaction of any kind being already established, for activation of any specific call restriction services, the MS shall establish a parallel MM transaction, sending a CM SERVICE REQUEST with CM service type indicating "supplementary service activation".

2) Then the MS shall send a REGISTER message related to the present SS transaction containing a facility IE that includes an invoke of the ActivateSS operation with parameter values according to the user’s request (MMI action).

3) Upon receipt of the RELEASE COMPLETE message related to the present SS transaction, the SS transaction shall be released but the first transaction shall remain unaffected.

4) Upon receipt of the RELEASE COMPLETE message, the MS shall provide the appropriate user indication (which is to be described by the Manufacturer).

References

1) 3GPP TS 04.08 / 3GPP TS 44.018 subclauses 3.3.1.1.2 and 9.1.9.

2) 3GPP TS 04.08 / 3GPP TS 24.008 subclauses 4.5.1.1, 9.2.9 and 10.5.3.3.

3) 3GPP TS 04.88,
3GPP TS 04.80 subclauses 2.3 and 3.6.

4) 3GPP TS 02.30 subclause 4.5.

31.8.3.2.2.2 Test purpose

1) To check that, when a call transaction is already established, the MS correctly requests the establishment of a parallel MM transaction for supplementary service transaction of activation of one specific call restriction service, sending a CM SERVICE REQUEST.

2) To check that the MS sends a REGISTER message containing the invoke of the ActivateSS operation with the expected parameter values for activation of one specific call restriction service.

3) To check that upon receipt of the RELEASE COMPLETE message related to the present SS transaction, the first transaction remains unaffected.

4) To check that upon receipt of the RELEASE COMPLETE message, the MS provides the appropriate user indication (as described by the Manufacturer).

Those checks are performed with a call transaction already established for:

– BAIC, the RELEASE COMPLETE message being sent at the end of the procedure with a facility IE containing a return_error(error) where error is "NegativePasswordCheck".

31.8.3.2.2.3 Method of test

Initial conditions

System Simulator:

1 cell, default parameters.

Mobile Station:

The MS is in CC state U10.

Specific PICS Statements

PIXIT Statements

– Description of the user’s commands and of display of the answers from the network for call barring.

Foreseen final state of the MS

The MS is in CC state U10.

Test procedure

By means of appropriate MMI functions (using either 3GPP TS 02.30 or manufacturer defined MMI), the user requests activation of BAIC.

Upon receipt of the REGISTER message, the system simulator answers with the FACILITY message with the Facility information element containing an invoke of the GetPassword operation requiring the current password.

If the manufacturer defined MMI has been used to request the activation of BAIC, then the MS may, by means of appropriate manufacturer defined MMI functions, prompt the user to give a password, depending on the implementation of the manufacturer defined MMI functions.

Upon receipt of the FACILITY message, the system simulator sends RELEASE COMPLETE message (PD and TI of the SS transaction) with the Facility information element containing a Return_error(error: NegativePasswordCheck) of the GetPassword operation.

The system simulator sends STATUS ENQUIRY, the MS responds with STATUS message indicating CC state U10.

Maximum duration of test

3 minutes.

Expected sequence

Step

Direction

Message

Comments

1

MS

The MS is made to initiate a registration of BAIC

2

MS -> SS

CM SERVICE REQUEST

cause: "supplementary service activation"

3

SS -> MS

CM SERVICE ACCEPT

4

MS -> SS

REGISTER

5

SS -> MS

FACILITY

Invoke = GetPassword (password)

6

MS -> SS

FACILITY

GetPassword operation Return Result

7

SS -> MS

RELEASE COMPLETE

Register Password operation ReturnError

8

MS

provide correct MMI user indication

9

SS -> MS

STATUS ENQUIRY

10

MS -> SS

STATUS

CC state U10

Specific message content

step 4 – BAIC

– protocol discriminator: non call related SS message.

– message type: REGISTER.

– facility:

invoke = Activation:

Supplementary service code = BAIC.

step 5 – All Barring services

– protocol discriminator: non call related SS message.

– transaction identifier: in FACILITY same as previous REGISTER message.

– message type: FACILITY.

– facility:

invoke = GetPassword:

Guidance info: Password (step 5).

step 8 –

– protocol discriminator: non call related SS message.

– transaction identifier: same TI as previous REGISTER message.

– message type: RELEASE COMPLETE.

– facility:

reject code: NegativePasswordCheck.

For the reject the invoke ID must be the same as in the invoke of the GetPassword operation.

31.8.4 Deactivation

31.8.4.1 Deactivation accepted

31.8.4.1.1 Conformance requirements

1) For deactivation of any group of call restriction services with any parameters, the MS shall transmit successively

1.1) a CHANNEL REQUEST with establishment cause set to "other services requested by the mobile user";

1.2) a CM SERVICE REQUEST with CM service type indicating "supplementary service activation";

1.3) and then the REGISTER message containing a facility IE that includes an invoke of the DeactivateSS operation with parameter values according to the user’s request (MMI action).

2) Upon receipt of FACILITY message requiring the password, the MS shall be able to send a password by sending a FACILITY message.

3) Upon receipt of the RELEASE COMPLETE message, the MS shall provide the appropriate user indication (which is to be described by the manufacturer).

References

1) 3GPP TS 04.08 / 3GPP TS 44.018 subclauses 3.3.1.1.2 and 9.2.9.

2) 3GPP TS 04.88,
3GPP TS 04.80 subclauses 2.3 and 3.6.

3) 3GPP TS 02.30 subclause 4.5.

31.8.4.1.2 Test purpose

1) To check that the MS correctly requests a supplementary service transaction for deactivation of a group of call barring services in CHANNEL REQUEST message.

2) To check that the MS correctly requests a supplementary service transaction for deactivation of a group of call barring services in the subsequent CM SERVICE REQUEST.

3) To check that the MS sends a REGISTER message containing the invoke of the DeactivateSS operation with the expected parameter values for deactivation of a group of call restriction services.

4) To check that upon receipt of FACILITY message requiring the password, the MS is able to send a password by sending a FACILITY message.

5) To check that upon receipt of the RELEASE COMPLETE message, the MS provides the appropriate user indication (which is to be described by the manufacturer).

These checks are done for:

a) all restrictions, for basic service group "speech".

b) barring of outgoing calls, for all facsimile.

31.8.4.1.3 Method of test

Initial conditions

System Simulator:

1 cell, default parameters.

Mobile Station:

The MS is "idle updated".

Specific PICS Statements

PIXIT Statements

– Description of the user’s commands and of display of the answers from the network for call barring.

Foreseen final state of the MS

The MS is "idle updated".

Test procedure

By means of appropriate MMI functions (using either 3GPP TS 02.30 or manufacturer defined MMI), the user requests deactivation of all restrictions, for speech.

Upon receipt of the operation (in a REGISTER message), the system simulator answers with the FACILITY message with the Facility information element containing an invoke of the GetPassword operation requiring the current password.

If the manufacturer defined MMI has been used to request the deactivation of all restrictions for speech, then the MS may, by means of appropriate manufacturer defined MMI functions, prompt the user to give a password, depending on the implementation of the manufacturer defined MMI functions.

Upon receipt of the FACILITY message, the system simulator answers with the FACILITY message with the Facility information element containing the Return_result of the DeactivateSS operation.

The SS transaction and the dedicated channel are released.

Then again, by means of appropriate MMI functions, the user requests deactivation of barring of outgoing calls, for all facsimile.

Upon receipt of the operation (in a REGISTER message), the system simulator answers with the FACILITY message with the Facility information element containing an invoke of the GetPassword operation requiring the current password.

If the manufacturer defined MMI has been used to request the deactivation of barring of outgoing calls for all facsimile, then the MS may, by means of appropriate manufacturer defined MMI functions, prompt the user to give a password, depending on the implementation of the manufacturer defined MMI functions.

Upon receipt of the FACILITY message, the system simulator answers with a RELEASE COMPLETE message with the Facility information element containing the Return_result of the DeactivateSS operation.

The dedicated channel is released.

Maximum duration of test

5 minutes.

Expected sequence

Step

Direction

Message

Comments

1

MS

The MS is made to initiate a deactivation of all call restrictions(speech)

2

MS -> SS

CHANNEL REQUEST

with establishment cause "Other procedures which can be completed with an SDCCH"

3

SS -> MS

IMMEDIATE ASSIGNMENT

4

MS -> SS

CM SERVICE REQUEST

cause: "supplementary service activation"

5

SS -> MS

CM SERVICE ACCEPT

6

MS -> SS

REGISTER

7

SS -> MS

FACILITY

GetPassword

8

MS -> SS

FACILITY

Getpassword operation Return Result

9

SS -> MS

RELEASE COMPLETE

DeactivateSS operation Return_result

10

SS -> MS

CHANNEL RELEASE

11

MS

The MS is made to initiate a deactivation of barring of outgoing calls(all facsimile),

12

MS -> SS

CHANNEL REQUEST

with establishment cause "Other procedures which can be completed with an SDCCH"

13

SS -> MS

IMMEDIATE ASSIGNMENT

14

MS -> SS

CM SERVICE REQUEST

cause: "supplementary service activation"

15

SS -> MS

CM SERVICE ACCEPT

16

MS -> SS

REGISTER

17

SS -> MS

FACILITY

GetPassword

18

MS -> SS

FACILITY

Getpassword operation Return Result

19

SS -> MS

RELEASE COMPLETE

DeactivateSS operation Return result

21

SS -> MS

CHANNEL RELEASE

21

MS

Provide correct MMI user indication after step 19

Specific message contents

step 6 – all call restrictions:

– protocol discriminator: non call related SS message.

– message type: REGISTER.

– facility:

invoke = Deactivation:

Supplementary service code = B.

Basic service code: no Bearer Service present, Tele Service AllSpeechTransmissionServices (TS10) or Telephony (TS 11).

step 16 – barring of outgoing calls,

– protocol discriminator: non call related SS message.

– message type: REGISTER.

– facility:

invoke = Deactivation:

Basic service code: no bearer service present, teleservice: all facsimile.

steps 7, 17 –

– protocol discriminator: non call related SS message.

– transaction identifier: in FACILITY same as previous REGISTER message.

– message type: FACILITY.

– facility:

invoke = GetPassword:

Guidance info: Password.

31.8.4.2 Deactivation rejected

31.8.4.2.1 Rejection after invoke of DeactivateSS operation

31.8.4.2.1.1 Conformance requirements

1) A transaction of any kind being already established, for deactivation of a group of call restriction services, the MS shall establish a parallel MM transaction, sending a CM SERVICE REQUEST with CM service type indicating "supplementary service activation".

2) Then the MS shall send a REGISTER message related to the present SS transaction containing a facility IE that includes an invoke of the DeactivateSS operation with parameter values according to the user’s request (MMI action).

3) Upon receipt of the RELEASE COMPLETE message related to the present SS transaction, the SS transaction shall be released but the first transaction shall remain unaffected.

4) Upon receipt of the RELEASE COMPLETE message, the MS shall provide the appropriate user indication (which is to be described by the Manufacturer).

References

1) 3GPP TS 04.08 / 3GPP TS 44.018 subclauses 3.3.1.1.2 and 9.1.9.

2) 3GPP TS 04.08 / 3GPP TS 24.008 subclauses 4.5.1.1, 9.2.9 and 10.5.3.3.

3) 3GPP TS 04.88,
3GPP TS 04.80 subclauses 2.3 and 3.6.

4) 3GPP TS 02.30 subclause 4.5.

31.8.4.2.1.2 Test purpose

1) To check that, when a call transaction is already established, the MS correctly requests the establishment of a parallel MM transaction for supplementary service transaction of a group of call barring services, sending a CM SERVICE REQUEST.

2) To check that the MS sends a REGISTER message containing the invoke of the DeactivateSS operation with the expected parameter values for a group of call barring services.

3) To check that upon receipt of the RELEASE COMPLETE message related to the present SS transaction, the first transaction remains unaffected.

4) To check that upon receipt of the RELEASE COMPLETE message, the MS provides the appropriate user indication (as described by the Manufacturer).

These checks are performed with a call transaction already established for:

BOIC, the RELEASE COMPLETE message being sent at the beginning of the procedure with a facility IE containing a return_error(error) where error is "SS subscription violation".

31.8.4.2.1.3 Method of test

Initial conditions

System Simulator:

1 cell, default parameters.

Mobile Station:

The MS is in CC state U10.

Specific PICS Statements

PIXIT Statements

– Description of the user’s commands and of display of the answers from the network for call barring.

Foreseen final state of the MS

The MS is in CC state U10.

Test procedure

By means of appropriate MMI functions (using either 3GPP TS 02.30 or manufacturer defined MMI), the user requests deactivation of incoming calls.

Upon receipt of the operation (in a REGISTER message), the system simulator answers with the RELEASE COMPLETE (PD and TI of the SS transaction) message with the Facility information element containing a Return_error(error: SS subscription violation) of the DeactivateSS operation.

The system simulator then sends STATUS ENQUIRY, and the MS responds with STATUS message indicating CC state U10.

Maximum duration of test

30 s.

Expected sequence

Step

Direction

Message

Comments

1

MS

The MS is made to initiate a deactivation for bi

2

MS -> SS

CM SERVICE REQUEST

cause: "supplementary service activation"

3

SS -> MS

CM SERVICE ACCEPT

4

MS -> SS

REGISTER

5

SS -> MS

RELEASE COMPLETE

DeactivateSS operation Return_error

6

MS

provide correct MMI user indication

7

SS -> MS

STATUS ENQUIRY

8

MS -> SS

STATUS

CC state U10

Specific message content

step 4 –

– protocol discriminator: non call related SS message.

– message type: REGISTER.

– facility:

invoke = DeactivateSS:

Supplementary service code = bi.

step 5 –

– protocol discriminator: non call related SS message.

– transaction identifier: same TI as previous REGISTER message.

– message type: RELEASE COMPLETE.

– facility:

return error code: SS subscription violation.

For the return error the invoke ID must be the same as in the invoke of the DeactivateSS operation.

31.8.4.2.2 Rejection after use of password procedure

31.8.4.2.2.1 Conformance requirements

1) A transaction of any kind being already established, for deactivation of a group of call restriction services, the MS shall establish a parallel MM transaction, sending a CM SERVICE REQUEST with CM service type indicating "supplementary service activation".

2) Then the MS shall send a REGISTER message related to the present SS transaction containing a facility IE that includes an invoke of the DeactivateSS operation with parameter values according to the user’s request (MMI action).

3) Upon receipt of the RELEASE COMPLETE message related to the present SS transaction, the SS transaction shall be released but the first transaction shall remain unaffected.

4) Upon receipt of the RELEASE COMPLETE message, the MS shall provide the appropriate user indication (which is to be described by the Manufacturer).

References

1) 3GPP TS 04.08 / 3GPP TS 44.018 subclauses 3.3.1.1.2 and 9.1.9.

2) 3GPP TS 04.08 / 3GPP TS 24.008 subclauses 4.5.1.1, 9.2.9 and 10.5.3.3.

3) 3GPP TS 04.88,
3GPP TS 04.80 subclauses 2.3 and 3.6.

4) 3GPP TS 02.30 subclause 4.5.

31.8.4.2.2.2 Test purpose

1) To check that, when a call transaction is already established, the MS correctly requests the establishment of a parallel MM transaction for supplementary service transaction of deactivation of a group of call restriction services, sending a CM SERVICE REQUEST.

2) To check that the MS sends a REGISTER message containing the invoke of the DeactivateSS operation with the expected parameter values for deactivation of a group of call restriction service.

3) To check that upon receipt of the RELEASE COMPLETE message related to the present SS transaction, the first transaction remains unaffected.

4) To check that upon receipt of the RELEASE COMPLETE message, the MS provides the appropriate user indication (as described by the Manufacturer).

Those checks are performed with a call transaction already established for:

BOICExHC, the RELEASE COMPLETE message being sent at the end of the procedure with a facility IE containing a return_error(error) where error is "NegativePasswordCheck".

31.8.4.2.2.3 Method of test

Initial conditions

System Simulator:

1 cell, default parameters.

Mobile Station:

The MS is in CC state U10.

Specific PICS Statements

PIXIT Statements

– Description of the user’s commands and of display of the answers from the network for call barring.

Foreseen final state of the MS

The MS is in CC state U10.

Test procedure

By means of appropriate MMI functions (using either 3GPP TS 02.30 or manufacturer defined MMI), the user requests deactivation of a group of call restriction services.

Upon receipt of the REGISTER message, the system simulator answers with the FACILITY message with the Facility information element containing an invoke of the DeactivateSS operation requiring the current password.

If the manufacturer defined MMI has been used to request the deactivation of a group of call restriction services, then the MS may, by means of appropriate manufacturer defined MMI functions, prompt the user to give a password, depending on the implementation of the manufacturer defined MMI functions.

Upon receipt of the FACILITY message, the system simulator sends RELEASE COMPLETE message (PD and TI of the SS transaction) with the Facility information element containing a Return_error(error: NegativePasswordCheck) of the GetPassword operation.

The system simulator sends STATUS ENQUIRY, the MS responds with STATUS message indicating CC state U10.

Maximum duration of test

3 minutes.

Expected sequence

Step

Direction

Message

Comments

1

MS

The MS is made to initiate a deactivation of BoicExHC

2

MS -> SS

CM SERVICE REQUEST

cause: "supplementary service activation"

3

SS -> MS

CM SERVICE ACCEPT

4

MS -> SS

REGISTER

5

SS -> MS

FACILITY

Invoke = GetPassword (password)

6

MS -> SS

FACILITY

GetPassword operation Return Result

7

SS -> MS

RELEASE COMPLETE

Register Password operation ReturnError

8

MS

provide correct MMI user indication

9

SS -> MS

STATUS ENQUIRY

10

MS -> SS

STATUS

CC state U10

Specific message content

step 4 –

– protocol discriminator: non call related SS message.

– message type: REGISTER.

– facility:

invoke = DeactivateSS:

Supplementary service code = BOICExHC.

step 7 –

– protocol discriminator: non call related SS message.

– transaction identifier: same TI as previous REGISTER message.

– message type: RELEASE COMPLETE.

– facility:

reject code: NegativePasswordCheck.

For the reject the invoke ID must be the same as in the invoke of the DeactivateSS operation.

step 5 –

– protocol discriminator: non call related SS message.

– transaction identifier: in FACILITY same as previous REGISTER message.

– message type:FACILITY.

– facility:

invoke = GetPassword:

Guidance info: Password (step 5).

31.8.5 Invocation

Invocation is not applicable.

31.8.6 Interrogation

31.8.6.1 Interrogation accepted

31.8.6.1.1 Conformance requirements

1) For interrogation of any specific call restriction service with any parameters, the MS shall transmit successively:

1.1) a CHANNEL REQUEST with establishment cause set to "other services requested by the mobile user";

1.2) a CM SERVICE REQUEST with CM service type indicating "supplementary service activation";

1.3) and then the REGISTER message containing a facility IE that includes an invoke of the InterrogateSS operation with parameter values according to the user’s request (MMI action).

2) Upon receipt of the RELEASE COMPLETE message, the MS shall provide the appropriate user indication (which is to be described by the manufacturer).

References

1) 3GPP TS 04.08 / 3GPP TS 44.018 subclauses 3.3.1.1.2 and 9.1.9.

2) 3GPP TS 04.08 / 3GPP TS 24.008 subclauses 4.5.1.1, 9.2.9 and 10.5.3.3.

3) 3GPP TS 04.88,
3GPP TS 04.80 subclauses 2.3 and 3.6.

4) 3GPP TS 02.30 subclause 4.5.

31.8.6.1.2 Test purpose

1) To check that the MS correctly requests a supplementary service transaction for interrogation of a specific call barring service in CHANNEL REQUEST message.

2) To check that the MS correctly requests a supplementary service transaction for interrogation of a call barring service in the subsequent CM SERVICE REQUEST.

3) To check that the MS sends a REGISTER message containing the invoke of the InterrogateSS operation with the expected parameter values for interrogation of one call restriction service.

4) To check that upon receipt of the RELEASE COMPLETE message, the MS provides the appropriate user indication (which is to be described by the manufacturer).

These checks are done for:

a) BAIC, the result of the operation being a Basic Service code if supported by the MS.

b) BOICExHC, the result of the operation being a SS-status if supported by the MS.

31.8.6.1.3 Method of test

Initial conditions

System Simulator:

1 cell, default parameters.

Mobile Station:

The MS is "idle updated".

Specific PICS Statements

– Support of Barring of All Incoming Calls (TSPC_Serv_SS_BAIC)

– Support of Barring of Outgoing International Calls except those directed to the Home PLMN Country (TSPC_Serv_SS_BOICexHC)

PIXIT Statements

– Description of the user’s commands and of display of the answers from the network for call barring.

Foreseen final state of the MS

The MS is "idle updated".

Test procedure

By means of appropriate MMI functions (using either 3GPP TS 02.30 or manufacturer defined MMI), the user requests interrogation of BAIC if supported by the MS.

Upon receipt of the operation (in a REGISTER message), the system simulator answers with a RELEASE COMPLETE message with the Facility information element containing the Return_result (basic service) of the InterrogateSS operation.

The SS transaction and the dedicated channel are released.

By means of appropriate MMI functions, the user requests interrogation of BOICExHC if supported by the MS.

Upon receipt of the operation (in a REGISTER message), the system simulator answers with a RELEASE COMPLETE message with the Facility information element containing the Return_result(SS-status) of the InterrogateSS operation.

The dedicated channel is released.

Maximum duration of test

3 minutes.

Expected sequence

Step

Direction

Message

Comments

Steps 1-9 are applicable if MS supports BAIC (TSPC_Serv_SS_BAIC) and steps 10-18 are applicable if MS supports BOICExHC (TSPC_Serv_SS_BOICexHC).

1

MS

The MS is made to initiate a interrogation of BAIC

2

MS -> SS

CHANNEL REQUEST

with establishment cause "Other procedures which can be completed with an SDCCH"

3

SS -> MS

IMMEDIATE ASSIGNMENT

4

MS -> SS

CM SERVICE REQUEST

cause: "supplementary service activation"

5

SS -> MS

CM SERVICE ACCEPT

6

MS -> SS

REGISTER

7

SS -> MS

RELEASE COMPLETE

InterrogateSS operation Return_result

9

SS -> MS

CHANNEL RELEASE

9

MS

Provide correct MMI user indication after step 7

10

MS

The MS is made to initiate a interrogation of call forwarding service for BOICExHC,

11

MS -> SS

CHANNEL REQUEST

with establishment cause "Other procedures which can be completed with an SDCCH"

12

SS -> MS

IMMEDIATE ASSIGNMENT

13

MS -> SS

CM SERVICE REQUEST

cause: "supplementary service activation"

14

SS -> MS

CM SERVICE ACCEPT

15

MS -> SS

REGISTER

16

SS -> MS

RELEASE COMPLETE

InterrogateSS operation Return result

17

SS -> MS

CHANNEL RELEASE

18

MS

Provide correct MMI user indication after step 16

Specific message contents

step 6 – BOIC

– protocol discriminator: non call related SS message.

– message type: REGISTER.

– facility:

invoke = Interrogation:

Supplementary service code = BAIC.

step 14 – BOICExHC

– protocol discriminator: non call related SS message.

– message type: REGISTER.

– facility:

invoke = Interrogation:

Supplementary service code = BOICExHC.

31.8.6.2 Interrogation rejected

31.8.6.2.1 Conformance requirements

1) A transaction of any kind being already established, for interrogation of any specific call barring with any parameters, the MS shall establish a parallel MM transaction, sending a CM SERVICE REQUEST with CM service type indicating "supplementary service activation".

2) Then the MS shall send a REGISTER message related to the present SS transaction containing a facility IE that includes an invoke of the InterrogateSS operation with parameter values according to the user’s request (MMI action).

3) Upon receipt of the RELEASE COMPLETE message related to the present SS transaction, the SS transaction shall be released but the first transaction shall remain unaffected.

4) Upon receipt of the RELEASE COMPLETE message, the MS shall provide the appropriate user indication (which is to be described by the Manufacturer).

References

1) 3GPP TS 04.08 / 3GPP TS 44.018 subclauses 3.3.1.1.2 and 9.1.9.

2) 3GPP TS 04.08 / 3GPP TS 24.008 subclauses 4.5.1.1, 9.2.9 and 10.5.3.3.

3) 3GPP TS 04.88,
3GPP TS 04.80 subclauses 2.3 and 3.6.

4) 3GPP TS 02.30 subclause 4.5.

31.8.6.2.2 Test purpose

1) To check that the MS correctly requests the establishment of a parallel MM transaction for supplementary service transaction of interrogation of a specific call barring service message, sending a CM SERVICE REQUEST.

2) To check that the MS sends a REGISTER message containing the invoke of the InterrogateSS operation with the expected parameter values for interrogation of call barring.

3) To check that upon receipt of the RELEASE COMPLETE message related to the present SS transaction, the first transaction remains unaffected.

4) To check that upon receipt of the RELEASE COMPLETE message, the MS provides the appropriate user indication (as described by the Manufacturer).

These checks are performed with a call transaction already established for:

a) BICRoam, the RELEASE COMPLETE message being sent with a facility IE containing a return_error(error) where error is "SS not available".

b) BOIC, the RELEASE COMPLETE message being sent with a facility IE containing a reject(invoke_problem) where invoke_problem is "resource limitation".

31.8.6.2.3 Method of test

Initial conditions

System Simulator:

1 cell, default parameters.

Mobile Station:

The MS is in CC state U10.

Specific PICS Statements

– Barring of Outgoing International Calls (TSPC_Serv_SS_BOIC)

Barring of Incoming Calls when Roaming Outside the Home PLMN Country (TSPC_Serv_SS_BICRoam)

PIXIT Statements

– Description of the user’s commands and of display of the answers from the network for call barring.

Foreseen final state of the MS

The MS is in CC state U10.

Test procedure

By means of appropriate MMI functions (using either 3GPP TS 02.30 or manufacturer defined MMI), the user requests interrogation of BICRoam if supported by the MS.

Upon receipt of the operation (in a REGISTER message),the system simulator answers with a RELEASE COMPLETE message with the Facility information element containing a Return_error(error: SS not available) of the InterrogateSS operation.

The system simulator sends STATUS ENQUIRY, the MS responds with STATUS message indicating CC state U10.

By means of appropriate MMI functions, the user requests interrogation of BOIC if supported by the MS.

Upon receipt of the REGISTER message, the system simulator answers with the RELEASE COMPLETE message (same PD and TI that in the REGISTER message) with the Facility information element containing a reject(invoke_problem: resource limitation) of the InterrogateSS operation.

The system simulator sends STATUS ENQUIRY, the MS responds with STATUS message indicating CC state U10.

Maximum duration of test

3 minutes.

Expected sequence

Step

Direction

Message

Comments

Steps 1-8 are applicable if MS supports BICRoam (TSPC_Serv_SS_BICRoam) and Steps 9-16 are applicable if MS supports BOIC(TSPC_Serv_SS_BOIC).

1

MS

The MS is made to initiate a interrogation of call barring service for BICRoam

2

MS -> SS

CM SERVICE REQUEST

cause: "supplementary service activation"

3

SS -> MS

CM SERVICE ACCEPT

4

MS -> SS

REGISTER

5

SS -> MS

RELEASE COMPLETE

InterrogateSS operation Return_error

6

MS

provide correct MMI user indication

7

SS -> MS

STATUS ENQUIRY

8

MS -> SS

STATUS

CC state U10

9

MS

The MS is made to initiate a interrogation of call barring service for BOIC

10

MS -> SS

CM SERVICE REQUEST

cause: "supplementary service activation"

11

SS -> MS

CM SERVICE ACCEPT

12

MS -> SS

REGISTER

13

SS -> MS

RELEASE COMPLETE

InterrogateSS operation Return_reject

14

MS

provide correct MMI user indication

15

SS -> MS

STATUS ENQUIRY

16

MS -> SS

STATUS

CC state U10

Specific message content

step 4 – BICRoam

– protocol discriminator: non call related SS message.

– message type: REGISTER.

– facility:

invoke = Interrogation:

Supplementary service code = BICRoam.

step 5 –

– protocol discriminator: non call related SS message.

– transaction identifier: same TI as previous REGISTER message.

– message type: RELEASE COMPLETE.

– facility:

return error code: SS not available.

For the return error the invoke ID must be the same as in the invoke of the InterrogateSS operation.

step 11 – BOIC

– protocol discriminator: non call related SS message.

– message type: REGISTER.

– facility:

invoke = Interrogation:

Supplementary service code = BOIC.

step 12 –

– protocol discriminator: non call related SS message.

– transaction identifier: same TI as previous REGISTER message.

– message type: RELEASE COMPLETE.

– facility:

reject code: resource limitation.

For the reject the invoke ID must be the same as in the invoke of the InterrogateSS operation.

31.8.7 Normal operation

In case of barring of outgoing call the calling mobile receives information about the activation of supplementary services subscribed.

In case of barring of incoming call the calling mobile receives information about the activation of supplementary services subscribed by the other party (the mobile called).

31.8.7.1 Conformance requirements

Upon receipt of the RELEASE COMPLETE message the MS shall provide the appropriate user indication (which is to be described by the manufacturer).

References

31.8.7.2 Test purpose

To check that upon receipt of the RELEASE COMPLETE message the MS provides the appropriate user indication (as described by the manufacturer).

This is tested in the case of an MS making a call to a mobile with incoming calls barred.

31.8.7.3 Method of test

Initial conditions

System Simulator:

1 cell, default parameters.

Mobile Station:

The MS is "idle updated".

Specific PICS Statements

PIXIT Statements

– Description of the user’s commands and of display of the answers from the network for call barring.

Foreseen final state of the MS

The MS is "idle updated".

Test procedure

The MS is made to initiate a call.

Upon receipt of the SETUP message, the system simulator answers with the negative acknowledgement RELEASE COMPLETE (to simulate a case where call barring is activated).

Maximum duration of test

1 minute.

Expected sequence

Step

Direction

Message

Comments

1

MS -> SS

CHANNEL REQUEST

2

SS -> MS

IMMEDIATE ASSIGNMENT

3

MS -> SS

CM SERVICE REQUEST

4

SS -> MS

CM SERVICE ACCEPT

5

MS -> SS

SETUP

6

SS -> MS

RELEASE COMPLETE

7

SS -> MS

CHANNEL RELEASE

8

MS

Provide correct MMI user indication after step 8

Specific message content

RELEASE COMPLETE

– protocol discriminator.

– transaction identifier.

– message type.

– cause: cause value #8.

– facility:

invoke = notification:

SS code = BI.

SS status = activation indicator (indicating: Provisioned, registered and active).