Private inference in deep neural network

12346830 ยท 2025-07-01

Assignee

Inventors

Cpc classification

International classification

Abstract

A secure inference over Deep Neural Networks (DNNs) using secure two-party computation to perform privacy-preserving machine learning. The secure inference uses a particular type of comparison that can be used as a building block for various layers in the DNN including, for example, ReLU activations and divisions. The comparison securely computes a Boolean share of a bit representing whether input value x is less than input value y, where x is held by a user of the DNN, and where y is held by a provider of the DNN. Each party computing system parses their input into leaf strings of multiple bits. This is much more efficient than if the leaf strings were individual bits. Accordingly, the secure inference described herein is more readily adapted for using in complex DNNs.

Claims

1. A method for performing secure inference over a Deep Neural Network (DNN) using secure two-party computation, which involves a first party and a second party, to perform privacy-preserving machine learning such that a provider of the DNN does not learn anything about inputs to the DNN or about weights of the DNN beyond that which can be inferred from an output of the DNN and the inputs to the DNN, wherein said method is further performed in a manner to reduce communications between the first party and the second party via use of an oblivious transfer technique, the method comprising: performing a comparison that securely computes a Boolean share of a bit representing whether input value x is less than input value y, where x is held by a user of the DNN, and where y is held by the provider of the DNN, the comparison performed by: parsing x into q leaf strings x.sub.q-1 . . . x.sub.0, where each of the q leaf strings is more than one bit, and where x is equal to the concatenation x.sub.q-1 . . . x.sub.0; compute shares of inequality 1{x.sub.n<y.sub.n} for each of at least some n from q1 down to 1, where y is equal to the concatenation y.sub.q-1 . . . y.sub.0, by in each case using oblivious transfer; compute shares of equality 1{x.sub.n=y.sub.n} for each of at least some n from q1 down to 1 also in each case by using oblivious transfer; and recursively calculating shares of inequality of internal nodes according to the following equation: 1{x.sub.C<y.sub.C}=1{x.sub.B<y.sub.B}1{x.sub.B=y.sub.B}{x.sub.A<y.sub.A} (where x.sub.C=x.sub.Bx.sub.A, and y.sub.C=y.sub.By.sub.A), and shares of equality of internal nodes until the Boolean share of 1{x<y} is determined; and repeatedly performing the comparison for different inputs to traverse a garbled binary circuit that represents the DNN to thereby obtain a result of the garbled binary circuit.

2. The method in accordance with claim 1, wherein inputs x and y are each of size custom character bits, and each leaf string is of size m bits, where m divides custom character.

3. The method in accordance with claim 1, wherein inputs x and y are each of size custom character bits, and each leaf string has a maximum size of m bits, where m does not divide custom character.

4. The method in accordance with claim 1, the parsing comprising parsing so that at least one of the leaf strings of each of the inputs has less than m bits.

5. The method in accordance with claim 2, wherein custom character/m is not a power of 2.

6. The method in accordance with claim 5, the recursively calculating shares comprising first constructing a binary tree with a power of two leaves.

7. The method in accordance with claim 1, the computing shares of inequality 1{x.sub.n<y.sub.n} occurring for each of all n from q1 down to 1, and the computing shares of equality 1{x.sub.n=y.sub.n} occurring for each of all n from q1 down to 1.

8. The method in accordance with claim 1, wherein for at least one of the comparisons, the comparison is performed as part of a ReLU activation on a value acustom character.sub.L using arithmetic shares of a.

9. The method in accordance with claim 8, where shares of the ReLU activation are obtained by: performing the comparison on the input shares by performing the comparison on all but the most significant bit of a.

10. The method in accordance with claim 1, wherein for at least one of the comparisons, the comparison is performed as part of a division operation.

11. A method for performing secure inference over a Deep Neural Network (DNN) using secure two-party computation, which involves a first party and a second party, to perform privacy-preserving machine learning such that a provider of the DNN does not learn anything about inputs to the DNN or about weights of the DNN beyond that which can be inferred from an output of the DNN and the inputs to the DNN, wherein said method is further performed in a manner to reduce communications between the first party and the second party via use of an oblivious transfer technique, the method comprising: performing a comparison that securely computes a Boolean share of a bit representing whether input value x is less than input value y, where x is held by a user of the DNN, and where y is held by the provider of the DNN, the comparison performed by: parsing y into q leaf strings y.sub.q-1 . . . y.sub.0, where each of the q leaf strings is more than one bit, and where y is equal to the concatenation y.sub.q-1 . . . y.sub.0; compute shares of inequality 1{x.sub.n<y.sub.n} for each of at least some n from q1 down to 1, where x is equal to the concatenation x.sub.q-1 . . . x.sub.0, by in each case using oblivious transfer; compute shares of equality 1{x.sub.n=y.sub.n} for each of at least some n from q1 down to 1 also in each case by using oblivious transfer; and recursively calculating shares of inequality of internal nodes according to the following equation: 1{x.sub.C<y.sub.C}=1{x.sub.B<y.sub.B}1{x.sub.B=y.sub.B}1{x.sub.A<y.sub.A} (where x.sub.C=x.sub.Bx.sub.A, and y.sub.C=y.sub.By.sub.A), and shares of equality of internal nodes until the Boolean share of 1{x<y} is determined; and repeatedly performing the comparison for different inputs to traverse a garbled binary circuit that represents the DNN to thereby obtain a result of the garbled binary circuit.

12. The method in accordance with claim 11, wherein inputs x and y are each of size custom character bits, and each of multiple leaf string is of size m bits, the computation of shares of inequality 1{x.sub.n<y.sub.n} for each of at least one of the multiple leaf strings of size m bits is performed using ( M 1 ) - O T 1 oblivious transfer.

13. The method in accordance with claim 12, wherein multiple performances of the ( M 1 ) - O T 1 oblivious transfer are performed using a single call.

14. The method in accordance with claim 11, wherein inputs x and y are each of size custom character bits, and each of multiple leaf string is of size m bits, the computation of shares of equality 1{x.sub.n=y.sub.n} for each of at least one of the multiple leaf strings of size m bits is performed using ( M 1 ) - O T 1 oblivious transfer.

15. The method in accordance with claim 14, wherein multiple performances of the ( M 1 ) - O T 1 oblivious transfer are performed using a single call.

16. A computing system for performing secure inference over a Deep Neural Network (DNN) using secure two-party computation, which involves a first party and a second party, to perform privacy-preserving machine learning such that a provider of the DNN does not learn anything about inputs to the DNN or about weights of the DNN beyond that which can be inferred from an output of the DNN and the inputs to the DNN, wherein said method is further performed in a manner to reduce communications between the first party and the second party via use of an oblivious transfer technique, the computing system comprising: one or more processing units; and computer-readable storage media having thereon instructions that are executable by the one or more processing units to cause the computing system to perform a comparison that securely computes a Boolean share of a bit representing whether input value x is less than input value y, where x is held by a user of the DNN, and where y is held by the provider of the DNN, the comparison performed by: parsing y into q leaf strings y.sub.q-1 . . . y.sub.0, where each of the q leaf strings is more than one bit, and where y is equal to the concatenation y.sub.q-1 . . . y.sub.0; compute shares of inequality 1{x.sub.n<y.sub.n} for each of at least some n from q1 down to 1, where x is equal to the concatenation x.sub.q-1 . . . x.sub.0, by in each case using oblivious transfer; compute shares of equality 1{x.sub.n=y.sub.n} for each of at least some n from q1 down to 1 also in each case by using oblivious transfer; and recursively calculating shares of inequality of internal nodes according to the following equation: 1{x.sub.C<y.sub.C}=1{x.sub.B<y.sub.B}1{x.sub.B=y.sub.B}1{x.sub.A<y.sub.A} (where x.sub.C=x.sub.Bx.sub.A, and y.sub.C=y.sub.By.sub.A), and shares of equality of internal nodes until the Boolean share of 1{x<y} is determined; and repeatedly performing the comparison for different inputs to traverse a garbled binary circuit that represents the DNN to thereby obtain a result of the garbled binary circuit.

17. The computing system in accordance with claim 16, wherein inputs x and y are each of size & bits, and each of multiple leaf string is of size m bits, the computation of shares of inequality 1{x.sub.n<y.sub.n} for each of at least one of the multiple leaf strings of size m bits is performed using ( M 1 ) - O T 1 oblivious transfer.

18. The computing system in accordance with claim 17, wherein multiple performances of the ( M 1 ) - O T 1 oblivious transfer are performed using a single call.

19. The computing system in accordance with claim 16, wherein inputs x and y are each of size custom character bits, and each of multiple leaf string is of size m bits, the computation of shares of equality 1{x.sub.n=y.sub.n} for each of at least one of the multiple leaf strings of size m bits is performed using ( M 1 ) - O T 1 oblivious transfer.

20. The computing system in accordance with claim 19, wherein multiple performances of the ( M 1 ) - O T 1 oblivious transfer are performed using a single call.

Description

BRIEF DESCRIPTION OF THE DRAWINGS

(1) In order to describe the manner in which the above-recited and other advantages and features can be obtained, a more particular description of the subject matter briefly described above will be rendered by reference to specific embodiments which are illustrated in the appended drawings. Understanding that these drawings depict only typical embodiments and are not therefore to be considered to be limiting in scope, embodiments will be described and explained with additional specificity and details through the use of the accompanying drawings in which:

(2) FIG. 1 illustrates an environment in which the principles described herein in which a first party computing system and a second party computing system perform secure two-party computation over a Deep Neural Network (DNN);

(3) FIG. 2A illustrates a process performed by the first party computing system to compute its share of 1{x.sub.B<y.sub.B};

(4) FIG. 2B illustrates a process performed by the second party computing system to compute its share of 1{x.sub.B<y.sub.B};

(5) FIG. 3 shows the improvement of our ReLU the protocols described herein over garbles circuits in both LAN and WAN settings; and

(6) FIG. 4 illustrates an example computing system that may represent an example of the first party computing system and the second party computing system of FIG. 1.

DETAILED DESCRIPTION

1. Introduction

(7) Embodiments disclosed herein relate to secure inference over Deep Neural Networks (DNNs) using secure two-party computation to perform privacy-preserving machine learning. This privacy means that the provider of the deep neural network does not learn anything about inputs to the deep neural network, and the provider of inputs to the deep neural network does not learn anything about weights of the deep neural network beyond that which can be inferred from the output of the deep neural network and the inputs to the deep neural network.

(8) The secure inference uses a particular type of comparison that can be used as a building block for various layers in the DNN including, for example, ReLU activations and divisions. The comparison securely computes a Boolean share of a bit representing whether input value x is less than input value y, where x is held by a user of the DNN, and where y is held by a provider of the DNN.

(9) A computing system of one party to the comparison parses x into q leaf strings x.sub.q-1 . . . x.sub.0, where each of the q leaf strings is more than one bit, and where x is equal to the concatenation x.sub.q-1 . . . x.sub.0. Meanwhile the computing system of the second party parses y into q leaf strings y.sub.q-1 . . . y.sub.0, where each of the q leaf strings is more than one bit, and where x is equal to the concatenation y.sub.q-1 . . . y.sub.0. Note that each leaf string constitutes multiple bits. This is much more efficient than if the leaf strings were individual bits. Accordingly, the secure inference described herein is more readily adapted for using in complex DNNs.

(10) Each party computing system then computes shares of inequality 1{x.sub.n<y.sub.n} for each of at least some n from q1 down to 1, where y is equal to the concatenation y.sub.q-1 . . . y.sub.0, by in each case using oblivious transfer. In addition, the systems computes their respective shares of equality 1{x.sub.n=y.sub.n} for each of at least some n from q1 down to 1 also in each case by using oblivious transfer. The systems recursively calculates their respective shares of inequality of internal nodes according to the following equation: 1{x.sub.C<y.sub.C}=1{x.sub.B<y.sub.B}(1{x.sub.B=y.sub.B}1{x.sub.A<y.sub.A} (where x.sub.C=x.sub.Bx.sub.A, and y.sub.C=y.sub.By.sub.A), and their respective shares of equality of internal nodes until their respective Boolean share of 1{x<y} is determined.

(11) This comparison can be performed at many layers in the DNN to thereby traverse the garbled binary circuit that represents the DNN. Furthermore, each party computing system has access to only their respective share of the information at each internal node in the garbled circuit. Accordingly, the computing systems mutually perform the DNN layers in a manner that their respective data input into the process (e.g., the training data or the evaluation data for the first party computing system, and the weights for the second party computing system) are kept from being disclosed to the opposite party. Thus, privacy is preserved.

(12) A solution for secure inference such as the one described herein that scales to practical machine learning (ML) tasks would open a plethora of applications based on MLaaS (ML as a Service). Users can obtain value from ML services without worrying about the loss of their private data, while model owners can effectively offer their services with no fear of breaches of client data (they never observe private client data in the clear).

(13) Secure inference is an instance of secure 2-party computation (2PC) and cryptographically secure general protocols for 2PC have been known for decades [31, 62]. However, secure inference for practical ML tasks, e.g., ImageNet scale prediction [25], is challenging for two reasons: a) realistic DNNs use ReLU activations (ReLU(x) is defined as max(x, 0)) that are expensive to compute securely; and b) preserving inference accuracy requires a faithful implementation of secure fixed-point arithmetic. Conventional implementations [6, 30, 42, 47, 48, 50] of ReLUs can include replacing the activation with approximations that are more tractable for 2PC [23, 30, 48], which his approach results in significant accuracy losses that can degrade user experience. The only approaches known to the inventors to evaluate ReLUs efficiently require sacrificing security by making the untenable assumption that a non-colluding third party takes part in the protocol [7, 44, 49, 55, 60] or by leaking activations [13]. Moreover, some prior works [44, 48-50, 60] even sacrifice correctness of their fixed point implementations and the result of their secure execution can sometimes diverge from the expected result, i.e. cleartext execution, in random and unpredictable ways. Thus, correct and efficient 2PC protocols for secure inference over realistic DNNs remain elusive.

(14) 1.1 Our Contribution

(15) In this work, we address the above two challenges and build new semi-honest secure 2-party cryptographic protocols for secure computation of DNN inference. Our new efficient protocols enable the first secure implementations of ImageNet scale inference that complete in under a minute! We make three main contributions:

(16) First, we give a new comparison protocol that enables us to securely and efficiently evaluate the non-linear layers of DNNs such as ReLU, Maxpool and Argmax.

(17) Second, we provide new protocols for division. Together with new theorems that we prove on fixed-point arithmetic overshares, we show how to evaluate linear layers, such as convolutions, average pool and fully connected layers, faithfully.

(18) Finally, by providing protocols that can work on a variety of input domains, we build a system PIE that supports two different types of secure inference protocols where linear layers can be evaluated using either homomorphic encryption (PIE.sub.HE) or through oblivious transfer (PIE.sub.OT).

(19) We now provide more details of our main contributions.

(20) New millionaires' protocol. Our first main technical contribution is a novel protocol for the well-known millionaires' problem [62], where parties P.sub.0 and P.sub.1 hold custom character-bit integers x and y, respectively, and want to securely compute x<y (or, secret shares of x<y). The theoretical communication complexity of our protocol is 3 better than the most communication efficient prior millionaire's protocol [22, 28, 31, 61, 62]. In terms of round complexity, our protocol executes in log custom character rounds (e.g. 5 rounds for custom character=32 bits); this is much better than prior works except for those based on Yao's garbled circuits that require optimal 2 rounds, but have prohibitively high communication complexity (see Table 1 for a detailed comparison).

(21) TABLE-US-00001 TABLE 1 Comparison of communication with prior work for millionaire's problem. For our protocol, m is a parameter. For concrete bits of communication we use = 128. Layer Protocol Comm. (bits) Rounds Millionaire's GC [61, 62] 4custom character 2 on {0, 1}custom character GMW.sup.3/GSV [28, 31] 6custom character logcustom character + 3 SC3.sup.4[22] >3custom character 4 log* This work (m = 4) <custom character + 14custom character logcustom character Millionaire's GC [61, 62] 16384 2 example GMW/GSV [28, 31] 23140 8 custom character = 32 SC3 [22] 13016 15 This work (m = 7) 2930 5 This work (m = 4) 3844 5

(22) Under GMW.sup.3, we state the communication numbers for GWM [31] for a depth-optimized circuit. The circuit that would give the best communication would still have a complexity of >2custom character and would additionally pay an inordinate cost in terms of rounds, namely custom character. Further, under SC3.sup.4, Couteau [22] presented multiple protocols; we compare against the one that has the best communication complexity.

(23) Using our protocol for millionaire's problem, we build new and efficient protocols for computing non-linear activations such as ReLU and Maxpool for both custom character-bit integers (i.e., Z.sub.L, L=custom character) and general rings Z.sub.n. Providing support for custom character-bit integers Z.sub.L, as well as arbitrary rings Z.sub.n, allow us to securely evaluate the linear layers (such as matrix multiplication and convolutions) using the approaches of Oblivious Transfer (OT) [8, 50] as well as Homomorphic Encryption (HE) [29, 42, 48], respectively. This provides our protocols great flexibility when executing over different network configurations. Since all prior work [42, 47, 48, 50] known to the inventors for securely computing these activations rely on Yao's garbled circuits [62], our protocols are much more efficient in both settings. Asymptotically, our ReLU protocol over Z.sub.L, and Z.sub.n communicate 8 and 12 less bits than prior works [42, 47, 48, 50, 61, 62] (see Table 2 for a detailed comparison). Experimentally, our protocols are at least an order of magnitude more performant than prior protocols when computing ReLU activations at the scale of ML applications.

(24) TABLE-US-00002 TABLE 2 Comparision of communication with Garbled Circuits for ReLU. We define = log n. For concrete bits of communication we use = 128. Layer Protocol Comm. (bits) Rounds ReLU GC [61, 62] 8custom character 4 2 custom character This work <custom character + 18custom character logcustom character + 4 ReLU for GC [61, 62] 18 6 2 general custom character .sub.n This work < 3 2 ( + 1 ) + 31 log + 4 ReLU for GC [61, 62] 32256 2 custom character , custom character = 32 This work 3298 7 ReLU for GC [61, 62] 72960 2 custom character .sub.n, = 32 This work 5288 9

(25) Fixed-point arithmetic. The ML models used by all prior works known to the inventors on secure inference are expressed using fixed-point arithmetic; such models can be obtained from [38, 41, 44, 51]. A faithful implementation of fixed-point arithmetic is quintessential to ensure that the secure computation is correct, i.e., it is equivalent to the cleartext computation for all possible inputs. Given a secure inference task F (x,w), some prior works [44, 48-50, 60] give up on correctness when implementing division operations and instead compute an approximation F(x,w). In fixed-point arithmetic, each multiplication requires a division by a power-of-2 and multiplications are used pervasively in linear-layers of DNNs. Moreover, layers like average-pool require division for computing means. Loss in correctness is worrisome as the errors can accumulate and F(x,w) can be arbitrarily far from F (x,w). Recent work [48] has shown that even in practice the approximations can lead to significant losses in classification accuracy.

(26) As our next contribution, we provide novel protocols to compute division by power-of-2 as well as division by arbitrary integers that are both correct and efficient. The inputs to these protocols can be encoded over both custom character-bit integers Z.sub.L as well as Z.sub.n, for arbitrary n. The only known approach to compute division correctly is via garbled circuits which we compare with in Table 3. While garbled circuits based protocols require communication which is quadratic in custom character or log n, our protocols are asymptotically better and incur only linear communication. Concretely, for average pool with 77 filters and 32-bit integers, our protocols have 54 less communication.

(27) TABLE-US-00003 TABLE 3 Comparision of communication with Garbled Circuits for Avgpool.sub.d. We define = log n and = log(6 .Math. d). For concrete bits of communication we use = 128. Choice of d = 49 corresponds to average pool filter of size 7 7. Layer Protocol Comm. (bits) Rounds Avgpool.sub.d GC [61, 62] 2(custom character .sup.2 + 5custom character 3) 2 custom character This work <( + 21) .Math. (custom character + 3) log(custom character ) + 4 Avgpool.sub.d GC [61, 62] 2(.sup.2 + 9 3) 2 custom character .sub.n This work < 3 2 ( + 34 ) .Math. ( + 2 ) log() + 6 Avgpool.sub.49 GC [61, 62] 302336 2 custom character , custom character = 32 This work 5570 10 Avgpool.sub.49 GC [61, 62] 335104 2 custom character .sub.n, = 32 This work 7796 14

