31.15 Follow Me (FM)

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

This subclause applies to mobile station supporting Follow Me (FM). The objective of this clause is to test FM concerned procedures.

Unless indicated in individual sub-clauses, the default message contents in subclause 31.11 are applied.

31.15.1 Follow Me (FM) / Registration

31.15.1.1 Conformance requirement

1. The initiating subscriber registers the Follow Me feature with respect to a particular remote party. The initiating subscriber shall provide the following information to the network: the number of the remote party. The initiating subscriber shall receive an indication if the FM registration request was accepted or rejected by the network.

2. MS shall behave as indicated in the Information flow as indicated in 3GPP TS 23.094, figure 4.1.

3. As an operator’s option additional information (such as passwords) for registration may be required from the initiating subscriber. This information shall be coded as a USSD string with a length not exceeding 30 characters.

4. All the messages between MS and the mobile network and internal to the mobile network, which are used for control of Follow Me, are USSD Phase 2 messages.

5. If a mobile initiated USSD request using protocol version 2 is rejected by the network, and the reason for the rejection is indicated either by the problem code "unrecognized operation" or a cause "Facility rejected", the MS shall assume that the network only supports protocol version 1 of USSD operations. The MS shall re‑attempt the request by using the appropriate protocol version 1 USSD operation without an SS version indicator if the unstructured data entered by the user can be coded as an IA5 string.

References

3GPP TS 22.094 subclause 6.3.

3GPP TS 23.094 subclauses 4.1, 4.2 and 4.4.

3GPP TS 24.090 subclause 6.1.

31.15.1.2 Test purpose

1. To check that the MS correctly requests a supplementary service transaction for registration of FM in CHANNEL REQUEST message and in the subsequent CM SERVICE REQUEST.

2. To check that the MS sends a REGISTER message using USSD phase 2 and containing the FM-request control message for registration.

3. To check that upon receipt of the result or the error of the operation (in a RELEASE COMPLETE message), the MS provides the appropriate user indication (as described by the manufacturer).

4. To check that upon receipt of a rejection from the network with the problem code "unrecognized operation" or a cause "Facility rejected", the MS re-attempt the request by using USSD version 1.

31.15.1.3 Method of test

Initial conditions

System Simulator:

1 cell, default parameters.

Mobile Station:

The MS is in MM-state "idle, updated" with valid TMSI and CKSN.

Specific PICS Statements

PIXIT Statements

– Way to activate the registration of FM.

– Description of display of the FM answers from the network.

Foreseen final state of the MS

The MS is in MM-state "idle, updated" with valid TMSI.

Test procedure

By means of appropriate MMI functions, the user requests registration of FM for a remote number. Upon receipt of the REGISTER message, SS answers with the RELEASE COMPLETE message with an unsuccessful FM-result information. Check that the MS provides the appropriate user indication (as described by the manufacturer). Then SS transaction is released. This procedure is executed for all possible error values.

The user requests registration of FM for another remote subscriber. Upon receipt of the operation (in a REGISTER message), SS answers with a RELEASE COMPLETE message with a successful FM-response information. Check that the MS provides the appropriate user indication (as described by the manufacturer). The SS transaction is released.

Then user request again two registrations, upon receipt of the REGISTER message, SS answers with a RELEASE COMPLETE message including a rejection with respectively the problem code "unrecognized operation" or a cause "facility rejected". Check that MS re-attempt the request by using USSD version 1: without the SS version indicator information element included in the REGISTER message.

Maximum Duration of Test

2 minutes.

Expected Sequence

Test steps 1 to 10 are executed for k=1 to 13 with respectively the following error values:

1. Illegal interaction with incoming barring.

2. Unauthorised request.

3. Unknown remote party.

4. FM not subscribed.

5. Remote party already registered.

6. Unauthorised changes to remote party.

7. Illegal interaction with call forwarding.

8. Illegal interaction with call barring.

9. Request to own MSISDN not possible.

10. Forwarded-to number is invalid directory number.

11. Insufficient information.

