REAL-TIME IoT DATA SHARING SYSTEM SUPPORTING ATTRIBUTE-BASED ACCESS CONTROL AND METHOD THEREOF

Abstract

An IoT device according to an embodiment encrypts IoT data using a peripheral device and transmits the IoT data to a server, and a user device requests and obtains necessary IoT data from the server, thereby achieving real-time IoT data sharing. The IoT device performs only relatively low-performance operation of attribute-based encryption to encrypt IoT data collected through a sensor and outsources the remaining high-performance operations of attribute-based encryption to the peripheral device providing external communication network connection to the IoT device to generate a final ciphertext. A user device generates an attribute bloom filter using an access policy thereof, requests and obtains IoT data encrypted according to attribute-based encryption. A cloud server receives and stores IoT data encrypted by the IoT device and the peripheral device according to attribute-based encryption and transmits IoT data retrieved using the attribute bloom filter as a query to the user device.

Description

BACKGROUND OF THE INVENTION

Field of the Invention

The present invention relates to a system for sharing real-time IoT data, and more specifically, to a real-time IoT data sharing system that supports attribute-based access control.

Description of the Related Art

Data collected in real time from Internet of Things (IoT) devices can be transmitted to other electronic devices through the Internet and used in various ways. For example, when IoT data is encrypted and transmitted to a cloud server in order to allow an owner who has collected the IoT data and a user who needs the IoT data to share the IoT data, the cloud server can request that the owner generate a re-encryption key at the request of the user, convert the encrypted IoT data such that only the user can decrypt the same using the re-encryption key, and transmit the converted IoT data to the user. However, if the number of users requiring IoT data increases, it is difficult to share IoT data in real time due to the problem of performing complex encryption operations corresponding to the number of users because IoT devices have low computational performance.

SUMMARY OF THE INVENTION

According to embodiments, an IoT device that outsources some high-performance operations of an attribute-based encryption technique to a peripheral device in order to share IoT data in real time can be provided.

According to embodiments, a server that stores encrypted IoT data, retrieves IoT data using an attribute bloom filter as a query, and provides the IoT data to a legitimate consumer can be provided.

According to embodiments, a user device that generates an attribute bloom filter using attributes of an access policy thereof, transmits the attribute bloom filter to a server to request IoT data, and obtains IoT data retrieved using an attribute bloom filter as a query can be provided.

In accordance with an aspect of the present invention, the above and other objects can be accomplished by the provision of an IoT device including at least one sensor, which is configured to collect IoT data at regular intervals through the at least one sensor, to generate a partially encrypted intermediate ciphertext by performing at least some operations of attribute-based encryption on the IoT data, and to transmit the intermediate ciphertext to a peripheral device in order to request remaining operations of attribute-based encryption for the intermediate ciphertext.

In accordance with another aspect of the present invention, there is provided an electronic device including a communication interface, which is configured to provide external network communication connection to an IoT device using the communication interface, to receive data and an encryption request for the data from the IoT device, to generate a ciphertext by performing some operations of attribute-based encryption on the data in response to the encryption request, and to transmit the ciphertext to a server.

In accordance with a further aspect of the present invention, there is provided an electronic device configured to encrypt attributes constituting an access policy with a group key and create an attribute bloom filter using the encrypted access policy, to transmit the attribute bloom filter to a server to request IoT data, to receive a ciphertext searched by using the attribute bloom filter as a query and an attribute set for the ciphertext from the server, and to obtain IoT data by decrypting the ciphertext using the group key and a private key.

Other aspects, features, and advantages other than those described above will become apparent from the following drawings, claims, and detailed description of the invention.

According to embodiments, it is possible to safely transmit data to multiple receivers through one-time encryption using an attribute-based encryption technique in a system sharing IoT data.

According to embodiments, it is possible to share IoT data with consumers (receivers) through a server in real time by performing an attribute-based encryption operation that requires relatively low performance by an IoT device and performing attribute-based encryption operation that requires relatively high performance by a peripheral device in a system sharing IoT data.

According to embodiments, when a consumer encrypts the attribute of his/her access policy with a group key shared with a device that generates IoT data and requests encrypted IoT data from a server using an attribute bloom filter generated using the access policy, the server transmits a ciphertext retrieved using an attribute bloom filter as a query to the consumer, to thereby provide IoT data only to the legitimate consumer without leaking information on the ciphertext.

BRIEF DESCRIPTION OF THE DRAWINGS

The above and other objects, features and other advantages of the present invention will be more clearly understood from the following detailed description taken in conjunction with the accompanying drawings, in which:

FIG. 1 illustrates a network environment including a system for sharing IoT data according to an embodiment.

