15.4 Call forwarding

34.123-13GPPPart 1: Protocol conformance specificationRelease 15TSUser Equipment (UE) conformance specification

Tools: ARFCN - Frequency Conversion for 5G NR/LTE/UMTS/GSM

15.4.1 Call forwarding supplementary services, Registration accepted

15.4.1.1 Definition

15.4.1.2 Conformance requirements

A CFU registration request from a mobile user shall include the SS-Code of the forwarding service to be registered and possibly the BasicServiceCode the request applies to. If the BasicServiceCode is not included, the request applies to all basic services.

If the registration is successful, the CFU service will be registered and activated. The network will then send a return result indicating acceptance of the request including the ForwardedToNumber and possibly the BasicService (group) Code to which CFU is registered. If the request applied to a single elementary basic service group, the ForwardedToNumber may be accompanied by a ForwardedToSubAddress. In other cases, the result shall not contain a ForwardedToSubAddress. The result may also contain an SS‑Status parameter. If the MS does not send an SS Version Indicator in the invocation request then the network shall send an SS‑Status in the result. If the MS does send an SS Version Indicator in the invocation request then the inclusion of SS‑Status in the result is optional. If the SS‑Status is included the network shall set it to reflect the state of the service. The MS shall ignore the contents of the SS‑Status parameter if one is received. See figure 1.4.

Note that the use of SS‑Status is to provide backwards compatibility with phase 1.

If the system cannot accept a registration request, a corresponding error indication is returned to the served mobile subscriber that CFU registration was not successful. Error values are specified in 3GPP TS 24.080.

MS Network

————————————————————————————————————————>

Facility (Invoke = RegisterSS (CFU, BasicServiceCode, ForwardedToNumber, ForwardedToSubAddress, LongFTNsupported))

RELEASE COMPLETE

<————————————————————————————————————————

Facility (Return result = RegisterSS (BasicServiceCode, SS-Status, ForwardedToNumber, ForwardedToSubAddress))

RELEASE COMPLETE

<- – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – –

Facility (Return error (Error))

RELEASE COMPLETE

<- – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – –

Facility (Reject (Invoke_problem))

NOTE: If BasicServiceCode is not included it applies to all basic services. The ForwardedToNumber may be accompanied by a ForwardedToSubAddress. The SS-Status may not be included in all cases, see text.

Figure 1.4: Registration of call forwarding unconditional

When registering call forwarding, the SS‑Code may indicate the code for "all forwarding SS". In this case, if the subscriber has CFU provisioned, the return result shall contain the information for CFU. If the subscriber does not have CFU provisioned, the return result shall contain the information for any conditional call forwarding services which the subscriber has provisioned. The condition for the presence of longFTNsupport is specified in 3GPP TS 23.082 [15].

…

A CFNRy registration request from a mobile user shall include the SS‑Code of the forwarding service to be registered and possibly the applicable BasicServiceCode and NoReplyConditionTime. If the BasicServiceCode is not included, the request applies to all basic services. If the NoReplyConditionTime is not included, the previous value set by the mobile user or network operator applies.

If the registration is successful, the CFNRy service will be registered and activated. The network will then send a return result indicating acceptance of the request, including the ForwardedToNumber and possibly the applicable BasicService (group) code and NoReplyConditionTime. If the request applied to a single elementary basic service group, the ForwardedToNumber may be accompanied by a ForwardedToSubAddress. In other cases the result shall not contain a ForwardedToSubAddress. The result may also contain an SS‑Status parameter. If the MS does not send an SS Version Indicator in the invocation request then the network shall send an SS‑Status in the result. If the MS does send an SS Version Indicator in the invocation request then the inclusion of SS‑Status in the result is optional. If the SS‑Status is included the network shall set it to reflect the state of the service. The MS shall ignore the contents of the SS‑Status parameter if one is received. See figure 3.5.

Reference

3GPP TS 24.082 clauses 1.2.1 and 3.2.1

15.4.1.3 Test purpose

1) To check that the UE correctly requests a supplementary service transaction for registration of call forwarding in the CM SERVICE REQUEST.

2) To check that the UE sends a REGISTER message containing the invoke of the RegisterSS operation with the expected parameter values for registration of call forwarding.

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

These checks are done for:

a) CFNRy, for basic service group speech.

b) CFU, for basic service group speech.

15.4.1.4 Method of test

Initial Conditions

– System simulator:

– 1 cell, default parameters.

– User Equipment:

– the UE shall be in MM-state "Idle, updated";

Related ICS/IXIT Statements

Support of FDD Yes/No.

Support of CS speech Yes/No.

Description of the user’s commands and of display of the answers from the network for call forwarding

Support of Call Forwarding on No Reply Yes/No.

Support of Call Forwarding Unconditional Yes/No.Test procedure

By means of appropriate user actions, the user requests registration of CFNRy for Speech, to a number arbitrarily selected and with a no reply time value 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 RRC connection is released.

Then again, by means of appropriate user actions, the user requests registration of CFU for Speech, to a number arbitrarily selected.

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

Expected sequence

Step	Direction		Message	Comment
Step	UE	SS	Message	Comment
				If UE supports CFNRy, then step 1 to 10 are executed
