Service-based IoT system using hashtag method

Abstract

A service-based IoT system using a hashtag method according to one aspect of the present invention comprises: a plurality of IoT devices, each of which registers a list of providable services in an IoT edge device in the same network, and receives and processes a service request from the IoT edge device; and a plurality of IoT edge devices, each of which comprises middleware for registering and managing an IoT device in the same network and services provided by the IoT device, and a hashtag designation unit for assigning a hashtag input by a user to a registered IoT device or a registered service. The middleware selects an IoT device to process a service on the basis of a hashtag included in a service request.

Description

Service-based IoT system using hashtags

[0001] The present invention relates to a service-based IoT platform, and more particularly, to a technology for requesting a service using a hashtag designated for the service when requesting the service.

[0002] The Internet of Things (IoT) is becoming increasingly prevalent in our daily lives, and hundreds of IoT platforms are being developed to keep pace with this growth. An IoT platform is a software framework that enables management and connection of various smart devices and applications via the Internet, acting as a bridge between the layers of an IoT system, from the device layer to the application layer.

[0003] IoT platforms can be broadly categorized into cloud-based and edge-based types based on the location of the middleware. Cloud-based platforms deploy PaaS (Platform as a Service) middleware in the cloud and connect IoT devices via an internet network. Cloud-based platforms are more widely used due to their ease of implementation, low cost, and scalability. Edge-based platforms, on the other hand, offer several advantages over cloud-based platforms by providing cloud computing capabilities to edge devices. Edge-based IoT platforms eliminate the need to transmit data to the cloud, resulting in lower latency and improved responsiveness, along with additional security benefits. Furthermore, edge-based IoT platforms can continue operating even in poor network conditions.

[0004] Additionally, service-oriented IoT architectures are being studied. Most early IoT platforms were device-oriented, requiring users to directly control IoT devices and define IoT applications. However, service-oriented platforms abstract IoT devices into a set of services they provide, and define IoT applications based on the services requested by users. Service-oriented IoT abstracts devices into a set of services they provide, allowing users to request services rather than accessing devices to run new IoT applications. However, it cannot be considered strictly service-oriented unless it allows multiple devices to share the same service name.

[0005] The purpose of the present invention is to provide an IoT system that can select a device based on a service without directly designating an IoT device when there are multiple IoT devices capable of performing a service requested by a user in a service-based IoT system.

[0006] In addition, another object of the present invention is to provide an IoT system that provides a method for a user to intuitively transmit a desired command to a service-based IoT system without going through a complex specification process for the service.

[0007] A service-based IoT system using a hashtag method according to one aspect of the present invention includes at least one IoT device and at least one IoT edge device.

[0008] IoT devices register a list of available services with IoT edge devices within the same network and receive and process service requests from IoT edge devices.

[0009] The IoT edge device includes middleware that registers and manages IoT devices and services provided by IoT devices within the same network, and a hashtag designation unit that assigns a hashtag entered by the user to the registered IoT device or registered service.

[0010] The middleware selects the IoT device to process the service based on the hashtag included in the service request.

[0011] According to one aspect of the present invention, the hashtag designation unit can assign a hashtag input by a user or set in an IoT edge device to the middleware, and the middleware can assign the hashtag assigned to itself to a registered IoT device or service.

[0012] According to one aspect of the present invention, an IoT device can be registered by adding one or more default hashtags set at the time of manufacturing when registering with an IoT edge device.

[0013] In the present invention, a service request may be configured to include a string combining one or more hashtags and a service name.

[0014] When multiple IoT devices are searched for a hashtag included in a service request, the middleware can select all IoT devices that provide a service with a service name combined with the hashtag among the searched IoT devices as IoT devices to process the service.

[0015] According to another aspect of the present invention, a plurality of IoT edge devices form a tree-shaped hierarchical structure, wherein an IoT edge device at a higher level transmits a list of published services to an IoT edge device at a higher level, and the IoT edge device at the higher level has access to the services published by the IoT edge device at the lower level. The list of services includes the service names and hashtags assigned to the corresponding services.

