HK1167052B - Method, system and apparatus for facilitating reconciliation of accounts between different operators - Google Patents

Abstract

A system that enables reconciliation of accounts between a mobile virtual network operator (MVNO) and a mobile host operator (MHO) includes an asset loader server that receives data that defines a user event. The asset loader server generates a wholesale bill associated with the user event. The rate charged in the generated wholesale bill is based on a negotiated rate between the MVNO and the MHO that is different that the may be different than the rate at which the MVNO charges the user. The asset loader communicates the generated wholesale bill to a billing interface of the MNVO that is configured to receive an extensible markup language (XML) file that defines a wholesale bill associated with the MHO. The format of the generated wholesale bill is substantially the same as the format of the XML file associated with the MHO.

Description

Method, system and apparatus for supporting account reconciliation between different operators

Technical Field

The present invention relates generally to the checking (reconcile) of charging data in a telecommunications network. More particularly, the present invention relates to implementing a system that supports account reconciliation between a mobile virtual network operator ("MVNO") and a mobile host operator ("MHO").

Background

In recent years, the telecommunications industry has grown at an unprecedented rate. More and more consumers and merchants rely on communication technologies available over mobile networks. These consumers and merchants require their account accuracy to the minute level to ensure that they are fully aware of the costs associated with their mobile activities. To remain competitive, carriers respond to these demands. Thus, the ability to accurately bill a consumer for usage of a telecommunications network is a fundamental function of a telecommunications provider.

Mobile Host Operators (MHOs), such as cellular telephone network providers, have frequency and network capabilities to provide services to mobile subscribers. Generally, MHO needs to acquire a radio spectrum license from the government of the country in which it wishes to operate. MHOs have their own mobile infrastructure and can operate their own network routes. When MHOs provide mobile networks with their bandwidth and licenses, in some cases they do not have the service capabilities or resources to manage the service and end user needs and/or to fully commercialize the wireless spectrum licenses they have been granted.

In an effort to more fully commercialize wireless spectrum licenses, MHOs may come into contact with one or more third party service providers that provide services to end users. For example, the investment service may provide an application and/or hardware to the end-user client for performing stock trading. The application and/or hardware may communicate with one or more servers operated by the service provider via the network infrastructure provided by the MHO. In some cases, the end user is only in contact with and facing the service provider, and is not even aware that the MHO is providing the network infrastructure and not the service provider. Hereinafter, these types of service providers are referred to as Mobile Virtual Network Operators (MVNOs).

In the arrangement described above, the MHO may send a bill to the MVNO reflecting network usage associated with the client of the MVNO. However, in some cases, the bill may not accurately reflect the actual use of the client of the MVNO. For MVNOs with a large number of clients, it may be difficult to ascertain the accuracy of the bill.

Disclosure of Invention

One aspect of the present invention relates to a system and corresponding computer-implemented method that supports account reconciliation between a Mobile Virtual Network Operator (MVNO) and a Mobile Host Operator (MHO), wherein the system comprises: an asset loader server that receives data defining a user event. The asset loader server generates a wholesale bill associated with the user event. The rate charged in the generated wholesale bill is based on a negotiated rate between the MVNO and the MHO, which may be different than the rate charged by the MVNO for its clients. The asset loader server transmits the generated wholesale bill to a billing interface of the MVNO, the billing interface of the MVNO configured to receive an extensible markup language (XML) file, the XML file defining the wholesale bill associated with the MHO. The format of the generated wholesale bill is substantially the same as the format of the XML file associated with the MHO.

In another general aspect, there is provided a computer program product comprising computer readable instructions which, when loaded and run in a computer system and/or computer network system, cause the computer system and/or computer network system to perform the method as described.

The subject matter described in this specification can be implemented as a method or system or using a computer program product, tangibly embodied in an information carrier, such as a CD-ROM, DVD-ROM, semiconductor memory, a signal and/or data stream, and a hard disk. Such computer program products may cause a data processing apparatus to perform one or more operations described in this specification.

