ATIS 0300075-2008 Usage Data Management for Packet-Based Services Service-Neutral Architecture and Protocol Requirements.pdf

《ATIS 0300075-2008 Usage Data Management for Packet-Based Services Service-Neutral Architecture and Protocol Requirements.pdf》由会员分享，可在线阅读，更多相关《ATIS 0300075-2008 Usage Data Management for Packet-Based Services Service-Neutral Architecture and Protocol Requirements.pdf（25页珍藏版）》请在麦多课文档分享上搜索。

1、 TECHNICAL REPORT ATIS-0300075 USAGE DATA MANAGEMENT FOR PACKET-BASED SERVICES SERVICE-NEUTRAL ARCHITECTURE AND PROTOCOL REQUIREMENTS ATIS is the leading technical planning and standards development organization committed to the rapid development of global, market-driven standards for the informatio

2、n, entertainment and communications industry. More than 200 companies actively formulate standards in ATIS 17 Committees, covering issues including: IPTV, Cloud Services, Energy Efficiency, IP-Based and Wireless Technologies, Quality of Service, Billing and Operational Support, Emergency Services, A

3、rchitectural Platforms and Emerging Networks. In addition, numerous Incubators, Focus and Exploratory Groups address evolving industry priorities including Smart Grid, Machine-to-Machine, Networked Car, IP Downloadable Security, Policy Management and Network Optimization. ATIS is the North American

4、Organizational Partner for the 3rd Generation Partnership Project (3GPP), a member and major U.S. contributor to the International Telecommunication Union (ITU) Radio and Telecommunications Sectors, and a member of the Inter-American Telecommunication Commission (CITEL). ATIS is accredited by the Am

5、erican National Standards Institute (ANSI). For more information, please visit . Notice of Disclaimer however, they do not meet the real-time and high-performance requirements of todays rapidly evolving data networks. Based on more detailed analysis along the lines mentioned above, the need for a re

6、liable, fast, efficient and flexible accounting protocol exists. This document specifies these requirements. 1.2 Purpose and Scope This document specifies requirements and architecture for a family of protocols to collect usage data to be applied to a specified range of business applications across

7、various packet-based services. These protocols and architecture, a.k.a accounting management mechanism, should enable efficient and reliable delivery of any data, mainly Usage Entries from Network Elements and/or Service Elements to any systems, such as mediation systems and BSS/OSS. They should add

8、ress the critical needs for exporting high volume of Data Records from the Service Element with efficient use of network, storage, and processing resources. Standardization of this accounting management mechanism should provide technical information that is sufficient for practical implementations o

9、f interchange of usage data among Network Elements and/or Service Elements participating in the delivery of IP-based services, either within a single enterprise or across multiple enterprises. The objective is to facilitate the integration of IP-based Network Elements and Service Elements into billi

10、ng, reporting and Service Assurance systems. In particular, one key goal is to define a service-independent usage information model and exchange protocol to facilitate the flow of usage information from IP Network Elements and/or Service Elements to support systems. This document specifies a high le

11、vel architecture of this accounting management mechanism. This document is intended to be a general delta document with the ITU-T recommendation “Y.2233” 1 as a basis. This document is not intended to provide detailed specific, point by point, section by section, differences from 1 Future revisions

12、of this specification are expected to make every attempt to preserve investments made by service providers and solution vendors by considering backward and forward compatibility whenever it is practical. ATIS-0300075 2 1.3 Target Applications The following are a service-independent set of applicatio

13、ns that should be considered in determining the requirements for the protocol to be applied at this interface1. The target applications are: Retail Billing The rendering of an invoice for charges due to a Service Provider by a Subscriber to their services, as per an agreed rate plan and service agre

14、ement. Wholesale Billing The rendering of an invoice for charges due to a Network Operator from a Service Provider for access or transport services via which the Service Providers services were delivered. Intercarrier Settlement The process by which Service Providers determine the periodic net charg

15、es due from one party to another for services rendered by each of the parties on behalf of the others Subscribers. In addition the protocol can be used by the following applications: Internal Cost Accounting (e.g. Chargeback) Use of accounting information by a commercial Subscriber for separating th

16、e aggregate usage into sub-accounts associated with the enterprises financial components. Customer Care All those activities associated with the sustenance of satisfactory Subscriber service levels, including inquiries, account changes, restoral, and termination. Marketing Information Demographic, f

