KR102367738B1 - Group Member Validation Method and System for Virtual Resource - Google Patents

Abstract

A method for group member validation of a virtual resource is provided. The group validation method according to an embodiment of the present invention obtains parent resource type information of a resource designated by a group member ID included in a group creation request, and verifies the group validity using the acquired information on the parent resource. Thereby, it becomes possible to verify the validity of a virtual resource as a group member.

Description

Group Member Validation Method and System for Virtual Resource}

The present invention relates to Machine to Machine (M2M)/Internet of Things (IoT) technology, and more particularly, to a method of verifying the validity of a group member to be included in a group resource.

1 is a diagram provided for description of group resources. 1 shows a situation in which a resource "group1", which is a group resource, is created.

The "group1" resource contains the <fanOutPoint> resource. The <fanOutPoint> resource is a virtual resource that can be viewed as a kind of function only for function execution, without including types and properties, as well as any other information or data.

The <fanOutPoint> resource transfers the request of the Originator device to the "/CSE02/base1/res2" and "/CSE03/base1/res3" resources, which are members included in the "group1" resource, as shown in FIG. , collects the responses and delivers them to the Originator device.

2 is a diagram provided to explain a conventional method for verifying group member validity. In Fig. 2, it is assumed that the originator device designates "/CSE02/base1/res2" and "/CSE03/base1/res3" as member IDs while requesting creation of the "group1" resource, as the member type as "container". did

The group hosting CSE retrieves the resources of "/CSE02/base1/res2" and "/CSE03/base1/res3" to verify the validity of the members that the Originator device wants to include in the group and retrieves the resource type can figure out In addition, it is also possible to determine by partially retrieving only the resource type attribute rather than acquiring all of the resource.

As shown in FIG. 2 , the resource type of the identified group members will be “container”, which matches the member type “container” included in the group creation request, so the group validation is successful.

3 is a diagram provided to explain a problem in conventional group member validation. In FIG. 3 , it is assumed that the originator device designates the member type as “latest” and designates “/CSE02/base1/cnt/latest” as the member ID while requesting the creation of the “group1” resource.

The <latest> resource is a virtual resource that returns the last created <contentInstance> resource among the child resources of the parent <container> resource when a retrieve request is received.

Like the aforementioned <fanOutPoint> resource, the <latest> resource is also a virtual resource, so it does not retain information on its own type.

In addition, the <latest> resource refers to the last <contentInstance> resource created among the <contentInstance> resources that it has a sibling relationship with, so the group hosting CSE uses the "/CSE02/base1/cnt/latest" resource. The resource type to be checked by acquiring <latest> will be "contentInstance", which is the resource type of "inst9" that he is referencing, not the type of the <latest> resource.

Therefore, it is impossible to verify the validity of a virtual resource with conventional techniques as a group member.

The present invention has been devised to solve the above problems, and an object of the present invention is to provide a method for verifying the validity of a virtual resource as a group member.

According to an embodiment of the present invention for achieving the above object, a group validation method includes the steps of: checking a type attribute of a parent resource of a member to be included in a group; and determining validity as a member of the group based on the confirmation result.

In addition, the checking step may be performed when the member is a resource that does not have type information.

Also, the checking step may be performed when the member is a virtual resource.

In addition, the virtual resource may be addressed by adding the resource name of the virtual resource to the resource ID of the parent resource.

Also, the resource name of the virtual resource may be predetermined.

In addition, the parent resource of the virtual resource may be limited to a predetermined resource.

In addition, the virtual resource is the latest resource that applies the most recent resource among existing resources to the request when there is a request, and the oldest resource that applies the oldest resource among the existing resources to the request when there is a request. It may include at least one of the resources.

In addition, the checking step may further include a first checking step of checking whether the parent resource is a type capable of using the virtual resource as a child.

In addition, the checking step may further include a second checking step of checking whether the type of the virtual resource matches the member type of the group.

And, according to an embodiment of the present invention, the group validation method includes, if a member to be included in a group is a normal resource, determining the validity as a member of the group by checking the type attribute of the normal resource; may include more.

In addition, the confirmation step may be performed in the group creation procedure.

And, the confirmation step may be performed in the group update procedure.

On the other hand, the electronic device according to another embodiment of the present invention, the processor for checking the type attribute of a parent resource of a member to be included in a group, and determining validity as a member of the group based on the check result; and a storage unit providing a storage space required for the processor.

And, the processor may be performed when the member is a virtual resource.

In addition, when it is determined that the parent resource is a type that can have the virtual resource as a child, the processor may determine validity by checking whether the virtual resource type matches the group member type.

As described above, according to embodiments of the present invention, it is possible to verify the validity of a virtual resource as a group member. Therefore, virtual resources can be grouped and used based on virtual resource validation that is not currently supported.

