# US 2021/0281401 A1 · Methods, systems, and computer readable media for utilizing predetermined encryption keys in a test simulation environment

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2021/0281401 A1
- Document ID: US20210281401A1
- Status: Published application
- Kind: A1
- Application number: 17/329,033
- Filed: 2021-05-24
- Published: 2021-09-09
- Earliest claimed: 2013-08-28
- Assignees: Keysight Technologies Singapore (Sales) Pte. Ltd.
- Applicants: Keysight Technologies Singapore (Sales) Pte. Ltd.
- Inventors: Andrei Cipu; Alexandru Badea; George Ciobanu
- Web page: https://patentgrep.com/patent/US20210281401A1

## CPC

- H04L 9/0841: {involving Diffie-Hellman or related key agreement protocols}
- H04L 43/10: Active monitoring, e.g. heartbeat, ping or trace-route
- H04L 43/50: Testing arrangements
- H04L 63/061: {for key exchange, e.g. in peer-to-peer networks (cryptographic mechanisms or cryptographic arrangements for key agreement H04L9/0838)}
- H04L 63/164: {at the network layer}
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

Methods, systems, and computer readable media for utilizing predetermined encryption keys in a test simulation environment are disclosed. In one embodiment, a method includes generating, prior to an initiation of an Internet protocol security (IPsec) test session, a private key and a public key at a traffic emulation device and storing the private key and the public key in a local storage associated with the traffic emulation device. The method further includes retrieving, from the local storage, the private key and the public key upon the initiation of the IPsec test session between the traffic emulation device and a device under test (DUT) and generating a shared secret key utilizing the retrieved private key and a DUT public key received from the DUT.

## Claims

### Claim 1

A method for utilizing predetermined key exchange data in a test simulation environment, the method comprising:
prior to an initiation of a first test session, provisioning a device under test (DUT) with a first key exchange number that is known by both the DUT and a traffic emulation device configured to conduct the first test session, wherein the first test session is a test session involving a Diffie-Hellman key exchange;
generating, prior to the initiation of the first test session, a private key and a public key at the traffic emulation device, wherein the public key is generated by the traffic emulation device using a second key exchange number;
storing the private key and the public key in a local storage associated with the traffic emulation device, wherein the stored private key and the public key are mapped to the second exchange key number in the local storage;
retrieving, by the traffic emulation device from the local storage, the second exchange key number, the private key and the public key upon the initiation of the first test session between the traffic emulation device and the DUT;
providing the second exchange key number and the public key to the DUT, wherein the DUT utilizes the second exchange key number and the previously provisioned first exchange key number to generate a DUT public key;
generating, by the traffic emulation device, a shared secret key utilizing the retrieved private key and the DUT public key generated by and received from the DUT; and
retrieving, by the traffic emulation device, the private key and the public key from the local memory upon an initiation of a second test session between the traffic emulation device and the DUT and generating a second shared secret key utilizing the retrieved private key and a second DUT public key generated by and received from the DUT, wherein the second test session is a test session involving a Diffie-Hellman key exchange.

### Claim 2 (depends on 1)

The method of claim 1 comprising determining, prior to generating the public key, at least one key exchange number.

### Claim 3 (depends on 2)

The method of claim 2 wherein generating the public key includes deriving the public key using the at least one key exchange number.

### Claim 4 (depends on 3)

The method of claim 3 comprising sending the public key and the at least one key exchange number to the DUT.

### Claim 5 (depends on 1)

The method of claim 1 comprising receiving the DUT public key from the DUT upon the initiation of the first test session.

### Claim 6 (depends on 1)

The method of claim 1 wherein the traffic emulation device functions as either a client entity or a server entity.

### Claim 7 (depends on 1)

The method of claim 1 wherein the public key is generated using the private key and the at least one key exchange number.

### Claim 8 (depends on 1)

The method of claim 1 wherein each of the private key, the public key, and the shared secret key is generated utilizing a Diffie-Hellman method.

### Claim 9 (depends on 1)

The method of claim 1 wherein the DUT includes at least one of: a firewall device, a router device, and a serving gateway (SGW), a packet data network gateway (PGW).

