1、 ETSI TS 132 295 V15.0.0 (2018-06) Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); LTE; Telecommunication management; Charging management; Charging Data Record (CDR) transfer (3GPP TS 32.295 version 15.0.0 Release 15) TECHNICAL SPECIFIC
2、ATION ETSI ETSI TS 132 295 V15.0.0 (2018-06)13GPP TS 32.295 version 15.0.0 Release 15Reference RTS/TSGS-0532295vf00 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 Associati
3、on 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/or print ve
4、rsions 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 kept on a s
5、pecific 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 https:/portal.etsi.org/TB/ETSIDeliverableStatus.aspx 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. ETSI 2018. All rights reserved. DECTTM, PLUGTESTSTM, UMTSTMand t
8、he ETSI logo are trademarks of ETSI registered 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 registe
9、red and owned by the GSM Association. ETSI ETSI TS 132 295 V15.0.0 (2018-06)23GPP TS 32.295 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 es
10、sential 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 respect of ETSI standards“, which is available from the ETSI Secretariat. Latest upda
11、tes 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 other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web serv
12、er) which are, or may be, or may become, essential 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 ETS
13、I, and conveys no right to use or reproduce 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 prod
14、uced 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 should be interpreted as being references to the corresponding ETSI deliverables. The cross reference be
15、tween 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“, “may“, “need not“, “will“, “will not“, “can“ and “cannot“ are to be interpreted as described in clause 3
16、.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 295 V15.0.0 (2018-06)33GPP TS 32.295 version 15.0.0 Release 15Contents Intellectual Property Rights 2g3Forew
17、ord . 2g3Modal verbs terminology 2g3Foreword . 5g31 Scope 6g32 References 6g33 Definitions, symbols and abbreviations . 7g33.1 Definitions 7g33.2 Symbols 9g33.3 Abbreviations . 10g34 Architecture considerations 11g34.1 High level architecture . 11g35 Transfer principles and scenarios . 12g35.1 Trans
18、fer principles 12g35.1.0 General 12g35.1.1 Charging related transfer requirements . 12g35.1.2 CDR transport by GTP . 12g35.1.2.1 CDF - CGF communication 12g35.1.2.2 CGF - CGF communication 12g35.1.3 Port usage . 13g35.2 GTP transfer scenarios . 14g35.2.1 Basic principles . 14g35.2.2 GTP messaging ca
19、ses . 14g35.2.2.0 General 14g35.2.2.1 The normal CDR packet transfer 15g35.2.2.2 The CDF-CGF connection breaks before a successful CDR reception . 16g35.2.2.3 The CDF-CGF connection breaks after a successful CDR reception 18g35.2.2.4 CGF redundancy mechanism 20g36 Data description for the transfer .
20、 23g36.1 The GTP charging protocol . 23g36.1.0 General 23g36.1.1 Usage of GTP header in charging . 23g36.1.2 Information Elements (IEs). 23g36.2 GTP message types 24g36.2.1 List of all GTP message types 24g36.2.2 Reused GTP message types 25g36.2.3 GTP message type modifications, implied by GTP . 25g
21、36.2.4 GTP message types 26g36.2.4.0 General 26g36.2.4.1 Node Alive Request 26g36.2.4.2 Node Alive Response 26g36.2.4.3 Redirection Request 27g36.2.4.4 Redirection Response 28g36.2.4.5 Data Record Transfer Request 28g36.2.4.5.0 Introduction . 28g36.2.4.5.1 Information Elements in Data Record Transfe
22、r Request . 28g36.2.4.5.2 Packet Transfer Command IE 29g36.2.4.5.3 Data Record Packet IE . 30g36.2.4.5.4 Sequence Numbers of Released Packets IE . 30g36.2.4.5.5 Sequence Numbers of Cancelled Packets IE . 31g36.2.4.5.6 Private Extension IE 31g36.2.4.6 Data Record Transfer Response 32g36.3 Data Record
23、 Format in GTP 33g3ETSI ETSI TS 132 295 V15.0.0 (2018-06)43GPP TS 32.295 version 15.0.0 Release 156.3.0 Introduction. 33g36.3.1 Standard Data Record Format . 33g36.3.2 Private Data Record Formats 33g36.4 Data Record Format Version for CDRs . 34g3Annex A (informative): Bibliography . 35g3Annex B (inf
24、ormative): Change history . 36g3History 37g3ETSI ETSI TS 132 295 V15.0.0 (2018-06)53GPP TS 32.295 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 with
25、in 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 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 f
26、or 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 substance, i.e. technical enhancements, corrections, updates, etc. z the third digit is incremented when editorial only changes hav
27、e been incorporated in the document. ETSI ETSI TS 132 295 V15.0.0 (2018-06)63GPP TS 32.295 version 15.0.0 Release 151 Scope The present document is part of a series of Technical Specifications (TSs) that specify charging functionality and charging management in 3GPP networks (GSM/UMTS/EPS). The 3GPP
28、 core network charging architecture and principles are specified in TS 32.240 1, which provides an umbrella for other charging management TSs that specify: - the content of the CDRs per domain / subsystem / service (offline charging); - the content of real-time charging messages per domain / subsyst
29、em / service (online charging); - the functionality of online and offline charging for those domains / subsystems / services; - 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
30、defined in TS 32.240 1. The present document specifies the transaction based mechanism for the near real time transfer of CDRs within the network. The present document is related to other 3GPP charging TSs as follows: - The common 3GPP charging architecture is specified in TS 32.240 1; - The paramet
31、ers, abstract syntax and encoding rules for the CDRs are specified in TS 32.298 51; - The file based mechanism used to transfer the CDRs from the network to the operators Billing Domain (e.g. the post-processing system or a mediation device) is specified in TS 32.297 52; The 3GPP Diameter applicatio
32、n that is used for offline and online charging is specified in TS 32.299 50. All terms, definitions and abbreviations used in the present document, that are common across 3GPP TSs, are defined in the 3GPP Vocabulary, TR 21.905 100. Those that are common across charging management in 3GPP domains ser
33、vices, 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. Finally, those items that are specific to the present document are defined exclusively in the present document. Furthermore, requirements that govern the c
34、harging work are specified in TS 22.115 101. 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
35、-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 sam
36、e Release as the present document. 1 3GPP TS 32.240: “Telecommunication 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 3GPP TS 32.251: “Telecommunica
37、tion management; Charging management; Packet Switched (PS) domain charging“. ETSI ETSI TS 132 295 V15.0.0 (2018-06)73GPP TS 32.295 version 15.0.0 Release 1512 - 29 Void. 30 3GPP TS 32.270: “Telecommunication management; Charging management; Multimedia Messaging Service (MMS) charging“. 31 - 49 Void.
38、 50 3GPP TS 32.299: “Telecommunication management; Charging management; Diameter charging application“. 51 3GPP TS 32.298: “Telecommunication management; Charging management; Charging Data Record (CDR) parameter description“. 52 3GPP TS 32.297: “Telecommunication management; Charging management; Cha
39、rging Data Record (CDR) file format and transfer“. 53 - 99 Void. 100 3GPP TR 21.905: “Vocabulary for 3GPP Specifications“. 101 3GPP TS 22.115: “Service aspects; Charging and billing“. 102 - 199 Void. 200 3GPP TS 29.060: “General Packet Radio Service (GPRS); GPRS Tunnelling Protocol (GTP) across the
40、Gn and Gp interface“. 201 3GPP TS 29.274: “3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3“. 202 - 299 Void. 300 - 399 Void. 400 - 403 Void. 404 IETF RFC 768 (1980): “User Datagram Protocol“ (STD 6). 405 IETF RFC
41、793 (1981): “Transmission Control Protocol“ (STD 7). 406 IETF RFC 791 (1981): “Internet Protocol“ (STD 5). 407 IETF RFC 792 (1981): “Internet Control Message Protocol“ (STD 5). 3 Definitions, symbols and abbreviations 3.1 Definitions For the purposes of the present document, the following terms and
42、definitions given in TR 21.905 50, TS 32.240 1, and the following apply: 2G- / 3G-: prefixes 2G- and 3G- refers to functionality that supports only GSM or UMTS, respectively, e.g. 2G-CDF refers only to the GSM functionality of an CDF. accounting: process of apportioning charges between the Home Envi
43、ronment, Serving Network and User. billing: function whereby CDRs generated by the charging function are transformed into bills requiring payment. Billing Domain: Part of the operator network, which is outside the core network, that receives and processes CDR files from the core network charging fun
44、ctions. It includes functions that can provide billing mediation and billing 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 utilizing telecommunications ne
45、twork infrastructure and related services for: ETSI ETSI TS 132 295 V15.0.0 (2018-06)83GPP TS 32.295 version 15.0.0 Release 15- 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);
46、or - inter-network communication (e.g. transferring calls, signalling, or short messages); or - mobility (e.g. roaming or inter-system handover); and - that the network operator wants to charge for. charged party: user involved in a chargeable event who has to pay parts or the whole charges of the c
47、hargeable event, or a third party paying the charges caused by one or all users involved in the chargeable event, or a network operator. charging: function whereby information related to a chargeable event is formatted and transferred in order to make it possible to determine usage for which the cha
48、rged party may be billed. Charging Data Record (CDR): A formatted 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 char
49、geable 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 function: entity inside the core network domain, subsystem or service that is involved in charging for that domain, subsystem or service. circuit switched domain: domain within GSM / UMTS in which information is transferred in circuit mode. domain: part of a communicat
