# US 2025/0173788 A1 · Electronic Mobile Commerce Transactions in a Wireless Network Using a Wireless Mobile End-User Device and a Transaction Server

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2025/0173788 A1
- Document ID: US20250173788A1
- Status: Published application
- Kind: A1
- Application number: 19/039,717
- Filed: 2025-01-28
- Published: 2025-05-29
- Earliest claimed: 2009-01-28
- Assignees: Headwater Research LLC
- Applicants: Headwater Research LLC
- Inventors: Gregory G. Raleigh
- Web page: https://patentgrep.com/patent/US20250173788A1

## CPC

- G06Q 40/03: Credit; Loans; Processing thereof
- H04M 15/00: Arrangements for metering, time-control or time indication {; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP}
- H04M 15/68: {Payment of value-added services}
- H04M 15/8083: {involving reduced rates or discounts, e.g. time-of-day reductions or volume discounts}
- H04W 4/24: Accounting or billing
- H04M 2215/0192: Sponsored, subsidised calls via advertising, e.g. calling cards with ads or connecting to special ads, free calling time by purchasing goods
- G06Q: INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- H04M: TELEPHONIC COMMUNICATION (circuits for controlling other apparatus via a telephone cable and not involving telephone switching apparatus G08)
- H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72)

## Abstract

There is provided a method for use by a wireless end-user device. The method includes sending device information embedded in a web browser request, the device information indicating a central billing option is available to compatible transaction servers, in response to sending the device information embedded in the web browser request, receiving a confirmation request, performing a compatibility confirmation process based on the confirmation request for confirming compatibility of the transaction server, after the compatibility confirmation process confirms compatibility of the transaction server, receiving a purchase selection from a user, and sending the purchase selection, in response to sending the purchase selection, receiving a user purchase confirmation request from the transaction server, in response to receiving the user purchase confirmation request, requesting a purchase confirmation from the user, and in response to receiving the purchase confirmation from the user, confirming the purchase selection with the transaction server.

## Claims

### Claim at position 1

1-40. (canceled)

### Claim 41

A method for use by a wireless end-user device having an application and a mobile payment agent, the method comprising:
sending, to a transaction server over a wireless network, device information embedded in a web browser request, the device information indicating a central billing option is available to compatible transaction servers;
in response to sending the device information embedded in the web browser request, receiving, using the mobile payment agent from the transaction server over the wireless network, a confirmation request;
performing, using the mobile payment agent, a compatibility confirmation process based on the confirmation request for confirming compatibility of the transaction server;
after the compatibility confirmation process confirms compatibility of the transaction server, receiving a purchase selection from a user of the application of the wireless end-user device;
sending, using the application over the wireless network, the purchase selection to the transaction server;
in response to sending the purchase selection to the transaction server, receiving, using the mobile payment agent over the wireless network, a user purchase confirmation request from the transaction server;
in response to receiving the user purchase confirmation request, requesting, using the mobile payment agent, a purchase confirmation from the user of the application; and
in response to receiving the purchase confirmation from the user of the application, confirming, using the mobile payment agent over the wireless network, the purchase selection with the transaction server.

### Claim 42 (depends on 41)

The method of claim 41, wherein the application is one of a plurality of applications on the wireless end-user device.

### Claim 43 (depends on 41)

The method of claim 41, wherein the web browser request is an HTTP request or a WAP request.

### Claim 44 (depends on 41)

The method of claim 41, wherein the compatibility confirmation process comprises checking a signature of the confirmation request received from the transaction server against a list of compatible transaction servers.

### Claim 45 (depends on 41)

The method of claim 41, wherein the compatibility confirmation process comprises forwarding a signature of the confirmation request received from the transaction server to a billing server for confirmation.

### Claim 46 (depends on 41)

The method of claim 41, wherein the user is required to provide at least one of a password, a key, or a biometric for the purchase confirmation.

### Claim 47 (depends on 41)

The method of claim 41, further comprising:
in response to receiving the user purchase confirmation request, confirming, using the mobile payment agent, that a user account of the user has a sufficient credit limit to perform the purchase selection.

