31.12 eMLPP Service

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

This subclause is applicable to the mobile stations supporting eMLPP service. The eMLPP is applicable to teleservices 1x, 6x, 9x and bearer services 2x, 3x, 4x, 5x.

For an MS supporting speech the test procedures in subclauses 31.12.1 and 31.12.2 are performed for full rate speech (teleservice 11, telephony). For an MS not supporting speech but supporting at least one of telecommunication services (TS6x, BS2x, BS3x, BS4x, BS5x), for each of the test procedures 31.12.1 and 31.12.2 a full rate service supported by the MS (see PICS/PIXIT statement) is chosen, and the test is performed corresponding to that service.

31.12.1 eMLPP Service / priority level of MO call

31.12.1.1 Conformance requirement

For the MS supporting MO calls:

1. Mobile stations indicate the priority of their call in the signalling that takes place during the call establishment process.

2. The MS shall verify the selected priority level against the priority levels stored in the SIM. If the selected priority is not allowed, then the priority of the call shall be modified to that of the nearest allowed priority level below the requested level.

3. In case of no priority selection or use of a non-compatible Mobile Station the Mobile Station shall send a standard service request message.

4. Signalling information required for the prioritisation at mobile originating call establishment. (see figure 1 of 3GPP TS 04.67 subclause 4.1.1) and Signalling information between the network and the calling mobile station required for the prioritisation in case of a VGCS or VBS call (figure 4 of 3GPP TS 04.67 subclause 4.1.4).

5. The user or the network may wish to omit or postpone authentication and ciphering in order to provide for a faster call set-up.

Reference(s)

3GPP TS 03.67 subclauses 11.3.1.1, 11.3.1.2, 11.6 and 11.3.1.3.

3GPP TS 02.67 clause 4.

3GPP TS 04.67 subclauses 4.1.1 and 4.1.4.

31.12.1.2 Test purpose

For the MS supporting MO, to verify that:

1. When user selects priority level for normal MO call, the priority level is indicated in the signalling message.

2. The MS verifies the selected priority level against the priority levels stored in the SIM. If the selected priority is not allowed, then the priority of the call shall be modified to that of the nearest allowed priority level below the requested level.

3. If the user does not select a priority level, the priority level is not indicated in the signalling message.

4. If a priority selection is performed by the user the MS provides the priority level information element in L3-MM CM SERVICE REQUEST message when a group call is initiated.

5. The mobile is able to establish a normal MO call with a priority level or a group call with a priority level according to the procedure specified in 3GPP TS 04.67 subclause 4.1.1 and the procedure in 3GPP TS 04.67 subclause 4.1.4.

6. The mobile is able to initiate a fast call set-up without authentication and ciphering.

31.12.1.3 Method of test

Initial Conditions

System Simulator:

1 cell with default parameters.

Mobile Station:

The MS is in idle mode with SIM in which the available priority levels are level 2, level 3, and level 4

Specific PICS Statements

– Support mobile originating call (TSPC_AddInfo_MOsvc)

– Support mobile emergency call (TSPC_Serv_TS12)

– Support VGCS originating (TSPC_AddInfo_VGCS_Originating)

– Support VBS originating (TSPC_AddInfo_VBS_Originating)

PIXIT Statements

– Way to select a priority level.

Foreseen Final State of the MS

"Idle, updated".

Test Procedure

The test steps 1 to 26 are repeated for k=1, 2, 3. After the repetition is finished the steps 27 to 71 are performed.

The test steps 1 to 7 are performed if the mobile station supports normal MO call. The steps 8 to 13 are executed if the MS supports TS12. The test steps 20 to step 26 are executed for k= 1, 2, 3, if the mobile station supports VGCS/VBS originating.

An allowed priority level (level 3) or a priority level (level 1) higher than allowed level or no priority level is selected by MMI action (for k=1, 2, 3 respectively). An MO call is attempted. It is checked that the MS indicates the selected priority level (for k=1) or the nearest allowed priority level below the selected level (for k=2) or no priority level (for k=3) in the signalling message.

