WO2001073577A2

WO2001073577A2 - Revenue settlement system and method for wireless revenue settlement

Info

Publication number: WO2001073577A2
Application number: PCT/IB2001/000961
Authority: WO
Inventors: Jim D. Brown; Gianni M. Polidoro; Lawrence P. Baziw
Original assignee: Superwings Canada, Inc.
Priority date: 2000-03-30
Filing date: 2001-03-30
Publication date: 2001-10-04
Also published as: AU5870301A; WO2001073577A9

Abstract

An electronic revenue settlement system and a business method for wireless carriers and information/commerce merchants with applications on mobile phones, personal digital assistants, interactive pagers, and similar mobile devices. Based on customer activity, merchants will provide some form of credit or debit, revenue, or other monetary incentive system based on each customer's actions. This credit or debit may be applied to each customer's wireless carrier bill. These credits or debits may be tracked or logged using activity detail records and/or forwarded to a service bureau that will handle the reconciliation of these credits or debits.

Description

TITLE: REVENUE SETTLEMENT SYSTEM AND METHOD

FORWIRELESS REVENUE SETTLEMENT

This invention relates to wireless data applications and their use in a revenue settlement system to provide for an inventive business method for wireless carriers, information/commerce merchants, and customers.

Those skilled in the art recognize that mobile devices are used for a variety of purposes. Moreover, devices are capable of browsing using a handheld device markup language/wireless mark-up language ("HDML/WML") sites on personal communication services ("PCS") mobile devices. Typically, the carrier provides connectivity and access to HDML/WML sites. The merchant owns this HDML/WML site with content, e-commerce capability information content, and/or a phone link to an actual person.

In this situation, the customer views, transacts, receives an alert, and/or places a call from an embedded number. The customer typically pays a carrier fee for usage and for whatever transaction costs that are incurred from the merchant. Additionally, the carrier bills the customer for wireless data usage on the PCS mobile device.

Furthermore, the merchant may bill the customer for the transaction costs.

These multiple billings not only discourage the customer from using the capabilities offered by this arrangement, but also fail to provide the customer with incentives necessary to encourage loyalty and repeated use of the merchant.

Therefore, a need exists for a system and a method of use that will provide customers with the incentive to use their wireless devices with these merchants, a method to pay for goods through a wireless device with these merchants, and provides a method which allows for global settlement of value transfer, either credit or debits, between carriers, information/commerce merchants or users.

This invention provides an electronic revenue settlement system and a business method for wireless carriers and information/commerce merchants with applications on mobile devices such as mobile phones, personal digital assistants, interactive pagers, and similar mobile devices. Based on customer activity, information/commerce merchants will provide some form of credit or debit, revenue, or other monetary incentive system based on the customer's actions. Actions may include viewing or looking at information/commerce applications in a manner known commonly as "surfing," placing a call, viewing an application, requesting/receiving an alert, downloading any type of content, and conducting a commerce transaction through the mobile device, or similar actions involving the usage of at least one of these mobile devices. When a customer has connected to perform an activity such as these described, that customer will receive some form of credit or debit, revenue, or other reward or incentive from the information/commerce merchant. The customer may also use the present invention as a method for payment to the information/commerce wireless merchant. This credit or debit may be applied to the customer's wireless carrier bill. The present invention provides for an electronic, revenue settlement system and business method for wireless carrier systems and information/commerce wireless merchant services with applications and devices based on customer activity comprising viewing or looking at information/commerce applications, placing calls from these devices, viewing these applications, requesting/receiving an alert to the customer's mobile device based on one of these wireless applications, or conducting a commerce transaction through the mobile device wherein an exchange of funds such as credit or debit, or cash is taking place. The customer will receive a revenue credit or debit from the information/commerce wireless merchant service site as described herein. This will be tracked to the information/commerce merchants through an activity detail record and may be forwarded to at least one service bureau that will handle the reconciliation of credit or debit, revenue, or other "e-cash" transaction on behalf of the information/commerce merchants with each wireless carrier system.

Reconciliation can take place in real-time or from batching process such that reconciliation occurs preferably at least on a daily basis. The service bureau will be responsible for maintaining on behalf of the information/commerce merchants' accounts or "floats" which will be used for settlement/reconciliation of revenue credit or debits with wireless carriers. Wireless carriers and/or information/commerce merchants will receive funds through the information/commerce merchants' accounts based on activities by customers that are conducted on the information/commerce merchants' applications on the customers' mobile devices.

Wireless carriers systems will receive some form of credit or debit, revenue, or other e-cash via electronic transfer of some form of credit or debit, revenue, or other kind of e-commerce based on details provided in these activity detail records. Based on these activity detail records, some form of credit or debit, revenue, or other e-cash will ultimately be credit or debited to the customer through the wireless carrier system's billing process. The service bureau will provide both the wireless carrier system and the information/commerce merchant with reports either electronically or by other means.

This system and business method is compatible with any wireless carrier system, using any wireless technology, regardless of the type of mobile device being employed. Any computer operating system or hardware type known those skilled in the art should be operable with this system and method.

The wireless data application revenue settlement system and business settlement system for wireless carrier systems for wireless information/commerce merchant sites and customers are arranged with notable elements:

(1) wherein data is defined as the movement of encoded information by means of electronic transmission systems;

(2) wherein wireless data includes CDMA ("Code Division Multiple Access")-based data GSM ("Global System for Mobile Communications")-European standard for digital cellular telephones systems with increasing use within the United States based on the earlier name of Groupe Special Mobile - based data, TDMA ("Time Division/Domain Multiple Access")- base data, and/or 2.5G ("Two and a half Generation") data;

(3) wherein mobile device is defined by an electronic communication device having a screen or similar device for display of graphics, text, and/or video, which may include devices such as the PCS ("Personal Communication Service") mobile devices, interactive pagers, PDA ("Personal Digital Assistants") and/or similar devices; (4) wherein wireless data includes both packet data and circuit switch types;

(5) wherein settlement or reconciliation is defined as the balancing of values owed to a party after certain activity takes place - settlement may occur in real-time or batched in the future based upon a designated amount of time;

(6) wherein the wireless carrier system refers to companies or entities that provide a means to connect to voice or data networks through the use of mobile or wireless devices and/or receivers that are connected electronically to wireless carrier system network transmission facilities; (7) wherein a wireless information commerce merchants is defined to include companies or entities that have business processes, either information or commerce, which are electronically accessible through mobile devices for consumers to view or interact with;

(8) wherein an application is defined by a computer program designed for a specific task or use, including activities which are conducted through the communications network commonly known as the Internet formerly known as the Advanced Research Projects Agency Network, but not limited to this wide area network;

