WO2020147009A1

WO2020147009A1 - Method and device for configuring fog node device, and computer readable medium

Info

Publication number: WO2020147009A1
Application number: PCT/CN2019/071787
Authority: WO
Inventors: 温海波
Original assignee: 上海诺基亚贝尔股份有限公司; 诺基亚通信公司
Priority date: 2019-01-15
Filing date: 2019-01-15
Publication date: 2020-07-23
Also published as: CN113169996B; CN113169996A

Abstract

A method and device for configuring a fog node device, and a computer readable medium. The method comprises: sending, from a fog node device to an address management device, a request for the network address of a fog server (510), the fog server being configured to manage the fog node device; receiving the network address of the fog server from the address management device (520); and sending, from the fog node device to the fog server on the basis of the network address, information related to a resource that the fog node device can provide (530).

Description

Method, device and computer readable medium for configuring fog node device

Technical field

The embodiments of the present disclosure generally relate to communication technologies, and more specifically, to methods, devices, and computer-readable media for configuring fog node devices.

Background technique

With the development of information technology, cloud computing has become more and more widely used. Cloud computing has some inherent features, such as scalability, on-demand resource allocation, reduced management work, and simple application and service provision. Cloud computing can provide terminal equipment or end users with outsourcing computing and storage functions, so that they will not worry about managing their own infrastructure, but enjoy flexible and convenient services.

However, cloud computing still has some limitations. Due to the introduction of the Internet of Things (IoT), the Internet of Things aims to connect billions of smart objects to the Internet, and these objects are expected to generate a large amount of data and send the data to the cloud for further processing, and then related actions. In fact, sending all the captured data to the cloud is not very useful. In addition, this method will also lead to waste of resources (such as network, storage, etc.). The connection between the cloud and the terminal device will cause longer delays, which is not suitable for delay-sensitive applications. In fact, some applications prefer to be processed nearby, which can reduce network transmission resource consumption, rapid response, and reduce response time.

In order to solve the above problems, Fog Computing is proposed as an extended concept of cloud computing. Fog computing is not composed of powerful servers, but is composed of weaker and more scattered functional devices with idle resources, such as various devices that infiltrate factories, cars, electrical appliances, street lights, and people's material lives And other composition. Fog computing can distribute services along the cloud-to-thing continuity to the vicinity of end users. It covers mobile and wired scenarios, traverses hardware and software, resides at the edge of the network, but can also access the network and end users. Fog computing enables computing at the edge of the network, closer to the Internet of Things and/or end user equipment. Fog computing can increase the battery life of terminal devices by reducing energy requirements, especially for mobile terminals in critical situations. It can also reduce the communication delay of certain selected applications with low edge latency. In addition, it can also achieve New value-added services, such as IoT applications.

Summary of the invention

In general, the embodiments of the present disclosure relate to methods, devices, and computer-readable media for configuring fog node devices.

In a first aspect, an embodiment of the present disclosure provides an electronic device. The electronic device includes: at least one processor; and a memory coupled with the at least one processor, and an instruction is stored in the memory. When the instruction is executed by the at least one processor, the electronic device executes an action, and the action includes: slave fog node The device sends a request for the network address of the fog server to the address management device. The fog server is configured to manage the fog node device; receives the network address of the fog server from the address management device; and based on the network address, sends a request from the fog node device to the fog server. Information about the resources that the fog node device can provide.

In some embodiments, the fog node device includes a Dynamic Host Configuration Protocol DHCP client, and the address management device includes a DHCP server.

In some embodiments, sending a request for a network address to the address management device includes sending a DHCP discovery message or a DHCP request message to the address management device, the DHCP discovery message and the DHCP request message each including an indication of the request for the network address.

In some embodiments, the address management device includes a router.

In some embodiments, sending a request for a network address to the address management device includes sending a route request message to the address management device, and the route request message includes an indication of the request for the network address.

In some embodiments, the action further includes: receiving an instruction to provide a service to the terminal device from the fog server, the service being determined based on information about the resource that the fog node device can provide; and using the resource to provide the service to the terminal device.

In some embodiments, providing a service to a terminal device includes: receiving application code required to provide the service from the fog server; and providing the service by running the application code.

In a second aspect, embodiments of the present disclosure provide an electronic device. The electronic device includes: at least one processor; and a memory coupled with the at least one processor, and an instruction is stored in the memory. When the instruction is executed by the at least one processor, the electronic device executes an action, and the action includes: At the device, a request for the network address of the fog server is received from the fog node device, the fog server is configured to manage the fog node device; and the fog node device is sent the network address of the fog server.

In some embodiments, receiving a request for a network address from the fog node device includes: receiving a DHCP discovery message or a DHCP request message from the fog node device, the DHCP discovery message and the DHCP request message each including an indication of the request for the network address.

In some embodiments, the address management device includes a router.

In some embodiments, receiving a request for a network address from the fog node device includes: receiving a routing request message from the fog node device, the routing request message including an indication of the request for the network address.