12. Forwarded-to number is a special code.

13. Conflicting situation with other supplementary services.

Step

Direction

Message

Comments

0

MS

The MS is in idle mode.

1

MS

The MS is made to initiate a registration of FM

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

Check that the content of this message matches specific message contents.

7

SS -> MS

RELEASE COMPLETE

With an unsuccessful FM-result info with the following error value:

k=1: Illegal interaction with incoming barring (code 21)

k=2: Unauthorised request (code 22)

k=3: Unknown remote party (code 41)

k=4: FM not subscribed (code 42)

k=5: Remote party already registered (code 61)

k=6: Unauthorised changes to remote party (code 64)

k=7: Illegal interaction with call forwarding (code 65)

k=8: Illegal interaction with call barring (code 66)

k=9: Request to own MSISDN not possible (code 67)

k=10: Forwarded-to number is invalid directory number (code 80)

k=11: Insufficient information (code 81)

k=12: Forwarded-to number is a special code (code 82)

k=13: Conflicting situation with other supplementary services (code 83)

See specific message contents.

8

SS -> MS

CHANNEL RELEASE

9

MS

Check that the MS, in a way described by the manufacturer, displays the error after step 7

15

MS

The MS is made to initiate a registration of FM

16

MS -> SS

CHANNEL REQUEST

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

17

SS -> MS

IMMEDIATE ASSIGNMENT

18

MS -> SS

CM SERVICE REQUEST

Cause: "supplementary service activation"

19

SS -> MS

CM SERVICE ACCEPT

20

MS -> SS

REGISTER

Check that the content of this message matches specific message contents.

21

SS -> MS

RELEASE COMPLETE

With a successful FM-result. See specific message contents.

22

SS -> MS

CHANNEL RELEASE

23

MS

It is checked that the MS, in a way described by the manufacturer, displays the positive result after step 21

30

MS

The MS is made to initiate a registration of FM

31

MS -> SS

CHANNEL REQUEST

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

32

SS -> MS

IMMEDIATE ASSIGNMENT

33

MS -> SS

CM SERVICE REQUEST

Cause: "supplementary service activation"

34

SS -> MS

CM SERVICE ACCEPT

35

MS -> SS

REGISTER

Check that the content of this message matches specific message contents.

36

SS -> MS

RELEASE COMPLETE

Including a rejection with the problem code "unrecognized operation"

37

SS -> MS

CHANNEL RELEASE

38

MS -> SS

CHANNEL REQUEST

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

39

SS -> MS

IMMEDIATE ASSIGNMENT

40

MS -> SS

CM SERVICE REQUEST

Cause: "supplementary service activation"

41

SS -> MS

CM SERVICE ACCEPT

42

MS -> SS

REGISTER

Check that SS version indicator IE is not included. See specific message contents.

43

SS -> MS

RELEASE COMPLETE

With a successful FM-result. See specific message contents.

44

SS -> MS

CHANNEL RELEASE

45

It is checked that the MS, in a way described by the manufacturer, displays the positive result after step 43

50

MS

The MS is made to initiate a registration of FM

51

MS -> SS

CHANNEL REQUEST

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

52

SS -> MS

IMMEDIATE ASSIGNMENT

53

MS -> SS

CM SERVICE REQUEST

Cause: "supplementary service activation"

54

SS -> MS

CM SERVICE ACCEPT

55

MS -> SS

REGISTER

The SS checks that the content of this message matches specific message contents.

56

SS -> MS

RELEASE COMPLETE

Including a rejection with the cause value Facility rejected. See specific message contents.

57

SS -> MS

CHANNEL RELEASE

58

MS -> SS

CHANNEL REQUEST

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

59

SS -> MS

IMMEDIATE ASSIGNMENT

60

MS -> SS

CM SERVICE REQUEST

Cause: "supplementary service activation"

61

SS -> MS

CM SERVICE ACCEPT

62

MS -> SS

REGISTER

Check that SS version indicator IE is not included. See specific message contents.

63

SS -> MS

RELEASE COMPLETE

