KR20140099654A - A method for managing information of M2M system and apparatus therefor - Google Patents

Abstract

Provided are a method for managing M2M information and an apparatus therefor. The method comprises: recording data as a resource according to an M2M resource structure; and storing a last access time attribute indicating the time that the resource to save the data is ultimately loaded.

Description

[0001] The present invention relates to a method and apparatus for managing M2M information,

The present invention relates to a method and apparatus for managing information on M2M data in an M2M (Machine to Machine Communication) network.

"Machine-to-machine communication" or M2M, "Machine type communication" or "Smart Device communication" or "Machine oriented communication") means that all communication methods Refers to a communication method.

The European Telecommunications Standards Institute (ETSI) has announced the ETSI TS 102 690 V1.1.1 (hereinafter "structure") functional structure for providing M2M communication in October 2011.

The M2M platform (server) stores the data when the data is transmitted from the device, the gateway or the device connected to the gateway by using the container resource defined according to the structure of the existing ETSI M2M standard.

In addition, when this data is stored, various pieces of information related to the data are also stored. The M2M service provider manages the data through this information.

The present invention provides a method and apparatus for generating and managing information on M2M data.

According to an embodiment of the present invention, there is provided a method of managing data, comprising: recording data as resources according to an M2M resource structure; And storing a lastAccessTime attribute indicating a time at which the resource storing the data is finally read.

In the method, the final reference time attribute may be updated if the resource is successfully transmitted according to a retrieve or notify request.

In addition, the final reference time attribute may be stored as a common attribute or an individual attribute of each of the resources.

The resource can be searched through the final reference time attribute using a reference (ifAccessedSince) item as a filter criterion, which is used as a condition for searching for a resource referenced after a specified point in time.

Also, the resource can be searched through the final reference time attribute using a specific point in time, which is a condition for searching for an unreferenced resource after a designated time, as a filterCriteria.

Meanwhile, the M2M device according to the present invention records data as a resource according to the M2M resource structure and stores a lastAccessTime attribute indicating a time when the resource storing the data is finally read.

According to the present invention, more information is provided to manage data in the M2M system, and data can be more efficiently managed.

It can also provide flexibility in terms of M2M system management by providing more information about the resource to the M2M system and utilizing it as a means of verifying the value of the resource.

1 is a diagram illustrating a configuration of an M2M system according to an embodiment of the present invention.
2 is a diagram for explaining an information update procedure according to an embodiment of the present invention.
3 is a diagram for explaining an information update procedure according to another embodiment of the present invention.
4 is a diagram for explaining an application example of embodiments of the present invention.
5 is a view for explaining another application example of the embodiments of the present invention.
6 is a view for explaining another application example of the embodiments of the present invention.
7 is a view for explaining another application example of the embodiments of the present invention.
8 is a view for explaining a structure of an M2M device to which embodiments of the present invention are applied.

Hereinafter, some embodiments of the present invention will be described in detail with reference to exemplary drawings. It should be noted that, in adding reference numerals to the constituent elements of the drawings, the same constituent elements are denoted by the same reference symbols as possible even if they are shown in different drawings. In the following description 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.

In describing the components of the present invention, terms such as first, second, A, B, (a), and (b) may be used. These terms are intended to distinguish the constituent elements from other constituent elements, and the terms do not limit the nature, order or order of the constituent elements. When a component is described as being "connected", "coupled", or "connected" to another component, the component may be directly connected or connected to the other component, Quot; may be "connected," "coupled," or "connected. &Quot;

Embodiments of the present invention will be described with reference to object communication. Object communication is variously divided into machine-to-machine communication (M2M), Machine Type Communication (MTC), Internet of Things (IOT), Smart Device Communication (SDC), and Machine Oriented Communication And will be described in the following description with reference to M2M. However, this description is not limited to M2M, but is applicable to all systems and structures providing inter-device communication, i.e., object communication, and communication occurring in these systems.

In addition, such object communication can be applied to various fields including Smart Meter, e-Health, Connected Consumer, City Automation, and Automotive Application .