FIG. 2 is a sequence diagram showing a procedure in which the system for sharing IoT data according to an embodiment shares IoT data with a user device.

FIG. 3 is a table showing definitions of variables used in a method of sharing IoT data according to an embodiment.

FIG. 4 is a flowchart of a protocol for sharing IoT data in the system for sharing IoT data according to an embodiment.

FIG. 5 is a sequence diagram illustrating an IoT data storage protocol according to an embodiment.

FIG. 6 is a sequence diagram illustrating a data access protocol of a user device according to an embodiment.

FIG. 7 is a flowchart of a method in which an IoT device shares IoT data according to an embodiment.

FIG. 8 is a flowchart of a method in which a peripheral device shares IoT data according to an embodiment.

FIG. 9 is a flowchart of a method in which a user device shares IoT data according to an embodiment.

DETAILED DESCRIPTION OF THE INVENTION

Hereinafter, embodiments will be described in detail with reference to the accompanying drawings. However, the scope of rights is not restricted or limited by these embodiments. Like reference numerals in each figure indicate like elements.

The terms used in the description below have been selected as general and universal ones in the related technical field, but there may be other terms depending on the development and/or change of technology, the preference of those skilled in the art, etc. Therefore, the terms used in the following description should not be understood as limiting technical ideas, but should be understood as exemplary terms for describing embodiments.

In addition, in a specific case, there are also terms arbitrarily selected by the applicant, and in this case, the detailed meaning will be described in the corresponding description section. Therefore, the terms used in the following description should be understood based on the meanings of the terms and the contents throughout the specification, not simply the names of the terms.

FIG. 1 illustrates a network environment including a system 100 for sharing IoT data according to an embodiment. The system 100 for sharing IoT data may include an IoT device 110 and a peripheral device 120 located around the IoT device 110. In one embodiment, the system 100 for sharing IoT data may encrypt data collected from the IoT device 110 according to attribute-based encryption (ABE) and transmit the data to a server 200. Attribute-based encryption is a public key encryption method and can encrypt data using an attribute. Decryption can be performed when attributes assigned to a ciphertext match attributes of a private key. Attribute-based encryption enables fine-grained access control because only specific receivers can access data through attribute assignment. Attribute-based encryption (ABE) includes ciphertext-policy (CP)-ABE and key-policy (KP)-ABE. The CP-ABE is a method in which an access policy composed of attributes is assigned to a ciphertext and an attribute set is assigned to a decryption key. On the other hand, KP-ABE is a method in which an attribute set is assigned to a ciphertext and an access policy is assigned to a decryption key. In one embodiment, the system 100 for sharing IoT data and a user device 300 may perform data encryption/decryption using KP-ABE in which an attribute set is assigned to a ciphertext. Since a ciphertext according to KP-ABE includes an attribute set used to encrypt data, and attributes represent information on the data of the ciphertext, information on the original data may be leaked. In one embodiment, the system 100 for sharing IoT data prevents data leakage by symmetrically encrypting attributes included in a ciphertext using a group key. The IoT device 110 may encrypt attributes of IoT data using the group key, and the user device 300 may encrypt attributes constituting an access policy thereof with the group key. The IoT device 110 may transmit the encrypted IoT data and the encrypted attribute set to the server 200 through the peripheral device 120, and the user device 300 may generate an attribute bloom filter using the encrypted access policy and transmit the attribute bloom filter to the server 200 to request IoT data. The server 200 may retrieve attribute sets of a plurality of pieces of stored IoT data by using the attribute bloom filter as a query and transmit encrypted IoT data corresponding to the matched attribute set to the matched user device 300. Since the server 200 cannot ascertain the group key shared by the IoT device 110 and the user device 300, the server 200 can act as a broker for data sharing without leakage of IoT data.

The IoT device 110 may detect data (e.g., human heartbeat) therearound through a sensor (e.g., an electrocardiogram sensor) at the end of the system 100 for sharing IoT data and share the detected data with another electronic device (e.g., user device 300). In one embodiment, the IoT device 110 may encrypt IoT data together with the peripheral device 120. For example, the IoT device 110 with low computational performance may outsource some operations of an encryption process according to attribute-based encryption to the peripheral device 120 with relatively high computational performance. The peripheral device 120 may be located around the IoT device 110 and serve as a path connecting the IoT device 110 to the external Internet. In one embodiment, the peripheral device 120 may provide resources necessary for the IoT device 110 to encrypt data. In terms of providing resources for encryption operation, the peripheral device 120 may be regarded as a security agent (SA). In various embodiments, the peripheral device 120 has better performance than the IoT device 110 and may be, for example, a router, a base station, or a roadside device. Attribute-based encryption includes a multiplication operation, an exponential operation, and a bilinear pairing operation, and the exponential operation and the bilinear pairing operation require a large amount of computation. Since the IoT device 110 has low power and low computational performance, it takes a long time to execute operations and it is difficult to process data in real time and transmit the same to the server 200 if all operations of attribute-based encryption are performed. In one embodiment, the IoT device 110 may perform only some operations of attribute-based encryption based on edge-computing and outsource a process including an exponential operation and a bilinear pairing operation requiring a relatively large amount of computation to the peripheral device 120.

