# US 2026/0253055 A1 · 24HWS_BEI_Systemic 999 Infrastructure for Sovereign Terminal Platform

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

- Number: US 2026/0253055 A1
- Document ID: US20260253055A1
- Status: Published application
- Kind: A1
- Application number: 19/177,665
- Filed: 2025-04-14
- Published: 2026-08-27
- Earliest claimed: 2025-04-14
- Inventors: FURONG BEI
- Web page: https://patentgrep.com/patent/US20260253055A1

## CPC

- G06Q 20/3229: {Use of the SIM of a M-device as secure element}
- G06Q 20/385: {using an alias or single-use codes}
- G06Q 20/401: {Transaction verification}
- G06Q 20/4014: {Identity check for transactions}
- 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

## Abstract

A domain-resolved ReadName Token Terminal infrastructure generates a terminal endpoint from identity, system, demand, time-window, and nonce inputs and binds the endpoint to a behavioral-economic identity (BEI) anchor, terminal reference, communication endpoint, wallet endpoint, clearing endpoint, access registry, lifecycle state, and receipt reference. A switchless communication module routes messages or sessions using domain-linked sender and recipient references, behavioral context, verification fields, nonces, and validity windows without requiring a telephone number, SIM credential, or switch code as a controlling endpoint. A SIM-free authentication module validates terminal operations using domain keypairs, time signatures, behavior-time proofs, and terminal state. A wallet and clearing module authorizes payments or settlements using domain-linked credentials and machine-verifiable receipts. Cross-domain synchronization, risk isolation, lifecycle control, optional hardware attestation, metadata locking, bounded-correction interfaces, and index-output modules update BEI credential, terminal, transaction, revocation, receipt, licensing, marketplace, audit, compliance, and synchronization states across interoperable platforms.

## Claims

### Claim 1

A domain-resolved ReadName Token Terminal infrastructure system, comprising: a domain namespace backbone comprising a plurality of domain-based systems configured to support terminal endpoint references; a Dynamic Domain Generation Engine configured to generate a ReadName terminal endpoint from input fields comprising an identity reference, a system reference, a demand or context type, a time-window value, and a nonce or random seed; a ReadName Token Terminal endpoint record binding the ReadName terminal endpoint to an identity anchor, a terminal reference, a communication endpoint, a wallet endpoint, a clearing endpoint, an access registry reference, a policy version, a lifecycle state, and a receipt reference; an endpoint resolver configured to map a domain-linked reference, terminal-linked reference, wallet reference, service endpoint, marketplace endpoint, or governance endpoint to at least one communication, navigation, payment, clearing, terminal-access, receipt, or index operation; a switchless communication routing module configured to route a message or session using domain-linked sender and recipient references, a behavioral context field, a verification field, a nonce, and a validity window without requiring a telephone number, SIM credential, or switch code as a controlling endpoint; a SIM-free terminal authentication module configured to validate a terminal operation using a domain keypair, time signature, terminal identifier, behavior-time proof, nonce, validity window, and policy version; a behavior-time routing module configured to resolve a communication, navigation, payment, or access request using at least one of behavior density, time continuity, interaction diversity, route confidence, relationship state, or domain context; a wallet or clearing endpoint module configured to authorize a payment or settlement operation using a domain-linked credential and to generate a machine-verifiable receipt; a terminal access registry configured to enable, limit, suspend, revoke, or require re-verification of at least one terminal module according to an access state; and an output module configured to update at least one credential state, terminal state, transaction state, revocation state, receipt state, or index state.

### Claim 2 (depends on 1)

The system of claim 1, wherein the plurality of domain-based systems includes one or more national, regional, industry, professional, temporal, cultural, alphabetical, numerical, symbolic, service, financial, medical, educational, governance, or marketplace domain categories.

### Claim 3 (depends on 1)

The system of claim 1, wherein the Dynamic Domain Generation Engine generates the ReadName terminal endpoint using a cryptographic hash, deterministic mapping, policy-controlled mapping, or collision-resistant generation operation over at least the identity reference, system reference, demand or context type, time-window value, and nonce or random seed.

### Claim 4 (depends on 1)

The system of claim 1, wherein the ReadName Token Terminal endpoint record further comprises a domain reference, a communication route status, a wallet scope, a clearing status, a revocation state, an evidence commitment, and a validity window.

### Claim 5 (depends on 1)

The system of claim 1, wherein the switchless communication routing module routes at least one text, voice, video, service, credential, wallet, marketplace, governance, or terminal-access signal without using a phone number, SIM credential, switch code, QR identifier, or platform username as the controlling routing endpoint.

### Claim 6 (depends on 1)

The system of claim 1, wherein the SIM-free terminal authentication module validates the terminal operation by checking a domain keypair signature, a time signature, a terminal identifier, a behavior-time proof reference, a nonce, a validity window, a policy version, and a lifecycle state.

### Claim 7 (depends on 1)

The system of claim 1, further comprising an authorization software development kit configured to sign or verify at least one identity, communication, payment, navigation, minting, terminal-access, lifecycle, revocation, settlement, or receipt-retrieval operation.