In a third aspect, embodiments of the present disclosure provide an electronic device. The electronic device includes: at least one processor; and a memory coupled with the at least one processor, and an instruction is stored in the memory. When the instruction is executed by the at least one processor, the electronic device executes an action, and the action includes: At the office, receiving information related to the resources that the fog node device can provide from the fog node device; and managing the fog node device based on the information related to the resource.

In some embodiments, the action further includes: in response to receiving a request to provide a service from the terminal device, determining whether the fog node device can provide the service based on information related to the resource; and in response to determining that the fog node device can provide the service, The fog node device sends an instruction to provide services to the terminal device.

In some embodiments, the action further includes: sending application code required to provide services to the fog node device.

In a fourth aspect, embodiments of the present disclosure provide a communication method. The method includes: sending a request for a network address of a fog server from a fog node device to an address management device, and the fog server is configured to manage the fog node device. The method also includes receiving the network address of the fog server from the address management device. The method further includes sending information related to the resources that the fog node device can provide from the fog node device to the fog server based on the network address.

In the fifth aspect, the embodiments of the present disclosure provide a communication method. The method includes: at an address management device, receiving a request for a network address of a fog server from a fog node device, and the fog server is configured to manage the fog node device. The method further includes: sending the network address of the fog server to the fog node device.

In the sixth aspect, the embodiments of the present disclosure provide a communication method. The method includes: at the fog server, receiving information related to the resources that the fog node device can provide from the fog node device. The method also includes: managing the fog node device based on the information related to the resource.

In a seventh aspect, embodiments of the present disclosure provide a computer-readable storage medium. The computer-readable storage medium includes program code stored thereon, which when executed by the device, causes the device to perform the method according to the fourth aspect.

In an eighth aspect, embodiments of the present disclosure provide a computer-readable storage medium. The computer-readable storage medium includes program code stored thereon, which when executed by the device, causes the device to perform the method according to the fifth aspect.

In a ninth aspect, embodiments of the present disclosure provide a computer-readable storage medium. The computer-readable storage medium includes a program code stored thereon, and when the program code is executed by an apparatus, the apparatus executes the method according to the sixth aspect.

It should be understood that the content described in the content of the invention is not intended to limit the key or important features of the embodiments of the present disclosure, nor is it intended to limit the scope of the present disclosure. Other features of the present disclosure will be easily understood by the following description.

BRIEF DESCRIPTION

With reference to the accompanying drawings and the following detailed description, the above and other features, advantages and aspects of the embodiments of the present disclosure will become more apparent. In the drawings, the same or similar reference signs indicate the same or similar elements, in which:

Fig. 1 is a schematic diagram of a communication network in which embodiments described in the present disclosure can be implemented;

Figure 2 shows a signaling diagram of communication according to certain embodiments of the present disclosure;

Figure 3 shows a schematic diagram of a message format according to certain embodiments of the present disclosure;

Figure 4 shows a schematic diagram of a message format according to some embodiments of the present disclosure;

FIG. 5 shows a flowchart of an example method implemented at a fog node device according to some embodiments of the present disclosure;

Figure 6 shows a flowchart of an example method implemented at an address management device according to some embodiments of the present disclosure;

FIG. 7 shows a flowchart of an example method implemented at a fog server according to some embodiments of the present disclosure;

Figure 8 shows a block diagram of a communication device according to some embodiments of the present disclosure.

In all the drawings, the same or similar parameter numbers indicate the same or similar elements.

detailed description

Hereinafter, embodiments of the present disclosure will be described in more detail with reference to the accompanying drawings. Although some embodiments of the present disclosure are shown in the drawings, it should be understood that the present disclosure can be implemented in various forms and should not be construed as being limited to the embodiments set forth herein. On the contrary, these embodiments are provided for Have a more thorough and complete understanding of this disclosure. It should be understood that the drawings and embodiments of the present disclosure are only used for exemplary purposes, and are not used to limit the protection scope of the present disclosure.

The term "circuit" as used herein refers to one or more of the following:

(a) Only hardware circuit implementation (such as only analog and/or digital circuit implementation); and

(b) A combination of hardware circuits and software, such as (if applicable): (i) a combination of analog and/or digital hardware circuits and software/firmware, and (ii) any part of the hardware processor and software (including working together to Digital signal processors, software and memory that enable devices such as OLT or other computing devices to perform various functions); and

(c) A hardware circuit and/or processor, such as a microprocessor or a part of a microprocessor, which requires software (e.g. firmware) for operation, but may not have software when it is not required for operation.

The definition of circuit is applicable to all usage scenarios of this term in this application (including any claims). As another example, the term "circuit" used herein also covers only a hardware circuit or a processor (or multiple processors), or a part of a hardware circuit or a processor, or an implementation of software or firmware accompanying it. For example, if applicable to specific claim elements, the term "circuitry" also covers baseband integrated circuits or processor integrated circuits or similar integrated circuits in OLT or other computing devices.