The user device 300 may serve as a consumer that requests and obtains necessary IoT data from the server 200 to utilize the IoT data. The user device 300 may obtain/decrypt only desired data by receiving a private key from a trust authority (TA) 400 according to definition of an access policy. In one embodiment, the user device 300 may use an attribute bloom filter as a query in order to check whether an attribute set encrypted in a ciphertext in which IoT data has been encrypted according to attribute-based encryption and the private key of the data receiver (user device 300) match each other. A bloom filter is a probabilistic data structure used to test whether a set includes an element. The bloom filter includes several blocks, each block being composed of one bit and represented by a value of 0 or 1, to test whether an element is present in a set. In the Garbled bloom filter, one block is composed of several bits, and data stored in the bloom filter can be recovered. An access policy or an attribute set is included in a ciphertext according to attribute-based encryption, and a bloom filter for the access policy or attribute set may be generated. The IoT device 110 according to an embodiment may encrypt an attribute set for attributes of IoT data using a group key and transmit the encrypted attribute set to the server 200 through the peripheral device 120, and the user device 300 according to an embodiment may encrypt the access policy included in the private key generated according to KP-ABE with the group key, generate an attribute bloom filter, and transmit the attribute bloom filter to the server 200. The server 200 may query the encrypted attribute set generated by the IoT device 110 and the attribute bloom filter generated by the user device 300, and if they match, ascertain that the attribute set of the ciphertext and the access policy of the private key match each other. The receiver who succeeds in matching can decrypt the ciphertext using the private key. Since the process of generating and querying the attribute bloom filter includes only hash function operation, it requires a small amount of computation and enables rapid computation.

The server 200 may store encrypted IoT data using, for example, a cloud server. The server 200 may serve as a broker for retrieving stored IoT data for IoT data desired by a user and transmitting the IoT data in response to a user request. The server 200 may query attribute bloom filters created and transmitted by a plurality of user devices for necessary data thereof with respect to data attributes of a ciphertext, and transmit matching IoT data to each user device. Since only the system 100 for sharing IoT data and the user device 300 have a group key for IoT data, the server 200 only knows some information (attribute bloom filter) on the ciphertext and cannot decrypt the ciphertext, and thus security can be maintained.

The trust authority (TA) 400 may provide system initialization and authorization for entities. The TA 400 may provide device authentication for the IoT device 110 during an initial construction process. The TA 400 may generate parameters for the system through a setting process and distribute encryption keys suitable for respective entities (e.g., the IoT device 110 and the user device 300).

A key management center (KMC) 500 may periodically update and manage a group key G shared by the IoT device 110 and the user device 300.

FIG. 2 is a sequence diagram showing a procedure in which the system for sharing IoT data according to an embodiment shares IoT data with a user device. The system 100 for sharing IoT data may encrypt some of IoT data collected by the IoT device 110, generate a final ciphertext in the peripheral device 120, and share the final ciphertext with the user device 300 through the server 200.

In step S201, the IoT device 110 may collect data at regular intervals using a sensor. In various embodiments, the IoT device 110 may include various sensors, and the IoT device 110 may operate in a fixed position or may be movable. The IoT device 110 may perform primary encryption on the collected sensor data according to attribute-based encryption. For example, the IoT device 110 may perform some operations including only relatively simple operations in attribute-based encryption. The IoT device 110 may generate an attribute set obtained by symmetrically encrypting attributes of IoT data using a group key.

In step S202, the IoT device 110 may transmit the primarily encrypted data to the peripheral device 120. The IoT device 110 may transmit the encrypted attribute set to the peripheral device 120 along with the encrypted data.

In step S203, the peripheral device 120 may receive the data primarily encrypted according to attribute-based encryption and perform secondary encryption according to attribute-based encryption to generate a final ciphertext. The peripheral device 120 may perform a communication function for connecting to the external Internet, and may perform relatively high-performance computation compared to the IoT device 110. The peripheral device 120 may be, for example, a router, and may perform remaining operations of attribute-based encryption on the received data.

