|Connected Services Framework 3.0 - Billing Standard Business Event|
|Building Solutions with the Billing Standard Business Event|
This section describes how to set up the BillingSBE to provide solutions so that your billing systems can receive usage data from and exchange advice of charge data with VAS systems.
The BillingSBE uses WSE Policy to apply security and encryption to asynchronous messages that it sends to your billing systems.
The most common method of routing billing usage data into the BillingSBE is to subscribe it to receive a known raw billing event from a VAS system. A known raw billing event is one whose details, such as the VAS system endpoint and the root element in the message body, are known in advance.
Unsolicited events are messages containing usage data that arrive at the BillingSBE for which it has not been subscribed. For example, the Service Logic component in a solution created by using the Order Handling Standard Business Event (OHSBE) may open a session with the BillingSBE and send billing usage data whenever an order is completed. The steps to register a transform, subscribe a billing system to a transformed event, and configure the delivery settings for the transformed event are the same for both solicited and unsolicited events; however, you create the session differently to receive unsolicited events.
You can use the BillingSBE to discover and subscribe to raw billing events that are sourced by certain VAS systems.
Microsoft recommends that you implement billing systems and VAS systems that participate in solutions that are provided by the BillingSBE as Well-enabled Services. However, in many scenarios this may not be possible. For example, in the case of legacy systems or VAS systems that are maintained by your business partners. For these systems you must create an adapter that enables them to participate in the Connected Services Framework environment.