KR102214185B1 - Resource Retrieval Method - Google Patents

Abstract

A resource acquisition method is provided. A resource acquisition method according to an embodiment of the present invention acquires multiple resources at once in a desired order for <latest> resources, <oldest> resources, <container> resources, <flexContainer> resources, and <timeSeries> resources. . Accordingly, it is possible to obtain a specific number by sorting data in the storage according to a specific criterion.

Description

Resource Retrieval Method}

The present invention relates to a method of acquiring resources, and more particularly, to a method of arranging and acquiring a plurality of resources.

The oneM2M standard technology basically allows one resource to be acquired (RETRIEVE) with a single request, but N resources can be acquired simultaneously by using the Result Content request parameter.

For example, in order to acquire <contentInstance> resources that are children of the <container> resource at once, indicate the <container> resource as the To parameter, and set the Result Content parameter value to "child-resource", the <container> resource <contentInstances> resources, which are children's resources, can be acquired at once.

In this case, if the limit and level condition of the Filter Criteria request parameter are used together, the number and range of resources received as a result can be limited. The limit indicates the number of resources included in the response message, and the level indicates the depth of the resource tree from the target resource (i.e. To parameter).

When using Result Content as described above, the platform may deliver all the resources the requestor wants in one request message at a time, or only part of it.

This can prevent a single response message received by the requestor from becoming too large, and for a platform that simultaneously processes requests from multiple requesters, it is overhead to process all resources by one requestor at once. Can be, so this can be done selectively.

If the platform returns only some resources from the overall result, the requestor transmits the location information (offset) to be re-acquired by an additional request message as a Content Offset response parameter. In this case, it also includes the Content Status value, indicating that only partial results, not all results, are included in the response message.

When the requestor receives such a response message, an additional acquisition request message can be sent to the platform, and an additional request message is transmitted using the Content Offset value received from the platform in the offset condition of the Filter Criteria.

The offset condition can also be used in the above example, and even when the requestor attempts to acquire a certain number of resources from an arbitrary location, it is also possible to use the offset condition regardless of the previously received platform response message.

In this case, the To parameter uses the same value as the previous request message. When receiving this request, the platform internally performs the acquisition operation from the To parameter, but does not include the resources corresponding to the offset in the response message, and includes resource information in the response message from the position indicated by the offset.

1 shows a method of acquiring multiple resources at once in oneM2M.

When requesting to acquire multiple resources using the Result Content parameter for <container> resources, it is not possible to predict what order the platform applies and includes the resources in the response message.

In the case of <container> resources, it has <latest> and <oldest> virtual resources as child resources. This provides a way to access resources in the chronological order they were created. However, only one of the children of the <container> resource can access the latest or oldest <contentInstance> resource, and has the disadvantage that it cannot be sorted by criteria other than chronological order.

Similar to the <container>/<contentInstance> resource, there are <flexContainer> and <timeSeries>/<timeSeriesInstance> resources as resource types related to storing and sharing data, but they are limited to <oldest>, < It doesn't even have the latest> resources. Fig. 2 shows a method for indicating a limited order, which is a problem in oneM2M.

The present invention has been conceived to solve the above problems, and an object of the present invention is to provide a method for acquiring a plurality of resources at once according to a specific order.

Another object of the present invention is to provide a method capable of acquiring a plurality of resources of a specific number (when using a limit condition of Filter Criteria) from a specific location (when using an offset condition of Filter Criteria) at one time.

According to an embodiment of the present invention for achieving the above object, the resource acquisition method is, in a desired order, for <latest> resources, <oldest> resources, <container> resources, <flexContainer> resources, <timeSeries> resources, etc. Acquire multiple resources at once.

As described above, according to the embodiments of the present invention, data in the storage may be sorted according to a specific criterion and obtained from a specific location by a specific number. In addition, the above operation can be applied to various resource types storing data.

1 is a diagram showing a method of acquiring multiple resources at once in oneM2M;
2 is a diagram showing a method for indicating a limited order, which is a problem in oneM2M;
3 is a condition used to acquire multiple resources by ordering <latest> and <oldest> resources,
4 is a condition used to obtain multiple by ordering <container> resources,
5 is a condition used to obtain multiple <flexContainer> resources by ordering them.

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

1. How to apply to <latest>, <oldest> resources

Conventionally, when the Filter Criteria is included in the request message, this is not applied directly to the target virtual resource. For example, if a request message to be fan-out is transmitted to the <fanOutPoint> resource including Filter Criteria, the Group Hosting CSE includes this parameter in the fan-out request message and transmits it to Member Hosting CSE. fanOutPoint> It does not apply to the fan-out operation itself, which is a function of virtual resources.

Therefore, in order to apply Filter Criteria to virtual resources such as <latest> and <oldest>, a new condition (indicator) having the same name as the virtualResource shown in FIG. 3 may be included.

If this value is included with other filter conditions in the request message (for example, a Boolean value such as TRUE), the platform will also process other filter conditions in the process of processing the virtual resource when the target resource indicated by the To parameter is a virtual resource. It is applied, and the operation of the virtual resource can be changed and applied.

