KR102450911B1 - Method of identifying internet or things group service based on object identifier - Google Patents

Abstract

Disclosed is an object identifier-based IoT group service identification method. The object identifier-based service group identification method according to an embodiment includes a first group identifier of a first service group corresponding to the first object identifier in response to the first object identifier transmitted through a URI corresponding to the first object identifier retrieving, identifying services belonging to the first service group using the first group identifier, and transmitting information of the identified services, wherein the first service group is The requested service group.

Description

Object identifier-based IoT group service identification method {METHOD OF IDENTIFYING INTERNET OR THINGS GROUP SERVICE BASED ON OBJECT IDENTIFIER}

The following embodiment relates to IoT identifier technology as an object identifier-based identification and interpretation technique.

The Internet of Things (IoT) is easy to provide separate services only within each domain or region based on diverse and heterogeneous resources.

As a way to integrate operation and management of these characteristics, all IoT services are grouped and provided in parallel or sequentially, so efficient integrated service operation is required.

The form of grouping individual services and providing them in an integrated way is called service grouping.

Embodiments may provide a separate identification and interpretation technology for existing IoT services in a group form.

The embodiments provide a system (grouping) method for integrating and operating these services in order to solve a problem limited in the integrated operation of heterogeneous and diverse IoT individual services, and a technology for identifying and interpreting a service group based on an object identifier. can

The object identifier-based service group identification method according to an embodiment includes a first group identifier of a first service group corresponding to the first object identifier in response to the first object identifier transmitted through a URI corresponding to the first object identifier retrieving, identifying services belonging to the first service group using the first group identifier, and transmitting information of the identified services, wherein the first service group is The requested service group.

The URI may be location information of a group service analysis server that has created the first service group.

The information may include a service identifier of the services and an identifier of a corresponding registry.

The first object identifier may be assigned to identify the group service interpretation server.

The method may further include individually requesting a specific service from among the services to a corresponding service registry by using the information.

The method may further include registering the specific service in response to a registration request for the specific service.

The registering includes: creating a second service group by grouping the specific service; generating a second group identifier corresponding to the second service group; and a second object allocated to the second service group. and managing the identifier and the second group identifier by matching the group list.

The registering may further include managing the mapping between the second group identifier and the specific service information.

The information on the specific service may include a service identifier of the specific service and an identifier of a corresponding registry.

The method may further include mapping and managing a second object identifier assigned to the second service group and a URI of a group service interpretation server that has created the second service group.

1 is an example of the architecture of an object identifier-based resolution framework of group services (OID-based resolution framework of group services) according to an embodiment.
FIG. 2 is a diagram for explaining a schematic operation of the GRS shown in FIG. 1 .
FIG. 3 is a diagram for explaining a schematic operation of the ORS shown in FIG. 1 .
FIG. 4 is a diagram for explaining a schematic operation of the service registry shown in FIG. 1 .
5 is a diagram for explaining a registration procedure of an object identifier-based group service according to an embodiment.
6 is a diagram for explaining an interpretation procedure of an object identifier-based group service according to an embodiment.

Hereinafter, embodiments will be described in detail with reference to the accompanying drawings. However, since various changes may be made to the embodiments, the scope of the patent application is not limited or limited by these embodiments. It should be understood that all modifications, equivalents and substitutes for the embodiments are included in the scope of the rights.

The terms used in the examples are used for the purpose of description only, and should not be construed as limiting. The singular expression includes the plural expression unless the context clearly dictates otherwise. In the present specification, terms such as “comprise” or “have” are intended to designate that a feature, number, step, operation, component, part, or combination thereof described in the specification exists, but one or more other features It should be understood that this does not preclude the existence or addition of numbers, steps, operations, components, parts, or combinations thereof.

Terms such as first or second may be used to describe various elements, but the elements should not be limited by the terms. The terms are used only for the purpose of distinguishing one element from another element, for example, without departing from the scope of rights according to the concept of the embodiment, a first element may be named as a second element, and similarly The second component may also be referred to as the first component.

Unless defined otherwise, all terms used herein, including technical or scientific terms, have the same meaning as commonly understood by one of ordinary skill in the art to which the embodiment belongs. Terms such as those defined in a commonly used dictionary should be interpreted as having a meaning consistent with the meaning in the context of the related art, and should not be interpreted in an ideal or excessively formal meaning unless explicitly defined in the present application. does not

