WO2013168911A1 - Method for forming container resource using user identification information, recording medium, and device therefor - Google Patents

Description

Method for configuring container resource using user identification information, recording medium, and apparatus therefor

The present invention relates to a method for configuring container resource information for identifying a user in a machine to machine communication (M2M) device, a gateway or a device connected to a gateway, or an M2M platform, a recording medium thereof, and an apparatus therefor.

Communication of things (MTC, "Machine to machine communication" or M2M, "Machine type communication" or smart device communication "Smart Device communication" or "Machine oriented communication") refers to all aspects of how a person communicates without interfering with the communication process. Refers to a communication method.

The European Telecommunications Standards Institute (ETSI) announced a functional structure for providing M2M communication as ETSI TS 102 690 V1.1.1 (hereinafter referred to as 'structure') in October 2011.

When information is transmitted from a device, a gateway, or a device connected to the gateway using a container resource defined according to the structure of the existing ETSI M2M standard, the M2M platform (server) stores the information.

However, on the application side of the M2M platform, there is no method for identifying and controlling a user of a specific device, a gateway, or a device connected to the gateway according to resource related information, or checking a control result.

In order to solve the above-described problem, an object of the device and the gateway or the device connected to the gateway in the mId interface defined by ETSI, the purpose of the M2M platform to identify and control using the container resource information.

In addition, it aims to identify and apply information generated by a plurality of M2M devices or gateways or devices connected to the gateway in the dIa interface in the M2M platform.

According to an embodiment of the present invention, there is provided a recording medium on which data is recorded as a resource that is an object having a unique address in an expressive state transfer architecture, which is an M2M resource structure.

The recording medium has a structure in which a content instance resource generated as an object to store the data includes a content that is an accessory resource for storing the data and an attribute for storing meta information related to the content. The included attribute includes user related content information for the data stored in the content which is the accessory resource.

According to an embodiment of the present invention, in an M2M device that stores data in a server according to an M2M resource structure, user-related content information about the data to generate a content instance resource for storing the data in the server to store data. Creating a content instance creation request message comprising a; Transmitting the created content instance creation request message to the server; And transmitting the data to the server when a successful response message for the content instance creation request message is received from the server. According to an embodiment of the present invention, a communication module for transmitting and receiving a content instance creation request message for requesting the creation of a content instance resource to store the data in order to store data as a resource according to the M2M resource structure; And an M2M module configured to generate a content instance resource including a content that is an accessory resource for storing the data and an attribute for storing meta information related to the content according to the content instance creation request message. An M2M object is provided, comprising: configuring user-related information on the data stored in content in the attribute included in the content instance resource.

In addition, according to an embodiment of the present invention, a communication module for transmitting and receiving a content instance query request message for requesting a content instance resource query is stored as data in accordance with the M2M resource structure; And an M2M module for querying a content instance resource including a content that is an accessory resource for storing the data and an attribute for querying meta information related to the content, according to the content instance inquiry request message, wherein the M2M module includes: An M2M object is provided, comprising: configuring user related information about the data stored in the content in the attribute included in the content instance resource.

In addition, according to an embodiment of the present invention, a communication module for transmitting and receiving a content instance deletion request message for requesting to delete the content instance resource for deleting the stored data for the content instance resource in which data is stored as a resource according to the M2M resource structure; And an M2M module for deleting a content instance resource including a content storing the data as an accessory resource of the content instance resource and an attribute storing meta information related to the content according to the content instance deletion request message. The M2M module is provided with an M2M object, characterized in that to delete the user-related information for the data from the attribute included in the content instance resource.

According to the present invention, a simple, fast, and accurate process of generating, inquiring, or deleting a <contentInstance> generated in a plurality of M2M devices, gateways, or devices connected to a gateway in an mId interface may be performed.

In addition, each SCL in mIa and dIa interfaces has the effect of simple, fast and accurate processing of creating, querying, or deleting <contentInstance>.

In particular, since the number of M2M devices or gateways connected to the communication network is expected to be higher than that of a mobile phone or a smartphone, the present invention can improve the processing and searching performance of the M2M platform.

In addition, the identification process of M2M devices and gateways and the information of devices connected to the gateways can be quickly processed using consistent processing methods. In the mIa interface, the device information can be identified and processed quickly to update or modify the information stored in the M2M platform.

Information generated by multiple users in one DA can be identified in a systematic and standardized manner in the system, and the identified information can be applied.

1 is a diagram illustrating a configuration of an M2M system according to an exemplary embodiment of the present invention.

2 is a diagram illustrating a method of configuring an M2M container resource according to an embodiment of the present invention.

