KR101807312B1 - Data Transferring Method between Device/Gateway and Network Application Server - Google Patents

Abstract

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

Description

[0001] The present invention relates to a data transferring method between a device / gateway and a 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. The data transmitted in such object communication may include data related to the privacy of the individual.

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

According to an aspect of the present invention, there is provided an information processing apparatus comprising: a device application module; And a device service capability module for providing a function shared by the application of the device application module, wherein the device service capability module transmits the data to the application server when the attribute of the data of the application is related to privacy And transmits the data to the M2M platform when the data is not related to the privacy.

Another embodiment of the present invention provides a device application module, And a device service capability module for providing a function shared by the application of the device application module, wherein the device service capability module is configured to transmit data encrypted with the data when the attribute of the data of the application is related to privacy And transmits the data to the M2M platform and transmits the data to the M2M platform when the data is not related to the privacy.

Another embodiment of the present invention is a gateway application module comprising: a gateway application module; And a gateway service capability module that provides a function shared by the application of the gateway application module and is capable of communicating with the M2M device, wherein the gateway service capability module determines whether the attribute of the application data is related to privacy And transmits the data to the application server, and transmits the data to the M2M platform when the data is not related to the privacy.

Another embodiment of the present invention is a gateway application module comprising: a gateway application module; And a gateway service capability module that provides a function shared by the application of the gateway application module and is capable of communicating with the M2M device, wherein the gateway service capability module determines whether the attribute of the application data is related to privacy Transmits the encrypted data to the M2M platform, and transmits the encrypted data to the M2M platform when the data is not related to the privacy.

Another embodiment of the present invention is a method for controlling an application, comprising: confirming an attribute of data of an application; Transmitting the data to an application server when the attribute of the data is related to privacy; And transmitting the data to the M2M platform when the attribute of the data is not related to the privacy.

Another embodiment of the present invention is a method for controlling an application, comprising: confirming an attribute of data of an application; Transmitting the encrypted data to the M2M platform when the attribute of the data is related to privacy; And transmitting the data to the M2M platform when the attribute of the data is not related to the privacy.

Another embodiment of the present invention is an M2M platform for communicating with a device, a gateway, and an application server, and providing functions shared by applications of the application server, wherein an attribute of data transmitted from and stored in the device or gateway is stored in a privacy And transmits the data to the application server when the data is related, and then deletes the data.

And, another embodiment of the present invention is a method of transmitting data, comprising: storing data transmitted from a device or a gateway; Transmitting the data to an application server; Confirming attributes of the data; And deleting the data when the attribute of the data is related to privacy.

According to the present invention described above, data related to privacy in object communication can pass through the M2M platform or pass through after encryption. Thus, the service provider can satisfy the user's need for privacy.

1 is a diagram showing an example of the structure of an M2M system to which embodiments of the present invention can be applied;
FIG. 2 is a flow chart illustrating a process of acquiring application data in the system of FIG. 1;
3 is a diagram showing an example of a structure of a resource to which embodiments of the present invention can be applied;
FIG. 4 is a flowchart illustrating a process of acquiring application data in the first embodiment of the present invention; FIG.
5 is a flowchart illustrating a process of acquiring application data in a second embodiment of the present invention;
FIG. 6 is a flowchart illustrating a process of acquiring application data in the third embodiment of the present invention. FIG.
7 is a flow chart illustrating a method of transmitting data by a GGC or DGC in a fourth embodiment of the present invention, and
8 is a flow chart illustrating a method of transmitting data by a GGC or DGC in a fifth embodiment of the present invention.

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.

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 may be applied.

Referring to FIG. 1, an entire M2M system 100 includes a network application 110, an M2M service capability (hereinafter referred to as "NSC") 120 A core network 130, an access network 140, an M2M gateway 160, a local network 170, and an M2M device M2M Device (180, 190).

The 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 that is shared by various applications. The NSC 120 may be operated by an operator other than the NA 110.

The NSC 120 is a network service capability layer (hereinafter referred to as "NSCL ") that includes a service capability (hereinafter referred to as" SC " 121). The NSCL 121 may have various SCs 122 to 127 capable of providing different functions.

