3 Call Forwarding on No Reply (CFNRy)

24.0823GPPCall Forwarding (CF) Supplementary ServicesRelease 17Stage 3TS

3.1 Normal operation

3.1.1 Served mobile subscriber side

When call forwarding on no reply is active, all incoming calls for the specified basic service(s) that are not answered within the period defined by the no reply condition timer, will be forwarded.

When an incoming call is forwarded on no reply the served mobile subscriber can, as a subscription option, receive a NotifySS operation containing the SS‑Notification indicating that a call has been forwarded, see figure 3.1.

MS Network

FACILITY

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

Facility (Invoke = NotifySS (CFNRy, SS-Notification))

Figure 3.1: Notification to the served mobile subscriber that the call is forwarded on no reply

When CFNRy is active, the ability of the served mobile subscriber to originate calls is not affected. However, a NotifySS operation containing the SS‑Status indicating that a conditional call forwarding supplementary service is currently active and operative will be sent to the served mobile subscriber each time an outgoing call is made, see figure 3.2.

MS Network

SETUP

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

e.g. ALERTING

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

Facility (Invoke = NotifySS (SS-Code, SS-Status))

NOTE: The SS-Code will be the common SS‑Code for all conditional call forwarding services.

Figure 3.2: Notification to the served mobile subscriber that a conditional call forwarding service is active

3.1.2 Forwarded‑to mobile subscriber side

The forwarded‑to mobile subscriber will receive a NotifySS operation containing the SS‑Notification indicating that the incoming call is a forwarded call. When available, the SS‑Code of the invoked forwarding service is also included, see figure 3.3.

When multiple forwarding occurs the value of the SS‑Code shall relate to the last invoked forwarding service.

In addition the forwarded-to mobile subscriber will receive the redirecting party BCD number and optionally, a redirecting party subaddress.

The redirecting party BCD number information element is made up of a number of information units as indicated in 3GPP TS 24.008.

In addition to or instead of the redirecting party’s digits, the subscriber may be given the following information:

– screening indicator;

– presentation indicator.

Indicator values are given in 3GPP TS 24.008.

The redirecting party subaddress information element is made up of a number of information units as indicated in 3GPP TS 24.008.

MS Network

SETUP

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

Facility (Invoke = NotifySS (CFNRy, SS-Notification))

Redirecting party BCD number (screening indicator, presentation indicator, redirecting party digits),

Redirecting party subaddress

NOTE: If the specific call forwarding service is not known the common SS‑Code for "all forwarding SS" will be used.

Figure 3.3: Notification to the forwarded‑to mobile subscriber that the incoming call is a forwarded call

3.1.3 Calling mobile subscriber side

As a subscription option, the served mobile subscriber can request that the calling mobile subscriber receives a NotifySS operation containing the SS‑Notification indicating that the call has been forwarded. When available, the SS‑Code of the invoked forwarding service is also included, see figure 3.4.

MS Network

SETUP

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

FACILITY

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

Facility (Invoke = NotifySS (CFNRy, SS-Notification))

NOTE: If the specific call forwarding service is not known the common SS‑Code for "all forwarding SS" will be used.

Figure 3.4: Notification to the calling mobile subscriber that the call is forwarded

3.2 Registration

The following information has to be registered in the network:

‑ the ForwardedToNumber, which may be accompanied by a ForwardedToSubAddress;

‑ information as to whether all calls or all calls of a specific basic service should be forwarded;

‑ the duration of the no reply condition timer.

3.2.1 Registration by the served mobile subscriber

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.

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 CFNRy registration was not successful. Error values are specified in 3GPP TS 24.080.

MS Network

REGISTER

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

Facility (Invoke = RegisterSS (CFNRy, BasicServiceCode, ForwardedToNumber, ForwardedToSubAddress, NoReplyConditionTime, LongFTNsupported))

RELEASE COMPLETE

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

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

RELEASE COMPLETE

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

Facility (Return error (Error))

RELEASE COMPLETE

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

