Transaction processing
First Claim
1. A method for generating a billing event for a download transaction of an application from a download server, wherein generating said billing event requires a first set of information and a second set of information, comprising:
- storing said first set of information as a metadata, said metadata comprising a plurality of blocks;
responsive to the download transaction conducted by the download server, receiving raw transaction data, said raw transaction data comprisinga plurality of references to blocks of said metadata, andsaid second set of information;
correlating each of said plurality of references in said raw transaction data to retrieve said first set of information from said metadata; and
creating said billing event from said first and second sets of information.
1 Assignment
0 Petitions
Accused Products
Abstract
Systems and methods consistent with the present invention provide a transaction processing during which a transaction billing event is created. Metadata associated with an application is stored in a transaction manager database. When a wireless device downloads an application, raw transaction information is sent to and stored in the database. The raw transaction data may include a subset of the metadata and additional information included by other devices and/or systems. Billing events are created by correlating the metadata and the raw transaction data. In addition, subscription billing events, such as those having reoccurring charges, are calculated by evaluating those transactions having a subscription transaction type and their associated metadata stored in the database.
-
Citations
9 Claims
-
1. A method for generating a billing event for a download transaction of an application from a download server, wherein generating said billing event requires a first set of information and a second set of information, comprising:
-
storing said first set of information as a metadata, said metadata comprising a plurality of blocks; responsive to the download transaction conducted by the download server, receiving raw transaction data, said raw transaction data comprising a plurality of references to blocks of said metadata, and said second set of information; correlating each of said plurality of references in said raw transaction data to retrieve said first set of information from said metadata; and creating said billing event from said first and second sets of information. - View Dependent Claims (2, 3, 4, 5)
-
-
6. A machine readable medium storing a sequence of machine executable instruction, which when executed, causes a machine which generates a billing event for a download transaction of an application from a download server, wherein generating said billing event requires a first set of information and a second set of information, to perform a sequence of steps comprising:
-
storing said first set of information as a metadata, said metadata comprising a plurality of blocks; responsive to the download transaction conducted by the download server, receiving raw transaction data, said raw transaction data comprising a plurality of references to blocks of said metadata, and said second set of information; correlating each of said plurality of references in said raw transaction data to retrieve said first set of information from said metadata; and creating said billing event from said first and second sets of information. - View Dependent Claims (7)
-
-
8. A billing system for generating a billing event for a download transaction of an application from a download server, wherein generating said billing event requires a first set of information and a second set of information, the system comprising:
-
a first system for receiving said first information and for storing said first information as a metadata, said metadata comprising a plurality of blocks; a second system, said second system comprising; a storage device; and a conversion engine, coupled to said storage device, wherein said conversion engine; receives raw transaction data generated by the download server responsive to the download transaction, said raw transaction data comprising a plurality of references to blocks of said metadata, and said second set of information; said conversion engine stores said raw transaction data and said second set of information on said storage device; said conversion engine correlates each of said plurality of references with said first system to retrieve said first set of information from said first system; and said conversion engine generates a billing event based on said first and second set of information. - View Dependent Claims (9)
-
Specification