KR101852727B1 - Cross-Resource Subscriptions Management Method - Google Patents

Abstract

A cross-resource subscription management method is provided. The cross-resource subscription management method according to an embodiment of the present invention includes allowing a subscription host to generate a first subscription resource in a first resource, to store the information of the first resource in a first target attribute, and to store the information of the first resource in a subscription resource attribute. Accordingly, when a subscription list is deleted by the host of the subscription resource, more specifically, even when a subscription list generated by a cross-resource subscription host is deleted, a target attribute can be managed uptodately. Thus, it is possible to provide a cross-resource subscription/notification service having no error.

Description

[0001] Cross-Resource Subscriptions Management Method [

The present invention relates to IoT (Internet of Things) / M2M (Machine to Machine) technology, and more particularly, to a method for managing resource subscription on an M2M platform.

The IoT / M2M service is generally implemented by a process of acquiring various data and performing a specific operation when the acquired data satisfies a predetermined condition at the same time.

The service application can perform subscriptions to efficiently retrieve the data. And, when the necessary data is various data provided from various resources, it is possible to perform a cross-resource subscription in which a plurality of resources are linked and subscribed.

Figure 1 is an illustration of a cross-resource subscription in the oneM2M standard. As shown in FIG. 1, a cross-resource subscription may be associated with a general resource and a subscription resource.

The property "regularResourceAsTarget" is an attribute that allows the cross-resource subscription host (hosting CSE) to create a new subscription resource (CSE2 / res2 / sub2) in a resource (CSE2 / res2) and the subscribed-to resource information (CSE2 / res2) is recorded as a target.

The attribute "subscriptionResourceAsTarget" is an attribute that allows a cross-resource subscription host to associate an already existing subscription resource (CSE3 / res3 / sub3), and resource information (CSE3 / res3 / sub3) is recorded as a target.

The "regularResourceAsTarget" attribute and the "subscriptionResourceAsTarget" attribute must always maintain a list of target resources up to date, because the cross-resource subscription host sends notifications to the application only if all of the data received from the resources satisfies the specified conditions do.

That is, if subscription resources are deleted, they must also be deleted in the target attributes of the cross-resource subscription host.

To this end, as shown in FIG. 2, when the cross-resource subscription host deletes the subscription resource including the attribute "associatedCrossResourceSub" which is the resource to which the subscription is subscribed, the host of the subscription resource inserts the subscription resource information into the DELETE request To the host's <subscriptionLinkDeletion> resource.

Thus, although the "subscriptionResourceAsTarget" attribute containing the subscription resource information can be updated, the "regularResourceAsTarget" attribute containing the subscription-to resource information in which the subscription resource is created can not be updated.

To solve this problem, the host of the subscription resource that deleted the subscription resource associated with the "regularResourceAsTarget" attribute puts "/ CSE2 / res2", which is information of the subscribed-to resource, not the subscription resource in the DELETE request, And the like.

However, because the subscription resource does not know which attribute is associated with the "regularResourceAsTarget" attribute and the "subscriptionResourceAsTarget" attribute, unless the host of the subscription resource has the RETRIEVE permission to the <crossSubscriptionResource> resource, Is practically impossible.

It is an object of the present invention to provide a cross-resource subscription capable of completely managing a target attribute in the latest when there is a deletion of a subscription list by a host of a subscription resource. Management method.

According to an aspect of the present invention, there is provided a method of managing a resource subscription, the method comprising: generating a first subscription resource in a first resource; A first storage step of the subscription host storing information of the first resource in a first target attribute; And a second storing step in which the subscription host stores the information of the first subscription resource in the subscription resource attribute.

In the second storing step, the subscription host may store the information of the first subscription resource in the subscription resource attribute together with the information of the first resource.

According to another aspect of the present invention, there is provided a method of managing a resource subscription, comprising: generating a second subscription resource on a second resource; And the subscription host storing the information of the second subscription resource in the second target attribute.

The second resource is a resource not created by the subscription host, and the information of the second subscription resource may not be stored in the subscription resource attribute.

Also, a method of managing a resource subscription according to an exemplary embodiment of the present invention includes: checking whether a subscription resource matches a resource attribute when the subscription host is notified of deletion of the subscription resource; And deleting, from the first target attribute, information of the created resource if the subscription resource is matched with the subscription resource.

The method of managing a resource subscription according to an exemplary embodiment of the present invention may further include deleting a subscription resource from a resource attribute if there is a matching subscription resource.

The method of managing a resource subscription according to an exemplary embodiment of the present invention may further include requesting deletion of subscription resources stored in the subscription resource attribute when the subscription host deletes the resource subscription resource.

According to another aspect of the present invention, there is provided a computer-readable recording medium including: a subscription host generating a first subscription resource on a first resource; A first storage step of the subscription host storing information of the first resource in a first target attribute; And a second storing step of storing information of the first subscription resource in the subscription resource attribute, and a second storing step of storing the information of the first subscription resource in the subscription resource attribute.

As described above, according to the embodiments of the present invention, when there is a deletion of the subscription list by the host of the subscription resource, more specifically, even when the subscription list generated by the cross-resource subscription host is deleted, Attributes can be managed up to date, and error-free cross-resource subscription / notification services become possible.

1 is a diagram for explaining a cross-resource subscription in the oneM2M standard,
FIG. 2 is a diagram for explaining a problem of cross-resource subscription management in the oneM2M standard; FIG.
3 is a diagram provided in the conceptual description of a cross-resource subscription / notification in an M2M platform,
FIG. 4 illustrates a resource structure of oneM2M platform for cross-resource subscription management according to an embodiment of the present invention; FIG.
FIG. 5 illustrates a process of deleting a subscription resource under cross-resource subscription management according to an embodiment of the present invention; FIG.
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.

Figure 3 is a diagram provided in the conceptual description of cross-resource subscription / notification in the M2M platform. Cross-resource subscriptions / notifications are a way in which a single notification occurs when all of the resources to which it subscribes meet specified conditions.

That is, the manner in which one notification message is received for multiple events, rather than the manner in which notification messages are received separately for individual events. In Fig. 3, notification is made to the user application when the window satisfies all three conditions: "open", the blind is "open", and the temperature is "34 ° C".

The user application running on the user terminal is not interested in whether the individual data individually met the condition, but is concerned that all of the data are interested in each of the conditions.

In the embodiment of the present invention, a cross-resource subscription management method is presented in oneM2M platform. Specifically, even if a <subscription> resource created in a subscribed-to resource is deleted, it is possible to delete it from the target of the "regularResourceAsTarget" attribute of the cross-resource subscription host.

4 is a diagram illustrating a resource structure of oneM2M platform for cross-resource subscription management according to an embodiment of the present invention.

As shown in FIG. 4, for the cross-resource subscription management according to an embodiment of the present invention, the "regularResourceSubscription" attribute is added to the cross-resource subscription resource of the cross-resource subscription host.

When the cross-resource subscription host newly creates the subscription resource (CSE2 / res2 / sub2), as shown in FIG. 4, the "regularResourceAsTarget" attribute stores information "subscribed- / res2 ", and the" regularResourceSubscription "property stores the information" CSE2 / res2 / sub2 "of the subscription resource.

At this time, the "regularResourceSubscription" attribute can further store the information of the subscribed-to resource in addition to the information of the subscription resource. Furthermore, it is possible to store more names of subscription resources in the "regularResourceSubscription" attribute or to store only the names instead of addresses of subscription resources.

The "regularResourceSubscription" attribute is used to delete the associated subscription resource (/ CSE2 / res2 / sub2 in FIG. 4) when the cross-resource subscription host deletes the cross-resource subscription resource. Furthermore, the "regularResourceSubscription" attribute can be utilized to allow an application to manage subscription resources separately.

FIG. 5 illustrates a process of deleting a subscription resource under cross-resource subscription management according to an exemplary embodiment of the present invention.

As shown in FIG. 5, when a cross-resource subscription host deletes a subscription resource including a "associatedCrossResourceSub" attribute, which is a resource to which a subscription resource is subscribed, the host of the subscription resource records its subscription resource information to be deleted in a DELETE request To the host's <subscriptionLinkDeletion> resource.

The cross-resource subscription host then deletes the subscription resource information contained in the DELETE request received in the <subscriptionLinkDeletion> resource from the "subscriptionResourceAsTarget" attribute and deletes it. When the subscription resource "CSE3 / res3 / sub3" is deleted, this process is performed.

In addition, when the subscription resource information matching the subscription resource information included in the DELETE request received in the <subscriptionLinkDeletion> resource is retrieved from the "regularResourceSubscription" property, the cross-resource subscription host stores the subscribed-to resource information of the retrieved subscription resource as "regularResourceAsTarget "Attribute.

When the subscription resource "CSE2 / res2 / sub2" is deleted, this process is performed and "CSE2 / res2" is deleted from the "regularResourceAsTarget" attribute. In addition, the cross-resource subscription host can delete "CSE2 / res2 / sub2" from the "regularResourceSubscription" attribute.

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 perform the functions of the CSE as the M2M platform. In other words, the server 100-1, the gateways 100-21 and 100-22, and the devices 100-31, 100-32, 100-33, and 100-34 all share the cross- Management can be performed.

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.

Resource subscription management of the processor 120, and the storage unit 130 provides a storage space necessary for the processor 120 to perform the cross-resource subscription management.

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. [

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.

"regularResourceAsTarget" property
"regularResourceSubscription" property
"subscriptionResourceAsTarget" property
"associatedCrossResourceSub" Property
<subscriptionLinkDeletion> Resources

Claims (8)

The subscription host creating a first subscription resource on the first resource;
A first storage step of the subscription host storing information of the first resource in a first target attribute;
A second storage step of the subscription host storing information of the first subscription resource in the subscription resource attribute;
And a third storing step of storing, in the second target attribute, the information of the second subscription resource generated in the second resource by the subscription host,
The second subscription resource,
This resource is not created by the subscription host,
The information of the second subscription resource,
And is not stored in a subscription resource attribute.
The method according to claim 1,
In the second storing step,
Wherein the subscription host stores the information of the first subscription resource in the subscription resource attribute together with the information of the first resource.
delete delete The method according to claim 1,
If the subscription host is notified of the deletion of the subscription resource, checking whether there is a subscription resource matching the subscription resource attribute; And
And deleting, from the first target attribute, the information of the resource in which the subscription resource is created if there is a matching subscription resource.
The method of claim 5,
And if there is a matching subscription resource, deleting the subscription resource from the subscription resource property.
The method according to claim 1,
Further comprising: when the subscription host deletes the subscription resource, requesting deletion of the subscription resource stored in the subscription resource attribute.
The subscription host creating a first subscription resource on the first resource;
A first storage step of the subscription host storing information of the first resource in a first target attribute;
A second storage step of the subscription host storing information of the first subscription resource in the subscription resource attribute;
And a third storing step of storing, in the second target attribute, the information of the second subscription resource generated in the second resource by the subscription host,
The second subscription resource,
This resource is not created by the subscription host,
The information of the second subscription resource,
Wherein the program is capable of performing a resource subscription management method characterized in that the program is not stored in a subscription resource attribute.

Images