Tech-invite3GPPspaceIETF RFCsSIP
Quick21222324252627282931323334353637384‑5x

Content for  TS 22.173  Word version:  17.3.0

Top   Top   Up   Prev   Next
1…   8…   8.2.8…   8.2.16…   8.2A…   A…   C…   E…

 

8  Supplementary Servicesp. 15

8.1  Generalp. 15

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.
Up

8.2  Supplementary Services applicable to IMS Multimedia Telephonyp. 15

8.2.1  Originating Identification Presentation (OIP)p. 15

8.2.1.1  Definition |R8|p. 15

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 TS 22.228.

8.2.1.2  Service interactions with other IMS supplementary services |R8|p. 16

8.2.1.2.1  Identification servicesp. 16
8.2.1.2.1.1  Originating Identification Restriction (OIR) p. 16
The requirements for the interactions between presenting and withholding the originating party's identity shall be as described in TS 22.228.
8.2.1.2.1.2  Enhanced Calling Name p. 16
For users that subscribe to both OIP and eCNAM, originating party identity and eCNAM identity data shall be delivered to the terminating party.
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 a trusted data source.
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.
Up
8.2.1.2.2  Diversion servicesp. 16
8.2.1.2.2.1  Communication Forwarding Unconditional (CFU) p. 16
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) p. 16
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.3  Communication Forwarding No Reply (CFNR) p. 16
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.4  Communication Forwarding on Not Logged-in (CFNL) p. 16
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.5  Communication Deflection (CD) p. 16
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) p. 17
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.7Void
8.2.1.2.3  Communication Waiting (CW)p. 17
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 |R8|p. 17

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)p. 17

8.2.2.1  Definition |R8|p. 17

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 TS 22.228. Those requirements also allow certain terminating party to override the restriction (override capability).

8.2.2.2  Service interactions with other IMS supplementary services |R8|p. 17

8.2.2.2.1  Identification servicesp. 17
8.2.2.2.1.1  Originating Identification Presentation (OIP) p. 17
The requirements for the interactions between presenting and withholding the originating parties' identity shall be as described in TS 22.228.
8.2.2.2.1.2  Enhanced Calling Name p. 17
The requirements for interactions between presenting and withholding the originating party's eCNAM identity data shall adhere to the rules described in TS 22.228 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 servicesp. 17
8.2.2.2.2.1  Communication Forwarding Unconditional (CFU) p. 17
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) p. 17
Same as for CFU.
8.2.2.2.2.3  Communication Forwarding No Reply (CFNR) p. 18
Same as for CFU.
8.2.2.2.2.4  Communication Forwarding on Not Logged-in (CFNL) p. 18
Same as for CFU.
8.2.2.2.2.5  Communication Deflection (CD) p. 18
Same as for CFU.
8.2.2.2.2.6  Communication Forwarding on Subscriber Not Reachable (CFNRc) p. 18
Same as for CFU.
8.2.2.2.2.7Void
8.2.2.2.3  Explicit Communication Transfer (ECT)p. 18
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 |R8|p. 18

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.
Up

8.2.3  Terminating Identification Presentation (TIP)p. 18

8.2.3.1  Definition |R8|p. 18

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 TS 22.228.

8.2.3.2  Service interactions with other IMS supplementary services |R8|p. 18

8.2.3.2.1  Identification servicesp. 18
8.2.3.2.1.1  Terminating identification presentation restriction p. 18
The requirements for the interactions between presenting and withholding the terminating party's identity shall be as described in TS 22.228.
8.2.3.2.2  Diversion servicesp. 18
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 |R8|p. 19

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)p. 19

8.2.4.1  Definition |R8|p. 19

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 TS 22.228. 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].
Up

8.2.4.2  Service interactions with other IMS Multimedia Telephony services |R8|p. 19

8.2.4.2.1  Identification servicesp. 19
8.2.4.2.1.1  Terminating Identification Presentation (TIP) p. 19
The requirements for the interactions between presenting and withholding the terminating party's identity shall be as described in TS 22.228.

8.2.4.3  Interoperability with PSTN/ISDN and mobile CS Networks |R8|p. 19

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)p. 19

8.2.5.1  Definition |R8|p. 19

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.
Up

8.2.5.2  Service interactions with other IMS supplementary services |R8|p. 20

8.2.5.2.1  Diversion Servicesp. 20
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) p. 20
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) p. 20
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)p. 20
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)p. 20
The conference controller cannot invoke the malicious call identification IMS supplementary service for participants within the conference.
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.
Up
8.2.5.2.4  Three-Party (3PTY)p. 20
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 |R8|p. 20

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)p. 20

8.2.6.1  Definition |R8|p. 20

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.
Up

8.2.6.2  Service interactions with other IMS supplementary services |R8|p. 21

8.2.6.2.1  Identification Servicesp. 21
8.2.6.2.1.1  Originating Identification Presentation (OIP) p. 21
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) p. 21
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 Servicesp. 21
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.
Up
8.2.6.2.2.1  Communication Forwarding Unconditional (CFU) p. 21
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) p. 21
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) p. 21
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.
8.2.6.2.2.4  Communication Forwarding on Not Logged-in (CFNL) p. 22
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) p. 22
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)p. 22
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)p. 22
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:
  1. 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.
  2. 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.
Up

8.2.6.3  Interoperability with PSTN/ISDN |R8|p. 22

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)p. 22

8.2.7.1  Definition |R8|p. 22

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.
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-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.
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-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).
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.
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.
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-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.
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.
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.
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.
Up

8.2.7.2Void

8.2.7.3  Service interactions with other IMS supplementary services |R8|p. 25

8.2.7.3.1  Identification servicesp. 25
8.2.7.3.1.1  Originating Identification Presentation (OIP) p. 25
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) p. 25
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) p. 25
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) p. 25
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) p. 25
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)p. 25
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)p. 25
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 servicesp. 25
8.2.7.3.4.1  Communication Forwarding Unconditional (CFU) p. 25
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.
Up
8.2.7.3.4.2  Communication Forwarding Busy (CFB) p. 26
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.
Up
8.2.7.3.4.3  Communication Forwarding No Reply (CFNR) p. 26
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.
Communication Forwarding on Subscriber Not Reachable (CFNRc):
No impact, i.e. this IMS supplementary service should not affect any other IMS supplementary service.
Up
8.2.7.3.4.4  Communication Forwarding on Not Logged-in (CFNL) p. 26
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.
Up
8.2.7.3.4.5  Communication Deflection (CD) p. 27
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.
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.
Up
8.2.7.3.4.6  Communication Forwarding on Subscriber Not Reachable (CFNRc) p. 27
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)
Up
8.2.7.3.4.7Void
8.2.7.3.5  Communication Waiting (CW)p. 28
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.
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.
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.
Up
8.2.7.3.6  Communication Barring (CB)p. 28
8.2.7.3.6.1  Outgoing communication barring-fixed p. 28
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.
Up
8.2.7.3.6.2  Outgoing communication barring-user controlled p. 28
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.
Up
8.2.7.3.7  Completion of Communications to Busy Subscriber (CCBS)p. 29
CCBS recalls shall never be diverted. They shall be provided to the original originating party.
8.2.7.3.8  Advice Of Charge (AOC)p. 29
8.2.7.3.8.1  Charging information at the End of the communication (AOC-E) p. 29
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".
Up

8.2.7.4  Interoperability with PSTN/ISDN and CS mobile networks |R8|p. 29

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.

Up   Top   ToC