The term "network device" used herein refers to any appropriate entity or device that can provide a cell or coverage so that a terminal device can access the network or receive services from it. Examples of network equipment include, for example, a base station. The term "base station" (BS) used herein can mean Node B (NodeB or NB), evolved Node B (eNodeB or eNB), gNB, remote radio unit (RRU), radio head (RH), remote radio head Terminal (RRH), repeater, or low power node such as pico base station, femto base station, etc.

The term "terminal device" or "user equipment" (UE) used herein refers to any entity or device capable of wireless communication with network devices or with each other. As an example, the terminal device may include a mobile terminal (MT), a subscriber station (SS), a portable subscriber station (PSS), a mobile station (MS) or an access terminal (AT), the above-mentioned equipment in a vehicle, and a machine with communication function Or electrical appliances, etc.

The term "fog node device" as used herein refers to a device that can provide local computing resources and/or storage resources. As an example, fog node devices may include routers, switches, access nodes, optical distribution nodes (ODN), gateways, optical line terminals (OLT), terminal devices, and so on.

The term “fog server” used herein refers to a server that can provide information about the fog computing environment and manage the resources of the fog node device. For example, the fog server can select a fog node device that can provide corresponding resources in the fog computing environment for a computing or storage request of a terminal device to respond to the request.

The term "address management device" as used herein refers to any appropriate entity or device that manages the addresses of devices in the network. As an example, the address management device may include a server, a router, and so on.

The term "router" used here refers to a layer three device that supports routing protocols and realizes network interconnection by forwarding data packets.

The term "including" and its variations as used herein are open-ended includes, that is, "including but not limited to". The term "based on" is "based at least in part on." The term "one embodiment" means "at least one embodiment"; the term "another embodiment" means "at least one additional embodiment." Related definitions of other terms will be given in the description below.

Fog is a "cloud close to the ground", which extends the traditional cloud computing architecture to the edge of the network. A device that can provide local computing resources and/or storage resources is called a “fog node device”, and a server that can provide information about the fog computing environment and manage the resources of the fog node device is called a “fog server”. How a device that wants to become a fog node device discovers a fog server to provide it with information about the resources that the device can provide has become an urgent problem to be solved.

In order to at least partially solve the above-mentioned problems, the embodiments of the present disclosure propose a solution for implementing fog node device configuration in a fog computing environment. According to the configuration scheme of the fog node device of the present disclosure, the fog node device obtains the network address of the fog server from the address management device, and then communicates with the fog server based on the obtained network address. With the solution of the present disclosure, the effective automatic configuration of the fog node device can be realized. Hereinafter, the configuration scheme of the fog node device according to the present disclosure will be described in detail with reference to FIGS. 1 to 7.

Figure 1 illustrates an example communication system 100 in which embodiments of the present disclosure may be implemented. The communication system 100 includes a fog node device 110, an address management device 120, and a fog server 130. The address management device 120 is configured to manage the addresses of devices in the communication system 100. The fog node device 110 obtains the network address of the fog server 130 from the address management device 120, and then communicates with the fog server 130 based on the obtained network address. Thus, the fog server 130 can manage the fog node device 110.

It should be understood that the number of fog node devices and fog servers shown in FIG. 1 is only for illustrative purposes and is not intended to be limiting. The communication system 100 may include any suitable type and number of fog node devices and fog servers. In the case that the communication system 100 includes multiple fog servers, each fog server can manage different types of resources and any appropriate number of fog node devices in the communication system 100, thereby achieving load balancing.

The fog node device 110, the address management device 120 and the fog server 130 can communicate with each other. The communication between the fog node device 110, the address management device 120 and the fog server 130 may follow any appropriate wireless communication technology and corresponding communication standards. Examples of communication technologies include, but are not limited to, Long Term Evolution (LTE), LTE-Advanced (LTE-A), Wideband Code Division Multiple Access (WCDMA), Code Division Multiple Access (CDMA), Global System for Mobile Communications (GSM) , Orthogonal Frequency Division Multiple Access (OFDM), Wireless Local Area Network (WLAN), Worldwide Interoperability for Microwave Access (WiMAX), Bluetooth, Zigbee technology, Machine Type Communication (MTC), D2D, or M2M, etc. Moreover, communication can be performed according to any appropriate communication protocol, which includes, but is not limited to, Transmission Control Protocol (TCP)/Internet Protocol (IP), Hypertext Transfer Protocol (HTTP), User Datagram Protocol (UDP), Session Description protocol (SDP) and other protocols. It should be noted that although the embodiments of the present disclosure mainly use the UDP protocol as an example for description, this is only exemplary, and the technical solution of the present disclosure can use other suitable existing or future developed protocols.

FIG. 2 shows a signaling diagram of a fog node device configuration process 200 according to some embodiments of the present disclosure. The process 200 may be executed by the fog node device 110, the address management device 120, and the fog server 130 as shown in FIG. 1, for example. To facilitate discussion, the description of the process 200 will be performed in conjunction with the fog node device 110, the address management device 120, and the fog server 130. It should be understood that the process 200 may also include additional actions not shown and/or actions shown may be omitted, and the scope of the present disclosure is not limited in this respect.

