8 Supplementary Services

22.1733GPPIP Multimedia Core Network Subsystem (IMS) Multimedia Telephony Service and supplementary servicesRelease 17Stage 1TS

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

8.1 General

This clause provides the description of the supplementary services applicable to IMS Multimedia Telephony service.

The behaviour of IMS supplementary services, as perceived by the user, shall be consistent with the behaviour perceived when using the equivalent supplementary services on PSTN/ ISDN and CS mobile networks.

For each supplementary service, the following is provided:

a short service definition;
a description of the normal operation with successful outcome.

And when applicable also:

a description of exceptional operation or unsuccessful outcome;
descriptions on interaction with other supplementary services applicable to IMS Multimedia Telephony service;
consideration for interworking with the CS mobile and fixed services.

In general, if a service is not mentioned within the interaction clause then there is no impact.

The support of some of these services may be mandatory or optional depending on specific country/regional regulation.

For CEPT members see annex C.

Some services are not applicable to UE accessing IMS via 3GPP accesses. See annex D.

8.2 Supplementary Services applicable to IMS Multimedia Telephony

8.2.1 Originating Identification Presentation (OIP)

8.2.1.1 Definition

The OIP service provides the terminating party with the Identity of the originating party.

The requirements for Presentation of session originating party identity shall be handled as described in [4].

8.2.1.2 Service interactions with other IMS supplementary services

8.2.1.2.1 Identification services

8.2.1.2.1.1 Originating Identification Restriction (OIR)

The requirements for the interactions between presenting and withholding the originating party’s identity shall be as described in [4].

8.2.1.2.1.2 Enhanced Calling Name

For users that subscribe to both OIP and eCNAM, originating party identity and eCNAM identity data shall be delivered to the terminating party.

If the originating party’s telephone number cannot be obtained, eCNAM shall not be retrieved. Instead, the terminating service provider shall indicate the unavailability of the eCNAM identity data to the terminating party.

The interface between terminating service provider and the trusted data source shall be private and secure.

The conditions for exchange of data are governed by regional regulation and through service provider agreement.

8.2.1.2.2 Diversion services

8.2.1.2.2.1 Communication Forwarding Unconditional (CFU)

When a communication has been forwarded and the forwarded-to party has been provided with the OIP service, the forwarded-to party shall receive the identity information of the original originating party, if this originating party has not subscribed to or invoked the OIR service.

8.2.1.2.2.2 Communication Forwarding Busy (CFB)

8.2.1.2.2.3 Communication Forwarding No Reply (CFNR)

8.2.1.2.2.4 Communication Forwarding on Not Logged-in (CFNL)

8.2.1.2.2.5 Communication Deflection (CD)

When a communication has been deflected and the deflected-to party has been provided with the OIP service, the deflected-to party shall receive the identity information of the original originating party, if this originating party has not subscribed to or invoked the OIR service.

8.2.1.2.2.6 Communication Forwarding on Subscriber Not Reachable (CFNRc)

8.2.1.2.2.7 (void)

8.2.1.2.3 Communication Waiting (CW)

If a party has the OIP service active and is notified that an incoming communication is waiting, then this party shall receive the identity information of the originating party, if this originating party has not subscribed to or invoked the OIR service.

8.2.1.3 Interoperability with PSTN/ISDN and mobileCS Networks

The IMS Multimedia Telephony service shall support the interoperability of the OIP service with mobile CS and PSTN/ISDN Supplementary Service CLIP and vice‑versa. The scope of this interworking may result in a limited service capability (only E.164 numbers can be used in the PSTN/ISDN).

8.2.2 Originating Identification Restriction (OIR)

8.2.2.1 Definition

The Originating Identification Restriction (OIR) service enables the originating party to withhold the presentation of its asserted identity information to the terminating party.

The requirements for withholding the originators identity shall be as described in [4]. Those requirements also allow certain terminating party to override the restriction (override capability).

8.2.2.2 Service interactions with other IMS supplementary services

8.2.2.2.1 Identification services

8.2.2.2.1.1 Originating Identification Presentation (OIP)

The requirements for the interactions between presenting and withholding the originating parties’ identity shall be as described in [4].

8.2.2.2.1.2 Enhanced Calling Name

The requirements for interactions between presenting and withholding the originating party’s eCNAM identity data shall adhere to the rules described in [4] for the presentation of session originator identity.

If the originating party subscribed to or invokes OIR, eCNAM identity information shall not be delivered, including data elements that the originating party had consented to release.

8.2.2.2.2 Diversion services

8.2.2.2.2.1 Communication Forwarding Unconditional (CFU)

When the OIR service has been invoked, the originating party’s identity information shall not be presented to the forwarded-to party unless the forwarded-to party has an override capability.

8.2.2.2.2.2 Communication Forwarding Busy (CFB)

Same as for CFU.

8.2.2.2.2.3 Communication Forwarding No Reply (CFNR)

Same as for CFU.

8.2.2.2.2.4 Communication Forwarding on Not Logged-in (CFNL)

Same as for CFU.

8.2.2.2.2.5 Communication Deflection (CD)

Same as for CFU.

8.2.2.2.2.6 Communication Forwarding on Subscriber Not Reachable (CFNRc)

Same as for CFU.

8.2.2.2.2.7 (void)

8.2.2.2.3 Explicit Communication Transfer (ECT)

An originating party’s restriction requirements from the original communication shall be used in order to restrict the presentation of that party’s identity to any party in a transferred communication.

8.2.2.3 Interoperability with PSTN/ISDN and mobile CS Networks

The IMS Multimedia Telephony service shall support the interoperability of OIR service with the mobile CS and the PSTN/ISDN Supplementary Service CLIR and vice‑versa. The scope of this interworking may result in a limited service capability. The Originating Identity Restriction information shall be conveyed from IMS to a mobile CS or a PSTN/ISDN and vice-versa. The network to which the called/terminating party is connected to is responsible to handle this service.

In case of limited interoperability, the restriction, OIR/CLIR shall have precedence.

8.2.3 Terminating Identification Presentation (TIP)

8.2.3.1 Definition

The TIP service provides the originating party with the asserted identity of the terminating party. The requirements for the presentation of the terminating identity shall be as described in [4].

NOTE: See also service definition in [E-17].

8.2.3.2 Service interactions with other IMS supplementary services

8.2.3.2.1 Identification services

8.2.3.2.1.1 Terminating identification presentation restriction

The requirements for the interactions between presenting and withholding the terminating party’s identity shall be as described in [4].

8.2.3.2.2 Diversion services

If forwarding party B chooses to restrict the presentation of the forwarded-to party C’s identity, the originating party A shall not receive the terminating party C’s identity irrespective of whether the terminating party C has TIR activated or not.

8.2.3.3 Interoperability with PSTN/ISDN and mobile CS Networks

The IMS Multimedia Telephony service shall support the interoperability of the TIP services with mobile CS and PSTN/ISDN Supplementary Service COLP and vice‑versa. The scope of this interworking may result in a limited service capability

8.2.4 Terminating Identification Restriction (TIR)

8.2.4.1 Definition

The Terminating Identification Restriction (TIR) enables the terminating party to withhold presentation of its asserted identity information to the originating party.

The requirements for withholding the terminating party’s identity are described in [4]. Those requirements also allow certain originating parties to override the restriction (override capability).

This service description is based on the service description described in [E-20].

8.2.4.2 Service interactions with other IMS Multimedia Telephony services

8.2.4.2.1 Identification services

8.2.4.2.1.1 Terminating Identification Presentation (TIP)

The requirements for the interactions between presenting and withholding the terminating party’s identity shall be as described in [4].

8.2.4.3 Interoperability with PSTN/ISDN and mobile CS Networks

The IMS Multimedia Telephony service shall support the interoperability of the TIR services with mobile CS and PSTN/ISDN Supplementary Services and vice‑versa. The scope of this interworking may result in a limited service capability.

In the case the target network does not support TIR service, the TIP information shall not be forwarded.

8.2.5 Malicious Communication IDentification (MCID)

8.2.5.1 Definition

The MCID service enables an incoming communication to be identified as malicious and registered.

This service may be available to a user only after subscription. Once the user has indicated to the network that the communication is malicious, the IMS shall register at least the following information:

Terminating Identity Information;
Originator Identity Information;
Local Time and Date of the invocation in the network serving the terminating entity;

The information shall not be available to the terminating entity nor the originating entity. The information shall be under the control of the network operator.

The user may identify the communication as malicious during the alerting phase, during an ongoing communication, or for a limited period after the communication has ceased.

8.2.5.2 Service interactions with other IMS supplementary services

8.2.5.2.1 Diversion Services

The MCID service can be invoked for a diverted communication. In addition to the normal operation of the MCID service, the identity of the first diverting party shall be registered and, as a network option, the last diverting party can be registered.

8.2.5.2.1.1 Communication Forwarding No Reply (CFNR)

If the terminating party has activated CFNR, once forwarding has taken place, the forwarding party cannot invoke the MCID service.

8.2.5.2.1.2 Communication Deflection (CD)

If the terminating party has activated communication deflection, once deflection has taken place, the deflecting party cannot invoke the MCID service.

8.2.5.2.2 Explicit Communication Transfer (ECT)

The transferring party cannot invoke the malicious communication identification service on a communication after transfer of that communication has been successfully invoked.

If after a transfer has been completed, the transferred-to party successfully invokes the malicious communication identification service, then the network shall register the identities of all parties involved.

8.2.5.2.3 CONFerence (CONF)

The conference controller cannot invoke the malicious call identification IMS supplementary service for participants within the conference.

NOTE: To activate the malicious call identification IMS supplementary service, the conference controller should first create a private communication with the user to be identified using the malicious call identification IMS supplementary service.

If a participant invokes the malicious call identification IMS supplementary service, only information about the connection to the conference controller shall be registered. No information about the other participants shall be registered.

8.2.5.2.4 Three-Party (3PTY)

See clause 8.2.5.2.3, noting that 3PTY is a special case of CONF.

8.2.5.3 Interoperability with PSTN/ISDN Networks

The MCID service shall interoperate for all communications from a PSTN/ISDN to an IMS Network supporting IMS Multimedia Telephony service and vice-versa. The registered information shall be stored in the invoking party’s network and may also be stored in the malicious party’s network.

8.2.6 Anonymous Communication Rejection (ACR)

8.2.6.1 Definition

The Anonymous Communications Rejection (ACR) service allows the terminating party to reject incoming communications from originating parties that have restricted their identity presentation.

Anonymous communications rejection provides the capability for network, on behalf of the user, to reject incoming sessions from users who have restricted the presentation of their originating identity, i.e. the asserted originating identity is marked "presentation restricted".

This service description is based on the service description described in [E-14].

Optional feature

In case of ACR service,

a allow list should contain certified public identities or identity ranges of users, from which incoming anonymous communications are allowed whatever ACR activation state,
a block list should contain certified public identities or identity ranges of users, from which incoming anonymous communications are not allowed whatever ACR activation state.

8.2.6.2 Service interactions with other IMS supplementary services

8.2.6.2.1 Identification Services

8.2.6.2.1.1 Originating Identification Presentation (OIP)

No impact, i.e. neither IMS supplementary service shall affect the operation of the other IMS supplementary service.

8.2.6.2.1.2 Originating Identification Restriction (OIR)

If the terminating party has activated the ACR service, then the OIR service causes the execution of the ACR service in accordance with the procedures in clause 8.2.6.1.

If the terminating party has the override capability according to the OIR service, then the ACR service shall not apply.

8.2.6.2.2 Diversion Services

NOTE: The precedence that ACR takes over the communication diversion services does not exclude the use of forwarding functionality in the ACR functionality itself. As an example: forwarding of anonymous communications (e.g. to a voice mailbox), as part of the ACR functionality is possible.

If the diverted-to user has activated the ACR service, then the ACR service shall take precedence over the communication diversion supplementary service i.e. the communication shall be rejected according to the ACR service.

8.2.6.2.2.1 Communication Forwarding Unconditional (CFU)

If the forwarding party has activated the ACR service, then the ACR service shall take precedence over the communication forwarding unconditional service i.e. the communication shall be rejected according to the ACR service.

