WO2019022583A1

WO2019022583A1 - Data query method of specific type device, based on location information

Info

Publication number: WO2019022583A1
Application number: PCT/KR2018/008599
Authority: WO
Inventors: 정승명; 안일엽; 김재호; 이지호
Original assignee: 전자부품연구원
Priority date: 2017-07-28
Filing date: 2018-07-30
Publication date: 2019-01-31
Also published as: WO2019022360A1

Abstract

A data query method of a specific type device, based on location information, is provided. In the data query method according to an embodiment of the present invention, when a data query request including location information is received, a data resource, to which a location information attribute matching the location information included in the data query request is applied, is searched for and results are returned. Therefore, an application can specify location information in a query for data such that only data of a device located at a corresponding location is queried about.

Description

How to look up specific type device data based on location information

The present invention relates to an Internet of Things (IoT) / M2M (Machine to Machine) technology, and more particularly, to a method of inquiring device data on an IoT / M2M platform.

Currently, it is impossible for oneM2M standard to inquire device data based on standardized location information. That is, it does not provide a link between device data and location information.

A method of storing fixed location information in a non-standardized manner in the " labels " attribute of a <container> resource that stores device data can be assumed. However, since this is a non-standard method, as shown in FIG. 1, other applications or platforms may not be able to know the meaning of this information and use it.

Therefore, currently oneM2M standard can not retrieve data associated with a specific location. Therefore, it is required to search for a solution to solve this problem.

SUMMARY OF THE INVENTION The present invention has been made in order to solve the above problems, and it is an object of the present invention to provide a method and system for an application to inquire only data of a device located at a corresponding location by specifying location information in a query for data .

According to an aspect of the present invention, there is provided a data inquiry method including receiving a data inquiry request including location information; Retrieving a data resource to which a location information attribute matching the location information included in the data inquiry request is applied; And returning the search result.

The location information attribute may be stored in the data resource.

In addition, the location information attribute may be included in the upper resource of the data resource.

The location information attribute may include the location information of the device or the ID of the resource containing the location information of the device.

Also, the data resource may include an attribute including information on whether or not the positional information attribute is applied.

The location information included in the data inquiry request may include information on three or more coordinates for specifying the area, and information for designating the inside or outside of the area.

In addition, the data inquiry request includes a resource type condition, and the retrieving step is capable of retrieving a resource of a type that conforms to the resource type condition, to which a location information attribute conforming to the received location information is applied.

According to another embodiment of the present invention, an M2M system includes: a communication unit for receiving a data inquiry request including location information from an application executed in a user terminal; And a processor for searching for a data resource to which a location information attribute matching the location information included in the data inquiry request is applied, and for returning the search result to the application.

As described above, according to the embodiments of the present invention, an application can specify location information in a query on data and inquire only data of a device in the corresponding location.

In addition, according to the embodiments of the present invention, not only the location information but also the data resource type can be specified and only the specific type of data of the device at the corresponding location can be inquired.

1 illustrates a problem of storing fixed location information in a non-standardized manner in oneM2M platform,

FIG. 2 is a block diagram illustrating the concept of the present invention,

3 is a diagram illustrating a resource structure of oneM2M platform for location information based device data inquiry,

4 is a diagram showing another structure of resources of oneM2M platform for location information based device data inquiry;

FIG. 5 is a diagram illustrating a process of searching for location information and returning a search result,

6 is a diagram illustrating an IoT / M2M system to which the present invention is applicable,

7 is an internal block diagram of the electronic devices shown in Fig.

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

1. Display device data based on location information

2 is a diagram provided in a conceptual description of the present invention. As shown in FIG. 2, a method of inquiring device data based on location information is disclosed in the embodiment of the present invention.

In other words, the application executed in the user terminal may include location information such as "are in {" x1, y1 "," x2, y2 "," x3, y3 " Quot;} " to inquire only the data of the device at the corresponding position.

Furthermore, in the embodiment of the present invention, a method of specifying not only location information but also a data resource type and inquiring only data of a specific type among data generated by a device at the corresponding location is presented.

2. Resource structure for location information based query # 1

3 is a view showing a resource structure of oneM2M platform for location information based device data inquiry. For ease of understanding and explanation, FIG. 3 further shows an application for inquiring data.

