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.2.16  Reverse charging |R8|p. 40

8.2.16.1  Definitionp. 40

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

8.2.16.2  Service interactions with other IMS supplementary servicesp. 40

None.

8.2.16.3  Interoperability with PSTN/ISDNp. 40

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) |R8|p. 40

8.2.17.1  Definitionp. 40

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

8.2.17.2  Service interactions with other IMS supplementary servicesp. 41

8.2.17.2.1  Diversion servicesp. 41
8.2.17.2.1.1  Communication Forwarding Unconditional (CFU)p. 41
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.
Up
8.2.17.2.1.2  Communication Forwarding Busy (CFB)p. 41
See interactions with CFU 8.2.17.2.1.1
8.2.17.2.1.3  Call Forwarding No Reply (CFNR)p. 41
See interactions with CFU 8.2.17.2.1.1
8.2.17.2.1.4  Communication Forwarding on Not Logged-in (CFNL)p. 41
See interactions with CFU 8.2.17.2.1.1
8.2.17.2.1.5  Communication Forwarding on Subscriber Not Reachable (CFNRc).p. 41
See interactions with CFU 8.2.17.2.1.1
8.2.17.2.1.6  Communication Deflection (CD)p. 41
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.
Up
8.2.17.2.2  Explicit Communication Transfer (ECT)p. 42
The two communications shall use the same CUG for the transfer to be successful.
8.2.17.2.3  Three-Party (3PTY)p. 42
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)p. 42
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/ISDNp. 42

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) |R8|p. 42

8.2.18.1  Definitionp. 42

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

8.2.18.2  Service interactions with other IMS supplementary servicesp. 42

8.2.18.2.1  Terminating Identification Presentation (OIR)p. 42
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)p. 42
See clause 8.2.13.2.5, noting that 3PTY is a special case of CONF.
8.2.18.2.3  Three-Party (3PTY)p. 43
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)p. 43
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.

8.2.18.3  Interoperability with PSTN/ISDNp. 43

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) |R8|p. 43

8.2.19.1  Definitionp. 43

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

8.2.19.2  Service interactions with other IMS supplementary servicesp. 43

8.2.19.2.1  Identification servicesp. 43
8.2.19.2.1.1  Terminating Identification Presentation (TIP) p. 43
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) p. 43
If the FA Pilot Identity has TIR activated, the termination identification is not presented.
8.2.19.2.1.3  Originating Identification Presentation (OIP) p. 43
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) p. 43
No impact, i.e. neither service shall affect the operation of the other service.
8.2.19.2.2  Diversion servicesp. 44
8.2.19.2.2.1  Communication Forwarding Unconditional (CFU) p. 44
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) p. 44
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) |R8|p. 44

8.2.20.1  Definitionp. 44

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.

8.2.20.2  Service interactions with other IMS supplementary servicesp. 44

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) |R8|p. 44

8.2.21.1  Definitionp. 44

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 servicesp. 44

8.2.21.2.1  Identification servicesp. 44
8.2.21.2.1.1  Originating Identification Restriction (OIR) p. 44
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) p. 44
The interaction between CAT and the TIR supplementary services shall be as described in [9].
8.2.21.2.2  Diversion servicesp. 45
8.2.21.2.2.1  Communication Forwarding Unconditional (CFU) p. 45
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) p. 45
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) p. 45
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) p. 45
The interaction between CAT and the CFNR supplementary services shall be as described in [9]
8.2.21.2.3  Communication Waiting (CW)p. 45
The interaction between CAT and the CW supplementary services shall be as described in [9].
8.2.21.2.4  Explicit Communication Transfer (ECT)p. 45
The interaction between CAT and the ECT supplementary services shall be as described in [9].

8.2.22  Customized Ringing Signal (CRS) |R8|p. 45

8.2.22.1  Definitionp. 45

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 servicesp. 45

8.2.22.2.1  Identification servicesp. 45
8.2.22.2.1.1  Originating Identification Restriction (OIR) p. 45
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) p. 45
The interaction between CRS and the OIP supplementary services shall be as described in [10].
8.2.22.2.2  Diversion servicesp. 45
8.2.22.2.2.1  Communication Forwarding Unconditional (CFU) p. 45
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) p. 45
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) p. 46
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) p. 46
The interaction between CRS and the CFNR supplementary services shall be as described in [10]
8.2.22.2.3  Communication Waiting (CW)p. 46
The interaction between CRS and the CW supplementary services shall be as described in [10].
8.2.22.2.4  Explicit Communication Transfer (ECT)p. 46
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) |R9|p. 46

