KR20130068218A - Device, gateway, data transferring method of device and gateway, and network application server - Google Patents

Abstract

PURPOSE: A data managing device, a gateway, a data transmitting method of the gateway, and a network application server are provided to make data relevant to privacy pass through in M2M(Machine to Machine) communications in case of not passing through the M2M platform or after being encrypted. CONSTITUTION: An M2M apparatus includes DSCs(Device Service capability), and a DA(Device Application). The DSC provides a function shared by applications operated in the DA. The DSC includes a SC(Service Capability). The SC delivers a message to a different SC within the DSC from a NGC(Network Generic Communication Capability) or includes a DGC(Device Generic Communication Capability) oppositely delivering a message. The DGC forms a security tunnel session and exchanges data with different DSC layers. The DGC transmits and receives data related with the application. [Reference numerals] (120) M2M service capability; (130) Core network; (140) Connection network; (160) M2M gateway; (170) Local network; (180) M2M device; (190) M2M device; (193) Other SC

Description

Device, gateway, data transfer method of device and gateway, and network application server

The present invention relates to a method of transmitting data in M2M communication.

Object communication is variously called M2M (Machine to Machine communication), MTC (Machine Type Communication), IoT (Internet of Things), Smart Device Communication (SDC), or Machine Oriented Communication . Object communication refers to various communication in which communication is performed without a person intervening in the communication process. Object communication can be used in various fields including Smart Meter, e-Health, Connected Consumer, City Automation, and Automotive Application. Data transmitted in such a thing communication may include data related to the privacy of the individual.

An object of the present invention is to provide a method for managing data related to privacy in a thing communication and an apparatus to which the method is applied.

One embodiment of the present invention, a device application module; And a device service capability module providing a function shared by an application of the device application module, wherein the device service capability module is configured to encrypt the data if the attribute of the data relates to privacy; And transmitting at least one of a transmission path of the M2M platform, whether the M2M platform stores the data, and a period during which the M2M platform stores the data.

Another embodiment of the invention, the step of identifying the attributes of the data; Determining whether an attribute of the data is related to privacy; If the attribute of the data is related to privacy, checking at least one of whether the data is encrypted, a transmission path of the data, whether an M2M platform stores the data, and a period during which the M2M platform stores the data; And it provides a data transmission method of the device comprising the step of transmitting the data.

Another embodiment of the present invention, a gateway application module; And a gateway service capability module providing a function shared by an application of the gateway application module, wherein the gateway service capability module is configured to determine whether to encrypt the data when the attribute of the data is related to privacy. A gateway, characterized in that for transmitting at least one of the transmission path, whether or not the M2M platform stores the data, and the period in which the M2M platform stores the data to transmit the data.

Another embodiment of the invention, the step of identifying the attributes of the data; Determining whether an attribute of the data is related to privacy; If the attribute of the data is related to privacy, checking at least one of whether the data is encrypted, a transmission path of the data, whether an M2M platform stores the data, and a period during which the M2M platform stores the data; And it provides a data transmission method of the gateway comprising the step of transmitting the data.

Another embodiment of the present invention is an M2M platform that communicates with a device or gateway and an application server and provides a function shared by an application of the application server, wherein the attribute of data transmitted and stored from the device or gateway is stored in privacy. If relevant, check whether at least one of whether to store the data based on the information contained in the data, whether to store the data to be encrypted or stored, and when the data is stored, the storage period of the data, and the data It provides an M2M platform, characterized in that for transmitting to the application server.

Another embodiment of the present invention includes storing data transmitted from a device or a gateway; Determining whether an attribute of the data is related to privacy based on information included in the data; Determining whether or not the data is stored based on information included in the data, when the attribute of the data is related to privacy; If it is determined that the data is to be stored, storing the data; And it provides a data transmission method of the M2M platform comprising the step of transmitting the data to the application server.

According to the present invention described above, the data related to privacy in the thing communication can pass through the M2M platform or after encrypted. Thus, the service provider can satisfy the user's needs with respect to privacy.

1 is a diagram illustrating an example of a structure of an M2M system to which embodiments of the present invention can be applied;
2 is a flowchart illustrating a process of acquiring application data in the system of FIG. 1;
3 and 4 illustrate an example of a structure of a resource to which embodiments of the present invention can be applied;
5 illustrates a process of obtaining application data according to an embodiment of the present invention.
FIG. 6 illustrates the process after S508 of FIG. 5 when the value of “routing” is “NA”.
FIG. 7 illustrates the process after S508 of FIG. 5 when the value of “routing” is “NSCL”.