A normal MO call is attempted with an allowed priority level (level 3). It is checked that the MS establishes completely this call.

If the mobile station supports VGCS/VBS originating a VGCS/VBS call is initiated via the MMI by using the SETUP procedure.

A MO VGCS/VBS call is attempted with the allowed priority level 0. It is checked that the MS establishes completely this call using the immediate setup procedure without authentication and ciphering.

Maximum Duration of Test

5 minutes.

Expected Sequence

Step

Direction

Message

Comments

1

MS

for k=1, MMI action to select a priority level 3

for k=2, MMI action to select a priority level 0

for k=3, no MMI action to select priority level

2

MS

to initiate a normal MO call

3

MS -> SS

CHANNEL REQUEST

4

SS -> MS

IMMEDIATE ASSIGNMENT

5

MS -> SS

CM SERVICE REQUEST

for k=1, containing priority IE with the selected priority

for k=2, containing priority IE with a priority level nearest allowed priority level below the requested one (level 2)

for k=3, containing no priority IE

6

SS -> MS

CM SERVICE REJECT

7

SS -> MS

CHANNEL RELEASE

8

MS

to initiate a normal MO emergency call

9

MS -> SS

CHANNEL REQUEST

10

SS -> MS

IMMEDIATE ASSIGNMENT

11

MS -> SS

CM SERVICE REQUEST

for k=1, containing priority IE with the selected priority

for k=2, containing priority IE with a priority level nearest allowed priority level below the requested one (level 2)

for k=3, containing no priority IE

12

SS -> MS

CM SERVICE REJECT

13

SS -> MS

CHANNEL RELEASE

20

MS

for k=1, MMI action to select a priority level 3

for k=2, MMI action to select a priority level 0

for k=3, no MMI action to select priority level

21

MS

to initiate a VGCS call by setup procedure, if supporting VGCS originating.

to initiate a VBS call by setup procedure, if supporting only VBS originating.

22

MS -> SS

CHANNEL REQUEST

23

SS -> MS

IMMEDIATE ASSIGNMENT

24

MS -> SS

CM SERVICE REQUEST

for k=1, containing priority IE with the selected priority

for k=2, containing priority IE with a priority level nearest allowed priority level below the requested one (level 2)

for k=3, containing no priority IE

25

SS -> MS

CM SERVICE REJECT

26

SS -> MS

CHANNEL RELEASE

27

MS

MMI action to select a priority level 3

28

MS

initiate a normal MO call

29

MS -> SS

CHANNEL REQUEST

30

SS -> MS

IMMEDIATE ASSIGNMENT

31

MS -> SS

CM SERVICE REQUEST

containing priority IE with a priority level nearest allowed priority level below the requested one (level 3)

32

SS -> MS

AUTHENTICATION REQUEST

33

MS -> SS

AUTHENTICATION RESPONSE

34

SS -> MS

CIPHERING MODE COMMAND

no ciphering

35

MS -> SS

CIPHERING MODE COMPLETE

36

MS -> SS

SETUP

37

SS -> MS

CALL PROCEEDING

38

SS -> MS

ASSIGNMENT COMMAND

39

MS -> SS

ASSIGNMENT COMPLETE

40

SS -> MS

ALERTING

41

SS -> MS

CONNECT

42

MS -> MS

CONNECT ACKNOWLEDGE

43

SS -> MS

DISCONNECT

44

MS -> SS

RELEASE

45

SS -> MS

RELEASE COMPLETE

46

SS -> MS

CHANNEL RELEASE

Steps 47 – 71 are performed if the MS supports VGCS/VBS originating

47

MS

MMI action to select a priority level 3 and initiate a VGCS/VBS call by setup procedure

49

MS -> SS

CHANNEL REQUEST

50

SS -> MS

IMMEDIATE ASSIGNMENT

51

MS -> SS

CM SERVICE REQUEST