### Claim 10

A system for utilizing predetermined encryption keys data in a test simulation environment, the system comprising:
a device under test (DUT) configured to generate a DUT public key and to be subjected to a first test session, wherein the first test session is a test session involving a Diffie-Hellman key exchange; and
a traffic emulation device configured to provision, prior to an initiation of the first test session, the DUT with a first key exchange number that is known by both the DUT and the traffic emulation device, to generate, prior to the initiation of the first test session with the DUT, a private key and a public key, wherein the public key is generated by the traffic emulation device using a second key exchange number, to store the private key and the public key in a local storage, wherein the private key and the stored public key are mapped to the second exchange key number in the local storage, to retrieve the second exchange key number, the private key and the public key from the local storage upon the initiation of the first test session, to provide the second exchange key number and the public key to the DUT, wherein the DUT utilizes the second exchange key number and the previously provisioned first exchange key number to generate a DUT public key, to generate a shared secret key utilizing the retrieved private key and the DUT public key generated by and received from the DUT, to retrieve the private key and the public key from the local memory upon an initiation of a second test session between the traffic emulation device and the DUT wherein the second test session is a test session involving a Diffie-Hellman key exchange, and to generate a second shared secret key utilizing the retrieved private key and a second DUT public key generated by and received from the DUT.

### Claim 11 (depends on 10)

The system of claim 10 wherein the traffic emulation device is further configured to determine, prior to generating the public key, at least one key exchange number.

### Claim 12 (depends on 11)

The system of claim 11 wherein the traffic emulation device is further configured to derive the public key using the at least one key exchange number.

### Claim 13 (depends on 12)

The system of claim 12 wherein the traffic emulation device is further configured to send the public key and the at least one key exchange number to the DUT.

### Claim 14 (depends on 10)

The system of claim 10 wherein the traffic emulation device is further configured to receive the DUT public key from the DUT upon the initiation of the first test session.

### Claim 15 (depends on 10)

The system of claim 10 wherein the traffic emulation device functions as either a client entity or a server entity.

### Claim 16 (depends on 10)

The system of claim 10 wherein the public key is generated using the private key and the at least one key exchange number.

### Claim 17 (depends on 10)

The system of claim 10 wherein each of the private key, the public key, and the shared secret key is generated utilizing a Diffie-Hellman method.

### Claim 18 (depends on 10)

The system of claim 10 wherein the DUT includes at least one of: a firewall device, a router device, and a serving gateway (SGW), a packet data network gateway (PGW).

### Claim 19

A non-transitory computer readable medium having stored thereon executable instructions that when executed by the processor of a computer control the computer to perform steps comprising:
prior to an initiation of a first test session, provisioning a device under test (DUT) with a first key exchange number that is known by both the DUT and a traffic emulation device configured to conduct the first test session, wherein the first test session is a test session involving a Diffie-Hellman key exchange;
generating, prior to the initiation of the first test session, a private key and a public key at the traffic emulation device, wherein the public key is generated by the traffic emulation device using a second key exchange number;
storing the private key and the public key in a local storage associated with the traffic emulation device, wherein the stored private key and the public key are mapped to the second exchange key number in the local storage;
retrieving, by the traffic emulation device from the local storage, the second exchange key number, the private key and the public key upon the initiation of the first test session between the traffic emulation device and the DUT;
providing the second exchange key number and the public key to the DUT, wherein the DUT utilizes the second exchange key number and the previously provisioned first exchange key number to generate a DUT public key;
generating, by the traffic emulation device, a shared secret key utilizing the retrieved private key and the DUT public key generated by and received from the DUT; and
retrieving, by the traffic emulation device, the private key and the public key from the local memory upon an initiation of a second test session between the traffic emulation device and the DUT and generating a second shared secret key utilizing the retrieved private key and a second DUT public key generated by and received from the DUT, wherein the second test session is a test session involving a Diffie-Hellman key exchange.

### Claim 20 (depends on 19)

The non-transitory computer readable medium of claim 19 wherein the traffic emulation device is further configured to determine, prior to generating the public key, at least one key exchange number.
