28 Test of autocalling restrictions

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

28.1 General

It is essential that all autocalling apparatus is prevented from continuously dialling a given number, to avoid machines repeatedly disturbing PSTN subscribers in error, or numerous repeat attempts to unobtainable numbers which cause waste of valuable network resources. Therefore autocalling restrictions are defined by 3GPP TS 02.07.

The tests shall be performed using all of the call methods specified by the supplier in the PIXIT statement (annex 3). The supplier shall state any autocalling procedures implemented and how many times they can be repeated to a single number and the minimum re-attempt interval(s), i.e. the complete re-try schedule or algorithm with parameter values. The supplier shall further describe any automatic methods for making repeated calls to a single number. The supplier shall also state in the PIXIT statement (annex 3) the number of B-party numbers that can be stored on the list of blacklisted numbers as described in 3GPP TS 02.07, annex A.

For an external R-interface the supplier shall state in the PIXIT statement (annex 3) the procedure for autocalling restrictions for that interface and the possible parameter settings for the number of times the LTE can make a re-attempt and the minimum accepted time between re-attempts accepted by the MS. The conditions for clearing the autocalling constraints shall be stated in the PIXIT statement (annex 3).

For external interfaces the LTE must be programmed so that it clearly attempts to violate the autocalling constraints.

28.2 Constraining the access to a single number (3GPP TS 02.07 category 3)

During this test the SETUP messages shall contain the same B-party number.

No manual intervention shall be performed except to initiate and end the test.

28.2.1 Conformance requirement

A repeat call attempt may be made when a call attempt is unsuccessful for the reasons listed below (as defined in 3GPP TS 04.08 / 3GPP TS 24.008).

These reasons are classified in three major categories:

1. "Busy destination".

2. "Unobtainable destination – temporary".

3. "Unobtainable destination – permanent/long term".

NOTE: Cause values for each category are defined in 3GPP TS 02.07, annex A.

The table below describes a repeat call restriction pattern to any B number. This pattern defines a maximum number (n) of call repeat attempts; when this number n is reached, the associated B number shall be blacklisted by the MT until a manual re-set at the MT is performed in respect of that B number. When a repeat attempt to anyone B number fails, or is blacklisted, this does not prevent calls being made to other B numbers.

For the categories 1 and 2 above, n shall be 10; for category 3, n shall be 1.

Call attempt

Minimum duration between call attempts

Initial call attempt

1st repeat attempt

5 s

2nd repeat attempt

1 min

3rd repeat attempt

1 min

4th repeat attempt

1 min

5th repeat attempt

3 min

.

.

nth repeat attempt

3 min

Reference:

3GPP TS 02.07, annex A.

Purpose of the test

28.2.2 Test purpose

To ensure the correct behaviour of the MS to 3GPP TS 02.07 Category 3.

28.2.3 Method of test

Initial condition.

There shall be no numbers in the list of blacklisted numbers in the MS. The time set between the first re-attempt and the next re-attempt is set to the minimum value possible. The number of re-attempts is set to the lowest possible number greater than 1 that is supported by the MS. The autocalling function is invoked for the B-party number to be used during the test.

Specific PICS statements:

  • Implementation of cause number 27 of busy autocalling in category 2 (TSPC_AddInfo_Impl_CNr27_Cat2)
  • Implementation of cause number 27 of busy autocalling in category 3 (TSPC_AddInfo_Impl_CNr27_Cat3)

PIXIT statements:

– Description of auto calling management:

– selection of the auto calling;

– indication that the call failed and a re-try is attempted;

– indication that a call finally failed;

– number of B-party numbers that can be stored in the list of blacklisted numbers

– Non standard keystroke sequences to be used on the EMMI (in line with 3GPP TS 11.10, clause 36).

Foreseen Final State of the MS

The MS has a valid TMSI. It is "idle updated".

Test Procedure