[0016] At this time, the hashtag designation unit can assign identification information specified for the hierarchy level or layer of the IoT edge device to the middleware as a hashtag.

[0017] In this aspect, an upper-layer IoT edge device can create a composite service by combining services registered to the IoT edge device with services disclosed by a lower-layer IoT edge device, or by combining services disclosed by a lower-layer IoT edge device, and each service request that constitutes the composite service is configured to include a string that combines one or more hashtags and a service name.

[0018] IoT edge devices dynamically manage the execution status of the services they provide and report the execution status in response to service execution status reporting requests received from upper-layer IoT edge devices.

[0019] At this time, an upper-layer IoT edge device requesting execution of a service disclosed by a lower-layer IoT edge device included in a composite service can check the availability of the service on the lower-layer IoT edge device before requesting execution of the service.

[0020] According to the present invention, when there are multiple IoT devices capable of performing a service requested by a user, a device can be selected based on a service without directly specifying an IoT device.

[0021] Additionally, according to the present invention, a user can intuitively transmit a desired command to a service-based IoT system without going through a complex specification process for the service.

[0022] Figure 1 illustrates an example of using hashtags in a simple IoT system including one IoT edge device of the present invention.

[0023] Figure 2 illustrates various examples of specifying hashtags.

[0024] Figure 3 is a diagram conceptually illustrating an example of a composite service.

[0025] FIG. 4 conceptually illustrates an IoT system of the present invention having a hierarchical structure between IoT edge devices.

[0026] The aforementioned and additional aspects are concretized through embodiments described with reference to the attached drawings. It is understood that various combinations of components of each embodiment are possible within the embodiment, unless otherwise stated or inconsistent with each other. Each block of the block diagram may in some cases represent a physical component, but in other cases may be a logical representation of a portion of the function of a single physical component or a function spanning multiple physical components. Sometimes, the entity of a block or a portion thereof may be a set of program instructions. These blocks may be implemented in whole or in part by hardware, software, or a combination thereof.

[0027]

[0028] FIG. 1 illustrates an example of using hashtags in a simple IoT system including one IoT edge device of the present invention, and FIG. 2 illustrates various examples of designating hashtags. A service-based IoT system (10) utilizing a hashtag method according to one aspect of the present invention includes at least one IoT device (120) and at least one IoT edge device (110).

[0029] The IoT system (10) of the present invention is an edge-based platform and a service-based IoT system. An IoT device (120) abstracts the functions provided by the device into a service and registers it with an IoT edge device (110).

[0030] An IoT device (120) is a hardware device, such as a sensor, home appliance, or other machine, that is controlled or exchanges data via a network. The IoT device (120) of the present invention compiles a list of services it can provide into a service list and registers it with an IoT edge device (110) within the same network. The service list used by the IoT device (120) during registration is a list of names of abstracted services that the IoT device can provide.

[0031] The IoT device (120) receives and processes a service execution request from the IoT edge device (110) or receives a control command converted from the service by the IoT edge device (110) and executes the service.

[0032] An IoT edge device (110) may be a hub device with computing capabilities. The IoT edge device (110) includes middleware (111). The middleware (111) relays all communications between IoT devices that are geographically close and use the same network, thereby implementing smart offices, smart homes, and the like.

[0033] The IoT edge device (110) includes middleware (111) and a hashtag designation unit (112).

[0034] Middleware (111) searches for IoT devices (120) within the same network and registers and manages the searched IoT devices (120) and services provided by the IoT devices (120).

[0035] The IoT edge device (110) may additionally provide a user interface through which a user can designate a hashtag to an IoT device (120) or a registered service registered to the IoT edge device (110) according to his / her intention. The user interface provided by the IoT edge device (110) may be an interface that can be linked with an application running on a mobile terminal such as a smartphone or a computing device such as a computer used by the user, or may be a web-based interface through which the user's computing device can be linked. When the IoT edge device (110) is linked with the user's computing device based on the web, the IoT edge device (110) additionally includes a web server.