The fog node device 110 sends 210 a request for the network address of the fog server 130 to the address management device 120. The fog server 130 is configured to manage the fog node device 110.

The address management device 120 may be configured with the network address of the fog server 130 in advance. Thus, after receiving the request from the fog node device 110, the address management device 120 sends 220 the network address of the fog server 130 to the fog node device 110.

In some embodiments, the fog node device 110 includes a Dynamic Host Configuration Protocol (DHCP) client, and the address management device 120 includes a DHCP server.

In such an embodiment, the fog node device 110 may request the network address of the fog server 130 by sending a DHCP discovery (Discover) message to the address management device 120, where the DHCP discovery message includes an indication of the request for the network address of the fog server 130 . Accordingly, the address management device 120 may send the network address of the fog server 130 by sending a DHCP reply (Reply) message to the fog node device 110.

Alternatively, the fog node device 110 may request the network address of the fog server 130 by sending a DHCP request (Request) message to the address management device 120, where the DHCP request message includes an indication of the request for the network address of the fog server 130. Accordingly, the address management device 120 may send the network address of the fog server 130 by sending a DHCP acknowledgement (ACK) message to the fog node device 110.

In an embodiment in which the fog node device 110 requests the network address of the fog server 130 by sending a DHCP discovery message or a DHCP request message to the address management device 120, the predefined "DHCP fog server" in the DHCP discovery message or DHCP request message may be used. Option" to indicate a request for the network address of the fog server 130.

FIG. 3 shows an example format of a DHCP fog server option 300 according to some embodiments of the present disclosure. As shown in the figure, the fog server option 300 includes at least an option code 310, an option length 320, and a network address part 330. Option code 310 can be defined as any suitable decimal value. The option length 320 indicates the length of the network address part 330. The network address part 330 is used to carry the network addresses of one or more fog servers. In the example of FIG. 3, it is assumed that the fog server 130 adopts an IPv4 address, so the length of the network address of a single fog server 130 is 4 octets. Therefore, the length of the network address portion 330 is an integer multiple of 4 octets.

As mentioned above, in some embodiments, the communication system 100 may include multiple fog servers, each configured as different types of resources. In such an embodiment, the address management device 120 may provide the fog node device 110 with the network address of each of the fog servers. For example, in the example of FIG. 3, the address management device 120 may add the network addresses of multiple fog servers to the network address part 330.

In some embodiments, after receiving the network addresses of multiple fog servers, the fog node device 110 may select one of the multiple fog servers to communicate based on the resources it can provide, so that the resources of the fog node device 110 can be obtained. Best use.

In other embodiments, after receiving the network addresses of multiple fog servers, the fog node device 110 may try to communicate with each of the multiple fog servers one by one.

In addition, as more and more IoT devices will be connected to the Internet, there may not be enough IPv4 addresses for future use. For this reason, an IPv6 address with a length of 128 bits (16 bytes) is used to solve the problem of IPv4 address exhaustion. Compared with IPv4 addresses, the address space of IPv6 is greatly increased, which can meet the future demand for network addressing. In the case where the fog server 130 adopts an IPv6 address, the DHCP fog server option may adopt the example format shown in FIG. 4.

As shown in FIG. 4, the fog server option 400 includes at least an option code 410, an option length 420, and a network address part 430. Option code 410 can be defined as any suitable decimal value. The option length 420 indicates the length of the network address part 430. The network address part 430 is used to carry the network addresses of one or more fog servers. In the example of FIG. 4, it is assumed that the fog server 140 adopts an IPv6 address, so the length of the network address of a single fog server 130 is 16 octets. Therefore, the length of the network address portion 430 is an integer multiple of 16 octets.

In an embodiment in which the communication system 100 includes a plurality of fog servers, the address management device 120 may add the network address of each of the plurality of fog servers to the network address part 430.

It can be understood that the DHCP client can use the Parameter Request List Option (Parameter Request List Option) to request the value of the specified configuration parameter from the DHCP server. The list of configuration parameters is specified as n octets (n is a natural number), where each octet is an option code of a predefined DHCP option. Therefore, the fog node device 110 including the DHCP client can add the option code of the DHCP fog server option to the parameter request list option, and add the parameter request list option to the DHCP discovery message or the DHCP request message, so as to include the DHCP server The address management device 120 requests the network address of the fog server 130. For example, the fog node device 110 may add the option code 310 of the DHCP fog server option 300 shown in FIG. 3 or the option code 410 of the DHCP fog server option 400 shown in FIG. 4 to the parameter request list option, and request the parameter The list option is added to the DHCP discovery message or the DHCP request message in order to request the address management device 120 for the network address of the fog server 130.

