AMADNS: A Usage Data Transport and Processing System
March 30, 1994
Mike Kogut
Bellcore
908-758-5222
kogut@cc.bellcore.com
Shoshi Loeb
Bellcore
201-829-4528
shoshi@thumper.bellcore.com
Outline
- Logical Architecture
- Interface Protocols
- Mapping to Internet Accounting Architecture
- System Features
- Specialized Processing
- Implementation Plans
- Conclusion
Logical Architecture
Figure
(GIF - 20274 bytes)
Interface Protocols
Table
(GIF - 24558 bytes)
Mapping of AMADNS to Internet Accounting Architecture
Figure
(GIF - 31477 bytes)
System Features
- Sender- and receiver-initiated data transfer
- Near-real-time data availability
- Standard protocols
- Specialized data processing
- Standard centralized system management
The Need for Usage Data Processing
- Usage data collected within the Internet accounting system
needs to be processed and managed
- Some of the data processing and management functions (e.g.,
aggregation) need to be done close to the network (e.g., at the
Meter), while others (e.g., correlation) may need to the done
close to the application
- The processing and management needs are likely to evolve over
time, as the needs for usage data develop
- There is a need for a flexible and extensible application
creation environment for applications that process or use the
usage data
Specialized Processing Examples
- Aggregation - a summation of usage events as described by
specific criteria, e.g., time interval
- Correlation - an association of usage events based on single
service or product instance
- Distribution - the filtering and forwarding of incoming
usage data records to different outgoing files
- Format conversion - the transformation of usage data
- Surveillance - the monitoring of usage data to detect
deviations from established norms
- Validation - the inspection of usage data to ensure integrity
Where should the specialized processing functions reside?
Figure
(GIF - 14782 bytes)
Concluding Remarks
- The generic requirements that define the AMADNS components are
completed and available to the community (Generic Requirements
are equivalent to industry standards
- We would like to assist in adapting any aspect of the AMADNS
work to help the working group reach its goals