# US 12,192,795 B2 · Collaborative computing and electronic records > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 12,192,795 B2 - Document ID: US12192795B2 - Status: Granted - Kind: B2 - Application number: 18/375,833 - Filed: 2023-10-02 - Published: 2024-03-28 - Granted: 2025-01-07 - Earliest claimed: 2010-11-05 - Applicants: Mark Cummings - Inventors: Mark Cummings - Web page: https://patentgrep.com/patent/US12192795B2 ## CPC - H04W 24/02: Arrangements for optimising operational condition - G06F 9/4411: {Configuring for operating with peripheral devices; Loading of device drivers} - G06F 30/327: Logic synthesis; Behaviour synthesis, e.g. mapping logic, HDL to netlist, high-level language to RTL or netlist - H04L 67/51: Discovery or management thereof, e.g. service location protocol [SLP] or web services - H04W 8/22: Processing or transfer of terminal data, e.g. status or physical capabilities - H04W 28/0215: {based on user or device properties, e.g. MTC-capable devices (services for machine-to-machine communication [M2M] or machine type communication [MTC] H04W4/70; wireless resource selection or allocation plan definition based on terminal or device properties H04W72/51)} - H04W 48/16: Discovering, processing access restriction or access information - H04W 24/00: Supervisory, monitoring or testing arrangements - H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72) - G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N) - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) ## Abstract Collaborative computing and electronic records are disclosed. An entity that may be able to help achieve an objective is discovered and a connection to the entity established. A meta-language is used to exchange with the entity a description of the objective and a description of the entity. The meta-language is used to negotiate with the entity a contract to help achieve the objective. In the event a contract to help achieve the objective is reached, performing a self-configuration in accordance with the contract. ## Claims ### Claim 1 A method, comprising: discovering, by a first orchestrator associated with a first cloud-based entity, a second orchestrator associated with a second cloud-based entity, wherein the first cloud-based entity is associated with an application; connecting to the second cloud-based entity, wherein the first orchestrator associated with the first cloud-based entity and the second orchestrator associated with the second cloud-based entity are configured to negotiate and enter into a contract; utilizing a meta-language to exchange with the second orchestrator associated with the second cloud-based entity a description of at least one of the first cloud-based entity or the application; transitioning the application from the first cloud-based entity to the second cloud-based entity; and terminating a connection with the application. ### Claim 2 (depends on 1) The method of claim 1, wherein the first orchestrator associated with the first cloud-based entity and the second orchestrator associated with the second cloud-based entity are configured to negotiate one or more security requirements. ### Claim 3 (depends on 2) The method of claim 2, wherein the one or more security requirements include at least one of identity protection and protection of metadata in transit. ### Claim 4 (depends on 3) The method of claim 3, wherein the metadata includes behavioral data. ### Claim 5 (depends on 1) The method of claim 1, wherein the first orchestrator associated with the first cloud-based entity and the second orchestrator associated with the second cloud-based entity are configured to negotiate one or more management requirements. ### Claim 6 (depends on 1) The method of claim 1, wherein the first orchestrator associated with the first cloud-based entity and the second orchestrator associated with the second cloud-based entity are configured to negotiate requirements that involve security and management. ### Claim 7 (depends on 1) The method of claim 1, wherein the application is part of a cloud-based service. ### Claim 8 (depends on 7) The method of claim 7, wherein the cloud-based service spans a plurality of clouds. ### Claim 9 (depends on 1) The method of claim 1, wherein the application is configured based on the negotiations between the first orchestrator associated with the first cloud-based entity and the second orchestrator associated with the second cloud-based entity. ### Claim 10 (depends on 1) The method of claim 1, wherein the application is associated with a third orchestrator. ### Claim 11 (depends on 10) The method of claim 10, wherein the first orchestrator associated with the first cloud-based entity and the second orchestrator associated with the second cloud-based entity are configured to negotiate how the third orchestrator is to be modified from being an orchestrator in the first cloud-based entity to an orchestrator in the second cloud-based entity. ### Claim 12 (depends on 10) The method of claim 10, wherein the third orchestrator is configured based on the negotiations between the first orchestrator associated with the first cloud-based entity and the second orchestrator associated with the second cloud-based entity. ### Claim 13 (depends on 10) The method of claim 10, wherein the third orchestrator is transitioned with the application from the first cloud-based entity to the second cloud-based entity. ### Claim 14 (depends on 10) The method of claim 10, wherein the first orchestrator associated with the first cloud-based entity and the second orchestrator associated with the second cloud-based entity are configured to negotiate and enter into a second contract with the third orchestrator. ### Claim 15 (depends on 1) The method of claim 1, wherein the first cloud-based entity and the second cloud-based entity are part of a system. ### Claim 16 (depends on 15) The method of claim 15, wherein the system includes an intermediary that is configured to interface with the first cloud-based entity and the second cloud-based entity. ### Claim 17 (depends on 16) The method of claim 16, wherein the intermediary is configured to communicate metadata, new rules, new objectives, and/or new algorithms with the first orchestrator associated with the first cloud-based entity and the second orchestrator associated with the second cloud-based entity. ### Claim 18 (depends on 16) The method of claim 16, wherein the intermediary is configured to provide instructions to the first orchestrator associated with the first cloud-based entity and the second orchestrator associated with the second cloud-based entity. ### Claim 19 (depends on 16) The method of claim 16, wherein the intermediary is configured to receive and store information from the first orchestrator associated with the first cloud-based entity and the second orchestrator associated with the second cloud-based entity. ### Claim 20 A system, comprising: a processor associated with a first cloud-based entity, wherein the processor is configured to; communicate with an orchestrator associated with a second cloud-based entity; discover the orchestrator associated with the second cloud-based entity, wherein the first cloud-based entity is associated with an application; connect to the second cloud-based entity, wherein the processor and the orchestrator associated with the second cloud-based entity are configured to negotiate and enter into a contract; utilize a meta-language to exchange with the orchestrator associated with the second cloud-based entity a description of at least one of the first cloud-based entity or the application; transition the application from the first cloud-based entity to the second cloud-based entity; and terminate a connection with the application; and a memory coupled to the processor and configured to provide the processor with instructions. ### Claim 21 (depends on 20) The system of claim 20, wherein the processor and the orchestrator associated with the second cloud-based entity are configured to negotiate one or more security requirements, wherein the one or more security requirements include at least one of identity protection and protection of metadata in transit. ### Claim 22 (depends on 20) The system of claim 20, wherein the application is part of a cloud-based service. ### Claim 23 (depends on 20) The system of claim 20, wherein the application is configured based on the negotiations between the processor and the orchestrator associated with the second cloud-based entity. ### Claim 24 (depends on 20) The system of claim 20, wherein the application is associated with a corresponding orchestrator. ### Claim 25 (depends on 24) The system of claim 24, wherein the processor and the orchestrator associated with the second cloud-based entity are configured to negotiate how the corresponding orchestrator associated with the application is to be modified from being an orchestrator in the first cloud-based entity to an orchestrator in the second cloud-based entity. ### Claim 26 A computer program product, the computer program product being embodied in a non-transitory computer readable storage medium, and comprising computer instructions for: discovering, by a first orchestrator associated with a first cloud-based entity, a second orchestrator associated with a second cloud-based entity, wherein the first cloud-based entity is associated with an application; connecting to the second cloud-based entity, wherein the first orchestrator associated with the first cloud-based entity and the second orchestrator associated with the second cloud-based entity are configured to negotiate and enter into a contract; utilizing a meta-language to exchange with the second orchestrator associated with the second cloud-based entity a description of at least one of the first cloud-based entity or the application; transitioning the application from the first cloud-based entity to the second cloud-based entity; and terminating a connection with the application.