1 is a diagram provided for the description of a virtual resource;
2 is a view provided for the description of a conventional group member validation method;
3 is another view provided for the description of a conventional method for determining group member validity;
4 is a diagram provided for explanation of a group member validation method according to an embodiment of the present invention;
5 is a flowchart provided for the description of a group member validation method according to an embodiment of the present invention;
6 is a view showing an M2M / IoT system to which the present invention is applicable;
FIG. 7 is an internal block diagram of the electronic devices shown in FIG. 6 .

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

4 is a diagram provided to explain a group member validation method according to an embodiment of the present invention.

In the group member validation method according to an embodiment of the present invention, when a virtual resource is to be included as a group member, a technique for verifying the validity of the virtual resource is presented.

In FIG. 4, while the Originator device requests creation of a resource "group1", the member type is designated as "latest", and the address of the virtual resource is "/CSE02/ base1/cnt/latest" was assumed.

The group hosting CSE can guess from the member ID list whether the member that the Originator device wants to include in the group is a virtual resource or a general resource. The member ID list consists of IDs of member resources. In the case of a virtual resource, the resource ID (or resource address) is defined by adding the virtual resource name with "/" after the ID of the parent resource.

Unlike general resources, the procedure to create an instance is not defined for virtual resources, so resource names cannot be given separately by device and application requests, and the predefined virtual resource type name is used as the virtual resource name. . Therefore, the virtual resource name and the virtual resource type (name) used in the embodiment of the present invention can be regarded as the same. Since this virtual resource is automatically created virtually when the parent resource is created, a general child resource with the same name as the virtual resource's name (or virtual resource type name) cannot be created in the parent resource of this resource.

In the above example, the member type of the group resource is <latest>, and the first member ID ends with "latest". Therefore, the group hosting CSE determines whether this member "/CSE02/base1/cnt/latest" resource that the Originator device wants to include in the group is an actual <latest> type virtual resource or a resource instance of another type named "latest". should check

In the case of a general resource, the type information of the resource can be directly checked through the resourceType property value of the resource, but the type information cannot be directly checked because the virtual resource does not have any property value. For example, in the above example, when the group hosting CSE obtains information to confirm the type of resource "/CSE02/base1/cnt/latest", the assumption that it is an actual <latest> type resource is assumed to be any < Since contentInstance> resource is returned, it can be misjudged as <contentInstance> resource type.

Accordingly, in the embodiment of the present invention, a specific virtual resource is automatically created as a resource of a specific general resource, and the name of the virtual resource and the type information of the parent resource are used using the relationship that the name is predefined as the resource type name. Confirm the type information of the virtual resource by checking together.

Therefore, in the situation shown in FIG. 4, since the resource "/CSE02/base1/cnt/latest" is indicated as "latest", the resource "/CSE02/base1/cnt", which is the parent resource of "latest", is of type <container>. If you check that it is a resource, you can confirm that "/CSE02/base1/cnt/latest" is a resource of the actual <latest> type. This is because the <container> resource (represented as "cnt" resource in FIG. 4) always has a child virtual resource named "latest" when it is instantiated.

An additional reason to check the type of the parent resource when checking the type information of the virtual resource is that, for example, a resource named "latest" can be created even if it is not a <container> type resource. For example, when a <CSEBase> resource has a resource of type <AE> as a child, it can use the name "latest".

Therefore, when the name of a virtual resource (or virtual resource type name) is included as a member ID, the group hosting CSE verifies whether the parent resource is a type that can have virtual resources as children by checking the parent resource type of the corresponding resource. If verification is successful, the group hosting CSE confirms that the resource indicated by the member ID is a virtual resource of the type indicated by the corresponding name. Also, by verifying that the resource type of the corresponding member is the same as the member type (memberType attribute) included in the group creation request, the validity of the group resource including the virtual resource member is verified.

As an alternative to the type verification method for the virtual resource described above, for example, when <contentInstance> is indicated for the group member type and type information of the resource indicated by the member ID is obtained like a conventional general resource, and this is a <latest> type You can think of a way to check it by recognizing it as a <contentInstance> type. However, for example, in the case of a group in which one member has a <latest> resource and another member has an <oldest> resource, both of them turn out to be <contentInstance> types, so the group hosting CSE cannot differentiate between the two types in validation. is left In the case of a specific application, depending on the service, the oldest information and the latest information may be required at the same time, so this alternative that cannot distinguish these two resource types cannot be applied.

