A three-party communication system including an end device, an edge server for controlling the end device, and a cloud server, and an operating method thereof

Abstract

According to various embodiments, a three-way communication system including an end device, an edge server for controlling the end device, and a cloud server, and an operating method thereof, are configured such that during a connection between the edge server and the cloud server, the edge server wirelessly connects with at least one end device, the edge server determines a control command in cooperation with the cloud server, the edge server wirelessly transmits the control command to the end device, and the end device operates according to the control command.

Description

Technical Field

[0001] Various embodiments relate to a three-party communication system including an end device, an edge server for controlling the end device, and a cloud server, and an operation method thereof.

Background Art

[0002] Generally, various functions are added to an electronic device to perform complex functions. With the development of technology, the electronic device has come to be realized by a robot, which has come to process various tasks. The robot includes a drive module having a physical mechanism and a processor for controlling the drive module. The processor processes sensing data for the surrounding environment and determines control commands for the drive module. By driving the drive module according to the control commands, the robot can process tasks.

Summary of the Invention

Problems to be Solved by the Invention

[0003] The robot as described above drives independently and processes all control operations by itself. However, in order to ensure high-performance and high-precision driving of the robot, high performance of the processor is required. At this time, the higher the performance of the processor, the higher the manufacturing cost of the robot and the higher the power consumption. Furthermore, the higher the performance of the processor, the larger the size of the processor. As a result, it becomes difficult for a small-sized robot to drive with high performance and high precision.

Means for Solving the Problems

[0004] End devices according to various embodiments include a communication module configured to communicate wirelessly with an edge server managed by a cloud server, and a processor connected to the communication module, the processor being configured to receive control commands from the edge server via the communication module and to operate according to the control commands.

[0005] The operation methods of the end device according to various embodiments may include the steps of wirelessly connecting to an edge server managed by a cloud server, wirelessly receiving control commands from the edge server, and driving according to the control commands.

[0006] An edge server according to various embodiments includes at least one end device, a communication module configured to communicate with a cloud server configured to manage the edge server, and a processor connected to the communication module, the processor being configured to determine control commands for the end device, and the communication module being configured to wirelessly transmit the control commands to the end device.

[0007] The operation methods of the edge servers according to various embodiments may include the steps of wirelessly connecting to an end device, determining a control command for the end device, and wirelessly transmitting the control command to the end device, while connected to a cloud server configured to manage at least one edge server.

[0008] A cloud server according to various embodiments includes a communication module configured to communicate with at least one edge server configured to control at least one end device, and a processor coupled to the communication module, the processor of which the communication module may be configured to receive data related to the end device from the edge server and process the data.

[0009] The operation methods of the cloud server according to various embodiments may include the steps of connecting to at least one edge server configured to control at least one end device, receiving data associated with the end device from the edge server, and processing the data.

[0010] A communication system according to various embodiments includes at least one end device, at least one edge server configured to wirelessly control the end device, and a cloud server connected to the edge server and configured to manage the end device and the edge server, wherein the edge server is configured to determine control commands in cooperation with the cloud server and to wirelessly transmit the control commands to the end device, and the end device is configured to wirelessly receive the control commands from the edge server and to drive according to the control commands.

[0011] A method for driving a communication system according to various embodiments may include the steps of: the edge server wirelessly connecting to at least one end device during connection between the edge server and the cloud server; the edge server determining a control command in cooperation with the cloud server; the edge server wirelessly transmitting the control command to the end device; and the end device driving according to the control command. [Effects of the Invention]

[0012] In various embodiments, an edge server can act as the brain for at least one end device, enabling wireless control of the end device. That is, because the edge server processes control commands for the end device, the end device only needs to operate according to the commands, eliminating the need for high processing performance in the end device itself. This reduces the manufacturing cost of the end device and lowers its power consumption. Furthermore, high-performance and highly precise operation is possible regardless of the size of the end device. In addition, because the edge server can control a large number of end devices with its high processing performance, the communication system including the end devices and edge server can improve the efficiency of resource utilization, including cost and power. [Brief explanation of the drawing]

[0013] [Figure 1a] This diagram illustrates communication systems according to various embodiments. [Figure 1b] This figure shows a communication system according to one embodiment. [Figure 2a] This diagram illustrates the operation methods of communication systems according to various embodiments. [Figure 2b] This diagram illustrates the operation methods of communication systems according to various embodiments. [Figure 3a] This figure shows end devices according to various embodiments. [Figure 3b] Figure 3a shows a communication module according to one embodiment. [Figure 3c] This figure shows the processor of Figure 3a according to various embodiments. [Figure 3d] This figure shows the data generation unit of Figure 3c according to one embodiment. [Figure 4] This figure illustrates the operation methods of end devices according to various embodiments. [Figure 5a] This figure illustrates the operation of connecting to the edge server shown in Figure 4, according to various embodiments. [Figure 5b]It is a diagram showing an operation of transmitting first data to the edge server of FIG. 4 according to one embodiment. [Figure 5c] It is a diagram showing an operation of transmitting first data to the edge server of FIG. 4 according to one embodiment. [Figure 6a] It is a diagram showing edge servers according to various embodiments. [Figure 6b] It is a diagram showing the processor of FIG. 6a. [Figure 7a] It is a diagram showing an operation method of an edge server according to various embodiments. [Figure 7b] It is a diagram showing an operation method of an edge server according to one embodiment. [Figure 8a] It is a diagram showing cloud servers according to various embodiments. [Figure 8b] It is a diagram showing the processor of FIG. 8a. [Figure 9] It is a diagram showing an operation method of a cloud server according to various embodiments.

MODE FOR CARRYING OUT THE INVENTION

[0014] Hereinafter, various embodiments of the present invention will be described with reference to the accompanying drawings.

[0015] FIG. 1a is a diagram showing a communication system 100 according to various embodiments.

[0016] Referring to FIG. 1a, a communication system 100 according to various embodiments is a three-party communication system, and may include at least one end device 110, at least one edge server 120, and a cloud server 130.

[0017] The end device 110 is an electronic device, which may include a robot. The edge server 120 is an electronic device, which may act as the brain of the end device 110. That is, each edge server 120 may wirelessly control at least one end device 110. In this case, the edge server 120 may control the end device 110 based on a defined control cycle. The control cycle may be determined by the sum of the time given to process the data associated with the end device 110 and the time given to provide control commands to the end device 110. The cloud server 130 may manage at least one of the end devices 110 or the edge server 120. In this case, the edge server 120 may act as a server with respect to the end device 110 and as a client with respect to the cloud server 130.

[0018] The end device 110 and the edge server 120 may communicate wirelessly, and the edge server 120 and the cloud server 130 may communicate wired or wirelessly. In this case, the end device 110 and the edge server 120 may communicate via a wireless network capable of ultra-reliable and low latency communications (URLLC). The wireless network is characterized not only by its ultra-reliable and low latency capabilities, but also by its ability to handle high-speed, high-capacity (enhanced mobile broadband: eMBB) and massive machine-type communications (mMTC). Here, the wireless network may include at least one of the first wireless network or the second wireless network. The first wireless network may include a long-range wireless network, such as a 5G network, and the second wireless network may include a short-range wireless network, such as Wi-Fi 6 (Wi-Fi ad / ay). For example, the edge server 120 may include a MEC (mobile edge computing, multi-access edge computing) server and be located at a base station. This reduces the latency time caused by communication between the end device 110 and the edge server 120. In this case, the time available for providing control commands to the end device 110 in the control cycle of the edge server 120 is reduced, thereby increasing the time available for processing data. On the other hand, the edge server 120 and the cloud server 130 may communicate via a wireless network such as the internet.

[0019] In one embodiment, multiple edge servers 120 may be connected via a wireless mesh network, and the functions of the cloud server 130 may be distributed among the edge servers 120. In such a case, one of the edge servers 120 may act as an edge server 120 for a particular end device 110, and at least one of the edge servers 120 may cooperate with any one of the other edge servers 120 to act as a cloud server 130 for the end device 110.

[0020] Figure 1b is a diagram showing a communication system 100 according to one embodiment.

[0021] Referring to Figure 1b, the edge server 120 may include a first edge server 121 and a second edge server 123. Here, the first edge server 121 and the second edge server 123 may communicate with the cloud server 130, respectively. In addition, each end device 110 may communicate wirelessly with at least one of the first edge server 121 or the second edge server 123. The first edge server 121 may communicate with the end device 110 via a first wireless network, for example, a 5G network. The second edge server 123 may communicate with the end device 110 via a second wireless network, for example, Wi-Fi 6 (Wi-Fi ad / ay). In this case, the end device 110 may communicate with the first edge server 121 outside the communication area (A) of the second edge server 123. On the other hand, within the communicationable area (A) of the second edge server 123, the end device 110 may communicate with at least one of the first edge server 121 or the second edge server 123.

[0022] A three-party communication system 100 according to various embodiments may include at least one end device 110 configured to collect data, at least one edge server 120 configured to wirelessly control the end device 110, and a cloud server 130 configured to connect to the edge server 120 and manage the end device 110 and the edge server 120.

