# US 12,217,197 B2 · Transaction-enabled systems and methods for transaction execution with licensing smart wrappers

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

- Number: US 12,217,197 B2
- Document ID: US12217197B2
- Status: Granted
- Kind: B2
- Application number: 16/692,655
- Filed: 2019-11-22
- Published: 2020-04-09
- Granted: 2025-02-04
- Earliest claimed: 2018-05-06
- Assignees: Strong Force TX Portfolio 2018, LLC
- Applicants: Strong Force TX Portfolio 2018, LLC
- Inventors: Charles Howard Cella
- Web page: https://patentgrep.com/patent/US12217197B2

## CPC

- G06Q 10/04: Forecasting or optimisation specially adapted for administrative or management purposes, e.g. linear programming or "cutting stock problem" (market predictions or forecasting for commercial activities G06Q30/0202)
- G05B 19/00: Program-control systems
- G05B 19/41865: {characterised by job scheduling, process planning, material flow}
- G05B 19/4188: {characterised by CIM planning or realisation}
- G06F 9/3836: {Instruction issuing, e.g. dynamic instruction scheduling or out of order instruction execution}
- G06F 9/3891: {organised in groups of units sharing resources, e.g. clusters}
- G06F 9/466: {Transaction processing}
- G06F 9/4806: {Task transfer initiation or dispatching}
- G06F 9/4881: {Scheduling strategies for dispatcher, e.g. round robin, multi-level priority queues}
- G06F 9/50: Allocation of resources, e.g. of the central processing unit [CPU]
- G06F 9/5005: {to service a request}
- G06F 9/5016: {the resource being the memory}
- G06F 9/5027: {the resource being a machine, e.g. CPUs, Servers, Terminals}
- G06F 9/5072: {Grid computing}
- G06F 9/541: {via adapters, e.g. between incompatible applications}
- G06F 16/182: Distributed file systems
- G06F 16/1865: {Transactional file systems}
- G06F 16/23: Updating
- G06F 16/2365: {Ensuring data consistency and integrity}
- G06F 16/2379: {Updates performed during online database operations; commit processing}
- G06F 16/24: Querying
- G06F 16/27: Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
- G06F 16/951: Indexing; Web crawling techniques
- G06F 18/2148: {characterised by the process organisation or structure, e.g. boosting cascade}
- G06F 18/2155: {characterised by the incorporation of unlabelled data, e.g. multiple instance learning [MIL], semi-supervised techniques using expectation-maximisation [EM] or naïve labelling}
- G06F 21/105: {Arrangements for software license management or administration, e.g. for managing licenses at corporate level}
- G06F 21/602: {Providing cryptographic facilities or services}
- G06F 30/27: using machine learning, e.g. artificial intelligence, neural networks, support vector machines [SVM] or training a model
- G06N 3/02: Neural networks
- G06N 3/042: Knowledge-based neural networks; Logical representations of neural networks
- G06N 3/043: based on fuzzy logic, fuzzy membership or fuzzy inference, e.g. adaptive neuro-fuzzy inference systems [ANFIS]
- G06N 3/044: Recurrent networks, e.g. Hopfield networks
- G06N 3/0442: characterised by memory or gating, e.g. long short-term memory [LSTM] or gated recurrent units [GRU]
- G06N 3/0455: Auto-encoder networks; Encoder-decoder networks
- G06N 3/0464: Convolutional networks [CNN, ConvNet]
- G06N 3/0475: Generative networks
- G06N 3/0495: Quantised networks; Sparse networks; Compressed networks
- G06N 3/08: Learning methods
- G06N 3/084: Backpropagation, e.g. using gradient descent
- G06N 3/088: Non-supervised learning, e.g. competitive learning
- G06N 3/09: Supervised learning
- G06N 3/094: Adversarial learning
- G06N 5/04: Inference or reasoning models
- G06N 20/00: Machine learning
- G06Q 10/0631: Resource planning, allocation, distributing or scheduling for enterprises or organisations
- G06Q 10/06314: {Calendaring for a resource}
- G06Q 10/06315: {Needs-based resource requirements planning or analysis}
- G06Q 10/067: Enterprise or organisation modelling
- G06Q 20/06: Private payment circuits, e.g. involving electronic currency used among participants of a common payment scheme
- G06Q 20/065: {using e-cash}
- G06Q 20/0655: {e-cash managed centrally}
- G06Q 20/0855: {involving a third party}
- G06Q 20/12: specially adapted for electronic shopping systems
- G06Q 20/123: {Shopping for digital content}
- G06Q 20/145: {Payments according to the detected use or quantity}
- G06Q 20/29: {characterised by micropayments}
- G06Q 20/308: {using the Internet of Things}
- G06Q 20/367: {involving electronic purses or money safes}
- G06Q 20/38215: {Use of certificates or encrypted proofs of transaction rights}
- G06Q 20/384: {using social networks}
- G06Q 20/389: {Keeping log of transactions for guaranteeing non-repudiation of a transaction}
- G06Q 20/4016: {involving fraud or risk level assessment in transaction processing}
- G06Q 20/405: {Establishing or using transaction specific rules}
- G06Q 30/0201: Market modelling; Market analysis; Collecting market data
- G06Q 30/0202: Market predictions or forecasting for commercial activities
- G06Q 30/0205: {based on location or geographical consideration}
- G06Q 30/0206: {Price or cost determination based on market factors}
- G06Q 30/0247: {Calculate past, present or future revenues}
- G06Q 30/0273: Determination of fees for advertising
- G06Q 30/06: Buying, selling or leasing transactions
- G06Q 40/04: Trading; Exchange, e.g. stocks, commodities, derivatives or currency exchange
- G06Q 40/10: Tax strategies
- G06Q 50/04: Manufacturing
- G06Q 50/06: Energy or water supply
- G06Q 50/184: {Intellectual property management}
- H02J 3/008: Circuit arrangements for power supply or distribution technologies responsive to energy trading
- H02J 3/14: by switching loads on to, or off from, the networks, e.g. progressively balanced loading
- H02J 3/28: Arrangements for balancing of the load in networks by storage of energy
- H02J 3/388: Arrangements for the handling of islanding, e.g. for disconnection or for avoiding the disconnection of power
- H04L 9/3239: {involving non-keyed hash functions, e.g. modification detection codes [MDCs], MD5, SHA or RIPEMD}
- H04L 9/50: {using hash chains, e.g. blockchains or hash trees}
- H04L 12/14: Charging, metering or billing arrangements specially adapted for data communications, e.g. authentication, authorisation and accounting [AAA] framework
- H04L 47/783: Distributed allocation of resources, e.g. bandwidth brokers
- H04L 47/788: {Autonomous allocation of resources}
- H04L 47/83: based on usage prediction
- G05B 2219/36542: Cryptography, encrypt, access, authorize with key, code, password
- G06F 9/3838: {Dependency mechanisms, e.g. register scoreboarding}
- G06F 16/2457: with adaptation to user needs
- G06N 3/0418: {using chaos or fractal principles}
- G06N 3/048: Activation functions
- G06N 5/01: Dynamic search techniques; Heuristics; Dynamic trees; Branch-and-bound
- G06N 5/022: Knowledge engineering; Knowledge acquisition
- G06N 5/046: Forward inferencing; Production systems
- G06Q 10/40: Business processes related to social networking or social networking services
- G06Q 20/4015: {using location information}
- G06Q 30/0254: {based on statistics}
- G06Q 30/0276: {Advertisement creation}
- G06Q 2220/00: Business processing using cryptography
- G06Q 2220/12: Usage or charge determination
- G06Q 2220/18: Licensing
- H02J 3/003: {Load forecast, e.g. methods or systems for forecasting future load demand}
- H04L 9/0643: {Hash functions, e.g. MD5, SHA, HMAC or f9 MAC}
- H04L 67/10: in which an application is distributed across nodes in the network (software deployment G06F8/60; multiprogramming arrangements G06F9/46)
- H04L 67/12: specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
- H04L 67/34: {involving the movement of software or configuration parameters (network booting or remote initial program loading [RIPL] G06F9/4416)}
- Y02B 70/3225: Demand response systems, e.g. load shedding, peak shaving
- Y02D 10/00: Energy efficient computing, e.g. low power processors, power management or thermal management
- Y02P 90/02: Total factory control, e.g. smart factories, flexible manufacturing systems [FMS] or integrated manufacturing systems [IMS]
- Y02P 90/845: Inventory and reporting systems for greenhouse gases [GHG]
- Y04S 10/50: Systems or methods supporting the power network operation or management, involving a certain degree of interaction with the load-side end user applications
- Y04S 20/222: Demand response systems, e.g. load shedding, peak shaving
- Y04S 40/20: Information technology specific aspects, e.g. CAD, simulation, modelling, system security
- Y04S 50/10: Energy trading, including energy flowing from end-user application to grid
- Y04S 50/12: Billing, invoicing, buying or selling transactions or other related activities, e.g. cost or usage evaluation
- Y04S 50/14: Marketing, i.e. market research and analysis, surveying, promotions, advertising, buyer profiling, customer management or rewards
- 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
- G05B: CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS (systems for controlling or regulating non-electric variables G05D; systems for regulating electric or magnetic variables G05F; control devices or systems insofar as characterised by mechanical features only G05G)
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- G06N: COMPUTING ARRANGEMENTS BASED ON SPECIFIC COMPUTATIONAL MODELS
- H02J: ELECTRIC POWER NETWORKS; CIRCUIT ARRANGEMENTS OR SYSTEMS FOR SUPPLYING OR DISTRIBUTING ELECTRIC POWER; SYSTEMS FOR STORING ELECTRIC ENERGY
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- Y02B: CLIMATE CHANGE MITIGATION TECHNOLOGIES RELATED TO BUILDINGS, e.g. HOUSING, HOUSE APPLIANCES OR RELATED END-USER APPLICATIONS
- Y02D: CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02P: CLIMATE CHANGE MITIGATION TECHNOLOGIES IN THE PRODUCTION OR PROCESSING OF GOODS
- Y04S: SYSTEMS INTEGRATING TECHNOLOGIES RELATED TO POWER NETWORK OPERATION, COMMUNICATION OR INFORMATION TECHNOLOGIES FOR IMPROVING THE ELECTRICAL POWER GENERATION, TRANSMISSION, DISTRIBUTION, MANAGEMENT OR USAGE, i.e. SMART GRIDS

