Next Article in Journal
Landauer’s Principle a Consequence of Bit Flows, Given Stirling’s Approximation
Next Article in Special Issue
Full-Duplex Relay with Delayed CSI Elevates the SDoF of the MIMO X Channel
Previous Article in Journal
Secrecy Analysis and Error Probability of LIS-Aided Communication Systems under Nakagami-m Fading
Previous Article in Special Issue
A Review on Machine Learning Approaches for Network Malicious Behavior Detection in Emerging Technologies
 
 
Font Type:
Arial Georgia Verdana
Font Size:
Aa Aa Aa
Line Spacing:
Column Width:
Background:
Article

On the Existence of XOR-Based Codes for Private Information Retrieval with Private Side Information

by
Murali Krishnan K. H.
1,* and
Jagadeesh Harshan
2
1
Bharti School of Telecom Technology and Management, Indian Institute of Technology Delhi, New Delhi 110016, India
2
Department of Electrical Engineering, Indian Institute of Technology Delhi, New Delhi 110016, India
*
Author to whom correspondence should be addressed.
Entropy 2021, 23(10), 1287; https://doi.org/10.3390/e23101287
Submission received: 17 August 2021 / Revised: 27 September 2021 / Accepted: 28 September 2021 / Published: 30 September 2021
(This article belongs to the Special Issue Information-Theoretic Approach to Privacy and Security)

Abstract

:
We consider the problem of Private Information Retrieval with Private Side Information (PIR-PSI), wherein the privacy of the demand and the side information are jointly preserved. Although the capacity of the PIR-PSI setting is known, we observe that the underlying capacity-achieving code construction uses Maximum Distance Separable (MDS) codes therefore contributing to high computational complexity when retrieving the demand. Pointing at this drawback of MDS-based PIR-PSI codes, we propose XOR-based PIR-PSI codes for a simple yet non-trivial setting of two non-colluding databases and two side information files at the user. Although our codes offer substantial reduction in complexity when compared to MDS-based codes, the code-rate marginally falls short of the capacity of the PIR-PSI setting. Nevertheless, we show that our code-rate is strictly higher than that of XOR-based codes for PIR with no side information. As a result, our codes can be useful when privately downloading a file especially after having downloaded a few other messages privately from the same database at an earlier time-instant.

1. Introduction

Private Information Retrieval (PIR) deals with the design of queries to a database to provide privacy to the messages downloaded by the user. A trivial way of achieving information-theoretic privacy is to download all the messages stored in the database so that the identity of the demand, i.e., the message the user wants, will be unknown. However, it is well known that this increases the download cost substantially. Ever since the problem of PIR was first introduced in [1], various methods have been introduced to efficiently retrieve the demand with privacy, including the code constructions that achieve the capacity of the classic PIR problem [2]. Other than the capacity-achieving code constructions, several low-complexity constructions are also known [3,4] for the classic PIR problem.
Since the contribution of [2], numerous variants of the PIR problem have gained attention [5,6,7]. Among them, an important variant is the problem of PIR with side information. In this setting, the user already knows one or more messages in the database, and she uses this information to reduce the download cost compared to that without side information. The work on PIR with side information began with the cache-aided PIR in [8]. Other crucial works on PIR-SI were followed in [9,10,11,12,13]. A prominent variant of PIR with side information is the problem of PIR with private side information (PIR-PSI), wherein the privacy of both the demand and the side information are jointly preserved, i.e., the database should not know which message is being queried by the user and which side information is available at her. The application of PIR-PSI has practical significance when users must query a message privately from a database after having downloaded a few other messages privately from the same database at an earlier time-instant. Suppose a user has already queried messages A and B with full privacy. Furthermore, suppose that the same user wants to query another message C at a later point in time. One way to query C is using the capacity-achieving fully private scheme [2]. Alternatively, the user can reduce the download cost for retrieving C using A and B as the side information. This way, as the number of side information messages increases, the download cost for a particular demand can potentially decrease. For these applications, PIR-PSI protocol ensures that demand is downloaded with the help of side information, while jointly preserving the privacy of both the demand and the side information.

1.1. Existing Codes for PIR-PSI Setting and Their Limitations

A solution for PIR-PSI was first developed by Kadhe et al. in [14] for the single database setting. Chen et al. further extended it in [15] for multiple databases in colluding and non-colluding environments. Both their schemes achieved capacity; however, both the schemes for single database and multiple databases mentioned in [14,15], respectively, rely on Maximum Distance Separable (MDS) codes. From the viewpoint of implementation, it is well known that any MDS-coded scheme would have high computational complexity compared to a counterpart code that is constructed using XOR bit additions. For example, consider the code in [15] for two non-colluding databases with three messages A , B , C with a length of eight bits per message. Let A be the demand and C be the side information for a particular user. As mentioned in [Section 4.1.1] in [15], the query would initially be in the form of Sun-Jafar’s capacity-achieving scheme mentioned in [2], with four bits of A retrieved out of seven bits queried from a database. This query of seven bits would be converted to an ( n = 13 , k = 7 ) systematic MDS code, e.g., a Reed-Solomon code, and the six bits of the non-systematic part would be downloaded. With the help of the side information C, the user can retrieve four demand bits from these six bits, therefore improving the rate. Here, the encoding operation for Reed-Solomon code would require 91 finite field multiplications and 78 finite field additions, which in turn are computation-intensive tasks compared to executing four XOR bit additions in Sun-Jafar’s capacity-achieving scheme. In general, any MDS code for PIR-PSI would depend on the message length L, as seen above, and L itself depends on N K (where N is the number of databases and K is the number of messages). Therefore, the computational complexity of MDS-coded PIR-PSI codes will exponentially increase as the number of messages increases. Please note that this discussion on complexity is not related to sub-packetization of the messages, instead it is only on the arithmetic operations post sub-packetization process.

1.2. Motivation

We note that a majority of existing PIR schemes such as in [2,7,16,17,18] are XOR-based code constructions, i.e., each database returns a set of XOR combinations of bits of various files, and similarly, the user also performs corresponding XOR operations to recover the message in demand. However, when tackling the PIR-PSI problems, instead of constructing XOR-based codes, MDS code-based constructions have been presented in [14,15]. Although these MDS codes achieve the capacity of the PIR-PSI setting, from a practical viewpoint, for a large number of messages, the number of computations would become prohibitively large to create a huge latency in downloading the demand. For instance, even though a computationally powerful database may return the queries to the user after finite field computations, performing similar finite field computations on this query for recovering the message at the user is challenging if the user’s device is not computationally powerful [19,20,21,22]. Therefore, existing PIR-PSI codes are not amenable to implementation in such cases. On the other hand, using the PIR scheme of [2], which is an XOR-based code construction, is not a good idea as it would affect the rate for not exploiting the side information. With this background, we ask the question: are there PIR-PSI codes based on XOR computations with rates strictly more than the code in [2]?

1.3. Contributions

Inspired by the problem statement discussed above, we make the following contributions in this paper:
  • We present the first XOR-based code construction for the PIR-PSI problem. Our code construction is applicable for the scenario when K messages, each of length L = 2 K 1 bits, are replicated across N = 2 non-colluding databases, and the user wishes to retrieve a message with M = 2 side information at her side. Although the setting of N = 2 databases and M = 2 side information messages may be applicable to a specific distributed storage model, we highlight that the code contribution is non-trivial as it affirmatively answers the question posed in the motivation section, and moreover it is applicable for any K.
  • Owing to the use of XOR-based queries, we show that our codes offer substantial reduction in the decoding complexity compared to the MDS-based counterparts of [15]. However, the rate of our codes marginally fall short of the capacity of the PIR-PSI problem for the setting of N = 2 non-colluding databases with M = 2 side information at the user (as seen in Figure 1). Nevertheless, the rates of our codes are strictly higher than that of the fully private codes [2] therefore advertising themselves as a preferred choice when privately downloading a message after having downloaded a few other messages privately from the same database at an earlier time-instant. For N = 2 and M = 2 , a comparison between existing solutions for PIR-PSI and our solution is captured in Table 1.
  • For the proposed code construction, we prove the joint-privacy property by explicitly showing that the query to one of the databases can be fixed, and then the query to the other database can be modified in such a way that any combination of side information can be used to retrieve any demand from the two databases. This is a novel approach to physically verify the privacy of any XOR-based PIR codes.
We believe that our work opens up a wide range of new problems for investigation, such as: (i) Does the XOR constraint in the code construction reduce the rate of the codes from the capacity of PIR-PSI? (ii) Are there capacity-achieving XOR-based code construction for PIR-PSI?, if not, what is the capacity of XOR-based PIR-PSI codes?

1.4. A Sneak-Peek at Our Codes

Before formally stating the problem statement, and presenting the code construction, we present an example for our codes with K = 4 . This example serves two purposes: (i) assists the reader to verify the PIR-PSI property explicitly, and (ii) confirms that the rate is higher than the code in [2]. Consider two databases N 1 and N 2 with four messages A , B , C and D of length eight bits each. Let a user want to retrieve message A with B and C as the side information. Table 2 shows the query obtained as per the proposed code construction to retrieve eight bits of A from using B and C as side information. In this description of the code, the notation A 1 , A 2 , , A 8 denote the eight bits of the file A. Similarly, { B i | 1 i 8 } , { C i | 1 i 8 } , and { D i | 1 i 8 } denote the eight bits of the files B , C and D, respectively.
To show the privacy of the code in Table 2, we fix the query to N 1 (that was generated when A is the demand and B , C are the side information), and then generate all possible queries to N 2 such that any demand can be retrieved using any two side information. All possible queries to N 2 when D is a side information, a byproduct, and the demand, are listed in Table 3, Table 4 and Table 5, respectively. In this context, a byproduct is a message that is neither side information nor demand. In all the three tables, the three-tuple format on the top row indicates (Demand, Side Information, Byproduct) combination for the query in that column. In each of the cases, we highlight that the structure of the queries to N 2 are unaltered compared to the original query to N 2 in Table 2.
From Table 3, Table 4 and Table 5, it is evident that from the perspective of N 1 the query given in Table 2 can be for any demand-side information combination. Since the structure of query at N 2 is exactly same as that of N 1 , a similar reasoning can also be applied to show that for a query at N 2 , any demand can be retrieved using any side information from N 1 . Thus, N 1 and N 2 cannot identify the identity of the demand and the side information jointly, and hence, the scheme is jointly private.
The rest of the paper concerns the following sections. Section 2 presents the problem statement and related notations. Section 3 presents the code construction, whereas Section 4 provides the proof for joint privacy of the XOR-based codes for arbitrary values of K. Section 5 exemplifies the privacy proof for the case when K = 7 . Finally, some directions for future research are presented in Section 6. A preliminary version of this work is also available at [23].

2. Problem Statement

Consider two replicated non-colluding databases, N 1 and N 2 with K messages namely X 1 , X 2 , , X K 1 , X K . All the K messages are of size L = 2 K 1 bits which are independent and uniformly distributed. Therefore, we denote the i-th file X i as X i = [ X i , 1 , X i , 2 , , X i , L ] . Among the K messages, let X γ , for γ [ K ] , be the demand message for a user who already has M = 2 side information messages X α and X β , such that α , β [ K ] \ { γ } satisfying α β . In this model the messages other than X γ , X α and X β are referred to as byproducts. The user wishes to leverage the knowledge of X α and X β to retrieve X γ by downloading fewer bits from each database compared to retrieving X γ using the scheme in [2] without using the side information. At the same time, the user also wants to jointly preserve the privacy of the demand X γ and the side information messages X α and X β , i.e., the indices γ , α and β should be unknown to both databases. In the context of this work, the code for retrieving X γ should be such that each database provides the user a set of XOR additions of the bits of the K messages. This way, the user would be able to retrieve X γ by performing simple XOR bit additions on the downloaded bits while using the prior knowledge of X α and X β .
Towards constructing an XOR-based code for PIR-PSI, we make the following definitions. In order to retrieve the demand X γ using the side information X α and X β , every combination of message bits submitted to a database is referred to as codeword, the set of codewords submitted to a database is called a query, and the union of queries submitted to N 1 and N 2 is referred to as the code. When designing the codewords of a query it is important to find the right set of XOR combinations of the K message indices, and then choose the appropriate bit locations of the message indices in the XOR combinations. To formally describe the XOR combinations of the message indices, we introduce the following definitions.
Definition 1.
For a finite set M = { M 1 , M 2 , , M P } containing Z distinct variables, we define a mapping Φ such that Φ ( M ) = i = 1 Z M i if Z 1 , and Φ ( M ) = ϕ if M is empty set.
Definition 2.
With X = { X 1 , X 2 , , X K } , we define a power set-based skeleton structure P ( X ) = { Φ ( V ) | V P S ( X ) } , where Φ ( · ) is as introduced in Definition 1, and P S ( X ) is the power set of X .
From Definition 2, it is clear that the queries (without specifying the bit locations of each message) submitted to N 1 and N 2 must be subsets of P ( X ) \ { ϕ } , wherein the + operator in Φ is treated as XOR operation. Henceforth, throughout the paper, the queries submitted to N 1 and N 2 to retrieve X γ using the side information X α and X β are denoted by C 1 and C 2 , respectively, and the overall code is denoted by ( C 1 , C 2 ) . To propose formal design criteria to choose the subsets of P ( X ) \ { ϕ } as queries, we define a singleton block in a query as the set of codewords that consist of only a single message bit. Similarly, we define an n-tuple sum block in a query, for 2 n < K , as the set of codewords that consist of XOR bit additions of n different messages.

