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.8  Communication Waiting (CW)p. 29

8.2.8.1  Definition |R8|p. 29

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

8.2.8.2  Service interactions with other IMS supplementary services |R8|p. 29

8.2.8.2.1  Anonymous Communication Rejection (ACR)p. 29
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.8.2.1a  Enhanced Calling Name (eCNAM) |R15|p. 30
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 servicesp. 30
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)p. 30
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 |R8|p. 30

No requirements.

8.2.9  Communication HOLD (HOLD)p. 30

8.2.9.1  Definition |R8|p. 30

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

8.2.9.2  Service interactions with other IMS supplementary services |R8|p. 30

8.2.9.2.1  CONFerence (CONF)p. 30
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)p. 30
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 |R8|p. 30

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

8.2.10.1  Definition |R8|p. 31

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

8.2.10.2  Service interactions with other IMS supplementary services |R8|p. 32

8.2.10.2.1  Diversion servicesp. 32
8.2.10.2.1.1  Communication Forwarding Unconditional (CFU) p. 32
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..
Up
8.2.10.2.1.2  Communication Forwarding Busy (CFB) p. 32
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.
Up
8.2.10.2.1.3  Communication Forwarding No Reply (CFNR) p. 32
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.
Up
8.2.10.2.1.4  Communication Forwarding on Not Logged-in (CFNL) p. 33
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.
Up
8.2.10.2.1.5  Communication Deflection (CD) p. 33
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 |R8|p. 33

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

8.2.11.1  Definitionp. 33

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

8.2.11.2  Service interactions with other IMS supplementary services |R8|p. 34

8.2.11.2.1  Identification servicesp. 34
8.2.11.2.2  Anonymous Communication Rejection (ACR)p. 34
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.
Up
8.2.11.2.3  Communication DIVersion (CDIV)p. 34
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)p. 34
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)p. 34
No impact, i.e. this IMS supplementary service should not affect any other IMS supplementary service.
8.2.11.2.6  Communication Barring (CB)p. 34
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)p. 34
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.
Up
8.2.11.2.8  Advice Of Charge services (AOC)p. 35
Charging information can be provided for the original communication, and for the resulting CCBS communication.
8.2.11.2.9  Enhanced Calling Name (eCNAM) |R15|p. 35
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 |R8|p. 35

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

8.2.12.1  Definitionp. 35

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

8.2.12.2  Service interactions with other servicesp. 35

8.2.12.2.1  Diversion servicesp. 35
8.2.12.2.1.1  Communication Forwarding Unconditional (CFU) p. 35
The MWI shall never be diverted.
8.2.12.2.1.2  Communication Forwarding Busy (CFB) p. 35
Same as CFU.
8.2.12.2.1.3  Communication Forwarding No Reply (CFNR) p. 35
Same as CFU.
8.2.12.2.1.4  Communication Forwarding on Not Logged-in (CFNL) p. 35
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 networksp. 36

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

8.2.13  CONFerence (CONF) |R8|p. 36

8.2.13.1  Definitionp. 36

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

8.2.13.2  Service interactions with other IMS supplementary servicesp. 36

8.2.13.2.1  Diversion servicesp. 36
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)p. 36
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)p. 36
No impact, i.e. this IMS supplementary service should not affect any other IMS supplementary service. Communication diversion.
8.2.13.2.4  Originating Identification Restriction (OIR)p. 36
The OIR service shall take precedence as required in TS 22.228.
8.2.13.2.5  Terminating Identification Restriction (TIR)p. 36
The TIR service shall take precedence as required in TS 22.228.
8.2.13.2.6  Three-Party (3PTY)p. 37
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 networksp. 37

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

8.2.14.1  Definitionp. 37

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

8.2.14.2  Service interactions with other IMS supplementary servicesp. 37

8.2.14.2.1  Diversion servicesp. 37
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.
8.2.14.2.2  Completion of Communications to Busy Subscriber (CCBS)p. 37
Charging information shall be provided for the original communication, and for the resulting CCBS communication.
8.2.14.2.3  CONFerence (CONF)p. 37
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/ISDNp. 38

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

8.2.15.1  Definitionp. 38

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:
    1. the transferring party wants to perform the transfer without any further action on the transfer operation (ECT Blind),
    2. 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.
Up

8.2.15.2  Service interactions with other IMS supplementary servicesp. 38

8.2.15.2.1  Identification servicesp. 38
8.2.15.2.1.1  Terminating Identification Restriction (TIR) p. 38
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.
Up
8.2.15.2.1.2  Originating Identification Presentation (OIP) p. 39
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) p. 39
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)p. 39
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.
Up
8.2.15.2.3  CONFerence (CONF)p. 39
The conference controller cannot transfer the conference to another party.
8.2.15.2.4  Advice Of Charge (AOC)p. 39
8.2.15.2.4.0  General p. 39
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) p. 39
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) p. 39
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.
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) p. 40
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.
Up
8.2.15.2.5  Explicit Communication Transfer (ECT)p. 40
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.
Up

8.2.15.3  Interoperability with PSTN/ISDN and CS mobile networksp. 40

No restrictions.

Up   Top   ToC