1、 ETSI TS 123 035 V15.0.0 (2018-06) Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); Immediate Service Termination (IST); Stage 2 (3GPP TS 23.035 version 15.0.0 Release 15) TECHNICAL SPECIFICATION ETSI ETSI TS 123 035 V15.0.0 (2018-06)13G
2、PP TS 23.035 version 15.0.0 Release 15Reference RTS/TSGS-0323035vf00 Keywords GSM,SECURITY,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-Prf
3、ecture de Grasse (06) N 7803/88 Important notice The present document 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 b
4、e modified without the prior written authorization of ETSI. In case of 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 Secretar
5、iat. Users of the present document should be aware that the document 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, ple
6、ase send your comment to one of the following services: https:/portal.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 per
7、mission of ETSI. The content of the PDF version shall not be modified without the written authorization of ETSI. The copyright and the foregoing restriction extend to reproduction in all media. ETSI 2018. All rights reserved. DECTTM, PLUGTESTSTM, UMTSTMand the ETSI logo are trademarks of ETSI regist
8、ered for the benefit of its Members. 3GPPTM and LTETMare trademarks of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners. oneM2M logo is protected for the benefit of its Members. GSMand the GSM logo are trademarks registered and owned by the GSM Association. ETSI
9、 ETSI TS 123 035 V15.0.0 (2018-06)23GPP TS 23.035 version 15.0.0 Release 15Intellectual Property Rights Essential patents IPRs essential or potentially essential to normative deliverables may have been declared to ETSI. The information pertaining to these essential IPRs, if any, is publicly availabl
10、e 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 respect of ETSI standards“, which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web server (
11、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 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, e
12、ssential to the present document. Trademarks The present document may include trademarks and/or tradenames which are asserted and/or registered by their owners. ETSI claims no ownership of these except for any which are indicated as being the property of ETSI, and conveys no right to use or reproduc
13、e any trademark and/or tradename. Mention of those trademarks in the present document does not constitute an endorsement by ETSI of products, services or organizations associated with those trademarks. Foreword This Technical Specification (TS) has been produced by ETSI 3rd Generation Partnership Pr
14、oject (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 GSM, UMTS, 3GPP and ETSI identities
15、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 the ETSI Drafting Rules (Verbal form
16、s 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 035 V15.0.0 (2018-06)33GPP TS 23.035 version 15.0.0 Release 15Contents Intellectual Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Forewo
17、rd . 4g31 Scope 5g32 References 5g33 Definitions and abbreviations . 5g33.1 Definitions 5g33.2 Abbreviations . 5g34 Information flows . 6g34.1 CAMEL implementation 6g34.2 Non-CAMEL implementation 6g35 Functional behaviour - CAMEL implementation . 6g35.1 Subscriber settings 6g35.2 DP Settings . 7g35.
18、3 Call termination 7g36 Functional behaviour - Non-CAMEL implementation 7g36.1 Subscriber Settings . 7g36.2 Periodic reporting mechanism 8g36.2.1 IST Alert timer Settings 8g36.2.2 Call termination 8g36.3 IST standalone mechanism . 8g36.4 Exception procedure . 9g37 Control of IST 10g3Annex A (Informa
19、tive): Change History 11g3History 12g3ETSI ETSI TS 123 035 V15.0.0 (2018-06)43GPP TS 23.035 version 15.0.0 Release 15Foreword 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
20、 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 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 inf
21、ormation; 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 substance, i.e. technical enhancements, corrections, updates, etc. z the third digit is incremented when editorial only changes have been
22、 incorporated in the document. ETSI ETSI TS 123 035 V15.0.0 (2018-06)53GPP TS 23.035 version 15.0.0 Release 151 Scope This Technical Specification specifies the stage 2 description of the Immediate Service Termination (IST) service which provides the means for the HPLMN to terminate all the activiti
23、es of an HPLMN subscriber in a VPLMN. Two implementations of IST are described: an implementation based on CAMEL, and an implementation based on a new MAP message. 2 References - The following documents contain provisions which, through reference in this text, constitute provisions of the present do
24、cument. - 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
25、 (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 TR 21.905: “3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Vocabulary for 3GPP Specificat
26、ions“. 2 3GPP TS 22.032: “3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Immediate Service Termination (IST), Service description - Stage 1“. 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the following terms
27、and definitions apply. Subscriber activities: subscriber activities that must be terminated. These can be call related events (e.g. call set-up, call termination) or the invocation of call related and call independent supplementary services (e.g. Call Hold, Call Waiting, Call Transfer, Call Forwardi
28、ng, Unstructured Supplementary Service Data (USSD). 3.2 Abbreviations For the purposes of the present document, the abbreviations given in TR 21.905 1 and the following abbreviations apply: IST Immediate Service Termination FDS Fraud Detection System FIGS Fraud Information Gathering System MO Mobile
29、 Originated MT Mobile TerminatedO-CSI Originating CAMEL Subscription Information T-CSI Terminating CAMEL Subscription Information ETSI ETSI TS 123 035 V15.0.0 (2018-06)63GPP TS 23.035 version 15.0.0 Release 154 Information flows 4.1 CAMEL implementation For the Customised Applications for Mobile net
30、work Enhanced Logic (CAMEL) implementation of Immediate Service Termination (IST) for a particular subscriber, an “IST“ command (in reality, the CAMEL message “ReleaseCall“) must be sent by the gsmSCF of the home PLMN to the gsmSSF controlling the call, for all the calls of the subscriber. Prior to
31、the sending of the IST command, the Mobile Application Part (MAP) command “Cancel Location“ should be sent to the VLR at which the subscriber is registered. This will ensure that the subscriber cannot re-commence service at that VLR after the IST command has been executed. See Annex A of TS 22.032 2
32、. The compilation of the list of MSCs to which the IST command should be sent is outside the scope of this specification. However, if a PLMN operator wishes to implement IST using CAMEL, the list of MSCs to which the IST command should be sent for a subscriber is the list of MSCs with which the CAME
33、L server has a relationship for that subscriber. If this data is not available directly from the CAMEL server, it may be obtained using Fraud Information Gathering System (FIGS) or an Fraud Detection System (FDS) (if the HPLMN is using CAMEL for IST then it is likely that it will also be monitoring
34、the subscribers activities using FIGS level 2 or 3, which use CAMEL). 4.2 Non-CAMEL implementation For each non-CAMEL-subscriber under IST control, the HLR shall request the MSCs during location update and routeing information retrieval to report for each remaining activity periodically at the frequ
35、ency defined by the IST Alert timer value about the remaining activity for this subscriber in the node by sending an IST Alert Message to the HLR, as long as the activity is ongoing. The IST Alert timer value is set by HPLMN and communicated to VPLMN and IPLMN on subscriber basis. The HLR shall be a
36、ble to request termination of ongoing call activities for a subscriber by returning a call termination indicator to the MSC in response to the IST Alert message initiated by this MSC. When this call termination indicator is received, the MSC shall terminate the call activities for that subscriber (t
37、he MSC shall terminate the call activity that triggered the IST Alert dialogue, and optionally other call activities in that MSC if the MSC is able to link the calls related to the subscriber). As an implementation option the HLR may for each non-CAMEL-subscriber under IST control maintain a list of
38、 MSCs which possibly have ongoing activities for the subscriber. The HLR may then send at any time (i.e. without waiting for the IST Alert message) an unsolicited IST Command message to these MSCs in order to request termination of all ongoing activities for the subscriber. The HLR should send unsol
39、icited IST Command message only to those MSCs that are likely to be carrying a call that needs to be terminated. Before sending of any IST Command message for a subscriber, the HLR should send the MAP Cancel Location message to the VLR at which the subscriber is registered. This will ensure that the
40、 subscriber cannot re-commence service at the corresponding MSC after the IST Command message has been executed. See Annex A of TS 22.032 2. The MSC shall be prepared to receive an IST Command message before and/or after the subscriber record has been removed from the VLR. 5 Functional behaviour - C
41、AMEL implementation This clause describes the implementation of IST using CAMEL. CAMEL can be used to terminate all the mobile originated (MO), mobile terminated (MT) and forwarded (CF) calls of a subscriber, provided there is a control relationship between the CAMEL server (the gsmSCF) in the HPLMN
42、 and the MSC (visited MSC or GMSC) (the gsmSSF) controlling the call or forwarding leg. 5.1 Subscriber settings The subscriber is marked as a CAMEL subscriber by setting Originating CAMEL Subscription Information (O-CSI) and Terminating CAMEL Subscription Information (T-CSI) in the subscriber data s
43、tored in the HLR of the HPLMN. The O-CSI is sent to the VPLMN when the subscriber first registers in the VPLMN; the T-CSI is sent to the GMSC in the response to a request for routeing information. If the subscriber is being monitored using FIGS, it will already be marked as a CAMEL subscriber. ETSI
44、ETSI TS 123 035 V15.0.0 (2018-06)73GPP TS 23.035 version 15.0.0 Release 15If the HPLMN wishes to mark a subscriber as a CAMEL subscriber when the subscriber is already registered in the VPLMN, it modifies the subscriber data in the VPLMN using the command Insert Subscriber Data. 5.2 DP Settings A ca
45、ll cannot be terminated using CAMEL unless there is a control relationship between the gsmSCF and the gsmSSF controlling the call. To ensure that the IST command can be used at any point in the duration of a call, right up to the end of the call, there must be a control relationship until the end of
46、 the call. A “control relationship“ exists where there is at least one armed DP in the gsmSSF. This can be achieved if the DP O/T_Disconnect (which will trigger the sending of an Event_Report_BCSM to the gsmSCF) is set for the call. If the subscriber is being monitored using FIGS level 2 or 3, the s
47、ubscriber will already be marked as a CAMEL subscriber and DP O/T_Disconnect will already have been set. If the subscriber is not being monitored using FIGS levels 2 or 3 then O/T_Disconnect is set with command Request_Report_BCSM_Event sent to the gsmSSF by the gsmSCF after the gsmSCF has received
48、notification of a call attempt via the Initial_DP message received from the gsmSSF. Initial_DP notifies the gsmSCF of call attempts. If the gsmSCF wishes to be notified of the success or failure of a call attempt, and so not be keeping a register of “calls“ that may not have commenced, DP O/T_Answer
49、 can be set to inform the gsmSCF when a call is answered by the calling party. If the non-reception of an Event_Report_BCSM indicating call answer is not sufficient indication to the HPLMN of the failure of a call attempt, DPs O_Route_Select_Failure, O/T_Busy, O/T_No_Answer, O/T_Abandon, O/T_Not_Reachable can be set to inform the gsmSCF explicitly if the call attempt fails. If the various failure DPs are not armed, the gsmSCF can still deduce that the call attempt has failed because the gsmSSF will terminate the relationship when the call fails by sending message A