As shown in FIG. 3, in the oneM2M platform according to the embodiment of the present invention, a location information attribute is added to a data container resource.

In FIG. 3, two types of location information attributes, a "locationContainerID" attribute and a "locationTag" attribute, are selectively used depending on whether the device is moved or not.

Specifically, in the case of a fixed device, location information fixed in the "locationTag" attribute is recorded, and the location information can be used without limitation in the types and types such as GPS coordinates, address, zip code, and the like.

In the case of a mobile device, location information is stored in other container resources and updated periodically. The ID of the container resource containing the location information is stored in the "locationContainerID" attribute so that the container resource can be linked to the container resource.

As with fixed devices, there is no restriction on the format and type of location information for mobile devices.

<Container> resources with location information properties are searched for location information based queries, but <container> resources without location information properties are not searched for location information based queries.

In FIG. 3, it is assumed that the <container> resource is created and the location information of the device storing the data is added to the <container> resource as the location information attribute. However, the resource type for storing the data is expandable.

That is, the technical idea of the present invention can also be applied to a case where a location information attribute is added to a resource other than the <container> resource, such as the <timeSeries> resource, the <flexContainer> resource, and the <semanticDescriptor> resource.

3. Resource structure for location information based query # 2

4 is a view showing another structure of resources of oneM2M platform for location information based device data inquiry.

As shown in FIG. 4, the "locationContainerID" attribute and the "locationTag" attribute may be added to the <AE> resource which is an upper resource of the resource in which data is stored.

At this time, the location information attribute stores <AE> location information of the device that created the resource.

As shown in FIG. 4, a " locationInfoInheritence " attribute is added to a < container > resource in which data <AE> The " locationInfoInheritence " attribute contains information indicating whether the location information is applied to the <container> resource.

Specifically, when the "locationInfoInheritence" property is "true", the <container> resource refers to the location information of the device that generated the parent node <AE>. In this case, the data of the <container> resource is searched for in the location information based query.

On the other hand, if the "locationInfoInheritence" property is "false", the <container> resource does not refer to the location information of the device that generated the parent node <AE>. In this case, the data of the <container> resource is not searched for in the location information based query.

If the <AE> resource does not have the location property attributes "locationContainerID" and "locationTag" attributes, all data resources subordinate to the <AE> resource are not searched for location information based queries.

Meanwhile, the location information recording by the resource structure shown in FIG. 4 is applicable even when the upper resource of the resource in which data is stored is a resource other than the <AE> resource, for example, a <remoteCSE> resource.

Furthermore, the technical idea of the present invention can be applied to a case where data is stored in resources other than the <container> resource, the <timeSeries> resource, the <flexContainer> resource, and the <semanticDescriptor> resource as described above.

4. Filter condition for querying location-based data

5 is a view for explaining a process of oneM2M platform to retrieve and return data based on location information when an application inquires data based on location information.

In the location information based inquiry request of the application, a filter condition may be added as shown on the left side of FIG. 5, and a plurality of filter conditions may be combined into a logical operation.

If the "locationBasedDataQuery" in the filter condition is "true", the data of the container resource is returned instead of the ID of the data container resource of the device satisfying the location. At this time, the container resource data may be implemented to be returned to the latest data.

On the other hand, if "locationBasedDataQuery" is "false", the ID of the data container resource of the device satisfying the position is returned.

And, among the filter conditions, " locationCoordinates " and " coordinateBorder " are conditions for specifying a position as a region by three or more coordinates. The " locationCoordinates " contains three or more coordinates that can specify a region, and " coordinateBorder " contains information specifying the inside of the region, outside the boundary, inside the boundary, and outside the boundary.

In the first filter condition of the location information based inquiry request shown in FIG. 5, the inside of the boundary of the rectangular area specified by the four coordinates is specified as the device location.

On the other hand, it is possible to represent all or a part of the coordinates constituting "locationCoordinates" by a location information attribute of "locationContainerID" or "locationTag".

Among the filter conditions, "locationTag" is a condition for specifying a location to a point other than an area.

The "resourceType" can be added to the filter condition of the location information based inquiry request. "resourceType" is a condition for specifying the resource type (<container>, <timeSeries>, <flexContainer>, <semanticDescriptor>).

