patent.fyi
Applications  /  US 2026/0355637
United States Patent Application Publication

US 2026/0355637 A1

Published
Nov 12, 2026
Filed
Nov 14, 2023
Earliest date on the face
Nov 18, 2022
Classification
A63F 13/79
First published here
Nov 19, 2026

Generated automatically. Not reviewed by a person. Not legal advice or an opinion.

Section 1 · machine-generated

What if?

Questions about how individual parts of claim 1 might be changed. A question may describe something different from what the claim language recites, or a version of it; no view is offered on which.

1.1Direct manipulation of game state

What ifWhat if the player interface writes object positions directly into editable game state?
Claim language“in-game action requests”

In a private building session, dragging an object updates its coordinates in a shared scene buffer. A fixed-rate simulation loop reads committed positions from the buffer and recalculates collisions and support constraints.

1.2Database polling for ownership changes

What ifWhat if the game server updates persistent state and an ownership worker polls that state?
Claim language“relay a plurality of messages”

The game server applies each completed trade in a database transaction that updates the asset's owner and increments its revision counter. An ownership worker reads changed rows through a revision index and records the latest owner for each asset.

1.3Local hardware filters game events

What ifWhat if an on-premises programmable logic board selects ownership events for replication?
Claim language“a cloud processor”

The game server sends fixed-length event frames over a dedicated wired link to a board in the same equipment rack. The board compares each frame's event code with a hardware lookup table and forwards matching frames to the ledger endpoint.

1.3Live reads from authoritative storage

What ifWhat if ownership consumers read current asset records directly from the authoritative database?
Claim language“which, if any, of the plurality of messages should be replicated”

The game server commits inventory changes to an ownership table keyed by asset identifier. Inventory screens and trade services query the table through a read endpoint whenever they need the current owner.

1.4Relational ownership with row locking

What ifWhat if asset ownership is recorded in a relational database with transactional row locking?
Claim language“using blockchain”

An ownership service locks the row for the asset and checks that its recorded owner matches the sender. The same transaction sets the recipient as the new owner and inserts a transfer-history row with a unique transaction identifier.

Section 2 · machine-generated

Variations

Further arrangements of the same subject matter, described here as of the publication date at the foot of this page.

Other field of use

Equipment transfers between repair depots

A depot terminal sends equipment transfer requests to an inventory server after an operator scans a serialized equipment tag. The server records the pending transfer and relays a message containing the equipment identifier, source depot, destination depot, and transfer identifier to a replication processor. The processor forwards the message to the blockchain server when the receiving depot confirms receipt using the same transfer identifier. The blockchain server checks the recorded source depot, updates the owner, and returns the committed record identifier to the inventory server.

Component substitution

Ownership records in a relational database

A player interface sends action requests to a game server, which relays action messages to a cloud processor that selects ownership changes for replication. A replicated relational database replaces the blockchain server and stores a current ownership table and an append-only transfer table. For each selected message, a serializable transaction checks the expected owner and record version, updates the ownership row, and inserts a transfer row. A unique constraint on the action identifier makes retries return the stored result without applying the transfer again.

Parameter or scale variation

Bounded batches for ownership updates

Game servers relay player action messages to a cloud processor that selects ownership changes and assigns them to 16 queues by asset identifier. Each queue flushes when it contains 128 changes or when its oldest change has waited 250 milliseconds. The processor submits each batch to the blockchain server in queue order and waits for a commit result before sending the next batch from that queue. The blockchain server applies version checks per asset, records accepted action identifiers, and returns a result for each change.

Combination with existing systems

Marketplace settlement with payment escrow

A player submits a purchase through the game marketplace, and the game server relays the purchase identifier, asset identifier, and buyer and seller identifiers to the cloud processor. The processor correlates the purchase with a funds-held event from a payment escrow system before forwarding the transfer to the blockchain server. The blockchain server checks the current owner, updates the ownership record, and returns a commit receipt tied to the purchase identifier. The escrow system releases funds to the seller on a committed transfer and releases the hold back to the buyer on a definitive rejection.

Automated or data-driven variant

Automatic retry of unconfirmed transfers

The game server relays player actions to a cloud processor that stores each selected ownership change in a durable queue with a unique action identifier and a submission timestamp. A scheduled worker queries the blockchain server for changes that have lacked a commit receipt for 30 seconds. The worker stores any receipt it finds, resubmits changes with no recorded result, and sends definitive rejections to the game server for resolution. The blockchain server processes a repeated action identifier by returning its recorded result without changing ownership a second time.

Ownership checkpoints at match completion

The game server relays asset transfer messages tagged with a match identifier and a sequence number to the cloud processor. At match completion, the game server sends a closing message containing the final sequence number and the ownership versions used at match start. The processor checks for missing messages, replays the transfers in sequence, and forwards the final owner and expected starting version for each asset whose owner changed. The blockchain server checks all expected versions and commits the checkpoint atomically, or returns the conflicting asset identifiers to the game server.