(9) wherein customers are defined to include persons who may be clients of either a wireless carrier system and/or an information/commerce merchant;

(10) wherein customer activities may comprise such activities such as viewing or "surfing" information content, placing a call to a telephone number embedded in the application or similar designation, receiving an "alert" either visual. motion, and/or sound, downloading content, and/or execution of commerce through the mobile device;

(11) wherein the mobile device screen includes visually viewable area that may be observed by a customer; (12) wherein some form of credit or debit, monetary form, revenue, incentive, reward, and/or other e-commerce is defined as a value such as wireless data minutes, voice minutes, or some other form of "e-minutes";

(13) wherein some form of debit, payment, monetary form, revenue, and/or other e-commerce is defined as a value such as wireless data minutes, voice minutes, or some other form of "e-minutes":

(14) wherein a bill is defined as a customer statement that will provide a record of communication conducted by the customer through the wireless carrier that may be received either in the electronic format such as an invoice via an electronic messaging system or paper base format such as invoice bill; (15) wherein Pre-paid wireless device account is defined as an account that the wireless customer has paid for wireless usage prior to engaging in wireless voice or data activities, and does not involve a paper based invoice;

( 16) wherein service bureau is defined as an entity typically with a plurality of local server computers utilizing high speed modems or Wide Area Network, backbone etc. that are capable of compilations, reconciliation, payment and recording data, and/or similar performance characteristics useful to business entities;

(17) wherein "counts" or "floats" are defined as secure repositories of monetary value; (18) wherein an electronic transfer of funds is defined as a process of an electronically transmitting monetary value to at least one party;

(19) wherein an activity detail records are defined as either physical or electronic records which provide details of action conducted by users and mobile devices;

(20) wherein a report is defined as a compilation of data regarding activities, some form of credit or debits, revenues, incentives, rewards, charges, and or e-commerce, and other pertinent marketing data is in a format useful to business entities. FIG. 1 is a representative flow-chart of an embodiment of the present invention:

FIG. 1A is a flow chart of an alternative embodiment of the present invention; FIG. 2 is a representative flow-chart of an embodiment of a customer action; FIG. 3 is a representative flow-chart of an embodiment of a customer action; FIG. 4 is a representative flow-chart of an embodiment of a customer action;

FIG. 5 is a representative flow-chart of an embodiment of a customer action; FIG. 6 is a representative summary invoice; and FIG. 7 is a representative detailed billing invoice.

The following provides a preferred embodiment of this system and a preferred method to implement this revenue settlement system. Those skilled in the art will recognize that substantial variation from the components that are used in this explanation is to be envisioned within this scope of this invention. Additional terminology used herein include: OS ("Operating System"), UNIX

("Universal Interexchange"), NT ("Network Termination"), LINUX ("Linus Torvald's UNIX"), TDMA ("Time Divisional - Domain Multiple Access"), SSTDMA ("Satellite Switch Time Division Multiple Access"), CDMA ("Code Division Multiple Access"), GSM ("Global Systems for Mobile Communications"), PCS ("Personal Communications Service" or "Personal Communication Services"), WML ("Wireless Markup Language"), HDML ("Hand-Held Device Markup Language"), cHTML ("Compact Hyper Text Markup Language"); -HTML ("tiny Hyper Text Markup Language"); VXML ("Voice Extensible Markup Language"); CDR ("Call Detail Recording" or "Call Dial Rerouting"), M-ADR ("Merchant Activity Detail Record"), CIBER ("Cellular Intercarrier Billing Exchange Roamer") - that is the standard for the exchange for cellular billing data as established by the Center for International Business Education and Research that is used today by wireless carriers to exchange roaming subscriber information for call detail records. IPDR ("Internet Protocol Detail Record") - that is the standard for open, carrier-grade IP-based support systems that enable next-generation service providers to operate efficiently and cost effectively, ESN ("Electronic Serial Number"), MIN ("Mobile Identification Number"), XML ("Extensible Markup Language"), SGML ("Standard Generalized Markup Language"), ML ("Markup Language"), PIN ("Personal Identification Number"), and CSR ("Customer Service Representative").