containing priority IE with a priority level nearest allowed priority level below the requested one (level 3)

52

SS -> MS

AUTHENTICATION REQUEST

53

MS -> SS

AUTHENTICATION RESPONSE

54

SS -> MS

CIPHERING MODE COMMAND

no ciphering

55

MS -> SS

CIPHERING MODE COMPLETE

56

MS -> SS

SETUP

57

SS -> MS

CHANNEL MODE MODIFY

58

MS -> SS

CHANNEL MODE MODIFY ACKNOWLEDGE

59

SS -> MS

CONNECT

60

SS

Verify that TCH is through connected

61

SS -> MS

TERMINATION

62

SS -> MS

CHANNEL RELEASE

63

MS

MMI action to select a priority level 0, MMI action to initiate VGCS/VBS call.

64

MS -> SS

CHANNEL REQUEST

65

SS -> MS

IMMEDIATE ASSIGNMENT

TCH/F, single RF channel

GSM 450: 275

GSM 480: 322

GSM 900: 50

DCS 1800: 750

PCS 1 900: 650

GSM 710, GSM 750, T-GSM 810: 470

GSM 850: 177

66

MS -> SS

IMMEDIATE SETUP

L2: SABM / UA

67

SS -> MS

CHANNEL MODE MODIFY

very early assignment

68

MS -> SS

CHANNEL MODE MODIFY ACKNOWLEDGE

69

SS -> MS

CONNECT

verify that the TCH is through connected

70

SS

Verify that TCH is through connected

70

SS -> MS

TERMINATION

71

SS -> MS

CHANNEL RELEASE

Special Message Contents

CM SERVICE REQUEST in step 5 and step 24

for k=1, 2

Information Element

value/remark

as default except:

CM Service Type

not checked

Ciphering key sequence number

not checked

Mobile station classmark

not checked

Priority

Information element identifier

0001

Spare

0

Call priority

010 for k=1

011 for k=2

for k=3

Information Element

value/remark

as default except:

CM Service Type

not checked

Ciphering key sequence number

not checked

Mobile station classmark

not checked

Priority

not present

CM SERVICE REQUEST in step 11

for k=1, 2

Information Element

value/remark

as default except:

CM Service Type

"emergency call establishment"

Ciphering key sequence number

not checked

Mobile station classmark

not checked

Priority

Information element identifier

0001

Spare

0

Call priority

010 for k=1

for k=3

Information Element

value/remark

as default except:

CM Service Type

"emergency call establishment"

Ciphering key sequence number

not checked

Mobile station classmark

not checked

Priority

not present

31.12.2 eMLPP Service / automatic answering point-to-point MT call

31.12.2.1 Conformance requirement

For the MS supporting MT call:

1. Automatic answering or, if necessary, called-party pre-emption has to be performed by the Mobile Station as defined in the following:

– point-to-point calls:

If the user is in idle mode, the Mobile Station shall automatically connect to an incoming call of a sufficient priority level. If the user is in dedicated mode and has a subscription to Call Waiting, a Call Waiting indication including the priority level of the call shall be given to the Mobile Station which automatically accepts the waiting call.

2. In dedicated mode, in the case where the called subscriber has a subscription for eMLPP and for Call Waiting and is using a compatible Mobile Station, the Mobile Station shall be informed of the priority of the new call together with the call waiting indication. The Mobile Station will then consult the internal service configuration list stored on the SIM to establish whether it should automatically accept the waiting call without consulting the user, or whether the call waiting facility will be used as normal.

3. In the case where the called subscriber has a subscription for eMLPP and for CW, the mobile station shall be informed of the priority of the new call together with the CW indication. On reception of the set-up message the compatible mobile station decides on called party pre-emption. If called party pre-emption applies, the mobile station shall automatically accept the waiting call and send a hold message to the network. If a hold acknowledge is received, the waiting call is accepted. If a hold reject is received for any reason, e.g. there is no subscription for hold, the other call shall be released and the waiting call accepted. If the ongoing call is not a TS11 call, the mobile station should not send a hold message to the network but release the call and accept the waiting call.