8.2.6.2.2.2 Communication Forwarding Busy (CFB)

If the forwarding party has activated the ACR service, then the ACR service shall take precedence over the communication forwarding busy service i.e. the communication shall be rejected according to the ACR service.

8.2.6.2.2.3 Communication Forwarding No Reply (CFNR)

If the forwarding party has activated the ACR service:

no impact, i.e. neither IMS supplementary service shall affect the operation of the other IMS supplementary service.

NOTE: If the originating party has restricted its identity due to the OIR service the communication will not be presented.

8.2.6.2.2.4 Communication Forwarding on Not Logged-in (CFNL)

If the forwarding party has activated the ACR service, then the ACR service shall take precedence over the communication forwarding on not logged in service i.e. the communication shall be rejected according to the ACR service.

8.2.6.2.2.5 Communication Forwarding on Subscriber Not Reachable (CFNRc)

If the forwarding party has activated the ACR service, then the ACR service shall take precedence over the communication forwarding on subscriber not reachable service i.e. the communication shall be rejected according to the ACR service.

8.2.6.2.3 Communication Waiting (CW)

If the terminating party has activated the ACR service, then the ACR service shall take precedence over the Communication Waiting service. The ACR service can be activated while a communication is waiting without changing the state of the waiting communication session.

8.2.6.2.4 Completion of Communications to Busy Subscriber (CCBS)

NOTE: A CCBS recall (from the network to the originating party) resulting from the completion of communications to busy subscribers shall not be rejected due to the application of the ACR service.

Assuming the originating party connects to the terminating party and the terminating party activates the ACR service (or has activated the ACR service), two cases are possible:

a) The ACR service was activated by the terminating party before the originating party originates a communication:

No impact, i.e. no IMS supplementary service shall affect the operation of the other IMS supplementary service.

NOTE: If the originating party has restricted its identity due to the OIR service and if the terminating party is busy, the originating party will receive no busy indication, and the completion of communications to busy subscriber service will not apply. Instead the communication session attempt shall be rejected according to the normal procedures of the ACR service.

b) The ACR service is activated by the terminating party after the originating party has activated the completion of communications to busy subscriber service on the terminating party:

If the terminating party activates the ACR service after the originating party has activated the completion of communications to busy subscriber service on the terminating party, then the communication resulting from the completion of communications to busy subscriber service shall be rejected if the originating party has restricted its identity due to the OIR service.

8.2.6.3 Interoperability with PSTN/ISDN

The IMS Multimedia Telephony service shall support the interoperability of the ACR services with PSTN/ISDN Supplementary Services and vice‑versa. The scope of this interworking may result in a limited service capability.

8.2.7 Communication DIVersion (CDIV)

8.2.7.1 Definition

The following Communication DIVersion services are defined:

Communication Forwarding Unconditional (CFU).
Communication Forwarding Busy (CFB).
Communication Forwarding No Reply (CFNR).
Communication Forwarding on Not Logged in (CFNL).
Communication Deflection (CD).
Communication Forwarding on Subscriber Not Reachable (CFNRc).

For all communications diversion services, a service provider option of notification of diversion may be provided to the originating party. This service provider option may also include support for the invoking user to suppress the notification.

As a service option, CDIV services may be associated with a time and/or date setting. To support roaming, the time zone may also be included.

As a service option, CDIV services may be associated with the results of spoofed call detection applied to the session originator identity.

The use of any of the network determined diversion services on a call identified as a callback to an emergency call, by a user that is not the PSAP, shall be precluded.

Communication Forwarding Unconditional (CFU)

The CFU service enables a user to have the network redirect all communications to another user. The CFU service may operate on all communication, or just those associated with specified services. The user’s ability to originate communications is unaffected by the CFU service. After the CFU service has been activated, communications are forwarded independent of the status of the user.

As a service provider option, a subscription option can be provided to enable the user to receive an indication that the CFU service has been activated. This indication may be provided when the user originates a communication if the CFU service has been activated for the user’s identity and for the service requested for the communication.

The maximum number of diversions permitted for each communication is a service provider option. The service provider shall define the upper limit of diversions. When counting the number of diversions, all types of diversion are included.

This service description is based on the service description described in [E-1].

Communication Forwarding Busy (CFB)

The CFB service enables a user to have the network redirect communications, which would otherwise be regarded as busy, to another user. The CFB service may operate on all communications, or just those associated with specified services. The user’s ability to originate communications is unaffected by the CFB service.

As a service provider option, a subscription option can be provided to enable the user to receive an indication that the CFB service has been activated. This indication may be provided when the user originates a communication if the CFB service has been activated for the user and for the service requested for the communication.

This service description is based on the service description described in [E-2].

Communication Forwarding No Reply (CFNR)

The CFNR service enables a user to have the network redirect communications, when the communication request is not responded to within a defined period of time, to another user. The CFNR service may operate on all communications, or just those associated with specified services. The user’s ability to originate communications is unaffected by the CFNR service.

The CFNR service can only be invoked by the network after the communication has been offered to the user and an indication that the user has been informed of the communication request.

As a service provider option, a subscription option can be provided to enable the user to receive an indication that the CFNR service has been activated. This indication may be provided when the user originates a communication if the CFNR service has been activated for the user and for the service requested for the communication.

This service description is based on the service description described in [E-3].

As a service option, CFNR activation confirmation may include information from the network providing the public identity where the communication will be forwarded to, and the expiry time before the communication is forwarded.

As a service option, the user may be allowed to dynamically extend this timing.

Communication Forwarding on Not Logged-in (CFNL)

The Communication Forwarding on Not Logged-in (CFNL) service enables a user to redirect incoming communications, when the user is not currently registered (logged-in), to another user. The CFNL service may operate on all communications, or just those associated with specified services.

As a service provider option, a subscription option can be provided to enable the user to receive an indication that the CFNL service has been activated. This indication may be provided when the user next registers (logs in). An indication may also be provided as part of de-registration (log out).

Communication Deflection (CD)

The CD service enables the user to respond to an incoming communication by requesting redirection of that communication to another user. The CD service can only be invoked before the communication is established by the user, i.e. in response to the offered communication, or during the period that the user is being informed of the communication. The user’s ability to originate communications is unaffected by the CD service.

This service description is based on the service description described in [E-4].

Communication Forwarding on Subscriber Not Reachable (CFNRc)

The CFNRc service enables a user to have the network redirect all incoming communications, or just those associated with a specific service, when called mobile subscriber’s address is not reachable (e.g. there is no IP connectivity to the user’s terminal, or, in the case of a mobile device, it is not in radio coverage), to another address. The CFNRc service may operate on all communications, or just those associated with specified services. The user’s ability to originate communications is unaffected by the CFNRc service.

NOTE: It may be affected by the reason that have triggered the loss of connectivity, e.g. in the mobile case if the mobile subscriber is de-registered, if there is radio congestion or if the mobile subscriber for example is being out of radio coverage,

As a service provider option, a subscription option can be provided to enable the user to receive an indication that the CFNRc service has been activated. This indication may be provided when the user originates a communication if the CFNRc service has been activated for the user and for the service requested for the communication.

Optional feature

Lists can be used also in association to Communication Diversions (CDIV).

a block list should contain public identities or identity ranges of users, from which incoming communications are not forwarded when CDIV is activated.
a allow list should contain public identities or identity ranges of users, from which incoming communications are forwarded when CDIV is activated.

8.2.7.2 (void)

8.2.7.3 Service interactions with other IMS supplementary services

8.2.7.3.1 Identification services

8.2.7.3.1.1 Originating Identification Presentation (OIP)

When a communication has been diverted and the diverted-to party has been provided with the originating identification presentation service, the diverted-to party shall receive the identity of the originating party, if this originating party has not subscribed to or invoked the originating identification restriction service.

8.2.7.3.1.2 Originating Identification Restriction (OIR)

When the originating identification restriction service has been invoked, the originating party’s identity shall not be presented to the diverted-to party unless the diverted-to party has an override capability.

8.2.7.3.1.3 Terminating Identification Presentation (TIP)

When a communication has been diverted and the originating party has been provided with the terminating identification presentation service, the originating party shall receive the identity of the diverted-to party, unless the diverting user has selected the option to suppress the notification of diversion.

8.2.7.3.1.4 Terminating Identification Restriction (TIR)

If the diverting party or the diverted-to party has invoked the Terminating Identification Restriction service, then the diverted-to party’s identity shall not be provided to the originating party unless the originating party has override capability.

8.2.7.3.1.5 Enhanced Calling Name (eCNAM)

When a communication has been diverted and the diverted-to party subscribes to the eCNAM service, the diverted-to party shall receive the eCNAM identity data of the original originating party, if this originating party has not subscribed to or invoked OIR.

8.2.7.3.2 Malicious Communication IDentification (MCID)

This services does not apply to UE accessing from mobile 3GPP access networks.

See clause 8.2.5.2.1.

8.2.7.3.3 Anonymous Communication Rejection (ACR)

This service does not apply to UE accessing from mobile 3GPP access networks.

See clause 8.2.6.2.2.

8.2.7.3.4 Diversion services

8.2.7.3.4.1 Communication Forwarding Unconditional (CFU)

Communication Forwarding Unconditional (CFU): Not applicable.

Communication Forwarding Busy (CFB): Invocation of the communication forwarding unconditional service shall take precedence over the CFB service.

Communication Forwarding No Reply (CFNR): Invocation of the communication forwarding unconditional service shall take precedence over the CFNR service.

Communication Forwarding on Not Logged-in (CFNL): Invocation of the communication forwarding unconditional service shall take precedence over the CFNL service.

Communication Deflection (CD): Invocation of the communication forwarding unconditional service shall take precedence over the CD service.

Communication Forwarding on Subscriber Not Reachable (CFNRc): Invocation of the communication forwarding unconditional service shall take precedence over the CFNRc service.

8.2.7.3.4.2 Communication Forwarding Busy (CFB)

Communication Forwarding Unconditional (CFU): Invocation of the CFU service shall take precedence over the communication forwarding busy service.

Communication Forwarding Busy (CFB): Not applicable.

Communication Forwarding No Reply (CFNR): No impact, i.e. this IMS supplementary service should not affect any other IMS supplementary service.

Communication Forwarding on Not Logged-in (CFNL): No impact, i.e. this IMS supplementary service should not affect any other IMS supplementary service.

Communication Deflection (CD): If the terminating party is not network determined user busy, then the CD service or the communication forwarding busy service can be invoked, depending on the response from the terminating party.

Communication Forwarding on Subscriber Not Reachable (CFNRc): If the terminating party is network determined busy, then CFB shall take precedence over CFNRc. Otherwise, if the terminating party is not network determined user busy, then there is no impact, i.e. this IMS supplementary service should not affect any other IMS supplementary service.

8.2.7.3.4.3 Communication Forwarding No Reply (CFNR)

Communication Forwarding Unconditional (CFU): Invocation of the CFU service shall take precedence over the communication forwarding no reply service.

Communication Forwarding Busy (CFB): No impact, i.e. this IMS supplementary service should not affect any other IMS supplementary service.

Communication Forwarding No Reply (CFNR): Not applicable.

Communication Forwarding on Not Logged-in (CFNL): No impact, i.e. this IMS supplementary service should not affect any other IMS supplementary service.

Communication Deflection (CD): No impact, i.e. this IMS supplementary service should not affect any other IMS supplementary service.

NOTE: If the network indicates the arrival of an incoming communication to the terminating party, then the CD service, or the communication forwarding no reply service can be invoked, depending on the response, or lack of response, from the terminating party.

Communication Forwarding on Subscriber Not Reachable (CFNRc): No impact, i.e. this IMS supplementary service should not affect any other IMS supplementary service.

8.2.7.3.4.4 Communication Forwarding on Not Logged-in (CFNL)

Communication Forwarding Unconditional (CFU): Invocation of the communication forwarding unconditional service shall take precedence over the CFNL service.

Communication Forwarding Busy (CFB): No impact, i.e. this IMS supplementary service should not affect any other IMS supplementary service.

Communication Forwarding No Reply (CFNR): No impact, i.e. this IMS supplementary service should not affect any other IMS supplementary service.

Communication Forwarding on Not Logged-in (CFNL): Not applicable.

