# US 2019/0320040 A1 · Methods, apparatus, and systems to dynamically discover and host services in fog servers

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

- Number: US 2019/0320040 A1
- Document ID: US20190320040A1
- Status: Published application
- Kind: A1
- Application number: 15/993,622
- Filed: 2018-05-31
- Published: 2019-10-17
- Earliest claimed: 2018-04-17
- Assignees: VMware, Inc.
- Applicants: Vmware, Inc.
- Inventors: Ravi Kumar Reddy Kottapalli; Shubham Verma; Suket Gakhar; Kannan Balasubramanian
- Web page: https://patentgrep.com/patent/US20190320040A1

## CPC

- 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 47/76: using dynamic resource allocation, e.g. in-call renegotiation requested by the user or requested by the network in response to changing network conditions
- H04L 47/781: {Centralised allocation of resources}
- H04L 67/51: Discovery or management thereof, e.g. service location protocol [SLP] or web services
- H04L 67/60: Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources (admission control or resource allocation H04L47/70)
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

Methods, apparatus, systems and articles of manufacture to dynamically discover and host services in fog servers are disclosed. An example apparatus includes a service manager to determine that a received service request from an Internet of things (IoT) device is not able to be performed locally at a first fog server; a first interface to transmit the service request to a fog resource manager; and a second interface to transmit instructions to the IoT device to transmit the service request to a second fog server, a response from the fog resource manager including service data related to the second fog server.

## Claims

### Claim 1

An apparatus to perform service requests in a fog environment, the apparatus comprising:
a service manager to determine that a received service request from an Internet of things (IoT) device is not able to be performed locally at a first fog server;
a first interface to transmit the service request to a fog resource manager; and
a second interface to transmit instructions to the IoT device to transmit the service request to a second fog server, a response from the fog resource manager including service data related to the second fog server.

### Claim 2 (depends on 1)

The apparatus of claim 1, wherein the first interface is the second interface.

### Claim 3 (depends on 1)

The apparatus of claim 1, wherein the service manager is to determine that the received service request is not able to be performed locally based on a service table, the service table identifying services that are locally provided at the first fog server and the availability of the services.

### Claim 4 (depends on 3)

The apparatus of claim 3, wherein the first interface is to transmit a resource update to the fog resource manager when the service table is updated.

### Claim 5 (depends on 1)

The apparatus of claim 1, wherein the service manager is to process the response from the fog resource manager to identify the second fog server.

### Claim 6 (depends on 1)

The apparatus of claim 1, wherein the fog resource manager is a first fog resource manager, wherein the first interface is to transmit the service request to a second fog resource manager when a connection to the first resource manager is unavailable, a response from the second fog resource manager including service data related to the second fog server.

### Claim 7 (depends on 1)

The apparatus of claim 1, wherein the instructions include instructions to update a datacenter component of an IoT gateway to correspond to the second fog server.

### Claim 8

An apparatus to host services in fog servers, the apparatus comprising:
a database to store service tables corresponding to capabilities and availability of fog servers in a network of fog servers;
a service manager to process the service tables to select a first fog server capable of performing a received service request from a second fog server; and
an interface to transmit service details corresponding to the first fog server to the second fog server.

### Claim 9 (depends on 8)

The apparatus of claim 8, wherein the second fog server is not capable of performing the service request.

### Claim 10 (depends on 8)

The apparatus of claim 8, wherein the service manager selects the first fog server based on a location of the first fog server.

### Claim 11 (depends on 10)

The apparatus of claim 10, wherein the service manager is to determine if a distance between the second fog server and the first fog server is more than a threshold distance.

### Claim 12 (depends on 8)

The apparatus of claim 8, wherein the service details include at least one of an identifier or an address of the first fog server.

### Claim 13 (depends on 8)

The apparatus of claim 8, wherein the service manager is to determine if the second fog server has received more than a threshold number of service requests corresponding to a service type of the received service request.

### Claim 14 (depends on 13)

The apparatus of claim 13, wherein the interface is to, when the second fog server has received more than the threshold number of service requests corresponding to the service type, instruct a neighboring fog server to reconfigure resources of the neighboring fog server to be able to execute services corresponding to the service type.

### Claim 15

A tangible computer readable storage medium comprising instructions which, when executed, cause a machine to at least:
determine that a received service request from an Internet of things (IoT) device is not able to be performed locally at a first fog server;
transmit the service request to a fog resource manager; and
transmit instructions to the IoT device to transmit the service request to a second fog server, a response from the fog resource manager including service data related to the second fog server.

### Claim 16 (depends on 15)

The computer readable storage medium of claim 15, wherein the instructions cause the machine to determine that the received service request is not able to be performed locally based on a service table, the service table identifying services that are locally provided at the first fog server and the availability of the services.

### Claim 17 (depends on 16)

The computer readable storage medium of claim 16, wherein the instructions cause the machine to transmit a resource update to the fog resource manager when the service table is updated.

### Claim 18 (depends on 15)

The computer readable storage medium of claim 15, wherein the instructions cause the machine to process the response from the fog resource manager to identify the second fog server.

### Claim 19 (depends on 15)

The computer readable storage medium of claim 15, wherein the fog resource manager is a first fog resource manager, wherein the instructions cause the machine to transmit the service request to a second fog resource manager when a connection to the first resource manager is unavailable, a response from the second fog resource manager including service data related to the second fog server.

### Claim 20 (depends on 15)

The computer readable storage medium of claim 15, wherein the instructions include instructions to update a datacenter component of an IoT gateway to correspond to the second fog server.