Hereinafter, some embodiments of the present invention will be described in detail with reference to exemplary 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 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.

Embodiments of the present invention will be described with reference to object communication. Object communication is variously called M2M (Machine to Machine communication), MTC (Machine Type Communication), IoT (Internet of Things), Smart Device Communication (SDC), or Machine Oriented Communication . Object communication refers to various communication in which communication is performed without a person intervening in the communication process. Object communication can be used in various fields including Smart Meter, e-Health, Connected Consumer, City Automation, and Automotive Application.

1 illustrates a structure of an M2M system to which embodiments of the present invention can be applied.

Referring to FIG. 1, the entire M2M system 100 includes a network application (hereinafter referred to as “NA”) 110, M2M service capabilities (hereinafter referred to as “NSC”) 120 ( Or M2M platform), Core Network (130), Access Network (140), M2M Gateway (M2M Gateway) 160, Local Network (170) and M2M Device (M2M Device) 180, 190 may be included.

NA 110 is an application server. The NA 110 may provide a user interface.

The NSC 120, or M2M platform, is a server that provides M2M functionality shared by various applications. NSC 120 may be operated by NA 110 and other operators.

The NSC 120 is referred to as a Network Service Capability Layer (NSCL) including a service capability (hereinafter referred to as “SC”) that provides a function shared by various applications. 121). The NSCL 121 may have various SCs 122 to 127 that may provide different functions.

Of these, the Network Generic Communication Capability (NGC) 122 transmits messages between the M2M gateway 160, the M2M device 190, and other SCs (SC1 123 to SC 127) in the NSCL 121. Can be used for NGC 122 may establish a secure tunnel session to exchange data with all SCs. The NGC 122 may perform a function of analyzing the traffic transmitted as needed.

The NGC 122 may transmit and receive data related to the application. In addition, NGC 122 may receive data related to Performance Management (PM), Configuration Management (CM), and Fault Management (FM) from GGC 162 or DGC 192. Can be.

The NSC 120 may be connected to the core network 130 through the NGC 122. The core network 130 may provide a connection means including a minimum Internet Protocol (IP) connection.

Meanwhile, in FIG. 1, the NA 110 may be directly connected to the core network 130 without passing through the NSC 120.

The access network 140 is a network that allows the M2M gateway 170 and the M2M device 190 to communicate with the core network 130. The access network 140 may be, for example, a digital subscriber line (xDSL), a hybrid fiber coaxial (HFC), a power line communication (PLC), a satellite, a GSM EDGE Radio Access Network (GERAN), or a UMTS Terrestrial Radio Access Network (UTRAN). , evolved UMTS Terrestrial Radio Access Network (eUTRAN), Wireless Local Area Network (W-LAN), Worldwide Interoperability for Microwave Access (WiMAX), and the like.

The M2M device may be connected to the direct access network 140 or through the M2M gateway.

The M2M device 180 may be connected to the access network 140 through the M2M gateway 160. The M2M device 180 may be connected to the M2M gateway 160 using an M2M area network 170.

The M2M gateway 160 may act as a proxy of the M2M network on behalf of the connected M2M device 180. The M2M gateway 160 may perform a process such as authentication, approval, registration, management, and provision in terms of the connected M2M device 180.

The M2M gateway 160 may include a gateway service capability module (hereinafter referred to as "GSC") 161 and a gateway application module (hereinafter referred to as "GA") 165. . GSC 161 provides functionality shared by applications running on GA 165.

The GSC 161 may include an SC that provides functionality shared by the gateway application. The SC may include a Gateway Generic Communication Capability (GGC) 162 that forwards the message from the NGC 122 to other SC 163 in the GSC 161 and vice versa. GGC 162 may establish a secure tunnel session to exchange data with other gateway service capability layers.

The GGC 162 may transmit and receive data related to an application. GGC 162 may also send data related to performance management, configuration management, and failure management to NGC 122.

The local network 170 connecting the M2M gateway 160 and the M2M device 180 may include, for example, Institute of Electrical and Electronics Engineers (IEEE) 802.15.x, Zigbee, and IETF (Internet Engineering Task Force) ROLL (Routing). Personal Area Network (PAN) such as Over Low power and Lossy networks, International Society of Automation (ISA) 100.11a, or Power Line Communication (PLC), Meter-BUS (M-BUS), Wireless M-BUS Or a local area network (LAN) such as KNX.