2.1. Design Criteria for XOR-Based PIR-PSI Codes

For N = 2 , M = 2 and any K 3 , let ( C 1 , C 2 ) be an XOR-based code to retrieve X γ using the side information X α and X β The code ( C 1 , C 2 ) is said to be XOR-based PIR-PSI code if keeping the query to N 1 (or N 2 ) unchanged, it is possible to design a query to N 2 (or N 1 ) such that
  • Condition 1: any demand can be retrieved from N 1 and N 2 using any two side information messages.
  • Condition 2: the structure of the new query to N 2 (or N 1 ) is same as that of C 2 (or C 1 ), namely: (i) the number of singleton and n-tuple sum blocks is the same, for any 2 n K 1 , and (ii) the frequency distribution of the message bits across all the codewords in the query is the same as that of C 2 (or C 1 ).
We take a two-step approach to design codes satisfying the above criteria. First, we present the queries of the code for a given demand X γ and a pair of side information X α and X β , and prove the correctness of the construction in retrieving X γ . Subsequently, we present a rigorous proof to show that keeping the query to N 1 (or N 2 ) unchanged, new queries to N 2 (or N 1 ) can be constructed by satisfying Condition 1 and Condition 2. We show that the rate of code is more than that of [2], implying that our codes can be used when sequentially downloading files at different time-instants. The construction procedure for XOR-based PIR-PSI code is explained in the next section.

3. XOR-Based PIR Codes with Private Side Information

Among the K messages, let X 1 be the demand, and X 2 and X 3 be the side information. With M = 2 , our construction is applicable only for K 3 . For K = 3 , the code construction is trivial with rate one since an XOR version of all the files can be downloaded. For K > 3 , the ingredients and the instructions provided in the next two sections must be followed to obtain the queries for N 1 and N 2 . Although the individual bits of the K files will be used to retrieve the L bits of X 1 , first, our construction provides a way to place the file index in the query, and then describes a way to choose the specific bits of each file in the query. Along with the steps for ingredients and code construction, a running example for K = 4 , with messages A , B , C , D is also presented, wherein A plays the role of demand, i.e., X 1 , B and C play the role of side information, i.e., X 2 , and X 3 .

3.1. Ingredients and Construction Strategy

With X = { X 1 , X 2 , , X K 1 } , we construct P ( X ) = { Φ ( V ) | V P S ( X ) } , where Φ ( · ) is as introduced in Definition 1, P S ( X ) is the power set of X . In the context of the running example with K = 4 , we have X = { A , B , C } , and therefore, P ( { A , B , C } ) is given in Table 6.
Owing to the use of power set, the elements of P ( X ) are unique, generating a total of 2 K 1 elements using 2 K 2 copies of each message. Towards converting P ( X ) into a query, we will allocate distinct indices for each copy of the message, therefore resulting in 2 K 2 unique bits of a message. This will ensure that the query at this stage will contain K 1 messages each containing L = 2 K 2 bits. In order to prepare the desired query with K messages, we need to add 2 K 2 copies of the message X K to the existing elements of P ( X ) . In the context of the example, as seen in Table 6, 4 bits of A , B , C are present in P ( { A , B , C } ) . Therefore, 4 copies of D should be added at different positions. In the next section, we provide a set of instructions to add X K .

3.2. Algorithm for Code Construction

1. Rewrite P ( { X 1 , X 2 , , X K 1 } ) as P ( { X 1 , X 2 } ) P ( { X 3 , X 4 , , X K 1 } ) , where ⨂ operator can be defined on two sets M 1 and M 2 as
M 1 M 2 = { α + β , | α M 1 , β M 2 } ,
such that ϕ + ϕ = ϕ , α + ϕ = α and ϕ + β = β . For the example with K = 4 , it is straightforward to verify that applying ⨂ operator on P ( { A , B } ) and P ( { C } ) , as given in Table 7, gives P ( { A , B , C } ) given in Table 6.
2. From Step 1, we know that the size of P ( { X 3 , X 4 , , X K 1 } ) is 2 K 3 . Form a new table with two columns, namely: Column 1 and Column 2. Excluding ϕ , replicate the 2 K 3 1 entries of P ( { X 3 , X 4 , , X K 1 } ) into two columns, therefore forming a total of 2 ( 2 K 3 1 ) = 2 K 2 2 elements. For the example, ϕ is removed from P ( { C } ) , and the remaining element is replicated into 2 columns as shown in Table 8.
3. Add X K to all the entries of Column 1. Leave Column 2 unaltered. Through this step, out of the 2 K 2 copies, 2 K 3 1 copies of X K are added. For the example, the two columns are as shown in Table 9.
4. Form a new table with two columns, namely: Column 1’ and Column 2’. Perform ⨂ operation between { ϕ , X 1 + X 2 } and all the entries in the two-tuple sum block and three-tuple sum block of Column 1 from Step 3, and place the result in Column 1’. Similarly, perform ⨂ operation between { X 1 , X 2 } and all the entries in the singleton block and two-tuple sum block of Column 2 from Step 3, and place the result in Column 2’. In the example, only a singleton block is present, and therefore, the corresponding Column 1’ and Column 2’ are presented in Table 10.
5. Skip this step if K < = 5 since largest value of n for the n-tuple sum block is 2. This is already addressed in the previous step.
  • If K = 6 or 7, perform ⨂ operation between { X 1 , X 2 } and all the entries in the n-tuple sum block, for n { 4 , 5 , , K 2 } of Column 1, and append the result in Column 1’. Similarly, perform ⨂ operation between { ϕ , X 1 + X 2 } and all the entries in the n-tuple sum block, for n { 3 , 4 , , K 3 } , of Column 2, and append the result in Column 2’.
  • If K > 7 , perform ⨂ operation between { X 1 , X 2 } and all the entries in the n-tuple sum block, for n { 4 , 5 , , K 3 } of Column 1, and append the result in Column 1’. Similarly, perform ⨂ operation between { ϕ , X 1 + X 2 } and all the entries in the n-tuple sum block, for n { 3 , 4 , , K 4 } , of Column 2, and append the result in Column 2’. However, for the ( K 2 ) -tuple sum block in Column 1, perform ⨂ operation with { ϕ , X 1 + X 2 } and append the result in Column 1’. Similarly, for the ( K 3 ) -tuple sum block in Column 2, perform ⨂ operation { X 1 , X 2 } and append the result in Column 2’.
This step is not applicable to the running example since K = 4 . At the end of this step, both Column 1’ and Column 2’ contain 2 K 2 2 elements each owing to the ⨂ operation. With this, we highlight that the union of Column 1’and Column 2’ has generated 2 K 1 4 elements of P ( { X 1 , X 2 , , X K 1 } ) . This does not include { ϕ , X 1 , X 2 , X 1 + X 2 } since ϕ of P ( { X 3 , X 4 , , X K 1 } ) was excluded when constructing Column 1 and Column 2 in Step 2. Furthermore, since X K was already added to Column 1 (containing 2 K 3 1 elements), at the end of Step 5, Column 1’ contains 2 K 2 2 copies of X K . This implies that only two more copies of X K are to be added to ensure that each message has 2 K 2 copies. In the example, Step 3 added one copy of D, and Step 4 made it two copies. Now two more copies are remaining.
6. From { ϕ , X 1 , X 2 , X 1 + X 2 } , omit ϕ , and add X K to X 2 . This generates { X 1 , X 2 + X K , X 1 + X 2 } . Place these elements in a new column, referred to as Column 3. Please note that one more copy of X K must be added to achieve 2 K 2 copies. In the example, Column 3 is given in Table 11.
7. Form the query to N 1 by taking the union of all the elements in Column 1’, Column 2’ and Column 3. By construction, this set contains X 1 + X 3 coming from Column 2’. Therefore, add the last remaining copy of X K to X 1 + X 3 , and update it as X 1 + X 3 + X K . Thus, we have a total of 2 K 1 1 elements in this query constructed by adding 2 K 2 copies of K files { X 1 , X 2 , , X K } . Finally, in the query to N 1 , provide distinct indices to every copy of a message therefore ensuring that every bit of a message is used only once. Overall, the query is a set of linear combinations of { X i , j | i [ K ] , j [ L ] } . In the example, the query to N 1 after following the above steps are given in Table 12 (without indices) and Table 13 (with indices).
Before we present the procedure to construct the query to N 2 , we present special structures in the query defined as the known byproduct combination and the unknown byproduct combination, and then present some results on their structure. Known byproduct combination are the bit combinations of byproducts in a codeword that does not contain the demand index. Formally, if X 1 is the demand, X 2 , X 3 are the side information, and the format of the codeword is H + W , where H P ( { X 2 , X 3 } ) and W P ( { X 4 , X 5 , , X K } ) \ { ϕ } , then W is the known byproduct combination. Informally, this is the combination of byproduct messages that can be retrieved from the database. Unknown byproduct combinations are the bit combinations of the byproducts in a codeword that contains the demand index with or without the side information message bits. Formally, if X 1 is the demand, X 2 , X 3 are the side information, and the codeword is of the form X 1 + H + W , where H P ( { X 2 , X 3 } ) and W P ( { X 3 , X 4 , , X K } ) \ { ϕ } , then W is the unknown byproduct combination. Informally, this is the combination of byproduct messages that cannot be retrieved from the database due to the unknown demand index that is along with it.
Proposition 1.
If the message combination W P ( { X 4 , X 5 , , X K } ) \ { ϕ } appears as an unknown byproduct in the query to N 1 , then it also exists as a known byproduct, but with different index values on each message.
Proof. 
By definition, if W is an unknown byproduct, then it appears in the query along with the demand X 1 . Since W may appear alone or along with the side information messages, we shall denote the query associated with the unknown byproduct as U = X 1 + f ( X 2 , X 3 ) + W , where f ( X 2 , X 3 ) { ϕ , X 2 , X 3 , X 2 + X 3 } . From the code construction, U must be equal to X 1 + X 3 + X K that was added in Step 7, or it must belong to either Column 1’ or Column 2’ of Step 4 and Step 5. If U = X 1 + X 3 + X K , then the corresponding known byproduct is available in Column 3 of Step 6. However, if U is available in Column 1’, then the corresponding known byproduct is also in Column 1’ because the elements of Column 1’ are generated by performing ⨂ operation with either { X 1 , X 2 } or { ϕ , X 1 + X 2 } . The same argument is also applicable if U is available in Column 2’. Finally, the index values used on the known byproduct are different from that of unknown byproduct since every copy of a message is assigned different indices as per Step 7. This completes the proof.  □
8. To generate query to N 2 , the following instructions must be followed. Copy the structure of N 1 as it is without the indices of bits. For the demand X 1 , the first 2 K 2 bits are already queried in N 1 . Therefore, give the next 2 K 2 numbers as the indices of X 1 in N 2 . Use the same index number on each message of the side information as that of the query in N 1 . From Proposition 1, the query to N 1 produces a symmetric sequence of known and unknown byproduct combinations. List the unknown and known byproduct combinations in two separate columns in the ascending order of n-tuple length following the lexicographical order and ascending order of indices of bits. For a given byproduct combination of messages in the unknown column, an identical byproduct combination exists in the known column, but with the difference that the index values used by the unknown combination is different from the known combination. To assign index values on the byproduct messages of N 2 , for a given byproduct combination, use the index values of the unknown combination of N 1 on the known combination of N 2 , and vice-versa. This ensures that all the byproduct messages can be indexed using one-to-one mapping between the unknown and the known column.
For the given example, in the fourth and fifth bit of Table 13, D 1 and D 2 are with side information, and therefore, they become the known byproduct bits. Similarly, in the sixth and seventh bit of the query to N 1 , D 3 and D 4 are with the demand, and therefore, they become unknown byproduct bits, as listed in Table 14. To generate the query for N 2 , the structure of N 1 is copied without the indices. The indices of the demand are { 5 , 6 , 7 , 8 } in N 2 . The indices of B , C are maintained as they are. Based on the one-to-one mapping in Table 14, D 3 and D 1 are swapped, and so are D 4 and D 2 . Finally, the query for N 2 is as shown in Table 15. This completes the code construction.
Theorem 1.
For N = 2 and any K > 3 , with the knowledge of side information X 2 and X 3 , the proposed code construction can retrieve 2 K 2 bits of X 1 per database by downloading 2 K 1 1 bits per database. Thus, the rate of the code is
R = 2 K 2 2 K 1 1 .
Proof. 
From the code construction, the query to N 1 and N 2 are obtained by adding 2 K 2 bits of X K to the power set structure P ( { X 1 , X 2 , , X K 1 } ) \ { ϕ } . Since the cardinality of P ( { X 1 , X 2 , , X K 1 } ) \ { ϕ } is 2 K 1 1 , and every message in P ( { X 1 , X 2 , , X K 1 } ) \ { ϕ } appears 2 K 2 times, the rate of the code is as given in (1). In the rest of the proof, we show that every bit of X 1 can be retrieved from N 1 and N 2 using the side information. If a bit of X 1 appears in the form of X 1 + f ( X 2 , X 3 ) either in N 1 or N 2 , where f ( X 2 , X 3 ) { ϕ , X 2 , X 3 , X 2 + X 3 } , then this bit can be retrieved since X 1 and X 2 are known. On the other hand, if a bit of X 1 appears in the form of X 1 + f ( X 2 , X 3 ) + W on database N 1 (or N 2 ), where W P ( { X 4 , X 5 , , X K } ) \ { ϕ } , then from Step 8 of the code construction this bit can also be retrieved using the side information and the corresponding known byproduct of W, which is downloaded from N 2 (or N 1 ). This completes the proof.  □
The above theorem provided the proof for correctness to retrieve X 1 using X 2 and X 3 as the side information, for any K > 3 . In the next section, we show that the proposed codes satisfy the joint-privacy criteria in Section 2.1.

