KR20170051718A

KR20170051718A - Method for sharing resource information of thing

Info

Publication number: KR20170051718A
Application number: KR1020150152241A
Authority: KR
Inventors: 강현중; 문영백; 오세원; 이호성
Original assignee: 한국전자통신연구원
Priority date: 2015-10-30
Filing date: 2015-10-30
Publication date: 2017-05-12
Also published as: KR101823386B1

Abstract

The present invention relates to a method for sharing resource information of a thing in an environment of the internet of things (IoT). According to an embodiment of the present invention, the method for sharing resource information of a thing comprises: a step of collecting thing metadata of a target resource; a step of using the collected thing metadata to prepare a thing specification if the collected thing metadata are not identical to previously registered thing metadata; and a step of transferring the prepared thing specification to a thing registry. Collection of the thing metadata can be periodically or non-periodically performed. According to embodiments of the present invention, resource information for multiple things located in a dispersion environment can be collected, converted, and updated through a unified window to unify search and update of thing resource information to be performed by various application services to process search and update. Maintenance of information freshness can be improved.

Description

[0001] The present invention relates to a method for sharing resource information,

Embodiments of the present invention relate to a method for sharing object resource information in an object internet environment.

The Internet of things is variously defined in organizations such as the International Telecommunication Union Telecommunication Standardization Sector (ITU-T), the European Telecommunications Standards Institute (ETSI), the Institute of Electrical and Electronics Engineers (IEEE), and the Internet Engineering Task Force (IETF) Commonly, intelligent and automated things based on context awareness can be defined as global network infrastructures that exchange information with each other.

Things The most important part of Internet technology is the exchange of information between various objects. In order to exchange information, mutual connectivity between objects is very important. Currently, various standardization organizations are working on standardization for mutual connection of objects. Standardized procedures and standardized procedures including identifiers, attributes, and so on are standardized so that various objects can share their information on the Internet and manage shared information.

The space or system in which the object resource information is stored according to the standard defined by each standard is called CSE (Common Service Entity) or SCL (Service Capability Layer). Hereinafter, the space or system in which the object resource information is stored is referred to as a object store.

Meanwhile, the conventional Web crawling technology is a technology that enables information of a target resource to be used by searching and managing a large number of registered resources on the web through an organized and automated method. Today's myriad of search engines collect information and provide search results through these web crawling technologies.

It is also necessary to search and manage resources in the Internet environment. Although providing functions for retrieval from individual object repositories, the user or application service provider must directly access the object repository to find the objects for which the information is to be acquired. Therefore, there is a need for a method of collecting and managing object resource information scattered on various object repositories and providing them to the outside.

Korean Patent Publication No. 10-2014-0133779 entitled " Open Type M2M System and Method "

Embodiments of the present invention provide a method for searching, collecting, and updating object resource information in consideration of the object internet environment in which the state of the object and information are constantly changing.

Embodiments of the present invention allow the collected object resource information to be processed and provided as information corresponding to a request of an application service.

A method for sharing object resource information according to an embodiment of the present invention includes collecting object meta data of a target resource; Creating an object description using the collected object metadata if the collected object metadata is not the same as previously registered object metadata; And delivering the created object specification to the object registry, wherein the object metadata collection can be periodic or non-periodic.

According to the embodiments of the present invention, resource information about a plurality of objects located in a distributed environment is collected, transformed, and updated through a unified window, thereby unifying and processing object resource information search and update to be performed by various application services And can improve the maintenance of freshness of information.

According to the embodiments of the present invention, since various application services are expected to search for objects suitable for the user, accessibility to objects in the object internet environment can be improved by reflecting more specific object resource information publication criteria and the like .

FIG. 1 is an exemplary diagram showing a shared structure of object resource information in an object Internet environment; FIG.
2 is an exemplary diagram showing resource information having object metadata of a hierarchical structure,
3 is an exemplary diagram illustrating resource information according to the oneM2M standard,
FIG. 4 is an exemplary diagram showing the flow of object resource information in the Internet of objects;
5 is a diagram illustrating a flow of object resource information in an object Internet environment to which an object resource information sharing apparatus according to an embodiment of the present invention is applied.
FIG. 6 is a flowchart for explaining the object repository searching process according to an embodiment of the present invention; FIG.
FIG. 7 is an exemplary diagram for explaining a resource information registration procedure according to an embodiment of the present invention; FIG.
FIG. 8 is a flow chart for explaining a resource information re-searching process according to an embodiment of the present invention;
9 is a block diagram for explaining a RaaT according to an embodiment of the present invention,
FIG. 10 illustrates an example in which a thing registry is managed in a distributed environment according to an embodiment of the present invention; FIG.