Reference(s)

3GPP TS 02.67 subclause 4, 5.9.

3GPP TS 03.67 clause 4, subclauses 11.3.2.4, 11.3.2.5 and 11.6.

3GPP TS 04.67 subclause 4.1.3.

3GPP TS 04.83 subclauses 1.1 and 1.2.

31.12.2.2 Test purpose

For the MS supporting MT call, to verify that:

1. In idle mode the MS automatically accepts an incoming point-to-point call of priority level for which automatic answering is enabled.

2. In idle mode the MS alerts an incoming point-to-point call of a priority level for which automatic answering is disabled.

3. In dedicated mode and supporting Call Waiting, when a Call Waiting indication includes a level for which automatic answering is enabled and the priority level is higher than the ongoing point-to-point call, the MS automatically confirms the waiting call and sends a hold message to the network. If a hold reject is received the other call is released and the waiting call is accepted.

4. In dedicated mode and supporting Call Waiting, when a Call Waiting indication includes a priority level for which automatic answering is enabled and the priority level is equal or lower than the priority level of the ongoing call, the MS indicates the waiting call.

5. In group receive mode the MS automatically responds to the paging message containing a priority level for which automatic answering is enabled and the priority level is higher than the priority level of the ongoing call.

6. In group receive mode the MS indicates an incoming point-to-point call of a priority level for which automatic answering is enabled and the priority level is equal or lower than the priority level of the ongoing call.

31.12.2.3 Method of test

Initial Conditions

System Simulator:

1 cell with default parameters.

Mobile Station:

The MS is in idle mode.

The auto answering priority level is set to higher than priority level 2.

Specific PICS Statements

– Support VGCS listening (TSPC_AddInfo_VGCS_Listening)

– Support VBS listening (TSPC_AddInfo_VBS_Listening)

PIXIT Statements

– Way to configure automatic answering.

– Way to indicate a call has been automatically answered.

Foreseen Final State of the MS

"Idle, updated".

Test Procedure

The call waiting is activated. The MS is in idle mode and automatic answering for priority level 2 is disabled. A PAGING REQUEST message containing priority level 2 is sent. It is checked that the MS indicates the incoming call to the user. The automatic answering for level 1 is enabled. A PAGING REQUEST message with priority level 2 is sent. It is checked that the MS automatically accepts the incoming normal call. The call is released. A PAGING REQUEST message without priority level is sent, and during the call set-up the SETUP message contains priority level 1. It is checked that the MS automatically accepts the incoming normal call.

The MS is in dedicated mode (If the MS supports TS11, TS11service shall be selected for the dedicated mode testing). a SETUP message with priority level higher enough for auto answering is sent by the SS. It is checked that the MS automatically accepts the incoming normal call. A SETUP message containing low priority level without auto answering is sent. It is checked that the MS indicates the incoming call to the user.

The MS is in group receive mode, a NOTIFICATION/FACCH message containing paging information and a PAGING REQUEST message with priority level 0 are sent. It is checked that the MS automatically accepts the incoming normal call. The MS is brought into group receive mode. A NOTIFICATION/FACCH message containing paging information and a PAGING REQUEST message containing low priority level are sent. It is checked that the MS indicates the incoming call to the user.

Maximum Duration of Test

5 minutes.

Expected Sequence

Step

Direction

Message

Comments

0

MS

the MS is in idle mode and auto answering for priority level 2 is disabled

1

SS -> MS

PAGING REQUEST TYPE 1

with priority level 2

2

MS -> SS

CHANNEL REQUEST

3

SS -> MS

IMMEDIATE ASSIGNMENT

SDCCH

4

MS -> SS

PAGING RESPONSE

5

SS -> MS

SETUP

containing priority level 2, but no signal IE

6

MS -> SS

CALL CONFIRMED

7

SS -> MS

ASSIGNMENT COMMAND

TCH