## Abstract

Transaction-enabled systems and methods for transaction execution with licensing smart wrappers are disclosed. An example system may include a smart contract wrapper configured to access a distributed ledger comprising a plurality of IP licensing terms for a plurality of IP assets comprising an aggregate stack of IP. The smart contract wrapper may be further configured to interpret an IP description value and an IP addition request and, in response to the request and IP description value, to add an IP asset to the aggregate stack of IP. A transaction execution circuit provides a transaction implementation command in response to at least one of a transaction geographic value or a transaction jurisdiction value.

## Claims

### Claim 1

A method, comprising:
accessing, by a smart wrapper, a distributed ledger comprising a plurality of intellectual property (IP) licensing terms corresponding to a plurality of IP assets, the plurality of IP assets comprising an aggregate stack of IP, the aggregate stack of IP including at least one instance of executable instructions and at least one identifier for a patent, the executable instructions being added to the aggregate stack of IP by a contributing entity, wherein the executable instructions are one of the plurality of IP assets,
wherein the executable instructions are digital and provide executable steps for producing a physical object, and wherein the executable steps include steps for at least one of: a coating process, a 3D printing process, a semiconductor fabrication process, a food preparation process, a polymer production process, a chemical synthesis process, a biological production process, or a crystal fabrication process;
the executable instructions of the one of the plurality of IP assets being added to the aggregate stack of IP by:
storing the executable instructions in an IP asset data store separate from and in communication with the distributed ledger over a network infrastructure, the IP asset data store including a non-transitory computer-readable storage medium; and
storing, on the distributed ledger, a pointer referencing a location of the executable instructions in the IP asset data store;
receiving, from a first party via a web-based user interface provided by the smart wrapper, verification information of the first party, an IP description value and an IP addition request for updating the one of the plurality of IP assets with updated executable instructions;
verifying an authorization of the first party based on the verification information, the verification information including information obtained via a login interface of the web-based user interface and an internet protocol address of the first party, wherein the first party provides the information to the login interface over the network infrastructure via a remote mobile device;
in response to the authorization, the IP addition request, and the IP description value, the smart wrapper updating the IP asset on the aggregate stack of IP and storing the updated IP asset by:
storing, in the IP asset data store separate from and in communication with the distributed ledger, underlying data of the updated IP asset including the updated executable instructions; and
updating, on the distributed ledger, the pointer to reference the location of the updated executable instructions stored in the IP asset data store,
wherein distributed memory locations of the distributed ledger agree on a consistency of the updated pointer on the distributed ledger to thereby create an updated version of the distributed ledger;
receiving access requests and royalty payments to access the updated executable instructions by respective parties;
executing an operation, responsive to receiving one of the access requests, to commit one of the respective parties to at least one of the plurality of IP licensing terms corresponding to the one of the IP assets including the updated executable instructions via the distributed ledger, whereby the one of the respective parties is provided with access to the updated executable instructions in accordance with the at least one of the plurality of IP licensing terms;
providing access to the updated executable instructions to the one of the respective parties by providing an interface description for the updated executable instructions, the interface description including an application programming interface (API) for accessing the updated executable instructions, wherein the access is restricted according to a scope of use defined by the at least one of the plurality of IP licensing terms, the scope of use including at least one of a time frame for using the updated executable instructions or a volume of use of the updated executable instructions;
recording on the distributed ledger, by the smart wrapper, access information of the one of the respective parties based on providing the one of the respective parties with access to the updated executable instructions in accordance with the at least one of the plurality of IP licensing terms, wherein the access information includes at least one of a username, an e-mail address, an internet protocol address, a geographic location, a time stamp, or which portion of the updated executable instructions are available for access by the one of the respective parties;
interpreting a transaction request provided by a party requesting access to the updated executable instructions in exchange for a royalty, the royalty being provided as a cryptocurrency, the transaction request indicating a cryptocurrency type and an amount of the cryptocurrency,
wherein the party provides the transaction request to the smart wrapper via the web-based user interface provided by the smart wrapper to the party,
the smart wrapper is included with a controller, and
the smart wrapper provides a consistent web-based user interface to the party for receiving the transaction request from the party such that changes to the controller are invisible to the party;
determining a transaction location parameter corresponding to the transaction request, the transaction location parameter comprising at least one of a transaction geographic value or a transaction jurisdiction value; and
providing, by the smart wrapper, a transaction implementation command for the one of the plurality of IP assets in response to the transaction location parameter and the IP licensing terms, the transaction implementation command indicating a geographical location of a server on which to execute a transaction corresponding to the transaction request.