17、inancial, statistical, geographical, and temporal data used to aid in decision making and direction setting for product and services positioning and introduction by a Service Provider. Law Enforcement Information Support capture of targeted service usage entries, requested by a legal order for use b

18、y various agencies of law enforcement. Capacity Planning Predictive extension of existing usage patterns to allow for adequate resources to be staged in such a timeframe as to ensure continuity of agreed service levels. Traffic Profiling Statistical portrayal of usage information for characterizing

19、the patterns of usage levels and concentrations at nodal points and across transport boundaries. Traffic Engineering Use of traffic profile information to manage the configuration of infrastructure resources so as to ensure service level continuity. Performance Management Use of statistical data der

20、ived from network and service element telemetry to adapt the configuration of those elements to ensure service level continuity. Revenue assurance - Any activity an organization performs to ensure that processes, practices, and procedures result in revenue that is billed and collected completely, ac

21、curately and in a timely manner. This involves all areas of the organization, from customer care and network systems to invoicing and collections and finance, crossing all boundaries. Revenue leakage is revenue the company has earned, but has neither billed for nor collected. This revenue is lost. R

22、evenue assurance includes Fraud Abatement e.g., Attack/Intrusion Detection Use of statistical and pattern recognition results to detect, prevent, and interdict in usage by Service Consumers not authorized for such usage by a Subscription agreement. QoS Monitoring / SLA Management Use of all varietie

23、s of network and BSS data in the tracking and adaptation of network behavior to ensure service level continuity. 1It should be noted that the protocol specified in satisfaction of these requirements may not apply directly to the implementation of many of these applications, but the applications indi

24、rectly induce requirements on the protocol at the point of interface where the protocol is implemented. ATIS-0300075 3 The generic requirements for all application types along with the suggested level of requirements, per application, for every single requirement, are specified in Clause 7. Specific

25、 service requirements (such as VOIP) are described in separate documents. 1.4 Target Network/Service Elements Target Network/Service Elements that are involved in some way with the handling of or are aware of packet-based service/s and where packet-based accounting protocol can be implemented and re

26、side include: Soft-switches Passive/active Probes Firewalls Web/Proxy servers Application servers Edge access devices (such as: routers, CSUs/DSUs and modems) There are additional Network/Service Elements that switch, route, handle, treat differentially, or recognize packet-based data, but are dedic

27、ated to a specific application or service (such as VoIP traffic or signaling Network/Service elements). The packet-based accounting protocol can be implemented in these Network/Service Elements as well. Please refer to the specific application/service (e.g., VOIP) accounting management requirements

28、document for more information in this regard. 1.5 Relationship to Other Standards Activities The Internet Protocol Detail Record Organization, Inc. (IPDR.org) has developed a comprehensive solution set for the business problem of management of usage information in IP-based services, concentrating on

29、 the financial-grade requirements of Billing and Supplier/Partner Settlement applications 2. The IPFIX (IP Flow Information eXport) Working Group (WG) at the Internet Engineering Task Force (IETF) went through the process of specifying the requirements for the export of measured IP flow information

30、out of routers, traffic measurement probes, and middle-boxes, while specifically excluding applications requiring financial-grade data management 3. The Third Generation Partnership Project (3GPP) has published technical specifications describing charging architecture and principles regarding GSM/UM

31、TS-based services 4, as well as charging management CDR transfer 5 and charging management CDR file format and transfer 6 where it specifies that “the use of IPDR may optionally be supported on the Bx reference point”. Study Group 13 (SG-13) at the ITU-T drove an effort to harmonize the perspectives

32、 of various standard development organizations (SDOs) with respect to high level requirements and high level reference architecture allowing accounting and charging capabilities in Next Generation Network (NGN). This effort was resulted in the development of the ITU-T recommendation Y.2233. The SDOs

33、 that have been participated in this process include: the ATIS TMOC Accounting Management Task Force, the 3GPP SA5 group, the ETSI TISPAN WG2, the ETSI TISPAN WG8, the ITU-T SG-13 Q.2 and the ITU-T SG-4 Q.8. Additional work in this area including further refinement and in depth analysis is planned t

34、o be continued by the Study Group 4 (SG-4) at the ITU-T. The ATIS TMOC Accounting Management Task Force and the 3GPP SA5 group collaborated to respond to a request from the ITU-T NGNMFG to harmonize architecture and (if possible) protocols, resulting in a single international standard. The results o