8

MS -> SS

ASSIGNMENT COMPLETE

9

MS -> SS

ALERTING

10

MS

An alerting indication as defined in a PICS/PIXIT statement is given by the MS

11

MS

The MS is made to accept the call in the way described in a PICS/PIXIT statement

12

MS -> SS

CONNECT

13

SS -> MS

CONNECT ACKNOWLEDGE

14

SS -> MS

DISCONNECT

15

MS -> SS

RELEASE

16

SS -> MS

RELEASE COMPLETE

17

SS -> MS

CHANNEL RELEASE

return to idle mode

21

SS -> MS

PAGING REQUEST TYPE 1

containing priority level 1

22

MS -> SS

CHANNEL REQUEST

23

SS -> MS

IMMEDIATE ASSIGNMENT

SDCCH

24

MS -> SS

PAGING RESPONSE

25

SS -> MS

SETUP

containing priority level 1, but no signal IE

26

MS -> SS

CALL CONFIRMED

27

MS -> SS

CONNECT

automatic connection

28

SS -> MS

ASSIGNMENT COMMAND

TCH

29

MS -> SS

ASSIGNMENT COMPLETE

30

SS -> MS

CONNECT ACKNOWLEDGE

31

MS

to check that the MS gives an indication as defined in a PICS/PIXIT statement for call automatically answered

32

SS -> MS

DISCONNECT

33

MS -> SS

RELEASE

34

SS -> MS

RELEASE COMPLETE

35

SS -> MS

CHANNEL RELEASE

return to idle mode

36

SS -> MS

PAGING REQUEST TYPE 1

containing no priority level

37

MS -> SS

CHANNEL REQUEST

38

SS -> MS

IMMEDIATE ASSIGNMENT

SDCCH

39

MS -> SS

PAGING RESPONSE

40

SS -> MS

SETUP

containing priority level 3, but no signal IE

41

MS -> SS

CALL CONFIRMED

42

MS -> SS

CONNECT

automatic connection

43

SS -> MS

ASSIGNMENT COMMAND

TCH

44

MS -> SS

ASSIGNMENT COMPLETE

45

SS -> MS

CONNECT ACKNOWLEDGE

51

SS -> MS

SETUP

new transaction, containing priority level 1 and Signal Information Element with value #7

52

MS -> SS

CALL CONFIRMED

on new transaction with cause #17

53a

MS -> SS

HOLD

on old transaction for service TS11

53b

no signalling for services other than TS11

54a

SS -> MS

HOLD REJECT

on old transaction for service TS11 with cause #69

54b

no signalling for services other than TS11

55

MS -> SS

DISCONNECT

on old transaction, cause = ‘Normal call clearing’

56

SS -> MS

RELEASE

on old transaction

57

MS -> SS

RELEASE COMPLETE

on old transaction

58

MS -> SS

CONNECT

on new transaction

59

SS -> MS

CONNECT ACKNOWLEDGE

on new transaction

60

SS -> MS

SETUP

another new transaction different from step 51, containing priority level 1 and Signal Information Element with value #7

61

MS -> SS

CALL CONFIRMED

on the same transaction as step 60, with cause #17

62

MS -> SS

ALERTING

on the same transaction as step 60

63

MS

to check that the MS gives incoming call indication

64

SS -> MS

DISCONNECT

on the same transaction as step 51

65

MS -> SS

RELEASE

on the same transaction as step 51

66

SS -> MS

RELEASE COMPLETE

on the same transaction as step 51

67

SS -> MS

CHANNEL RELEASE

70

MS

the MS is in group receive mode, the priority level of current call is level 3

72

SS -> MS

PAGING REQUEST TYPE 1

containing priority level 0

73

MS -> SS

CHANNEL REQUEST

74

SS -> MS

IMMEDIATE ASSIGNMENT

SDCCH

75

MS -> SS

PAGING RESPONSE

76

SS -> MS

SETUP

without priority level and signal IE

77

MS -> SS