In the following description of the embodiments of the present invention, a detailed description of known functions and configurations incorporated herein will be omitted when it may make the subject matter of the present invention rather unclear.

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

FIG. 1 is an exemplary diagram showing a shared structure of object resource information in an object internet environment.

In the Internet environment, various objects register their resource information in the object repository via the Internet, and exchange object resource information among the objects through the object repository. Several standards related to the Internet are developing these object repositories on their own. These object repositories have a common function of allowing various objects to be searched by the same reference within each standard scope, a function of collecting resource information about the retrieved objects, and a control of objects based on object resource information It includes the ability to

On the other hand, the object resource information representing an object on the object Internet may include one or more resources, and each resource may have an identifier (for example, a Uniform Resource Identifier (URI)). Each resource can record its information as object metadata. The object metadata can be created, modified or deleted according to the state of the object or at the request of the external user. Each resource may have similar or different information representing object attributes as object metadata. Resources can be represented in a parallel or hierarchical structure. That is, there may be multiple resources to represent an object, a particular resource may represent an object, and the resources and sub-resources may be used to represent an object.

2 is an exemplary diagram showing resource information having object metadata in a hierarchical structure.

An object can be represented by a resource of application. An application can have a sub-resource called a repository, and the repository can be operated as a sub-resource of an application. A repository can have a sub-resource called a storage object, and a storage object can also be operated as a sub-resource of an application. The storage object belongs to the repository hierarchically and can manage the object metadata related to the application.

For example, the application may be an application that provides temperature / humidity information. The temperature / humidity application can have the object metadata as the time when it is registered in the current platform and the keyword for searching from the outside. Temperature / humidity applications may have reservoirs that store temperature values below. The repository may have object metadata as the time at which the repository was created and keywords for retrieval from outside. The repository may have a storage object that stores the actual sensing value, and the storage object may have the object metadata as the temperature value, the Celsius, and the recording date and time. Also, the repository may have a storage object for storing information of the sensor, and the storage object may include a measurement unit, a specification of a product, a point of interest (POI), a performance information, a function and a control Data.

On the other hand, object metadata can be expressed in various formats such as XML (Extensible Markup Language) or JSON (JavaScript Object Notation). The object metadata includes at least one of a resource ID, a resource type, a keyword, a time at which a resource is created, a time at which information of the resource is updated, a time at which the resource is to be discarded, , Usage right, and availability information.

The object metadata may include unique information according to the type of object. For example, the object metadata of an object providing temperature information includes information about the type of the arenetwork, such as Celsius / Fahrenheit, current temperature value, product name, precision, unit of measure, product unique identifier, Unit, product specification, point of interest (POI), performance information, function, and control (or use) method. For example, the object meta data of a smart plug may include at least one of a method of turning on / off a relay of a smart plug, and a current use power.

The structure of the object metadata may be defined in each standard or may be constituted by the product manufacturer or user unless otherwise defined in the standard.

3 is an exemplary diagram showing resource information according to the oneM2M standard.

3, information (Label: homeEnvironmentMonitor) indicating that the application entity (AE) is for monitoring the home environment and time (creationTime: 2015-07-31T13: 32:21) Data.

Then, it is shown that the sub-resource of the application entity has a keyword (Label: temperature) for object search as object metadata.

In addition, the contentInstance of the container is determined by the manufacturer (samsung), the temperature unit (unit: Fahrenheit), the temperature value (value: 76) and the temperature measurement time (creationTime: 2015-08-01T07 : 32: 11) as object metadata.

FIG. 4 is a diagram illustrating an example of a flow of object resource information in an object internet environment.

The object registry can provide information required for the application service through the interface with the application service. The application service may be, for example, a cloud service for an application installed in the communication terminal. The object registry can search for objects in the object repository for each object repository, and select the appropriate object from among the object repositories to provide resource information for the object to the application service.

