Classifications

• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
  • H04L9/08—Key distribution or management, e.g. generation, sharing or updating, of cryptographic keys or passwords
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L63/00—Network architectures or network communication protocols for network security
  • H04L63/04—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks
  • H04L63/0428—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks wherein the data content is protected, e.g. by encrypting or encapsulating the payload
  • H04L63/0435—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks wherein the data content is protected, e.g. by encrypting or encapsulating the payload wherein the sending and receiving network entities apply symmetric encryption, i.e. same key used for encryption and decryption
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L63/00—Network architectures or network communication protocols for network security
  • H04L63/04—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks
  • H04L63/0428—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks wherein the data content is protected, e.g. by encrypting or encapsulating the payload
  • H04L63/0471—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks wherein the data content is protected, e.g. by encrypting or encapsulating the payload applying encryption by an intermediary, e.g. receiving clear information at the intermediary and encrypting the received information at the intermediary before forwarding
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L63/00—Network architectures or network communication protocols for network security
  • H04L63/06—Network architectures or network communication protocols for network security for supporting key management in a packet data network
  • H04L63/061—Network architectures or network communication protocols for network security for supporting key management in a packet data network for key exchange, e.g. in peer-to-peer networks
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L63/00—Network architectures or network communication protocols for network security
  • H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L63/00—Network architectures or network communication protocols for network security
  • H04L63/16—Implementing security features at a particular protocol layer
  • H04L63/166—Implementing security features at a particular protocol layer at the transport layer
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
  • H04L9/002—Countermeasures against attacks on cryptographic mechanisms
  • H04L9/003—Countermeasures against attacks on cryptographic mechanisms for power analysis, e.g. differential power analysis [DPA] or simple power analysis [SPA]
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
  • H04L9/006—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols involving public key infrastructure [PKI] trust models
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
  • H04L9/08—Key distribution or management, e.g. generation, sharing or updating, of cryptographic keys or passwords
  • H04L9/0816—Key establishment, i.e. cryptographic processes or cryptographic protocols whereby a shared secret becomes available to two or more parties, for subsequent use
  • H04L9/0819—Key transport or distribution, i.e. key establishment techniques where one party creates or otherwise obtains a secret value, and securely transfers it to the other(s)
  • H04L9/0822—Key transport or distribution, i.e. key establishment techniques where one party creates or otherwise obtains a secret value, and securely transfers it to the other(s) using key encryption key
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
  • H04L9/08—Key distribution or management, e.g. generation, sharing or updating, of cryptographic keys or passwords
  • H04L9/0816—Key establishment, i.e. cryptographic processes or cryptographic protocols whereby a shared secret becomes available to two or more parties, for subsequent use
  • H04L9/0819—Key transport or distribution, i.e. key establishment techniques where one party creates or otherwise obtains a secret value, and securely transfers it to the other(s)
  • H04L9/0825—Key transport or distribution, i.e. key establishment techniques where one party creates or otherwise obtains a secret value, and securely transfers it to the other(s) using asymmetric-key encryption or public key infrastructure [PKI], e.g. key signature or public key certificates
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
  • H04L9/08—Key distribution or management, e.g. generation, sharing or updating, of cryptographic keys or passwords
  • H04L9/088—Usage controlling of secret information, e.g. techniques for restricting cryptographic keys to pre-authorized uses, different access levels, validity of crypto-period, different key- or password length, or different strong and weak cryptographic algorithms
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
  • H04L9/08—Key distribution or management, e.g. generation, sharing or updating, of cryptographic keys or passwords
  • H04L9/0894—Escrow, recovery or storing of secret information, e.g. secret key escrow or cryptographic key storage

Definitions