CALL CONFIRMED

78

MS -> SS

CONNECT

automatic connection

79

SS -> MS

ASSIGNMENT COMMAND

TCH

80

MS -> SS

ASSIGNMENT COMPLETE

81

SS -> MS

CONNECT ACKNOWLEDGE

82

SS -> MS

DISCONNECT

83

MS -> SS

RELEASE

84

SS -> MS

RELEASE COMPLETE

85

SS -> MS

CHANNEL RELEASE

86

MS

the MS is brought into group receive mode with the priority level 3

88

SS -> MS

PAGING REQUEST TYPE 1

containing priority level 3

89

MS

to check that the MS gives incoming call indication

90

SS -> MS

CHANNEL RELEASE

UI format

31.12.3 eMLPP Service / automatic answering MT VGCS or VBS call

31.12.3.1 Conformance requirement

For the MS supporting VGCS/VBS listening:

1. Automatic answering or, if necessary, called-party pre-emption has to be performed by the Mobile Station as defined in the following:

– voice group calls and voice broadcast calls:

Notifications for other voice group calls, voice broadcast calls or information on paging for point-to-point calls shall be given to the Mobile Stations involved in on-going voice group calls or voice broadcast calls as defined in 3GPP TS 03.68 and 3GPP TS 03.69, respectively. The notifications include the related priority level of the call. In case of a notified call with higher priority where called-party pre-emption applies, the Mobile Station shall automatically leave the on-going voice group call or voice broadcast call and react according to the type of the notified call type.

2. In dedicated mode, in the case where the called subscriber has a subscription for eMLPP and for Call Waiting and is using a compatible Mobile Station, the Mobile Station shall be informed of the priority of the new call together with the call waiting indication. The Mobile Station will then consult the internal service configuration list stored on the SIM to establish whether it should automatically accept the waiting call without consulting the user, or whether the call waiting facility will be used as normal.

3. In the case where the called subscriber has a subscription for eMLPP and for CW, the mobile station shall be informed of the priority of the new call together with the CW indication. On reception of the notification message the compatible mobile station decides on called party pre-emption. If called party pre-emption applies, the mobile station shall automatically release the call and join the new call.

Reference(s)

3GPP TS 02.67 clause 4.

3GPP TS 03.68 clause 4, subclauses 11.3.1.3 and 11.3.1.4.

3GPP TS 03.67 clause 4.

3GPP TS 04.67 subclause 4.1.5.

31.12.3.2 Test purpose

For the MS supporting VGCS/VBS listening, to verify that:

1. In idle mode the MS automatically accepts an incoming VGCS or VBS call of sufficient priority level.

2. In idle mode the MS indicates an incoming VGCS or VBS call of priority level not high enough for automatic answering.

3. In dedicated mode, the MS automatically accepts an incoming VGCS or VBS call of sufficient priority level.

4. In dedicated mode, the MS indicates an incoming VGCS or VBS call of priority level not high enough for automatic answering.

5. In group receive mode the MS automatically accepts an incoming VGCS or VBS call of sufficient priority level.

6. In group receive mode the MS indicates an incoming VGCS or VBS call of priority level not high enough for automatic answering.

31.12.3.3 Method of test

Initial Conditions

System Simulator:

1 cell with default parameters.

Mobile Station:

The MS is in idle mode.

The auto answering priority level is set to higher than priority level 2.

Specific PICS Statements

PIXIT Statements

– Way to configure automatic answering.

– Way to indicate that a VGCS/VBS call has been automatically accepted.

Foreseen Final State of the MS

"Idle, updated".

Test Procedure

The MS is in idle mode. a NOTIFICATION/NCH message with priority level higher enough for auto answering is sent. It is checked that the MS automatically accepts the incoming VGCS/VBS call. The call is released. A NOTIFICATION/NCH message containing low priority level without auto answering is sent. It is checked that the MS indicates the incoming VGCS/VBS call to the user.