A MS initiated generic call setup is performed up to and including CIPERING MODE COMPLETE. The SS then releases the establishment with a cause value from Category 3 3GPP TS 02.07 annex A.

The MS will make one further generic call setup attempt invoked by the auto calling function after a channel release is sent out by the SS.

Step

Direction

Message

Comments

1

MS

"called number" entered

2

MS -> SS

CHANNEL REQUEST

Establishment cause indicates "originating call".

3

SS -> MS

IMMEDIATE ASSIGNMENT

4

MS -> SS

CM SERVICE REQUEST

Message is contained in SABM.

5

SS -> MS

AUTHENTICATION REQUEST

6

MS -> SS

AUTHENTICATION RESPONSE

7

SS -> MS

CIPHERING MODE COMMAND

8

MS -> SS

CIPHERING MODE COMPLETE

9

SS

SS starts ciphering.

10

MS -> SS

SETUP

11

SS -> MS

CIPHERING MODE COMMAND

12

MS -> SS

CIPHERING MODE COMPLETE

13

SS

SS stops ciphering

14

SS -> MS

RELEASE COMPLETE

Cause value from category 3 of 3GPP TS 02.07, annex A.

15

SS -> MS

CHANNEL RELEASE

The main signalling link is released

16

The MS is invoking the auto calling function. The time between step 15 and 17 must be minimum 5 sec.

17

MS -> SS

CHANNEL REQUEST

Establishment cause indicates "originating call".

18

SS -> MS

IMMEDIATE ASSIGNMENT

19

MS -> SS

CM SERVICE REQUEST

Message is contained in SABM.

20

SS -> MS

AUTHENTICATION REQUEST

21

MS -> SS

AUTHENTICATION RESPONSE

22

SS -> MS

CIPHERING MODE COMMAND

23

MS -> SS

CIPHERING MODE COMPLETE

24

SS

SS starts ciphering.

25

MS -> SS

SETUP

26

SS -> MS

CIPHERING MODE COMMAND

27

MS -> SS

CIPHERING MODE COMPLETE

28

SS

SS stops ciphering

29

SS -> MS

RELEASE COMPLETE

Cause value from category 3 of 3GPP TS 02.07, annex A.

30

SS -> MS

CHANNEL RELEASE

The main signalling link is released

31

MS

Clear the auto calling constraint by manual intervention after a minimum of 2 minutes from step 30.

28.3 Constraining the access to a single number (3GPP TS 02.07 categories 1 and 2)

During this test the SETUP messages shall contain the same B-party number.

No manual intervention shall be performed except to initiate and end the test.

28.3.1 Conformance requirement

The MS must fulfil the requirements for category 1 and 2, see subclause 28.2.1

Reference:

3GPP TS 02.07, annex A.

28.3.2 Test purpose

To ensure the correct behaviour of the MS to 3GPP TS 02.07 Categories 1 and 2.

28.3.3 Method of test

Initial condition.

There shall be no numbers in the list of blacklisted numbers in the MS. The re-try scheme is set to give the shortest possible intervals between re-tries. The number of re-attempts is set to the maximum possible number (N) that is supported by the MS. The autocalling function is invoked for the B-party number to be used during the test.

Specific PICS statements:

  • Implementation of cause number 27 of busy autocalling in category 2 (TSPC_AddInfo_Impl_CNr27_Cat2)
  • Implementation of cause number 27 of busy autocalling in category 3 (TSPC_AddInfo_Impl_CNr27_Cat3)

PIXIT statements:

– Description of auto calling management:

– selection of the auto calling;

– indication that the call failed and a re-try is attempted;

– indication that a call finally failed;

– number of B-party numbers that can be stored in the list of blacklisted numbers

– Non standard keystroke sequences to be used on the EMMI (in line with 3GPP TS 11.10, clause 36).

Foreseen Final State of the MS

The MS has a valid TMSI. It is "idle updated".

Test Procedure

A, MS initiated, generic call setup is performed up to and including CIPHERING MODE COMPLETE. The SS then releases the establishment with a cause value from category 1 or 2 ( 3GPP TS 02.07, annex A).