### Claim 2 (depends on 1)

The method of claim 1, further comprising interpreting transactions and storing transaction location parameter values corresponding to each of the transactions according to at least one of: transaction type, transaction amount, or entity characteristics corresponding to requesting entities for the transactions.

### Claim 3 (depends on 2)

The method of claim 2, further comprising executing transaction tasks including providing transaction implementation commands based at least in part on the transaction location parameter values.

### Claim 4 (depends on 1)

The method of claim 1, further comprising:
interpreting a plurality of transaction request values, wherein each transaction request value includes a transaction description for a proposed transaction.

### Claim 5 (depends on 4)

The method of claim 4, further comprising commanding execution of the proposed transaction.

### Claim 6 (depends on 4)

The method of claim 4, wherein the transaction description includes a cryptocurrency type value and a transaction amount value.

### Claim 7 (depends on 1)

The method of claim 1, wherein the executable instructions includes descriptions to perform a proprietary operation.

### Claim 8 (depends on 1)

The method of claim 1, further comprising:
the smart wrapper operating to provide an interface to the party for receiving the transaction request, and to provide an interface to a transaction engine for sending the transaction implementation command.

### Claim 9 (depends on 1)

The method of claim 1, wherein the distributed ledger is a blockchain, and wherein more than half of the distributed memory locations of the blockchain agree on the updated pointer.