(28) Scaling to practical DNNs. These efficient protocols, help us securely evaluate practical DNNs like SqueezeNet on ImageNet scale classification tasks in under a minute. In sharp contrast, all prior works on secure 2-party inference ([4, 6, 14, 18, 20, 23, 30, 42, 47, 48, 50, 54, 56]) has been limited to small DNNs on tiny datasets like MNIST and CIFAR. While MNIST deals with the task of classifying black and white handwritten digits given as 2828 images into the classes 0 to 9, ImageNet tasks are much more complex: typically 224224 colored images need to be classified into thousand classes (e.g., agaric, gyromitra, ptarmigan, etc.) that even humans can find challenging. Additionally, our work is the first to securely evaluate practical convolutional neural networks (CNNs) like ResNet50 and DenseNet121; these DNNs are at least an order of magnitude larger than the DNNs considered in prior work, provide over 90% Top-5 accuracy on ImageNet, and have also been shown to predict lung diseases from chest X-ray images [44, 64]. Thus, our work provides the first implementations of practical ML inference tasks running securely. Even on the smaller MNIST/CIFAR scale DNNs, our protocols require an order of magnitude less communication and significantly outperform the state-of-the-art [42, 48] in both LAN and WAN settings (see Table 5 in Section 7.2).

(29) OT vs HE. Through our evaluation, we also resolve the OT vs HE conundrum: although the initial works on secure inference [47, 50] used OT-based protocols for evaluating convolutions, the state-of-the-art protocols [42, 48], which currently provide the best published inference latency, use HE-based convolutions. HE-based secure inference has much less communication than OT but HE's computation increases with the sizes of convolutions. Since practical DNNs have large Gigabyte-sized convolutions, at the onset of this work, it was not clear to us whether HE-based convolutions would provide us the best latency in practice.

(30) To resolve this empirical question, we implement a cryptographic library PIE that provides two classes of protocols, PIE.sub.OT and PIE.sub.HE. In PIE.sub.OT, inputs are in Z.sub.L (L=custom character, for a suitable choice of custom character). Linear layers such as matrix multiplication and convolution are performed using OT-based techniques [8, 50], while the activations such as ReLU, Maxpool and Avgpool are implemented using our new protocols over Z.sub.L. In PIE.sub.HE, inputs are encoded in an appropriate prime field Z.sub.n. Here, we compute linear layers using homomorphic encryption and the activations using our protocols over Z.sub.n. In both PIE.sub.OT and PIE.sub.HE faithful divisions after linear layers are performed using our new protocols over corresponding rings. Next, we evaluate ImageNet-scale inference tasks with both PIE.sub.OT and PIE.sub.HE. We observe that in a WAN setting, where communication is a bottleneck, HE-based inference is always faster and in a LAN setting OT and HE are incomparable.

(31) 1.2 Our Techniques

(32) Millionaires'. Our protocol for securely computing the millionaire's problem (the bit x<y) uses the following observation (previously made in [28]). Let x=x.sub.1x.sub.0 and y=y.sub.1y.sub.0 (where denotes concatenation and x.sub.1,y.sub.1 are strings of the same length). Then, x<y is the same as checking if either x.sub.1<y.sub.1 or x.sub.1=y.sub.1 and x.sub.0<y.sub.0. Now, the original problem is reduced to computing two millionaires' instances over smaller length strings (x.sub.1<y.sub.1 and x.sub.0<y.sub.0) and one equality test (x.sub.1=y.sub.1). By continuing recursively, one could build a tree all the way where the leaves are individual bits, at which point one could use 1-out-of-2 OT-based protocols to perform the comparison/equality. However, the communication complexity of this protocol is still quite large.

(33) We make several important modifications to this approach. First, we modify the tree so that the recursion is done log(custom character/m) times to obtain leaves with strings of size m, for a parameter m. We then use 1-out-of-2.sup.m OT to compute the comparison/equality at the leaves. Second, we observe that by carefully setting up the receiver's and sender's messages in the OT protocols for leaf comparisons and equality, multiple 1-out-of-2 m OT instances can be combined to reduce communication. Next, recursing up from the leaves to the root, requires securely computing the AND functionality that uses Beaver bit triples [8] (This functionality takes as input shares of bits x, y from the two parties and outputs shares of x AND y to both parties). Here, the AND function takes as input shares of bits x, y from the two parties and output shares of x AND y to both parties. To the best of our knowledge, prior work required a cost of 2 bits per triple [5, 24] (where is the security parameter and typically 128). Now, since the same secret shared value is used in 2 AND instances, we construct correlated pairs of bit triples using 1-out-of-8 OT protocols [43] to reduce this cost to +8 bits (amortized) per triple. Finally, by picking m appropriately, we obtain a protocol for millionaires' whose concrete communication (in bits) is nearly 5 times better than prior work.

(34) ReLU activation. The function ReLU(a) is defined as a.Math.ReLU(a), where ReLU(a)=1 if a>0 and 0 otherwise. Hence, computing ReLU reduces to computing ReLU(a). Let a be additively secret shared as a.sub.0, a.sub.1 over the appropriate ring. Note that a>0 is defined differently for custom character-bit integers (i.e., Z.sub.L) and general rings Z.sub.n. Over Z.sub.L, ReLU(a)=1MSB(a), where MSB(a) is the most significant bit of a. Moreover, MSB(a)=MSB(a.sub.0)MSB(a.sub.1)carry. Here, carry=1 if a.sub.0+a.sub.1custom character, where a.sub.0, a.sub.1 denotes the integer represented by the lower custom character1 bits of a.sub.0, a.sub.1. We compute this carry bit using a call to our millionaires' protocol. Over Z.sub.n, ReLU(a)=1 if a[0, n/2). Given the secret shares a.sub.0, a.sub.1, this is equivalent to (a.sub.0+a.sub.1)[0, n/2)[n, 3n/2) over integers. While this can be navely computed by making 3 calls to the millionaires' protocol, we show that by carefully selecting the inputs to the millionaires' protocol, one can do this with only 2 calls.

(35) Division and Truncation. As a technical result, we provide a correct decomposition of division of a secret ring element in Z.sub.L or Z.sub.n by a public integer into division of secret shares by the same public integer and correction terms (Theorem 4.1). These correction terms consist of multiple inequalities on secret values. As a corollary, we also get a much simpler expression for the special case of truncation, i.e., dividing custom character-bit integers by a power-of-2 (Corollary 4.2). We believe that the general theorem as well as the corollary can be of independent interest. Next, we give efficient protocols for both general division (used for Avgpool, Table 3) as well as division by a power-of-2 (used for multiplication in fixed-point arithmetic). The inequalities in the correction term are computed using our new protocol for millionaires' and the division of shares can be done locally by the respective parties. Our technical theorem is the key to obtaining secure implementation of DNN inference tasks that are bitwise equivalent to cleartext fixed-point execution.

(36) 1.3 Organization

(37) We begin with the details on security and cryptographic primitives used in Section 2 on preliminaries. In Section 3 we provide our protocols for millionaires' (Section 3.1) and ReLU (Section 3.2, 3.3), over both Z.sub.L, and general ring Z.sub.n. In Section 4, we present our protocols for general division, as well as the special case of division by power-of-2. We describe the various components that go into a neural network inference algorithm in Section 5 and show how to construct secure protocols for all these components given our protocols from Sections 3 and 4. We present our implementation details in Section 6 and our experiments in Section 7. We conclude discussion of these general principles in Section 8. Section 9 describes a computing system that may employ the principles described herein. Section 10 is an appendix. Section 11 is a bibliography.

2. Preliminaries

(38) Notation. Let be the computational security parameter and negl() denote a negligible function in . For a set W,

(39) w $ W
denotes sampling an element w, uniformly at random from W. [custom character] denotes the set of integers {1, . . . , custom character}. Let 1{b} denote the indicator function that is 1 when b is true and 0 when b is false.
2.1 Threat Model and Security

(40) We provide security in the simulation paradigm [19, 31, 46] against a static semi-honest probabilistic polynomial time (PPT) adversary custom character. That is, a computationally bounded adversary custom character corrupts either P.sub.0 or P.sub.1 at the beginning of the protocol and follows the protocol specification honestly. Security is modeled by defining two interactions: a real interaction where P.sub.0 and P.sub.1 execute the protocol in the presence of custom character and the environment custom character and an ideal interaction where the parties send their inputs to a trusted functionality that performs the computation faithfully. Security requires that for every adversary custom character in the real interaction, there is an adversary custom character (called the simulator) in the ideal interaction, such that no environment custom character can distinguish between real and ideal interactions. Many of our protocols invoke multiple sub-protocols and we describe these using the hybrid model. This is similar to a real interaction, except that sub-protocols are replaced by the invocations of instances of corresponding functionalities. A protocol invoking a functionality custom character is said to be in custom character-hybrid model.

(41) 2.2 Cryptographic Primitives

(42) 2.2.1 Secret Sharing Schemes. Throughout this work, we use 2-out-of-2 additive secret sharing schemes over different rings [12, 58]. The 3 specific rings that we consider are the field custom character.sub.2, the ring custom character.sub.L, where L=custom character (custom character=32, typically), and the ring custom character.sub.n, for a positive integer n (this last ring includes the special case of prime fields used in the works of [42, 48]). We let Share.sup.L (x) denote the algorithm that takes as input an element x in custom character.sub.L, and outputs shares over custom character.sub.L, denoted by custom characterxcustom character.sub.0.sup.L and custom characterxcustom character.sub.1.sup.L. Shares are generated by sampling random ring elements custom characterxcustom character.sub.0.sup.L and custom characterxcustom character.sub.1.sup.L, with the only constraint that custom characterxcustom character).sub.0.sup.L+custom characterxcustom character.sub.1.sup.L=x (where + denotes addition in custom character.sub.L). Additive secret sharing schemes are perfectly hiding, i.e., given a share custom characterxcustom character.sub.0.sup.L or custom characterxcustom character.sub.1.sup.L, the value x is completely hidden. The reconstruction algorithm Reconst.sup.L (custom characterxcustom character.sub.0.sup.L, custom characterxcustom character.sub.1.sup.L) takes as input the two shares and outputs x=custom characterxcustom character.sub.0.sup.L+custom characterxcustom character.sub.1.sup.L. Shares (along with their corresponding Share( ) and Reconst( ) algorithms) are defined in a similar manner for custom character.sub.2 and custom character.sub.n with superscripts B and n, respectively. We sometimes refer to shares over custom character.sub.L and custom character.sub.n as arithmetic shares and shares over custom character.sub.2 as boolean shares.

(43) 2.2.2 Oblivious Transfer. Let

(44) ( k 1 ) - O T
denote the 1-out-of-k Oblivious Transfer (OT) functionality [17] (which generalizes 1-out-of-2 OT [26, 53]). The sender's inputs to the functionality are the k strings m.sub.1, . . . , m.sub.k, each of length custom character and the receiver's input is a value i[k]. The receiver obtains m.sub.i from the functionality and the sender receives no output. We use the protocols from [43], which are an optimized and generalized version of the OT extension framework proposed in [9, 40]. This framework allows the sender and receiver, to reduce .sup.c number of oblivious transfers to base OTs in the random oracle model [11] (for any constant c>1). We also use the notion of correlated 1-out-of-2 OT [5], denoted by

(45) ( k 1 ) - COT .
In our context, this is a functionality where the sender's input is a ring element x and the receiver's input is a choice bit b. The sender receives a random ring element r as output and the receiver obtains either r or x+r as output depending on b. The protocols for

(46) ( k 1 ) - OT [ 43 ] and ( 2 1 ) - COT [ 5 ]
execute in 2 rounds and have total communication of 2+kcustom character and +custom character, respectively. Moreover, simpler

(47) ( 2 1 ) - O T
has a communication of +2custom character bits [5, 40] (The protocol of

(48) ( k 1 ) - O T [ 43 ]
incurs a communication cost of +kcustom character. However, to achieve the same level of security, their security parameter needs to be twice that of

(49) ( 2 1 ) - COT .
In concrete terms, therefore, we write the cost as 2+k).

(50) 2.2.3 Multiplexer and B2A conversion. The functionality custom character.sub.MUX.sup.n takes as input arithmetic shares of a over n and boolean shares of choice bit c from P.sub.0, P.sub.1, and returns shares of a if c=1, else returns shares of 0 over the same ring. A protocol for custom character.sub.MUX.sup.n can easily be implemented by 2 simultaneous calls to

(51) 0 ( 2 1 ) - O T
and communication complexity is 2(+2), where =log n.

(52) The functionality custom character.sub.B2A.sup.n (for boolean to arithmetic conversion) takes boolean (i.e., over custom character.sub.2) shares as input and gives out arithmetic (i.e., over custom character.sub.n) shares of the same value as output. It can be realized via one call to

(53) ( 2 1 ) - COT
and hence, its communication is +. For completeness, we provide the protocols realizing custom character.sub.MUX.sup.n as well as custom character.sub.B2A.sup.n formally in Appendix A.3 and Appendix A.4, respectively.

(54) 2.2.4 Homomorphic Encryption. A homomorphic encryption of x allows computing encryption of f (x) without the knowledge of the decryption key. In this work, we require an additively homomorphic encryption scheme that supports addition and scalar multiplication, i.e. multiplication of a ciphertext with a plaintext. We use the additively homomorphic scheme of BFV [16, 27] (the scheme used in the recent works of Gazelle [42] and Delphi [48]) and use the optimized algorithms of Gazelle for homomorphic matrix-vector products and homomorphic convolutions. The BFV scheme uses the batching optimization [45, 59] that enables operation on plaintext vectors over the field custom character.sub.n, where n is a prime plaintext modulus of the form 2KN+1, K is some positive integer and N is scheme parameter that is a power-of-2.

3. Millionaire's and ReLU Protocols

(55) In this section, we provide our protocols for millionaire's problem and ReLU(a) (defined to be 1 if a>0 and 0 otherwise) when the inputs are custom character bit signed integers as well as elements in general rings of the form custom character.sub.n (including prime fields). Our protocol for Millionaire's problem invokes instances of custom character.sub.AND that takes as input Boolean shares of values x,y{0, 1} and returns boolean shares of xy. We discuss efficient protocols for custom character.sub.AND in Appendix A.1 and A.2

(56) 3.1 Protocol for Millionaires'

(57) In the Yao Millionaires' problem, party P.sub.0 holds x and party P.sub.1 holds y and they wish to learn boolean shares of 1{x<y}. FIG. 1 illustrates an environment 100 in which the learning occurs and includes first party computing system 101 owned by P.sub.0 and a second party computing system 102 owned by P.sub.1. The first party computing system 101 holds input x, whereas the second party computing system 102 holds input y. Each of the computing systems 101 and 102 may be structured as described below for the computing system 400 of FIG. 4.

(58) As represented by arrow 121, the first party computing system 101 provides its input x to the two-party computation module 110. Also, as represented by arrow 122, the second party computing system 102 provides its input y to the two-party computing module 110. As represented by arrows 131 and 132, the two-party computation module 110 outputs a first share 111 of the value 1{x<y} to the first party computing system 101, and outputs a second share 112 of the value 1{x<y} to the second party computing system 102. At this point, the first and second party computing systems 101 and 102 could not independently reconstruct the value 140 (1{x<y}) unless they acquired the share they do not have from the other party. Thus, unless the two computing systems 101 and 102 were to share their shares (as represented by arrows 141 and 142), the result of the computation remains secure.

(59) Here, x and y are custom character-bit unsigned integers. We denote this functionality by custom character. Our protocol for custom character builds on the following observation (Equation 1) that was also used in [28].
1{x<y}=1{x.sub.1<y.sub.1}(1{x.sub.1=y.sub.1}1{x.sub.0<y.sub.0}),(1)
where, x=x.sub.1x.sub.0 and y=y.sub.1y.sub.0.

(60) Let m be a parameter and M=2.sup.m. First, for ease of exposition, we consider the special case when m divides custom character and q=custom character/m is a power of 2. FIG. 2 illustrates the an general process flow that each of the two computing systems would employ. We describe our protocol for millionaire's problem in this setting formally in Algorithm 1. We use Equation 1 above, recursively log q times to obtain q leaves of size m bits. For example, That is, let x=x.sub.q-1 . . . x.sub.0 and y=y.sub.q-1 . . . y.sub.0 (where every x.sub.1,y.sub.1{0, 1}.sup.m).

(61) Now, we compute the shares of the inequalities and equalities of strings at the leaf level using

(62) ( M 1 ) - OT 1
(steps 9 and 10, resp.). Next, we compute the shares of the inequalities (steps 14 & 15) and equalities (step 16) at each internal node upwards from the leaf using Equation 1. Value of inequality at the root gives the final output.