In step S204, the peripheral device 120 may transmit the final ciphertext and the attribute set for the ciphertext to the server 200.

In order to request desired IoT data, the user device 300 may encrypt attributes constituting an access policy included in a private key thereof using the group key and generate an attribute bloom filter (ABF) for the encrypted access policy in step S205, and request the desired IoT data by transmitting the attribute volume filter (ABF) to the server 200 in step S206.

In step S207, the server 200 may retrieve stored encrypted IoT data for an attribute set of matched IoT data using the attribute bloom filter (ABF) as a query. Since the encrypted attribute set and the attribute bloom filter using the encrypted access policy are compared, the server 200 can serve as a broker without the need to ascertain (decrypt) the encrypted IoT data.

In step S208, the server 200 may transmit a matched IoT data ciphertext to the user device 300 that has requested the IoT data.

In step S209, the user device 300 may decrypt the received ciphertext using the private key according to attribute-based encryption.

FIG. 3 is a table showing variables used when IoT data is encrypted according to attribute-based encryption according to an embodiment and definitions thereof. In the present disclosure, variables and descriptions (definitions) of the variables are first described in the table of FIG. 3 in order to describe embodiments. Variables mentioned in the present disclosure can be interpreted in detail through the description of FIG. 3.

FIG. 4 is a flowchart of a protocol for sharing IoT data in the system for sharing IoT data according to an embodiment.

In step S401, the TA 400 may initialize the system by setting parameter values for performing the protocol.

In step S402, each entity may set security through the TA 400. Each entity (e.g., the IoT device 110, peripheral device (SA) 120, server 200, and user device 300) may transmit an ID to the TA for the entire system for sharing IoT data, and register with the TA to receive parameters necessary in a process of sharing IoT data.

In step S403, the IoT device 110 and the peripheral device (SA) 120 may exchange keys for authentication before transmitting IoT data. For example, the IoT device 110 may exchange key values necessary for mutual authentication in order to outsource a part of data encryption to the peripheral device 120 in advance.

In step S404, mutual authentication with the peripheral device (SA) 120 for the movable IoT device 110 may be established. As the mobile IoT device 110 such as a vehicle or a smartphone moves, the peripheral device (SA) 120 for Internet connection may be continuously changed. The IoT device 110 needs to rapidly authenticate with the peripheral device 120 to enable real-time data sharing. A handover process at the time of moving from a previous peripheral device 120 to the next peripheral device 120 may be set in advance. In various embodiments, various methods that can be used for handover between the mobile IoT device 110 and the peripheral device (SA) 120 for communication establishment may be applied. For example, the IoT device 110 may use a secure domain-based handover ReHand for rapid mutual authentication with respect to the peripheral device 120.

In step S405, mutual authentication is performed between the IoT device 110 and the peripheral device 120 to share IoT data, and the IoT device 110 and the peripheral device 120 encrypt the IoT data together and transmit the encrypted IoT data to the server 200. The IoT device 110 collects data through a sensor, and the IoT device 110, the peripheral device (SA) 120, and the server 200 perform mutual authentication using keys exchanged in system initialization settings. The IoT device 110 may randomly select a symmetric key and symmetrically encrypts the IoT data to create ED=(Data). The IoT device 110 may generate an intermediate ciphertext by encrypting the symmetric key with an algorithm .

The algorithm includes some operations of attribute-based encryption, and may include multiplication and subtraction operations requiring a relatively small amount of computation. The algorithm can partially encrypt data M for an attribute set S using a previously calculated MC. The IoT device 110 may symmetrically encrypt the attribute set S of IoT data using a key K_Group received from the KMC 500 to generate . The IoT device 110 may transmit ED obtained by symmetrically encrypting the IoT data, the intermediate ciphertext MC′, and the encrypted attribute set to the peripheral device (SA) 120. The peripheral device (SA) 120 may generate a final ciphertext CT= by performing the remaining operations of attribute-based encryption using an algorithm on the intermediate ciphertext MC′. The peripheral device (SA) 120 may transmit the symmetric ciphertext ED, the final ciphertext CT, and the encrypted attribute set to the server 200. The server 200 may store the symmetric ciphertext ED, the final ciphertext CT, and the encrypted attribute set received from the peripheral device (SA) 120 in the cloud server. This step will be described in detail in FIG. 5.

In step S406, the user device 300 may perform mutual authentication and data request for the server 200 for IoT data access and may receive IoT data. The user device 300 and the server 200 may authenticate each other prior to IoT data request and transmission. The user device 300 may perform symmetric encryption

$\left({𝔸}_{C_n}^{\mathrm{CRC}}=E_{K_{\mathrm{Group}}}\left({𝔸}_{C_n}\right)\right)$