The MS is in dedicated mode. a NOTIFICATION/FACCH message with priority level higher enough for auto answering is sent. It is checked that the MS automatically accepts the incoming VGCS/VBS call. A NOTIFICATION/FACCH message containing low priority level without auto answering is sent. It is checked that the MS indicates the incoming VGCS/VBS call to the user.

The MS is in group receive mode. a NOTIFICATION/FACCH message with priority level higher enough for auto answering and containing VGCS/VBS channel description is sent. It is checked that the MS automatically accepts the incoming VGCS/VBS call. A NOTIFICATION/FACCH message containing priority level not higher enough for auto answering and containing VGCS/VBS channel description is sent. It is checked that the MS indicates the incoming VGCS/VBS call to the user.

Maximum Duration of Test

5 minutes.

Expected Sequence

Step

Direction

Message

Comments

1

MS

the MS is in idle mode

2

SS -> MS

NOTIFICATION/NCH

containing priority level 1

3

MS

to check that the MS automatically accepts the VGCS/VBS call

4

SS

stop sending NOTIFICATION/NCH

5

SS -> MS

CHANNEL RELEASE

UI format, release VGCS/VBS channel

6

SS -> MS

NOTIFICATION/NCH

containing priority level 3

7

MS

to check that the MS indicates the VGCS/VBS call to the user

8

SS

stop sending NOTIFICATION/NCH

15

MS

the MS is in dedicated mode, the priority level of current call is level 3

16

SS -> MS

NOTIFICATION/FACCH

containing priority level 2

17

MS -> SS

DISCONNECT

18

SS -> MS

RELEASE

19

MS -> SS

RELEASE COMPLETE

20

SS -> MS

CHANNEL RELEASE

21

MS

to check that the MS automatically accepts the VGCS/VBS call

22

SS -> MS

CHANNEL RELEASE

UI format, release VGCS/VBS channel

23

MS

the MS is brought into dedicated mode, the priority level of current call is level 3

24

SS -> MS

NOTIFICATION/FACCH

containing priority level 4

25

MS

to check that the MS indicates the VGCS/VBS call to the user

26

SS

stop sending NOTIFICATION/FACCH

27

SS -> MS

DISCONNECT

28

MS -> SS

RELEASE

29

SS -> MS

RELEASE COMPLETE

30

SS -> MS

CHANNEL RELEASE

I format, release dedicated channel

31

MS

the MS is in group receive mode, the priority level of current call is level 3

32

SS -> MS

NOTIFICATION/FACCH

containing priority level 1 and with VGCS/VBS channel description

33

MS

to check the MS automatically accepts the incoming VGCS/VBS call

34

SS -> MS

NOTIFICATION/FACCH

containing priority level 4 and with VGCS/VBS channel description

35

MS

to check the MS indicates the incoming VGCS/VBS call to the user

36

SS -> MS

CHANNEL RELEASE

UI format, release VGCS/VBS channel

31.12.4 eMLPP Service / registration

31.12.4.1 Conformance requirement

For registration of eMLPP default priority level, the MS shall transmit successively:

1. A CHANNEL REQUEST with establishment cause set to "other services requested by the mobile user".

2. A CM SERVICE REQUEST with CM service type indicating "supplementary service activation".

3. An eMLPP registration request from a mobile user shall include the SS-Code of the eMLPP service and the default priority level.

Reference(s)

3GPP TS 04.67 subclause 4.2 (figure 6).

3GPP TS 04.08 / 3GPP TS 44.018 subclauses 3.3.1.2 and 9.1.8.

3GPP TS 04.08 / 3GPP TS 24.008 subclauses 4.5.1.1 and 9.2.9.

31.12.4.2 Test purpose

To check that the MS:

1. Correctly requests a supplementary service transaction for registration of eMLPP in CHANNEL REQUEST message.

2. Correctly requests a supplementary service transaction for registration of eMLPP in the subsequent CM SERVICE REQUEST.

3. Then sends a REGISTER message containing the invoke of the RegisterSS operation with the expected parameter values for registration of eMLPP default priority level.