(63) TABLE-US-00004 Algorithm 1 Millionaires,custom character : Input: P.sub.0, P.sub.1 hold x {0, 1custom character and y {0, 1custom character , respectively. Output: P.sub.0, P.sub.1 learn custom character 1{x < y}custom character .sub.0.sup.B and custom character 1{x < y}custom character .sub.1.sup.B, respectively. 1: P.sub.0 parses its input as x = x.sub.q1 || . . . || x.sub.0 and P.sub.1 parses its input as y = y.sub.q1 || . . . ||y.sub.0, where x.sub.i, y.sub.i {0, 1}.sup.m, q = custom character /m. 2: Let M= 2.sup.m. 3: for j= {0,...,q -1} do 4: P 0 samples .Math. lt 0 , j .Math. 0 B , .Math. eq 0 , j .Math. 0 B $ { 0 , 1 } . 5: for k= {0, . . . , M-1} do 6: P.sub.0 sets s.sub.j,k = custom character lt.sub.0,jcustom character .sub.0.sup.B {x.sub.j < k}. 7: P.sub.0 sets t.sub.j,k = custom character eq.sub.0,jcustom character .sub.0.sup.B {x.sub.j = k}. 8: end for 9: P.sub.0 & P.sub.1 invoke an instance of ( M 1 ) - O T 1 where P.sub.0 is the sender with inputs {s.sub.j,k}.sub.k and P.sub.1 is the receiver with input y.sub.j. P.sub.1 sets its output as custom character lt.sub.0,jcustom character .sub.1.sup.B. 10: P.sub.0 & P.sub.1 invoke an instance of ( M 1 ) - O T 1 where P.sub.0 is the sender with inputs {t.sub.j,k}.sub.k and P.sub.1 is the receiver with input y.sub.j. P.sub.1 sets its output ascustom character eq.sub.0,jcustom character .sub.1.sup.B. 11: end for 12: for i= {1, . . . , log q} do 13: for j = {0, . . . , (q/2.sup.i) 1} do 14: For b {0, 1}, P.sub.b invokes custom character .sub.AND with inputs custom character lt.sub.i1,2jcustom character .sub.b.sup.B and custom character eq.sub.i1,2j+1custom character .sub.b.sup.B to learn output custom character tempcustom character .sub.b.sup.B. 15: P.sub.b sets custom character lt.sub.i,jcustom character .sub.b.sup.B = custom character lt.sub.i1,2j+1custom character .sub.b.sup.B custom character tempcustom character .sub.b.sup.B. 16: For b {0, 1}, P.sub.b invokes custom character .sub.AND with inputs custom character eq.sub.i1,2jcustom character .sub.b.sup.B and custom character eq.sub.i1,2j+1custom character .sub.b.sup.B to learn output custom character eq.sub.i,2custom character .sub.b.sup.B. 17: end for 18: end for 19: For b {0, 1}, P.sub.b outputs custom character lt.sub.log n,0custom character .sub.b.sup.B.

(64) Let us take a concrete example to further clarify with respect to FIGS. 2A and 2B. FIG. 2A shows the processing associated with the first party computing system. FIG. 2B shows the processing associated with the second party computing system. Suppose that the length of the input f is 16, and that the length of each leaf string m will be 4. Here M will be 2.sup.4 or 16. Furthermore, q=custom character/m, which equals 16/4 or 4. Equation 1 will be performed recursively log.sub.2 q times, or in other words log.sub.2 4 times, or in other words twice. This is the special cases since m divides l, and since q is a power of 2 (2.sup.2). Now let us discuss an example input x=1001010110000001, and an example input y=1001010110001000.

(65) In line 1 of Algorithm 1, and referring to the arrow 201A of FIG. 2A, P.sub.0 parses x to obtain x.sub.3=1001, x.sub.2=0101, x.sub.1=1000, and x.sub.0=0001. Also in line 1 and referring to the arrow 201B of FIG. 2B, P.sub.1 parses y to obtain y.sub.3=1001, y.sub.2=0101, y.sub.1=1000, and y.sub.0=1000. Note that the value of 1{x<y} is binary 1 since x is indeed less than y, but neither party knows this at least at this stage, and neither party will ever know this if this is not the final output of the garbled circuit representing the DNN. Instead, each party will only learn their respective Boolean share of 1{x<y}.

(66) In line 9, using

(67) ( 1 6 1 ) - O T 1
each party learns their Boolean share of 1{x.sub.3<y.sub.3}, 1{x.sub.2<y.sub.2}, 1{x.sub.1<y.sub.1}, and 1{x.sub.0<y.sub.0}, or in other words, their respective Boolean share of 0, 0, 0, and 1 since only 1{x.sub.0<y.sub.0} is equal to one. As represented by arrow 211A of FIG. 2A, the first party computing system learns its shares 221A of 1{x.sub.3<y.sub.3}, 1{x.sub.2<y.sub.2}, 1{x.sub.1<y.sub.1}, and 1{x.sub.0<y.sub.0}. As represented by arrow 211B of FIG. 2B, the second party computing system also learns its shares 221B of 1{x.sub.3<y.sub.3}, 1{x.sub.2<y.sub.2}, 1{x.sub.1<y.sub.1}, and 1{x.sub.0<y.sub.0}. Again, each party only knows Boolean shares of these values, and thus continues to be obvious as to the truth of each of these inequalities.

(68) In line 10, each party uses

(69) ( 1 6 1 ) - O T 1 to
to learn their Boolean share of 1{x.sub.3=y.sub.3}, 1{x.sub.2=y.sub.2}, 1{x.sub.1=y.sub.1} and 1{x.sub.0=y.sub.0}, or in other words their Boolean share of 1, 1, 1, 0, since only x.sub.0=y.sub.0 is false, and since the leaf strings x.sub.3, x.sub.2 and x.sub.1 are each equal to the respective leaf strings y.sub.3, y.sub.2 and y.sub.1. As represented by arrow 212A of FIG. 2A, the first party computing system learns its shares 222A of 1{x.sub.3=y.sub.3}, 1{x.sub.2=y.sub.2}, 1{x.sub.1=y.sub.1} and 1{x.sub.0=y.sub.0}. As represented by arrows 212B of FIG. 2B, the second party computing system learns its shares 222B of 1{x.sub.3=y.sub.3}, 1{x.sub.2=y.sub.2}, 1{x.sub.1=y.sub.1} and 1{x.sub.0=y.sub.0}. Again, each party only knows Boolean shares of these values, and thus continues to be obvious as to the truth of each of these inequalities.

(70) In the first recursion 230 (when i is equal to 1), there is an inequality and equality to be learned for x.sub.32 and y.sub.32 (when j is equal to 0, and where x.sub.32=x.sub.3x.sub.2 and y.sub.32=y.sub.3y.sub.2), and an equality and inequality to be learned for x.sub.10 and y.sub.1- (when j is equal to 1, and where x.sub.10=x.sub.1x.sub.1 and y.sub.10=y.sub.1y.sub.1).

(71) The first iteration will now be described with respect to the example. In this example x.sub.32 is 10010101, and y.sub.32 is also 10010101. Thus, we expect 1{x.sub.32<y.sub.32} to be 0. Applying Equation 1 to inputs y.sub.3. y.sub.2, x.sub.3, and x.sub.2, each party learns their respective Boolean shares 231A and 231B of 1{x.sub.32<y.sub.32}, which is 0(10), or 00, or 0. Applying custom character.sub.AND to these same inputs, each party learns their respective shares 233A and 233B of 1{x.sub.32=y.sub.32}, which is 1. Also in this example x.sub.10 is 10000001, and y.sub.10 is also 10001000. Thus, we expect 1{x.sub.10<y.sub.10} to be 1. Applying Equation 1 to inputs y.sub.1. y.sub.0, x.sub.1, and x.sub.1, each party learns their respective Boolean shares 232A and 232B of 1{x.sub.10<y.sub.10}, which is 0(11), or 01, or 1. Applying custom character.sub.AND to these same inputs, each party learns their respective shares 234A and 234B of 1{x.sub.10=y.sub.10}, which is 0. In the second iteration, the value 1{x<y} should be 1 since x is less than y. Applying Equation 1 to inputs y.sub.32. y.sub.10, x.sub.32, and x.sub.10, each party learns their respective Boolean shares 241A and 241B of 1{x<y}, which is 0(11), or 01, or 1.

(72) Correctness and security. Correctness is shown by induction on the depth of the tree starting at the leaves. First, by correctness of

(73) ( M 1 ) - O T 1
in step 9, custom characterlt.sub.0,jcustom character.sub.1.sup.B=custom characterlt.sub.0,jcustom character.sub.0.sup.B1{x.sub.j<y.sub.j}. Similarly, custom charactereq.sub.0,icustom character.sub.1.sup.B=custom charactereq.sub.0,icustom character.sub.0.sup.B1{x.sub.j=y.sub.j}. This proves the base case. Let q.sub.i=q/2.sup.i. Also, for level i of the tree, parse x=x.sup.(i)=x.sub.q.sub.i.sub.1.sup.(i) . . . x.sub.0.sup.(i) and y=y.sup.(i)=y.sub.q.sub.i.sub.1.sup.(i) . . . y.sub.0.sup.(i). Assume that for i it holds that lt.sub.i,j=custom characterlt.sub.i,j custom character.sub.0.sup.Bcustom characterlt.sub.i,jcustom character.sub.1.sup.B=1{x.sub.j.sup.(i)<y.sub.j.sup.(i)} and custom charactereq.sub.i,j custom character.sub.0.sup.B custom charactereq.sub.i,jcustom character.sub.1.sup.B=1{x.sub.j.sup.(i)=y.sub.j.sup.(i)} for all j{0, . . . , q.sub.i1}. Then, we prove the same for i+1 as follows: By correctness of custom character.sub.AND, for j{0, . . . , q.sub.i+11}, custom characterlt.sub.i+1,jcustom character.sub.0.sup.Bcustom characterlt.sub.i+1,jcustom character.sub.1.sup.B=lt.sub.i,2j+1(lt.sub.i,2jeq.sub.i,2j+1)=1{x.sub.2j+1.sup.(i)<y.sub.2j+1.sup.(i)}(1{x.sub.2j.sup.(i)<y.sub.2j.sup.(i) }1{x.sub.2j+1.sup.(i)=y.sub.2j+1.sup.(i)})=1{x.sub.j.sup.(i+1)y.sub.j.sup.(i+1)} (using Equation 1). The induction step for eq.sub.i+1,j holds in a similar manner, thus proving correctness. Given uniformity of custom characterlt.sub.0,jcustom character.sub.0.sup.B, custom charactereq.sub.0,jcustom character.sub.0.sup.B for all j{0, . . . , q1}, security follows easily in the

(74) ( ( M 1 ) - OT 1 ,
custom character.sub.AND)-hybrid.

(75) General case. When m does not divide custom character and q=custom character/m is not a power of 2, we make the following modifications to the protocol. Since m does not divide custom character, x.sub.q-1{0, 1}.sup.r, where r=custom character mod m (Note that r=m when m|custom character). When doing the compute for x.sub.q-1 and y.sub.q-1, we perform a small optimization and use

(76) 0 ( R 1 ) - OT 1
in steps 9 and 10, where R=2.sup.r. Second, since q is not a power of 2, we do not have a perfect binary tree of recursion and we need to slightly change our recursion/tree traversal. In the general case, we construct maximal possible perfect binary trees and connect the roots of the same using the relation in Equation 1. Let be such that 2.sup.<q2.sup.+1. Now, our tree has a perfect binary sub-tree with 2 leaves and we have remaining q=q2.sup. leaves. We recurse on q. In the last step, we obtain our tree with q leaves by combining the roots of perfect binary tree with 2.sup. leaves and tree with q leaves using Equation 1. Note that value at the root is computed using log q sequential steps starting from the leaves.

(77) Again, let us take a concrete example to further clarify. Suppose that the length of the input custom character is 11, and that the length of each leaf string m will be 4. As an example suppose that input x=10110000001, and input y=10110001000. Here, m does not divide custom character. Accordingly, x.sub.q-1{0, 1}.sup.r, where r=custom character mod m (Note that r=m when mcustom character). Accordingly, x.sub.2 is equal to 101, and y.sub.2 is equal to 101. q is equal to 3, and thus there is no x.sub.3 and y.sub.3. x.sub.1, x.sub.0, y.sub.1 and y.sub.2 are the same as in the previous example. Here, when doing the compute for x.sub.2 and y.sub.2, the Boolean shares of the inequality and equality are each learned using uses

(78) ( 8 1 ) - O T 1
instead of uses

(79) ( 1 6 1 ) - O T 1 .
In the first iteration, the Boolean shares the equalities and inequalities of x.sub.2 and y.sub.2 are calculated However, the equalities and inequalities for x.sub.10 and y.sub.10 are still calculated. Then, in the second recursion, the Boolean shares of the inequality for x and y is calculated using inputs, x.sub.2 and x.sub.10, and y.sub.2 and y.sub.10.

(80) 3.1.1 Optimizations. We reduce the concrete communication complexity of our protocol using the following optimizations that are applicable to both the special and the general case.

(81) Combining two

(82) ( M 1 ) - O T 1
calls into one

(83) ( M 1 ) - O T 2 :
Since the input of P.sub.1 (OT receiver) to

(84) ( M 1 ) - O T 1
in steps 9 and 10 is the same, i.e. y.sub.j, we can collapse these steps into a single call to

(85) ( M 1 ) - O T 2
where P.sub.0 and P.sub.1 input {(s.sub.j,kt.sub.j,k)}.sub.k and y.sub.j, respectively. P.sub.1 sets its output as (custom characterlt.sub.0, custom character.sub.1.sup.Bcustom charactereq.sub.0,jcustom character.sub.1.sup.B). This reduces the cost from 2(2+M) to (2+2M).

(86) Realizing custom character.sub.AND efficiently: It is known that custom character.sub.AND can be realized using Beaver bit triples [8]. In prior works [5, 24], generating a bit triple costs 2 bits. For our protocol, we observe that the 2 calls to custom character.sub.AND in steps 14 and 16 have a common input, custom charactereq.sub.i1,2j+1custom character.sub.b.sup.B. Hence, we optimize communication of these steps by generating correlated bit triples (custom characterdcustom character.sub.b.sup.B, custom characterecustom character.sub.b.sup.B, custom characterfcustom character.sub.b.sup.B) and (custom characterdcustom character.sub.b.sup.B, custom characterecustom character.sub.b.sup.B, custom characterfcustom character.sub.b.sup.B) for b{0, 1}, such that de=f and de=f. Next, we use

(87) ( 8 1 ) - O T 2
to generate one such correlated bit triple (Appendix A.2) with communication 2+16 bits, giving the amortized cost of +8 bits per triple. Given correlated bit triples, we need 6 additional bits to compute both custom character.sub.AND calls.

(88) Removing unnecessary equality computations: As observed in [28], the equalities computed on lowest significant bits are never used. Concretely, we can skip computing the values eq.sub.i,0 for i{0, . . . , log q}. Once we do this optimization, we only need a single call to custom character.sub.AND instead of 2 correlated calls for the leftmost branch of the tree. We use the

(89) ( 16 1 ) - O T 2 .fwdarw. 2 ( 4 1 ) - O T 1
reduction to generate 2 regular bit triples (Appendix A.1) with communication of 2+32 bits. This gives us amortized communication of +16 bits per triple. This is 2 improvement over 2 bits required in prior works [5, 24]. Given a bit triple, we need 4 bits to realize custom character.sub.AND. This reduces the total communication by M (for the leaf) plus (+2).Math.log q (for leftmost branch) bits.

(90) 3.1.2 Communication Complexity. In our protocol, we communicate in protocols for OT (steps 9&10) and custom character.sub.AND (steps 14&16). With above optimizations, we need 1 call to

(91) ( M 1 ) - O T 1 ,
(q2) calls to

(92) 0 ( M 1 ) - O T 2
and 1 call to

(93) ( R 1 ) - O T 2
which cost (2+M), ((q2).Math.(2+2M)(and (2+2R) bits, respectively. In addition, we have log q invocations of custom character.sub.AND and (q1log q) invocations of correlated custom character.sub.AND. These require communication of (+20).Math.log q and (2+22).Math.(q1log q) bits. This gives us total communication of (4qlog q2)+M(2q3)+2R+22(q1)2log q bits. Using this expression for custom character=32 we get the least communication for m=7 (Table 1). We note that there is a trade-off between communication and computational cost of OTs used and we discuss our choice of m for our experiments in Section 6.
3.2 Protocol for ReLU for custom character-Bit Integers

(94) Here, we describe our protocol for custom character that takes as input arithmetic shares of a and returns boolean shares of ReLU(a) (DReLU stands for derivative of ReLU, i.e., ReLU). Note that ReLU(a)=(1MSB(a)), where MSB(a) is the most significant bit of a. Let arithmetic shares of acustom character.sub.L be custom characteracustom character.sub.0.sup.L=msb.sub.0x.sub.0 and custom characteracustom character=msb.sub.1x.sub.1 such that msb.sub.0, msb.sub.1{0, 1}. We compute the boolean shares of MSB(a) as follows: Let carry=1{(x.sub.0+x.sub.1)>custom character1}. Then, MSB(a)=msb.sub.0msb.sub.1carry. We compute boolean shares of carry by invoking an instance of custom character.

(95) TABLE-US-00005 Algorithm 2custom character -bit integer ReLUcustom character : Input: P.sub.0, P.sub.1 holdcustom character acustom character .sub.0.sup.L andcustom character acustom character .sub.1.sup.L, respectively. Output: P.sub.0, P.sub.1 getcustom character ReLU(a)custom character .sub.0.sup.B andcustom character ReLU(a)custom character .sub.1.sup.B. 1: P.sub.0 parses its input ascustom character acustom character .sub.0.sup.L = msb.sub.0x.sub.0 and P.sub.1 parses its input ascustom character acustom character .sub.1.sup.L = msb.sub.1x.sub.1, s.t. b {0, 1}, msb.sub.b {0, 1}, x.sub.b {0, 1}custom character . 2: P.sub.0 & P.sub.1 invoke an instance ofcustom character , where P.sub.0's input iscustom character 1 x.sub.0 and P.sub.1's input is x.sub.1. For b {0, 1}, P.sub.b learnscustom character carrycustom character .sub.b.sup.B. 3: For b {0, 1}, P.sub.b setscustom character ReLUcustom character .sub.b.sup.B = msb.sub.b custom character carrycustom character .sub.b.sup.B b.

(96) Correctness and security. By correctness of custom character, Reconst.sup.B (custom charactercarrycustom character).sub.0.sup.B, (custom charactercarrycustom character.sub.1.sup.B)=1{custom character1x.sub.0)<x.sub.1}=1{(x.sub.0+x.sub.1)>custom character1}. Also, Reconst.sup.B (custom characterReLUcustom character).sub.0.sup.B, custom characterReLUcustom character.sub.1.sup.B)=msb.sub.0msb.sub.1 carry1=MSB(a)1. Security follows trivially in the custom character hybrid.

(97) Communication complexity In Algorithm 2, we communicate the same as in custom character; that is <+14)(custom character1) by using m=4.

(98) 3.3 Protocol for ReLU for General custom character.sub.n

(99) We describe a protocol for custom characterthat takes arithmetic shares of a over custom character.sub.n as input and returns boolean shares of ReLU(a). For integer rings custom character.sub.n, ReLU(a)=1 if a<n/2 and 0 otherwise. Note that this includes the case of prime fields considered in the works of [42, 48]. We first describe a (simplified) protocol for ReLU in custom character.sub.n, in Algorithm 3 with protocol logic as follows: Let arithmetic shares of acustom character.sub.n be custom characteracustom character.sub.0.sup.n, and custom characteracustom character.sub.1.sup.n. Define wrap=1{custom characteracustom character.sub.0.sup.n+custom characteracustom character.sub.n.sup.1>n1}, lt=1{custom characteracustom character.sub.0.sup.n+custom characteracustom character.sub.1.sup.n>(n1)/2} and rt=1{custom characteracustom character.sub.0.sup.n+custom characteracustom character.sub.1.sup.n>n+(n1)/2}. Then, ReLU(a) is (1lt) if wrap=0, else it is (1rt). In Algorithm 3, steps 1, 2, 3, compute these three comparisons using custom character.sub.MILL. Final output can be computed using an invocation of custom character.sub.MUX.sup.2.

(100) TABLE-US-00006 Algorithm 3 Simple Integer ring ReLU .sub.DReLU.sub.simple.sup.ring, n : Input: P.sub.0, P.sub.1, holdcustom character acustom character .sub.0.sup.n andcustom character acustom character .sub.1.sup.n , respectively, where a custom character .sub.n. Output: P.sub.0, P.sub.1 getcustom character ReLU(a)custom character .sub.0.sup.B andcustom character ReLU(a)custom character .sub.1.sup.B. 1: P.sub.0 & P.sub.1 invoke an instance ofcustom character .sub.MILL.sup. with = log n, where P.sub.0's input is (n 1 custom character acustom character .sub.0.sup.n) and P.sub.1's input iscustom character acustom character .sub.1.sup.n .Math. For b {0, 1}, P.sub.b learnscustom character wrapcustom character .sub.b.sup.B as output. 2: P.sub.0 & P.sub.1 invoke an instance ofcustom character .sub.MILL.sup.+1, where P.sub.0's input is (n 1 custom character acustom character .sub.0.sup.n) and P.sub.1's input is ((n 1)/2 +custom character acustom character .sub.1.sup.n). For b {0, 1}, P.sub.b learnscustom character ltcustom character .sub.b.sup.B as output. 3: P.sub.0 & P.sub.1 invoke an instance ofcustom character .sub.MILL.sup.+1, where P.sub.0's input is (n + (n 1)/2 custom character acustom character .sub.0.sup.n) and P.sub.1's input iscustom character acustom character .sub.1.sup.n .Math. For b {0, 1}, P.sub.b learnscustom character rtcustom character .sub.b.sup.B as output. 4: For b {0, 1}, P.sub.b invokescustom character .sub.MUX.sup.2 with input (custom character ltcustom character .sub.b.sup.B custom character rtcustom character .sub.b.sup.B) and choicecustom character wrapcustom character .sub.b.sup.B to learn custom character zcustom character .sub.b.sup.B. 5: For b {0,1}, P.sub.b outputscustom character zcustom character .sub.b.sup.B custom character ltcustom character .sub.b.sup.B b.

(101) Optimizations We describe an optimized protocol for custom character.sub.DReLU.sup.ring,n in Algorithm 4 that reduces the number of calls to custom character.sub.MILL to 2. First, we observe that if the input of P.sub.1 is identical in all three invocations, then the invocation of OT in Algorithm 1 (steps 9&10) can be done together for the three comparisons. This reduces the communication for each leaf OT invocation in steps 9&10 by an additive factor of 4. To enable this, P.sub.0, P.sub.1 add (n1)/2 to their inputs to custom character.sub.MILL.sup.+1 in steps 1, 3 (=log n). Hence, P.sub.1's input to custom character.sub.MILL.sup.+1 is (n1)/2+custom characteracustom character.sub.1.sup.n in all invocations and P.sub.0's inputs are (3(n1)/2custom characterncustom character.sub.0.sup.n) (n1custom characteracustom character.sub.0.sup.n), (2n1custom characteracustom character.sub.0.sup.n) in steps 1, 2, 3, respectively.

(102) TABLE-US-00007 Algorithm 4 Optimized Integer ring ReLU, .sub.DReLU.sup.ring,n: Input: P.sub.0, P.sub.1 hold custom character acustom character .sub.0.sup.n and custom character acustom character .sub.1.sup.n, respectively, where a custom character .sub.n. Let = logn. Output: P.sub.0, P.sub.1 get custom character ReLU(a)custom character .sub.0.sup.B and custom character ReLU(a)custom character .sub.1.sup.B. 1: P.sub.0 & P.sub.1 invoke an instance of custom character .sub.MILL.sup.+1, where P.sub.0s input is (3(n 1)/2 custom character acustom character .sub.0.sup.n) and P.sub.1s input is (n 1)/2 + custom character acustom character .sub.1.sup.n. For b {0, 1}, P.sub.b learns custom character wrapcustom character .sub.b.sup.B as output. 2: P.sub.0 sets x =(2n 1 custom character acustom character .sub.0.sup.n) if custom character acustom character .sub.0.sup.n > (n 1)/2, else x =(n 1 custom character acustom character .sub.0.sup.n). 3: P.sub.0 & P.sub.1 invoke an instance of custom character .sub.MILL.sup.+1, where P.sub.0s input is x and P.sub.1s input is ((n 1)/2 + custom character acustom character .sub.1.sup.n). For b {0, 1}, P.sub.b learns custom character xtcustom character .sub.b.sup.B as output. 4: P 0 samples .Math. z .Math. 0 B $ { 0 , 1 } . 5: for j = {00, 01, 10, 11} do 6: P.sub.0 parses j as j.sub.0||j.sub.1 and sets t.sub.j = 1 custom character xtcustom character .sub.0.sup.B j.sub.0. 7: if custom character acustom character .sub.0.sup.n > (n 1)/2 then 8: P.sub.0 sets s.sub.j = t.sub.j (custom character wrapcustom character .sub.0.sup.B j.sub.1). 9: else 10: P.sub.0 sets s.sub.j = t.sub.j ((1 t.sub.j) (custom character wrapcustom character .sub.0.sup.B j.sub.1)). 11: end if 12: P.sub.0 sets s.sub.j = s.sub.j custom character zcustom character .sub.0.sup.B 13: end for 14: P 0 & P 1 invoke an instance of ( 4 1 ) - O T 1 where P 0 is the sender with inputs { s j } j and P 1 is the receiver with inputcustom character xtcustom character .sub.1.sup.B||custom character wrapcustom character .sub.1.sup.B. P.sub.1 sets its output ascustom character zcustom character .sub.1.sup.B. 15: For b {0, 1}, P.sub.b outputscustom character zcustom character .sub.b.sup.B.

(103) Next, we observe that one of the comparisons in step 2 or step 3 is redundant. For instance, if custom characteracustom character.sub.0.sup.n>(n1)/2, then the result of the comparison lt=custom characteracustom character.sub.0.sup.n+custom characteracustom character.sub.1.sup.n>(n1)/2 done in step 2 is always 1. Similarly, if custom characteracustom character.sub.0.sup.n(n1)/2, then the result of the comparison rt=1{custom characteracustom character.sub.0.sup.n+custom characteracustom character.sub.1.sup.n>n+(n1)/2} done in step 3 is always 0. Moreover, P.sub.0 knows based on her input custom characteracustom character.sub.0.sup.n which of the two comparisons is redundant. Hence, in the optimized protocol, P.sub.0 and P.sub.1 always run the comparison to compute shares of wrap and one of the other two comparisons. Note that the choice of which comparison is omitted by P.sub.0 need not be communicated to P.sub.1, since P.sub.1's input is same in all invocations of custom character.sub.MILL. Moreover, this omission does not reveal any additional information to P.sub.1 by security of custom character.sub.MILL. Finally, P.sub.0 and P.sub.1 can run a

(104) ( 4 1 ) - O T 1
to learn the shares of ReLU(a). Here, P.sub.1 is the receiver and her choice bits are the shares learnt in the two comparisons. P.sub.0 is the sender who sets the 4 OT messages based on her input share, and two shares learnt from the comparison protocol. We elaborate on this in the correctness proof below.

(105) Correctness and Security. First, by correctness of custom character.sub.MILL.sup.+1 (step 1), wrap=Reconst.sup.B (custom characterwrapcustom character.sub.0.sup.B, custom characterwrapcustom character.sub.1.sup.B)=1{custom characteracustom character.sub.0.sup.L+custom characteracustom character.sub.1.sup.L>n1}. Let j*=custom characterxtcustom character.sub.1.sup.Bcustom characterwrapcustom character.sub.1.sup.B. Then t.sub.j*=1xt. We will show that s.sup.t.sub.j*=ReLU(a), and hence, by correctness of

(106) ( 4 1 ) - O T 1 ,
z=ReconstB (custom characterzcustom character.sub.0.sup.B, custom characterzcustom character.sub.1.sup.B)=ReLU(a). We have the following two cases.

(107) When custom characteracustom character.sub.0.sup.L>(n1)/2, lt=1, and ReLU(a)=wrap(1rt). Here, by correctness of custom character.sub.MILL.sup.+1 (step 3), xt=Reconst.sup.B (custom characterxtcustom character.sub.0.sup.B, custom characterxtcustom character.sub.1.sup.B)=rt. Hence, s.sub.j*=t.sub.j*(custom characterwrapcustom character.sub.0.sup.Bj*.sub.1)=(1rt)wrap.

(108) When custom characteracustom character.sub.0.sup.L(n1)/2, rt=0, ReLU(a) is 1lt if wrap=0, else 1. It can be written as (1lt)(ltwrap). In this case, by correctness of custom character.sub.MILL.sup.+1 (step 3), xt=Reconst.sup.B (custom characterxcustom character.sub.0.sup.B, custom characterxtcustom character.sub.1.sup.B)=lt. Hence, s.sub.j*=t.sub.j*((1t.sub.j*)(custom characterwrapcustom character.sub.0.sup.Bj*.sub.1))=(1lt)(ltwrap). Since custom characterzcustom character.sub.0.sup.B is uniform, security follows in the

(109) ( MILL + 1 , ( 4 1 ) - O T 1 ) - hybrid .

(110) Communication complexity. With the above optimization, the overall communication complexities of our protocol for ReLU in custom character.sub.n is equivalent to 2 calls to .sub.MILL.sup.+1 where P.sub.1 has same input plus 2+4 (for protocol for

(111) ( 4 1 ) - O T 1 ) .
Two calls to .sub.MILL.sup.+1 in this case (using m=4) cost<3/2(+1)+28(+1) bits. Hence, total communication is <3/2(+1)+28(+1)+2+4. We note that the communication complexity of simplified protocol in Algorithm 3 is approximately 3 independent calls to .sub.MILL.sup., which cost 3(+14) bits, plus 2+4 bits for custom character.sub.MUX.sup.2. Thus, our optimization gives almost 2 improvement.

4 Division and Truncation

(112) We present our results on secure implementations of division in the ring by a positive integer and truncation (division by power-of-2) that are bitwise equivalent to the corresponding cleartext computation. We begin with closed form expressions for each of these followed by secure protocols that use them.

(113) 4.1 Expressing General Division and Truncation Using Arithmetic Over Secret Shares

(114) Let idiv: custom charactercustom character.fwdarw.custom character denote signed integer division, where the quotient is rounded towards and the sign of the remainder is the same as that of divisor. We denote division of a ring element by a positive integer using rdiv: custom character.sub.ncustom character.fwdarw.custom character.sub.n defined as
r div(a,d)custom characteri div(a.sub.u1{a.sub.un/2}.Math.n,d)mod n,
where the integer a.sub.u{0, 1, . . . , n1} is the unsigned representation of acustom character.sub.n lifted to integers and 0<d<n. For brevity, we use x=.sub.n y to denote x mod n=y mod n.

(115) THEOREM 4.1. (Division of ring element by positive integer). Let the shares of acustom charactern be custom characteracustom character.sub.0.sup.n, custom characteracustom character.sub.1.sup.ncustom character.sub.n, for some n=n.sup.1.Math.d+n.sup.0custom character, where n.sup.0, n.sup.1, dcustom character and 0n.sup.0<d<n. Let the unsigned representation of a, custom characteracustom character.sub.0.sup.n, custom characteracustom character.sub.1.sup.n in custom character.sub.n lifted to integers be a.sub.u, a.sub.0, a.sub.1{0, 1, . . . , n1}, respectively, such that a.sub.0=a.sub.0.sup.1.Math.d+a.sub.0.sup.0 and a.sub.1=a.sub.1.sup.1.Math.d+a.sub.1.sup.0, where a.sub.0.sup.1, a.sub.0.sup.0, a.sub.1.sup.1, a.sub.1.sup.0custom character and 0a.sub.0.sup.0, a.sub.1.sup.0<d. Let n=n/2custom character. Define corr, A, B, Ccustom character as follows:

(116) corr = { - 1 ( a u n ) ( a 0 < n ) ( a 1 < n ) 1 a u < n a 0 n a 1 n 0 otherwise A = a 0 0 + a 1 0 - ( 1 { a 0 n } + 1 { a 1 n } - corr ) .Math. n 0 . B = idiv ( a 0 0 - 1 { a 0 n } .Math. n 0 , d ) + idiv ( a 1 0 - 1 { a 1 n } .Math. n 0 , d ) C = 1 { A < d } + 1 { A < 0 } + 1 { A < - d }
Then, we have:
r div(custom characteracustom character.sub.0.sup.n,d)+r div(custom characteracustom character.sub.1.sup.n,d)+(corr.Math.n.sup.1+1CB)mod n=.sub.nr div(a,d).
The proof of the above theorem is presented in Appendix C.

(117) 4.1.1 Special Case of truncation for custom character bit integers. The expression above can be simplified for the special case of division by 2.sup.s of custom character-bit integers, i.e., arithmetic right shift with s (>>s), as follows:

(118) COROLLARY 4.2. (Truncation for custom character-bit integers). Let the shares of acustom character.sub.L be custom characteracustom character.sub.0.sup.L, custom characteracustom character.sub.1.sup.Lcustom character.sub.L. Let the unsigned representation of a, custom characteracustom character.sub.0.sup.L, custom characteracustom character.sub.1.sup.L in custom character.sub.L lifted to integers be a.sub.u, a.sub.0, a.sub.1{0, 1, . . . , custom character1}, respectively, such that a.sub.0=a.sub.0.sup.1.Math.2.sup.s+a.sub.0.sup.0 and a.sub.1=a.sub.1.sup.1.Math.2.sup.s+a.sub.1.sup.0, where a.sub.0.sup.1, a.sub.0.sup.0, a.sub.1.sup.1, a.sub.1.sup.0custom character and 0a.sub.0.sup.0, a.sub.1.sup.0<2.sup.s. Let corrcustom character be defined as in Theorem 4.1. Then, we have:
(a.sub.0>>s)+(a.sub.1>>s)+corr.Math.custom character+1{a.sub.0.sup.0+a.sub.1.sup.02.sup.s}=L(a>>s).
PROOF. The corollary follows directly from Theorem 4.1 as follows: First, (a>>s)=rdiv(a, 2.sup.s). Next, n=custom character, n.sup.1=2custom character.sup..sup.s, and n.sup.0=0. Using these, we get A=a.sub.0.sup.0+a.sub.1.sup.0, B=0 and C=1{A<2s}=1{a.sub.0.sup.0+a.sub.1.sup.0<2.sup.s}.
4.2 Protocols for Division

(119) In this section, we describe our protocols for division in different settings. We first describe a protocol for the simplest case of truncation for f-bit integers followed by a protocol for general division in custom character.sub.n by a positive integer (Section 4.2.2). Finally, we discuss another simpler case of truncation, which allows us to do better than general division for rings with a special structure (Section 4.2.3).

(120) TABLE-US-00008 Algorithm 5 Truncation, custom character : Input: For b {0, 1}, P.sub.b holds custom character acustom character .sub.b.sup.L, where a custom character .sub.L. Output: For b {0, 1}, P.sub.b learns custom character zcustom character .sub.b.sup.L s.t. z = a >> s. 1: For b {0, 1}, let a.sub.b, a.sub.b.sup.1 custom character be as defined in Corollary 4.2. 2: For b {0, 1}, P.sub.b invokes custom character .sub.DReLU.sup.int,custom character .sup., with input custom character acustom character .sub.b.sup.L to learn output custom character custom character .sub.b.sup.B. Party P.sub.b sets custom character mcustom character .sub.b.sup.B= custom character custom character .sub.b.sup.B b. 3: For b {0, 1}, P.sub.b sets x.sub.b = MSB(custom character acustom character .sub.b.sup.L). 4: P 0 samples .Math. corr .Math. 0 L $ Z 2 t . 5: for j = {00, 01, 10, 11} do 6: P.sub.0 computes t.sub.j = (custom character mcustom character .sub.0.sup.B j.sub.0 x.sub.0) (custom character mcustom character .sub.0.sup.B j.sub.0 j.sub.1) s.t.j = ( j.sub.0||j.sub.1). 7: if t.sub.j 1 {x.sub.0 = 0} then 8: P.sub.0 sets s.sub.j = L custom character corrcustom character .sub.0.sup.L 1. 9: else if t.sub.j 1 {x.sub.0 = 1} then 10: P.sub.0 sets s.sub.j = L custom character corrcustom character .sub.0.sup.L + 1. 11: else 12: P.sub.0 sets s.sub.j = L custom character corrcustom character .sub.0.sup.L. 13: end if 14: end for 15: 0 P 0 & P 1 invoke an instance of ( 4 1 ) - OT , where P 0 is the sender with inputs { s j } j and P.sub.1 is the receiver with input custom character mcustom character .sub.1.sup.B||x.sub.1 and learns custom character corrcustom character .sub.1.sup.L. 16: P.sub.0 & P.sub.1 invoke an instance of custom character .sub.MILL.sup.s with P.sub.0s input as 2.sup.s1a.sub.0.sup.0 and P.sub.1s input as a.sub.1.sup.0. For b {0, 1}, P.sub.b learns custom character ccustom character .sub.b.sup.B. 17: For b {0, 1}, P.sub.b invokes an instance of custom character .sub.B2A.sup.L (L = 2custom character ) with input custom character ccustom character .sub.b.sup.B and learns custom character dcustom character .sub.b.sup.L. 18: P.sub.b outputs custom character zcustom character .sub.b.sup.L = (custom character acustom character .sub.b.sup.L>> s) +custom character corrcustom character .sub.b.sup.L. 2custom character .sup.s + custom character dcustom character .sub.b.sup.L, b {0, 1}.

(121) 4.2.1 Protocol for truncation of custom character-bit integer. Let custom character be the functionality that takes arithmetic shares of a as input and returns arithmetic shares of a>>s as output. In this work, we give a protocol Algorithm 5 that realizes the functionality custom character correctly building on Corollary 4.2.

(122) Parties P.sub.0 & P.sub.1 first invoke an instance of custom character (where one party locally flips its share of ReLU(a)) to get boolean shares custom charactermcustom character.sub.b.sup.B of MSB(a). Using these shares, they use a

(123) ( 4 1 ) - O T 1
for calculating custom charactercorrcustom character.sub.b.sup.L, i.e., arithmetic shares of corr term in Corollary 4.2. Next, they use an instance of custom character.sub.MILL.sup.s to compute boolean shares of c=1{a.sub.0.sup.0+a.sub.1.sup.02.sup.s}. Finally, they compute arithmetic shares of c using a call to custom character.sub.B2A.sup.L (Algorithm 7).

(124) Correctness and Security. For any zcustom character.sub.L, MSB(z)=1{z.sub.ucustom character}, where z.sub.u is unsigned representation of z lifted to integers. First, note that Reconst.sup.B(custom charactermcustom character.sub.0.sup.B, custom charactermcustom character.sub.1.sup.B)=1Reconst.sup.B(custom characteracustom character.sub.0.sup.B, custom characteracustom character.sub.1.sup.B)=MSB(a) by correctness of custom character. Next, we show that Reconst.sup.L(custom charactercorrcustom character.sub.0.sup.L, custom charactercorrcustom character.sub.1.sup.L)=corr, as defined in Corollary 4.2. Let x.sub.b=MSB(custom characteracustom character.sub.b.sup.L) for b{0, 1}, and let j*=(custom charactermcustom character.sub.1.sup.Bx.sub.1). Then, t.sub.j*=(custom charactermcustom character.sub.0.sup.Bcustom charactermcustom character.sub.1.sup.B x.sub.0)(custom charactermcustom character.sub.0.sup.Bcustom charactermcustom character.sub.1.sup.Bx.sub.1)=(MSB(a)x.sub.0)(MSB(a)x.sub.1). Now, t.sub.j*=1 implies that we are in one of the first two cases of expression for corrwhich case we are in can be checked using x.sub.0 (steps 7 & 9). Now we can see that s.sub.j*=custom charactercorrcustom character.sub.0.sup.L+corr=custom charactercorrcustom character.sub.1.sup.L. Next, by correctness of custom character.sub.MILL.sup.s, c=Reconst.sup.B custom characterccustom character.sub.0.sup.B, custom characterccustom character.sub.1.sup.B)=1{a.sub.0.sup.0+a.sub.1.sup.02.sup.s}. That is, c=custom characterccustom character.sub.0.sup.Bcustom characterccustom character.sub.1.sup.B. Given boolean shares of c, step 17, creates arithmetic shares of the same using an instance of custom character.sub.B2A.sup.L. Since custom charactercorrcustom character.sub.0.sup.L is uniformly random, security of our protocol is easy to see in

(125) ( DReLU int , , ( 4 1 ) - OT , MILL s , B 2 A L ) - hybrid .

(126) Communication complexity. custom character involves a single call each to

(127) DReLU int , , ( 4 1 ) - OT , B 2 A L and MILL s .
Hence, communication required is <custom character+2+19custom character+communication for custom character.sub.MILL.sup.s that depends on parameters. For custom character=32 and s=12, our concrete communication is 4310 bits (using m=7 for .sub.MILL.sup.12 as well as .sub.MILL.sup.31 inside .sub.DReLU.sup.int,32) as opposed to 24064 bits for garbled circuits.

(128) 4.2.2 Protocol for division in ring. Let custom character.sub.Div.sup.ring,n,d be the functionality for division that takes arithmetic shares of a as input and returns arithmetic shares of rdiv(a, d) as output. Our protocol builds on our closed form expression from Theorem 4.1. We note that custom character-bit integers is a special case of custom character.sub.n and we use the same protocol for division of an element in custom character.sub.L by a positive integer.

(129) This protocol is similar to the previous protocol for truncation and uses the same logic to compute shares of corr term. The most non-trivial term to compute is C that involves three signed comparisons over custom character. We emulate these comparisons using calls to custom character.sub.DReLU.sup.int, where is large enough to ensure that there are no overflows or underflows. We can see that 2d+2A2d2 and hence, 3d+2Ad,A,A+d3d2. Hence, we set = log d. Now, with this value of , the term C can we re-written as (ReLU(Ad)1)+(ReLU(A)1)+(ReLU(A+d)1), which can be computed using three calls to custom character.sub.DReLU.sup.int, (Step 19) and custom character.sub.B2A.sup.n (Step 20) each. Finally, note that to compute C we need arithmetic shares of A over the ring custom character.sub., =2.sup.. And this requires shares of corr over the same ring. Hence, we compute shares of corr over both custom character.sub.n and custom character.sub. (Step 15). Due to space constraints, we describe the protocol formally in Appendix D. Table 3 provides theoretical and concrete communication numbers for division in both custom character.sub.L and custom character.sub.n, as well as a comparison with garbled circuits.

(130) 4.2.3 Truncation in rings with special structure. Truncation by s in general rings can be done by performing a division by d=2.sup.s. However, we can omit a call to custom character.sub.DReLU.sup.int, and custom character.sub.B2A.sup.n when the underlying ring and d satisfy a relation. Specifically, if we have 2.Math.n.sup.0d=2.sup.s, then A is always greater than equal to d, where n.sup.0, AZ are as defined in Theorem 4.1. Thus, the third comparison (Ad) in the expression of C from Theorem 4.1 can be omitted. Moreover, this reduces the value of needed and =log 4d suffices since 2dAd, A2d2.

(131) Our homomorphic encryption scheme requires n to be a prime of the form 2KN+1 (Section 2.2.4), where K is a positive integer and N8192 is a power-of-2. Thus, we have n.sup.0=n mod 2.sup.s=1 for 1s14. For all our benchmarks, s12 and we use this optimization for truncation in PIE.sub.HE.

5 Secure Inference

(132) We give an overview of all the layers that are computed securely to realize the task of secure neural network inference. Layers can be broken into two categorieslinear and non-linear. An inference algorithm simply consists of a sequence of layers of appropriate dimension connected to each other. Examples of linear layers include matrix multiplication, convolutions, Avgpool and batch normalization, while non-linear layers include ReLU, Maxpool, and Argmax.

(133) We are in the setting of secure inference where the model owner, say P.sub.0, holds the weights. When securely realizing each of these layers, we maintain the following invariant: Parties P.sub.0 and P.sub.1 begin with arithmetic shares of the input to the layer and after the protocol, end with arithmetic shares (over the same ring) of the output of the layer. This allows us to stitch protocols for arbitrary layers sequentially to obtain a secure computation protocol for any neural network comprising of these layers. For protocols in PIE.sub.OT, this arithmetic secret sharing is over custom character.sub.L; in PIE.sub.HE, the sharing is over custom character.sub.n, prime n.

(134) 5.1 Linear Layers

(135) 5.1.1 Fully connected layers and convolutions. A fully connected layer in a neural network is simply a product of two matricesthe matrix of weights and the matrix of activations of that layerof appropriate dimension. At a very high level, a convolutional layer applies a filter (usually of dimension ff for small integer f) to the input matrix by sliding across it and computing the sum of elementwise products of the filter with the input. Various parameters are associated with convolutionse.g. stride (a stride of 1 denotes that the filter slides across the larger input matrix beginning at every row and every column) and zero-padding (which indicates whether the matrix is padded with 0s to increase its dimension before applying the filter). When performing matrix multiplication or convolutions over fixed-point values, the values of the final matrix are scaled down appropriately so that it has the same scale as the inputs to the computation. We note that our values are in fixed-point with an associated scale s and have been encoded into appropriate size rings custom character.sub.L or custom character.sub.n as follows: a Real r is encoded as [r2.sup.s] mod k where k=L or n. Hence, to do faithful fixed-point arithmetic, we first compute the matrix multiplication or convolution over the ring (custom character.sub.L or custom character.sub.n) followed by truncation, i.e., division-by-2s of all the values. In PIE.sub.OT, multiplication and convolutions over the ring custom character.sub.L are done using oblivious transfer techniques and in PIE.sub.HE these are done over custom character.sub.n using homomorphic encryption techniques that we describe next followed by our truncation method.

(136) OT based computation. We note that OT-based techniques for multiplication are known [8, 24, 50] and we describe them briefly for completeness. First consider the simple case of secure multiplication of 2 elements a and b in custom character.sub.L where P.sub.0 knows a and P.sub.0 and P.sub.1 hold arithmetic shares of b. This can be done with custom character instances of

(137) ( 2 1 ) - COT + 1 2 .
Using this, multiplying two matrices Acustom character.sub.L.sup.M,N and Bcustom character.sub.L.sup.N,K such that P.sub.0 knows A and B is arithmetically secret shared requires MNKcustom character instances of

(138) ( 2 1 ) - COT + 1 2 .
This can be optimized by using the structured multiplications inside a matrix multiplication by combining all the COT sender messages when multiplying with the same element, reducing the complexity to NKcustom character instances of

(139) ( 2 1 ) - COT M ( + 1 ) 2 .
Finally, we reduce the task of secure convolutions to secure matrix multiplication similar to [44, 49, 60].

(140) HE based computation. PIE.sub.HE, uses techniques from Gazelle [42] and Delphi [48] to compute matrix multiplications and convolutions over a field custom character.sub.L (prime n), of appropriate size. At a high level, first, P.sub.1 sends an encryption of its arithmetic share to P.sub.0. Then, P.sub.0 homomorphically computes on this ciphertext using weights of the model (known to P.sub.0) to compute an encryption of the arithmetic share of the result and sends this back to P.sub.1. Hence, the communication only depends on the input and output size of the linear layer and is independent of the number of multiplications being performed. Homomorphic operations can have significantly high computational costto mitigate this, we build upon the output rotations method from [42] for performing convolutions, and reduce its number of homomorphic rotations. At a very high level, after performing convolutions homomorphically, ciphertexts are grouped, rotated in order to be correctly aligned, and then packed using addition. In our work, we divide the groups further into subgroups that are misaligned by the same offset. Hence the ciphertexts within a subgroup can first be added and the resulting ciphertext can then be aligned using a single rotation as opposed to c.sub.i/c.sub.n in [42] (where c.sub.i denotes the number of input channels and c.sub.n is the number of channels that fit in a single ciphertext). We refer the reader to Appendix E for details.

(141) Faithful truncation. To correctly emulate fixed-point arithmetic, the value encoded in the shares obtained from the above methods are divided-by-2s, where s is the scale used. For this we invoke custom character in PIE.sub.OT and custom character.sub.Div.sup.ring,n,2.sup.s in PIE.sub.HE for each value of the resulting matrix. With this, result of secure implementation of fixed-point multiplication and convolutions is bitwise equal to the corresponding cleartext execution. In contrast, many prior works on 2PC [48, 50] and 3PC [44, 49, 60] used a local truncation method for approximate truncation based on a result from [50]. Here, the result can be arbitrarily wrong with a (small) probability p and with probability 1p the result can be wrong in the last bit. Since p grows with the number of truncations, these probabilistic errors are problematic for large DNNs. Moreover, even if p is small, 1-bit errors can accumulate and the results of cleartext execution and secure execution can diverge; this is undesirable as it breaks correctness of 2PC.

(142) 5.1.2 Avgpool.sub.d. The function Avgpool.sub.d (a.sub.1, . . . , a.sub.d) over a pool of d elements a1, . . . , ad is defined to be the arithmetic mean of these d values. The protocol to compute this function works as follows: P.sub.0 and P.sub.1 begin with arithmetic shares (e.g. over custom character.sub.L in PIE.sub.OT) of a.sub.i, for all i[d]. They perform local addition to obtain shares of w=.sub.i=1d a.sub.i (i.e., P.sub.b computes custom characterwcustom character.sub.b.sup.L=.sub.i=1.sup.dcustom charactera.sub.icustom character.sub.b.sup.L). Then, parties invoke custom character.sub.Div.sup.ring,L,d on inputs custom characterwcustom character.sub.b.sup.L to obtain the desired output. Correctness and security follow in therein custom character.sub.Div.sup.ring,L,d-hybrid model. Here too, unlike prior works, our secure execution is bitwise equal to the cleartext version.

(143) 5.1.3 Batch Normalization. This layer takes as input vectors c, x, d of the same length, and outputs cx+d, where cx refers to the element-wise product of the vectors c and x. Moreover, c and d are a function of the mean and the variance of the training data set, and some parameters learnt during training. Hence, c and d are known to model owner, i.e., P.sub.0. This layer can be computed using techniques of secure multiplication.

(144) 5.2 Nonlinear Layers

(145) 5.2.1 ReLU. Note that ReLU(a)=a if a0, and 0 otherwise. Equivalently, ReLU(a)=ReLU(a).Math.a. Once we compute the boolean shares of ReLU(a) using a call to custom character we compute shares of ReLU(a) using a call to multiplexer functionality custom character.sub.MUX.sup.L (Section 2.2.3). We describe the protocol for ReLU(a) over custom character.sub.L formally in Algorithm 8, Appendix B (the case of Z.sub.n follows in a similar manner). For communication complexity, refer to Table 2 for comparison with garbled circuits and Appendix B for detailed discussion.

(146) 5.2.2 Maxpool.sub.d and Argmax.sub.d. The function Maxpool.sub.d (a.sub.1, . . . , a.sub.d) over d elements a.sub.1, . . . , a.sub.d is defined in the following way. Define gt(x,y)=z, where w=xy and z=x, if w>0 and z=y, if w0. Define z.sub.1=a.sub.1 and z.sub.i=gt(a.sub.i, z.sub.i1), recursively for all 2id. Now, Maxpool.sub.d (a.sub.1, . . . , a.sub.d)=z.sub.d.

(147) We now describe a protocol such that parties begin with arithmetic shares (over custom character.sub.L) of a.sub.i, for all i[d] and end the protocol with arithmetic shares (over custom character.sub.L) of Maxpool.sub.d (a.sub.1, . . . , a.sub.d). For simplicity, we describe how P.sub.0 and P.sub.1 can compute shares of z=gt(x,y) (beginning with the shares of x and y). It is easy to see then how they can compute Maxpool.sub.d. First, parties locally compute shares of w=xy (i.e., P.sub.b computes custom characterwcustom character.sub.b.sup.L=custom characterxcustom character.sub.b.sup.Lcustom characterycustom character.sub.b.sup.L, for b{0, 1}). Next, they invoke custom character with input custom characterwcustom character.sub.b.sup.L to learn output custom charactervcustom character.sub.b.sup.B. Now, they invoke custom character.sub.MUX.sup.L with input custom characterwcustom character.sub.b.sup.L and custom charactervcustom character.sub.b.sup.B to learn output custom charactertcustom character.sub.b.sup.L. Finally, parties' output custom characterzcustom character.sub.b.sup.L=custom characterycustom character.sub.b.sup.L+custom charactertcustom character.sub.b.sup.L. The correctness and security of the protocol follows in a straightforward manner. Computing Maxpool d is done using d1 invocations of the above sub-protocol in d1 sequential steps.

(148) Argmax.sub.d (a.sub.1, . . . , a.sub.d) is defined similar to Maxpool.sub.d (a.sub.1, . . . , a.sub.d), except that its output is an index i*s.t. a.sub.i*=Maxpool.sub.d (a.sub.1, . . . , a.sub.d). Argmax.sub.d can be computed securely similar to Maxpool.sub.d (a.sub.1, . . . , a.sub.d).

6 Implementation

(149) We implement our cryptographic protocols in a library PIE and integrate them into the CrypTFlow framework [1, 44] as a new cryptographic backend. CrypTFlow compiles high-level Tensor-Flow [3] inference code to secure computation protocols, that are then executed by its cryptographic backends. We modify the truncation behavior of CrypTFlow's float-to-fixed compiler, Athos, in support of faithful fixed-point arithmetic. We start by describing the implementation of our cryptographic library, followed by the modifications that we made to Athos.

(150) 6.1 Cryptographic Backend

(151) To implement our protocols, we build upon the

(152) ( 2 1 ) - COT
implementation from EMP [61] and extend it to

(153) ( k 1 ) - COT
using the protocol from [43]. Our linear-layer implementation using PIE.sub.HE is based on SEAL/Delphi [2, 57] and PIE.sub.OT is based on EMP. All our protocol implementations are multi-threaded.
Oblivious Transfer.

(154) ( k 1 ) - COT
uses AES.sub.256.sup.IC as a hash function in the random oracle model to mask the sender's messages in the OT extension protocol of [43] (There are two types of AES in MPC applicationsfixed key (FK) and ideal cipher (IC) [10, 34]. While the former runs key schedule only once and is more efficient, the latter generates a new key schedule for every invocation and is required in this application. It is parameterized by the key size, which is 256 in this case). We incorporated the optimizations from [32, 33] for AES key expansion and pipelining these AES.sub.256.sup.IC calls. This leads to roughly 6 improvement in the performance of AES.sub.256.sup.IC calls, considerably improving the overall execution time of

(155) 0 ( k 1 ) - COT
(e.g. 2.7 over LAN for

(156) ( 16 1 ) - COT 8 .

(157) Millionaires' protocol. Recall that m is a parameter in our protocol custom character. While we discussed the dependence of communication complexity on m in Section 3.1.2, here we discuss its influence on the computational cost. Our protocol makes calls to

(158) ( M 1 ) - OT 2
(after merging steps 9&10), where M=2.sup.m. Using OT extension techniques, generating an instance of

(159) ( M 1 ) - OT 2
requires 6 AES.sub.256.sup.IC and (M+1) AES.sub.256.sup.IC evaluations. Thus, the computational cost grows super-polynomial with m. We note that for custom character=32, even though communication is minimized for m=7, empirically we observe that m=4 gives us the best performance under both LAN and WAN settings (communication in this case is about 30% more than when m=7 but computation is 3 lower).

(160) Implementing linear layers in PIE.sub.HE. To implement the linear layers in PIE.sub.HE, we build upon the Delphi implementation [2, 48], that is in turn based on the SEAL library [57]. We implement the fully connected layers as in [48]. For convolution layers, we parallelize the code, employ modulus-switching [57] to reduce the ciphertext modulus (and hence ciphertext size), and implement the strided convolutions proposed in Gazelle [42] These optimizations resulted in significant performance improvement of convolution layers. E.g. for the first convolution layer of ResNet50, the runtime decreased from 306s to 18s in the LAN setting and communication decreased from 204 MiB to 76 MiB (Layer parameters: image size 230230, filter size 77, input channels 3, output channels 64, and stride size 22).

(161) 6.2 CrypTFlow Integration

(162) We integrate our protocols into the CrypTFlow framework [1, 44] as a new cryptographic backend. CrypTFlow's float-to-fixed compiler, Athos, outputs fixed-point DNNs that use 64-bit integers and sets an optimal scale using a validation set. CrypTFlow required 64-bits to ensure that the probability of local truncation errors in its protocols is small (Section 5.1.1). Since our protocols are correct and have no such errors, we extend Athos to set both the bitwidth and the scale optimally using the validation set. The bitwidth and scale leak information about the weights and this leakage is similar to the prior works on secure inference [42, 44, 47-50, 60].

(163) Implementing faithful truncations using custom character requires the parties to communicate. We implement the following peephole optimizations in Athos to reduce the cost of these truncation calls. Consider a DNN having a convolution layer followed by a ReLU layer. While truncation can be done immediately after the convolution, moving the truncation call to after the ReLU layer can reduce the cost of our protocol custom character. Since the values after ReLU are guaranteed to be all positive, the call to custom character within it (step 2 in Algorithm 5) now becomes redundant and can be omitted. Our optimization further accounts for operations that may occur between the convolutions and ReLU, say a matrix addition. Moving the truncation call from immediately after convolution to after ReLU means the activations flowing into the addition operation are now scaled by 2s, instead of the usual s. For the addition operation to then work correctly, we scale the other argument of addition by s as well. These optimizations are fully automatic and need no manual intervention.

7 Experiments

(164) We empirically validate the following claims: In Section 7.1, we show that our protocols for computing ReLU activations are more efficient than state-of-the-art garbled circuits-based implementations (Table 4). Additionally, our division protocols outperforms garbled circuits when computing average pool layers (Table 7). On the DNNs considered by prior work on secure inference, our protocols can evaluate the non-linear layers much more efficiently (Section 7.2). We show the first empirical evaluation of 2-party secure inference on ImageNet-scale benchmarks (Section 7.3). These results show the tradeoffs between OT and HE-based secure DNN inference (Table 6).

(165) We start with a description of our experimental setup and benchmarks, followed by the results.

(166) Experimental Setup. We ran our benchmarks in two network settings, namely, a LAN setting with both machines situated in West Europe, and transatlantic WAN setting with one of the machines in East US. The bandwidth between the machines is 377 MBps and 40 MBps in the LAN and the WAN setting respectively and the echo latency is 0.3 ms and 80 ms respectively. Each machine has commodity class hardware: 3.7 GHz Intel Xeon processor with 4 cores and 16 GBs of RAM.

(167) Our Benchmarks. We evaluate on the ImageNet-scale benchmarks considered by [44]: SqueezeNet [39], ResNet50 [36], and DenseNet121 [37]. To match the reported accuracies, we need 37-bit fixed-point numbers for ResNet50, whereas 32 bits suffice for DenseNet121 and SqueezeNet. Recall that our division protocols lead to correct secure executions and there is no accuracy loss in going from cleartext inference to secure inference. A brief summary of the complexity of these benchmarks is given in Appendix F.

(168) 7.1 Comparison with Garbled Circuits

(169) We compare with EMP-toolkit [61], the state-of-the-art library for Garbled Circuits (GC). FIG. 4 shows the improvement of our ReLU protocols over GC in both LAN and WAN settings.

(170) On the x-axis, which is in log-scale, the number of ReLUs range from 2.sup.0 to 2.sup.20. The histogram shows, using the right y-axis, the cumulative number of layers in our benchmarks (SqueezeNet, ResNet50, DenseNet121) which require the number of ReLU activations given on the x-axis. We observe that these DNNs have layers that compute between 2.sup.13 and 2.sup.20 ReLUs. For such layers, we observe (on the left y-axis) that our protocols are 2-25 faster than GCthe larger the layers the higher the speedups, and gains are larger in the WAN settings. Specifically, for WAN and >2.sup.17 ReLUs, the speedups are much higher than the LAN setting. Here, the cost of rounds is amortized over large layers and the communication cost is a large fraction of the total runtime. Note that our implementations perform load-balancing to leverage full-duplex TCP.

(171) Next, we compare the time taken by GC and our protocols in computing the ReLU activations of our benchmarks in Table 4.

(172) TABLE-US-00009 TABLE 4 Performance comparison of Garbled Circuits with our protocols for computing ReLU layers. Runtimes are in seconds and communication numbers are in GiB. Garbled Circuits Our Protocols Benchmark LAN WAN Comm LAN WAN Comm (a) over custom character SqueezeNet 26.4 265.6 7.63 3.5 33.3 1.15 ResNet50 136.5 1285.2 39.19 16.4 69.4 5.23 DenseNet121 199.6 1849.3 56.57 24.8 118.7 8.21 (b) over custom character .sub.n SqueezeNet 51.7 525.8 16.06 5.6 50.4 1.77 ResNet50 267.5 2589.7 84.02 28.0 124.0 8.55 DenseNet121 383.5 3686.2 118.98 41.9 256.0 12.64

(173) Our protocol over custom character.sub.L is up to 8 and 18 faster than GC in the LAN and WAN settings respectively, while it is 7 more communication efficient. As expected, our protocol over custom character.sub.n has even better gains over GC. Specifically, it is up to 9 and 21 faster in the LAN and WAN settings respectively, and has 9 less communication.

(174) We also performed a similar comparison of our protocols with GC for the Avgpool layers of our benchmarks, and saw up to 51 reduction in runtime and 41 reduction in communication. We report the concrete performance numbers and discuss the results in more detail in Appendix G.

(175) 7.2 Comparison with State-of-the-Art

(176) In this section, we compare with Gazelle [42] and Delphi [48], which are the current state-of-the-art for 2-party secure DNN inference that outperform [13, 14, 18, 20, 23, 30, 47, 55]. They use garbled circuits for implementing their non-linear layers, and we show that with our protocols, the time taken to evaluate the non-linear layers of their benchmarks can be decreased significantly.

(177) For a fair evaluation, we demonstrate these improvements on the benchmarks of Delphi [48], i.e., the MiniONN (CIFAR-10) [47] and ResNet32 (CIFAR-100) DNNs (as opposed to the ImageNet-scale benchmarks for which their systems have not been optimized). For these benchmarks, Gazelle and Delphi have the same total time and communication; we refer to them as GD. Since Gazelle's choice of parameters was insecure, which was later fixed in Delphi, we use Delphi's implementation for comparing with them.)

(178) In Table 5, we report the performance of GD for evaluating the linear and non linear components of MiniONN and ResNet32 separately, along with the performance of our protocols for the same non-linear computation (Our non-linear time includes the cost of truncation).

(179) TABLE-US-00010 TABLE 5 Performance comparison of our protocols for non-linear layers with Gazelle/Delphi (GD). Runtimes are in seconds and communication numbers are in GiB. Benchmark Computation LAN WAN Comm MiniONN GD linear 10.7 11.4 0.02 GD Non-Linear 30.2 124.0 3.15 Our Non-Linear 1.0 14.5 0.28 ResNet32 GD Linear 15.9 22.7 0.07 GD Non-Linear 52.9 211.3 5.51 Our Non-Linear 2.4 45.3 0.59

(180) The table shows that the time to evaluate non-linear layers is the bulk of the total time and our protocols are 4-30 faster in evaluating the non-linear layers. Also note that we reduce the communication by 11 on MiniONN, and require around 9 less communication on ResNet32.

(181) 7.3 Evaluation on Practical DNNs

(182) With all our protocols and implementation optimizations in place, we demonstrate the scalability of PIE by efficiently running ImageNet-scale secure inference. Table 6 shows that both our backends, PIE.sub.OT and PIE.sub.HE, are efficient enough to evaluate SqueezeNet in under a minute and scale to ResNet50 and DenseNet121.

(183) TABLE-US-00011 TABLE 6 Performance of PIE on ImageNet-scale benchmarks. Runtimes are in seconds and communication in GiB. Benchmark Protocol LAN WAN Comm SqueezeNet PIE.sub.OT 44.3 293.6 26.07 PIE.sub.HE 59.2 156.6 5.27 ResNet50 PIE.sub.OT 619.4 3611.6 370.84 PIE.sub.HE 545.8 936.0 32.43 DenseNet121 PIE.sub.OT 371.4 2257.7 217.19 PIE.sub.HE 463.2 1124.7 35.56

(184) In the LAN setting, for both SqueezeNet and DenseNet121, PIE.sub.OT performs better than PIE.sub.HE by at least 20% owing to the higher compute in the latter. However, the quadratic growth of communication with bitlength in the linear-layers of PIE.sub.OT can easily drown this difference if we go to higher bitlengths. Because ResNet50, requires 37-bits (compared to 32 in SqueezeNet and DenseNet121) to preserve accuracy, PIE.sub.HE outperforms PIE.sub.OT in both LAN and WAN settings. In general for WAN settings where communication becomes the major performance bottleneck, PIE.sub.HE performs better than PIE.sub.OT: 2 for SqueezeNet and DenseNet121 and 4 for ResNet50. Overall, with PIE, we could evaluate all the 3 benchmarks within 10 minutes on LAN and 20 minutes on WAN. Since PIE supports both PIE.sub.OT and PIE.sub.HE, one can choose a specific backend depending on the network statistics [18, 52] to get the best secure inference latency. To the best of our knowledge, no prior system provides this support for OT and HE-based secure DNN inference.

8 Conclusion

(185) We have presented secure, efficient, and correct implementations of practical 2-party DNN inference that outperform prior work in both latency and scale. Like all prior work on 2PC for secure DNN inference, PIE only considers semi-honest adversaries.

9. Computing System

(186) Because the principles described herein are performed in the context of a computing system, some introductory discussion of a computing system will be described with respect to FIG. 4. Computing systems are now increasingly taking a wide variety of forms. Computing systems may, for example, be handheld devices, appliances, laptop computers, desktop computers, mainframes, distributed computing systems, data centers, or even devices that have not conventionally been considered a computing system, such as wearables (e.g., glasses). In this description and in the claims, the term computing system is defined broadly as including any device or system (or a combination thereof) that includes at least one physical and tangible processor, and a physical and tangible memory capable of having thereon computer-executable instructions that may be executed by a processor. The memory may take any form and may depend on the nature and form of the computing system. A computing system may be distributed over a network environment and may include multiple constituent computing systems.

(187) As illustrated in FIG. 4, in its most basic configuration, a computing system 400 includes at least one hardware processing unit 402 and memory 404. The processing unit 402 includes a general-purpose processor. Although not required, the processing unit 402 may also include a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), or any other specialized circuit. In one embodiment, the memory 404 includes a physical system memory. That physical system memory may be volatile, non-volatile, or some combination of the two. In a second embodiment, the memory is non-volatile mass storage such as physical storage media. If the computing system is distributed, the processing, memory and/or storage capability may be distributed as well.