With a successful FM-result. See specific message contents.

64

SS -> MS

CHANNEL RELEASE

65

MS

It is checked that the MS, in a way described by the manufacturer, displays the positive result after step 63

Specific message contents:

REGISTER

Information Element

value/remark

Supplementary service protocol discriminator

Supplementary service (call independent)

Transaction identifier

‘1011’B

Message type

As 3GPP TS 24.080

Facility 1C

See below

SS version indicator

As specified in 3GPP TS 24.080

For steps 42 and 62 omitted

For steps 6, 20, 35 and 55, Facility Information Element with Invoke = ProcessUnstructuredSS-Request component type as defined in 3GPP TS 24.080 subclause 3.6.1 table 3.3.

Contents

Value/remark

Facility IE identifier

As 3GPP TS 24.080

Length of FIE contents

depending on the length of ussd-string

Component type tag

Invoke CS/C/tag=1

Component length

depending on the length of ussd-string

InvokeID tag

From 3GPP TS 24.080

Invoke ID length

1

Invoke ID

Arbitrary (1 octet)

Operation Code tag

From 3GPP TS 24.080

Operation Code length

1

Operation Code

UnstructuredSS-Request

Ussd-dataCodingScheme

1 octet long. Alphabet indicator set to "default alphabet". Language indicator set to "undefined"

Ussd-string

For step 6 **214*04965878***#

For step 20 **214*04969***#

For steps 35 and 55 **214*31245688***#

RELEASE COMPLETE

Information Element

value/remark

Supplementary service protocol discriminator

Supplementary service (call independent)

Transaction identifier

the transaction value is the same as the REGISTER transaction value but the transaction flag is different

Message type

As 3GPP TS 24.080

Cause

For step 56, cause is set to "facility rejected" and FIE is omitted.

For steps 7,21,43,63,36 this field is omitted.

Facility Information Element

See below (omitted for step 56)

SS version indicator

As specified in 3GPP TS 24.080

For steps 7, 21, 43 and 63, Facility Information Element with Return result = ProcessUnstructuredSS-Request return result component type as defined in 3GPP TS 24.080 subclause 3.6.1 table 3.6.

Contents

Value/remark

Facility IE identifier

As 3GPP TS 24.080

Length of FIE contents

depending on the length of ussd-string

Component type tag

Return result

Component length

depending on the length of ussd-string

InvokeID tag

From 3GPP TS 24.080

Invoke ID length

1

Invoke ID

The same as the invoke of the ProcessUnstructuredSS-Request

Ussd-dataCodingScheme

1 octet long. Alphabet indicator set to "default alphabet". Language indicator set to "undefined"

Ussd-string

For step 7: value of the error code

For steps 21 43 and 63: 01

For step 36, Facility Information Element with Reject = ProcessUnstructuredSS-Request return result component type as defined in 3GPP TS 24.080 subclause 3.6.1 table 3.6.

Contents

Value/remark

Facility IE identifier

As 3GPP TS 24.080

Length of FIE contents

depending on the length of ussd-string

Component type tag

Reject

Component length

depending on the length of ussd-string

InvokeID tag

From 3GPP TS 24.080

Invoke ID length

1

Invoke ID

The same as the invoke of the ProcessUnstructuredSS-Request

Problem Code tag

As 3GPP TS 24.080

Problem Code length

1

General Problem code

Unrecognized operation

31.15.2 Follow Me (FM) / Interrogation

31.15.2.1 Conformance requirement

1. An initiating subscriber (also the FM service supervisor) shall be able to interrogate the Follow Me data of any remote party, for which she is authorised to become initiating subscriber.

2. In case the remote party corresponds to a subscriber the remote party shall be able to interrogate her own Follow Me data stored in the network.

3. As an operator’s option additional information (such as passwords) for interrogation may be required from the subscriber. The registration procedure shall transport this information from the subscriber to the network of the remote party. This information shall be coded as a USSD string with a length not exceeding 30 characters.

4. All the messages between MS and the mobile network and internal to the mobile network, which are used for control of Follow Me, are USSD Phase 2 messages.