Communication Deflection (CD): No impact, i.e. this IMS supplementary service should not affect any other IMS supplementary service.

Communication Forwarding on Subscriber Not Reachable (CFNRc): No impact, i.e. this IMS supplementary service should not affect any other IMS supplementary service.

8.2.7.3.4.5 Communication Deflection (CD)

Communication Forwarding Unconditional (CFU): Invocation of the CFU service shall take precedence over the communication deflection service.

Communication Forwarding Busy (CFB): If the terminating party is not network determined user busy, then the communication deflection service or the CFB service can be invoked, depending on the response from the terminating party.

Communication Forwarding No Reply (CFNR): No impact, i.e. this IMS supplementary service should not affect any other IMS supplementary service.

NOTE: If the network indicates the arrival of an incoming communication to the terminating party, then the communication deflection service, or the CFNR service can be invoked, depending on the response, or lack of response, from the terminating party.

Communication Forwarding on Not Logged-in (CFNL): No impact, i.e. this IMS supplementary service should not affect any other IMS supplementary service.

Communication Deflection (CD): Not applicable.

Communication Forwarding on Subscriber Not Reachable (CFNRc): No impact, i.e. this IMS supplementary service should not affect any other IMS supplementary service.

8.2.7.3.4.6 Communication Forwarding on Subscriber Not Reachable (CFNRc)

Communication Forwarding Unconditional (CFU): Invocation of the communication forwarding unconditional service shall take precedence over the CFNRc service.

Communication Forwarding Busy (CFB): If the terminating party is network determined busy, then CFB shall take precedence over CFNRc. Otherwise, if the terminating party is not network determined user busy, then there is no impact, i.e. this IMS supplementary service should not affect any other IMS supplementary service.

Communication Forwarding No Reply (CFNR): No impact, i.e. this IMS supplementary service should not affect any other IMS supplementary service.

Communication Forwarding on Not Logged-in (CFNL): No impact, i.e. this IMS supplementary service should not affect any other IMS supplementary service.

Communication Deflection (CD): No impact, i.e. this IMS supplementary service should not affect any other IMS supplementary service.

Communication Forwarding on Subscriber Not Reachable (CFNRc): Not applicable.

Explicit Communication Transfer (ECT)

No interaction, i.e. this IMS supplementary service should not affect any other IMS supplementary service.

Other services:

Communication Forwarding on Mobile Subscriber Not Reachable (CFNRc) shall interact with the following IMS supplementary services in exactly the same way as described for Communication Forwarding No Reply (CFNR):

Originating Identification Presentation (OIP)
Originating Identification Restriction (OIR)
Terminating Identification Presentation (TIP)
Terminating Identification Restriction (TIR)
Communication Diversion (CDIV); Communication Forward Unconditional
Communication Diversion (CDIV); Communication Deflection
Communication Diversion (CDIV); Communication Forward On not Logged-in
Communication Hold (HOLD)
Communication Barring (CB)
Message Waiting Indication (MWI)
Conference (CONF)

8.2.7.3.4.7 (void)

8.2.7.3.5 Communication Waiting (CW)

Communication Forwarding Unconditional (CFU): CW has no impact on CFU. The communication will be forwarded without regard to the terminating party’s state. A forwarded-to party may have communication waiting service and this will be activated if busy.

A forwarded communication can result in the communication waiting service.

Communication Forwarding Busy (CFB): No impact, i.e. neither service shall affect the operation of other service. A forwarded communication can result in the communication waiting service.

NOTE: If the terminating party is Network Determined User Busy, the communication waiting service is not be invoked, and the CFB service is invoked if it was activated.

Communication Forwarding No Reply (CFNR): If the terminating party has activated the CFNR service, then a waiting communication shall still be offered. If the CFNR timer expires before an answer is received then the CFNR service shall be invoked and the communication shall be forwarded and communication waiting ceased.

A forwarded communication can result in the communication waiting service.

Communication Forwarding on Not Logged-in (CFNL): No impact.

NOTE: If a party with an active communication waiting logs out, the all active and offered communication would be released.

Communication Deflection (CD): When receiving the communication waiting indication, terminating party can invoke the CD service. A deflected communication can result in the communication waiting service.

Communication Forwarding on Subscriber Not Reachable (CFNRc): No impact, i.e. this IMS supplementary service should not affect any other IMS supplementary service.

8.2.7.3.6 Communication Barring (CB)

8.2.7.3.6.1 Outgoing communication barring-fixed

If the outgoing communication barring-fixed service has already been activated, a request to activate any CDIV service shall be rejected if the forwarding party’s communication to the diverted-to party would be barred by the outgoing communication barring-fixed service.

If the CDIV service was activated before the activation of the outgoing communication barring-fixed service, the outgoing communication barring-fixed service can still be activated. When the two services have already been activated, a request to invoke the CDIV service shall be rejected if the forwarding party’s communication to the diverted-to party would be barred by the outgoing communication barring-fixed service at the time of the invocation attempt of the CDIV service.

8.2.7.3.6.2 Outgoing communication barring-user controlled

If the outgoing communication barring-user controlled service has already been activated, a request to activate any CDIV service shall be rejected if the forwarding party’s communication to the diverted-to party would be barred by the outgoing communication barring-user controlled service.

If the CDIV service was activated before the activation of the outgoing communication barring-user controlled service, the outgoing communication barring-user controlled service can still be activated. When the two services have already been activated, a request to invoke the CDIV service shall be rejected if the forwarding party’s communication to the diverted-to party would be barred by the outgoing communication barring-user controlled service at the time of the invocation attempt of the CDIV service.

8.2.7.3.7 Completion of Communications to Busy Subscriber (CCBS)

CCBS recalls shall never be diverted. They shall be provided to the original originating party.

8.2.7.3.8 Advice Of Charge (AOC)

8.2.7.3.8.1 Charging information at the End of the communication (AOC-E)

Originating party: No impact, i.e. this IMS supplementary service should not affect any other IMS supplementary service.

Forwarding party: When a communication is forwarded and the forwarding party is charged for the forwarded part of the communication, then as a network option, the charging information can be transferred to the forwarding user when the communication is terminated provided that the served user has subscribed to the advice of charge: charging information at the end of the communication service with the value of the subscription option set to "for all communications automatically".

8.2.7.4 Interoperability with PSTN/ISDN and CS mobile networks

The IMS Multimedia Telephony service shall support the interoperability of the CDIV service with mobile CS and PSTN/ISDN Supplementary Services and vice‑versa. The scope of this interworking may result in a limited service capability. The CLI information of the originating party as well as further CLI information (first redirected address, last redirected address) may be provided to the final called party, if the network allows this.

8.2.8 Communication Waiting (CW)

8.2.8.1 Definition

The Communication Waiting (CW) service enables a terminating party to be informed at the time that a new communication is requested, and that no resources are available for that incoming communication.

The user has then the choice of accepting, rejecting or ignoring the incoming communication.

The maximum number of communications that may be waiting is a service provider option.

If the current number of communications waiting is equal to the maximum, then any new attempted incoming communication request shall be rejected with a busy cause.

This service description is based on the service description described in [E-6] and [E-5].

As a service option, the communication waiting indication may also include the expiry time. As a service option, the user may be allowed to dynamically extend this timing.

In the presence of another call at the destination user where the incoming call is identified as a callback to an emergency call, then either the communication request shall be presented, or the CW service shall be used.

8.2.8.2 Service interactions with other IMS supplementary services

8.2.8.2.1 Anonymous Communication Rejection (ACR)

8.2.8.2.1a Enhanced Calling Name (eCNAM)

If the terminating party has the eCNAM service active and is notified that an incoming communication is waiting, then this terminating party shall receive the eCNAM identity data of the incoming waiting party, if this originating party has not subscribed to or invoked the OIR service.

8.2.8.2.2 Diversion services

The interactions between Communication Waiting and Communication Diversion services are described in clause 8.2.7.3.5 of the present document.

8.2.8.2.3 Completion of Communications to Busy Subscriber (CCBS)

If a subscriber to the completion of communications to busy subscriber service places a communication to a terminating party who has subscribed to the CW service, and the terminating party is provided the communication waiting indication, then invocation of completion of communications to busy subscriber service cannot occur.

8.2.8.3 Interoperability with PSTN/ISDN

No requirements.

8.2.9 Communication HOLD (HOLD)

8.2.9.1 Definition

The communication HOLD service enables a user to suspend media within a session, and resume that media at a later time.

Each party in a communication can hold and retrieve the communication independently from the other party. This also applies when a communication involves more than two parties (e.g. CONF).

This service description is based on the service description described in [4], dealing about the user ability to suspend and resume a session.

The use of HOLD on an emergency call, or a call identified as a callback to an emergency call, by a user that is not the PSAP, shall be precluded.

8.2.9.2 Service interactions with other IMS supplementary services

8.2.9.2.1 CONFerence (CONF)

A, B and C are in a conference that was created by B invoking the CONF service. B can interrupt their own participation in the conference by using the HOLD service. When B does this, A and C shall not receive the HOLD notification and are not prevented from carrying on their conversation

8.2.9.2.2 Three-Party (3PTY)

See clause 8.2.9.2.1, noting that 3PTY is a special case of CONF.

8.2.9.3 Interoperability with PSTN/ISDN and CS mobile networks

The IMS Multimedia Telephony service shall support the interoperability of the HOLD service with mobile CS and PSTN/ISDN Supplementary Services and vice‑versa. The scope of this interworking may result in a limited service capability.

8.2.10 Communication Barring (CB)

8.2.10.1 Definition

The group of Communication Restriction Services includes two services:

Outgoing Communications Barring (OCB).

This service allows a user to bar certain categories of outgoing communications. The network shall provide the capability for a user to select a set of categories (e.g. identities or range of identities) for barring. The type of barring is chosen by the user at provision time, and shall be valid for all outgoing communications. The network shall provide the capability for the user to bar outgoing communications based on user defined identities or identity ranges. Barring of an outgoing communication for a specific identity, a number of specific identities, or a range of identities shall be dependent on an entry in a OCB identity list held in the network. This list shall either be a "block list" or "allow list". A "block list" shall contain the identities or identity ranges to be barred by the network for outgoing communications. A "allow list" shall contain the identities or identity ranges that shall be allowed by the network for outgoing communications, i.e. all identities not in the "allow list" shall be barred.

The ability of the served user to receive communications and to originate emergency communications shall be unaffected by OCB.

This service description is based on the service description described in [E-15] and [E-16].

Incoming Communications Barring (ICB).

This service allows a user to bar certain categories of incoming communications. The service also allows the user to have the barring of incoming communications activated always or only during certain conditions. The network shall provide the capability for a user to select from a set of categories (e.g. identities or range of identities) for barring. Barring of an incoming communication shall be dependent on an entry in an ICB identity list held in the network. This list shall be a "block list" which contains the identities or identity ranges to be barred by the network for incoming communications. The type of barring is chosen by the user at provision time and may be valid for all incoming communications, or be limited to a specific service group or certain conditions (e.g. when the user is roaming).

The ability of the served user to set-up outgoing communications shall be unaffected by ICB.

The ICB service includes a roaming condition. The roaming condition is set to true when the served user is roaming.

The use of ICB on a call identified as a callback to an emergency call, by a user that is not the PSAP, shall be precluded.

ICB enhancement of dynamic blocking of incoming communications

As a service option, the dynamic blocking of incoming communications service facilitates either or both of the following:

– A terminating users register of unwanted callers within the network for barring future incoming communications from the unwanted callers either permanently or for a temporary period or for a maximum lifetime which is set by the network operator. As an option, an additional "dynamic block list" may be provided, which is different compared to the standard ICB list. If this additional "dynamic block list" is provided, the user shall have the option to activate and deactivate that list independent of the already existing standard ICB list.

– A terminating user activates barring of spoofed calls either permanently or for a temporary period or for a maximum lifetime which is set by the network operator based on associated spoofed call detection applied to the session originator identity.

The following information shall be stored by the network for dynamic blocking of incoming calls:

Actual Identity of caller: This is the network asserted identity of the caller.

Start and end date for barring: This specifies the duration of block. If not provided, it implies the caller should be barred permanently or for a maximum lifetime which is set by the network operator.