The M2M device 190 may be directly connected to the access network 140. The M2M device 190 may perform a process such as authentication, approval, registration, management, and provision. The M2M device 190 may include a device service capability module (hereinafter referred to as “DSC”) 191 and a device application module (hereinafter referred to as “DA”) 195. . The DSC 191 provides functionality shared by applications running on the DA 195.

The DSC 191 may include an SC that provides functionality shared by the device application. The SC may include a Device Generic Communication Capability (DGC) 192 that forwards the message from the NGC 122 to another SC 193 in the DSC 191 or vice versa. The DGC 192 may establish a secure tunnel session to exchange data with other device service capability layers.

The DGC 192 may transmit and receive data related to an application. In addition, the DGC 192 may transmit data related to performance management, configuration management, and fault management to the NGC 122.

The above-mentioned NA (110), GA (165), DA (195), and M2M Service Capability Layer (SCL) in the NSC (120), GSC (161), DSC (191) RESTful format can be applied as a principle for exchanging information between RESTful form means following the principles of Representational State Transfer (REST).

An important concept of REST is the existence of resources, each represented by an identifier. To handle these resources, the components of the network (eg, NA 110, GA 165, DA 195, and NSC 120, GSC 161 in the system 100 of FIG. 1). The SCL in DSC 191 may communicate over a standardized interface and exchange representations of these resources. Such a resource may have a tree structure.

When dealing with resources in a RESTful structure, the following four basic methods can be applied to resources.

Create (C): Creates a child resource.

Retrieve (R): Read the contents of a resource.

Update (U): Write the contents of a resource.

Delete (D): Delete a resource.

This method may be called a CRUD method. In addition to this CRUD method, a request (S) for resource exchange, a notification (N) for resource exchange, and an execution (E) of a management command / task represented by the resource may be defined.

2 is a flowchart illustrating a process of obtaining application data in the illustrated system of FIG.

The NA 110 may attempt to obtain application data of the GA 165 or the DA 195 at a time by a predetermined rule. Alternatively, the NA 110 may attempt to acquire application data of the GA 165 or the DA 195 by a command of a user accessed through the user interface of the NA 110.

The NA 110 may transmit a data request signal to the NSC 120, and the data request signal may be transmitted to the NGC 122 in the NSC 120 (S201). The NGC 122 transmits a data request signal, which may be transmitted to the GGC 162 of the GSC 161 or the DGC 192 of the DGC 191 through the core network 130 and the access network 140 ( Step S202).

In addition, the GGC 162 or the DGC 192 may request data of an application from the GA 165 or the DA 195 (step S203). In operation S203, the data request may be executed through a service capability layer (eg, Gateway Remote Entity Management (GREM) Capability or Device Remote Entity Management (DERM) Capability) of the GSC 161 or the DSC 191.

The GA 165 or the DA 195 receiving the data request may transmit the data of the corresponding application to the GGC 162 or the DGC 192 (step S204). In operation S204, data transmission may be performed through the service capability layer of the GSC 161 or the DSC 191.

Meanwhile, the application data to be acquired may be stored and managed by the GSC 161 or the DSC 191 in advance. In this case, steps S203 and S204 may be omitted, and the GGC 161 or the DGC 191 may acquire data from the service capability layer of the GSC 161 or the DSC 191.

The GGC 162 or the DGC 192 may transfer data to the NGC 122 through the access network 140 and the core network 130 (step S205). At this time, the data required for the NSC 120 to manage the gateway 160, the device 190, and the like, data related to performance management, configuration management, and failure management may also be used from the GGC 162 or the DGC 192 to the NGC 122. Can be delivered.

The application data received through the NGC 122 is exchanged with the corresponding NSCL 121 (step S206), and the corresponding NSCL 121 may store the application data (step S207). The NSCL 121, which stores the data, identifies the resource and, for example, checks the “accessRights” attribute, which may indicate the right to access the application data, to determine the NA 110 accessible to that application data. Can be identified.

The NSCL 121 may notify the corresponding NA 110 that data is stored (step S208). Upon receiving the notification, the NA 110 may read data stored in the NSCL 121 (step S209). The NA 110 having successfully obtained data may transmit a reception success response. The reception success response may be transmitted to the GA 165 or the DA 195 through the NGC 122, the GGC 162, the DGC 192, or the like (step S210).