• At least some embodiments disclosed herein relate to security processing or storage in general.
• One embodiment replaces a distributed encryption solution for data object storage with a centralized encryption solution, which is more reliable, secure, and manageable and in many cases provides much higher performance.
• a centralized encryption system and centralized key manager is significantly easier to manage and protect than a distributed
• a payload encryption method uses symmetric encryption algorithms with authentication to encrypt or decrypt a payload file object or data.
• the gateway encrypts the payload (file object or data) using a specific key associated to the client and/or object.
• the gateway then encrypts the payload to a remote-side transport encryption protocol and sends the encrypted payload to a remote server or cloud server.
• a system includes: a first computing device
• the first computing device comprising at least one processor (e.g., for data path and/or cryptographic processing) and at least one memory
• the encryption gateway configured to receive data in a payload from a client application (e.g., the client application can be implemented in either hardware or software), to encrypt the data, and to send or write the encrypted data to a remote cloud storage or a data server; a router or switch, configured to provide, via local- side transport, the payload from the client application to the encryption gateway; and a key manager, the key manager configured to provide at least one key to the encryption gateway for encryption of the data in the payload, wherein at least one key is associated to the client application (or the corresponding client) or the payload, and the encryption of the data uses a remote-side transport protocol associated with the remote cloud storage or server.
• a method includes: receiving, by an encryption gateway from a hardware or software client application, a request to read data from a remote cloud storage or server; receiving the data in a first payload from the remote cloud storage or server, wherein the data has been encrypted using a remote-side transport protocol associated with the remote cloud storage or data server; decrypting, by at least one processor of the encryption gateway, the received data in the first payload using the remote-side transport protocol, wherein the decrypting uses a key of the client application and the key is retrieved from a memory; encrypting, by the encryption gateway, the first payload using a client-side transport protocol; and sending, from the encryption gateway to the client application, the encrypted first payload (for a non-limiting example, see Figure 1 ).
• an encryption gateway includes at least one processor; and memory storing instructions configured to instruct at least one processor to: receive, via local-side transport, data in a payload from a client application; receive, from a key manager, at least one key for encryption of the data in the payload, wherein at least one key is associated to the client application or the payload; encrypt the data in the payload, the encryption using a remote-side transport protocol associated with a remote cloud storage or server; and send or write the encrypted data to the remote cloud storage or server.
• the disclosure includes methods and apparatuses which perform these methods, including data processing systems which perform these methods, and computer readable media containing instructions which when executed on data processing systems cause the systems to perform these methods.
• Figure 1 shows a top level diagram of a communication system in one embodiment.
• Figure 2 shows detailed TLS implementation details of one embodiment.
• FIG. 3 shows detailed TLS/MACSEC implementation details of one embodiment.
• FIG. 4 shows detailed MACSEC implementation details of one embodiment.
• FIG. 5 shows clients and servers using TLS (HTTPS) connections in one embodiment.
• TLS HTTPS
• FIG. 6 shows a TLS (HTTPS) proxy data flow in one embodiment.
• FIG. 7 shows clients using HTTP and server using TLS (HTTPS) in one embodiment.
• FIG 8 shows HTTP client to TLS (HTTPS) server proxy connection data flow in one embodiment.
• FIG. 9 shows persistent TLS (HTTPS) connections to server in one embodiment.
• the data is double encrypted in transit at 10 Gigabits to 100 Gigabits or higher data rates.
• HTTPS is equivalent to HTTP over TLS or SSL (or another equivalent security).
• Figures 1 -4 show example embodiments of the communication system.
• Figure 1 illustrates an example of the communication system in situ.
• Figure 2 illustrates an embodiment of the system with TLS transport security on both local and remote sides of the system.
• Figure 3 illustrates an embodiment of the system with TLS transport security on local side and MACSEC transport security on the remote side of the system.
• Figure 4 illustrates an embodiment of the system with MACSEC transport security on both local and remote sides of the system.
• a local client sends or writes data to the cloud or remote server flow.
• the client uses any transport encryption method on the file object or data to the gateway.
• the gateway decrypts the local-side transport to yield the plain text file object or data.
• the gateway encrypts the payload (file object or data) using a specific key associated to the client and/or object.
• the gateway then encrypts the payload to the remote-side transport encryption protocol and sends to the remote server or cloud server.
• the remote server or cloud server decrypts the transport protocol. At this time, the payload is still encrypted by the client's key.
• the encrypted payload data is then stored.
• the aggregated gateway terminates remote side communication (e.g., MACSEC, IPSEC, TLS), performs encryption as required on the TCP stream of data (e.g., encrypt a file object in a file transfer stream), and then performs new independent transport encryption (e.g., TCP and TLS sessions) on the remote side.
• data is read or local client receives data from the cloud or remote server. The client requests that the remote server or cloud server reads the encrypted stored data. The remote server or cloud server encrypts the data using remote-side transport protocol. The gateway receives the data and decrypts the remote-side transport protocol.
• the gateway decrypts the payload file object or data and then encrypts the data using the client- side transport protocol.
• the client receives the transport data and decrypts.
• the aggregated gateway terminates local side communication (e.g., TCP and TLS sessions), performs decryption as required on the TCP stream of data (e.g., encrypt a file object in a file transfer stream), and then performs new independent transport encryption (e.g., MACSEC, IPSEC, TLS) on the remote side.
• the transport encryption method is used to protect the data during transmission between physical sites or buildings (i.e., point-to-point encryption).
• the transport encryption method can be, for example, an industry standard such as, for example, TLS (Transport Security Layer), IPSec (Internet Protocol Security), MACSEC (IEEE MAC Security standard), or any custom transport protocol.
• TLS, MACSEC, IPSec all have authentication information that will be used to associate the client's payload keys.
• the payload encryption method uses symmetric encryption algorithms with authentication (e.g., AES-GCM) to encrypt or decrypt the payload file object or data.
• the symmetric encryption algorithms with authentication is required to associate the proper client's payload key to the file object or data.
• the payload key manager facilitates the loading of client payload keys into the gateway.
• the client keys can be either loaded via a secure port or over the network using a secure method. Once the key are loaded into the gateway, the keys are pre- associated to the clients that are connected to the gateway. The client's key is associated to the client based on the information provided by the transport
• the payload key manager communicates with transport encryption protocol to determine who the client is and what client payload key to associate with the file object or data for payload encryption or decryption.
• One of the key features is the ability to encrypt the payload data at the file object level and associate the client's payload key to the file object.
• a first computing device is configured as an encryption gateway, the first computing device comprises at least one processor (e.g., for data path and/or cryptographic processing) and at least one memory.
• the encryption gateway is configured to authenticate a client using one or multiple authentication factors, and further configured to receive TLS (or other transport encryption) data from a client application.
• the encryption gateway will terminate the client TLS connection and extract the payload and encrypt the payload with authentication.
• the encryption gateway inserts the encrypted-authenticated payload into the cloud or data server TLS data packet/format.
• the encryption gateway establishes a cloud or data server TLS connection.
• the cloud or data server terminates the TLS connection, which includes TCP termination, and stores the encrypted-authenticated payload in the cloud or data server memory.
• an approach terminates a client TLS connection which also includes TCP termination, extracts data from a payload and encrypts the extracted data with authentication (using an encryption key from a key manager).
• a TLS connection is set-up to a cloud or data server, and the encrypted authenticated data is inserted into a TLS cloud payload with key association information.
• the cloud or data server terminates the TLS connection and the encrypted authenticated payload data is stored on the cloud or data server memory/storage.
• the design is not limited to TLS and Cloud Services file encryption, and this description is an example and discussion of the tradeoffs of a single embodiment of the general design.
• the TLS algorithm can be implemented using a systolic matrix architecture as referred to below.
• TLS background (used in this example) and other transport encryption methods are, for example, IPSEC, MACSEC, or a custom method.
• the transport and packet processing can be implemented using a systolic matrix architecture as referred to below.
• Transport Layer Security or Secure Socket Layer (SSL) is used to secure data in flight at Layer 6 of the OSI model. It provides both certificate authentication and transport encryption for all application layer data.
• TLS gives the client confidence that its data is only connected to the cloud service provider.
• TLS operates by negotiating a session key per TLS or Secure Socket Layer (SSL) connection.
• SSL Secure Socket Layer
• the hardware encryption gateway acts as a TLS proxy between client applications and cloud storage as shown in Figure 5.
• Figure 6 shows a flow chart describing the process of decrypting and re- encrypting the TLS connections.
• the encryption gateway negotiates a TLS connection to the client and a TLS connection to the cloud servers.
• the client TLS encryption will be decrypted using the client session key.
• the file object will be encrypted using a key derived from the file object metadata (Object ID for example).
• the HTTP stream will be TLS encrypted for transport to the cloud server using the cloud session key.
• This option allows both cloud servers and client applications to continue operating transparently, provided the proxy (Hardware Encryption Gateway) is able to provide a valid cloud certificate to the client. If the proxy does not have a valid certificate for the cloud domain, the clients would need to accept the proxy certificate as a security exception.
• the proxy Hard Encryption Gateway
• the cost of Hardware Encryption Gateway using TLS for both the client and the cloud server is that the number of TLS negotiations required has doubled compared to not using a proxy. This can reduce throughput performance for clients due to added TLS negotiation time, especially for small-sized files. This also puts a heavy burden on the proxy (Hardware Encryption Gateway) because it must deal with the aggregate client TLS sessions.
• Hardware Encryption Gateway would act as a client-only TLS proxy. Hardware Encryption Gateway will modify the client HTTP packets to the HTTPS. This will reduce the number of TLS negotiations in half from the full HTTPS option, and will remove a level of decryption in client-to-proxy traffic and a level of encryption in the proxy-to-client traffic, relieving both client and proxy of that computational burden. Note that this solution may require a change to the client side software.
• Option 3 outlines potential performance optimizations that could reduce the number of TLS negotiations that are needed between cloud server and proxy from the direct-connect HTTPS network used in both Options 1 and 2.
• the TLS proxy Hard Encryption Gateway
• Hardware Encryption Gateway would set up TLS sessions with a cloud server before clients initiate any data transfer. As clients move data to/from the cloud servers, Hardware Encryption Gateway would use a pre-opened TLS session for the client, modifying the client IP address and port number to that of the active TLS session.
• Hardware Encryption Gateway would insert a TLS header, modify the server TCP port number to HTTPS, and perform all the necessary TLS encryption and authentication.
• server-to-client traffic For server-to-client traffic,
• Hardware Encryption Gateway would reverse the process described above.
• This option can be used in combination with either Option 1 or Option 2. In either case, it would reduce the number of proxy-to-server TLS sessions required especially in the case of many short-lived client connections. This option also disassociates the lag of proxy-to-server connections from the client-to-proxy connections so that the client does not see additional latency in individual client connections.
• a general hardware aggregated encryption gateway enables centralized encryption of communications leaving a corporate or other site.
• the Hardware Encryption Gateway can negotiate hundreds of TLS connections per second and maintain thousands of TCP connections simultaneously.
• the Hardware Encryption Gateway is programmable for real-time HTTP 100 Gbs full duplex TLS and data at rest encryption that is transparent to clients and cloud.
• the encryption gateway may be implemented by or use encryption/decryption and/or communication methods and systems as described in U.S. Patent Application Serial No. 14/177,392, filed February 1 1 , 2014, entitled "SECURITY DEVICE WITH PROGRAMMABLE SYSTOLIC-MATRIX
• the encryption gateway may use systolic matrix packet engines and multiplexers to process and route packets or other data, as described in the foregoing applications.
• At least some aspects disclosed can be embodied, at least in part, in software. That is, the techniques may be carried out in a computer system or other data processing system in response to its processor(s), such as a microprocessor, executing sequences of instructions contained in a memory, such as ROM, volatile RAM, non-volatile memory, cache or a remote storage device.
• processor(s) such as a microprocessor
• a memory such as ROM, volatile RAM, non-volatile memory, cache or a remote storage device.
• hardwired circuitry e.g., one or more hardware processors or other computing devices
• software instructions e.g., the communication system may be implemented using one or more computing devices.
• the techniques are neither limited to any specific combination of hardware circuitry and software nor to any particular source for the instructions executed by the data processing system.
• a computing device may be used that comprises an inter-connect (e.g., bus and system core logic), which interconnects a
• microprocessor (s) and a memory.
• the microprocessor is coupled to cache memory in one example.
• the inter-connect interconnects the microprocessor(s) and the memory together and also interconnects them to a display controller and display device and to peripheral devices such as input/output (I/O) devices through an input/output controller(s).
• I/O devices include mice, keyboards, modems, network interfaces, printers, scanners, video cameras and other devices which are well known in the art.
• the inter-connect may include one or more buses connected to one another through various bridges, controllers and/or adapters.
• the I/O controller includes a USB (Universal Serial Bus) adapter for controlling USB peripherals, and/or an IEEE-1394 bus adapter for controlling IEEE-1394 peripherals.
• USB Universal Serial Bus
• the memory may include ROM (Read Only Memory), and volatile RAM (Random Access Memory) and non-volatile memory, such as hard drive, flash memory, etc.
• ROM Read Only Memory
• RAM Random Access Memory
• non-volatile memory such as hard drive, flash memory, etc.
• Volatile RAM is typically implemented as dynamic RAM (DRAM) which requires power continually in order to refresh or maintain the data in the memory.
• DRAM dynamic RAM
• Non-volatile memory is typically a magnetic hard drive, a magnetic optical drive, or an optical drive (e.g., a DVD RAM), or other type of memory system which maintains data even after power is removed from the system.
• the non-volatile memory may also be a random access memory.
• the non-volatile memory can be a local device coupled directly to the rest of the components in the data processing system.
• a non-volatile memory that is remote from the system such as a network storage device coupled to the data processing system through a network interface such as a modem or Ethernet interface, can also be used.
• a data processing system such as the computing device above is used to implement one or more of the following: an encryption gateway, a router, a switch, a key manager, a client application, cloud storage, a load balancer, and a firewall.
• a data processing system such as the computing device above is used to implement a user terminal, which may provide a user interface for control of a computing device.
• a user interface may permit configuration of the encryption gateway.
• a user terminal may be in the form of a personal digital assistant (PDA), a cellular phone or other mobile device, a notebook computer or a personal desktop computer.
• PDA personal digital assistant
• one or more servers of the data processing system can be replaced with the service of a peer to peer network of a plurality of data processing systems, or a network of distributed computing systems.
• the peer to peer network, or a distributed computing system can be collectively viewed as a server data processing system.
• Embodiments of the disclosure can be implemented via the
• microprocessor(s) and/or the memory above For example, the functionalities described can be partially implemented via hardware logic in the microprocessor(s) and partially using the instructions stored in the memory. Some embodiments are implemented using the microprocessor(s) without additional instructions stored in the memory. Some embodiments are implemented using the instructions stored in the memory for execution by one or more general purpose microprocessor(s). Thus, the disclosure is not limited to a specific configuration of hardware and/or software.
• microprocessor Alternatively, or in combination, the functions and operations can be implemented using special purpose circuitry, with or without software instructions, such as using an Application-Specific Integrated Circuit (ASIC) or a Field- Programmable Gate Array (FPGA).
• ASIC Application-Specific Integrated Circuit
• FPGA Field- Programmable Gate Array
• Embodiments can be implemented using hardwired circuitry without software instructions, or in combination with software instructions. Thus, the techniques are limited neither to any specific combination of hardware circuitry and software, nor to any particular source for the instructions executed by the data processing system.
• At least some aspects disclosed can be embodied, at least in part, in software. That is, the techniques may be carried out in a computer system or other data processing system in response to its processor, such as a microprocessor, executing sequences of instructions contained in a memory, such as ROM, volatile RAM, non-volatile memory, cache or a remote storage device.
• processor such as a microprocessor
• a memory such as ROM, volatile RAM, non-volatile memory, cache or a remote storage device.
• Hardware and/or software may be used to implement the embodiments above.
• the software may be a sequence of instructions referred to as "computer programs.”
• the computer programs typically comprise one or more instructions set at various times in various memory and storage devices in a computer, and that, when read and executed by one or more processors in a computer, cause the computer to perform operations necessary to execute elements involving the various aspects.
• Software used in an embodiment may be stored in a machine readable medium.
• the executable software when executed by a data processing system, causes the system to perform various methods.
• the executable software and data may be stored in various places including for example ROM, volatile RAM, nonvolatile memory and/or cache. Portions of this software and/or data may be stored in any one of these storage devices.
• the data and instructions can be obtained from centralized servers or peer to peer networks. Different portions of the data and instructions can be obtained from different centralized servers and/or peer to peer networks at different times and in different communication sessions or in a same communication session. The data and instructions can be obtained in entirety prior to the execution of the applications. Alternatively, portions of the data and
• instructions can be obtained dynamically, just in time, when needed for execution. Thus, it is not required that the data and instructions be on a machine readable medium in entirety at a particular instance of time.
• Examples of computer-readable media include but are not limited to recordable and non-recordable type media such as volatile and non-volatile memory devices, read only memory (ROM), random access memory (RAM), flash memory devices, floppy and other removable disks, magnetic disk storage media, optical storage media (e.g., Compact Disk Read-Only Memory (CD ROMS), Digital Versatile Disks (DVDs), etc.), among others.
• the computer-readable media may store the instructions.
• a tangible machine readable medium includes any mechanism that provides (e.g., stores) information in a form accessible by a machine (e.g., a computer, network device, personal digital assistant, manufacturing tool, any device with a set of one or more processors, etc.).
• a machine e.g., a computer, network device, personal digital assistant, manufacturing tool, any device with a set of one or more processors, etc.

