KR102302302B1 - Ultra-Small Disposable IoT Service Infrastructure - Google Patents

Abstract

An ultra-small Disposable IoT service infrastructure and an optimal operation method of the infrastructure are provided. Disposable IoT infrastructure operating method according to an embodiment of the present invention, through an IDE, the Disposable IoT terminal to develop a task that is an individual function that can be provided; and registering the developed task in a TR (Task Repository) of the infrastructure.
Thereby, the infrastructure for the micro-disposable IoT service is configured, and the optimal operation of resources in the configured infrastructure is possible, thereby making it possible to provide an effective service.

Description

Ultra-Small Disposable IoT Service Infrastructure

The present invention relates to IoT technology, and more particularly, to an infrastructure that connects and provides services to ultra-small IoT terminals.

The development of IoT technology and the expansion of services are accelerating in recent years. Recently, research and development to provide a service by connecting a very small number of IoT terminals is being conducted.

However, in an environment in which more than tens of thousands of ultra-small IoT terminals are operated in a complex manner, it is practically impossible for a person to intervene and directly configure, manage, and operate them to provide services.

Accordingly, it is required to find a way to enable micro-IoT terminals to autonomously configure themselves to provide services and to optimally manage terminal resources according to service demands.

The present invention has been devised to solve the above problems, and an object of the present invention is to provide a micro-disposable IoT service infrastructure and an optimal operation method of the infrastructure.

According to an embodiment of the present invention for achieving the above object, a Disposable IoT infrastructure operation method includes the steps of: developing, through an IDE, a task that is an individual function that a Disposable IoT terminal can provide; and registering the developed task in a TR (Task Repository) of the infrastructure.

The method for operating a Disposable IoT infrastructure according to the present invention may further include a step of, by a Service Orchestrator (SO), searching for a task corresponding to a service requirement in the TR.

The method for operating a Disposable IoT infrastructure according to the present invention may further include, based on the task list searched by the SO, generating a service template suitable for a service request.

The method for operating a Disposable IoT infrastructure according to the present invention may further include distributing the service template generated by the SO.

The method for operating a Disposable IoT infrastructure according to the present invention may further include transmitting the received service template-based task configuration information to the Disposable IoT terminal.

The method for operating a Disposable IoT infrastructure according to the present invention may further include the step of initially driving the Disposable IoT terminal receiving the task configuration information and requesting registration.

The method for operating a Disposable IoT infrastructure according to the present invention may further include the step of changing, by the Disposable IoT terminal, an adjustable parameter in a task.

According to another aspect of the present invention, Disposable IoT terminal; Disposable IoT infrastructure comprising a TR (Task Repository) for registering a task, which is an individual function that can be provided by the Disposable IoT terminal, is provided.

As described above, according to the embodiments of the present invention, an infrastructure for a micro-disposable IoT service is configured, and optimal operation of resources in the configured infrastructure is possible, thereby making it possible to provide an effective service.

1 is a conceptual diagram of an infrastructure for a micro-disposable IoT service according to an embodiment of the present invention;
2 is a configuration diagram of a micro-disposable IoT service infrastructure according to an embodiment of the present invention;
3 is a diagram provided for the description of the Disposable IoT terminal task development and registration process;
4 is a diagram provided for the description of the Service Orchestrator task discovery process;
5 is a diagram provided for the description of the Service Orchestrator service template creation process;
6 is a view provided for the description of the service template distribution process;
7 is a diagram provided for the description of the terminal task setting process, and,
8 is a diagram provided to explain an initial driving process of a Disposable IoT terminal.

Hereinafter, the present invention will be described in more detail with reference to the drawings.

1 is a conceptual diagram of an infrastructure for a micro-disposable IoT service according to an embodiment of the present invention.

The micro-disposable IoT infrastructure according to an embodiment of the present invention provides interoperability with the existing IoT platform as well as the existing heterogeneous cloud/edge/fog network infrastructure.

In addition, the micro-disposable IoT infrastructure according to an embodiment of the present invention is an automated provisioning-based infrastructure management technique for optimal management of micro-disposable terminals, information modeling including terminal object definition for optimal micro-disposable terminal operation according to service requirements Techniques and ultra-light messaging techniques for resource-constrained micro-disposable terminals are applied.

2 is a block diagram of a micro-disposable IoT service infrastructure according to an embodiment of the present invention.

The micro-disposable IoT infrastructure according to the embodiment of the present invention provides optimal task orchestration of cloud/edge/micro-disposable terminals through autonomous recognition of services and environments, resource-constrained micro-disposable terminals, and computation offloading for edge load distribution, Zero-touch Management, which supports autonomous optimal management of tens of thousands or more of micro-disposable terminals without human intervention, and geolocation determination of non-GPS micro-disposable terminals.