### Claim 48 (depends on 47)

The method of claim 47, wherein confirming that the user account has the sufficient credit limit comprises one of checking a stored credit limit stored in the wireless end-user device or querying a billing server.

### Claim 49

A wireless end-user device comprising:
an application; and
a mobile payment agent;
wherein the wireless end-user device is configured to:
send, to a transaction server over a wireless network, device information embedded in a web browser request, the device information indicating a central billing option is available to compatible transaction servers;
in response to sending the device information embedded in the web browser request, receive, using the mobile payment agent from the transaction server over the wireless network, a confirmation request;
perform, using the mobile payment agent, a compatibility confirmation process based on the confirmation request for confirming compatibility of the transaction server;
after the compatibility confirmation process confirms compatibility of the transaction server, receive a purchase selection from a user of the application of the wireless end-user device;
send, using the application over the wireless network, the purchase selection to the transaction server;
in response to sending the purchase selection to the transaction server, receive, using the mobile payment agent over the wireless network, a user purchase confirmation request from the transaction server;
in response to receiving the user purchase confirmation request, request, using the mobile payment agent, a purchase confirmation from the user of the application; and
in response to receiving the purchase confirmation from the user of the application, confirm, using the mobile payment agent over the wireless network, the purchase selection with the transaction server.

### Claim 50 (depends on 49)

The wireless end-user device of claim 49, wherein the application is one of a plurality of applications on the wireless end-user device.

### Claim 51 (depends on 49)

The wireless end-user device of claim 49, wherein the web browser request is an HTTP request or a WAP request.

### Claim 52 (depends on 49)

The wireless end-user device of claim 49, wherein the compatibility confirmation process comprises checking a signature of the confirmation request received from the transaction server against a list of compatible transaction servers.

### Claim 53 (depends on 49)

The wireless end-user device of claim 49, wherein the compatibility confirmation process comprises forwarding a signature of the confirmation request received from the transaction server to a billing server for confirmation.

### Claim 54 (depends on 49)

The wireless end-user device of claim 49, wherein the user is required to provide at least one of a password, a key, or a biometric for the purchase confirmation.

### Claim 55 (depends on 49)

The wireless end-user device of claim 49, wherein the wireless end-user device is further configured to:
in response to receiving the user purchase confirmation request, confirm, using the mobile payment agent, that a user account of the user has a sufficient credit limit to perform the purchase selection.

### Claim 56 (depends on 55)

The wireless end-user device of claim 55, wherein confirming that the user account has the sufficient credit limit comprises one of checking a stored credit limit stored in the wireless end-user device or querying a billing server.

### Claim 57

A method for use by a wireless end-user device having an application and a mobile payment agent, the method comprising:
sending, to a transaction server over a wireless network, device information embedded in a web browser request, the device information indicating a central billing option is available to compatible transaction servers;
in response to sending the device information embedded in the web browser request, receiving, using the mobile payment agent from the transaction server over the wireless network, a confirmation request;
performing, using the mobile payment agent, a compatibility confirmation process based on the confirmation request for confirming compatibility of the transaction server; and
after the compatibility confirmation process confirms compatibility of the transaction server, performing, using the mobile payment agent, a purchase transaction with the transaction server.

### Claim 58 (depends on 57)

The method of claim 57, wherein the web browser request is an HTTP request or a WAP request.

### Claim 59 (depends on 57)

The method of claim 57, wherein the compatibility confirmation process comprises:
checking a signature of the confirmation request received from the transaction server against a list of compatible transaction servers; or
forwarding the signature of the confirmation request received from the transaction server to a billing server for confirmation.

### Claim 60 (depends on 57)

The method of claim 57, further comprising:
confirming, using the mobile payment agent, that a user account of the user has a sufficient credit limit to perform the purchase transaction;
wherein confirming that the user account has the sufficient credit limit comprises one of checking a stored credit limit stored in the wireless end-user device or querying a billing server.