An M2M object or device herein may be an M2M device (e.g., an M2M standard device (D), an M2M non-standard device (d) or an M2M partial standard device (D ' G) or an M2M network server.

1 is a diagram illustrating an example of an M2M service architecture to which the present invention is applied.

Referring to FIG. 1, an M2M service structure of an M2M standard structure includes, for example, a case 1, a case 2, a legacy case 1, a legacy case 2, a legacy case 3, (Legacy case 3) and the like can be considered.

The M2M service architecture consists of the M2M device domain and the network / application domain or M2M server platform to provide the object intelligence communication service.

The network / application domain includes M2M applications, M2M applications, Core Network, and M2M SC, which access or provide service logic to M2M Service Capabilities (M2M Service Capabilities).

On the other hand, an M2M device domain includes an M2M device or an M2M gateway. M2M devices and M2M gateways also include M2M applications, and may further include M2M SC.

If the M2M device includes an M2M SC, it may interwork and interconnection in the network / application domain via the included M2M SC.

In addition, if the M2M device does not include the M2M SC, it can interworking and interconnection in the network / application domain through the interface with the M2M SC included in the M2M gateway.

The M2M device can operate the M2M application to interoperate and interconnection in the network / application domain through the M2M service capability (Service Capabilities: SC) of the M2M device or the M2M gateway to utilize the functions of the network domain.

The SC may include one or more of xAE, xGC, xRAR, xCS, xREM, xSEC, xHDR, xTM, xTM, xIP, xCB or xTOE, where x is N for a network, G for a gateway, D can be. That is, xIP can be NIP, GIP, or DIP. The xSEC described below is a security capability, which may be NSEC, GSEC or DSEC.

The Service Capability Layer (SCL) of the M2M device or the M2M gateway forms a specific interface with the Service Capability Layer (SCL) of the network domain to inter-operate and inter-operate.

In addition, the SCs in the network domain can interface with one or more core networks. In this case, the functions of the core network can be utilized through known interfaces according to other existing standards.

To this end, reference points of mIa, mId, and dIa are defined as the interface between the network domain and the device and gateway domains according to the M2M standard structure.

mIa is a reference point used in the network domain, and is an interface standard between an NSCL (M2M Service Capability Layer in the network), which is a service capability layer provided by the M2M platform, and a Network Application (NA), which is a network application.

mId is the interface specification between the NSCL of the network domain and the device / gateway service capability layer D / G SCL (DSCL or GSCL) of the device / gateway domain. In other words, mId is an interface standard applied between the NSCL of the network domain provided by the M2M platform and the DSCL (M2M Service Capabilities in the M2M Device), which is the service capability layer of the device, and the NSCL of the network and the GSCL M2M Gateway).

dIa is a reference point used in the M2M device / gateway domain. It is an interface between a device service capability layer (DSCL) and a device application (DA) provided by the M2M device, a gateway service capability layer (GSCL ), A gateway application (GA) interface, and an interface specification of GSCL and DA provided by the M2M gateway.

Case 1 shows an M2M device (D) 110 including an M2M service capability (SC) 113 and an M2M application 111. The M2M device (D) 210 may interface with the NSCL of the network domain 190 using the mId reference point.

Case 2 shows an M2M device (D ') 130 including the M2M application 131 but containing the M2M SC. The M2M device (D ') 130 may rely on the M2M SC (173) of the M2M gateway (G) 170 using the dIa reference point instead of the M2M SC.

Legacy cases 1 to 3 (Legacy cases 1 to 3) correspond to a case where the device is a legacy device (d) 150, which is a nonstandard standard device that does not include the M2M service as well as the M2M service capability. In this case, the legacy device d may interworking and interconnection in the network domain 190 via Interworking Proxy capability (xIP), which is an embodiment of the SC.

Where x may be N for a network, G for a gateway, or D for a device. That is, xIP can be NIP, GIP, DIP.

The xIP can discover the structure of the M2M area network and create an M2M resource structure representing the M2M area network structure in the SCL. When the M2M area network structure changes, the M2M resource structure can be managed to reflect this.

Legacy case 1 may allow non-standard device (d) 150 to interwork and interconnection in network domain 290 through the NIP of the network domain.

Also, legacy case 2 may allow interoperable and interconnection of non-standard device (d) 150 in network domain 190 via the GIP of M2M gateway.

Legacy case 3 may also interworking and interconnection the non-standard device (d) 150 in the network domain 190 via the DIP of the M2M device (D).

According to the ETSI M2M standard, data generated by an M2M device such as various sensors is stored in a form of a resource in a form of a tree in a RESTful structure, (resources) can be managed by methods defined according to the M2M standard.

ETSI M2M technology defines CRUD (Create, Retrieve, Update, Delete) as a method for resource management. In other words, the Create method is used to create the resource, and the Retrieve method is used to read the contents of the resource. In addition, the Update method is used to update the contents of the resource, and the Delete method is used to delete the resource. In addition to these four methods, notify and execute methods are further defined.

A resource can have one or more attributes, which are meta-data about the data stored in the resource, which actually represent information about the content of the resource. Among the attributes of the resource, there are the attributes having the time information at the time when the resource is created or modified.

For each of the above-described methods, an associated property value called creation time is defined in the case of Create and an attribute value called lastModifiedTime is defined in case of Update. In other words, the resource creation time and the last modified time information can be known.

Therefore, we define a property value related to the retrieval (Retrieve) to provide a method of managing the time information of the resource last read. That is, the attribute of the last reference time (lastAccessTime) can be introduced as a common attribute used for resource management in the M2M system. Alternatively, it is possible to introduce an attribute of the last reference time (lastAccessTime) in addition to common attributes for resource management, if necessary for each resource.

To this end, the attribute 'lastAccessTime' may be additionally defined in '9.2.2 Common attributes' of 'ETSI TS 102 690 M2M Functional Architecture' to provide information on the final time of reading the resource. In this specification, the attribute of the last reference time (lastAccessTime) is defined as the last time information to which the resource is referenced, but the name is not limited to this, and other names such as the last read time may be used.

Meanwhile, the attribute value of the finally defined reference time (lastAccessTime) defined according to the present invention must be updated each time the resource is referred to. Therefore, in order to prevent overhead of the system, for example, the attribute value may be defined as an optional attribute value instead of a mandatory attribute depending on the nature of the resource or the application used.

According to the M2M architecture, attributes can also be read / write (RW), which can be read / written by the client, read-only (RO) written by the server and read only by the client, (Write-Once).

Therefore, the type of the last reference time (lastAccessTime) (or lastReadTime), which is the last time information referred to in the above-described resource, can be defined as RO. Accordingly, the content of the resource can be defined through a retrieve method or a notify method, Can be made to update the value of the last reference time (lastAccessTime) attribute on the server side, not on the client. That is, the issuer of the method can not arbitrarily change the value of the lastAccessTime attribute.

In the case of the lastAccessTime attribute, the resource attribute must define its own data type. In the case of the lastAccessTime attribute, the format of the basic data type defined by the M2M standard, "DateTime" (for example, "2012-11-15T17: 00: 00.000 + 09: 00 ").

Table 1 below shows common attribute values for M2M resources.

Name Description accessRightID An attribute value that contains a resource URI that contains access rights information for the resource, used to determine if it has the necessary access rights to perform a specific operation (retrieve, update, delete, etc.).
URI of an access rights resource. The permissions are defined in the accessRight resource that is referenced by who is allowed to access the resource containing this attribute for a specific purpose (retrieve, update, delete etc.).
(Omitted below) ...
(Middle omitted)
... filterCriteria It is used as a basis for filtering results and can be used at GET or resource subscription.
This is the criteria that filter the results. They can be used in a GET (as query parameters) or in a subscribe. lastModifiedTime Time when the resource was last modified
Last modification time of a resource. Link Within the <scl> resource, this attribute value is the URI of the <sclBase> resource of the registered SCL. This value is the URI of the resource that requested the disclosure to the outside.
URI of the related remote resource. In an announced resource, this is the URI of the announcing resource. In an < scl > resource, this is the URI of the < sclBase > resource of the registered SCL. searchStrings Character information used when searching for resources
Tokens used as keys for discovering resources. lastAccessTime The time when the resource was last referenced
Last accessed time of a resource

0000-00-00T00: 00: 00.000 + 00: 00 "may be assigned to the last reference time attribute (lastAccessTime) at the time of creation of the resource to indicate that it has not been referred to at all. The update of the lastAccessTime attribute value can be updated only when the retrieve method or the notify method is successfully performed.

2 is a diagram for explaining an information update procedure according to an embodiment of the present invention.

The above-described lastAccessTime attribute value may be updated in response to a Retrieve request for the resource.

According to the M2M technology, a hosting SCL 220 means an SCL in which a resource to be a target of various methods such as a retrieve is actually stored, and an issuer 210 stores various methods (NA, DA, GA) or SCL as a requesting entity.

The requestor 210 transmits a retrieve message for the resource using the address of the specific resource to the hosting SCL 220 to request the read (S251).

Accordingly, the hosting SCL 220 receiving the retrieve request for the resource confirms whether the corresponding resource exists or not and determines whether or not the corresponding request is performed (S253) If the access to the resource is permitted and the resource is permitted, a response message of success is generated. Otherwise, a response message of failure is generated and a response message of failure or success is transmitted to the requester (S255).

If the last access time attribute exists in the resource and the successful request for the read request is issued to the issuer 210, the hosting SCL 220 determines that the last value Update the reference time (lastAccessTime). However, even if the value of the lastAccessTime property is changed, the last modification time (lastModifiedTime) is not changed. The lastModifiedTime attribute value must be changed by the update method rather than the retrieve method.

The M2M specification provides a method for partial addressing of resource specific attribute values. Therefore, the last reference time (lastAccessTime) should be updated even when only a specific attribute value is referred to in a partial accessing method. However, if only the lastAccessTime attribute value is referred to, the resource content is not considered to be referenced, so do not update it.

In addition, the M2M system provides a discovery function for resource discovery, which does not update the last reference time (lastAccessTime) since the discovery request is not a retrieve request for the resource.

3 is a view for explaining another embodiment of the present invention.

The M2M technology provides a mechanism to subscribe to the resource in order to receive notifications of changes in a particular resource, and the SCL that stores the subscribed resources in this manner is called a subscribed-to SCL (SCL).

The Notify method is a method used by the subscribed SCL 320, that is, the hosting SCL 320, to inform the subscriber 310 of the resource that the corresponding resource has been changed. Upon receiving the Notify method, the subscriber 310 may send a retrieve request to receive the contents of the changed resource. Therefore, in this case, the process of transmitting and receiving the notification message will be the same as the detection request step described above with reference to FIG.

Meanwhile, the hosting SCL 320 may send the contents of the changed resource in the notify request message, and in this case, when the notify method is successfully performed, that is, when the successful response to the notify method Update the value of the last reference time (lastAccessTime) attribute.

That is, referring to FIG. 3, when a change occurs in a resource, the hosting SCL 320 generates a notification request message including the changed resource content (S351) (notification message) to the subscriber 310 of the corresponding resource (S353). The subscriber 310 of the resource may be an M2M application or an SCL.

The subscriber 310 of the resource receiving the notification message transmits a response message including an appropriate response value to the hosting-SCL 320 (S355).

The hosting SCL 320 that has received the response message has the last access time attribute (lastAccessTime) for the resource informed to the subscriber, and if the code in the response message is "STATUS_OK", that is, if the notification message was successfully received, To update the lastAccessTime attribute value.

On the other hand, the M2M technology has an attribute called filterCriteria, and the filter criterion (filterCriteria) is used to search for the resource and to extract only the desired information from the resource. Additional definitions are needed to use the lastAccessTime attribute as an argument in the filter criteria (filterCriteria). Table 2 below defines the attributes of the filter criteria.

Name type Predefined values and examples Description ifModifiedSince DateTime [0..1] Criteria for filtering resources whose time the resource was last modified since this point in time
This is particularly useful for preventing initial notify from being created when creating a subscription resource.
A resource matches this criterion if and only if the lastModified attribute of the resource is chronologically after the specified value.
It is particularly useful to suppress the initial notify when used in a create subscription (see clause 10.25.2). ifUnmodifiedSince DateTime [0..1] The criteria for filtering resources that are older than this point in time when the resource was last modified.
A resource matches this criterion if and only if the lastModifiedAttribute of the resource is chronologically before the specified value. ?
(Middle omitted)
? createdafter DateTime [0..1] Criteria for filtering resources whose creation time is after a specified time
A resource matches this criterion if and only if the creationTime attribute of the resource is chronologically after the specified value. createdBefore DateTime [0..1] Criteria for filtering resources that are older than a specified point in time when resources are created
A resource matches this criterion if and only if the creationTime attribute of the resource is chronologically before the specified value. ifAccessedSince DateTime [0..1] Criteria for filtering resources whose last referenced time is beyond this point
A resource matches this criterion if and only if the lastAccessTime attribute of the resource is chronologically after the specified value. ifUnaccessedSince DateTime [0..1] Criteria for filtering resources that are older than this point in time when the resource was last referenced
A resource matches this criterion if and only if the lastAccessTime attribute of the resource is chronologically before the specified value

Refer to Table 2 to further define a new reference item (ifAccessedSince) and a postponed reference (ifUnaccessedSince) at a specific point in the filter criterion (filterCriteria) To provide a way to search The ifAccessedSince item can be used as a condition for retrieving a resource referenced after a specified point in time, and the ifUnaccessedSince item can be used as a search condition for searching for resources not referenced after a specified point in time.

Table 3 below shows a search example using the last reference time (lastAccessTime) as the filter condition (filterCriteria).

<filterCriteria>
<ifAccessedSince> 2012-11-10T12: 00: 00.000 + 09: 00 </ ifAccessedSince>

Referring to an example in which a search is performed based on a reference time of a resource in a filter criterion (filterCriteria) as shown in Table 3, ifAccessedSince and ifUnaccessedSince proposed in the present invention are used as a factor of a filter criterion (filterCriteria) When used, it is possible to search for resources referenced in a specific period (from 12:00 on November 10, 2012 to 12:00 on November 16, 2012) in the manner shown in Table 3.

Hereinafter, specific embodiments in which the lastAccessTime attribute value suggested in the present invention is utilized in the M2M system will be described.

4 is a diagram for explaining an application example of embodiments of the present invention.

It may provide a redelivery mechanism for a missing notification request message. According to the M2M system, a subscription-to-SCL (Subscription-to-SCL) creates a subscription resource in a sub-resource format for subscribers of a specific resource managed by the subscriber, and when a change of the resource occurs, A notification message may be provided.

However, if a subscriber, which is a subscriber to be a notification message transmission destination, is offline or a notification message can not be received by the subscriber due to other network problems, a notification may be missed to the subscriber. In this case, when the subscriber of the resource is brought back online, it is possible to transmit a notification request message that was dropped to the subscriber for the resources changed or newly created during the off-line state by using the lastAccessTime value.

In FIG. 4, the subscriber 410 is a subscriber who desires to be informed of changes to the resource A (A), the resource B (B), the resource C (C), and the resource D (D). In general, NA / DA / GA / SCL can assume the role of subscriber, but assume that SCL (service capability layer) is a subscriber.

The hosting SCL 420 is the SCL that hosts the subscribed resources.

The resource A (A) has changed after 10:00 hours in a state where the communication path between the hosting SCL (Hosting-SCL) 420 and the subscriber 410 is offline or the message can not be received for other reasons, However, the notification request message is not transmitted and is missed (S451).

When the communication path between the hosting SCL 420 and the subscriber 410 is restored, the hosting SCL 420 determines that the resource A (A) and the resource D (D) (lastModifiedTime) attribute value is greater than the lastAccessTime attribute value (S453).

Accordingly, the hosting SCL 420 may retransmit the missing notification request messages collectively (S455).

5 is a view for explaining another application example of the embodiments of the present invention.

The final reference time can be applied to the deletion policy of the content instance (contentInstance) resource.

Container resource <container> consists of attached resources such as attributes, subcontainers, contentInstances, and subscriptions.

A content resource, which is a sub-resource of a container resource, is a collection of content instances within a container. A content instance resource <contentInstance> which is a sub resource of a container resource is composed of an attribute and a content. The content of the content instance stores the actual data content, the attribute stores the metadata associated with the actual data stored in the content, and is used to exchange container instances at mId, mIa, and dIa.

Also, the container resource is supposed to delete the oldest content instance (contentInstance) by policies such as maxNrOfInstances and maxByteSize. Deleting the oldest content instance (contentInstance) is to avoid exceeding the limited size of the resource by deleting the content with the lowest information value. However, it can not be said that the oldest content instance has the lowest value as information, and in some cases it is the oldest, but if it is referred to recently, it is highly value as information.

That is, it can be judged that the resource having the oldest reference time point among the content instance resources has a low value as information. Therefore, we intend to introduce a policy that determines and deletes the value of content instance as information by using the last reference time (lastAccessTime).

Referring to FIG. 5, the DA 510 is an M2M device application that periodically generates data and stores it in a content instance (contentInstance) which is a sub-resource of the container resource of the DSCL 520. The NA 540 is an M2M network application that uses a content instance resource (contentInstance) which is data generated by the DA 510.

As shown in FIG. 5, after the generation (S551) of data 1 (Data1) (A), the interface mId between the DSCL 520 and the NSCL 530, which hosts data as a content instance resource, Data 1 (A) remain unreferenced and then the interface mId is restored and data 2 (Data2) (B) is generated (S553) ) (LastAccessTime) is updated.