Facility (Reject (Invoke_problem))

NOTE: If BasicServiceCode is not included it applies to all basic services. If NoReplyConditionTime is not included the value previously registered in the network applies. The ForwardedToNumber may be accompanied by a ForwardedToSubAddress. The SS‑Code may also indicate the code for "all conditional forwarding SS", as specified in subclause 2.2.1, or the code for "all forwarding SS", as specified in subclause 1.2.1. The SS‑Status may not be included in all cases, see text.

Figure 3.5: Registration of call forwarding on no reply

The presence of longFTN support is specified in 3GPP TS 23.082 [15].

3.3 Erasure

A previous registration can be erased in one of three ways:

‑ the subscriber can specifically erase a previous registration with an appropriate control procedure;

‑ the subscriber can register information for CFNRy for the specific basic service to another directory number, thus causing the previous registration of CFNRy to be overridden;

‑ all information is erased as a result of withdrawal of the supplementary service (administrative handling).

3.3.1 Erasure by the served mobile subscriber

A CFNRy erasure request from a mobile subscriber may include the BasicServiceCode. If this is not the case, the erasure applies to all basic services.

If the erasure is successful, the CFNRy service will be erased (and automatically deactivated). The network will then send a return result indicating acceptance of the request. The result is formatted according to the options shown below:

‑ The result includes the BasicService (group) Code for which CFNRy was erased. 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.6.

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

‑ If the request did not include a BasicServiceCode, and the erasure was successful for all basic services, the network may send an empty return result to the MS. This option applies whether or not an SS Version Indicator is received from the MS.

If the network cannot accept the erasure request, the status of CFNRy in the network remains unchanged. An error indication will then be returned to the served mobile subscriber that erasure of CFNRy was unsuccessful. Error values are specified in 3GPP TS 24.080.

MS Network

REGISTER

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

Facility (Invoke = EraseSS (CFNRy, BasicServiceCode))

RELEASE COMPLETE

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

Facility (Return result = EraseSS (BasicServiceCode, SS-Status))

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 SS‑Code may also indicate the code for "all conditional forwarding SS" or the code for "all forwarding SS". The SS‑Status may not be included in all cases, see text.

Figure 3.6: Erasure of call forwarding on no reply

3.4 Activation

An explicit CFNRy activation request shall contain the SS‑Code of the supplementary service to be activated and possibly the BasicServiceCode the request applies to. If a BasicServiceCode is not included in the activation request the request applies to all basic services against which a CFNRy forwarded‑to number is registered. The user shall receive appropriate notification of acceptance, rejection or partial acceptance of the CFNRy activation request, see figure 3.7.

Error values (which are used in the two latter situations) are specified in 3GPP TS 24.080.

MS Network

REGISTER

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

Facility (Invoke = ActivateSS (CFNRy, LongFTNsupported, BasicServiceCode))

RELEASE COMPLETE

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

Facility (Return result = ActivateSS (SS-Status))

RELEASE COMPLETE

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

Facility (Return error (Error))

RELEASE COMPLETE

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

Facility (Reject (Invoke_problem))

NOTE: The SS‑Code may also indicate the code "all conditional forwarding SS" group, as specified in subclause 2.2.1, or the "all forwarding SS" group, as specified in subclause 1.2.1.

Figure 3.7: Activation of call forwarding on no reply

The condition for the presence of longFTNsupport is specified in 3GPP TS 23.082 [15].

3.5 Deactivation

An explicit CFNRy deactivation request shall contain the SS‑Code of the supplementary service to be deactivated and possibly the BasicServiceCode the request applies to. If a BasicServiceCode is not included in the deactivation request the request applies to all basic services against which CFNRy is activated. The user shall receive appropriate notification of acceptance or rejection of the CFNRy deactivation request, see figure 3.8.

Error values to be used in the latter situation are specified in 3GPP TS 24.080.

Deactivation shall not lead to erasure of the information registered in the network.

MS Network

REGISTER

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

Facility (Invoke = DeactivateSS (CFNRy, BasicServiceCode))