on an access policy included in the private key thereof using the key K_Group. The key K_Group is received from the KMC 500 and is shared with the IoT device 110, and the server 200 does not know the key K_Group. The user device 300 may generate an attribute bloom filter for the encrypted access policy using an algorithm ABFBuild and transmit the attribute bloom filter to the server 200 to request necessary IoT data. The server 200 may retrieve suitable IoT data be performing

$\mathrm{ABFQuery}\left({\mathrm{ABF}}_{{𝔸}_{C_n}^{\mathrm{CRC}}}·S_{\mathrm{enc}}\right)$

on the stored in the cloud server using the received attribute bloom filter as a query. The server 200 may transmit for which TRUE is obtained as a result of ABFQuery to the user device 300. At the time of transmitting , the server 200 may transmit along with the symmetric ciphertext ED and the final ciphertext CT with respect to to the user device 300. The user device 300 may decrypt the received with the key K_Group to obtain an attribute set S of IoT data. The user device 300 may obtain the symmetric key by using Decrypt for the private key, the final ciphertext CT, and the attribute set S. The user device 300 may obtain the IoT data by decrypting the symmetric ciphertext ED using the symmetric key . This step will be described in detail in FIG. 6.

FIG. 5 is a sequence diagram illustrating an IoT data storage protocol according to an embodiment. When the IoT device 110 primarily performs some operations of attribute-based encryption on IoT data to generate an intermediate ciphertext and transmits the intermediate ciphertext to the peripheral device 120, the peripheral device 120 may perform the remaining operations of attribute-based encryption on the intermediate ciphertext to generate a final ciphertext and transmit the final ciphertext to the server 200 to store the IoT data. Prior to description of each step of FIG. 5, functions used in the IoT data storage protocol will be described first.

The IoT data storage protocol of an embodiment may outsource a complex operation to the peripheral device (SA) 120 according to encryption outsourced key-policy attribute-based encryption (EO-KP-ABE). An access structure is composed of three components such as =. A is a l×m matrix, and ρ is a function mapped to each row A_i of A with the attribute name {att₁ . . . att_n}. Each att_k=ρ(i) has an attribute value included in an attribute value set T=. An attribute set S for encrypted data can be defined as S=, and each value is an attribute value of att_k.

A setup function Setup can be defined as Setup. The setup function Setup can generate a bilinear group having for different primes by executing . and _T are multiplicative cyclic groups for N=p₁p₂p₃ and a bilinear map . In addition, is a randomly selected value. The setup function Setup outputs a public key PK= and a master private key MSK= of the system.

A key generation function can be defined as KeyGen (PK.MSK.=(A.ρ.T)) KeyGen generates a private key corresponding to the access structure of each user device for the user device. Any column vector in which the first row is may be selected. For each , Q_i can represent an attribute set . For each row A_i, may be selected by increasing X₃ by an arbitrary power, and may be randomly selected. The key generation function calculates and outputs a secret key

An offline encryption function OfflineEnc can be defined as OfflineEnc(PK). OfflineEnc can select a random number set K=. OfflineEnc calculates AC= and outputs MC=.

A primary attribute-based encryption function can be defined as . partially encrypts a message M for an attribute set S using a previously calculated MC. selects, , calculates AC′=M·AC=M· S′=, and outputs MC′=.

A secondary attribute-based encryption function can be defined as (PK.MC′). calculates C=AC′. , and outputs CT=.

A decryption function Decrypt can be defined as Decrypt. Decrypt outputs M if S satisfies an authenticated set . First, it finds a set , and calculates if S satisfies . can be calculated as . Decrypt outputs FALSE (−) if it cannot find . Otherwise, it calculates

${\tilde{D}}_i=D_i\prod _{j\in Q_i}{D}_{i,j}^n={g^{A_i,n}\left(h_0\sum _{j=1}^n{h}_j^n\right)}^r{R}_i\sum _{j=1}^n{R}_{i,j}^n$

for each i ∈ . In addition, it calculates

$e\left(C_0,\prod _{i\in ℐ}{\tilde{D}}_i^{\omega }\right)/e\left(C_1·\prod _{i\in ℐ}{D}_i^{\omega }\right)={e\left(g·g\right)}^{\mathrm{ns}}$

and outputs M=C/. Hereinafter, the IoT device 110 may be referred to as D_i, the peripheral device 120 may be referred to as SA_t, and the server 200 may be referred to as Br.

In step S501, D_i may select constants n₁ and n₂, calculate AU₁=Hn₁, AU₂=HHn₂, σ₁=∥n₂, and σ₂=|n₂), and send }to SA_t.