In the above example, different application data requested by the plurality of NAs 110 are stored in the NSC 120, and the accessibility to each application data stored in the NSC 120 is determined by attributes in the resource.

Application data stored in the NSC 120 may be data relating to privacy. For example, in the system of FIG. 1, the M2M devices 180 and 190 may be data related to personal health information and location information. In this case, the NA 110 or a user accessing the NA 110 and using the service may have application data related to privacy accessible by a plurality of NAs 110 and may be operated by an operating entity different from the NAs 110. May not trust what is stored in the NSC 120.

3 and 4 illustrate an example of a structure of a resource that can be applied in an embodiment of the present invention.

In an embodiment of the invention, the resource has a tree structure. In the following figures, resources are shown as rectangles without rounds, and attribute information is shown as rectangles with rounds. The name of the resource or attribute information represented by <> may be replaced with any name in the process of configuring the system.

The <container> resource 300 is a resource in which data of an application is stored.

Referring to FIG. 3, a <container> resource 300 has an attribute “attribute” 310, a contentInstance 320, subscriptions 330, and a subordinate resource <privacyProfile> 340.

"Attribute" 310 may indicate an attribute of a <container> resource 300. For example, “attribute” 310 may be an expirationTime representing the time when the resource is to be deleted, an accessRightID representing the URI of an object that has permission to access the resource, searchStrings used as a key to search for the resource, CreationTime representing the creation time, lastModifiedTime representing the last change time of the resource, announceTo representing the list of SCLs to be notified when a request is made, maxNrOfInstance representing the maximum number of instances of the resource <container> 300, for all instances maxByteSize representing the maximum number of bytes allocated to the <container> resource 300, and maxInstanceAge representing the maximum lifetime of an instance of the <container> resource 300.

The contentInstances 320 resource, which is a lower resource of the <container> resource 300, may store data.

The subscription 330 resource, which is a subordinate resource of the <container> resource 300, may be used to track the usage state.

The <privacyProfile> resource 340, which is a subordinate resource of the <container> resource 300, may be used to store information for security processing of the <container> resource 300.

Referring to FIG. 4, the <privacyProfile> resource 340 includes attributes “attribute” 341, encryption 342, storage 343, routing 344, and storageTime 345, accessRights 346, and subscriptions. 347 has a lower resource.

Table 1 below describes sub-resources of the <privacyProfile> resource 340.

[Table 1]

In Table 1, Multiplicity represents the number of resources and Description represents a description of the resource.

Referring to Table 1, the accessRights resource 346 may include a <accessRight> resource, which is a child resource generated by the parent application, and the subscriptions resource 347 is a <subscription> resource, which is a child resource representing an individual subscription to the resource. It may include.

Table 2 below describes the attributes of the <privacyProfile> resource 340.

[Table 2]

In Table 2, Mandatory / Optional indicates whether attribute information is mandatory (M) or optional (O). Type indicates whether the attribute information can be read / written, RW means that read / write is possible, and RO means that only read is possible. Description represents a description of the attribute information.

In Table 2, accessRightID, creationTime, lastModifiedTime, and privacyFlag are information included in “attribute” 341. accessRightID represents the URI of an object that has permission to access the resource, creationTime represents the resource's creation time, and lastModifiedTime represents the last modified time of the resource.

The privacyFlag indicates whether data included in the <container> resource 300 requires security processing. If privacyFlag is "OFF", security processing is not required. As shown in FIG. 2, the message is processed through a general data processing process. When privacyFlag is "ON", security processing is required, and as described below, security processing is performed by checking the value of each attribute.

Attribute information encryption 342 indicates whether data should be encrypted until it is passed from the source (eg, M2M gateway 160 or M2M device 190) to the destination (eg, NA 110). It can have a value of "ON" or "OFF". If Encryption 342 has a value of “ON,” the data must remain encrypted from the origin to the destination, and storage (eg, at NSCL 121) can also be stored encrypted. Thus, data security can be maintained. If Encryption 342 has a value of "OFF", the data is not encrypted.