(188) The computing system 400 also has thereon multiple structures often referred to as an executable component. For instance, the memory 404 of the computing system 400 is illustrated as including executable component 406. The term executable component is the name for a structure that is well understood to one of ordinary skill in the art in the field of computing as being a structure that can be software, hardware, or a combination thereof. For instance, when implemented in software, one of ordinary skill in the art would understand that the structure of an executable component may include software objects, routines, methods (and so forth) that may be executed on the computing system. Such an executable component exists in the heap of a computing system, in computer-readable storage media, or a combination.

(189) One of ordinary skill in the art will recognize that the structure of the executable component exists on a computer-readable medium such that, when interpreted by one or more processors of a computing system (e.g., by a processor thread), the computing system is caused to perform a function. Such structure may be computer readable directly by the processors (as is the case if the executable component were binary). Alternatively, the structure may be structured to be interpretable and/or compiled (whether in a single stage or in multiple stages) so as to generate such binary that is directly interpretable by the processors. Such an understanding of example structures of an executable component is well within the understanding of one of ordinary skill in the art of computing when using the term executable component.

(190) The term executable component is also well understood by one of ordinary skill as including structures, such as hard coded or hard wired logic gates, that are implemented exclusively or near-exclusively in hardware, such as within a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), or any other specialized circuit. Accordingly, the term executable component is a term for a structure that is well understood by those of ordinary skill in the art of computing, whether implemented in software, hardware, or a combination. In this description, the terms component, agent, manager, service, engine, module, virtual machine or the like may also be used. As used in this description and in the case, these terms (whether expressed with or without a modifying clause) are also intended to be synonymous with the term executable component, and thus also have a structure that is well understood by those of ordinary skill in the art of computing.