As shown in FIG. 1 , the micro-disposable IoT service infrastructure according to the embodiment of the present invention is composed of the infrastructure, the terminal SW mounted on the micro-disposable IoT terminal, and the micro-disposable IoT terminal, and the main components are as follows. .

TR (Task Repository): A task repository that stores information of tasks that can be operated in cloud/edge/micro-disposable IoT terminals.

SO: A service orchestrator that creates a service template according to the service demand based on the task information stored in the task repository (TR) and delivers it to the cloud/edge.

ZTM: Zero-touch that is mounted on the cloud or edge, receives a service template from a service orchestrator (SO), and delivers task information that needs to be operated to a micro-disposable terminal connected to the lower part (to ZTM of the edge in the case of cloud) based on this Management module

IDE: As a web-based development tool to develop tasks mounted on micro-disposable terminals, the developed tasks are registered in the TR of the infrastructure and loaded to suit the purpose of the terminal when developing micro-disposable terminals.

IoTWare: A terminal SW framework that is mounted on an ultra-small disposable terminal to drive various types of tasks to perform terminal-specific functions, and provides services in connection with the edge/cloud of infrastructure

3 is a diagram provided to explain a Disposable IoT terminal task development and registration process in a micro-disposable IoT service infrastructure. As shown in FIG. 3 , the task of the Disposable IoT terminal is developed through the IDE of the infrastructure and is registered in the TR of the infrastructure.

The task of the terminal means an individual function that the terminal can provide, and it must be possible to configure the operation of the terminal by combining the individual functions.

ex1) Temperature collection → LoRa data transmission, etc.

ex2) In the case of a terminal that supports temperature, humidity, and illuminance complex sensors, it is possible to collect only temperature information and transmit it to the edge according to the service request.

The task must specify the type of node that can be operated according to the type. It should be possible to determine whether the SO can operate in any of cloud/edge/terminal through task information, and therefore, a parameter that can be specified for the type of node is required.

For each task, input and output are specified, that is, what input is received, what kind of work is performed, and what kind of result is clearly specified, so that the SO can combine tasks to configure the service. Depending on the function of the task, either Input or Output may not exist.

Each task has adjustable parameters. It can hold parameters that can be dynamically changed according to service requests and terminal status (Zero-touch Management).

ex) Sensing cycle, upload cycle, etc.

4 is a diagram provided to explain a service orchestrator task discovery process in a micro-disposable IoT service infrastructure. This is the process in which SO searches for tasks registered in TR to create service templates.

As shown in FIG. 4 , the SO searches for a task corresponding to a service requirement, and when searching for a task, the TR provides various options for the search.

ex) All tasks, by node type, task category, task name, task keyword, etc.

5 is a diagram provided to explain a process of creating a Service Orchestrator service template in an ultra-small Disposable IoT service infrastructure. This is the process of creating a service template that meets the service needs based on the task list retrieved from SO.

As shown in FIG. 5, the SO creates a service template by combining the tasks of cloud/edge/terminal to satisfy the service request based on the searched task list, and the corresponding task is determined by the cloud/edge through the node type of the task. / Find out where it can be operated from among the terminals. In addition, it is necessary to define a method for determining which node among numerous edges and terminals connected to the cloud to perform the task.

6 is a diagram provided to explain a service template distribution process in a micro-disposable IoT service infrastructure. This is the process of distributing the template created in SO to the cloud and edge.

To this end, the SO sends the created service template to the cloud and edge, and the ZTM of each cloud and edge receives the service template from the SO.

7 is a diagram provided to explain a terminal task setting process in a micro-disposable IoT service infrastructure. This is the process of transmitting service template-based task configuration information to the edge and terminal connected to the lower part when the service template is received from the cloud and edge.

To this end, the service template is transmitted from the cloud to the edge, task configuration information is transmitted from the edge to the terminal, the ZTM requirement (R3) is derived, and the task configuration information is transmitted from the edge to the terminal.

If the object receiving the service template from the SO is the cloud, the service template is delivered to the edge connected to the bottom, and each edge delivers task configuration information to the terminal connected to it when receiving the service template.

It can be transmitted only to the terminal for performing the task in the service template, and the task performing terminal is identified through the terminal task identification method defined in the template generation.

8 is a diagram provided to explain an initial driving process of a Disposable IoT terminal in a micro-disposable IoT service infrastructure. Disposable This is the process of registering as edge and cloud when the terminal is first started.