For example, in the case of <latest> resource, an operation that points to the most recent sibling <contentInstance> resource is performed, but in the case of a request that includes the above virtualResource condition, multiple resources in the latest order rather than one <contentInstance> resource Other filter conditions can be applied. For example, a value such as offset can be applied from the most recent <contentInstance> resource to multiple resources and returned.

In this case, a conventional Result Content value may be used to indicate that multiple resources are acquired. Since the <latest>, <oldest> and the <contentInstance> resource actually returned are siblings rather than a parent/child relationship, the Result Content value may have the same value as "sibling-resources", not the conventional value.

2. How to apply to <container> resources

When <container> resources are used as targets for obtaining multiple resources, the Result Content parameter is used as a "child-resources" value. In this case, a value for indicating the resource sorting order can be included in the Filter Criteria condition and used.

4 is a new Filter Criteria condition for this, which may indicate an alignment condition. This indicates the sorting order between sibling resources, and may have values such as in order of creation time and in reverse order of generation time. This may be defined as a value related to a value to which an order can be applied, such as common attributes (creationTime, lastModifiedTime, stateTag) included in the resource.

Additionally, this condition may include level information to which the alignment is applied. For example, if this value is all_level, when the target <container> resource includes multiple <container> resources under the order, the result can be returned by applying an order to all <contentInstance> resources. In the case of one_level, sorting can be performed within the <contentInstance> resource group that each individual <container> resource in the tree has.

3. How to apply to <flexContainer> resources

The <flexContainer> parent resource has a <flexContainer> resource as a child resource, and actual data can be stored there. Also, when the <flexContainer> resource type is created as an actual resource instance, it is created as a separate specialization type rather than the <flexContainer> resource type. Therefore, it has the information indicating the actual type as containerDefinition property.

In order to apply the technique of applying the sort order between data, it is possible to indicate which specialization type has data among the child <flexcontainer> resources included in the parent <flexcontainer> resource. This may be added to the resourceType condition of the existing Filter Criteria or indicated as a separate specialization condition as shown in FIG. 5. The remaining order conditions are the same as the method applied to the <container> resource.

4. How to apply to <timeSeries> resources

Since the <timeSeries> resource is a sub-resource and cannot have the <timeSeries> resource, it is basically the same as the case targeting the <container> resource, but the order cannot be indicated.

Meanwhile, it goes without saying that the technical idea of the present invention can be applied to a computer-readable recording medium containing a computer program that performs functions of the apparatus and method according to the present embodiment. Further, the technical idea according to various embodiments of the present disclosure may be implemented in the form of a computer-readable code recorded on a computer-readable recording medium. The computer-readable recording medium can be any data storage device that can be read by a computer and can store data. For example, a computer-readable recording medium may be a ROM, RAM, CD-ROM, magnetic tape, floppy disk, optical disk, hard disk drive, or the like. Further, a computer-readable code or program stored in a computer-readable recording medium may be transmitted through a network connected between computers.

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

virtualResource
order
resourceType
specializationType

Claims (8)

Receiving, by the M2M platform, an acquisition request message;
A first verification step of confirming, by the M2M platform, whether the target resource indicated by the To parameter of the acquisition request message is a virtual resource;
And a first return step of returning a result by applying filter conditions included in the acquisition request message in the process of processing the virtual resource by the M2M platform when the target resource is identified as a virtual resource.
The method according to claim 1,
The first verification step,
When a condition of a name indicating a virtual resource is included in the acquisition request message, it is checked whether the target resource is a virtual resource.
The method according to claim 2,
The first return step is,
When the target resource is a <latest> resource, a method of obtaining a resource, comprising applying filter conditions to a plurality of sibling resources in the latest order and returning a result.
The method of claim 3,
The acquisition request message in the first verification step,
A resource acquisition method, characterized in that Result Content is set to a value indicating a sibling resource.
The method according to claim 1,
A second verification step of confirming, by the M2M platform, whether the target resource indicated by the To parameter of the acquisition request message is a <container>resource;
If the target resource is identified as a <container> resource, a second return step of returning a result by applying filter conditions included in the acquisition request message in the process of processing the <container> resource by the M2M platform; includes,
In the second return step, the filter conditions are,
A method of obtaining a resource, comprising: a sort order between sibling resources and level information for applying the sort.
The method of claim 5,
level information,
When the <container> resource includes multiple <container> resources, level information that applies the sort order to all <contentInstance> resources and within the <contentInstance> resource group that each individual <container> resource has on the tree A method of acquiring a resource, comprising level information to which a sort order is applied.
The method according to claim 1,
A third verification step of confirming, by the M2M platform, whether the target resource indicated by the To parameter of the acquisition request message is a <flexContainer>resource;
If the target resource is identified as a <flexContainer> resource, a third return step of returning a result by applying filter conditions included in the acquisition request message in the process of processing the <container> resource by the M2M platform; includes,
In the third return step, the filter conditions are:
including resourceType condition, specialization condition
Receiving, by the M2M platform, an acquisition request message;
A first verification step of confirming, by the M2M platform, whether the target resource indicated by the To parameter of the acquisition request message is a virtual resource;
If the target resource is identified as a virtual resource, a first return step of returning a result by applying filter conditions included in the acquisition request message in the process of processing the virtual resource by the M2M platform; a resource acquisition method comprising: A recording medium that can be read by a computer with a program that can be executed.

Images