Call Detail Records for UNI 1.0

Dan SpearsDirector – Applications Marketing

CIENA Corporation

Types of Telecommunications Services Not Usage-based

• Examples include traditional transport services• Provisioned via operations system• Typically billed on a flat-rate monthly basis

Usage-based• Examples include traditional telephone services• Dynamically established using signaling messages• Typically billed based on usage (e.g. connection

duration, bandwidth, distance between endpoint, etc.)

O-UNI

UNI

Connection request

Client requests connection between client source and destination Client sees optical network as a “cloud” Optical network responsible for routing connection to destination

OpticalNetwork

Billing for OIF UNI Connections Each carrier will choose how to bill for OIF UNI

connections• Flat-rate• Charge per connection based on usage

Usage-based billing requires ability to capture usage info

CDR-01 – Call Detail Records for UNI 1.0

Specifies what usage information is to be collected,when it is collected, and how it is formatted

Processing of Call Detail Records

Client Client

Carrier’s Optical NetworkCarrier’s Optical Network

UNI UNI

CallDetail

Records

Carrier’sBillingSystem

UNI 1.0 Connection

Content of Call Detail Record Content of a Call Detail Record:

• Call Type• Generating System• Recording Office• Connect Date• Timing Indicator• Connect Time• Elapsed Time• GMT Time Zone• Release Cause (Optional)• Source Transport Network Address• Source Logical Port Identifier

(Optional)• Destination Transport Network Address• Destination Logical Port Identifier

(Optional)• Local Connection Identifier

• Encoding Type• Traffic Parameters• Directionality• Generalized Payload

Identifier• Service Level• Diversity• Contract ID (Optional)

Call Detail Record Formats

Three CDR Formats Specified in CDR-01 Implementation Agreement:• Telcordia Billing AMA Format (BAF)• ASCII Format (ACDR)• XML Format (XCDR)

Summary

CDR-01(Call Detail Records-01)• Specifies what information is collected, when

it is collected, and how it is formatted for a UNI 1.0 connection

• Enables carriers to bill for UNI 1.0 connections on a usage-sensitive basis