To this end, the Disposable terminal requests registration to the edge. When a Disposable terminal is initially driven, it performs a terminal registration request to the edge to which it is connected. When a terminal registration request is made, self information of a Disposable terminal and information on tasks that it can perform are delivered to the edge.

Then, the edge receiving the terminal registration request requests registration to the cloud. When registering a terminal, the cloud assigns a unique ID to identify the terminal in the system.

Based on the assigned ID, task management and optimal resource management of the terminal are performed, and the corresponding ID is unique within the cloud, and the system should be able to manage whether the change is made even if the edge to which the terminal is connected changes.

If there is no service template, the terminal operates only the standby state or basic functions after simple registration.

If there is a service template after the Disposable terminal is registered, the ZTM delivers real-time task configuration information to the terminal. The subsequent process is the same as the process in which the edge transmits task configuration information to the terminal.

9 is a diagram provided to explain a configuration change process while driving a disposable terminal in a micro-disposable IoT service infrastructure. Disposable This is a process of changing terminal task parameters according to a service request or terminal resource during terminal operation.

Since each task has adjustable parameters, it is possible to dynamically change task parameters according to a service request and a terminal state to provide an optimal service and maintain an optimal terminal resource.

ex1) Changing the sensing period of the terminal according to the service request

ex2) Change the upload cycle according to the battery resource status of the terminal

On the other hand, it goes without saying that the technical idea of the present invention can also be applied to a computer-readable recording medium containing a computer program for performing the functions of the apparatus and method according to the present embodiment. In addition, the technical ideas according to various embodiments of the present invention may be implemented in the form of computer-readable codes recorded on a computer-readable recording medium. The computer-readable recording medium may be any data storage device readable by the computer and capable of storing data. For example, the computer-readable recording medium may be a ROM, RAM, CD-ROM, magnetic tape, floppy disk, optical disk, hard disk drive, or the like. In addition, the computer-readable code or program stored in the computer-readable recording medium may be transmitted through a network connected between computers.

In addition, although preferred embodiments of the present invention have been illustrated and described above, the present invention is not limited to the specific embodiments described above, and the technical field to which the present invention belongs without departing from the gist of the present invention as claimed in the claims Various modifications are possible by those of ordinary skill in the art, and these modifications should not be individually understood from the technical spirit or prospect of the present invention.

TR: Task Repository
SO: Service Orchestrator
ZTM : Zero-touch Management Module
IoTWare

Claims (8)

Developing a task that is an individual function that the Disposable IoT terminal can provide through the IDE;
registering the developed task in a TR (Task Repository) of the infrastructure;
Searching, by a Service Orchestrator (SO), a task corresponding to the service requirement from the TR;
generating a service template that meets the service request based on the task list searched by the SO;
distributing the service template created by the SO;
transmitting, by the edge system, the distributed service template-based task configuration information to the Disposable IoT terminal;
requesting registration by the Disposable IoT terminal receiving the task configuration information;
Including, by the Disposable IoT terminal, changing an adjustable parameter in the task
The task is
It includes a parameter and an adjustable parameter specifying an operable Node type, and the Node type is:
Including cloud systems, edge systems, and Disposable IoT terminals,
The search step is
The task is searched using the Node type search option,
The transmission step is
The task configuration information is transmitted only to the Disposable IoT terminal to perform the corresponding task in the distributed service template,
Based on the parameter that specifies the operable Node type, the Disposable IoT terminal for performing the task is identified,
The change step is
Disposable IoT infrastructure operation method, characterized in that the adjustable parameters are dynamically changed according to the service request and the status of the Disposable IoT terminal.
delete delete delete delete delete delete Disposable IoT terminal;
TR (Task Repository) for registering a task, which is an individual function that a Disposable IoT terminal can provide;
SO (Service Orchestrator) that searches for tasks corresponding to service requirements in TR and creates and distributes service templates that meet service needs based on the searched task list;
An edge system that transmits the distributed service template-based task configuration information to the Disposable IoT terminal;
The task is
It includes a parameter specifying an operable Node type and an adjustable parameter,
Node type is
Including cloud systems, edge systems, and Disposable IoT terminals,
SO,
The task is searched using the Node type search option,
edge system,
The task configuration information is transmitted only to the Disposable IoT terminal for performing the task in the distributed service template, but the Disposable IoT terminal for performing the task is identified based on the parameter specifying the operable Node type,
The Disposable IoT terminal that has received the task configuration information,
A Disposable IoT infrastructure system, characterized in that it requests registration and dynamically changes parameters that can be adjusted in a task according to a service request and a Disposable IoT terminal status.

Images