RELEASE COMPLETE

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

Facility (Return result = DeactivateSS (SS-Status))

RELEASE COMPLETE

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

Facility (Return error (Error))

RELEASE COMPLETE

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

Facility (Reject (Invoke_problem))

NOTE: The SS‑Code may also indicate "all conditional forwarding SS" group or the "all forwarding SS" group.

Figure 3.8: Deactivation of call forwarding on no reply

3.6 Interrogation

Data request

The data request procedure enables the mobile subscriber to obtain information about the data stored in the PLMN. After having requested this procedure the network shall return the following information:

‑ in response to a general data request (i.e. not including a BasicServiceCode) the served mobile subscriber should be given the following data for each basic service group to which CFNRy is registered:

‑ the SS‑Status indicating whether the supplementary service is "not active", "active and operative" or "active and quiescent";

‑ the associated ForwardedToNumber which shall not be accompanied by a ForwardedToSubAddress;

‑ the duration of the no reply condition timer,

see figure 3.9.

If CFNRy is not registered for any basic service groups, only the SS‑Status parameter indicating "not registered" is returned.

MS Network

REGISTER

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

Facility (Invoke = InterrogateSS (CFNRy, LongFTNsupported))

RELEASE COMPLETE

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

Facility (Return result = InterrogateSS (BasicServiceCode, SS-Status, ForwardedToNumber, NoReplyConditionTime))

RELEASE COMPLETE

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

Facility (Return error (Error))

RELEASE COMPLETE

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

Facility (Reject (Invoke_problem))

NOTE: The ForwardedToNumber shall not be accompanied by a ForwardedToSubAddress. The return result may consist of a list of parameters, each relating to a specific basis service group.

Figure 3.9: Interrogation of active call forwarding on no reply for all basic services

‑ in response to a specific request (i.e. containing one particular BasicService (group) code, the served mobile subscriber should receive the SS‑Status parameter, indicating whether or not CFNRy is registered, including information as to whether or not it is active and operative or active and quiescent for that basic service group. If CFNRy is registered for the interrogated basic service group, the associated ForwardedToNumber and the duration of the no reply condition timer shall be given, see figure 3.10. 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 condition for the presence of longFTNsupport is specified in 3GPP TS 23.082 [15].

If CFNRy is not registered for the interrogated BasicService (group) code, only the SS‑Status parameter indicating "not registered" is returned.

MS Network

REGISTER

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

Facility (Invoke = InterrogateSS (CFNRy, BasicServiceCode, LongFTNsupported))

RELEASE COMPLETE

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

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

RELEASE COMPLETE

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

Facility (Return error (Error))

RELEASE COMPLETE

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

Facility (Reject (Invoke_problem))

NOTE: The ForwardedToNumber may be accompanied by a ForwardedToSubAddress.

Figure 3.10: Interrogation of active call forwarding on no reply for one particular basic service

The values "all forwarding SS" and "all conditional forwarding SS" shall not be sent over the air interface by the MS in an interrogation. If an interrogation is received containing one of these codes the network shall send a return error component. The condition for the presence of longFTNsupport is specified in 3GPP TS 23.082 [15].

3.7 Cross phase compatibility

3.7.1 Network only supports protocol version 1 control of SS by the subscriber

A CFNRy registration request which contains a ForwardedToSubaddress shall be rejected by the network if any network element involved is of protocol version 1.

Note that a CFNRy activation or deactivation request will be rejected by the network is any network element involved is of protocol version 1.

3.7.2 MS only supports protocol version 1 control of SS by the subscriber

In response to a CFNRy interrogation request, where the SS Version Indicator is not received from the MS, the network shall only return data for basic service groups to which CFNRy is activated and operative. Data shall not be returned for basic service groups to which CFNRy is deactivated. This means that the subscriber is not always aware of the true state of the service.

In response to a CFNRy registration or erasure request, where the SS Version Indicator is not received from the MS, the network shall always include the SS‑Status parameter.