4. Proof for Joint Privacy of XOR-Based PIR-PSI Codes

Our approach is to use the code construction that is designed for the case when X 1 is the demand and X 2 , X 3 are the side information messages. Using this code, we fix the query submitted to N 1 , and then show by construction that a query to N 2 can be generated in such a way that any demand can be retrieved from the two databases using any two messages as the side information. Considering the case of arbitrary values of K, constructions are provided in three parts, namely:
  • By fixing X K as one of the side information messages, we show that a query to N 2 can be synthesized such that any two messages out of the remaining K 1 messages can play the role of the demand and the other side information.
  • With X K as the demand, we show that a query to N 2 can be synthesized such that any two messages out of the remaining K 1 messages play the role of side information.
  • By fixing X K as one of the byproducts, we show that a query to N 2 can be synthesized such that any three messages out of the remaining K 1 messages can play the role of the demand and two side information.
We start with the construction when X K is a side information. Since the code construction is presented by adding 2 K 2 copies of X K to P ( { X 1 , X 2 , , X K 1 } ) \ { ϕ } , the privacy proof for this case is directly dependent on the power set structure of P ( { X 1 , X 2 , , X K 1 } ) \ { ϕ } . Given the power set structure, for any K 3 byproducts bits, the known and the unknown byproduct combinations in the query to N 1 are symmetric. As a result, the query submitted to N 2 must follow the same structure as that of N 1 except that (i) the index values of the demand will change from 2 K 2 + 1 to 2 K 1 instead of 1 to 2 K 2 , (ii) the known and unknown byproduct combinations are swapped similar to the proposed construction, and (iii) the index values of all the side information can be retained as they were in N 1 . The method used for constructing query to N 2 under this case is summarized in the first row of Table 16.
When X K is the demand message, for any given combination of the side information, i.e., X i X j such that i j and i , j [ K ] \ { K } , we first list the corresponding known and unknown byproduct combinations using the existing query at N 1 . Please note that these byproduct combinations will involve the bits of messages other than that of X K , X i , X j . Subsequently, we pick the query submitted to N 1 , and then apply a suitable transformation between { X 1 , X 2 , X 3 } and { X 1 , X 2 , , X K 1 } such that the known and the unknown byproduct combinations of the modified query are symmetric. Finally, if the known (or the unknown) byproduct combination in the query to N 1 is available as an unknown (or known) byproduct in the modified query, we swap their indices, otherwise, we perform suitable modifications to the modified query such that the demand X K can be retrieved. Given that the proposed code construction is applicable when X 1 is the demand and X 2 , X 3 are the side information, the same set of transformations is applicable on the query to N 1 for the side information messages within the following classes, namely: (i) the side information is one of { X 1 X 2 , X 2 X 3 } , (ii) the side information is one of { X 1 X i | 2 i K 1 , i 3 } , (iii) the side information is one of { X 2 X i | 3 i K 1 } , (iv) the side information is one of { X 3 X i | 4 i K 1 } , and (v) the side information is one of { X i X j | 4 i , j K 1 , i j } . For each of these cases, the set of transformations that must be carried on the query submitted to N 1 is presented in the third column of Table 16, whereas the set of manipulations that must be applied after the transformation is listed in the fourth column of Table 16. It is important to note that after applying the transformations in the third column, a subset of the unknown and known byproduct combinations of the query to N 1 would be symmetric with that of the transformed query. On those subsets, the known and unknown byproduct combinations must be swapped similar to the case when X K plays the role of a side information.
Finally, when X K is a byproduct, for a given demand and side information messages, we propose a sequence of transformations between the messages in the query to N 1 to ensure that the known and the unknown byproduct combinations match as much as that with that of the query to N 1 . For the cases when the known and unknown byproduct combinations do not match, we propose modifications on the transformed query to retrieve all the bits of the demand. Table 17 lists the instructions to obtain the query at N 2 for the case when X K is one of the byproducts.
In both Table 16 and Table 17, the operator ⇌ represents swapping the elements on either side of the ⇌ operator, i.e., swap all the position of element in left hand side of ⇌ with the one in its right-hand side in the given query. For example, A B implies that swap all positions of A and B in the given query. If the ⇌ operator has two juxtaposed elements in either side, swap first and second element of the left side with first and second element of the right side, respectively. Similarly, the operator ⇒ represents the replacement of the codeword in the left of the ⇒ operator with the one in the right. For example, A + B C + D implies replacing the codeword A + B with C + D in the given query. In summary, the first row of Table 16, shows that when X K is a side information, any demand can be retrieved with any side information pair in N 2 while keeping the query at N 1 unaltered and making necessary changes in N 2 without altering the structure of code in N 1 . Similarly, Table 16 and Table 17 show that the same is possible when X K is the demand and X K is one of the byproducts, respectively. This shows that the query obtained from the code construction algorithm in Section 3 can be used to retrieve any demand with any pair of side information in N 2 while keeping the query at N 1 unaltered.
Please note that Table 16 and Table 17 only provide the instructions to obtain the queries to N 2 for any demand-side information combination keeping the query at N 1 fixed. However, the correctness of the joint-privacy proof follows from the fact that the instructions for any particular demand-side information combination retraces back to the structure of query at N 1 , which was proved to be correct in Theorem 1.

5. Proof for Joint Privacy for the Code with K = 7

In this section, we demonstrate the joint-privacy proof using our code with K = 7 as presented in Table 18. We choose K = 7 for this demonstration since using K < 7 will not cover all the cases mentioned in Table 16 and Table 17. On the other hand, using K > 7 as an example is not feasible for exposition due to large queries, of length 127 and beyond. In this example, the letter G will play the role of X K , whereas the letters A , B , C , , F play the role of X 1 , X 2 , , X K 1 , respectively. The objective of this section is to show the execution of instructions presented in Table 16 and Table 17.

5.1. G as a Side Information

Recall that the queries for K > 3 , M = 2 is formed by adding 2 K 2 copies of X K (in this case G for K = 7 ) to P ( { X 1 , X 2 , , X K 1 } ) \ { ϕ } (in this case the power set structure P ( { A , B , C , D , E , F } ) \ { ϕ } ). Since G is the side information, it can be removed from downloaded bits, and therefore, the privacy proof of the code is directly dependent on the structure of P ( { A , B , C , D , E , F } ) \ { ϕ } . For any given demand and any side information from the remaining five messages, structure of P ( { A , B , C , D , E , F } ) \ { ϕ } guarantees that the known byproduct combinations and the unknown byproduct combinations in the query to N 1 are symmetric. Hence, the query submitted to N 2 follows the same structure as that of N 1 except that
  • The index values of the demand will change from 33 to 64 instead of 1 to 32.
  • The known and unknown byproduct combinations are swapped similar to the proposed construction.
  • The index values of all the side information can be retained as they were in N 1 .

5.2. G as the Demand

When G is the demand, the two side information messages can come from { A , B , , E , F } in K 1 2 = 6 2 = 15 ways. The 15 combinations are { A B , A C , A D , A E , A F , B C , B D , B E , B F , C D , C E , C F , D E , D F , E F } , implying that the two letters juxtaposed next to each other are the side information messages. These 15 combinations are grouped into five different types, namely: { A C , B C } , { A B , A D , A E , A F } , { B D , B E , B F } , { C D , C E , C F } and { D E , D F , E F } . The reason for this classification is attributed to the fact that the query to N 1 was constructed assuming A as the demand and B , C as the side information, and therefore, when we have to design the new query to N 2 , it should match with the existing query to N 1 .

5.2.1. One of { A C , B C } as Side Information and G as the Demand

When either A C or B C are the side information messages, the known and unknown byproduct combinations are symmetric. With the side information A C , the pattern of unknown and known byproduct combinations without the indices are given in Table 19. Therefore, the demand G can be retrieved by swapping the indices of the known and unknown byproduct combinations. Similar to the code construction, when submitting the query to N 2 , the indices on side information must be the same, whereas the indices of the demand on N 2 must be new.
In the case when B C are the side information messages, the pattern of the known and the unknown byproduct combinations remains symmetric, and therefore, the query to N 2 is similar to that when A C were the side information messages. The only exception is that the role of A and B is swapped as A becomes a byproduct and B becomes a side information. Thus, all the bits of G can be retrieved from both databases without altering the structure of query to N 1 when one of { A C , B C } are the side information messages.

5.2.2. One of { A B , A D , A E , A F } as Side Information and G as the Demand

In the case when one of { A B , A D , A E , A F } are the side information, the known and unknown byproduct combinations are almost symmetric with one exception that a singleton bit of byproduct C goes to the unknown side from the known side. For instance, when A B are the side information, the known and unknown byproduct combinations are as shown in the first two columns of Table 20. Therefore, the query to N 2 should somehow accommodate this extra unknown bit without changing the structure. To construct a query to N 2 , we use the query to N 1 and make appropriate modifications as discussed hereafter. For exposition, we take the case when A B are the side information. We already know that the query to N 1 gives a symmetric known-unknown byproduct combinations for side information A C and demand G. We pick the query submitted to N 1 , and propose a simple transformation of BC, i.e., swapping all positions of B with C, to generate a new query. Due to the transformation, it is clear that this new query gives a symmetric known-unknown byproduct combinations when G is the demand and A B are the side information. This pattern of unknown and known byproduct combinations are shown in the third and the fourth columns of Table 20.
We now provide modifications on the new query after the transformation BC so that we can use as our query to N 2 . To help this cause, the original query to N 1 for K = 7 (without indices) is numbered from 1 to 63 for each codeword in Table 18. Since one bit of C moved to the unknown side from the known side in the existing query to N 1 , we pick the new query (after the transformation) and then swap the singleton bit A (at bit number 1) and the bit C from the two-tuple sum C + G (bit number 10). This ensures that the extra unknown bit C is retrieved in bit number 1 while still being able to retrieve the demand G bit in bit number 10 since A is a side information. This sequence of operations from taking a copy of the query to N 1 , the transformation of BC, and the final exchange in bit positions 1 and 10 are displayed in the last three columns of Table 21. The rows of Table 21 indicated in red are the ones that are modified. Thus, the last column of this table forms the query to N 2 when A B are the side information. Of course, swapping of the known-unknown byproducts indices is required wherever they are symmetric.
In general, when handling the other cases of { A D , A E , A F } as the side information, the procedure for obtaining query for N 2 is similar to that when A B is the side information. We pick the query submitted to N 1 and perform the transformation of C with D , E , F for the cases A D , A E , A F , respectively. The modifications made to the new query after the transformation is the same as that when A B were the side information. Finally, the bit numbers would change according to the new position of codeword C + G .