In summary, this invention provides a method for retailers, wireless hardware vendors and carrier system provider, and customers to work within the existing technical standards and the existing information technology "IT" infrastructure. Moreover, the present invention is able to utilize existing HDML/WML ("Hand-Held

Device Markup Language/Wireless Markup Language") wireless applications and wireless gateway servers.

HDML/WML is used for making web pages accessible by the many browsers used in hand-held wireless devices. (As used herein, HDML/WML shall further refer also to cHTML, tHTML and VXML.) HDML/WML served as the basis of the wireless access protocol ("WAP") forms wireless markup language ("ML"). Products using this language are able to deliver e-mail and similar Internet information services of wireless phones and similar devices. Moreover, these devices may utilize networks that operate over the Global System for Mobile Communications ("GSM"). Code Division Multiple Access ("CDMA"). Time Divisional/Domain Multiple Access ("TDMA"), Satellite-Switched Time Division Multiple Access ("SSTDMA"), Programme Delivery Control ("PDC"), Personal Handy Phone System ("PHS"). Cellular Digital Packet Data ("CDPD"), and/or devices such as a Personal Communication Systems Mobile Device ("PCSMD"). Personal Digital Assistant ("PDA"), or similar pager.

With the present invention, carrier systems and mobile commerce merchants will share the business model based on the profitability and actions of the customer. Mobile or wireless merchant sites will provide a revenue credit or debit to customers by passing this credit or debit via the wireless carrier billing system. (Any time a debit or credit is created by the mobile or wireless merchant and is in the process of being passed back to the mobile customer, it could further be placed on a third party billing agent billing system, such as a major credit card system like VISA®, Master Card®, American Express®, Discover®, etc., or other like Service Bureau's. Thus, for purposes herein, the term "wireless carrier billing system" as used herein may refer to a third party billing agent billing system.) The wireless carrier system will take a small share of this transaction revenue as the credit or debit is passed to the consumer. This shared transaction revenue is in effect an award or reward or charge for the customer transacting, surfing, receiving an alert, or otherwise acting on a mobile merchant site.

In preferred implementation, mobile merchants and wireless carriers will initially apply via a secure web interface to be included within the system. In turn, mobile customers will be able to find out general information regarding this system via the Internet using the browsers or similar methods to visit web sites having information on the subject.

Turning to FIG. 1 , a representative flow chart of the preferred embodiment of the present invention is shown. In this embodiment, a consumer or user 10 is shown using a wireless device 11, such as a PCS mobile device. In this example, the user 10 is using the PCS mobile device 11 such that the user 10 is browsing a WML/HDML site that will be discussed herein.

The PCS mobile device transmits signals via a carrier network 12 to a carrier system 13. This carrier system 13 provides connectivity and access to a WML/HDML wireless merchant site 14 via the Internet 15. Before accessing site 14. Server 19 logs subscriber ID, CODE, DATE, TIME, DESTINATION NAME, DESTINATION LOCATION, ORIGIN NAME, ORIGIN LOCATION. Server 19 will either be internal in Carrier 13 or sit in parallel to Carrier 13 or reside on Wireless Merchant Site 14. Preferably, the merchant will own this WML/HDML wireless merchant site 14 and provide content, e-commerce capability, and/or an embedded phone number in the HDML/WML code in this situation.

As shown herein, it is likely that the carrier system 13 will connect with the merchant wireless site 14 via the Internet or similar wide area network 15. As shown, the user 10 utilizes the mobile device 11 in a data mode that makes a data call. The call is routed through the carrier network 12 to the carrier wireless Internet gateway server 13. This signal in turn passes via the Internet 15 or other wide area network ("WAN"). When customer 10 makes his or her data call and a request to a HDML/WML service is made, the carrier system 13 adds a header that provides information about the customer, host, and mobile device. This information is used to identify the details about the customer 10. The present invention then translates details of the actions with regard to the information/commerce merchant site 14 on the basis of what actions are taken and are logged to Server 19. Preferably, the following information can be included in the Server 19 log: a subscriber ID (Globally unique), a wireless Internet Gateway Host Name, the browser version, and/or the device language. Additionally, Activity Information could include Activity Code (B, P, T, A), activity date, activity time, destination name, destination location, destination ID, origin name, origin location, and origin ID. For example, the following information could be collected: B, 01221999, 152322, eFuzion Web site, www.efuzion.com, 207.216.077.008, Bell Mobility, wireless gateway.bellmobility.ca, 161.216.124.002, respectively. In the preferred embodiment, this previous information will comply with the standard CIBER ("Cellular Intercarrier Billing Exchange Roamer") or IPDR ("Internet Protocol Detail Record") standard for exchange of cellular billing data format used at the present time by wireless carriers 13. The data calls routed through the Internet 15 to a merchant wireless site 14 can provide information/commerce.

The customer 10 may perform any of the following actions: browse the wireless HDML/WML sites with the mobile devices, set up to receive an alert message through the mobile device; place a call to a telephone number embedded in the information/commerce merchant wireless site; download content from a information/commerce merchant site; and/or transact commerce such as executing a trade, buying a good or service, or similar activity. Such an invention will also be able to track future activities not described herein.

In turn, the customer 10 executes at least one action. The present invention will log this activity in a logging device on the Server 19. This activity log may be used to generate a merchant activity detail record that includes header, activity, and/or trailer to form the details of the activity that was created.

The information/commerce merchant located at the information/commerce merchant site 14 rewards the customer 10 with a compensation for his or her actions at the merchant's wireless site 14 or charges the customer based on his or her actions. This value is predetermined based on how the information/commerce merchant has configured and negotiated the present invention as discussed herein. This action takes place on the Service Bureau using the merchant web admin 18a for the merchant and carrier web admin 18b for the carrier. When the customer 10 is finished his or her action is logged in a file or database. Preferably, this information is forwarded in the merchant activity detail record format from Server 19 to a service bureau 16. This database of information is processed with the output used to form a detail record that is formatted to mimic a CIBER or IPDR record. Typically, the service bureau 16 processes each merchant activity detail record by calculating the activity and credit or debit value and forwards the result to the carrier system 13. Based on the value of the credit or debit for the activity, the service bureau 16 withholds a small portion of the credit or debit value before passing the remainder to the carrier system 13 that includes amounts for both carrier 13 and customer 10.

The carrier activity detail record is sent from the service bureau 16 to the carrier system 13 in either real-time or is batched with other carrier system activity detail records and processed on a time basis (i.e. daily). Those skilled in the art will recognize the significant variation from this system may be agreeable to the service bureau 16 and the carrier system 13. For security reasons, those skilled in the art will recognize that this information may be transferred in an encrypted form.

The carrier system 13 processes the carrier activity detail record. At this time, the carrier systems 13 retains the amount allotted to the carrier configuration at carrier web admin 18b. The carrier system 13 passes the difference in credit or debit value to the carrier billing system 17, in turn, forwarding it to each customer 10. It is envisioned that this credit or debit value may be included as a credit or debit on the customer 10's monthly billing. Each carrier activity detail record credit or debit will be logged and applied to the carrier customer 10's monthly bill. For verification, it is also envisioned that the service bureau 16 will calculate a total value of all activities with a carrier system 13 and send a summary of the carrier activity detail record to each carrier 13 on a routine basis. As before, it is envisioned that this summary carrier activity detail record may also be encrypted prior to sending to each carrier system 13. In turn, each carrier 13 settles with the service bureau 16 the amount of value owed by the service bureau 16 to the carrier system 13.

Alternatively, the information/commerce merchant located at the information/commerce merchant site 14 can debit the customer 10 for payment for the use of the mobile application, such as a transaction, alert, etc.. This "air debit" will ultimately appear on the customer^'s carrier bill, or be deducted from the customer's pre-paid wireless device account.

Typically, it is envisioned that each wireless carrier and/or information/commerce merchant named to any information/commerce merchant site 14 will maintain "float" account of monies with the service bureau 16. Those skilled in the art will recognize that variation of this system to allow for a credit or debit situation to develop between the merchant wireless site 14 and the service bureau 16 may be preferable. Preferably, the carrier system 13 will have the capability to electronically retrieve a total value of the carrier activity detail records from the appropriate information/commerce merchant float account. In this arrangement, the service bureau 16 may electronically send daily notifications to the information/commerce merchant wireless site 14 of how much value has been subtracted from their account. To ensure daily resolution of these accounts, it is preferable that each information/commerce merchant maintaining that information commerce/merchant wireless site 14 maintains a minimum level in each float account.

Many variations of this system and method will be evidence to those skilled the art. For example, FIG. 1A shows a representative flow chart of an alternative embodiment of the present invention. In this alternative embodiment, consumers or users 10a, 10b, and 10c are shown using wireless devices 1 1a, l ib, and l ie, respectively, such as PCS mobile devices. The users 10a, 10b, and 10c are using mobile devices 11a, l ib, and 1 lc, respectively, such that each user 10a, 10b, and 10c are browsing WML/HDML sites that will be discussed herein. These PCS mobile devices 11a, l ib, and l ie transmit signals via carrier networks 12a, 12b, and 12c to carrier systems 13a, 13b, and 13c, respectively. These carrier systems 13a, 13b, and 13c provide connectivity and access to WML/HDML wireless merchant sites 14a, 14b, 14c, and/or 14d via the Internet 15. Preferably, each WML/HDML wireless merchant sites 14a, 14b, 14c, and 14d provide content, ecommerce capability, and/or an embedded phone number in the HDML/WML code as previously discussed with respect to FIG. 1.

As before, these users 10a, 10b, and 10c utilize mobile devices 11a, l ib, and l ie in data modes that makes data calls. These calls are passed through carrier networks 12a, 12b, 12c, and 12d to carriers 13a, 13b, and 13c, respectively. These signals in turn pass via the Internet 15 or similar wide area networks known to those skilled in the art.

Similarly to description herein with respect to FIG. 1, these information/commerce merchants located at the information/commerce merchant sites 14a, 14b, 14c, and/or 14d provide these customers 10a, 10b. and 10c with compensation for their actions at the merchants' wireless sites 14a, 14b, 14c, and/or

14d. Demonstrating the flexibility and scope of the invention, multiple service bureaus 16a and 16b have been depicted in FIG 1A. These service bureaus 16a and 16b are capable of processing merchant activity detail records as previously described herein. As previously discussed, these service bureaus 16a and 16b may electronically send daily notifications to the information/commerce merchant wireless sites 14a, 14b, 14c, and/or 14d of how much value has been subtracted from their accounts. To insure daily resolutions of these accounts, these information/commerce merchants, maintaining that information, commerce/merchant wireless sites 14a, 14b, 14c, and/or 14d maintain minimum levels in each float account.

The depiction of FIG. 1A respects an alternative embodiment but certainly does not represent the broader scope envision within the patent as described herein or as claimed. It should be evidence to those scoping the art that virtually any combination or permutation of service bureaus, information/commerce merchants. carrier systems, carrier networks, mobile devices, and/or customers or users are within the scope of this invention as described and claimed herein.

FIGs. 2-5 show representative actions taken by a customer 10. As shown in FIG. 2, a representative browse process, a wireless customer 10 initiates a browse process using a mobile device 11 (not shown) via wireless network 12 to a carrier system 13. In turn, the carrier system 13 contacts a merchant wireless service 14 via the Internet 15. Customer activity is logged on Server 19. The browsing activity creates a merchant activity detail record 20 that is transmitted from Server 19 via the Internet 15 to service bureau 16. Service bureau 16 processes this merchant activity detail record, calculates merchant amount, herein (-$0.05), calculates the service bureau amount, herein $0.01, calculates carrier amount, herein $0.02 and calculates customer amount herein $0.02. The service bureau forwards a carrier activity detail record 22 via the Internet 15 to the carrier system 13. The carrier system 13 processes the carrier activity detail record 22 and retains a portion thereof, herein $0.02, and forwards the credit of $0.02 to the carrier billing system 17. The carrier billing system 17 will be reflected as a credit on the customer's invoice 24 as shown in FIG. 6 and FIG. 7.

Additionally, FIG. 2 also shows a representation of the daily settlement between the service bureau 16, the merchant account 28, and the carrier account 27. As previously discussed, the service bureau 16 generates a record on a routine basis and uses the record 25 and 26 to settle within the carrier account 27 and merchant account 28, respectively. With regard to the carrier account 27, the daily settlement 25 would reflect the $0.04 of carrier activity detail record 22 in addition to any other carrier activity detail records that were transmitted that day. Moreover, the service bureau 16 will also generate a notification to the merchant 14 of a daily settlement 26 requesting $0.05 for merchant 14. If the float account, as previously discussed herein has been implemented, the service bureau 16 will deduct this $0.05 to resolve the daily settlement 26.

Turning to FIG. 3, a typical alert process is shown. In this embodiment, the wireless customer 10 receives and an alert generated by the merchant wireless service 14 or the service bureau push engine. In this configuration, when the alert is appropriate, the merchant wireless service 14 or service bureau 16 using a push engine will send a signal via the Internet 15 to the carrier system 13. In turn, the carrier system 13 will forward this alert via the wireless network 12 to the wireless customer 10. Simultaneously, the merchant wireless service 14 logs the alert activity in Server 19. The alert activity creates a merchant activity detail record to the service bureau 16. In this embodiment, an alert activity has been shown on the merchant activity detail record 20 that has been forwarded to the service bureau 16. If the service bureau 16 generated the alert, the activity is logged within the service bureau logs and no merchant activity detail record is produced.

The service bureau 16 retains $0,002 and forwards a carrier activity detail record 22 to the carrier system 13. Showing the deduction, the representative amount of $0,004 has been calculated for both the carrier and the customer and has been forwarded in the customer activity detail record to the carrier system 13. The carrier system 13 retains $0,004 and forwards to the carrier billing 17 an amount of $0,004 to be credited to the customer invoice 24.

As before, this service bureau 16 performs daily settlements 25 and 26 to both the carrier account 27 and merchant account 28, respectively. The daily settlement 25 to carrier account 27 shows each of the totals of the carrier activity detail records of the day. In this example, this daily settlement would show $0,008. Moreover, the service bureau 16 also performs a daily settlement 26 with the merchant's account 28. This daily settlement 26 will reflect the daily merchant activity detail records that were forwarded from the merchant wireless service 14 or logged with service bureau push engine. In this example, the daily settlement 26 shows an amount due of $0.01.

As previously discussed, this $0.01 may be subtracted by the service bureau 16 from money held in "float" for the alert activity from the merchant wireless service 14 or service bureau 16. Turning to FIG. 4, a place call process is shown. The customer 10 initiates this process via the wireless network 12 to the carrier system 13. In turn, the carrier system 13 contacts the merchant wireless site 14 via the Internet 15. Logging of activity takes place on 19. At this point, this process is similar to the browse action shown in FIG. 2. The server 19 will forward a merchant activity detail record 20 to the service bureau 16.

As shown herein, the merchant activity detail record 20 comprises (as an example) of the place call activity and forwarded to the service bureau 16. The service bureau 16 processes this merchant activity detail record and calculates the merchant amount, herein $0.50, and the service bureau amount, herein, $0.10. In this example the remainder is forwarded via a carrier activity detail record 22, to the carrier system 13 showing $0.20 to the carrier and $0.20 to the customer. In turn, the carrier system 13, after retaining a portion of the fee, herein $0.20, forwards the remainder to the carrier billing system 17 such that the customer's invoice 24 will reflect a $0.20 credit. As before, the service bureau 16 will also maintain daily settlements 25 and 26 with the carrier account 27 and merchant account 28, respectively. The daily settlements will notify the carrier of the $0.40 received in the daily settlement 25 for this example. Moreover, the service bureau 16 will notify the merchant that $0.50 has been removed from the float account maintained for that merchant based on the daily settlement 26.

Of note, this process of placing a call also initiates a voice call. When the customer activates a call, the device switches from data mode to voice mode and dials the number that was embedded. When the customer hangs up, the device returns to the same spot left in data mode before initiating the call.

As shown in FIG. 5, the wireless customer 10 has placed a representative transaction. In this typical transaction, the wireless customer 10 initiates a signal using a wireless device 11 (not shown) via the network 12 to carrier system 13. In turn, carrier system 13 connects to the merchant wireless site 14 via the Internet 15.

Logging of activity takes place through Server 19. The with merchant wireless service 14 forwards the transaction information via the Internet 15 to a transaction processor 51. As with the other aspects of this invention, it is envisioned that this transaction may be encrypted to ensure secrecy and security. The transaction processor 51 will collect the data and perform whatever transaction has been purchased or sold, for example a stock. Those skilled in the art will recognize that transaction processor 51 may require manual intervention. This manual intervention may take virtually any form but may include but not limited to the human processing of shipping orders, verification of information, or similar activities.

Of note, Logging System Server 19 forwards a merchant activity detail record 20 to service bureau 16. The service bureau processes this merchant activity detail record 20 and calculates amounts for the carrier customer, and service bureau. Herein, the carrier receives $1.50, the customer $1.20 and service bureau the remainder. Service bureau 16 retains a portion and forwards the remainder in carrier activity detail record 22.

As shown herein, service bureau 16 retained $0.30 and forwarded $2.70 in carrier activity detail record 22 with $1.20 for the customer and $1.50 for carrier. Carrier activity detail record 22 has been forwarded to the carrier 13. Carrier 13 in turn retains a portion, herein $1.50, and forwards the remainder to carrier billing 17. The carrier billing processes this amount $1.20 and forwards a credit to the customer invoice 24 to be reflected against the monthly fee. As shown herein, customer invoice 24 will receive a credit of $1.20. A representative invoice and detailed billing are shown in FIGS. 6 and 7, respectively. These invoices show representative incentives or credits that the customer will enjoy as a result of their actions.

As before, service bureau 16 also generates daily settlements 25 and 26 with the carrier account 27 and merchant account 28, respectively. As shown herein, the daily settlement 25 with carrier account 27 will show $2.70 based on this carrier activity detail record 22. As before, additional carrier activity detail records would be reflected in this daily settlement 25. Moreover, daily settlement 26 will be with merchant account 28.

Of note, daily settlement 26 reflects the merchant activity detail record 20 of (-$3.00). Similarly, daily settlement 26 would reflect additional merchant activity detail records that were processed for that day. As before, service bureau 16 subtracts the amount of daily settlement 26 from the float account maintained for each merchant wireless service 14. As shown in FIG. 5 A, the wireless customer 10 has placed a representative transaction. In this typical transaction, the wireless customer 10 initiates a signal using a wireless device 11 (not shown) via the network 12 to carrier system 13. In turn, carrier system 13 connects to the merchant wireless site 14 via the Internet 15. Logging of activity takes place through Server 19. The merchant wireless service 14 forwards the transaction information via the Internet 15 to Server 19. Those skilled in the art will recognize that Server 19 may reside within Service Bureau 16. As with the other aspects of this invention, it is envisioned that this transaction may be encrypted to ensure secrecy and security. Server 19 will collect the data and perform whatever transaction has been purchased or sold, for example an interactive game. Of note. Logging System Server 19 forwards a merchant activity detail record 20 to service bureau 16. The service bureau processes this merchant activity detail record 20 and calculates amounts for the carrier customer, and service bureau. Herein, the carrier receives/keeps $.25, the customer pays $2.00 and service bureau the receives/keeps $.25.

As shown herein, service bureau 16 retained $0.25 and forwarded $2.00 in carrier activity detail record 22 with $2.00 charged to the customer. Carrier activity detail record 22 has been forwarded to the carrier 13. Carrier 13 forwards the $2.00 to carrier billing 17. The carrier billing processes this amount $2.00 and forwards a debit to the customer invoice 24 to be reflected against the monthly fee. As shown herein, customer invoice 24 will receive a debit or charge of $2.00. A sample representative invoice and detailed billing are shown in FIGS. 6A and 7A, respectively. These invoices show representative charges or debits that the customer will be charged as a result of this transaction.

As before, service bureau 16 also generates daily settlements 25 and 26 with the carrier account 27 and merchant account 28, respectively. As shown herein, the daily settlement 25 with carrier account 27 will show $1.75 based on this carrier activity detail record 22. As before, additional carrier activity detail records would be reflected in this daily settlement 25. Moreover, daily settlement 26 will be with merchant account 28.

Of note, daily settlement 26 reflects the merchant activity detail record 20 of $1.50. Similarly, daily settlement 26 would reflect additional merchant activity detail records that were processed for that day.

In the instance that wireless customer 10 has a Pre-paid wireless device account, those skilled in the art will recognize this transaction working in reverse, such that a transaction charge $2.00 will be subtracted from wireless customer 10's Pre-paid account.

Those skilled in the art will recognize that the placement of the present invention within the present infrastructure may be developed in phases. Namely, the inventors envision a development that it will include the development of software for wireless carrier systems, wireless merchants, wireless software vendors, and wireless hardware vendors. It will be possible for the software to be embedded in other companies' wireless Internet hardware. This development will include the development of at least one service bureau 16. Each service bureau 16 subsists based on retaining a percentage of the credit or debit as a fee for providing the brokering/aggregation service. Moreover, the mobile wireless merchant sites 14 will maintain their flow to funds with each service bureau 16. It is envisioned that service bureau 16 would be capable of providing hosting services for smaller merchant services 14 or smaller carrier systems 13. It is also envisioned that the present invention comprises the ability to track activity of customers 10 via the header information provided as previously discussed herein. The present invention may easily comprise a database of information for each mobile merchant wireless service 14 while tracking the activity of these customers 10 via Logging System Server 19. Furthermore, it is envisioned that service bureau 16 will comprise the ability to notify each merchant wireless service 14 to replenish the float accounts maintained by the service bureau 16.

The present invention may also comprise a messenger module. It may be used for a number of different functions for both wireless carrier systems 13 and merchant wireless services 14. Notably, this system may be used to deliver notification to customers 10 of additional mobile merchant wireless services 14 or special incentive programs such as coupons or rebates available to customers 10. Of note, profile information on each customer 10 may better target these notifications. This messenger service may be provided both in a wireless form or web form depending on the profiles established by each customer during the application process. For initial registration of each customer 10, it is envisioned that the inclusion of the customer 10's e-mail mobile address would be helpful, however, not essential. This would allow each customer 10 to be notified when additional mobile merchant wireless services 14 are available that suit their profile and also allow them to check balances of revenue credits or debits they have accumulated. Customers may also go to the system's Web site to access any of the information/commerce merchant wireless sites. Moreover, it allows for targeted advertising based on mobile merchant sites 14 having incentive programs that would be of interest to each customer 10 based on his or her profile.

Similarly, each wireless carrier system 13 needs to register with this present invention. Preferably, using a secure connection, it is envisioned that each wireless carrier system 13 would register with the system via a secure web site or similar connection known to those skilled in the art. The identifying information such as user name, password, login names, hint questions for forgotten passwords, and similar questions may be included within this registration. This is calculated/configured by the carrier via carrier web admin 18b.

Moreover, each merchant wireless service 14 that is incorporated would fulfill a similar registration process. In addition to identifying information as discussed herein, the merchant would indicate additional information with regard to the services and goods being offered via the merchant wireless service 14. At the initial registration process, both merchant wireless services 14 and carrier systems 13 would go through an initial login procedure that would verify the identity of each. This is calculated/configures by the wireless merchant via web admin 18a. Furthermore, these systems must be designed to allow subsequent profile changes. An additional feature that may be incorporated into the present invention is a merchant wireless service 14 profile configurator. This configurator would be responsible for maintaining the profile of each merchant wireless service 14 on an ongoing basis. Specifically, it is envisioned that unique and specific business models based on negotiations of policies with each wireless carrier system 13 may be included with this profile. Information such as the nature of splitting of revenues with each carrier system 13 can be negotiated by establishing profiles and making preferences of negotiations such as requiring flat fees or percentages of the customers actions with regard to each carrier system 13 through Service Bureau 16. This relationship allows for each merchant wireless site 14 to negotiate and contract for a distinct agreement with each carrier system 13 through Service Bureau 16.

Moreover, each merchant wireless service 14 may include information regarding special features or abilities that each merchant wireless service 14 comprises. For instance, the merchant wireless service 14 may accept Microsoft Passports™, Key-Passes™, e-Wallets™, or similar devices. Similarly, each carrier system 13 is responsible for maintaining its profile on an ongoing basis in a similar manner. Not only does each carrier system 13 through Service Bureau 16, include information regarding terms of negotiations with each merchant wireless service 14, but each wireless carrier system 13 through Service Bureau 16 could identify information regarding the customer 10's profile. This enables merchant wireless services 14 "shopping" for carrier systems 13 to better evaluate each customer 10 that will be available on the Service Bureau 16.

Another aspect of the present invention may include a merchant wireless service 14 tracking database through service bureau 16. This database would allow for the tracking on a monthly basis of the credits or debits, charges, awards, incentives, rewards, or values that have been passed to each mobile customer 10 on an individual total basis. Information such as the mobile ESN, MIN, and similar identification may be included. It is expressly envisioned that e-mail addresses and information relating to the identification of the carrier system 13 that each mobile system then use to access the merchant wireless site 14 would be especially useful.

Additional information that may be useful include information related to the date of the call, the time of the call, the duration of the call, the customer 10's action performed such as surfing, viewing, placing a call, receiving an alert, or executing a transaction would be especially useful. Additionally, this database could comprise information regarding the credit or debit value provided and whether it was a flat dollar amount, a rate based on seconds for the activity, or a percentage of the transaction with the mobile customer 10. Additionally, this database could correlate these credits or debits to a specific dollar amount that represents the value of these credits or debits. Finally, whether third party such as Microsoft Passport™, Key- Pass™, e- Wallet™, or similar services was used may be logged.

This database allows each merchant wireless service 14 to track its programs with the various wireless carrier systems 13 to compare the effectiveness of the present invention between each carrier system 13. Based on monthly performance derived from this database, each merchant wireless service 14 may be able to renegotiate or better focus their efforts on carrier systems 13 that provide customers 10 that are performing favorable actions with regard to the merchant wireless service 14. In addition, this database could include aggregate totals of each month with regard to the number of unique of SUB-ID' s ESNs received, the unique MINs used, the unique e-mail addresses collected, the total actions performed, the total value of credits or debits collected by e- Wallets™, for example, the total dollar value for credits or debits provided to mobile customers 10, a total dollar value of credits or debits to be invoiced from wireless carrier systems 13, and/or running total per credits or debits passed year to date. Each of these portions of information will allow each merchant wireless service 14 to better evaluate the effectiveness of the present invention and further configure their profile to better attract customers 10 perform or receive actions from that particular merchant wireless service 14.

Similarly, each carrier system 13 could benefit from a tracking database. In a similar manner, the carrier system 13 could benefit from a tracking database that shows the mobile customers 10 by ESN, MIN, e-mail address URL's visited, date of call, time of data call, action activities performed, credit or debit value provided, dollar amount of credit or debit, and e-Wallet™ links as previously discussed. As before, information relating to the activities performed such as surfing viewing, placing a call, sending an alert, or executing a transaction is especially important.

Moreover, the credit or debit value provided, whether by flat dollar amount, seconds based on a rate, or percentage of the transaction to the mobile user 10, represents an important piece of information. Finally, it is envisioned that additional information related to the sites visited by the mobile users 10 could better allow each carrier system 13 to better tailor their negotiations with each merchant wireless service 14 to not only negotiate for better rates for their customers, but also to insure that the carrier system 13 is recognizing each merchant wireless service 14 demanded by the customers 10.

A detailed breakdown of this tracking database is especially useful for each carrier system 13. Specifically, this information may be analyzed to allow the wireless carrier system 13 to determine that each mobile customer 10 focuses his or her actions on specific sites for specific purposes. Moreover, each carrier system 13 will be able to determine what specific action each wireless customer 10 undertakes when connecting via that particular carrier system 13.

As before, aggregate totals for the wireless carrier system 13 database are also useful. Information such as the number of unique ESNs, Subscriber ID's, number of unique MINs, number of unique e-mail addresses, and totals for the actions performed are especially useful. With regard to the monetary crediting or debiting process, it is important to determine the total value from e- Wallets™ collected, total value of credits or debits received from merchants, total amount of funds to be invoiced to merchant wireless services 14, and maintaining a running total for credits or debits passed year to date to the mobile customers 10. This system allows each carrier system 13 to evaluate the effectiveness of the present invention and further modify their profile to attract mobile merchant wireless services 14 that their customers 10 require. Ultimately, it is also envisioned that a master tracking database maintain on a monthly, accurate basis can provide an overall picture of overall activity of what has been transpired between each carrier system 13, each merchant wireless site 14, and each mobile customer 10. This transaction may be connected to form a breakdown of the mobile merchant wireless services 14, the wireless carrier systems 13. the e-mail addresses of each mobile user 10, and specific information of each.

For example, this master tracking database could provide an overall picture of which carrier systems 13 are being used, the e-mail addresses of each mobile customer 10 performing actions, and specific information related to each action performed. In addition, this master tracking database could provide an overall of which carrier system 13 and merchant wireless services 14 are being more utilized by customers 10 to fulfill the goals of the present invention. Moreover, the analysis of the e-mail addresses could provide information regarding the carrier system 13 that is being used by the mobile customers 10 to access specific merchant wireless services 13.

Information related to the mobile ESNs and MINs numbers could provide an activity report that could show patterns of customers 10. Information related to the area codes and mobile telephone numbers used along with the number of calls, and the date of the calls, and/or the average length of the calls, could determine the shopping/activity habits of customers with regard to specific sites such as a specific merchant wireless service 14. Moreover, an analysis of the credit or debit value provided by each merchant wireless service 14 via the carrier system 13 to each customer 10 allows for an assessment of the effectiveness of the present invention. Additionally, aggregate totals based on the number of unique ESNs, unique

MINs, unique e-mail addresses, unique sites visited, and totals thereof may present information to show the effectiveness of the present invention. Moreover, total numbers related to site visited, activities performed-including a breakdown of surfing viewing/placing a call, sending alerts, downloads of content, and executing transactions, total value of credits or debits received from merchant wireless services 14, total value of credits or debits provided to mobile customers 10 via carrier systems 13, and a running total per credits or debits passed year to date to mobile customers 10 would be especially useful.

In addition, it is envisioned that at least one service bureau 16 will act as a third party in the settling of funds between wireless carrier systems 13 and mobile merchants wireless services 14. As discussed with regard to FIGs. 1-5, this system has been shown on a simplified scale. With the single service bureau 16 in this situation, it effectively provides for the reconciliation between each carrier system 13 and each merchant wireless service 14. Moreover, the inclusion of a plurality of service bureaus and discussed with regard to FIG. 1A shows the intended scope and breadth of this invention.

Service bureaus 16 may offer the following functions: hosting of the applications for smaller wireless carrier system 13; hosting of the applications for smaller merchant wireless services 14; reconciling of funds between merchant wireless services 14 and carrier systems 13; and/or auditing and reporting functions; and maintaining of databases as previously discussed herein.

Though many payment systems with regard to each service bureau 16 will be evident to those skilled in the art, the payment and reconciliation size settlement goal is to facilitate transaction and to reduce the requirement to collect funds from merchant wireless service 14 and wireless carrier system 13. This may be accomplished in multiple ways. Of note, it is envisioned that service bureau merchant accounts may be maintained. In this situation, merchant wireless services 14 will have an account with the service bureau 16 that will be used to settle transfers from settlement services. This will act as a float for revenue settlement.

Moreover, wireless carrier systems 13 will therefore be compensated for all of the following transactions: surf/view; place a call; send an alert; download content; and/or execute a transactions. Moreover, upon an activity occurring by customer 10, the activity detail record as previously discussed will be created and routed by the

Logging System Server 19 to the service bureau 16. These activity detail records will be used to help reconcile the funds that are transferred to the wireless carrier 13 on a daily basis.

Furthermore, settlement will occur by having funds electronically transferred to or received from each wireless carrier system 13. Mobile merchant systems require that merchant wireless services 14 will have electronically transferred funds to or received from the float account based on certain thresholds that may determine either by a float level or the time of the month basis. Alternatively, merchant wireless services 14 may be invoiced by the service bureau, based on a time period such as monthly, that would immediately activate upon the crossing of the account threshold. As previously discussed the service bureau 16 takes a small percentage as a management fee for each of these activities. Alternatively, the reconciliation process may be comprised of a directory service. Software embedded within the mobile wireless service gateway will allow customer 10 at the point-of-purchase to be asked whether they are a member of the directory service either by a local merchant director or a third party directory such as Microsoft Passport™, Key-Pass™, e-Wallet™, or similar service. Once each customer 10 has answered this directory question and provided a personal identification number ("PIN") appropriate, an authorization procedure takes place.

In this situation, the funds are authorized by a directory service such as Key- Pass™, the funds would be provided to the merchant wireless service 14, and the service bureau 16 would be provided with its portion. It is envisioned that the service bureau 16 would also route the portion due to the wireless carrier system 13. In turn, the carrier system 13 would subtract its percentage either based upon a fixed rate, a rate of time, or a percentage, and then forward the remainder to the customer 10 billing invoice previously discussed herein.

Another aspect of the invention includes the development of the customer service system. Each service bureau 16 will design a graphically usable interface via a web-based service that will allow the administration and manipulation of database information. To ensure security, it is envisioned that different access levels will be provided to allow for individuals at each wireless carrier system 13 and mobile merchant wireless service 14 to properly administer applications without intruding upon the privacy of others. It is envisioned that the maintenance of this database information would require a certain level of customer service with regard to resetting of passwords, maintaining customer profiles, and providing for sanitized client profile information based on the sensitivity of the information provided.

Given that the present invention may be adapted to multiple platforms utilizing wireless technology, this invention preferably functions with at least one wireless carrier system 13, one merchant wireless service 14, one service bureau 16, and at least one wireless customer 10. This represents an oversimplification for the purposes of understanding the present invention.

In practice, the present invention benefits from being able to derive from a plurality of each of these components with the reward system as described herein with reference to FIG. 1A, a plurality of customers 10 using a plurality of carrier systems 13, and Logging System Server 19, in the manner previously discussed, are performing activities with regard to plurality of wireless merchant services 14. Though shown with only one service bureau 16 in this embodiment, multiple service bureaus 16 cannot only aide in the settlement and transfer of funds as previously discussed herein, but allows for an additional interface between each service bureau 16 as depicted in Figure 1 A.

In this relationship, each service bureau 16 may be tailored geographically, based on the provisions of goods and services, or similar classification to function in a more efficient manner. The end result in the present invention is shown in FIG. 6, 6A and FIG. 7, 7A, a representative customer invoice.

As reflected on these invoices, the aggregate total would award or show charges for the activities performed by each customer 10. As shown in the detailed activity shown in FIG. 7, each action performed by the customer 10 or received by the customer 10 has received some form of award or credit or debit and thus will encourage customer 10 to continue to use these services via that respective wireless merchant service 14 accordingly. Each customer 10 will develop a loyalty and take a more active use of the wireless carrier system 13. As shown in 7A, the transaction activity has appeared as a charge on the customer invoice. This system allows merchant wireless systems 14 to tailor and have better control over the reward and payment efforts for each customer 10. Additionally, each merchant wireless system 14 is able to better understand the benefits and results to each customer via the databases as discussed herein. Additionally, each customer 10 benefits from their actions and sees a quantifiable reward or charge for the activities performed with regard to each of the wireless services 14 discussed herein. Accordingly, each customer 10 is more likely to visit this merchant wireless service 14 again. With regard to the merchant wireless service 14, this loyalty or retention or ease of payment for the customer develops brand awareness among the customers 10 and also develops additional traffic to the site. These new customers 10 may seek out the wireless service 14 because of the competitive differentiation provided by its employment of the present invention. This encourages more active customers 10 that share more direct relationships to the advertising and benefits offered by each wireless service 14. Ultimately, an extremely active customer 10 could perform enough activity generating credits with wireless merchant services 14 such that his or her monthly invoice from his or her carrier system 13 would be significantly reduced or eliminated. Moreover, a significant level of activity could generate a monthly credit or debit that could be applied toward future months or otherwise reimbursed by each carrier system 13 as known by those skilled in the art. This lower monthly invoice ultimately allows each carrier system 13 to encourage and attract additional mobile users 10 to use their carrier system 13. The following is offered as a preferred embodiment for some of the representative features described herein. For example, the communication process may be employed as follows (X means alpha numeric preferably, 9 means numeric preferably):

Case 1: Browse, transaction, place call

For each Carrier System 13 to track carrier info:

TABLE 1: Track carrier information

For each Merchant Site 14 to track activity info:

TABLE 2: Track activity information

For each activity logging Server 19 to form a Log activity record:

TABLE 3: Forming activity record

Parameter Description Type Format Example

ORIG-NAME For a browse, X(52) Carrier Bell Mobility transact and Name place call activity this field would indicate the name of the carrier

For each real time transaction or daily batch transfer activity info to service bureau 16:

TABLE 4: Transferring activity information

For each Service Bureau 16 to allow each Merchant Web Admin 18a to configure browse, and/or place call, transact amount for merchant rate:

TABLE 5: Merchant Configuration

For each Carrier Web admin 18b to configure browse, place call, and/or transact amount for carrier rate. The Service Bureau 16, automatically calculates the customer rate based on Merchant and Carrier rates: TABLE 6: Carrier Configuration and Customer Rate

The Service Bureau 16 maps each CUST SUBNO to a customer to identify the customer, calculates merchant remittance, calculates carrier take, calculates customer take, calculates any taxes, and performs daily settlement for merchant and carrier:

TABLE 7: Calculation Amounts

With regards to the C-ADR:

TABLE 8: C-ADR Information

Case 2: Alert

In a push engine to push out alert message in the Activity log:

TABLE 9: Push out alert message

, -

For Service Bureau 16 to allow Merchant Web Admin 18a to configure alert rate for merchant rate:

TABLE 10: Merchant Configuration

For Carrier Web Admin 18b to configure alert amount for carrier rate, the Service Bureau 16 automatically calculates the customer rate based on merchant and carrier rates, customer rate:

TABLE 11: Carrier Configuration and Customer Rate

The Service Bureau 16 maps each CUST SUBNO to a customer to identify the customer such that the system calculates merchant remittance, calculates the carrier take, calculates customer take, calculates any taxes, and performs daily settlement for merchant and/or carrier:

TABLE 12: Calculation Amounts

With regards to the C-ADR:

TABLE 13: C-ADR Information

For Billing detail:

TABLE 14: Customer Number

Customer Mobile Number

4165551234

TABLE 15: Representative Browse

TABLE 16: Representative Transact

TABLE 17: Representative Place Call

TABLE 18: Representative Alert

TABLE 19: Representative Tax Inclusion

Taxes

0.38

Those skilled in the art will recognize that the present invention may operate with any or a combination of operating systems such as Windows®, UNIX. LINUX, or similar operating systems known to those skilled in the art. Moreover, the embodiment of this system and its method of use as disclosed herein should not be limited to the preferred embodiment disclosed. This system and method in many of its intended advantages, will be understood from the disclosure herein and it will be apparent that, although the invention and its advantages have been described in detail. various changes, substitutions, and alterations may be made in the form, construction, and/or arrangement of the elements without departing from the spirit and scope of the invention as defined by the appending claims, or sacrificing its material advantages. the form described previously being merely a preferred or exemplary embodiment thereof

Claims

I claim: 1. A system for revenue settlement comprising: at least one wireless device capable of transmitting and receiving signals; at least one carrier capable of receiving and transmitting the signals from each wireless device; at least one merchant site capable of being contacted via a wide area network by each carrier wherein each merchant site transmits a credit or debit for actions transmitted or received by each wireless device at the merchant site.

2. The system of Claim 1 comprising at least one service bureau capable of reconciling credits or debits transmitted by each merchant site.

3. The system of Claim 1 wherein the wide area network is the Internet.

4. The system of Claim 1 wherein each action comprises viewing, surfing, receiving an alert, or transacting.

5. The system of Claim 1 wherein each wireless device is a mobile phone, a personal digital assistant, or an interactive pager.

6. The system of Claim 1 further comprising a customer invoice for monies owed to the carrier from the customer wherein a portion of the credit or debit from the merchant site is applied to at least partially satisfy monies owed to the carrier as shown on the customer invoice.

7. The system of Claim 2 further comprising at least one database maintained by the service bureau that logs the actions of each customer.

8. The system of Claim 2 wherein the service bureau is capable of reconciling the credits or debits in real-time.

9. The system in Claim 1 wherein each credit or debit is a revenue, an incentive, a reward, or similar e-commerce.

10. A method for merchants to provide incentives for performing actions on a merchant site maintained by the merchant comprising providing a credit or debit for each action taken at the merchant site wherein the credit or debit is transmitted from the merchant site.

11. The method of Claim 10 further comprising logging each credit or debit in a database maintained by a service bureau.

12. The method of Claim 10 further comprising dividing the credit or debit amongst a service bureau, a carrier, and at least one customer.

13. The method of Claim 10 wherein providing occurs in real-time.

14. The method of Claim 10 wherein different actions cause the merchant to provide different amounts of credit or debit.

15. The method of Claim 10 wherein each action comprises viewing content at the merchant site, receiving an alert from the merchant site, or transacting at the merchant site.

16. The method of Claim 11 wherein logging further comprises collecting activity information related to each action.

17. The method of Claim 10 wherein providing credit or debit complies with the Cellular Intercarrier Billing Exchange Roamer Standard.

18. The method of Claim 10 wherein at least one action is a transaction further comprising using a third party directory for the transaction.