[0023] According to various embodiments, the edge server 120 may be configured to wirelessly receive data from the end device 110, determine a control command based on the data, and wirelessly transmit the control command to the end device 110.

[0024] According to one embodiment, the edge server 120 may include a first edge server 121 of a first wireless network and a second edge server 123 of a second wireless network.

[0025] For example, the first wireless network may be a long-range wireless network, and the second wireless network may be a short-range wireless network.

[0026] According to various embodiments, the end device 110 may be configured to wirelessly receive control commands from the edge server 120 and to drive according to the control commands.

[0027] According to one embodiment, the end device 110 may be configured to transmit data to either the first edge server 121 or the second edge server and to receive control commands wirelessly from either the first edge server 121 or the second edge server 123.

[0028] According to various embodiments, the edge server 120 may be configured to determine, based on data, whether cooperation with the cloud server 130 is necessary, and if it is determined that cooperation with the cloud server 130 is not necessary, to determine a control command within a predetermined control cycle and transmit the control command.

[0029] According to various embodiments, the edge server 120 may be configured to communicate with the cloud server 130 based on data and determine control commands when it determines that cooperation with the cloud server 130 is necessary.

[0030] According to one embodiment, the first edge server 121 may be configured to determine a control command based on data and to transmit the control command to the end device 110 via the first wireless network.

[0031] According to one embodiment, the second edge server 123 may be configured to determine, based on the data, whether cooperation with the cloud server 130 is necessary, and if it determines that cooperation with the cloud server 130 is not necessary, to determine a control command within a predetermined control cycle and to transmit the control command to the end device 110 via the second wireless network.

[0032] According to one embodiment, the second edge server 123 may be configured to communicate with the cloud server 130 based on data when it determines that cooperation with the cloud server 130 is necessary, to determine a control command, and to send the control command to the end device 110 via the second wireless network.

[0033] Figure 2a is a diagram illustrating the operation methods of the communication system 100 according to various embodiments.

[0034] Referring to Figure 2a, the edge server 120 may connect to the cloud server 130 in step 211 and to the end device 110 in step 213. The edge server 120 may connect to the end device 110 while connected to the cloud server 130. At this time, the edge server 120 may connect to the cloud server 130 by wire or wireless, and to the end device 110 by wireless. Here, the edge server 120 may connect to the end device 110 via a wireless network capable of ultra-high reliability low latency communication (URLLC).

[0035] In step 215, the end device 110 may transmit first data to the edge server 120. For this purpose, the end device 110 may collect first data. The first data may include at least one of the following: sensing data about the external environment of the end device 110, state data of the end device 110, or requirements for the operation of the end device 110. Here, the sensing data may include positioning data used to estimate the location of the end device 110 by indicating the distance between the end device 110 and a base station, for example, a Wi-Fi AP (access point).

[0036] In step 217, the edge server 120 may determine a control command for the end device 110. At this time, the edge server 120 may determine the control command based on first data. The control command may be for controlling the movement of the end device 110. After this, in step 219, the edge server 120 may send the control command to the end device 110. At this time, the edge server 120 may determine the control command based on first data and send the control command within a defined control cycle. The control cycle may be determined by the sum of the time required to determine the control command based on first data and the time required to send the control command to the end device 110. For example, if the defined control cycle is 5ms, the edge server 120 may determine the control command based on first data in 4ms and send the control command to the end device 110 in 1ms. Here, the edge server 120 may send the control command along with the map information associated with the end device 110.

[0037] In step 221, the end device 110 may be driven according to control commands. For example, the end device 110 may change its position or orientation by changing its motion.

[0038] Figure 2b is a diagram illustrating the operation methods of the communication system 100 in various embodiments.

[0039] Referring to Figure 2b, the edge server 120 may connect to the cloud server 130 in step 231 and to the end device 110 in step 233. The edge server 120 may connect to the end device 110 while connected to the cloud server 130. At this time, the edge server 120 may connect to the cloud server 130 by wire or wireless, and to the end device 110 by wireless. Here, the edge server 120 may connect to the end device 110 via a wireless network capable of ultra-high reliability low latency communication (URLLC).

[0040] In step 235, the end device 110 may transmit first data to the edge server 120. For this purpose, the end device 110 may collect first data. The first data may include at least one of the following: sensing data about the external environment of the end device 110, state data of the end device 110, or requirements for the operation of the end device 110. Here, the sensing data may include positioning data used to estimate the location of the end device 110, indicating the distance between the end device 110 and a base station, for example, a Wi-Fi AP.

[0041] In step 237, the edge server 120 may process the first data received from the end device 110. At this time, the edge server 120 may detect second data based on the first data. The second data may include at least one of the processing results for the first data or a query for the end device 110. After this, in step 239, the edge server 120 may send the second data to the cloud server 130.

[0042] In step 241, the cloud server 130 may process the second data received from the edge server 120. At this time, the cloud server 130 may detect third data corresponding to the second data. The third data may include at least one of the processing results for the second data or a response to a request for the end device 110. Here, the cloud server 130 may use a machine-learned model to detect the third data from the second data. Additionally, the cloud server 130 may perform machine learning on the second data and update the machine-learned model. According to one embodiment, in step 243, the cloud server 130 may send the third data to the edge server 120.

[0043] In step 245, the edge server 120 may determine a control command for the end device 110. At this time, the edge server 120 may determine the control command based on at least one of the first data or the third data. According to one embodiment, the edge server 120 may determine the control command based on the third data received from the cloud server 130. The control command may be for controlling the movement of the end device 110, or it may be for updating software. According to another embodiment, the edge server 120 may process the second data. At this time, the edge server 120 may detect the third data based on the second data and determine a control command based on the third data. Here, the edge server 120 may use a machine-learned model to detect the third data from the second data. Additionally, the edge server 120 may perform machine learning on the second data and update the machine-learned model. The control command may be for controlling the movement of the end device 110. Subsequently, in step 247, the edge server 120 may send a control command to the end device 110. Here, the edge server 120 may send the control command along with the map information associated with the end device 110.

[0044] In step 249, the end device 110 may be driven according to control commands. For example, the end device 110 may change its position or orientation by changing its motion, and its software may be updated.

[0045] The driving method of the three-party communication system 100 according to various embodiments may include the steps of: the edge server 120 wirelessly connecting with at least one end device 110 during connection between the edge server 120 and the cloud server 130; the end device 110 collecting data; the end device 110 wirelessly transmitting data to the edge server 120; the edge server 120 determining a control command based on the data; the edge server 120 wirelessly transmitting a control command to the end device 110; and the end device 110 driving according to the control command.

[0046] According to one embodiment, the edge server 120 may include a first edge server 121 of a first wireless network and a second edge server 123 of a second wireless network.

[0047] For example, the first wireless network may be a long-range wireless network, and the second wireless network may be a short-range wireless network.

[0048] According to one embodiment, the method for driving the three-party communication system 100 may further include the steps of: the first edge server 121 receiving data from the end device 110; the first edge server 121 determining a control command based on the data; and the first edge server 121 transmitting a control command to the end device 110 via the first wireless network.

[0049] According to one embodiment, the method for driving the three-party communication system 100 may further include the steps of: the second edge server 123 receiving data from the end device 110; the second edge server 123 determining whether cooperation with the cloud server 130 is necessary based on the data; if it is determined that cooperation with the cloud server 130 is not necessary, the second edge server 123 determining a control command within a defined control cycle; and the second edge server 123 transmitting a control command to the end device 110 via the second wireless network.

[0050] According to one embodiment, the method for driving the three-party communication system 100 may further include the steps of: when it is determined that cooperation with the cloud server 130 is necessary, the second edge server 123 communicates with the cloud server 130 based on the data to determine a control command; and the second edge server 123 transmits the control command to the end device 110 via the second wireless network.

[0051] Figure 3a shows an end device 110 according to various embodiments, Figure 3b shows a communication module 340 of Figure 3a according to one embodiment, Figure 3c shows a processor 360 of Figure 3a according to various embodiments, and Figure 3d shows a data generation unit 361 of Figure 3c according to one embodiment.

[0052] Referring to Figure 3a, the end device 110 according to various embodiments is an electronic device that may include at least one of the following: a sensor module 310, a camera module 320, a drive module 330, a communication module 340, a memory 350, or a processor 360. In one embodiment, at least one of the components of the end device 110, for example, the camera module 320, may be omitted, or at least one other component may be added. In one embodiment, at least two of the components of the end device 110 may be implemented in a single integrated circuit. In this case, the end device 110 may be a robot.

[0053] The sensor module 310 may sense the external environmental conditions of the end device 110 and generate corresponding sensing data. For example, the sensor module 310 may include a distance sensor, gesture sensor, gyro sensor, barometric pressure sensor, magnetic sensor, acceleration sensor, grip sensor, proximity sensor, color sensor, IR (infrared) sensor, biosensor, temperature sensor, humidity sensor, or illuminance sensor. As an example, the distance sensor may include at least one of the following: a sonar sensor, a ToF (time of flight) sensor, an LRF (laser range finder) sensor, or an IMU (inertial measurement unit) sensor.

