1、 ETSI TS 1Digital cellular telecoUniversal Mobile TelTelecommCharLocation S(3GPP TS 32.2TECHNICAL SPECIFICATION132 271 V13.0.0 (2016communications system (Phaelecommunications System (LTE; munication management; arging management; n Services (LCS) charging .271 version 13.0.0 Release 1316-02) hase 2
2、+); (UMTS); 13) ETSI ETSI TS 132 271 V13.0.0 (2016-02)13GPP TS 32.271 version 13.0.0 Release 13Reference RTS/TSGS-0532271vd00 Keywords GSM,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
3、 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 present document may be made available in electronic versions and/or in print. The content of any electronic and/o
4、r 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 versions and/or in print, the only prevailing document is the print of the Portable Document Format (PDF) version k
5、ept 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 current status of this and other ETSI documents is available at http:/portal.etsi.org/tb/status/status.asp If yo
6、u 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 be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and mic
7、rofilm 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 restriction extend to reproduction in all media. European Telecommunications Standards Institute 2016. All rights
8、 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 of its Members and of the 3GPP Organizational Partners. GSM and the GSM logo are Trade Marks registered and own
9、ed by the GSM Association. ETSI ETSI TS 132 271 V13.0.0 (2016-02)23GPP TS 32.271 version 13.0.0 Release 13Intellectual 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 public
10、ly 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 respect of ETSI standards“, which is available from the ETSI Secretariat. Latest updates are available on the ETSI W
11、eb 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 other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web server) which are, or may be, or ma
12、y 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 to technical specifications or reports using their 3GPP identities, UMTS identities or GSM identities. These sho
13、uld 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/queryform.asp. Modal verbs terminology In the present document “shall“, “shall not“, “should“, “should not“, “ma
14、y“, “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“ and “must not“ are NOT allowed in ETSI deliverables except when used in direct citation. ETSI ETSI TS 132 271 V13
15、.0.0 (2016-02)33GPP TS 32.271 version 13.0.0 Release 13Contents Intellectual Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 5g31 Scope 6g32 References 7g33 Definitions, symbols and abbreviations . 8g33.1 Definitions 8g33.2 Symbols 10g33.3 Abbreviations . 10g34 Architecture co
16、nsiderations 12g34.1 High level LCS architecture . 12g34.2 LCS offline charging architecture 13g34.3 LCS online charging architecture . 13g35 LCS charging principles and scenarios 14g35.1 LCS charging principles . 14g35.2 LCS offline charging scenarios 15g35.2.1 Basic principles . 15g35.2.2 Rf messa
17、ge flows 15g35.2.3 CDR Generation . 15g35.2.3.0 Introduction . 15g35.2.3.1 Mobile Originated Location Request (MO-LR) 16g35.2.3.2 Mobile Terminated Location Request (MT-LR) . 17g35.2.3.3 Network Induced Location Request (NI-LR) 19g35.2.4 Ga record transfer flows . 19g35.2.5 BLCDR file transfer . 20g
18、35.3 LCS online charging scenarios . 20g35.3.0 General 20g35.3.1 Basic principles . 20g35.3.2 Ro message flows . 21g35.3.2.0 General 21g35.3.2.1 Mobile Originated Location Request (MO-LR) 21g35.3.2.2 Mobile Terminated Location Request (MT-LR) . 22g36 Definition of charging information 23g36.0 Genera
19、l . 23g36.1 Data description for LCS offline charging . 23g36.1.0 Introduction. 23g36.1.1 Rf message contents 23g36.1.2 Ga message contents . 23g36.1.3 CDR description on the BLinterface 23g36.1.3.0 Introduction . 23g36.1.3.1 LCS records for Mobile Originated Location Request (LCS-GMO-CDR) . 23g36.1
20、.3.2 LCS records for Mobile Terminated Location Request (MT-LR) 24g36.1.3.2.1 LCS records for Requesting GMLC (LCS-RGMT-CDR) 24g36.1.3.2.2 LCS records for Home GMLC (LCS-HGMT-CDR) 25g36.1.3.2.3 LCS records for Visited GMLC (LCS-VGMT-CDR) . 25g36.1.3.3 LCS Records for Network Initiated Location Reque
21、st (LCS-GNI-CDR) . 26g36.2 Data description for LCS online charging 27g36.2.1 Ro message contents . 27g36.2.1.0 General 27g36.2.1.1 Debit / Reserve Units Request message 27g3ETSI ETSI TS 132 271 V13.0.0 (2016-02)43GPP TS 32.271 version 13.0.0 Release 136.2.1.2 Debit / Reserve Units Response message.
22、 28g36.3 LCS charging specific parameters 28g36.3.1 Definition of LCS charging information . 28g36.3.1.0 General 28g36.3.1.1 LCS charging information assignment for Service Information . 28g36.3.1.2 Definition of the LCS Information 28g3Annex A (informative): Bibliography . 30g3Annex B (informative)
23、: Change history . 31g3History 32g3ETSI ETSI TS 132 271 V13.0.0 (2016-02)53GPP TS 32.271 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 TS
24、G 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 inform
25、ation; 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 in
26、corporated in the document. ETSI ETSI TS 132 271 V13.0.0 (2016-02)63GPP TS 32.271 version 13.0.0 Release 131 Scope The present document is part of a series of Technical Specifications (TSs) that specify charging functionality and charging management in GSM/UMTS networks. The GSM/UMTS core network ch
27、arging architecture and principles are specified in TS 32.240 1, which provides an umbrella for other charging management documents that specify - the content of the CDRs per domain and subsystem (offline charging); - the content of real-time charging events per domain / subsystem (online charging);
28、 - the functionality of online and offline charging for those domains and subsystems; - the interfaces that are used in the charging framework to transfer the charging information (i.e. CDRs or charging events). The complete document structure for these TSs is defined in TS 32.240 1. The present doc
29、ument specifies the LCS Offline and Online Charging description for the LCS domain, based on the functional stage 2 description of the LCS in TS 23.071 201. This charging description includes the offline and online charging architecture and scenarios specific to the LCS, as well as the mapping of th
30、e common 3GPP architecture specified in TS 32.240 1 onto the LCS domain. It further specifies the structure and content of the CDRs for offline charging and the charging events for online charging. The present document is related to other 3GPP charging TSs as follows: - The common 3GPP charging arch
31、itecture is specified in TS 32.240 1; - The parameters, abstract syntax and encoding rules for these CDR types are specified in TS 32.298 51. - A transaction based mechanism for the transfer of CDRs within the network is specified in TS 32.295 54. - The file based mechanism used to transfer the CDRs
32、 from the network to the operator“s billing domain (e.g. the billing system or a mediation device) is specified in TS 32.297 52. - The 3GPP Diameter application that is used for LCS domain offline and online charging is specified in TS 32.299 50. All terms, definitions and abbreviations, used in the
33、 present document, that are common across 3GPP TSs, are defined in TR 21.905 100. Those that are common across charging management in GSM/UMTS domains, services, or subsystems are provided in the umbrella document TS 32.240 1 and are copied into clause 3 of the present document for ease of reading.
34、Finally, those items that are specific to the present document are defined exclusively in the present document. Furthermore, requirements that govern the charging work are specified in TS 22.115 101. ETSI ETSI TS 132 271 V13.0.0 (2016-02)73GPP TS 32.271 version 13.0.0 Release 132 References The foll
35、owing 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
36、 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 3GPP TS 32.240: “Telecommunic
37、ation management; Charging management; Charging architecture and principles“. 2 - 9 Void. 10 3GPP TS 32.250: “Telecommunication management; Charging management; Circuit Switched (CS) domain charging“. 11 - 19 Void. 20 3GPP TS 32.260: “Telecommunication management; Charging management; IP Multimedia
38、Subsystem (IMS) charging“. 21 - 29 Void. 30 3GPP TS 32.270: “Telecommunication management; Charging management; Multimedia Messaging Service (MMS) charging“. 31 - 49 Void 50 3GPP TS 32.299: “Telecommunication management; Charging management; Diameter charging application“. 51 3GPP TS 32.298: “Teleco
39、mmunication management; Charging management; Charging Data Record (CDR) encoding rules description“. 52 3GPP TS 32.297: “Telecommunication management; Charging management; Charging Data Record (CDR) file format and transfer“. 53 3GPP TS 32.296: “Telecommunication management; Charging management; Onl
40、ine Charging System (OCS) applications and interfaces“. 54 3GPP TS 32.295: “Telecommunication management; Charging management; Charging Data Record (CDR) transfer“. 55 - 99 Void. 100 3GPP TR 21.905: “Vocabulary for 3GPP Specifications“. 101 3GPP TS 22.115: “Service aspects; Charging and billing“. 10
41、2 - 199 Void. 200 Void. 201 3GPP TS 23.271: “Functional stage 2 description of Location Services (LCS)“. 202 Void. 203 3GPP TS 25.305: “Stage 2 functional specification of User Equipment (UE) positioning in UTRAN“. ETSI ETSI TS 132 271 V13.0.0 (2016-02)83GPP TS 32.271 version 13.0.0 Release 13204 3G
42、PP TS 43.059: “Functional stage 2 description of Location Services (LCS) in GERAN“. 205 3GPP TS 24.002: “GSM - UMTS Public Land Mobile Network (PLMN) Access Reference Configuration“. 206 - 299 Void. 301 - 399 Void. 400 Void. 401 IETF RFC 3588 (2003): “Diameter Base Protocol“. 402 IETF RFC 4006 (2005
43、): “Diameter Credit-Control Application“. 3 Definitions, symbols and abbreviations 3.1 Definitions For the purposes of the present document, the terms and definitions defined in TR 21.905 100 and TS 32.240 1, and the following apply: accounting: process of apportioning charges between the Home Envir
44、onment, Serving Network and Subscriber. billing: function whereby CDRs generated by the charging function(s) are transformed into bills requiring payment. Billing Domain (BD): part of the operator network, which is outside the telecommunications network, that receives and processes CDR files from th
45、e network charging functions. It includes functions that can provide billing mediation and billing or other (e.g. statistical) end applications. It is only applicable to offline charging (see “Online Charging System“ for equivalent functionality in online charging). chargeable event: activity utiliz
46、ing telecommunications network resources and related services for: - user to user communication (e.g. a single call, a data communication session or a short message); or - user to network communication (e.g. service profile administration); or - inter-network communication (e.g. transferring calls,
47、signalling, or short messages); or - mobility (e.g. roaming or inter-system handover); and - that the network operator may want to charge for. As a minimum, a chargeable event characterises the resource / service usage and indicates the identity of the involved end user(s). charging: a function with
48、in the telecommunications network and the associated OCS/BD components whereby information related to a chargeable event is collected, formatted, transferred and evaluated in order to make it possible to determine usage for which the charged party may be billed. Charging Data Record (CDR): a formatt
49、ed collection of information about a chargeable event (e.g. time of call set-up, duration of the call, amount of data transferred, etc) for use in billing and accounting. For each party to be charged for parts of or all charges of a chargeable event a separate CDR shall be generated, i.e. more than one CDR may be generated for a single chargeable event, e.g. because of its long duration, or because more than one charged party is to be charged. charging event: a set of chargin