5.2.3. One of { B D , B E , B F } as Side Information and G as the Demand

In the case when one of { B D , B E , B F } are the side information, the known and unknown byproduct combinations are almost symmetric with two exceptions that a two-tuple sum of byproduct combination, A + C goes to the unknown side from the known side while a bit of byproduct A goes to the known side from the unknown side. For instance, when B D are the side information, the known and unknown byproduct combinations are as shown in the first two columns of Table 22. Therefore, the query to N 2 should somehow accommodate these deviations without changing the structure. To construct a query to N 2 , we use the query to N 1 and make appropriate modifications as discussed hereafter. For exposition, we take the case when B D are the side information. We already know that the query to N 1 gives a symmetric known-unknown byproduct combinations for side information A C and demand G. We pick the query submitted to N 1 , and perform a transformation of AB and CD, to generate a new query. Due to the transformation, it is clear that this new query gives a symmetric known-unknown byproduct combinations when G is the demand and B D are the side information. This pattern of unknown and known byproduct combinations are shown in the third and the fourth columns of Table 22.
Since a bit of A + C is moved to the unknown side from the known side in the existing query to N 1 , there is only one known bit of A + C available to retrieve G. But the query after transformation uses 2 bits of A + C (bit number 39 and 45) to retrieve 2 bits of G as seen in the third column of Table 23. Since we have one extra bit of A available, to obtain the extra bit of A + C , the bit C + G in bit number 12 is replaced with bit B + G . G is still retrievable since B is side information. The bit of C freed from bit number 12 along with extra bit of A contributes to the second A + C bit. Since one more B is added to the query, the singleton bit of B is replaced with demand bit G as seen in bit number 1 in the table below. Since one extra demand bit is retrieved, the bit number 38 is changed from B + A + D + G to B + A + D + C so that the extra unknown bit of A + C is also acquired. Since one bit of C was removed in bit number 12, this change will bring back the uniform distribution of bits while keeping the structure of query at N 2 maintained as that of N 1 . This sequence of operations from taking a copy of the query to N 1 , the transformation of AB and CD, and the final exchange in bit positions 1, 12, and 38 are displayed in the last three columns of Table 23. Thus, the last column of this table forms the query to N 2 when B D are the side information. Of course, swapping of the known-unknown byproducts indices is required wherever they are symmetric.
In general, when handling the other cases of { B E , B F } as the side information, the procedure for obtaining query for N 2 is similar to that when B D were the side information. We pick the query submitted to N 1 and perform the transformation between A with B, and then between C and E (or F), for B E (or B F ) as the side information. The modifications made to the new query after the transformation when B D were the side information can be reproduced to retrieve G from N 2 .

5.2.4. One of { C D , C E , C F } as Side Information and G as the Demand

In the case when one of { C D , C E , C F } are the side information, there is a drastic change in the known and unknown byproduct combinations compared to the previous cases when of G is the demand. For instance, when C D are the side information the singleton bits of byproducts A and B are unknown only one time whereas they are known for three times. The two-tuple sum block combinations of byproducts except A + B are unknown only one time but are known three times whereas A + B is unknown three times but known only one time. All the three-tuple sum blocks combinations of byproducts are unknown three times while they are known only once. The four-tuple sum block combinations of byproducts are known three times while they are unknown only once. The known and unknown byproduct combinations are as shown in Table 24.
The query to N 2 should somehow accommodate these deviations without changing the structure. To construct a query to N 2 , we use the query to N 1 and make appropriate modifications as discussed hereafter. For exposition, we take the case when C D are the side information. We already know that the query to N 1 gives a symmetric known-unknown byproduct combinations for side information A C and demand G. We pick the query submitted to N 1 , and perform the transformation AD, to generate a new query. Due to the transformation, it is clear that this new query gives a symmetric known-unknown byproduct combinations when G is the demand and C D are the side information. Since one bit of A + B moves towards the unknown side from the known side, there is only one bit of A + B available in known bits to retrieve G. But the new query after transformation uses 2 bits of A + B (bit number 39 and 43) to retrieve 2 bits of G as seen in the third column of Table 25. This is rectified by swapping bit G in bit number 39 with F, therefore retrieving the extra bit of A + B + F required in the unknown while removing the necessity of second known bit of A + B . This increments and decrements the bit count (total number of bits of a message) of F and G respectively by 1. The extra bit of A + B required is obtained by swapping bit E in the bit number 19 with B since all the two-tuple sum combinations except A + B are unknown only once. This increments and decrements the bit count of B and E respectively by 1. Since the bit A + F is unknown only once, the bit number 29, which is the second query for A + F is changed to B + D + G to use the extra known bit B along with side information D to retrieve G. This neutralises the differences occurred in bit count of F and G and also increments the bit count of B and D and decrements the bit count of A and C respectively by 1. B has a net increment of 2 in the bit count. This increment of D and decrement of C is neutralised in bit number 56 by swapping D with C. Now the four-tuple sum bit A + B + E + F is known three times and is unknown only once. Therefore B and side information C are swapped in bit numbers 49 and 62. Bit number 49, which was initially querying a bit of A + B + E + F will now query the extra unknown bit of A + E + F . Bit number 62 was supposed to be the second query for G bit using A + E + F but all the three-tuple sum bits have only one known bit. This A + E + F is replaced by the extra known bit of A + B + E + F . The extra unknown bit of three-tuple sum bit B + E + F is retrieved by swapping G with F in bit number 40. This increments and decrements the bit count of F and G respectively by 1. Bit numbers 15 and 23 which queries the second bit A and B + E respectively are together used to retrieve the extra unknown bit of A + B + E since A and B + E are unknown only once. Bit numbers 57–59 uses three-tuple sums A + B + E , A + B + F and B + E + F to retrieve G for the second time but they are known only once. Therefore, these bits are obtained by combining the bits { A , B + E } , { A , B + F } and { B , E + F } since A, B and all the two-tuple sum blocks except A + B are known one extra time. B + D of bit number 38 is replaced with A + E and B of bit number 41 is replaced with A so that the extra two-tuple sum bits, A + E and A + F will be used to retrieve G. This neutralises the bit count of B and E while increments the bit count of A by 2 and decrements the bit count of D by 1. Since bit count of A was already lagging 1 bit behind, this step increases it by 2 bits to give a net increment of 1 for A. C of bit number 33 is replaced with B and C + A of bit number 28 is replaced with B + G so that the extra two-tuple sum bits, B + E and B + F will be used to retrieve G. This neutralises the bit count of G and A while decrements the bit count of D by 1. This also increments and decrements the bit count of B and C respectively by 2. The B from bit number 10 is swapped with side information D, while D itself in bit number 1 is swapped with G. The G bit and B bit of bit numbers 14 and 2 are swapped with C to obtain the second unknown bit of F and therefore neutralising B , C and G. B is swapped with E in both bit numbers 6 and 9 to retrieve extra unknown bit E and only unknown bit of E + F . This increments and decrements the bit count of E and B respectively by 2. E in bit numbers 21 and 31 are swapped with G and B respectively and F in bit number 31 is swapped with D to retrieve extra unknown bit of F and only unknown bit of B. This neutralises D , E and F while incrementing B and G one time with B with a net decrement of 1 bit. G of bit number 13 is swapped with A to retrieve the only known bit of A + E while A of bit number 30 is swapped with the last known bit of B to retrieve G which neutralises the bit count of B and G and achieving the uniform distribution of bits while keeping the structure of query at N 2 maintained as that of N 1 . This sequence of operations from taking a copy of the query to N 1 , the transformation of AD, and the final exchange in bit positions are displayed in the last three columns of Table 25. Thus, the last column of this table forms the query to N 2 when C D are the side information. Of course, swapping of the known-unknown byproducts indices is required wherever they are symmetric.
In general, when handling the other cases of { C E , C F } as the side information, the procedure for obtaining query for N 2 is similar to that when C D are the side information. We pick the query submitted to N 1 and perform the transformation between A with D. The modifications made to the new query after transformation when C D were the side information can be reproduced to retrieve G from N 2 .

5.2.5. One of { D E , D F , E F } Is the Side Information and G Is the Demand

Compared to the previous case (Section 5.2.4), this case has one more singleton bit of A going to the known side from the unknown side and one bit of A + C going from the known side to the unknown side for all side information from { D E , D F , E F } . A minor modification to the previous code for N 2 seen in Table 25 can incorporate the change required. Since the fourth column of Table 25 gave the query to N 2 for demand G and side information C D , swap C D with the desired side information from { D E , D F , E F } to obtain a new query. Since one more A goes to the known side, all 4 bits of A are known. Therefore, a side information in the bit number 15 in the fourth column of Table 25 which queries the only unknown A can be replaced with C to make it retrieve A + C . Bit number 38 which retrieves G using A + C can be now used to retrieve G using the fourth known A bit by swapping C with the side information swapped before. Therefore, all bits of G can be retrieved from both databases when one of { D E , D F , E F } is the side information without altering the structure of query from N 1 .

5.3. G as a Byproduct

G can be byproduct in (the demand can come from { A , B , C , D , E , F } in K 1 1 = 6 1 = 6) × (the 2 side information messages can come from { A , B , C , D , E , F } D e m a n d in K 2 2 = 5 2 = 10) = 6 × 10 = 60 ways. This is subdivided into 4 different cases.

5.3.1. A Is the Demand

When A is the demand and B C are the side information, the known and unknown byproduct combinations are symmetric. The demand can be retrieved similar to the operation mentioned in step 8 of the code construction in Section 3. Now when one of { B D , B E , B F } are the side information there is a small difference from symmetry. In the unknown side one singleton bit of C and G is removed (does not go to the known side) and one bit of C + G is added to unknown (is not removed from known). The structure of code remains the same as that of N 1 since the C and G of the extra unknown C + G bit can be obtained from the individual querying itself since one singleton bit of C and G is removed from unknown. Now when one of { C D , C E , C F } are the side information, the known and unknown byproduct combinations are similar to the case when G was the demand and one of { C D , C E , C F } were the side information (Section 5.2.4). A simple transformation of AG in the code structure provided in Section 5.2.4 will provide the necessary query to N 2 . Now when one of { D E , D F , E F } is the side information, the known and unknown byproduct combinations are similar to the case of { C D , C E , C F } with a small difference. The difference is same as { B D , B E , B F } case, in the unknown side one singleton bit of C and G is removed (does not go to the known side) and one bit of C + G is added to unknown (is not removed from known). The structure of code remains the same as { C D , C E , C F } since the C and G of the extra unknown C + G bit can be obtained from the individual querying itself since one singleton bit of C and G is removed from unknown. This completes all side information cases for A as a demand and G as one of the byproducts. Therefore, all cases with A as a demand is retrievable.

5.3.2. B Is the Demand

When B is the demand, the cases are similar to A as the demand except for the side information set { D E , D F , E F } . When B is the demand and A C are the side information, the known and unknown byproduct combinations are symmetric. The demand can be retrieved similar to the operation mentioned in step 8 of the code construction in Section 3. Now when one of { A D , A E , A F } are the side information there is a small difference from symmetry. In the unknown side one singleton bit of C and G is removed (does not go to the known side) and one bit of C + G is added to unknown (is not removed from known). The structure of code remains the same as that of N 1 since the C and G of the extra unknown C + G bit can be obtained from the individual querying itself since one singleton bit of C and G is removed from unknown. Now when one of { C D , C E , C F } are the side information, the known and unknown byproduct combinations are similar to the case when G was the demand and one of { C D , C E , C F } were the side information (Section 5.2.4). A simple transformation of BG in the code structure provided in Section 5.2.4 will provide the necessary query to N 2 . Now when one of { D E , D F , E F } is the side information, the known and unknown byproduct combinations are similar to the case when G was the demand and one of { D E , D F , E F } were the side information (Section 5.2.5) with a small difference. The unknown bit A + C is replaced with just A while the known bit A + G is replaced with A + C + G . When G was the demand and one of { C D , C E , C F } were the side information, for obtaining second known bit of A + B + E we had to combine individual bits of A and B + E as explained in Section 5.2.4. Similar operation was performed for A + B + C in Section 5.2.5. Since second A + C + G (which is analogous of A + B + C from Section 5.2.5) bit is available as known, we can use it directly to query demand B therefore freeing individual bits of A and C + G . Now this free known bit C + G is used in place of retrieving B with singleton G. This frees a singleton G and this along with the singleton A freed before is used to retrieve B with bit A + G (since the only known A + G was converted to A + C + G ). Finally, the query bit that retrieves A + C is now used to retrieve the new unknown A bit. This completes all side information cases for B as a demand and G as one of the byproducts. Therefore, all cases with B as a demand is retrievable.