Additionally, the following information may be provided by the user or spoofed call detection and associated with the actual identity:

– Reason: This specifies the reason for blocking or an alias, e.g. "Telemarketer". This field may assist the subscriber to manage their block list

– Published Identity of caller: This may be the actual identity of caller or ‘private’ or ‘anonymous’ if the caller has opted for privacy.

NOTE: The unwanted caller may have requested privacy e.g. by subscribing to OIR service which prevents the calling identity being shown to the called user. In these cases the called user may just see "Anonymous" or "Unknown". However the called party can still invoke caller ID blocking since the network knows the true identity of the caller. To facilitate the management of the list of blocked callers, the user may use the reason field to identify the blocked caller.

The network shall never reveal an identity withheld using privacy, OIR, or other mechanisms (i.e. list management must use the published identity).

As an option and subject to the network operator policy, the network shall notify (e.g. announcement) the blocked originating user (unwanted user), that the called user has set an incoming communication barring for his identity.

Subject to the network operator policy, the subscriber may request notification of communication barrings within the network in addition to subscribing to the dynamic blocking of incoming communications service.

NOTE 1: The contents of information received as part of notification for the dynamic blocking of incoming communications, could be the same as the ones, that are registered as part of communication barring.

NOTE 2: Off-line management of the barring list (e.g. via a web page) may be provided as a service option.

NOTE 3: Where required by regulation, this enhanced service may be used to block calls from a previously malicious caller.

8.2.10.2 Service interactions with other IMS supplementary services

8.2.10.2.1 Diversion services

8.2.10.2.1.1 Communication Forwarding Unconditional (CFU)

If the OCB service has already been activated, a request to activate the communication forwarding unconditional service shall be rejected if the user’s communication to the forwarded-to user would be barred by the OCB service at the time of the activation attempt of the communication forwarding service.

If the communication forwarding unconditional service was activated before the activation of the OCB service, the OCB service can still be activated. When the two services have already been activated, a request to invoke the communication forwarding unconditional service shall be rejected if the forwarding party’s communication to the forwarded-to party would be barred by the OCB service at the time of the invocation attempt of the communication forwarding unconditional service..

8.2.10.2.1.2 Communication Forwarding Busy (CFB)

If the OCB service has already been activated, a request to activate the communication forwarding busy service shall be rejected if the forwarding party’s communication to the forwarded-to party would be barred by the OCB service at the time of the activation attempt of the communication forwarding service.

If the communication forwarding busy service was activated before the activation of the OCB service, the OCB service can still be activated. When the two services have already been activated, a request to invoke the communication forwarding busy service shall be rejected if the forwarding party’s communication to the forwarded-to party would be barred by the OCB service at the time of the invocation attempt of the communication forwarding busy service.

8.2.10.2.1.3 Communication Forwarding No Reply (CFNR)

If the OCB service has already been activated, a request to activate the communication forwarding no reply service shall be rejected if the forwarding party’s communication to the forwarded-to party would be barred by the OCB service at the time of the activation attempt of the communication forwarding service.

If the communication forwarding no reply service was activated before the activation of the OCB service, the OCB service can still be activated. When the two services have already been activated, a request to invoke the communication forwarding no reply service shall be rejected if the forwarding party’s communication to the forwarded-to party would be barred by the OCB service at the time of the invocation attempt of the communication forwarding no reply service.

8.2.10.2.1.4 Communication Forwarding on Not Logged-in (CFNL)

If the OCB service has already been activated, a request to activate the communication forwarding no registration service shall be rejected if the forwarding party’s communication to the forwarded-to party would be barred by the OCB service at the time of the activation attempt of the communication forwarding service.

If the communication forwarding on Not Logged-in service was activated before the activation of the OCB service, the OCB service can still be activated. When the two services have already been activated, a request to invoke the communication forwarding on Not Logged-in service shall be rejected if the forwarding party’s communication to the forwarded-to party would be barred by the OCB service at the time of the invocation attempt of the communication forwarding on Not Logged-in service.

8.2.10.2.1.5 Communication Deflection (CD)

If the OCB service has been activated, a request to invoke the communication deflection service shall be rejected if the deflecting party’s communication to the deflected-to party would be barred by the OCB service at the time of the invocation attempt of the communication deflection service.

8.2.10.3 Interoperability with PSTN/ISDN and CS mobile networks

The IMS Multimedia Telephony service shall support the interoperability of the CB service with mobile CS and PSTN/ISDN Supplementary Service CB and with ODB [6], and vice‑versa. The scope of this interworking may result in a limited service capability.

8.2.11 Completion of Communications to Busy Subscriber (CCBS)

8.2.11.1 Definition

The CCBS service enables originating party, encountering a busy terminating party, to have the communication completed without having to make a new communication attempt when the terminating party becomes free.

When originating party requests the CCBS service, the network will monitor for terminating party becoming free.

When terminating party becomes free then the network will wait a short time in order to allow the resources to be re-used for originating a communication. If the resources are not re-used by terminating party within this time, then the network will automatically inform originating party that terminating party has become free. Originating party can generate the CCBS communication to terminating party.

When originating party accepts the CCBS recall, then the network will automatically generate a CCBS communication to terminating party.

NOTE: A service provided to terminating party which prevents the registration of CCBS requests is outside the scope of the present document.

During CCBS recall, information shall be provided which indicates a CCBS recall. The information provided in the original communication attempt shall be included in the CCBS recall.

This service description is based on the service description described in [E-9].

As a service option, the time to expiry of the CCBS and the terminating party identity may be provided by the network, either at successful activation, or as a result of an interrogation.

8.2.11.2 Service interactions with other IMS supplementary services

8.2.11.2.1 Identification services

8.2.11.2.2 Anonymous Communication Rejection (ACR)

A CCBS recall (from the network to the originating party) resulting from the completion of communications to busy subscribers shall not be rejected due to the application of the ACR service.

Assume the originating party connects to the terminating party and the terminating party activates the ACR service or has activated the ACR service:

The ACR service is activated by the terminating party after the originating party has activated the completion of communications to busy subscriber service on the terminating party:
If the terminating party activates the ACR service after the originating party has activated the completion of communications to busy subscriber service on the terminating party, then the communication resulting from the completion of communications to busy subscriber service shall be rejected if the originating party has restricted its identity due to the OIR service.

8.2.11.2.3 Communication DIVersion (CDIV)

CCBS recalls shall never be diverted. They shall be provided to the original originating party.

CCBS can not be activated on a diverted communication.

8.2.11.2.4 Communication Waiting (CW)

NOTE: For a waiting communication, terminating party is not considered as busy.

If the Communication Waiting indication cannot be provided at the terminating party, originating party will receive busy indication and can invoke the CCBS service to terminating party.

CCBS requests in the terminating party’s CCBS queue shall only be processed if there are no communications waiting.

8.2.11.2.5 Communication HOLD (HOLD)

No impact, i.e. this IMS supplementary service should not affect any other IMS supplementary service.

NOTE 1: When receiving a CCBS communication indication, originating party may invoke the communication hold service in order to make interface resources available for the establishment of the CCBS communication.

NOTE 2: When originating party is busy or CCBS busy and is notified that terminating party is free, invocation of the communication hold service will not result in the CCBS communication being established.

8.2.11.2.6 Communication Barring (CB)

The originating party calls the terminating party who is busy, and then the originating party invokes CCBS. If the originating party then invokes OCB before the terminating party becomes free, the CCBS communication may be rejected due to the OCB invocation.

8.2.11.2.7 Completion of Communications to Busy Subscriber (CCBS)

A user can be both an "originating party" and a "terminating party" simultaneously, i.e. that user can have activated the CCBS service and have CCBS requests outstanding whilst at the same time that user can be the destination of CCBS requests from other users.

If a user receives a CCBS recall while that terminating party’s CCBS queue is being processed, then the CCBS recall shall take priority over the handling of the terminating party’s CCBS queue. The handling of CCBS requests activated by this user shall have priority over the handling of CCBS requests activated by other users on this user.

If one of the user’s CCBS requests matures as a result, then the user shall be provided a CCBS recall or notification. The terminating party idle guard timer, if running, shall be cancelled.

8.2.11.2.8 Advice Of Charge services (AOC)

Charging information can be provided for the original communication, and for the resulting CCBS communication.

8.2.11.2.9 Enhanced Calling Name (eCNAM)

The originating party’s eCNAM identity data shall be delivered to the CCBS customer’s UE when the terminating party becomes free and a CCBS communication is generated to the terminating party.

If the terminating party has subscribed to or invoked OIR, the originating party’s eCNAM identity data shall not be delivered to the originating party.

8.2.11.3 Interoperability with PSTN/ISDN

The IMS Multimedia Telephony service shall support the interoperability of the CCBS service with PSTN/ISDN Supplementary Service CCBS and vice‑versa. The scope of this interworking may result in a limited service capability.

8.2.12 Message Waiting Indication (MWI)

8.2.12.1 Definition

The MWI service enables the network, upon the request of a controlling user to indicate to the receiving user, that there is at least one message waiting. The indication is sent to the receiving user when a message is deposited. Optionally, the network may send an indication to the user that there are no more unread message in the mail box. This indication may be send when the last unread message is read.

NOTE: As an example, a voice message is stored by the network for a particular user. The network then provides the MWI to the user to indicate there is a message for retrieval. Having received this indication, the receiving user can subsequently access the mail box, to listen to the message.

The means by which the receiving user accesses and manages the mail box voice message service are outside the scope of the present document.

This service description is based on the service description described in [E-13].

8.2.12.2 Service interactions with other services

8.2.12.2.1 Diversion services

8.2.12.2.1.1 Communication Forwarding Unconditional (CFU)

The MWI shall never be diverted.

8.2.12.2.1.2 Communication Forwarding Busy (CFB)

Same as CFU.

8.2.12.2.1.3 Communication Forwarding No Reply (CFNR)

Same as CFU.

8.2.12.2.1.4 Communication Forwarding on Not Logged-in (CFNL)

The MWI shall never be diverted. The indication shall be provided to the owning identity on re-registering.

8.2.12.3 Interoperability with PSTN/ISDN and CS mobile networks

There is no interoperability with mobile CS and PSTN/ISDN because MWI is a local service.

8.2.13 CONFerence (CONF)

8.2.13.1 Definition

The CONF service enables a user to participate in and control a simultaneous communication involving a number of users.

When the CONF service is invoked, conference resources are allocated to the served user.

Once a conference is active, users can join and leave a conference, and remote users can be added to or removed from the conference.

This service description is based on the service description described in [E-7] and [E-8].

Conference participants can request to be informed of these actions. This information can include details beyond that described in [E-7] and [E-8], about other participants including their identity.

The use of CONF on an emergency call, or a call identified as a callback to an emergency call, by a user that is not the PSAP, shall be precluded.

8.2.13.2 Service interactions with other IMS supplementary services

8.2.13.2.1 Diversion services

No impact, i.e. neither IMS supplementary service shall affect the operation of the other IMS supplementary service.

8.2.13.2.2 CONFerence (CONF)

A user can be involved as the conference controller separately in more than one conference. However, the user cannot add any conference to another conference.

The CONFerence service shall provide a similar user experience as the circuit switched Multiparty supplementary service but with multimedia capabilities.

8.2.13.2.3 Advice Of Charge services (AOC)

No impact, i.e. this IMS supplementary service should not affect any other IMS supplementary service. Communication diversion.

NOTE: Every communication within the CONF service may be charged according to the normal communication procedures. Special arrangements (e.g. conference initiator may be charged for other parties’ communications in the conference) are out of scope of the present specification.

8.2.13.2.4 Originating Identification Restriction (OIR)

The OIR service shall take precedence as required in [4].

NOTE: A conference participant joining with an active OIR therefore has no details that can be included in any conference notifications.

8.2.13.2.5 Terminating Identification Restriction (TIR)

The TIR service shall take precedence as required in [4].

NOTE: A conference participant added with an active TIR therefore has no details that can be included in any conference notifications.

8.2.13.2.6 Three-Party (3PTY)

See clause 8.2.13.2.2, noting that 3PTY is a special case of CONF.

8.2.13.3 Interoperability with PSTN/ISDN and CS Mobile networks

