IPDR'ORG Protocol Working Group Update

1
IPDR.ORG Protocol Working GroupUpdate

• Jeff Meyer

2
Agenda

• Introduction
• Q4 01/Q1 02 Group Accomplishments
• Future Protocol Working Group Objectives

3
Introduction

• Group Charter The IPDR Protocols Working group
  will define the notation, syntax, encoding and
  transport used to convey usage information to
  Business Support Systems.

4
Group Structure

• Lead Jeff Meyer, HP jeff_meyer2_at_hp.com
• Editor Ken Sarno, IPDR kensarno_at_ipdr.org
• About 5 other participants over past few months.

5
Group Work Model

• Weekly telecon.
• E-mail submissions
• Web based archive of key references, minutes and
  member contributions.
• Incorporate results into base NDM-U document (in
  particular Ch. 4)
• Guide development of reference library

6
Q4 01/Q1 02 Group Accomplishments

• Contractor selected for Reference Library,
  Infosys
• Requirements defined
• Design reviewed
• Libraries released incrementally and reviewed.
• Libraries available now for C and
  Javahttp//www.ipdr.org/members/protocol/contrib
  s/infosys

7
NDM-U 3.1 Work

• Make corrections based on reference library
  implementation experience.

8
IPDR Library Summary

• The libraries provide mechanisms to both produce
  and consume IPDR documents in either an XML or
  binary format.
• In addition a schema library provides the ability
  to examine a service definition and apply
  validation logic.
• The libraries define a simple programmatic format
  for representing usage events.
• The IPDR file transfer protocol is provided.

9
Key Libraries for common IPDR processing
Data Access Library
real-time via network
source-independent representation (programmatic)
source-independent representation (serialization)
Decode Library
source-independent representation (programmatic)
Encode Library

• binary or
• XML

batch/ offline/ tailing
Persistence
Dictionary Library
Data Dictionary
10
IPDR File Transfer Library
Producer
Consumer
File Delivery
File Access

• binary or
• XML

persistence
Capabilities
IPDRDoc
Control File
IPDRDoc
Range File
Control Files
IPDRDocs
11
Sample IPDR XML Dictionary Fragment
ltelement name subscriberId" type string"gt
ltannotationgt ltdocumentationgt
The identifier of the customer associated
with this event. lt/documentationgt
lt/annotationgt lt/elementgt ltelement name
ipAddress" type ipdripv4Addr"gt
ltannotationgt ltdocumentationgt
IP address of system initiating connection
lt/documentationgt lt/annotationgt lt/elementgt
ltelement name "startTime" type
"timeInstant"gt ltannotationgt
ltdocumentationgt Time instant the
stream starts playing. lt/documentationgt
lt/annotationgt lt/elementgtgt
12
XML Serialized Form Fragment
ltIPDR xsitype"AA-Type"gt
ltsubscriberIdgtjoelt/subscriberIdgt
ltipAddressgt192.168.2.64lt/ipAddressgt
ltnasIdentifiergtnas1.foo.comlt/nasIdgt
ltacctInputOctetsgt13444lt/acctInputOctetsgt
ltacctOutputOctetsgt77777lt/acctOutputOctetsgt
lt/IPDRgt
13
IPDR Compact (binary) Format
header
version
descriptor (0)
ipdrRecorderInfo
event (type 0)
startTime
event (type 0)
defaultNameSpace
event (type 0)
otherNameSpaces
descriptor (1)
serviceDefinitionURI
event (type 1)
docId
event (type 0)
descriptor mark
descriptor (2)
typeName
event (type 1)
descriptorId
event (type 2)
event (type 2)
event (type 0)
...
event mark
docEnd
descriptorId
valueA
valueB
docEnd mark
count
valueC
valueD
endTime
14
Compact Serialized Fragment (hex)
00 00 00 02 00 00 00 01 FF FF FF FF 00 00
00 03 j o e 00 C0 98 40 20 00 00 00
0C n a s 1 . f o o . c o m
00 00 34 84 00 01 2F DF
15
Future Work for Protocol WG

• Define means for representing other structures
  beyond First Normal Form, in particular
  sublists (e.g. legs of conference call grouped in
  a single record)
• Refine direct communication models for realtime
  delivery. (Currently have SOAP model, but other
  streaming options are available with
  CompactIPDR)