U.S. patent application number 11/757373 was filed with the patent office on 2007-10-04 for billing system with authenticated wireless device transaction event data.
Invention is credited to Ravinder Paul CHANDHOK, Richard Wayne III GARDNER, Brian MINEAR, Stephen A. SPRIGG, Jun YAMADA.
Application Number | 20070232263 11/757373 |
Document ID | / |
Family ID | 33541147 |
Filed Date | 2007-10-04 |
United States Patent
Application |
20070232263 |
Kind Code |
A1 |
CHANDHOK; Ravinder Paul ; et
al. |
October 4, 2007 |
BILLING SYSTEM WITH AUTHENTICATED WIRELESS DEVICE TRANSACTION EVENT
DATA
Abstract
An apparatus comprising a server is provided. The server is
operable to gather authenticated transaction data to generate
billing for wireless devices conducting transactions across a
wireless network, receive transaction event data from one or more
wireless devices, authenticate the transaction event data, and
aggregate the authenticated transaction event data into transaction
event billing data such that each transaction event is billable to
a specific wireless device that effected the transaction event. The
transaction event data is caused by one or more billable
transaction events generated by the specific wireless device
interacting with a computer device over the wireless network. Each
of the billable transaction events is capable of generating an
authenticated transaction event data configured to verify that a
specific billable transaction event has been generated by a
specific wireless device. Each authenticated transaction event data
includes a first key and a second key.
Inventors: |
CHANDHOK; Ravinder Paul;
(Poway, CA) ; MINEAR; Brian; (San Diego, CA)
; YAMADA; Jun; (Yokohama, JP) ; GARDNER; Richard
Wayne III; (Rancho Santa Fe, CA) ; SPRIGG; Stephen
A.; (Poway, CA) |
Correspondence
Address: |
QUALCOMM INCORPORATED
5775 MOREHOUSE DR.
SAN DIEGO
CA
92121
US
|
Family ID: |
33541147 |
Appl. No.: |
11/757373 |
Filed: |
June 3, 2007 |
Related U.S. Patent Documents
|
|
|
|
|
|
Application
Number |
Filing Date |
Patent Number |
|
|
10610439 |
Jun 30, 2003 |
|
|
|
11757373 |
Jun 3, 2007 |
|
|
|
Current U.S.
Class: |
455/406 |
Current CPC
Class: |
H04M 15/00 20130101;
G06Q 20/145 20130101; H04M 15/48 20130101; H04M 15/68 20130101;
G06Q 30/04 20130101; H04M 2215/0196 20130101; H04W 4/24 20130101;
H04M 2215/0156 20130101; G06Q 20/325 20130101 |
Class at
Publication: |
455/406 |
International
Class: |
H04M 11/00 20060101
H04M011/00 |
Claims
1. An apparatus comprising: a server operable to: gather
authenticated transaction data to generate billing for wireless
devices conducting transactions across a wireless network; receive
transaction event data from one or more wireless devices;
authenticate the transaction event data; and aggregate the
authenticated transaction event data into transaction event billing
data such that each transaction event is billable to a specific
wireless device that effected the transaction event, wherein the
transaction event data is caused by one or more billable
transaction events generated by the specific wireless device
interacting with a computer device over the wireless network, each
of the billable transaction events being capable of generating an
authenticated transaction event data configured to verify that a
specific billable transaction event has been generated by the
specific wireless device, and wherein each authenticated
transaction event data includes: a first key from the computer
device participating in the billable transaction event, the first
key identifying the billable transaction event, and a second key
from the specific wireless device, the second key identifying the
specific wireless device.
2. The apparatus of claim 1, wherein the server is a billing
computer in selective communication with the wireless network.
3. The apparatus of claim 1, wherein a service provider is operable
to provide the wireless computer device access to the wireless
network, and the wireless device is configured to have a
subscriber, and the server is further operable to bill the wireless
device subscriber for the transaction events caused by the wireless
device.
4. The apparatus of claim 3, wherein the server is further operable
to generate a bill to the subscriber of each wireless device based
upon the authenticated and aggregated transaction event data.
5. The apparatus of claim 4, wherein the server is further operable
to: generate transaction event billing data based upon the
authenticated transaction event data; and transmit the transaction
event billing data to a wireless service provider.
6. The apparatus of claim 1, wherein the second key is a digital
signature associated with the wireless device.
7. A server for gathering authenticated transaction data to
generate billing for wireless devices conducting transactions
across a wireless network, the server comprising: means for
receiving transaction event data from one or more wireless devices;
means for authenticating the transaction event data; and means for
aggregating the authenticated transaction event data into
transaction event billing data such that each transaction event is
billable to a specific wireless device that effected the
transaction event, wherein the transaction event data is caused by
one or more billable transaction events generated by the specific
wireless device interacting with a computer device over the
wireless network, each of the billable transaction events being
capable of generating an authenticated transaction event data
configured to verify that a specific billable transaction event has
been generated by the specific wireless device, and wherein each
authenticated transaction event data includes: a first key from the
computer device participating in the billable transaction event,
the first key identifying the billable transaction event, and a
second key from the specific wireless device, the second key
identifying the specific wireless device.
8. The server of claim 7, wherein the means for aggregating the
authenticated transaction event data is a billing computer in
selective communication with the wireless network.
9. The server of claim 7, wherein a service provider is operable to
provide the wireless computer device access to the wireless
network, and the wireless device is configured to have a
subscriber, and the server further comprises: means for billing the
wireless device subscriber for the transaction events caused by the
wireless device.
10. The server of claim 9, further comprising: means for generating
a bill to the subscriber of each wireless device based upon the
authenticated and aggregated transaction event data.
11. The server of claim 9, further comprising: means for generating
transaction event billing data based upon the authenticated
transaction event data; and means for transmitting the transaction
event billing data to a wireless service provider.
12. The server of claim 8, wherein the second key is a digital
signature associated with the wireless device.
13. A wireless device operable to generate authenticated
transaction data from conducting transactions across a wireless
network with a computer device, the wireless device comprising:
means for interacting with the computer device across the wireless
network to cause a billable transaction event; means for generating
authenticated transaction event data, the authenticated transaction
event data verifying a performance of a specific billable
transaction event by a specific device, the authenticated
transaction event data comprising a first key associated with the
billable transaction event received from the computer device, and a
second key identifying the specific wireless device; and means for
selectively transmitting the authenticated transaction event data
to a billing device in selective communication with the wireless
network.
14. The wireless device of claim 13, wherein the wireless device
further includes means for transmitting the authenticated
transaction event data to a wireless service provider for that
wireless device.
15. The wireless device of claim 13, wherein the means for causing
a billable transaction event includes means for downloading an
application to the wireless device from the computer device.
16. The wireless device of claim 13, wherein the means for causing
a billable transaction event includes means for effecting a
subscription to a service provider by the computer device to the
wireless device.
17. The wireless device of claim 13, wherein the means for
transmitting the authenticated transaction event data operates to
transmit the authenticated transaction event data at the time the
billable transaction event occurs.
18. The wireless device of claim 13, wherein the second key is a
digital signature associated with the specific wireless device.
19. A computer-readable medium comprising instructions, which, when
executed by a computer, cause the computer to perform operations,
the instructions comprising: at least one instruction for
interacting with a computer device across a wireless network to
cause a billable transaction event; at least one instruction for
generating authenticated transaction event data, the authenticated
transaction event data verifying a performance of a specific
billable transaction event by a specific wireless device, the
authenticated transaction event data comprising a first key
associated with the billable transaction event received from a
computer device, and a second key identifying the specific wireless
device; and at least one instruction for selectively transmitting
the authenticated transaction event data to a billing device in
selective communication with the wireless network.
20. The computer-readable medium of claim 19, the instructions
further comprising: at least one instruction for transmitting the
authenticated transaction event data to a wireless service provider
for that wireless device.
21. The computer-readable medium of claim 19, wherein the at least
one instruction for causing a billable transaction event comprises:
at least one instruction for causing a billable transaction event
for downloading an application to the wireless device from the
computer device.
22. The computer-readable medium of claim 19, wherein the at least
one instruction for causing a billable transaction event comprises:
at least one instruction for effecting a subscription to a service
provider by the computer device to the wireless device.
23. The computer-readable medium of claim 19, wherein the at least
one instruction for transmitting the authenticated transaction
event data comprises: at least one instruction for transmitting the
authenticated transaction event data at the time the billable
transaction event occurs.
24. The computer-readable medium of claim 19, wherein the second
key is a digital signature associated with the specific wireless
device.
25. The computer-readable medium of claim 19, further comprising:
at least one instruction for storing the authenticated transaction
event data; and at least one instruction for selectively
transmitting the stored authenticated transaction event data to
another computer device on the network.
Description
CROSS-REFERENCE TO RELATED APPLICATIONS
[0001] The subject application is a continuation of and claims
priority from U.S. patent application entitled "BILLING SYSTEM WITH
AUTHENTICATED WIRELESS DEVICE TRANSACTION EVENT DATA," filed on
Jun. 30, 2003, having U.S. application Ser. No. 10/610,439. This
application is incorporated herein by reference in its
entirety.
BACKGROUND
[0002] I. Field
[0003] The present invention generally relates to wireless devices
and wireless networks. More particularly, the invention relates to
a system and method that permits accurate and reliable transaction
data for third party application sales and services to wireless
telecommunication devices across a wireless network, and can
provide accurate data sufficient to bill wireless service
subscribers for the billable transactions.
[0004] II. Description of the Related Art
[0005] Wireless devices, such as cellular telephones, communicate
packets including voice and data over a wireless network. In
existing wireless telecommunication systems, such as cellular
telecommunication systems, fees are typically charged by a wireless
network provider to a wireless service subscriber for the initial
activation of a telecommunication device and then fees can be
charged for ongoing airtime and device usage. However, existing
wireless network systems, such as cellular networks, typically do
not account for other activities at the telecommunication device
beyond airtime usage.
[0006] If the subscriber of the wireless device desires to download
and use a software application or upgrade the functionality of the
wireless device, the subscriber will typically either call a
service provider or contact the service provider through another
electronic means, such as through a separate Internet access. In
some instances, the service provider can transmit the application
to the wireless device across the wireless network (through a one
time direct access download) or allow the user access a network
site within the wireless device through the wireless network, and
at such site the application is downloadable or accessible to the
wireless device. The access of the wireless device to the
application most typically occurs through a secure-socket layer
(SSL) or other secure data link. Otherwise, service personnel of
the provider must have physical access to the telecommunication
device to install the software or upgrade the components
thereof.
[0007] The existing systems for monitoring and billing for wireless
telecommunication device activity thus do not allow a service
provider to bill or account for activities by the wireless device
that not occur on the computer devices of that provider, and which
are not accomplished through a secure data link. Further, the
wireless device provider does not have a method to reliably bill
its subscribers for any service provided to its subscribers through
a third party solely across the wireless network without some
manner of direct communication between the provider and the third
party. Accordingly, the present invention is primarily directed to
a system and method that allows the billing for wireless device
billable transaction events that occur on the wireless network from
the wireless devices of the subscribers interacting with other
computer devices on the wireless network.
SUMMARY
[0008] The present invention is a system, method, and computer
program that utilizes gathered authenticated data to bill wireless
device subscribers for any billable interaction with applications
and services resident on third party computer devices that are
accessible through a wireless network, such as a cellular
telecommunication network. The system uses authenticated
transaction data that is created when a wireless device conducts a
billable transaction, such as an application download or service
subscription, whereby the data is a secure indication that a
wireless device has performed a specific billable transaction
event. The transaction data is aggregated to generate reliable
billing data for billable transaction events, and the billing data
can be gathered and billed from a billing computer on the network,
or the billing data can be sent to a wireless service provider for
billing to the wireless device subscriber.
[0009] In one embodiment, an apparatus comprising a server is
provided. The server is operable to gather authenticated
transaction data to generate billing for wireless devices
conducting transactions across a wireless network. The server is
further operable to receive transaction event data from one or more
wireless devices and authenticate the transaction event data. The
server is further operable to aggregate the authenticated
transaction event data into transaction event billing data such
that each transaction event is billable to a specific wireless
device that effected the transaction event. The transaction event
data is caused by one or more billable transaction events generated
by the specific wireless device interacting with a computer device
over the wireless network. Each of the billable transaction events
is capable of generating an authenticated transaction event data
configured to verify that a specific billable transaction event has
been generated by a specific wireless device. Each authenticated
transaction event data includes a first key from the computer
device participating in the billable transaction event and a second
key from the specific wireless device. The first key identifies the
billable transaction event and the second key identifies the
specific wireless device.
[0010] In another embodiment, a server for gathering authenticated
transaction data to generate billing for wireless devices
conducting transactions across a wireless network is provided. The
server comprises means for receiving transaction event data from
one or more wireless devices and means for authenticating the
transaction event data. The server further includes means for
aggregating the authenticated transaction event data into
transaction event billing data such that each transaction event is
billable to a specific wireless device that effected the
transaction event. The transaction event data is caused by one or
more billable transaction events generated by the specific wireless
device interacting with a computer device over the wireless
network. Each of the billable transaction events is capable of
generating an authenticated transaction event data configured to
verify that a specific billable transaction event has been
generated by the specific wireless device. Each authenticated
transaction event data includes a first key from the computer
device participating in the billable transaction event and a second
key from the specific wireless device. The first key identifies the
billable transaction event and the second key identifies the
specific wireless device.
[0011] In still another embodiment, a wireless device operable to
generate authenticated transaction data from conducting
transactions across a wireless network with a computer device is
provided. The wireless device includes means for interacting with
the computer device across the wireless network to cause a billable
transaction event. The wireless device further includes means for
generating authenticated transaction event data. The authenticated
transaction event data verifies a performance of a specific
billable transaction event by a specific device. The authenticated
transaction event data comprises a first key associated with the
billable transaction event received from the computer device, and a
second key identifying the specific wireless device. Further
included in the wireless device is means for selectively
transmitting the authenticated transaction event data to a billing
device in selective communication with the wireless network.
[0012] In yet another embodiment, a computer-readable medium
comprising instructions, which, when executed by a computer, cause
the computer to perform operations is provided. The instructions
include at least one instruction for interacting with a computer
device across a wireless network to cause a billable transaction
event. The instructions further include at least one instruction
for generating authenticated transaction event data. The
authenticated transaction event data verifies a performance of a
specific billable transaction event by a specific wireless device.
The authenticated transaction event data comprises a first key
associated with the billable transaction event received from the
computer device, and a second key identifying the special wireless
device. Further included in the instructions is at least one
instruction for selectively transmitting the authenticated
transaction event data to a billing device in selective
communication with the wireless network.
[0013] In yet another embodiment, the system includes the wireless
network supporting at least data communication thereacross, and one
or more wireless computer devices are in selective communication
with other computer devices across the wireless network. Each
wireless device has the ability to conduct billable transactions
with the other computer devices and the occurrence of a billable
transaction causes authenticated transaction event data to be
generated through which it can be verified that a specific wireless
device has performed a specific transaction event. At least one
billing computer is in selective communication with the wireless
network and gathers at least some of the transaction event data for
the wireless devices and authenticates and aggregates the
transaction event data into transaction event billing data whereby
each transaction event is billable to the specific wireless device
that effected that transaction event. The billing computer can
either send a bill to the wireless device subscriber or send the
billing data to another entity, such as wireless service provider,
to enable the other entity to bill for the transaction events.
[0014] The method for utilizing authenticated transaction data to
generate billing for wireless devices conducting transactions
across a wireless network includes the steps of causing a billable
transaction event to occur on the wireless network through the
wireless computer device interacting with another computer device
across the wireless network, and then generating authenticated
transaction event data through which it can be verified that the
specific wireless devices has performed the specific transaction
event. Finally, the method includes the step of aggregating the
authenticated transaction event data into transaction event billing
data such that each transaction event is billable to the specific
wireless device that effected that transaction event. The method
can further include the step of transmitting a bill directly to the
wireless device subscriber for the transaction events caused by the
wireless device, or the transaction event billing data can be
transmitted to another device on the network.
[0015] The system and method accordingly give wireless service
providers the ability to bill reliably for wireless
telecommunication device transactions, such as application download
and execution that occur solely on the wireless network with third
party computer devices. Through use of the system, the wireless
service provider has an advantage in that the provider can give
wireless airtime subscribers access to additional value-added
services of third parties and effectively bill and capture the
revenue from the third party services. Moreover, the billing system
does not require that the subscriber contact the service provider
or the third party outside of the computing environment in order to
receive or access the additional service.
[0016] Other objects, advantages, and features of the present
invention will become apparent after review of the hereinafter set
forth Brief Description of the Drawings, Detailed Description of
the Invention, and the Claims.
BRIEF DESCRIPTION OF THE DRAWINGS
[0017] FIG. 1 is a representative diagram of a wireless network and
the computer hardware and wireless devices that can be used within
the billing system utilizing authenticated transaction event data
for wireless device transactions.
[0018] FIG. 2 is a block diagram illustrating a cellular
telecommunication network with the billing system tracking billable
transaction events occurring on wireless devices that interact with
other computer devices across the wireless network . . .
[0019] FIG. 3 is an interactive menu that is presented to the users
of the wireless devices when contacting a third party application
download server across the wireless network and a plurality of
options for interaction is represented on the display.
[0020] FIG. 4 is an object diagram illustrating an embodiment of
the system wherein the formation of an authenticated transaction
event data object occurs from interaction between the downloadable
application and the wireless device download interface.
[0021] FIG. 5 is a flowchart illustrating one embodiment of the
process or subprocess executing on the wireless device computer
platform that seeks to download an application (a billable
transaction event) and uses a digital signature to verify the
identity of the wireless device that makes the download.
[0022] FIG. 6 is a flowchart illustrating one embodiment of the
process or subprocess executing on the computer platform of the
third party computer application download server wherein the
digital signature of the wireless device that downloads an
application therefrom is gathered, and authenticated transaction
event data is generated and transmitted at the completion of the
download.
[0023] FIG. 7 is a flowchart illustrating one embodiment of the
process or subprocess executing on a billing computer that
receives, authenticates, and stores transaction event data from the
wireless network and aggregates and sends transaction event billing
data to a wireless service provider upon request.
DETAILED DESCRIPTION
[0024] With reference to the figures in which like numerals
represent like elements throughout, FIG. 1 illustrates one
embodiment of the present inventive system 10 for tracking
authenticated billable events occurring through wireless devices,
such as cellular telephone 12, in communication across a wireless
network 14, with third party computer devices, such as a third
party application download server 16, that selectively downloads
software applications or other data to the wireless devices across
a wireless communication portal or other data access to the
wireless network 14. In developing wireless networks 14, if the
end-user of the wireless device desires to download and use a
software application, the end-user will attempt to connect to an
application download server, either the carrier's server or a third
party application download server 16, through bridging a
communication connection to the wireless network 14, and attempt to
access and download the desired software application. Once the
wireless device contacts the application download server 16, an
initial contact is made and the application download server 16 can
determine what applications and data are available to that wireless
device 12, 18, 20, and 22 and send the appropriate information,
such as a menu (FIG. 3), for display on the wireless device 12, 18,
20, and 22 so the user at the wireless device can learn of the
available applications and services.
[0025] As shown here, the wireless device can be a cellular
telephone 12, with a graphics display 13, a personal digital
assistant 18, a pager 20 with a graphics display, which is shown
here as a two-way text pager, or even a separate computer platform
22 that has a wireless communication portal, and may otherwise have
a wired connection 24 to a network or the Internet. The system 10
can thus be performed on any form of remote computer module
including a wireless communication portal, including without
limitation, wireless modems, PCMCIA cards, access terminals,
personal computers, access terminals, telephones without a display
or keypad, or any combination or sub-combination thereof. Further,
the term "application" as used herein is intended to encompass
executable and nonexecutable software files, raw data, aggregated
data, patches, and other code segments.
[0026] In the system 10, one or more wireless devices 12, 18, 20,
and 22 are in selective communication with other computer devices
across the wireless network 14, such as through a voice or data
call between devices. Each wireless device has the ability to
conduct billable transactions with other computer devices, such as
an application download, execution, service or other value-added
interaction, and the occurrence of a billable transaction causes
authenticated transaction event data 74 (FIG. 4) to be generated
which permits the verification that a specific wireless device 12,
18, 20, and 22 has performed a specific transaction event. At least
one billing computer 30 can be in selective communication with the
wireless network 14 to gather at least some of the authenticated
transaction event data for the wireless devices, and the billing
computer 30 can also authenticate and aggregate the transaction
event data into transaction event billing data such that each
transaction event is billable to the specific wireless device that
effected that transaction event. As is more fully described herein,
the billing computer 30 can generate bills to the wireless service
subscriber for the wireless device that caused a billable
transaction event, or the transaction event billing data can be
transmitted to another computer device on the wireless network 14
or a local network 26, such as a third party billing computer 32,
which is typically a wireless service provider.
[0027] The one or more wireless devices 12, 18, 20, and 22,
typically at the direction of an end-user operating the device,
selectively communicate with other computer devices across a
wireless network, application download server 16, which can
partially exist on a local server-side network 26 with other
computer elements in communication with the wireless network 14,
such as a billable transaction event database 28 that can contain
either authenticated or non-authenticated transaction event data
for the wireless devices. All of the components can work in tandem
to gather data relative to billable transaction events of the
wireless devices 12, 18, 20, and 22 and aggregate the transaction
event data at the billing computer 30 as is further described
herein. However, it should be noted that all server-side functions
can be performed on one server, such as billing computer 30.
Further, any computer or server-side computer platform can provide
separate services and processes to the wireless devices 12, 18, 20,
and 22 across the wireless network 14.
[0028] FIG. 2 is a block diagram that more fully illustrates the
components of the wireless network 14 and interrelation of the
elements of the system 10. The wireless network 14 is merely
exemplary and can include any system whereby remote modules, such
as wireless devices 12, 18, 20, and 22, communicate over-the-air
between and among each other and/or between and among components of
a wireless network 14, including, without limitation, wireless
network carriers and/or servers. The server side components are a
billing server 16, third party application download server 16, a
billable transaction event database 28, a billing computer 30, a
wireless device database 34, and a wireless service provider
billing computer 41. Other server-side components will be present
on the cellular data network with any other components that are
needed to provide cellular telecommunication services. The
server-side components as embodied in FIG. 2 can by themselves
create a billing system 10 solely through tracking applications
downloaded from the third party application download server 16 and
the billing for the download will be generated (and authenticated)
through correlation of the billable transaction event database 28
and wireless device database 34 by the billing computer 30. The
system 10 can also transmit transaction event billing data to a
wireless service provider billing computer 41 that can gather
wireless device data, such as from database 34, and generate
billing to the wireless service subscribers of that provider. With
the use of third party hardware readily scalable, the number of
computer devices that can be made accessible to the wireless
devices is theoretically unlimited.
[0029] The server-side components communicate with a carrier
network 40 through a data link, such as the Internet, a secure LAN,
WAN, or other network. The carrier network 40 controls messages
(generally in the form of data packets) sent to a messaging service
controller ("MSC") 42. The carrier network 40 communicates with the
MSC 42 by a network, the Internet and/or POTS ("plain ordinary
telephone system"). Typically, the network or Internet connection
between the carrier network 40 and the MSC 42 transfers data, and
the POTS transfers voice information. The MSC 42 is connected to
multiple base stations ("BTS") 44. In a similar manner to the
carrier network, the MSC 42 is typically connected to the BTS 44 by
both the network and/or Internet for data transfer and POTS for
voice information. The BTS 44 ultimately broadcasts messages
wirelessly to the wireless devices, such as cellular telephone 12,
by short messaging service ("SMS"), or other over-the-air methods
known in the art.
[0030] The wireless device, such as cellular telephone 12, has a
computer platform 50 that can receive and execute software
applications transmitted from the application download server 16.
The computer platform 50 includes, among other components, an
application-specific integrated circuit ("ASIC") 52, or other
processor, microprocessor, logic circuit, programmable gate array,
or other data processing device. The ASIC 52 is installed at the
time of manufacture of the wireless device and is not normally
upgradeable. The ASIC 52 or other processor executes an application
programming interface ("API") layer 54 that interfaces with any
resident programs in the memory 56 of the wireless device. The
memory can be comprised of read-only or random-access memory (RAM
and ROM), EPROM, EEPROM, flash cards, or any memory common to
computer platforms. The computer platform 50 also includes a local
database 58 that can hold the software applications not actively
used in memory 56, such as the software applications downloaded
from the third party application download server 16. The local
database 58 is typically comprised of one or more flash memory
cells, but can be any secondary or tertiary storage device as known
in the art, such as magnetic media, EPROM, EEPROM, optical media,
tape, or soft or hard disk.
[0031] Cellular telephones and telecommunication devices, such as
cellular telephone 12, are being manufactured with increased
computing capabilities and are becoming tantamount to personal
computers and hand-held personal digital assistants ("PDAs"). These
"smart" cellular telephones allow software developers to create
software applications that are downloadable and executable on the
processor, such as ASIC 52, of the cellular device. The wireless
device, such as cellular telephone 12, can download many types of
applications, such as games and stock monitors, or simply data such
as news and sports-related data. The downloaded data or executed
applications can be immediately displayed on the display 13 or
stored in the local database 58 when not in use. The software
applications can be treated as a regular software application
resident on the wireless device 12, 18, 20, and 22, and the user
can selectively upload stored resident applications from the local
database 58 to memory 56 for execution on the API 54. The user of
the wireless device 12, 18, 20, and 22 can also selectively delete
a software application from the local database 58. As a result,
end-users of cellular telephones 12 can customize their telephones
with programs, such as games, printed media, stock updates, news,
or any other type of information or program available for download
from application download servers through the wireless network
14.
[0032] The use of these value-added services of third parties by
the wireless device 12, 18, 20, and 22 cause billable transaction
events for which the wireless network service provider will bill
the subscriber of the wireless device, who is not necessarily the
end-user of the wireless device at the time of the billable event.
The billable events typically occur from the end-user conducting
some activity with applications provided from the third party
application download server 30. Examples of billable events
include, but are not to be limited to, downloading an application
from a third party application download server 16 on the wireless
network 14 to the wireless device computer platform 50, the
execution of an application on the wireless device 12, 18, 20,22;
accessing an application resident on another computer device on the
wireless network 14, such as application download server 16, or an
accessible database, or other parameter of execution or interaction
therewith.
[0033] The system 10 accordingly allows a third party, such as an
independent software vendor or developer, either through the third
parties own computer devices or through a network carrier 40, to
provide software applications as downloadable to the wireless
device. A multitude of computer devices can be involved in the
ultimate delivery of applications and services, and the wireless
device 12, 18, 20, and 22 can make several accesses to one or more
third party computer devices. The system 10 can thus after-bill the
carrier 40 for their subscriber billable event transactions, which
typical is a different fee than what the carrier 40 will use to
bill their subscribers, and the billing computer 30 can aggregate
and generate the transaction event billing data and can provide the
data to the wireless service provider.
[0034] To illustrate the possible services provided from the third
party application download server 30 to the wireless devices 12,
18, 20, and 22, FIG. 3 is a partial view 60 of the display 13
having a menu 62 displayed thereon listing potential interactions
with the application download server 16. Simple data for display at
the wireless device is shown in an available news section 64,
wherein the wireless device will pay for simple access to the data.
The wireless devices 12, 18, 20, and 22, can therefore select to
download an application from the menu, as shown at selection site
66, which will cause a from the third party application download
server 16 is shown. The subscriber for the wireless device
(end-user or not) will be discretely billed if one or more of the
applications are downloaded.
[0035] In one embodiment of the system 10, the billable transaction
event data for the one or more wireless devices 12, 18, 20, and 22
is ultimately gathered at billing computer 30 such that the billing
information for each wireless device that the billing computer
accounts for is contained at the billing computer 30. As embodied
in FIG. 2, the billing information will ultimately be provided to
the carrier network 40 to the wireless service provider billing
computer 41 for billing to the carrier's subscriber. However, the
billing computer 30 can generate a bill to the wireless device
subscriber, for whom it can access the information of the wireless
device data 34. While the billable event data is ultimately
gathered at the billing computer 30, the third party computer
device (application download server 16) can also gather the
billable event data and transmit it periodically to the billing
computer 30. The third party computer device can transmit billable
transaction event data to the billing computer 30 at the completion
of the billable transaction event, upon query from the billing
computer 30, or at a predetermined interval of time, e.g. every 30
minutes while active. And if the billing computer 30 further
generates a bill for a wireless device 12, 18, 20, and 22 based
upon the gathered billable event data, the generated bill can be
transmitted from the billing computer to another computer device on
the wireless network 14. It should also be noted that the
transaction event data (authenticated or not) can thus be stored at
any computer device on the network, such as the application
download server 16, and then ultimately transmitted to the billing
computer 30.
[0036] FIG. 4 is an object diagram illustrating the downloadable
application 70 creating the authenticated transaction event data
object 74 from interaction with the wireless device download
interface 72. The downloadable application includes at least as
data a seller key, and as methods a "create authenticated
transaction event object" and a "send seller key and digital
signature." And the wireless device download interface 72 includes
as data a digital signature, or other identification data such as
an encryption key or other unique data as known in the art, and a
method to "send the digital signature." Thus, when the wireless
device download interface 72 interacts with the downloadable
application 70 to effect a download of the application, which is a
billable transaction event to the wireless device 12, 18, 20, and
22, the digital signature is sent to the downloadable application
object 70 and the downloadable application 70 creates the
transaction event data object 74 and then populates the transaction
event data object 74 with the seller key and digital signature
whereby the transaction event data object 74 can be authenticated
with the unique data of the seller of the application and the
purchasing wireless device. It should be noted that the wireless
device download interface 72 can contain the method to create the
transaction event data object 74, or share such a method with the
downloadable application 70 as would be known to one of skill in
the art.
[0037] In sum, as embodied in FIG. 4, in an object-oriented
paradigm, the downloaded application 70 creates a software object
of the transaction event data 74 comprised of authenticated
transaction data for wireless devices 12, 18, 20, and 22 conducting
transactions across a wireless network 14, where the object
verifies that a specific wireless device has performed a specific
billable transaction event such that the object is utilizable to
generate billing for billable transaction events that occur on the
wireless network 14. The transaction event data 74 can be
transmittable to the billing computer 30 in selective communication
with the wireless network, and can be resident on within the
downloadable application 70, or the wireless device download
interface 72 or both. Further, the transaction event data 74 can be
created upon an application download, or the wireless device
effecting a subscription to a service provided by one or more
computer devices to the wireless computer device across the
wireless network 14. Further, the transaction event data 74 can
modified after the creation at the occurrence of a transaction
event,
[0038] FIG. 5 is a flowchart illustrating one embodiment of the
process or subprocess executing on the wireless device computer
platform 50 where the user seeks to download an application (a
billable transaction event) and the digital signature of the
wireless device 12, 18, 20, and 22 is used to verify the identity
of the wireless device 12, 18, 20, and 22. The wireless device
computer platform 50 receives a command to access the application
menu 62 of the application download server 16, as shown at step 80,
and then the computer platform 50 accesses the menu 60 as shown at
step 82. A determination is then made as to whether the user has
request a download, as shown at decision 84. If a request for a
download has occurred at decision 84, the digital signature is sent
to the application download server 16 and an attempt to download
the application is made, as shown at step 86, and then a
determination is made as to whether the application has been
successfully downloaded as shown at decision 88. If the application
has been successfully downloaded at decision 88, then process
returns to decision 84 to determine if another application download
has been requested. If the application has not been successfully
downloaded at decision 88, an error is output to the user that
attempted to download the application, as shown at step 90, and
then the process returns again to decision 84.
[0039] If the user has not requested the download of an application
at decision 84, a determination is made as to whether the user has
requested to exit the menu, as shown at decision 92. If the user
has not requested to exit from the menu at decision 92, the process
returns to decision 84 and iterates decision 84 to determine if a
download has been requested, and decision 92 to determine if menu
exit has been requested. If the user requested menu exit at
decision 92, the access of the wireless device 12, 18, 20, and 22
to the menu of the application download server 16 is ended.
[0040] FIG. 6 is a flowchart illustrating one embodiment of the
process or subprocess executing on the third party computer
application download server 16 wherein the digital signature of the
wireless device that downloads an application therefrom is
gathered, and transaction event data is generated, as shown in FIG.
4, and transmitted at the completion of the download. A download
request is received from a wireless device 12, 18, 20, and 22 as
shown at step 100, and a determination is made as to whether the
digital signature of the wireless device 102 has been received as
shown at decision 102. If the digital signature has not been
received at decision 102, an error is output to the user for
failure to receive digital signature and authenticate the user, as
shown at step 104 and the download process is ended. Otherwise, if
the digital signature is received at decision 102, the requested
application is downloaded to the wireless device of the user as
shown at step 106, and then the transaction event data is generated
containing a the seller key and digital signature, as shown step
108, and further illustrated in FIG. 4. The transaction event data
is then transmitted to the billing computer 30 as shown at step 110
and the download process ends.
[0041] The process can be alternately embodied such that the
transaction event generation process (step 108) is performed on
another computer on the wireless network 14. Further, the
transaction event data can be transmitted to one or more other
computers on the wireless network 14, instead of solely the billing
computer 30.
[0042] FIG. 7 is a flowchart illustrating one embodiment of the
process or subprocess executing on a billing computer 30 that
receives, authenticates, and stores transaction event data 74 from
the wireless network 14, and aggregates and sends transaction event
billing data 74 to a wireless service provider billing computer 41
upon request. The process is entered through a determination as to
whether transaction event data 74 has been received from the one or
more wireless devices 12, 18, 20, and 22, as shown at decision 118.
If transaction event data 74 has been received at decision 112, the
transaction event data 74 is received and authenticated as shown at
step 114. The authentication occurs, in one embodiment, from the
verification of the seller key and digital signature of the
wireless device 12, 18, 20, and 22. However, other methods of
identity verification, such as PGP or other encryption key
technology, can be used in the present system as would be known to
one of skill in the art. After authentication of the transaction
event data 74, the authenticated data is stored, as shown at step
116. Then the process continues to decision 118, which is also
reached if there was no transaction event data 74 at decision 112,
wherein a determination is made as to whether a request has been
received to transmit transaction billing data to a wireless service
provider billing computer 41. If a request to transmit the
transaction billing data has not been received at decision 118, the
process returns to decision 112 and thus enters a wait-state and
constantly determining if transaction data and a transaction
billing data transmission request has been made.
[0043] Otherwise, if transaction event billing data transmission
has been requested at decision 118, then the stored authenticated
transaction data is aggregated into transaction event billing data,
as shown at step 120, and then the transaction event billing data
is sent to the wireless service provider billing computer 41, as
shown at step 122. Alternately, billing for the wireless devices
12, 18, 20, and 22 can be generated at step 120 and then sent to
the wireless devices 12, 18, 20, and 22 themselves, transmitted to
another computer such as a wireless service provider computer 41,
or the transaction billing data can be converted into actual
printed bills for mailing to the wireless service subscriber for
the wireless devices 12, 18, 20, and 22.
[0044] It can be seen that the system 10 thus provides a method for
utilizing authenticated transaction data to generate billing for
wireless devices 12, 18, 20, and 22 conducting transactions across
a wireless network 14 supporting at least data communication
thereacross, having the steps of causing a billable transaction
event to occur on the wireless network 14 through a wireless
computer device interacting with another computer device across the
wireless network 14, generating authenticated transaction event
data 74 that is usable to verify that the specific wireless device
has performed the specific transaction event, authenticating the
transaction event data, and then aggregating the transaction event
authentication data 74 into transaction event billing data such
that each transaction event is billable to the specific wireless
device 12, 18, 20, and 22 that effected that transaction event The
step of aggregating the authenticated transaction event data can
occur at a billing computer 30 in selective communication with the
wireless network 14. The method can also have the step of billing
the wireless device subscriber for the transaction events caused by
their wireless device(s).
[0045] The method can be embodied so as to include the step of
generating a bill to the subscriber of each wireless computer
device 12, 18, 20, and 22 based upon the authenticated and
aggregated transaction event authentication data. The method can
also include the steps of generating transaction event billing data
based upon the authenticated transaction event data 74, and
transmitting the transaction event billing data to a service
provider, such as wireless service provider billing computer 41.
The step of causing a billable transaction event can be downloading
an application to the wireless computer device 12, 18, 20, and 22
from another computer device across the wireless network, as
described in FIGS. 5 and 6. Alternately, the step of causing a
billable transaction event can be effecting a subscription to a
service provided by one or more computer devices to the wireless
computer device 12, 18, 20, and 22 across the wireless network 14.
The step of generating authenticated transaction event data can be
generating authenticated transaction event data from the
downloadable application 70, as shown in FIG. 4, and if the
wireless computer device includes a digital signature and the
application has a secure key, and the step of generating
authenticated transaction event data is forming the transaction
event data from the digital signature and secure key, as is also
shown in FIG. 4. Moreover, the step of aggregating the
authenticated transaction event data into transaction event billing
data can occurs at the time of the transaction event occurrence, or
alternately, the method can include the steps of storing the
transaction event data 74 (authenticated or not), and transmitting
the stored transaction event data to another computer device on the
wireless network 14, such as wireless service provider billing
computer 41.
[0046] In view of the method being executable on the computer
platform of a computer device such as billing computer 30, the
present system includes a program resident in a computer readable
medium, where the program directs a server or other computer device
having a computer platform to perform the steps of the method. The
computer readable medium can be the memory of the billing computer
30, or can be in a connective database, such as billable
transaction event database 28. Further, the computer readable
medium can be in a secondary storage media that is loadable onto a
wireless device computer platform, such as a magnetic disk or tape,
optical disk, hard disk, flash memory, or other storage media as is
known in the art.
[0047] In the context of FIGS. 5, 6 and 7 the method may be
implemented, for example, by operating portion(s) of the wireless
network 14 to execute a sequence of machine-readable instructions,
such as wireless device computer platform 50, the billing computer
30, and third party application download server 16. The
instructions can reside in various types of signal-bearing or data
storage primary, secondary, or tertiary media. The media may
comprise, for example, RAM (not shown) accessible by, or residing
within, the components of the wireless network 14. Whether
contained in RAM, a diskette, or other secondary storage media, the
instructions may be stored on a variety of machine-readable data
storage media, such as DASD storage (e.g., a conventional "hard
drive" or a RAID array), magnetic tape, electronic read-only memory
(e.g., ROM, EPROM, or EEPROM), flash memory cards, an optical
storage device (e.g. CD-ROM, WORM, DVD, digital optical tape),
paper "punch" cards, or other suitable data storage media including
digital and analog transmission media.
[0048] While the foregoing disclosure shows illustrative
embodiments of the invention, it should be noted that various
changes and modifications could be made herein without departing
from the scope of the invention as defined by the appended claims.
Furthermore, although elements of the invention may be described or
claimed in the singular, the plural is contemplated unless
limitation to the singular is explicitly stated.
* * * * *