5.3.3. C Is the Demand

When C is the demand and one of { A B , A D , A E , A F } are the side information, the known and unknown byproduct combinations are similar to the case when G was the demand and one of { A B , A D , A E , A F } were the side information (Section 5.2.2). The query for N 2 can be obtained similar to that case with a transformation of CG. When one of { B D , B E , B F } are the side information, the known and unknown byproduct combinations are similar to the case when G was the demand and one of { B D , B E , B F } were the side information (Section 5.2.3). The query for N 2 can be obtained similar to that case with a transformation of CG. When one of { D E , D F , E F } are the side information, the known and unknown byproduct combinations is similar to the one when B was the demand and one of { D E , D F , E F } were the side information (Section 5.3.2) with some minor differences. In the unknown side, one bit of A + G is removed while one bit of A and 2 bits of G are included. In the known side 2 bits of B + G are replaced by just B while one bit of A + B is replaced by A + B + G . For instance, when E F are the side information, the known and unknown byproduct combinations are as shown in the first two columns of Table 26.
The query to N 2 should somehow accommodate these deviations without changing the structure. For exposition, we take the case when E F are the side information. To construct a query to N 2 , we use the query to N 2 from Table 25 and make appropriate modifications as discussed hereafter. To this query we perform the transformation C D E F , to generate a new query. To this query we perform the modifications mentioned as in the case of G as the demand and one of { D E , D F , E F } as the side information to obtain a new query. To this query we perform a transformation BG to obtain a new query. To this query we perform the modifications mentioned as in the case of B as the demand and one of { D E , D F , E F } as the side information to obtain a new query. Please note that this query is exactly the query to N 2 for the case of B as the demand and E F are the side information. To this query we perform a transformation of BC as seen in third column of Table 27. Please note that the third column of Table 27 is not obtained by direct transformation of BC in N 1 . Rather, it is obtained after the execution of various steps as discussed earlier. Since one bit of A + G is removed from the unknown, bit number 7 which was initially querying A + G can now be used to query one extra bit of G. Bit number 2 which was just a combination of side information E + F can be used to query second extra bit of G. Bit number 8 and 28 are modified to query C with two extra known singleton B bits since one B + G bit in known set is removed. Since bit number 8 which queried B + G which was required to obtain third bit of unknown A + B + G is modified, the third bit of A + B + G is queried by modifying bit number 38. This modification removes the retrieval of one bit of demand using A + D . This is neutralised by modifying bit number 41 to remove query of demand with B + G (since 2 bits of B + G was removed from known set) and replace it with A + D . Since this A + B + G is queried directly, A retrieved in bit number 11 which was supposed to be the A in A + B + G can be now used to retrieve the extra singleton bit A which came to the unknown side. Finally, bit number 53 which was the bit that used A + B to query C can now be used to query A + B + D + G (since one bit of A + C is removed from known) while bit number 61 which was initially supposed to query A + B + D + G is now used to retrieve C with the extra A + B + G bit that is available in the known set. Query to N 1 , the transformation of BC to query of N 2 for the case of B as the demand and E F are the side information, and the final exchange in bit positions are displayed in the last three columns of Table 27. Thus, the last column of this table forms the query to N 2 when E F are the side information and C is the demand.
In general, when handling the other cases of { D E , D F } as the side information, the procedure for obtaining query for N 2 is similar to that when E F are the side information. We pick the query submitted to N 2 for the case of B as the demand and { D E , D F } as the side information respectively and perform the transformation between B with C. The modifications made to the new query after transformation when E F were the side information can be reproduced to retrieve B from N 2 .

5.3.4. One of { D , E , F } Is the Demand

When one of { D , E , F } is the demand, the known and unknown byproduct combinations are symmetric if either A or B is one of the side information. The demand can be retrieved similar to the operation mentioned in step 8 of the code construction in Section 3. For other side information pairs which does not have either A or B in side information, the known and unknown byproduct combinations are same as the previous case where C was the demand and one of { D E , D F , E F } were side information with two exceptions. One bit of A goes to the unknown side while one bit of A + G comes to the known side. For exposition let us consider D as the demand. To obtain the query for N 2 , perform the transformation of CD to the query for N 2 in Table 27. To this new query, use any bit that queries A + G to query A. Use any bit that retrieves D using A to retrieve D using A + G .
In general, when handling the other cases of { E , F } as the demand, pick the query submitted to N 2 for the case of C as the demand and { D E , D F , E F } as the side information respectively and perform the transformation between C with demand. The modifications made to the new query after transformation when D was the demand can be reproduced to retrieve demand from N 2 . This completes all side information cases when one of { D , E , F } is the demand and G is one of the byproducts. Therefore, all cases with one of { D , E , F } as the demand are retrievable.

6. Discussion and Directions for Future Work

In this work, we have presented the first XOR-based code construction for a PIR-PSI setting involving N = 2 databases and M = 2 side information. We have shown that our codes achieve the rate 2 K 2 2 K 1 1 . Although our code construction marginally falls short of the capacity of PIR-PSI setting, it offers substantial reduction in the decoding complexity when compared to the MDS counterpart (which achieves the capacity). This implies that our codes are applicable when multiple files have to be downloaded by a user at different time-instants from the two databases. We believe that this work can be extended in one of the following directions, namely: (i) How to construct XOR-based PSR-PSI codes for N = 2 non-colluding databases with arbitrary values of M side information messages? (ii) How to construct XOR-based PSR-PSI codes for arbitrary values of N and M? and finally, (iii) Do XOR-based PIR-PSI codes exist that achieve the capacity of the PSR-PSI setting? Importantly, we have shown that our codes provide rates strictly higher than the capacity of PIR schemes. Among the above set of questions posed for future research, we believe that solving (iii) is challenging. A probable reason for the fall in rate for XOR-based code constructions is the XOR constraint itself. In the simplest setting of K = 4 , the capacity is 2 3 . To achieve this rate, the query must consist of 3 codewords satisfying the criteria in Section 2.1 such that 2 of them retrieve the demand. Using exhaustive search, we observe that this scenario is hard to begin with, and therefore, we believe that the problem is challenging for arbitrary values of K.

Author Contributions

Conceptualization, M.K.K.H. and J.H. All authors equally contributed to this work. All authors have read and agreed to the published version of the manuscript.

Funding

This work was supported by the Indigenous 5G Test Bed Project from the Department of Telecommunications, Ministry of Communications, New Delhi, India.

Institutional Review Board Statement

Not applicable.

Informed Consent Statement

Not applicable.

Conflicts of Interest

The authors declare no conflict of interest.

References

  1. Chor, B.; Goldreich, O.; Kushilevitz, E.; Sudan, M. Private information retrieval. In Proceedings of the 36th Annual Symposium on Foundations of Computer Science, Milwaukee, WI, USA, 23–25 October 1995; pp. 41–50. [Google Scholar]
  2. Sun, H.; Jafar, S.A. The Capacity of Private Information Retrieval. IEEE Trans. Inf. Theory 2017, 63, 4075–4088. [Google Scholar] [CrossRef]
  3. Lex, C.J.; Gnilke, O.W. Low-Complexity PIR Using Subfield Subcodes. arXiv 2021, arXiv:2105.07369. [Google Scholar]
  4. Xu, J.; Zhang, Z. Building capacity-achieving PIR schemes with optimal sub-packetization over small fields. In Proceedings of the IEEE International Symposium on Information Theory, Vail, CO, USA, 17–22 June 2018; pp. 1749–1753. [Google Scholar]
  5. Banawan, K.; Ulukus, S. The capacity of private information retrieval from coded databases. IEEE Trans. Inf. Theory 2018, 64, 1945–1956. [Google Scholar] [CrossRef]
  6. Tajeddine, R.; Gnilke, O.W.; Rouayheb, S.E. Private information retrieval from mds coded data in distributed storage systems. IEEE Trans. Inf. Theory 2018, 64, 7081–7093. [Google Scholar] [CrossRef]
  7. Sun, H.; Jafar, S.A. The capacity of robust private information retrieval with colluding databases. IEEE Trans. Inf. Theory 2018, 64, 2361–2370. [Google Scholar] [CrossRef]
  8. Tandon, R. The capacity of cache aided private information retrieval. In Proceedings of the 2017 55th Annual Allerton Conference on Communication, Control, and Computing (Allerton), Monticello, IL, USA, 3–6 October 2017; pp. 1078–1082. [Google Scholar]
  9. Heidarzadeh, A.; Kazemi, F.; Sprintson, A. Capacity of Single-Server Single-Message Private Information Retrieval with Coded Side Information. In Proceedings of the 2018 IEEE Information Theory Workshop (ITW), Guangzhou, China, 25–29 November 2018; pp. 1–5. [Google Scholar]
  10. Kazemi, F.; Karimi, E.; Heidarzadeh, A.; Sprintson, A. Private Information Retrieval with Private Coded Side Information: The Multi-Server Case. In Proceedings of the 2019 57th Annual Allerton Conference on Communication, Control, and Computing (Allerton), Monticello, IL, USA, 24–27 September 2019; pp. 1098–1104. [Google Scholar]
  11. Li, S.; Gastpar, M. Converse for Multi-Server Single-Message PIR with Side Information. In Proceedings of the 2020 54th Annual Conference on Information Sciences and Systems (CISS), Princeton, NJ, USA, 18–20 March 2020; pp. 1–6. [Google Scholar]
  12. Wei, Y.; Ulukus, S. Private Information Retrieval with Private Side Information Under Storage Constraints. In Proceedings of the 2018 IEEE Information Theory Workshop (ITW), Guangzhou, China, 25–29 November 2018; pp. 1–5. [Google Scholar]
  13. Shariatpanahi, S.P.; Siavoshani, M.J.; Maddah-Ali, M.A. Multi-Message Private Information Retrieval with Private Side Information. In Proceedings of the 2018 IEEE Information Theory Workshop (ITW), Guangzhou, China, 25–29 November 2018; pp. 1–5. [Google Scholar]
  14. Kadhe, S.; Garcia, B.; Heidarzadeh, A.; Rouayheb, S.E.; Sprintson, A. Private information retrieval with side information: The single server case. In Proceedings of the 2017 55th Annual Allerton Conference on Communication, Control, and Computing (Allerton), Monticello, IL, USA, 3–6 October 2017; pp. 1099–1106. [Google Scholar]
  15. Chen, Z.; Wang, Z.; Jafar, S.A. The Capacity of T-Private Information Retrieval With Private Side Information. IEEE Trans. Inf. Theory 2020, 65, 4761–4773. [Google Scholar] [CrossRef] [Green Version]
  16. Sun, H.; Jafar, S.A. The Capacity of Symmetric Private Information Retrieval. IEEE Trans. Inf. Theory 2018, 65, 322–329. [Google Scholar] [CrossRef] [Green Version]
  17. Sun, H.; Jafar, S.A. Optimal Download Cost of Private Information Retrieval for Arbitrary Message Length. IEEE Trans. Inf. Forensics Secur. 2017, 12, 2920–2932. [Google Scholar] [CrossRef]
  18. Tian, C.; Sun, H.; Chen, J. Capacity-Achieving Private Information Retrieval Codes With Optimal Message Size and Upload Cost. IEEE Trans. Inf. Theory 2019, 65, 7613–7627. [Google Scholar] [CrossRef]
  19. Tan, X.; Huang, C.; Ji, L. Access Control Scheme Based on Combination of Blockchain and XOR-Coding for ICN. In Proceedings of the 5th IEEE International Conference on Cyber Security and Cloud Computing (CSCloud), New York, NY, USA, 3–5 November 2018. [Google Scholar]
  20. Chou, R.A.; Kliewer, J. Secure Distributed Storage: Rate-Privacy Trade-Off and XOR-Based Coding Scheme. In Proceedings of the IEEE International Symposium on Information Theory (ISIT), Los Angeles, CA, USA, 21–26 June 2020; pp. 605–610. [Google Scholar]
  21. Seo, Y.-S.; Huh, J.-H. GUI-based software modularization through module clustering in edge computing based IoT environments. J. Ambient. Intell. Humaniz. Comput. 2019, 22, 7287–7311. [Google Scholar] [CrossRef]
  22. Wang, Y. Privacy-Preserving Data Storage in Cloud Using Array BP-XOR Codes. IEEE Trans. Cloud Comput. 2005, 3, 425–435. [Google Scholar] [CrossRef]
  23. Harshan, J. XOR-Based Codes for Private Information Retrieval with Private Side Information. arXiv 2021, arXiv:2105.05788. [Google Scholar]