The IMS Multimedia Telephony service shall support the interoperability of the CONF service with mobile CS and PSTN/ISDN Supplementary Services and vice‑versa. The scope of this interworking may result in a limited service capability.

8.2.14 Advice Of Charge (AOC)

8.2.14.1 Definition

AOC is a group of services as follows:

Advice Of Charge: charging information at communication Set-up time (AOC-S);

The advice of charge at communication set-up service provides the user with information about the charging rates at the time of communication establishment or during the communication in the case of charging rates changes. The charge information provided relates to the charges incurred on the network to which the served user is attached.

This service description is based on the service description described in [E-10] for AoC-S on a permanent mode.

Advice Of Charge: charging information During the communication (AOC-D);

The advice of charge during the communication service enables the user to receive information on the recorded charges for a communication during the active phase of the communication. The provided charging information may be exchanged between different operator domain if those operators have interconnect agreements to do so.

This service description is based on the service description described in [E-11] for AoC-S on a permanent mode.

Advice Of Charge: charging information at the End of the communication (AOC-E)

The advice of charge at end of communication service provides the user with charging information for a communication when the communication is terminated. Dependent on the option chosen at the time of subscription, the information can be sent for all communications, or on a per communication basis. The charge information provided relates to the charges incurred on the network to which the served user is attached.

This service description is based on the service description described in [E-12] for AoC-S on a permanent mode.

8.2.14.2 Service interactions with other IMS supplementary services

8.2.14.2.1 Diversion services

Originating party: No impact, i.e. this IMS supplementary service should not affect any other IMS supplementary service.

8.2.14.2.2 Completion of Communications to Busy Subscriber (CCBS)

Charging information shall be provided for the original communication, and for the resulting CCBS communication.

8.2.14.2.3 CONFerence (CONF)

No impact, i.e. neither IMS supplementary service shall affect the operation of the other IMS supplementary service.

8.2.14.3 Interoperability with PSTN/ISDN

The IMS shall support the interoperability of the AOC service with PSTN/ISDN Supplementary Services and vice‑versa. The scope of this interworking may result in a limited service capability.

8.2.15 Explicit Communication Transfer (ECT)

8.2.15.1 Definition

The Explicit Communication Transfer (ECT) service enables a party involved in a communication to transfer that communication to a third party.

There are two situations in which transfer shall be possible:

– The transferring party has no ongoing communication with the transfer Target (ECT Blind/Assured) then either:

a) the transferring party wants to perform the transfer without any further action on the transfer operation (ECT Blind),

b) the transferring party wants to have the possibility to act on the transfer operation progress (ECT Assured).

– The transferring party has a communication with the transfer Target (ECT Consultative).

ECT Blind/Assured:

The ECT Blind/Assured enables the transferring party A who has an active communication with a party B, which can be an incoming or outgoing communication, to transfer that communication into a new communication between party B and a third party C with out having prior communication with the third party C, and release it self from the communication.

Because of the blind call towards party C, it is not possible to know in advance the result of the transfer. Therefore, party A should be informed of the establishment state of the transfer before being released from the communication.

For Assured transfer, the transferring party A can limit the duration of the transfer attempt, release the transfer before it is completed or retrieve its communication with the transferee in case of transfer failure.

ECT Consultative:

The ECT Consulative enables a transferring party A to transform two of that party’s communications (e.g. an active communication and a communication on hold, to parties B and C), each of which can be an incoming communication or an outgoing communication, into a new communication between party B and party C.

Prior to transfer, the media session shall have been established on the communication between transferring party A and party B (transferee). On the communication between transferring party A and party C (transfer target), the media session shall have been established prior to transfer.

The service should be applicable independent of whether party B and party C are IMS users or not.

This service description is based on the service description described in [E-18].

The use of ECT on an emergency call, or a call identified as a callback to an emergency call, by a user that is not the PSAP, shall be precluded.

8.2.15.2 Service interactions with other IMS supplementary services

8.2.15.2.1 Identification services

8.2.15.2.1.1 Terminating Identification Restriction (TIR)

A terminating party’s restriction requirements from the original communication shall be used in order to restrict the presentation of that party’s identity to the other user in a transferred communication.

NOTE: If the media flow(s) is established on the communication to party C after transfer, the presentation of the identity of party C shall be restricted according to party C’s Terminating identification restriction service (i.e. as for the normal operation of the Terminating identification restriction service).

8.2.15.2.1.2 Originating Identification Presentation (OIP)

For ECT Blind, the transferee identity shall be presented to the transfer target subject to the transferee’s originating identification restriction service.

The transferring party identity may also be presented to the transfer target based on operator policy and terminal capability and subject to the transferring party’s originating identification restriction service.

8.2.15.2.1.3 Enhanced Calling Name (eCNAM)

The transferee eCNAM identity data shall be delivered to the transfer target subject to the transferee’s originating identification restriction service, and assuming the transfer target has eCNAM service.

The transferring party eCNAM identity data may also be delivered to the transfer target based on operator policy and terminal capability and subject to the transferring party’s originating identification restriction service.

8.2.15.2.2 Communication Barring (CB)

In case the transferring party A has outgoing communication barring active towards party C, transferring party As request for communication transfer of party B to party C shall also be barred, if it occurs in relation to the establishment of the communication to C.

For ECT Blind, if the transfer target has incoming communication barring active, the transferee identity shall be checked to apply the service restriction. The transferring party identity may also be checked with Communication Barring based on operator policy.

8.2.15.2.3 CONFerence (CONF)

The conference controller cannot transfer the conference to another party.

NOTE: Conferees can invoke the ECT service in order to transfer their connection to the conference to another party after that connection has been established.

8.2.15.2.4 Advice Of Charge (AOC)

8.2.15.2.4.0 General

This services does not apply to UE accessing from mobile 3GPP access networks.

8.2.15.2.4.1 Advice Of Charge at communication Set-up (AOC-S)

When party A transfers a communication, AOC-S shall be considered as completed.

For party B and party C, no impact, i.e. this IMS supplementary service should not affect any other IMS supplementary service.

8.2.15.2.4.2 Advice Of Charge During the communication (AOC-D)

When party A transfers a communication and has activated AOC-D, the charge up to that time shall be sent as a subtotal charge for that communication. The AOC-D service shall then be considered as completed.

NOTE: If party A had activated the AOC-D, then party A will receive information separately for both of the communications.

For party B and party C, no impact, i.e. this IMS supplementary service should not affect any other IMS supplementary service.

8.2.15.2.4.3 Advice Of Charge at the End of a communication (AOC-E)

If a party A is charged for the transferred part of the communication and has activated the AOC-E, then either:

a) the charging information shall be sent to party A when the transferred communication is terminated; or

b) when the communications are transferred, party A shall be informed that charging information is not available. The AOC-E shall then be considered as completed.

For party B and party C, no impact, i.e. this IMS supplementary service should not affect any other IMS supplementary service.

8.2.15.2.5 Explicit Communication Transfer (ECT)

The ECT service can be invoked simultaneously by any of the parties on an active communication, but this is not regarded as a normal situation. The network shall not explicitly prevent this occurring.

Therefore, both parties (party A and party B) in a normal communication, who have each subscribed to the ECT service, can simultaneously transfer the communication. That is, if party A and party B are involved in a communication on which the connection has been established, party A can transfer the communication to party C and party B can transfer the communication to another party.

NOTE: Mechanisms which prevent the ECT service from resulting in a connection which contains no parties able to terminate the communication may result in rejection of simultaneous requests to invoke the ECT service by the parties involved in the communication.

8.2.15.3 Interoperability with PSTN/ISDN and CS mobile networks

No restrictions.

8.2.16 Reverse charging

8.2.16.1 Definition

The reverse charging at communication set up time service allows the terminating party to be charged for the entire communication. Only usage based charges can be applied to the terminating party. The service shall be requested by the originating party at communication set up time. The terminating party must receive an explicit indication of a reverse charge communication request.

This service description is based on the service description described in [E-19].

8.2.16.2 Service interactions with other IMS supplementary services

None.

8.2.16.3 Interoperability with PSTN/ISDN

The IMS Multimedia Telephony service shall support the interoperability of Reverse Charging with the PSTN/ISDN and vice‑versa.

8.2.17 Closed User Group (CUG)

8.2.17.1 Definition

The CUG service enables users to form groups of members, whose communication profile is restricted for incoming and outgoing communications. Members of a specific CUG can communicate among themselves but not, in general, with users outside the group.

Specific CUG members can have additional capabilities that allow them to initiate outgoing communications to users outside the group, and/or to accept incoming communications from users outside the group. Specific CUG members can have additional restrictions that prevent outgoing communications to other members of the CUG, or prevent incoming communications from other members of the CUG.

A closed user group consists of a number of members from one or more public, and/or private networks. Identification of each member shall be according to the requirements in [8]. A specific user may be a member of one or more CUGs. Subscription to a closed user group shall be defined for all communication services, or in relation to one, or to a list of communication services.

This service description is based on the ISDN service description described in [E-22].

8.2.17.2 Service interactions with other IMS supplementary services

8.2.17.2.1 Diversion services

8.2.17.2.1.1 Communication Forwarding Unconditional (CFU)

CUG restrictions shall be checked and met for the communication between the originating party and the forwarding party. The information of a CUG applied by the IMS Multimedia Telephony service on the original communication shall be used for the communication forwarding and by this means CUG restrictions shall be checked and met for the communication between the originating party and the forwarded-to party.
In the case of multiple forwarding, CUG restrictions between the originating party and the forwarding party have to be checked and met at each intermediate forwarding point. In addition, CUG restrictions between the originating party and forwarded-to party shall be met end-to-end.

The outgoing communication barring information of the forwarding party shall not be used to determine whether the communication can be forwarded.

The CUG information sent to the "forwarded-to" destination shall the same CUG information of the originating party that was sent from the originating network.

8.2.17.2.1.2 Communication Forwarding Busy (CFB)

See interactions with CFU 8.2.17.2.1.1

8.2.17.2.1.3 Call Forwarding No Reply (CFNR)

See interactions with CFU 8.2.17.2.1.1

NOTE: CUG restrictions were checked and met for the communication between the originating party and the forwarding party when the communication was offered to the forwarding party.

8.2.17.2.1.4 Communication Forwarding on Not Logged-in (CFNL)

See interactions with CFU 8.2.17.2.1.1

8.2.17.2.1.5 Communication Forwarding on Subscriber Not Reachable (CFNRc).

See interactions with CFU 8.2.17.2.1.1

8.2.17.2.1.6 Communication Deflection (CD)

The information of a CUG applied on the original communication shall be used for the deflected part of the communication and by this means CUG restrictions shall be checked and met for the communication between the originating party and the deflected-to party.

In the case of multiple deflections, CUG restrictions between the originating party and the deflecting party have to be checked and met at each intermediate deflecting point. In addition, CUG restrictions between the originating party and deflected-to party shall be met end-to-end.
When a communication is deflected, a new check of the CUG restrictions between the originating party and the deflected-to party is made at the "deflected-to" destination. The CUG information sent to the "deflected-to" destination is the same CUG information of the originating party that was sent from the originating network.

The outgoing communication barring information of the deflecting party shall not be used to determine whether the communication can be deflected.

NOTE: CUG restrictions were checked and met for the communication between the originating party and the deflecting party when the communication was offered to the deflecting party.

8.2.17.2.2 Explicit Communication Transfer (ECT)

The two communications shall use the same CUG for the transfer to be successful.

NOTE: CUG restrictions between users will have been checked when the first communication is established. Similarly, CUG restrictions between users will have been checked when establishing the second communication.

8.2.17.2.3 Three-Party (3PTY)

For the successful invocation of the three party service any CUG restrictions applied to one communication shall match with any CUG restrictions applied to the other communication.

8.2.17.2.4 CONFerence (CONF)

When the communication involving the first conferee is added to the conference, then the conference shall assume the CUG of that communication.
In order to add a subsequent communication to the conference, then the CUG of that communication shall be checked against the CUG of the conference.

8.2.17.3 Interoperability with PSTN/ISDN

The IMS Multimedia Telephony service shall support the interoperability of the CUG service with the PSTN/ISDN and vice versa.No restrictions.