Thereafter, when the DA 510 requests the DSCL 520 to create a resource of data 3 (Data 3) (S555), it is determined whether the maximum number of content instances does not exceed a predetermined value or the container resource management When a situation occurs in which one of the existing container instances Data 1 (Data 1) and Data 2 (Data 2) (B) must be deleted according to the policy, according to the policy of the conventional M2M standard, Data1) (A) will be deleted. However, in view of the NA 540 actually using the resource, the data 1 (Data 1) 1 (A), which has not been referred to yet but has been used more than the already used data 2 (Data 2) It may be advantageous to delete data 2 (Data 2) (B) rather than data 1 (Data 1) (A).

Therefore, in this case, it is possible to delete the data 2 (Data 2) (B) whose usage value is further decreased by using the last reference time (lastAccessTime).

6 is a view for explaining another application example of the embodiments of the present invention.

The unused resources can be retrieved and utilized by applying the embodiments of the present invention.

In the M2M network domain, a Network Service Capability Layer (NSCL) 610 stores resources created by a plurality of M2M devices in an M2M server. As the number of M2M devices connected to the NSCL 610 increases, the resources stored in the M2M server increase.

According to the former M2M standard, the entity that created the resource deletes the resource it has created itself, or assigns the expiration time to manage the life cycle of the resource. However, if the M2M device does not manage the resources properly after setting the expirationTime value to a too long time or an abnormal value (such as a negative value), unnecessary resources not used by the M2M server may overflow and the M2M server There may be a case where the storage space of the resource object becomes insufficient and the resource object is generated too much, and the resource discovery performance is deteriorated. In this case, the M2M server administrator needs to search for unused or unnecessary resources.

