1、 ETSI TS 123 135 V14.0.0 (2017-04) Universal Mobile Telecommunications System (UMTS); LTE; Multicall supplementary service; Stage 2 (3GPP TS 23.135 version 14.0.0 Release 14) TECHNICAL SPECIFICATION ETSI ETSI TS 123 135 V14.0.0 (2017-04)13GPP TS 23.135 version 14.0.0 Release 14Reference RTS/TSGC-042
2、3135ve00 Keywords LTE,UMTS ETSI 650 Route des Lucioles F-06921 Sophia 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
3、 can be downloaded from: http:/www.etsi.org/standards-search The present 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 o
4、f any existing or perceived difference in contents between such versions 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
5、may be subject to revision or change of status. Information on the current status of this and other ETSI documents is available at https:/portal.etsi.org/TB/ETSIDeliverableStatus.aspx If you find errors in the present document, please send your comment to one of the following services: https:/portal
6、.etsi.org/People/CommiteeSupportStaff.aspx Copyright Notification No part may 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
7、 without the written authorization of ETSI. The copyright and the foregoing restriction extend to reproduction in all media. European Telecommunications Standards Institute 2017. All rights reserved. DECTTM, PLUGTESTSTM, UMTSTMand the ETSI logo are Trade Marks of ETSI registered for the benefit of i
8、ts Members. 3GPPTM and LTE are Trade Marks of ETSI registered for the benefit 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 123 135 V14.0.0 (2017-04)23GPP TS 23.135 version 14.0.0 Release 14Intel
9、lectual Property Rights IPRs essential or potentially essential to the present 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 Righ
10、ts (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in respect 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, ha
11、s been carried out by ETSI. No guarantee can be given as to the existence of other 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 th
12、e ETSI 3rdGeneration Partnership Project (3GPP). The present document may refer to 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 G
13、SM, UMTS, 3GPP and ETSI identities can be found under http:/webapp.etsi.org/key/queryform.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 t
14、he ETSI Drafting Rules (Verbal forms for the expression of provisions). “must“ and “must not“ are NOT allowed in ETSI deliverables except when used in direct citation. ETSI ETSI TS 123 135 V14.0.0 (2017-04)33GPP TS 23.135 version 14.0.0 Release 14Contents Intellectual Property Rights 2g3Foreword . 2
15、g3Modal verbs terminology 2g3Foreword . 5g31 Scope 6g32 References 6g33 Definitions and abbreviations . 6g33.1 Definitions 6g33.2 Abbreviations . 6g34 Descriptions 6g34.1 Handling of Multicall . 6g34.1.1 Provision . 6g34.1.2 Withdrawal . 7g34.1.3 Registration . 7g34.1.4 Erasure 8g34.1.5 Activation .
16、 9g34.1.6 Deactivation 9g34.1.7 Interrogation . 9g34.2 Call related procedures . 11g34.2.1 MO call . 11g34.2.2 MT call . 11g34.3 Messages and their contents . 13g34.3.1 Messages between MS and MSC 13g34.3.2 Messages on B interface (MSC-VLR) 14g34.3.2.1 Send Info For Outgoing Call . 14g34.3.2.2 Send
17、Info For Outgoing Call negative response 14g34.3.2.3 Send Info For Incoming Call . 14g34.3.2.4 Send Info For Incoming Call ack 14g34.3.2.5 Send Info For Incoming Call negative response . 14g34.3.2.6 Complete Call . 14g34.3.2.7 Complete Call ack . 14g34.3.2.8 Page MS 14g34.3.2.9 Page MS negative resp
18、onse . 15g34.3.2.10 Process Access Request 15g34.3.2.11 Process Access Request ack 15g34.3.2.12 Process Access Request negative response . 15g34.3.2.13 Search For MS 15g34.3.2.14 Search For MS ack 15g34.3.2.15 Search For MS negative response . 15g35 Network entity functions 16g35.1 General . 16g35.2
19、 MO call . 16g35.2.1 Functional requirements of serving MSC . 16g35.2.2 Functional requirements of VLR 17g35.3 MT call . 19g35.3.1 Functional requirements of serving MSC . 19g35.3.2 Functional requirements of VLR 23g36 Interaction with telecommunication services . 25g36.1 Speech 25g36.2 Short messag
20、e service 25g36.3 Facsimile service 25g36.4 Data circuit asynchronous 25g3ETSI ETSI TS 123 135 V14.0.0 (2017-04)43GPP TS 23.135 version 14.0.0 Release 146.5 Data circuit synchronous 25g36.6 Void 25g36.7 GPRS 25g37 Interaction with other supplementary services . 25g37.1 Line Identification services 2
21、5g37.2 Call forwarding unconditional (CFU) 25g37.3 Call forward on busy (CFB) . 26g37.4 Call forwarding on no reply (CFNRy) . 26g37.5 Call forwarding on MS not reachable (CFNRc) . 26g37.6 Call Hold (CH) . 26g37.7 Call Waiting (CW) . 26g37.8 Multiparty service (MPTY) 26g37.9 Closed user group (CUG) .
22、 26g37.10 Advice Of Charge (AoC) . 26g37.11 Call Barring services 26g37.12 Explicit call transfer (ECT) 26g37.13 Call Deflection (CD) 26g37.14 Completion of calls to busy subscriber (CCBS) . 26g38 Interaction with network features . 27g38.1 Customised Applications for Mobile network Enhanced Logic (
23、CAMEL) . 27g38.2 Support of Optimal Routeing (SOR) 27g38.3 Operator Determined Barring (ODB) . 27g39 Information stored in the HLR . 27g310 State transition model . 27g311 Transfer of information from HLR to VLR . 28g312 Information stored in VLR . 28g313 Handover 28g3Annex A (informative): Examples
24、 . 29g3Annex B (informative): Change history . 33g3History 34g3ETSI ETSI TS 123 135 V14.0.0 (2017-04)53GPP TS 23.135 version 14.0.0 Release 14Foreword This Technical Specification (TS) has been produced by ETSI 3rd Generation Partnership Project (3GPP). The present document gives the stage 2 descrip
25、tion of the Multicall service within the 3GPP system. The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying cha
26、nge 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 indicates TSG approved document under change control. y the second digit is incremented for all changes of subst
27、ance, 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 123 135 V14.0.0 (2017-04)63GPP TS 23.135 version 14.0.0 Release 141 Scope The present document gives the stage 2 description
28、 of the Multicall supplementary service. 2 References 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-spe
29、cific. - For a specific reference, subsequent revisions do not apply. - For a non-specific reference, the latest version applies. 1 3GPP TR 21.905: “3GPP Vocabulary“. 2 3GPP TS 22.100: “UMTS Phase 1“. 3 3GPP TS 22.105: “Services Technical realization“. 8 3GPP TS 23.083: “Call Waiting (CW) and Call H
30、old (HOLD) Supplementary Service - Stage 2“. 9 3GPP TS 24.008: “Mobile radio interface layer 3 specification Core Network Protocol Stage 3“. 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the terms and definitions given in TS 22.135 and the following apply.
31、 Speech Call: speech call means one of TS11 (Telephony), TS12 (Emergency call), TS61 (Alternate speech and facsimile group 3). 3.2 Abbreviations Abbreviations used in the present document are listed in TR 21.905. 4 Descriptions 4.1 Handling of Multicall 4.1.1 Provision No special signalling procedur
32、es apply. ETSI ETSI TS 123 135 V14.0.0 (2017-04)73GPP TS 23.135 version 14.0.0 Release 144.1.2 Withdrawal No special signalling procedures apply. 4.1.3 Registration The information flow for registration is shown in figure 1. The registration process is shown in figure 2. MS MSC VLR HLR Register Mult
33、icall Register Multicall Register Multicall ACK ACK Release complete (Nbr_User) (Nbr_User) (Nbr_User) ISD (SS-Code = MC, Nbr_User) (SS-status, Nbr_User) (SS-status, Nbr_User) (SS-status, Nbr_User) Figure 1: Registration of Multicall ETSI ETSI TS 123 135 V14.0.0 (2017-04)83GPP TS 23.135 version 14.0.
34、0 Release 14Multicall Registrationprocess in HLRProcess Register_Multicall_HLR RM_HLR1(1)IdleRegisterMulticallMulticallprovisioned?Nbr_UserProvided?0 1Negative response: =Multicall not provisionedResult: =Fail Result:= PassTotal number of bearers in use = Nbr_UserNegative response: =Nbr_User exceede
35、dResult:= PassNoYesNoYesYesNoETSI ETSI TS 123 135 V14.0.0 (2017-04)193GPP TS 23.135 version 14.0.0 Release 145.3 MT call 5.3.1 Functional requirements of serving MSC Figure 10: Procedure Check_MT_Multicall_MSC. This procedure is called when the MSC receives a Page MS message or a Search For MS messa
36、ge from the VLR. The maximum number of bearers (Nbr) indicates the minimum value of Nbr_User, Nbr_SN and Nbr_UE. After handover to another MSC is completed, Nbr_SN, as defined for the target MSC, shall overwrite the previous Nbr_SN. “Call in Setup“ means that the MS is engaged in at least one call t
37、hat has not reached the established phase (called party answer). The test “Call waiting“ takes the “Yes“ exit if a waiting call has been offered to the subscriber but the outcome of offering the call has not been determined. Figure 11: Procedure Establish_Terminating_TCH_Multicall. This procedure is
38、 called when the MSC receives a Call Confirmed or a Connect message from the MS. If the MS indicates “No bearer“ as the value of the Stream Identifier in the Call Confirmed message the test “Bearer allocation pending“ takes the “Yes“ exit. Figure 12: Procedure MC_TCH_Check This procedure is called w
39、hen the MSC needs to establish a terminating TCH. ETSI ETSI TS 123 135 V14.0.0 (2017-04)203GPP TS 23.135 version 14.0.0 Release 14Procedure to determinethe way to offer the calland whether the MS is NDUBProcedure Check_MT_Multicall_MSC CMM_MSC1(1)Nbr_User indicated?Result :=Not provisionedCurrent nu
40、mber of terminatingcalls Ncs_MTNew callis speech?Result :=NDUBSpeech callexists?Current number of bearers in use NbrNOTE: Each call in set-up iscounted as one bearer.Speech callis in Setup?All calls arein Setup?Waiting callexists?Result :=NDUBResult :=More calls possibleResult :=NDUBResult :=Offered
41、NoYesYesNoYesNoNoYesNoYesNoYesNoYesYesNoFigure 10: Procedure Check_MT_Multicall_MSC ETSI ETSI TS 123 135 V14.0.0 (2017-04)213GPP TS 23.135 version 14.0.0 Release 14Figure 11: Procedure Establish_Terminating_TCH_Multicall Procedure to allocate a TCHafter checkingMulticall limitationProcedure Establis
42、h_Terminating_TCH_Multicall ETTM1(1)Bearer allocationpending?MC_TCH_CheckResultAllocatechannelWait_For_Allocation_CompleteReleasetransactionResult:=FailAllocationfailureReleasetransactionAllocationcompleteResult:=PassReleaseReleasetransactionResult:=AbortedResult:=FailResult:=AbortedResult:=PassResu
43、lt:=RejectedResult:=PassNoAllocate Fail Aborted PassRejectYesETSI ETSI TS 123 135 V14.0.0 (2017-04)223GPP TS 23.135 version 14.0.0 Release 14Figure 12: Procedure MC_TCH_CheckProcedure to allocate TCHafter checking Multicall limitationProcedure MC_TCH_Check MTC1(1)New bearerrequested?Nbrreached?TCH_C
44、heck See TS 23.018ResultResult:=RejectResult:=AbortedResult :=FailResult :=AllocateResult :=PassYesNoNoYesReject Aborted Fail Allocate Use existingETSI ETSI TS 123 135 V14.0.0 (2017-04)233GPP TS 23.135 version 14.0.0 Release 145.3.2 Functional requirements of VLR Figure 13: Procedure Get_CW_Subscrip
45、tion_Info_Multicall_VLR. This procedure is called when the VLR receives a Page MS negative response message or a Search For MS negative response message with the negative response IE set to “Busy (More Calls Possible)“. ETSI ETSI TS 123 135 V14.0.0 (2017-04)243GPP TS 23.135 version 14.0.0 Release 14
46、Figure 13: Procedure Get_CW_Subscription_Info_Multicall_VLR Procedure in the VLR to retrieve subscription information for the Call Waiting serviceProcedure Get_CW_Subscription_Info_Multicall_VLR CWIM_VLR1(1)Signals to/from the rightare to/from the processMAF013 (TS 23.083)BS :=first BS1initiatehandl
47、ingof CWWait_For_CW_InfoFrom MSC AbortProcesscallwaitingIndicator=CW available?Indicator :=CW availableNext BSexists?BS :=next BSIndicator :=CW not available1YesNoYesNoETSI ETSI TS 123 135 V14.0.0 (2017-04)253GPP TS 23.135 version 14.0.0 Release 146 Interaction with telecommunication services 6.1 Sp
48、eech The Multicall supplementary service does not provide multiple traffic channels for speech calls. Refer to Procedure Check_OG_Multicall_MSC and Procedure Check_MT_Multicall_MSC. If Nbr_UE is greater than Nbr_SN, the mobile station may initiate an Emergency call even if Nbr_SN has been reached. W
49、hen the network receives an Emergency call Setup message from the mobile station: - if Nbr_SN has not been reached, the network shall accept it regardless of Nbr_SB or Nbr_User; - if Nbr_SN has been reached, the network shall reject the emergency call setup attempt. The MS shall release one or more existing calls and it shall re-initiate an Emergency call. The MS shall ensure that an emergency call Setup request is acceptable to a serving network which does not support multicall, if necessary by releasing one or more existing calls. 6.2 Short message service No im