Based on the application's location information based query request, oneM2M platform searches for resources satisfying the resource type condition as resources having the location information attribute according to the filter condition, and stores the ID of the retrieved resource or the latest data And returns it to the application along with the location information and the "labels" attribute (eg "temp_sensor1").

5. IoT / M2M system

6 is a diagram illustrating an IoT / M2M system to which the present invention is applicable. As shown in FIG. 6, the IoT / M2M system to which the present invention is applicable includes a server 100-1, gateways 100-21 and 100-22, devices 100-31, 100-32, and 100-33 , 100-34) are connected and constructed so that they can communicate with each other.

The number of electronic devices shown in FIG. 6, for example, the server 100-1, the gateways 100-21 and 100-22, and the devices 100-31, 100-32, and 100- 33, and 100-34) are illustrative, the technical idea of the present invention can be applied to the case of implementing them differently.

Further, it is needless to say that the connection structure of the electronic devices shown in Fig. 6 can be replaced by other methods as needed.

All the electronic devices shown in Fig. 6 can function as an M2M platform. That is, the server 100-1, the gateways 100-21 and 100-22, and the devices 100-31, 100-32, 100-33, and 100-34 are all based on the location information based on the embodiment of the present invention It is possible to provide a specific type resource data inquiry service.

7 is an internal block diagram of the electronic devices shown in Fig. The configurations necessary for implementing the embodiment of the present invention include all of the servers 100-1, the gateways 100-21 and 100-22, the devices 100-31, 100-32, 100-33, and 100-34 Common. Therefore, they are collectively referred to as " 100 " in Fig. 6, and are collectively referred to as electronic devices hereinafter.

7, the electronic apparatuses according to another embodiment of the present invention include a communication unit 110, a processor 120, a storage unit 130, and a function block 140. As shown in FIG.

The communication unit 110 is communication interface means for communicating with an external device and accessing an external network.

Processor 120 includes at least one AE (Application Entr) and a CSE (Common Service Entity). Depending on the type and function of the electronic device, AE may not be included.

The processor 120 performs the procedures necessary for the specific type device data inquiry service based on the location information based on the location information described above and the processor 120 performs the specific type device data inquiry service based on the location information Provide the necessary storage space.

The function block 140 performs the function of the electronic device itself. For example, if the electronic device is the server 100-1, the virtual machines that provide the user service correspond to the function block 140. [

6. Variations

It goes without saying that the technical idea of the present invention can also be applied to a computer-readable recording medium having a computer program for performing the functions of the apparatus and method according to the present embodiment. In addition, the technical idea according to various embodiments of the present invention may be embodied in computer-readable code form recorded on a computer-readable recording medium. The computer-readable recording medium is any data storage device that can be read by a computer and can store data. For example, the computer-readable recording medium may be a ROM, a RAM, a CD-ROM, a magnetic tape, a floppy disk, an optical disk, a 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 the computers.

While the present invention has been particularly shown and described with reference to exemplary embodiments thereof, it is to be understood that the invention is not limited to the disclosed exemplary embodiments, but, on the contrary, It will be understood by those skilled in the art that various changes in form and detail may be made therein without departing from the spirit and scope of the present invention.

Claims

Receiving a data inquiry request including location information;

Retrieving a data resource to which a location information attribute matching the location information included in the data inquiry request is applied; And

And returning a result of the search.
The method according to claim 1,

The location information attribute,

And the data is stored in a data resource.
The method according to claim 1,

The location information attribute,

And the data is stored in a higher resource of the data resource.
The method according to claim 2 or 3,

In the location information attribute,

And the ID of the resource in which the location information of the device is stored or the location information of the device is stored.
The method of claim 3,

In the data resource,

Wherein the attribute information includes information on whether or not the location information attribute is applied.
The method according to claim 1,

The location information included in the data inquiry request includes,

Information on three or more coordinates for specifying an area, and information for designating an inside or outside of the area.
The method according to claim 1,

The data query request includes a resource type condition,

In the retrieving step,

A location information attribute matching the received location information is applied, and a resource of a type conforming to the resource type condition is retrieved.
A communication unit for receiving a data inquiry request including location information from an application executed in a user terminal; And

And a processor for searching a data resource to which a location information attribute corresponding to the location information included in the data inquiry request is applied, and for returning the search result to the application.