1				The UE is made to initiate a registration of call forwarding service for CFNRy (Speech) The SS verifies that the IE “Establishment cause” in the received RRC CONNECTION REQUEST message is set to “Originating High Priority Signalling”.
2	->		CM SERVICE REQUEST	CM service type: "Supplementary service activation"
3	<-		AUTHENTICATION REQUEST
4	->		AUTHENTICATION RESPONSE
5	<-		SECURITY MODE COMMAND
6	->		SECURITY MODE COMPLETE
7	->		REGISTER
8	<-		RELEASE COMPLETE	RegisterSS operation Return result
9	SS			The SS releases the RRC connection.
10	UE			Provide user indication
				If UE supports CFU, then step 11 to 20 are executed
11	UE			The UE is made to initiate a registration of call forwarding service for CFU (Speech). “Establishment cause” in the received RRC CONNECTION REQUEST message is set to “Originating High Priority Signalling”.
12	->		CM SERVICE REQUEST	CM service type: "supplementary service activation"
13	<-		AUTHENTICATION REQUEST	Steps 13 and 14 are not execuded if steps 3 and 4 were executed.
14	->		AUTHENTICATION RESPONSE
15	<-		SECURITY MODE COMMAND
16	->		SECURITY MODE COMPLETE
17	->		REGISTER
18	<-		RELEASE COMPLETE	RegisterSS operation Return result
19	SS			The SS releases the RRC connection.
20	UE			Provide user indication

Specific Message Contents

Information Element	Value/remark	Condition
Facility
Invoke component
Operation Code	registerSS
Parameters
SS-Code
ss-Code	00101010 CFNRy
BasicServiceCode	TeleService AllSpeechTransmissionServices (TS10) or Telephony (TS 11), no Bearerservice present
ForwardedToNumber	Any number
NoReplyConditionTime	As selected

RELEASE COMPLETE with Return result component with operation code (Step 8)

Information Element	Value/remark	Condition
Invoke ID	the same Invoke ID as in the REGISTER in Step 7
Operation code	registerSS
BasicServiceCode	TeleService AllSpeechTransmissionServices (TS10) or Telephony (TS 11), no Bearerservice present
ForwardedToNumber	Same number as in step 7
NoReplyConditionTime	Same as in step 7
SS-Status	‘0110’Provisioned and Registered

Information Element	Value/remark	Condition
Facility
Invoke component
Operation Code	registerSS
Parameters
SS-Code
ss-Code	00100001 CFU
BasicServiceCode	TeleService AllSpeechTransmissionServices (TS10) or Telephony (TS 11), no Bearerservice present
ForwardedToNumber	Any number

RELEASE COMPLETE with Return result component with operation code (Step 18)

Information Element	Value/remark	Condition
Invoke ID	the same Invoke ID as in the REGISTER in Step 17
Operation code	registerSS
BasicServiceCode	TeleService AllSpeechTransmissionServices (TS10) or Telephony (TS 11), no Bearerservice present
ForwardedToNumber	Same number as in step 17
SS-Status	‘0110’Provisioned and Registered

15.4.1.5 Test requirements

In Step 2, the UE sends the CM SERVICE REQUEST message with the service type: "Supplementary service activation".

In Step 7, the UE sends the REGISTER message with correct parameters for registration of CFNRy.

In Step 10, the UE provides the appropriate user indication.

In Step 12, the UE sends the CM SERVICE REQUEST message with the service type: "Supplementary service activation".

In Step 17, the UE sends the REGISTER message with the correct parameters for registration of CFU.

In Step 20, the UE provides the appropriate user indication.

15.4.2 Call forwarding supplementary services, Registration rejected

15.4.2.1 Definition

15.4.2.2 Conformance requirements

Note that the use of SS‑Status is to provide backwards compatibility with phase 1.

MS Network

————————————————————————————————————————>

Facility (Invoke = RegisterSS (CFU, BasicServiceCode, ForwardedToNumber, ForwardedToSubAddress, LongFTNsupported))

RELEASE COMPLETE

<————————————————————————————————————————

Facility (Return result = RegisterSS (BasicServiceCode, SS-Status, ForwardedToNumber, ForwardedToSubAddress))

RELEASE COMPLETE

<- – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – –

Facility (Return error (Error))

RELEASE COMPLETE

<- – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – –

Facility (Reject (Invoke_problem))

Figure 1.4: Registration of call forwarding unconditional

…

Reference

3GPP TS 24.082 clauses 1.2.1 and 3.2.1

15.4.2.3 Test purpose

1) To check that the UE correctly requests the establishment of a parallel MM transaction for supplementary service transaction for registration of call forwarding, sending a CM SERVICE REQUEST.

2) To check that the UE sends a REGISTER message containing the invoke of the RegisterSS operation with the expected parameter values for registration of call forwarding.

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 UE provides the appropriate user indication (as described by the Manufacturer).

These checks are done for:

a) CFNRy, for basic service group speech.

b) CFU, for basic service group speech.

15.4.2.4 Method of test

Initial Conditions

– System simulator:

– 1 cell, default parameters.

– User Equipment:

– the UE shall be in CC state U10.

Related ICS/IXIT Statements

Support of FDD Yes/No.

Support of CS speech Yes/No.

Description of the user’s commands and of display of the answers from the network for call forwarding
Support of Call Forwarding on No Reply Yes/No
Support of Call Forwarding Unconditional Yes/No