[0054] The camera module 320 may capture images. For example, the camera module 320 may include at least one of the following: at least one lens, an image sensor, an image signal processor, or a flash.

[0055] The drive module 330 may enable the physical operation, i.e., motion, of the end device 110. According to one embodiment, the drive module 330 may move the position or change the orientation of the end device 110. For example, the drive module 330 may include at least one of a wheel mechanism, a joint mechanism, or an actuator. An actuator is a device for controlling the position, speed, force, etc., of a wheel mechanism or joint mechanism, and may include, for example, a motor or an encoder. According to another embodiment, the drive module 330 may output information. For example, the drive module 330 may include at least one of a display module or an audio output module.

[0056] The communication module 340 may support wireless communication between the end device 110 and an external device. Here, the communication module 340 may support the establishment of a wireless communication channel with the external device and the execution of communication via the communication channel based on a predetermined communication scheme. In this case, the communication module 340 may communicate with the edge server 120 via a wireless network capable of ultra-high reliability low latency communication (URLLC). The wireless network may include at least one of a first wireless network, such as a 5G network, or a second wireless network, such as Wi-Fi 6 (Wi-Fi ad / ay). The communication module 340 may verify and authenticate the end device 110 using recorded identification information.

[0057] According to one embodiment, the communication module 340 may include a first communication module 341 and a second communication module 343, as shown in Figure 3b. The first communication module 341 may communicate with a first edge server 121 via a first wireless network, for example, a 5G network. The second communication module 343 may communicate with a second edge server 123 via a second wireless network, for example, Wi-Fi 6 (Wi-Fi ad / ay).

[0058] Memory 350 may record data used by at least one of the components of the end device 110. The data may include input or output data for program 351 and its associated instructions. For example, memory 350 may record parameters and dynamic model information for the motion of the end device 110. Memory 350 may include volatile or non-volatile memory. Program 351 may be recorded in memory 350 as software and may include an operating system that controls the resources of the end device 110.

[0059] The processor 360 may control the overall operation of the end device 110. The processor 360 may communicate with the edge server 120 via the communication module 340. At this time, the processor 360 may transmit the collected first data to the edge server 120. The first data may include at least one of the following: sensing data about the external environment of the end device 110, state data of the end device 110, or requests required for the operation of the end device 110. Here, the sensing data may include positioning data used to estimate the location of the end device 110 by indicating the distance between the end device 110 and a base station, for example, a Wi-Fi AP. The processor 360 may also be driven according to control instructions received from the edge server 120. The processor 360 may drive the drive module 330 according to the control instructions. Alternatively, the processor 360 may update the software of the memory 350 according to the control instructions.

[0060] According to various embodiments, the processor 360 may include a data generation unit 361 and a data transmission unit 365, as shown in Figure 3c. The data generation unit 361 may generate first data. The data transmission unit 365 may transmit the first data to the edge server 120. At this time, the data transmission unit 365 may transmit the first data to the edge server 120 via a communication module 340. At this time, the data transmission unit 365 may schedule the transmission for the first data.

[0061] According to one embodiment, the data generation unit 361 may classify the first data while generating it. The data generation unit 361 may classify the first data based on at least one of the first data or a control command received from the edge server 120 in response to the first data. Here, the data generation unit 361 may classify the first data depending on whether at least one of the first data or a control command requires low-latency transmission or high-volume transmission. If at least one of the first data or a control command requires low-latency transmission, the data generation unit 361 may classify the first data into a first type. On the other hand, if at least one of the first data or a control command requires high-volume transmission, the data generation unit 361 may classify the first data into a second type. For example, if the first data includes positioning data, or if a control command received in response to the first data is received along with map information, the data generation unit 361 may classify the first data as a second type; otherwise, the data generation unit 361 may classify the first data as a first type. As a result, the data transmission unit 365 may transmit the first data of the first type to the first edge server 121 via the first communication module 341. Alternatively, the data transmission unit 365 may transmit the second data of the second type to the second edge server 123 via the second communication module 343. In this case, if both the first data of the first type and the first data of the second type exist, the data transmission unit 365 may determine the transmission priority for the first data of the first type and the first data of the second type, and schedule the transmissions based on this priority.

[0062] In other embodiments, the data generation unit 361 may include a first data generation unit 362 and a second data generation unit 363. The first data generation unit 362 may generate first data of a first type. In this case, if low-latency transmission is required for at least one of the first data to be generated or the control command received by the edge server 120 in response to the first data to be generated, the first data generation unit 362 may generate the relevant first data. The second data generation unit 363 may generate first data of a second type. In this case, if high-capacity transmission is required for at least one of the first data to be generated or the control command received by the edge server 120 in response to the first data to be generated, the second data generation unit 363 may generate the relevant first data. As a result, the data transmission unit 365 may transmit the first type of first data to the first edge server 121 via the first communication module 341. Alternatively, the data transmission unit 365 may transmit the second type of second data to the second edge server 123 via the second communication module 343. In this case, if both the first type of first data and the second type of first data exist, the data transmission unit 365 may determine the transmission priority for the first type of first data and the second type of first data, and schedule the transmissions based on this priority.

[0063] The end device 110 according to various embodiments may include a communication module 340 configured to communicate wirelessly with an edge server 120 managed by a cloud server 130, and a processor 360 connected to the communication module 340.

[0064] According to one embodiment, the edge server 120 may include a first edge server 121 of a first wireless network and a second edge server 123 of a second wireless network.

[0065] For example, the first wireless network may be a long-range wireless network, and the second wireless network may be a short-range wireless network.

[0066] According to various embodiments, the processor 360 may be configured to receive control commands from the edge server 120 via the communication module 340 and to drive according to the control commands.

[0067] According to various embodiments, the end device 110 may further include a drive module 330 configured to perform physical operations.

[0068] According to various embodiments, the processor 360 may be configured to drive the drive module 330 according to control instructions.

[0069] According to various embodiments, the end device 110 may further include a sensing module 310 configured to collect data.

[0070] According to various embodiments, the processor 360 may be configured to transmit data to the edge server 120 via the communication module 340.

[0071] According to one embodiment, the processor 360 may be configured to generate data, transmit the data to either the first edge server 121 or the second edge server 123 via the communication module 340, and receive control commands from either the first edge server 121 or the second edge server 123 via the communication module 340.

[0072] For example, the processor 360 may be configured to determine which of the first or second wireless network is suitable for transmitting data, based on at least one of the following: the type of data, the resources required to transmit the data, or the resources required for the control instructions received in response to the data.

[0073] As an example, the processor 360 may include a data generation unit 361 configured to generate data and classify it into at least one of a first type corresponding to a first wireless network or a second type corresponding to a second wireless network, and a data transmission unit 365 configured to transmit the first type of data to a first edge server 121 via the first wireless network and the second type of data to a second edge server 123 via the second wireless network.

[0074] As another example, the processor 360 may include a first data generation unit 362 configured to generate a first type of data corresponding to a first wireless network, a second data generation unit 363 configured to generate a second type of data corresponding to a second wireless network, and a data transmission unit 365 configured to transmit the first type of data to a first edge server 121 via the first wireless network and the second type of data to a second edge server 123 via the second wireless network.

[0075] According to various embodiments, the processor 360 may be configured to detect a failure in the wireless connection state with the edge server 120 via the communication module 340 and to stop operating.

[0076] According to various embodiments, the processor 360 may be configured to detect fault resolution by the communication module 340 and to wait for control commands to be received by the communication module 340.

[0077] According to various embodiments, the processor 360 may be configured to update software in accordance with control instructions.

[0078] Figure 4 shows the operation methods of the end device 110 in various embodiments.

[0079] Referring to Figure 4, in step 411, the end device 110 may be connected to the edge server 120. The processor 360 may be connected to the edge server 120 by the communication module 340. In this case, the communication module 340 may be connected to the edge server 120 via a wireless network capable of ultra-high reliability low latency communication (URLLC). The wireless network may include at least one of the first wireless network or the second wireless network. The first wireless network may include a long-range wireless network, such as a 5G network, and the second wireless network may include a short-range wireless network, such as Wi-Fi 6 (Wi-Fi ad / ay).

[0080] In one embodiment, the edge server 120 may include a first edge server 121 of a first wireless network and a second edge server 123 of a second wireless network. Furthermore, the communication module 340 of the end device 110 may include a first communication module 341 for communicating with the first wireless network and a second communication module 343 for communicating with the second wireless network. In this case, the end device 110 may be connected to the first edge server 121 outside the communicationable area (A) of the second edge server 123. At this time, the processor 360 may be connected to the first edge server 121 via the first communication module 341. Conversely, within the communicationable area (A) of the second edge server 123, the end device 110 may be connected to both the first edge server 121 and the second edge server 123, respectively. At this time, the processor 360 may be connected to the first edge server 121 by the first communication module 341 and to the second edge server 123 by the second communication module 343.