5 is a diagram illustrating an example of a flow of object resource information in an object internet environment to which an object resource information sharing apparatus according to an embodiment of the present invention is applied.

The object resource sharing device can unify and process the object resource information search and update that must be performed by various application services in the object internet environment. Hereinafter, for convenience of explanation, the object resource information sharing device is referred to as RaaT (Resource as a Thing). In addition, the object that conveys the object specification conformed through the resource information is called the object registration register, the object resource information sharing system is called the object register storage, and the representative resource of the object registered in the object store is called the application.

The RaaT can periodically or non-periodically search and subscribe to each object repository to register and manage resource information of objects connected to each object repository. Accordingly, the object registry can collect the latest resource information of various objects and objects by interworking with the RaaT, and can provide them to the application service.

The method of sharing information on the object resources performed by the RaaT will be described with reference to FIGS. 6 to 8. FIG.

FIG. 6 is a flowchart for explaining the object repository searching process according to an embodiment of the present invention. Depending on the embodiment, at least one of the steps shown in Fig. 6 may be omitted.

At step 601, the RaaT may load the URI information of the object repository from the database. The URI information may include a URI of the object repository and a re-search cycle corresponding to the URI.

In step 603, the RaaT checks whether there is a URI that has arrived at the re-search cycle based on the loaded URI information, and if there is a URI to which the re-search cycle comes, the process may proceed to step 605.

In step 605, the RaaT may register the URI of the object repository that will perform the search in the database and record that the registration has been initiated. Here, the database may be a space (for example, a hard disk) capable of continuously storing, or a volatile storage space (e.g., memory) that is stored only during a process is performed.

In step 607, the RaaT may register RaaT itself as an application in the object repository on which it performs the search.

In step 609, the RaaT can perform an application discovery by performing a discovery based on a standard that the object repository applies to the object repository.

In step 611, RaaT may store the URI of the retrieved application in the database.

In step 613, the RaaT may perform a resource information registration procedure for the searched application. In this regard, a more detailed description will be made with reference to FIG.

In step 615, when the resource information is registered in the object registry, the RaaT can record the object registration registry information (for example, information on registration) of the corresponding object repository in the database. Then, the RaaT can record the next search time (rediscovery cycle) for the object store in the database.

In the object store search process, RaaT may register a subscription to external object store information added to the object store. For example, in oneM2M, each object repository can manage information about its own and subordinate resources, starting with a resource named CSEbase. In addition, each object repository can interwork with other object repositories through a resource called remoteCSE (external object repository) to provide information about its own common services entity (CSE). Thus, the RaaT can register a subscription to such external repository information.

FIG. 7 is an exemplary diagram illustrating a resource information registration procedure according to an embodiment of the present invention. Referring to FIG. Depending on the embodiment, at least one of the steps shown in Fig. 7 may be omitted.

In step 701, the RaaT may load a list of applications to retrieve from the database. The database may store information (e.g., a URI) of the application found through the object repository search process described with reference to FIG. RaaT can exclude applications that have already been shipped, or that have not yet arrived at the rediscovery cycle, to be searched.

In step 703, the RaaT may set the type of the target resource (application, repository, storage object, etc.).

In step 705, the RaaT may collect object metadata of the target resource. The target resource can be configured variously according to the hierarchical structure of the resources to which the object repository to be searched is subjected.

In step 707, RaaT may register the subscription for the discovered resource. Accordingly, when a change to the resource occurs in the future, the RaaT can receive notification of the change. The RaaT can register a URI or the like to which the notification will be posted to receive the notification.

Here, the subscription function may exist as a service or function in the object store, or may exist in an application service. The subscription function performs a periodic search on the target resource, and when information that is different from the previous one is registered, it transmits information such as the changed information or the URI of the resource where the change occurs to the URI registered as a subscription. The subscription process can be done at any time after the URI for the target resource is obtained.

In step 709, the RaaT checks whether additional resources are required for creating the object specification, and if there are additional resources required, the process proceeds to step 703, otherwise, in step 711, .

In step 711, when the collection of information on all the resources is completed, the RaaT can create the object specification using the collected object meta data.

In step 713, RaaT can deliver the created object specification to the object registry.

In step 715, the RaaT may update the object registry information of the resource to the database.