Test procedure

By means of appropriate user actions, the user requests registration of CFNRy for Speech, to a number arbitrarily selected and with a no reply time value 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 a Return_error(error: BearerService not provisioned) of the RegisterSS operation.

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

Then again, by means of appropriate user actions, the user requests registration of CFU for Speech, to a number arbitrarily selected.

Upon receipt of the REGISTER message, the system simulator answers with the RELEASE COMPLETE message with the Facility information element containing a reject(invoke_problem: resource limitation) of the RegisterSS operation.

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

Expected sequence

Step	Direction		Message	Comment
Step	UE	SS	Message	Comment
				If UE supports CFNRy, then step 1 to 8 are executed
1				The UE is made to initiate a registration of call forwarding service for CFNRy (Speech)
2	->		CM SERVICE REQUEST	CM service type: "Supplementary service activation"
3	<-		CM SERVICE ACCEPT
4	->		REGISTER
5	<-		RELEASE COMPLETE	RegisterSS operation Return error component with BearerService not provisioned
6	UE			Provide user indication
7	<-		STATUS ENQUIRY
8	->		STATUS	CC state U10
				If UE supports CFU, then step 9 to 16 are executed
9	UE			The UE is made to initiate a registration of call forwarding service for CFU (Speech)
10	->		CM SERVICE REQUEST	CM service type: "supplementary service activation"
11	<-		CM SERVICE ACCEPT
12	->		REGISTER
13	<-		RELEASE COMPLETE	RegisterSS operation Reject component with cause “resource limitation”
14	UE			Provide user indication
15	<-		STATUS ENQUIRY
16	->		STATUS	CC state U10

Specific Message Contents

Information Element	Value/remark	Condition
Facility
Invoke component
Operation Code	registerSS
Parameters
SS-Code
ss-Code	00101010 CFNRy
BasicServiceCode	TeleService AllSpeechTransmissionServices (TS10) or Telephony (TS 11), no Bearerservice present
ForwardedToNumber	Any number
NoReplyConditionTime	As selected

RELEASE COMPLETE with Return error component with error code (Step 5)

Information Element	Value/remark	Condition
Invoke ID	the same Invoke ID as in the REGISTER in Step 4
Error Code	bearerServiceNotProvisioned

STATUS (Step 8)

Information Element	Value/remark	Condition
Cause	30 “Response to STATUS ENQUIRY”
Call state	U10- active

Information Element	Value/remark	Condition
Facility
Invoke component
Operation Code	registerSS
Parameters
SS-Code
ss-Code	00100001 CFU
BasicServiceCode	TeleService AllSpeechTransmissionServices (TS10) or Telephony (TS 11), no Bearerservice present
ForwardedToNumber	Any number

RELEASE COMPLETE with Reject component with problem code (Step 13)

Information Element	Value/remark	Condition
Invoke ID	the same Invoke ID as in the REGISTER in Step 12
Problem Code	Resource Limitation

STATUS (Step 16)

Information Element	Value/remark	Condition
Cause	30 “Response to STATUS ENQUIRY”
Call state	U10- active

15.4.2.5 Test requirements

In Step 2, the UE sends the CM SERVICE REQUEST message with the service type: "Supplementary service activation".

In Step 4, the UE sends the REGISTER message with correct parameters for registration of CFNRy.

In Step 6, the UE provides the appropriate user indication.

In Step 8, the UE sends the STATUS message with the correct parameters.

In Step 10, the UE sends the CM SERVICE REQUEST message with the service type: "Supplementary service activation".

In Step 12, the UE sends the REGISTER message with the correct parameters for registration of CFU.

In Step 14, the UE provides the appropriate user indication.

In Step 16, the UE sends the STATUS message with the correct parameters.

15.4.3 Call forwarding supplementary services, Erasure accepted

15.4.3.1 Definition

15.4.3.2 Conformance requirements

For erasure of any type of call forwarding, the UE shall transmit successively:

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

2) and then the REGISTER message containing a facility that includes an invoke of the EraseSS operation with the expected parameter values according to the user request (MMI action);

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

Reference

3GPP TS 24.082 clauses 2.3.1 and 4.3.1

15.4.3.3 Test purpose

1) To check that the UE correctly requests a supplementary service transaction for erasure of call forwarding in the CM SERVICE REQUEST.

2) To check that the UE sends a REGISTER message containing the invoke of the EraseSS operation with the expected parameter values for erasure of call forwarding.

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

These checks are done for:

a) CFB, for all basic service groups.

b) CFNRc, for all basic service groups.

15.4.3.4 Method of test

Initial Conditions

– System simulator:

– 1 cell, default parameters.

– User Equipment:

– the UE shall be in MM-state "Idle, updated";

Related ICS/IXIT Statements

Support of FDD Yes/No.

Support of CS speech Yes/No.

Description of the user’s commands and of display of the answers from the network for call forwarding

Support of Call Forwarding on Mobile Subscriber Busy Yes/No.

Support of Call Forwarding on Mobile Subscriber Not Reachable Yes/No.

Test procedure

By means of appropriate user actions, the user requests erasure of CFB for all basic service groups.

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

The SS transaction is released and the RRC connection is released.

Then again, by means of appropriate user actions, the user requests erasure of CFNRc for all basic service groups.