[0081] In step 413, the end device 110 may generate first data. The first data may include at least one of the following: sensing data about the external environment of the end device 110, state data of the end device 110, or requirements for the operation of the end device 110. Here, the sensing data may include positioning data used to estimate the location of the end device 110, indicating the distance between the end device 110 and a base station, e.g., a Wi-Fi AP. The processor 360 may collect sensing data using the sensing module 310 or the camera module 320. For example, the state data may include at least one of the following: identification information of the end device 110, state information of a battery (not shown), or state information of the drive module 330 (e.g., idle or working). The processor 360 may collect positioning data using the communication module 340. For example, the processor 360 may calculate the distance between the end device 110 and the base station based on the strength of the signal received from the base station. According to one embodiment, the processor 360 may mosaic or blow out areas associated with people in the video captured by the camera module 320 and generate them as first data.

[0082] In step 415, the end device 110 may transmit the first data to the edge server 120. The processor 360 may transmit the first data to the edge server 120 via the communication module 340. At this time, the processor 360 may transmit the first data to the edge server 120 via a first wireless network, such as a 5G network, or a second wireless network, such as Wi-Fi 6 (Wi-Fi ad / ay).

[0083] According to one embodiment, the processor 360 may transmit first data to either the first edge server 121 or the second edge server 123. To this end, the processor 360 may decide, based on the first data, whether to transmit the first data to the first edge server 121 or to the second edge server 123. For example, the processor 360 may determine which of the first wireless network or the second wireless network is suitable for transmitting the first data, based on at least one of the following: the type of data for the first data, the resources required to transmit the first data, or the resources required for the control instruction received in response to the first data. As a result, the processor 360 may transmit the first data to the first edge server 121 via the first wireless network or to the second edge server 123 via the second wireless network. This will be explained in more detail with reference to Figures 5b and 5c.

[0084] In step 417, the end device 110 may receive a control command from the edge server 120. The processor 360 may receive a control command from the edge server 120 via the communication module 340. At this time, the processor 360 may receive the control command from the edge server 120 via a first wireless network, such as a 5G network, or a second wireless network, such as Wi-Fi 6 (Wi-Fi ad / ay). Here, the processor 360 may receive the control command along with the map information associated with the end device 110.

[0085] According to one embodiment, the processor 360 may receive a control instruction from either the first edge server 121 or the second edge server 123. In this case, if the first data is transmitted to the first edge server 121, the processor 360 may receive a control instruction from the first edge server 121. On the other hand, if the first data is transmitted to the second edge server 123, the processor 360 may receive a control instruction from the second edge server 123.

[0086] In step 419, the end device 110 may be driven according to a control instruction. The processor 360 may control at least one of the components of the end device 110 according to the control instruction.

[0087] According to one embodiment, the processor 360 may drive the drive module 330 according to a control instruction. For example, the control instruction may include at least one position coordinate or velocity value relative to the movement path or target position of the end device 110. When the control instruction includes a position coordinate, the processor 360 may drive the drive module 330 to move the end device 110 to the position coordinate of the control instruction. When the control instruction includes a velocity value, the processor 360 may drive the drive module 330 to move the end device 110 according to the velocity value of the control instruction. As another example, the control instruction may include an operation variable for using the end device 110 to process a task, and the processor 360 may drive the drive module 330 and control the joint mechanism based on the operation variable to cause the end device 110 to process the task. Here, the processor 360 may control the drive based on sensing data collected by the sensor module 310 or camera module 320 while the drive module 330 is being driven. For example, if an obstacle is detected in the movement path of the end device 110 from the sensing data, the processor 360 may move the end device 110 to avoid the obstacle.

[0088] In another embodiment, the processor 360 may update the software according to a control instruction. For example, if the control instruction includes update information, the processor 360 may use the update information to update the software in the memory 350.

[0089] Figure 5a is a diagram showing the connection operation with the edge server 120 in Figure 4, and is a diagram showing a part of the embodiment of step 411 in Figure 4.

[0090] Referring to Figure 5a, in step 511, the end device 110 may determine the connection status with the edge server 120. At this time, if the communication module 340 is connected to the edge server 120 via a wireless network, the processor 360 may continue to monitor the connection status with the edge server 120 via the communication module 340. For example, the processor 360 may detect at least one of the reception status or reception strength of a reference signal transmitted from the edge server 120.

[0091] In step 513, the end device 110 may determine whether a fault has been detected based on the connection status with the edge server 120. For example, if the reference signal transmitted from the edge server 120 is not received, or if the received signal strength is below a defined threshold, the processor 360 may detect a fault.

[0092] If no fault is detected in step 513, the end device 110 may return to Figure 4 and proceed to step 413. For example, even if a fault is detected in step 513, the processor 360 may ignore the fault if it is resolved within a specified time. If the processor 360 is operating in accordance with previously received control instructions, it may ignore the fault and continue operating.

[0093] On the other hand, if a fault is detected in stage 513, the end device 110 may stop in stage 515. For example, if the fault persists for a predetermined period of time from the time it was detected, the processor 360 may determine that a fault has been detected. As a result, if the end device 110 is operating according to a previously received control instruction, the processor 360 may stop operating. In stage 517, the end device 110 may determine whether the fault has been resolved. At this time, while the operation is stopped, the processor 360 may continue to monitor the connection status with the edge server 120 using the communication module 340. For example, if a reference signal transmitted from the edge server 120 is received or the received strength is above a threshold, the processor 360 may determine that the fault has been resolved. If the fault is not resolved in stage 517, the end device 110 may return from stage 511 to stage 515 and continue to stop.

[0094] On the other hand, if the fault is resolved in step 517, the end device 110 may return to step 413 in Figure 4.

[0095] In one embodiment, the edge server 120 may include a first edge server 121 of a first wireless network and a second edge server 123 of a second wireless network. The communication module 340 of the end device 110 may include a first communication module 341 for communicating with the first wireless network and a second communication module 343 for communicating with the second wireless network. In this case, the processor 360 may monitor the connection status of the first edge server 121 and the second edge server 123, respectively. At this time, the processor 360 may monitor the connection status with the first edge server 121 using the first communication module 341 and the connection status with the second edge server 123 using the second communication module 343. This makes it possible for the processor 360 to be connected to at least one of the first edge server 121 or the second edge server 123.

[0096] Figure 5b is a diagram showing an example of the operation of transmitting first data to the edge server 120 in Figure 4 in one embodiment. Figure 5b may show a part of the embodiment of step 415 in Figure 4. According to one embodiment, the edge server 120 may include a first edge server 121 of the first wireless network and a second edge server 123 of the second wireless network. In addition, the communication module 340 of the end device 110 may include a first communication module 341 for communicating with the first wireless network and a second communication module 343 for communicating with the second wireless network.

[0097] Referring to Figure 5b, in step 512, the end device 110 may determine whether low-latency transmission is required for the first data. The processor 360 may determine whether low-latency transmission is required for the first data, or whether high-capacity transmission is required in addition to low-latency transmission, based on at least one of the first data or a control instruction received from the edge server 120 in response to the first data. For example, the processor 360 may determine whether low-latency transmission is required or high-capacity transmission is required for the first data based on the type of data for the first data, the resources required for transmitting the first data, etc. For example, if the first data includes positioning data, or if the control instruction received in response to the first data is received together with map information, the processor 360 may determine that high-capacity transmission is required for the first data; otherwise, it may determine that low-latency transmission is required for the first data.

[0098] If it is determined in step 521 that low-latency transmission is required for the first data, then in step 527, the end device 110 may transmit the first data to the first edge server 121. The processor 360 may transmit the first data to the first edge server 121 via the first wireless network. At this time, the processor 360 may transmit the first data to the first edge server 121 via the first communication module 341. After this, the end device 110 may return to Figure 4 and proceed to step 417.

[0099] On the other hand, if it is determined in step 521 that the first data requires high-capacity transmission rather than low-latency transmission, then in step 523, the end device 110 may determine whether it is connected to the second edge server 123. The processor 360 may check the connection status with the second edge server 123 via the second wireless network. At this time, the processor 360 may check the connection status with the second edge server 123 using the second communication module 343. This makes it possible for the processor 360 to determine whether the connection with the second edge server 123 is maintained.

[0100] If it is determined in step 523 that the end device 110 is connected to the second external server 123, then in step 525, the end device 110 may send the first data to the second edge server 123. The processor 360 may send the first data to the second edge server 123 via the second wireless network. At this time, the processor 360 may send the first data to the second edge server 123 via the second communication module 343. After this, the end device 110 may return to Figure 4 and proceed to step 417.

[0101] On the other hand, if it is determined in step 523 that the end device 110 is not connected to the second edge server 123, then in step 527, the end device 110 may send the first data to the first edge server 121. The processor 360 may send the first data to the first edge server 121 via the first wireless network. At this time, the processor 360 may send the first data to the first edge server 121 via the first communication module 341. In other words, since the end device 110 is not connected to the second edge server 123, even if the first data requires a larger data transmission than low-latency transmission, the processor 360 can send the first data to the first edge server 121. After this, the end device 110 may return to Figure 4 and proceed to step 417.