In addition, the subject matter described in this specification can also be implemented as a system that includes a processor and a memory coupled to the processor. The memory may encode one or more programs that cause the processor to perform one or more of the method acts described in this specification. Further, the subject matter described in this specification can be implemented using various MRI machines.

Drawings

The accompanying drawings form a part of the specification and the display, and illustrate specific exemplary embodiments thereof. The modules in the drawings are not necessarily to scale, emphasis instead being placed upon illustrating the principles of the invention. Moreover, in the figures, like reference numerals designate corresponding parts throughout the different views. The principles described herein, however, may be embodied in many different forms and this description should not be construed as limiting the claims. Rather, these embodiments are provided so that this disclosure will be thorough and complete.

FIG. 1 illustrates an exemplary MHO/MVNO environment;

FIG. 2 illustrates an exemplary embodiment of an MVNO system architecture according to the present invention;

FIG. 3 illustrates an exemplary embodiment of an asset loader server to be used with the MVNO system architecture of FIG. 2, in accordance with the present invention;

FIG. 4 illustrates exemplary operation of the asset loader server of FIG. 3; and

FIG. 5 illustrates a general computer system, which may represent any of the computing devices referenced herein.

Detailed Description

The exemplary embodiments below describe an asset loader server. Typically, the asset loader server is configured to retrieve data from an audit/tracking table database of a billing system operated by the MVNO, the data defining individual retail accounts associated with MVNO clients. The asset loader then generates an XML structured file that defines a wholesale bill for each retail account based on the information defined in the contract between the MHO and the MVNO. The asset loader server then transmits the XML file to the billing system of the MVNO via the billing interface of the billing system. The billing interface is configured to receive an XML structured file from an HMO that defines a wholesale bill. The XML format of the wholesale bill generated by the asset loader server is formatted in a similar manner to the XML file transmitted from the MHO so that the charging interface of the charging system does not have to be reconfigured.

For services of the MHO used by the MVNO client, the described embodiments advantageously allow easy reconsolidation (reconsolidation) of the bills transmitted by the MHO to the MVNO, which are difficult or even impossible to check manually. Another advantage is that the asset loader server generates a virtual bill associated with each MVNO client and transmits it to a billing system (which may be configured to reconcile MHO bills via an interface of the billing system that receives the bills from the MHOs). In other words, the billing system does not have to be reconfigured.

FIG. 1 shows an MHO/MVNO environment 100. The MHO110, MVNO120, contract 130, mobile host operator network ("MHON") 140, and one or more MVNO clients 150 are shown. As described above, the MHO110 may own and operate a network infrastructure, such as the MHON 140. The MVNO120 may join a contract 130 with the MHO110 to gain access to the MHON140 to provide mobile services to the MVNO client 150.

The contract 130 between the MHO110 and the MVNO120 may require: the MVNO120 is charged the full network traffic charge associated with the MVNO client 150 according to a contractually agreed fee schedule or a negotiated billing plan between the MHO110 and the MVNO 120. The cost plan in the contract 130 is sometimes referred to as a wholesale catalog. The wholesale catalog contains pricing rules for each service provided by the MHO used by the MVNO client 150. The wholesale catalog includes pricing rules for various events generated by the MVNO client 150, such as termination and marking events. The termination event represents the cost the MVNO120 pays to the MHO110 for each event that starts from or arrives at the MVNO client 150 using the MHO network 140. The tagged events represent the cost that the MHO110 pays the MVNO120 for each event that reaches the MVNO120 client 150 that spans the MHO110 network but starts at a different MHO carrier's network. Each event generated by the MVNO client 150 is associated with one or both of the above events.