Upon receipt of the REGISTER message, the system simulator answers with the RELEASE COMPLETE message with the Facility information element containing the return result of the EraseSS operation

Expected sequence

Step	Direction		Message	Comment
Step	UE	SS	Message	Comment
				If UE supports CFB, then step 1 to 10 are executed. The SS verifies that the IE “Establishment cause” in the received RRC CONNECTION REQUEST message is set to “Originating High Priority Signalling”.
1				The UE is made to initiate erasure of call forwarding for CFB (all basic services)
2	->		CM SERVICE REQUEST	CM service type: "Supplementary service activation"
3	<-		AUTHENTICATION REQUEST
4	->		AUTHENTICATION RESPONSE
5	<-		SECURITY MODE COMMAND
6	->		SECURITY MODE COMPLETE
7	->		REGISTER
8	<-		RELEASE COMPLETE	EraseSS operation Return result
9			void
10	SS			The SS releases the RRC connection.
10a	UE			Provide user indication
				If UE supports CFNRc, then step 11 to 20 are executed
11	UE			The UE is made to initiate a erasure of call forwarding service for CFNRc (all basic services). “Establishment cause” in the received RRC CONNECTION REQUEST message is set to “Originating High Priority Signalling”.
12	->		CM SERVICE REQUEST	CM service type: "supplementary service activation"
13	<-		AUTHENTICATION REQUEST	Steps 13 and 14 are not executed if steps 3 and 4 were executed.
14	->		AUTHENTICATION RESPONSE
15	<-		SECURITY MODE COMMAND
16	->		SECURITY MODE COMPLETE
17	->		REGISTER
18	<-		RELEASE COMPLETE	EraseSS operation Return result
19	SS			The SS releases the RRC connection.
20	UE			Provide user indication

Specific Message Contents

Information Element	Value/remark	Condition
Facility
Invoke component
Operation Code	eraseSS
Parameters
SS-Code
ss-Code	00101001 CFB
BasicServiceCode	no bearer service present, no teleservice present

RELEASE COMPLETE with Return result component with operation code (Step 8)

Information Element	Value/remark	Condition
Invoke ID	the same Invoke ID as in the REGISTER in Step 7
Operation code	eraseSS
BasicServiceCode	no bearer service present, no teleservice present
SS-Status	‘0100’Provisioned

Information Element	Value/remark	Condition
Facility
Invoke component
Operation Code	eraseSS
Parameters
SS-Code
ss-Code	00101011 CFNRc
BasicServiceCode	no bearer service present, no teleservice present

RELEASE COMPLETE with Return result component with operation code (Step 18)

Information Element	Value/remark	Condition
Invoke ID	the same Invoke ID as in the REGISTER in Step 17
Operation code	eraseSS
BasicServiceCode	no bearer service present, no teleservice present
SS-Status	‘0100’Provisioned

15.4.3.5 Test requirements

In Step 2, the UE sends the CM SERVICE REQUEST message with the service type: "Supplementary service activation".

In Step 7, the UE sends the REGISTER message with correct parameters for erasure of CFB.

In Step 10a, the UE provides the appropriate user indication.

In Step 12, the UE sends the CM SERVICE REQUEST message with the service type: "Supplementary service activation".

In Step 17, the UE sends the REGISTER message with the correct parameters for erasure of CFNRc.

In Step 20, the UE provides the appropriate user indication.

15.4.4 Call forwarding supplementary services, Erasure rejected

15.4.4.1 Definition

15.4.4.2 Conformance requirements

For erasure of any type of call forwarding, the UE shall transmit successively:

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

2) and then the REGISTER message containing a facility that includes an invoke of the EraseSS operation with the expected parameter values according to the user request (MMI action);

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

Reference

3GPP TS 24.082 clauses 2.3.1 and 4.3.1

15.4.4.3 Test purpose

1) To check that the UE correctly requests the establishment of a parallel MM transaction for supplementary service transaction of erasure of call forwarding, sending a CM SERVICE REQUEST.

2) To check that the UE sends a REGISTER message containing the invoke of the EraseSS operation with the expected parameter values for erasure of call forwarding.

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 UE provides the appropriate user indication (as described by the Manufacturer).

These checks are done for:

a) CFB, for speech.

b) CFNRc, for all basic service groups.

15.4.4.4 Method of test

Initial Conditions

– System simulator:

– 1 cell, default parameters.

– User Equipment:

– the UE shall be in CC state U10

Related ICS/IXIT Statements

Support of FDD Yes/No.

Support of CS speech Yes/No.

Description of the user’s commands and of display of the answers from the network for call forwarding
Support of Call Forwarding on Mobile Subscriber Busy Yes/No
Support of Call Forwarding on Mobile Subscriber Not Reachable Yes/No

Test procedure

By means of appropriate user actions, the user requests erasure of CFB for speech.

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: TeleService not provisioned) of the EraseSS operation.

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

Then again, by means of appropriate user actions, the user requests erasure of CFNRc for all basic service groups..

Upon receipt of the REGISTER message, the system simulator answers with the RELEASE COMPLETE message with the Facility information element containing a Reject(invoke_problem: resource limitation) of the EraseSS operation.

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

Expected sequence

Step	Direction		Message	Comment
Step	UE	SS	Message	Comment
				If UE supports CFB, then steps 1 to 8 are executed