[0102] Figure 5c is a diagram showing another example of the first data transmission operation to the edge server 120 of Figure 4 in one embodiment. According to one embodiment, the edge server 120 may include a first edge server 121 of a first wireless network and a second edge server 123 of a second wireless network. Also, the communication module 340 of the end device 110 may include a first communication module 341 for communicating with the first wireless network and a second communication module 343 for communicating with the second wireless network.

[0103] Referring to Figure 5c, in step 531, the end device 110 may determine whether low-latency transmission is required for the first data. The processor 360 may determine, based on at least one of the first data or a control instruction received from the edge server 120 in response to the first data, whether low-latency transmission is required for the first data or whether high-capacity transmission is required in addition to low-latency transmission. For example, the processor 360 may determine whether low-latency transmission is required for the first data or high-capacity transmission is required based on the type of data for the first data, the resources required for transmitting the first data, etc. For example, if the first data includes positioning data, or if the control instruction received in response to the first data is received together with map information, the processor 360 may determine that high-capacity transmission is required for the first data; otherwise, it may determine that low-latency transmission is required for the first data.

[0104] If it is determined in step 531 that low-latency transmission is required for the first data, then in step 537, the end device 110 may transmit the first data to the first edge server 121. The processor 360 may transmit the first data to the first edge server 121 via the first wireless network. At this time, the processor 360 may transmit the first data to the first edge server 121 via the first communication module 341. After this, the end device 110 may return to Figure 4 and proceed to step 417.

[0105] On the other hand, if it is determined in step 531 that the first data requires high-capacity transmission rather than low-latency transmission, then in step 533, the end device 110 may determine whether it is connected to the second edge server 123. The processor 360 may check the connection status with the second edge server 123 via the second wireless network. At this time, the processor 360 may check the connection status with the second edge server 123 using the second communication module 343. This makes it possible for the processor 360 to determine whether the connection with the second edge server 123 is maintained.

[0106] If a connection with the second external server 123 is determined in step 533, then in step 535, the end device 110 may send the first data to the second edge server 123. The processor 360 may send the first data to the second edge server 123 via the second wireless network. At this time, the processor 360 may send the first data to the second edge server 123 via the second communication module 343. After this, the end device 110 may return to Figure 4 and proceed to step 417.

[0107] On the other hand, if it is determined in step 533 that the end device 110 is not connected to the second edge server 123, the end device 110 may wait until it is connected to the second edge server 123. The processor 360 may wait without transmitting the first data until it is reconnected to the second edge server 123. If it is determined in step 533 that the end device 110 is connected to the second edge server 123, then in step 535, the end device 110 may transmit the first data to the second edge server 123. The processor 360 may transmit the first data to the second edge server 123 via the second wireless network. At this time, the processor 360 may transmit the first data to the second edge server 123 via the second communication module 343. That is, if the first data requires high-capacity transmission in addition to low-latency transmission, the processor 360 may transmit the first data only to the second edge server 123. After this, the end device 110 may return to Figure 4 and proceed to step 417.

[0108] The operation method of the end device 110 according to various embodiments may include the steps of wirelessly connecting to an edge server 120 managed by a cloud server 130, wirelessly receiving control commands from the edge server 120, and driving according to the control commands.

[0109] According to one embodiment, the edge server 120 may include a first edge server 121 of a first wireless network and a second edge server 123 of a second wireless network.

[0110] For example, the first wireless network may be a long-range wireless network, and the second wireless network may be a short-range wireless network.

[0111] According to various embodiments, the end device 110 may include a drive module 330 configured to perform physical operations.

[0112] According to various embodiments, the driving step may include a step of driving the drive module 330 in accordance with a control command.

[0113] According to various embodiments, the receiving step may include a step of collecting data, a step of wirelessly transmitting data to the edge server 120, and a step of wirelessly receiving control commands generated based on the data from the edge server 120.

[0114] According to one embodiment, the receiving step may include the steps of generating data, transmitting the data to either the first edge server 121 or the second edge server 123, and wirelessly receiving a control command from either the first edge server 121 or the second edge server 123. For example, the receiving step may further include the step of determining which of the first wireless network or the second wireless network is suitable for transmitting the data, based on at least one of the following: the type of data, the resources required to transmit the data, or the resources required for the control command received in response to the data.

[0115] For example, the generation step may further include a step of generating data and classifying the data into at least one of a first type corresponding to a first wireless network or a second type corresponding to a second wireless network, and the transmission step may include a step of transmitting the first type data to a first edge server via the first wireless network and a step of transmitting the second type data to a second edge server via the second wireless network.

[0116] As another example, the generation stage may include the stage of generating a first type of data corresponding to a first wireless network and the stage of generating a second type of data corresponding to a second wireless network, and the transmission stage may include the stage of transmitting the first type of data to a first edge server via the first wireless network and the stage of transmitting the second type of data to a second edge server via the second wireless network.

[0117] According to various embodiments, the method may further include the steps of detecting a failure in the wireless connection state with the edge server 120, and stopping the operation.

[0118] According to various embodiments, the method may further include the steps of detecting the resolution of a fault and waiting to receive a control command.

[0119] According to various embodiments, the driving step may include a step of updating the software in accordance with control commands.

[0120] Figure 6a shows an edge server 120 according to various embodiments, and Figure 6b shows the processor 630 of Figure 6a.

[0121] Referring to Figure 6a, the edge server 120 according to various embodiments may include at least one of the following: a communication module 610, a memory 620, or a processor 630. In one embodiment, at least one of the components of the edge server 120 may be omitted, or at least one other component may be added. In one embodiment, at least two of the components of the edge server 120 may be implemented in a single integrated circuit. In this case, the edge server 120 may operate as a server to the end device 110 and as a client to the cloud server 130. The edge server 120 may also operate as the brain of the end device 110 to control the end device 110.

[0122] The communication module 610 may support communication between the edge server 120 and an external device. Here, the communication module 610 may support the establishment of a communication channel with the external device and the execution of communication over the communication channel. In this case, the communication module 610 may include a first communication module and a second communication module. The first communication module may communicate with the end device 110 via a wireless network capable of ultra-high reliability low latency communication (URLLC). The wireless network may include at least one of the first wireless network or the second wireless network. The first wireless network may include a long-range wireless network, such as a 5G network, and the second wireless network may include a short-range wireless network, such as Wi-Fi 6 (Wi-Fi ad / ay). The second communication module may communicate with the cloud server 130. For example, the second communication module may communicate with the cloud server 130 via the internet. Here, the first communication module and the second communication module may be integrated into one component (e.g., a single chip) or implemented in separate components (e.g., multiple chips). The communication module 610 may use the recorded identification information to verify and authenticate the edge server 120.

[0123] According to one embodiment, the edge server 120 may be either the first edge server 121 or the second edge server 123. If the edge server 120 is the first edge server 121, the communication module 610, i.e., the first communication module, may communicate with the end device 110 via a first wireless network, such as a 5G network. On the other hand, if the edge server 120 is the second edge server 123, the communication module 610, i.e., the first communication module, may communicate with the end device 110 via a second wireless network, such as Wi-Fi 6 (Wi-Fi ad / ay).

[0124] Memory 620 may record data used by at least one of the components of the edge server 120. Memory 620 may include volatile memory or non-volatile memory.

[0125] The processor 630 may control the overall operation of the edge server 120. The processor 630 may communicate with the end device 110 and the cloud server 130, respectively, via the communication module 610. According to various embodiments, the processor 630 may include at least one of the following: a data processing module 631, a control detection module 633, an end control module 635, an end management module 637, or a learning module 639, as shown in Figure 6b.

[0126] The data processing module 631 may process data between the end device 110 and the cloud server 130. In this case, the data processing module 631 may receive first data from the end device 110 via the communication module 610. The first data may include at least one of the following: sensing data relating to the external environment of the end device 110, or state data of the end device 110. The data processing module 631 may also process the first data. In this case, the data processing module 631 may detect second data based on the first data. The second data may include at least one of the processing results for the first data or a request for the end device 110. For example, if the first data includes positioning data of the end device 110, the data processing module 631 may estimate the position of the end device 110 based on the positioning data. Here, the data processing module 631 may use the FTM (fine timing measurement) function to estimate the position of the end device 110. The data processing module 631 may transmit second data to the cloud server 130 via the communication module 610. The data processing module 631 may also receive third data from the cloud server 130. The third data may include at least one of the following: the processing result for the second data or a response to a request for the end device 110.

[0127] The control detection module 633 may determine a control command for the end device 110. Here, the control detection module 633 may determine the control command based on at least one of the first data or the third data. According to one embodiment, the control command may be for controlling the movement of the end device 110. According to another embodiment, the control command may be for updating the software of the end device 110.

[0128] The end control module 635 may control the end device 110 using control commands. To this end, the end control module 635 may send control commands to the end device 110 via the communication module 610.

[0129] The end management module 637 may manage the end devices 110 controlled by the edge server 120. In this case, the end management module 637 may manage one end device 110 or multiple end devices 110. Here, the end management module 637 may manage each end device 110 in accordance with the identification information of each end device 110. For example, the end management module 637 may monitor each end device 110 based on at least one of the first data, second data, or third data. The end management module 637 may also design operating plans associated with each end device 110, such as charging plans. The end management module 637 may also detect map information associated with the end devices 110.