FIG. 8 is a flowchart for explaining a resource information re-searching process according to an embodiment of the present invention. Depending on the embodiment, at least one of the steps shown in Fig. 8 may be omitted.

In step 801, the RaaT may receive the notification.

The notification may be received when the corresponding resource is changed according to the subscription information registered for the resource. In this case, the notification may be performed on all resources or on a resource corresponding to a specific resource type. The notification may include ID or URI information of the resource to which the change has been made, and may further include object metadata changed according to the embodiment.

The notification may be received when a re-search cycle designated by RaaT or an application service arrives. Resources associated with all objects and objects registered in RaaT can have cycles, and when the cycle arrives, re-searching and updating of information about the target resource can be performed.

In step 803, the RaaT can check what type of target resource the received notification is. For example, RaaT can identify application, repository, and storage objects of the target resource.

In step 805, the RaaT may retrieve object metadata of the target resource.

In step 807, the RaaT compares the currently retrieved information with the information stored in the database and can verify whether the two pieces of information are identical. If the currently retrieved information is not the same as the previously stored information, the RaaT may proceed to step 809. [

At step 809, the RaaT can check if additional resources are needed to create the object specification. If there are further resources required, the RaaT proceeds to step 803, else it may proceed to step 811.

In step 811, when the collection of information on all the resources is completed, the RaaT can create the object specification using the collected object metadata.

In step 813, the RaaT can deliver the created object specification to the object registry.

In step 815, the RaaT may update the object registry information of the resource to the database.

9 is a block diagram for explaining a RaaT according to an embodiment of the present invention.

9, a RaaT according to an exemplary embodiment of the present invention includes a resource search unit 910, a subscription management unit 920, a resource distribution unit 930, an object specification combination unit 940, 950 and a search resource database 960. Depending on the embodiment, at least one of the aforementioned components may be omitted.

The resource search unit 910 can collect resource information registered in the object repository by performing discovery on the object repository.

The subscription management unit 920 can manage subscription information for a single or a plurality of resource types and subscription information received according to a subscription.

The resource distribution unit 930 can extract information used for object description creation from the resource information received from the resource search unit 910. [ The resource distribution unit 930 may have a separate management unit for each resource type.

The item specification combination unit 940 can convert the information required by the object registry using the resource information received from the resource distribution unit 930. [ The item specification combination unit 940 can collect the object meta data of all the resources constituting the individual object. The object metadata may be stored in memory until the collection ends, or may be stored in an auxiliary storage device such as a hard disk. When collection of object metadata ends, the object metadata may be deleted or stored in a persistent storage such as a database and used as a log or the like.

The object specification sending unit 950 can deliver the object specification created by the object specification combination unit 940 to the object registry. The object specification sending unit 950 converts the information received from the object description combining unit 940 into a format that can be used by the object registry through serialization or the like according to a standard used in the object registration place .

The search resource database 960 manages various resource information collected by the resource search unit 910, manages object repository information for searching for resource information, and manages object specification information.

10 is a diagram illustrating an example in which RaaT is managed in a distributed environment according to an embodiment of the present invention.

As the number of object repositories grows, RaaT, which registers and retrieves them, can be increased. In this case, as shown in FIG. 10, a load monitor unit for monitoring the load is arranged in each RaaT, and a load management unit for managing a plurality of RaaTs in a distributed environment based on the load information received by the load monitor unit is added Can operate.

The embodiments of the invention described above may be implemented in any of a variety of ways. For example, embodiments of the present invention may be implemented using hardware, software, or a combination thereof. When implemented in software, it may be implemented as software running on one or more processors using various operating systems or platforms. Additionally, such software may be written using any of a number of suitable programming languages, and may also be compiled into machine code or intermediate code executable in a framework or virtual machine.

Also, when embodiments of the present invention are implemented on one or more processors, one or more programs for carrying out the methods of implementing the various embodiments of the invention discussed above may be stored on a processor readable medium (e.g., memory, A floppy disk, a hard disk, a compact disk, an optical disk, a magnetic tape, or the like).

Claims

Collecting object metadata of the target resource;
Creating an object description using the collected object metadata if the collected object metadata is not the same as previously registered object metadata; And
And delivering the created object specification to the object registry,
The collection of the object metadata may be performed periodically or non-periodically
How to share information on object resources.