5. MS shall behave as indicated in the Information flow as indicated in 3GPP TS 23.094, figure 4.1.

References

3GPP TS 22.094 subclauses 6.8 and 7.3.

3GPP TS 23.094 subclauses 4.1, 4.2 and 4.4.

3GPP TS 24.090 subclause 6.1.

31.15.2.2 Test purpose

1. To check that the MS (as initiating subscriber or remote party) correctly requests a supplementary service transaction for interrogation of FM in CHANNEL REQUEST message and in the subsequent CM SERVICE REQUEST.

2. To check that the MS sends a REGISTER message using USSD version 2 and containing the FM-request control message for interrogation.

3. To check that upon receipt of the result or the error of the operation (in a RELEASE COMPLETE message), the MS provides the appropriate user indication (as described by the manufacturer).

31.15.2.3 Method of test

Initial conditions

System Simulator:

1 cell, default parameters.

Mobile Station:

The MS is in MM-state "idle, updated" with valid TMSI and CKSN. The MS is registered to FM with respect to a remote party B.

Specific PICS Statements

PIXIT Statements

– Way to activate the interrogation of FM.

– Description of display of the FM answers from the network.

Foreseen final state of the MS

The MS is in MM-state "idle, updated" with valid TMSI.

Test procedure

MS is registered to FM.

By means of appropriate MMI functions, the user requests interrogation of FM for a remote number. Upon receipt of the REGISTER message, SS answers with the RELEASE COMPLETE message with an unsuccessful FM-result in a facility information element. Check that the MS provides the appropriate user indication (was described by the manufacturer). Then SS transaction is released. This procedure is executed for all possible error values.

The user requests interrogation of FM for another remote subscriber. Upon receipt of the operation (in a REGISTER message), SS answers with a RELEASE COMPLETE message with a successful FM-response information. Check that the MS provides the appropriate user indication (as described by the manufacturer). The SS transaction is released.

Maximum Duration of Test

2 minutes.

Expected Sequence

Test steps 1 to 10 are executed for k=1 to 6 with respectively the following error values:

1. Illegal interaction with incoming barring.

2. Unauthorised request.

3. Unknown remote party.

4. FM not subscribed.

5. FM not registered to remote party.

6. Conflicting situation with other supplementary services.

Step

Direction

Message

Comments

0

MS

The MS is in idle mode. MS is registered to FM with respect to a remote party B.

1

MS

The MS is made to initiate an interrogation of FM of remote subscriber other than B.

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

Check that the content of this message matches specific message contents.

7

SS -> MS

RELEASE COMPLETE

With an unsuccessful FM-result info with the following error value:

k=1: Illegal interaction with incoming barring (code 21)

k=2: Unauthorised request (code 22)

k=3: Unknown remote party (code 41)

k=4: FM not subscribed (code 42)

k=5: FM not registered to remote party (code 62)

k=6: Conflicting situation with other supplementary services (code 83)

See specific message contents.

8

SS -> MS

CHANNEL RELEASE

9

MS

It is checked that the MS, in a way described by the manufacturer, displays the error after step 7

15

MS

The MS is made to initiate an interrogation of FM of remote party B.

16

MS -> SS

CHANNEL REQUEST

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

17

SS -> MS

IMMEDIATE ASSIGNMENT

18

MS -> SS

CM SERVICE REQUEST

Cause: "supplementary service activation"

19

SS -> MS

CM SERVICE ACCEPT

20

MS -> SS

REGISTER

Check that the content of this message matches specific message contents.

21

SS -> MS

RELEASE COMPLETE

With a successful FM-result. See specific message contents.

22

SS -> MS

CHANNEL RELEASE

23

MS

Check that the MS, in a way described by the manufacturer, displays the positive result after step 21

Specific message contents:

REGISTER

Information Element

value/remark

Supplementary service protocol discriminator

Supplementary service (call independent)

Transaction identifier

‘1011’B

Message type

As 3GPP TS 24.080