### Claim 8 (depends on 1)

The system of claim 1, wherein the behavior-time routing module resolves a route or endpoint using a behavior density value, time continuity value, interaction diversity value, route confidence value, domain-node context, relationship state, trust value, relevance value, or policy state, and wherein GPS data is not required as the sole controlling route source.

### Claim 9 (depends on 1)

The system of claim 1, further comprising a cross-domain synchronization or mapping module configured to synchronize or map at least one identity state, credential state, terminal state, transaction state, revocation state, receipt state, access state, risk state, or index state across at least two domain-based systems.

### Claim 10

A computer-implemented method for generating, authenticating, routing, settling, and controlling a domain-resolved ReadName Token Terminal, comprising: receiving, by one or more processors, an identity reference, terminal reference, demand or context type, time-window value, nonce, and domain context; generating, by a Dynamic Domain Generation Engine, a ReadName terminal endpoint; binding the ReadName terminal endpoint to an identity anchor and a terminal endpoint record; generating or retrieving an endpoint record comprising at least a communication endpoint, wallet endpoint, clearing endpoint, access registry reference, lifecycle state, and receipt reference; authenticating a terminal operation using a SIM-free terminal authentication record comprising a domain keypair reference, time signature, behavior-time proof, terminal identifier, nonce, validity window, and policy version; verifying a behavior-time routing context associated with a communication, navigation, payment, settlement, terminal access, marketplace, governance, or lifecycle request; routing the request or authorizing a payment or settlement according to the verified behavior-time routing context and the endpoint record; updating at least one lifecycle state, risk state, access state, transaction state, revocation state, receipt state, or index state; generating a machine-verifiable receipt for the operation; and outputting an index update, feedback record, synchronization record, or interoperable asset-output record.

### Claim 11 (depends on 10)

The method of claim 10, wherein a payment request is authorized using a behavior-time proof and domain-linked credential instead of, or in addition to, a static QR identifier.

### Claim 12 (depends on 10)

The method of claim 10, further comprising binding a terminal event to a time-domain reference to generate at least one time-asset record, eligibility record, service credit record, settlement record, audit record, or receipt.

### Claim 13 (depends on 10)

The method of claim 10, further comprising assigning to the ReadName terminal endpoint or identity anchor a lifecycle state selected from initialized, pending, active, limited, suspended, revoked, expired, inherited, transferred, recovered, disputed, quarantined, or re-verification-required.

### Claim 14 (depends on 10)

The method of claim 10, further comprising generating a risk isolation signal in response to detecting an abnormal route, invalid nonce, duplicate credential, replay attempt, terminal compromise, payment conflict, policy conflict, expired validity window, or unauthorized transfer.

### Claim 15 (depends on 10)

The method of claim 10, wherein the machine-verifiable receipt or event metadata lock includes an event type, endpoint reference, identity anchor, terminal reference, policy version, prior state, new state, verification result, evidence commitment, time-window field, and receipt status.

### Claim 16 (depends on 10)

The method of claim 10, further comprising applying a bounded-correction or finality interface that supports at least one dispute, freeze, mask, annotation, callback, clawback, rollback, reissue, invalidate, restrict, finality, duplicate-prevention, or unauthorized-reopening-prevention state.

### Claim 17

A non-transitory computer-readable medium storing instructions that, when executed by one or more processors, cause the one or more processors to perform operations comprising: generating a ReadName terminal endpoint from an identity reference, system reference, demand or context type, time-window value, and nonce or random seed; resolving the ReadName terminal endpoint to an endpoint record comprising an identity anchor, terminal reference, communication endpoint, wallet endpoint, clearing endpoint, access registry reference, lifecycle state, and receipt reference; authenticating a terminal operation without requiring a SIM credential as the controlling identity source; verifying a behavior-time proof, nonce, validity window, and policy version associated with a communication, navigation, payment, clearing, terminal-access, lifecycle, marketplace, governance, or receipt request; routing or authorizing the request using a domain-linked endpoint reference; generating a machine-verifiable receipt; and updating a credential state, terminal state, transaction state, revocation state, access state, receipt state, or index state.

### Claim 18 (depends on 17)

The non-transitory computer-readable medium of claim 17, wherein the operations further comprise receiving or verifying an optional hardware-attestation record generated using a physical unclonable function, trusted execution environment, secure enclave, measured boot verification, root-key derivation, secure storage, or remote attestation report.

### Claim 19 (depends on 17)

The non-transitory computer-readable medium of claim 17, wherein the operations further comprise generating or updating at least one license package, transfer package, marketplace listing, audit record, asset package, valuation metadata, trust index, time index, route index, payment eligibility index, terminal reliability index, or asset valuation index.

### Claim 20 (depends on 17)

The non-transitory computer-readable medium of claim 17, wherein the operations further comprise exposing an application programming interface for at least one of ReadName initialization, endpoint lookup, SIM-free authentication, message routing, payment clearing, navigation resolution, terminal access, lifecycle update, revocation, receipt retrieval, risk isolation, index update, marketplace listing, licensing, transfer, or audit verification.