### Claim 10

A non-transitory computer readable storage medium storing instructions that, when executed by one or more processors, comprise:
accessing, by a smart wrapper, a distributed ledger comprising a plurality of intellectual property (IP) licensing terms corresponding to a plurality of IP assets, the plurality of IP assets comprising an aggregate stack of IP, the aggregate stack of IP including at least one instance of executable instructions and at least one identifier for a patent, the executable instructions being added to the aggregate stack of IP by a contributing entity, wherein the executable instructions are one of the plurality of IP assets,
wherein the executable instructions are digital and provide executable steps for producing a physical object, and wherein the executable steps include steps for at least one of: a coating process, a 3D printing process, a semiconductor fabrication process, a food preparation process, a polymer production process, a chemical synthesis process, a biological production process, or a crystal fabrication process;
the executable instructions of the one of the plurality of IP assets being added to the aggregate stack of IP by:
storing the executable instructions in an IP asset data store separate from and in communication with the distributed ledger over a network infrastructure, the IP asset data store including a non-transitory computer-readable storage medium; and
storing, on the distributed ledger, a pointer referencing a location of the executable instructions in the IP asset data store;
receiving, from a first party via a web-based user interface provided by the smart wrapper, verification information of the first party, an IP description value and an IP addition request for updating the one of the plurality of IP assets with updated executable instructions;
verifying an authorization of the first party based on the verification information, the verification information including information obtained via a login interface of the web-based user interface and an internet protocol address of the first party, wherein the first party provides the information to the login interface over the network infrastructure via a remote mobile device;
in response to the authorization, the IP addition request, and the IP description value, the smart wrapper updating the IP asset on the aggregate stack of IP and storing the updated IP asset by:
storing, in the IP asset data store separate from and in communication with the distributed ledger, underlying data of the updated IP asset including the updated executable instructions; and
updating, on the distributed ledger, the pointer to reference the location of the updated executable instructions stored in the IP asset data store,
wherein distributed memory locations of the distributed ledger agree on a consistency of the updated pointer on the distributed ledger to thereby create an updated version of the distributed ledger;
receiving access requests and royalty payments to access the updated executable instructions by respective parties;
executing an operation, responsive to receiving one of the access requests, to commit one of the respective parties to at least one of the plurality of IP licensing terms corresponding to the one of the IP assets including the updated executable instructions via the distributed ledger, whereby the one of the respective parties is provided with access to the updated executable instructions in accordance with the at least one of the plurality of IP licensing terms;
providing access to the updated executable instructions to the one of the respective parties by providing an interface description for the updated executable instructions, the interface description including an application programming interface (API) for accessing the updated executable instructions, wherein the access is restricted according to a scope of use defined by the at least one of the plurality of IP licensing terms, the scope of use including at least one of a time frame for using the updated executable instructions or a volume of use of the updated executable instructions;
recording on the distributed ledger, by the smart wrapper, access information of the one of the respective parties based on providing the one of the respective parties with access to the updated executable instructions in accordance with the at least one of the plurality of IP licensing terms, wherein the access information includes at least one of a username, an e-mail address, an internet protocol address, a geographic location, a time stamp, or which portion of the updated executable instructions are available for access by the one of the respective parties;
interpreting a transaction request provided by a party requesting access to the updated executable instructions in exchange for a royalty, the royalty being provided as a cryptocurrency, the transaction request indicating a cryptocurrency type and an amount of the cryptocurrency,
wherein the party provides the transaction request to the smart wrapper via the web-based user interface provided by the smart wrapper to the party,
the smart wrapper is included with a controller, and
the smart wrapper provides a consistent web-based user interface to the party for receiving the transaction request from the party such that changes to the controller are invisible to the party;
determining a transaction location parameter corresponding to the transaction request, the transaction location parameter comprising at least one of a transaction geographic value or a transaction jurisdiction value; and
providing, by the smart wrapper, a transaction implementation command for the one of the plurality of IP assets in response to the transaction location parameter and the IP licensing terms, the transaction implementation command indicating a geographical location of a server on which to execute a transaction corresponding to the transaction request.

