# US 12,602,240 B2 · Remote edge virtualization management > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 12,602,240 B2 - Document ID: US12602240B2 - Status: Granted - Kind: B2 - Application number: 17/886,885 - Filed: 2022-08-12 - Published: 2024-01-25 - Granted: 2026-04-14 - Earliest claimed: 2022-07-19 - Assignees: VMware, Inc. - Applicants: VMware LLC - Inventors: Tiejun Chen - Web page: https://patentgrep.com/patent/US12602240B2 ## CPC - G06F 9/45558: {Hypervisor-specific management and integration aspects} - H04L 51/21: Monitoring or handling of messages - H04L 67/562: Brokering proxy services - G06F 2009/45595: {Network integration; Enabling network access in virtual machine instances} - 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 Aspects of remote edge virtualization management are described. An edge hypervisor shadow application is executed. The edge hypervisor shadow application acts as an Input/Output for an edge hypervisor that is IP inaccessible to a virtualization service. The edge hypervisor shadow application receives a hypertext transport protocol (HTTP) communication from the virtualization service. A Message Queue Telemetry Transport (MQTT) message is generated to include the HTTP request, and is published to an MQTT broker service, the MQTT message comprising the HTTP request. ## Claims ### Claim 1 A system, comprising: at least one computing device comprising one or more processors; and instructions executable by the one or more processors to cause the at least one computing device perform operations comprising executing an edge hypervisor shadow application that provides Input/Output (I/O) functionalities for an edge hypervisor that is IP inaccessible to a virtualization service, wherein the edge hypervisor shadow application is IP accessible to the virtualization service; receiving, by the edge hypervisor shadow application, a hypertext transport protocol (HTTP) request from the virtualization service, wherein the HTTP request comprises virtualization instructions for the edge hypervisor; generating, by the edge hypervisor shadow application, a Message Queue Telemetry Transport (MQTT) message that includes the HTTP request; and publishing, by the edge hypervisor shadow application to an MQTT broker service, the MQTT message that includes the HTTP request; receiving, by the edge hypervisor shadow application, a response MQTT message comprising an HTTP response that the edge hypervisor generates in response to the HTTP request; extracting, by the edge hypervisor shadow application, the HTTP response from the MQTT message; and transmitting, by the edge hypervisor shadow application, the HTTP response to the virtualization service. ### Claim 2 (depends on 1) The system of claim 1, wherein the edge hypervisor shadow application publishes the MQTT message to a topic identifier that an edge agent subscribes to, wherein the edge hypervisor is IP accessible to the edge agent. ### Claim 3 (depends on 1) The system of claim 1, wherein the edge hypervisor shadow application generates the MQTT message by modifying the HTTP request by replacing a network address of the edge hypervisor shadow application with a private IP address of the edge hypervisor. ### Claim 4 (depends on 1) The system of claim 1, wherein the edge hypervisor shadow application is deployed within a virtual machine that is executed in a host device that is IP accessible to the virtualization service. ### Claim 5 (depends on 1) The system of claim 1, wherein the operations further comprise: subscribing, by the edge hypervisor shadow application, to a topic identifier uniquely associated with the edge hypervisor. ### Claim 6 (depends on 1) The system of claim 1, wherein the edge hypervisor shadow application runs on a host selected by the virtualization service. ### Claim 7 (depends on 1) The system of claim 1 wherein the operations further comprise: registering, by the edge hypervisor shadow application, as the edge hypervisor with the virtualization service; and communicating, by the edge hypervisor shadow application, with the virtualization service as a local Input/Output (I/O) endpoint for the edge hypervisor. ### Claim 8 A method, comprising: executing an edge hypervisor shadow application that provides Input/Output (I/O) functionalities for an edge hypervisor that is IP inaccessible to a virtualization service, wherein the edge hypervisor shadow application is IP accessible to the virtualization service; receiving, by the edge hypervisor shadow application, a hypertext transport protocol (HTTP) request from the virtualization service, wherein the HTTP request comprises virtualization instructions for the edge hypervisor; generating, by the edge hypervisor shadow application, a Message Queue Telemetry Transport (MQTT) message that includes the HTTP request; publishing, by the edge hypervisor shadow application to an MQTT broker service, the MQTT message that includes the HTTP request; receiving, by the edge hypervisor shadow application, a response MQTT message comprising an HTTP response that the edge hypervisor generates in response to the HTTP request; extracting, by the edge hypervisor shadow application, the HTTP response from the MQTT message; and transmitting, by the edge hypervisor shadow application, the HTTP response to the virtualization service. ### Claim 9 (depends on 8) The method of claim 8, wherein the edge hypervisor shadow application publishes the MQTT message to a topic identifier that an edge agent subscribes to, wherein the edge hypervisor is IP accessible to the edge agent. ### Claim 10 (depends on 8) The method of claim 8, wherein the edge hypervisor shadow application generates the MQTT message by modifying the HTTP request by replacing a network address of the edge hypervisor shadow application with a private IP address of the edge hypervisor. ### Claim 11 (depends on 8) The method of claim 8, wherein the edge hypervisor shadow application is deployed within a virtual machine that is executed in a host device that is IP accessible to the virtualization service. ### Claim 12 (depends on 8) The method of claim 8, further comprising: subscribing, by the edge hypervisor shadow application, to a topic identifier uniquely associated with the edge hypervisor. ### Claim 13 (depends on 8) The method of claim 8, wherein the edge hypervisor shadow application runs on a host selected by the virtualization service. ### Claim 14 (depends on 8) The method of claim 8, further comprising: registering, by the edge hypervisor shadow application, as the edge hypervisor with the virtualization service; and communicating, by the edge hypervisor shadow application, with the virtualization service as a local Input/Output (I/O) endpoint for the edge hypervisor. ### Claim 15 A non-transitory computer readable medium embodying instructions executable by one or more processors to perform operations comprising: executing an edge hypervisor shadow application that provides Input/Output (I/O) functionalities for an edge hypervisor that is IP inaccessible to a virtualization service, wherein the edge hypervisor shadow application is IP accessible to the virtualization service; receiving, by the edge hypervisor shadow application, a hypertext transport protocol (HTTP) request from the virtualization service, wherein the HTTP request comprises virtualization instructions for the edge hypervisor; generating, by the edge hypervisor shadow application, a Message Queue Telemetry Transport (MQTT) message that includes the HTTP request; publishing, by the edge hypervisor shadow application to an MQTT broker service, the MQTT message that includes the HTTP request; receiving, by the edge hypervisor shadow application, a response MQTT message comprising an HTTP response that the edge hypervisor generates in response to the HTTP request; extracting, by the edge hypervisor shadow application, the HTTP response from the MQTT message; and transmitting, by the edge hypervisor shadow application, the HTTP response to the virtualization service. ### Claim 16 (depends on 15) The non-transitory computer readable medium of claim 15, wherein the edge hypervisor shadow application publishes the MQTT message to a topic identifier that an edge agent subscribes to, wherein the edge hypervisor is IP accessible to the edge agent. ### Claim 17 (depends on 15) The non-transitory computer readable medium of claim 15, wherein the edge hypervisor shadow application generates the MQTT message by modifying the HTTP request by replacing a network address of the edge hypervisor shadow application with a private IP address of the edge hypervisor. ### Claim 18 (depends on 15) The non-transitory computer readable medium of claim 15, wherein the edge hypervisor shadow application is deployed within a virtual machine that is executed in a host device that is IP accessible to the virtualization service. ### Claim 19 (depends on 18) The non-transitory computer readable medium of claim 18, wherein the operations further comprise: subscribing, by the edge hypervisor shadow application, to a topic identifier uniquely associated with the edge hypervisor; and receiving, by the edge hypervisor shadow application, a response MQTT message comprising an HTTP response that the edge hypervisor generates in response to the HTTP request. ### Claim 20 (depends on 15) The non-transitory computer readable medium of claim 15, wherein the edge hypervisor shadow application runs on a host selected by the virtualization service.