8.2.18 Three-Party (3PTY)

8.2.18.1 Definition

The 3PTY service enables a user to establish, participate in and control a simultaneous communication involving a number of users.

The 3PTY service can be invoked by the served user who is involved in at least two calls (one active communication and at least one held communication), each of which may be an incoming or outgoing communication.

The connections shall be established on each of the two communications prior to the invocation of the 3PTY service.

3PTY communication setup is equivalent to a three party conference created on request of the served user from existing communication sessions, this is equivalent to three party conference creation in CONF, For this reason 3PTY can be seen as a special case of CONF and most of service interactions for CONF apply also to 3PTY.

This service description is based on the service description described in [E-21].

8.2.18.2 Service interactions with other IMS supplementary services

8.2.18.2.1 Terminating Identification Presentation (OIR)

See clause 8.2.13.2.4, noting that 3PTY is a special case of CONF.

8.2.18.2.2 Terminating Identification Restriction (TIR)

See clause 8.2.13.2.5, noting that 3PTY is a special case of CONF.

8.2.18.2.3 Three-Party (3PTY)

A, B and C are in a three-way conversation that was created by B invoking the 3PTY service. A can create a second three-way conversation involving the original three-way conversation and D by invoking the 3PTY service.

8.2.18.2.4 CONFerence (CONF)

A, B and C are involved in a conference that was created by B invoking the CONF service. A can create a three-way conversation involving the original conference call and D by invoking the 3PTY service.

NOTE: It is FFS whether there is a conflict with the requirement expressed by 8.2.13.2.2, considering that 3PTY is just a special case of CONF.

8.2.18.3 Interoperability with PSTN/ISDN

The IMS Multimedia Telephony service shall support the interoperability of the 3PTY service with PSTN/ISDN supplementary service 3PTY and vice-versa. The scope of this interworking may result in a limited service capability.

8.2.19 Flexible Alerting (FA)

8.2.19.1 Definition

Flexible Alerting (FA) causes a call to a Pilot Identity to branch the call into several legs to alert several FA group members simultaneously or sequentially. In the simultaneous case, the first leg to be answered is connected to the calling party and the other call legs are abandoned. In the sequential case the order in which legs are alerted depends on application-specific criteria (including static preferences, last used device, last registered device).

FA group members are alerted by dialling the public addressable identity (e.g. Public User Identity) associated with the FA group (i.e., a E.164 number or a SIP URI), which is referred to as the Pilot Identity. The Pilot Identity maps to a set of public addressable identities (e.g. PUI or GRUU) where each identity references a member of the FA group. The FA group consists of a list of identities, and can be configured by the user or the operator.

In FA, there are two configuration options for busy indication: Single User Busy, and Multiple User Busy. The configuration of the option for a particular FA group shall be performed by the operator.

– For Single User Busy, the FA Group returns a busy indication if any group member indicates busy before the call is answered.

– For Multiple User Busy, the FA Group returns a busy indication if all accessible members indicate busy.

8.2.19.2 Service interactions with other IMS supplementary services

8.2.19.2.1 Identification services

8.2.19.2.1.1 Terminating Identification Presentation (TIP)

If an originating call from a user has TIP activated, the termination identification is the FA Pilot Identity.

8.2.19.2.1.2 Terminating Identification Restriction (TIR)

If the FA Pilot Identity has TIR activated, the termination identification is not presented.

8.2.19.2.1.3 Originating Identification Presentation (OIP)

If the FA Pilot Identity has OIP activated, incoming calls to the FA Pilot Identity apply OIP to the members of the FA group.

8.2.19.2.1.4 Originating Identification Restriction (OIR)

No impact, i.e. neither service shall affect the operation of the other service.

8.2.19.2.2 Diversion services

8.2.19.2.2.1 Communication Forwarding Unconditional (CFU)

CFU takes precedence over FA. CFU of the FA Pilot Identity shall apply to calls to the Pilot Identity when CFU is active.

CFU for the FA pilot identity takes precedence over CFU of the individual FA members. That is, if both the FA pilot identity and an FA member have CFU active, CFU treatment is determined by the FA pilot identity.

8.2.19.2.2.2 Communication Forwarding Busy (CFB)

CFB of the FA Pilot Identity shall apply to calls to the Pilot Identity when CFB is active and the FA group is considered to be busy.

CFB for the FA pilot identity takes precedence over CFB of the individual FA members. That is, if both the FA pilot identity and an FA member have CFB active, CFB treatment is determined by the FA pilot identity.

8.2.20 Personal Network Management (PNM)

8.2.20.1 Definition

Personal Network Management (PNM) as specified in TS22.259 allows a user to manage her UEs in regard to terminating services according to preferences set by the user, capabilities and availabilities of devices.

NOTE: Fixed network terminals could become subject of PNM

8.2.20.2 Service interactions with other IMS supplementary services

Invocation of supplementary services for terminating services applicable to the active UE take precedence over invocation of supplementary service applicable to the called UE. There is no impact on specified interaction among supplementary services once invoked.

There is no impact on the registration, erasure, activation, deactivation and interrogation of supplementary services.

8.2.21 Customized Alerting Tone (CAT)

8.2.21.1 Definition

The Customized Alerting Tone Service (CAT service) is an operator specific service by which an operator enables the subscriber to customize the alerting tone which is played to the calling party. The requirements for CAT within IMS shall be as described in [9].

8.2.21.2 Service interactions with other IMS supplementary services

8.2.21.2.1 Identification services

8.2.21.2.1.1 Originating Identification Restriction (OIR)

The interaction between CAT and the OIR supplementary services shall be as described in [9].

8.2.21.2.1.2 Terminating Identification Restriction (TIR)

The interaction between CAT and the TIR supplementary services shall be as described in [9].

8.2.21.2.2 Diversion services

8.2.21.2.2.1 Communication Forwarding Unconditional (CFU)

The interaction between CAT and the CFU supplementary services shall be as described in [9].

8.2.21.2.2.2 Communication Forwarding Busy (CFB)

The interaction between CAT and the CFU supplementary services shall be as described in [9].

8.2.21.2.2.3 Communication Forwarding on Not Reachable (CFNRc)

The interaction between CAT and the CFNRc supplementary services shall be as described in [9]

8.2.21.2.2.4 Communication Forwarding No Reply (CFNR)

The interaction between CAT and the CFNR supplementary services shall be as described in [9]

8.2.21.2.3 Communication Waiting (CW)

The interaction between CAT and the CW supplementary services shall be as described in [9].

8.2.21.2.4 Explicit Communication Transfer (ECT)

The interaction between CAT and the ECT supplementary services shall be as described in [9].

8.2.22 Customized Ringing Signal (CRS)

8.2.22.1 Definition

The Customized Ringing Signal (CRS service) is an operator specific service by which an operator enables the subscriber to customize the ringing signal which is played to the called party. The requirements for CRS within IMS shall be as described in [10].

8.2.22.2 Service interactions with other IMS supplementary services

8.2.22.2.1 Identification services

8.2.22.2.1.1 Originating Identification Restriction (OIR)

The interaction between CRS and the OIR supplementary services shall be as described in [10].

8.2.22.2.1.2 Originating Identification Presentation (OIP)

The interaction between CRS and the OIP supplementary services shall be as described in [10].

8.2.22.2.2 Diversion services

8.2.22.2.2.1 Communication Forwarding Unconditional (CFU)

The interaction between CRS and the CFU supplementary services shall be as described in [10].

8.2.22.2.2.2 Communication Forwarding Busy (CFB)

The interaction between CRS and the CFU supplementary services shall be as described in [10].

8.2.22.2.2.3 Communication Forwarding on Not Reachable (CFNRc)

The interaction between CRS and the CFNRc supplementary services shall be as described in [10]

8.2.22.2.2.4 Communication Forwarding No Reply (CFNR)

The interaction between CRS and the CFNR supplementary services shall be as described in [10]

8.2.22.2.3 Communication Waiting (CW)

The interaction between CRS and the CW supplementary services shall be as described in [10].

8.2.22.2.4 Explicit Communication Transfer (ECT)

The interaction between CRS and the ECT supplementary services shall be as described in [10].

8.2.23 Completion of Communications on No Reply (CCNR)

8.2.23.1 Definition

The CCNR service enables the originating party, encountering a terminating party who does not answer the communication (No Reply), to have the communication completed without having to make a new communication attempt when the terminating party becomes not busy after having initiated an activity.

When the originating party requests the CCNR service, the network will monitor for the terminating party becoming not busy after having initiated an activity.

When the terminating party becomes not busy after having initiated an activity, then the network will wait a short time in order to allow the resources to be re-used for originating a communication. If the resources are not re-used by the terminating party within this time, then the network will automatically recall the originating party.

When the originating party accepts the CCNR recall, then the network will automatically generate a CCNR call to the terminating party.

NOTE: A service provided to the terminating party which prevents the registration of CCNR requests is outside the scope of the present document.

During CCNR recall, information shall be provided which indicates a CCNR recall. The information provided in the original communication attempt shall be included in the CCNR recall.

This service description is based on the service description described in [E-23].

8.2.23.2 Service interactions with other IMS supplementary services

8.2.23.2.1 Identification services

8.2.23.2.1.1 Originating Identification Presentation (OIP)

No impact, i.e. neither service shall affect the operation of the other service.

NOTE: If the originating party accepts a CCNR recall, the resulting CCNR call is a basic communication and the terminating party can receive originating identification presentation.

8.2.23.2.1.2 Originating Identification Restriction (OIR)

No impact, i.e. neither service shall affect the operation of the other service.

NOTE: If the originating party has invoked originating identification restriction and the terminating party accepts a CCNR recall, then the resulting CCNR call is a basic communication and the terminating party will not receive the originating identification of the originating party.

8.2.23.2.1.3 Terminating Identification Presentation (TIP)

No impact, i.e. neither service shall affect the operation of the other service.

8.2.23.2.1.4 Terminating Identification Restriction (TIR)

No impact, i.e. neither service shall affect the operation of the other service.

8.2.23.2.2 Advice Of Charge services (AOC)

Charging information can be given for the original communication, and for the resulting CCNR communication.

8.2.23.2.3 Communication Waiting (CW)

CCNR requests in the CCNR queue of the terminating party shall only be processed if there are no communications waiting. In other situations there is no impact between the CW and the CCNR service.

8.2.23.2.4 Communication HOLD (HOLD)

No impact, i.e. neither supplementary service shall affect the operation of the other supplementary service.

NOTE 1: When receiving a CCNR recall indication, the originating party may invoke the communication hold service in order to make interface resources available for the establishment of the CCNR communication.

NOTE 2: When the originating party is busy or CCNR busy and is notified that the terminating party is not busy, invocation of the communication hold service will not result in the CCNR communication being established.

8.2.23.2.5 Explicit Communication Transfer (ECT)

No impact, i.e. neither service shall affect the operation of the other service.

8.2.23.2.6 Closed User Group (CUG)

Closed user group information from the original communication shall also be included in the CCNR communication.

NOTE: Closed user group information is not included in the check for a compatible terminal. If a terminal performs an internal closed user group check and uses the closed user group information provided on a communication to determine whether, or not, to inform the user of the incoming communication, then such a terminal may react positively to the check for a compatible terminal due to the absence of closed user group information, but due to the internal closed user group check such a terminal may then not inform the user of the arrival of the resulting CCNR call.

8.2.23.2.7 Completion of communications services

8.2.23.2.7.1 Completion of Communications to Busy Subscriber (CCBS)

A user can be both an originating party and a terminating party simultaneously, i.e. that user can have activated the CCNR service or the completion of communications to busy subscriber (CCBS) service and have CCNR requests or CCBS requests outstanding whilst at the same time that user can be the destination of CCNR requests or CCBS requests from other users.

CCBS requests and CCNR requests against the same terminating party shall be queued in the same queue.

If a user receives a CCNR recall or CCBS recall (i.e. as originating party) while that user’s queue as terminating party is being processed, then the CCNR recall or CCBS recall shall take priority over the handling of that user’s queue. The handling of CCNR requests and CCBS requests activated by this user (i.e. as originating party) shall have priority over the handling of CCNR requests and CCBS requests activated by other users on this user (i.e. as terminating party).

