Internet Protocol Detail Record (IPDR) to SID Mapping: Introduction

Internet Protocol Detail Record (IPDR) to SID Mapping: Introduction : Object diagram

Created:	6/5/2022 11:02:15 AM
Modified:	6/8/2022 7:30:21 AM
Project:
Author:	Cecile ludwichowski
Version:	1.0
Advanced:
ID:	{B1FE1CD5-85A1-49dc-A36D-ECC984CF64C0}

One of the main purposes of the SID is to act as the telecommunication world map and used as the universal language for developer and operators. The SID describes the telecommunication information model. It includes the different components and the relation between them. In the industry there are existing OSS and BSS implementations for the telecommunication as well as different standards that are based on different telecommunication data models. The SID developed in order to improve the communication and enable better understanding of requirements in one hand and better understating of the different solutions on the other hand. Mapping each of the existing data models to one agreed information model (i.e. the SID) will enable seamless integration between different OSS and BSS products and solutions and will save a lot of time and money. The IPDR.org, now part of the TM Forum, is an open consortium of leading service providers, equipment vendors, system integrators, and billing and mediation vendors collaborating to facilitate the exchange of usage and control data between network and hosting elements and operations and business support systems by deployment of IPDR standards. Among other things it defines the usage records or in other words the fields that should be present in Internet Protocol Detail Record (IPDR) document for each class of service (Service Specifications). The formal definition language for Service Specifications is XML Schema. Additional standards under development to address by IPDR.org are provisioning and settlement of next-generation data services. Mapping the IP Detail Records to the SID will leverage the SID as the universal telecommunication map in one hand and will enable seamless adoption of the IPDR.org products and artifacts by the industry. Purpose and Scope The purpose of this chapter is to present mapping between the IPDR.org data model to the SID. The scope includes mapping of all the entities modeled by IPDR.org into the SID. It includes the way to map the IPDR Service Specifications, and mapping of the relevant IPDR Streaming Protocol (IPDR/SP) data model. Out of scope It was agreed that IPDR documents (IPDRDocs) are more of an implementation artifact, while the SID is focused on an information model (logical) therefore IPDRDocs is not modeled in the SID and out of the scope of this document. It was also agreed that although Supplier/Partner Settlements (S/PS) supposed to be modeled in the SID, it will be out of the scope in the first stage and the mapping between the S/PS data model in the IPDR.org and the SID will be done later in one of the next versions of this document. Terminology <ul>
<li>IPDR Service Specification – a document that is intended to specify the business use case and formal XML Schema for specific service such as VoIP, DOCSIS, etc. In this document the "IPDR Service Specification" can be treat to an xsd schema or even just to the relevant business record type definition in the xsd file (for example: IPDR-VoIP-Type, IPDR-SM-Type, etc.).</li><li>SID UsageSpecification – a formal description to describe what is defining the Usage Meta Data. Instance of service specification is the Meta data for specific Usage record.</li></ul>
Clarification There are at least two approaches that can be used to model IPDRs.As we agreed in the IPDR-SID sub team, we are going to present two modelling approaches. Other relevant documents <ul>
<li>Shared Information/Data (SID) Model; Addendum 2 Customer Business Entity Definitions (Release 7.0)</li><li>IPDR Service Specification Design Guide Version 3.5.1</li></ul>
- IPDRType.xsd - PDRDoc3.5.1.xsd <ul>
<li>All the IPDR Service Specification files and the relevant xsd files.</li></ul>
- Service Specification “ Public WLAN Access Version 3.5-A.0.1 - PublicWLANAccess3.5-A.0.1.xsd <ul>
<li>IPDR/SP Protocol Specification Version 2.1 (Future versions of this document will map to more advanced versions of IPDR and IPDR/SP)</li></ul>
IPDR Base Model Note: The "IPDR base model" data model is derived from the IPDR Service Specification Design Guide Version 3.5.1 and the set of IPDR Service Specifications. IPDR/SP The IPDR/SP specification provides an advanced streaming protocol for detail records and especially accounting information exchange. It delivers a compelling solution to the technical and business challenges faced by the next-generation equipment and server vendors.One of the key design requirements was achieving reliability while optimizing network element resources, network bandwidth, and collection system resources. The protocol achieves these efficiencies by controlling or limiting the exported network data to only that which is requested by the collection system. Other characteristics of IPDR/SP include: interoperability across multiple vendors, versions and record structure through the use of protocol negotiation features; flexible record structures, supporting vendor specific extensions and a wide variety of services; support for a wide range of billing models; and back-end compatibility for a wide variety of OSS/BSS functions. IPDR/SP leverage the IPDR base model and use IPDR Service Specification as reference in its Template definitions. The IPDR/SP enable negotiate the usage records template. In order to do it, IPDR/SP modelled the usage Meta data (and not just the usage record itself). Note: The IPDR/SP data model is derived from the IPDR/SP IDL message definitions.