# US 11,443,326 B2 · Geo-location compliance

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

- Number: US 11,443,326 B2
- Document ID: US11443326B2
- Status: Granted
- Kind: B2
- Application number: 16/432,728
- Filed: 2019-06-05
- Published: 2020-12-10
- Granted: 2022-09-13
- Earliest claimed: 2019-06-05
- Assignees: International Business Machines Corporation
- Applicants: International Business Machines Corporation
- Inventors: Dulce B. Ponceleon; Nitin Gaur
- Web page: https://patentgrep.com/patent/US11443326B2

## CPC

- G06Q 30/018: Certifying business or products
- G06F 16/27: Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
- G06Q 2220/00: Business processing using cryptography
- 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
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

An example operation may include one or more of acquiring, by a provision server, system policy data from a system policy engine, receiving, by the provision server, jurisdiction policy parameters from a jurisdiction policy engine, selecting, by the provision server, a smart contract from a smart contract repository based on the system policy data and the jurisdiction policy parameters, mapping, by the provision server, the smart contract to a node, and provisioning the node to a blockchain network.

## Claims

### Claim 1

A provision server in a blockchain network, the provision server comprising:
a memory storing one or more instructions; and
a processor that when executing the one or more instructions is configured to, in response to a new node being added to the blockchain network:
acquire system policy data from a system policy engine,
receive jurisdiction policy parameters associated with a geographical location from a jurisdiction policy engine, the jurisdiction policy parameters defining requirements for an execution of smart contract in the geographical location,
generate a smart contract execution environment that includes the system policy data and the jurisdiction policy parameters,
select a smart contract from a smart contract repository via the smart contract execution environment,
map the smart contract to the new node, and
create a feedback loop that provides information associated with the new node to the smart contract repository.

### Claim 2 (depends on 1)

The provision server of claim 1, wherein the processor is further configured to:
receive data from the blockchain network to validate the smart contract prior to a mapping.

### Claim 3 (depends on 1)

The provision server of claim 1, wherein the processor is further configured to:
ensure that the node adheres to the jurisdiction policy parameters prior to a provisioning.

### Claim 4 (depends on 1)

The provision server of claim 1, wherein the processor is further configured to:
acquire deployment and runtime data upon execution of the smart contract.

### Claim 5 (depends on 4)

The provision server of claim 4, wherein the processor is further configured to:
use the deployment and runtime data for registration and revalidation of the node.

### Claim 6 (depends on 4)

The provision server of claim 4, wherein the processor is further configured to:
update the smart contract repository based on the runtime data.

### Claim 7 (depends on 1)

The provision server of claim 1, wherein the processor is further configured to:
validate the smart contract against the jurisdiction policy parameters upon an update of the smart contract.

### Claim 8

A method, comprising:
in response to a new node being added to the blockchain network:
acquiring, by a provision server in a blockchain network, system policy data from a system policy engine;
receiving, by the provision server, jurisdiction policy parameters associated with a geographical location from a jurisdiction policy engine, the jurisdiction policy parameters defining requirements for an execution of smart contract in the geographical location;
generating, by the provision server, a smart contract execution environment that includes the system policy data and the jurisdiction policy parameters;
selecting, by the provision server, a smart contract from a smart contract repository via the smart contract execution environment;
mapping, by the provision server, the smart contract to the new node; and
creating, by the provision server, a feedback loop providing information associated with the new node to the smart contract repository.

### Claim 9 (depends on 8)

The method of claim 8, further comprising:
receiving data from the blockchain network to validate the smart contract prior to a mapping.

### Claim 10 (depends on 9)

The method of claim 9, further comprising:
ensuring that the node adheres to the jurisdiction policy parameters prior to a provisioning.

### Claim 11 (depends on 8)

The method of claim 8, further comprising:
acquiring deployment and runtime data upon execution of the smart contract.

### Claim 12 (depends on 11)

The method of claim 11, further comprising:
using the deployment and runtime data for registration and revalidation of the node.

### Claim 13 (depends on 11)

The method of claim 11, further comprising:
updating the smart contract repository based on the runtime data.

### Claim 14 (depends on 8)

The method of claim 8, further comprising:
validating the smart contract against the jurisdiction policy parameters upon an update of the smart contract.

### Claim 15

A non-transitory computer readable medium comprising one or more instructions that when executed by a processor of a provision server in a blockchain network configure the processor to perform, in response to a new node being added to the blockchain network:
acquiring system policy data from a system policy engine;
receiving jurisdiction policy parameters associated with a geographical location from a jurisdiction policy engine, the jurisdiction policy parameters defining requirements for an execution of smart contract in the geographical location;
generating a smart contract execution environment that includes the system policy data and the jurisdiction policy parameters;
selecting a smart contract from a smart contract repository via the smart contract execution environment;
mapping the smart contract to the new node; and
creating a feedback loop that providing information associated with the new node to the smart contract repository.

### Claim 16 (depends on 15)

The non-transitory computer readable medium of claim 15, wherein the one or more instruction further configure the processor to perform:
receiving data from the blockchain network to validate the smart contract prior to a mapping.

### Claim 17 (depends on 15)

The non-transitory computer readable medium of claim 15, wherein the one or more instruction further configure the processor to perform:
ensuring that the node adheres to the jurisdiction policy parameters prior to a provisioning.

### Claim 18 (depends on 15)

The non-transitory computer readable medium of claim 15, wherein the one or more instruction further configure the processor to perform:
acquiring deployment and runtime data upon execution of the smart contract.

### Claim 19 (depends on 18)

The non-transitory computer readable medium of claim 18, wherein the one or more instruction further configure the processor to perform:
using the deployment and runtime data for registration and revalidation of the node.

### Claim 20 (depends on 19)

The non-transitory computer readable medium of claim 19, wherein the one or more instruction further configure the processor to perform:
updating the smart contract repository based on the runtime data.