If one of the user’s CCNR requests can be processed, then this user (see first paragraph) shall be given a CCNR recall or notification as described in [E-23] clause 5. The served user’s terminating party idle guard timer, if running, shall be cancelled. The processing of CCBS requests shall be according to the requirements of the CCBS supplementary service.

If a network supports the option to retain CCNR requests (see [E-23] clause 5.3.3.1 b)), then CCBS requests shall be retained when a CCBS call encounters a busy destination.

If the network checks for identical requests in the user’s queue, the check shall include both CCNR requests and CCBS requests.

If an originating party has a CCBS recall pending on arrival of a CCNR recall, this should be treated in the same way as in the case where the originating party is CCNR busy (see [E-23] clause 5.2.3 and clause 5.3.3.2 b)).

8.2.23.2.7.2 Completion of Communications on No Reply (CCNR)

A user can be both a originating party and a terminating party simultaneously, i.e. that user can have activated the CCNR service and have CCNR requests outstanding whilst at the same time that user can be the destination of CCNR requests from other users.

If a user receives a CCNR recall while that user’s CCNR queue as terminating party is being processed, then the CCNR recall shall take priority over the handling of the CCNR queue. The handling of CCNR requests activated by this user shall have priority over the handling of CCNR requests activated by other users on this user.

If one of the user’s CCNR requests can be processed as a result, then this user (see first paragraph) shall be given a CCNR recall or notification as described in [E-23] clause 5. The served user’s terminating party idle guard timer, if running, shall be cancelled.

8.2.23.2.8 CONFerence (CONF)

No impact, i.e. neither supplementary service shall affect the operation of the other supplementary service.

8.2.23.2.9 Communication DIVersion (CDIV)

8.2.23.2.9.1 General

CCNR recalls shall not be diverted. They shall be given to the originating party at the originating party’s original location.

8.2.23.2.9.2 Communication Forwarding Unconditional (CFU)

For CFU activated by user B before user A requests CCNR:

– If user B has activated CFU, and the forwarded communication results in a communication completion on no reply condition at user C, user A shall be informed that CCNR is possible at user C. If user A activates CCNR and subsequently activates CFU, the CCNR recall shall be given to user A at his original location.
As a network option, in case of a diversion at user B, user A shall not be informed that CCNR is possible.

For CFU activated by user B after user A requests CCNR on user B:

– If user B activates CFU after user A has activated CCNR on user B, then the CCNR request shall be cancelled and a notification "CCNR cancelled" shall be sent to the user A.
As a network option, the CCNR request shall be suspended until user B deactivates CFU. If the service duration timer expires before user B deactivates CFU, the CCNR request shall be cancelled.

8.2.23.2.9.3 Communication Forwarding Busy (CFB)

For CFB activated by user B before user A requests CCNR:

– If user B has activated the communciation forwarding busy service and is busy, and the forwarded communication results in a call-completion on no reply condition at user C, user A shall be informed that CCNR is possible at user C.

For CFB activated by user B after user A requests CCNR on user B:

– If user B activates the communication forwarding busy service after user A has activated the CCNR service on user B, the communication forwarding busy service shall not be invoked for the CCNR communication.

8.2.23.2.9.4 Communication Forwarding No Reply (CFNR)

For CFNR activated by user B before user A requests CCNR:

– If user B has activated the communication forwarding on no reply service and does not answer the communication, and the forwarded communication results in a communication-completion on no reply condition at user C, user A shall be informed that CCNR is possible at user C.
As a network option, user A shall be informed that CCNR at user B is possible.

For CFNR activated by user B after user A requests CCNR on user B:

– If user B activates the communication forwarding on no reply service after user A has activated the communication forwarding on no reply service on user B, a CCNR communication from user A which encounters a no reply condition at user B shall be treated as follows:

– the procedures of CCNR shall be applied; or

– the communication shall be forwarded as a normal communication.

8.2.23.2.9.5 Communication Forwarding on Not Logged in (CFNL)

For CFNL activated by user B before user A requests CCNR:

– If user B has activated the communication forwarding not registered service and is not logged in, and the forwarded communication results in a communication completion on no reply condition at user C, user A shall be informed that CCNR is possible at user C.
As a network option, user A shall be informed that CCNR at user B is possible.

For CFNL activated by user B after user A requests CCNR on user B:

If user B activates the communication forwarding not registered service after user A has activated CCNR on user B, then the CC request shall be cancelled and a notification "CCNR cancelled" shall be sent to the user A.
As a network option, the CCNR request shall be suspended until user B deactivates CFNL. If the service duration timer expires before user B deactivates CFNL, the CCNR request shall be cancelled.

8.2.23.2.9.6 Communication Deflection (CD)

For the originating user A:

– If a communication to the called user B is deflected to user C by the CD service and results in a communication completion on no reply condition at user C, user A shall be informed that CCNR is possible at user C. A CCNR recall shall not be deflected.

For the called user B:

– A CCNR call shall not be deflected.

8.2.23.2.10 Malicious Communication IDentification (MCID)

No impact, i.e. neither service shall affect the operation of the other service.

8.2.23.2.11 Anonymous Communication Rejection and Communication Barring (ACR/CB)

No impact, i.e. neither service shall affect the operation of the other service.

8.2.23.2.12 Message Waiting Indication (MWI)

No impact, i.e. neither service shall affect the operation of the other service.

8.2.23.2.13 Flexible Alerting (FA)

No impact, i.e. neither service shall affect the operation of the other service.

8.2.23.2.14 Customized Alerting Tones (CAT)

No impact, i.e. neither service shall affect the operation of the other service.

8.2.23.3 Interoperability with PSTN/ISDN

The IMS Multimedia Telephony service shall support the interoperability of the CCNR service with PSTN/ISDN Supplementary Service CCNR and vice‑versa. The scope of this interworking may result in a limited service capability.

8.2.24 Enhanced Calling Name (eCNAM)

8.2.24.1 Definition and Scope

The eCNAM service [15] provides the terminating party with the eCNAM identity data of the originating party. The eCNAM identity data consists of a name and metadata. This service is available to a user only after subscription.

NOTE: The size of the eCNAM identity data can be up to 1000 characters.

The eCNAM service informs and protects terminating users from fraud attempts (e.g., fraudulent robocalls) through its retrieval, assembly and delivery of the call metadata together with the results of the Caller Identity Analytics function (defined in Section 3.1).

The Caller Identity Analytics function is expected to encompass the results of verification, such as the Secure Telephone Identity Revisited (STIR) [16] / Signature-based Handling of Asserted information using toKENs (SHAKEN) [17].

The eCNAM service combines its metadata and the results of the Caller Identity Analytics function so that the end user receives an all-inclusive display of the pertinent call information. As a result, the end user receives the eCNAM metadata, authentication and verification mechanisms, and the outcome of the Caller Identity Analytics in the same eCNAM message.

8.2.24.2 Service Requirements and Functionality

The terminating service provider shall extract the originating party’s telephone number from the originating party identity (e.g., from the tel-URI) to use in its query to retrieve eCNAM identity data from an authoritative data source. eCNAM identity data includes any information that allows the recipient to identify or contact the calling party, including the telephone number, name, logo.

The terminating service provider shall ensure that the received calling number is verified.

If the terminating service provider determines that the originating party’s telephone number is verified and OIR is not invoked, the terminating service provider shall retrieve the originating party’s eCNAM identity data.

If the originating party’s telephone number cannot be obtained, eCNAM identity data may not be available and the terminating service provider shall indicate the unavailability of the eCNAM identity data to the terminating party.

If the originating party’s telephone number cannot be verified, eCNAM identity data may not be displayed to the user. However, subject to service provider policy, the results of the Caller Identity Analytics function – if available – shall be included in the eCNAM message delivered to the UE.

The interface between the terminating service provider (eCNAM service) and the Caller Identity Analytics function shall be private and secure.

NOTE 1: The Caller Identity Analytics function is expected to have information (e.g., statistical and reputation) about the caller and/or the call that could be useful to the user. Therefore, even in the absence of a verification service, the delivery of this analytics information can protect the user against fraud and help service providers meet their regulatory obligations.

The terminating service provider shall obtain the eCNAM identity data from a trusted source. This trusted source may be the originating service provider or a third party with a business arrangement with the originating service provider.

The interface between the terminating service provider and the trusted data source shall be private and secure.

The conditions for exchange of data are governed by regional regulatory administration and through service provider agreement.

The terminating service provider’s delivery of originating party’s eCNAM identity data to the terminating party shall be subject to Originating Identification Restrictions (OIR).

If a terminating service provider requests a data element that the originating party did not consent to releasing, the data element shall not be returned.

NOTE 2: A trusted source contains subscriber identity information that is obtained directly from the subscriber’s communications service record, and is updated in near-real time with any changes in the subscriber’s service record. A subscriber’s communications service record is created when the user starts service with the service provider. The record contains information such as the name, address, billing information.

The service provider shall obtain its subscribers’ consent for elements listed on the subscriber’s communications service record at the start of communications service, and allow the subscriber to modify his/her consent at any point during the service.

NOTE 3: The metadata is intended to provide additional identity information about the originating party to the terminating party. The originating party’s privacy is a primary factor determining presentation of his/her metadata to the terminating party; no identity information is presented without his/her consent. Examples of the metadata include: the postal code, the preferred language, the business name and the business segment. The metadata delivered can vary from one service provider to another. The metadata offered by each service provider is subject to expansion and modifications over time, as more data or updated data becomes available about the originating party.

For the eCNAM service, the originating and terminating service providers shall agree on the retrievable metadata with the originating party’s consent based on regional regulations.

The eCNAM service shall support a service provider policy to establish the priority of delivering the identity data received from eCNAM query results and originating party identity data over any other data received from the originating party.

NOTE 4: OIP and eCNAM have the same level of priority.

3GPP systems shall support the delivery of the eCNAM identity data in multiple languages (e.g., Chinese). Semantic translation is outside the scope of this standard.

3GPP systems shall relay the eCNAM identity data from the trusted sources to the terminating party without modification.

NOTE 5: The purpose of the preceding two requirements is to deliver eCNAM in more languages, such as Chinese.However, this does not require the storage of the eCNAM data in multiple languages in the databases.

8.2.24.3 Service interactions with other IMS supplementary services

8.2.24.3.1 Identification Services

8.2.24.3.1.1 Originating Identification Presentation (OIP)

For users that subscribe to both OIP and eCNAM, both originating party identity and eCNAM identity data shall be delivered to the terminating party.

8.2.24.3.1.2 Originating Identification Restriction (OIR)

The requirements for presenting and withholding the originating party’s eCNAM identity data shall adhere to the rules described in [4] for the presentation of session originator identity.

If the originating party subscribed to or invokes OIR, eCNAM identity data shall not be delivered to the terminating party, including data elements that the originating party had consented to release.

Non-identifying information generated by the Caller Identity Analytics function to alert the user against possible fraud (e.g., “Known Scam”) can be delivered to the user on calls from anonymous (private) callers. It is therefore possible for the user to receive a display such as:

Private Number… "Known Scam"

8.2.24.3.2 Diversion Services

8.2.24.3.2.1 Communication Forwarding Unconditional (CFU)

When a communication has been forwarded and the forwarded-to party has been provided with the eCNAM service, the forwarded-to party shall receive the eCNAM identity data of the original originating party, if this originating party has not subscribed to or invoked the OIR service.

8.2.24.3.2.2 Communication Forwarding Busy (CFB)

Same as CFU.

8.2.24.3.2.3 Communication Forwarding No Reply (CFNR)

Same as CFU.

8.2.24.3.2.4 Communication Forwarding on Not Logged-in (CFNL)

Same as CFU.

8.2.24.3.2.5 Communication Deflection (CD)

When a communication has been deflected and the deflected-to party has been provided with the eCNAM service, the deflected-to party shall receive the eCNAM identity data of the original originating party, if this originating party has not subscribed to or invoked the OIR service.

8.2.24.3.2.6 Communication Forwarding on Subscriber Not Reachable (CFNRc)

Same as CFU.

8.2.24.3.3 Communication Waiting (CW)