In addition, in the description with reference to the accompanying drawings, the same components are assigned the same reference numerals regardless of the reference numerals, and the overlapping description thereof will be omitted. In the description of the embodiment, if it is determined that a detailed description of a related known technology may unnecessarily obscure the gist of the embodiment, the detailed description thereof will be omitted.

“Object identifier (OID)” is an international standard, and it is easy to expand and operate heterogeneous services in an integrated manner.

1 is an example of the architecture of an object identifier-based resolution framework of group services (OID-based resolution framework of group services) according to an embodiment.

1, the service resolution system (service resolution system; 10) is an object identifier resolution server (object identifier resolution server (ORS); 100), a plurality of group service resolution servers (group service resolution server (GRS); 200; ) is included. In addition, the service interpretation system 10 further includes one or more service providers and one or more service registries 300-1 to 300-3.

The ORS 100 is interconnected with each GRS 200 , and may perform OID and location information management and interpretation of each GRS corresponding to the OID.

Each GRS 200 may be interconnected with a service registry of a service provider (service providers A, B, and/or C) to manage information about a service group (eg, a group of services).

The GRS 200 may create and manage a service group, and may perform connection information and interpretation with detailed IoT services belonging to the service group. The GRS 200 may manage information on a service group and connect a user to a required specific service belonging to the service group.

A service provider may have at least one service registry to manage. The service provider has its own identification scheme for providing a specific service by itself, and may include a corresponding service registry 300-1 to 300-3 for managing service-related information.

That is, the plurality of service registries 300-1 to 300-3 may be operated by a service provider. For example, the first service registry 300-1 is operated by the service provider A, the second service registry 300-2 is operated by the service provider B, and the third service registry 300-3 is It is operated by service provider C.

Each service registry 300-1 to 300-3 may manage information of a specific service provided by a corresponding service provider, for example, an IoT service. In addition, each service registry 300-1 to 300-3 may manage detailed IoT services and information that can be provided by a corresponding service provider.

FIG. 2 is a diagram for explaining a schematic operation of the GRS shown in FIG. 1 .

Referring to FIG. 2 , the GRS may perform service group management for IoT services. IoT services belonging to a service group may be services having similar properties. That is, IoT services having similar properties may be grouped.

For service group management, the GRS may include an OID and a list (group list) for managing the group ID (gID) of the service group corresponding to the OID. In addition, the GRS may include a database for mapping a group ID (gID) and information of IoT services belonging to a service group. For example, the information may include a service ID (sID), a registry ID (regID), service provider information, and service-related details.

GRS may perform the role of identification (identification) for the service group. The OID may be used as a key value for identifying a group ID (gID). Accordingly, the GRS may return a corresponding group ID (gID) and information on IoT services belonging to the corresponding service group.

The GRS may receive the OID, interpret a group ID (gID) that is an identifier of a service group corresponding to the OID, and interpret information on detailed IoT services included in the corresponding service group.

The GRS may request the service provider to perform a required IoT service by the user through the detailed IoT service information obtained by the final interpretation.

FIG. 3 is a diagram for explaining a schematic operation of the ORS shown in FIG. 1 .

Referring to FIG. 3 , the ORS may perform centralized management for each GRS. For example, the ORS may manage information of each GRS.

In addition, the ORS may perform identification and interpretation for each GRS. . The ORS may include an OID and a database in which location information of each GRS corresponding to the OID (eg, URI (based on UIF)) is stored.

OID has a predefined and globally unique value, and can be individually assigned to all GRSs. This means that since a group ID is assigned to only one GRS, each group of IoT services can be identified with an assigned OID.

The OID can be used as a publicly well-known value, such as a port number for Transmission Control Protocol/Internet Protocol (TCP/IP). Accordingly, all nodes can recognize the OID value related to the IoT service group.

That is, the OID may be used as a key value for identifying each GRS. For example, when an arbitrary user transmits an OID value to the ORS, the ORS may return a URI value of the GRS corresponding to the OID.

All terminals can know the identifier value of the service group for the IoT service through the OID. Users know which GRS service can be provided through ORS while using OID as an identifier for the service group.

FIG. 4 is a diagram for explaining a schematic operation of the service registry shown in FIG. 1 .

Referring to FIG. 4 , a local service provider may maintain and manage one service registry. The service registry may be a local resolution system that supports specific services. For example, the service registry may be a server managed by a service manager in which detailed IoT services are finally executed.

The service registry may manage a service ID (sID) and a database in which a service (eg, “call police”) corresponding to the service ID (sID) is stored.

This database can be used by the service registry to look up the service ID corresponding to the service.