The attribute information storage 343 indicates whether data is to be stored in the system NSNS 121 and may have a value of “ENCRYPTED”, “DECRYTED” or “NO”. When the storage 343 has a value of "ENCRYPTED", the data is stored in the encrypted state in the NSCL 121. Thus, it is possible to prevent the third party from confirming the contents of the data. When the storage 343 has a value of “DECRYPTED”, the data is stored in the NSCL 121 in an unencrypted state. When the storage 343 has a value of "NO", data is not stored in the NSCL 121. That is, the NSCL 121 transfers the received data directly to the NA 110 without storing the received data, or transfers the received data to the NA 110 and deletes the data stored in the NSCL 121. Thus, the third party can be prevented from accessing the data.

The attribute information routing 344 indicates a transmission path of data and may have a value of “NSCL” or “NA”. If the routing 344 has a value of "NSCL", the data passes through the NSCL 121 to the NA 110. If the routing 344 has a value of “NA”, the data is passed directly to the NA 110 without passing through “NSCL”. Thus, a third party using the NSCL 121 can be prevented from accessing the data.

The attribute information storageTime 345 indicates the time when the data is stored in the NSCL 121 when the data is stored in the NSCL 121, and when the time of the storageTime 345 elapses, the data is deleted from the NSCL 121. For example, storageTime may be a value indicating one day, one week, one month, one year, or the like. For another example, storageTime may represent a time to be stored in seconds, hours, days, or the like. If the data need to be used in the NSCL 121 for the management of the system, but it is not desirable to store the data in the NSCL 121 for a long time for security reasons, the value of storageTime can be appropriately set.

The above-described <privacyProfile> resource 340 enters a sub-resource of the <container> resource that contains information of all applications. That is, even if the data is generated from the same application, different security policies can be applied to each <container>. For example, personal information generated in a specific application is not encrypted or stored in the NSCL 121 by applying a security policy, and data for management of a specific application and state management of a terminal may not be applied to a security policy.

5 illustrates a process of acquiring application data according to an embodiment.

Referring to FIG. 5, the NA 110 transmits a message requesting data of an application to the NSC 120 (S501), and the NGC 122 of the NSC 120 transmits a GGC 162 of the M2M gateway 160. Alternatively, the application data request message is transmitted to the DGC 192 of the M2M device 190 (S502), and the M2M gateway 160 or the M2M device 190 transmits the data request message to the GA 165 or the DA 195. (S503).

The GA 165 or the DA 195 generates a privacyProfile shown in FIG. 5 (S504). The GA 165 or the DA 195 determines whether the data requested by the NA 110 is data requiring privacy including personal information, and determines the required security level when the data is required for privacy. Based on this, the above-described privacyProfile is generated. Alternatively, the data request message from the NA 110 may include information on the privacyProfile to be generated, and the GA 165 or the DA 195 may generate the privacyProfile based on the information. Alternatively, the NSC 120 may determine the security level of the data to include information on the privacyProfile to be generated in the data request message, and the GA 165 or the DA 195 may generate the privacyProfile based on the information.

The GA 165 or the DA 195 transmits the requested data including the privacyProfile to the GSC 161 or the DGC 191 (S505).

The GSC 161 or the DSC 191 determines whether the "privacyFlag" of the <privacyProfile> is "ON" or "OFF" (S506). If "privacyFlag" is "OFF", steps S205 to S210 in FIG. 2 will be executed.

When the “privacyFlag” is “ON”, the GSC 161 or DSC 191 determines whether data such as “encryption”, “storage”, “routing”, and “storageTime” exist, and if so, how much the value is. Check (S507). If data such as “encryption”, “storage”, “routing”, and “storageTime” do not exist, a preset default value may be used.

In one example, the value of "encryption" may be checked first. If the value of "encryption" is "YES", data may be encrypted first regardless of subsequent transmission procedure.

In one example, the value of “routing” may be checked first. If the value of “routing” is 'NA', the values of “storage” and “storageTime”, which specify whether data is stored, whether data is encrypted or not, and how long the data is stored, cannot be checked in the NSCL 121. have.

If the value of "encryption" is "YES", the GSC 161 or the DSC 191 encrypts the data. The GSC 161 or the DSC 191 transmits data to the GGC 162 or the DGC 192 (S508).

FIG. 6 illustrates the process after S508 of FIG. 5 when the value of “routing” is “NA”.