It should be understood that the fog node device 110 requesting the address management device 120 for the network address of the fog server 130 based on the DHCP protocol is only an example, and is not intended to limit the scope of the present disclosure. Depending on the specific implementation, the fog node device 110 may request the network address of the fog server 130 from the address management device 120 based on any appropriate communication protocol. For example, in the case where the address management device 120 includes a router, the fog node device 110 may request the network address of the fog server 130 by sending a route request (Router Solicitation, RS) message to the address management device 120. An indication of the request for the network address of the server 130. In response, the address management device 120 may provide the requested network address by sending a router advertisement (RA) message to the fog node device 110.

Continuing to refer to FIG. 2, based on the network address of the fog server 130 obtained from the address management device 120, the fog node device 110 sends 230 to the fog server 130 information related to the resources that the fog node device 110 can provide.

In some embodiments, the resources that the fog node device 110 can provide may include, but are not limited to: storage resources, computing resources, and services that the fog node device 110 can provide. The services that the fog node device 110 can provide may include, but are not limited to: video surveillance, video conversion, video compression, environmental monitoring, firewall functions, etc. in a specific area. For example, in an embodiment where the services that the fog node device 110 can provide include video surveillance services in a specific area, the information related to the resources that the fog node device 110 can provide may include the physical location information of the fog node device 110 and the fog node device 110 Information about video surveillance equipment (such as cameras).

After receiving the information about the resources that the fog node device 110 can provide, the fog server 130 may record the information of the fog node device 110 locally, so as to manage 240 the resources of the fog node device 110.

In some embodiments, after the fog server 130 receives the request to provide the service from the terminal device, it may determine 250 whether the fog node device 110 can provide the service based on the information related to the resources that the fog node device 110 can provide. If the fog server 130 determines that the fog node device 110 can provide the service, the fog server 130 sends 260 an instruction to provide the service to the terminal device to the fog node device 110. After the fog node device 110 receives the instruction, it uses the resources it can provide to provide the service to the terminal device. After providing the service to the terminal device, the fog node device 110 sends 270 a report to the fog server 130 to indicate the completion of the instruction. It should be understood that the services that the fog node device can provide also include the functions that the fog node device can provide, such as the video surveillance function of a specific area. In this regard, the service provision instruction sent by the fog server 130 to the fog node device 110 may also include an instruction to enable the fog node device 110 to provide a specific function.

In some embodiments, in order to enable the fog node device 110 to provide the service, the fog server 130 may push to the fog node device 110 the application code required to provide the service. After the fog node device 110 receives the application code, it provides the service by running the application code. In such an embodiment, the fog server 130 may send the instruction to provide the service and the application code required to provide the service to the fog node device 110 in parallel or sequentially.

FIG. 5 shows a flowchart of a method 500 implemented at a fog node device according to an embodiment of the present disclosure. For the convenience of description, the method 500 will be described below with reference to FIG. 1 and taking implementation at the fog node device 110 shown in FIG. 1 as an example. It should be understood that the method 500 may further include additional steps not shown and/or the shown steps may be omitted, and the scope of the present disclosure is not limited in this respect.

In block 510, a request for the network address of the fog server 130 is sent from the fog node device 110 to the address management device 120, and the fog server 130 is configured to manage the fog node device 110.

At block 520, the network address of the fog server 130 is received from the address management device 120.

In block 530, based on the network address, information related to the resources that the fog node device 110 can provide is sent from the fog node device 110 to the fog server 130.

In some embodiments, the fog node device 110 includes a Dynamic Host Configuration Protocol DHCP client, and the address management device 120 includes a DHCP server.

In some embodiments, sending a request for a network address to the address management device 120 includes sending a DHCP discovery message or a DHCP request message to the address management device 120, the DHCP discovery message and the DHCP request message each including an indication of the request for the network address.

In some embodiments, the address management device 120 includes a router.

In some embodiments, sending a request for a network address to the address management device 120 includes sending a route request message to the address management device 120, and the route request message includes an indication of the request for the network address.

In some embodiments, the method 500 further includes: receiving an instruction to provide a service to the terminal device from the fog server 130, and the service is determined based on information about the resource that the fog node device 110 can provide; and using the resource to provide a service to the terminal device.

In some embodiments, providing a service to a terminal device includes: receiving application code required to provide the service from the fog server 130; and providing the service by running the application code.

FIG. 6 shows a flowchart of a method 600 implemented at an address management device according to an embodiment of the present disclosure. For the convenience of description, the method 600 will be described below with reference to FIG. 1 and taking the implementation at the address management device 120 shown in FIG. 1 as an example. It should be understood that the method 600 may further include additional steps not shown and/or the shown steps may be omitted, and the scope of the present disclosure is not limited in this respect.

In block 610, the address management device 120 receives a request for the network address of the fog server 130 from the fog node device 110, and the fog server 130 is configured to manage the fog node device 110.

In block 620, the address management device 120 sends the network address of the fog server 130 to the fog node device 110.

In some embodiments, receiving a request for a network address from the fog node device 110 includes: receiving a DHCP discovery message or a DHCP request message from the fog node device 110, the DHCP discovery message and the DHCP request message each including an indication of the request for the network address.

In some embodiments, the address management device 120 includes a router.

