Abstract
This paper proposes a novel image retrieval scheme over encrypted cloud data, which achieves high efficiency and confidentiality. For the purpose of improving search efficiency, an index tree is often deployed in the image retrieval scheme. Meanwhile, the confidentiality of the sensitive cloud data, such as outsourced images, index tree, and query request, is also a key issue. Firstly, a balanced binary clustering algorithm is exploited over the integrated image features composed of basic features, such as HSV histogram and DCT histogram, yielding a balanced binary tree (BBT). In particular, due to the adoption of a balanced index tree, our scheme can achieve logarithmic search time. Secondly, the secure inner product is employed to encrypt the index vector and query feature. Finally, to resist the statistical attack of the frequency distribution of the retrieved results, we copy the database and merge the subtree of encrypted BBT to blind the search results. Security analysis and experimental results show that the proposed scheme is secure and efficient.
1. Introduction
With the arrival of the cloud computing, secure image retrieval on the cloud has attracted more and more attention in recent years [1]. Due to high convenience and economic savings, both enterprises and individuals tend to employ the cloud to store and manage their sensitive data, such as photo albums and personal health documents. To ensure the confidentiality of outsourced data, the common approach is to encrypt the data before it is outsourced to the cloud. However, the traditional encryption may make the basic data operations unfeasible, for example, the information retrieval of encrypted data. In the ciphertext scenario, how to achieve an efficient retrieval while protecting the privacy of customers becomes a challenging problem.
At present, there are three main issues that restrict the development of information retrieval in the encrypted domain. The first issue is to realize searchable functionality on encrypted data and achieve the same precision as plaintext data. Certainly, a naive approach is to download all the ciphertext, decrypt them, and search locally in the plaintext. However, it will incur heavy cost of bandwidth and computation. To address this issue, cryptographic techniques, such as homomorphic encryption [2] and multiparty computation, can be employed to encrypt the plaintext data and support search operation in the ciphertext. However, the above methods are concerned more with data confidentiality than retrieval efficiency, and the cost is expensive in practical applications. In the contrary, some efficient techniques, such as orderpreserving encryption (OPE) [3, 4], randomized hash functions [5–7], and asymmetric scalarproductpreserving encryption (ASPE) [8], are widely adopted. The reason is that they take both the data confidentiality and retrieval efficiency into account. The second issue is that although plaintext content of the encrypted data is not leaked in the above schemes, some statistical information, such as the request frequency of encrypted query (i.e., query pattern) or the access frequency of encrypted result (i.e., access pattern), may leak the privacy of query user. Oblivious RAMs [9] is a solution to protect the access pattern, but not practical enough. The third issue is that a retrieval scheme of linear efficiency is not desirable, because the search time will increase as the dataset becomes larger. In fact, secure information retrieval is commonly used for images or documents stored in a cloud server. We detail them as follows.
On the one hand, abundant works have been put forward to achieve secure retrieval in the encrypted documents. For example, Boolean search based on the single keyword is separately proposed in symmetric key setting [11] and public key setting [12]. Since similarity search is more practical than Boolean search, multikeyword ranked search [13] is studied to enrich search functionality and improve result accuracy, where each document is associated with an index vector. Each element of the vector indicates whether a keyword exists or represents its “term frequency (TF) inverse document frequency (IDF).” Then, the knearest neighbor is found by comparing the cosine similarity between the query vector and all index vectors, which is linear efficiency. In order to improve retrieval efficiency, a few works based on index tree are proposed. For example, Sun et al. [14] present a treebased search scheme that constructs index vectors of all documents as an MDBtree. It achieves sublinear search efficiency via setting the prediction threshold for each level of the index tree. Although a tighter prediction value can obtain logarithmic search efficiency, the result accuracy is sacrificed at the same time. Moreover, Xia et al. [15] build a KBBtree from a bottomup approach. In KBBtree, the element of internal node vector is the maximum value of the corresponding position of its child node vectors. A “GreedyDepthFirst Search” algorithm is executed to find k most relevant leaf nodes, which are stored in an RList. If the correlation score between the query vector and the internal node vector is smaller than the minimum score in the RList, the subtree of the internal node does not need to be searched. Thus, this scheme can also achieve sublinear efficiency.
On the other hand, some works have been proposed for encrypted image retrieval. In [16], a privacyenhanced face recognition is realized with a help of Paillier homomorphic encryption (HE). The drawback is that the adoption of HE incurs heavy cost of computation and communication. To be practical, Lu et al. propose a secure contentbased image retrieval (CBIR) scheme based on feature/index randomization [17] or minHash [5]. Meanwhile, the performance comparison between homomorphic encryption and distancepreserving randomization is studied in [18]. Due to the oneway and binary property of hash code, secure CBIR that exploits the hash function to encrypt features is effective and efficient in the largescale database [6]. However, the access pattern is leaked in the above schemes. To solve this issue, Weng et al. [7] omit certain bits of the hash code of query image. As a result, the cloud returns all possible candidates to the user. Therefore, the query pattern and access pattern are protected. But the user is involved to compare the features of candidates and obtain an accurate result. Also, it is difficult to generate hash codes that uniformly distributed in the feature space. In further, under the vector space model, there is only a handful of works that support efficient index structure. For example, Xia et al. [19] use localsensitive hash (LSH) to construct a prefilter table, but a refinement of the candidate results is also a linear comparison. Thus, it just achieves sublinear search efficiency. Yuan et al. [20] employ kmeans to build an index tree. Since kmeans is not a balanced clustering algorithm, it is inevitable to generate an index tree of skewed hierarchies. Subsequently, due to uneven depth in different parts of index tree, the search efficiency tends to be sublinear. In short, under the vector space model, the requirement for secure and efficient image retrieval mechanisms remains open up to date.
Besides the above schemes that based on the encrypted feature, the secure retrieval scheme directly based on encrypted images has been proposed. It is designed for the widely used JPEG image. For example, Zhang and Cheng first use DC histogram preserved in the encrypted image as a feature [21] and then exploit AC histogram [22] and a new block feature [23] for retrieval. However, the efficiency of linear comparison or blockwise comparison is unacceptable. Therefore, the construction of secure index tree is necessary.
In this paper, we propose an efficient image retrieval scheme over encrypted cloud data, which based on a balanced index tree, i.e., balanced binary tree (BBT). We introduce a novel balanced binary clustering (BBC) algorithm and use integrated features to build the BBT. Owing to the fact that this paper realizes similarity search, we tend to utilize global feature (such as color, shape) instead of accurate local feature (such as SIFT, BRIEF). Hence, our integrated feature is composed of widely used HSV histogram and DCT histogram [5, 21, 22, 24]. We focus on the construction of index tree and protection of query pattern and access pattern. As for the image encryption, we adopt partial image encryption technique [23, 25, 26] for JPEG format image and mature cryptographic ciphers (such as AES) for the other format images. Note that the key distribution is an independent issue and out of the scope of this paper. Our main contributions lie in three aspects:
(1) We combine HSV histogram in the color space and DCT histogram in the transform domain as an integrated feature. To improve the search efficiency, we construct a BBT for the image database. The BBT is built from a topdown approach. Since the hierarchical index tree is approximately balanced, the scheme can achieve logarithmic search time.
(2) By incorporating secure inner product (i.e., ASPE), the BBT is encrypted as secure BBT (SBBT) by a secret key, and query feature is encrypted. The database image is encrypted by another secret key. After that, the sensitive data in the cloud is protected; meanwhile, the searchable functionality of the encrypted feature is still valid. Further, the random number extended in the query feature can blind the query pattern.
(3) To blind the search result, we copy the database and merge the subtree to rebuild SBBT. The reduced SBBT and the weighted factor of the integrated feature make the search result of one query image not unique. Therefore, the query privacy about access pattern is protected.
The rest of this paper is organized as follows. In Section 2, we introduce system model, threat model, and design goals. Also, common notations are defined. In Section 3, we propose BBC algorithm, use BBC to build a BBT, and adopt ASPE to encrypted BBT. Section 4 presents and discusses experimental results. Finally, we conclude the paper in Section 5.
2. Problem Formulation
2.1. System Model
The system contains three parties: the data owner, the cloud server, and authorized users, as illustrated in Figure 1.
The owner first extracts feature vectors, such as HSV histogram and DCT histogram, from each image in his database. They are concatenated into an integrated feature. After the feature extraction, the plaintext image is encrypted as the ciphertext by a secret key. For improving search efficiency, the owner builds an index tree based on the integrated features. Then, he utilizes another secret key to encrypt the index tree. The leaf node of the secure index tree is associated with the encrypted image. Afterward, the owner outsources the encrypted database images and the secure index tree to the cloud. In addition, the owner sends secret keys to each authorized user through a secure channel.
The authorized user extracts feature vectors from the query image. To fetch encrypted images in the secure index tree, he encrypts the integrated feature of a query image and submits it to the cloud.
The cloud stores the encrypted database images and secure index tree from the owner. After receiving an encrypted query feature, the cloud executes the search operation in the secure index tree. After that, he returns encrypted images that associated with retrieved leaf node to the user.
2.2. Thread Model
We assume that three parties follow a semihonest model, in which any two parties do not collude to share information. However, even if the cloud does not know the content of the encrypted query, it may count the query frequency of same encrypted request and the access frequency of the same returned result. Thus, depending on the available information to the cloud, we consider two threat models here.
Known Ciphertext Model. The cloud only knows encrypted database, secure index tree, and the encrypted query.
Known Background Model. In this stronger model, the cloud knows background knowledge about the frequency distribution of the query images. For example, Trump’s photos are very popular in the presidential campaign. The cloud can conduct a statistical attack to identify certain image via the access frequency of the returned images.
2.3. Design Goals
To enable secure image retrieval over encrypted cloud data under the above models, our scheme should achieve the following design goals.
Effectiveness. The scheme is designed to support search over encrypted data. The result is as accurate as the search in the plaintext domain.
Efficiency. Under vector space model, we structure the feature vectors of image database as an SBBT. Instead of linear or sublinear search efficiency, our scheme will achieve logarithmic search time.
Privacy. The goal is to protect the privacy of owner and user, which is summarized as follows. (1) The database and its index tree confidentiality: namely, the image and its index tree exist in the ciphertext form in the cloud. (2) The query privacy: it is not possible to determine whether two requests are from the same query image. Note that to ease the overload of computation and communication, our goals are not to fully protect access pattern, i.e., the search path in the SBBT.
2.4. Notations
Assume that the total number of images in the database is . We define common notations as follows:(i) the database, namely, the set of images(ii) the ciphertext form of stored in the cloud(iii) the normalized feature, such as HSV histogram from the th image, , it is a dimensional row vector(iv) the normalized feature, such as DCT histogram from the th image, , it is a dimensional row vector(v) the integrated feature, , a weighted factor (vi) the index vector in each node of BBT, it is generated from (vii) the height BBT for the whole image database , (viii) the ciphertext index which corresponds to plaintext (ix) the ciphertext form of (x) the normalized feature of the query image, such as HSV histogram(xi) the normalized feature of the query image, such as DCT histogram(xii) the query vector, , a weighted factor (xiii) the encryption key is a random invertible matrix, (xiv) the ciphertext query, corresponding to plaintext
To find the knearest neighbor of the query image, we adopt “inner product similarity” to evaluate the distance among the features. Specifically, is an integrated feature of the database image, including HSV histogram and DCT histogram. is the integrated feature of the query image. The final similarity score is obtained by . Based on the score, the most relevant images in the database are returned to the user.
3. Proposed Scheme
In order to achieve logarithmic search efficiency, we first build a balanced index tree for the plaintext image database, in which a novel balanced binary clustering algorithm is proposed. Then, to ensure the confidentiality of index vector and query vector , the secure inner product computation is employed to encrypt the vector and . Also, we adopt a partial image encryption to encrypt database images. Finally, we improve the scheme to enhance privacy protection in the known background model.
3.1. BBC Algorithm: Balanced Binary Clustering
To build the balanced index tree, we need a balanced binary clustering (BBC) algorithm to find a separating vector which divides each dataset into two equal (or nearly equal) clusters. However, traditional kmeans aims at finding cluster centers so that the sum of the distance between each point and its nearest center is maximized, rather than the equal size of clusters. Thus, frequency sensitive competitive learning (FSCL) [27] is introduced to improve kmeans. FSCL is a conscience type algorithm that takes the size of clusters as a weight factor which makes the bigger cluster less likely to win more points in next iteration. It can converge to a local minimum [28]. Although the difference of cluster centers can be used as a separating vector , FSCL does not ensure that the k clusters are equally sized. In fact, it is experienced as very unstable in highdimensional vector spaces [29]. On the contrast, balanced kmeans [30] can split a dataset into two equalsized clusters by finding a perfect matching in a bipartite graph. But it does not generate the separating vector . Thus, we propose a novel BBC to find a separating vector that makes the size of two clusters equal. To our best knowledge, this work is the first endeavor to combine FSCL and balanced kmeans to achieve balanced clustering. The detail of BBC algorithm is elaborated in the following.
Given points , at the th iteration, the size of cluster is and the cluster center is . The BBC algorithm works as follows.
Initialization. We adopt kmeans++ to choose two points from as initial centers .
First, uniformly choose an initial center from .
Second, choose the next initial center from with probability , .
Finally, according to the distance to the initial centers, other points are divided into two categories , the size of which is .
Cluster Assignment. Let new be the solution of optimization problem as follows.where . A smaller value of indicates that the two vectors are more similar.
Inspired by balanced kmeans, we first turn (1) as a linear assignment problem (LAP) [31]. The cost matrix is defined aswhere . If it is not a square matrix, a column of zeros is added to make it square. Then, we adopt VolgenantJonker (VJ) algorithm [32, 33] to find a perfect matching in a bipartite graph. Finally, if the vector is assigned to center , and 0 otherwise.
Cluster Update. Update the cluster centers , the “selection” variables , and the size of clusters as follows:
Cluster assignment and cluster update are repeated until or .
Output. The above three steps run several times with different initial centers , .
Owing to the fact that different initial centers may generate different results, the result that the sizes of two clusters are most similar is chosen as a final output. The size similarity of two clusters is defined as
Finally, the output isThe dataset of points can be divided into two equal (nearly equal) clusters by the separating vector .
3.2. UBBT: Unencrypted Balanced Binary Tree
In this subsection, we build the BBT for the whole database. Firstly, we generate an integrated feature for each image in the database. Then, an index vector of the root node or internal node of the BBT is generated by a topdown approach. BBC algorithm generates to separate image features into two clusters of nearly equal size, i.e., , . Namely,Algorithm 1 recursively divides feature vectors of the database images into two clusters until no cluster has more than two feature vectors. The hierarchical index tree is shown in Figure 2. The level of the root node is 0 and the level of the leaf node is . Thus, the height of entire index tree is . The subtree that the root node is at th level of the index tree has the height of . The root and internal node in our BBT are defined as follows:where is the identity of node, is the index vector dividing images on the leaf nodes into two clusters and , and and are the pointers to the left and right child node. If is a leaf node, it is defined aswhere points to the images.