(191) In the description that follows, embodiments are described with reference to acts that are performed by one or more computing systems. If such acts are implemented in software, one or more processors (of the associated computing system that performs the act) direct the operation of the computing system in response to having executed computer-executable instructions that constitute an executable component. For example, such computer-executable instructions may be embodied on one or more computer-readable media that form a computer program product. An example of such an operation involves the manipulation of data. If such acts are implemented exclusively or near-exclusively in hardware, such as within a FPGA or an ASIC, the computer-executable instructions may be hard-coded or hard-wired logic gates. The computer-executable instructions (and the manipulated data) may be stored in the memory 404 of the computing system 400. Computing system 400 may also contain communication channels 408 that allow the computing system 400 to communicate with other computing systems over, for example, network 410.

(192) While not all computing systems require a user interface, in some embodiments, the computing system 400 includes a user interface system 412 for use in interfacing with a user. The user interface system 412 may include output mechanisms 412A as well as input mechanisms 412B. The principles described herein are not limited to the precise output mechanisms 412A or input mechanisms 412B as such will depend on the nature of the device. However, output mechanisms 412A might include, for instance, speakers, displays, tactile output, virtual or augmented reality, holograms and so forth. Examples of input mechanisms 412B might include, for instance, microphones, touchscreens, virtual or augmented reality, holograms, cameras, keyboards, mouse or other pointer input, sensors of any type, and so forth.