[0130] The learning module 639 may perform machine learning using the second data. In this case, the learning module 639 may acquire at least a portion of the third data based on the second data. The learning module 639 may also provide at least a portion of the third data to the control detection module 633.

[0131] In various embodiments, the edge server 120 may include at least one end device 110, a communication module 610 configured to communicate with a cloud server 130 configured to manage the edge server 120, and a processor 630 connected to the communication module 610.

[0132] According to one embodiment, the edge server 120 may be the first edge server 121 of the first wireless network or the second edge server 123 of the second wireless network.

[0133] For example, the first wireless network may be a long-range wireless network, and the second wireless network may be a short-range wireless network.

[0134] According to various embodiments, the processor 630 may be configured to determine control instructions for the end device 110 and to transmit the control instructions wirelessly to the end device 110 via the communication module 610.

[0135] According to various embodiments, the processor 630 may be configured to wirelessly receive first data collected by the end device 110 via the communication module 610 and to determine a control command based on the first data.

[0136] According to various embodiments, the processor 630 may be configured to determine whether cooperation with the cloud server 130 is necessary based on first data, and if it is determined that cooperation with the cloud server 130 is not necessary, to determine a control command and transmit the control command within a predetermined control cycle.

[0137] According to various embodiments, the processor 630 may be configured to process first data, detect second data from the first data, send the second data to the cloud server 130 via the communication module 610, receive third data corresponding to the second data from the cloud server 130 via the communication module 610, and use the third data to determine a control command.

[0138] According to various embodiments, the processor 630 may be configured to receive update information from the cloud server 130 via the communication module 610 and to determine control commands for updating the software of the end device 110 based on the update information.

[0139] Figure 7a is a diagram illustrating the operation methods of the edge server 120 in various embodiments.

[0140] Referring to Figure 7a, in step 711, the edge server 120 may be connected to the end device 110 and the cloud server 130. The processor 630 may be connected to the end device 110 and the cloud server 130 by a communication module 610. In this case, the communication module 610 may be connected to the end device 110 via a wireless network capable of ultra-high reliability low latency communication (URLLC). The wireless network may include at least one of a first wireless network or a second wireless network. The first wireless network may include a long-range wireless network, such as a 5G network, and the second wireless network may include a short-range wireless network, such as Wi-Fi 6 (Wi-Fi ad / ay). The communication module 610 may also be connected to the cloud server 130 via, for example, the internet.

[0141] According to one embodiment, the edge server 120 may be either the first edge server 121 of the first wireless network or the second edge server 123 of the second wireless network. If the edge server 120 is the first edge server 121, the processor 630 may be connected to the end device 110 by the communication module 610. On the other hand, if the edge server 120 is the second edge server 123, the processor 630 may be connected to the end device 110 by the communication module 610. In this case, the end device 110 is located inside the communicationable area (A) of the second edge server 123, so the processor 630 may be connected to the end device 110 by the communication module 610.

[0142] In step 713, the edge server 120 may receive first data from the end device 110. The processor 630 may receive first data from the end device 110 via the communication module 610. The first data may include at least one of the following: sensing data regarding the external environment of the end device 110, status data of the end device 110, or requests required for the operation of the end device 110. For example, the status data may include at least one of the following: identification information of the end device 110, battery (not shown) status information, or status information of the drive module 330.

[0143] At step 715, the edge server 120 may determine whether cooperation with the cloud server 130 is necessary to control the end device 110. At this time, the edge server 120 may determine whether cooperation with the cloud server 130 is necessary based on the first data. For example, the processor 630 may determine whether cooperation with the cloud server 130 is necessary based on whether the first data contains an directive to instruct the edge server 120 to cooperate with the cloud server 130. If the first data does not contain a directive, the processor 630 may decide that the end device 110 may be controlled independently. If the first data contains a directive, the processor 630 may decide that the end device 110 must be controlled in cooperation with the cloud server 130. As another example, the processor 630 may determine whether cooperation with the cloud server 130 is necessary based on at least one of the attributes of the first data, such as size or importance. If the size of the first data is less than a defined value or the importance of the first data is below a defined criterion, the processor 630 may decide that it is acceptable to control the end device 110 independently. If the size of the first data is greater than or equal to a defined value or the importance of the first data is greater than or equal to a defined criterion, the processor 630 may decide that it must control the end device 110 in cooperation with the cloud server 130. As another example, the processor 630 may predict the time required to control the end device 110 based on the first data. Here, the processor 630 may predict the time required to control the end device 110 based on the attributes of the first data, the current status of at least one of the end device 110 or the edge server 120, etc. If the time required to control the end device 110 is predicted to be less than or equal to a defined control cycle, the processor 630 may decide that it is acceptable to control the end device 110 independently. If the time required to control the end device 110 is predicted to exceed a predetermined control cycle, the processor 630 may decide that it must control the end device 110 in cooperation with the cloud server 130.

[0144] If it is determined in step 715 that cooperation with the cloud server 130 is necessary, then in step 717, the edge server 120 may process the first data. The first data may be processed by the processor 630. At this time, the processor 630 may detect the second data based on the first data. The second data may include at least one of the following: the processing result for the first data or a request for the end device 110. The processing result for the first data may include, for example, at least one of the following: sensing data of the end device 110, state data of the end device 110, the location of the end device 110, a map associated with the end device 110, at least one point of interest (POI), or the degree of task processing. The request for the end device 110 may include at least one of the following: a data retrieval request or a request for update information for a software update of the end device 110. For this purpose, the processor 630 may determine the location of the end device 110. Alternatively, the processor 630 may generate or update a map of the area surrounding the end device 110. Alternatively, the processor 630 may extract points of interest (POIs) from the map of the area surrounding the end device 110. Alternatively, the processor 630 may detect the processing level of the task of the end device 110. According to one embodiment, if the first data includes video containing a person, the processor 630 may mosaic or blow out the area in the video that is associated with the person. After this, in step 719, the edge server 120 may send the second data to the cloud server 130. The processor 630 may send the second data to the cloud server 130 via the communication module 610.

[0145] In step 721, the edge server 120 may detect third data. According to one embodiment, the processor 630 may receive third data from the cloud server 130 via the communication module 610. The third data may include at least one of the processing results for the second data or a response to a request for the end device 110. The processing results for the second data may include, for example, the latest map information updated based on the map associated with the end device 110, or at least one of the machine learning results for the second data. The response to a request for the end device 110 may include, for example, data search results or at least one of the update information for the end device 110. According to another embodiment, the processor 630 may process the second data and detect third data based on the second data. Here, the processor 630 may perform machine learning on the second data. The third data may represent the processing results for the second data. The processing results for the second data may include, for example, the latest map information updated based on the map associated with the end device 110, task information processed by the end device 110, or machine learning results for the second data, at least one of these.

[0146] In step 723, the edge server 120 may determine a control instruction for the end device 110. The processor 630 may determine the control instruction based on at least one of the first data or the third data. According to one embodiment, the control instruction may be for controlling the movement of the end device 110. In this case, the processor 630 may determine the control instruction based on at least one of the following: the position of the end device 110, a map associated with the end device 110, or at least one point of interest (POI). As an example, the control instruction may include at least one of at least one position coordinate or velocity value relative to the movement path or target position of the end device 110. As another example, the control instruction may include an operational variable for using the end device 110 to process a task. According to another embodiment, the control instruction may be for updating the software of the end device 110. After this, in step 725, the edge server 120 may send the control instruction to the end device 110. The processor 630 may send control commands to the end device 110 via the communication module 610.

[0147] On the other hand, if it is determined in step 715 that cooperation with the cloud server 130 is not necessary, then in step 723, the edge server 120 may determine a control instruction for the end device 110. The processor 630 may determine the control instruction based on the first data. According to one embodiment, the control instruction may be for controlling the movement of the end device 110. In this case, the processor 630 may determine the control instruction based on at least one of the following: the position of the end device 110, a map associated with the end device 110, or at least one point of interest (POI). As an example, the control instruction may include at least one of at least one position coordinate or velocity value relative to the movement path or target position of the end device 110. As another example, the control instruction may include an operational variable for using the end device 110 to process a task. After this, in step 725, the edge server 120 may send the control instruction to the end device 110. The processor 630 may send a control command to the end device 110 via the communication module 610. At this time, the edge server 120 may determine a control command based on the first data and send the control command within a defined control cycle. The control cycle may be determined by the sum of the time it takes to determine the control command based on the first data and the time it takes to send the control command to the end device 110. For example, if the defined control cycle is 5ms, the edge server 120 may determine the control command based on the first data in 4ms and send the control command to the end device 110 in 1ms. Here, the second edge server 123 may send the control command along with the map information associated with the end device 110.