Referring to FIG. 6, when the value of “routing” is “NA”, the GGC 162 or the DGC 192 transmits data directly to the NA 110 without passing through the NSC 120 (S601). And, in order to prevent the NSC 120 from waiting for data reception without knowing that the data is directly transmitted to the NA 110 or determining that there is a problem with the M2M gateway 160 or the M2M device 190, the GGC ( 162 or the DGC 192 transmits a response message indicating that data has been transmitted to the NA 120 to the NGC 122 (S602), and the NGC 122 transmits the response message to the NSCL 121 (S603). ). Meanwhile, the NA 110 receiving the data transmits a reception success response message to the GA 165 or the DA 195 (S604).

FIG. 7 illustrates the process after S508 of FIG. 5 when the value of “routing” is “NSCL”.

Referring to FIG. 7, when the value of “routing” is “NA”, the GGC 162 or the DGC 192 transmits data to the NGC 122 (S701), and the NGC 122 transmits the data to the NSCL 122. In step S702). The NSCL 122 checks the “privacyFlag” of the privacyProfile included in the data, and checks the “storage” and “storageTime” when the value of the “privacyFlag” is “ON” (if the data is related to privacy). (S703).

When “storage” is “ENCRYPTED”, the NSCL 122 encrypts and stores the data. If "storage" is "DECRYPTED", NSCL 122 stores the data in plain text without encrypting. If "storage" is "NO", NSCL 122 does not store data.

If "storage" is not "NO", that is, "storage" is "ENCRYPTED" or "DECRYPTED", NSCL 122 checks "storageTime". If “storageTime” is present, NSCL 122 will store the value and delete the data after the time according to the value of “storageTime” has elapsed.

Next, the NSCL 121 transfers data to the NA 110 (S704). The NA 110 receiving the data transmits a reception success response message to the GA 165 or the DA 195 (S705).

The foregoing description is merely illustrative of the technical idea of the present invention, and various changes and modifications may be made by those skilled in the art 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 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.

Claims (13)

A device application module; And
A device service capability module providing a function shared by an application of the device application module;
When the attribute of data is related to privacy, the device service capability module may include at least one of whether the data is encrypted, a transmission path of the data, whether an M2M platform stores the data, and a period during which the M2M platform stores the data. Device for identifying the one to transmit the data. The method of claim 1,
And the transmission path of the data is an application server or the M2M platform. Identifying attributes of the data;
Determining whether an attribute of the data is related to privacy;
If the attribute of the data is related to privacy, checking at least one of whether the data is encrypted, a transmission path of the data, whether an M2M platform stores the data, and a period during which the M2M platform stores the data; And
Transmitting the data. The method of claim 3, wherein
The data transmission path is a data transmission method of the device, characterized in that the application server or the M2M platform. A gateway application module; And
A gateway service capability module providing a function shared by an application of the gateway application module;
When the attribute of data is related to privacy, the gateway service capability module may include at least one of whether the data is encrypted, a transmission path of the data, whether an M2M platform stores the data, and a period during which the M2M platform stores the data. Gateway, characterized in that to transmit the data to identify one. The method of claim 5, wherein
The transmission path of the data is a gateway, characterized in that the application server or the M2M platform. Identifying attributes of the data;
Determining whether an attribute of the data is related to privacy;
If the attribute of the data is related to privacy, checking at least one of whether the data is encrypted, a transmission path of the data, whether an M2M platform stores the data, and a period during which the M2M platform stores the data; And
And transmitting the data. The method of claim 7, wherein
The data transmission path is a data transmission method of the gateway, characterized in that the application server or the M2M platform. An M2M platform that communicates with a device or gateway and an application server and provides a function shared by an application of the application server.
When the attribute of data transmitted and stored from the device or gateway is related to privacy, whether to store the data based on the information included in the data, whether to store the data encrypted or when storing the data, and when storing the data M2M platform characterized in that to check at least one of the storage period of the data, and to transmit the data to the application server. The method of claim 9,
M2M platform, characterized in that for deleting the stored data after the storage period has elapsed. Storing the data sent from the device or gateway;
Determining whether an attribute of the data is related to privacy based on information included in the data;
Determining whether or not the data is stored based on information included in the data, when the attribute of the data is related to privacy;
If it is determined that the data is to be stored, storing the data; And
And transmitting the data to an application server. The method of claim 11,
In the data storing step, when the data is stored, the data is stored with or without encryption based on the information included in the data. The method of claim 11,
When storing the data, checking a storage period of the data included in the data; And
And deleting the stored data after the storage period has elapsed.

Images