# US 2026/0267681 A1 · Hierarchical allocation of transaction identifiers

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

- Number: US 2026/0267681 A1
- Document ID: US20260267681A1
- Status: Published application
- Kind: A1
- Application number: 19/070,588
- Filed: 2025-03-05
- Published: 2026-09-10
- Earliest claimed: 2025-03-05
- Assignees: Infineon Technologies AG
- Applicants: Infineon Technologies AG
- Inventors: Frank Hellwig
- Web page: https://patentgrep.com/patent/US20260267681A1

## CPC

- G06F 9/4818: {Priority circuits therefor}
- G06F 9/526: {Mutual exclusion algorithms}
- G06F 9/45533: {Hypervisors; Virtual machine monitors}
- G06F 9/45554: {Instruction set architectures of guest OS and hypervisor or native processor differ, e.g. Bochs or VirtualPC on PowerPC MacOS}
- G06F 9/466: {Transaction processing}
- G06F 9/468: {Specific access rights for resources, e.g. using capability register}
- G06F 9/4881: {Scheduling strategies for dispatcher, e.g. round robin, multi-level priority queues}
- G06F 9/5011: {the resources being hardware resources other than CPUs, Servers and Terminals}
- G06F 9/5027: {the resource being a machine, e.g. CPUs, Servers, Terminals}
- G06F 9/52: Program synchronisation; Mutual exclusion, e.g. by means of semaphores
- G06F 9/4401: Bootstrapping (security arrangements therefor G06F21/57)
- G06F 2209/522: Manager
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

Systems, methods, and circuitries, are provided for hierarchically allocating transaction identifiers (TIDs) in a controller. In one example, TID allocation circuitry is configured to process TID locking commands from one or more priority entities. The locking commands disable TIDs in a first set of TIDs and a disabled status of the TIDs of the first set of TIDs is locked until a next controller reset. The TID allocation circuitry is configured to then process TID enablement/disablement commands from one or more application entities, wherein each application entity is associated with an initiator. The enablement/disablement commands enable or disable one or more TIDs for use by the associated initiator subject to the constraint that the TIDs in the first set of TIDs cannot be enabled for use by an enablement command.

## Claims

### Claim 1

A controller, comprising:
at least one target module;
one or more initiators coupled to the at least one target module by an interconnect, the one or more initiators configured to generate transactions seeking access to a target module, wherein each transaction is associated with an application sub-task in execution on a respective initiator; and
transaction identifier (TID) allocation circuitry, the TID allocation circuitry configured to
process TID locking commands from one or more priority entities, wherein the locking commands disable TIDs in a first set of TIDs, wherein a disabled status of the TIDs of the first set of TIDs is locked until a next controller reset, and
process TID enablement/disablement commands from one or more application entities, wherein each application entity is associated with an initiator, further wherein the enablement/disablement commands enable or disable one or more TIDs for use by the associated initiator subject to the constraint that the TIDs in the first set of TIDs cannot be enabled for use by an enablement command.

### Claim 2 (depends on 1)

The controller of claim 1, further comprising TID assignment circuitry configured to
based on an application sub-task associated with a transaction generated by the associated initiator, append a mapped TID to the transaction; and
provide the transaction and the appended TID to the interconnect.

### Claim 3 (depends on 1)

The controller of claim 1, further comprising TID mapping circuitry configured to
process TID mapping commands from one or more mapping entities; and
based on the TID mapping commands, map respective enabled TIDs to application sub-tasks in execution on the associated initiator, wherein each TID is mapped to a type of read and/or write access in one or more of the at least one target module.

### Claim 4 (depends on 3)

The controller of claim 3, wherein respective TID mapping circuitries are implemented in respective initiators of the one or more initiators.

### Claim 5 (depends on 3)

The controller of claim 3, wherein the TID mapping circuitry is implemented external to the one or more initiators.

### Claim 6 (depends on 3)

The controller of claim 3, wherein the TID mapping circuitry is configured to reject TID mapping commands received from entities not identified as mapping entities.

### Claim 7 (depends on 1)

The controller of claim 1, wherein the TID locking commands are received during a boot phase of the controller.

### Claim 8 (depends on 1)

The controller of claim 1, wherein the TID enablement/disablement commands are received after a boot phase of the controller.

### Claim 9 (depends on 1)

The controller of claim 1, wherein the TID allocation circuitry is configured to reject TID locking commands received from entities not identified as priority entities.

### Claim 10 (depends on 1)

The controller of claim 1, wherein the TID allocation circuitry is configured to reject TID enablement/disablement commands received from entities not identified as application entities.

### Claim 11 (depends on 1)

The controller of claim 1, wherein the priority entities and the application entities are independently configured by a priority entity.

### Claim 12 (depends on 1)

The controller of claim 1, wherein respective TID allocation circuitries are implemented in respective initiators.

### Claim 13 (depends on 1)

The controller of claim 1, wherein the TID allocation circuitry is implemented external to the one or more initiators.

### Claim 14

Transaction identifier (TID) allocation circuitry, comprising
a priority entity mask that defines one or more priority entities authorized to permanently disable TIDs from a set of TIDs, wherein a TID disabled by the priority entities cannot be used by any application;
an application entity mask that defines one or more application entities authorized to enable and disable TIDs for use by an application;
a priority TID register that includes a bit corresponding to each TID in the set of TIDs, wherein the priority TID register includes a locking feature that locks a disabled status of selected bits until a next controller reset, wherein access for setting an enabled or disabled status of the bits the priority TID register is limited to entities defined in the priority entity mask; and
an application TID register that includes a bit corresponding to each TID in the set of TIDs, wherein access for setting an enabled or disabled status of the bits the application TID register is limited to entities defined in the application entity mask, further wherein bits in the application TID register corresponding to TIDs that are disabled in the priority TID register cannot be set to an enabled status.

### Claim 15 (depends on 14)

The TID allocation circuitry of claim 14, further comprising write access check circuitry configured to
process, based on the priority entity mask, TID locking commands that set bits in the priority TID register to a disabled status; and
process, based on the application entity mask and the priority TID register, enablement/disablement commands that set bits in the application TID register to an enabled or disabled status.

### Claim 16 (depends on 15)

The TID allocation circuitry of claim 15, wherein the write access check circuitry is configured to reject TID locking commands received from entities not identified as priority entities.

### Claim 17 (depends on 15)

The TID allocation circuitry of claim 15, wherein the write access check circuitry is configured to reject TID enablement/disablement commands received from entities not identified as application entities.

### Claim 18 (depends on 14)

The TID allocation circuitry or claim 14, wherein an enablement/disablement status of bits in the application TID register is locked until the next controller reset.

### Claim 19

TID mapping circuity, comprising:
a priority TID register that includes a bit corresponding to each TID in a set of TIDs, wherein the priority TID register includes a locking feature that locks a disabled status of selected bits until a next controller reset;
an application TID register that includes a bit corresponding to each TID in the set of TIDs, wherein bits in the application TID register corresponding to TIDs that are disabled in the priority TID register cannot be set to an enabled status;
a mapping entity mask that defines one or more entities authorized to map TIDs to sub-tasks of an application; and
write access check circuitry configured to
process mapping commands that map TIDs to sub-tasks of the application based on the priority TID register, the application TID register, and the mapping entity mask; and
populate one or more transaction assignment registers based on the mapping commands.

### Claim 20 (depends on 19)

The TID mapping circuitry of claim 19, wherein the write access check circuitry is configured to reject TID mapping commands received from entities not identified as mapping entities in the mapping entity mask.
