# US 2022/0286453 A1 · Block-chain enabled service provider system

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

- Number: US 2022/0286453 A1
- Document ID: US20220286453A1
- Status: Published application
- Kind: A1
- Application number: 17/701,544
- Filed: 2022-03-22
- Published: 2022-09-08
- Earliest claimed: 2016-12-30
- Assignees: BC Development Labs GmbH
- Applicants: BC Development Labs GmBH
- Inventors: Christoph Jentzsch; Simon Jentzsch; Stéphane Tual
- Web page: https://patentgrep.com/patent/US20220286453A1

## CPC

- H04L 63/0869: {for achieving mutual authentication (cryptographic mechanisms or cryptographic arrangements for mutual authentication H04L9/3273)}
- G06F 21/445: {by mutual authentication, e.g. between devices or programs}
- H04L 9/3239: {involving non-keyed hash functions, e.g. modification detection codes [MDCs], MD5, SHA or RIPEMD}
- H04L 9/3247: {involving digital signatures}
- H04L 63/101: {Access control lists [ACL]}
- H04L 63/126: {the source of the received data}
- G06F 2221/2147: Locking files
- H04L 9/50: {using hash chains, e.g. blockchains or hash trees}
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

A distributed ledger, e.g., blockchain, enabled operating environment includes a user device that accesses services of a service device by leveraging the decentralized blockchain. For example, a user device can lock/unlock a door (e.g., service device) by interfacing with a smart contract stored on the decentralized blockchain. The user device provides parameters, such as payment, that satisfies the variables of the smart contract such that the user device can access the service device. The service device regularly retrieves information stored in the smart contract on the decentralized blockchain. For example, the retrieved information can specify that the user device is authorized to access the service device or that the service device is to provide a service. Therefore, given the retrieved information, the service device provides the service to the user device.

## Claims

### Claim at position 1

1-20. (canceled)

### Claim 21

A method comprising:
receiving a request for a selected service;
obtaining, from the request, a user identifier; and
determining, based on the user identifier and a permission data structure associated with a service device corresponding to the selected service, whether to provide the selected service, wherein the permission data structure is maintained on a distributed ledger and comprises one or more user identifiers that have been granted access to the service device.

### Claim 22 (depends on 21)

The method of claim 21, wherein the permission data structure associated with the service device is stored locally on the service device.

### Claim 23 (depends on 21)

The method of claim 21, wherein the permission data structure is managed by a smart contract on the distributed ledger.

### Claim 24 (depends on 23)

The method of claim 23, wherein the smart contract is configured to mediate a value transfer associated with the selected service.

### Claim 25 (depends on 24)

The method of claim 24, wherein the value transfer comprises a transfer of one or more tokens.

### Claim 26 (depends on 23)

The method of claim 23, wherein the smart contract is listed in a register as being associated with the selected service.

### Claim 27 (depends on 26)

The method of claim 26, wherein the smart contract comprises a first smart contract, and wherein the register is managed by a second smart contract on the distributed ledger.

### Claim 28 (depends on 21)

The method of claim 21, wherein determining whether to provide the selected service comprises:
determining whether the user identifier is listed in the permission data structure.

### Claim 29 (depends on 21)

The method of claim 21, further comprising:
polling the distributed ledger to synchronize a local copy of the permission data structure.

### Claim 30 (depends on 21)

The method of claim 21, further comprising:
in response to determining that the selected service is to be provided, causing the service device to provide the selected service.

### Claim 31 (depends on 30)

The method of claim 30, wherein causing the service device to provide the selected service comprises:
queuing a service request on the distributed ledger.

### Claim 32 (depends on 21)

The method of claim 21, wherein the request for the selected service indicates one or more options selected from a plurality of options for the selected service.

### Claim 33 (depends on 21)

The method of claim 21, wherein the selected service comprises one or more services selected from a group comprising: access to a selected physical space, access to a selected piece of equipment, and access to a selected container.

### Claim 34 (depends on 21)

The method of claim 21, wherein the request for the selected service is received from a user device via one or more of a wireless local area network, a wireless personal area network, or a near-field communication.

### Claim 35 (depends on 34)

The method of claim 34, further comprising:
sending, to the user device, a request to poll a smart contract that manages the permission data structure on the distributed ledger,

### Claim 36 (depends on 35)

The method of claim 35, wherein the request to poll the smart contract indicates a client that is selected.

### Claim 37 (depends on 36)

The method of claim 36, further comprising:
selecting the client from a whitelist of clients, wherein the whitelist of clients stores a public key of the client.

### Claim 38 (depends on 37)

The method of claim 37, further comprising:
using the public key of the client to check a signature in a response received via the user device.

### Claim 39

A non-transitory computer readable storage medium comprising memory with instructions encoded thereon, the instructions, when executed, causing one or more processors to perform operations, the instructions comprising instructions to:
receive a request for a selected service;
obtain from the request, a user identifier; and
determine, based on the user identifier and a permission data structure associated with a service device corresponding to the selected service, whether to provide the selected service, wherein the permission data structure is maintained on a distributed ledger and comprises one or more user identifiers that have been granted access to the service device.

### Claim 40

A system comprising:
memory with instructions encoded thereon; and
one or more processors that, when executing the instructions, are caused to perform operations comprising:
receiving a request for a selected service;
obtaining, from the request, a user identifier; and
determining, based on the user identifier and a permission data structure associated with a service device corresponding to the selected service, whether to provide the selected service, wherein the permission data structure is maintained on a distributed ledger and comprises one or more user identifiers that have been granted access to the service device.