Facility 1C

See below

SS version 7F

As 3GPP TS 24.080

For steps 6 and 20, Facility Information Element with Invoke = ProcessUnstructuredSS-Request component type as defined in 3GPP TS 24.080 subclause 3.6.1 table 3.3.

Contents

Value/remark

Facility IE identifier

As 3GPP TS 24.080

Length of FIE contents

depending on the length of ussd-string

Component type tag

CS/C/tag=1

Component length

depending on the length of ussd-string

InvokeID tag

From 3GPP TS 24.080

Invoke ID length

1

Invoke ID

Arbitrary (1 octet)

Operation Code tag

From 3GPP TS 24.080

Operation Code length

1

Operation Code

ProcessUnstructuredSS-Request

Ussd-dataCodingScheme

1 octet long. Alphabet indicator set to "default alphabet". Language indicator set to "undefined"

Ussd-string

For step 6: #21445896**#

For step 20: #21431245688**#

RELEASE COMPLETE

Information Element

value/remark

Supplementary service protocol discriminator

Supplementary service (call independent)

Transaction identifier

the transaction value is the same as the REGISTER transaction value but the transaction flag is different

Message type

As 3GPP TS 24.080

Cause

Omitted.

Facility Information Element

See below

SS version indicator

As specified in 3GPP TS 24.080

For steps 7 and 21, Facility Information Element with Return result = ProcessUnstructuredSS-Request return result component type as defined in 3GPP TS 24.080 subclause 3.6.1 table 3.6.

Contents

Value/remark

Facility IE identifier

As 3GPP TS 24.080

Length of FIE contents

depending on the length of ussd-string

Component type tag

Return result

Component length

depending on the length of ussd-string

InvokeID tag

From 3GPP TS 24.080

Invoke ID length

1

Invoke ID

The same as the invoke of the ProcessUnstructuredSS-Request

Ussd-dataCodingScheme

1 octet long. Alphabet indicator set to "default alphabet". Language indicator set to "undefined"

Ussd-string

For step 7: value of the error code

For steps 21: 03 31245688

31.15.3 Follow Me (FM) / Erasure

31.15.3.1 Conformance requirement

A previous FM registration can be erased in either of the following ways:

a) The initiating subscriber can specifically erase her previous registration with an appropriate control procedure.

b) In case the remote party corresponds to a subscriber the remote party can erase any previous registration with an appropriate control procedure.

c) The FM service supervisor can erase any previous registration to any remote party with an appropriate control procedure (forced erasure).

The subscriber who initiates the FM erase request shall be informed of the outcome of the request by the network.

As an operator’s option additional information (such as passwords) for erasure may be required from the subscriber. The registration procedure shall transport this information from the subscriber to the network of the remote party. This information shall be coded as a USSD string with a length not exceeding 30 characters.

MS shall behave as indicated in the Information flow as indicated in 3GPP TS 23.094, figure 4.1.

All the messages between MS and the mobile network and internal to the mobile network, which are used for control of Follow Me, are USSD Phase 2 messages.

References

3GPP TS 22.094 subclause 6.4.

3GPP TS 23.094 subclauses 4.1, 4.2 and 4.4.

3GPP TS 24.090 subclause 6.1.

31.15.3.2 Test purpose

1. To check that the MS, acting as an initiating subscriber or as a remote party, correctly requests a supplementary service transaction for erasure of FM in CHANNEL REQUEST message and in the subsequent CM SERVICE REQUEST.

2. To check that the MS as initiating subscriber or remote party sends a REGISTER message containing the FM-request control message for erasure.

3. To check that the MS, acting as a supervisor, correctly requests a supplementary service transaction for erasure of FM in CHANNEL REQUEST message and in the subsequent CM SERVICE REQUEST

4. To check that the MS as supervisor sends a REGISTER message containing the FM-request control message for forced-erasure.

5. To check that upon receipt of the result or the error of the operation (in a RELEASE COMPLETE message), the MS provides the appropriate user indication (as described by the manufacturer).

31.15.3.3 Method of test