The MHO110 may track all network activities associated with all MVNO clients 150. The MHO110 may send MHO reports 137 of all such activities to the billing system of the MVNO120 in a batch manner. The MHO report 137 may include a list of all costs associated with the MVNO client 150 usage of the MHON 140. For example, the MHO report 137 may include a list of network time amounts and dates used by the MVNO client 150. Alternatively, the MHO report 137 may simply report an amount representing the overall usage of the MHO110 network by all the MVNO clients 150. However, MHO reports 137 may not divide the use of MHON140 by individual MVNO clients 150, which makes it difficult for the MVNO120 to determine the accuracy of the MHO reports 137 based solely on the information in the MHO reports 137.

The MHO110 may also send a single wholesale bill/ticket 135 to the MVNO120 associated with the MHO report 137. Wholesale bill 135 lists the charges associated with the activity reported in MHO report 137. These charges may be based on a contract 130 between the MHO110 and the MVNO 120. The wholesale bill 135 and MHO report 137 may be sent to the MVNO120 in an extensible markup language (XML) formatted data file 133.

In some cases, a given MVNO120 may have thousands of MVNO clients 150. MVNO clients 150 may be individual mobile subscribers or companies with several subscribers using cell phones, PDAs, or operable to transmit information via MHON140 to access services provided by MVNOs 120. In some cases, the MVNO120 has a direct relationship with the MVNO clients 150 and handles client services, account establishment, and related billing associated with each MVNO client 150.

The MVNO120 determines usage data for each MVNO client 150. The usage data may include MVNO client 150 usage of MVNO120 services (hereinafter "service usage") and MHON140 (hereinafter "MHON usage"). For example, the MVNO120 may determine MHON usage by determining the duration of the MVNO120 server accessed by the MVNO client 150, the type of service requested, the amount of data downloaded, and/or whether the service is used within the network or when it is roaming. After determining the usage data, the MVNO120 may generate a retail bill 139 for each MVNO client 150. The MVNO120 may bill each MVNO client 150 based on the type of transaction and/or amount of usage requested by the MVNO client 150.

The retail bill 139 prepared by the MVNO120 for each MVNO client 150 may be based on a cost plan that is different from the cost plan specified in the contract 130 between the MVNO120 and the MHO 110. The cost plan may define various rates for different types of events generated by individual MVNO clients 150. For example, the cost plan may define a service usage rate for a particular service utilizing MVNOs 120. The cost plan may also define MHON usage rates associated with MHON140 usage. The rate stated in the cost plan may be based on a wholesale price charged by the MHO and is referred to hereinafter as a wholesale price. As described below, the MVNO120 may include a billing system that charges the MVNO client 150, in part, using wholesale prices from the cost plan.

In accordance with a preferred embodiment of the present invention, the MVNO120 may compare the wholesale bill 135 transmitted from the MHO110 with the usage data for each MVNO client 150 to ensure the accuracy of the wholesale bill 135. The MVNO120 verifies the wholesale bill 135 by comparing the wholesale bill 135 with the generated wholesale bills 135 associated with each MVNO client 150. The MVNO120 may include or be in communication with an asset loader server (such as the asset loader server 210 described below with respect to fig. 2) that generates a wholesale bill for each MVNO client 150. The charges listed in the generated wholesale bill for each MVNO client 150 are based in part on the rates defined in the contract 130 between the MHO110 and the MVNO 120. The asset loader server may transmit the generated wholesale bill for each MVNO client 150 to the billing interface of the MVNO 120. The MVNO120 may then sum the charges in the wholesale bill generated for each MVNO client 150 to obtain an aggregate charge for the MVNO clients 150. The MVNO120 may then compare the aggregate charge from the generated wholesale bill to the charges listed in the wholesale bill 135 to determine whether the wholesale bill 135 is accurate. In a preferred embodiment, the comparison allows for minor differences between bills. The comparison may be performed automatically by the billing system of the MVNO120 and/or the operator of the MVNO 120.