If a terminating party has the eCNAM service active and is notified that an incoming communication is waiting, then this terminating party shall receive the eCNAM identity data of the originating party, if this originating party has not subscribed to or invoked the OIR service.

8.2.24.3.4 Completion of Communication to Busy Subscriber (CCBS)

The originating party’s eCNAM identity shall be transmitted to the CCBS customer’s UE when the terminating party becomes free and a CCBS communication is generated to the terminating party.

If the terminating party subscribed to or has invoked OIR, the terminating party eCNAM identity data shall not be delivered to the originating party.

8.2.24.3.5 Explicit Communication Transfer (ECT)

The transferee’s eCNAM identity data shall be delivered to the transfer target subject to the transferee’s OIR, and assuming the transfer target has eCNAM active.

The transferring party eCNAM identity data may also be delivered to the transfer target based on operator policy and terminal capability and subject to the transferring party’s OIR.

8.2.24.4 Interoperability with PSTN/ISDN and mobile CS services

The IMS Multimedia Telephony service shall support the interoperability of the eCNAM service with mobile CS and PSTN/ISDN Supplementary Service CLIP. The eCNAM service shall utilize only the calling number originating from the PSTN to obtain the originating party’s eCNAM identity data.

eCNAM is not offered in the PSTN.

8.2A Supplementary Services applicable to IMS Multimedia Telephony without equivalent in non-IMS networks

8.2A.1 Completion of Communications on Not Logged-in (CCNL)

8.2A.1.1 Definition

The CCNL service enables the originating party, encountering a terminating party who is not registered, to have the communication completed without having to make a new communication attempt when the terminating party registers again.

When the originating party requests the CCNL service, the network will monitor for the terminating party registering again.

As a service provider option only originating parties who are listed in the terminating party’s whitelist are allowed to request the CCNL service.

NOTE: The administration of the terminating party’s whitelist is out of scope of this document.

When the terminating party registers again, then the network will wait a short time in order to allow the terminating party to originate a communication. If no communication is originated by the terminating party within this time, then the network will automatically recall the originating party. As a service provider option the terminating user’s acceptance of the CCNL request shall be required before the originating party will be recalled. When the originating party accepts the CCNL recall, then the network will automatically generate a CCNL call to the terminating party.

When the terminating party is busy or not logged-in upon arrival of the CCNL call, the original CCNL request shall retain its position in the queue, and the remaining period in which the CCNL request remains valid shall not be changed by this event.

During CCNL recall, information shall be provided which indicates a CCNL recall. The information provided in the original communication attempt shall be included in the CCNL recall.

8.2A.1.2 Service interactions with other IMS supplementary services

8.2A.1.2.1 Identification services

8.2A.1.2.1.1 Originating Identification Presentation (OIP)

No impact, i.e. neither service shall affect the operation of the other service.

NOTE: If the originating party accepts a CCNL recall, the resulting CCNL call is a basic communication and the terminating party can receive originating identification presentation.

8.2A.1.2.1.2 Originating Identification Restriction (OIR)

No impact, i.e. neither service shall affect the operation of the other service.

NOTE: If the originating party has invoked originating identification restriction and the terminating party accepts a CCNL recall, then the resulting CCNL call is a basic communication and the terminating party will not receive the originating identification of the originating party.

8.2A.1.2.1.3 Terminating Identification Presentation (TIP)

No impact, i.e. neither service shall affect the operation of the other service.

8.2A.1.2.1.4 Terminating Identification Restriction (TIR)

No impact, i.e. neither service shall affect the operation of the other service.

8.2A.1.2.2 Advice Of Charge services (AOC)

Charging information can be given for the original communication, and for the resulting CCNL communication.

8.2A.1.2.3 Communication Waiting (CW)

CCNL requests in the CCNL queue of the terminating party shall only be processed if there are no communications waiting. In other situations there is no impact between the CW and the CCNL service.

8.2A.1.2.4 Communication HOLD (HOLD)

No impact, i.e. neither supplementary service shall affect the operation of the other supplementary service.

NOTE 1: When receiving a CCNL recall indication, the originating party may invoke the communication hold service in order to make interface resources available for the establishment of the CCNL communication.

NOTE 2: When the originating party is busy or CCNL busy and is notified that the terminating party is available, invocation of the communication hold service will not result in the CCNL communication being established.

8.2A.1.2.5 Explicit Communication Transfer (ECT)

No impact, i.e. neither service shall affect the operation of the other service.

8.2A.1.2.6 Closed User Group (CUG)

Closed user group information from the original communication shall also be included in the CCNL communication.

8.2A.1.2.7 Completion of communications services (CC)

The following Completion of Communications services are defined: Completion of Communications to Busy Subscriber (CCBS), Completion of Communications on No Reply (CCNR) and Completion of Communications on Not Logged-in (CCNL)

A user can be both an originating party and a terminating party simultaneously, i.e. that user can have activated CC services and have CC requests outstanding whilst at the same time that user can be the destination of CC requests from other users.

CC requests against the same terminating party shall be queued in the same queue.

If a user receives a CCNL recall (i.e. as originating party) while that user’s queue as terminating party is being processed, then the CCNL recall shall take priority over the handling of that user’s queue. The handling of CCNL requests activated by this user (i.e. as originating party) shall have priority over the handling of CC requests activated by other users on this user (i.e. as terminating party).

If one of the user’s CCNL requests can be processed, then this user shall be given a CCNL recall or a notification. The served user’s terminating party idle guard timer, if running, shall be cancelled. The processing of CCBS or CCNR requests shall be according to the requirements of the CCBS or CCNR supplementary services.

If the network checks for identical requests in the user’s queue, the check shall include CCNL, CCNR and CCBS requests.

If an originating party has a CCBS or CCNR recall pending on arrival of a CCNL recall, this should be treated in the same way as in the case where the originating party is CCNL busy. In this case, the CCNL request shall be suspended until user A becomes neither busy nor CCNL busy.

8.2A.1.2.8 CONFerence (CONF)

No impact, i.e. neither supplementary service shall affect the operation of the other supplementary service.

8.2A.1.2.9 Communication DIVersion (CDIV)

8.2A.1.2.9.1 General

CCNL recalls shall not be diverted.

8.2A.1.2.9.2 Communication Forwarding Unconditional (CFU)

For CFU activated by user B before user A requests CCNL:

– If user B has activated CFU, and the forwarded communication results in a communication completion on not logged-in condition at user C, user A shall be informed that CCNL is possible at user C. If user A activates CCNL and subsequently activates CFU, the CCNL recall shall be given to user A.
As a network option, in case of a diversion at user B, user A shall not be informed that CCNL is possible.

For CFU activated by user B after user A requests CCNL on user B:

– If user B activates CFU after user A has activated CCNL on user B, then the CCNL request shall be cancelled and a notification "CCNL cancelled" shall be sent to the user A.
As a network option, the CCNL request shall be suspended until user B deactivates CFU. If the service duration timer e2Apires before user B deactivates CFU, the CCNL request shall be cancelled.

8.2A.1.2.9.3 Communication Forwarding Busy (CFB)

For CFB activated by user B before user A requests CCNL:

– If user B has activated the communication forwarding busy service and is busy, and the forwarded communication results in a call-completion on not logged-in condition at user C, user A shall be informed that CCNL is possible at user C.
As a network option, in case of a diversion at user B, user A shall not be informed that CCNL is possible.

For CFB activated by user B after user A requests CCNL on user B:

– If user B activates the communication forwarding busy service after user A has activated the CCNL service on user B, the communication forwarding busy service shall not be invoked for the CCNL communication.

8.2A.1.2.9.4 Communication Forwarding No Reply (CFNR)

For CFNR activated by user B before user A requests CCNL:

– If user B has activated the communication forwarding on no reply service and does not answer the communication, and the forwarded communication results in a communication-completion on not logged-incondition at user C, user A shall be informed that CCNL is possible at user C.
As a network option, in case of a diversion at user B, user A shall not be informed that CCNL is possible.

For CFNR activated by user B after user A requests CCNL on user B:

If user B activates the communication forwarding on no reply service after user A has activated CCNL on user B, then the CCNL request shall be cancelled and a notification "CCNL cancelled" shall be sent to the user A.
As a network option, the CCNL request shall be suspended until user B deactivates CFNR. If the service duration timer e2Apires before user B deactivates CFNR, the CCNL request shall be cancelled.

8.2A.1.2.9.5 Communication Forwarding on Not Logged in (CFNL)

For CFNL activated by user B before user A requests CCNL:

– If user B has activated the communication forwarding not registered service and is not logged in, and the forwarded communication results in a communication completion on not logged-in condition at user C, user A shall be informed that CCNL is possible at user C.
As a network option, user A shall be informed that CCNL at user B is possible.

For CFNL activated by user B after user A requests CCNL on user B:

– If user B activates the communication forwarding not registered service after user A has activated the communication forwarding on not logged-in service on user B, a CCNL communication from user A which encounters a not logged in condition at user B shall be treated as follows:

– the procedures of CCNL shall be applied; or

– the communication shall be forwarded as a normal communication.

8.2A.1.2.9.6 Communication Deflection (CD)

For the originating user A:

– If a communication to the called user B is deflected to user C by the CD service and results in a communication completion on not logged-in condition at user C, user A shall be informed that CCNL is possible at user C. A CCNL recall shall not be deflected.

For the called user B:

– A CCNL call shall not be deflected.

8.2A.1.2.10 Malicious Communication IDentification (MCID)

No impact, i.e. neither service shall affect the operation of the other service.

8.2A.1.2.11 Anonymous Communication Rejection and Communication Barring (ACR/CB)

No impact, i.e. neither service shall affect the operation of the other service.

8.2A.1.2.12 Message Waiting Indication (MWI)

No impact, i.e. neither service shall affect the operation of the other service.

8.2A.1.2.13 Flexible Alerting (FA)

No impact, i.e. neither service shall affect the operation of the other service.

8.2A.1.2.14 Customized Alerting Tones (CAT)

No impact, i.e. neither service shall affect the operation of the other service.

8.2A.1.3 Interoperability with PSTN/ISDN

Not applicable.

8.3 Concepts associated with IMS supplementary services

8.3.1 Administration of supplementary services

Provision, Withdrawal, Registration, Erasure, Activation, Deactivation and Invocation shall be as defined in ITU-T Recommendation I.210 [5].

Users shall be able to register, activate, deactivate, withdraw, interrogate and reconfigure IMS supplementary services via the UE, or web portals.

8.3.2 Unstructured SS data operations

The Multimedia Telephony Service shall provide a consistent service experience to the user for mobile initiated USSD operations in MMI mode and reserved for HPLMN use, according to TS 22.090 [12].

8.3.3 Network Announcement and Tones Insertion

The Multimedia Telephony Service shall be able to play network announcements or tones to the subscriber at any time during a session.

If there is an appropriate bilateral agreement, the home network shall be able to instruct the visited network to play a network announcement or tone to the subscriber at any time during a session.

When the UE locally renders the supervisory tones, the UE should follow the procedure indicated in Annex A.2 applicable for the home operator network of the UE in particular within a mobile network. The UE shall not locally render tones to indicate diversion or queueing of calls.

8.4 Use of authorization option in relation to IMS supplementary services

8.4.1 Definition

Some IMS supplementary services (e.g. communication session barring) can be offered to a user with the subscription option of authorization to control the service. When this option is selected, every action (related to that IMS supplementary service), such as registration, erasure, activation or deactivation is performed by the user with concurrent authentication.

For IMS supplementary services requiring authorization by user authentication, the service experience for the user shall be consistent with the procedures defined in TS 22.030 [14] for password based supplementary service management.

8.4.2 Description

When the subscription option authorized control of a IMS supplementary service is provided, authentication handling is supported by the network.

8.4.3 Management – normal procedures and successful outcome

8.4.3.1 Provision of authorization

Each IMS supplementary service which requires authorization to control this service may be offered with the subscription option authorized control of the IMS supplementary service. The values of this option may be:

user authentication;
by the service provider.

8.4.3.2 Withdrawal of authorization

Authorization may be withdrawn for administrative reasons or due to subscription modification.

8.4.3.3 Authentication requirements

The network shall provide, and allow the user to maintain, the authentication credentials.