[0036] The hashtag designation unit (112) assigns a hashtag input by a user through a user interface to a registered IoT device (120) or a registered service. When a hashtag is assigned to an IoT device (120), the hashtag is used to identify the device, and the same hashtag may be assigned to multiple IoT devices. When a hashtag is assigned to a registered service, the hashtag is used to identify the service provided by a specific IoT device, and the same hashtag may be assigned to multiple services. In other words, since the present invention does not impose any restrictions on the method by which a user assigns a hashtag, the same hashtag may be assigned to different services.

[0037] In the example illustrated in FIG. 1, the hashtag designation unit (112) assigned hashtags #HT1 and #HT2 to IoT device 1 (120_1), hashtag #HT4 to IoT device 2 (120_2), hashtag #HT5 to IoT device 3 (120_3), and hashtag #HT6 to IoT device 4 (120_4). In addition, hashtag #HT3 was assigned to service B of IoT device 1 (120_1).

[0038] The examples illustrated in FIG. 2 illustrate examples of assigning hashtags (#HT1, #HT21, #HT4, #HT5, #HT6) to IoT devices (120_1, 120_2, 120_3, 120_4) by user input, assigning hashtags (#HT3) to specific services of specific IoT devices (120_1), assigning hashtags (#Edge1, #Edge2) to IoT edge devices (110_1, 110_2) by user input or presetting, and assigning hashtags (#Manufacturer1) when manufacturing IoT devices (120_4).

[0039] The middleware (111) selects an IoT device (120) to process a service based on a hashtag included in a service request. If the hashtag is assigned to an IoT device (120), the middleware (111) can search for the hashtag and select multiple IoT devices. If the hashtag is assigned to a service, the middleware (111) can select a specific service of a specific IoT device or a specific service of one or more IoT devices (120).

[0040] The IoT edge device (110) may additionally provide a user interface through which a user can request a desired service. The user interface provided by the IoT edge device (110) may be an interface that can be linked with an application running on a mobile terminal such as a smartphone or a computing device such as a computer used by the user, or may be a web-based interface that the user's computing device can link with.

[0041] In addition to a user entering a service request, an application running on an IoT edge device (110) can request a service.

[0042] A service request may consist of a string containing one or more hashtags and a service name.

[0043] The hashtag used according to the intention of the user requesting the service using the hashtag reduces the scope of the IoT device (120) executing the service. At this time, the IoT edge device (110) executes the corresponding service of the IoT device (120) that provides the service matching the service name among all IoT devices searched by the hashtag according to the policy or implementation method. If there are multiple IoT devices (120) providing the corresponding service, the execution request can be made simultaneously or one device can be selected to execute the service.

[0044] The present invention can also assign hashtags to middleware (111) running on an IoT edge device (110). Since the middleware (111) implements smart offices, smart homes, etc. using IoT devices that are geographically close and use the same network, it may be necessary to assign the same hashtag to IoT devices registered to the middleware (111) so that the smart office, smart home, etc. can be distinguished from other smart offices, smart homes, etc. In addition to this purpose, hashtags can be assigned to the middleware (111) and used according to the user's intention.

[0045] According to one aspect of the present invention, the hashtag designation unit (112) can assign a hashtag that is input by a user to the middleware (111) or preset to the IoT edge device (110).

[0046] Middleware (111) can uniformly add and assign a hashtag assigned to itself to registered IoT devices (120) or services.

[0047] In addition to users assigning hashtags to IoT devices (120) registered with IoT edge devices (110), hashtags may be pre-added to IoT devices (120). For example, IoT devices (120) may set general information suitable for the device, such as manufacturer information and device category, as hashtags during manufacturing. The present invention defines these as default hashtags, and these are set by default on the device regardless of whether the user uses these default hashtags.

[0048] According to one aspect of the present invention, an IoT device (120) can be registered by adding one or more basic hashtags set during manufacturing when registering with an IoT edge device (110). That is, if the IoT device (120) includes a basic hashtag when registering the device with the middleware (111), the basic hashtag is also transmitted to register the device.

[0049] The present invention searches for an IoT device (120) or a service provided by an IoT device (120) using a hashtag included in a service request. At this time, the middleware (111) searches for an IoT device (120) using the hashtag included in the service request, and if multiple IoT devices are found using the requested hashtag as a result of the search, all IoT devices that provide a service with a service name combined with the hashtag among the found IoT devices can be selected as IoT devices to process the service. At this time, the middleware (111) executes the corresponding service of an IoT device (120) that provides a service matching the service name among all IoT devices searched using the hashtag according to a policy or implementation method, and if there are multiple IoT devices (120) providing the corresponding service, the middleware can request execution at the same time or select one device to execute it.

[0050] Figure 3 is a diagram conceptually illustrating a composite service. The middleware (111) of an IoT edge device (110) can create a new composite service by combining services registered to it. The composite service is a type of application program written in a scripting language or programming language. If the composite service is written in a scripting language, the IoT edge device (110) additionally includes a user interface that can define the composite service in script form. The format of the scripting language defining the composite service is not limited, but it is preferable to support control statements based on a general scripting language.

[0051] The IoT edge device (110) that created the composite service can also assign a hashtag to the composite service.

[0052] In the example of Fig. 3, "#environment" is assigned to the IoT thermometer device (120_1), "#entrance #CCTV" is assigned to the CCTV (120_2), and "#livingroom #robot" is assigned to the robot (120_3). In the case of the robot (120_3), a hashtag is also assigned to the service it provides. The composite service exemplified in Fig. 3, which is configured based on this, is a service in which the robot moves to the window, closes the window, and outputs a guidance voice when the indoor temperature is lower than 21 degrees.

[0053] Figure 4 conceptually illustrates an IoT system of the present invention having a hierarchical structure among IoT edge devices. According to another aspect of the present invention, multiple IoT edge devices form a tree-shaped hierarchical structure. The IoT system (10) of the present invention facilitates system scalability by introducing a hierarchical structure among IoT edge devices. As shown in the example illustrated in Figure 4, IoT edge devices form a tree-shaped hierarchical structure.

[0054] An IoT edge device (e.g., 110_11) with a higher layer transmits a list of services it has disclosed to IoT edge devices of a higher layer (e.g., 110_21, 110_31, 110_4), and the IoT edge devices of a higher layer (e.g., 110_21, 110_31, 110_4) have access to the services disclosed by the IoT edge devices of a lower layer (e.g., 110_11). The list of services includes the service name and the hashtag assigned to the service.

[0055] The IoT edge device (110) abstracts the functions provided by the IoT device (120) into services and provides them. At this time, the services can be abstracted in the form of application programs written and implemented in a scripting language or a programming language. Users, etc. can request services using a hashtag or a string composed of one or more hashtags and a service name. The IoT edge device (110) executes a service corresponding to the hashtag or a string composed of one or more hashtags and a service name and issues control commands related to the execution of the service to the IoT device (120).

[0056] Middleware (111) manages IoT devices (120) by mapping them with the services provided by each IoT device (120). For example, middleware (111) can manage them by mapping a device identifier (e.g., device ID) with a service identifier (e.g., service name).

[0057] Additionally, the middleware (111) sets whether registered services are made public. The IoT edge device (110) provides a user interface for setting whether services are made public, allowing users or administrators to set service disclosure through this interface. There are no restrictions on the implementation of the user interface provided by the IoT edge device (110).

[0058] In the present invention, a service disclosed by a lower-layer middleware (111) is authorized to be executed by an upper-layer middleware (111) located on the path from the corresponding layer to the highest layer. The upper-layer middleware (111) can only execute the service disclosed by the lower-layer middleware (111), and access to data required for executing the service is blocked.

[0059] The middleware (111) determines whether its upper layer exists, and if it determines that the upper layer exists, it transmits the list of services set to public to the middleware (111) of the upper layer. In other words, the IoT edge device (110) having the upper layer transmits the list of services it has disclosed to the IoT edge device (110) of the upper layer. The middleware (111) of the upper layer that has received the list of services disclosed from the middleware (111) of the lower layer can register and manage the services received from the lower layer, distinguishing them from the services registered to itself.

[0060] In addition, when a service request is made by another IoT edge device (110), the middleware (111) determines whether the IoT edge device (110) requesting the service has access rights, that is, determines whether the service is provided based on the access rights. At this time, the upper layer IoT edge device (110) on the path from the lower layer to the highest layer has access rights to the service disclosed by the lower layer IoT edge device (110).

[0061] The example of Fig. 4 shows an example in which IoT edge devices have a hierarchical structure divided into four tiers, where the first tier is an office-level tier, the second tier is a floor-level tier, the third tier is a building-level tier, and the fourth tier is a campus-level tier with multiple buildings. The service disclosed by IoT edge device 1-1 (110_11) is accessible to its upper tiers, IoT edge device 2-1 (110_21), IoT edge device 3-1 (110_31), and IoT edge device 4 (110_4), but IoT edge device 1-L (110_1L), IoT edge device 2-M (110_2M), and IoT edge device 3-N (110_3N) do not have access.

[0062] Since the middleware (111) has a hierarchical structure, information related to the hierarchy (e.g., hierarchy level) can be added and utilized as a hashtag. Accordingly, the hashtag designation unit (112) can assign identification information designated for the hierarchy level or hierarchy of the IoT edge device (110) to the middleware (111) as a hashtag. For example, if a building is designated as the third hierarchy, each floor as the second hierarchy, and each office as the first hierarchy, "#3F" can be assigned to the middleware (111) as a hashtag related to the hierarchy.

[0063] Depending on the aspect of the invention, the middleware (111) belonging to a lower layer of the middleware (111) in which a hashtag related to a layer is set can uniformly add and assign a hashtag assigned in relation to the layer to the registered IoT device (120) or service. In the example described above, the middleware (111) of the IoT edge device (110) for office 301 of the first layer can uniformly add and assign the hashtag "#3rd floor" to the registered IoT device (120) or service.

[0064] According to another aspect of the present invention, an upper-layer IoT edge device (110) creates a composite service by combining services registered with the IoT edge device (110) and services disclosed by a lower-layer IoT edge device (110), or by combining services disclosed by a lower-layer IoT edge device (110). Each service request constituting the composite service is configured to include a string that combines one or more hashtags and a service name.

[0065] At this time, the composite service is a new service created by using an IoT device (120) registered and disclosed to a lower-layer IoT edge device (110) as a shared resource. The composite service is a type of application written in a scripting language or programming language.

[0066] The IoT edge device (110) that created the composite service can also assign a hashtag to the composite service.

[0067] The individual services included in the composite service may be services of IoT devices (120) connected to IoT edge devices (110) in other locations, i.e., services registered in IoT edge devices (110) of a lower layer. In this case, the IoT devices (120) may be dynamically removed or may become unable to provide services due to malfunctions, etc. Therefore, when executing the composite service, execution of the services included in the composite service may fail.

[0068] An IoT edge device (110) that processes a composite service can stop executing the composite service and notify the requesting user of the failure in processing the composite service if the execution of one service that constitutes the composite service fails.

[0069] In an IoT edge system where a hierarchical structure is formed, multiple identical IoT devices (120) can be registered and used in different IoT edge devices (110) or in the same IoT edge device (110).

[0070] An IoT edge device (110) that processes a composite service upon request may request execution of the failed service from another IoT edge device (110) that provides the same service when execution of a service that constitutes the composite service fails and the same service is provided by another IoT edge device (110). That is, when there are multiple IoT devices (120) that provide the same specific service in the IoT edge system, even if execution of the service fails, execution of the composite service can be requested from another IoT edge device (110) that provides the same service without stopping the execution of the service.

[0071] At this time, the service must also be made public on other IoT edge devices (110), and the IoT edge device (110) that created the composite service must be a higher layer of the other IoT edge devices (110) and must have access rights. In other words, IoT edge devices that provide the same service are lower layers of the IoT edge device of the higher layer that created the composite service, and each IoT edge device of the lower layer must set the service to be public so that the services are delivered to the IoT edge device of the higher layer that created the composite service.

[0072] The middleware (111) executing the composite service does not stop the composite service even if the execution of a specific service fails, and checks whether there is another IoT edge device that provides the same service mapped by the middleware (111), and if there is another IoT edge device, the middleware can request the same service to the IoT edge device. According to an aspect of the invention, if the middleware (111) of the IoT edge device that created the composite service recognizes that one service that constitutes the composite service has failed (e.g., receives a failure notification from the middleware (111) of the IoT edge device), the middleware does not transmit the result to the user who requested the service, but checks whether there is another IoT edge device that provides the same service mapped by the middleware (111), and if there is another IoT edge device, the middleware can request the same service to the IoT edge device.

[0073] If all other IoT edge devices providing the same service also fail to execute the service, the execution of the composite service is stopped as described above and the failure to process the composite service is notified to the user who requested the service.

[0074] As described above, multiple identical IoT devices (120) can be registered and used in different IoT edge devices or the same IoT edge device, and thus the present invention can process them in a distributed manner.

[0075] According to another aspect of the present invention, when a lower layer service constituting a composite service is provided equally by a plurality of IoT edge devices, an IoT edge device (110) processing the composite service can request service processing so that the services constituting the composite service are distributed and executed by a plurality of IoT edge devices.

[0076] When the middleware (111) of an IoT edge device (110) executing a composite service processes a specific service within the composite service, if there are multiple IoT edge devices (110) that provide the same service, the middleware (111) can request that the service be distributed and processed among multiple IoT edge devices.

[0077] At this time, the middleware (111) executing the composite service can request the same service from another IoT edge device that provides the same service mapped by the middleware (111) without stopping the composite service even if the execution of a specific service for which distributed processing has been requested fails.

[0078] According to another aspect of the present invention, an IoT edge device (110) dynamically manages the execution status of the services it provides. The middleware (111) of the IoT edge device can monitor the status of a registered IoT device (120) and the execution status of the services provided by the IoT device (120) and dynamically manage the status thereof.

[0079] The middleware (111) of the IoT edge device manages the status so that the IoT device (120) can be dynamically added or removed. When the IoT device (120) is removed, the middleware (111) can also remove the service provided by the IoT device (120).

[0080] Middleware (111) can create and manage a service status table that manages the status of services provided by IoT devices registered to the IoT edge device (110). Middleware (111) can manage the service status as running or waiting for execution. However, this is not limited to this, and other statuses may be added as needed.

[0081] When the middleware (111) receives a request to execute a service registered to itself, it checks the execution status of the corresponding service in the service status table, and if it is waiting for execution, it transmits the service execution request to the mapped IoT device (120) and changes the execution status of the corresponding service in the service status table to running. Thereafter, when the middleware (111) receives a notification of completion of execution from the IoT device (120) executing the service, it changes the execution status of the corresponding service in the service status table to waiting for execution.

[0082] The middleware (111) of the IoT edge device of the upper layer can send a service execution status report request to determine the execution status of the service provided by the IoT edge device of the lower layer.

[0083] When the middleware (111) of the IoT edge device receives a request for reporting the execution status of a service from an upper-layer IoT edge device, it searches for the corresponding service in the service status table and then reports the execution status in response to the request.

[0084] The IoT system (10) of the present invention can request execution of a service disclosed by a lower-layer IoT edge device through a middleware (111) of an upper-layer IoT edge device. Whether the current service is executable is managed using a service status table in the IoT edge device (110) where the service is registered. Even if the service is disclosed, an upper-layer IoT edge device with access rights other than the IoT edge device (110) where the service is registered does not directly manage the status of the service. Therefore, an upper-layer IoT edge device requests a service without knowing whether the disclosed lower-layer service is executable, which causes a problem in that unnecessary requests are made even in a situation where the service cannot be executed.

[0085] An upper-layer IoT edge device requesting execution of a service disclosed by a lower-layer IoT edge device included in a composite service can check the availability of the service on the lower-layer IoT edge device before requesting the service execution. At this time, the middleware (111) of the upper-layer IoT edge device can transmit a service execution status report request to the middleware (111) of the lower-layer IoT edge device and receive the result to check the availability of the service.

[0086] As described above, according to one aspect of the present invention, the IoT edge device (110) can dynamically manage the execution status of the service it provides. The middleware (111) of the IoT edge device (110) can monitor the status of the registered IoT device and the execution status of the service provided by the IoT device (120) and dynamically manage the status.

[0087] An IoT edge device (110) executing a composite service can initiate execution of the composite service after checking the availability of all services that constitute the composite service.

[0088] The middleware (111) of the IoT edge device executing the composite service checks the availability of all services that constitute the composite service by requesting a report on the execution status of the service to the IoT edge device (110) in which the IoT device (120) mapped to the corresponding service is registered, and then executes the composite service when it is determined that all services are available.

[0089]

[0090] The various embodiments disclosed in this specification and drawings are merely specific examples to aid understanding and are not intended to limit the scope of the various embodiments of the present invention.

[0091] Accordingly, the scope of the various embodiments of the present invention should be interpreted as including all changes or modifications derived based on the technical ideas of the various embodiments of the present invention in addition to the embodiments described herein.

Claims

1. At least one IoT device that registers a list of available services to the IoT edge devices below within the same network and receives and processes service requests from the IoT edge devices below; and At least one IoT edge device including middleware for registering and managing IoT devices and services provided by IoT devices within the same network, and a hashtag designation unit for assigning a hashtag entered by a user to a registered IoT device or registered service; Including, but not limited to, Middleware is a service-based IoT system that uses a hashtag approach to select IoT devices to process services based on hashtags included in service requests.

2. In paragraph 1, The hashtag designation section assigns a hashtag that the user inputs or that is set on the IoT edge device to the middleware. Middleware is a service-based IoT system that uses a hashtag method to assign a hashtag to each registered IoT device or service.

3. In paragraph 1, IoT devices register by adding one or more default hashtags set at the time of manufacturing when registering with the IoT edge device. A service-based IoT system using hashtags.

4. In paragraph 1, A service request consists of a string containing one or more hashtags and a service name. A service-based IoT system using hashtags.

5. In paragraph 4, When multiple IoT devices are searched for a hashtag included in a service request, the middleware selects all IoT devices that provide a service with a service name combined with the hashtag as IoT devices to process the service. A service-based IoT system using hashtags.

6. In paragraph 4, Middleware creates composite services by combining registered services. Each service request that constitutes a composite service consists of a string that includes one or more hashtags and a service name. A service-based IoT system using hashtags.

7. In paragraph 1, Multiple IoT edge devices form a tree-like hierarchical structure, and an IoT edge device in a higher layer transmits a list of services it has disclosed to an IoT edge device in a higher layer, and an IoT edge device in a higher layer has access to the services disclosed by an IoT edge device in a lower layer. The list of services includes the service name and the hashtag assigned to that service. A service-based IoT system using hashtags.

8. In paragraph 7, The hashtag designation part assigns the middleware with the identification information specified for the hierarchy level or layer of the IoT edge device as a hashtag. A service-based IoT system using hashtags.

9. In paragraph 7, The IoT edge device of the upper layer creates a composite service by combining the services registered in the IoT edge device and the services disclosed by the IoT edge device of the lower layer, or by combining the services disclosed by the IoT edge device of the lower layer. Each service request that constitutes a composite service consists of a string that includes one or more hashtags and a service name. A service-based IoT system using hashtags.

10. In paragraph 9, IoT edge devices dynamically manage the execution status of the services they provide, and report the execution status in response to service execution status reporting requests received from upper-layer IoT edge devices. The upper layer IoT edge device that requests execution of a service disclosed by a lower layer IoT edge device included in a composite service checks the availability of the service to the lower layer IoT edge device before requesting execution of the service. A service-based IoT system using hashtags.

Images