Fig. 2 illustrates an exemplary MVNO system architecture 200, which may correspond to MVNO120 described above. MVNO system architecture 200 is referred to herein as MVNO 200. MVNO 200 includes a billing envelope/interface 205, an asset loader server 210, a billing system 215, and an audit/tracking table (ATT) database 220.

The billing interface 205 may implement a set of web service functions for interfacing the billing system 215 with other systems, such as the system of the MHO110 of fig. 1, that communicate with the wholesale bill 135 of fig. 1. The Web service may define functionality to receive and interpret files in XML format, such as wholesale bills 135. The billing interface 205 may be configured to store the received XML file and other details regarding the ATT database 220.

The billing interface 205 may also implement a collection of web services that support receiving retail data 207, the retail data 207 defining retail events initiated by the MVNO client 150, such as requests with the MVNO 200 application server. Billing interface 205 stores retail data 207 in a retail data file that resides in ATT database 220 or a different database. Retail data 207 may define MVNO client IDs, timestamps associated with events, durations of MHO usage, durations of MVNO service usage, customer prices associated with MVNO clients, transaction type identification information, and/or other data.

The billing system 215 is in communication with the billing interface 205 and the ATT database 220 and is generally configured to manage billing and revenue associated with the MVNO 200. The billing system 215 may correspond to an Oracle BRM (billing and revenue management system) or a different billing system. The billing system 215 may be configured to perform various billing-related functions. For example, billing system 215 may process retail data 207 transmitted via billing interface 205 to generate a ticket to be sent to MVNO client 150 in fig. 1. The billing system 215 may process the XML formatted data file 133 (including the wholesale bill 135 and MHO report 137) transmitted by the MHO 110. For example, the billing system 215 may determine the amount specified in the wholesale bill 135 from the MHO110 and may direct funds from the bank account of the MVNO120 to the MHO 110. The billing system 215 may be configured to create a virtual wholesale account for each MVNO client 150 when the generated wholesale bill for the MVNO client 150 is received for the first time, for example from the asset loader server 210. Once a virtual wholesale account is created for a particular MVNO client 150, the billing system 215 may be configured to update the account when a newly generated wholesale bill is received from the asset loader server 210.

The billing system 215 may also be configured to check the generated wholesale bill transmitted by the asset loader server 210 per MVNO client 150 against the wholesale bill 135 transmitted from the MHO for all MVNO clients 150. For example, the billing system 215 may sum the charges in the generated wholesale bill for each MVNO client 150 to obtain an aggregate charge and compare the aggregate charge to the charges in the wholesale bill 135. The billing system 215 may be configured to perform other billing-related functions.

The asset loader server 210 is in communication with the billing interface 205 and the ATT database 220 and is configured to generate and transmit to the billing interface 205 a wholesale bill 230 in XML format for each MVNO client 150 based on the retail data 207 stored in the ATT database 220. The billing interface 205 may then transmit the generated wholesale bill 230 to the billing system 215 to create or update a virtual wholesale account associated with each of the respective MVNO clients 150.

In operation, the asset loader server 210 creates a virtual wholesale account to represent the MHO 110. In turn, asset loader server 210 generates a wholesale bill 230 for each MVNO client retail account located in ATT database 220. The generated wholesale bill 230 defines the MVNO client 150 usage data in terms of a rate defined in the contract 130 between the MHO110 and the MVNO 120. In other words, the rate defined in the contract 130 is for the rate in the generated wholesale bill 230. Each time the MVNO client 150 triggers an event, the billing system 215 updates the retail account balance according to the tariff plan between the MVNO120 and the MVNO client 150, and updates the wholesale account balance associated with the MVNO client 150 according to the contract 130 between the MHO110 and the MVNO 120.

In some implementations, the asset loader server 210 resides within the MVNO system. In other embodiments, asset loader server 210 may reside outside MVNO120 and may communicate with the MVNO system via a network such as the internet.