The MS is continuously making new generic call setup attempts invoked by the auto calling function after each CHANNEL RELEASE from the SS.

Step

Direction

Message

Comments

1

MS

"called number" entered

2

MS -> SS

CHANNEL REQUEST

Establishment cause indicates "originating call".

3

SS -> MS

IMMEDIATE ASSIGNMENT

4

MS -> SS

CM SERVICE REQUEST

Message is contained in SABM.

5

SS -> MS

AUTHENTICATION REQUEST

6

MS -> SS

AUTHENTICATION RESPONSE

7

SS -> MS

CIPHERING MODE COMMAND

SS starts deciphering after sending the message.

8

MS -> SS

CIPHERING MODE COMPLETE

9

SS

SS starts ciphering.

10

MS -> SS

SETUP

11

SS -> MS

CIPHERING MODE COMMAND

12

MS -> SS

CIPHERING MODE COMPLETE

13

SS

SS stops ciphering

14

SS -> MS

RELEASE COMPLETE

Cause value from category 1 or 2 of 3GPP TS 02.07, annex A. This shall be chosen randomly, from both categories. Cause no. 27 shall be excluded if the MS has implemented in category 3 of 3GPP TS 02.07, as declared in PIXIT statement

15

SS -> MS

CHANNEL RELEASE

The main signalling link is released

16

The MS is invoking the auto calling function. 1: At the first re-attempt the time between step 15 and 17 must be minimum 5 sec. 2: At the 2nd, 3rd and 4th re-attempt the time between step 15 and 17 must be minimum 1 min. 3: At the 5th to 10th re-attempt the time between step 15 and 17 must be minimum 3 min.

17

MS -> SS

CHANNEL REQUEST

Establishment cause indicates "originating call".

18

SS -> MS

IMMEDIATE ASSIGNMENT

19

MS -> SS

CM SERVICE REQUEST

Message is contained in SABM.

20

SS -> MS

AUTHENTICATION REQUEST

21

MS -> SS

AUTHENTICATION RESPONSE

22

SS -> MS

CIPHERING MODE COMMAND

SS starts deciphering after sending the message.

23

MS -> SS

CIPHERING MODE COMPLETE

24

SS

SS starts ciphering.

25

MS -> SS

SETUP

26

SS -> MS

CIPHERING MODE COMMAND

27

MS -> SS

CIPHERING MODE COMPLETE

28

SS

SS stops ciphering

29

SS -> MS

RELEASE COMPLETE

Cause value from category 1 or 2 of 3GPP TS 02.07, annex A. This shall be chosen randomly, from both categories. Cause no. 27 shall be excluded if the MS has implemented in category 3 of 3GPP TS 02.07, as declared in PIXIT statement

30

SS -> MS

CHANNEL RELEASE

The main signalling link is released.

31

The auto calling function shall repeat step 16 to 30 (N‑1) times. The MS shall not make more than maximum 10 re-attempts.

32

MS

Clear the auto calling constraint by manual intervention after a minimum of 4 minutes from step 31. Following the final completion of step 31 the MS initiate a call prior to manual intervention.

28.4 Behaviour of the MS when its list of blacklisted numbers is full

The number of B-party numbers that can be stored in the list of blacklisted numbers, as stated in the PIXIT statement (annex 3), is M.

28.4.1 Conformance requirement

The number of B numbers that can be held in the blacklist is at the manufacturer’s discretion but there shall be at least 8. However, when the blacklist is full the MT shall prohibit further automatic call attempts to any one number until the blacklist is manually cleared at the MT in respect of one or more B numbers.

Reference:

3GPP TS 02.07, annex A.

28.4.2 Test purpose

To ensure the correct behaviour of the MS when its list of blacklisted numbers is full.

28.4.3 Method of test

Initial condition.

The list of blacklisted numbers, in the MS, shall be full. This may be achieved as described in the procedure in subclause 28.2, applied to M B-party numbers.