In step S502, SA_t may retrieve stored Ver_Di through TID_Di included in the message. SA_t obtains n₁= and checks whether σ₁H∥n₁. If checking passes, SA_t calculates AU′₂=AU₂:. SA_t randomly selects a constant , and calculates and . SA_t may transmit including some values received from D_i to Br.

In step S503, Br may retrieve using and obtain and . Br checks whether and . If either of two fails, then Br stops the above step. Otherwise, if both pass, Br calculates SK_IB=H, =H, and =H. Then, Br transmits to SA_t.

In step S504, checks SA_t whether . If checking passes, SA_t calculates and transmits to D_i.

In step S505, D_i checks whether , and if it is, calculates SK_IB =H. Then, D_i checks whether , and if checking passes, calculates =, and replaces stored with . Then, it generates a symmetric key for encrypting Data, which is IoT data that D_i intends to share, and calculates ED=(Data). In addition, D_i generates MC′ using . Then, D_i calculates = and . After calculating , D_i transmits to .

In step S506, SA_t calculates = and checks whether . If checking passes, SA_t calculates =, replaces stored with , and replaces stored with . SA_t calculates = and transmits to Br.

In step S507, Br calculates = and checks whether =. If checking passes, Br replaces stored with . Then, Br calculates and stores in a storage space of the server.

FIG. 6 is a sequence diagram illustrating a data access protocol of a user device according to an embodiment. The user device 300 may perform mutual authentication first and obtain data satisfying an access policy , from the server 200. Hereinafter, the server 200 may be referred to Br and the user device 300 may be referred to as . Prior to description of each step of FIG. 6, functions used in the data access protocol will be described. According to the data access protocol of an embodiment, since attributes of data are encrypted with a group key K_Group of the protocol, the server 200 serving as a broker cannot ascertain the attributes of the data. The server 200 cannot compare attributes with an access policy of a consumer. In an embodiment, the server 200 may use an attribute bloom filter in order to check a hidden attribute value with relatively little computation. If the user device 300 generates an attribute volume filter (ABF) for the access policy included in the private key thereof through a function ABFBuild and transmits the attribute volume filter to the server 200, the server 200 may find a ciphertext satisfying the access policy by executing a function ABF Query on the received ABF and encrypted attributes stored in a storage server.