Referring to FIG. 6, it is possible to manage a resource that has not been used for a predetermined period or more by searching for a last reference time (lastAccessTime) and deleting the resource.

The NA 620 may act as a management application that monitors the resource search performance and manages the storage space. The NA 620 can recognize that the search performance of the resource is lowered at a specific point in time or the storage space is insufficient below a certain threshold value (S651).

Accordingly, the NA 620 determines ifUnmodifiedSince (a condition for searching unchanged resources after a specified point) and ifUnaccessedSince (a reference point after a point designated as a search condition proposed according to the present invention) as a parameter of resource discovery (S653), the NSCL 610 searches for a resource that has not been changed since the specific point in time and is not referenced.

The NSCL 610 generates an address list of resources matching the provided condition according to the search request, and sends the response message to the NA 620 (S655). Accordingly, according to the address list of the received resources, the NA 620 requests the related service provider or the application provider to delete unused resources or deletes the resources with the administrator's authority, (Step S657).

7 is a view for explaining another application example of the embodiments of the present invention. Depending on the individual characteristics of the resources, the accessibility of the resources can be improved through different management methods.

Each resource can have different characteristics from resource to resource. For example, there may be resources that have recently referenced resources that are likely to be referenced again, and resources that are most likely to be referenced the most long ago may exist. In this case, the M2M server can increase the access speed by managing the resources that are likely to be accessed during the idle time of the system in a fast-access storage medium. Also, the search performance can be improved by applying the last reference time (lastAccessTime) to the search algorithm at the time of resource discovery.