1				The UE is made to initiate erasure of call forwarding for CFB (speech)
2	->		CM SERVICE REQUEST	CM service type: "Supplementary service activation"
3	<-		CM SERVICE ACCEPT
4	->		REGISTER
5	<-		RELEASE COMPLETE	EraseSS operation Return_error
6	UE			Provide user indication
7	<-		STATUS ENQUIRY
8	->		STATUS	CC state U10
				If UE supports CFNRc, then steps 9 to 16 are executed
9	UE			The UE is made to initiate erasure of call forwarding service for CFNRc (all basic services)
10	->		CM SERVICE REQUEST	CM service type: "supplementary service activation"
11	<-		CM SERVICE ACCEPT
12	->		REGISTER
13	<-		RELEASE COMPLETE	EraseSS operation Reject
14	UE			Provide user indication
15	<-		STATUS ENQUIRY
16	->		STATUS	CC state U10

Specific Message Contents

Information Element	Value/remark	Condition
Facility
Invoke component
Operation Code	eraseSS
Parameters
SS-Code
ss-Code	00101001 CFB
BasicServiceCode	Tele Service AllSpeechTransmissionServices (TS10) or Telephony (TS 11), no Bearerservice present.

RELEASE COMPLETE with Return error component with operation code (Step 5)

Information Element	Value/remark	Condition
Invoke ID	the same Invoke ID as in the REGISTER in Step 4
Error Code	teleServiceNotProvisioned

STATUS (Step 8)

Information Element	Value/remark	Condition
Cause	30 “Response to STATUS ENQUIRY”
Call state	U10- active

Information Element	Value/remark	Condition
Facility
Invoke component
Operation Code	eraseSS
Parameters
SS-Code
ss-Code	00101011 CFNRc
BasicServiceCode	no bearer service present, no teleservice present

RELEASE COMPLETE with Reject component with operation code (Step 13)

Information Element	Value/remark	Condition
Invoke ID	the same Invoke ID as in the REGISTER in Step 12
Problem Code	Resource Limitation

STATUS (Step 16)

Information Element	Value/remark	Condition
Cause	30 “Response to STATUS ENQUIRY”
Call state	U10- active

15.4.4.5 Test requirements

In Step 2, the UE sends the CM SERVICE REQUEST message with the service type: "Supplementary service activation".

In Step 4, the UE sends the REGISTER message with correct parameters for erasure of CFB.

In Step 6, the UE provides the appropriate user indication.

In Step 8, the UE sends the STATUS message with the correct parameters.

In Step 10, the UE sends the CM SERVICE REQUEST message with the service type: "Supplementary service activation".

In Step 12, the UE sends the REGISTER message with the correct parameters for erasure of CFNRc.

In Step 14, the UE provides the appropriate user indication.

In Step 16, the UE sends the STATUS message with the correct parameters.

15.4.5 Call forwarding supplementary services, Activation

15.4.5.1 Definition

15.4.5.2 Conformance requirements

For activation of any type of call forwarding with any parameters, the MS shall transmit successively

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

2) 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);

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

Reference

3GPP TS 24.082 clauses 1.4 and 2.4

15.4.5.3 Test purpose

1) To check that the UE correctly requests a supplementary service transaction for activation of call forwarding in the CM SERVICE REQUEST.

2) To check that the UE sends a REGISTER message containing the invocation of the ActivateSS operation with the expected parameter values for activation of call forwarding.

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

These checks are done for:

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

b) CFU, for all basic service groups.

15.4.5.4 Method of test

Initial Conditions

– System simulator:

– 1 cell, default parameters.

– User Equipment:

– the UE shall be in MM-state "Idle, updated";

Related ICS/IXIT Statements

Support of FDD Yes/No.

Support of CS speech Yes/No.

Description of the user’s commands and of display of the answers from the network for call forwarding

Support of Call Forwarding on Mobile Subscriber Busy Yes/No.

Support of Call Forwarding Unconditional Yes/No.

Test procedure

By means of appropriate user actions, the user requests activation of CFB for 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 the return result of the ActivateSS operation.

The SS transaction and the RRC connection are released.

Then again, by means of appropriate user actions, the user requests activation of CFU for all basic service groups.

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

Expected sequence

Step	Direction		Message	Comment
Step	UE	SS	Message	Comment
				If UE supports CFB, then step 1 to 10 are executed.
1				The UE is made to initiate an activation of call forwarding service for CFB (all synchronous services). The SS verifies that the IE “Establishment cause” in the received RRC CONNECTION REQUEST message is set to “Originating High Priority Signalling”.
2	->		CM SERVICE REQUEST	CM service type: "Supplementary service activation"
3	<-		AUTHENTICATION REQUEST
4	->		AUTHENTICATION RESPONSE
5	<-		SECURITY MODE COMMAND
6	->		SECURITY MODE COMPLETE
7	->		REGISTER
8	<-		RELEASE COMPLETE	ActivateSS operation Return result
9	SS			The SS releases the RRC connection.
10	UE			Provide user indication
				If UE supports CFU, then step 11 to 20 are executed