Another alternative is to create a group of <container> resources, which are parent resources, instead of creating a group of child resources such as <latest>. For example, if member 1 is “cnt1/latest” and member 2 is “cnt2/latest”, configure “cnt1” and “cnt2” instead of “latest” as a group, and then add “cnt1” and “cnt2” to each <latest> virtual resource at once. To access, Originator sends the address of the child resource common to each member to the address performing fan-out, such as "/CSE02/grp2/fanOutPoint/latest", and the group hosting CSE sends "cnt1/latest", "cnt2 /latest" forwards the request to each. However, in this method, as in the example above, "/latest", which is the address after "fanOutPoint" of the original request message, is appended after the member resource addresses of "cnt1" and "cnt2", so all member resources have the same name (the same for virtual resources). resource type), which can be applied very limitedly. In other words, when using virtual or general resources other than <latest> in a group, it cannot be verified.

5 is a flowchart provided to explain a group member validation method according to an embodiment of the present invention.

As shown in FIG. 5 , first, the group hosting CSE acquires a group member ID included in the group creation request received from the originator device (S110).

If the group member ID (address) obtained in step S110 includes the virtual resource type name at the end (S120-Yes), the group hosting CSE obtains type information of the parent resource of the resource designated as a group member (S140) .

If the parent resource type identified in step S140 is verified as a type that can include the virtual resource identified in step S120 (S150-Yes), the group hosting CSE determines that the group member type included in the group creation request received from the originator device is S120 By checking whether the virtual resource type identified in the step matches, the group member validity is verified (S170).

Step S150 corresponds to a procedure of checking whether the parent resource identified in step S140 is of a type that can use the virtual resource identified in step S120 as a child. This is because the parent resource type of the virtual resource is limited to a predetermined specific resource type.

And, step S170 corresponds to a procedure of checking whether the virtual resource type identified in step S120 matches the group member type recorded in the group creation request.

If it is confirmed that the group member type does not match the virtual resource type (S170-No), group validation fails (S160). In addition, even when it is confirmed that the parent resource type identified in step S140 cannot include the virtual resource identified in step S120 (S150-No), group validation fails (S160).

On the other hand, when the group member ID obtained in step S110 does not include the virtual resource type name, that is, when all group members are normal resources (S120-No), the group hosting CSE is directly from the group member resource. The type information of the specified resource is acquired (S130), and the group member validity is verified by checking whether the group member type included in the group creation request received from the originator device matches the type identified in step S130 (S170).

Validation of general resources is a virtual resource that uses the type property of the parent resource for validation, in that it verifies the validity as a member of the group by checking the type property of the resource designated as a group member rather than the type property of the parent resource. is different from

If group member validation does not fail, steps S110 to S190 are repeated until performed for all group member IDs included in the group creation request (S180), and when group member validation is successful for all group member IDs ( S180-No), the group validation is successful (S190).

On the other hand, if the group member validation fails for even one group member ID, the group validation fails ( S160 ).

Up to now, a preferred embodiment has been described in detail for a method for validating group members of a virtual resource.

The <latest> resource mentioned in the above embodiment is the most recent <contentInstance> resource among the <contentInstance> resources that exist in a sibling relationship with itself as a child resource of the parent <container> resource upon request. As a resource indicating the function to apply to the request, it is mentioned as one of the virtual resources, which is a kind of resource that does not hold the type information of the resource. Another kind of virtual resource that does not have type information, such as the oldest <contentInstance> resource among <contentInstance> resources that exist as a sibling relationship with itself as a child resource of the parent <container> resource upon request. The technical idea of the present invention may also be applied to the <oldest> resource, other <fanOutPoint> resources, <semanticFanOutPoint> resources, <pollingChannelURI> resources, <notificationTargetSelfReference> resources, etc. that apply to the request.

Furthermore, if it is a resource that performs the same function as a virtual resource but does not have type information even if it is not a virtual resource or other resource called by a different name, the technical idea of the present invention can be applied to any type of resource. is of course

That is, in verifying validity as a member of a member to be included in a group, the technical idea of the present invention is applicable to a method of referring to the type attribute of its parent resource rather than a member.

In the above embodiment, the virtual resource validation process used when creating a <group> resource may be equally used even when a member ID list is changed when updating a <group> resource.

In addition, in the above embodiment, a structured resource ID (hierarchical address) is referred to as a resource ID and a group member ID, but it is merely exemplary. The technical idea of the present invention can also be applied to a case where the resource ID is designated/used as an unstructured resource ID (non-hierarchical address).

In addition, in the above embodiment, a structured resource ID (hierarchical resource ID) is referred to as a resource ID and group member ID, which is a connection of resource names in the resource tree from the parent to the corresponding resource by "/". It is merely exemplary. As another example, it is equally applicable to a case where Unstructured resource ID (non-hierarchical resource ID) and resource name(s) are mixed. In the case of "/CSE02/base1/cnt/latest" resource ID in the above example, if the non-hierarchical resource ID named "cnt" is "res123", the same resource can be represented as "res123/latest", in this case If the contents of the invention are applied, it will be carried out as a procedure to obtain a "res123" resource and check whether this resource is a <container> type.

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