Specific PICS statements:

  • Implementation of cause number 27 of busy autocalling in category 2 (TSPC_AddInfo_Impl_CNr27_Cat2)
  • Implementation of cause number 27 of busy autocalling in category 3 (TSPC_AddInfo_Impl_CNr27_Cat3)

PIXIT statements:

– Description of auto calling management:

– selection of the auto calling;

– indication that the call failed and a re-try is attempted;

– indication that a call finally failed;

– number of B-party numbers that can be stored in the list of blacklisted numbers.

– Non standard keystroke sequences to be used on the EMMI (in line with 3GPP TS 11.10, clause 36).

Foreseen Final State of the MS

The MS has a valid TMSI. It is "idle updated".

Test Procedure

The autocalling function is invoked for a B-party number that is not in the list of blacklisted numbers.

Clear the autocalling constraint by manual intervention after a minimum of 2 minutes.

28.4.4 Test requirements

The MS must not initiate a call.

Step

Direction

Message

Comments

1

MS

"called number" entered

2

MS -> SS

CHANNEL REQUEST

Establishment cause indicates "originating call".

3

SS -> MS

IMMEDIATE ASSIGNMENT

4

MS -> SS

CM SERVICE REQUEST

Message is contained in SABM.

5

SS -> MS

AUTHENTICATION REQUEST

6

MS -> SS

AUTHENTICATION RESPONSE

7

SS -> MS

CIPHERING MODE COMMAND

SS starts deciphering after sending the message.

8

MS -> SS

CIPHERING MODE COMPLETE

9

SS

SS starts ciphering.

10

MS -> SS

SETUP

11

SS -> MS

CIPHERING MODE COMMAND

SS stops deciphering after sending the message.

12

MS -> SS

CIPHERING MODE COMPLETE

13

SS

SS stops ciphering.

14

SS -> MS

RELEASE COMPLETE

Cause value from category 3 of 3GPP TS 02.07, annex A. This shall be chosen randomly. Cause no. 27 shall be excluded if the MS has implemented in category 2 of 3GPP TS 02.07, as declared in PIXIT statement

15

SS -> MS

CHANNEL RELEASE

The main signalling link is released

16

The MS is invoking the auto calling function. The time between step 15 and 17 must be minimum 5 sec.

17

MS -> SS

CHANNEL REQUEST

Establishment cause indicates "originating call".

18

SS -> MS

IMMEDIATE ASSIGNMENT

19

MS -> SS

CM SERVICE REQUEST

Message is contained in SABM.

20

SS -> MS

AUTHENTICATION REQUEST

21

MS -> SS

AUTHENTICATION RESPONSE

22

SS -> MS

CIPHERING MODE COMMAND

SS starts deciphering after sending the message.

23

MS -> SS

CIPHERING MODE COMPLETE

24

SS

SS starts ciphering.

25

MS -> SS

SETUP

26

SS -> MS

CIPHERING MODE COMMAND

SS stops deciphering after sending the message.

27

MS -> SS

CIPHERING MODE COMPLETE

28

SS

SS stops ciphering.

29

SS -> MS

RELEASE COMPLETE

Cause value from category 3 of 3GPP TS 02.07, annex A. This shall be chosen randomly. Cause no. 27 shall be excluded if the MS has implemented in category 2 of 3GPP TS 02.07, as declared in PIXIT statement

30

SS -> MS

CHANNEL RELEASE

The main signalling link is released.

31

The test shall be repeated from steps 1 to 30 using a different B party number each time until the blacklist is full as declared in PIXIT statement. The MS shall not make more than a maximum of 1 re-attempt on each number.

32

The test shall be repeated from steps 1 to 15 using a non-blacklisted B party number

33

SS

The SS verifies that the MS does not initiate an automatic re-attempt for a minimum of 2 minutes from step 32.

34

MS

Clear the auto calling constraint by manual intervention.