[0148] According to one embodiment, the edge server 120 may be either the first edge server 121 of the first wireless network or the second edge server 123 of the second wireless network. In this case, the first edge server 121 and the second edge server 123 may operate in the same way. In this case, the first edge server 121 and the second edge server 123 may operate as shown in Figure 7a. However, the first edge server 121 may communicate with the end device 110 via the first wireless network, for example, a 5G network, and the second edge server 123 may communicate with the end device 110 via the second wireless network, for example, Wi-Fi 6 (Wi-Fi ad / ay). Alternatively, the first edge server 121 and the second edge server 123 may operate differently. In this case, the first edge server 121 may operate as shown in Figure 7b, and the second edge server 123 may operate as shown in Figure 7a. Similarly, the first edge server 121 may communicate with the end device 110 via a first wireless network, such as a 5G network, and the second edge server 123 may communicate with the end device 110 via a second wireless network, such as Wi-Fi 6 (Wi-Fi ad / ay).

[0149] Figure 7b is a diagram showing the operation method of the edge server 120 according to one embodiment. Figure 7b may also show the operation method of the first edge server 121.

[0150] Referring to Figure 7b, in step 731, the first edge server 121 may be connected to the end device 110 and the cloud server 130. The processor 630 may be connected to the end device 110 and the cloud server 130 by a communication module 610. In this case, the communication module 610 may be connected to the end device 110 via a first wireless network capable of ultra-high reliability low latency communication (URLLC). The first wireless network may include a long-range wireless network, such as a 5G network. The communication module 610 may also be connected to the cloud server 130, for example, via the internet.

[0151] In step 733, the first edge server 121 may receive first data from the end device 110. The processor 630 may receive first data from the end device 110 via the communication module 610. The first data may include at least one of the following: sensing data regarding the external environment of the end device 110, status data of the end device 110, or requests required for the operation of the end device 110. For example, the status data may include at least one of the following: identification information of the end device 110, status information of the battery (not shown), or status information of the drive module 330.

[0152] In step 735, the first edge server 120 may determine a control instruction for the end device 110. The processor 630 may determine the control instruction based on first data. For example, the control instruction may be for controlling the movement of the end device 110. In this case, the processor 630 may determine the control instruction based on at least one of the following: the position of the end device 110, a map associated with the end device 110, or at least one point of interest (POI). As an example, the control instruction may include at least one of at least one position coordinate or velocity value relative to the movement path or target position of the end device 110. As another example, the control instruction may include an operational variable for using the end device 110 to process a task. After this, in step 737, the first edge server 121 may send the control instruction to the end device 110. The processor 630 may send the control instruction to the end device 110 via the communication module 610.

[0153] In one embodiment, the first edge server 121 operates as shown in Figure 7b, while the second edge server 123 may operate as shown in Figure 7a. That is, the second edge server 123 may determine a control command based on the first data or detect third data by cooperating with the cloud server 130, and determine a control command based on the third data. For example, the control command may be for controlling the movement of the end device 110, or it may be for updating the software of the end device 110. As a result, the second edge server 123 may send a control command to the end device 110. Here, the second edge server 123 may send the control command along with the map information associated with the end device 110.

[0154] The operation method of the edge server 120 according to various embodiments may include the steps of: wirelessly connecting with at least one end device 110 while connected to a cloud server 130 configured to manage the edge server 120; determining control commands for the end device 110; and wirelessly transmitting control commands to the end device 110.

[0155] According to one embodiment, the edge server 120 may be the first edge server 121 of the first wireless network or the second edge server 123 of the second wireless network.

[0156] For example, the first wireless network may be a long-range wireless network, and the second wireless network may be a short-range wireless network.

[0157] According to various embodiments, the determination step may include the step of wirelessly receiving first data collected by the end device 110, and the step of determining a control command based on the first data.

[0158] According to various embodiments, the determination step may further include the steps of processing the first data to detect the second data from the first data, transmitting the second data to the cloud server 130, receiving the third data corresponding to the second data from the cloud server 130, and determining a control command using the third data.

[0159] According to various embodiments, the transmission step may include the step of receiving update information from the cloud server 130, and the step of determining control commands for updating the software of the end device 110 based on the update information.

[0160] Figure 8a shows a cloud server 130 according to various embodiments, and Figure 8b shows the processor 830 of Figure 8a.

[0161] Referring to Figure 8a, the cloud server 130 according to various embodiments may include at least one of the following: a communication module 810, a memory 820, or a processor 830. In one embodiment, at least one of the components of the cloud server 130 may be omitted, or at least one other component may be added. In one embodiment, at least two of the components of the cloud server 130 may be implemented in a single integrated circuit.

[0162] The communication module 810 may support communication between the cloud server 130 and external devices. Here, the communication module 810 may support the establishment of a communication channel with the external device and the execution of communication via the communication channel. In this case, the communication module 810 may communicate with the edge server 120. For example, the communication module 810 may communicate with the edge server 120 via the internet. The communication module 810 may verify and authenticate the cloud server 130 using recorded identification information.

[0163] Memory 820 may record data used by at least one of the components of the cloud server 130. Memory 820 may include volatile memory or non-volatile memory.

[0164] The processor 830 may control the overall operation of the cloud server 130. The processor 830 may communicate with the edge server 120 via the communication module 810. According to various embodiments, the processor 830 may include at least one of the following: a control module 831, a service module 833, a data management module 835, or a learning module 837, as shown in Figure 8b.

[0165] The control module 831 may manage the end device 110 and the edge server 120. In this case, the control module 831 may perform management based on the identification information of the end device 110 and the identification information of the edge server 120. The control module 831 may link and manage the edge server 120 and the end device 110 controlled by the edge server 120. Here, the control module 831 may manage the state of the end device 110 and the state of the edge server 120.

[0166] The service module 833 may provide a cloud service for at least one of the end device 110 or the edge server 120. In this case, the service module 833 may receive second data from the edge server 120 via the communication module 810. The second data may include at least one of the processing results for the first data or a request for the end device 110. The service module 833 may also send third data to the edge server 120 via the communication module 810. The third data may include at least one of the processing results for the second data or a response to the request for the end device 110.

[0167] The data management module 835 may record various types of information for the cloud service. For example, the data management module 835 may record map information or task information. The task information may include, for example, at least one task model that can be processed by the end device 110. The data management module 835 may also update the information based on first data or third data. For example, the data management module 835 may update map information based on a map of the area surrounding the end device 110.

[0168] The learning module 837 may process the second data. At this time, the learning module 837 may perform machine learning on the second data. As a result, the learning module 837 may obtain the third data based on the second data.

[0169] A cloud server 130 according to various embodiments may include a communication module 810 configured to communicate with at least one edge server 120 configured to control at least one end device 110, and a processor 830 connected to the communication module 810.

[0170] According to various embodiments, the processor 830 may be configured to receive data from the edge server 120 and associated data with the end device 110 via the communication module 810, and to process the data.

[0171] According to various embodiments, the data may include first data collected by the end device 110 and second data detected by the edge server 120.

[0172] According to various embodiments, the processor 830 may be configured to process the second data, detect the third data corresponding to the second data, and transmit the third data to the edge server 120 via the communication module 810.

[0173] According to various embodiments, the processor 830 may be configured to send update information to the edge server 120 for updating the software of the end device 110 via the communication module 810.

[0174] According to one embodiment, the edge server 120 may include at least one of the first edge server 121 of the first wireless network or the second edge server 123 of the second wireless network.

[0175] For example, the first wireless network may be a long-range wireless network, and the second wireless network may be a short-range wireless network.

[0176] Figure 9 shows the operation methods of the cloud server 130 in various embodiments.

[0177] Referring to Figure 9, in step 911, the cloud server 130 may be connected to the edge server 120. The processor 830 may be connected to the edge server 120 via the communication module 810. For example, the communication module 810 may be connected to the edge server 120 via the internet.

[0178] In step 913, the cloud server 130 may receive second data from the edge server 120. The processor 830 may receive second data from the edge server 120 via the communication module 810. The second data may include at least one of the following: processing results for the first data or a request for the end device 110. The processing results for the first data may include, for example, at least one of the following: sensing data of the end device 110, state data of the end device 110, location of the end device 110, map associated with the end device 110, at least one point of interest (POI), or the degree to which the end device 110's task is processed. The request for the end device 110 may include at least one of the following: a data retrieval request or a request for update information to update the software of the end device 110.

[0179] At step 915, the cloud server 130 may process the second data. The processor 830 may process the second data. At this time, the processor 830 may detect the third data based on the second data. For this purpose, the processor 830 may perform machine learning on the second data. The third data may include at least one of the processing results for the second data or a response to a request for the end device 110. The processing results for the second data may include, for example, the latest map information updated based on the map associated with the end device 110, task information to be processed by the end device 110, or at least one of the machine learning results for the second data. The response to a request for the end device 110 may include, for example, at least one of the data search results or update information for the end device 110.

[0180] According to one embodiment, in step 917, the cloud server 130 may send third data to the edge server 120. The processor 830 may send third data to the edge server 120 via the communication module 810. As an example, the processor 830 may send at least one of the processing result for the second data or a response to a request for the end device 110 as third data. As another example, the processor 830 may not send the processing result for the second data, but instead send a response to a request for the end device 110 as third data. That is, even if the processing result for the second data is detected as third data, the processor 830 may not send it.