The number of electronic devices shown in FIG. 6 , that is, the number of servers 200 - 1 constituting the M2M/IoT system is exemplary, and thus, the technical idea of the present invention may be applied to a different implementation.

Furthermore, it goes without saying that the connection structure of the electronic devices shown in FIG. 6 may also be replaced in other ways if necessary.

All electronic devices shown in FIG. 6 may create and update a resource group. That is, the server 200-1, the gateways 200-21, 200-22, and the devices 200-31, 200-32, 200-33, and 200-34 can all create/update a resource group. And, in this process, they also perform group member validation according to the flowchart shown in FIG. 5 .

FIG. 7 is an internal block diagram of the electronic devices shown in FIG. 6 . The components necessary for implementing an embodiment of the present invention are the server 200-1, the gateways 200-21, 200-22, and the devices 200-31, 200-32, 200-33, and 200-34. common Accordingly, in FIG. 7 , these are collectively referred to as “200”, and hereinafter will be collectively referred to as an electronic device.

As shown in FIG. 7 , electronic devices according to another embodiment of the present invention include a communication unit 210 , a processor 220 , a storage unit 230 , and a function block 240 .

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

The processor 220 includes at least one application entity (AE) and a common service entity (CSE). Depending on the type and function of the electronic device, AE may not be included.

The CSE of the processor 220 may create/update the resource group, and in this process, member validation is performed according to the algorithm shown in FIG. 5 .

The storage unit 230 provides a storage space necessary for the processor 220 to operate, for example, create/update a resource group, and verify member validity in this process.

The function block 240 performs an original function of the electronic device. For example, when the electronic device is the device 200-31 , 200-32 , 200-33 , and 200-34 , a sensor and/or an actuator corresponds to this function block 240 .

On the other hand, 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 for performing the functions of the apparatus and method according to the present embodiment. In addition, the technical ideas according to various embodiments of the present invention may be implemented in the form of computer-readable codes recorded on a computer-readable recording medium. The computer-readable recording medium may be any data storage device readable by the computer and capable of storing data. For example, the computer-readable recording medium may be a ROM, RAM, CD-ROM, magnetic tape, floppy disk, optical disk, 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 computers.

In addition, although 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 as 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 perspective of the present invention.

200-1 : Server
200-21, 200-22: Gateway
200-31, 200-32, 200-33, 200-34: device

Claims (8)

a first determination step of determining, by the electronic device, whether a member's type attribute matches a member type attribute of the group, if the member to be included in the group is a general resource to determine validity as a member of the group; and
If the member to be included in the group is a virtual resource, the electronic device checks whether the member's parent resource is a type that can have a virtual resource as a child, instead of checking whether the member's type property matches the group's member type property, and checks the member's parent When a resource is identified as a type that can have a virtual resource as a child, the member's type property is determined as a virtual resource type, and then the member's type property is checked whether the member's type property matches the member type property of the group to determine the validity as a member of the group. 2 judgment step; including,
A member's parent resource is:
If a type cannot create a virtual resource as a child, it can have a general resource with the same name as the virtual resource as a child,
If it is a type that can create a virtual resource as a child, a group member validation method, characterized in that it cannot have a general resource with the same name as the virtual resource as a child.
The method according to claim 1,
virtual resources,
A group member validation method, characterized in that the address is addressed by adding the resource name of the virtual resource to the resource ID of the parent resource.
The method according to claim 1,
The resource name of the virtual resource is,
Group member validation method, characterized in that predetermined.
The method according to claim 1,
The parent resource of a virtual resource is:
A group member validation method, characterized in that it is limited to a predefined resource type.
The method according to claim 1,
virtual resources,
At least one of the latest resource that applies the latest resource among existing resources to the request when there is a request, and the oldest resource that applies the oldest resource among existing resources when there is a request. Group member validation method, characterized in that.
The method according to claim 1,
The first determination step and the second determination step are,
A group member validation method, characterized in that performed in the group creation procedure.
The method according to claim 1,
The first determination step and the second determination step are,
A group member validation method, characterized in that performed in the group update procedure.
If the member to be included in the group is a general resource, the validity of the member as a member is determined by checking whether the member's type property matches the group's member type property. If the member to be included in the group is a virtual resource, the member's type property is the Instead of checking whether the type property matches the type property, it checks whether the parent resource of the member is a type that can have a virtual resource as a child. a processor for determining validity as a member of the group by determining whether the type attribute of the member matches the member type attribute of the group after determining the type; and
It includes; a storage unit that provides a storage space required for the processor;
A member's parent resource is:
If a type cannot create a virtual resource as a child, it can have a general resource with the same name as the virtual resource as a child,
Electronic device, characterized in that, if the type can create a virtual resource as a child, it is impossible to have a general resource with the same name as the virtual resource as a child.

Images