Fig. 3 illustrates an exemplary asset loader server 300, which may correspond to the asset loader server 210 of fig. 2 described above. Asset loader server 300 includes a processor 320 and a structure table database 315. The processor 320 may correspond to a microprocessor based microprocessorOrOr a different computer. Processor 320 may include an operating system, such as Microsoft basedLinux, or the likeThe operating system of (1). The processor may be configured to communicate with other computers via the interface. For example, the processor may include a network interface that supports communication between the asset loader server 300 and the billing interface 205, the ATT database 220, the billing system 215, or any other system described herein.

Processor 320 may include code and logic to implement Simple Object Access Protocol (SOAP) based tool 305. SOAP tool 305 is operable to create, modify, update, delete, and perform other functions on XML files transmitted from billing interface 205 of fig. 2. The SOAP tool 305 is further configured to transmit the reassembled XML file to the billing interface 205. The reassembled XML file is exported from the retail account to manage wholesale accounts on the billing system. The SOAP tool 305 updates the structure table database 315 with a response received by the envelope 205 or billing interface of fig. 2 by transmitting an update request, such as an SQL update request, to the billing envelope.

For each MVNO account, SOAP tool 305 generates a wholesale XML SOAP file and sends a request to billing interface 205 to process the XML SOAP file. Each generated wholesale XML SOAP file represents a virtual wholesale account associated with the MVNO client account. The generated wholesale XML SOAP file includes wholesale pricing rules based on the contract 130 between the MVNO120 and the MHO 110. The billing interface 205 of fig. 1 processes the request and sends a response to the SOAP tool 305. The SOAP tool 305 is configured to perform several parallel processes, creating a large number of XML files in a few seconds. This feature reduces the necessary resources and improves performance.

The processor 320 also includes code and logic to implement the script executor 310. The script executor 310 is operable to execute scripts, such as structured query language ("SQL") scripts 420. For example, script inserter 310 may implement a relational database management system such as Microsoft SQLServer.

The script is further operable to cause script executor 310 to extract retail data 207 stored in ATT database 220; formatting retail data 207; and inserting formatted retail data 207 into structural table database 315.

The XML format generated by the script executor 310 is used to manage retail customers and wholesale customers. Each entry in the structure table of structure table database 315 represents a particular type of operation for maintaining each account asset. Each row in the structure table specifies the XML details that need to be processed and the result of the operation performed.

Fig. 4 illustrates exemplary operations of an asset loader server 300 (fig. 3) that may be performed in MVNO 200 of fig. 2. At block 400, unprocessed accounts and assets may be determined. For example, script inserter 310 may extract unprocessed retail account data from ATT database 220 and insert the data into structure table database 315.

At block 405, the SOAP tool 305 may retrieve unprocessed retail accounts and assets from the structure table database 315.

At block 410, the SOAP tool 305 may generate a wholesale bill according to the XML structure. The format of the generated wholesale bill may be structured to be the same as the XML format of the wholesale bill transmitted from the MHO110 of fig. 1.

At block 415, the SOAP tool 305 may transmit a request to the billing interface 205 for billing account and asset creation. The SOAP tool 305 may transmit the XML formatted wholesale file generated at block 410 with the request.

At block 420, the SOAP tool 305 may receive a response from the billing interface 205. The response may indicate: billing accounts and assets have been successfully created within MVNO billing systems.

At block 425, if there are additional accounts for the analysis, the operations repeat from block 400. Otherwise, the operation ends. In some implementations, the operations from block diagram 400 may be performed on a periodic basis, such as daily or weekly. Operations may also be performed at other intervals.

Fig. 5 illustrates a general computer system 500 that may represent the processor 320 (fig. 3) of the asset loader server 300 of fig. 3 or any other computing device referenced herein. The computer system 500 may include a set of instructions 545, which set of instructions 545 may be executed to cause the computer system 500 to perform any one or more of the methods or computer-based functions disclosed herein. The computer system 500 may operate as a standalone device or may be connected (e.g., using a network) to other computer systems or peripheral devices.