11	UE			The UE is made to initiate an activation of call forwarding service for CFU (all basic service groups). The SS verifies that the IE “Establishment cause” in the received RRC CONNECTION REQUEST message is set to “Originating High Priority Signalling”.
12	->		CM SERVICE REQUEST	CM service type: "supplementary service activation"
13	<-		AUTHENTICATION REQUEST	Steps 13 and 14 are not executed if steps 3 and 4 were executed.
14	->		AUTHENTICATION RESPONSE
15	<-		SECURITY MODE COMMAND
16	->		SECURITY MODE COMPLETE
17	->		REGISTER
18	<-		RELEASE COMPLETE	ActivateSS operation Return result
19	SS			The SS releases the RRC connection.
20	UE			Provide user indication

Specific Message Contents

Information Element	Value/remark	Condition
Facility
Invoke component
Operation Code	activateSS
Parameters
SS-Code
ss-Code	00101001 CFB
BasicServiceCode	Bearer Service (all synchronous services), no teleservice present.

RELEASE COMPLETE with Return result component with operation code (Step 8)

Information Element	Value/remark	Condition
Invoke ID	the same Invoke ID as in the REGISTER in Step 7
Operation code	activateSS
SS-Status	‘0111’Provisioned, Registered and Activated

Information Element	Value/remark	Condition
Facility
Invoke component
Operation Code	activateSS
Parameters
SS-Code
ss-Code	00100001 CFU
BasicServiceCode	no bearer service present, no teleservice present

RELEASE COMPLETE with Return result component with operation code (Step 18)

Information Element	Value/remark	Condition
Invoke ID	the same Invoke ID as in the REGISTER in Step 17
Operation code	activateSS
SS-Status	‘0111’Provisioned, Registered and Activated

15.4.5.5 Test requirements

In Step 2, the UE sends the CM SERVICE REQUEST message with the service type: "Supplementary service activation".

In Step 7, the UE sends the REGISTER message with correct parameters for activation of CFB.

In Step 10, the UE provides the appropriate user indication.

In Step 12, the UE sends the CM SERVICE REQUEST message with the service type: "Supplementary service activation".

In Step 17, the UE sends the REGISTER message with the correct parameters for activation of CFU.

In Step 20, the UE provides the appropriate user indication.

15.4.6 Call forwarding supplementary services, Deactivation

15.4.6.1 Definition

15.4.6.2 Conformance requirements

For deactivation of any type of call forwarding with any parameters, the MS shall transmit successively:

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

2) 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);

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

Reference

3GPP TS 24.082 clauses 2.5 and 4.5

15.4.6.3 Test purpose

1) To check that the UE correctly requests a supplementary service transaction for deactivation of call forwarding in the CM SERVICE REQUEST.

2) To check that the UE sends a REGISTER message containing the invoke of the DeactivateSS operation with the expected parameter values for deactivation of call forwarding.

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

These checks are done for:

a) CFB, for basic service group speech.

b) CFNRc, for basic service group speech.

15.4.6.4 Method of test

Initial Conditions

– System simulator:

– 1 cell, default parameters.

– User Equipment:

– the UE shall be in MM-state "Idle, updated";

Related ICS/IXIT Statements

Support of FDD Yes/No.

Support of CS speech Yes/No.

Description of the user’s commands and of display of the answers from the network for call forwarding

Support of Call Forwarding on Mobile Subscriber Busy Yes/No.

Support of Call Forwarding on Mobile Subscriber Not Reachable Yes/No.

Test procedure

By means of appropriate user actions, the user requests deactivation of CFB for speech.

The SS transaction and the RRC connection are released.

Then again, by means of appropriate user actions, the user requests deactivation of CFNRc for speech.

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

Expected sequence

Step	Direction		Message	Comment
Step	UE	SS	Message	Comment
				If UE supports CFB, then step 1 to 10 are executed.
1				The UE is made to initiate a deactivation of call forwarding service for CFB (speech). The SS verifies that the IE “Establishment cause” in the received RRC CONNECTION REQUEST message is set to “Originating High Priority Signalling”.
2	->		CM SERVICE REQUEST	CM service type: "Supplementary service activation"
3	<-		AUTHENTICATION REQUEST
4	->		AUTHENTICATION RESPONSE
5	<-		SECURITY MODE COMMAND
6	->		SECURITY MODE COMPLETE
7	->		REGISTER
8	<-		RELEASE COMPLETE	DeactivateSS operation Return result
9	SS			The SS releases the RRC connection.
10	UE			Provide user indication
				If UE supports CFNRc, then step 11 to 20 are executed
11	UE			The UE is made to initiate a deactivation of call forwarding service for CFNRc (speech). The SS verifies that the IE “Establishment cause” in the received RRC CONNECTION REQUEST message is set to “Originating High Priority Signalling”.
12	->		CM SERVICE REQUEST	CM service type: "supplementary service activation"
13	<-		AUTHENTICATION REQUEST	Steps 13 and 14 are not executed if steps 3 and 4 were executed.
14	->		AUTHENTICATION RESPONSE
15	<-		SECURITY MODE COMMAND
16	->		SECURITY MODE COMPLETE
17	->		REGISTER
18	<-		RELEASE COMPLETE	DeactivateSS operation Return result
19	SS			The SS releases the RRC connection.
20	UE			Provide user indication

Specific Message Contents

Information Element	Value/remark	Condition
Facility
Invoke component
Operation Code	deactivateSS
Parameters
SS-Code
ss-Code	00101001 CFB
BasicServiceCode	no bearer service, teleservice (All Speech Transmission Services) (TS10) or Telephony(TS11).