Figure 1. Rate of the proposed code construction along with the capacity of the PIR-PSI scheme for M = 2 and N = 2 .
Figure 1. Rate of the proposed code construction along with the capacity of the PIR-PSI scheme for M = 2 and N = 2 .
Entropy 23 01287 g001
Table 1. Table comparing the rate of our scheme with the capacity of PIR-PSI setting.
Table 1. Table comparing the rate of our scheme with the capacity of PIR-PSI setting.
SchemeRateMethodComputational Complexity
 [15] 2 K 3 2 K 2 1 MDS codingHigh. Exponential as
(higher than our code) K increases. Finite field
multiplication involved.
Our scheme 2 K 2 2 K 1 1 XORLow. Bit-wise XOR involved
 [2] 2 K 1 2 K 1 XORLow. Bit-wise XOR involved
(lower than our code)
Table 2. Query obtained as per the proposed code construction when A is the demand, and B and C are the side information.
Table 2. Query obtained as per the proposed code construction when A is the demand, and B and C are the side information.
Query to N 1 Query to N 2
A 1 A 5
A 2 + B 1 A 6 + B 1
B 2 + C 1 B 2 + C 1
B 3 + D 1 B 3 + D 3
C 2 + D 2 C 2 + D 4
A 3 + C 3 + D 3 A 7 + C 3 + D 1
A 4 + B 4 + C 4 + D 4 A 8 + B 4 + C 4 + D 2
Table 3. For a given query to N 1 (in the first column), all possible queries to N 2 when D is a side information.
Table 3. For a given query to N 1 (in the first column), all possible queries to N 2 when D is a side information.
Query to N 1 ( A , BD , C )( A , CD , B )( B , AD , C )( B , CD , A )( C , AD , B )( C , BD , A )
A 1 A 5 A 5 A 1 A 2 A 1 A 3
A 2 + B 1 A 6 + B 1 A 6 + B 2 A 2 + B 5 A 1 + B 5 A 2 + B 2 A 4 + B 1
B 2 + C 1 B 2 + C 3 B 1 + C 3 B 6 + C 2 B 6 + C 2 B 1 + C 5 B 2 + C 5
B 3 + D 1 B 3 + D 1 B 4 + D 1 B 7 + D 1 B 7 + D 1 B 4 + D 1 B 4 + D 1
C 2 + D 2 C 4 + D 2 C 4 + D 2 C 1 + D 2 C 1 + D 2 C 6 + D 2 C 6 + D 2
A 3 + C 3 + D 3 A 7 + C 1 + D 3 A 7 + C 1 + D 3 A 3 + C 4 + D 3 A 4 + C 4 + D 3 A 3 + C 7 + D 3 A 1 + C 7 + D 3
A 4 + B 4 + C 4 + D 4 A 8 + B 4 + C 2 + D 4 A 8 + B 3 + C 2 + D 4 A 4 + B 8 + C 3 + D 4 A 3 + B 8 + C 3 + D 4 A 4 + B 3 + C 8 + D 4 A 2 + B 3 + C 8 + D 4
Table 4. All possible queries to N 2 when D is a byproduct.
Table 4. All possible queries to N 2 when D is a byproduct.
Query to N 1 ( A , BC , D )( B , AC , D )( C , AB , D )
A 1 A 5 A 1 D 2
A 2 + B 1 A 6 + B 1 A 2 + B 5 A 1 + D 3
B 2 + C 1 B 2 + C 1 B 6 + C 1 B 1 + C 5
B 3 + D 1 B 3 + D 3 B 7 + D 2 B 2 + D 4
C 2 + D 2 C 2 + D 4 C 2 + D 1 A 2 + C 6
A 3 + C 3 + D 3 A 7 + C 3 + D 1 A 3 + C 3 + D 4 A 3 + B 3 + C 7
A 4 + B 4 + C 4 + D 4 A 8 + B 4 + C 4 + D 2 A 4 + B 8 + C 4 + D 3 A 4 + B 4 + C 8 + D 1
Table 5. All possible queries to N 2 when D is the demand.
Table 5. All possible queries to N 2 when D is the demand.
Query to N 1 ( D , BC , A )( D , AC , B )( D , AB , C )
A 1 D 5 A 1 C 2
A 2 + B 1 D 6 + B 1 A 2 + D 5 A 1 + C 3
B 2 + C 1 B 2 + C 1 D 6 + C 1 B 1 + D 5
B 3 + D 1 B 3 + A 3 D 7 + B 2 B 2 + C 4
C 2 + D 2 C 2 + A 4 C 2 + B 3 A 2 + D 6
A 3 + C 3 + D 3 D 7 + C 3 + A 1 A 3 + C 3 + B 4 A 3 + B 3 + D 7
A 4 + B 4 + C 4 + D 4 D 8 + B 4 + C 4 + A 2 A 4 + D 8 + C 4 + B 2 A 4 + B 4 + D 8 + C 1
Table 6. P ( X ) for the running example.
Table 6. P ( X ) for the running example.
P ( { A , B , C } )
ϕ
A
B
C
A+B
A+C
B+C
A+B+C
Table 7. Step 1 applied on the running example.
Table 7. Step 1 applied on the running example.
P ( { A , B } ) P ( { C } )
ϕ ϕ
AC
B
A+B
Table 8. Step 2 applied on the running example.
Table 8. Step 2 applied on the running example.
Column 1Column 2
CC
Table 9. Step 3 applied on the running example.
Table 9. Step 3 applied on the running example.
Column 1Column 2
C+DC
Table 10. Step 4 applied on the running example.
Table 10. Step 4 applied on the running example.
Column 1’Column 2’
C+DC+A
C+D+A+BC+B
Table 11. Step 6 applied on the running example.
Table 11. Step 6 applied on the running example.
Column 3
A
B+D
A+B
Table 12. Step 7 applied on the running example without indices.
Table 12. Step 7 applied on the running example without indices.
Query to N 1 without Indices
A
A + B
B + C
B + D
C + D
A + C + D
A + B + C + D
Table 13. Step 7 applied on the running example with indices.
Table 13. Step 7 applied on the running example with indices.
Query to N 1 with Indices
A 1
A 2 + B 1
B 2 + C 1
B 3 + D 1
C 2 + D 2
A 3 + C 3 + D 3
A 4 + B 4 + C 4 + D 4
Table 14. Unknown and known byproducts of the running example.
Table 14. Unknown and known byproducts of the running example.
UnknownKnown
D 3 D 1
D 4 D 2
Table 15. Final query to N 1 and N 2 .
Table 15. Final query to N 1 and N 2 .
Query to N 1 Query to N 2
A 1 A 5
A 2 + B 1 A 6 + B 1
B 2 + C 1 B 2 + C 1
B 3 + D 1 B 3 + D 3
C 2 + D 2 C 2 + D 4
A 3 + C 3 + D 3 A 7 + C 3 + D 1
A 4 + B 4 + C 4 + D 4 A 8 + B 4 + C 4 + D 2
Table 16. Instructions to obtain query at N 2 when X K is either SI or demand.
Table 16. Instructions to obtain query at N 2 when X K is either SI or demand.
No.CaseTransformationManipulations
1 X K as SINoneSwap the known and unknown
byproducts to obtain query at N 2 .
2 X K as demand,NoneSwap the known and unknown
X 1 X 3 or X 2 X 3 are SI byproducts to obtain query at N 2 .
3 X K as demandPick query atSwap the singleton bit X 1
X 1 X i are SI N 1 and applyand the bit X 3 from
2 i K 1 , i 3 X i X 3 the two-tuple sum X 3 + X K
4 X K as demandPick query at X 3 + X K X 2 + X K
X 2 X i are SI N 1 and apply X 2 X K
4 i K 1 X 1 X 3 X 2 X i X 2 + X 1 + X i + X K X 2 + X 1 + X i + X 3
5 X K as demandPick query atIf i = 4 and K 7 , perform the following:
X 3 X i are SI N 1 and apply X 4 X K , X 2 + X 4 X 3 + X 4 , X 2 + X 3 X 5 + X 3 ,
4 i K 1 X 1 X 4 X 2 + X 6 X 5 + X 6 , X 2 + X K X 4 + X K , X 5 + X K
X 5 + X 1 , X 6 + X K X 6 + X 3 , X 4 + X 1 + X 5
X 4 + X 1 + X 2 , X 4 + X 5 + X 6 X 4 + X K + X 6 ,
X 3 + X 1 + X 5 X 2 + X K + X 5 , X 3 + X 1 + X 6
X 2 + X K + X 4 , X 3 + X 1 + X K X 2 + X K + X 3 ,
X 3 + X 5 + X 6 X 3 + X 2 + X 4 , X 3 + X 6 + X K
X 2 + X 6 + X K , X 4 + X 2 + X 3 + X K X 1 + X 5 + X 3 + X K ,
X 4 + X 2 + X 1 + X K X 1 + X 2 + X 6 + X 4 ,
X 4 + X 2 + X 5 + X K X 4 + X 2 + X 5 + X 6 ,
X 4 + X 2 + X 6 + X K X 4 + X 1 + X 6 + X K ,
X 4 + X 2 + X 1 + X 5 + X 6 X 4 + X 3 + X 1 + X 5 + X 6 ,
X 4 + X 1 + X 5 + X 6 + X K X 3 + X 1 + X 5 + X 6 + X K ,
X 4 + X 3 + X 1 + X 5 + X 6 + X K
X 4 + X 2 + X 1 + X 5 + X 6 + X K . For  i 4 and K 7
apply X 4 X i to the query obtained after transformation
in column 3 and perform the manipulations mentioned above.
For K > 7 , rearrange the query in column 3 such a way that
the first 2 K 2 1 codewords do not contain X t where
t = m a x ( { 4 , 5 , , K 1 } ) , t i . Perform manipulations on
these codewords by the steps proposed under the same
scenario, but by treating the message set as
{ X 1 , X 2 , , X K } \ { X t } . For the remaining 2 K 2 codewords
perform the following: Perform manipulations on all codewords
of the form X t + Q + X K , where
Q P ( { X 1 , X 2 , , X K 1 } \ { X t } ) \ { ϕ } similar to the steps
proposed under the same scenario of K 1 messages,
i.e., perform the same manipulations done to the codewords of
the form X t 1 + Q + X K 1 , where
Q P ( { X 1 , X 2 , , X K 2 } \ { X t 1 } ) \ { ϕ } when number of
messages was K 1 . Similarly, the manipulations performed
for the codewords of the form X t 1 + Q when number of
messages was K 1 should be repeated for all codewords of
the form X t + Q . If  K = 8 , perform the following (else skip):
X 1 + X m + X n + X o + U X m + X n + X o + U and
X 2 + X m + X n + X o + U X 1 + X 2 + X m + X n + X o + U ,
where U   P ( { X 3 , X i } ) , 4 m , n , o K 1 , m n o i .
6 X K as demandPick query at X p + X q + X 1 X q + X 3 + X 1
X p X q are SI N 2 obtained X 1 + X t + X 3 + X K X 1 + X t + X p + X K
4 p , q K 1 from case 5where X t is some byproduct
p q X 3 X i X p X q other than X 1 and X 3 .
Table 17. Instructions to obtain query at N 2 when X K one of the byproducts.
Table 17. Instructions to obtain query at N 2 when X K one of the byproducts.
No.CaseTransformationManipulations
9 X 1 as demand, X 2 X i NoneSwap the known and unknown
are SI, 3 i K 1 byproducts to obtain query at N 2 .
10 X 1 as demand, X p X q Pick query atNone
are SI, 3 p , q K 1 N 2 obtained
p q from case 5
X 3 X i X p X q
X 1 X K
11 X 2 as demand, X 1 X i NoneSwap the known and unknown
are SI, 3 i K 1 byproducts to obtain query at N 2 .
12 X 2 as demand, X p X q Pick query atNone
are SI, 3 p , q K 1 N 2 obtained
p q from case 5
X 3 X i X p X q
X 2 X K
13 X 3 as demandPick query atNone
X 1 X i are SI N 2 obtained
2 i K 1 , i 3 from Case 3
X 3 X K
14 X 3 as demandPick query atNone
X 2 X i are SI N 2 obtained
4 i K 1 , i 3 from Case 4
X 3 X K
15 X 3 as demandPick query at X i + X j X K + X j , X K + X 1 X K + X i , X K + X 2
X i X j are SI N 2 obtained X 3 + X 2 , X K + X 3 + X 2 X j + X 3 + X 2 ,
4 i , j K 1 , i j from Case 10 X 2 + X K + X j + X 3 X 1 + X 4 + X i + X 3 ,
X 2 X 3 X j + X 1 + X 4 + X 3 X j + X 1 + X 2 + X K
X j + X i + X 1 + X 2 + X 3 X 1 + X K + X 2 + X 4 + X j
X j + X K + X i + X 1 + X 2 + X 4
X 1 + X 2 + X K + X 3 + X i + X j
16 X δ as demand, X i X j NoneSwap the known and unknown
are SI, 4 δ K 1 byproducts to obtain query at N 2 .
1 i 2 , 2 j K 1 ,
i j , i , j δ
17 X δ as demand, X p X q Pick query atNone
are SI, 4 δ K 1 , N 2 obtained
3 p , q K 1 , p q from case 5
p , q δ X 3 X i X p X q
X δ X K
18 X δ as demand, X p X q Pick query at X 1 + X δ X 2 + X δ , X 2 + X δ + X p X 1 + X K + X δ ,
are SI, 4 δ K 1 , N 2 obtained X 1 + X K + X q X 1 + X q + X p
4 p , q K 1 , p q from case 5
p , q δ X 3 X i X p X q
X δ X K
Table 18. Query to N 1 and N 2 as per our code construction.
Table 18. Query to N 1 and N 2 as per our code construction.
Query to N 1 Query to N 2
A 1 A 33
A 2 + B 1 A 34 + B 1
A 3 + D 1 A 35 + D 2
A 4 + E 1 A 36 + E 2
A 5 + F 1 A 37 + F 2
B 2 + C 1 B 2 + C 1
B 3 + D 2 B 3 + D 1
B 4 + E 2 B 4 + E 1
B 5 + F 2 B 5 + F 1
B 6 + G 1 B 6 + G 6
C 2 + G 2 C 2 + G 13
D 3 + G 3 D 16 + G 14
E 3 + G 4 E 16 + G 15
F 3 + G 5 F 16 + G 16
A 6 + C 3 + D 4 A 38 + C 3 + D 7
A 7 + C 4 + E 4 A 39 + C 4 + E 7
A 8 + C 5 + F 4 A 40 + C 5 + F 7
A 9 + C 6 + G 6 A 41 + C 6 + G 1
A 10 + D 5 + E 5 A 42 + D 8 + E 8
A 11 + D 6 + F 5 A 43 + D 9 + F 8
A 12 + E 6 + F 6 A 44 + E 9 + F 9
B 7 + C 7 + D 7 B 7 + C 7 + D 4
B 8 + C 8 + E 7 B 8 + C 8 + E 4
B 9 + C 9 + F 7 B 9 + C 9 + F 4
B 10 + D 8 + E 8 B 10 + D 5 + E 5
B 11 + D 9 + F 8 B 11 + D 6 + F 5
B 12 + E 9 + F 9 B 12 + E 6 + F 6
C 10 + D 10 + E 10 C 10 + D 18 + E 18
C 11 + D 11 + F 10 C 11 + D 19 + F 18
C 12 + D 12 + G 7 C 12 + D 20 + G 17
C 13 + E 11 + F 11 C 13 + E 19 + F 19
C 14 + E 12 + G 8 C 14 + E 20 + G 18
C 15 + F 12 + G 9 C 15 + F 20 + G 19
D 13 + E 13 + F 13 D 21 + E 21 + F 21
D 14 + E 14 + G 10 D 22 + E 22 + G 20
D 15 + F 14 + G 11 D 23 + F 22 + G 21
E 15 + F 15 + G 12 E 23 + F 23 + G 22
A 13 + B 13 + C 16 + G 13 A 45 + B 13 + C 16 + G 2
A 14 + B 14 + D 16 + G 14 A 46 + B 14 + D 3 + G 3
A 15 + B 15 + E 16 + G 15 A 47 + B 15 + E 3 + G 4
A 16 + B 16 + F 16 + G 16 A 48 + B 16 + F 3 + G 5
C 17 + D 17 + E 17 + F 17 C 17 + D 30 + E 30 + F 30
A 17 + B 17 + C 18 + D 18 + E 18 A 49 + B 17 + C 18 + D 10 + E 10
A 18 + B 18 + C 19 + D 19 + F 18 A 50 + B 18 + C 19 + D 11 + F 10
A 19 + B 19 + C 20 + D 20 + G 17 A 51 + B 19 + C 20 + D 12 + G 7
A 20 + B 20 + C 21 + E 19 + F 19 A 52 + B 20 + C 21 + E 11 + F 11
A 21 + B 21 + C 22 + E 20 + G 18 A 53 + B 21 + C 22 + E 12 + G 8
A 22 + B 22 + C 23 + F 20 + G 19 A 54 + B 22 + C 23 + F 12 + G 9
A 23 + B 23 + D 21 + E 21 + F 21 A 55 + B 23 + D 13 + E 13 + F 13
A 24 + B 24 + D 22 + E 22 + G 20 A 56 + B 24 + D 14 + E 14 + G 10
A 25 + B 25 + D 23 + F 22 + G 21 A 57 + B 25 + D 15 + F 14 + G 11
A 26 + B 26 + E 23 + F 23 + G 22 A 58 + B 26 + E 15 + F 15 + G 12
A 28 + C 25 + D 25 + F 24 + G 24 A 60 + C 25 + D 28 + F 27 + G 28
A 29 + C 26 + E 25 + F 25 + G 25 A 61 + C 26 + E 28 + F 28 + G 29
A 30 + D 26 + E 26 + F 26 + G 26 A 62 + D 29 + E 29 + F 29 + G 30
B 27 + C 27 + D 27 + E 27 + G 27 B 27 + C 27 + D 24 + E 24 + G 23
B 28 + C 28 + D 28 + F 27 + G 28 B 28 + C 28 + D 25 + F 24 + G 24
B 29 + C 29 + E 28 + F 28 + G 29 B 29 + C 29 + E 25 + F 25 + G 25
B 30 + D 26 + E 26 + F 26 + G 26 B 30 + D 29 + E 29 + F 29 + G 30
A 31 + B 31 + C 30 + D 30 + E 30 + F 30 A 63 + B 31 + C 30 + D 17 + E 17 + F 17
A 32 + C 31 + D 31 + E 31 + F 31 + G 31 A 64 + C 31 + D 32 + E 32 + F 32 + G 32
B 32 + C 32 + D 32 + E 32 + F 32 + G 32 B 32 + C 32 + D 31 + E 31 + F 31 + G 31
Table 19. Pattern of unknown-known byproducts for SI A C .
Table 19. Pattern of unknown-known byproducts for SI A C .
UnknownKnown
BB
BB
DD
DD
EE
EE
FF
FF
B+DB+D
B+DB+D
B+EB+E
B+EB+E
B+FB+F
B+FB+F
D+ED+E
D+ED+E
D+FD+F
D+FD+F
E+FE+F
E+FE+F
B+D+EB+D+E
B+D+EB+D+E
B+D+FB+D+F
B+D+FB+D+F
B+E+FB+E+F
B+E+FB+E+F
D+E+FD+E+F
D+E+FD+E+F
B+D+E+FB+D+E+F
B+D+E+FB+D+E+F
Table 20. Pattern of unknown-known byproducts for SI A B and after BC.
Table 20. Pattern of unknown-known byproducts for SI A B and after BC.
UnknownKnownUnknown FOR BCKnown FOR BC
C
C CC
CCCC
DDDD
DDDD
EEEE
EEEE
FFFF
FFFF
C+DC+DC+DC+D
C+DC+DC+DC+D
C+EC+EC+EC+E
C+EC+EC+EC+E
C+FC+FC+FC+F
C+FC+FC+FC+F
D+ED+ED+ED+E
D+ED+ED+ED+E
D+FD+FD+FD+F
D+FD+FD+FD+F
E+FE+FE+FE+F
E+FE+FE+FE+F
C+D+EC+D+EC+D+EC+D+E
C+D+EC+D+EC+D+EC+D+E
C+D+FC+D+FC+D+FC+D+F
C+D+FC+D+FC+D+FC+D+F
C+E+FC+E+FC+E+FC+E+F
C+E+FC+E+FC+E+FC+E+F
D+E+FD+E+FD+E+FD+E+F
D+E+FD+E+FD+E+FD+E+F
C+D+E+FC+D+E+FC+D+E+FC+D+E+F
C+D+E+FC+D+E+FC+D+E+FC+D+E+F
Table 21. Final query to N 2 given in the fourth column.
Table 21. Final query to N 2 given in the fourth column.
Bit Number N 1 BC N 2
1AAC
2A+BA+CA+C
3A+DA+DA+D
4A+EA+EA+E
5A+FA+FA+F
6B+CC+BC+B
7B+DC+DC+D
8B+EC+EC+E
9B+FC+FC+F
10B+GC+GA+G
11C+GB+GB+G
12D+GD+GD+G
13E+GE+GE+G
14F+GF+GF+G
15A+C+DA+B+DA+B+D
16A+C+EA+B+EA+B+E
17A+C+FA+B+FA+B+F
18A+C+GA+B+GA+B+G
19A+D+EA+D+EA+D+E
20A+D+FA+D+FA+D+F
21A+E+FA+E+FA+E+F
22B+C+DC+B+DC+B+D
23B+C+EC+B+EC+B+E
24B+C+FC+B+FC+B+F
25B+D+EC+D+EC+D+E
26B+D+FC+D+FC+D+F
27B+E+FC+E+FC+E+F
28C+D+EB+D+EB+D+E
29C+D+FB+D+FB+D+F
30C+D+GB+D+GB+D+G
31C+E+FB+E+FB+E+F
32C+E+GB+E+GB+E+G
33C+F+GB+F+GB+F+G
34D+E+FD+E+FD+E+F
35D+E+GD+E+GD+E+G
36D+F+GD+F+GD+F+G
37E+F+GE+F+GE+F+G
38A+B+C+GA+C+B+GA+C+B+G
39A+B+D+GA+C+D+GA+C+D+G
40A+B+E+GA+C+E+GA+C+E+G
41A+B+F+GA+C+F+GA+C+F+G
42C+D+E+FB+D+E+FB+D+E+F
43A+B+C+D+EA+C+B+D+EA+C+B+D+E
44A+B+C+D+FA+C+B+D+FA+C+B+D+F
45A+B+C+D+GA+C+B+D+GA+C+B+D+G
46A+B+C+E+FA+C+B+E+FA+C+B+E+F
47A+B+C+E+GA+C+B+E+GA+C+B+E+G
48A+B+C+F+GA+C+B+F+GA+C+B+F+G
49A+B+D+E+FA+C+D+E+FA+C+D+E+F
50A+B+D+E+GA+C+D+E+GA+C+D+E+G
52A+B+E+F+GA+C+E+F+GA+C+E+F+G
53A+C+D+E+GA+B+D+E+GA+B+D+E+G
54A+C+D+F+GA+B+D+F+GA+B+D+F+G
55A+C+E+F+GA+B+E+F+GA+B+E+F+G
56A+D+E+F+GA+D+E+F+GA+D+E+F+G
57B+C+D+E+GC+B+D+E+GC+B+D+E+G
58B+C+D+F+GC+B+D+F+GC+B+D+F+G
59B+C+E+F+GC+B+E+F+GC+B+E+F+G
60B+D+E+F+GC+D+E+F+GC+D+E+F+G
61A+B+C+D+E+FA+C+B+D+E+FA+C+B+D+E+F
62A+C+D+E+F+GA+B+D+E+F+GA+B+D+E+F+G
63B+C+D+E+F+GC+B+D+E+F+GC+B+D+E+F+G
Table 22. Pattern of unknown and known byproducts for SI B D and after AB and CD.
Table 22. Pattern of unknown and known byproducts for SI B D and after AB and CD.
UnknownKnownUnknown FOR AB
C D
Known FOR AB
C D
A
AAA
AAAA
CCCC
CCCC
EEEE
EEEE
FFFF
FFFF
A+CA+C
A+C A+CA+C
A+C A+CA+C
A+EA+EA+EA+E
A+EA+EA+EA+E
A+FA+FA+FA+F
A+FA+FA+FA+F
C+EC+EC+EC+E
C+EC+EC+EC+E
C+FC+FC+FC+F
C+FC+FC+FC+F
E+FE+FE+FE+F
E+FE+FE+FE+F
A+C+EA+C+EA+C+EA+C+E
A+C+EA+C+EA+C+EA+C+E
A+C+FA+C+FA+C+FA+C+F
A+C+FA+C+FA+C+FA+C+F
A+E+FA+E+FA+E+FA+E+F
A+E+FA+E+FA+E+FA+E+F
C+E+FC+E+FC+E+FC+E+F
C+E+FC+E+FC+E+FC+E+F
A+C+E+FA+C+E+FA+C+E+FA+C+E+F
A+C+E+FA+C+E+FA+C+E+FA+C+E+F
Table 23. Final query to N 2 given in the fourth column.
Table 23. Final query to N 2 given in the fourth column.
Bit Number N 1 AB, CD N 2
1ABG
2A+BB+AB+A
3A+DB+CB+C
4A+EB+EB+E
5A+FB+FB+F
6B+CA+DA+D
7B+DA+CA+C
8B+EA+EA+E
9B+FA+FA+F
10B+GA+GA+G
11C+GD+GD+G
12D+GC+GB+G
14F+GF+GF+G
15A+C+DB+D+CB+D+C
16A+C+EB+D+EB+D+E
17A+C+FB+D+FB+D+F
18A+C+GB+D+GB+D+G
19A+D+EB+C+EB+C+E
20A+D+FB+C+FB+C+F
21A+E+FB+E+FB+E+F
22B+C+DA+D+CA+D+C
23B+C+EA+D+EA+D+E
24B+C+FA+D+FA+D+F
25B+D+EA+C+EA+C+E
26B+D+FA+C+FA+C+F
27B+E+FA+E+FA+E+F
28C+D+ED+C+ED+C+E
29C+D+FD+C+FD+C+F
30C+D+GD+C+GD+C+G
31C+E+FD+E+FD+E+F
32C+E+GD+E+GD+E+G
33C+F+GD+F+GD+F+G
34D+E+FC+E+FC+E+F
35D+E+GC+E+GC+E+G
36D+F+GC+F+GC+F+G
37E+F+GE+F+GE+F+G
38A+B+C+GB+A+D+GB+A+D+C
39A+B+D+GB+A+C+GB+A+C+G
40A+B+E+GB+A+E+GB+A+E+G
41A+B+F+GB+A+F+GB+A+F+G
42C+D+E+FD+C+E+FD+C+E+F
43A+B+C+D+EB+A+D+C+EB+A+D+C+E
44A+B+C+D+FB+A+D+C+FB+A+D+C+F
45A+B+C+D+GB+A+D+C+GB+A+D+C+G
46A+B+C+E+FB+A+D+E+FB+A+D+E+F
47A+B+C+E+GB+A+D+E+GB+A+D+E+G
48A+B+C+F+GB+A+D+F+GB+A+D+F+G
49A+B+D+E+FB+A+C+E+FB+A+C+E+F
50A+B+D+E+GB+A+C+E+GB+A+C+E+G
51A+B+D+F+GB+A+C+F+GB+A+C+F+G
52A+B+E+F+GB+A+E+F+GB+A+E+F+G
53A+C+D+E+GB+D+C+E+GB+D+C+E+G
54A+C+D+F+GB+D+C+F+GB+D+C+F+G
55A+C+E+F+GB+D+E+F+GB+D+E+F+G
56A+D+E+F+GB+C+E+F+GB+C+E+F+G
57B+C+D+E+GA+D+C+E+GA+D+C+E+G
58B+C+D+F+GA+D+C+F+GA+D+C+F+G
59B+C+E+F+GA+D+E+F+GA+D+E+F+G
60B+D+E+F+GA+C+E+F+GA+C+E+F+G
61A+B+C+D+E+FB+A+D+C+E+FB+A+D+C+E+F
62A+C+D+E+F+GB+D+C+E+F+GB+D+C+E+F+G
63B+C+D+E+F+GA+D+C+E+F+GA+D+C+E+F+G
Table 24. Pattern of unknown and known byproducts for SI C D .
Table 24. Pattern of unknown and known byproducts for SI C D .
UnknownKnown
AA
BA
EA
EB
EB
FB
FE
FF
A+BA+B
A+BA+E
A+BA+E
A+EA+E
A+FA+F
B+EA+F
B+FA+F
E+FB+E
A+B+EB+E
A+B+EB+E
A+B+EB+F
A+B+FB+F
A+B+FB+F
A+B+FE+F
A+E+FE+F
A+E+FE+F
A+E+FA+B+E
B+E+FA+B+F
B+E+FA+E+F
B+E+FB+E+F
A+B+E+FA+B+E+F
A+B+E+F
A+B+E+F
Table 25. Final query to N 2 given in the fourth column.
Table 25. Final query to N 2 given in the fourth column.
Bit Number N 1 AD N 2
1ADG
2A+BD+BD+C
3A+DD+AD+A
4A+ED+ED+E
5A+FD+FD+F
6B+CB+CE+C
7B+DB+AB+A
8B+EB+EB+E
9B+FB+FE+F
10B+GB+GD+G
11C+GC+GC+G
12D+GA+GA+G
13E+GE+GE+A
14F+GF+GF+C
15A+C+DD+C+AD+C+A
16A+C+ED+C+ED+C+E
17A+C+FD+C+FD+C+F
18A+C+GD+C+GD+C+G
19A+D+ED+A+ED+A+B
20A+D+FD+A+FD+A+F
21A+E+FD+E+FD+G+F
22B+C+DB+C+AB+C+A
23B+C+EB+C+EB+C+E
24B+C+FB+C+FB+C+F
25B+D+EB+A+EB+A+E
26B+D+FB+D+FB+D+F
27B+E+FB+E+FB+E+F
28C+D+EC+A+EB+G+E
29C+D+FC+A+FB+D+G
30C+D+GC+A+GC+B+G
31C+E+FC+E+FC+B+D
32C+E+GC+E+GC+E+G
33C+F+GC+F+GB+F+G
34D+E+FA+E+FA+E+F
35D+E+GA+E+GA+E+G
36D+F+GA+F+GA+F+G
37E+F+GE+F+GE+F+G
38A+B+C+GD+B+C+GA+E+C+G
39A+B+D+GD+B+A+GA+B+F+D
40A+B+E+GD+B+E+GD+B+E+F
41A+B+F+GD+B+F+GD+A+F+G
42C+D+E+FC+A+E+FC+A+E+F
43A+B+C+D+ED+B+C+A+ED+B+C+A+E
44A+B+C+D+FD+B+C+A+FD+B+C+A+F
45A+B+C+D+GD+B+C+A+GD+B+C+A+G
46A+B+C+E+FD+B+C+E+FD+B+C+E+F
47A+B+C+E+GD+B+C+E+GD+B+C+E+G
48A+B+C+F+GD+B+C+F+GD+B+C+F+G
49A+B+D+E+FD+B+A+E+FD+C+A+E+F
51A+B+D+F+GD+B+A+F+GD+B+A+F+G
52A+B+E+F+GD+B+E+F+GD+B+E+F+G
53A+C+D+E+GD+C+A+E+GD+C+A+E+G
54A+C+D+F+GD+C+A+F+GD+C+A+F+G
55A+C+E+F+GD+C+E+F+GD+C+E+F+G
56A+D+E+F+GD+A+E+F+GC+A+E+F+G
57B+C+D+E+GB+C+A+E+GB+C+A+E+G
58B+C+D+F+GB+C+A+F+GB+C+A+F+G
59B+C+E+F+GB+C+E+F+GB+C+E+F+G
60B+D+E+F+GB+A+E+F+GB+A+E+F+G
61A+B+C+D+E+FD+B+C+A+E+FD+B+C+A+E+F
62A+C+D+E+F+GD+C+A+E+F+GD+B+A+E+F+G
63B+C+D+E+F+GB+C+A+E+F+GB+C+A+E+F+G
Table 26. Pattern of unknown and known byproducts for SI E F .
Table 26. Pattern of unknown and known byproducts for SI E F .
UnknownKnown
AA
AA
BA
BA
BB
DB
DB
DG
GG
GG
GD
A+GA+B
A+GB+G
B+GD+G
A+BD+G
D+GD+G
A+DA+D
B+DA+D
A+B+GA+D
A+B+GB+D
A+B+GB+D
A+D+GB+D
A+D+GA+B+G
A+D+GA+B+G
B+D+GA+B+G
B+D+GA+D+G
B+D+GB+D+G
A+B+DA+B+D
A+B+DA+B+D+G
A+B+DA+B+D+G
A+B+D+GA+B+D+G
Table 27. Final query to N 2 given in the fourth column.
Table 27. Final query to N 2 given in the fourth column.
Bit Number N 1 BC N 2
1ACC
2A+BF+EF+G
3A+DF+AF+A
4A+EF+BF+B
5A+FF+DF+D
6B+CB+EB+E
7B+DG+AG+E
8B+EG+BC+B
9B+FB+DB+D
10B+GF+CF+C
11C+GE+CE+C
12D+GA+CA+C
13E+GE+AE+A
14F+GD+ED+E
15A+C+DE+B+AE+B+A
16A+C+EF+E+BF+E+B
17A+C+FF+E+DF+E+D
18A+C+GF+E+CF+E+C
19A+D+EF+A+GF+A+G
20A+D+FF+A+DF+A+D
21A+E+FF+C+DF+C+D
22B+C+DG+E+AG+E+A
23B+C+EG+E+BG+E+B
24B+C+FG+E+DG+E+D
25B+D+EG+A+BG+A+B
26B+D+FG+F+DG+F+D
27B+E+FG+B+DG+B+D
28C+D+EG+C+BF+C+B
29C+D+FG+F+CG+F+C
30C+D+GE+G+CE+G+C
31C+E+FE+G+FE+G+F
32C+E+GE+B+CE+B+C
33C+F+GG+D+CG+D+C
34D+E+FA+B+DA+B+D
35D+E+GA+B+CA+B+C
37E+F+GB+D+CB+D+C
38A+B+C+GB+G+F+CA+D+E+C
39A+B+D+GA+G+D+FA+G+D+F
40A+B+E+GF+G+B+DF+G+B+D
41A+B+F+GF+A+D+CF+A+B+G
42C+D+E+FE+A+B+DE+A+B+D
43A+B+C+D+EF+G+E+A+BF+G+E+A+B
44A+B+C+D+FF+G+E+A+DF+G+E+A+D
45A+B+C+D+GF+G+E+A+CF+G+E+A+C
46A+B+C+E+FF+G+E+B+DF+G+E+B+D
47A+B+C+E+GF+G+E+B+CF+G+E+B+C
48A+B+C+F+GF+G+E+D+CF+G+E+D+C
49A+B+D+E+FF+E+A+B+DF+E+A+B+D
50A+B+D+E+GF+G+A+B+CF+G+A+B+C
51A+B+D+F+GF+G+A+D+CF+G+A+D+C
52A+B+E+F+GF+G+B+D+CF+G+B+D+C
53A+C+D+E+GF+E+A+B+CA+G+B+D+F
54A+C+D+F+GF+E+A+D+CF+E+A+D+C
55A+C+E+F+GF+E+B+D+CF+E+B+D+C
56A+D+E+F+GE+A+B+D+CE+A+B+D+C
57B+C+D+E+GG+E+A+B+CG+E+A+B+C
58B+C+D+F+GG+E+A+D+CG+E+A+D+C
59B+C+E+F+GG+E+B+D+CG+E+B+D+C
60B+D+E+F+GG+A+B+D+CG+A+B+D+C
61A+B+C+D+E+FF+G+E+A+B+DA+B+G+C+E+F
62A+C+D+E+F+GF+G+A+B+D+CF+G+A+B+D+C
63B+C+D+E+F+GG+E+A+B+D+CG+E+A+B+D+C
Publisher’s Note: MDPI stays neutral with regard to jurisdictional claims in published maps and institutional affiliations.

Share and Cite

MDPI and ACS Style

Krishnan K. H., M.; Harshan, J. On the Existence of XOR-Based Codes for Private Information Retrieval with Private Side Information. Entropy 2021, 23, 1287. https://doi.org/10.3390/e23101287

AMA Style

Krishnan K. H. M, Harshan J. On the Existence of XOR-Based Codes for Private Information Retrieval with Private Side Information. Entropy. 2021; 23(10):1287. https://doi.org/10.3390/e23101287

Chicago/Turabian Style

Krishnan K. H., Murali, and Jagadeesh Harshan. 2021. "On the Existence of XOR-Based Codes for Private Information Retrieval with Private Side Information" Entropy 23, no. 10: 1287. https://doi.org/10.3390/e23101287

APA Style

Krishnan K. H., M., & Harshan, J. (2021). On the Existence of XOR-Based Codes for Private Information Retrieval with Private Side Information. Entropy, 23(10), 1287. https://doi.org/10.3390/e23101287

Note that from the first issue of 2016, this journal uses article numbers instead of page numbers. See further details here.

Article Metrics

Back to TopTop