ETSI TS 124 642-2016 Digital cellular telecommunications system (Phase 2+) Universal Mobile Telecommunications System (UMTS) LTE Completion of Communications to Busy Subscriber (CC.pdf

《ETSI TS 124 642-2016 Digital cellular telecommunications system (Phase 2+) Universal Mobile Telecommunications System (UMTS) LTE Completion of Communications to Busy Subscriber (CC.pdf》由会员分享，可在线阅读，更多相关《ETSI TS 124 642-2016 Digital cellular telecommunications system (Phase 2+) Universal Mobile Telecommunications System (UMTS) LTE Completion of Communications to Busy Subscriber (CC.pdf（58页珍藏版）》请在麦多课文档分享上搜索。

1、 ETSI TS 1Digital cellular telecoUniversal Mobile TelCompletion of Commuand Completion of Cousing IP Multimedia (Prot(3GPP TS 24.6TECHNICAL SPECIFICATION124 642 V13.0.0 (2016communications system (Phaelecommunications System (LTE; unications to Busy SubscribeCommunications by No Replyia (IM) Core Ne

2、twork (CN) subsrotocol specification .642 version 13.0.0 Release 1316-01) hase 2+); (UMTS); iber (CCBS) ly (CCNR) bsystem; 13) ETSI ETSI TS 124 642 V13.0.0 (2016-01)13GPP TS 24.642 version 13.0.0 Release 13Reference RTS/TSGC-0124642vd00 Keywords GSM,LTE,UMTS ETSI 650 Route des Lucioles F-06921 Sophi

3、a Antipolis Cedex - FRANCE Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 Siret N 348 623 562 00017 - NAF 742 C Association but non lucratif enregistre la Sous-Prfecture de Grasse (06) N 7803/88 Important notice The present document can be downloaded from: http:/www.etsi.org/standards-search The pre

4、sent document may be made available in electronic versions and/or in print. The content of any electronic and/or print versions of the present document shall not be modified without the prior written authorization of ETSI. In case of any existing or perceived difference in contents between such vers

5、ions and/or in print, the only prevailing document is the print of the Portable Document Format (PDF) version kept on a specific network drive within ETSI Secretariat. Users of the present document should be aware that the document may be subject to revision or change of status. Information on the c

6、urrent status of this and other ETSI documents is available at http:/portal.etsi.org/tb/status/status.asp If you find errors in the present document, please send your comment to one of the following services: https:/portal.etsi.org/People/CommiteeSupportStaff.aspx Copyright Notification No part may

7、be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm except as authorized by written permission of ETSI. The content of the PDF version shall not be modified without the written authorization of ETSI. The copyright and the foregoing re

8、striction extend to reproduction in all media. European Telecommunications Standards Institute 2016. All rights reserved. DECTTM, PLUGTESTSTM, UMTSTMand the ETSI logo are Trade Marks of ETSI registered for the benefit of its Members. 3GPPTM and LTE are Trade Marks of ETSI registered for the benefit

9、of its Members and of the 3GPP Organizational Partners. GSM and the GSM logo are Trade Marks registered and owned by the GSM Association. ETSI ETSI TS 124 642 V13.0.0 (2016-01)23GPP TS 24.642 version 13.0.0 Release 13Intellectual Property Rights IPRs essential or potentially essential to the present

10、 document may have been declared to ETSI. The information pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found in ETSI SR 000 314: “Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in respe

11、ct of ETSI standards“, which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web server (https:/ipr.etsi.org/). Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee can be given as to the existence of o

12、ther IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web server) which are, or may be, or may become, essential to the present document. Foreword This Technical Specification (TS) has been produced by ETSI 3rd Generation Partnership Project (3GPP). The present document may refer t

13、o technical specifications or reports using their 3GPP identities, UMTS identities or GSM identities. These should be interpreted as being references to the corresponding ETSI deliverables. The cross reference between GSM, UMTS, 3GPP and ETSI identities can be found under http:/webapp.etsi.org/key/q

14、ueryform.asp. Modal verbs terminology In the present document “shall“, “shall not“, “should“, “should not“, “may“, “need not“, “will“, “will not“, “can“ and “cannot“ are to be interpreted as described in clause 3.2 of the ETSI Drafting Rules (Verbal forms for the expression of provisions). “must“ an

15、d “must not“ are NOT allowed in ETSI deliverables except when used in direct citation. ETSI ETSI TS 124 642 V13.0.0 (2016-01)33GPP TS 24.642 version 13.0.0 Release 13Contents Intellectual Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 6g31 Scope 7g32 References 8g33 Definitio

16、ns and abbreviations . 8g33.1 Definitions 8g33.2 Abbreviations . 9g34 Completion of Communications to Busy Subscriber (CCBS), Completion of Communications on No Reply (CCNR) and Completion of Communications on Not Logged-in (CCNL) . 10g34.1 Introduction 10g34.2 Description . 10g34.2.1 General descri

17、ption . 10g34.3 Operational requirements . 11g34.3.1 Provision/withdrawal 11g34.4 Coding requirements 11g34.5 Signalling requirements 12g34.5.1 Activation/deactivation . 12g34.5.2 Registration/erasure 12g34.5.3 Interrogation . 12g34.5.4 Invocation and operation 12g34.5.4.1 Actions at the originating

18、 UE 12g34.5.4.2 Actions at the originating AS 13g34.5.4.2.0 General 13g34.5.4.2.1 CC Invocation 13g34.5.4.2.1.1 Normal procedures 13g34.5.4.2.1.1.1 Detecting if CC is possible 13g34.5.4.2.1.1.2 Starting of the service retention procedure 13g34.5.4.2.1.1.3 CC service invocation by user A . 14g34.5.4.

19、2.1.1.4 Stopping of the service retention procedure 14g34.5.4.2.1.1.5 Sending of the CC invocation request to the terminating AS 14g34.5.4.2.1.1.6 Procedures after CC invocation confirmation from the terminating AS 15g34.5.4.2.1.2 Exceptional procedures 16g34.5.4.2.2 CC Revocation 16g34.5.4.2.2.1 No

20、rmal procedures 16g34.5.4.2.2.1.1 Generating a revocation request 16g34.5.4.2.2.1.2 Revocation requested by the user 16g34.5.4.2.2.1.3 Revocation caused by timer expiry 17g34.5.4.2.2.2 Exceptional procedures 17g34.5.4.2.3 CC Operation . 17g34.5.4.2.3.1 Normal procedures 17g34.5.4.2.3.2 Exceptional p

21、rocedures 18g34.5.4.2.3.2.1 Non-acceptance of CC recall . 18g34.5.4.2.3.2.2 User A is found not available 18g34.5.4.2.3.2.3 The caller makes another call to the same destination B . 19g34.5.4.2.3.2.4 CC call failure . 19g34.5.4.3 Actions at the terminating AS . 19g34.5.4.3.0 General 19g34.5.4.3.1 CC

22、 possible indication . 19g34.5.4.3.1.1 Normal operation . 19g34.5.4.3.1.2 Exceptional procedures 20g34.5.4.3.2 CC Invocation 20g3ETSI ETSI TS 124 642 V13.0.0 (2016-01)43GPP TS 24.642 version 13.0.0 Release 134.5.4.3.2.1 Normal operation . 20g34.5.4.3.2.2 Exceptional procedures 21g34.5.4.3.3 CC Revoc

23、ation 21g34.5.4.3.3.1 Normal operation . 21g34.5.4.3.3.2 Exceptional procedures 21g34.5.4.3.4 CC Operation . 21g34.5.4.3.4.1 Normal operation . 21g34.5.4.3.4.1.1 The callee becomes available 21g34.5.4.3.4.1.2 The CC recall is started . 22g34.5.4.3.4.1.3 Incoming communication during the CC recall pr

24、ocessing . 22g34.5.4.3.4.1.4 Procedures after the CC call was offered to the callee 22g34.5.4.3.4.1.5 Further procedures . 23g34.5.4.3.4.2 Exceptional procedures 23g34.5.4.4 Actions at the terminating UE . 24g34.5.5 SIP specific Event Notifications . 24g34.6 Interaction of Call-Completion with other

25、 services 24g34.6.1 Communication waiting (CW) 24g34.6.2 Communication Hold (HOLD) . 24g34.6.3 Terminating Identification Presentation (TIP) 24g34.6.4 Terminating Identification Restriction (TIR) 24g34.6.5 Originating identification presentation (OIP) . 24g34.6.6 Originating identification restricti

26、on (OIR) 24g34.6.7 Conference calling (CONF) 24g34.6.8 Communication diversion services (CDIV) 25g34.6.8.1 General 25g34.6.8.2 Communication Forwarding Unconditional 25g34.6.8.3 Communication forwarding busy 25g34.6.8.4 Communication forwarding no reply 25g34.6.8.5 Communication forwarding not regis

27、tered 26g34.6.8.6 Communication deflection (CD) . 26g34.6.9 Advice of charge (AOC) . 26g34.6.10 Completion of communications (CCBS/CCNR/CCNL). 26g34.6.11 Malicious communication identification (MCID) 26g34.6.12 Anonymous Communication Rejection and Communication Barring (ACR/CB) . 26g34.6.13 Message

28、 Waiting Indication (MWI) . 26g34.6.14 Explicit Communication Transfer (ECT) . 26g34.6.15 Flexible Alerting (FA) 27g34.6.16 Customized Alerting Tones (CAT) . 27g34.7 Void 27g34.8 Parameter values (timers) . 27g34.8.1 Timers referring to the originating AS 27g34.8.2 Timers referring to the terminatin

29、g AS . 27g34.9 Communication completion configuration XCAP application usage . 28g34.9.1 General 28g34.9.2 Data semantics 28g34.9.3 XML schema 28g34.10.2 Communication completion request records XCAP application usage 29g34.10.2.1 Application Unique ID (AUID) 29g34.10.2.2 XML schema . 29g34.10.2.3 D

30、efault document namespace 29g34.10.2.4 MIME type 30g34.10.2.5 Validation constraints 30g34.10.2.6 Data semantics 30g34.10.2.7 Naming conventions 30g34.10.2.8 Resource interdependencies 30g34.10.2.9 Authorization policies . 30g3Annex A (informative): Signalling flows 31g3A.1 CCBS activation and CCBS

31、call 31g3A.2 CCBS suspend and resume procedures 37g3ETSI ETSI TS 124 642 V13.0.0 (2016-01)53GPP TS 24.642 version 13.0.0 Release 13A.3 CCNR activation 40g3A.4 CCNR call 43g3A.5 CCNL invocation . 45g3A.6 CCNL call 49g3Annex B (informative): Example of filter criteria . 52g3B.0 General . 52g3B.1 Origi

32、nating side 52g3B.2 Terminating side . 52g3Annex C (informative): IANA Registration templates 53g3C.1 IANA registry for application media types 53g3C.1.1 IANA registration template for application/vnd.3gpp.ccrr+xml 53g3Annex D (informative): Change history . 55g3History 57g3ETSI ETSI TS 124 642 V13.

33、0.0 (2016-01)63GPP TS 24.642 version 13.0.0 Release 13Foreword This Technical Specification has been produced by the 3rdGeneration Partnership Project (3GPP). The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the T

34、SG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: Version x.y.z where: x the first digit: 1 presented to TSG for information; 2 presented to TSG for approval; 3 or greater indicat

35、es TSG approved document under change control. y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. z the third digit is incremented when editorial only changes have been incorporated in the document. ETSI ETSI TS 124 642 V13.0.0 (20

36、16-01)73GPP TS 24.642 version 13.0.0 Release 131 Scope 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 Logge

37、d-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 Bu

38、sy 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, encoun

39、tering 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 supplemen

40、tary 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 Applic

41、ation Servers (AS) which are intended to support the CCBS and CCNR supplementary services. ETSI ETSI TS 124 642 V13.0.0 (2016-01)83GPP TS 24.642 version 13.0.0 Release 132 References The following documents contain provisions which, through reference in this text, constitute provisions of the presen

42、t 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 (

43、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 3GPP TS 22.173: “IP Multimedia Core Network Subsystem (IMS) Multimedia Telephony Service and supplementary services; Stage 1“. 2 3GPP TS 24.229:

44、 “Internet Protocol (IP) multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3“. 3 3GPP TS 24.628: “Common Basic Communication procedures using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification“. 4 3GPP TS 24.

45、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 3GPP TS 2

46、4.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 IETF RFC 4825: “The Exten

47、sible Markup Language (XML) Configuration Access Protocol (XCAP)“. 11 IETF RFC 3023: “XML Media Types“. 12 IETF RFC 4483: “A Mechanism for Content Indirection in Session Initiation Protocol (SIP) Messages“. 13 IETF RFC 3261: “SIP: Session Initiation Protocol“. 3 Definitions and abbreviations 3.1 Def

48、initions For the purposes of the present document, the terms and definitions given in 3GPP TS 22.173 1 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 speci

49、fic 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. ETSI ETSI TS 124 642 V13.0.0 (2016-01)93GPP TS 24.642 version 13.0.0 Release 13callee: 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 pen