Hereinafter, a method for improving accessibility to resources using the last reference time (lastAccessTime) will be described.

When the DA1 710, the DA2 720 and the DA3 730 are homogeneous M2M applications, they are applications having similar characteristics, and therefore they are likely to refer to the same resource. In this case, when the NSCL 740 receives a request to retrieve a resource A from the DA2 720 and receives a response (S751), the NSCL 740 transmits the request for the resource A most recently Transfer the referenced resource A to a fast storage location or storage medium and store it. The operation of moving the resource A to the storage location or the storage medium having a fast access time is performed in the idle state of the NSCL 740, for example, .

Therefore, if a retrieve request for a recently accessed resource A from the DA1 710 or the DA3 730 occurs (S755 or S759), the NSCL 740 accesses the resource A more quickly and stores it in the resource By transferring the data, it is possible to improve access performance to resources in the M2M system.

As described above, by adding the lastAccessTime attribute as a resource attribute that is not defined in the conventional M2M standard, it is possible to provide additional information about the resource to the M2M entities to compensate for the problems that may occur in the M2M environment, And can provide flexibility in terms of M2M system management.

8 is a diagram illustrating a configuration of an M2M device according to an embodiment of the present invention.

The illustrated M2M device may be implemented to operate as an M2M device, an M2M gateway, or an M2M network domain, respectively.