4. Provides the appropriate user indication (as described by the manufacturer) upon receipt of the result of the operation (in a RELEASE COMPLETE message).

31.12.4.3 Method of test

Initial Conditions

System Simulator:

1 cell with default parameters.

Mobile Station:

the MS is in idle mode

Specific PICS Statements

PIXIT Statements

– Way to select a priority level.

– Way to initiate eMLPP registration.

– Way to indicate the result of the eMLPP registration.

Foreseen Final State of the MS

"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 eMLPP for a default priority level DefaultPriorityLevel arbitrarily selected.

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 of the RegisterSS operation.

The SS transaction is released and the dedicated channel is released.

Then check the MS provides a correct user indication.

Maximum Duration of Test

3 minutes.

Expected Sequence

Step

Direction

Message

Comments

1

MS

The MS is made to initiate a registration of eMLPP default priority level

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

RegisterSS(eMLPP, DefaultPriorityLevel)

7

SS -> MS

RELEASE COMPLETE

RegisterSS operation Return_result

8

SS -> MS

CHANNEL RELEASE

9

MS

Provide correct MMI user indication after step 7

Special Message Contents

REGISTER:

Information Element

value/remark

as default except:

Facility

invoke

RegisterSS

Supplementary service code

eMLPP

Default Priority

arbitrary

31.12.5 eMLPP Service / interrogation

31.12.5.1 Conformance requirement

For interrogation of eMLPP default priority level, the MS shall transmit successively:

1. A CHANNEL REQUEST with establishment cause set to "other services requested by the mobile user".

2. A CM SERVICE REQUEST with CM service type indicating "supplementary service activation".

3. And then the REGISTER message containing a facility IE that includes an invoke of the InterrogateSS operation with parameter values eMLPP (MMI action) (see figure 7 of 3GPP TS 04.67 subclause 4.5).

Reference(s)

3GPP TS 04.67 subclause 4.5 (figure 7).

3GPP TS 04.08 / 3GPP TS 44.018 subclauses 3.3.1.2 and 9.1.9.

3GPP TS 04.08 / 3GPP TS 24.008 subclauses 4.5.1.1 and 9.2.9.

31.12.5.2 Test purpose

To check that the MS:

1. Correctly requests a supplementary service transaction for interrogation of eMLPP in CHANNEL REQUEST message.

2. Correctly requests a supplementary service transaction for interrogation of eMLPP in the subsequent CM SERVICE REQUEST.

3. Then sends a REGISTER message containing the invoke of the InterrogateSS operation with the expected parameter values for interrogation of eMLPP default priority level.

4. Provides the appropriate user indication (as described by PIXIT) upon receipt of the result of the operation (in a RELEASE COMPLETE message).

31.12.5.3 Method of test

Initial Conditions

System Simulator:

1 cell with default parameters.

Mobile Station:

the MS is in idle mode

Specific PICS Statements

PIXIT Statements

– Way to select a priority level.

– Way to initiate eMLPP interrogation.

– Way to indicate the result of the eMLPP interrogation.

Foreseen Final State of the MS

"Idle, updated".

Test Procedure

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

2. 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 of the InterrogateSS operation.

3. The SS transaction is released and the dedicated channel is released.

4. Then check the MS provides a correct user indication.

Maximum Duration of Test

3 minutes.

Expected Sequence

Step

Direction

Message

Comments

1

MS

The MS is made to initiate a interrogation of eMLPP default priority level

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

InterrogateSS(eMLPP)

7

SS -> MS

RELEASE COMPLETE

InterrogateSS operation Return_result containing SS-Status, MaximumPriorityLevel, DefaultPriorityLevel

8

SS -> MS

CHANNEL RELEASE

9

MS

Provide correct MMI user indication after step 7

Special Message Contents

REGISTER:

Information Element

value/remark

as default except:

Facility

invoke

InterrogateSS

Supplementary service code

eMLPP