# US 2016/0253371 A1 · Accessing data entities

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

- Number: US 2016/0253371 A1
- Document ID: US20160253371A1
- Status: Published application
- Kind: A1
- Application number: 15/149,170
- Filed: 2016-05-08
- Published: 2016-09-01
- Earliest claimed: 2007-08-30
- Assignees: International Business Machines Corporation
- Applicants: International Business Machines Corporation
- Inventors: FRANK NEUMANN; GERHARD PFAU
- Web page: https://patentgrep.com/patent/US20160253371A1

## CPC

- G06F 16/2343: {Locking methods, e.g. distributed locking or locking implementation details}
- G06F 16/23: Updating
- G06F 16/2329: {using versioning}
- G06F 16/24552: {Database cache management}
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

Data entities in a client-server system are accessed. The client-server system comprises a set of clients, a server system, and a repository for storing a plurality of data entities. The server system comprises an inter-transactional cache, the inter-transactional cache being accessible for each client of the set of clients. A first client of the set of clients comprises a first intra-transactional cache. If a copy of a first data entity is in the inter-transactional cache, a version identifier of the original first data entity is read from the repository. If the copy of the first data entity is to be accessed with an exclusive lock, a copy of the copy of the first data entity is added to the first intra-transactional cache. The copy of the copy of the first data entity in the first intra-transactional cache is accessed for further processing of the first data entity by the first client.

## Claims

### Claim at position 1

-17. (canceled)

### Claim 18

A method, within an application server, of modifying an intra-transactional cache, comprising:
determining whether a copy of an original first data entity, accessed in the intra-transactional cache by a first client, has been updated;
determining whether the copy is also within an inter-transactional cache;
adding, upon the copy not being within the inter-transactional cache, the copy to the inter-transactional cache; and
removing, after the copy has been added to the inter-transactional cache, the copy from the intra-transactional cache, the copy.

### Claim 19 (depends on 18)

The method of claim 18, further comprising:
removing, from a data entry list for the copy within the intra-transactional cache, a client ID and lock entry.

### Claim 20 (depends on 18)

The method of claim 18, wherein
both the intra-transactional cache and the inter-transactional cache are accessible by the application server.

### Claim 21 (depends on 18)

The method of claim 18, wherein
both the intra-transactional cache and the inter-transactional cache are within the application server.

### Claim 22

A method, within an application server, of modifying an intra-transactional cache, comprising:
determining whether a copy of an original first data entity, accessed in the intra-transactional cache by a first client, has been updated;
determining whether the copy is also within an inter-transactional cache;
determining, upon a determination that the copy is within the inter-transactional cache, whether a lock exists for the copy within the inter-transactional cache; and
removing, from the intra-transactional cache, the copy.

### Claim 23 (depends on 22)

The method of claim 22, further comprising:
upon a determination that no lock exists for the copy within the inter-transactional cache, updating the copy within the inter-transactional cache.

### Claim 24 (depends on 22)

The method of claim 22, wherein
both the intra-transactional cache and the inter-transactional cache are accessible by the application server.

### Claim 25 (depends on 22)

The method of claim 22, further comprising:
removing, from a data entry list for the copy within the intra-transactional cache, a client ID and lock entry.

### Claim 26

A computer program product, comprising:
a computer usable storage device having stored therein computer usable program code for modifying an intra-transactional cache,
the computer usable program code, which when executed by an application server, causes the application server to perform:
determining whether a copy of an original first data entity, accessed in the intra-transactional cache by a first client, has been updated;
determining whether the copy is also within an inter-transactional cache;
adding, upon the copy not being within the inter-transactional cache, the copy to the inter-transactional cache; and
removing, after the copy has been added to the inter-transactional cache, the copy from the intra-transactional cache.

### Claim 27 (depends on 26)

The computer program product of claim 26, wherein the computer usable program code further causes the application server to perform:
removing, from a data entry list for the copy within the intra-transactional cache, a client ID and lock entry.

### Claim 28 (depends on 26)

The computer program product of claim 26, wherein
both the intra-transactional cache and the inter-transactional cache are accessible by the application server.

### Claim 29 (depends on 26)

The computer program product of claim 26, wherein
both the intra-transactional cache and the inter-transactional cache are within the application server.

### Claim 30

A computer program product, comprising:
a computer usable storage device having stored therein computer usable program code for modifying an intra-transactional cache,
the computer usable program code, which when executed by an application server, causes the application server to perform:
determining whether a copy of an original first data entity, accessed in the intra-transactional cache by a first client, has been updated;
determining whether the copy is also within an inter-transactional cache;
determining, upon a determination that the copy is within the inter-transactional cache, whether a lock exists for the copy within the inter-transactional cache; and
removing, from the intra-transactional cache, the copy.

### Claim 31 (depends on 30)

The computer program product of claim 30, wherein the computer usable program code further causes the application server to perform:
upon a determination that no lock exists for the copy within the inter-transactional cache, updating the copy within the inter-transactional cache.

### Claim 32 (depends on 30)

The computer program product of claim 30, wherein
both the intra-transactional cache and the inter-transactional cache are accessible by the application server.

### Claim 33 (depends on 30)

The computer program product of claim 30, wherein the computer usable program code further causes the application server to perform:
removing, from a data entry list for the copy within the intra-transactional cache, a client ID and lock entry.