### Claim 11 (depends on 10)

The non-transitory computer readable storage medium of claim 10, wherein the instructions further comprise interpreting transactions and storing transaction location parameter values corresponding to each of the transactions according to at least one of: transaction type, transaction amount, or entity characteristics corresponding to requesting entities for the transactions.

### Claim 12 (depends on 11)

The non-transitory computer readable storage medium of claim 11, wherein the instructions further comprise executing transaction tasks including providing transaction implementation commands based at least in part on the transaction location parameter values.

### Claim 13 (depends on 10)

The non-transitory computer readable storage medium of claim 10, wherein the instructions further comprise:
interpreting a plurality of transaction request values,
wherein each transaction request value includes a transaction description for a proposed transaction.

### Claim 14 (depends on 13)

The non-transitory computer readable storage medium of claim 13, wherein the instructions further comprise commanding execution of the proposed transaction.

### Claim 15 (depends on 13)

The non-transitory computer readable storage medium of claim 13, wherein the transaction description includes a cryptocurrency type value and a transaction amount value.

### Claim 16 (depends on 10)

The non-transitory computer readable storage medium of claim 10, wherein the executable instructions includes descriptions to perform a proprietary operation.

### Claim 17 (depends on 10)

The non-transitory computer readable storage medium of claim 10, wherein the instructions further comprise:
the smart wrapper operating to provide an interface to the party for receiving the transaction request, and to provide an interface to a transaction engine for sending the transaction implementation command.

### Claim 18 (depends on 10)

The non-transitory computer readable storage medium of claim 10, wherein the distributed ledger is a blockchain, and wherein more than half of the distributed memory locations of the blockchain agree on the updated pointer.