RELEASE COMPLETE with Return result component with operation code (Step 8)

Information Element	Value/remark	Condition
Invoke ID	the same Invoke ID as in the REGISTER in Step 7
Operation code	deactivateSS
SS-Status	‘0110’Provisioned and Registered

Information Element	Value/remark	Condition
Facility
Invoke component
Operation Code	deactivateSS
Parameters
SS-Code
ss-Code	00101011 CFNRc
BasicServiceCode	no bearer service, teleservice (All Speech Transmission Services) (TS10) or Telephony(TS11).

RELEASE COMPLETE with Return result component with operation code (Step 18)

Information Element	Value/remark	Condition
Invoke ID	the same Invoke ID as in the REGISTER in Step 17
Operation code	deactivateSS
SS-Status	‘0110’Provisioned and Registered

15.4.6.5 Test requirements

In Step 2, the UE sends the CM SERVICE REQUEST message with the service type: "Supplementary service activation".

In Step 7, the UE sends the REGISTER message with correct parameters for deactivation of CFB.

In Step 10, the UE provides the appropriate user indication.

In Step 12, the UE sends the CM SERVICE REQUEST message with the service type: "Supplementary service activation".

In Step 17, the UE sends the REGISTER message with the correct parameters for deactivation of CFNRc.

In Step 20, the UE provides the appropriate user indication.

15.4.7 Call forwarding supplementary services, Interrogation accepted

15.4.7.1 Definition

15.4.7.2 Conformance requirements

For interrogation of any specific call forwarding service (not applicable to a group of services) with any parameters, the UE shall transmit successively:

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

2) 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);

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

Reference

3GPP TS 24.082 clauses 2.6 and 3.6

15.4.7.3 Test purpose

1) To check that the UE correctly requests a supplementary service transaction for interrogation of call forwarding in the CM SERVICE REQUEST.

3) To check that the UE sends a REGISTER message containing the invoke of the InterrogateSS operation with the expected parameter values for interrogation of call forwarding.

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

These checks are done for:

a) CFB, for all basic service groups.

b) CFNRy, for basic service group speech.

15.4.7.4 Method of test

Initial Conditions

– System simulator:

– 1 cell, default parameters.

– User Equipment:

– the UE shall be in MM-state "Idle, updated";

Related ICS/IXIT Statements

Support of FDD Yes/No.

Support of CS speech Yes/No.

Description of the user’s commands and of display of the answers from the network for call forwarding

Support of Call Forwarding on Mobile Subscriber Busy Yes/No.

Support of Call Forwarding on No Reply Yes/No.

Test procedure

By means of appropriate user actions, the user requests interrogation of CFB for all basic service groups.

The SS transaction and the RRC connection are released.

Then again, by means of appropriate user actions, the user requests interrogation of CFNRy for speech.

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

Expected sequence

Step	Direction		Message	Comment
Step	UE	SS	Message	Comment
				If UE supports CFB, then step 1 to 10 are executed
1				The UE is made to initiate an interrogation of call forwarding service for CFB (all). The SS verifies that the IE “Establishment cause” in the received RRC CONNECTION REQUEST message is set to “Originating High Priority Signalling”.
2	->		CM SERVICE REQUEST	CM service type: "Supplementary service activation"
3	<-		AUTHENTICATION REQUEST
4	->		AUTHENTICATION RESPONSE
5	<-		SECURITY MODE COMMAND
6	->		SECURITY MODE COMPLETE
7	->		REGISTER
8	<-		RELEASE COMPLETE	InterrogateSS operation Return result
9	SS			The SS releases the RRC connection.
10	UE			Provide user indication
				If UE supports CFNRy, then step 11 to 20 are executed
11	UE			The UE is made to initiate an interrogation of call forwarding service for CFNRy(speech). “Establishment cause” in the received RRC CONNECTION REQUEST message is set to “Originating High Priority Signalling”.
12	->		CM SERVICE REQUEST	CM service type: "supplementary service activation"
13	<-		AUTHENTICATION REQUEST	Steps 13 and 14 are not executed if steps 3 and 4 were executed.
14	->		AUTHENTICATION RESPONSE
15	<-		SECURITY MODE COMMAND
16	->		SECURITY MODE COMPLETE
17	->		REGISTER
18	<-		RELEASE COMPLETE	InterrogateSS operation Return result
19	SS			The SS releases the RRC connection.
20	UE			Provide user indication

Specific Message Contents

Information Element	Value/remark	Condition
Facility
Invoke component
Operation Code	interrogateSS
Parameters
SS-Code
ss-Code	00101001 CFB
BasicServiceCode	no Bearer Service present, no teleservice present

RELEASE COMPLETE with Return result component with operation code (Step 8)

Information Element	Value/remark	Condition
Invoke ID	the same Invoke ID as in the REGISTER in Step 7
Operation code	interrogateSS
BasicServiceCode	no Bearer Service present, no teleservice present
ForwardedToNumber	Any number
SS-Status	‘0110’Provisioned and Registered

Information Element	Value/remark	Condition
Facility
Invoke component
Operation Code	interrogateSS
Parameters
SS-Code
ss-Code	00101010 CFNRy
BasicServiceCode	no bearer service present, teleservice (All Speech Transmission Services (TS10) or Telephony (TS11))