35、f this collaboration are included in this standard. ATIS-0300075 4 From these various sources, one of several implementations of protocol for various packet-based services can be specified. The following figure shows the schematic depiction of a family of standards and specifications that will be de

36、veloped for this purpose: IIFIPTV Architecture RequirementsATIS 0800002ITU-TRecommendation Y.2233PTSCVoIP Call FlowsATIS-1000009.2006ATIS-0300075IPDR 3GPPATIS-0300075.1ATIS-0300075.2IPTV Service Specification ATIS-0300075.3VoIP Service SpecificationATIS-0300075.2.xIPDR Service Definition -IPTVATIS-0

37、300075.2.y3GPP Call Data DefinitionIPTVATIS-0300075.3.xIPDR Service Definition -VoIPATIS-0300075.3.y3GPP Call Data DefinitionVoIPFigure 1: Document Family Schematic The documents depicted as “3-D” boxes at the top of this figure are produced by organizations with which ATIS TMOC has a liaison relati

38、onship and from which information is analyzed to produce ATIS and American National Standards, depicted as simple boxes. This document (ATIS-0300075) defines the requirements and reference architecture from which American National Standards in the 75.x “series” are specified. The protocol specificat

39、ion (75.1) specifies a technology-neutral architecture from which specific implementations can be derived. In addition, specific IP-based services which are ATIS-0300075 5 defined in other ATIS organizations such as IIF and PTSC are specified in a similar technology-neutral manner. Technology-specif

40、ic protocol implementations and service specifications can then, in turn, be specified as determined appropriate (documents designated in the figure as 75.2.x, 75.3.x, 75.2.y, and 75.3.y). 2 DEFINITIONS, ACRONYMS, AND ABBREVIATIONS 2.1 Terminology Term Definition Accounting The process of collecting

41、 and analyzing service and resource usage metrics for the purposes of capacity and trend analysis, cost allocation, auditing, and billing, etc. Accounting management requires that resource consumption be measured, rated, assigned, and communicated between appropriate business entities. Accountable U

42、sage Records A record that contains information details regarding which services were provided to which consumers Collector A Collector is a module that is typically part of a BSS. It implements the function of usage data receiving and aggregation. It can collect usage data from one or more Exporter

43、s. There could be more than one Collector connected to one Exporter to improve robustness of the usage information export system. Exporter An Exporter is a module that is typically integrated with the Service Elements software. It enables to produce, record and send out usage data records to an inte

44、rested consumer system (Collector) using an appropriate transfer protocol. Interim Usage Details Usage records describing a service delivery event that cannot be correctly interpreted without context provided by other data. For example, “Start Call” and “Stop Call” entries shall be correlated to eac

45、h other in order to determine call length. Other examples of interim entries might be: Start Application, Service Query, Connect additional line to conference, Drop line from conference, Convert text message to voice, etc. Mediation In view of the eTOM/RDC Charging management; Charging Architecture

46、and Principles“.35 3GPP TS 32.295 Release 7 June 7th 2007 - Telecommunication management; Charging management; Charging Data Record (CDR) transfer .36 3GPP TS 32.297 Release 7 June 7th 2007 - Telecommunication management; Charging management; Charging Data Record (CDR) file format and transfer.37 IT

47、U-T M.3050.0 (03/07) - Enhanced Telecom Operations Map (eTOM) Introduction.28 A Baseline of Security Requirements for the Management Plane, ATIS-0300276.2008.42This document is available from the International Telecommunications Union. 3This document is available from the Third Generation Partnershi

48、p Project (3GPP) at . 4This document is available from the Alliance for Telecommunications Industry Solutions (ATIS), 1200 G Street N.W., Suite 500, Washington, DC 20005. ATIS-0300075 8 5 ARCHITECTURE MODEL 5.1 The ETOM RDC namely: 1. The Network and Service Element (SE) layer 2. The Mediation layer

49、 3. The Operation/Business Support Systems (OSS/BSS) layer Each layer is discussed below: 1. Network and service element layer (NSE): The NSE layer consists of all the network and service elements required to provide an IP-based service to a given customer. For example, routers, access devices and transmission facilities together provide basic connectivity; firewalls might provide a security service; email, file and print servers provide application services; gateways provide a translation service fr