### Claim 21

A tangible computer readable storage medium comprising instructions which, when executed, cause a machine to at least:
store service tables corresponding to capabilities and availability of fog servers in a network of fog servers;
process the service tables to select a first fog server capable of performing a received service request from a second fog server; and
transmit service details corresponding to the first fog server to the second fog server.

### Claim 22 (depends on 21)

The computer readable storage medium of claim 21, wherein the second fog server is not capable of performing the service request.

### Claim 23 (depends on 21)

The computer readable storage medium of claim 21, wherein the instructions cause the machine to select the first fog server based on a location of the first fog server.

### Claim 24 (depends on 23)

The computer readable storage medium of claim 23, wherein the instructions cause the machine to determine if a distance between the second fog server and the first fog server is more than a threshold distance.

### Claim 25 (depends on 21)

The computer readable storage medium of claim 21, wherein the service details include at least one of an identifier or an address of the first fog server.

### Claim 26 (depends on 21)

The computer readable storage medium of claim 21, wherein the instructions cause the machine to determine if the second fog server has received more than a threshold number of service requests corresponding to a service type of the received service request.

### Claim 27 (depends on 26)

The computer readable storage medium of claim 26, wherein the instructions cause the machine to, when the second fog server has received more than the threshold number of service requests corresponding to the service type, instruct a neighboring fog server to reconfigure resources of the neighboring fog server to be able to execute services corresponding to the service type.

### Claim 28

A method to perform service requests in a fog environment, the method comprising:
determining, by executing an instruction using a processor, that a received service request from an Internet of things (IoT) device is not able to be performed locally at a first fog server;
transmitting the service request to a fog resource manager; and
transmitting instructions to the IoT device to transmit the service request to a second fog server, a response from the fog resource manager including service data related to the second fog server.

### Claim 29 (depends on 28)

The method of claim 28, further including determining that the received service request is not able to be performed locally based on a service table, the service table identifying services that are locally provided at the first fog server and the availability of the services.

### Claim 30 (depends on 29)

The method of claim 29, further including transmitting a resource update to the fog resource manager when the service table is updated.

### Claim 31 (depends on 28)

The method of claim 28, further including processing the response from the fog resource manager to identify the second fog server.

### Claim 32 (depends on 28)

The method of claim 28, wherein the fog resource manager is a first fog resource manager, further including transmitting the service request to a second fog resource manager when a connection to the first resource manager is unavailable, a response from the second fog resource manager including service data related to the second fog server.

### Claim 33 (depends on 28)

The method of claim 28, further including updating a datacenter component of an IoT gateway to correspond to the second fog server.

### Claim 34

A method to host services in fog servers, the method comprising:
storing service tables corresponding to capabilities and availability of fog servers in a network of fog servers;
processing, by executing an instruction using a processor, the service tables to select a first fog server capable of performing a received service request from a second fog server; and
transmitting service details corresponding to the first fog server to the second fog server.

### Claim 35 (depends on 34)

The method of claim 34, wherein the second fog server is not capable of performing the service request.

### Claim 36 (depends on 34)

The method of claim 34, further including selecting the first fog server based on a location of the first fog server.

### Claim 37 (depends on 36)

The method of claim 36, further including determining if a distance between the second fog server and the first fog server is more than a threshold distance.

### Claim 38 (depends on 34)

The method of claim 34, wherein the service details include at least one of an identifier or an address of the first fog server.

### Claim 39 (depends on 34)

The method of claim 34, further including determining if the second fog server has received more than a threshold number of service requests corresponding to a service type of the received service request.

### Claim 40 (depends on 39)

The method of claim 39, further including, when the second fog server has received more than the threshold number of service requests corresponding to the service type, instructing a neighboring fog server to reconfigure resources of the neighboring fog server to be able to execute services corresponding to the service type.

### Claim 41

A system to host services in fog servers, the system comprising:
a first fog server to:
determine that a received service request from a requesting device cannot be executed locally at the first fog server; and
transmit the received service request to a fog resource manager;
the fog resource manager of a software defined data center to:
identify a second fog server that is capable of executing the service request; and
transmit data corresponding to the second fog server to the first fog server,
the first fog server to instruct the second fog server to execute the service request.

### Claim 42 (depends on 41)

The system of claim 41, wherein the first fog server cannot execute the service request locally because at least one of the first fog server is not configured to execute the service request or the first fog server does not have sufficient resources to execute the service request.

### Claim 43 (depends on 41)

The system of claim 41, wherein the fog resource manager is to monitor the first and second fog servers using service tables.

### Claim 44 (depends on 43)

The system of claim 43, wherein the first fog server is to update the service tables when at least one of an execution of a service is initiated by the first fog server, an execution of a service is terminated by the first fog server, when service throttling is initiated, an execution of a service has been migrated, or an execution of a service has restarted or paused.

### Claim 45 (depends on 43)

The system of claim 43, wherein the first fog server is to transmit resource updates to the fog resource manager when the first fog server updates a service table corresponding to the first fog server.

### Claim 46 (depends on 41)

The system of claim 41, wherein the first fog server is to receive service request results from the second fog server and transmits the service request results to the requesting device.

### Claim 47 (depends on 41)

The system of claim 41, wherein the fog resource manager is to instruct the first fog server to configure one or more containers of the first fog server to be able to execute selected services.

### Claim 48 (depends on 41)

The system of claim 41, wherein the fog resource manager registers the first fog server and the second fog server.
