OSS/J

Questionnaire for Qualified Products
OSS Billing Mediation API (JSR 130)

Company: Highdeal
Product: Highdeal Transactive
Version: 3.0

• G.01 - Is the product tested against the Reference Implementation?

  Yes

  Comments: Please note that only the client part of the API has been developed.
  This implementation has been tested against the Reference Implementation, to ensure that it was able to query/receive events and display the usage content.

• G.02 - Is the product tested against certified products?
  If yes list for each product the company name, product name, version, and testing procedure

  No

• G.03 - Is the product client of the JVT implementation of the API?
  If yes list the company name, product name, and version of all application servers the product has been tested against

  Yes

  Comments: Implementation made by Sun MicroSystem, for the Sun mail server, using Bea Weblogic as an Application Server.

• G.04 - Is the product client of the XML/JMS implementation of the API?
  If yes list the company name, product name, and version of all application servers the product has been tested against

  No

  Comments: Implementation made by Nec, using JBoss as an Application server.

• Does the product consist of EJBs that run in the same application server(s) of the OSS/J API implementation?
  Please list the company name, product name, and version of all application servers supporting the product, if any

  No

• G.06 - Does the product use the full API?
  If not please list features not used (or used, if only few)

  No

  Comments: Features used:

  • client side feature of the API, including queries on the supported features or capabilities of the JVTProducerSession object
  • ability to look up for producer of events,
  • ability to handle the events sent by the producer (mainly UsageDataAvailableEvent)

• G.07 - Does the product use extended features of the API?
  If yes please list them (optional features, specific extensions)

  No

• G.08 - Is the application supporting extensibility as defined by the OSS/J Design Guidelines?

  No

• G.09 - For each used event defined by the API, please indicate how the event is handled: a) event is ignored; b) event is simply displayed; c) event is used as input for further processing.

  Comments: All events are displayed. In addition, the UsageEventAvailableEvent produces a rating action that extracts the usage content, and sends it for rating and billing to Highdeal Rating and Billing system.

• G.10 - Is the application able to handle all exceptions thrown by the used features of the API?

  No

  Comments: Basic exception management has been implemented for this first version, with no discrimination or special treatment of the exception raised.

• G.11 - Is the application able to handle all return types?

  No

  Comments: Only the types expected from the producer and agreed upon before are handled.

• S.01 - Please list all supported of data formats, encodings and schemas. For each of the above, list the data transfer methods that are supported (file-based or UsageRecValueIterator)

  Comments: [all through UsageRecValueterator]

  • IPDR for email (Network Data Management – Usage (NDM-U) For IP-Based Services Service Specification– E-mail - Version 3.0-A.0)
  • IPDR for Wholesale (Network Data Management – Usage (NDM-U) For IP-Based Services Service Specification– Wholesale IP Bandwidth (WS) Version 3.0-A.0)

• S.02 - Is transfer status monitoring supported?

  No

• S.03 - Is usage data query supported?

  Yes

  Comments: The client application is able to query for data, however this ability mainly relies on the event producer capabilities.