(193) Embodiments described herein may comprise or utilize a special-purpose or general-purpose computing system including computer hardware, such as, for example, one or more processors and system memory, as discussed in greater detail below. Embodiments described herein also include physical and other computer-readable media for carrying or storing computer-executable instructions and/or data structures. Such computer-readable media can be any available media that can be accessed by a general-purpose or special-purpose computing system. Computer-readable media that store computer-executable instructions are physical storage media. Computer-readable media that carry computer-executable instructions are transmission media. Thus, by way of example, and not limitation, embodiments of the invention can comprise at least two distinctly different kinds of computer-readable media: storage media and transmission media.

(194) Computer-readable storage media includes RAM, ROM, EEPROM, CD-ROM, or other optical disk storage, magnetic disk storage, or other magnetic storage devices, or any other physical and tangible storage medium which can be used to store desired program code means in the form of computer-executable instructions or data structures and which can be accessed by a general-purpose or special-purpose computing system.

(195) A network is defined as one or more data links that enable the transport of electronic data between computing systems and/or modules and/or other electronic devices. When information is transferred or provided over a network or another communications connection (either hardwired, wireless, or a combination of hardwired or wireless) to a computing system, the computing system properly views the connection as a transmission medium. Transmission media can include a network and/or data links which can be used to carry desired program code means in the form of computer-executable instructions or data structures and which can be accessed by a general-purpose or special-purpose computing system. Combinations of the above should also be included within the scope of computer-readable media.

(196) Further, upon reaching various computing system components, program code means in the form of computer-executable instructions or data structures can be transferred automatically from transmission media to storage media (or vice versa). For example, computer-executable instructions or data structures received over a network or data link can be buffered in RANI within a network interface module (e.g., a NIC), and then be eventually transferred to computing system RANI and/or to less volatile storage media at a computing system. Thus, it should be understood that storage media can be included in computing system components that also (or even primarily) utilize transmission media.

(197) Computer-executable instructions comprise, for example, instructions and data which, when executed at a processor, cause a general-purpose computing system, special-purpose computing system, or special-purpose processing device to perform a certain function or group of functions. Alternatively, or in addition, the computer-executable instructions may configure the computing system to perform a certain function or group of functions. The computer executable instructions may be, for example, binaries or even instructions that undergo some translation (such as compilation) before direct execution by the processors, such as intermediate format instructions such as assembly language, or even source code.

(198) Although the subject matter has been described in language specific to structural features and/or methodological acts, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the described features or acts described above. Rather, the described features and acts are disclosed as example forms of implementing the claims.

(199) Those skilled in the art will appreciate that the invention may be practiced in network computing environments with many types of computing system configurations, including, personal computers, desktop computers, laptop computers, message processors, hand-held devices, multi-processor systems, microprocessor-based or programmable consumer electronics, network PCs, minicomputers, mainframe computers, mobile telephones, PDAs, pagers, routers, switches, datacenters, wearables (such as glasses) and the like. The invention may also be practiced in distributed system environments where local and remote computing system, which are linked (either by hardwired data links, wireless data links, or by a combination of hardwired and wireless data links) through a network, both perform tasks. In a distributed system environment, program modules may be located in both local and remote memory storage devices.

(200) Those skilled in the art will also appreciate that the invention may be practiced in a cloud computing environment. Cloud computing environments may be distributed, although this is not required. When distributed, cloud computing environments may be distributed internationally within an organization and/or have components possessed across multiple organizations. In this description and the following claims, cloud computing is defined as a model for enabling on-demand network access to a shared pool of configurable computing resources (e.g., networks, servers, storage, applications, and services). The definition of cloud computing is not limited to any of the other numerous advantages that can be obtained from such a model when properly deployed.

(201) For the processes and methods disclosed herein, the operations performed in the processes and methods may be implemented in differing order. Furthermore, the outlined operations are only provided as examples, and some of the operations may be optional, combined into fewer steps and operations, supplemented with further operations, or expanded into additional operations without detracting from the essence of the disclosed embodiments.

10. Appendix

(202) A. Supporting Protocols

(203) Here, we describe supporting protocols that our main protocols rely on.

(204) A.1 Protocol for Regular custom character.sub.and

(205) Regular custom character.sub.AND can be realized using bit-triples [8], which are of the form (custom characterdcustom character).sub.b.sup.B, custom characterecustom character.sub.b.sup.B, custom characterfcustom character.sub.b.sup.B), where b{0, 1} and de=f. Using an instance of

(206) ( 16 1 ) - OT 2 ,
the parties can generate two bit-triples. We describe this protocol for generating the first triple, and from there, it will be easy to see how to also generate the second one. The parties start by sampling random shares

(207) .Math. d .Math. b B , .Math. e .Math. b B $ { 0 , 1 } for b { 0 , 1 } .
P.sub.1 sets the first two bits of its input to

(208) ( 16 1 ) - O T 2 ,
as custom characterdcustom character.sub.1.sup.Bcustom characterecustom character.sub.1.sup.B, while the other two bits are used for the second triple. P.sub.0 samples a random bit r and sets its input messages to

(209) ( 16 1 ) - OT 2
as follows: for the i-th message, where i{0, 1}.sup.4, P.sub.0 uses the first two bits i.sub.1i.sub.2 of i to compute r((i.sub.1custom characterdcustom character.sub.0.sup.B(i.sub.2custom characterecustom character.sub.0.sup.B)), and sets it as the first bit of the message, while reserving the second bit for the other triple. Finally, P.sub.0 sets custom characterfcustom character.sub.0.sup.B=r, and P.sub.1 sets the first bit of the output of

(210) ( 16 1 ) - O T 2 as .Math. f .Math. 1 B .
Correctness can be seen by noting that custom characterfcustom character.sub.1.sup.B=custom characterfcustom character.sub.0.sup.B(de), and since custom characterfcustom character.sub.0.sup.B is uniformly random, security follows directly in the

(211) ( 16 1 ) - OT 2 - hybrid .

(212) The communication of this protocol is the same as that of

(213) 0 ( 16 1 ) - O T 2 ,
which is 2+16.Math.2 bits. Since we generate two bit-triples using this protocol, the amortized cost per triple is +16 bits, which is 144 for =128.
A.2 Protocol for Correlated custom character.sub.AND

(214) Correlated triples are two sets of bit triples (custom characterdcustom character.sub.b.sup.B, custom characterecustom character.sub.b.sup.B, custom characterfcustom character.sub.b.sup.B) and (custom characterdcustom character.sub.b.sup.B), custom characterecustom character.sub.b.sup.B, custom characterfcustom character.sub.b.sup.B), for b{0, 1}, such that e=e, de=f, and de=f. The protocol from Appendix A.1 used a

(215) ( 16 1 ) - O T 2
invocation to generate two regular triples, where the 4 bits of P.sub.1's input were its shares of d, e, d, and e. However, when generating correlated triples, we can instead use an instance of

(216) ( 8 1 ) - O T 2
because e=e, and thus, 3 bits suffice to represent P.sub.1's input. Correctness and security follow in a similar way as in the case of regular custom character.sub.AND (see Appendix A.1).

(217) The communication of this protocol is equal to that of

(218) ( 8 1 ) - O T 2 ,
which costs 2+8.Math.2 bits. Thus, we get an amortized communication of +8 bits per correlated triple.
A.3 Protocol for Multiplexer

(219) We describe our protocol for realizing custom character.sub.MUX.sup.2 in Algorithm 6. First we argue correctness. Let c=Reconst.sup.B(custom characterccustom character.sub.0.sup.B, custom characterccustom character.sub.1.sup.B)=custom characterccustom character.sub.0.sup.Bcustom characterccustom character.sub.1.sup.B. By correctness of

(220) ( 2 1 ) - O T ,
x.sub.1=r.sub.0+c.Math.custom characteracustom character.sub.0.sup.n. Similarly, x.sub.0=r.sub.1+c.Math.custom characteracustom character.sub.1.sup.n. Hence, Reconst.sup.n (custom characterzcustom character.sub.0.sup.n, custom characteracustom character.sub.1.sup.n)=z.sub.0+z.sub.1=c.Math.a. Security trivially follows in

(221) ( 2 1 ) - O T - hybrid .
Communication complexity is 2(+).

(222) TABLE-US-00012 Algorithm 6 Multiplexer, .sub.MUX.sup.n: Input: For b {0, 1}, P.sub.b holds custom character acustom character .sub.b.sup.n and custom character ccustom character .sub.b.sup.B. Output: For b {0, 1}, P.sub.b learns custom character zcustom character .sub.b.sup.n s.t. z = a if c = 1, else z = 0. 1: For b { 0 , 1 } , P b picks r b $ n . 2: P.sub.0 sets s.sub.0, s.sub.1 as follows: If custom character ccustom character .sub.0.sup.B= 0, (s.sub.0, s.sub.1) = (r.sub.0, r.sub.0 + custom character acustom character .sub.0.sup.n ). Else, (s.sub.0, s.sub.1) = (r.sub.0+custom character acustom character .sub.0.sup.n, r.sub.0). 3: P.sub.0 & P.sub.1 invoke an instance of ( 2 1 ) - OT where P.sub.0 is the sender with inputs (s.sub.0, s.sub.1) and P.sub.1 is the receiver with input custom character ccustom character .sub.1.sup.B. Let P.sub.1s output be x.sub.1. 4: P.sub.1 sets t.sub.0, t.sub.1 as follows: If custom character ccustom character .sub.1.sup.B = 0, (t.sub.0, t.sub.1) = (r.sub.1, r.sub.1 + custom character acustom character .sub.1.sup.n ).Else, (t.sub.0, t.sub.1) =(r.sub.1 + custom character acustom character .sub.1.sup.n, r.sub.1). 5: P.sub.0 & P.sub.1 invoke an instance of ( 2 1 ) - OT where P.sub.1 is the sender with inputs (t.sub.0, t.sub.1) and P.sub.0 is the receiver with input custom character ccustom character .sub.0.sup.B. Let P.sub.0s output be x.sub.0. 6: For b {0, 1}, P.sub.b outputs custom character zcustom character .sub.b.sup.n = r.sub.b + x.sub.b.
A.4 Protocol for B2A

(223) We describe our protocol for realizing custom character.sub.B2A.sup.n formally in Algorithm 7. For correctness, we need to show that d=Reconst.sup.L (custom characterdcustom character.sub.0.sup.n, custom characterdcustom character.sub.1.sup.n)=custom characterccustom character.sub.0.sup.B+custom characterccustom character.sub.1.sup.B2custom characterccustom character.sub.0.sup.Bcustom character ccustom character.sub.1.sup.B. By correctness of

(224) ( 2 1 ) - C O T , y 1 = x + .Math. c .Math. 0 B .Math. c .Math. 1 B .
Using this, custom characterdcustom character.sub.0.sup.n=custom characterccustom character.sub.0.sup.B+2x and custom characterdcustom character.sub.1.sup.n=custom characterccustom character.sub.1.sup.B2x2custom characterccustom character.sub.0.sup.Bcustom characterccustom character.sub.1.sup.B. Security follows from the security of

(225) 0 ( 2 1 ) - C O T
and communication required is + bits.

(226) TABLE-US-00013 Algorithm 7 Boolean to Arithmetic, .sub.B2A.sup.n: Input: P.sub.0, P.sub.1 hold custom character ccustom character .sub.0.sup.B and custom character ccustom character .sub.1.sup.B, respectively, where c {0, 1}. Output: P.sub.0, P.sub.1 learn custom character dcustom character .sub.0.sup.n and custom character dcustom character .sub.1.sup.n, respectively, s.t. d = c. 1: P 0 & P 1 invoke an instance of ( 2 1 ) - C OT where P 0 is the sender with correlation function f (x) = x + custom character ccustom character .sub.0.sup.B and P.sub.1 is the receiver with input custom character ccustom character .sub.1.sup.B. Party P.sub.0 learns x and sets y.sub.0 = n x and P.sub.1 learns y.sub.1. 2: For b {0, 1}, P.sub.b computes custom character dcustom character .sub.b.sup.n = custom character ccustom character .sub.b.sup.B 2.Math.y.sub.b.
B Protocol for ReLU

(227) We describe our ReLU protocol for the case where the input and output shares are over custom character.sub.L in Algorithm 8, and note that the case of custom character.sub.n follows similarly. It is easy to see that the correctness and security of the protocol follow in the (custom character, custom character.sub.MUX.sup.L)-hybrid.

(228) Communication complexity. We first look at the complexity of custom character, which involves a call to custom character, and custom character.sub.MUX.sup.L. custom character, has the same communication as custom character, which requires (custom character1)+13(custom character1)222 bits if we assume m=4 and m|(custom character1), and exclude optimization (3.1.1) in the general expression from Section 3.1.2. custom character.sub.MUX.sup.L incurs a cost of 2+4custom character bits, bringing the total cost to custom character+17custom character35 bits, which can be rewritten as <ltcustom character+18custom character. We get our best communication for custom character=32 (with all the optimizations) by taking m=7 for the .sub.MILL.sup.32, invocation inside .sub.DReLU.sup.int,32, which gives us a total communication of 3298 bits.

(229) Now, we look at the complexity of .sub.ReLU.sup.ring,n, which makes calls to custom character.sub.DReLU.sup.ring,n and custom character.sub.MUX.sup.n). The cost of custom character.sub.DReLU.sup.ring,n is 2+4 bits for

(230) ( 4 1 ) - O T 1 ,
plus (3/2) (+1)+27(+1)444 bits for 2 invocations of custom character.sub.MILL.sup.n+1, where P.sub.1's input is the same in both invocations and the same assumptions are made as for the expression of custom character above. The cost of custom character.sub.MUX.sup.n is 2+4 bits, and thus, the total cost is (3/2) (+1)+3113, which can be rewritten as <(3/2) (+1)+31. Concretely, we get the best communication for =32 by taking m=7 for the millionaire invocations, getting a total communication of 5288 bits.

(231) TABLE-US-00014 Algorithm 8custom character -bit integer ReLU,custom character : Input: P.sub.0, P.sub.1 holdcustom character acustom character .sub.0.sup.L andcustom character acustom character L.sub.1.sup.L , respectively. Output: P.sub.0, P.sub.1 getcustom character ReLU(a)custom character .sub.0.sup.L andcustom character ReLU(a)custom character .sub.1.sup.L. 1: For b {0, 1}, P.sub.b invokescustom character with inputcustom character acustom character .sub.b.sup.L to learn outputcustom character ycustom character .sub.b.sup.B. 2: For b {0, 1}, PP.sub.b invokescustom character .sub.MUX.sup.L with inputscustom character acustom character .sub.b.sup.L andcustom character ycustom character .sub.b.sup.B to learncustom character zcustom character .sub.b.sup.L and sets custom character ReLU(a)custom character .sub.b.sup.L =custom character zcustom character .sub.b.sup.L.
C Proof of Division Theorem

