WO2022060046A1 - Système informatique en périphérie de réseau et procédé de transfert intercellulaire destinés à un dispositif informatique en périphérie de réseau - Google Patents

Système informatique en périphérie de réseau et procédé de transfert intercellulaire destinés à un dispositif informatique en périphérie de réseau Download PDF

Info

Publication number
WO2022060046A1
WO2022060046A1 PCT/KR2021/012461 KR2021012461W WO2022060046A1 WO 2022060046 A1 WO2022060046 A1 WO 2022060046A1 KR 2021012461 W KR2021012461 W KR 2021012461W WO 2022060046 A1 WO2022060046 A1 WO 2022060046A1
Authority
WO
WIPO (PCT)
Prior art keywords
edge
edge device
edge computing
computing service
processor
Prior art date
Application number
PCT/KR2021/012461
Other languages
English (en)
Korean (ko)
Inventor
이종원
김무현
송가진
이선기
Original Assignee
삼성전자 주식회사
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 삼성전자 주식회사 filed Critical 삼성전자 주식회사
Publication of WO2022060046A1 publication Critical patent/WO2022060046A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/40—Support for services or applications
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/14—Session management
    • H04L67/148—Migration or transfer of sessions
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/2866—Architectures; Arrangements
    • H04L67/289—Intermediate processing functionally located close to the data consumer application, e.g. in same machine, in same home or in same sub-network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/51—Discovery or management thereof, e.g. service location protocol [SLP] or web services