In a networked deployment, the computer system 500 may operate in the capacity of a server, or as a client user computer in a server-client user network environment, or as an endpoint computer system in a peer-to-peer (or distributed) network environment. The computer system 500 may also be implemented as or incorporated into various devices, such as a personal computer or a mobile device capable of executing a set of instructions 545 (serial or otherwise), the set of instructions 545 specifying actions to be taken by the machine. Further, each of the described systems may include any collection of subsystems that individually or jointly execute a set or multiple sets of instructions to perform one or more computer functions.

Computer system 500 may include one or more memory devices 510, such as ATT database 220 and/or fabric table database 315, on a bus for transferring information. Additionally, the code is operable to cause the computer system to perform any of the acts or operations described herein that may be stored in the memory 510. The memory 510 may be a random access memory, a read only memory, a programmable memory, a hard disk device, or any other type of memory or storage device.

Computer system 500 may include a display 530, such as a Liquid Crystal Display (LCD), Cathode Ray Tube (CRT), or any other display suitable for communicating information. The display 530 may serve as an interface to a user to view the functional operation of the processor 505, or in particular to interface with software stored in the memory 510 or drive unit 515.

Additionally, computer system 500 may include an input device 525, such as a keyboard or mouse, configured to allow a user to interact with any of the components of system 500.

The computer system 500 may also include a disk or optical drive unit 515. The disk drive unit 515 may include a computer-readable medium 540 in which one or more sets of instructions 545, e.g., software, may be implemented. Further, the instructions 545 may perform one or more of the operations described herein. The instructions 545 may reside, completely or at least partially, within the memory 510 and/or within the processor 505 during execution by the computer system 500. The memory 510 and processor 505 may also include computer-readable media as described above.

Computer system 500 may include a communication interface 535 to support communication via a network 550. The network 550 may include a wired network, a wireless network, or a combination thereof. Communication interface 535 the network may support communication via any number of communication standards, such as 802.11, 802.12, 802.20, WiMax, cellular telephone standards, or other communication standards.

Thus, the methods and systems may be implemented in hardware, software, or a combination of hardware and software. The method and system may be realized in a centralized fashion in at least one computer system, or in a distributed fashion where different elements are spread across several interconnected computer systems. Any kind of computer system or other apparatus adapted for carrying out the methods described herein. A typical combination of hardware and software could be a general purpose computer system with a computer program that, when being loaded and executed, controls the computer system such that it carries out the methods described herein.

The methods and systems may also be implemented in a computer program product that includes all the features enabling the implementation of the operations described herein, which operations are capable of being performed when loaded in a computer system. Computer program in the present context means any expression, in any language, code or notation, of a set of instructions intended to cause a system having an information processing capability to perform a particular function either directly or sequentially or both: a) conversion to another language, code or notation; b) replicated in different material forms.

As shown, the asset loader servers 210, 300 support the MNVO to check the accuracy of the wholesale bill transmitted from the MHO. For example, the asset loader server generates a wholesale bill associated with each MVNO client. The generated wholesale bill represents the transaction of the MVNO client 150 in terms of the overhead specified in the contract between the MHO110 and the MVNO 120. The asset loader server 210, 300 transmits the generated wholesale bill to the billing interface 205 of the MNVO 120. The format of the generated wholesale bill may match the format of the wholesale bill transmitted from the MHO110 to support transmission of the generated wholesale bill to the billing system without having to customize the billing interface 205. The billing system may then compare the generated wholesale bill with the wholesale bill transmitted from the MHO110 to verify the accuracy of the MHO wholesale bill 135.