In some embodiments, receiving a request for a network address from the fog node device 110 includes: receiving a routing request message from the fog node device 110, the routing request message including an indication of the request for the network address.

FIG. 7 shows a flowchart of a method 700 implemented at a fog server according to an embodiment of the present disclosure. For the convenience of description, the method 700 will be described below with reference to FIG. 1 and taking the implementation at the fog server 130 shown in FIG. 1 as an example. It should be understood that the method 700 may further include additional steps not shown and/or the shown steps may be omitted, and the scope of the present disclosure is not limited in this respect.

In block 710, the fog server 130 receives information related to the resources that the fog node device 110 can provide from the fog node device 110.

In block 720, the fog node device 110 is managed based on the information related to the resource.

In some embodiments, the method 700 further includes: in response to receiving a request to provide a service from the terminal device, determining whether the fog node device 110 can provide the service based on information related to the resource; and in response to determining that the fog node device 110 can provide the service , Send an instruction to provide service to the terminal device to the fog node device 110.

In some embodiments, the method 700 further includes: sending to the fog node device 110 application program codes required to provide services.

It should be understood that the operations and related features performed by the fog node device 110, the address management device 120, and the fog server 130 described above in conjunction with FIGS. 1 to 4 are also applicable to the

methods

500, 600, and 700, and have the same effect. The specific details will not be repeated.

In some embodiments, a device capable of executing the method 500 (for example, the fog node device 110) may include corresponding components for executing each step of the method 500. These components can be implemented in any suitable way. For example, it can be implemented by a circuit or a software module.

In some embodiments, the apparatus includes: means for sending a request for the network address of the fog server from the fog node device to the address management device, the fog server is configured to manage the fog node device; and for receiving fog from the address management device A component for the network address of the server; and a component for sending information about the resources that the fog node device can provide from the fog node device to the fog server based on the network address.

In some embodiments, the means for sending a request for a network address to an address management device includes: sending a DHCP discovery message or a DHCP request message to the address management device. The DHCP discovery message and the DHCP request message each include a request for a network address. Instructions.

In some embodiments, the address management device includes a router.

In some embodiments, the means for sending a request for a network address to the address management device includes: sending a route request message to the address management device, the route request message including an indication of the request for the network address.

In some embodiments, the apparatus further includes: a component for receiving an instruction to provide a service to a terminal device from the fog server, and the service is determined based on information about the resource that the fog node device can provide; and for using the resource to the terminal device. The parts of the equipment that provide services.

In some embodiments, the components used to provide services to the terminal device include: components used to receive application code required to provide services from the fog server; and components used to provide services by running the application code.

In some embodiments, a device capable of executing the method 600 (for example, the address management device 120) may include corresponding components for executing each step of the method 600. These components can be implemented in any suitable way. For example, it can be implemented by a circuit or a software module.

In some embodiments, the apparatus includes: means for receiving a request for the network address of the fog server from the fog node device at the address management device, the fog server being configured to manage the fog node device; and The fog node device sends the network address of the fog server.

In some embodiments, the means for receiving a request for a network address from the fog node device includes: receiving a DHCP discovery message or a DHCP request message from the fog node device, the DHCP discovery message and the DHCP request message each including a network address The indicated part of the request.

In some embodiments, the address management device includes a router.

In some embodiments, the means for receiving a request for a network address from the fog node device includes: a means for receiving a route request message from the fog node device, the route request message including an indication of the request for the network address.

In some embodiments, a device capable of executing the method 700 (for example, the fog server 130) may include corresponding components for executing each step of the method 700. These components can be implemented in any suitable way. For example, it can be implemented by a circuit or a software module.

In some embodiments, the apparatus includes: a component for receiving information related to resources that the fog node device can provide from the fog node device at the fog server; The part that the device manages.

In some embodiments, the apparatus further includes: in response to receiving a request to provide a service from the terminal device, a component for determining whether the fog node device can provide the service based on information related to the resource; and in response to determining the fog node A component that can provide services to the fog node device and send instructions to provide services to the terminal device.

In some embodiments, the apparatus further includes: a component for sending application code required to provide services to the fog node device.

FIG. 8 shows a block diagram of an electronic device 800 suitable for implementing embodiments of the present disclosure. The device 800 may be used to implement the fog node device, address management device, or fog server in the embodiments of the present disclosure, such as the fog node device 110, the address management device 120, and the fog server 130 shown in FIG. 1.

As shown in the example in FIG. 8, the electronic device 800 may include one or more processors 810, one or more memories 820 coupled to the processor 810, and one or more transmitters coupled to the processor 810 and/ Or the receiver (TX/RX) 840.

The processor 810 may be of any suitable type suitable for the local technical environment, and may include, but is not limited to, general-purpose computers, special-purpose computers, microcontrollers, digital signal controllers (DSP), and processors based on multi-core processor architecture. One or more. The electronic device 800 may have multiple processors, such as an application specific integrated circuit chip that is time-driven by a clock synchronized with the main processor.