Landscapes

• Engineering & Computer Science (AREA)
• Computer Security & Cryptography (AREA)
• Computer Networks & Wireless Communication (AREA)
• Signal Processing (AREA)
• Computer Hardware Design (AREA)
• Computing Systems (AREA)
• General Engineering & Computer Science (AREA)
• Data Exchanges In Wide-Area Networks (AREA)
• Computer And Data Communications (AREA)
• Information Transfer Between Computers (AREA)

Priority Applications (8)

Applications Claiming Priority (4)

Publications (1)

Family

ID=58283307

Family Applications (1)

Country Status (6)

Cited By (10)

Families Citing this family (28)

Citations (7)

Family Cites Families (99)

• 2016
  • 2016-09-14 US US15/264,840 patent/US9794064B2/en active Active
  • 2016-09-15 IL IL294252A patent/IL294252B2/en unknown
  • 2016-09-15 EP EP16847265.2A patent/EP3350974B1/en active Active
  • 2016-09-15 AU AU2016323147A patent/AU2016323147A1/en not_active Abandoned
  • 2016-09-15 IL IL258095A patent/IL258095B/en unknown
  • 2016-09-15 WO PCT/US2016/051834 patent/WO2017048896A1/en not_active Ceased
  • 2016-09-15 JP JP2018534774A patent/JP2018534884A/ja active Pending
• 2021
  • 2021-03-18 AU AU2021201714A patent/AU2021201714B2/en active Active
  • 2021-10-28 JP JP2021176856A patent/JP2022023942A/ja active Pending
• 2023
  • 2023-06-02 JP JP2023091525A patent/JP2023116573A/ja active Pending

Patent Citations (7)

Also Published As

Similar Documents

Legal Events