While the method and system have been described with reference to particular embodiments, it will be understood by those skilled in the art that various changes may be made and equivalents may be substituted without departing from the scope thereof. In addition, many modifications may be made to adapt a particular situation or material to the teachings without departing from the scope thereof. Therefore, it is intended that the present method and system not be limited to the particular embodiments disclosed, but that the method and system may include all embodiments falling within the scope of the appended claims.

Claims (18)

1. A computer-implemented method of supporting account reconciliation between a mobile virtual network operator, MVNO, and a mobile host operator, MHO, the method comprising:

receiving, by an asset loader server from an MVNO database, data defining retail account information for a plurality of MVNO clients using services provided by the MVNO;

receiving an MHO wholesale bill at the MVNO, the MHO wholesale bill specifying an aggregate cost associated with usage of MHO services by the plurality of MVNO clients;

receiving, by the asset loader server, data defining a wholesale catalog defining pricing rules for each service provided by the MHO used by an MVNO client of the plurality of MVNO clients;

receiving, by the asset loader server, data defining MVNO client events associated with the plurality of MVNO clients from the MVNO database, wherein the MVNO charges each MVNO client at a retail rate associated with the corresponding client event, and wherein when the MVNO determines that an MVNO resource has been used by the client, the MVNO stores the data defining the MVNO client event into the MVNO database;

generating, by the asset loader server, a plurality of virtual wholesale bills associated with the plurality of MVNO clients based on the MVNO client events and pricing rules in the wholesale directory, wherein each virtual wholesale bill comprises overhead associated with use of the MHO service by a given MVNO client, and wherein the virtual wholesale bills are represented as extensible markup language (XML) files formatted to match a format of an MHO wholesale bill;

transmitting, by the asset loader server, the virtual wholesale bill to a billing interface of the MVNO, the billing interface configured to receive the MHO wholesale bill;

accumulating the costs for each virtual wholesale bill to determine a total cost associated with the plurality of virtual wholesale bills; and

comparing, by a billing system of the MVNO, the accumulated total costs to the aggregate costs specified in the MHO wholesale bill to determine whether the accumulated total costs and the aggregate costs match.

2. The computer-implemented method of claim 1, wherein the data defining the MVNO client event is selected from the group consisting of: a user ID, a timestamp associated with the event, a duration of use, and a user retail price.

3. The computer-implemented method of claim 1, further comprising: extracting, by a scripting tool, data defining the MVNO client event from a database of the MVNO.

4. The computer-implemented method of claim 3, further comprising: processing, by the scripting tool, the data defining the MVNO client event, and storing the processed MVNO client event data to an asset loader server database.

5. The computer-implemented method of claim 3, further comprising: the XML file is generated by a Simple Object Access Protocol (SOAP) based tool from data stored in an asset loader server database.

6. The computer-implemented method of claim 5, further comprising: receiving, by the SOAP-based tool from the billing interface, confirmation that the generated wholesale bill has been processed.

7. A system for supporting account reconciliation between a mobile virtual network operator, MVNO, and a mobile host operator, MHO, the system comprising:

an asset loader server configured to receive data from an MVNO database defining retail account information for a plurality of MVNO clients using services provided by the MVNO; receiving data defining a wholesale catalog defining pricing rules for each service provided by the MHO used by an MVNO client of the plurality of MVNO clients;

receiving data defining MVNO client events associated with the plurality of MVNO clients from the MVNO database, wherein the MVNO charges each MVNO client at a retail rate associated with the corresponding client event, and wherein when the MVNO determines that an MVNO resource has been used by the client, the MVNO stores the data defining the MVNO client events into the MVNO database;

generating a plurality of virtual wholesale bills associated with the plurality of MVNO clients based on the MVNO client events and pricing rules in the wholesale directory, wherein each virtual wholesale bill comprises an overhead associated with use of the MHO service by a given MVNO client, and wherein the virtual wholesale bills are represented as extensible markup language (XML) files formatted to match a format of an MHO wholesale bill;