3 is a diagram for describing a method of configuring an attribute constituting a <contentInstance> resource according to an embodiment of the present invention.

FIG. 4 is a diagram for describing a method of configuring a control command and a response for creating, inquiring, or deleting a <contentInstance> resource according to an embodiment of the present invention.

5 is a diagram illustrating an example of search term attributes (searchStrings) constituting content instance information according to an exemplary embodiment of the present invention.

6 is a diagram illustrating a procedure of configuring a container resource according to an embodiment of the present invention.

7 is a diagram illustrating a procedure of generating a content instance according to an embodiment of the present invention.

8 is a diagram illustrating a procedure of querying a content instance according to an embodiment of the present invention.

9 is a diagram illustrating a procedure of deleting a content instance according to an embodiment of the present invention.

10 is a diagram illustrating an apparatus for configuring, querying, and deleting an M2M container resource according to an embodiment of the present invention.

11 to 13 are diagrams for explaining examples in which the present invention is implemented.

[Description of the code]

1010: M2M device 1030: M2M server

Hereinafter, some embodiments of the present invention will be described in detail with reference to the accompanying drawings. In adding reference numerals to the components of each drawing, it should be noted that the same reference numerals are assigned to the same components as much as possible even though they are shown in different drawings. In addition, in describing the present invention, when it is determined that the detailed description of the related well-known configuration or function may obscure the gist of the present invention, the detailed description thereof will be omitted.

In addition, in describing the component of this invention, terms, such as 1st, 2nd, A, B, (a), (b), can be used. These terms are only for distinguishing the components from other components, and the nature, order or order of the components are not limited by the terms. If a component is described as being "connected", "coupled" or "connected" to another component, that component may be directly connected or connected to that other component, but between components It will be understood that may be "connected", "coupled" or "connected".

Embodiments of the present invention will be described based on communication of things. IoT is variously called Machine to Machine communication (M2M), Machine Type Communication (MTC), Internet of Things (IoT), Smart Device Communication (SDC), or Machine Oriented Communication. In the present specification, the description will be made based on M2M. However, this description is not limited to M2M, but is applicable to all systems and structures that provide inter-device communication, that is, thing communication, and communication that occurs in these systems.

In addition, the IoT may be applied to various fields including smart meter, eHealth, connected consumer, city automation, automotive application, and the like.

1 is a diagram illustrating a configuration of an M2M system according to an exemplary embodiment of the present invention.

The M2M system according to the present invention is applied in an environment that provides a function for accommodating multiple access networks in a device / gateway and an M2M core platform.

The M2M structure consists of an M2M device / gateway domain for providing an IoT communication service shown in the left side of the figure and a network domain or M2M server platform shown in the right side of the figure.

Referring to the drawings, the M2M device D (111, 121, 131, 151, 161, 171) capable of direct communication with the M2M platform, M2M gateway (211, 221), M2M must communicate via the M2M gateway to communicate with the M2M platform Device D '311, 321, 331, 351, 361, 371 and M2M server platform 411 are shown.

The components of the M2M gateways 211 and 221 are the GAs 213 and 223 and the GSCLs 215 and 225. The GSCLs 215, 216 of the M2M gateway may provide the GIPs 217, 227. The M2M gateway provides communication with the M2M platform 411 via the dIa interface to devices 311, 321, 331, 351, 361, 371 that do not provide SCL functionality.

The M2M platform 411, which is a network domain, includes an M2M Network Application 413 that accesses an M2M Network Service Capability Layer (NSCL) 415, which is an M2M service capability layer, or provides service logic.

