Content for TS 24.642 Word version: 18.0.0
1 Scope p. 7
The present document specifies the stage three Protocol Description of the Completion of Communications to Busy Subscriber (CCBS) service, the Completion of Communications on no Reply (CCNR) service, and Completion of Communications on not Logged-in (CCNL) service, based on stage one and two of the ISDN supplementary services. It provides the protocol details in the IP Multimedia (IM) Core Network (CN) subsystem based on the Session Initiation Protocol (SIP) and the Session Description Protocol (SDP).
The Completion of Communications to Busy Subscriber CCBS service enables user A, encountering a busy destination B, to have the communication completed without having to make a new communication attempt when the destination B becomes not busy.
The Completion of Communications on No Reply CCNR supplementary service enables user A, encountering a destination B which does not answer the communication (No Reply), to have the communication completed without having to make a new communication attempt when the destination becomes not busy after having initiated an activity.
The Completion of Communications on Not Logged-in CCNL supplementary service enables user A, encountering a destination B which is not registered with the IMS network, to have the communication completed without having to make a new communication attempt when the destination becomes registered.
The present document is applicable to User Equipment (UE) and Application Servers (AS) which are intended to support the CCBS and CCNR supplementary services.
2 References p. 8
The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
- For a specific reference, subsequent revisions do not apply.
- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.
[1]
TS 22.173: "IP Multimedia Core Network Subsystem (IMS) Multimedia Telephony Service and supplementary services; Stage 1".
[2]
TS 24.229: "Internet Protocol (IP) multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3".
[3]
TS 24.628: "Common Basic Communication procedures using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification".
[4]
TS 24.623: "Extensible Markup Language (XML) Configuration Access Protocol (XCAP) over the Ut interface for Manipulating Supplementary Services".
[5]
RFC 6910 (April 2013): "Completion of Calls for the Session Initiation Protocol (SIP)".
[6]
RFC 6665 (July 2012): "SIP-Specific Event Notification".
[7]
TS 24.238: "Session Initiation Protocol (SIP) based user configuration".
[8]
ITU-T Recommendation I.221 (1993): "Common specific characteristics of services".
[9]
RFC 5875 (May 2010): "An Extensible Markup Language (XML) Configuration Access Protocol (XCAP) Diff Event Package ".
[10]
RFC 4825: "The Extensible Markup Language (XML) Configuration Access Protocol (XCAP)".
[11]
RFC 3023: "XML Media Types".
[12]
RFC 4483: "A Mechanism for Content Indirection in Session Initiation Protocol (SIP) Messages".
[13]
RFC 3261: "SIP: Session Initiation Protocol".
3 Definitions and abbreviations p. 8
3.1 Definitions p. 8
For the purposes of the present document, the terms and definitions given in TS 22.173 and the following terms and definitions apply.
busy:
See ITU-T Recommendation I.221 [8], subclause 2.1.5.
call information retention:
A procedure of network A to store the call information of a specific call so that it can be used for that call.
caller:
The user who originated the call and to whom the CCBS service is provided.
callee:
The user which is identified as destination B.
CC:
Completion of Communication
CC busy:
Any one of the following conditions will cause a CCBS busy condition:
- maximum number of calls reached at user A (see ITU-T Recommendation I.221 [8], subclause 2.1.3, item 2));
- no resources (bandwidth) available at user A;
- CC recall pending on user A.
A call generated by the network connecting the caller to the callee, resulting from the callers' acceptance of a CC recall.
CC recall:
An indication informing the caller that the network is ready to initiate a CC call to the callee and that the network is awaiting a response to this indication.
CC request:
An instance of an activation of the CCBS/CCNR/CCNL service which is held in a queue pending the correct conditions for the CCBS/CCNR/CCNL service to be completed.
Suspended CC request:
A CC request which cannot be served even if the callee is in the appropriate state because the caller is busy.
CC request retention:
If an attempt to establish a CC call fails because the destination is busy again, then the network provider option "CC request retention" defines whether the CC supplementary service is continued or not, i.e. if the "CC request retention" is supported, the original CC request retains its position in the queue B, and monitoring of user B shall continue. Otherwise the CC request is revoked.
CC service duration timer:
A maximum time a CC service will remain activated for the caller within the network.
destination B:
The entity addressed in the original call.
long-term denial:
The network cannot accept user A's request to activate the CC service and a later attempt to activate the CC service for the same destination B will also be rejected.
queue A:
A buffer at the originating side for the control of CC requests associated with the caller.
queue B:
A buffer at the terminating side for the control of CC requests associated with destination B.
retain option:
The retain option, if supported in both the originating and destination network, will maintain the CC request in the destination B queue, if a CC call has failed due to destination busy condition.
short-term denial:
The network temporarily cannot accept user A's request to activate the CC service. A later attempt to activate the CC service for the same destination B may succeed.
UE-A:
The caller's UE.
UE-B:
The callee's UE.
3.2 Abbreviations p. 9
For the purposes of the present document, the following abbreviations apply:
AOC
Advice Of Charge
AS
Application Server
CB
Communication Barring
CC
Completion of Communications
CCBS
Completion of Communications to Busy Subscriber
CCNL
Completion of Communications on Not Logged-in
CCNR
Completion of Communications on No Reply
CD
Communication Deflection
CDIV
Call DIVersion
CFB
Communication Forwarding Busy
CFNL
Communication Forwarding on No Logged-in
CFU
Communication Forwarding Unconditional
CN
Core Network
CNR
Completion of communication on No Reply
CONF
CONFerence calling
CS
Circuit Switched
CW
Communication Waiting
ECT
Explicit Communication Transfer
HOLD
Communication HOLD
IFC
Initial Filter Criteria
IM
IP Multimedia
IMS
IP Multimedia Subsystem
IP
Internet Protocol
ISDN
Integrated Service Data Network
MCID
Malicious Communication IDentification
MiD
Multi-iDentity
MIME
Multipurpose Internet Mail Extensions
MuD
Multi-Device
OIP
Originating Identification Presentation
OIR
Originating Identification Restriction
PLMN
Public Land Mobile Network
PSTN
Public Switch Telephone Network
SIP
Session Initiation Protocol
TIP
Terminating Identification Presentation
TIR
Terminating Identification Restriction
UE
User Equipment