wherein the asset loader server is further configured to transmit the virtual wholesale bill to a billing interface of a billing system of the MVNO, the billing interface configured to receive the MHO wholesale bill, the MHO wholesale bill specifying an aggregate cost associated with usage of the MHO services by the plurality of MVNO clients; and is

A billing system configured to accumulate the cost for each virtual wholesale bill to determine a total cost associated with the plurality of virtual wholesale bills; and comparing the accumulated total costs to the aggregate costs specified in the MHO wholesale bill to determine whether the accumulated total costs and the aggregate costs match.

8. The system of claim 7, wherein the data defining the MVNO client event is selected from the group consisting of: a user ID, a timestamp associated with the event, a duration of use, and a user retail price.

9. The system of claim 7, further comprising a scripting tool configured to extract data defining the MVNO client events from the database of MVNOs.

10. The system of claim 9, wherein the scripting tool is further configured to process the data defining the MVNO client events and store the processed MVNO client event data to an asset loader server database.

11. The system of claim 9, further comprising code and logic to implement a Simple Object Access Protocol (SOAP) -based tool configured to generate the XML file from data stored in an asset loader server database.

12. The system of claim 11, wherein the SOAP-based tool is further configured to receive confirmation from the billing interface that the generated wholesale bill has been processed.

13. A computer-implemented apparatus supporting account reconciliation between a mobile virtual network operator, MVNO, and a mobile host operator, MHO, the apparatus comprising:

means for receiving, by an asset loader server from an MVNO database, data defining retail account information for a plurality of MVNO clients using services provided by the MVNO;

means for receiving an MHO wholesale bill at the MVNO, the MHO wholesale bill specifying an aggregate cost associated with usage of MHO services by the plurality of MVNO clients;

means for receiving, by the asset loader server, data defining a wholesale catalog defining pricing rules for each service provided by the MHO used by an MVNO client of the plurality of MVNO clients;

means for receiving, by the asset loader server, data defining MVNO client events associated with the plurality of MVNO clients from the MVNO database, wherein the MVNO charges each MVNO client at a retail rate associated with the corresponding client event, and wherein the MVNO stores the data defining the MVNO client events into the MVNO database when the MVNO determines that an MVNO resource has been used by the client;

means for generating, by the asset loader server, a plurality of virtual wholesale bills associated with the plurality of MVNO clients based on the MVNO client events and pricing rules in the wholesale directory, wherein each virtual wholesale bill comprises overhead associated with use of the MHO service by a given MVNO client, and wherein the virtual wholesale bills are represented as extensible markup language (XML) files formatted to match a format of an MHO wholesale bill;

means for transmitting, by the asset loader server, the virtual wholesale bill to a billing interface of the MVNO, the billing interface configured to receive the MHO wholesale bill;

means for aggregating the costs for each virtual wholesale bill to determine a total cost associated with the plurality of virtual wholesale bills; and

means for comparing, by a billing system of the MVNO, the accumulated total costs to the aggregate costs specified in the MHO wholesale bill to determine whether the accumulated total costs and the aggregate costs match.

14. The computer-implemented device of claim 13, wherein the data defining the MVNO client event is selected from the group consisting of: a user ID, a timestamp associated with the event, a duration of use, and a user retail price.

15. The computer-implemented apparatus of claim 13, further comprising: means for extracting, by a scripting tool, data defining the MVNO client event from a database of the MVNO.

16. The computer-implemented apparatus of claim 15, further comprising: means for processing, by the scripting tool, the data defining the MVNO client events and storing the processed MVNO client event data to an asset loader server database.

17. The computer-implemented apparatus of claim 15, further comprising: means for generating, by a Simple Object Access Protocol (SOAP) -based tool, the XML file from data stored in an asset loader server database.

18. The computer-implemented apparatus of claim 17, further comprising: means for receiving, by the SOAP-based tool from the billing interface, confirmation that the generated wholesale bill has been processed.