Referring to the drawings, an M2M device includes an M2M application module 121, an M2M service capability module 122, and a communication module 125.

Although the M2M application module 121 and the M2M service capability module 122 are shown as separate elements in the drawing, they may be implemented as separate processors or in a single processor.

The M2M application module 121 and the M2M service capability module 122 operate in cooperation with each other and can integrally control the components in the M2M device to implement the above-described embodiments according to the present invention. In this case, the M2M application module 121 and / or the M2M service capability module 122 may be implemented as an integrated controller or an M2M service module 123 and may be implemented as a single processor.

The M2M application module 121 and the M2M service module 122 create a request and a response message for collecting and transmitting information about another M2M device to which the request is to be received or another M2M device that has transmitted the request, (125) to transmit and receive the above-mentioned messages and to transmit and receive the above-mentioned response messages.

In addition, when the M2M device is implemented as a hosting SCL, the M2M application module 121 and the M2M service module 122 analyze the information received from the connected M2M devices and store the information as resources.

In addition, the M2M application module 121 and the M2M service module 122 use the filter criteria described above to manage the M2M information and manage the resources by searching the attribute values.

Meanwhile, the communication module 125 performs an interconnection so that M2M communication between the M2M devices can be performed, and is connected to the communication module 125 through an existing area network or a core network. The communication module 125 may be connected to a local network such as IEEE 802.15.1 [i.3], Zigbee, Bluetooth, IETF ROLL, ISA100.11a or PLC, M-BUS, Wireless M- Or a core network communication module such as a local area network communication module and / or xDSL, HFC, satellite communication, GERAN, UTRAN, eUTRAN, W-LAN and WiMAX. It will be apparent to those skilled in the art that various modifications and variations may be made without departing from the essential characteristics of the present invention. Therefore, the embodiments disclosed in the present invention are intended to illustrate rather than limit the scope of the present invention, and the scope of the technical idea of the present invention is not limited by these embodiments. The scope of protection of the present invention should be construed according to the following claims, and all technical ideas falling within the scope of the same shall be construed as falling within the scope of the present invention.