The Network Generic Communication Capability (NGC) 122 is used to transmit a message between the M2M gateway 160, the M2M device 190 and the other SCs (SC1 123 to SC 127) in the NSCL 121 Lt; / RTI > NGC 122 may establish a secured tunnel session to exchange data with all SCs. The NGC 122 may perform the function of analyzing the traffic that is transmitted as needed.

The NGC 122 can send and receive data related to the application. NGC 122 also receives data related to performance management (PM), configuration management (CM), and fault management (FM) from GGC 162 or DGC 192 .

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

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 a digital subscriber line (DSL), a hybrid fiber coaxial (HFC), a power line communication (PLC), a satellite, a GSM EDGE radio access network (UAGAN), a UMTS terrestrial radio access network , Evolved 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 M2M gateway or directly to the access network 140. [

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

The M2M gateway 160 may act as a proxy for the M2M network on behalf of the connected M2M device 180. [ The M2M gateway 160 may perform processes such as authentication, authorization, registration, management, and provisioning on the side of the connected M2M device 180.

The M2M gateway 160 may include a Gateway Service Capabilities (GSC) 161 and a Gateway Application (GA) 165 . The GSC 161 provides functions shared by applications executed in the GA 165.

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

The GGC 162 can send and receive data related to the application. In addition, the GGC 162 may send data related to performance management, configuration management, and fault management to the NGC 122. [

Local network 170 to connect the M2M gateway 160 and the M2M device 180 is, for example, IEEE (Institute of Electrical and Electronics Engineers ) Personal area networks (PANs) such as 802.15.x, Zigbee, IETF (Internet Engineering Task Force) ROLL (Routing Over Low power and Lossy networks), ISA (International Society of Automation) A local area network (LAN) such as a Power Line Communication (M-BUS), a wireless M-BUS, and a KNX.

The M2M device 190 may be coupled to the direct access network 140. The M2M device 190 may perform processes such as authentication, authorization, registration, management, and provisioning. The M2M device 190 may include a Device Service Capabilities (DSC) 191 and a Device Application (DA) 195 . The DSC 191 provides functions shared by applications executed in the DA 195.

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

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

The M2M service capability layer (hereinafter referred to as "SCL") in the NA 110, the GA 165, the DA 195, and the NSC 120, the GSC 161, ) As a rule for exchanging information with each other. RESTful types are meant to follow the Representational State Transfer (REST) principle.

An important concept of REST is the presence of a resource, each represented by an identifier. To process these resources, the components of the network (e.g., NA 110, GA 165, DA 195, and NSC 120, GSC 161 in system 100 of FIG. 1) , SCL in DSC 191) may communicate via a standardized interface and exchange representations of such resources. These resources may have a tree structure.

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

- Create (C): Creates a sub resource.

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

- Update (U): writes the contents of the resource.

- Delete (D): Delete the resource.

This method can be referred to as the CRUD method. In addition to this CRUD method, application (S) of resource exchange, notification (N) of resource exchange, and execution (E) of management command / task expressed by resources can be defined.

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

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

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

The GGC 162 or the DGC 192 can request data of the application with the GA 165 or DA 195 (step S203). The data request may be executed through the service capability layer (e.g., Gateway Remote Entity Management (GREM) Capability or Device Remote Entity Management (DERM) Capability) of the GSC 161 or the DSC 191 in step S203.

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

On the other hand, 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 obtain data from the service capability layer of the GSC 161 or the DSC 191. [

The GGC 162 or the DGC 192 may transmit data to the NGC 122 through the access network 140 and the core network 130 in operation S205. Data related to performance management, configuration management, and fault management is also requested from the GGC 162 or the DGC 192 as data required for the NSC 120 to manage the gateway 160 and the device 190, ). ≪ / RTI >

The application data received via the NGC 122 is exchanged with the corresponding NSCL 121 in step S206, and the corresponding NSCL 121 can store the application data in step S207. The NSCL 121 storing the data confirms the resource and confirms the "accessRights" attribute, which can indicate, for example, the right to access the application data, and transmits an NA 110 Can be identified.

Then, the NSCL 121 can notify that the data is stored in the corresponding NA 110 (step S208). The NA 110 receiving the notification can read the data stored in the NSCL 121 (step S209). The NA 110 that successfully acquired the data can transmit a successful reception 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 example described above, the different application data requested by the plurality of NAs 110 are stored in the NSC 120, and the accessibility of each application data stored in the NSC 120 is determined by the attributes in the resource.

The application data stored in the NSC 120 may be data related to privacy. For example, in the system of FIG. 1, M2M devices 180 and 190 may be data related to individual health information, location information, and the like. In this case, a user who accesses the NA 110 or the NA 110 and uses the service can receive the application data related to privacy through a plurality of NAs 110 and can be operated by an operator other than the NA 110 Lt; RTI ID = 0.0 > NSC 120 < / RTI >

Fig. 3 shows an example of the structure of a resource that can be applied in the embodiment of the present invention.

Referring to FIG. 3, the <application> resource 300 has a tree structure. The <application> 300 stores information about the application.

Subordinate resources including "attribute" 301, Containers 302, Groups 303, accessRights 304, Subscriptions 305, and NotificationChannels 306 may be located under <application> resource 300 .

"attribute" 301 "can display the attributes of < application >

Containers 302 may be an upper resource of < container > a general resource used for exchanging data between an application and / or M2M SCL.

Groups 303 may be upper resources of group resources used to define and access groups of other resources.

accessRights 304 may indicate an access permission.

The subscription 305 can be used to track the active usage state on the parent resource.

The NotificationChannel 306 may display a set of notification channels for use by the registered application.

Subordinate to the Containers 302 is an attribute 311, container 312, containerAnnc 313, location 314, locationAnnc 315 and subscription 316 There may be resources.

The "attribute" 311 can display the attributes of < Containers >

<container> (312) is a generic resource used to exchange data between an application and / or an M2M SCL.

< containerAnnc > (313) may indicate the content of the container's activity in another SCL. &lt; containerAnnc &gt; (313) can maintain a link to the original resource.

The <location> 314 may indicate location information of the M2M entity (M2M gateway / device).

< locationAnnc > (315) may indicate the activity of the location in another SCL. < locationAnnc > (315) can maintain a link to the original resource.

The subscription 316 may be used to track the active usage state of the parent resource.

Subordinate resources including "attribute" (321), contentInstances (322), and subscriptions (323) may be located under <container>

The "attribute" 321 may indicate an attribute of < container >

The <contentInsances> 322 may represent an instance of the content in the container 312.

Hereinafter, embodiments of the present invention will be described.

1st Example

The attribute (AttributeName) in the "attribute" 301 may include 'privacyData' for distinguishing whether there is data requesting privacy among data of the application. The 'privacyData' may be 1 bit or 1 byte, which may have a value of "Yes " and" No " specifying whether or not there is data requesting privacy.

4 is a flowchart illustrating a process of acquiring application data in this embodiment.

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

The NA 110 transmits a data request signal to the NSC 120 and the data request signal can be transmitted to the NGC 122 in the NSC 120 in step S401. The NGC 122 may send a data request signal which may be delivered to the GGC 162 of the GSC 161 or the DGC 192 of the DGC 191 via the core network 130 and the access network 140 S402).