(232) Here, we prove Theorem 4.1.

(233) From Equation 2, we can write rdiv(custom characteracustom character.sub.i.sup.n, d) as:

(234) rdiv ( .Math. a .Math. i n , d ) = n idiv ( a i - 1 { a i n } .Math. n , d ) = n idiv ( a i 1 .Math. d + a i 0 - 1 { a i n } .Math. ( n 1 .Math. d + n 0 ) , d ) = n a i 1 - 1 { a i n } .Math. n 1 + idiv ( a i 0 - 1 { a i n } .Math. n 0 , d ) , ( 3 )
for i{0, 1}. a.sub.u can be expressed as a.sub.u=a.sub.0+a.sub.1w.Math.n, where the wrap-bit w=1{a.sub.0+a.sub.1n}. We can rewrite this as:

(235) a u = a 0 + a 1 - w .Math. n = ( a 0 1 + a 1 1 - w .Math. n 1 ) .Math. d + ( a 0 0 + a 1 0 - w .Math. n 0 ) = ( a 0 1 + a 1 1 - w .Math. n 1 + k ) .Math. d + ( a 0 0 + a 1 0 - w .Math. n 0 - k .Math. d ) , ( 4 )
for some integer k such that 0a.sub.0.sup.0+a.sub.1.sup.0w.Math.n.sup.0k.Math.d<d. Similar to Equation 3 and from Equation 4, we can write rdiv(a, d) as:

(236) rdiv ( a , d ) = n a 0 1 + a 1 1 - w .Math. n 1 + k - 1 { a n } .Math. n 1 + idiv ( a 0 0 + a 1 0 - w .Math. n 0 - k .Math. d - 1 { a n } .Math. n 0 , d ) = n a 0 1 + a 1 1 - w .Math. n 1 - 1 { a n } .Math. n 1 + idiv ( a 0 0 + a 1 0 - w .Math. n 0 - 1 { a n } .Math. n 0 , d ) . ( 5 )
From Equations 3 and 5, we have the following correction term:

(237) c = n rdiv ( a , d ) - rdiv ( .Math. a .Math. 0 n , d ) - rdiv ( .Math. a .Math. 1 n , d ) = n ( 1 { a 0 n } + 1 { a 1 n } - w - 1 { a n } ) .Math. n 1 + idiv ( a 0 0 + a 1 0 - w .Math. n 0 - 1 { a n } .Math. n 0 , d ) - ( idiv ( a 0 0 - 1 { a 0 n } .Math. n 0 , d ) + idiv ( a 1 0 - 1 { a 1 n } .Math. n 0 , d ) ) . ( 6 ) = n c 1 .Math. n 1 + c 0 - B ( 7 )
Let A.sub.ii=idiv(a.sub.0.sup.0+a.sub.1.sup.0i.Math.n.sup.0, d). Then the values of the correction terms c.sup.1 and c.sup.0 are as summarized in the following table:

(238) TABLE-US-00015 # 1 (a.sub.0 n) 1 (a.sub.1 n) 1 (a.sub.u n) w c.sup.1 c.sup.0 1 0 0 0 0 0 A.sub.0 2 0 0 1 0 1 A.sub.1 3 0 1 0 1 0 A.sub.1 4 0 1 1 0 0 A.sub.1 5 1 0 0 1 0 A.sub.1 6 1 0 1 0 0 A.sub.1 7 1 1 0 1 1 A.sub.1 8 1 1 1 1 0 A.sub.2

(239) From the table, we have c.sup.1=corr and can rewrite the correction term as c=.sub.n corr.Math.n.sup.1+c.sup.0B. Thus, adding corr.Math.n.sup.1B mod n to rdiv(custom characteracustom character.sub.0.sup.n, d)+rdiv(custom characteracustom character.sub.1.sup.n, d) accounts for all the correction terms except c.sub.0 mod n.

(240) Now all that remains to be proven is that c.sup.0=1C. Let C.sub.0=1{A<d}, C.sub.1=1{A<0}, and C.sub.2=1{A<d}. Then, we have C=C.sub.0+C.sub.1+C.sub.2. Note from the theorem statement that A=a.sup.0.sub.0+a.sub.1.sup.0 and A=a.sub.0.sup.0+a.sub.1.sup.02.Math.n.sup.0 for the cases corresponding to rows 1 and 8 respectively from the table, while A=a.sub.0.sup.0+a.sub.1.sup.0n.sup.0 for the rest of cases. Thus, it can be herein seen that c.sup.0=idiv(A, d). Also note that 2.Math.d+2A2.Math.d2, implying that the range of c.sup.0 is {2, 1, 0, 1}. Now we look at each value assumed by c.sup.0 separately as follows: c.sup.0=2: In this case, we have (A<d), implying C.sub.0=C.sub.1=C.sub.2=1, and 1C=2. c.sup.0=1: In this case, we have (dA<0), implying C.sub.0=C.sub.1=1, C.sub.2=0 and 1C=1. c.sup.0=0: In this case, we have (0A<d), implying C.sub.0=1, C.sub.1=C.sub.2=0 and 1C=0. c.sup.0=1: In this case, we have (dA), implying C.sub.0=C.sub.1=C.sub.2=0 and 1C=1.
Thus, c=.sub.n corr.Math.n.sup.1+(1C)B=.sub.n rdiv(a, d)rdiv(custom characteracustom character.sub.0.sup.n, d)rdiv(custom characteracustom character.sub.1.sup.n, d).
D Protocol for General Division

(241) We describe our protocol for general division formally in Algorithm 9. As discussed in Section 4.2.2, our protocol builds on Theorem 4.1 and we compute the various sub-terms securely using our new protocols. Let =log d. We compute the shares of corr over both custom character.sub.n and custom character.sub. (Step 15). We write the term C as (ReLU(Ad)1)+(ReLU(A)1)+(ReLU(A+d)1), which can be computed using three calls to custom character.sub.DReLU.sup.int, (Step 19) and custom character.sub.B2A.sup.n (Step 20) each.

(242) TABLE-US-00016 Algorithm 9 Integer ring division, .sub.DIV.sup.ring,n,d: Input: For b {0, 1}, P.sub.b holds custom character acustom character .sub.b.sup.n, where a custom character n. Output: For b {0, 1}, P.sub.b learns custom character zcustom character .sub.b.sup.n s.t. z = rdiv(a, d). 1: For b {0, 1}, let a.sub.b, a.sub.b.sup.0, a.sub.b.sup.1 custom character and n.sup.0, n.sup.1, n custom character be as defined in Theorem 4.1. Let = log(n), = log 6d, and = 2.sup.. 2: For b {0, 1}, P.sub.b invokescustom character .sub.DReLU.sup.ring,n with input custom character acustom character .sub.b.sup.n to learn output custom character acustom character .sub.b.sup.B. Party P.sub.b sets custom character mcustom character .sub.b.sup.B = custom character custom character .sub.b.sup.B b. 3: For b {0, 1}, P.sub.b sets x.sub.b = 1{custom character custom character .sub.b.sup.B n}. 4: P 0 samples .Math. corr .Math. 0 n $ n and .Math. corr .Math. 0 $ . 5: for j = {00, 01, 10, 11} do 6: P.sub.0 computes t.sub.j = (custom character mcustom character .sub.0.sup.B j.sub.0 x.sub.0) (custom character mcustom character .sub.0.sup.B j.sub.0 j.sub.1) s.t.j = (j.sub.0||j.sub.1). 7: if t.sub.j 1{x.sub.0 = 0} then 8: P.sub.0 sets s.sub.j =.sub.n custom character corrcustom character .sub.0.sup.n 1 and r.sub.j =.sub. custom character corrcustom character .sub.0.sup. 1. 9: else if t.sub.j 1{x.sub.0 = 1} then 10: P.sub.0 sets s.sub.j =.sub.n custom character corrcustom character .sub.0.sup.n + 1 and r.sub.j =.sub. custom character corrcustom character .sub.0.sup. + 1. 11: else 12: P.sub.0 sets s.sub.j =.sub.n custom character corrcustom character .sub.0.sup.n and r.sub.j =.sub. custom character corrcustom character .sub.0.sup.. 13: end if 14: end for 15: P 0 & P 1 invoke an instance of ( 4 1 ) - O T + 8 where P 0 is the sender with inputs { s j || r j } j and P.sub.1 is the receiver with inputcustom character mcustom character .sub.1.sup.B||x.sub.1. P.sub.1 sets its output ascustom character corrcustom character .sub.1.sup.n||custom character corrcustom character .sub.1.sup.. 16: For b {0, 1}, P.sub.b setscustom character Acustom character .sub.b.sup. =.sub. a.sub.b.sup.0 (x.sub.b custom character corrcustom character .sub.b.sup.) .Math. n.sup.0. 17: For b {0, 1}, P.sub.b setscustom character A.sub.0custom character .sub.b.sup. =.sub.custom character Acustom character .sub.b.sup. b .Math. d,custom character A.sub.1custom character .sub.b.sup. =custom character Acustom character .sub.b.sup. ,andcustom character A.sub.2custom character .sub.b.sup. =.sub.custom character Acustom character .sub.b.sup.+ b .Math. d. 18: for j = {0, 1, 2} do 19: For b {0, 1}, P.sub.b invokescustom character .sub.DReLU.sup.int, with inputcustom character A.sub.jcustom character .sub.b.sup. to learn outputcustom character .sub.jcustom character .sub.b.sup. .Math. Party P.sub.b setscustom character Cjcustom character B.sub.b =custom character .sub.jcustom character .sub.b.sup.B b. 20: For b {0, 1}, P.sub.b invokes an instance ofcustom character .sub.B2A.sup.n with inputcustom character C.sub.jcustom character .sub.b.sup.B and learnscustom character C.sub.jcustom character .sub.b.sup.n. 21: end for 22: For b {0, 1}, P.sub.b setscustom character Ccustom character .sub.b.sup.n =custom character C.sub.0custom character .sub.b.sup.n+custom character C.sub.1custom character .sub.b.sup.n+custom character C.sub.2custom character .sub.b.sup.n. 23: For b {0, 1}, P.sub.b sets B.sub.b = idiv(a.sub.b.sup.0 x.sub.b .Math. n.sup.0, d). 24: P.sub.b setscustom character zcustom character .sub.b.sup.n =.sub.n rdiv(custom character acustom character .sub.b.sup.n, d) +custom character corrcustom character .sub.b.sup.n.Math. n.sup.1 +b custom character Ccustom character .sub.b.sup.n B.sub.b, for b {0, 1}.

(243) Correctness and Security. First, m=Reconst.sup.B(custom charactermcustom character.sub.0.sup.B, custom charactermcustom character.sub.1.sup.B)=Reconst.sup.B(custom characteracustom character.sub.0.sup.B, custom characteracustom character.sub.1.sup.B)=1{an}. Next, similar to Algorithm 5, Reconst.sup.L(custom charactercorrcustom character.sub.0.sup.L, custom charactercorrcustom character.sub.1.sup.L)=corr=Reconst.sup.(custom charactercorrcustom character.sub.0.sup., custom charactercorrcustom character.sub.1.sup.), where corr is as defined in Theorem 4.1. Given the bounds on value of A (as discussed above), we can see that Steps 16 & 17 compute arithmetic shares of A, and A.sub.0=(Ad), A.sub.1=A, A.sub.2=(A+d), respectively. Now, invocation of custom character.sub.DReLU.sup.int, on shares of A.sub.j (Step 19) returns boolean shares of =(1MSB(A.sub.j)) over bit integers, which is same as 11{A.sub.j<0} over custom character. Hence, C.sub.j=Reconst.sup.B (custom characterC.sub.jcustom character).sub.0.sup.B, custom characterCcustom character.sub.1.sup.B)=1{A.sub.j<0}. By correctness of custom character.sub.B2A.sup.n, step 22 computes arithmetic shares of C as defined in Theorem 4.1. In step 23, B.sub.0+B.sub.1=.sub.n B as defined. Hence, correctness holds and custom characterzcustom character.sub.b.sup.n are shares of rdiv(a, d).

(244) Given that custom charactercorrcustom character.sub.0.sup.n and custom charactercorrcustom character.sub.0.sup. are uniformly random, security of the protocol can be seen in

(245) ( ( 4 1 ) - O T + , DReLU int , , B 2 A n ) - hybrid .

(246) Communication complexity. .sub.DIV.sup.ring,n,d involves a single call to custom character.sub.DReLU.sup.ring,n and

(247) 0 ( 4 1 ) - O T + ,
and three calls each to custom character.sub.DReLU.sup.int,, and custom character.sub.B2A.sup.n. From Appendix B, we have the cost of custom character.sub.DReLU.sup.ring,n as (3/2)+27/213 bits.

(248) ( 4 1 ) - O T +
and 3custom character.sub.B2A.sup.n cost 2+4.Math.(+) and 3+3 bits respectively. Since the cost of custom character is custom character+13custom character335 bits (see Appendix B), 3custom character.sub.DReLU.sup.int,, requires 3+409106 bits of communication. Thus, the overall communication of .sub.DIV.sup.ring,n,d is (3/2)+34+3+444119, which can be rewritten as <(3/2+34).Math.(+2). Concretely, we get the best communication for .sub.DIV.sup.ring,n,49 (=32) setting m=7 in all our millionaire invocations, which results in a total communication of 7796 bits.

(249) Note that for the case of custom character-bit integers, our division protocol would use a call to custom character and

(250) ( 4 1 ) - O T + ,
and three calls each to custom character.sub.DReLU.sup.int,, and custom character.sub.B2A.sup.L. The cost of custom character, and 3custom character.sub.DReLU.sup.int, are as mentioned in the previous paragraph, and the cost of

(251) ( 4 1 ) - O T +
and custom character.sub.B2A.sup.L are 2+4.Math.(custom character+) and 3+3custom character bits respectively. Thus, the overall communication is custom character+3+20custom character+447142 bits, which can be rewritten as <(+21).Math.(custom character+3). By setting m=8 in all our millionaire invocations, we get the best communication of 5570 bits for .sub.DIV.sup.ring,32,49.
E Improvement to Gazelle's Algorithm

(252) Gazelle [42] proposed two methods for computing convolutions, namely, the input rotations and the output rotations method. The only difference between the two methods is the number of (homomorphic) rotations required (the number of homomorphic additions also differ, but they are relatively very cheap). In this section, we describe an optimization to reduce the number of rotations required by the output rotations method.

(253) Let c.sub.i and c.sub.o denote the number of input and output channels respectively, and c.sub.n denote the number of channels that can fit in a single ciphertext. At a high level, the output rotations method works as follows: after performing all the convolutions homomorphically, we have c.sub.i.Math.c.sub.o/c.sub.n intermediate ciphertexts that are to be accumulated to form tightly packed output ciphertexts. Since most of these ciphertexts are misaligned after the convolution, they must be rotated in order to align and pack them. The intermediate ciphertexts can be grouped into c.sub.o/c.sub.n groups of c.sub.i ciphertexts each, such that the ciphertexts within each group are added (after alignment) to form a single ciphertext. In [42], the ciphertexts within each group are rotated (aligned) individually, resulting in c.sub.i.Math.c.sub.o/c.sub.n rotations. We observe that these groups can be further divided into c.sub.n subgroups of c.sub.i/c.sub.n ciphertexts each, such that ciphertexts within a subgroup are misaligned by the same offset. Doing this has the advantage that the c.sub.i/c.sub.n ciphertexts within each subgroup can first be added and then the resulting ciphertext can be aligned using a single rotation. This brings down the number of rotations by a factor of c.sub.i/c.sub.n to c.sub.n.Math.c.sub.o/c.sub.n.

(254) With our optimization, the output rotations method is better than the input rotations method when f.sup.2.Math.c.sub.i>c.sub.o, where f.sup.2 the filter size, which is usually the case.

(255) F Complexity of Our Benchmarks

(256) The complexity of the benchmarks we use in Section 7 is summarized as follows: SqueezeNet: There are 26 convolution layers of maximum filter size 33 and up to 1000 output channels. The activations after linear layers are ReLUs with size of up to 200,704 elements per layer. All ReLU layers combined have a size of 2,033,480. Additionally, there are 3 Maxpool layers and an Avgpool.sub.169 layer (Avgpool with pool size 169). ResNet50: There are 53 convolution layers of maximum filter size 77 and a peak output channel count of 2048. Convolution layers are followed by batch normalization and then ReLUs. There are 49 ReLU layers totaling 9,006,592 ReLUs, where the biggest one consists of 802,816 elements. Moreover, ResNet50 also has Maxpool layers and an Avgpool.sub.49. DenseNet121: There are 121 convolution layers with maximum filter dimension of 77 and up to 1000 output channels. Similar to ResNet50, between 2 convolution layers, there is batch normalization followed by ReLU. The biggest ReLU layer in DenseNet121 has 802,816 elements and the combined size of all ReLU layers is 15,065,344. In addition, DenseNet121 consists of a Maxpool, an Avgpool.sub.49 and 3 Avgpool.sub.4 layers.
G Garbled Circuits vs Our Protocols for Avgpool

(257) In this section, we compare our protocols with garbled circuits for evaluating the Avgpool layers of our benchmarks, and the corresponding performance numbers are given in Table 7.

(258) TABLE-US-00017 TABLE 7 Performance comparison of Garbled Circuits with our protocols for computing AVGpool layers. Runtimes are in seconds and communication numbers are in MiB. Garbled Circuits Our Protocol Benchmark LAN WAN Comm LAN WAN Comm (a) overcustom character SqueezeNet 0.2 2.0 36.02 0.1 0.8 1.84 ResNet50 0.4 3.9 96.97 0.1 0.8 2.35 DenseNet121 17.2 179.4 6017.94 0.5 3.5 158.83 (b) overcustom character .sub.n SqueezeNet 0.2 2.2 39.93 0.1 0.9 1.92 ResNet50 0.4 4.2 106.22 0.1 1.0 3.82 DenseNet121 19.2 198.2 6707.94 0.6 4.4 214.94

(259) On DenseNet121, where a total of 176, 640 divisions are performed, we have improvements over GC of more than 32 and 45 in the LAN and the WAN setting, respectively, for both our protocols. However, on SqueezeNet and ResNet50, the improvements are smaller (2 to 7) because these DNNs only require 1000 and 2048 divisions, respectively, which are not enough for the costs in our protocols to amortize well. On the other hand, the communication difference between our protocols and GC is huge for all three DNNs. Specifically, we have an improvement of more than 19, 27, and 31 on SqueezeNet, ResNet50, and DenseNet121 respectively, for both our protocols.

(260) The present invention may be embodied in other specific forms without departing from its spirit or characteristics. The described embodiments are to be considered in all respects only as illustrative and not restrictive. The scope of the invention is, therefore, indicate by the appended claims rather than by the foregoing description. All changes which come within the meaning and range of equivalency of the claims are to be embraced within their scope.

11. BIBLIOGRAPHY

