TIA-1137 400-2009 Converged Access Network Accounting Specification《融合接入网络结算规范》.pdf

《TIA-1137 400-2009 Converged Access Network Accounting Specification《融合接入网络结算规范》.pdf》由会员分享，可在线阅读，更多相关《TIA-1137 400-2009 Converged Access Network Accounting Specification《融合接入网络结算规范》.pdf（34页珍藏版）》请在麦多课文档分享上搜索。

1、 TIA-1137.400-2009 APPROVED: JUNE 1, 2009 REAFFIRMED: DECEMBER 6, 2013 TIA-1137.400 June 2009Converged Access Network Accounting Specification NOTICE TIA Engineering Standards and Publications are designed to serve the public interest through eliminating misunderstandings between manufacturers and p

2、urchasers, facilitating interchangeability and improvement of products, and assisting the purchaser in selecting and obtaining with minimum delay the proper product for their particular need. The existence of such Standards and Publications shall not in any respect preclude any member or non-member

3、of TIA from manufacturing or selling products not conforming to such Standards and Publications. Neither shall the existence of such Standards and Publications preclude their voluntary use by Non-TIA members, either domestically or internationally. Standards and Publications are adopted by TIA in ac

4、cordance with the American National Standards Institute (ANSI) patent policy. By such action, TIA does not assume any liability to any patent owner, nor does it assume any obligation whatever to parties adopting the Standard or Publication. This Standard does not purport to address all safety proble