Upon receiving a service ID requested from the GRS, the service provider may execute the corresponding service. Here, the method of generating the service identifier may differ depending on the SP.

Hereinafter, an object identifier-based group service interpretation framework procedure will be described.

5 is a diagram for explaining a registration procedure of an object identifier-based group service according to an embodiment.

Referring to FIG. 5 , in order to group and manage IoT services, a registration procedure needs to be performed first. Also, the IoT service group needs to be identified by OID.

The registration procedure may include a two-step registration procedure (SP-GRS & GRS-ORS). For example, a two-step registration procedure may provide an IoT service registration procedure from the service provider to the GRS and a GRS registration procedure to the ORS.

Among the registration procedures, step 1 is the IoT service registration procedure from the service provider to the GRS as follows.

A service provider may send a registration request to a service registry to register a specific IoT service with a service registry. The registration request may include a service ID (sID) corresponding to the IoT service.

The service ID (sID) may follow a different method of generating an identifier according to a service provider. That is, different service providers may generate service identifiers in different ID formats.

The service registry may manage (eg, register) a service ID (sID) corresponding to the IoT service in a database in response to a registration request transmitted from the service provider. The service registry may store and manage two-tier information, for example, a service ID-IoT service.

The service registry may send a registration request to the GRS to register the IoT service with the GRS. The registration request may include a service ID (sID) and a registry ID (regID).

That is, the service registry may transmit its own registry ID (regID) to the GRS as additional pairing information together with the service ID (sID). Since the service ID (sID) is transmitted to the GRS together with the service registry information (registry ID (regID)), it may be usable as a unique identifier in the identification and interpretation process.

Any service registry can be linked to GRS. The service registry may transmit its registry ID (regID) and service ID (sID) to the GRS whenever an IoT service is registered or at regular time.

The GRS may manage (eg, register) IoT service information in a database in response to a registration request transmitted from the service registry. For example, the IoT service information may include a service ID (sID), a registry ID (regID), service provider information, and service-related details.

The GRS may create a service group by grouping IoT services, and may generate a group ID corresponding to the service group. When a group is required for an IoT service, a service group is created in the database, and an ID for the service group can be created. The group ID is generated by the GRS according to the request of the GRS operator.

Since GRS cannot generate OIDs by itself, if an IoT service group is created, a registration request to request OID assignment corresponding to the service group can be sent to the ORS. A registration request may include a URI.

The second stage of the registration procedure is the registration to the ORS (Registration to OID resolution server) and is as follows.

The ORS may generate and allocate an allocable OID to the service group created by the GRS in response to the registration request transmitted from the GRS, and transmit the assigned OID. ORS may store and manage two-tier information, for example, URI-OID of GRS in a database.

The GRS may receive the OID, store and manage the group ID and corresponding OIDs (corresponding OIDs) in a list (eg, a group list).

6 is a diagram for explaining an interpretation procedure of an object identifier-based group service according to an embodiment.

An OID-based interpretation procedure for an IoT service group will be described with reference to FIG. 6 . This procedure assumes that all components are interconnected for networking over the Internet, and that the information for networking with GRS and ORS is well known. Also, consider the emergency situation.

1) The user can transmit the OID (1.1.1) corresponding to the IoT service to the ORS.

For example, in case of an emergency, a user who is one of the people around may open an application (application) to request an IoT service group "Emergency Service" with an electronic device (eg, a mobile phone). When the user clicks the "Emergency Service" button, the corresponding OID (1.1.1) can be sent to the designated ORS inside the application.

2) ORS may retrieve URI (..01), which is information on the location of GRS corresponding to OID (1.1.1) in the database, and transmit the retrieved URI (..01) of GRS to the user.

That is, the user knows the GRS information corresponding to the OID (1.1.1).

3) The user can transmit the OID (1.1.1) to the GRS using the URI (..01) transmitted from the ORS.

For example, the user's application can obtain the connection information to the GRS from the URI (..01) information returned from the ORS. The user's application may transmit the OID (1.1.1) to the GRS to obtain information about the IoT service group of "Emergency Service" by using the URI (..01).

4) The GRS may return the group ID (01) for "Emergency Service" and IoT service information belonging to the group to the user in response to the OID (1.1.1).

The GRS may receive the OID (1.1.1) and retrieve the group ID corresponding to the OID (1.1.1) from the group list. The GRS may search for information on the IoT service belonging to the group in the database using the found group ID (01). The GRS may transmit the group ID 01 and information (eg, network address, specific service ID, etc.) of the IoT service belonging to the group to the user application.