Meanwhile, the M2M device / gateway domain includes M2M device (D and D ') (111, 121, 131, 151, 161, 171, 311, 321, 331, 351, 361, 371) and M2M gateway (211,221). ). The M2M device also includes M2M device applications 113, 123, 133, 153, 163, 173, 313, 323, 333, 353, 363, 373, and the M2M gateway includes M2M gateway applications 213, 223, respectively.

In addition, the M2M device (D) (111, 121, 131, 151, 161, 171) further includes an M2M Device Capability Layer (M2M Device Capability Layer) (DSCL) 115, 125, 135, 155, 165, 175, and provides M2M communication service with NSCL of the network domain through the M2M DSCL. In addition to the DA (113, 123, 133, 153, 163, 173) and the DSCL (115, 125, 135, 155, 165, 175), the M2M device D (151, 161, 171) has a separate application without a separate dIa interface, For example, the DSCL includes a Device Interworking Proxy (DIP) module 157, 167, and 177 that provides interworking with a network domain for the M2M device D '(311, 321, 331, 351, 361, and 372). Can be.

In addition, when the M2M device does not include the M2M DSCL (D ') (311,321,331,351,361,371), the M2M Gateway Service Capability Layer (GSCL) 215,225 included in the M2M gateways 211,221 or the M2M device D (151). , 161 and 171 provide the NSCL and M2M communication service of the network domain. That is, the M2M device may operate its own M2M application in order to use the functions of the network domain and operate in the network domain through the M2M Service Capability Layer (SCL) of the M2M device or the M2M gateway.

M2M objects such as M2M devices, M2M gateways, M2M network domains, and M2M servers may include one or more specific SCs in each Service Capability Layer (SCL), and the SCs provide functionality shared by different applications. I say that.

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 communicate and interwork with each other.

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

Referring back to FIG. 1, mIa is a reference point used in a network domain and is an interface specification between an M2M Service Capability Layer in the network (NSCL) provided by an M2M platform and a network application (NA).

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

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

In addition, the ETSI M2M specification defines 'resource' for transmitting and controlling data in mIa, mId, and dIa interfaces. A resource is an object with a unique address in the Representative Architecture, an M2M resource structure.

Meta information for representing a resource is called an attribute. There are three properties: RW (Read Write), which can be read from the client, RW (Read Only), which can be written (set) by the server, and R only (Read Only), which can only be read by the client; Separate.

According to the M2M structure, resources include SclBase, SCL, Application, AccessRight, Container, LocationContainer, Group, Subscription, M2MPoC, MgmtObj, MgmtCmd, AttachedDevices, AttachedDevice, Announced, NotificationChannel, Discovery, Collection, etc.

Among these, container resources are used to exchange data in mIa, mId, and dIa interfaces. In other words, the device / gateway and network-side application and / or service capability layers utilize container resources as a kind of mediator for buffering data, so that both parties wishing to exchange information need not be online at the same time.

In the mIa interface, information is delivered from the network application (NA) to the network service capability layer (NSCL) using container resources.In the dIa interface, the device application (DA) uses the container to the device / gateway service capability layer (D / G SCL). Communicate information using resources The mId interface delivers containers from the device / gateway service capability layer (D / G SCL) to the network service capability layer (NSCL), or from the network service capability layer (NSCL) to the device / gateway service capability layer (D / G SCL). You can pass a container.

As described above, when information is transmitted from a device, a gateway, or a device connected to the gateway by using the container resource defined in the structure, the M2M platform stores the information.

However, according to the current M2M specification, there is no method for identifying and controlling a specific device, a gateway, or a device connected to the gateway in connection with specific information among the network information (NA) of the M2M platform. have.

For example, if control such as changing the frequency at which information collected from a specific device is delivered to the M2M platform is required, the M2M platform retrieves device identification information from a separate database instead of the container information. Control command must be sent to the device.

Therefore, in the M2M platform, in order to confirm the result of such control, the step of finding the device identification information and comparing the container information sent from the device must be performed twice.

In addition, when there is a need to control a device connected to a specific gateway, the M2M platform retrieves the device identification information from a separate database in addition to container information, and sends a control command to the gateway using the search results. It finds the device connected to the M2M Area Network and sends a control command. Therefore, in order to check the control result of the device connected to the gateway in the M2M platform, the step of finding the identification information of the gateway and the device, the step of finding the identification information of the device connected to the gateway, and the container information sent from the device connected to the gateway The comparing step must be performed.

For example, when an office wants to check the operation status of the lights in the home through a gateway in the home and to control the lights off or on partly, or to remotely read the information of several water meters, gas meters, and power meters. As described above, a step of separately searching for identification information of each device and comparing container information sent from the corresponding device should be performed in duplicate.

2 is a diagram illustrating a method of configuring a container resource for exchanging information in an mIa, mId, and dIa interface according to an exemplary embodiment of the present invention.

Container resource <container> is composed of accessory resources such as attributes, subcontainers, contentInstances, and subscriptions.

A ContentInstances resource, which is an accessory resource of a container resource, is a collection of content instances in a container. When querying a content instance, the content of the <contentInstance> resources in the collection is returned as a resource representation, rather than simply a reference to these accessory resources. When inquiring a content instance resource, only metadata of content instance <contentInstance> resources may be responded or actual content of each content instance may be responded with metadata.

ContentInstances resource does not include its own AccessRights, but applies the access rights of its container resource <container>.

2 shows a content instance resource <contentInstance> that is an accessory resource of a container resource. Referring to the figure, a content instance <contentInstance> resource is composed of an attribute and a content.

m means that the attribute can consist of several, and 1 means that there is one corresponding resource.

Content instance resource <contentInstance> represents a data instance in a container resource. The content of the instance may be inaccessible or even encrypted, depending on the M2M platform. However, the metadata associated with the instance is accessible.

Unlike other resources, a content instance <contentInstance> resource cannot be modified once created, regardless of the access rights of its associated parent resource.

3 is a diagram for describing a method of configuring an attribute constituting a <contentInstance> resource according to an embodiment of the present invention.

Referring to FIG. 3, an attribute which is an accessory resource of <contentInstance> is used to exchange container instances in mId, mIa, and dIa. In order to use the attribute information in exchanging container instances, 'M' means to be included to compose the attribute and 'O' means to be optionally included in constructing the attribute. In addition, the names constituting each attribute are classified into types of 'RW', 'RO', and 'WO'. As described above, RW (read / write) is a type that can be read and written by a client requesting an operation of creating, querying, updating, or deleting a corresponding attribute. Read only (RO) is a type of attribute that can only be read and not written by the client, and write once (WO) is a type of attribute that can only be written when first created.

The contentType attribute is information about the type of content included in the content attribute, and contentSize indicates the size of the content attribute in bytes. creationTime and lastModifiedTime represent the creation time and last modified time of the resource. DelayTolerance also indicates the time until the subscriber is notified of the addition of the retention of the <contentInstance> resource. searchStrings are tokens that are used as keys for resource searching, and can be used, for example, to display user associated contents. The content may be an actual inaccessible content of an instance, for example, an image captured by a security camera or a measurement temperature detected by a temperature sensor.

FIG. 4 is a diagram illustrating a method of configuring a request command and a message for creating, inquiring, or deleting a <contentInstance> according to an embodiment of the present invention.

In mId, mIa, and dIa, attribute information as shown in FIG. 4 is constituted in exchanging control commands and response messages for creating, querying, or deleting a content instance for storing data, that is, data on a server. Can be. Therefore, the client that wants to store the resource in the server creates a request message including metadata, that is, attribute information, as shown in FIG. 4, and transmits the message to the server.

Id represents an identifier proposed by the issuer in the creation request or provided by the hosting SCL in the response message. Href represents the URI address used to retrieve the contentInstance directly. The contentType attribute is information about the type of content included in the content attribute, and contentSize indicates the size of the content instance in bytes. creationTime and lastModifiedTime represent the creation time and last modified time of the resource. DelayTolerance also indicates the time until the subscriber is notified of the addition of the retention of the <contentInstance> resource. The searchStrings are tokens used as keys for resource searching, and may include identification information for displaying user associated contents, for example.

5 is a diagram illustrating an example of searchStrings constituting container instance information according to an exemplary embodiment of the present invention.

The search string (searchStrings) attribute is a token used as a key for resource search, and may include, for example, identification information capable of displaying user associated contents. The search term attribute is, for example, classifying or searching for a resource as a name or a name according to the content (content) of a stored resource such as "meter", "valve", or "zone (user name)". It can be used as a data identifier for.

6 is a diagram illustrating a procedure of configuring a container resource according to an embodiment of the present invention.

Issuers (DA, GA, NA) acting as clients who want to store data on the server send a content instance create request message (contentInstanceCreateRequestIndication) to determine the location for storing the data on the server to store their data. (S510).

The content instance creation request message is generated by including attribute information as shown in FIG. 4, and in particular, a feature of data to be stored in a content instance generated by including a search string (searchStrings) attribute, which is a token used as a key for resource search. In particular, it may include identification information capable of displaying user associated contents.

Accordingly, the server, which is the recipient of the request message, analyzes the request message to determine a location to store the data in the server, and has an M2M resource structure as shown in FIG. 2 including attribute information as shown in FIG. 3. A content instance is generated (S520).

Accordingly, when the request message is successfully processed, the server, which is the receiver, transmits the successful response message (contentInstanceResponseConfirm) to the issuer, which is the client (S530).

Subsequently, the issuer, which is a client, transmits data to be stored to the server and performs attribute information as shown in FIG. 3 (S540). That is, the attribute information, which is metadata about data stored in the content instance, is configured to include a data identifier such as user identification information in searchStrings attribute information as shown in FIG. 4.

Therefore, every object that wants to use the data, including the issuer (DA, GA, NA) and SCL recipients, can then distinguish the data by using data identifiers such as user identification information stored in searchStrings as identifiers for the data. It becomes possible.

For example, when the embodiment according to the present invention is implemented on a scale, when the person climbs on the scale, the scale measures the weight of the person, and the weight scale may record information such as the measurement date and the like as well as the weight of the person.

The scale sends the weight and the measurement date and time to the server. When a large number of family members use the scale, it is necessary to distinguish each user. To this end, according to the present invention, the user identification information is stored in the searchStrings property as metadata of the corresponding data, thereby distinguishing each user in the subsequent processing and management of each data. To process and manage the data.

7 is a diagram illustrating a procedure of generating a content instance according to an embodiment of the present invention.

The issuer that sends the request to generate container instance information may be, for example, a device / gateway application or network application or device / gateway, network service capability layer.

When the issuer is a device / gateway application (DA, GA), the receiver may be a device / gateway service capability layer (D / G SCL). Also, when the issuer is a network application, the receiver can be a network service capability layer (NSCL). Also, when the issuer is a device / gateway service capability layer (D / G SCL), the receiver can be a network service capability layer (NSCL), in which case the D / G SCL relays the creation of container instance information of the DA / GA. It performs the function.

The SC100 of FIG. 7 is a case where a request message is sent from a device / gateway application (DA / GA) and a response message is sent from a device / gateway service capability layer (D / GSCL). The SC110 sends a request message in the device / gateway service capability layer (D / GSCL) and sends a response message by the gateway service capability layer (SSCL). The SC120 is a case where a request message is sent by the network service capability layer (NSCL) and a response message is sent by the device / gateway service capability layer (D / GSCL). The SC130 is a case where a request message is sent by a network application (NA) and a response message is sent by a network service capability layer (NSCL).

The issuer constructs a content instance create request (contentInstanceCreateRequestIndication) message and transmits it to the receiver (S601, S611, S621, and S631).

In this case, the message composed by the issuer is configured to include attribute information as shown in FIG. 4 constituting the corresponding content instance, and the URI of the target object for which the issuer's own requesting object information and content instance information are generated. And optionally one of a content instance resource representation or raw content that is actual data.

The issuer is then an identifier for identifying data such as, for example, user identification information in searchStrings representing tokens used as keys for searching for resources and user associated contents among attribute information constituting the content instance. You can configure the request message to include.

When a recipient who receives a request message including user identification information as attribute information constituting a content instance requesting creation creates a content instance in which user identification information is composed of attribute information, the content instance is determined by the user identification information. It can be used for future information management and information retrieval of the content of the corresponding instance instance.

Recipients receiving the content instance creation request message interpret the content instance property information included in the received message, and receive a successful response message (ContentInstanceCreateResponseConfirm) (S603, S613, S623, S633) or a failed response message (ContentInstanceCreateResponseConfirm) (S605, S615). S625 and S635 are generated and transmitted to the issuer.

That is, the receiver determines whether the resource indicated by the creation request message exists, and grasps the authority of the request object information according to the access right (accessRightID). In addition, the receiver analyzes the received message structure if there is an indicator of the content instance resource according to the presence of the content instance resource or the representation of the content instance resource among the information included in the received message. The request is rejected as a response message (STATUS_BAD_REQUEST), and if there is raw content that is actual data, the hosting SCL, which is a receiver, uses the corresponding row content to generate a content instance resource representation.

The receiver then validates the resource indicator for creation. That is, if the parent resource of the corresponding content resource (contentInstances resource) corresponds to a location container resource with a location container type (locationContainerType) attribute value set to location server-based (LOCATION_SERVER_BASED) to validate the provided attribute, the request is Rejected as a failed response message with error information (STATUS_FORBIDDEN).

The hosting SCL, which is the receiver, creates the requested resource when the raw data that is the actual data is included in the received request message. The recipient SCL, which is the recipient, may generate a resource representation based on the metadata information.

The resource indicator generated by the hosting SCL that is the receiver is an indicator of the content instance resource requested to be generated, and the generated content instance may be generated to have the structure of FIGS. 2 and 3.

The receiver who created the resource indicator generates a successful response message (ResponseConfirm) and sends it to the issuer.

The receiver generates a successful response message (contentInstanceCreateResponseConfirm) for this purpose. The successful response message includes a status code (STATUS_CREATED), the resource URI that is the URI assigned to the created resource, and the generated content if the resource indicator of the content instance has been modified. You can include the resource instance of the instance (contentInstance).

The receiver includes the error information in the failed response message (contentInstanceCreateResponseConfirm) without including the information as shown in FIG.

Therefore, the issuer may use the searchStings attribute information as a key for searching for a resource related to a user by storing a data identifier such as user identification information in the searchStrings attribute information among the attribute information which is metadata about the resource of the content instance.

Therefore, after searching the searchStrings which are the property information of the created content instance in the client as well as other objects, it is possible to identify which user-related data is stored in the content instance.

As described above, searchStrings that can be used as data search identifiers can store information such as, for example, "meters", "valve", or "zone (user name), so that user identification information is stored. Can be.

8 is a diagram illustrating a procedure of querying a content instance according to an embodiment of the present invention.

8 is a procedure for inquiring information of a specific user stored in a device, a gateway, or an M2M platform. The SR200 sends a request message (contentInstanceRetrieveRequestIndication) to a device / gateway application (DA / GA) and sends a response message (contentInstanceRetrieveResponseConfirm) to the device. This is the case when the Gateway Service Capability Layer (D / GSCL). SR210 is a case where a request message is sent by the device / gateway service capability layer (D / GSCL) and a response message is sent by the gateway service capability layer (SSCL). The SR220 is a case where a request message is sent by the network service capability layer (NSCL) and a response message is sent by the device / gateway service capability layer (D / GSCL). SR230 is a case where a request message is sent by a network application (NA) and a response message is sent by a network service capability layer (NSCL).

The request message (contentInstanceRetrieveRequestIndication) and the successful response message (contentInstanceRetrieveResponseConfirm) of FIG. 8 are configured as shown in FIG. However, the failed response message does not send information as shown in FIG. 4, but transmits only an error code. At this time, the information to find the data related to the user is used as input of the property value of searchStrings.

9 is a diagram illustrating a procedure of deleting a content instance according to an embodiment of the present invention.

9 is a procedure for deleting information of a specific user stored in a device, a gateway, or an M2M platform. The SD300 sends a request message (contentInstanceDeleteRequestIndication) to the device / gateway application (DA / GA) and sends a response message (contentInstanceDeleteResponseConfirm) to the device. This is the case when the Gateway Service Capability Layer (D / GSCL). The SD310 is a case where a request message is sent by the device / gateway service capability layer (D / GSCL) and a response message is sent by the gateway service capability layer (SSCL). The SD320 is a case where a request message is sent by the network service capability layer (NSCL) and a response message is sent by the device / gateway service capability layer (D / GSCL). The SD330 is a case where a request message is sent by a network application (NA) and a response message is sent by a network service capability layer (NSCL).

The request message (contentInstanceDeleteRequestIndication) and the successful response message (contentInstanceDeleteResponseConfirm) of FIG. 9 are configured as shown in FIG. 4. However, the failed response message does not transmit the information as shown in FIG. 4 but transmits an error code. At this time, the information to find the data related to the user is used as input of the property value of searchStrings.

FIG. 10 illustrates an apparatus for configuring, querying and / or deleting an M2M container resource according to an embodiment of the present invention.

In the drawings, the elements for implementing a method of configuring, inquiring and / or deleting an M2M container resource according to the present invention are shown.

Referring to the drawings, M2M objects are composed of an M2M device 1010 that can be implemented as an M2M device or a gateway, and an M2M server 1030 that can be implemented as an M2M device, a gateway, or a network domain, respectively.

Referring to the drawings, the M2M device 1010 includes an M2M application module 1013, an M2M service capability module 1015, and a communication module 1011. In addition, the M2M device 1010 may further include a memory 1019 for storing various information.

In the drawing, the M2M application module 1013 and the M2M service capability module 1015 are shown as being implemented as separate elements, but each of them may be implemented as a separate processor or in one processor.

The M2M application module 1013 and the M2M service capability module 1015 interoperate with each other and perform device elements in the M2M device 1010 in order to process various operations such as configuring, inquiring, and deleting an M2M container resource according to the present invention. Integrated control is possible. In this case, the M2M application module 1013 and / or the M2M service capability module 1015 may be implemented as an integrated control unit, an M2M service module, or an M2M module 1012 and may be implemented as one processor or different processors.

In order to configure the M2M container resource, the M2M application module 1013 and the M2M service module 1015 collect a request message for collecting and transmitting information on the M2M object that is to receive the request and information on the container resource to be configured. And control the communication module 1011 to transmit the above-described request message and to receive the above-described response message. In this case, as shown in FIG. 4, the request message may include various attribute information including the user identification information as described above.

Meanwhile, the communication module 1011 performs interconnection to perform M2M communication between M2M objects and is connected through a network for this purpose. The communication module 125 may be configured to provide this functionality by using a local network or a local network (such as IEEE 802.15.1 [i.3], Zigbee, Bluetooth, IETF ROLL, ISA100.11a, or PLC, MBUS, Wireless MBUS, and KNX). Area Network) communication module and / or core network communication modules such as xDSL, HFC, satellite communication, GERAN, UTRAN, eUTRAN, WLAN and WiMAX.

The M2M server 1030 includes an M2M application module 1033, an M2M service capability module 1035, and a communication module 1031, and includes a memory 1039 for storing various information. It includes more.

The M2M application module 1033 and the M2M service capability module 1035 of the M2M server 1030 interpret the received request message to extract necessary information, and store data of the corresponding resource for creating, updating, or querying content instance resources. (1039) performs operations such as reading and writing.

In this case, the M2M server 1030 collects the attribute information as shown in FIG. 4 for the container resource from the M2M application module 1033 and the M2M service capability module 1035 through the mIa interface, and processes corresponding request information.

The mId interface between the M2M service capability modules 1015 and 1035 may control the communication modules 1011 and 1031 to transmit and receive information including container resources as shown in FIG. 4 and various attribute information including the above-described user identification information. have.

In addition, the M2M server 1030 operates the M2M application module 1033 and the M2M service module 1035 as a hosting SCL to analyze information received from various connected M2M devices, and includes the received data as attribute information. A function of storing the memory 1039 in the memory 1039 is performed.

According to the present invention, a control command classified to identify specific information can be transmitted from a device, a gateway, or a device connected to the gateway to a server using container resource attribute information. A specific device can be transmitted from a network application (NA). Alternatively, to control the gateway or a device connected to the gateway, the control result classified to enable identification of specific information may be transmitted using container resource attribute information.

In other words, when control such as changing the frequency of transferring information collected from a specific device to the M2M platform is required, the M2M platform can directly send a control command to the device based on the search result using the property information of the container. The property information can be used to confirm the result of control in the M2M platform.

In addition, when it is necessary to control a device connected to a specific gateway, it is possible to send a control command in the M2M platform using the attribute information of the specified container resource, the gateway is connected to the local network (M2M) using the attribute information of the container resource. Control commands can be sent to devices connected to an area network.

Also, in data communication between M2M devices, resources are created, inquired, updated, or deleted in the M2M platform using attribute information as identifiers of container resource data generated by a plurality of M2M devices, gateways, or devices connected to gateways. This enables simple, fast and accurate creation, inquiry, update, and deletion of requested resources.

11 to 13 are diagrams for explaining examples in which the present invention is implemented.

According to the examples of the drawings, in order to distinguish each user from the M2M device used by different users, the identification information of the user may be included in the identification information for various instances of the application. For example, as described above, searchStrings may include identification information of a user.

As described above, the M2M device includes a Device Service Capability Layer (DSCL) and a Device Application (DA).

Thus, for example, information generated by a plurality of users in one device application DA is identified and stored in a systematic and standardized manner in a system using user identification information included in searchStrings, and information stored by identification It can be applied in various ways.

Referring to FIG. 10, in the eHealth application of M2M, which is written in the technical report TR 102 732 by ETSI TC M2M, a M2M service using a heart rate monitor is a specific example of eHealth.

Sphygmomanometers include a device service capability layer (DSCL) and an application for performing blood pressure measurements (DA), and when a sphygmomanometer is used in the home, family members, such as fathers, mothers, sons, and daughters, share one sphygmomanometer Can be.

In this case, the device service capability layer DSCL may store user identification information of the blood pressure information measured by the application DA in, for example, the "searchStrings" attribute information to classify the blood pressure information by user, and the measured blood pressure information. It is possible to identify the information generated by a large number of users in the system in a systematic and standardized manner, and to apply the identified information by labeling the user identification information and transmitting the information to the server for storage and management.

In addition, running machines in the fitness center are examples of eHealth offering M2M services.

The running machine includes a device service capability layer (DSCL) for providing M2M functionality as an M2M device and an application (DA) for providing a running application.

At this time, the application DA of the running machine collects exercise related information such as running time and running distance. However, when a person uses a machine jointly, the exercise related information according to the user is stored by storing the collected exercise related information as resource attribute information configured in the resource in a name attribute for identification such as "searchStrings". Information can be managed separately.

In addition, when a plurality of blood pressure monitors are connected to one gateway, blood pressure information generated by the plurality of blood pressure monitors may be used as device attribute information for each blood pressure monitor or at least one user identification information using each blood pressure monitor as resource attribute information, for example, in searchStrings. By storing the resource together, the blood pressure information generated by each blood pressure monitor or the blood pressure information according to each user can be distinguished and managed in the same manner not only at the gateway but also at the M2M server connected thereto.

Referring to FIG. 12, in a vehicle application of M2M, which is written in the technical report TR 102 898 in ETSI TC M2M, the vehicle includes a device service capability layer (DSCL) and a device application (DA).

In this case, the application DA may collect various information such as driving time, driving distance, fuel consumption amount, RPM, brake signal, hourly position information, rapid acceleration, and rapid deceleration related to the driving of the vehicle.

When the M2M service of the vehicle is provided through, for example, a rental car, information collected by the application DA is different for each user of the rental car.

Therefore, even if the information collected by one application (DA) to use the content instance attribute information for data identification, such as "searchStrings" according to the present invention to classify the information collected by the user in a systematic and automated way, The information generated by multiple users can be identified in a systematic and standardized way in the system, and the identified information can be applied.

Referring to FIG. 13, in the city automation application of the M2M, which is written in the technical report TR 102 897 by the ETSI TC M2M, an access controller for access control of a company building is an example of city automatic.

The access controller includes a device service layer (DSCL) and an application (DA).

Application DA may collect a variety of information, such as company start time and leave time, or visit start time and end time, visit time, if the office worker by person.

In the case of providing the access controller M2M service, the information collected by the application DA of the access controller differs from each other in information such as access generation time.

Therefore, when using the content instance attribute information for data identification such as "searchStrings" according to the present invention in order to classify the information collected for each user in the application (DA) in a systematic and automated manner, a plurality of users generated Information can be identified and applied to the system in a systematic and standardized way.

Such access control is one of M2M services that can be widely applied in daily life such as company building, sports stadium, subway.

The above description is merely illustrative of the technical idea of the present invention, and those skilled in the art to which the present invention pertains may make various modifications and changes without departing from the essential characteristics of the present invention. Therefore, the embodiments disclosed in the present invention are not intended to limit the technical idea of the present invention but to describe the present invention, and the scope of the technical idea of the present invention is not limited thereto. The protection scope of the present invention should be interpreted by the following claims, and all technical ideas within the equivalent scope should be interpreted as being included in the scope of the present invention.

CROSS-REFERENCE TO RELATED APPLICATION

This patent application is filed with Korea Patent Application No. 10-2012-0049710 filed on May 10, 2012 and Korea Patent Application No. 10-2012-0061795 filed on June 8, 2012 and June 2012. Patent Application No. 10-2012-0069177 filed with Korea on 27th and Patent Application No. 10-2012-0073345 filed with Korea on 5 July 2012 and patent application filed with Korea on July 18, 2012 Priority to No. 10-2012-0078367 and Patent Application No. 10-2012-0130793, filed in Korea on November 19, 2012, pursuant to United States Patent Act section 119 (a) (35 USC § 119 (a)) All of which is hereby incorporated by reference in this patent application. In addition, if this patent application claims priority for the same reason for countries other than the United States, all its contents are incorporated into this patent application by reference.

Claims (15)

A recording medium in which data is recorded as a resource according to an M2M resource structure, The content instance resource generated as an object to store the data has a structure including content that is an accessory resource that stores the data and an attribute that stores meta information related to the content, And the attribute included in the content instance resource is configured to include user-related information about the data stored in content that is the accessory resource. The method of claim 1, And the user-related information is user identification information associated with the data. The method of claim 2, And the user identification information is a user name of the data. The method of claim 1, And the user-related information is recorded as a search word attribute among the attributes included in the content instance resource. The method of claim 1, The content instance resource is generated according to a content instance creation request message requested to store the data, and the user-related content information related to the data is obtained from the content instance creation request message. Recorded computer readable recording medium. In the M2M device to store data as a resource in the server according to the M2M resource structure, Creating a content instance creation request message that includes user related information about the data to generate a content instance resource for storing the data on the server to store data; Transmitting the created content instance creation request message to the server; And And transmitting the data to the server when a successful response message for the content instance creation request message is received from the server. The method of claim 6, The user related information, M2M resource configuration method characterized in that the content is included in the search word attribute of the attribute information of the content instance creation request message. The method of claim 7, wherein And the user related information is user identification information related to the data. The method of claim 8, The user identification information, M2M resource configuration method, characterized in that the user name of the data. The method of claim 6, Creating and sending a content instance inquiry request message including the user related information about the data to query the content instance resource of the data stored in the server; And Transmitting the data to the server when a successful response message to the content instance inquiry request message is received from the server. A communication module for transmitting and receiving a content instance creation request message for requesting generation of a content instance resource to store the data to store data as a resource according to an M2M resource structure; And According to the content instance creation request message, M2M module for generating a content instance resource including the content that is an accessory resource for storing the data and the property for storing the meta information associated with the content, The M2M module, M2M object, characterized in that to configure the user-related information about the data stored in the content in the attribute included in the content instance resource. The method of claim 11, The M2M module, M2M object, characterized in that for recording the user identification information associated with the data as the user-related information in the attribute. The method of claim 12, The M2M module records the user name of the data as the user identification information in the attribute. The method of claim 13, The M2M module, the M2M object, characterized in that for recording the user-related information in the search word attribute of the attribute included in the content instance resource. The method of claim 13, The M2M module, the M2M object, characterized in that to obtain the user-related information related to the data from the content instance creation request message.

Images