The function ABFBuild can be defined as ABFBuild(. The function ABFBuild generates a vacant ABF composed of blocks B_ABF. Here, each block is composed of λ-bits. The function ABFBuild connects an attribute name ρ(i) corresponding to the i-th row of A and an attribute value as one element . The function ABFBuild randomly selects J−1 λ-bit string in order to put each element e_i in ABF, and calculates . The function ABFBuild hashes as using J hash functions that output one of the integers from 1 to B_ABF. The result of each hash function represents the position index of ABF_A, and each enters the position of ABF_A with . If the position is occupied by a previously added string, it is reused by . The function ABF Build repeats the above process for all rows of A and outputs ABF_A.

The function ABFQuery can be defined as ABFQuery. The function ABFQuery combines the corresponding attribute name att_k for each attribute value , and hashes it as H with a hash function J. For each , the function ABFQuery can obtain a string at the position H of ABF_A. The function ABFQuery reconstructs the element as with this string. The function ABF Query takes the last +-bit string from the element and checks whether it is identical to att_k|. If they are identical, it can be interpreted that the attribute name att_k (and the attribute value are included in the access structure . The function ABFQuery obtains leading L bits of , which represent the row of the matrix corresponding to the attribute name att_k and attribute value . After repeating the above process for all , the function ABFQuery creates a set with the obtained row number. If S satisfies the function ABFQuery can find ω_i satisfying using the row of A corresponding to the obtained row number. In this case, the function ABFQuery outputs 1, which means TRUE, and in the opposite case, that is, if S does not satisfy , outputs 0.

In step S601, C_n randomly selects a constant d and calculates D= and . C_n transmits to Br.

In step S602, Br may retrieve using and obtain d=:D. Br checks whether , and if checking fails, the above step is stopped. Otherwise, Br calculates = and transmits to C_n.

In step S603, C_n checks whether . After checking, C_n calculates = and replaces with . Then, C_n calculates

${𝔸}_{C_n}^{\mathrm{CRC}}=E_{K_{\mathrm{Group}}}\left({𝔸}_{C_n}\right),{\mathrm{ABF}}_{{𝔸}_{C_n}^{\mathrm{CRC}}}=\mathrm{ABFBuild}\left({𝔸}_{C_n}^{\mathrm{CRC}}\right),{\delta }_3=H\left({\mathrm{ABF}}_{{𝔸}_{C_n}^{\mathrm{CRC}}}❘❘K_{C_n-\mathrm{Br}}^{\mathrm{new}}d-2\right)$

and transmits

$\left\{{\mathrm{ABF}}_{{𝔸}_{C_n}^{\mathrm{CRC}}}·{\delta }_3\right\}$

to Br.

In step S604, Br calculates and verifies whether

${\delta }_3\stackrel{?}{=}H\left({\mathrm{ABF}}_{{𝔸}_{C_n}^{\mathrm{CRC}}}{K}_{C_n-\mathrm{Br}}^{\mathrm{new}}❘d-\right).$

Br calculates = and replaces with , To find data including S satisfying , Br executes a function

$\mathrm{ABFQuery}\left({\mathrm{ABF}}_{{𝔸}_{C_n}^{\mathrm{CRC}}}·S_{\mathrm{enc}}\right)$

on all of the storage server. Br retrieves for all for which a query result value is TRUE and calculates

$\mathrm{ECT}=E_{K_{C_n-\mathrm{Br}}^{\mathrm{new}}}\left(\cdots ❘\mathrm{ED}·\mathrm{CT}·S_{\mathrm{enc}}\cdots \right)$

in order to encrypt all retrieval results. Br calculates = and transmits to C_n.

In step S605, C_n may obtain a ciphertext and a hidden attribute sets by performing step

$D_{K_{C_n-\mathrm{Br}}^{\mathrm{new}}}=\cdots \mathrm{ED}·\mathrm{CT}·S_{\mathrm{enc}}❘\cdots .$

C_n verifies whether and calculates S=, k_s=Decrypt, and Data=(ED) for all .

FIG. 7 is a flowchart of a method in which an IoT device shares IoT data according to an embodiment.

In step S701, the IoT device 110 may collect IoT data at regular intervals through at least one sensor included in the IoT device 110.

In step S702, the IoT device 110 may generate an intermediate ciphertext obtained by partially encrypting the collected IoT data by performing some operations of attribute-based encryption. Some operations of attribute-based encryption may include multiplication and subtraction operations, and may not include exponential operation and bilinear pairing operation.

In step S703, the IoT device 110 may generate an attribute set for the IoT data. The IoT device 110 may encrypt the attribute set using a group key. The group key may be shared in advance with the user device 300 requiring IoT data by the key management center 500.

In step S704, the IoT device 110 may transmit the intermediate ciphertext and the encrypted attribute set together to the peripheral device 120 in order to request execution of the remaining operations of attribute-based encryption. The peripheral device 120 may provide external network communication connection for the IoT device 110 and may perform higher-performance operation than the IoT device 110. The remaining operations of attribute-based encryption requested for the peripheral device 120 may include exponential operation and bilinear pairing operation.

FIG. 8 is a flowchart of a method in which a peripheral device shares IoT data according to an embodiment.

In step S801, the peripheral device 120 may receive an intermediate ciphertext and an encrypted attribute set from the IoT device 110.

In step S802, the peripheral device 120 may generate a final ciphertext for the intermediate ciphertext by performing the remaining operations of attribute-based encryption. The remaining operations of attribute-based encryption may include exponential operation and bilinear pairing operation.

In step S803, the peripheral device 120 may transmit the final ciphertext and the encrypted attribute set to the server.

FIG. 9 is a flowchart of a method in which a user device shares IoT data according to an embodiment.

In step S901, the user device 300 may generate an ABF for attributes of an access policy. The user device 300 may encrypt attributes constituting an access policy included in a private key using a group key and generate an attribute bloom filter using the encrypted access policy. The group key may be shared in advance with the IoT device 110 that has generated IoT data by the key management center 500.

In step S902, the user device 300 may transmit the ABF to the server 200 to request IoT data.

In step S903, the user device 300 may receive a ciphertext matching the ABF from the server 200. The ciphertext matching the ABF is a ciphertext of an attribute set retrieved using the ABF as a query.

In step S904, the user device 300 may decrypt the received ciphertext according to attribute-based encryption to obtain IoT data.

The embodiments described above may be implemented as hardware components, software components, and/or a combination of hardware components and software components. For example, the devices, methods and components described in the embodiments may be implemented using one or more general purpose or special purpose computers such as a processor, a controller, an arithmetic logic unit (ALU), a digital signal processor, a microcomputer, a field programmable gate array (FPGA), a programmable logic unit (PLU), microprocessors, or any other devices capable of executing and responding to instructions, for example. A processing device may execute an operating system (OS) and one or more software applications running on the operating system. Further, the processing device may access, store, operate, process, and generate data in response to execution of software. For convenience of understanding, there are cases in which one processing device is used, but those skilled in the art will understand that the processing device may include a plurality of processing elements and/or a plurality of types of processing elements. For example, the processing device may include a plurality of processors or a processor and a controller. Other processing configurations such as a parallel processor are possible.

Software may include a computer program, code, instructions, or a combination of one or more thereof, and may configure a processing device such that it operates as desired or issue commands to the processing device independently or collectively. To be interpreted by a processing device or to provide instructions or data to the processing device, software and/or data may be permanently or temporarily embodied in any type of machine, component, physical device, virtual equipment, computer storage medium or device, or transmitted signal waves. Software may be distributed to computer systems connected via a network and stored or executed in a distributed manner. Software and data may be stored in one or more computer-readable recording media.

The method according to the embodiments may be implemented in the form of program instructions that can be executed through various computer means and recorded on a computer-readable medium. The computer-readable medium may include program instructions, data files, data structures, etc. alone or in combination. Program commands recorded on the medium may be specially designed and configured for the embodiments or may be known to and usable by those skilled in computer software. Examples of computer-readable recording media include magnetic media such as hard disks, floppy disks and magnetic tapes, optical media such as CD- ROMs and DVDs, magneto-optical media such as floptical disks, and hardware devices specially configured to store and execute program instructions, such as a ROM, a RAM, and flash memory. Examples of program instructions include high-level language code that can be executed by a computer using an interpreter as well as machine language code such as code created by a compiler. The hardware devices described above may be configured to operate as one or more software modules to perform the operations of the embodiments, and vice versa.

Although the embodiments have been described with limited examples and drawings, as described above, those skilled in the art can make various modifications and variations from the above description. For example, even if the described techniques are performed in an order different from the method described, and/or components such as the described system, structures, devices, and circuits are combined in a different form from the method described above or replaced by other components or equivalents, appropriate results can be achieved. Therefore, other implementations, other embodiments, and equivalents of the claims are within the scope of the following claims.

Claims

1. An IoT device including at least one sensor, configured to: collect IoT data at regular intervals through the at least one sensor;generate a partially encrypted intermediate ciphertext by performing at least some operations of attribute-based encryption on the IoT data; andtransmit the intermediate ciphertext to a peripheral device in order to request remaining operations of attribute-based encryption for the intermediate ciphertext.

2. The IoT device according to claim 1, wherein the IoT device generates an attribute set for the IoT data, encrypts the attribute set using a group key, and transmits the encrypted attribute set to the peripheral device.

3. The IoT device according to claim 2, wherein the group key is shared in advance with a user device requesting the IoT data.

4. The IoT device according to claim 1, wherein the peripheral device provides external network communication connection to the IoT device and has higher computing performance than computing performance of the IoT device.

5. The IoT device according to claim 1, wherein the at least some operations of attribute-based encryption include a multiplication operation and a subtraction operation, and the remaining operations of attribute-based encryption include an exponential operation and a bilinear pairing operation.

6. The IoT device according to claim 1, wherein the peripheral device is identified according to a position of the IoT device on the basis of a handover method in response to movement of the IoT device, and the intermediate ciphertext is transmitted after the IoT device and the peripheral device perform mutual authentication.

7. An electronic device including a communication interface, configured to: provide external network communication connection to an IoT device using the communication interface;receive data and an encryption request for the data from the IoT device;generate a ciphertext by performing some operations of attribute-based encryption on the data in response to the encryption request; andtransmit the ciphertext to a server.

8. The electronic device according to claim 7, wherein the electronic device receives an encrypted attribute set for the data from the IoT device and transmits the attribute set along with the ciphertext to the server.

9. The electronic device according to claim 8, wherein the ciphertext is identified by using an attribute bloom filter created to request IoT data as a query.

10. The electronic device according to claim 7, wherein the some operations of attribute-based encryption according to the encryption request include an exponential operation and a bilinear pairing operation.

11. An electronic device configured to: encrypt attributes constituting an access policy with a group key and create an attribute bloom filter using the encrypted access policy;transmit the attribute bloom filter to a server to request IoT data;receive a ciphertext retrieved by using the attribute bloom filter as a query and an attribute set for the ciphertext from the server; andobtain IoT data by decrypting the ciphertext using the group key and a private key.

12. The electronic device according to claim 11, wherein the group key is shared in advance with an IoT device that generated the IoT data.

13. The electronic device according to claim 11, wherein the electronic device decrypts the attribute set using the group key and decrypts the ciphertext on the basis of attribute-based encryption using the private key.

14. The electronic device according to claim 13, wherein the attribute set corresponds to attributes constituting the access policy.