Specific version of a part

Ownership derived from immutable transfers

The server appends a signed transfer event containing an asset identifier, a recipient identifier and a sequence number. For each ownership query, an index locates the highest committed sequence number for that asset, and the server returns the recipient from that event.

Sequenced controller action requests

The player interface converts controller button presses into action requests carrying an action code, a session identifier and a sequence number. It groups requests into frames at a 60 Hz input sampling rate.

Server relay with durable queue

The game server receives action requests over a persistent connection and writes corresponding messages to a durable queue. Each message carries the original request identifier, the action type and the game tick at which the server receives it.

Cloud filtering by action type

A cloud worker consumes messages from the game server and checks each action code against a configured table. Trade completion and item grants enter the replication queue, while movement and camera actions pass through the worker without replication.

Blockchain updates with revision checks

A blockchain server receives replicated transfer messages and submits transactions containing the asset identifier, the recipient and the expected ownership revision. Ledger code checks the revision before it writes the new owner and increments the revision.

Section 3 · quoted from USPTO records

Other work

Passages reproduced word for word from two earlier-published U.S. patent documents, placed beside the language of claim 1. No characterization is offered. Each passage is marked A or B for the document it comes from; ¶ numbers are the paragraph numbers in the USPTO’s published full text of that document.

Document AUS 8,312,514 B2
Published
Nov 13, 2012
Filed
Oct 4, 2010
Class
H04L 29/06
Document BUS 2016/0236098 A1
Published
Aug 18, 2016
Filed
Jan 18, 2016
Class
A63F 13/87
Claim 1
Document A
Document B
1.1a player interface for receiving a plurality of in-game action requests from a player using a gaming system;
In a preferred embodiment, the control center automatically displays a list of different courses of actions. Alternatively, the owner could activate such a menu by interacting with the user interface of the control center.
A · US 8,312,514 B2 · ¶ 37
To enable in-game chat functionality, each of the game clients 107 is provided with in-game chat client 108, which is configured to exchange data, including, without limitation, chat messages, with the chat server in-game frontend 103.
B · US 2016/0236098 A1 · ¶ 43
1.2a game server in communication with the player interface for receiving the plurality of in-game action requests and configured to relay a plurality of messages corresponding to the plurality of in-game action requests;
The user selects an action from the network 12 to remove ownership information from the device 14 (step 300). The server 16 initiates the ownership revoking process by initiating a revocation transaction with the device 14 by sending a release command using a secure after access both ways has been established as described above.
A · US 8,312,514 B2 · ¶ 60
At step 203, a communication between the frontends 103, 104, 105 and 106 of the chat server 101 and the chat clients 108, 110, 111 and 112 is established to enable the exchange of messages between the aforesaid chat clients and/or chat clients and social interaction modules 113, 114 and 115, see step 204.
B · US 2016/0236098 A1 · ¶ 50
1.3a cloud processor configured to receive the plurality of messages corresponding to the plurality of an in-game action requests and determined which, if any, of the plurality of messages should be replicated; and
1.4a blockchain server configured to receive any of the plurality of the messages that are replicated and to update a record reflecting ownership of an asset using blockchain based on any of the plurality of the messages.
In this case, the ownership record may be updated as it travels through various channels to an end user, such as a distributor and retail store.
A · US 8,312,514 B2 · ¶ 24

An empty cell means only that no passage was reproduced there.

Statements in these documents
Accordingly, there is a need for a method and system for implementing and transferring device ownership in network devices in a manner that provides a barrier to device theft.
A · US 8,312,514 B2 · ¶ 7
The ownership record is then transmitted from the network to the device, and automatic access to the device is granted to the network once the device verifies the transmitted ownership record against the ownership record stored in the device.
A · US 8,312,514 B2 · ¶ 8
Therefore, new and improved systems and methods for implementing in-game chat are needed that would enable game players to communicate by way of in-game chat using other communication software applications or with users not involved in the active game session.
B · US 2016/0236098 A1 · ¶ 6
In one or more embodiments, the plurality of frontends comprises a web frontend, the plurality of chat clients comprises a web chat client, and wherein the web frontend is configured to communicate with the web chat client via an HTTP protocol.
B · US 2016/0236098 A1 · ¶ 9
Cite aspatent.fyi, US 2026/0355637 A1, claim 1, first published 2026-11-19T13:37:15-05:00, https://patent.fyi/US20260355637/, SHA-256 656b9215da4cc5fe13770eeec56cac9cfc1b012407ccd66288d5cf8c45a3900a
First published
Permanent addresshttps://patent.fyi/US20260355637/
Content fingerprint (SHA-256)656b9215da4cc5fe13770eeec56cac9cfc1b012407ccd66288d5cf8c45a3900a
Methodv2026-11-18.2 · automated, not reviewed by a person
Correctionscorrections@patent.fyi