5、ms associated with its use or all applicable regulatory requirements. It is the responsibility of the user of this Standard to establish appropriate safety and health practices and to determine the applicability of regulatory limitations before its use. (From Project No. 3-0291.400-RF1, formulated u

6、nder the cognizance of the TIA TR-45 Mobile (b) there is no assurance that the Document will be approved by any Committee of TIA or any other body in its present or any other form; (c) the Document may be amended, modified or changed in the standards development or any editing process. The use or pr

7、actice of contents of this Document may involve the use of intellectual property rights (“IPR”), including pending or issued patents, or copyrights, owned by one or more parties. TIA makes no search or investigation for IPR. When IPR consisting of patents and published pending patent applications ar

8、e claimed and called to TIAs attention, a statement from the holder thereof is requested, all in accordance with the Manual. TIA takes no position with reference to, and disclaims any obligation to investigate or inquire into, the scope or validity of any claims of IPR. TIA will neither be a party t

9、o discussions of any licensing terms or conditions, which are instead left to the parties involved, nor will TIA opine or judge whether proposed licensing terms or conditions are reasonable or non-discriminatory. TIA does not warrant or represent that procedures or practices suggested or provided in

10、 the Manual have been complied with as respects the Document or its contents. If the Document contains one or more Normative References to a document published by another organization (“other SSO”) engaged in the formulation, development or publication of standards (whether designated as a standard,

11、 specification, recommendation or otherwise), whether such reference consists of mandatory, alternate or optional elements (as defined in the TIA Engineering Manual, 4thedition) then (i) TIA disclaims any duty or obligation to search or investigate the records of any other SSO for IPR or letters of

12、assurance relating to any such Normative Reference; (ii) TIAs policy of encouragement of voluntary disclosure (see Engineering Manual Section 6.5.1) of Essential Patent(s) and published pending patent applications shall apply; and (iii) Information as to claims of IPR in the records or publications

13、of the other SSO shall not constitute identification to TIA of a claim of Essential Patent(s) or published pending patent applications. TIA does not enforce or monitor compliance with the contents of the Document. TIA does not certify, inspect, test or otherwise investigate products, designs or serv

14、ices or any claims of compliance with the contents of the Document. ALL WARRANTIES, EXPRESS OR IMPLIED, ARE DISCLAIMED, INCLUDING WITHOUT LIMITATION, ANY AND ALL WARRANTIES CONCERNING THE ACCURACY OF THE CONTENTS, ITS FITNESS OR APPROPRIATENESS FOR A PARTICULAR PURPOSE OR USE, ITS MERCHANTABILITY AN

15、D ITS NONINFRINGEMENT OF ANY THIRD PARTYS INTELLECTUAL PROPERTY RIGHTS. TIA EXPRESSLY DISCLAIMS ANY AND ALL RESPONSIBILITIES FOR THE ACCURACY OF THE CONTENTS AND MAKES NO REPRESENTATIONS OR WARRANTIES REGARDING THE CONTENTS COMPLIANCE WITH ANY APPLICABLE STATUTE, RULE OR REGULATION, OR THE SAFETY OR

16、 HEALTH EFFECTS OF THE CONTENTS OR ANY PRODUCT OR SERVICE REFERRED TO IN THE DOCUMENT OR PRODUCED OR RENDERED TO COMPLY WITH THE CONTENTS. TIA SHALL NOT BE LIABLE FOR ANY AND ALL DAMAGES, DIRECT OR INDIRECT, ARISING FROM OR RELATING TO ANY USE OF THE CONTENTS CONTAINED HEREIN, INCLUDING WITHOUT LIMI

17、TATION ANY AND ALL INDIRECT, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES (INCLUDING DAMAGES FOR LOSS OF BUSINESS, LOSS OF PROFITS, LITIGATION, OR THE LIKE), WHETHER BASED UPON BREACH OF CONTRACT, BREACH OF WARRANTY, TORT (INCLUDING NEGLIGENCE), PRODUCT LIABILITY OR OTHERWISE, EVEN IF ADVISED OF THE

18、 POSSIBILITY OF SUCH DAMAGES. THE FOREGOING NEGATION OF DAMAGES IS A FUNDAMENTAL ELEMENT OF THE USE OF THE CONTENTS HEREOF, AND THESE CONTENTS WOULD NOT BE PUBLISHED BY TIA WITHOUT SUCH LIMITATIONS. X.S0054-400-0 v1.0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 3

19、1 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 i ContentsConverged Access Network Accounting Specification: CONTENTS 1 Introduction1 1.1 Scope1 2 References2 2.1 Normative References2 2.2 Informative References2 3 Definitions and Abbreviations .3 3.1 Definit

20、ions .3 4 Accounting.4 4.1 Overview4 4.2 General Accounting Rules .5 4.2.1 Reservation/IP-session Based Accounting 5 4.2.2 IP-Session Based Accounting7 4.3 Reservation/IP-session Based Accounting.8 4.3.1 ADR Definition for Reservation/IP-Session Based Accounting .8 4.3.2 CAN Usage Data Record (UDR).

21、10 4.3.3 AGW Accounting Triggers12 4.4 IP-Session Based Accounting 13 4.4.1 UMB Usage Data Record (UDR) 13 4.4.2 AGW Accounting Triggers14 4.5 Accounting Call flows .15 4.5.1 Reservation/IP-Session Based Accounting Call Flow.15 4.5.2 IP-Session Based Accounting Call Flow.18 X.S0054-400-0 v1.0 1 2 3

22、4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 List of Figures ii LIST OF FIGURES Figure 1 Basic Accounting Architecture .4 Figure 2 Accounting with Two eBS in Route Set for Reservat

23、ion/IP-session Based Accounting16 Figure 3 IP-Session Based Accounting .19 X.S0054-400-0 v1.0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 iii List of TablesLIST OF TABLES Ta

24、ble 1 Additional RADIUS Attributes between AGW and SRNC during EAP Access Authentication and Authorization for Accounting Support 6 Table 2 Additional Diameter AVPs between AGW and SRNC during EAP Access Authentication and Authorization for Accounting Support 6 Table 3 Additional RADIUS Attributes b

25、etween AGW and AAA during EAP Access Authentication and Authorization for Accounting Support 7 Table 4 Additional Diameter AVPs between AGW and AAA during EAP Access Authentication and Authorization for Accounting Support 7 Table 5 ADR Format for Reservation/IP-session Based Accounting 9 Table 6 Res

26、ervation-Based-Usage VSA includes the following sub-types .9 Table 7 UDR Format for Reservation/IP-session Based Accounting 10 Table 8 UDR Format for IP-Session Based Accounting .13 X.S0054-400-0 v1.0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36

27、37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 Revision History iv REVISION HISTORY Revision Date Remarks 0 December 2007 Initial Release X.S0054-400-0 v1.0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 4

28、3 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 v ForewordFOREWORD (This foreword is not part of this Standard.) This document was prepared by 3GPP2 TSG-X. This document is a new specification. This document is part of a multi-part document consisting of multiple parts that together describes C

29、onverged Access Network. This document is subject to change following formal approval. Should this document be modified, it will be re-released with a change of release date and an identifying change in version number as follows: X.S0054-400-X version n.0 where: X an uppercase numerical or alphabeti

30、c character 0, A, B, C, that represents the revision level. n a numeric string 1, 2, 3, that indicates an point release level. This document uses the following conventions: “Shall” and “shall not” identify requirements to be followed strictly to conform to this document and from which no deviation i

31、s permitted. “Should” and “should not” indicate that one of several possibilities is recommended as particularly suitable, without mentioning or excluding others, that a certain course of action is preferred but not necessarily required, or that (in the negative form) a certain possibility or course

32、 of action is discouraged but not prohibited. “May” and “need not” indicate a course of action permissible within the limits of the document. “Can” and “cannot” are used for statements of possibility and capability, whether material, physical or causal. X.S0054-400-0 v1.0 1 2 3 4 5 6 7 8 9 10 11 12

33、13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 1.1 Scope 1 1 Introduction1 Introduction This document defines offline accounting functionality in the CAN. It describes the functional responsibilities of

34、the network elements including the accounting data to be collected by certain elements in the CAN architecture. It describes the protocol messages and message contents that are exchanged between eBSs in an ATs Route Set and the AGW, and between the AGW and the accounting server. Only RADIUS based ac

35、counting is specified in this release. 1.1 Scope This part specifies the requirements for the offline accounting functionality in a CAN system. X.S0054-400-0 v1.0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49

36、 50 51 52 53 54 55 56 57 58 59 60 2 References 2 2.1 Normative References2 References 2.1 Normative References This section provides references to other specifications and standards that are necessary to implement this document. 1 IETF: RFC 2866, Rigney. C, “RADIUS Accounting”, June 2000. 2 3GPP2: X

37、.S0054-000-0 v1.0, “CAN Wireless IP Network Overview and List of Parts”, December 2007. 3 3GPP2: X.S0054-100-0 v1.0, “Basic IP Services for Converged Access Network Specification”, December 2007. 4 3GPP2 X.S0054-910-0 v1.0, “CAN Data Dictionary”, December 2007. 5 3GPP2 A.S0020-0 v1.0, “Interoperabil

38、ity Specification (IOS) for Ultra Mobile Broadband (UMB) Radio Access Network Interfaces”, November 2007. 6 3GPP2 C.S0084-0 v2.0, “Ultra Mobile Broadband (UMB)TM1Air Interface Specification”, September 2007. 7 3GPP2 X.S0011-D v2.0, “Wireless IP Network Specifications”, December 2007. 8 IETF: RFC2794

39、, Calhoun, et.al., “Mobile IP Network Access Identifier Extension for IPv4”, March 2000 2.2 Informative References This section provides references to other documents that may be useful for the reader of this document. 3GPP2: X.S0054-102-0 v1.0, “Multiple-Authentication and Legacy Authentication Sup

40、port for Converged Access Network”, December 2007. 3GPP2: X.S0054-110 v1.0, “MIP4 Specification in Converged Access Network Specification”, December 2007. 3GPP2: X.S0054-210-0 v1.0, “CMIP based Inter-AGW Handoff”, December 2007. 3GPP2: X.S0054-220-0 v1.0, “Network PMIP Support”, December 2007. 3GPP2

41、: X.S0054-300-0 v1.0, “QoS Support for Converged Access Network Specification”, December 2007. 1Ultra Mobile BraoadbandTMand (UMBTM) are trade and service marks owned by the CDMA Development Group (CDG). X.S0054-400-0 v1.0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29

42、 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 3.1 Definitions 3 3 Definitions and Abbreviations3 Definitions and Abbreviations 3.1 Definitions Connection Time: Connection Time is the duration of time in seconds that the AT is associated with the traffi

43、c channel. IP-session based accounting: IP-session based accounting is accounting for each ATs IP address. Reservation/IP-session based accounting: Reservation/IP-session based accounting is accounting for each separate reservation/IP-session where a single reservation is identified by the reservati

44、on label and direction indicator associated with ATs IP address. X.S0054-400-0 v1.0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 4 Accounting 4 4.1 Overview4 Accounting Accou

45、nting in a CAN system is accomplished through functionality shared across the eBSs, the AGW and the accounting server. The three major functions are: 1. Measuring/counting of the quantity of data sent and received by an eBS on behalf of an AT or the amount of connected radio air time that an AT uses

46、 for a reservation. 2. Creation and management of accounting records that are sent to an AAA accounting server and used for billing purposes. 3. Assimilation of policy and charging control rules into the accounting process. Note: Dynamic policy and accounting interactions are not part of the first r

47、elease of this document. 4.1 Overview Figure 1 provides a pictorial overview of the offline accounting architecture in a CAN system. Figure 1 Basic Accounting Architecture Each eBS that is a member of the Route Set for an AT is responsible for reporting usage data for the AT that utilizes the resour

48、ces in the eBS to the AGW. Radio specific information is collected by the eBSs and delivered to the AGW in RADIUS VSAs. Accounting information is sent from the reporting eBSs of the Route Set to the AGW in Airlink Data Records (ADRs). Triggers to start and stop collecting usage information in the eB

49、S, triggers for the delivery of X.S0054-400-0 v1.0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 4.2 General Accounting Rules 5 4 Accountinginformation in ADRs to the AGW, and triggers for sending accounting information from the AGW to the Accounting Server (HAAA) are covered in subsequent sections. Accounting can be performed per Reservation and per IP-session Reservation/IP-session based accounting, or per IP s