8.2.23.1  Definitionp. 46

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

8.2.23.2  Service interactions with other IMS supplementary servicesp. 46

8.2.23.2.1  Identification servicesp. 46
8.2.23.2.1.1  Originating Identification Presentation (OIP)p. 46
No impact, i.e. neither service shall affect the operation of the other service.
8.2.23.2.1.2  Originating Identification Restriction (OIR)p. 46
No impact, i.e. neither service shall affect the operation of the other service.
8.2.23.2.1.3  Terminating Identification Presentation (TIP)p. 47
No impact, i.e. neither service shall affect the operation of the other service.
8.2.23.2.1.4  Terminating Identification Restriction (TIR)p. 47
No impact, i.e. neither service shall affect the operation of the other service.
8.2.23.2.2  Advice Of Charge services (AOC)p. 47
Charging information can be given for the original communication, and for the resulting CCNR communication.
8.2.23.2.3  Communication Waiting (CW)p. 47
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)p. 47
No impact, i.e. neither supplementary service shall affect the operation of the other supplementary service.
Up
8.2.23.2.5  Explicit Communication Transfer (ECT)p. 47
No impact, i.e. neither service shall affect the operation of the other service.
8.2.23.2.6  Closed User Group (CUG)p. 47
Closed user group information from the original communication shall also be included in the CCNR communication.
Up
8.2.23.2.7  Completion of communications servicesp. 47
8.2.23.2.7.1  Completion of Communications to Busy Subscriber (CCBS)p. 47
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 equests 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)).
Up
8.2.23.2.7.2  Completion of Communications on No Reply (CCNR)p. 48
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.
Up
8.2.23.2.8  CONFerence (CONF)p. 48
No impact, i.e. neither supplementary service shall affect the operation of the other supplementary service.
8.2.23.2.9  Communication DIVersion (CDIV)p. 48
8.2.23.2.9.1  Generalp. 48
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)p. 48
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.
Up
8.2.23.2.9.3  Communication Forwarding Busy (CFB)p. 48
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.
Up
8.2.23.2.9.4  Communication Forwarding No Reply (CFNR)p. 49
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.
Up
8.2.23.2.9.5  Communication Forwarding on Not Logged in (CFNL)p. 49
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.
Up
8.2.23.2.9.6  Communication Deflection (CD)p. 49
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)p. 49
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)p. 49
No impact, i.e. neither service shall affect the operation of the other service.
8.2.23.2.12  Message Waiting Indication (MWI)p. 49
No impact, i.e. neither service shall affect the operation of the other service.
8.2.23.2.13  Flexible Alerting (FA)p. 49
No impact, i.e. neither service shall affect the operation of the other service.
8.2.23.2.14  Customized Alerting Tones (CAT)p. 50
No impact, i.e. neither service shall affect the operation of the other service.

8.2.23.3  Interoperability with PSTN/ISDNp. 50

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) |R15|p. 50

8.2.24.1  Definition and Scopep. 50

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

8.2.24.2  Service Requirements and Functionalityp. 50

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

8.2.24.3  Service interactions with other IMS supplementary servicesp. 51

8.2.24.3.1  Identification Servicesp. 51
8.2.24.3.1.1  Originating Identification Presentation (OIP) p. 51
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) p. 51
The requirements for 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 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"
Up
8.2.24.3.2  Diversion Servicesp. 52
8.2.24.3.2.1  Communication Forwarding Unconditional (CFU) p. 52
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) p. 52
Same as CFU.
8.2.24.3.2.3  Communication Forwarding No Reply (CFNR) p. 52
Same as CFU.
8.2.24.3.2.4  Communication Forwarding on Not Logged-in (CFNL) p. 52
Same as CFU.
8.2.24.3.2.5  Communication Deflection (CD) p. 52
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) p. 52
Same as CFU.
8.2.24.3.3  Communication Waiting (CW)p. 52
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)p. 52
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)p. 52
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 servicesp. 53

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.

Up   Top   ToC