Definitions

  • This document is about an edge computing system, and more specifically, an edge computing system that can perform edge computing services by an edge device connected to data acquired from a leaf device, and an edge device connected to a leaf device in the edge computing system. It is about how to handover to another edge device.
  • Cloud computing technology is a technology for providing computing services such as servers, storage, software, or analysis by providing computing resources that exist in a different location to the user through a network.
  • User data or contents collected from IoT devices are stored in cloud servers, and cloud services are provided to users through data processing.
  • Cloud computing is being utilized to process data generated in the Internet of Things (IoT).
  • IoT Internet of Things
  • cloud computing as the amount of data and devices constituting the IoT increases, a load is created on the system, and security or privacy issues may occur in the process of data delivery and/or storage, an error may occur in the cloud server, or the Internet If it is not connected to , there may be a problem that the service cannot be provided.
  • Edge computing is an open architecture that extends cloud computing and some of its services to devices at the edge of a network. For example, when edge computing technology is utilized in IoT, applications or services processed in a cloud server, where low latency and privacy are important, can be partially distributed on the edge device.
  • edge computing technology is being used in IoT
  • the conventional edge computing service provides a service using a module fixed to an edge device fixed to a leaf device.
  • the process of disconnecting the previously connected edge device and then reconnecting with the new edge device is required do.
  • An object of the present document is to provide an edge computing system and a handover method of an edge computing device.
  • An electronic device includes a communication module, a memory, and a processor operatively connected to the communication module and the memory, wherein the processor includes a first external device and a second external device on a local network.
  • the processor includes a first external device and a second external device on a local network.
  • An electronic device includes a communication module, a memory, and a processor operatively connected to the communication module and the memory, wherein the processor is Based on the received data, an edge computing service is performed, a handover event of the edge computing service is detected, and in response to the detection of the handover event, it is connected to the first external device through the communication module and the A second external device capable of performing an edge computing service is identified, and information related to the identified second external device and information related to the handover event is provided to the first external device, the second external device, or an external server. It may be set to transmit to at least one of
  • An electronic device includes a communication module, a sensor, and a processor operatively connected to the communication module and the sensor, wherein the processor transmits data obtained through the sensor to the communication module to perform the edge computing service by transmitting to the first external device through and to request a connection for the edge computing service from the second external device.
  • the edge computing function when the edge device connected to the leaf device determines that it is necessary to change the edge computing function, the edge computing function is handed over so that the edge computing service can be performed by the new edge device.
  • a computing system and a handover method of an edge computing device may be provided.
  • FIG 1 illustrates devices in an IoT environment according to various embodiments.
  • FIGS. 2A and 2B illustrate respective devices of an edge computing system according to various embodiments.
  • FIG. 3 is a block diagram of a user device within a network environment, in accordance with various embodiments.
  • FIG. 4 is a block diagram of an edge device according to various embodiments of the present disclosure.
  • FIG. 5 is a block diagram of a leaf device according to various embodiments.
  • FIG. 6 is a flowchart of a handover method of an edge device according to various embodiments.
  • FIG. 7 is a flowchart of a method of determining a handover event according to movement of an edge device according to various embodiments of the present disclosure
  • FIG. 8 is a flowchart of a method of determining a handover event according to a resource of an edge device according to various embodiments of the present disclosure
  • FIG. 9 is a flowchart of a method of determining a handover event according to a power state or resource of an edge device according to various embodiments of the present disclosure
  • FIG. 10 is a diagram illustrating a change process of an edge device when an edge handover is initiated by a second edge device according to various embodiments of the present disclosure.
  • FIG. 11 is a diagram illustrating a process of changing an edge device when an edge handover is initiated by a second edge device according to various embodiments of the present disclosure.
  • FIG. 12 is a diagram illustrating a change process of an edge device when an edge handover is initiated by a leaf device according to various embodiments of the present disclosure.
  • FIG. 13 is a diagram illustrating a change process of an edge device when an edge handover is initiated by a leaf device according to various embodiments of the present disclosure.
  • FIG. 14 is a diagram illustrating a process of changing an edge device when an edge handover is initiated by an IoT server according to various embodiments of the present disclosure.
  • FIG. 15 illustrates a process of handing over some of the edge computing services being performed by the first edge device to the second edge device according to various embodiments of the present disclosure.
  • FIG 16 illustrates a process of handing over some of the edge computing services being performed by the first edge device to the second edge device according to various embodiments of the present disclosure.
  • FIG 1 illustrates devices in an IoT environment (or IoT system) according to various embodiments.
  • an internet of things (IoT) system (or edge computing system) 100 includes at least one leaf device 120 (leaf device), at least one edge device 110 (edge device), and a user. It may include a device 130 (user device) and a cloud network 140 (cloud network).
  • the leaf device 120 , the edge device 110 , and the user device 130 may be disposed in adjacent locations (eg, in a house) and connected to the same home network (eg, the same access point (AP)).
  • the cloud network 140 may be remotely located, but may be connected to the leaf device 120 , the edge device 110 , and the user device 130 through the Internet.
  • edge computing service is used to transmit data acquired from leaf devices to edge devices located adjacent to and located on the same home network of leaf devices, and to provide a series of data processing and other services on the edge devices It can mean the skill to Although this document defines a device that acquires data through a sensor (eg, a camera 121, a refrigerator 122, a light bulb 123a, and a digital thermometer 123b) as a leaf device, the leaf device is a client of an edge computing service. It may be defined by other names such as device, end device, sensor device, IoT device, and slave device. In addition, although defined as an edge device in this document, an edge device may be defined by other names, such as an edge server, a server device, a master device, a hub device, and a service device of an edge computing service.
  • a sensor eg, a camera 121, a refrigerator 122, a light bulb 123a, and a digital thermometer 123b
  • the leaf device is a client of an edge computing service. It
  • the leaf device 120, the edge device 110, and the user device 130 are classified and described according to the function and operation of each device in the edge computing system 100, but the same device (eg, a smart phone, a tablet PC) may operate as any one of the leaf device 120 , the edge device 110 , and the user device 130 in some cases.
  • the names and definitions of devices described in this document do not limit the functions and/or operations of the devices.
  • the leaf device 120 may collect various data using a sensor as an end point of the IoT system 100 and transmit it to the edge device 110 or the cloud network 140 . Also, the leaf device 120 may perform various operations according to a command transmitted from the cloud network 140 or the user device 130 .
  • a device such as a camera 121 , a refrigerator 122 , a light bulb 123a , and a digital thermometer 123b may be the leaf device 120 .
  • the leaf device 120 may access the cloud network 140 through the Internet, and devices that do not support Internet Protocol (IP) among the leaf devices 120 (eg, the light bulb 123a, digital
  • IP Internet Protocol
  • the thermometer 123b) transmits the sensed data to the hub device 124 through supported non-IP-based communication (eg, bluetooth, zigbee), and the hub device 124 sends each leaf to the cloud network 140 via the Internet. Sensing data of the devices 123a and 123b may be transmitted.
  • IP Internet Protocol
  • the cloud network 140 is located on the network and may include various server devices (eg, IoT management server and IoT hub server) supporting cloud computing services in the IoT system 100 .
  • the cloud network 140 may perform computing processing on the sensing data received from the leaf device 120 and transmit a command for controlling the leaf device 120 .
  • the cloud network 140 may perform a function of operating and managing a specific device in the home network to operate as the edge device 110 .
  • the cloud network 140 includes an IoT server (eg, an IoT management server or an IoT hub server), and the IoT server is an edge device such as registration, connection, and management of the edge device 110 and the leaf device 120 .
  • a computing service may be performed and a module (eg, a device module, a service module) necessary for the edge computing service may be provided to the edge device 110 .
  • the edge device 110 may directly process data received from the leaf device 120 or transmit it to the cloud network 140 (eg, an IoT server).
  • the edge device 110 may be a device including hardware and/or software resources necessary for an edge computing service, such as a TV 112 and a tablet PC 111 .
  • the edge device 110 may be connected to the cloud network 140 through the Internet, and may form a home network with the leaf device 120 .
  • a plurality of edge devices 110 may exist in the home network, and the leaf device 120 may be connected to any one of the plurality of edge devices 110 to transmit data.
  • the edge device 110 may download and execute a module (eg, a device module, a service module) required for an edge computing service from the cloud network 140 .
  • the edge device 110 may perform a device-specific function (eg, an image output function of a TV), and may perform hardware at least partially concurrently with the performance of the unique function or during an idle time that does not perform the unique function. and/or may perform edge computing services through software resources.
  • a device-specific function eg, an image output function of a TV
  • the edge device 110 may perform hardware at least partially concurrently with the performance of the unique function or during an idle time that does not perform the unique function. and/or may perform edge computing services through software resources.
  • edge device 110 A detailed configuration and operation of the edge device 110 will be described in more detail with reference to FIG. 4 .
  • the user device 130 may provide various user interfaces related to edge computing services through applications. For example, the user device 130 may obtain data (eg, camera image streaming) acquired from the leaf device 120 or data as a result of processing the data in the edge device 110 or the cloud network 140 (eg, a person). recognition) can be displayed on the display. In addition, the user device 130 may receive a user input such as connection of the edge device 110 and/or the leaf device 120 and server registration, and transmit it to the cloud network 140 . A detailed configuration and operation of the user device 130 will be described in more detail with reference to FIG. 3 .
  • data eg, camera image streaming
  • the cloud network 140 e.g, a person
  • the user device 130 may receive a user input such as connection of the edge device 110 and/or the leaf device 120 and server registration, and transmit it to the cloud network 140 .
  • the leaf device 120 may be connected to any one of a plurality of edge devices 110 located in the home network to perform an edge computing service, and may switch to another edge device according to the state of each edge device.
  • a connection can be handed over.
  • the leaf device 120 switches the connection to another edge device to continuously perform the edge computing service being performed.
  • the leaf device 120 can mean doing For example, while connected to the leaf device 120 and the first edge device (eg, the tablet PC 111) and performing edge computing services, the movement of the first edge device, network departure, lack of resources, change of power state, and Similarly, when the first edge device cannot perform the edge computing function, according to the handover event, the leaf device 120 is connected to the second edge device (eg, the TV 112) in the home network to provide an edge computing service. can be performed.
  • the first edge device eg, the tablet PC 111
  • the leaf device 120 is connected to the second edge device (eg, the TV 112) in the home network to provide an edge computing service. can be performed.
  • FIGS. 2A and 2B illustrate respective devices of an edge computing system according to various embodiments.
  • the edge computing system may include a leaf device 220 , an edge device 210 , a user device 230 , an IoT hub server 250 , and an IoT management server 240 .
  • various IoT devices may exist on the home network, and in FIG. 2 , one leaf device (eg, the camera 121 of FIG. 1 ) and one edge device ) (eg, the TV 112 of FIG. 1 ) will be described as an example.
  • the IoT management server 240 (eg, SmartThings TM server) is a server device that provides various services for determining, connecting and/or operating edge computing services, and includes a provision manager 242, a module It may include a manager 244 and an edge-leaf manager 246 .
  • the provision manager 242 may perform a relay function in the middle so that the edge device 210 can be connected to the IoT hub server 250 .
  • the provision manager 242 provides a connection string ( connection string) to the edge device 210 .
  • the module manager 244 may manage information on various modules provided for edge computing services and devices supporting each service.
  • the module required to perform the edge computing service is a device module 219 that enables the edge device 210 to transmit data transmitted from the leaf device 220 to an external server (eg, IoT hub server 250). and a service module 218 including programs executed to implement a service in the edge device 210 based on data transmitted from the leaf device 220 .
  • the edge-leaf manager 246 may manage the connection state between the edge device 210 and the leaf device 220 existing in several home networks. For example, when the edge device 210 and the leaf device 220 registered in the IoT management server 240 are connected or disconnected from each other, the edge device 210 and/or the leaf device 220 connects or connects. The release information is transmitted to the IoT management server 240, and the IoT management server 240 can store information about which edge device 210 and leaf device 220 are connected in real time, and which service is being performed. there is.
  • the leaf device 220 is connected to a specific edge device (eg, the tablet PC 111 of FIG. 1 ) to perform an edge computing service, and then disconnects from the corresponding edge device according to a handover event and releases the connection to another edge device.
  • a specific edge device eg, the tablet PC 111 of FIG. 1
  • the IoT management server 240 connects the edge device 210 and the leaf device 240 changed according to the handover event. Information can be updated.
  • the IoT hub server 250 supports a cloud computing platform, and provides data necessary for the leaf device 220 and the edge device 210 in the cloud environment to be connected to each other.
  • the IoT hub server 250 may include an IoT hub 252 and a module registry 254 .
  • the module registry 254 may be a storage of modules (eg, the device module 219 and the service module 218 ) required to perform an edge computing service.
  • the IoT hub 252 maintains a connection with the edge device 210 , provides a module stored in the module registry 254 to the edge device 210 , and provides multiple edge devices 210 . ) can maintain information of installed modules.
  • the edge device 210 (eg, the edge device 110 of FIG. 1 ) has device-specific functions such as a TV, a tablet PC, and a laptop PC, and configures hardware and/or software for an edge computing service. It can be a device containing (eg edge runtime, base module).
  • the edge computing service may be performed through hardware and/or software resources at least partially concurrently with the performance of the intrinsic function or during idle time when the intrinsic function is not performed.
  • the edge device 210 includes an interface 212 and an operating system (OS) 214 for communicating with the cloud (eg, the IoT management server 240 and the IoT hub server 250 ). and edge runtime 216 .
  • OS operating system
  • the edge device 210 may require hardware conditions (eg, CPU performance) for operating the operating system 214 , and may be configured as a real time operating system (RTOS).
  • RTOS real time operating system
  • An edge runtime 216 (edge runtime) and a basic module for edge computing may be installed in the edge device 210 through a process process or software upgrade of the edge device 210 .
  • the edge runtime 216 may include a daemon program for interworking with the IoT server, and the basic module may be configured as a container as a program necessary for communication with the IoT server.
  • the basic module may be a container installed in the edge runtime 216 environment.
  • the edge device 210 when the edge device 210 is connected to a specific leaf device 220 , it may receive and install at least one module for performing an edge computing service from the IoT hub server 250 .
  • the at least one module may be determined according to the type of the leaf apparatus 220 to be connected and/or the type of service that can be performed, and a device module 219 corresponding to the leaf apparatus 220 and / or may include a service module 218 corresponding to the type of service to be performed.
  • a device module 219 corresponding to the leaf apparatus 220 and / or may include a service module 218 corresponding to the type of service to be performed.
  • the edge device 210 is connected to the IoT hub server 250 by executing the edge runtime 216 in the provisioning process, and the at least one module is additionally installed according to the type of the leaf device 220 and can be executed
  • the edge device 210 may activate or deactivate the edge mode according to a command received from the IoT hub server 250 or the IoT management server 240 .
  • the edge device 210 performs only a unique function (eg, an image output function of the TV), and the device module 219 and the service module 218 may not be executed.
  • the leaf device 220 (eg, the leaf device 120 of FIG. 1 ) transmits data acquired using a sensor to the connected edge device 210 or a cloud network (eg, IoT management server 240 ); It can be transmitted to the IoT hub server (250).
  • a cloud network eg, IoT management server 240
  • IoT hub server 250
  • IP internet protocol
  • the user device 230 may be a device including a display capable of executing various applications, such as a smart phone and a tablet PC, and displaying a user interface (UI).
  • the user device 230 may install and/or execute an application for an edge computing service, and receive content and a notification generated by the leaf device 220 through the corresponding application.
  • the edge device 210 and the leaf device 220 are connected, the content or notification generated by the leaf device 220 may be transmitted to the user device 230 through the edge device 210 .
  • the functions of the IoT hub server 250 and the IoT management server 240 may be performed by one server device (eg, the IoT server 260 of FIG. 2B ).
  • the IoT server 260 includes the IoT hub 261 (eg, the IoT hub 252 of FIG. 2A ) that is a configuration of the IoT hub server 250 and the IoT management server 240 described above. ), module registry 262 (eg, module registry 254 in FIG. 2A ), provision manager 263 (eg, provision manager 242 in FIG. 2A ), module manager 264 (eg, FIG. 2A ). of the module manager 244) and the edge-leaf manager 265 (eg, the edge-leaf manager 246 of FIG. 2A).
  • the edge-leaf manager 265 eg, the edge-leaf manager 246 of FIG. 2A.
  • each configuration of the IoT hub server 250 and the IoT management server 240 of FIG. 2A is distributedly arranged by three or more plurality of server devices existing on the network, or some operations performed in each configuration It may also be distributed by several server devices.
  • FIG. 3 is a block diagram of a user device within a network environment, in accordance with various embodiments.
  • a user device of the edge computing system eg, the user device 130 of FIG. 1 and the user device 230 of FIG. 2A
  • an electronic device 301 may be referred to as an electronic device 301 .
  • the user device (or electronic device) 301 communicates with the electronic device 302 through a first network 398 (eg, a short-range wireless communication network), or 2 may communicate with the electronic device 304 or the server 308 through the network 399 (eg, a remote wireless communication network).
  • the electronic device 301 may communicate with the electronic device 304 through the server 308 .
  • the electronic device 301 includes a processor 320 , a memory 330 , an input module 350 , a sound output module 355 , a display module 360 , an audio module 370 , and a sensor module ( 376 , interface 377 , connection terminal 378 , haptic module 379 , camera module 380 , power management module 388 , battery 389 , communication module 390 , subscriber identification module 396 ) , or an antenna module 397 .
  • at least one of these components eg, the connection terminal 378
  • some of these components are integrated into one component (eg, display module 360 ). can be
  • the processor 320 for example, executes software (eg, a program 340) to execute at least one other component (eg, a hardware or software component) of the electronic device 301 connected to the processor 320 . It can control and perform various data processing or operations. According to one embodiment, as at least part of data processing or computation, the processor 320 converts commands or data received from other components (eg, the sensor module 376 or the communication module 390 ) to the volatile memory 332 . may be stored in , process commands or data stored in the volatile memory 332 , and store the result data in the non-volatile memory 334 .
  • software eg, a program 340
  • the processor 320 converts commands or data received from other components (eg, the sensor module 376 or the communication module 390 ) to the volatile memory 332 .
  • the volatile memory 332 may be stored in , process commands or data stored in the volatile memory 332 , and store the result data in the non-volatile memory 334 .
  • the processor 320 is a main processor 321 (eg, central processing unit or application processor) or a secondary processor 323 (eg, a graphics processing unit, a neural network processing unit) a neural processing unit (NPU), an image signal processor, a sensor hub processor, or a communication processor).
  • main processor 321 eg, central processing unit or application processor
  • secondary processor 323 eg, a graphics processing unit, a neural network processing unit
  • NPU neural processing unit
  • an image signal processor e.g., a sensor hub processor, or a communication processor.
  • the coprocessor 323 may be, for example, on behalf of the main processor 321 while the main processor 321 is in an inactive (eg, sleep) state, or when the main processor 321 is active (eg, executing an application). ), together with the main processor 321, at least one of the components of the electronic device 301 (eg, the display module 360, the sensor module 376, or the communication module 390) It is possible to control at least some of the related functions or states.
  • the coprocessor 323 eg, image signal processor or communication processor
  • the auxiliary processor 323 may include a hardware structure specialized for processing an artificial intelligence model.
  • Artificial intelligence models can be created through machine learning. Such learning may be performed, for example, in the electronic device 301 itself on which artificial intelligence is performed, or may be performed through a separate server (eg, the server 308 ).
  • the learning algorithm may include, for example, supervised learning, unsupervised learning, semi-supervised learning, or reinforcement learning, but in the above example not limited
  • the artificial intelligence model may include a plurality of artificial neural network layers.
  • Artificial neural networks include deep neural networks (DNNs), convolutional neural networks (CNNs), recurrent neural networks (RNNs), restricted boltzmann machines (RBMs), deep belief networks (DBNs), bidirectional recurrent deep neural networks (BRDNNs), It may be one of deep Q-networks or a combination of two or more of the above, but is not limited to the above example.
  • the artificial intelligence model may include, in addition to, or alternatively, a software structure in addition to the hardware structure.
  • the memory 330 may store various data used by at least one component (eg, the processor 320 or the sensor module 376 ) of the electronic device 301 .
  • the data may include, for example, input data or output data for software (eg, the program 340 ) and instructions related thereto.
  • the memory 330 may include a volatile memory 332 or a non-volatile memory 334 .
  • the program 340 may be stored as software in the memory 330 , and may include, for example, an operating system 342 , middleware 344 , or an application 346 .
  • the input module 350 may receive a command or data to be used in a component (eg, the processor 320 ) of the electronic device 301 from the outside (eg, a user) of the electronic device 301 .
  • the input module 350 may include, for example, a microphone, a mouse, a keyboard, a key (eg, a button), or a digital pen (eg, a stylus pen).
  • the sound output module 355 may output a sound signal to the outside of the electronic device 301 .
  • the sound output module 355 may include, for example, a speaker or a receiver.
  • the speaker can be used for general purposes such as multimedia playback or recording playback.
  • the receiver may be used to receive an incoming call. According to one embodiment, the receiver may be implemented separately from or as part of the speaker.
  • the display module 360 may visually provide information to the outside (eg, a user) of the electronic device 301 .
  • the display module 360 may include, for example, a control circuit for controlling a display, a hologram device, or a projector and a corresponding device.
  • the display module 360 may include a touch sensor configured to sense a touch or a pressure sensor configured to measure the intensity of a force generated by the touch.
  • the audio module 370 may convert a sound into an electric signal or, conversely, convert an electric signal into a sound. According to an embodiment, the audio module 370 obtains a sound through the input module 350 or an external electronic device (eg, a sound output module 355 ) connected directly or wirelessly with the electronic device 301 .
  • the electronic device 302 may output sound through (eg, a speaker or headphones).
  • the sensor module 376 detects an operating state (eg, power or temperature) of the electronic device 301 or an external environmental state (eg, a user state), and generates an electrical signal or data value corresponding to the sensed state. can do.
  • the sensor module 376 may include, for example, a gesture sensor, a gyro sensor, a barometric pressure sensor, a magnetic sensor, an acceleration sensor, a grip sensor, a proximity sensor, a color sensor, an IR (infrared) sensor, a biometric sensor, It may include a temperature sensor, a humidity sensor, or an illuminance sensor.
  • the interface 377 may support one or more specified protocols that may be used by the electronic device 301 to directly or wirelessly connect with an external electronic device (eg, the electronic device 302 ).
  • the interface 377 may include, for example, a high definition multimedia interface (HDMI), a universal serial bus (USB) interface, an SD card interface, or an audio interface.
  • HDMI high definition multimedia interface
  • USB universal serial bus
  • SD card interface Secure Digital Card
  • connection terminal 378 may include a connector through which the electronic device 301 can be physically connected to an external electronic device (eg, the electronic device 302 ).
  • the connection terminal 378 may include, for example, an HDMI connector, a USB connector, an SD card connector, or an audio connector (eg, a headphone connector).
  • the haptic module 379 may convert an electrical signal into a mechanical stimulus (eg, vibration or movement) or an electrical stimulus that the user can perceive through tactile or kinesthetic sense.
  • the haptic module 379 may include, for example, a motor, a piezoelectric element, or an electrical stimulation device.
  • the camera module 380 may capture still images and moving images. According to one embodiment, the camera module 380 may include one or more lenses, image sensors, image signal processors, or flashes.
  • the power management module 388 may manage power supplied to the electronic device 301 .
  • the power management module 388 may be implemented as, for example, at least a part of a power management integrated circuit (PMIC).
  • PMIC power management integrated circuit
  • the battery 389 may supply power to at least one component of the electronic device 301 .
  • battery 389 may include, for example, a non-rechargeable primary cell, a rechargeable secondary cell, or a fuel cell.
  • the communication module 390 is a direct (eg, wired) communication channel or a wireless communication channel between the electronic device 301 and an external electronic device (eg, the electronic device 302, the electronic device 304, or the server 308). It can support establishment and communication performance through the established communication channel.
  • the communication module 390 may include one or more communication processors that operate independently of the processor 320 (eg, an application processor) and support direct (eg, wired) communication or wireless communication.
  • the communication module 390 is a wireless communication module 392 (eg, a cellular communication module, a short-range wireless communication module, or a global navigation satellite system (GNSS) communication module) or a wired communication module 394 (eg, : It may include a LAN (local area network) communication module, or a power line communication module).
  • GNSS global navigation satellite system
  • a corresponding communication module among these communication modules is a first network 398 (eg, a short-range communication network such as Bluetooth, wireless fidelity (WiFi) direct, or infrared data association (IrDA)) or a second network 399 (eg, legacy It may communicate with the external electronic device 304 through a cellular network, a 5G network, a next-generation communication network, the Internet, or a computer network (eg, a telecommunication network such as a LAN or a WAN).
  • a first network 398 eg, a short-range communication network such as Bluetooth, wireless fidelity (WiFi) direct, or infrared data association (IrDA)
  • a second network 399 eg, legacy It may communicate with the external electronic device 304 through a cellular network, a 5G network, a next-generation communication network, the Internet, or a computer network (eg, a telecommunication network such as a LAN or a WAN).
  • a telecommunication network
  • the wireless communication module 392 uses the subscriber information (eg, International Mobile Subscriber Identifier (IMSI)) stored in the subscriber identification module 396 within a communication network, such as the first network 398 or the second network 399 .
  • the electronic device 301 may be identified or authenticated.
  • the wireless communication module 392 may support a 5G network after a 4G network and a next-generation communication technology, for example, a new radio access technology (NR).
  • NR access technology includes high-speed transmission of high-capacity data (eMBB (enhanced mobile broadband)), minimization of terminal power and access to multiple terminals (mMTC (massive machine type communications)), or high reliability and low latency (URLLC (ultra-reliable and low-latency) -latency communications)).
  • eMBB enhanced mobile broadband
  • mMTC massive machine type communications
  • URLLC ultra-reliable and low-latency
  • the wireless communication module 392 may support a high frequency band (eg, mmWave band) to achieve a high data rate, for example.
  • a high frequency band eg, mmWave band
  • the wireless communication module 392 uses various techniques for securing performance in a high frequency band, for example, beamforming, massive multiple-input and multiple-output (MIMO), all-dimensional multiplexing. It may support technologies such as full dimensional MIMO (FD-MIMO), an array antenna, analog beam-forming, or a large scale antenna.
  • the wireless communication module 392 may support various requirements specified in the electronic device 301 , an external electronic device (eg, the electronic device 304 ), or a network system (eg, the second network 399 ).
  • the wireless communication module 392 may include a peak data rate (eg, 20 Gbps or more) for realizing eMBB, loss coverage (eg, 164 dB or less) for realizing mMTC, or U-plane latency for realizing URLLC ( Example: downlink (DL) and uplink (UL) each 0.5 ms or less, or round trip 1 ms or less).
  • a peak data rate eg, 20 Gbps or more
  • loss coverage eg, 164 dB or less
  • U-plane latency for realizing URLLC
  • the antenna module 397 may transmit or receive a signal or power to the outside (eg, an external electronic device).
  • the antenna module 397 may include an antenna including a conductor formed on a substrate (eg, a PCB) or a radiator formed of a conductive pattern.
  • the antenna module 397 may include a plurality of antennas (eg, an array antenna). In this case, at least one antenna suitable for a communication scheme used in a communication network such as the first network 398 or the second network 399 is connected from the plurality of antennas by, for example, the communication module 390 . can be selected. A signal or power may be transmitted or received between the communication module 390 and an external electronic device through the selected at least one antenna.
  • other components eg, a radio frequency integrated circuit (RFIC)
  • RFIC radio frequency integrated circuit
  • the antenna module 397 may form a mmWave antenna module.
  • the mmWave antenna module comprises a printed circuit board, an RFIC disposed on or adjacent to a first side (eg, bottom side) of the printed circuit board and capable of supporting a designated high frequency band (eg, mmWave band); and a plurality of antennas (eg, an array antenna) disposed on or adjacent to a second side (eg, top or side) of the printed circuit board and capable of transmitting or receiving signals of the designated high frequency band. can do.
  • peripheral devices eg, a bus, general purpose input and output (GPIO), serial peripheral interface (SPI), or mobile industry processor interface (MIPI)
  • GPIO general purpose input and output
  • SPI serial peripheral interface
  • MIPI mobile industry processor interface
  • the command or data may be transmitted or received between the electronic device 301 and the external electronic device 304 through the server 308 connected to the second network 399 .
  • Each of the external electronic devices 302 or 304 may be the same as or different from the electronic device 301 .
  • all or part of the operations executed by the electronic device 301 may be executed by one or more external electronic devices 302 , 304 , or 308 .
  • the electronic device 301 may perform the function or service itself instead of executing the function or service itself.
  • one or more external electronic devices may be requested to perform at least a part of the function or the service.
  • One or more external electronic devices that have received the request may execute at least a part of the requested function or service, or an additional function or service related to the request, and transmit a result of the execution to the electronic device 301 .
  • the electronic device 301 may process the result as it is or additionally and provide it as at least a part of a response to the request.
  • cloud computing, distributed computing, mobile edge computing (MEC), or client-server computing technology may be used.
  • the electronic device 301 may provide an ultra-low latency service using, for example, distributed computing or mobile edge computing.
  • the external electronic device 304 may include an Internet of things (IoT) device.
  • the server 308 may be an intelligent server using machine learning and/or neural networks.
  • the external electronic device 304 or the server 308 may be included in the second network 399 .
  • the electronic device 301 may be applied to an intelligent service (eg, smart home, smart city, smart car, or health care) based on 5G communication technology and IoT-related technology.
  • the processor 320 connects an edge device (eg, the edge device 210 of FIG. 2A ) and a leaf device (eg, the leaf device 220 of FIG. 2A ) in the home network using the application 346 ). Control related to the edge computing service used can be performed.
  • an edge device eg, the edge device 210 of FIG. 2A
  • a leaf device eg, the leaf device 220 of FIG. 2A
  • Control related to the edge computing service used can be performed.
  • the application 346 may provide a function of registering the edge device and the leaf device with the IoT server (eg, the IoT management server 240 of FIG. 2A ).
  • the processor 320 may discover at least one edge device and a leaf device in the home network using the communication module 390 and receive device information (eg, identification information, network information) of each device. .
  • the processor 320 may display a list of identified devices on the application.
  • the processor 320 may request registration by transmitting device information of the edge device or the leaf device selected based on the user input to the IoT server.
  • the processor 320 may receive the name and/or location information of each device on the application 346 .
  • the processor 320 may receive data (eg, image streaming, sound data) obtained from a sensor of the leaf device from the leaf device from the cloud network while the edge mode of the edge device is deactivated. Thereafter, when the edge computing service is started, the data acquired from the leaf device is transmitted to the edge device, and the user device (eg, the user device 130 of FIG. 1 , the user device 230 of FIG. 2A , or the electronic device) 301 ) may receive sensor data and analysis data directly from the edge device or through a cloud network (eg, the cloud network 140 of FIG. 1 ) from the edge device.
  • data eg, image streaming, sound data
  • the processor 320 may display information related to connection or disconnection between the edge device and the leaf device on an application displayed on the display. For example, when the leaf device changes the connection from the first edge device to the second edge device according to a handover event, the user device 301 selects one of the leaf device, the first edge device, the second edge device, or the IoT server. Information related to the update of the edge-leaf connection may be received from at least one. The user device 301 may display updated edge-leaf connection information through an application based on the received information.
  • At least one of the components of the edge device or the leaf device may be configured to be at least partially identical to or similar to components of the electronic device 301 (eg, a user device).
  • the sensor of the leaf device may perform substantially the same function and/or operation as the sensor module 376 of the electronic device 301 .
  • the communication module of the edge device eg, the communication module 420 of FIG. 4
  • the interface eg, the interface 212 of FIG. 2A
  • the electronic device 301 may perform substantially the same function and/or operation as that of the interface 377 .
  • FIG. 4 is a block diagram of an edge device according to various embodiments of the present disclosure.
  • the edge device 400 shown in FIG. 4 is a first edge device (eg, the first edge device 1010 of FIG. 10 ) or a second edge device (eg, the second edge device of FIG. 10 ) according to various embodiments. 1020)) can be operated.
  • a handover event occurs while the edge device 400 is connected to a leaf device (eg, the leaf device 220 of FIG. 2A ) and performs an edge computing service, so that the leaf device is handed over to another edge device.
  • the edge device 400 may operate as a first edge device, and a handover event occurs while another edge device 400 is connected to a leaf device to perform an edge computing service, so that the leaf device becomes an edge device ( 400), the edge device 400 may operate as a second edge device.
  • a plurality of edge devices may exist, and each edge device may be a different type of device.
  • the edge device 400 may be implemented as a TV, a tablet PC, a laptop PC, or the like.
  • descriptions of features for the edge device 400 to execute device-specific functions will be omitted, and only operations necessary to operate as the edge device 400 in the edge computing system will be described.
  • the communication module 420 supports wireless communication (eg, short-range communication (Wi-Fi), cellular communication), a leaf device (eg, the leaf device 220 of FIG. 2A ), a user device ( For example: the user device 230 of FIG. 2A ) and an external server (eg, the IoT management server and the IoT hub server of FIG. 2A ) may transmit/receive data.
  • the communication module 420 is short-range wireless communication, near field communication (NFC), Bluetooth, bluetooth low energy (BLE), WiFi Direct, and a mesh network (eg, zigbee, z-wave). ) and/or UWB (ultra-wideband), and cellular communication, may be connected to a 4G network, and/or a 5G network (eg, standalone (SA), non-standalone (NSA)).
  • the sensor 440 may detect a movement of the electronic device.
  • the edge device 400 may be a device portable by a user (eg, a tablet PC, a laptop PC), and a gyroscope sensor to detect movement (or movement) of the edge device 400 , It may include at least one motion detection sensor such as an acceleration sensor.
  • the edge device 400 includes a sensor hub (not shown) that collects and processes data of various sensors 440 , and sensor data collected from the sensor hub may be provided to the processor 410 .
  • the power management module 450 may check the power state of the edge device 400 and may be implemented as at least a part of a power management integrated circuit (PMIC). For example, the power management module 450 detects the power state of the edge device 400, such as whether the edge device 400 is connected to an external power source, the amount of charge of the battery (not shown), and sends it to the processor 410 . can transmit the power state of the edge device 400, such as whether the edge device 400 is connected to an external power source, the amount of charge of the battery (not shown), and sends it to the processor 410 . can transmit
  • PMIC power management integrated circuit
  • the memory 430 may include a volatile memory and/or a non-volatile memory, and may store various data used in at least one component (eg, the processor 410 ) of the edge device 400 . It may be temporarily and/or permanently stored.
  • the memory 430 may store various instructions that may be executed by the processor 410 . Such instructions may include various control commands including arithmetic and logical operations, data movement, and input/output that can be recognized by the processor 410 .
  • the memory 430 may store device information, an edge runtime, a basic module, a device module, and a service module in relation to an edge computing service.
  • the device information may include identification information of the edge device 400 , for example, device ID, manufacturer, model name, capability, and device type.
  • the device information may further include at least some of location information (eg, a room, living room) and network information (eg, an IP address) of the edge device 400 .
  • location information e.g, a room, living room
  • network information e.g, an IP address
  • At least some of the device information may be input by the user on an application of the user device (eg, the electronic device 301 of FIG. 3 or the user device 301 of FIG. 3 ).
  • the edge runtime may include a daemon program for interworking with the IoT server.
  • the edge runtime is not executed when the edge mode of the edge device 400 is deactivated.
  • this value is It can be implemented using
  • the basic module may be configured as a container as a program necessary for communication with the IoT server.
  • a basic module for edge runtime and edge computing may be installed in the edge device 400 through a process process or software upgrade of the edge device 400 .
  • the edge device 400 may perform an over the air (OTA) software update as a software upgrade.
  • the OTA software update may include an open mobile alliance (OMA) download, a firmware OTA (FOTA), or a plain FTP (FTP).
  • the edge device 400 may store a device module and a service module as a module required for an edge computing service.
  • the device module may correspond to each connected leaf device, and the service module may correspond to each service to be performed.
  • a plurality of device modules and/or service modules may be installed according to the number of connected leaf devices and the number of services to be performed. (Example: device module 1 (219a) and device module 2 (219b) in FIG. 2A)
  • the device module converts data received according to the first protocol from the leaf device according to the second protocol (eg, message queue telemetry transport (MQTT)) and transmits it to an external server.
  • the first protocol and the second protocol are protocols related to a control channel for the edge device 400 to communicate with the IoT server, and the first protocol is a web socket.
  • the control channel is a channel for providing and/or processing device information
  • the edge device 400 may communicate with the IoT server using the control channel.
  • the service module may include programs that process and/or analyze the received data.
  • the edge device 400 During the process or software upgrade of the edge device 400 , only the edge runtime and the basic module may be installed, and the device module and the service module may not be installed. Thereafter, when the edge device 400 is connected to the leaf device, the device module and the service module may be downloaded and installed from the IoT server (eg, the module registry 254 of FIG. 2A ).
  • the IoT server eg, the module registry 254 of FIG. 2A
  • the memory 430 may further store various programs for executing a unique function of the edge device 400 (eg, an image output function of a TV).
  • the processor 410 is a configuration capable of performing an operation or data processing related to control and/or communication of each component of the edge device 400 , and includes a communication module 420 and a memory 430 . It may be operatively, functionally, and/or electrically coupled to each component of the back edge device 400 .
  • the edge device 400 is the first edge device (eg, in FIG. 10 ).
  • the second edge device eg, the second edge device 1020 of FIG. 10
  • a handover event is detected and an edge connection change process is performed according to the handover event.
  • various operations will be described.
  • the edge device 400 is connected to a leaf device (eg, the leaf device 220 of FIG. 2A ) through a home network, and may perform an edge computing service based on data received from the leaf device.
  • a leaf device eg, the leaf device 220 of FIG. 2A
  • the edge device 400 uses an audio-video (AV) module and an artificial intelligence (AI) vision module to stream video transmitted from the leaf device to an IoT server (eg:
  • AV audio-video
  • AI artificial intelligence
  • the data may be transmitted to the IoT management server 240 of FIG. 2A
  • image analysis eg, object recognition, face recognition
  • edge computing services that can be implemented through the edge device 400 and the leaf device and modules required accordingly are as follows.
  • Edge Computing Services device module service module camera Face Recognition, Object Detection MQTT Broker av stream gateway Face AI, Vision AI (Doorbell Service, Delivery notification) camera Daily Summary MQTT Broker av stream gateway Face AI, Pet AI (Daily Summary Video Clip) AI speaker Speaker Recognition MQTT Broker av stream gateway Speaker AI (Personized Service) TV Contents Recognition MQTT Broker av stream gateway Contents AI (AD Service, Shopping Service) Robot Vacuum Cleaner Pet Recognition, Bark detection MQTT Broker av stream gateway Pet AI (Pet Service)
  • the MQTT broker may be a module that provides a channel for exchanging commands and/or events between the leaf device and the edge device 400 .
  • the message queuing telemetry transport (MQTT) protocol includes a broker, a publisher, and a subscriber, and when an MQTT broker is installed in the edge device 400 , the MQTT broker of the edge device 400 receives the topic published by the publisher. It can perform the function of relaying to a subscriber.
  • the AV stream gateway may perform a function of relaying audio and/or video streaming transmitted from the leaf device to the AI module.
  • the processor 410 is connected to the leaf device to perform edge computing service while the edge device 400 state information (eg, resource status, network connection status, connected leaf device information, service being performed) ) to another device (eg, a second edge device) and/or an IoT server located in the home network.
  • the edge device 400 state information eg, resource status, network connection status, connected leaf device information, service being performed
  • another device eg, a second edge device
  • IoT server located in the home network.
  • the processor 410 may detect a handover event of an edge computing service being performed. For example, the processor 410 detects a handover event based on at least one of a movement (or movement) of the electronic device acquired using the sensor 440 or the strength of a signal received through the communication module 420 . can detect Alternatively, the processor 410 may detect a handover event based on at least one of available resources of the processor 410 and/or the memory 430 or the power state of the electronic device obtained from the power management module.
  • the processor 410 monitors information such as movement, resource shortage, or power state change during execution of the edge computing service, detects a handover event in advance before a situation in which the edge computing service is impossible to perform, and other devices can be forwarded to
  • a method for the processor 410 to detect a handover event will be described in more detail with reference to FIGS. 7 to 9 .
  • the edge device 400 may transmit a handover event to the IoT server through another network (eg, a cellular network).
  • another network eg, a cellular network
  • the processor 410 may identify the second edge device 400 located in the home network to handover the edge computing service.
  • the edge device 400 may identify the second edge device 400 through a discovery process or based on information received from the IoT server before the handover event occurs, or When an over event occurs, the second edge device 400 may be checked through discovery, or information related to the second edge device 400 located on the home network may be requested from the IoT server.
  • the processor 410 may check whether another identified edge device has a capability to receive an edge computing service handover with a leaf device.
  • the capability of the edge device includes whether the checked edge mode of the second edge device is activated, what services it can provide, whether it can be additionally connected to the leaf device, and the physical resources of the second edge device (eg, a processor). , memory available resources), an IP address, and may include at least some of OCF (open connectivity foundation) capability.
  • OCF open connectivity foundation
  • the processor 410 transmits the handover event to at least one of the second edge device, the leaf device, or the IoT server.
  • the processor 410 may transmit at least some of information on the connected leaf device, the type of service being performed, a module used for the service, and information on the second edge device to be handed over together with the handover event.
  • the processor 410 may terminate the edge computing service by disconnecting the leaf device.
  • the processor 410 notifies the IoT server of handover of the edge computing service and disconnection with the leaf device, and accordingly, the IoT server may update edge-leaf connection information.
  • the processor 410 may check a handover event of the edge computing service of the first edge device and the leaf device. For example, the processor 410 may receive information related to the handover event from the first edge device, and even if information related to the handover event is not received from the first edge device, the edge computing service delivered by the leaf device Based on a change request or a alive signal that the second edge device periodically exchanges with the first edge device, the occurrence of a handover event is confirmed and/or an operation for handover of the edge computing service to the second edge device is initiated.
  • the processor 410 may check a handover event of the edge computing service of the first edge device and the leaf device. For example, the processor 410 may receive information related to the handover event from the first edge device, and even if information related to the handover event is not received from the first edge device, the edge computing service delivered by the leaf device Based on a change request or a alive signal that the second edge device periodically exchanges with the first edge device, the occurrence of a handover event is confirmed and/or an operation
  • the processor 410 may check whether the edge device 400 can perform an edge computing service in response to a handover event. For example, the processor 410 is at least among the available resources of the processor 410 and/or memory, whether the edge mode is activated, or whether a module corresponding to the edge computing service being performed between the first edge device and the leaf device is installed. Based on some, it may be confirmed whether the edge device 400 can perform the edge computing service.
  • the processor 410 may transmit the result to at least one of the first edge device, the leaf device, and the IoT server.
  • the leaf device when it is determined that the edge device 400 cannot perform the edge computing service, the leaf device is connected to another edge device (eg, a third edge device in the network) or an IoT server to provide a service to at least one of another edge device, leaf device, or IoT server to perform
  • another edge device eg, a third edge device in the network
  • an IoT server to provide a service to at least one of another edge device, leaf device, or IoT server to perform
  • the processor 410 releases a connection with the first edge device to the leaf device in response to a handover event, and requests an edge computing service change including establishing a connection between the edge device 400 and the edge computing service. can be transmitted.
  • the processor 410 may perform a connection process for an edge computing service.
  • FIG. 5 is a block diagram of a leaf device according to various embodiments.
  • the leaf device 500 may include a communication module 520 , a processor 510 , and a sensor 540 , and even if some of the illustrated components are omitted or replaced, this document Various embodiments of can be implemented.
  • a plurality of leaf devices may exist, and each leaf device may be a different type of device.
  • the leaf device 500 may be implemented as a camera, a refrigerator, a light bulb, a digital thermometer, or the like.
  • descriptions of features for the leaf device 500 to execute device-specific functions will be omitted, and only operations necessary to operate as the leaf device 500 in the edge computing system will be described.
  • the communication module 520 supports wireless communication (eg, Wi-Fi), an edge device (eg, the edge device 210 of FIG. 2A , the edge device 400 of FIG. 4 ), a user A device (eg, the user device 230 of FIG. 2A , the user device 301 of FIG. 3 ) and an external server (eg, the IoT management server 240 of FIG. 2A , and the IoT hub server 250 ) can
  • wireless communication eg, Wi-Fi
  • an edge device eg, the edge device 210 of FIG. 2A , the edge device 400 of FIG. 4
  • a user A device eg, the user device 230 of FIG. 2A , the user device 301 of FIG. 3
  • an external server eg, the IoT management server 240 of FIG. 2A , and the IoT hub server 250
  • the leaf device 500 may include at least one sensor 540 .
  • the leaf device 500 may include an IP camera, it may include an image sensor for acquiring surrounding image data, and if it is an AI speaker, it may include a microphone for detecting surrounding sound.
  • a sensor 540 for sensing various data such as temperature, pressure, and impact amount may be provided according to the type of the leaf device 500 .
  • the processor 510 is a configuration capable of performing an operation or data processing related to control and/or communication of each component of the leaf device 500 , and a communication module 520 , a sensor 540 . It may be operatively, functionally, and/or electrically coupled with each component of the back leaf device 500 .
  • the leaf device 500 may be connected to a first edge device in the home network (eg, the first edge device 1010 of FIG. 10 ) to perform an edge computing service, and according to a handover event
  • the connection with the first edge device may be released and the edge computing service may be performed by being connected to the second edge device (eg, the second edge device 1020 of FIG. 10 ).
  • the processor 510 may perform an edge computing service by transmitting data (eg, image streaming) acquired through the sensor 540 to the first edge device through the communication module 520 .
  • data eg, image streaming
  • the processor 510 may check a handover event of the edge computing service.
  • the processor 510 may receive information related to a handover event from at least one of the first edge device, the second edge device, and the IoT server.
  • the processor 510 makes it impossible for the first edge device to perform an edge computing service when socket communication is not performed or when a connection termination on a transmission protocol is detected as an alive packet does not arrive. can be confirmed as
  • the processor 510 may transmit handover event information to the second edge device.
  • the processor 510 may identify a connectable second edge device for an edge computing service in response to a handover event. For example, the processor 510 may check information on the second edge device included in information related to a handover event received from at least one of the first edge device, the second edge device, and the IoT server. According to another embodiment, the second edge device may be identified through discovery on the home network.
  • the processor 510 may check whether the checked second edge device can perform the edge computing service. For example, the processor 510 is based on at least a part of the available resources of the processor 510 and/or memory of the second edge device, whether the edge mode is activated, or whether a module corresponding to the edge computing service is installed, It may be checked whether the second edge device can perform the edge computing service.
  • the processor 510 may request a connection between the second edge device and the edge computing service.
  • the processor 510 may transmit a request for an edge computing service or a cloud computing service to the IoT server.
  • the processor 510 may be connected to another edge device (eg, a third edge device) based on information received from the IoT server to perform an edge computing service or to perform a cloud computing service through the IoT server. there is.
  • FIG. 6 is a flowchart of a handover method of an edge device according to various embodiments.
  • the first edge device is an edge device that is connected to the current leaf device (eg, the leaf device 500 of FIG. 5 ) to perform edge computing services
  • the second edge device is located on the home network. It may be a device that can be connected to a leaf device when a handover event occurs.
  • the same edge device eg, edge device 400 in FIG. 4
  • the edge device may operate as the second edge device, and the edge device that has operated as the second edge device may operate as the first edge device.
  • the operation shown in FIG. 6 is not limited to operating in a specific subject (eg, a first edge device, a second edge device, a leaf device, and an IoT server).
  • a particular operation may be performed by a plurality of devices on the edge computing system, or may be performed by a device other than that described.
  • the first edge device may be connected to the leaf device on a home network to perform an edge computing service.
  • the leaf device is an IP camera
  • the edge device uses an audio-video (AV) module and an artificial intelligence (AI) vision module to stream video transmitted from the leaf device to an IoT server (eg, in FIG. 2A ).
  • AV audio-video
  • AI artificial intelligence
  • the IoT management server 240 and the IoT hub server 250 may be transmitted, and the image analysis data may be transmitted to the leaf device and/or the IoT server.
  • the first edge device is connected to the leaf device and while performing the edge computing service, the state information of the first edge device (eg, resource status, network connection status, information of the connected leaf device, service being performed) can be transmitted to another device (eg, a second edge device) and/or an IoT server located in the home network.
  • the state information of the first edge device eg, resource status, network connection status, information of the connected leaf device, service being performed
  • another device eg, a second edge device
  • IoT server located in the home network.
  • the first edge device, the second edge device, or the leaf device may detect a handover event.
  • the first edge device may be a device that a user can carry and move (eg, a tablet PC, a laptop PC), and the coverage of a Wi-Fi signal connectable to an access point (AP) of a home network is within several tens of meters. Since it is short, when the user takes the first edge device outdoors, the first edge device leaves the home network, and thus the edge computing service cannot be performed. In addition, since the first edge device performs edge computing services using some of the hardware and/or software resources, resources Occupying , there may be a shortage of resources for edge computing services. Also, when the power of the first edge device is insufficient, it may be impossible to provide the edge computing service. According to various embodiments, as described above, a handover event may be generated by determining a situation in which the first edge device cannot smoothly perform the edge computing service.
  • AP access point
  • the first edge device may determine a handover event based on at least one of a movement of the first edge device, a resource shortage, or a change in a power state.
  • the first edge device may monitor the information while the edge computing service is being performed, and may generate a handover event in advance before a situation in which the edge computing service cannot be performed occurs.
  • the first edge device may transmit the handover event to at least one of the second edge device, the leaf device, and the IoT server.
  • the first edge device may transmit a handover event to the IoT server through another network (eg, a cellular network).
  • the leaf device and/or the second edge device may detect a handover event by detecting that the signal transmitted from the first edge device is no longer transmitted.
  • a method for the first edge device to determine a handover event will be described in more detail with reference to FIGS. 7 to 9 .
  • the first edge device may identify the second edge device located in the home network.
  • the first edge device may identify the second edge device through a discovery process or based on information received from the IoT server before the handover event occurs, or the handover event occurs
  • the second edge device may be identified through discovery, or information related to the second edge device located on the home network may be requested from the IoT server to be transmitted.
  • operation 630 may be performed by a leaf device or an IoT server.
  • the leaf device receives a handover event from the first edge device or the IoT server or detects a handover event according to a change in a network signal
  • the second device based on the discovery process or information received from the IoT server You can check the edge device.
  • the first edge device may check whether the second edge device checked in operation 630 has a capability to receive an edge computing service handover with the leaf device.
  • the capability of the second edge device includes whether the checked edge mode of the second edge device is activated, what services it can provide, whether it can be additionally connected to the leaf device, and the physical resources of the second edge device (e.g. : processor, memory available resources), IP address, physical and/or software resources supported by the device, and methods of controlling the resources (eg, defined in IoT resource related standards such as open connectivity foundation (OCF), M2M, Connected Home over IP) capability) may include at least some of them.
  • IoT resource related standards such as open connectivity foundation (OCF), M2M, Connected Home over IP
  • the first edge device may determine that the edge mode is activated when the edge runtime of the second edge device is operating (or running).
  • the first edge device may confirm that the corresponding service can be provided.
  • the first edge device may check the service that the second edge device can perform, the device module installed in the second edge device, and the service module based on the device information received from the second edge device (or IoT server).
  • the first edge device has sufficient hardware and/or software resources to receive the leaf device and provide the service. can be checked to determine if it can be further connected with a leaf device.
  • the first edge device can synchronize and check the capability of the second edge device in advance before the handover event occurs, or the capability information can be uploaded to the IoT server in advance, or when a handover event occurs
  • the first edge device may be identified through the discovery process.
  • the discovery may be in the form of receiving a response by transmitting it in the network as a broadcasting message as a query on whether the edge computing service is supported.
  • the first edge device checks information that can be confirmed in advance among the capabilities of the second edge device (eg, a service that can be provided, OCF capability, etc.) through synchronization and requires confirmation in real time.
  • Information eg, physical resource, etc.
  • the first edge device may select one of them to handover the edge computing service. For example, the first edge device may determine one edge device suitable for receiving an edge computing service handover based on device information (or cloud parameters) and/or operation state information (or local parameters) of a plurality of edge devices.
  • the device information includes account, location information, edge computing service list, user weight information, device model information, service performance, online status, battery status, central processing unit (CPU) or random access memory (RAM) usage
  • edge service status may include at least one of
  • the operation state information may include at least one of whether the device wakes up or sleeps, an application running in the foreground, a connection state of a local network, and IP address information.
  • the IoT server primarily selects a part of a plurality of edge devices as a candidate device using at least a part of the device information and the operation state information, and the first edge device is a candidate device selected by the IoT server By establishing a connection with and checking the remaining part of device information and operation state information, one of the candidate devices may be finally determined as the second edge device.
  • operation 640 may be performed by a leaf device and/or an IoT server.
  • the first edge device may perform a handover operation of the edge computing service to the second edge device.
  • the process of handover of the edge computing service to the second edge device may be initiated by the first edge device, the second edge device, the leaf device, or the IoT server. Detailed embodiments will be described in more detail with reference to FIGS. 10-16. do it with
  • the second edge device may be connected to the leaf device to perform an edge computing service. Accordingly, the leaf device may transmit data (eg, image streaming) acquired through the sensor to the second edge device, and data analysis (eg, image analysis) may be performed in the second edge device.
  • the first edge device may pass data that has not been provided to the leaf device, but which has already been processed, to the second edge device.
  • the first edge device when the handover process of the edge computing service is started (or completed), the first edge device may release the connection with the leaf device.
  • the second edge device and/or the leaf device when the handover is completed (or initiated), the second edge device and/or the leaf device notifies the IoT server of a connection change, and the IoT server may update edge-leaf connection information.
  • FIG. 7 is a flowchart of a method of determining a handover event according to movement of an edge device according to various embodiments of the present disclosure
  • the edge device (eg, the edge device 400 of FIG. 4 ) includes at least one sensor (eg, the sensor 440 of FIG. 4 ) capable of detecting a motion of the edge device, and the sensor can be used to detect the motion of edge devices in real time.
  • the sensor eg, the sensor 440 of FIG. 4
  • the edge device may be connected to a leaf device (eg, the leaf device 500 of FIG. 5 ) to perform an edge computing operation.
  • a leaf device eg, the leaf device 500 of FIG. 5
  • the edge device uses an audio-video (AV) module and an artificial intelligence (AI) vision module to transmit video streaming from the leaf device to the IoT server, and analyze the video. Data can be sent to leaf devices and/or IoT servers.
  • AV audio-video
  • AI artificial intelligence
  • the edge device may determine whether the motion of the edge device detected through a sensor (eg, a gyro sensor or an acceleration sensor) is equal to or greater than a reference value. For example, the edge device may determine that the motion of the edge device is equal to or greater than a reference value when the motion of the edge device is equal to or greater than a predetermined speed and/or distance, or the number of times that the motion is sensed is greater than or equal to a predetermined value.
  • a sensor eg, a gyro sensor or an acceleration sensor
  • the edge device may determine whether the strength of a signal received from the AP through the communication module decreases.
  • the signal strength may be a received signal strength indicator (RSSI) and may be detected by a network chipset (eg, Wi-Fi chipset).
  • RSSI received signal strength indicator
  • network chipset eg, Wi-Fi chipset
  • the edge device determines the mobility of the edge device. is determined to have occurred, and it is possible to monitor whether an edge handover event has occurred.
  • the edge device may transmit information related to monitoring of the handover event to a connected leaf device, an external edge device connected to a home network, or an IoT server. Even while the edge device is monitoring the handover event, the edge computing service can continue to be performed by connecting with the leaf device.
  • the edge device may determine whether the detected motion of the edge device is greater than or equal to a predetermined distance and/or speed, and may determine whether the strength of a signal received from the AP is less than or equal to a predetermined value. According to an embodiment, the edge device may check only one of the motion of the edge device or the strength of a signal.
  • edge device For example, if a continuous motion is detected in the edge device and the signal received from the AP is weakened, it can be viewed as a situation in which the user moves the portable edge device from the room where the edge device and the leaf device are installed to another space. Since the AP has limited coverage, in this case, it can be seen that the edge device can no longer perform the function of the edge device on the home network.
  • the edge device determines that an edge handover event has occurred.
  • An operation for handover of an edge computing service to an external edge device (eg, the second edge device of FIG. 10 ) may be executed.
  • the edge device checks whether the change in motion and/or signal strength is lower than a predetermined level while monitoring the handover event, in this case, ends monitoring of the handover event, and edge computing service with the leaf device can continue to be performed.
  • FIG. 8 is a flowchart of a method of determining a handover event according to a resource of an edge device according to various embodiments of the present disclosure
  • the edge device may include a processor (eg, processor 410 of FIG. 4 ) and/or memory (eg, memory 420 of FIG. 4 ) of the edge device ) can determine whether to handover the edge computing service based on the available resources.
  • Edge device must perform its own functions (eg, tablet PC application, TV video transmission) other than edge computing service , it is possible to handover a leaf device to another edge device capable of edge computing services.
  • the edge device may check whether a situation that may change the resource state of the edge device, such as a user input or an alarm on the system, occurs, and monitor an edge handover event.
  • the edge device may be connected to a leaf device to perform an edge computing operation.
  • the edge device may detect whether a user input on the touch screen is generated. Since the user input on the touch screen is for performing an application or function provided by the edge device, available resources of a processor and/or memory required for an edge computing service may be reduced.
  • the edge device may detect whether a key (eg, hard key, soft key) input of the edge device occurs.
  • a key eg, hard key, soft key
  • the edge device may detect whether an input using a remote control is received.
  • the edge device may determine whether an alarm is generated in the operating system (OS). For example, it is possible to check the notification for the user provided by the operating system of the edge device, such as an emergency text message, SNS, system alarm, and the like.
  • OS operating system
  • the edge device may start resource monitoring.
  • operation 830 may be performed when any one of operations 822, 824, 826, and 828 is satisfied, and according to an embodiment, operation 830 may be performed when two or more conditions are satisfied.
  • the edge device may check how much of the hardware and/or software resources of the edge device required for the edge computing service are being used according to the execution of other functions or the occurrence of an event.
  • the edge device may determine whether the currently available resource is lower than a threshold value.
  • the threshold value may be determined according to the minimum amount of processor and/or memory required for the edge computing service.
  • the edge device determines that an edge handover event has occurred, and provides an edge to an external edge device (eg, the second edge device of FIG. 10 ).
  • An operation for handover of a computing service may be performed.
  • the edge device is The monitoring of the over event is terminated, and edge computing services with the leaf device can be continued.
  • FIG. 9 is a flowchart of a method of determining a handover event according to a power state or resource of an edge device according to various embodiments of the present disclosure
  • the edge device eg, the edge device 400 of FIG. 4
  • the power state of the edge device can be detected.
  • the edge device may be connected to a leaf device to perform an edge computing operation.
  • the edge device may determine whether the edge device operates in a low power mode. For example, depending on the setting of the edge device, the edge device may be set to operate in a low power mode when the edge device is not connected to an external power source and uses the power of the battery, or when the remaining amount of the battery is less than a predetermined value while the battery is not being charged. . If the edge device operates in low power mode or the remaining battery level is below a predetermined level, the edge device may be turned off due to insufficient power. Computing services may be continuously performed.
  • the edge device may determine whether a resource of a processor and/or a memory of the edge device is insufficient.
  • the edge device determines that an edge handover event has occurred, and provides an edge to an external edge device (eg, the second edge device of FIG. 10 ).
  • An operation for handover of a computing service may be performed.
  • FIG. 10 is a diagram illustrating a change process of an edge device when an edge handover is initiated by a second edge device according to various embodiments of the present disclosure.
  • FIG. 10 illustrates an embodiment in which the first edge device 1010 and the second edge device 1020 operate as subjects of handover when a handover event can be detected in advance.
  • the first edge device 1010 may be connected to the leaf device 1030 on a home network to perform an edge computing service.
  • the first edge device 1010 may detect a handover event.
  • the first edge device 1010 includes the movement of the first edge device 1010 acquired using a sensor (eg, the sensor 440 of FIG. 4 ), and a communication module (eg, the communication module of FIG. 4 ) 420)), the resource status of the processor (eg, the processor 410 of FIG. 4 ) and/or the memory (eg, the memory 430 of FIG. 4 ), and the power management module (eg, FIG. 4 )
  • the handover event may be detected based on at least one of the power states detected through the power management module 450 of the .
  • Various embodiments in which the first edge device 1010 detects a handover event have been described above with reference to FIGS. 7 to 9 .
  • the first edge device 1010 may identify the second edge device 1020 in the network to which the edge computing service is to be handed over. According to an embodiment, the first edge device 1010 checks the second edge device 1020 through a discovery process or based on information received from the IoT server 1040 before the handover event occurs. Alternatively, when a handover event occurs, the second edge device 1020 is checked through discovery, or information related to the second edge device 1020 located on the home network is transmitted to the IoT server 1040. you can request
  • the first edge device 1010 may check whether the checked second edge device 1020 has the capability to receive the edge computing service handover.
  • the capability of the second edge device 1020 is whether the checked edge mode of the second edge device 1020 is activated, what services it can provide, whether it can be additionally connected to the leaf device 1030.
  • the second edge device 1020 may include at least some of physical resources (eg, processor, memory available resources), an IP address, and open connectivity foundation (OCF) capability.
  • physical resources eg, processor, memory available resources
  • OCF open connectivity foundation
  • the first edge device 1010 may transmit a handover event to at least one of the second edge device 1020 , the leaf device 1030 , and the IoT server 1040 .
  • the first edge device 1010 may transmit information including information on the currently connected leaf device 1030 and edge computing service, or may transmit only information on the occurrence of a handover event.
  • the first edge device 1010 may broadcast a handover event to devices on a home network.
  • the second edge device 1020 may identify a handover event according to handover event information transmitted (or broadcast) from the first edge device 1010 .
  • the second edge device 1020 may request a change of the edge computing service delivered by the leaf device 1030 or the second edge device ( The generation of the handover event may be confirmed based on the alive packet exchanged periodically by the 1020 with the first edge device 1010 . In this case, operation 1064 may be omitted.
  • information on the leaf device 1030 has not been obtained in advance through connection with the first edge device 1010, or the handover event information transmitted from the first edge device 1010 (operation 1064). If information related to the leaf device 1030 is not included, in operation 1070 , the second edge device 1020 may identify the leaf device 1030 through discovery. Contrary to this, when the second edge device 1020 acquires information on the leaf device 1030 through handover event information or a signal periodically exchanged, operation 1070 may be omitted.
  • the second edge device 1020 may transmit an edge computing connection change request to the leaf device 1030 .
  • the leaf device 1030 may transmit an edge connection request to the second edge device 1020 in response to the request of the second edge device 1020 . Also, in operation 1076 , the leaf device 1030 may release the connection with the first edge device 1010 . According to an embodiment, the first edge device 1010 may pass data that has not been provided to the leaf device 1030 but has already been processed (eg, image analysis data) to the second edge device 1020 . Although operation 1076 is shown to be performed after operation 1074 in FIG. 10 , the order in which operations 1074 and 1076 are performed may be changed, and each operation may be performed at least partially simultaneously.
  • the second edge device 1020 may be connected to the leaf device 1030 to perform an edge computing service.
  • the edge computing service may be the same service as the edge computing service in operation 1050 .
  • the second edge device 1020 and/or the leaf device 1030 when the handover is completed (or initiated), notifies the IoT server 1040 of a connection change, and in operation 1090 , the IoT server 1040 may update edge-leaf connection information.
  • FIG. 11 is a diagram illustrating a process of changing an edge device when an edge handover is initiated by a second edge device according to various embodiments of the present disclosure.
  • FIG. 11 illustrates an embodiment in which the first edge device 1110 and the second edge device 1120 operate as subjects of handover when a handover event cannot be detected in advance.
  • the first edge device 1110 may be connected to the leaf device 1130 on a home network to perform an edge computing service.
  • a handover event may occur in the first edge device 1110 .
  • the handover event may occur in a situation in which the first edge device 1110 cannot detect it in advance, unlike the embodiment of FIG. 10 described above.
  • the first edge device 1110 transmits handover event information to the IoT server 1140 by connecting to another network (eg, a cellular network) when communication with an access point (AP) is impossible after moving outdoors. can be transmitted
  • another network eg, a cellular network
  • the leaf device 1130 may detect a handover event according to whether a signal transmitted from the first edge device 1110 is received. For example, when the leaf device 1130 does not perform socket communication or when a connection termination on a transmission protocol is detected as an alive packet does not arrive, the first edge device 1110 performs an edge computing service. It can be verified that this is impossible.
  • the leaf device 1130 and/or the IoT server 1140 may transmit handover event information to the second edge device 1120 .
  • the second edge device 1120 may check a handover event according to handover event information transmitted from the leaf device 1130 and/or the IoT server 1140 .
  • the second edge device 1120 may check the occurrence of a handover event based on the alive packet exchanged periodically with the first edge device 1110 . In this case, operation 1162 may be omitted.
  • information on the leaf device 1130 is not obtained in advance through connection with the first edge device 1110 , or a handover event received from the leaf device 1130 and/or the IoT server 1140 . If the information (operation 1162) does not include information related to the leaf device 1130, in operation 1170, the second edge device 1120 may identify the leaf device 1130 through discovery. Contrary to this, when the second edge device 1120 acquires the information of the leaf device 1130 through handover event information or a signal exchanged periodically, operation 1170 may be omitted.
  • the second edge device 1120 may transmit an edge computing connection change request to the leaf device 1130 .
  • the leaf device 1130 may transmit an edge connection request to the second edge device 1120 in response to the request of the second edge device 1120 .
  • the second edge device 1120 and the first edge device 1110 are connected to the leaf device 1130 to perform an edge computing service.
  • the edge computing service may be the same service as the edge computing service in operation 1150 .
  • the second edge device 1120 and/or the leaf device 1130 when the handover is completed (or initiated), notifies the IoT server 1140 of a connection change, and in operation 1190 , the IoT server 1140 may update edge-leaf connection information.
  • FIG. 12 is a diagram illustrating a change process of an edge device when an edge handover is initiated by a leaf device according to various embodiments of the present disclosure.
  • leaf device 12 illustrates an embodiment in which the leaf device 1230 operates as a handover subject when a handover event can be detected in advance.
  • the first edge device 1210 may be connected to the leaf device 1230 on a home network to perform an edge computing service.
  • the first edge device 1210 may detect a handover event and transmit handover event information to the leaf device 1230 .
  • the first edge device 1210 may include among the movement of the first edge device 1210 acquired using a sensor, the strength of a signal received through the communication module, the resource status of the processor and/or memory, and the power status.
  • a handover event may be detected based on at least one.
  • the first edge device 1210 detects a handover event have been described above with reference to FIGS. 7 to 9 .
  • the leaf device 1230 may identify a handover event according to handover event information transmitted (or broadcast) from the first edge device 1210 .
  • the leaf device 1230 may perform socket communication with the first edge device 1210 or a connection termination on a transmission protocol is sensed as an alive packet does not arrive, the first edge It may be determined that the device 1210 is unable to perform the edge computing service. In this case, operation 1260 may be omitted.
  • the leaf device 1230 when the handover event information (operation 1260) does not include information related to the second edge device 1220, in operation 1270, the leaf device 1230 performs a handover of the edge computing service.
  • the two-edge device 1220 may be discovered.
  • the leaf device 1230 may check whether the second edge device 1220 identified through discovery has a capability to receive an edge computing service handover.
  • the capability of the second edge device 1220 is whether the checked edge mode of the second edge device 1220 is activated, what services it can provide, whether it can be additionally connected to the leaf device 1230.
  • the second edge device 1220 may include at least some of physical resources (eg, processor and memory available resources), an IP address, and open connectivity foundation (OCF) capability.
  • the leaf device 1230 may identify the second edge device 1220 .
  • device information and capability information of the second edge device 1220 may be included in the handover event information, and in this case, operations 1270 and/or operation 1272 may be omitted.
  • the leaf device 1230 may attempt a handover by identifying an edge device in which the same service (eg, vision, NLU, etc.) is activated. there is.
  • the leaf device 1230 may transmit an edge computing connection request to the second edge device 1220 .
  • the leaf device 1230 may release the connection with the first edge device 1210 .
  • the leaf device 1230 may be connected to the second edge device 1220 to perform an edge computing service.
  • the leaf device 1230 and/or the second edge device 1220 notifies the IoT server 1240 of a connection change, and in operation 1290, the IoT server 1240 is edge- You can update leaf connection information.
  • FIG. 13 is a diagram illustrating a change process of an edge device when an edge handover is initiated by a leaf device according to various embodiments of the present disclosure.
  • leaf device 13 illustrates an embodiment in which the leaf device 1330 operates as a handover subject when a handover event can be detected in advance.
  • the first edge device 1310 may be connected to the leaf device 1330 on a home network to perform an edge computing service.
  • the first edge device 1310 may detect a handover event and transmit handover event information to the leaf device 1330 .
  • the leaf device 1330 may identify a handover event according to handover event information transmitted (or broadcast) from the first edge device 1310 .
  • the leaf device 1330 may perform socket communication with the first edge device 1310 or a connection termination on a transmission protocol is sensed as an alive packet does not arrive, the first edge device 1330 It may be determined that the device 1310 cannot perform the edge computing service. In this case, operation 1360 may be omitted.
  • the leaf device 1330 may confirm that the first edge device 1310 cannot perform the edge computing service, and may transmit a service request to the IoT server 1340 .
  • an artificial intelligence (AI) service which is a service related to image data acquired from the leaf device 1330, is performed on the edge device and/or IoT server 1340 in the network.
  • the leaf device 1330 may transmit a request for an edge computing service or a cloud computing service to the IoT server 1340 .
  • the IoT server 1340 checks at least one edge device registered with the same account and/or location as the leaf device 1330 in the database, and checks the operating state of the corresponding edge device.
  • the operation state is whether the checked edge mode of the second edge device 1320 is activated, what services can be provided, whether it can be additionally connected to the leaf device 1330, and the second edge device 1320 of the physical resource (eg, processor, memory available resource), IP address, and capability of the second edge device 1320 such as open connectivity foundation (OCF) capability.
  • the physical resource eg, processor, memory available resource
  • IP address e.g., IP address
  • OCF open connectivity foundation
  • the IoT server 1340 is located in the same home network as the leaf device 1330, and when a plurality of edge devices capable of edge computing services are identified, device information (or cloud parameters) of each edge device and /or it is possible to determine one edge device suitable for receiving an edge computing service handover based on the operation state information (or local parameter). Alternatively, a list of a plurality of edge devices capable of edge computing service may be transmitted to the user device, and one device may be determined as the second edge device 1320 according to the selection of the user device.
  • the IoT server 1340 may check whether the second edge device 1320 can perform the service requested by the leaf device 1330 .
  • the IoT server 1340 transmits device information of the second edge device 1320 to the leaf device 1330 , and the second edge device In connection with 1320 , it may notify to perform edge computing services.
  • the leaf device 1330 may transmit an edge connection request to the second edge device 1320 .
  • the leaf device 1330 may be connected to the second edge device 1320 to perform an edge computing service.
  • the IoT server 1340 connects to the leaf device 1330 as the IoT server 1340. It may notify you to perform cloud computing services.
  • the leaf device 1330 is connected to the IoT server 1340, and without transmitting the acquired data (eg, video streaming) to the edge device, it is transmitted directly to the IoT server 1340 to provide a cloud computing service.
  • FIG. 14 is a diagram illustrating a process of changing an edge device when an edge handover is initiated by an IoT server according to various embodiments of the present disclosure.
  • leaf device 1430 or the IoT server 1440 operates as a subject of handover when a handover event cannot be detected in advance.
  • the first edge device 1410 may be connected to the leaf device 1430 on a home network to perform an edge computing service.
  • a situation in which an edge computing service is suddenly impossible occurs in the first edge device 1410, such as disconnection of a network connection or power off, and thus a handover event may not be detected in advance.
  • the first edge device 1410 when the first edge device 1410 is disconnected from the network (eg, Wi-Fi network) used for the edge computing service, it uses another network (eg, cellular network) Handover event information may be transmitted to the IoT server 1440 .
  • the first edge device 1410 when the first edge device 1410 is in a situation in which access to another network is impossible, such as when the power is turned off, operation 1460 may be omitted, and the second edge device 1420, the leaf device 1430, or A handover event may be detected by the IoT server 1440 .
  • the IoT server 1440 checks at least one edge device registered with the same account and/or location as the leaf device 1430 in the database, and checks the operating state of the corresponding edge device.
  • the operating state may include the capability of the second edge device 1420 .
  • the IoT server 1440 may check whether the second edge device 1420 can perform the service requested by the leaf device 1430 .
  • the IoT server 1440 transmits device information of the second edge device 1420 to the leaf device 1430 , and the second edge device In connection with 1420, it may notify to perform edge computing service.
  • the leaf device 1430 may transmit an edge connection request to the second edge device 1420 .
  • the leaf device 1430 may be connected to the second edge device 1420 to perform an edge computing service.
  • the IoT server 1440 may update leaf-edge connection information as the leaf device 1430 is connected to the second edge device 1420 .
  • the IoT server 1440 connects to the leaf device 1430 as the IoT server 1440. It may notify you to perform cloud computing services.
  • the leaf device 1430 is connected to the IoT server 1440, and without transmitting the acquired data (eg, video streaming) to the edge device, it is transmitted directly to the IoT server 1440 to provide a cloud computing service.
  • the leaf device 1430 when the leaf device 1430 is not connected to the second edge device 1420 or there is no response from the IoT server 1440, the leaf device 1430 is an edge device found after local discovery.
  • a service connection may be requested, or information of the discovered edge device may be transmitted to the IoT server 1440 to request a service connection.
  • FIG. 15 illustrates a process of handing over some of the edge computing services being performed by the first edge device to the second edge device according to various embodiments of the present disclosure.
  • some of the edge computing services being performed between the first edge device 1510 and the leaf device 1530 are handed over to the second edge device 1520 according to a handover event, and the remaining part is handed over to the first edge device 1520. It may continue to be performed on the edge device 1510 .
  • the first edge device 1510 may be connected to the leaf device 1530 on a home network to perform an edge computing service.
  • the leaf device 1530 may be an IP camera device that acquires image data in real time, and services that can be provided through the acquired image data include a vision recognition service and a natural language understanding service. can do.
  • the second edge device 1520 may be connected to the home network, and an edge mode may be activated.
  • the second edge device 1520 may perform at least some of the services being performed by the first edge device 1510 , and may be a device in which a module necessary for the corresponding service is installed.
  • the first edge device 1510 may identify the second edge device 1520 .
  • the first edge device 1510 may detect a broadcasting signal from the second edge device 1520 and check whether the second edge device 1520 has connected to the home network or activated the edge mode.
  • the first edge device 1510 may transmit information on the first edge device 1510 and information on the edge computing service being performed to the second edge device 1520 .
  • the first edge device 1510 may broadcast functions and device performance capabilities that can be supported by the first edge device 1510 on a network.
  • the second edge device 1520 may transmit information of the second edge device 1520 to the first edge device 1510 .
  • the second edge device 1520 may transmit capability information of the second edge device 1520 to the first edge device 1510 in response to a signal broadcast from the first edge device 1510 . there is.
  • the first edge device 1510 and the second edge device 1520 are configured based on the capability information of the first edge device 1510 and the capability information of the second edge device 1520 .
  • the first edge device 1510 and the second edge device 1520 perform each service based on available resources of each device, installed modules (eg, device modules, service modules), mobility, power status, etc. You can decide which service is more suitable for each device.
  • the first edge device 1510 makes an edge connection change request for some of the services being performed (eg, natural language understanding service) along with the information of the second edge device 1520 and the leaf device. 1530 may be sent.
  • some of the services being performed eg, natural language understanding service
  • the leaf device 1530 transmits an edge connection request for a service (eg, natural language understanding service) determined to the second edge device 1520 according to the edge connection change request, and operation 1580 .
  • a service eg, natural language understanding service
  • the second edge device 1520 and the leaf device 1530 may be connected to each other to perform a predetermined service.
  • the first edge device 1510 and the leaf device 1530 continue to perform in the first edge device 1510 except for the service (eg, natural language understanding service) handed over to the second edge device 1520 . It can continue to perform the service it has decided to do (eg, a vision recognition service).
  • the first edge device 1510 and/or the second edge device 1520 notifies the IoT server 1540 that the edge connection has been changed, and in operation 1590, the IoT server 1540 ) can update edge-leaf connections.
  • FIG 16 illustrates a process of handing over some of the edge computing services being performed by the first edge device to the second edge device according to various embodiments of the present disclosure.
  • the first edge device 1610 may be connected to the leaf device 1630 on a home network to perform an edge computing service.
  • the leaf device 1630 may be an IP camera device that acquires image data in real time, and services that can be provided through the acquired image data include a vision recognition service and a natural language understanding service. can do.
  • the second edge device 1620 may be connected to the home network, and an edge mode may be activated.
  • the second edge device 1620 may transmit information on the second edge device 1620 to the IoT server 1640 .
  • the second edge device 1620 may transmit information including device information of the second edge device 1620 , resource status, installed modules, and edge mode activation status to the IoT server 1640 .
  • the IoT server 1640 may check information of the first edge device 1610 and the second edge device 1620 .
  • the IoT server 1640 may determine a service to be performed by each device based on capability information of the first edge device 1610 and capability information of the second edge device 1620 . For example, among the vision recognition service and natural language understanding service being performed by the first edge device 1610, the vision recognition service is continuously performed by the first edge device 1610, and the natural language understanding service is transferred to the second edge device 1620. It can be decided by handover.
  • the IoT server 1640 includes the first edge device 1610 and the second edge device 1620 based on available resources of each device, installed modules (eg, device modules, service modules), mobility, power status, etc. , it is possible to determine which of the services is more suitable for each device.
  • the IoT server 1640 may transmit information about a service to be performed by each device to the leaf device 1630 .
  • the leaf device 1630 transmits an edge connection request for a predetermined service (eg, natural language understanding service) to the second edge device 1620 according to the edge connection change request, and in operation 1674, the second edge device 1620 and the leaf device 1630 may be connected to each other to perform a predetermined service.
  • the first edge device 1610 and the leaf device 1630 continue to perform in the first edge device 1610 except for a service handed over to the second edge device 1620 (eg, natural language understanding service). It can continue to perform the service it has decided to do (eg, a vision recognition service).
  • the IoT server 1640 may update the edge-leaf connection.
  • An electronic device includes a communication module, a memory, and a processor operatively connected to the communication module and the memory, wherein the processor includes a first external device and a second external device on a local network.
  • the processor includes a first external device and a second external device on a local network.
  • the processor may be configured to receive the handover event from at least one of the first external device, the second external device, and the external server through the communication module.
  • the processor receives a predetermined signal from the first external device using the communication module while the first external device performs the edge computing service with the second external device, and When the predetermined signal is not received from the first external device, it may be configured to determine that the handover event has occurred.
  • the processor in response to the handover event, disconnects the connection from the first external device to the second external device and an edge including the electronic device and the establishment of a connection for the edge computing service Computing service may be configured to send a change request.
  • the processor may include available resources of the processor and/or the memory, whether an edge mode is activated, or a module corresponding to an edge computing service being performed between the first external device and the second external device. It may be configured to check whether the electronic device can perform the edge computing service based on at least a part of whether or not it is installed.
  • the processor when it is determined that the electronic device cannot perform the edge computing service, the processor is configured to connect the second external device to another edge device or an external server to perform the service. It may be configured to transmit to at least one of an external device, the second external device, or an external server.
  • the processor may be configured to perform some of edge computing services being performed between the first external device and the second external device.
  • the processor when the processor is connected to the second external device to perform the edge computing service, the processor may be configured to notify an external server of an edge computing service change.
  • An electronic device includes a communication module, a memory, and a processor operatively connected to the communication module and the memory, wherein the processor is Based on the received data, an edge computing service is performed, a handover event of the edge computing service is detected, and in response to the detection of the handover event, it is connected to the first external device through the communication module and the A second external device capable of performing an edge computing service is identified, and information related to the identified second external device and information related to the handover event is provided to the first external device, the second external device, or an external server. It may be set to transmit to at least one of
  • the processor includes at least one of the movement of the electronic device acquired using the sensor or the strength of a signal received through the communication module Based on one, it may be configured to detect the handover event.
  • the processor may be configured to detect the handover event based on at least one of an available resource of the processor and/or the memory or a power state of the electronic device.
  • the processor is configured to enable the second external device to be configured based on at least a part of available resources of the second external device, whether an edge mode is activated, or whether a module corresponding to the edge computing service is installed. It may be configured to check whether the edge computing service can be performed.
  • the processor may be configured to receive information related to whether the second external device can perform the edge computing service from the second external device or the external server.
  • information related to the second external device identified through a second network and information related to the handover event may be set to be transmitted to the external server.
  • An electronic device includes a communication module, a sensor, and a processor operatively connected to the communication module and the sensor, wherein the processor transmits data obtained through the sensor to the communication module transmits to the first external device to perform the edge computing service, checks the handover event of the edge computing service, and responds to the handover event and to request a connection for the edge computing service to the second external device.
  • the processor may be configured to identify the handover event based on the strength of a signal transmitted from the first external device through the communication module.
  • the processor may be configured to receive information related to the handover event from at least one of the first external device, the second external device, and the IoT server through the communication module.
  • the processor may be configured to request a connection to some of the edge computing services being performed from the second external device based on the received information related to the handover event.
  • the processor transmits a service connection request to the IoT server through the communication module in response to the handover event, and the second external device to perform the edge computing service from the IoT server. may be configured to receive information.
  • the processor when receiving a notification from the IoT server to connect to the cloud computing service, the processor may be configured to stop the edge computing service and transmit data obtained through the sensor to the IoT server there is.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Multimedia (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

Selon divers modes de réalisation, un dispositif électronique comprend un module de communication, une mémoire et un processeur connecté fonctionnellement au module de communication et à la mémoire. Le processeur peut être configuré : pour identifier un événement de transfert intercellulaire d'un service informatique en périphérie de réseau qui est effectué par un premier dispositif externe et un second dispositif externe sur un réseau local ; pour identifier si le dispositif électronique peut effectuer ou non le service informatique en périphérie de réseau ; et, quand le dispositif électronique peut effectuer le service informatique en périphérie de réseau, pour effectuer le service informatique en périphérie de réseau en connexion avec le second dispositif externe agissant en tant que dispositif feuille destiné au service informatique en périphérie de réseau.
PCT/KR2021/012461 2020-09-15 2021-09-14 Système informatique en périphérie de réseau et procédé de transfert intercellulaire destinés à un dispositif informatique en périphérie de réseau WO2022060046A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
KR10-2020-0118373 2020-09-15
KR1020200118373A KR20220036136A (ko) 2020-09-15 2020-09-15 엣지 컴퓨팅 시스템 및 엣지 컴퓨팅 장치의 핸드오버 방법

Publications (1)

Publication Number Publication Date
WO2022060046A1 true WO2022060046A1 (fr) 2022-03-24

Family

ID=80777143

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/KR2021/012461 WO2022060046A1 (fr) 2020-09-15 2021-09-14 Système informatique en périphérie de réseau et procédé de transfert intercellulaire destinés à un dispositif informatique en périphérie de réseau

Country Status (2)

Country Link
KR (1) KR20220036136A (fr)
WO (1) WO2022060046A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115914220A (zh) * 2022-09-27 2023-04-04 国网山西省电力公司 一种边缘计算设备控制方法、装置及存储介质

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20180242204A1 (en) * 2015-10-21 2018-08-23 Huawei Technologies Co., Ltd. Mec platform handover method, apparatus, and system
KR20180124419A (ko) * 2017-05-11 2018-11-21 에스케이텔레콤 주식회사 분산형 클라우드 기반 어플리케이션 실행 시스템, 이에 적용되는 장치 및 장치의 동작 방법
US20190021033A1 (en) * 2017-07-13 2019-01-17 Hon Hai Precision Industry Co., Ltd. Handover method and apparatus
US20190141593A1 (en) * 2017-11-03 2019-05-09 Hon Hai Precision Industry Co., Ltd. Methods and related devices for optimizing a mobile edge computing (mec) system
WO2019236755A1 (fr) * 2018-06-06 2019-12-12 Intel Corporation Continuité de session et de service de véhicule à tout de systèmes informatiques de périphérie de réseau d'automobile

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20180242204A1 (en) * 2015-10-21 2018-08-23 Huawei Technologies Co., Ltd. Mec platform handover method, apparatus, and system
KR20180124419A (ko) * 2017-05-11 2018-11-21 에스케이텔레콤 주식회사 분산형 클라우드 기반 어플리케이션 실행 시스템, 이에 적용되는 장치 및 장치의 동작 방법
US20190021033A1 (en) * 2017-07-13 2019-01-17 Hon Hai Precision Industry Co., Ltd. Handover method and apparatus
US20190141593A1 (en) * 2017-11-03 2019-05-09 Hon Hai Precision Industry Co., Ltd. Methods and related devices for optimizing a mobile edge computing (mec) system
WO2019236755A1 (fr) * 2018-06-06 2019-12-12 Intel Corporation Continuité de session et de service de véhicule à tout de systèmes informatiques de périphérie de réseau d'automobile

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115914220A (zh) * 2022-09-27 2023-04-04 国网山西省电力公司 一种边缘计算设备控制方法、装置及存储介质

Also Published As

Publication number Publication date
KR20220036136A (ko) 2022-03-22

Similar Documents

Publication Publication Date Title
WO2022019681A1 (fr) Système de calcul de frontière et procédé de recommandation de dispositif de connexion
WO2020067677A1 (fr) Procédé d'exploitation d'une application nécessitant une communication avec un dispositif externe, et dispositif électronique associé
WO2022019682A1 (fr) Système et procédé de calcul de frontière
WO2022203168A1 (fr) Dispositif électronique permettant de transmettre des données par le biais d'une communication à bande ultra-large, et procédé de fonctionnement du dispositif électronique
WO2022060046A1 (fr) Système informatique en périphérie de réseau et procédé de transfert intercellulaire destinés à un dispositif informatique en périphérie de réseau
WO2021033961A1 (fr) Dispositif électronique et procédé de fourniture de service par un dispositif électronique
WO2023277335A1 (fr) Dispositif électronique pour réaliser un fonctionnement de gestion de réseau et procédé de fonctionnement associé
WO2022124846A1 (fr) Dispositif concentrateur d'environnement iot, et procédé de traitement d'événement basé sur un réseau local
WO2022030814A1 (fr) Procédé de gestion d'une connexion sans fil d'un dispositif électronique, et appareil associé
WO2022031019A1 (fr) Procédé de recherche d'un dispositif perdu à l'aide d'une uwb et de l'ar et appareil associé
WO2022030801A1 (fr) Procédé de gestion d'une connexion sans fil d'un dispositif électronique, et dispositif associé
WO2022173144A1 (fr) Dispositif électronique, et procédé de détermination d'un dispositif de mise en service dans un réseau informatique de périphérie
WO2023075207A1 (fr) Dispositif électronique pour fournir un service basé sur l'emplacement, et procédé de fonctionnement de celui-ci
WO2023090722A1 (fr) Dispositif et procédé de transmission de paquet de réponse
WO2023068612A1 (fr) Dispositif électronique pour fournir un service basé sur la localisation et son procédé de fonctionnement
WO2023136453A1 (fr) Procédé de définition de canaux disponibles pour wlan et dispositif électronique pour la mise en œuvre dudit procédé
WO2023234522A1 (fr) Dispositif électronique pour commuter une connexion de communication d2d et procédé de fonctionnement pour dispositif électronique
WO2023043000A1 (fr) Dispositif électronique et procédé pour réaliser une communication par l'intermédiaire d'un réseau privé virtuel, et support de stockage lisible par ordinateur
WO2024080543A1 (fr) Dispositif électronique pour générer des faits marquants de vidéo, et son procédé de fonctionnement
WO2022154364A1 (fr) Procédé et appareil de gestion de connexion sans fil d'un dispositif électronique
WO2024053897A1 (fr) Dispositif électronique et procédé de communication basé sur nan
WO2023013878A1 (fr) Dispositif et procédé permettant d'établir une connexion
WO2024117484A1 (fr) Dispositif électronique de mise en œuvre de communication sans fil, et son procédé de fonctionnement
WO2024058375A1 (fr) Dispositif électronique permettant de prendre en charge de multiples sim et son procédé de fonctionnement
WO2024019376A1 (fr) Système de transmission de fichiers, dispositif électronique et procédé de transmission de fichiers par le même dispositif électronique

Legal Events

Date Code Title Description
NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 21869668

Country of ref document: EP

Kind code of ref document: A1