The search process starts from the root node of UBBT. If , we execute iterative retrieval upon the left subtree, otherwise upon the right subtree until obtaining the leaf node.
3.3. SBBT: Secure Balanced Binary Tree
In UBBT scheme, the leaf node is retrieved by the sign of the inner product . In order to protect the sensitive data and , we use the secure inner product (i.e., ASPE) [8] to encrypt the vectors and obtain the same result as the plaintext.
First of all, the owner generates a random invertible matrix to encrypt . The user also use it to encrypt , i.e.,where is the ciphertext index and is the ciphertext query. In addition, the JPEG images are encrypted via a partial image encryption [22, 25]. Therefore, index tree is encrypted as . The leaf node of is associated with the encrypted images. Then, they are outsourced to the cloud for secure image retrieval. When retrieving, the user submits of the query image to the cloud. Since , the cloud can use to execute an effective search on secure index tree . Therefore, the retrieved result and efficiency in the ciphertext would always be in line with that in the plaintext. Note that the more details of ASPE are described in [8].
Unfortunately, the relationship between and is deterministic. According to the same or , the cloud can count the query frequency of . Further, according to the same result, the cloud can also count the access frequency of . Therefore, if the query image and is a onetoone relationship, the proposed scheme cannot resist the statistical attack in the known background model.
To break the onetoone relationship between the query image and ciphertext query , we extend and as follows:where the random numbers , . Thus, the same query image can generate different ciphertext query by setting and . Meanwhile, is blinded by positive . The cloud cannot get available statistical information from the ciphertext query and the result . However, the sign of remains the same even if and are different, so the retrieved result and search path remain the same. The request frequency of a query image can be inferred from the access frequency of the same return image.
To overcome the issue, we first copy the image database. The owner uses partial image encryption [23] to protect plaintext image. According to different encryption keys, same plaintext image can be encrypted as different encrypted images, as shown in Figure 3. Meanwhile, the owner uses the embedding key to hide which encryption key was used [25]. Then, the owner shares encryption keys and the embedding key with authorized users through a secret channel. After obtaining an encrypted image, the user uses the embedding key to extract hidden data and select true encryption key to recover the plaintext image.
(a)
(b)
(c)
Second, different encrypted images derived from the same plaintext image correspond to different integrated features. For the diversity of the integrated feature, we use HSV histogram and DCT histogram as basic features. The reason is that HSV histogram in color space and DCT histogram in transform domain are image features from different perspectives. As shown in Figure 4, different features of the query image can still retrieve a similar image. For ease of description, we define the new ciphertext database as . Then, we set corresponding to the feature and corresponds to the feature . Finally, we use proposed BBC algorithm to build an index tree from and employ ASPE to encrypt the plaintext tree as a ciphertext tree .
(a)
(b)
(c)
(d)
(e)
(f)
(g)
(h)
To further enhance query privacy, we reduce the height of the index tree and return multiple encrypted images to the query user at the one time. Specifically, we set the internal node to be a new leaf node. Then, the new leaf node contains all the encrypted images in the subtree that the internal node of is a root node. Due to the fact that the index tree is balanced, leaf nodes of reduced index tree can always point to multiple encrypted images. Please note that some images in a subtree are similar, which is a compromise with effective retrieval.
3.4. Security Analysis
We analyze SBBT concerning the privacy requirements in the design goals:
(1) The database and its index are confidential. In SBBT, index vectors of BBT are encrypted as by the highdimensional random matrix which is kept confidential to the cloud. For images in the database, the partial encryption can protect their confidentiality [23, 25].
(2) Since the feature vector of the query image is extended by random numbers and , it can generate different ciphertext queries . The cloud cannot identify the same query image from its different ciphertext queries. The query pattern is protected.
(3) According to different , different features of same query image can retrieve different images. When is equal to or , different results can be recovered to the same query image. Thus, the retrieved result and path of the same query image are not unique but the retrieval is still effective. The cloud cannot link the different returned image to the same query image. The access pattern is protected.
(4) In addition, since the height of SBBT is reduced, one leaf node will point to multiple encrypted images. It further breaks the onetoone relationship between the query image and the return images. The access pattern is further protected.
In short, the SBBT is secure in the known ciphertext model and can resist the statistical attack in the known background model.
4. Performance Analysis
In this section, we show the experimental results and efficiency analysis of the proposed scheme. As we know that JPEG is the most commonly used image format and accounting for up to 95% of images on the web [34], so we adopt the Corel database [10] for the similarity search. The database contains 1000 JPEG images which belong to 10 categories: African, Beach, Architecture, Buses, Dinosaurs, Elephants, Flowers, Horses, Mountain, and Food. Each of them includes 100 images. As [5], we split an image into 256 blocks and extract hue, saturation, and value of brightness of each block. Then, we perform hierarchical clustering of block features to construct the “bag of word” model. The usage frequency of the visual word is the HSV histogram of the image. As [22], DC/AC coefficients of image blocks are quantized into different bins and the DCT histogram is the usage frequency of quantized DC/AC coefficients. Thus, the color feature and texture feature are set as the 991dimensional HSV histogram and 780dimensional DCT histogram, respectively.
4.1. Parameters Setting
First of all, we should set parameters of and of to construct an index tree. Because the integrated features compose of HSV histograms and DCT histogram, we first evaluate average histogram similarity of the images in the same category and different categories (denoted as corrintra and corrinter, respectively), as shown in Figure 5. We can see that the value of corrintra is larger than corrinter; thus, images of different categories can be distinguished by each histogram. According to the difference between corrintra and corrinter (i.e., corrdiff in Figure 5), we set for the integrated feature of the database . The purpose is to make the HSV histogram and DCT histogram have the same contribution to the search results.
For the parameter of , we hope that the index tree of database can better protect the access pattern. We use two different metrics to measure the privacy protection achieved by different . The two metrics are the number of different image categories in each subtree and the category entropy of each subtree. Figure 6 shows the average number of image categories contained in the subtree of different levels. Because the index tree of the database based on different has same height of 11 (i.e., ), the proposed BBC algorithm performs well. However, we can see from Figure 6 that the subtree near the leaf node contains a similar number of image categories. We will use category entropy to measure the privacy. The category entropy, which is defined as ( is the number of existing category), is used to measure the randomness of image categories in the subtree. From Table 1, we know that the index tree of has the highest average entropy at the 3th10th level, even its average category number at 3th6th level is not the biggest in Figure 6. Thus, we set the weighted factor for the integrated feature of database .
4.2. Index Tree Construction
In order to prove that our algorithm can classify feature vectors in a balanced manner, we use average similarity of the cluster size to compare the clustering performance of proposed BBC algorithm, balanced kmeans (i.e., Bkmeans), kmeans++, and FSCL. The average similarity based on (5) is defined as . From Figure 7, we can see that the index trees generated by the proposed BBC algorithm, Bkmeans, kmeans++, and FSCL have the height of 11, 12, 13, and 16, respectively. The smaller the height of the index tree indicates that the proposed algorithm can classify feature vectors into two clusters more evenly at each level of the index tree. Figure 7 shows that the cluster size of FSCL is the most unbalanced at 1th11th levels. There are two reasons: the first is that the change of the weight factor affects the stability of the clustering result, and the second is that the value of weight factor impacts the distance between the cluster center and other feature vectors. On contrast, due to the use of conscience weight factor, the proposed algorithm performs better than Bkmeans and kmeans++, and the result is much better than FSCL. The reason is that the bipartite graph matching mechanism constrains a balance of the two clusters and restricts the influence of weight factor. In short, the weight factor is still effective in improve the balance of clustering. In fact, above result is also similar in the database of different .
In further, we employ Dunn index (DI) [35] to evaluate mentioned clustering algorithms. The Dunn index is defined aswhere the numerator is the minimal distance of vectors in different clusters and the denominator is the largest withincluster distance. Thus, we can know that when separating two points into two clusters, the denominator is zero and DI is infinite. A high value of DI means good compactness. Table 2 shows the minimal DI of clustering results in each level. In the same level of the index tree, the most of BBC’s DI is smaller than other algorithms (i.e., Bkmeans, Kmeans++, and FSCL). Meanwhile, BBC’s DI of the last level is much smaller than other algorithms. Obviously, for the proposed BBC algorithm, the clustersize similarity is with higher priority than clustering compactness.
The above algorithms are implemented using MATLAB on a PC with an Intel Core i5 3.2 GHz CPU and 16 GB RAM. Time consumption for index tree construction is shown in Table 3. In particular, we execute 30 times clustering with random initial centers and select the result of highest score of clustersize similarity. Bkmeans is most time consuming because it is not designed to find a vector that splits a dataset evenly. In contrast, proposed BBC costs the least time.
4.3. Retrieval Performance
To evaluate the retrieval performance, each image in the Corel database is selected as a query image. The retrieval performance is evaluated by average precisionrecall (PR) curve, i.e.,Figure 8(a) compares the PR curves of the query feature based on different values. It can be seen that the performance of different achieves high precision when recall belongs to (0, 0.05). Besides, when only one image is returned, i.e., recall=1%, the precision of or 0.6 is 100%. The reason is that we set as or . Although two integrated features of a query image are different, the retrieved results are different encrypted versions of the same plaintext image. Since the query features, the corresponding results, and search paths are different, the statistical information of query image is protected.
(a)
(b)
Figure 8(b) shows the retrieval performance of the reduced index trees with different heights. It can be seen that the precision increases with the height of index tree, even if is set as 0 or 1. Further, Figure 9 shows the average maximum height of a reduced index tree, in which the returned leaf node contains the exact query image. It can be seen that the height of reduced index tree is 11 when is set as 0.1 or 0.6. If is set closer to 0.1 or 0.6, the height of reduced index tree is nearer to 11. When the height is 9, the most of exact query images are retrievable in the reduced index tree and one search returns four (2^{2}) images. Fortunately, as shown in Figure 8(b), the precision is about 70% at the 9th level of the index tree. Thus, the retrieval is still effective.
4.4. Privacy Protection
We consider the privacy protection from two aspects: query pattern and access pattern. Since the query feature is an integrated histogram, i.e., . Different correspond to different query features. In addition, even if is determined, the feature will be extended by random numbers as . Thus, the encrypted feature is . Obviously, the encrypted feature of a query image is not unique. The query pattern of each query image is protected.
To protect access pattern, the retrieved result of a query image should be not unique. We have built an index tree based on features of original database () and features of the copied database (). Then, the integrated features of different are used to retrieve in the index tree. We know the fact that the returned result is a leaf node of the index tree and different leaf nodes indicate different access paths. So, we define a path privacy to evaluate the protection level of access pattern
Different search path can be obtained by using the query feature of different . Figures 10(a) and 10(b) show the path privacy of different , where and 0.6 are baselines, respectively. It can be seen that the path privacy is 100% when is set as 0.6 in Figure 10(a) and 0.1 in Figure 10(b). The reason is that retrieval is separately carried out in the left or right subtree of the root node. Figure 10(a) also shows that search paths are in the same subtree of the root node when is set to 0.6, 0.8, or 1. But the search path of or 1 is still different with as shown in Figure 10(b). Similarly, when is set to 0, 0.0025, 0.05, 0.075, 0.1, 0.3, or 0.35, the search path is in the same subtree of the root node, but still different. Besides, when is set to 0.4, the search traverses in both subtrees of the root node. In addition, the path privacy increases with the height of the tree. In short, the access pattern can be protected by setting different . Please note that usage frequency of different can be optimized based on the frequency distribution of the query images.
(a)
(b)
In summary, Table 4 compares the proposed scheme with other schemes in the terms of search efficiency, query pattern protection, and access pattern protection. We compare the search efficiency of different schemes by theoretical analysis instead of experiments. The reason is that encrypted image retrieval schemes are based on different image databases according to the application. Also, some schemes utilize encrypted image feature, but other schemes employ the hash code of the image feature.
In the schemes under vector space model, such as Yuan [20], a skew index tree leads to search time. Xia [19] uses localsensitive hash (LSH) to construct a prefilter table. Then, with corresponding image feature, the cloud carries out a refinement of candidate results. Thus, it is a sublinear scheme. Cheng [22, 23] does not build an index tree, so the retrieval efficiency is . Weng [6, 7] uses a hash table to improve the search efficiency (i.e., ). In short, the index tree or hash table is a tradeoff between space and efficiency. Although Weng's scheme [7] and proposed scheme both protect query pattern and access pattern, the hash code and feature vector are, respectively, used. Specifically, Weng [7] omits certain bits of the hash code of query image and returns multiple candidates to the user for refinement. The user is involved in completing retrieval and obtaining the accurate result. In our scheme, the user can set as or to retrieve exact query image through different paths. Unlike [7], our scheme does not need the user to participate in the feature comparison. However, to protect access pattern and alleviate computation burden on the user, we copy the image database and cost more storage space in the cloud. Fortunately, the retrieval efficiency is .
5. Conclusion
This paper introduces a secure and efficient image retrieval scheme over encrypted cloud data. In this scheme, we propose a novel clustering algorithm, i.e., BBC, to build a balanced index tree, namely, BBT. Thus, our scheme can achieve logarithmic search time. Firstly, to support effective image retrieval in the ciphertext, we employ ASPE to encrypt the index of the image database and feature of the query image. In this case, the proposed SBBT is secure in the known ciphertext model. Secondly, to resist the statistical attack on known background model, we copy the database and build a new SBBT of the original database and the copied database. After that, adjusting the weighted factor of integrated feature, the search results of a query image are different leaf nodes. Finally, through merging the subtree of SBBT, the leaf node of new SBBT contains multiple encrypted images. Therefore, the onetoone relationship between the query image and the return image is broken. In short, the SBBT can protect query pattern and access pattern. Furthermore, proposed BBC and SBBT can be used as independent tools for encrypted document retrieval.
In future, we will improve the ASPE to support multiuser scenario, where a dishonest user may try to reveal the encrypted query of other users. It is also a meaningful work to generate a generic, highsemantic feature.
Conflicts of Interest
The authors declare that there are no conflicts of interest regarding the publication of this paper.
Acknowledgments
This work was supported by the National Natural Science Foundation of China (U1636206, 61602295, 61525203, and 61472235), the Shanghai Dawn Scholar Plan (14SG36), the Shanghai Excellent Academic Leader Plan (16XD1401200), the Natural Science Foundation of Fujian Province (2017J01502), and the Scientific Research Foundation of Fuzhou University (510483).