The memory 820 may be of any suitable type suitable for the local technical environment, and may be implemented using any suitable data storage technology, as non-limiting examples, such as non-transitory computer-readable storage media, semiconductor-based storage devices, magnetic memory Components and systems, optical storage devices and systems, fixed storage and removable storage.

The memory 820 stores at least a part of the program 830. TX/RX 840 is used for two-way communication. The TX/RX 840 has at least one antenna to facilitate communication, but in practice the device may have several antennas. The communication interface can represent any interface required for communication with other network elements.

The program 830 may include program instructions that, when executed by the associated processor 810, enable the device 800 to operate according to an embodiment of the present disclosure, as described with reference to FIGS. 1 to 7. In other words, the embodiments of the present disclosure may be implemented by computer software executable by the processor 810 of the electronic device 800, or by hardware, or by a combination of software and hardware.

In general, the various exemplary embodiments of the present disclosure may be implemented in hardware or special purpose circuits, software, logic, or any combination thereof. Certain aspects may be implemented in hardware, while other aspects may be implemented in firmware or software that may be executed by a controller, microprocessor, or other computing device. When various aspects of the embodiments of the present disclosure are illustrated or described as block diagrams, flowcharts, or using some other graphical representation, it will be understood that the blocks, devices, systems, techniques, or methods described herein can be regarded as non-limiting Examples are implemented in hardware, software, firmware, dedicated circuits or logic, general-purpose hardware or controllers or other computing devices, or some combination thereof. Examples of hardware devices that can be used to implement the embodiments of the present disclosure include, but are not limited to: Field Programmable Gate Array (FPGA), Application Specific Integrated Circuit (ASIC), Application Specific Standard Product (ASSP), System on Chip (SOC), Complex Programmable Logic Device (CPLD), etc.

As an example, the embodiments of the present disclosure may be described in the context of machine-executable instructions, such as included in program modules executed in devices on a target's real or virtual processor. Generally speaking, program modules include routines, programs, libraries, objects, classes, components, data structures, etc., which perform specific tasks or implement specific abstract data structures. In various embodiments, the functions of the program modules may be combined or divided among the described program modules. The machine executable instructions for the program modules can be executed in local or distributed devices. In distributed devices, program modules can be located in both local and remote storage media.

The computer program code used to implement the method of the present disclosure can be written in one or more programming languages. These computer program codes can be provided to the processors of general-purpose computers, special-purpose computers, or other programmable data processing devices, so that when the program codes are executed by the computer or other programmable data processing devices, they will cause changes in the flowcharts and/or block diagrams. The functions/operations specified in are implemented. The program code can be executed entirely on a computer, partly on a computer, as a stand-alone software package, partly on a computer and partly on a remote computer, or entirely on a remote computer or server.

In the context of the present disclosure, a machine-readable medium may be any tangible medium that contains or stores a program for or related to an instruction execution system, apparatus, or device. The machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. The machine-readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, device, or device, or any suitable combination thereof. More detailed examples of machine-readable storage media include electrical connections with one or more wires, portable computer disks, hard disks, random memory access (RAM), read-only memory (ROM), erasable programmable read-only Memory (EPROM or flash memory), optical storage device, magnetic storage device, or any suitable combination thereof.

In addition, although the operations are depicted in a specific order, this should not be understood as requiring such operations to be completed in the specific order shown or in a sequential order, or to perform all illustrated operations to obtain desired results. In some cases, multitasking or parallel processing can be beneficial. Likewise, although the above discussion contains certain specific implementation details, this should not be construed as limiting the scope of any invention or claims, but as a description of specific embodiments that can be directed to specific inventions. Certain features that are described in this specification in the context of separate embodiments can also be implemented in combination in a single embodiment. Conversely, various features described in the context of a single embodiment can also be implemented in multiple embodiments separately or in any suitable subcombination.

Although the subject matter has been described in language specific to structural features and/or method actions, it should be understood that the subject matter defined in the appended claims is not limited to the specific features or actions described above. Rather, the specific features and actions described above are disclosed as example forms for implementing the claims.

Claims

An electronic device, including:

At least one processor; and

A memory coupled to the at least one processor, and the memory stores instructions that, when executed by the at least one processor, cause the electronic device to perform actions, and the actions include:

Sending a request for the network address of the fog server from the fog node device to an address management device, the fog server being configured to manage the fog node device;

Receiving the network address of the fog server from the address management device; and

Based on the network address, information related to the resources that the fog node device can provide is sent from the fog node device to the fog server.
The device according to claim 1, wherein the fog node device includes a Dynamic Host Configuration Protocol DHCP client, and the address management device includes a DHCP server.
The device according to claim 2, wherein sending the request for the network address to the address management device comprises:

Sending a DHCP discovery message or a DHCP request message to the address management device, where the DHCP discovery message and the DHCP request message each include an indication of the request for the network address.
The device of claim 1, wherein the address management device includes a router.
The device according to claim 4, wherein sending the request for the network address to the address management device comprises:

Send a route request message to the address management device, where the route request message includes an indication of the request for the network address.
The device of claim 1, wherein the action further comprises:

Receiving an instruction to provide a service to a terminal device from the fog server, the service being determined based on the information about the resource that the fog node device can provide; and

The resource is used to provide the service to the terminal device.
The device according to claim 6, wherein providing the service to the terminal device comprises:

Receiving the application code required to provide the service from the fog server; and

The service is provided by running the application code.
An electronic device, including:

At least one processor; and

A memory coupled to the at least one processor, and the memory stores instructions that, when executed by the at least one processor, cause the electronic device to perform actions, and the actions include:

At the address management device, receiving a request for the network address of the fog server from the fog node device, the fog server being configured to manage the fog node device; and

Sending the network address of the fog server to the fog node device.
The device according to claim 8, wherein the fog node device includes a Dynamic Host Configuration Protocol DHCP client, and the address management device includes a DHCP server.
The device according to claim 9, wherein receiving the request for the network address from the fog node device comprises:

A DHCP discovery message or a DHCP request message is received from the fog node device, where the DHCP discovery message and the DHCP request message each include an indication of the request for the network address.
The device of claim 8, wherein the address management device includes a router.
The device according to claim 11, wherein receiving the request for the network address from the fog node device comprises:

Receiving a routing request message from the fog node device, the routing request message including an indication of the request for the network address.
An electronic device, including:

At least one processor; and

A memory coupled to the at least one processor, and the memory stores instructions that, when executed by the at least one processor, cause the electronic device to perform actions, and the actions include:

At the fog server, receiving information related to the resources that the fog node device can provide from the fog node device; and

Based on the information related to the resource, the fog node device is managed.
The device of claim 13, wherein the action further comprises:

In response to receiving a request to provide a service from a terminal device, determine whether the fog node device can provide the service based on the information related to the resource; and

In response to determining that the fog node device can provide the service, sending an instruction to the fog node device to provide the service to the terminal device.
The device of claim 14, wherein the action further comprises:

Sending the application code required to provide the service to the fog node device.
A communication method including:

Sending a request for the network address of the fog server from the fog node device to an address management device, the fog server being configured to manage the fog node device;

Receiving the network address of the fog server from the address management device; and

Based on the network address, information related to the resources that the fog node device can provide is sent from the fog node device to the fog server.
The method according to claim 16, wherein the fog node device includes a Dynamic Host Configuration Protocol DHCP client, and the address management device includes a DHCP server.
18. The method of claim 17, wherein sending the request for the network address to the address management device comprises:

Sending a DHCP discovery message or a DHCP request message to the address management device, where the DHCP discovery message and the DHCP request message each include an indication of the request for the network address.
The method of claim 16, wherein the address management device includes a router.
The method of claim 19, wherein sending the request for the network address to the address management device comprises:

Send a route request message to the address management device, where the route request message includes an indication of the request for the network address.
The method of claim 16, further comprising:

Receiving an instruction to provide a service to a terminal device from the fog server, the service being determined based on the information about the resource that the fog node device can provide; and

The resource is used to provide the service to the terminal device.
The method of claim 21, wherein providing the service to the terminal device comprises:

Receiving the application code required to provide the service from the fog server; and

The service is provided by running the application code.
A communication method including:

At the address management device, receiving a request for the network address of the fog server from the fog node device, the fog server being configured to manage the fog node device; and

Sending the network address of the fog server to the fog node device.
The method according to claim 23, wherein the fog node device includes a Dynamic Host Configuration Protocol DHCP client, and the address management device includes a DHCP server.
The method of claim 24, wherein receiving the request for the network address from the fog node device comprises:

A DHCP discovery message or a DHCP request message is received from the fog node device, where the DHCP discovery message and the DHCP request message each include an indication of the request for the network address.
The method of claim 23, wherein the address management device includes a router.
The method of claim 26, wherein receiving the request for the network address from the fog node device comprises:

Receiving a routing request message from the fog node device, the routing request message including an indication of the request for the network address.
A communication method including:

At the fog server, receiving information related to the resources that the fog node device can provide from the fog node device; and

Based on the information related to the resource, the fog node device is managed.
The method of claim 28, further comprising:

In response to receiving a request to provide a service from a terminal device, determine whether the fog node device can provide the service based on the information related to the resource; and

In response to determining that the fog node device can provide the service, sending an instruction to the fog node device to provide the service to the terminal device.
The method of claim 29, further comprising:

Sending the application code required to provide the service to the fog node device.
A computer-readable medium having instructions stored on the computer-readable medium. When the instructions are executed by at least one processing unit of a machine, the machine implements the method described in any one of claims 16-22 method.
A computer-readable medium having instructions stored on the computer-readable medium. When the instructions are executed by at least one processing unit of a machine, the machine implements the method described in any one of claims 23-27 method.
A computer-readable medium having instructions stored on the computer-readable medium. When the instructions are executed by at least one processing unit of a machine, the machine realizes the method described in any one of claims 28-30 method.