Initial conditions

System Simulator:

1 cell, default parameters.

Mobile Station:

The MS is in MM-state "idle, updated" with valid TMSI and CKSN. The MS is registered to FM with respect to a remote party B.

Specific PICS Statements

PIXIT Statements

– Way to activate the erasure of FM.

– Description of display of the FM answers from the network.

Foreseen final state of the MS

The MS is in MM-state "idle, updated" with valid TMSI.

Test procedure

MS is registered to FM.

By means of appropriate MMI functions, the user requests erasure of FM for a remote number. Upon receipt of the REGISTER message, SS answers with the RELEASE COMPLETE message with an unsuccessful FM-result information. Check that the MS provides the appropriate user indication (as described by the manufacturer). Then SS transaction is released. This procedure is executed for all possible error values.

The user requests erasure of FM for another remote subscriber. Upon receipt of the operation (in a REGISTER message), SS answers with a RELEASE COMPLETE message with a successful FM-response information. Check that the MS provides the appropriate user indication (as described by the manufacturer). The SS transaction is released.

By means of appropriate MMI functions, the user requests forced-erasure of FM for a remote number. Upon receipt of the REGISTER message, SS answers with the RELEASE COMPLETE message with an unsuccessful FM-result information. Check that the MS provides the appropriate user indication (which is to be described by the manufacturer). Then SS transaction is released. This procedure is executed for all possible error values.

The user requests forced-erasure of FM for another remote subscriber. Upon receipt of the operation (in a REGISTER message), SS answers with a RELEASE COMPLETE message with a successful FM-response information. Check that the MS provides the appropriate user indication (as described by the manufacturer). The SS transaction is released.

Maximum Duration of Test

2 minutes.

Expected Sequence

Test steps 1 to 10 and 25 to 34 are executed for k=1 to 10 with respectively the following error values:

1. Illegal interaction with incoming barring.

2. Unauthorised request.

3. Unknown remote party.

4. FM not subscribed.

5. FM not registered to remote party.

6. Remote party not registered to this MSISDN.

7. Unauthorised changes to remote party.

8. Illegal interaction with call barring.

9. Insufficient information.

10. Inconsistent with registration.

Step

Direction

Message

Comments

0

MS

The MS is in idle mode. MS is registered to FM with respect to a remote party B.

1

MS

The MS is made to initiate erasure of FM for a remote subscriber other than B.

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

Check that the content of this message matches specific message contents.

7

SS -> MS

RELEASE COMPLETE

With an unsuccessful FM-result info with the following error value:

k=1: Illegal interaction with incoming barring (code 21)

k=2: Unauthorised request (code 22)

k=3: Unknown remote party (code 41)

k=4: FM not subscribed (code 42)

k=5: FM not registered to remote party (code 62)

k=6: Remote party not registered to this MSISDN (code 63)

k=7: Unauthorised changes to remote party (code 64)

k=8: Illegal interaction with call barring (code 66)

k=9: Insufficient information (code 81)

k=10: Inconsistent with registration (code 84)

See specific message contents.

8

SS -> MS

CHANNEL RELEASE

9

MS

Check that the MS, in a way described by the manufacturer, displays the error after step 7

15

MS

The MS is made to initiate erasure of FM for remote subscriber B

16

MS -> SS

CHANNEL REQUEST

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

17

SS -> MS

IMMEDIATE ASSIGNMENT

18

MS -> SS

CM SERVICE REQUEST

Cause: "supplementary service activation"

19

SS -> MS

CM SERVICE ACCEPT

20

MS -> SS

REGISTER

Check that the content of this message matches specific message contents.

21

SS -> MS

RELEASE COMPLETE

With a successful FM-result. See specific message contents.

22

SS -> MS

CHANNEL RELEASE

23

MS

Check that the MS, in a way described by the manufacturer, displays the positive result after step 21

25

MS

The MS is made to initiate forced erasure

26

MS -> SS

CHANNEL REQUEST

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

27

SS -> MS

IMMEDIATE ASSIGNMENT