RELEASE COMPLETE with Return result component with operation code (Step 18)

Information Element	Value/remark	Condition
Invoke ID	the same Invoke ID as in the REGISTER in Step 17
Operation code	interrogateSS
BasicServiceCode	the same BasicServiceCode as in the REGISTER in Step 17
ForwardedToNumber	Any number
NoReplyConditionTime	Any time
SS-Status	‘0111’Provisioned, Registered and Activated

15.4.7.5 Test requirements

In Step 2, the UE sends the CM SERVICE REQUEST message with the service type: "Supplementary service activation".

In Step 7, the UE sends the REGISTER message with correct parameters for interrogation of CFB.

In Step 10, the UE provides the appropriate user indication.

In Step 12, the UE sends the CM SERVICE REQUEST message with the service type: "Supplementary service activation".

In Step 17, the UE sends the REGISTER message with the correct parameters for interrogation of CFNRy.

In Step 20, the UE provides the appropriate user indication.

15.4.8 Call forwarding supplementary services, Interrogation rejected

15.4.8.1 Definition

15.4.8.2 Conformance requirements

For interrogation of any specific call forwarding service (not applicable to a group of services) with any parameters, the UE shall transmit successively:

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

2) 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);

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

Reference

3GPP TS 24.082 clauses 2.6 and 3.6

15.4.8.3 Test purpose

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

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

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 UE provides the appropriate user indication (as described by the Manufacturer).

These checks are done for:

a) CFB, for all basic service groups.

b) CFNRy, for basic service group speech.

15.4.8.4 Method of test

Initial Conditions

– System simulator:

– 1 cell, default parameters.

– User Equipment:

– the UE shall be in CC state U10

Related ICS/IXIT Statements

Support of FDD Yes/No.

Support of CS speech Yes/No.

Description of the user’s commands and of display of the answers from the network for call forwarding
Support of Call Forwarding on Mobile Subscriber Busy Yes/No
Support of Call Forwarding on No Reply Yes/No

Test procedure

By means of appropriate user actions, the user requests interrogation of CFB for all basic service groups.

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 UE responds with STATUS message indicating CC state U10.

Then again, by means of appropriate user actions, the user requests interrogation of CFNRy for speech.

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 UE responds with STATUS message indicating CC state U10.

Expected sequence

Step	Direction		Message	Comment
Step	UE	SS	Message	Comment
				If UE supports CFB, then step 1 to 8 are executed
1				The UE is made to initiate an interrogation of call forwarding service for CFB (all)
2	->		CM SERVICE REQUEST	CM service type: "Supplementary service activation"
3	<-		CM SERVICE ACCEPT
4	->		REGISTER
5	<-		RELEASE COMPLETE	InterrogateSS operation Return_error
6	UE			Provide user indication
7	<-		STATUS ENQUIRY
8	->		STATUS	CC state U10
				If UE supports CFNRy, then step 9 to 16 are executed
9	UE			The UE is made to initiate an interrogation of call forwarding service for CFNRy(speech)
10	->		CM SERVICE REQUEST	CM service type: "supplementary service activation"
11	<-		CM SERVICE ACCEPT
12	->		REGISTER
13	<-		RELEASE COMPLETE	InterrogateSS operation Reject
14	UE			Provide user indication
15	<-		STATUS ENQUIRY
16	->		STATUS	CC state U10

Specific Message Contents

Information Element	Value/remark	Condition
Facility
Invoke component
Operation Code	interrogateSS
Parameters
SS-Code
ss-Code	00101001 CFB
BasicServiceCode	no Bearer Service present, no teleservice present

RELEASE COMPLETE with Return error component with operation code (Step 5)

Information Element	Value/remark	Condition
Invoke ID	the same Invoke ID as in the REGISTER in Step 4
Error Code	ss-NotAvailable

STATUS (Step 8)

Information Element	Value/remark	Condition
Cause	30 “Response to STATUS ENQUIRY”
Call state	U10- active

Information Element	Value/remark	Condition
Facility
Invoke component
Operation Code	interrogateSS
Parameters
SS-Code
ss-Code	00101010 CFNRy
BasicServiceCode	no bearer service present, teleservice (All Speech Transmission Services (TS10) or Telephony (TS11))

RELEASE COMPLETE with Reject component with operation code (Step 13)

Information Element	Value/remark	Condition
Invoke ID	the same Invoke ID as in the REGISTER in Step 12
Problem Code	Resource Limitation

STATUS (Step 16)

Information Element	Value/remark	Condition
Cause	30 “Response to STATUS ENQUIRY”
Call state	U10- active

15.4.8.5 Test requirements

In Step 2, the UE sends the CM SERVICE REQUEST message with the service type: "Supplementary service activation".

In Step 4, the UE sends the REGISTER message with correct parameters for interrogation of CFB.

In Step 6, the UE provides the appropriate user indication.

In Step 8, the UE sends the STATUS message with the correct parameters.

In Step 10, the UE sends the CM SERVICE REQUEST message with the service type: "Supplementary service activation".

In Step 12, the UE sends the REGISTER message with the correct parameters for interrogation of CFNRy.

In Step 14, the UE provides the appropriate user indication.

In Step 16, the UE sends the STATUS message with the correct parameters.