5) Each service ID (001 & 00a) may be transmitted to the corresponding service registry separately.

Users can receive all the information they need to request group services. Users can individually request related IoT services of groups with service IDs (001 & 00a) to the corresponding service registry. When the service registry receives a request from the GRS, the service provider may take an interest in performing the service.

6) A service provider may provide services (eg, “call police” and “call 911”).

Upon receiving the detailed IoT service identifier (service ID) value, the service provider executes the corresponding service. All IoT services belonging to the group may be performed by a one-stop request.

The above-described OID-based solution framework can be processed on the assumption that GRS and ORS information is well known. If the information of GRS and ORS is attacked by a third party, we cannot provide IoT services and group management, and it may have negative consequences for users. It is necessary to protect all input and output values of GRS and ORS.

In the embodiments, in the case of services with heterogeneous characteristics and diversity such as the Internet of Things, synergy is highly likely to be maximized due to the effect of integrated operation for linked services, and various services and technologies are not operated in mobile devices such as mobile phones. There is an advantage in that services and added value using it are expected under possible circumstances.

The method according to the embodiment may be implemented in the form of program instructions that can be executed through various computer means and recorded in a computer-readable medium. The computer-readable medium may include program instructions, data files, data structures, etc. alone or in combination. The program instructions recorded on the medium may be specially designed and configured for the embodiment, or may be known and available to those skilled in the art of computer software. Examples of the computer-readable recording medium include magnetic media such as hard disks, floppy disks and magnetic tapes, optical media such as CD-ROMs and DVDs, and magnetic such as floppy disks. - includes magneto-optical media, and hardware devices specially configured to store and execute program instructions, such as ROM, RAM, flash memory, and the like. Examples of program instructions include not only machine language codes such as those generated by a compiler, but also high-level language codes that can be executed by a computer using an interpreter or the like. The hardware devices described above may be configured to operate as one or more software modules to perform the operations of the embodiments, and vice versa.

The software may comprise a computer program, code, instructions, or a combination of one or more thereof, which configures a processing device to operate as desired or is independently or collectively processed You can command the device. The software and/or data may be any kind of machine, component, physical device, virtual equipment, computer storage medium or device, to be interpreted by or to provide instructions or data to the processing device. , or may be permanently or temporarily embody in a transmitted signal wave. The software may be distributed over networked computer systems and stored or executed in a distributed manner. Software and data may be stored in one or more computer-readable recording media.

As described above, although the embodiments have been described with reference to the limited drawings, those skilled in the art may apply various technical modifications and variations based on the above. For example, the described techniques are performed in a different order than the described method, and/or the described components of the system, structure, apparatus, circuit, etc. are combined or combined in a different form than the described method, or other components Or substituted or substituted by equivalents may achieve an appropriate result.

Therefore, other implementations, other embodiments, and equivalents to the claims are also within the scope of the following claims.

Claims (10)

retrieving a first group identifier of a first service group corresponding to the first object identifier in response to the first object identifier transmitted through the URI corresponding to the first object identifier;
identifying services belonging to the first service group using the first group identifier; and
transmitting information of the identified services;
including,
The first service group is a service group requested by a user,
The URI is location information of the group service analysis server that created the first service group,
The first object identifier is for identifying the group service interpretation server, and the first object identifier is used as a key value for identifying the first group identifier of the first service group, object identifier-based service group identification Way.
delete According to claim 1,
The information is an object identifier-based service group identification method including service identifiers of the services and identifiers of the corresponding registry.
delete According to claim 1,
individually requesting a specific service from among the services to a corresponding service registry using the information
An object identifier-based service group identification method further comprising a.
According to claim 1,
Registering the specific service in response to a registration request for the specific service
An object identifier-based service group identification method further comprising a.
7. The method of claim 6,
The registration step is
creating a second service group by grouping the specific service;
generating a second group identifier corresponding to the second service group; and
managing a second object identifier assigned to the second service group and the second group identifier by matching a group list
An object identifier-based service group identification method comprising a.
8. The method of claim 7,
The registration step is
Mapping and managing the second group identifier and information on the specific service
An object identifier-based service group identification method further comprising a.
9. The method of claim 8,
The object identifier-based service group identification method, wherein the information on the specific service includes a service identifier of the specific service and an identifier of a corresponding registry.
8. The method of claim 7,
Mapping and managing a second object identifier assigned to the second service group and a URI of a group service interpretation server that has created the second service group
An object identifier-based service group identification method further comprising a.

Images