[0181] The operation methods of the cloud server 130 according to various embodiments may include the steps of connecting to at least one edge server 120 configured to control at least one end device 110, receiving data related to the end device 110 from the edge server 120, and processing the data.

[0182] According to various embodiments, the data may include first data collected by the end device 110 and second data detected by the edge server 120.

[0183] According to various embodiments, the processing steps may include processing the second data to detect third data corresponding to the second data, and transmitting the third data to the edge server 120.

[0184] According to various embodiments, the method may further include the step of sending update information to the edge server 120 for updating the software of the end device 110.

[0185] According to one embodiment, the edge server 120 may include at least one of the first edge server 121 of the first wireless network or the second edge server 123 of the second wireless network.

[0186] For example, the first wireless network may be a long-range wireless network, and the second wireless network may be a short-range wireless network.

[0187] In various embodiments, the edge server 120 acts as the brain for at least one end device 110, enabling wireless control of the end device 110. That is, since the edge server 120 processes control commands for the end device 110, the end device 110 only needs to operate according to the commands, eliminating the need for high processing performance in the end device 110. This reduces the manufacturing cost of the end device 110 and also lowers its power consumption. Furthermore, high-performance and highly precise operation is possible regardless of the size of the end device 110. Additionally, because the edge server 120 can control multiple end devices 110 with its high processing performance, the communication system 100, including the end devices 110 and the edge server 120, can improve the efficiency of resource utilization, including cost and power. Moreover, since the cloud server 130 updates the software of the end device 110 via the edge server 120, the end device 110 can be kept up-to-date.

[0188] According to one embodiment, in the communication system 100, the first edge server 121 of the first wireless network and the second edge server 123 of the second wireless network can operate complementaryly. The first edge server 121 enables ultra-low latency transmission for the end device 110, and the second edge server 123 enables high-capacity transmission for the end device 110. Here, the second edge server 123 can also estimate the position of the end device 110 using positioning data received from the end device 110. Furthermore, the end device 110 can be driven even in shaded areas by the first edge server 121 and the second edge server 123.

[0189] The various embodiments and the terminology used herein are not intended to limit the technology described herein to any particular embodiment, but rather to include various modifications, equivalents, and / or substitutes of the applicable embodiments. In relation to the description of the drawings, similar components are denoted by similar reference numerals. A singular expression may include a plural expression unless the context clearly indicates otherwise. In this specification, expressions such as “A or B,” “A and / or B,” “A, B, or C,” or “A, B, and / or C,” may include all possible combinations of the listed items. Expressions such as “first,” “second,” “first,” or “second” modify the applicable component regardless of its order or importance, and are used only to distinguish one component from another, and not to limit the applicable component. When it is stated that one component (e.g., component 1) is "connected" or "linked" to another component (e.g., component 2), this includes not only cases where the component is directly connected to the other component, but also cases where it is connected via another component (e.g., component 3).

[0190] As used herein, the term "module" includes units composed of hardware, software, or firmware, and may be used interchangeably with terms such as logic, logic block, component, or circuit. A module may be a single component, or the smallest unit or part thereof that performs one or more functions. For example, a module may consist of an ASIC (application-specific integrated circuit).

[0191] Various embodiments of this specification may be implemented as software comprising one or more instruction words recorded on a storage medium (e.g., memory 350, memory 620, memory 820) readable by a machine (e.g., end device 110, edge server 120, cloud server 130). For example, the machine's processor (e.g., processor 360, processor 630, processor 830) may invoke and execute at least one instruction from the one or more instruction words recorded on the storage medium. This allows the machine to be operated to perform at least one function according to the invoked at least one instruction word. The one or more instruction words may comprise code that can be generated by a compiler or code that can be executed by an interpreter. The storage medium readable by the machine may be provided in the form of a non-transitory storage medium. Here, "non-temporary" simply means that the recording medium is a tangible device and does not contain signals (e.g., electromagnetic waves). This term does not distinguish between cases where data is recorded on the recording medium semi-permanently and cases where it is recorded temporarily.

[0192] According to various embodiments, each component of the described component (e.g., module or program) may include one or more individuals. According to various embodiments, one or more components or stages of the above-described component may be omitted, or one or more other components or stages may be added. Generally or additionally, multiple components (e.g., module or program) may be integrated into a single component. In such cases, the integrated component may perform one or more functions of each component of the multiple components in the same or similar manner as when performed by the component of the multiple components before integration. According to various embodiments, the stages performed by a module, program, or other component may be performed sequentially, in parallel, iteratively, or heuristically, one or more of the stages may be performed in a different order, omitted, or one or more other stages may be added.

Claims

1. An end device, comprising: a communication module configured to wirelessly communicate with an edge server managed by a cloud server; and a processor coupled to the communication module; The processor: receiving a control command from the edge server by the communication module; An end device configured to operate in accordance with the control instructions.

2. The edge server a first edge server of the first wireless network; and a second edge server of a second wireless network; The processor: Generate the data, transmitting the data to either the first edge server or the second edge server by the communication module; The end device of claim 1 , configured to receive the control command from either the first edge server or the second edge server via the communication module.

3. The processor:

3. The end device of claim 2, configured to determine whether the first wireless network or the second wireless network is suitable for transmitting the data based on at least one of a type of the data, resources required to transmit the data, or resources required in the control command received in response to the data.

4. The processor:

3. The end device of claim 2, configured to transmit a first type of data to the first edge server over the first wireless network and a second type of data to the second edge server over the second wireless network.

5. further comprising a drive module configured to perform a physical operation; The processor: The end device of claim 1 , configured to drive the drive module according to the control command.

6. 1. A method of operating an end device, comprising: wirelessly connecting to an edge server managed by a cloud server; wirelessly receiving control instructions from the edge server; and and driving the control instructions.

7. an edge server for controlling at least one end device, a communication module configured to communicate with a cloud server configured to manage the end device and the edge server; and a processor coupled to the communication module; The processor: determining control instructions for the end device; an edge server configured to wirelessly transmit the control instructions to the end device via the communication module;

8. The processor: wirelessly receiving first data collected by the end device via the communication module; The edge server of claim 7 , configured to determine the control instruction based on the first data.

9. The processor: determining whether cooperation with the cloud server is necessary based on the first data; If it is determined that cooperation with the cloud server is not necessary, the control command is determined and transmitted within a predetermined control period; If it is determined that cooperation with the cloud server is necessary, the first data is processed to detect second data from the first data; transmitting the second data to the cloud server by the communication module; receiving third data corresponding to the second data from the cloud server by the communication module; The edge server of claim 8 , configured to utilize the third data to determine the control command.

10. The processor: receiving update information from the cloud server by the communication module; The edge server of claim 7 , configured to determine the control instructions for updating software of the end device based on the update information.

11. 1. A method of operating an edge server for controlling at least one end device, comprising: wirelessly connecting to the end device while in connection with a cloud server configured to manage the edge server; determining control instructions for the end device; and wirelessly transmitting the control command to the end device.

12. A cloud server, a communication module configured to communicate with at least one edge server configured to control at least one end device; and a processor coupled to the communication module; The processor: receiving, by the communication module, data associated with the end device from the edge server; A cloud server configured to process the data.

13. The data includes second data detected by the edge server from first data collected by the end device; The processor: processing the second data to detect third data corresponding to the second data; The cloud server of claim 12 , configured to transmit the third data to the edge server by the communication module.

14. The processor: The cloud server of claim 12 , wherein the communication module is configured to send update information to the edge server for updating software of the end device.

15. 1. A method of operating a cloud server, comprising: connecting to at least one edge server configured to control at least one end device; receiving data associated with the end device from the edge server; and processing said data.

16. A three-way communication system, comprising: at least one end device configured to collect data; at least one edge server configured to wirelessly control the end devices; and a cloud server configured to connect to the edge server and manage the end device and the edge server; The edge server configured to wirelessly receive the data from the end device, determine a control command based on the data, and wirelessly transmit the control command to the end device; The end device is A communication system configured to wirelessly receive the control instructions from the edge server and operate in accordance with the control instructions.

17. The edge server a first edge server in a first wireless network and a second edge server in a second wireless network; The end device is Sending the data to either the first edge server or the second edge server; The communication system of claim 16 , configured to receive the control instructions wirelessly from either the first edge server or the second edge server.

18. The first edge server determining the control command based on the data; The communication system of claim 17 , configured to transmit the control command to the end device via the first wireless network.

19. The second edge server determining whether cooperation with the cloud server is necessary based on the data; If it is determined that cooperation with the cloud server is not necessary, the control command is determined within a predetermined control period; If it is determined that cooperation with the cloud server is necessary, communicating with the cloud server based on the data to determine the control command; The communication system of claim 17 , configured to transmit the control command to the end device via the second wireless network.

20. A method for operating a three-party communication system, comprising: During a connection between the edge server and the cloud server, the edge server wirelessly connects with at least one end device; the end device collecting data; the end device wirelessly transmitting the data to the edge server; the edge server determining a control command based on the data; the edge server wirelessly transmitting the control command to the end device; and The method includes a step of causing the end device to operate in accordance with the control command.

Images