The GGC 162 or the DGC 192 may request the data of the application with the GA 165 or DA 195 (step S403). In step S403, the data request may be executed via the service capability layer of the GSC 161 or the DSC 191. [

The GA 165 or DA 195 receiving the data request can transmit data of the corresponding application to the GGC 162 or the DGC 192 in step S404. In step S404, the data transfer may be performed through the service capability layer of the GSC 161 or the DSC 191. [

On the other hand, the application data to be acquired may be previously stored and managed by the GSC 161 or the DSC 191. In this case, steps S403 and S404 may be omitted, and the GGC 161 or the DGC 191 may obtain data from the service capability layer of the GSC 161 or the DSC 191.

The GGC 162 or the DGC 192 checks the attribute of 'privacyData' in the 'attribute' 301 resource (step S405). If the attribute of 'privacyData' is set so that the data does not require privacy, the data will be transmitted as shown in FIG.

data is directly transmitted from the GGC 162 or the DGC 192 to the NA 110 without going through the NSC 120 if the attribute of the 'privacyData' is set to require privacy (S406).

A report indicating that the data has been directly transferred from the GGC 162 or the DGC 192 to the NA 110 is transmitted from the GGC 162 or the DGC 192 to the NGC 122 in step S407, (Step S408). Thus, the NSC 120 can recognize that the data has been transferred to the NA 110 without going through it.

Alternatively, if the NSC 120 knows that the application data is data requiring privacy and that data will be transferred from the GGC 162 or the DGC 192 directly to the NA 110, steps S407 and S408 are omitted, The NSC 120 may not wait for a response from the GGC 162 or the DGC 192. [

The NA 110 receiving the data may transmit a response indicating that the reception is successful to the GA 165, DA 195, GSCL, or DSCL in step S409.

In this embodiment, data related to privacy is not transmitted or stored to the NSC 120. [ Therefore, an object other than the NA 110 can not access data related to privacy.

In this embodiment, the data related to the terminal management function is transferred to the NSC 120 and stored. Thus, the NSC 120 can continue to manage the terminal.

Second Example

The attribute (AttributeName) in the "attribute" 301 may include 'privacyData' for distinguishing whether there is data requesting privacy among data of the application. The 'privacyData' may be 1 bit or 1 byte, which may have a value of "Yes " and" No " specifying whether or not there is data requesting privacy.

5 is a flowchart illustrating a process of acquiring application data in this embodiment.

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

The NA 110 transmits a data request signal to the NSC 120 and the data request signal can be transmitted to the NGC 122 in the NSC 120 in step S501. The NGC 122 may send a data request signal which may be delivered to the GGC 162 of the GSC 161 or the DGC 192 of the DGC 191 via the core network 130 and the access network 140 S502).

The GGC 162 or the DGC 192 may request the data of the application with the GA 165 or DA 195 (S503). In step S503, the data request may be executed through the service capability layer of the GSC 161 or the DSC 191. [

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

On the other hand, the application data to be acquired may be previously stored and managed by the GSC 161 or the DSC 191. In this case, steps S503 and S504 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 checks the attribute of 'privacyData' in the resource 'attribute' 301 (S505). If the attribute of 'privacyData' is set so that the data does not require privacy, the data will be transmitted as shown in FIG.

If the attribute of 'privacyData' is set so that the data requires privacy, the data is encrypted (step S506).

The encrypted data is transferred from the GGC 162 or the DGC 192 to the NGC 122 in step S507 and transferred to the NSCL 121 in step S508. The NSCL 121 stores the encrypted data (step S509).

The NSCL 121 can notify that the encrypted data is stored in the corresponding NA 110 (step S510). The NA 110 having received the notification can read the encrypted data stored in the NSCL 121 (step S511). The NA 110 that successfully acquired the data can transmit a successful reception response. The reception success response may be transmitted to the GA 165, DA 195, GSCL, or DSCL through the NGC 122, the GGC 162, the DGC 192, or the like (S512).

In this embodiment, the privacy-related data is encrypted and transmitted to the NSC 120 and stored. Therefore, an object other than the NA 110 can not access data related to privacy.

Third Example

The attribute (AttributeName) in the "attribute" 301 may include 'privacyData' for distinguishing whether there is data requesting privacy among data of the application. The 'privacyData' may be 1 bit or 1 byte, which may have a value of "Yes " and" No " specifying whether or not there is data requesting privacy.

6 is a flowchart illustrating a process of acquiring application data in this embodiment.

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

The NA 110 transmits a data request signal to the NSC 120 and the data request signal can be transmitted to the NGC 122 in the NSC 120 in step S601. The NGC 122 may send a data request signal which may be delivered to the GGC 162 of the GSC 161 or the DGC 192 of the DGC 191 via the core network 130 and the access network 140 Step S602).

The GGC 162 or the DGC 192 may request the data of the application with the GA 165 or the DA 195 (S603). In step S503, the data request may be executed through the service capability layer of the GSC 161 or the DSC 191. [

The GA 165 or DA 195 receiving the data request can transmit data of the corresponding application to the GGC 162 or the DGC 192 in step S604. In step S504, the data transmission may be performed through the service capability layer of the GSC 161 or the DSC 191. [

On the other hand, the application data to be acquired may be previously stored and managed by the GSC 161 or the DSC 191. In this case, steps S603 and S604 may be omitted and the GGC 161 or the DGC 191 may obtain data from the service capability layer of the GSC 161 or the DSC 191. [

The GGC 162 or the DGC 192 may transmit data to the NGC 122 through the access network 140 and the core network 130 in operation S605. In this case, the data may be plain text data or ciphertext data encrypted with plain text data.

The application data received via the NGC 122 is exchanged with the corresponding NSCL 121 in step S606, and the corresponding NSCL 121 can store the application data in step S607.

Then, the NSCL 121 can notify that the data is stored in the corresponding NA 110 (step S608). The NA 110 receiving the notification can read the data stored in the NSCL 121 (step S609).

At this time, the NSCL 121 checks the attribute of 'privacyData' in the 'attribute' 301 resource (step S610). If the attribute of 'privacyData' is set so that the data does not require privacy, the data stored in the NSCL 121 can be maintained.

If the attribute of 'privacyData' is set to require privacy, the NSCL 121 deletes the stored data (step S611). At this time, it is also possible that information for confirming that the data is deleted is transmitted to the NA 110.

The NA 110 that successfully acquired the data can transmit a successful reception response. The reception success response may be transmitted to the GA 165, DA 195, GSCL, or DSCL through the NGC 122, the GGC 162, the DGC 192, or the like in step S612.

Data related to privacy is transferred to and stored in the NSC 120 but data stored in the NSC 120 is deleted after data related to privacy is transferred to the NA 110. Therefore, Other entities can not access privacy related data.

Fourth Example

The attribute (AttributeName) in the "attribute" 301 may include 'privacyData' for distinguishing whether there is data requesting privacy among data of the application. The 'privacyData' may be 1 bit or 1 byte, which may have a value of "Yes " and" No " specifying whether or not there is data requesting privacy.

In addition, the attribute (AttributeName) in the "attribute" 321 may include a privacyDataType that specifies the privacy type or the transmission type of the data of the corresponding <container> 312 resource.

7 is a flowchart showing a method of transmitting data by the GGC 162 or the DGC 192 when the 'privacyData' has a value of 'Yes' or 'No'.

Referring to FIG. 7, the GGC 162 or the DGC 192 confirms the value of 'privacyData' in the 'attribute' 301 (step S701).

If the 'privacyData' is 'No', the data does not require privacy. The GGC 162 or the DGC 192 transmits the data to the NGC 122, the NSCL 121, To the NA 110 (step S702).

If 'privacyData' is 'Yes', the data requires privacy.

At this time, some of the application data may request privacy and some may not require privacy. For example, the M2M device is a terminal for measuring data from the body for e-Health, the medical data of an individual measured by the terminal is treated as being related to privacy, and data representing the state of the terminal (for example, Battery level of the battery &lt; / RTI &gt; etc.) may be treated as not related to privacy.

Alternatively, the data transmission scheme required by each part of the application data requesting privacy may be different. For example, some data may be transmitted directly to the NA 110 and some other data may be encrypted and transmitted to the NGC 122. [

If 'privacyData' is 'Yes', the GGC 162 or the DGC 192 can confirm 'privacyDataType' in the 'attribute' 321 of the <container> 312 resource in step S703.

As an example, 'privacyDataType' may be one byte which may have the values of 'NONE_PRIVACY', 'SEND_DIRECT_TO_NA', 'SEND_ENCRYPTED_TO_NSCL', 'SEND_TO_NSCL_READ_AND_DELETE'.

When the 'privacyDataType' is 'NONE_PRIVACY', the corresponding data is data that does not require privacy. The GGC 162 or the DGC 192 transmits the corresponding data to the NGC 122 ) To the NA 110 via the NSCL 121.

In the case where the 'privacyDataType' is 'SEND_DIRECT_TO_NA', the corresponding data is data requiring privacy. The GGC 162 or the DGC 192, as described in the first embodiment, To the NA 110 without passing through the NGC 122 and the NSCL 121. [

When the 'privacyDataType' is 'SEND_ENCRYPTED_TO_NSCL', the corresponding data is data requiring privacy, and the GGC 162 or the DGC 192, as described in the second embodiment, And transmits the encrypted data to the NA 110 through the NGC 122 and the NSCL 121. [

When the 'privacyDataType' is 'SEND_TO_NSCL_READ_AND_DELETE', the corresponding data is data requiring privacy, and the GGC 162 or the DGC 192, as described in the third embodiment, The NSCL 121 confirms that the 'privacyData' is 'Yes' and the 'privacyDataType' is 'SEND_TO_NSCL_READ_AND_DELETE', and the data is transferred to the NA (110) through the NGC 122 and the NSCL 121, 110 and then delete the stored data.

As described above, the GGC 162 or the DGC 192 can transmit the corresponding part of the data according to the method defined in the 'privacyDataType' (step S704).

The values of 'privacyData' and 'privacyDataType' described above are merely examples, and values according to various methods for providing privacy can be applied. For example, when the data is encrypted and transmitted directly to the NA 110, the encrypted data is transmitted to the NSCL 121, the encrypted data is transferred to the NA 110, And a value for designating the case of deleting the data.

In the present embodiment, when 'privacyData' is 'Yes', a value of 'privacyDataType' is independently set for each part of the application data, and each part of the application data is transmitted in a method based on the value of 'privacyDataType' .

Fifth Example

The attribute (AttributeName) in the "attribute" 301 may include 'privacyData' for discriminating whether there is data requesting privacy among data of the corresponding application and whether all data requesting privacy is part or not. As an example, 'privacyData' may include values of 'ALL', 'NONE', and 'PARTIALL'.

8 is a flowchart illustrating a method of transmitting data by the GGC 162 or the DGC 192 when the 'privacyData' has one of the values 'ALL', 'NONE', and 'PARTIALL'.

Referring to FIG. 6, the GGC 162 or the DGC 192 checks the value of 'privacyData' (step S801).

When 'privacyData' is 'ALL', all data is data requiring privacy, and all data can be transmitted according to a previously set method (step S802). For example, the GGC 162 or the DGC 192 may transmit data directly to the NA 110 (not via the NGC 122, the NSCL 121), as described in the first embodiment with reference to FIG. Or encrypt the data and transfer it to the NA 110 via the NGC 122, the NSCL 121, as described in the second embodiment with reference to FIG. 5, The corresponding data is transmitted to the NA 110 via the NGC 122 and the NSCL 121 and the NSCL 121 confirms that the 'privacyData' is 'ALL' as described in the embodiment, 110 and then delete the stored data.

In the case where the "privacyData" is "NONE", all the data is data that does not require privacy. The GGC 162 or the DGC 192 transmits the data to the NGC 122, NSCL (Step S803).

When "privacyData" is "PARTIALL", a part of data is data requiring privacy and a part is data requiring no privacy.

If 'privacyData' is 'PARTIALL', the GGC 162 or the DGC 192 can check 'privacyDataType' in the 'attribute' 321 of the <container> 312 resource in step S804.

As an example, 'privacyDataType' may be one byte which may have the values of 'NONE_PRIVACY', 'SEND_DIRECT_TO_NA', 'SEND_ENCRYPTED_TO_NSCL', 'SEND_TO_NSCL_READ_AND_DELETE'.

When the 'privacyDataType' is 'NONE_PRIVACY', the corresponding data is data that does not require privacy. The GGC 162 or the DGC 192 transmits the corresponding data to the NGC 122 ) To the NA 110 via the NSCL 121.

In the case where the 'privacyDataType' is 'SEND_DIRECT_TO_NA', the corresponding data is data requiring privacy. The GGC 162 or the DGC 192, as described in the first embodiment, To the NA 110 without passing through the NGC 122 and the NSCL 121. [

When the 'privacyDataType' is 'SEND_ENCRYPTED_TO_NSCL', the corresponding data is data requiring privacy, and the GGC 162 or the DGC 192, as described in the second embodiment, And transmits the encrypted data to the NA 110 through the NGC 122 and the NSCL 121. [

When the 'privacyDataType' is 'SEND_TO_NSCL_READ_AND_DELETE', the corresponding data is data requiring privacy, and the GGC 162 or the DGC 192, as described in the third embodiment, The NSCL 121 confirms that the 'privacyData' is 'Yes' and the 'privacyDataType' is 'SEND_TO_NSCL_READ_AND_DELETE', and the data is transferred to the NA (110) through the NGC 122 and the NSCL 121, 110 and then delete the stored data.

As described above, the GGC 162 or the DGC 192 can transmit the corresponding part of the data according to the method specified in the 'privacyDataType' (step S805).

In the present embodiment, when 'privacyData' is 'ALL', all of the application data is transmitted in a predetermined manner, and when 'privacyData' is 'PARTIAL', the value of 'privacyDataType' Independently configured and each part of the application data is transmitted in a manner that is based on the value of 'privacyDataType'.

In the case of the fourth embodiment described above, when the application data is related to privacy, "privacyDataType" is confirmed in "attribute" (312) for all parts of the data. However, in the case of this embodiment, when all of the application data is related to privacy PrivacyDataType " in the "attribute" 312, thus omitting the unnecessary 'privacyDataType' attribute checking procedure.

The values of 'privacyData' and 'privacyDataType' described above are merely examples, and values according to various methods for providing privacy can be applied. For example, when the data is encrypted and transmitted directly to the NA 110, the encrypted data is transmitted to the NSCL 121, the encrypted data is transferred to the NA 110, And a value for designating the case of deleting the data.

In the embodiments described above, the value of the 'privacyData' and / or the 'privacyDataType' indicator may be a preset value. Alternatively, the values of the 'privacyData' and / or 'privacyDataType' directives may be dynamically set when the NA 110 requests data for the application.

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 scope of protection of the present invention should be construed according to the following claims, and all technical ideas within the scope of equivalents should be construed as falling within the scope of the present invention.

Claims (20)

Device application module; And
And a device service capability module for providing a function shared by the application of the device application module,
Wherein the device service capability module transmits the data to the application server when the attribute of the application data is related to privacy and transmits the data to the M2M platform when the attribute is not related to the privacy,
Wherein the M2M platform receives a report that the data has been transmitted directly to the application server if the attribute of the data is related to privacy. The method according to claim 1,
Wherein the device service capability module sends a portion of the data related to privacy to the application server when the attribute of a portion of the data of the application is related to privacy. Device application module; And
And a device service capability module for providing a function shared by the application of the device application module,
Wherein the device service capability module transmits data encrypted with the data to the M2M platform when the attribute of the data of the application is related to privacy and transmits the data to the M2M platform when the attribute is not related to privacy,
The M2M platform notifies the application server of information that the data encrypted with the data is stored in the M2M platform when the attribute of the data relates to privacy and the application server reads the encrypted data stored in the M2M platform . The method of claim 3,
Wherein the device service capability module sends data to the M2M platform that encodes a portion of the data related to privacy when the attribute of a portion of the application's data is privacy related. Confirming an attribute of data of the application;
Transmitting the data to an application server when the attribute of the data is related to privacy; And
And transmitting the data to the M2M platform when the attribute of the data is not related to privacy,
Wherein the M2M platform receives a report that the data has been transmitted directly to the application server when the attribute of the data is related to privacy. Confirming an attribute of data of the application;
Transmitting the data to the M2M platform if the attributes of the data are not entirely related to privacy;
Confirming an attribute of a part of the data when all or a part of the attributes of the data are related to privacy;
Transmitting a portion of the corresponding data to an application server when the attribute of the portion of the data is related to privacy; And
If the attribute for the portion of the data is not related to privacy, transmitting the portion of the corresponding data to the M2M platform,
Wherein the M2M platform receives a report that the data has been transmitted directly to the application server if the attribute for the portion of the data is related to privacy. Confirming an attribute of data of the application;
Transmitting the encrypted data to the M2M platform when the attribute of the data is related to privacy; And
And transmitting the data to the M2M platform when the attribute of the data is not related to privacy,
The M2M platform notifies the application server of information that the data encrypted with the data is stored in the M2M platform when the attribute of the data relates to privacy and the application server reads the encrypted data stored in the M2M platform The method comprising: Confirming an attribute of data of the application;
Transmitting the data to the M2M platform if the attributes of the data are not entirely related to privacy;
Confirming an attribute of a part of the data when all or a part of the attributes of the data are related to privacy;
Transmitting to the M2M platform data encrypted with a portion of the corresponding data when the attribute of the data portion is related to privacy; And
If the attribute for the portion of the data is not related to privacy, transmitting the portion of the corresponding data to the M2M platform,
Wherein the M2M platform informs the application server that the encrypted data is stored in the M2M platform when the attribute of the data part is related to privacy, and the application server reads the encrypted data stored in the M2M platform The data transmission method comprising the steps of: A gateway application module; And
And a gateway service capability module capable of providing a function shared by the application of the gateway application module and communicating with the M2M device,
Wherein the gateway service capability module transmits the data to the application server when the attribute of the data of the application is related to privacy and transmits the data to the M2M platform when the attribute is not related to the privacy,
Wherein the M2M platform receives a report that the data has been transmitted directly to the application server if the attribute of the data is related to privacy. 10. The method of claim 9,
Wherein the gateway service capability module transmits a portion of the data related to privacy to the application server when a property of a part of the data of the application is related to privacy. A gateway application module; And
And a gateway service capability module capable of providing a function shared by the application of the gateway application module and communicating with the M2M device,
Wherein the gateway service capability module transmits data encrypted with the data to the M2M platform when the attribute of the data of the application is related to privacy and transmits the data to the M2M platform when the attribute is not related to the privacy,
The M2M platform notifies the application server of information that the data encrypted with the data is stored in the M2M platform when the attribute of the data relates to privacy and the application server reads the encrypted data stored in the M2M platform To the gateway. 12. The method of claim 11,
Wherein the gateway service capability module transmits to the M2M platform data enciphering a portion of the data related to privacy when an attribute of a part of the data of the application is related to privacy. Confirming an attribute of data of the application;
Transmitting the data to the M2M platform if the attributes of the data are not entirely related to privacy;
Transmitting the data to an application server when the attribute of the data is related to privacy; And
And transmitting the data to the M2M platform when the attribute of the data is not related to privacy,
Wherein the M2M platform receives a report that the data has been transmitted directly to the application server when the attribute of the data is related to privacy. Confirming an attribute of data of the application;
Transmitting the data to the M2M platform if the attributes of the data are not entirely related to privacy;
Confirming an attribute of a part of the data when all or a part of the attributes of the data are related to privacy;
Transmitting a portion of the corresponding data to an application server when the attribute of the portion of the data is related to privacy; And
If the attribute for the portion of the data is not related to privacy, transmitting the portion of the corresponding data to the M2M platform,
Wherein the M2M platform receives a report that the data has been sent directly to the application server if the attribute for the portion of the data is related to privacy. Confirming an attribute of data of the application;
Transmitting the encrypted data to the M2M platform when the attribute of the data is related to privacy; And
And transmitting the data to the M2M platform when the attribute of the data is not related to the privacy,
The M2M platform informs the application server that the data encrypted with the data is stored in the M2M platform when the attribute of the data is related to privacy, and the application server transmits the encrypted data stored in the M2M platform to the gateway Data transmission method. Confirming an attribute of data of the application;
Transmitting the data to the M2M platform if the attributes of the data are not entirely related to privacy;
Confirming an attribute of a part of the data when all or a part of the attributes of the data are related to privacy;
Transmitting to the M2M platform data encrypted with a portion of the corresponding data when the attribute of the data portion is related to privacy; And
And transmitting the portion of the corresponding data to the M2M platform when the attribute for the portion of the data is not related to the privacy,
Wherein the M2M platform informs the application server that the encrypted data is stored in the M2M platform when the attribute of the data part is related to privacy, and the application server reads the encrypted data stored in the M2M platform A data transmission method of the gateway. An M2M platform for communicating with a device or gateway and an application server and providing functions shared by applications of the application server,
If the attribute of data transmitted from the device or gateway is related to privacy, the data is deleted after transmitting the data to the application server. If the attribute of the data transmitted to the application server is related to privacy, Wherein only the application server can access the M2M platform. 18. The method of claim 17,
And deletes a portion of the data related to the privacy of the number of data transmitted to the application server when the attribute of a part of the data transmitted from the device or the gateway is related to privacy. Storing data transmitted from a device or a gateway;
Transmitting the data to an application server;
Confirming attributes of the data; And
And deleting the data if the attribute of the data is related to privacy,
Wherein if the attribute of the data transmitted to the application server is related to privacy, the data can be accessed only by the application server. Storing data transmitted from a device or a gateway;
Transmitting the data to an application server;
Confirming attributes of the data;
Confirming an attribute of a part of the data when all or a part of the attributes of the data are related to privacy; And
And deleting a portion of the corresponding data when the attribute for the portion of the data is related to privacy,
Wherein if the attribute of the portion of data transmitted to the application server is related to privacy, the portion of the data is accessible only to the application server.

Images