210: Requestor 220: Hosting SCL

Claims (10)

Writing data into a resource according to an M2M resource structure; And
And storing a lastAccessTime attribute indicating a time at which the resource storing the data is finally read.
The method according to claim 1,
Wherein the last reference time attribute is updated when the resource is successfully transmitted according to a retrieve or notify request.
The method according to claim 1,
Wherein the last reference time attribute is stored as a common attribute or an individual attribute of each of the resources.
The method according to claim 1,
And the resource is searched through the final reference time attribute using a reference (ifAccessedSince) item as a filter criterion after a specific time point used as a condition for searching for a resource referenced after a designated time point. How to manage.
The method according to claim 1,
And the resource is searched through the final reference time attribute using a postponed reference (ifUnaccessedSince) item as a filter criterion at a specific time point used as a condition for searching for a resource not referred to after a designated time point M2M information management method.
According to the M2M resource structure, data is recorded as resources,
And stores a lastAccessTime attribute indicating a time at which the resource storing the data is finally read.
The method according to claim 6,
Wherein the last reference time attribute is updated if the resource is successfully transmitted according to a retrieve or notify request.
The method according to claim 6,
Wherein the last reference time attribute is stored as a common attribute or an individual attribute of each of the resources.
The method according to claim 6,
And the resource is searched through the last reference time attribute using a reference (ifAccessedSince) item as a filter criterion, which is used as a condition for searching for a resource referenced after a designated time point. .
The method according to claim 6,
And the resource is searched through the final reference time attribute using a postponed reference (ifUnaccessedSince) item as a filter criterion at a specific time point used as a condition for searching for a resource not referred to after a designated time point M2M device.

Images