28

MS -> SS

CM SERVICE REQUEST

Cause: "supplementary service activation"

29

SS -> MS

CM SERVICE ACCEPT

30

MS -> SS

REGISTER

Check that the content of this message matches specific message contents.

31

SS -> MS

RELEASE COMPLETE

With an unsuccessful FM-result info with the following error value:

k=1: Illegal interaction with incoming barring (code 21)

k=2: Unauthorised request (code 22)

k=3: Unknown remote party (code 41)

k=4: FM not subscribed (code 42)

k=5: FM not registered to remote party (code 62)

k=6: Remote party not registered to this MSISDN (code 63)

k=7: Unauthorised changes to remote party (code 64)

k=8: Illegal interaction with call barring (code 66)

k=9: Insufficient information (code 81)

k=10: Inconsistent with registration (code 84)

See specific message contents.

32

SS -> MS

CHANNEL RELEASE

33

MS

Check that the MS, in a way described by the manufacturer, displays the negative result after step 31

40

MS

The MS is made to initiate forced erasure

41

MS -> SS

CHANNEL REQUEST

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

42

SS -> MS

IMMEDIATE ASSIGNMENT

43

MS -> SS

CM SERVICE REQUEST

Cause: "supplementary service activation"

44

SS -> MS

CM SERVICE ACCEPT

45

MS -> SS

REGISTER

Check that the content of this message matches specific message contents.

46

SS -> MS

RELEASE COMPLETE

With a successful FM-result. See specific message contents.

47

SS -> MS

CHANNEL RELEASE

48

MS

Check that the MS, in a way described by the manufacturer, displays the positive result after step 46

Specific message contents:

REGISTER

Information Element

value/remark

Supplementary service protocol discriminator

Supplementary service (call independent)

Transaction identifier

‘1011’B

Message type

As 3GPP TS 24.080

Facility 1C

See below

SS version 7F

As 3GPP TS 24.080

For steps 6, 20, 30 and 45, Facility Information Element with Invoke = ProcessUnstructuredSS-Request component type as defined in 3GPP TS 24.080 subclause 3.6.1 table 3.3.

Contents

Value/remark

Facility IE identifier

As 3GPP TS 24.080

Length of FIE contents

depending on the length of ussd-string

Component type tag

CS/C/tag=1

Component length

depending on the length of ussd-string

InvokeID tag

From 3GPP TS 24.080

Invoke ID length

1

Invoke ID

Arbitrary (1 octet)

Operation Code tag

From 3GPP TS 24.080

Operation Code length

1

Operation Code

ProcessUnstructuredSS-Request

Ussd-dataCodingScheme

1 octet long. Alphabet indicator set to "default alphabet". Language indicator set to "undefined"

Ussd-string

For step 6: ##214*45896***#

For step 20: ##214*31245688***#

For steps 30 and 45: ##214*45896*88*0436987*#

RELEASE COMPLETE

Information Element

Value/remark

Supplementary service protocol discriminator

Supplementary service (call independent)

Transaction identifier

the transaction value is the same as the REGISTER transaction value but the transaction flag is different

Message type

As 3GPP TS 24.080

Cause

Omitted.

Facility Information Element

See below

SS version indicator

As specified in 3GPP TS 24.080

For steps 7, 21, 31 and 46, Facility Information Element with Return result = ProcessUnstructuredSS-Request return result component type as defined in 3GPP TS 24.080 subclause 3.6.1 table 3.6.

Contents

Value/remark

Facility IE identifier

As 3GPP TS 24.080

Length of FIE contents

depending on the length of ussd-string

Component type tag

Return result

Component length

depending on the length of ussd-string

InvokeID tag

From 3GPP TS 24.080

Invoke ID length

1

Invoke ID

The same as the invoke of the ProcessUnstructuredSS-Request

Ussd-dataCodingScheme

1 octet long. Alphabet indicator set to "default alphabet". Language indicator set to "undefined"

Ussd-string

For steps 7 and 31: value of the error code

For steps 21 and 46: 02