(261) [1] 2020. CrypTFlow: An End-to-end System for Secure TensorFlow Inference. https://github.com/mpc-msri/EzPC. (2020). [2] 2020. Delphi: A Cryptographic Inference Service for Neural Networks. https://github.com/mc2-project/delphi. (2020). [3] Martin Abadi, Ashish Agarwal, Paul Barham, Eugene Brevdo, Zhifeng Chen, Craig Citro, Gregory S. Corrado, Andy Davis, Jeffrey Dean, Matthieu Devin, Sanjay Ghemawat, Ian J. Goodfellow, Andrew Harp, Geoffrey Irving, Michael Isard, Yangqing Jia, Rafal Jzefowicz, Lukasz Kaiser, Manjunath Kudlur, Josh Levenberg, Dan Man, Rajat Monga, Sherry Moore, Derek Gordon Murray, Chris Olah, Mike Schuster, Jonathon Shlens, Benoit Steiner, Ilya Sutskever, Kunal Talwar, Paul A. Tucker, Vincent Vanhoucke, Vijay Vasudevan, Fernanda B. Vigas, Oriol Vinyals, Pete Warden, Martin Wattenberg, Martin Wicke, Yuan Yu, and Xiaoqiang Zheng. 2016. TensorFlow: Large-Scale Machine Learning on Heterogeneous Distributed Systems. CoRR abs/1603.04467 (2016). https://arxiv.org/abs/1603.04467 [4] Nitin Agrawal, Ali Shahin Shamsabadi, Matt J. Kusner, and Adri Gascn. 2019. QUOTIENT: Two-Party Secure Neural Network Training and Prediction. In Proceedings of the 2019 ACMSIGSAC Conference on Computer and Communications Security, CCS 2019, London, UK, Nov. 11-15, 2019. 1231-1247. [5] Gilad Asharov, Yehuda Lindell, Thomas Schneider, and Michael Zohner. 2013. More efficient oblivious transfer and extensions for faster secure computation. In 2013 ACM SIGSAC Conference on Computer and Communications Security, CCS' 13, Berlin, Germany, Nov. 4-8, 2013, Ahmad-Reza Sadeghi, Virgil D. Gligor, and Moti Yung (Eds.). ACM, 535-548. https://doi.org/10.1145/2508859.2516738 [6] Marshall Ball, Brent Carmer, Tal Malkin, Mike Rosulek, and Nichole Schimanski. 2019. Garbled Neural Networks are Practical. IACR Cryptology ePrint Archive 2019 (2019), 338. https://eprint.iacr.org/2019/338 [7] Assi Barak, Daniel Escudero, Anders Dalskov, and Marcel Keller. 2019. Secure Evaluation of Quantized Neural Networks. Cryptology ePrint Archive, Report 2019/131. (2019). https://eprint.iacr.org/2019/131. [8] Donald Beaver. 1991. Efficient Multiparty Protocols Using Circuit Randomization. In Advances in CryptologyCRYPTO '91, 11th Annual International Cryptology Conference, Santa Barbara, California, USA, Aug. 11-15, 1991, Proceedings. 420-432. [9] Donald Beaver. 1996. Correlated Pseudorandomness and the Complexity of Private Computations. In Proceedings of the Twenty-Eighth Annual ACM Symposium on the Theory of Computing, Philadelphia, Pennsylvania, USA, May 22-24, 1996, Gary L. Miller (Ed.). ACM, 479-488. https://doi.org/10.1145/237814.237996 [10] Mihir Bellare, Viet Tung Hoang, Sriram Keelveedhi, and Phillip Rogaway. 2013. Efficient Garbling from a Fixed-Key Blockcipher. In 2013 IEEE Symposium on Security and Privacy, S P 2013, Berkeley, CA, USA, May 19-22, 2013. IEEE Computer Society, 478-492. https://doi.org/10.1109/SP.2013.39 [11] Mihir Bellare and Phillip Rogaway. 1993. Random Oracles are Practical: A Paradigm for Designing Efficient Protocols. In CCS '93, Proceedings of the 1st ACM Conference on Computer and Communications Security, Fairfax, Virginia, USA, Nov. 3-5, 1993, Dorothy E. Denning, Raymond Pyle, Ravi Ganesan, Ravi S. Sandhu, and Victoria Ashby (Eds.). ACM, 62-73. https://doi.org/10.1145/168588.168596 [12] G. R Blakley. 1979. Safeguarding cryptographic keys. In Managing Requirements Knowledge, International Workshop on. IEEE Computer Society, Los Alamitos, CA, USA, 313. https://doi.org/10.1109/AFIPS.1979.98 [13] Fabian Boemer, Anamaria Costache, Rosario Cammarota, and Casimir Wierzynski. 2019. nGraph-HE2: A High-Throughput Framework for Neural Network Inference on Encrypted Data. In Proceedings of the 7th ACM Workshop on Encrypted Computing & Applied Homomorphic Cryptography, WAHC@CCS 2019, London, UK, Nov. 11-15, 2019, Michael Brenner, Tancrde Lepoint, and Kurt Rohloff (Eds.). ACM, 45-56. https://doi.org/10.1145/3338469.3358944 [14] Fabian Boemer, Yixing Lao, Rosario Cammarota, and Casimir Wierzynski. 2019. nGraph HE: A Graph Compiler for Deep Learning on Homomorphically Encrypted Data. In Proceedings of the 16th ACM International Conference on Computing Frontiers, C F 2019, Alghero, Italy, Apr. 30-May 2, 2019. 3-13. [15] Raphael Bost, Raluca Ada Popa, Stephen Tu, and Shafi Goldwasser. 2015. Machine Learning Classification over Encrypted Data. In 22nd Annual Network and Distributed System Security Symposium, NDSS 2015, San Diego, California, USA, Feb. 8-11, 2015. The Internet Society. https://www.ndss-symposium.org/ndss2015/machine-learning-classification-over-encrypted-data [16] Zvika Brakerski. 2012. Fully Homomorphic Encryption without Modulus Switching from Classical GapSVP. In Advances in CryptologyCRYPTO 2012-32nd Annual Cryptology Conference, Santa Barbara, CA, USA, Aug. 19-23, 2012. Proceedings (Lecture Notes in Computer Science), Reihaneh Safavi-Naini and Ran Canetti (Eds.), Vol. 7417. Springer, 868-886. https://doi.org/10.1007/978-3-642-32009-5_50 [17] Gilles Brassard, Claude Crpeau, and Jean-Marc Robert. 1986. All-or-Nothing Disclosure of Secrets. In Advances in CryptologyCRYPTO '86, Santa Barbara, California, USA, 1986, Proceedings (Lecture Notes in Computer Science), Andrew M. Odlyzko (Ed.), Vol. 263. Springer, 234-238. https://doi.org/10.1007/3-540-47721-7_17 [18] Niklas Bscher, Daniel Demmler, Stefan Katzenbeisser, David Kretzmer, and Thomas Schneider. 2018. HyCC: Compilation of Hybrid Protocols for Practical Secure Computation. In Proceedings of the 2018 ACM SIGSAC Conference on Computer and Communications Security, CCS 2018, Toronto, ON, Canada, Oct. 15-19, 2018, David Lie, Mohammad Mannan, Michael Backes, and Xiao Feng Wang (Eds.). ACM, 847-861. https://doi.org/10.1145/3243734.3243786 [19] Ran Canetti. 2000. Security and Composition of Multiparty Cryptographic Protocols. J. Cryptology 13, 1 (2000), 143-202. [20] Nishanth Chandran, Divya Gupta, Aseem Rastogi, Rahul Sharma, and Shardul Tripathi. 2019. EzPC: Programmable and Efficient Secure Two-Party Computation for Machine Learning. In IEEE European Symposium on Security and Privacy, EuroS&P 2019, Stockholm, Sweden, Jun. 17-19, 2019. 496-511. [21] Valerie Chen, Valerio Pastro, and Mariana Raykova. 2019. Secure Computation for Machine Learning With SPDZ. CoRR abs/1901.00329 (2019). arXiv:1901.00329 http://arxiv.org/abs/1901.00329 [22] Geoffroy Couteau. 2018. New Protocols for Secure Equality Test and Comparison. In Applied Cryptography and Network Security16th International Conference, ACNS 2018, Leuven, Belgium, Jul. 2-4, 2018, Proceedings (Lecture Notes in Computer Science), Bart Preneel and Frederik Vercauteren (Eds.), Vol. 10892. Springer, 303-320. https://doi.org/10.1007/978-3-319-93387-0_16 [23] Roshan Dathathri, Olli Saarikivi, Hao Chen, Kristin Lauter, Saeed Maleki, Madan Musuvathi, and Todd Mytkowicz. 2019. CHET: An Optimizing Compiler for Fully-Homomorphic Neural-Network Inferencing. In Proceedings of the 40th ACM SIGPLAN Conference on Programming Language Design and Implementation, PLDI 2019, Phoenix, AZ, USA, Jun. 22-26, 2019. 142-156. [24] Daniel Demmler, Thomas Schneider, and Michael Zohner. 2015. ABYA Framework for Efficient Mixed-Protocol Secure Two-Party Computation. In 22nd Annual Network and Distributed System Security Symposium, NDSS 2015, San Diego, California, USA, Feb. 8-11, 2015. [25] Jia Deng, Wei Dong, Richard Socher, Li-Jia Li, Kai Li, and Fei-Fei Li. 2009. ImageNet: A large-scale hierarchical image database. In 2009 IEEE Computer Society Conference on Computer Vision and Pattern Recognition (CVPR 2009), 20-25 Jun. 2009, Miami, Florida, USA. 248-255. [26] Shimon Even, Oded Goldreich, and Abraham Lempel. 1985. A Randomized Protocol for Signing Contracts. Commun. ACM 28, 6 (1985), 637-647. https://doi.org/10.1145/3812.3818 [27] Junfeng Fan and Frederik Vercauteren. 2012. Somewhat Practical Fully Homomorphic Encryption. Cryptology ePrint Archive, Report 2012/144. (2012). http://eprint.iacr.org/2012/144. [28] Juan A. Garay, Berry Schoenmakers, and Jos Villegas. 2007. Practical and Secure Solutions for Integer Comparison. In Public Key CryptographyPKC 2007, 10th International Conference on Practice and Theory in Public-Key Cryptography, Beijing, China, Apr. 16-20, 2007, Proceedings (Lecture Notes in Computer Science), Tatsuaki Okamoto and Xiaoyun Wang (Eds.), Vol. 4450. Springer, 330-342. https://doi.org/10.1007/978-3-540-71677-8_22 [29] Craig Gentry. 2009. Fully homomorphic encryption using ideal lattices. In Proceedings of the 41st Annual ACM Symposium on Theory of Computing, STOC 2009, Bethesda, MD, USA, May 31-Jun. 2, 2009, Michael Mitzenmacher (Ed.). ACM, 169 178. https://doi.org/10.1145/1536414.1536440 [30] Ran Gilad-Bachrach, Nathan Dowlin, Kim Lathe, Kristin E. Lauter, Michael Naehrig, and John Wernsing. 2016. CryptoNets: Applying Neural Networks to Encrypted Data with High Throughput and Accuracy. In Proceedings of the 33nd International Conference on Machine Learning, ICML 2016, New York City, NY, USA, Jun. 19-24, 2016. 201-210. [31] Oded Goldreich, Silvio Micali, and Avi Wigderson. 1987. How to Play any Mental Game or A Completeness Theorem for Protocols with Honest Majority. In Proceedings of the 19th Annual ACM Symposium on Theory of Computing, 1987, New York, New York, USA. 218-229. [32] Shay Gueron. 2016. AES-GCM-SIV implementations (128 and 256 bit). https://github.com/Shay-Gueron/AES-GCM-SIV. (2016). [33] Shay Gueron, Yehuda Lindell, Ariel Nof, and Benny Pinkas. 2018. Fast Garbling of Circuits Under Standard Assumptions. J. Cryptol. 31, 3 (2018). https://doi.org/10.1007/s00145-017-9271-y [34] C. Guo, J. Katz, X. Wang, and Y. Yu. 2020. Efficient and Secure Multiparty Computation from Fixed-Key Block Ciphers. In 2020 IEEE Symposium on Security and Privacy (SP). IEEE Computer Society, Los Alamitos, CA, USA, 247-263. https://doi.org/10.1109/SP.2020.00016 [35] Carmit Hazay, Yuval Ishai, Antonio Marcedone, and Muthuramakrishnan Venkitasubramaniam. 2019. LevioSA: Lightweight Secure Arithmetic Computation. In Proceedings of the 2019 ACM Conference on Computer and Communications Security, CCS 2019, London, UK, Nov. 11-15, 2019. 327-344. [36] Kaiming He, Xiangyu Zhang, Shaoqing Ren, and Jian Sun. 2016. Deep Residual Learning for Image Recognition. In 2016 IEEE Conference on Computer Vision and Pattern Recognition, CVPR 2016, Las Vegas, NV, USA, Jun. 27-30, 2016. 770-778. [37] Gao Huang, Zhuang Liu, Laurens van der Maaten, and Kilian Q. Weinberger. 2017. Densely Connected Convolutional Networks. In 2017 IEEE Conference on Computer Vision and Pattern Recognition, CVPR 2017, Honolulu, HI, USA, Jul. 21-26, 2017. 2261-2269. [38] Itay Hubara, Matthieu Courbariaux, Daniel Soudry, Ran El-Yaniv, and Yoshua Bengio. 2016. Binarized Neural Networks. In Advances in Neural Information Processing Systems 29: Annual Conference on Neural Information Processing Systems 2016, Dec. 5-10, 2016, Barcelona, Spain, Daniel D. Lee, Masashi Sugiyama, Ulrike von Luxburg, Isabelle Guyon, and Roman Garnett (Eds.). 4107-4115. [39] Forrest N. Iandola, Matthew W. Moskewicz, Khalid Ashraf, Song Han, William J. Dally, and Kurt Keutzer. 2016. SqueezeNet: AlexNet-level accuracy with 50 fewer parameters and <1 MB model size. CoRR abs/1602.07360 (2016).arXiv:1602.07360 http://arxiv.org/abs/1602.07360 [40] Yuval Ishai, Joe Kilian, Kobbi Nissim, and Erez Petrank. 2003. Extending Oblivious Transfers Efficiently. In Advances in CryptologyCRYPTO 2003, 23rd Annual International Cryptology Conference, Santa Barbara, California, USA, Aug. 17-21, 2003, Proceedings (Lecture Notes in Computer Science), Dan Boneh (Ed.), Vol. 2729. Springer, 145-161. https://doi.org/10.1007/978-3-540-45146-4_9 [41] Benoit Jacob, Skirmantas Kligys, Bo Chen, Menglong Zhu, Matthew Tang, Andrew G. Howard, Hartwig Adam, and Dmitry Kalenichenko. 2018. Quantization and Training of Neural Networks for Efficient Integer-Arithmetic-Only Inference. In 2018 IEEE Conference on Computer Vision and Pattern Recognition, CVPR 2018, Salt Lake City, UT, USA, Jun. 18-22, 2018. 2704-2713. [42] Chiraag Juvekar, Vinod Vaikuntanathan, and Anantha Chandrakasan. 2018. GAZELLE: A Low Latency Framework for Secure Neural Network Inference. In 27th USENIX Security Symposium, USENIX Security 2018, Baltimore, MD, USA, Aug. 15-17, 2018. 1651-1669. [43] Vladimir Kolesnikov and Ranjit Kumaresan. 2013. Improved OT Extension for Transferring Short Secrets. In Advances in CryptologyCRYPTO 2013-33rd Annual Cryptology Conference, Santa Barbara, CA, USA, Aug. 18-22, 2013. Proceedings, Part II (Lecture Notes in Computer Science), Ran Canetti and Juan A. Garay (Eds.), Vol. 8043. Springer, 54-70. https://doi.org/10.1007/978-3-642-40084-1_4 [44] Nishant Kumar, Mayank Rathee, Nishanth Chandran, Divya Gupta, Aseem Rastogi, and Rahul Sharma. 2020. CrypTFlow: Secure TensorFlow Inference. In 2020 IEEE Symposium on Security and Privacy, S&P 2020, San Francisco, CA, USA, May 18-20, 2020. 1521-1538. [45] Kim Lathe. 2017. Simple Encrypted Arithmetic Library 2.3.1. https://www.microsoft.com/en-us/research/uploads/prod/2017/11/sealmanual-2-3-1.pdf. [46] Yehuda Lindell. 2016. How To Simulate ItA Tutorial on the Simulation Proof Technique. Cryptology ePrint Archive, Report 2016/046. (2016). https://eprint.iacr.org/2016/046. [47] Jian Liu, Mika Juuti, Yao Lu, and N. Asokan. 2017. Oblivious Neural Network Predictions via MiniONN Transformations. In Proceedings of the 2017 ACM SIGSAC Conference on Computer and Communications Security, CCS 2017, Dallas, TX, USA, Oct. 30-Nov. 3, 2017. 619-631. [48] Pratyush Mishra, Ryan Lehmkuhl, Akshayaram Srinivasan, Wenting Zheng, and Raluca Ada Popa. 2020. Delphi: A Cryptographic Inference Service for Neural Networks. In 29th USENIX Security Symposium, USENIX Security 20. Boston, MA. [49] Payman Mohassel and Peter Rindal. 2018. ABY3: A Mixed Protocol Framework for Machine Learning. In Proceedings of the 2018 ACM SIGSAC Conference on Computer and Communications Security, CCS 2018, Toronto, ON, Canada, Oct. 15-19, 2018. 35-52. [50] Payman Mohassel and Yupeng Zhang. 2017. SecureML: A System for Scalable Privacy-Preserving Machine Learning. In 2017 IEEE Symposium on Security and Privacy, S&P 2017, San Jose, CA, USA, May 22-26, 2017. 19-38. [51] Markus Nagel, Mart van Baalen, Tijmen Blankevoort, and Max Welling. 2019. Data-Free Quantization Through Weight Equalization and Bias Correction. In 2019 IEEE/CVF International Conference on Computer Vision, ICCV 2019, Seoul, Korea (South), Oct. 27-Nov. 2, 2019. IEEE, 1325-1334. [52] Erman Pattuk, Murat Kantarcioglu, Huseyin Ulusoy, and Bradley A. Malin. 2016. CheapSMC: A Framework to Minimize Secure Multiparty Computation Cost in the Cloud. In Data and Applications Security and Privacy XXX30th Annual IFIP WG 11.3 Conference, DBSec 2016, Trento, Italy, Jul. 18-20, 2016. Proceedings (Lecture Notes in Computer Science), Silvio Ranise and Vipin Swarup (Eds.), Vol. 9766. Springer, 285 294. [53] Michael O. Rabin. 1981. How to exchange secrets with oblivious transfer. Technical Report TR-81, Aiken Computation Lab, Harvard University. (1981). https://eprint.iacr.org/2005/187.pdf. [54] M. Sadegh Riazi, Mohammad Samragh, Hao Chen, Kim Laine, Kristin E. Lauter, and Farinaz Koushanfar. 2019. XONN: XNOR-based Oblivious Deep Neural Network Inference. In 28th USENIX Security Symposium, USENIX Security 2019, Santa Clara, CA, USA, Aug. 14-16, 2019. 1501-1518. [55] M. Sadegh Riazi, Christian Weinert, Oleksandr Tkachenko, Ebrahim M. Songhori, Thomas Schneider, and Farinaz Koushanfar. 2018. Chameleon: A Hybrid Secure Computation Framework for Machine Learning Applications. In Proceedings of the 2018 on Asia Conference on Computer and Communications Security, AsiaCCS 2018, Incheon, Republic of Korea, Jun. 4-8, 2018. 707-721. https://doi.org/10.1145/3196494.3196522 [56] Bita Darvish Rouhani, M. Sadegh Riazi, and Farinaz Koushanfar. 2018. Deepsecure: scalable provably-secure deep learning. In Proceedings of the 55th Annual Design Automation Conference, D A C 2018, San Francisco, CA, USA, Jun. 24-29, 2018. ACM, 2:1-2:6. [57] SEAL 2019. Microsoft SEAL (release 3.3). https://github.com/Microsoft/SEAL. (2019). Microsoft Research, Redmond, WA. [58] Adi Shamir. 1979. How to Share a Secret. Commun. ACM 22, 11 (1979), 612-613. https://doi.org/10.1145/359168.359176 [59] N. P. Smart and F. Vercauteren. 2011. Fully Homomorphic SIMD Operations. Cryptology ePrint Archive, Report 2011/133. (2011). http://eprint.iacr.org/2011/133. [60] Sameer Wagh, Divya Gupta, and Nishanth Chandran. 2019. SecureNN: 3-Party Secure Computation for Neural Network Training. PoPETs 2019, 3 (2019), 26-49. [61] Xiao Wang, Alex J. Malozemoff, and Jonathan Katz. 2016. EMP-toolkit: Efficient MultiParty computation toolkit. https://github.com/emp-toolkit. (2016). [62] Andrew Chi-Chih Yao. 1986. How to Generate and Exchange Secrets (Extended Abstract). In 27th Annual Symposium on Foundations of Computer Science, Toronto, Canada, 27-29 Oct. 1986. IEEE Computer Society, 162-167. https://doi.org/10.1109/SFCS.1986.25 [63] Wenting Zheng, Raluca Ada Popa, Joseph E. Gonzalez, and Ion Stoica. 2019. Helen: Maliciously Secure Coopetitive Learning for Linear Models. In 2019 IEEE Symposium on Security and Privacy, S&P 2019, San Francisco, CA, USA, May 19-23, 2019. 724-738. [64] Xiaoyong Zhu, George Iordanescu, Ilia Karmanov, and Mazen Zawaideh. 2018. (March 2018). https://blogs.technet.microsoft.com/machinelearning/2018/03/07/using-microsoft-ai-to-build-a-lung-disease-prediction-model-using-chest-xray-images/