Facilitating lossless secure key rollover using data plane feedback

By sending messages when the new security key is installed, ensuring that the receiving and transmitting keys are installed on the protocol hardware, the problem of business loss during key flip is solved, and lossless key flip and resource conservation are achieved.

CN113630242BActive Publication Date: 2024-11-19HEWLETT PACKARD ENTERPRISE DEV LP
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202010803683.X
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Priority Date
2020-06-22
Filing Date
2020-08-11
Publication Date
2024-11-19
Estimated Expiration
2040-08-11

AI Technical Summary

Technical Problem

During the existing key flip process, the network device may send a message before the new security key is installed, causing the peer network device to not complete the receiving key installation, resulting in the loss of services and may consume computing resources to retransmit services.

Method used

By sending messages when the new security key is installed, ensure that the receiving key and the transmission key are installed on the protocol hardware before message acknowledging, avoiding business loss and without resetting the session or interrupting the security protocol Perform key flip.

Benefits of technology

Lossless security key flip is realized, which eliminates business loss, improves the overall predictability and stability of key servers and peer network devices, and reduces resource consumption.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN113630242B_ABST
    Figure CN113630242B_ABST
Patent Text Reader

Abstract

The first network device may install a reception key for decrypting a service on protocol hardware associated with a data plane of the first network device. The first network device may receive a first notification from the data plane indicating that the reception key is installed on the protocol hardware, and may provide a first message identifying the reception key to the second network device. The first network device may receive a confirmation message from the second network device indicating that the reception key is installed on the second network device, and may install a transmission key for encrypting the service on the protocol hardware. The first network device may receive a second notification from the data plane indicating that the transmission key is installed on the protocol hardware, and may provide a second message identifying the transmission key to the second network device.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to Indian Provisional Application No. 202041019240, filed on May 6, 2020, entitled “FACILITATING HITLESS SECURITY KEYROLLOVER”. The entire contents of that application are expressly incorporated herein by reference. Background Art

[0003] Media Access Control Security (MACsec) is a security standard defined by the Institute of Electrical and Electronics Engineers (IEEE) 802.1AE that specifies connectionless data confidentiality and integrity for media access independent protocols. The MACsec standard specifies a set of protocols to meet the security requirements for protecting data traversing Ethernet local area networks (LANs). MACsec defines a security infrastructure to provide data confidentiality, data integrity, and data origin authentication. Summary of the invention

[0004] According to some implementations, a method may include: receiving, by a first network device, encrypted data identifying a receive key for decrypting a service and a transport key for encrypting the service; installing, by the first network device, the receive key on protocol hardware associated with a data plane of the first network device; receiving a first notification from the data plane of the first network device, the first notification indicating that the receive key is installed on the protocol hardware; providing, by the first network device, a first key agreement control message identifying the receive key to a second network device, wherein the first key agreement control message is provided based on receiving the first notification; receiving, by the first network device, a confirmation message from the second network device, the confirmation message indicating that the receive key is installed on the second network device; installing, by the first network device, the transport key on the protocol hardware based on receiving the confirmation message; receiving a second notification from the data plane of the first network device, the second notification indicating that the transport key is installed on the protocol hardware; and providing, by the first network device, a second key agreement control message identifying the transport key to the second network device, wherein the second key agreement control message is provided based on receiving the second notification.

[0005] According to some implementations, a first network device may include one or more memories; and one or more processors for: receiving encrypted data identifying: a first key for decrypting a service; and a second key for encrypting the service; installing the first key on protocol hardware associated with a data plane of the first network device; receiving a first notification from the data plane indicating that the first key is installed on the protocol hardware; providing a first key agreement control message identifying the first key to a second network device, wherein the first key agreement control message is provided based on receiving the first notification; receiving a first confirmation message from the second network device, wherein the first confirmation message indicates that the first key is installed on the second network device; installing the second key on the protocol hardware based on receiving the first confirmation message; receiving a second notification from the data plane indicating that the second key is installed on the protocol hardware; providing a second key agreement control message identifying the second key to the second network device, wherein the second key agreement control message is provided based on receiving the second notification; and receiving a second confirmation message from the second network device, wherein the second confirmation message indicates that the second key is installed on the second network device.

[0006] According to some implementations, a non-transitory computer-readable medium may store one or more instructions. When the one or more instructions are executed by one or more processors of a first network device, the one or more processors are caused to: receive encrypted data identifying a receive key for decrypting a service and a transport key for encrypting the service; install the receive key on protocol hardware associated with a data plane of the first network device; receive a first notification from the data plane indicating that the receive key is installed on the protocol hardware; provide a first key agreement control message identifying the receive key to a second network device, wherein the first key agreement control message is provided based on receiving the first notification; receive a first confirmation message from the second network device, wherein the first confirmation message indicates that the receive key is installed on the second network device; install the transport key on the protocol hardware based on receiving the first confirmation message; receive a second notification from the data plane indicating that the transport key is installed on the protocol hardware; provide a second key agreement control message identifying the transport key to the second network device, wherein the second key agreement control message is provided based on receiving the second notification; receive a second confirmation message from the second network device, wherein the second confirmation message indicates that the transport key is installed on the second network device. Based on receiving the first confirmation message, encrypting the traffic using the transmission key and generating encrypted traffic; and providing the encrypted traffic to the second network device so that the second network device decrypts the encrypted traffic using the reception key. BRIEF DESCRIPTION OF THE DRAWINGS

[0007] Figures 1A to 1J is a schematic diagram of an example implementation described in this article.

[0008] Figure 2 is a schematic diagram of an example environment in which the systems and / or methods described herein may be implemented.

[0009] Figure 3 to Figure 4 yes Figure 2 A schematic diagram of example components of one or more devices.

[0010] Figures 5 to 7 is a flow chart of an example process for facilitating lossless secure key rollover. DETAILED DESCRIPTION

[0011] The following is a detailed description of example implementations with reference to the accompanying drawings.The same reference numbers in different drawings may identify the same or similar elements.

[0012] Various security protocols, such as the Media Access Control Security (MACsec) protocol, the Internet Protocol Security (IPsec) protocol, and / or similar protocols, are used for secure communications between network devices. In one example, during the use of the MACsec protocol, security keys (e.g., including transmission keys, reception keys, and / or the like) are created and maintained between communication network devices for use in encrypting and decrypting services (e.g., network services transmitted between network devices via a MACsec communication link). For example, a transmitting network device may use a transmission key to encrypt and send services to a receiving network device, which uses a reception key to decrypt the services. Security keys need to be changed from time to time to ensure that the MACsec communication link between communication network devices remains secure. This may be referred to as key rollover (e.g., when a network device installs and / or uses a new security key).

[0013] To facilitate key rollover, the key server network device initiates (e.g., using a protocol daemon in a control plane of the key server network device) installation of a new receive key on the key server network device (e.g., in a data plane of the key server network device) and sends the receive key to the peer network device, which initiates (e.g., using a protocol daemon in a control plane of the peer network device) installation of the new receive key on the peer network device (e.g., in a data plane of the peer network device). The peer network device then sends (e.g., using a protocol daemon in a control plane of the peer network device) a first confirmation to the key server network device, the first confirmation indicating that the peer network device has initiated installation of the receive key. The key server network device initiates (e.g., using a protocol daemon in a key server network device) installation of a new transport key on the key server network device (e.g., in a data plane of the key server network device) based on receiving the first confirmation. Accordingly, after installing the new transport key on the key server network device, the key server network device encrypts traffic using the new transport key and sends traffic to the peer network device for decryption using the new receive key. In addition, the key server network device sends the transport key to the peer network device, and the peer network device initiates (e.g., using a protocol daemon of the peer network device) installation of the new transport key on the peer network device (e.g., in a data plane of the peer network device). The peer network device then sends (e.g., using a protocol daemon of the peer network device) a second confirmation to the key server network device, the second confirmation indicating that the peer network device has initiated installation of the new transport key.

[0014] However, the above scheme relies on sending a message when the installation of the new security key has been initiated (rather than when the installation of the new security key is completed). Therefore, when the key server network device begins to transmit traffic that has been encrypted using the new transmission key to the peer network device (and the traffic can only be decrypted using the new reception key), the peer network device may not have completed the installation of the new reception key. This may be because the peer network device encounters processing or scheduling delays associated with other activities involving the data plane of the peer network device, so the installation of the reception key has not yet occurred. Therefore, the peer network device may receive traffic that the peer network device cannot decrypt (e.g., because the peer network device has not yet completed the installation of the new reception key), resulting in lost traffic. In addition, due to the loss of traffic, the key server network device, the peer network device and / or the like may consume computing resources (e.g., processing resources, memory resources, power resources and / or the like) to retransmit the traffic from the key server network device to the peer network device (e.g., after the peer network device has completed the installation of the reception key).

[0015] Some implementations described herein provide a key server network device and a peer network device that sends a message when the installation of a new security key is completed. In some implementations, a protocol daemon of a control plane of the key server network device can communicate with a data plane daemon of a data plane of the key server network device to install a received key on the data plane of the key server network device. After completing the installation of the received key, the data plane daemon can notify the protocol daemon that the received key is installed, thereby allowing the protocol daemon to send a first key agreement control message including the received key to the peer network device. The protocol daemon of the control plane of the peer network device can communicate with the data plane daemon of the data plane of the peer network device based on the first key agreement control message to install the received key on the data plane of the peer network device. After the installation of the received key is completed, the data plane daemon can notify the protocol daemon that the received key is installed, thereby allowing the protocol daemon to send a first confirmation message to the key server network device indicating that the received key has been installed on the peer network device.

[0016] In some implementations, the protocol daemon of the key server network device may communicate with the data plane daemon of the key server network device based on receiving the first confirmation message to install the transport key on the data plane of the key server network device. After the transport key installation is completed, the data plane daemon may notify the protocol daemon that the transport key is installed. Accordingly, the key server network device may encrypt the traffic received from the originating endpoint device using the transport key and based on receiving the first confirmation message, and may provide the encrypted traffic to the peer network device. The peer network device may decrypt the encrypted traffic using the received key and may send the traffic to the destination endpoint device.

[0017] Additionally or alternatively, after the installation of the transport key is complete and the protocol daemon has been notified that the transport key is installed, the protocol daemon may send a second key agreement control message including the transport key to the peer network device. The protocol daemon of the peer network device may communicate with the data plane daemon of the peer network device based on the second key agreement control message to install the transport key on the data plane of the peer network device. After the installation of the transport key is complete, the data plane daemon may notify the protocol daemon that the transport key is installed, which allows the protocol daemon to send a second confirmation message to the key server network device indicating that the transport key is installed on the peer network device.

[0018] In this manner, the key server network device and / or the peer network device can facilitate lossless rollover of security keys (e.g., security key rollover that eliminates traffic loss, which is also referred to as zero packet loss). This can eliminate the need to consume computing resources (e.g., processing resources, memory resources, power resources, and / or the like) to retransmit traffic from the key server network device to the peer network device. In addition, some implementations described herein provide key rollover without resetting peer sessions (e.g., MACsec sessions, IPsec sessions, and / or the like) associated with the key server network device and / or the peer network device; without interrupting security protocols (e.g., MACsec protocols, IPsec protocols, and / or the like) associated with the key server network device and / or the peer network device; and / or the like. In addition, some implementations described herein increase the overall predictability and / or stability of the key server network device and / or the peer network device, which can improve the performance of the key server network device and / or the peer network device.

[0019] Figures 1A to 1J is a schematic diagram of one or more examples 100 associated with facilitating lossless security key rollover. Figures 1A to 1J As shown, the example(s) 100 include a plurality of endpoint devices and a plurality of network devices. Figure 1A As shown, a plurality of network devices may be included in the network, and may include a key server network device and one or more peer network devices. The plurality of endpoint devices may communicate with each other via the network including the plurality of network devices.

[0020] like Figure 1B to Figure 1I As shown, each network device may be associated with a control plane (also referred to as a protocol layer) and a data plane. The control plane of the network device may include a protocol daemon (e.g., a process or program) that runs in the background of the control plane of the network device to control the installation of one or more security keys on the network device and / or communicate with other network devices to exchange one or more security keys. The data plane of the network device may include a data plane daemon and protocol hardware (e.g., hardware for receiving services, forwarding services, encrypting services, decrypting services, and / or the like). The data plane daemon (e.g., a process or program) may run in the background of the data plane of the network device to obtain one or more security keys from the protocol daemon of the control plane and install one or more security keys on the protocol hardware (e.g., allowing the network device to encrypt and / or decrypt services based on one or more security keys). The network device, protocol daemon, data plane daemon, protocol hardware, and / or the like may be associated with security protocols, such as media access control security (MACsec) protocols, Internet protocol security (IPsec) protocols, and / or the like.

[0021] like Figure 1B As shown, by reference numeral 105, a protocol daemon of a key server network device may receive encrypted data (e.g., from an endpoint device of a plurality of endpoint devices, another network device of a plurality of network devices, and / or the like). The encrypted data may identify one or more security keys (e.g., one or more MACsec keys, one or more IPsec keys, and / or the like). In some implementations, the encrypted data may identify a receive key for decrypting traffic and / or a transport key for encrypting traffic.

[0022] In some implementations, the protocol daemon may receive the encrypted data at some time as a specific amount of time after receiving previously encrypted data (e.g., including one or more previously secure keys, such as previously received keys, previously transmitted keys, and / or the like). For example, the protocol daemon of the key server may receive the encrypted data within 10 seconds, 30 seconds, 1 minute, 10 minutes, and / or the like after receiving the previously encrypted data. Alternatively or additionally, the protocol daemon may receive the encrypted data after processing a specific number of packets using one or more previously secure keys (e.g., after encrypting and / or decrypting a specific number of packets using one or more previously secure keys). For example, the protocol daemon may receive the encrypted data after processing 1,000 packets, 10,000 packets, 25,000 packets, and / or the like using one or more previously secure keys.

[0023] In some implementations, the protocol daemon may communicate with the data plane daemon of the key server network device to cause the receive key to be installed on the data plane of the key server network device. For example, the protocol daemon may send a request to the data plane daemon to install the receive key. As shown by reference numeral 110, the data plane daemon may install (or cause to be installed) the receive key on the protocol hardware of the key server network device (e.g., based on the request from the protocol daemon). For example, the data plane daemon may program the receive key into the protocol hardware.

[0024] like Figure 1C As shown, the data plane daemon process can determine that the installation of the receiving key on the protocol hardware is completed. For example, after the installation of the receiving key on the protocol hardware is completed, the protocol hardware can send a message indicating that the installation of the receiving key on the protocol hardware is completed to the data plane daemon process.

[0025] As shown at reference numeral 115, the data plane daemon may send a notification to the protocol daemon indicating that the received key is installed on the protocol hardware (e.g., based on determining that the installation of the received key on the protocol hardware is complete). As shown at reference numeral 120, the protocol daemon may provide (e.g., send, transmit, forward, and / or the like) a first key agreement control message to the peer network device (e.g., based on receiving the notification indicating that the received key is installed on the protocol hardware). The first key agreement control message may identify the received key (e.g., allow the received key to be installed on the peer network device).

[0026] like Figure 1D As shown and indicated by reference numeral 125, a protocol daemon of a peer network device may receive a first key agreement control message (e.g., sent by a protocol daemon of a key server network device to a peer network device). In some implementations, the protocol daemon may communicate with a data plane daemon of the peer network device to cause the received key to be installed on a data plane of the peer network device. For example, the protocol daemon may send a request to the data plane daemon to install the received key.

[0027] As shown at reference numeral 130, the data plane daemon may install (or cause to be installed) a receive key on the protocol hardware of the peer network device (e.g., based on a request from the protocol daemon). For example, the data plane daemon may program the receive key into the protocol hardware.

[0028] like Figure 1E As shown, the data plane daemon can determine that the installation of the receiving key on the protocol hardware is complete. For example, the protocol hardware can send a message indicating that the installation of the receiving key on the protocol hardware is complete to the data plane daemon when the installation of the receiving key on the protocol hardware is complete.

[0029] As shown at reference numeral 135, the data plane daemon may send a notification to the protocol daemon indicating that the received key is installed on the protocol hardware (e.g., based on determining that the installation of the received key on the protocol hardware is complete). As shown at reference numeral 140, the protocol daemon may provide (e.g., send, transmit, forward, and / or the like) a first confirmation message to the key server network device (e.g., based on receiving the notification indicating that the received key is installed on the protocol hardware). The first confirmation message may indicate that the received key is installed on the peer network device.

[0030] like Figure 1FAs shown and indicated by reference numeral 145, the protocol daemon of the key server network device may receive a first confirmation message (e.g., sent by the protocol daemon of the peer network device to the key server network device). In some implementations, the protocol daemon may communicate with the data plane daemon of the key server network device to transmit the transmission key (e.g., identified in the encrypted data received by the protocol daemon, as described herein with respect to Figure 1B The protocol daemon may send a request to the data plane daemon to install the transport key.

[0031] As shown at 150, the data plane daemon may install (or cause to be installed) a transport key on the protocol hardware of the key server network device (e.g., based on a request from the protocol daemon). For example, the data plane daemon may program the transport key into the protocol hardware.

[0032] like Figure 1G As shown, the data plane daemon can determine that the installation of the transport key on the protocol hardware is complete. For example, the protocol hardware can send a message indicating the installation of the transport key on the protocol hardware to the data plane daemon when the installation of the transport key on the protocol hardware is complete.

[0033] As shown at reference numeral 155, the data plane daemon may send a notification to the protocol daemon indicating that the transport key is installed on the protocol hardware (e.g., based on determining that the transport key is installed on the protocol hardware). As shown at reference numeral 160, the protocol daemon may provide (e.g., send, transmit, forward, and / or the like) a second key agreement control message to the peer network device (e.g., based on receiving a notification indicating that the transport key is installed on the protocol hardware). The second key agreement control message may identify the transport key (e.g., allowing the transport key to be installed on the peer network device).

[0034] like Figure 1H As shown and indicated by reference numeral 165, the protocol daemon of the peer network device may receive a second key agreement control message (e.g., sent by the protocol daemon of the key server network device to the peer network device). In some implementations, the protocol daemon may communicate with the data plane daemon of the peer network device to cause the transport key to be installed on the data plane of the peer network device. For example, the protocol daemon may send a request to the data plane daemon to install the transport key.

[0035] As shown at reference numeral 170, the data plane daemon may install (or cause to be installed) a transport key on the protocol hardware of the peer network device (e.g., based on a request from the protocol daemon). For example, the data plane daemon may program the transport key into the protocol hardware.

[0036] like Fig. 1I As shown, the data plane daemon can determine that the installation of the transport key on the protocol hardware is complete. For example, the protocol hardware can send a message indicating that the installation of the transport key on the protocol hardware is complete to the data plane daemon when the installation of the transport key on the protocol hardware is complete.

[0037] As shown at reference numeral 175, the data plane daemon may send a notification to the protocol daemon indicating that the transport key has been installed on the protocol hardware (e.g., based on determining that installation of the transport key on the protocol hardware is complete). As shown at reference numeral 180, the protocol daemon may provide (e.g., send, transmit, forward, and / or the like) a second confirmation message to the key server network device (e.g., based on receiving a notification indicating that the transport key is installed on the protocol hardware). The second confirmation message may indicate that the transport key is installed on the peer network device.

[0038] like Figure 1J As shown, a first endpoint device (e.g., an originating endpoint device) among a plurality of endpoint devices may send traffic destined for a second endpoint device (e.g., a destination endpoint device) to a key server network device. As shown at reference numeral 185, the key server network device may encrypt the traffic based on receiving a first confirmation message (e.g., indicating that a receiving key is installed on a peer network device) and using a transmission key to generate encrypted traffic. As shown at reference numeral 190, the key server network device may provide (e.g., send, route, forward, and / or the like) the encrypted traffic to the peer network device. As shown at reference numeral 195, the peer network device may decrypt the encrypted traffic using the receiving key. In some implementations, the peer network device may send the traffic (e.g., after decrypting the traffic) to the second endpoint device.

[0039] As mentioned above, Figures 1A to 1J is provided as an example. Other examples may be relevant to Figures 1A to 1J The content described is different. Figures 1A to 1J The number and arrangement of devices shown are provided as examples. Figures 1A to 1J There may be additional devices, fewer devices, different devices, or differently arranged devices than those shown. Figures 1A to 1J Two or more of the devices shown may be implemented in a single device, or Figures 1A to 1JThe single device shown may be implemented as multiple, distributed devices. Additionally or alternatively, Figures 1A to 1J The set of devices (e.g., one or more devices) shown may perform the Figures 1A to 1J Another group of devices is shown performing one or more functions.

[0040] Figure 2 2 is a diagram of an example environment 200 in which the systems and / or methods described herein may be implemented. Figure 2 As shown, environment 200 may include one or more endpoint devices 210, one or more network devices 220 (shown as network device 220-1 through network device 220-N, where N≥1), and network 230. The devices of environment 200 may be interconnected via wired connections, wireless connections, or a combination of wired and wireless connections.

[0041] Endpoint device 210 includes one or more devices capable of receiving, generating, storing, processing, and / or providing information, such as the information described herein. For example, endpoint device 210 may include a mobile phone (e.g., a smartphone, a wireless phone, and / or a similar device), a laptop computer, a tablet computer, a desktop computer, a handheld computer, a gaming device, a wearable communication device (e.g., a smart watch, smart glasses, a heart rate monitor, a fitness tracker, smart clothing, smart jewelry, a head-mounted display, and / or a similar device), a network device, or a similar type of device. In some implementations, endpoint device 210 may receive network traffic from other endpoint devices 210 and / or provide network traffic to other endpoint devices 210 via network 230 (e.g., by routing packets using network device 220 as an intermediary).

[0042] The network device 220 includes one or more devices capable of receiving, processing, storing, routing and / or providing services (e.g., data packets, other information or metadata and / or the like) in the manner described herein. For example, the network device 220 may include a router, such as a label switching router (LSR), a label edge router (LER), an ingress router, an egress router, a provider router (e.g., a provider edge router, a provider core router and / or the like), a virtual router and / or the like. Additionally or alternatively, the network device 220 may include a gateway, a switch, a firewall, a hub, a bridge, a reverse proxy, a server (e.g., a proxy server, a cloud server, a data center server and / or the like), a load balancer and / or the like. In some implementations, the network device 220 may be a key server network device, a peer network device and / or the like.

[0043] In some implementations, network device 220 may be a physical device implemented in a housing such as a chassis. In some implementations, network device 220 may be a virtual device implemented by one or more computer devices in a cloud computing environment or data center. In some implementations, a group of network devices 220 may be a group of data center nodes that are used to route traffic flows through network 230.

[0044] The network 230 includes one or more wired and / or wireless networks. For example, the network 230 may include a cellular network (e.g., a fifth generation (5G) network, a fourth generation (4G) network, such as a long term evolution (LTE) network, a third generation (3G) network, a code division multiple access (CDMA) network, a public land mobile network (PLMN), a local area network (LAN), a wide area network (WAN), a metropolitan area network (MAN), a telephone network (e.g., a public switched telephone network (PSTN), a dedicated network, a temporary network, an intranet, the Internet, a fiber-optic-based network, a cloud computing network, or the like, and / or a combination of these or other types of networks.

[0045] Figure 2 The number and arrangement of devices and networks shown are provided as one or more examples. Figure 2 There may be additional devices and / or networks, fewer devices and / or networks, different devices and / or networks, or differently arranged devices and / or networks than those shown. Figure 2 Two or more of the devices shown may be implemented in a single device, or Figure 2 The single device shown may be implemented as multiple, distributed devices. Additionally, or alternatively, one set of devices (eg, one or more devices) of environment 200 may perform one or more functions described as being performed by another set of devices of environment 200.

[0046] Figure 3 300. Device 300 may correspond to endpoint device 210 and / or network device 220. In some implementations, endpoint device 210 and / or network device 220 may include one or more devices 300 and / or one or more components of device 300. Figure 3 As shown, device 300 may include a bus 310 , a processor 320 , a memory 330 , a storage component 340 , an input component 350 , an output component 360 , and a communication interface 370 .

[0047] The bus 310 includes components that allow communication between components of the device 300. The processor 320 is implemented in hardware, firmware, or a combination of hardware and software. The processor 320 is a central processing unit (CPU), a graphics processing unit (GPU), an accelerated processing unit (APU), a microprocessor, a microcontroller, a digital signal processor (DSP), a field programmable gate array (FPGA), an application-specific integrated circuit (ASIC), or other types of processing components. In some implementations, the processor 320 includes one or more processors that can be programmed to perform functions. The memory 330 includes a random access memory (RAM), a read-only memory (ROM), and / or another type of dynamic or static storage device (e.g., flash memory, magnetic memory, and / or optical memory) that stores information and / or instructions for use by the processor 320.

[0048] Storage component 340 stores information and / or software related to the operation and use of device 300. For example, storage component 340 may include a hard disk (e.g., a magnetic disk, an optical disk, a magneto-optical disk, and / or a solid-state disk), a compact disk (CD), a digital versatile disk (DVD), a floppy disk, a cassette, a magnetic tape, and / or another type of non-transitory computer-readable medium, and a corresponding drive.

[0049] Input components 350 include components that allow device 300 to receive information, such as via user input (e.g., a touch screen display, a keyboard, a keypad, a mouse, buttons, switches, and / or a microphone). Additionally or alternatively, input components 350 may include sensors for sensing information (e.g., a global positioning system (GPS) component, an accelerometer, a gyroscope, and / or an actuator). Output components 360 include components that provide output information from device 300 (e.g., a display, a speaker, and / or one or more LEDs).

[0050] The communication interface 370 includes a transceiver-like component (e.g., a transceiver and / or a separate receiver and transmitter) that allows the device 300 to communicate with other devices, such as via a wired connection, a wireless connection, or a combination of wired and wireless connections. The communication interface 370 may allow the device 300 to receive information from another device and / or provide information to another device. For example, the communication interface 370 may include an Ethernet interface, an optical interface, a coaxial interface, an infrared interface, a radio frequency interface, a universal serial bus (USB) interface, a wireless local area network interface, a cellular network interface, and / or the like.

[0051] Device 300 may perform one or more processes described herein. Device 300 may perform these processes based on processor 320 executing software instructions stored by non-transitory computer-readable media such as memory 330 and / or storage component 340. Computer-readable media is defined herein as non-transitory memory devices. Memory devices include memory space within a single physical storage device or memory space distributed across multiple physical storage devices.

[0052] The software instructions may be read into the memory 330 and / or storage component 340 from another computer-readable medium or from another device via the communication interface 370. When executed, the software instructions stored in the memory 330 and / or storage component 340 may cause the processor 320 to perform one or more processes described herein. Additionally or alternatively, hardwired circuitry may be used in place of or in combination with software instructions to perform one or more processes described herein. Thus, the implementations described herein are not limited to any specific combination of hardware circuitry and software.

[0053] Figure 3 The number and arrangement of components shown are provided as an example. In practice, Figure 3 The device 300 may include additional components, fewer components, different components, or components arranged differently than the components shown. Additionally, or alternatively, a set of components (e.g., one or more components) of the device 300 may perform one or more functions that are performed by another set of components of the device 300.

[0054] Figure 4 4 is a diagram of example components of device 400. Device 400 may correspond to endpoint device 210 and / or network device 220. In some implementations, endpoint device 210 and / or network device 220 may include one or more devices 400 and / or one or more components of device 400. Figure 4 As shown, the device 400 may include one or more input components 410-1 to 410-A (A≥1) (hereinafter collectively referred to as input component 410, and individually referred to as input component 410), a switching component 420, one or more output components 430-1 to 430-B (B≥1) (hereinafter collectively referred to as output component 430, and individually referred to as output component 430) and a controller 440.

[0055] The input component 410 can be one or more attachment points of a physical link and can be one or more entry points for incoming traffic (e.g., data packets). The input component 410 can process incoming traffic, such as by performing data link layer encapsulation or decapsulation. In some implementations, the input component 410 can send and / or receive data packets. In some implementations, the input component 410 can include an input line card that includes one or more packet processing components (e.g., in the form of an integrated circuit), such as one or more interface cards (IFCs), packet forwarding components, line card controller components, input ports, processors, memories, and / or input queues. In some implementations, the device 400 can include one or more input components 410.

[0056] The switch component 420 may interconnect the input component 410 and the output component 430. In some implementations, the switch component 420 may be implemented via one or more crossbars, via a bus, and / or via a shared memory. The shared memory may serve as a temporary buffer to store data packets from the input component 410 before the data packets are ultimately scheduled for delivery to the output component 430. In some implementations, the switch component 420 may enable the input component 410, the output component 430, and / or the controller 440 to communicate with each other.

[0057] The output component 430 can store data packets and can schedule data packets for transmission on an output physical link. The output component 430 can support data link layer encapsulation or decapsulation, and / or various higher-level protocols. In some implementations, the output component 430 can transmit data packets and / or receive data packets. In some implementations, the output component 430 may include an output line card, which includes one or more packet processing components (e.g., in the form of an integrated circuit), such as one or more IFCs, packet forwarding components, line card controller components, output ports, processors, memories, and / or output queues. In some implementations, the device 400 may include one or more output components 430. In some implementations, the input component 410 and the output component 430 can be implemented by the same set of components (e.g., the input / output component can be a combination of the input component 410 and the output component 430).

[0058] The controller 440 includes a processor in the form of, for example, a CPU, a GPU, an APU, a microprocessor, a microcontroller, a DSP, an FPGA, an ASIC, and / or another type of processor. The processor is implemented in hardware, firmware, or a combination of hardware and software. In some implementations, the controller 440 may include one or more processors that can be programmed to perform functions.

[0059] In some implementations, the controller 440 may include RAM, ROM, and / or another type of dynamic or static storage device (eg, flash memory, magnetic storage, optical storage, etc.) that stores information and / or instructions for use by the controller 440 .

[0060] In some implementations, the controller 440 can communicate with other devices, networks, and / or systems connected to the device 400 to exchange information about the network topology. The controller 440 can create a routing table based on the network topology information, can create a forwarding table based on the routing table, and can forward the forwarding table to the input component 410 and / or the output component 430. The input component 410 and / or the output component 430 can use the forwarding table to perform routing lookups for incoming and / or outgoing data packets.

[0061] The controller 440 may perform one or more processes described herein. The controller 440 may perform these processes in response to executing software instructions stored by a non-transitory computer readable medium. A computer readable medium is defined herein as a non-transitory memory device. A memory device includes memory space within a single physical memory device or memory space distributed across multiple physical memory devices.

[0062] The software instructions may be read into a memory and / or storage component associated with the controller 440 from another computer-readable medium or from another device via a communication interface. When executed, the software instructions stored in the memory and / or storage component associated with the controller 440 may cause the controller 440 to perform one or more processes described herein. Additionally or alternatively, hardwired circuitry may be used in place of or in combination with software instructions to perform one or more processes described herein. Thus, the implementations described herein are not limited to any specific combination of hardware circuitry and software.

[0063] Figure 4 The number and arrangement of components shown are provided as an example. In practice, Figure 4 The device 400 may include additional components, fewer components, different components, or components in a different arrangement than the components shown. Additionally or alternatively, a set of components (e.g., one or more components) of the device 400 may perform one or more functions performed by another set of components of the device 400.

[0064] Figure 5 is a flow chart of an example process 500 associated with facilitating lossless security key rollover. In some implementations, Figure 5 One or more process blocks of may be performed by a first network device (e.g., network device 220). In some implementations, Figure 5One or more process blocks of may be performed by another device or group of devices separate from or including the first network device, such as an endpoint device (such as endpoint device 210) and / or the like. Additionally or alternatively, Figure 5 One or more process blocks may be performed by one or more components of device 300, such as processor 320, memory 330, storage component 340, input component 350, output component 360, communication interface 370, and / or the like; and / or the like; one or more components of device 400, such as input component 410, switching component 420, output component 430, controller 440, and / or the like; and / or the like.

[0065] like Figure 5 As shown, process 500 may include receiving encrypted data, the encrypted data identifying a receiving key for decrypting a service, and a transmission key for encrypting the service (block 510). For example, as described above, a first network device may receive encrypted data, the encrypted data identifying a receiving key for decrypting a service, and a transmission key for encrypting the service.

[0066] like Figure 5 As further shown, process 500 may include installing the received key on protocol hardware associated with the data plane of the first network device (block 520). For example, as described above, the first network device may install the received key on protocol hardware associated with the data plane of the first network device.

[0067] like Figure 5 As further shown, process 500 may include receiving a first notification from a data plane of the first network device indicating that a reception key is installed on the protocol hardware (block 530). For example, as described above, the first network device may receive a first notification from the data plane of the first network device indicating that a reception key is installed on the protocol hardware.

[0068] like Figure 5 As further shown, process 500 may include providing a first key agreement control message identifying the received key to the second network device, wherein the first key agreement control message is provided based on receiving the first notification (block 540). For example, as described above, the first network device may provide the first key agreement control message identifying the received key to the second network device. In some implementations, the first key agreement control message is provided based on receiving the first notification.

[0069] like Figure 5As further shown, process 500 may include receiving a confirmation message from the second network device indicating that the reception key is installed on the second network device (block 550). For example, as described above, the first network device may receive a confirmation message from the second network device indicating that the reception key is installed on the second network device.

[0070] like Figure 5 As further shown, process 500 may include installing the transport key on the protocol hardware based on receiving the confirmation message (block 560). For example, as described above, the first network device may install the transport key on the protocol hardware based on receiving the confirmation message.

[0071] like Figure 5 As further shown, process 500 may include receiving a second notification from the data plane of the first network device indicating that the transport key is installed on the protocol hardware (block 570). For example, as described above, the first network device may receive a second notification from the data plane of the first network device indicating that the transport key is installed on the protocol hardware.

[0072] like Figure 5 As further shown, process 500 may include providing a second key agreement control message identifying the transmission key to the second network device, wherein the second key agreement control message is provided based on receiving the second notification (block 580). For example, as described above, the first network device may provide the second key agreement control message identifying the transmission key to the second network device. In some implementations, the second key agreement control message is provided based on receiving the second notification.

[0073] Process 500 may include additional implementations, such as any single implementation or any combination of implementations described below and / or in association with one or more other processes described elsewhere herein.

[0074] In a first implementation, the confirmation message is based on an additional notification received by the second network device from a data plane of the second network device, the additional notification indicating that the received key is installed on protocol hardware associated with the data plane of the second network device.

[0075] In a second implementation, alone or in combination with the first implementation, process 500 includes encrypting the traffic with a transmission key based on the received confirmation information, generating encrypted traffic, and providing the encrypted traffic to the second network device so that the second network device decrypts the encrypted traffic with a reception key.

[0076] In a third implementation, alone or in combination with one or more of the first and second implementations, process 500 includes encrypting the traffic with a transmission key to generate encrypted traffic based on receiving another confirmation message, and providing the encrypted traffic to a second network device so that the second network device decrypts the encrypted traffic using a reception key.

[0077] In a fourth implementation, alone or in combination with one or more of the first to third implementations, the protocol hardware is associated with one of a media access control security protocol, or an internet protocol security protocol.

[0078] In a fifth implementation, alone or in combination with one or more of the first to fourth implementations, the first network device includes a key server network device and the second network device includes a peer network device.

[0079] In a sixth implementation, alone or in combination with one or more of the first to fifth implementations, the first notification and the second notification enable the first network device to provide security key rollover without causing service loss.

[0080] In a seventh implementation, alone or in combination with one or more of the first to sixth implementations, receiving encrypted data includes receiving encrypted data a specific time period after receiving a previous security key, the encrypted data identifying a receiving key and a transmitting key.

[0081] Although Figure 5 An example block diagram of process 500 is shown, but in some implementations, Figure 5 Process 500 may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in FIG. Additionally or alternatively, two or more blocks of process 500 may be performed in parallel.

[0082] Figure 6 is a flow chart of an example process 600 associated with facilitating lossless security key rollover. In some implementations, Figure 6 One or more process blocks of may be performed by a first network device (e.g., network device 220). In some implementations, Figure 6 One or more process blocks of may be performed by another device or group of devices separate from or including the first network device, such as an endpoint device (e.g., endpoint device 210) and / or the like. Additionally or alternatively, Figure 6One or more process blocks may be performed by one or more components of device 300, such as processor 320, memory 330, storage component 340, input component 350, output component 360, communication interface 370, and / or the like; and / or the like; one or more components of device 400, such as input component 410, switching component 420, output component 430, controller 440, and / or the like; and / or the like.

[0083] like Figure 6 As shown, process 600 may include receiving encrypted data identifying a first key and a second key (block 610), the first key being used to decrypt the service and the second key being used to encrypt the service. For example, as described above, a first network device may receive encrypted data identifying a first key and a second key, the first key being used to decrypt the service and the second key being used to encrypt the service.

[0084] like Figure 6 As further shown, process 600 may include installing the first key on protocol hardware associated with a data plane of the first network device (block 620). For example, as described above, the first network device may install the first key on protocol hardware associated with a data plane of the first network device.

[0085] like Figure 6 As further shown, process 600 may include receiving a first notification from a data plane indicating that a first key is installed on protocol hardware (block 630). For example, as described above, a first network device may receive a first notification from a data plane indicating that a first key is installed on protocol hardware.

[0086] like Figure 6 As further shown, process 600 may include providing a first key agreement control message identifying the first key to the second network device, wherein the first key agreement control message is provided based on receiving the first notification (block 640). For example, as described above, the first network device may provide the first key agreement control message identifying the first key to the second network device. In some implementations, the first key agreement control message is provided based on receiving the first notification.

[0087] like Figure 6 As further shown, process 600 may include receiving a first confirmation message from the second network device indicating that the first key is installed on the second network device (block 650). For example, as described above, the first network device may receive a first confirmation message from the second network device indicating that the first key is installed on the second network device.

[0088] like Figure 6As further shown, process 600 may include installing the second key on the protocol hardware based on receiving the first confirmation message (block 660). For example, as described above, the first network device may install the second key on the protocol hardware based on receiving the first confirmation message.

[0089] like Figure 6 As further shown, process 600 may include receiving a second notification from the data plane indicating that the second key is installed on the protocol hardware (block 670). For example, as described above, the first network device may receive a second notification from the data plane indicating that the second key is installed on the protocol hardware.

[0090] like Figure 6 As further shown in FIG. 6 , process 600 may include providing a second key agreement control message identifying the second key to the second network device, wherein the second key agreement control message is provided based on receiving the second notification (block 680). For example, as described above, the first network device may provide the second key agreement control message identifying the second key to the second network device. In some implementations, the second key agreement control message is provided based on receiving the second notification.

[0091] like Figure 6 As further shown, process 600 may include receiving a second confirmation message from the second network device indicating that the second key is installed on the second network device (block 690). For example, as described above, the first network device may receive a second confirmation message from the second network device indicating that the second key is installed on the second network device.

[0092] Process 600 may include additional implementations, such as any single implementation or any combination of implementations described below and / or in association with one or more other processes described elsewhere herein.

[0093] In a first implementation, receiving the encrypted data includes receiving the encrypted data identifying the first key and the second key after a number of packets have been processed with the previously secure key.

[0094] In a second implementation, either alone or in combination with the first implementation, the second network device is included in a plurality of peer network devices associated with the first network device, and process 600 includes receiving a plurality of confirmation messages from the plurality of peer network devices indicating that the first key is installed on each of the plurality of peer network devices, and encrypting traffic with a second key based on receiving the plurality of confirmation messages and generating encrypted traffic.

[0095] In a third implementation, either alone or in combination with one or more of the first and second implementations, process 600 includes providing encrypted traffic to one or more of the plurality of peer network devices so that the one or more of the plurality of peer network devices decrypt the encrypted traffic using a first key.

[0096] In a fourth implementation, alone or in combination with one or more of the first to third implementations, the first notification and the second notification enable the first network device to provide secure key rollover with zero packet loss.

[0097] In a fifth implementation, alone or in combination with one or more of the first to fourth implementations, installing the first key on the protocol hardware includes programming the first key into the protocol hardware.

[0098] In a sixth implementation, alone or in combination with one or more of the first to fifth implementations, installing the second key on the protocol hardware based on receiving the first confirmation message includes programming the second key into the protocol hardware after receiving the first confirmation message.

[0099] Although Figure 6 An example block diagram of process 600 is shown, but in some implementations, Figure 6 Process 600 may include additional blocks, fewer blocks, different blocks, or differently arranged blocks compared to the blocks depicted in FIG. Additionally or alternatively, two or more blocks of process 600 may be performed in parallel.

[0100] Figure 7 is a flow chart of an example process 700 associated with facilitating lossless security key rollover for a security key. In some implementations, Figure 7 One or more process blocks of may be performed by another device or group of devices separate from or including the first network device, such as an endpoint device (e.g., endpoint device 210) and / or the like. Additionally or alternatively, Figure 7 One or more process blocks may be performed by one or more components of device 300, such as processor 320, memory 330, storage component 340, input component 350, output component 360, communication interface 370, and / or the like; and / or the like; one or more components of device 400, such as input component 410, switching component 420, output component 430, controller 440, and / or the like; and / or the like.

[0101] like Figure 7As shown, process 700 may include receiving encrypted data, the encrypted data identifying a receiving key for decrypting the service and a transmission key for encrypting the service (block 705). For example, as described above, the first network device may receive encrypted data identifying a receiving key and a transmission key, the receiving key being used to decrypt the service and the transmission key being used to encrypt the service.

[0102] like Figure 7 As further shown, process 700 may include installing the received key on protocol hardware associated with a data plane of the first network device (block 710). For example, as described above, the first network device may install the received key on protocol hardware associated with a data plane of the first network device.

[0103] like Figure 7 As further shown, process 700 may include receiving a first notification from the data plane indicating that a reception key is installed on the protocol hardware (block 715). For example, as described above, the first network device may receive a first notification from the data plane indicating that a reception key is installed on the protocol hardware.

[0104] like Figure 7 As further shown, process 700 may include providing a first key agreement control message identifying the received key to the second network device, wherein the first key agreement control message is provided based on receiving the first notification (block 720). For example, as described above, the first network device may provide the first key agreement control message identifying the received key to the second network device. In some implementations, the first key agreement control message is provided based on receiving the first notification.

[0105] like Figure 7 As further shown, process 700 may include receiving a first confirmation message from the second network device indicating that the received key is installed on the second network device (block 725). For example, as described above, the first network device may receive a first confirmation message from the second network device indicating that the received key is installed on the second network device.

[0106] like Figure 7 As further shown, process 700 may include installing the transport key on the protocol hardware based on receiving the first confirmation message (block 730). For example, as described above, the first network device may install the transport key on the protocol hardware based on receiving the first confirmation message.

[0107] like Figure 7 As further shown, process 700 may include receiving a second notification from the data plane indicating that the transport key is installed on the protocol hardware (block 735). For example, as described above, the first network device may receive a second notification from the data plane indicating that the transport key is installed on the protocol hardware.

[0108] like Figure 7 As further shown, process 700 may include providing a second key agreement control message identifying the transmission key to the second network device, wherein the second key agreement control message is provided based on receiving the second notification (block 740). For example, as described above, the first network device may provide the second key agreement control message identifying the transmission key to the second network device. In some implementations, the second key agreement control message is provided based on receiving the second notification.

[0109] like Figure 7 As further shown, process 700 may include receiving a second confirmation message from the second network device indicating that the transmission key is installed on the second network device (block 745). For example, as described above, the first network device may receive a second confirmation message from the second network device indicating that the transmission key is installed on the second network device.

[0110] like Figure 7 As further shown, process 700 may include encrypting the traffic using the transmission key to generate encrypted traffic based on receiving the first confirmation message (block 750). For example, as described above, the first network device may encrypt the traffic using the transmission key to generate encrypted traffic based on receiving the first confirmation message.

[0111] like Figure 7 As further shown, process 700 may include providing the encrypted traffic to the second network device so that the second network device decrypts the encrypted traffic using the received key (block 755). For example, as described above, the first network device may provide the encrypted traffic to the second network device so that the second network device decrypts the encrypted traffic using the received key.

[0112] Process 700 may include additional implementations, such as any single implementation or any combination of implementations described below and / or in association with one or more other processes described elsewhere herein.

[0113] In a first implementation, receiving the encrypted data includes receiving the encrypted data identifying the receive key and the transmit key a certain period of time after receiving a previous security key or after processing a certain number of packets using the previous security key.

[0114] In a second implementation, alone or in combination with the first implementation, the first notification and the second notification enable the first network device to provide secure key rollover with zero packet loss.

[0115] In a third implementation, alone or in combination with one or more of the first and second implementations, installing the receive key on the protocol hardware includes programming the receive key into the protocol hardware.

[0116] In a fourth implementation, either alone or in combination with one or more of the first to third implementations, installing the transport key on the protocol hardware based on receiving the first confirmation message includes programming the transport key into the protocol hardware after receiving the first confirmation message.

[0117] In a fifth implementation, alone or in combination with one or more of the first to fourth implementations, the first confirmation message indicates that the receiving key is installed on protocol hardware associated with a data plane of the second network device based on the third notification.

[0118] Although Figure 7 Example blocks of process 700 are shown, but in some implementations, Figure 7 Process 700 may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in FIG. Additionally or alternatively, two or more blocks of process 700 may be performed in parallel.

[0119] The present disclosure discloses a method, comprising: receiving encrypted data by a first network device, the encrypted data identifying: a receiving key for decrypting a service, and a transmission key for encrypting the service; installing the receiving key on protocol hardware associated with a data plane of the first network device by the first network device; receiving a first notification from the data plane of the first network device, the first notification indicating that the receiving key is installed on the protocol hardware; providing a first key agreement control message identifying the receiving key to a second network device by the first network device, wherein the first key agreement control message is provided based on receiving the first notification; receiving a confirmation message from the second network device by the first network device, the confirmation message indicating that the receiving key is installed on the second network device; installing the transmission key on the protocol hardware by the first network device based on receiving the confirmation message; receiving a second notification from the data plane of the first network device, the second notification indicating that the transmission key is installed on the protocol hardware; and providing a second key agreement control message identifying the transmission key to the second network device by the first network device, wherein the second key agreement control message is provided based on receiving the second notification.

[0120] In some embodiments, the confirmation message is based on an additional notification received by the second network device from a data plane of the second network device, the additional notification indicating that the received key is installed on protocol hardware associated with the data plane of the second network device.

[0121] In some embodiments, the method further includes: based on receiving the confirmation message, encrypting the service using the transmission key to generate encrypted service; and providing the encrypted service to the second network device so that the second network device decrypts the encrypted service using the reception key.

[0122] In some embodiments, the protocol hardware is associated with one of: a media access control security protocol, or an internet protocol security protocol.

[0123] In some embodiments, wherein the first network device comprises a key server network device and the second network device comprises a peer network device.

[0124] In some embodiments, the first notification and the second notification enable the first network device to provide secure key rollover without causing service loss.

[0125] In some embodiments, receiving the encrypted data includes receiving the encrypted data identifying the received key and the transmitted key within a specific time period after receiving a previous security key.

[0126] The present disclosure discloses a first network device, comprising: one or more memories; and one or more processors, for receiving encrypted data, the encrypted data identifying: a first key for decrypting a service, and a second key for encrypting the service; installing the first key on protocol hardware associated with a data plane of the first network device; receiving a first notification from the data plane, the first notification indicating that the first key is installed on the protocol hardware; providing a first key agreement control message identifying the first key to a second network device, wherein the first key agreement control message is provided based on receiving the first notification; receiving a first confirmation message from the second network device, the first confirmation message indicating that the first key is installed on the second network device; installing the second key on the protocol hardware based on receiving the first confirmation message; receiving a second notification from the data plane, the second notification indicating that the second key is installed on the protocol hardware; providing a second key agreement control message identifying the second key to the second network device, wherein the second key agreement control message is provided based on receiving the second notification; and receiving a second confirmation message from the second network device, the second confirmation message indicating that the second key is installed on the second network device.

[0127] In some embodiments, the one or more processors, when receiving the encrypted data, are configured to: receive the encrypted data identifying the first key and the second key after some data packets have been processed using a previous security key.

[0128] In some embodiments, wherein the second network device is included in a plurality of peer network devices associated with the first network device, and the one or more processors are further used to: receive a plurality of confirmation messages from the plurality of peer network devices, the plurality of confirmation messages indicating that the first key is installed on each of the plurality of peer network devices; and based on receiving the plurality of confirmation messages, encrypt the traffic using the second key to generate encrypted traffic.

[0129] In some embodiments, the one or more processors are further configured to provide the encrypted traffic to one or more of the plurality of peer network devices, so that the one or more of the plurality of peer network devices decrypt the encrypted traffic using the first key.

[0130] In some embodiments, the first notification and the second notification enable the first network device to provide zero-packet-loss secure key rollover.

[0131] In some embodiments, the one or more processors, when installing the first key on the protocol hardware, are configured to: program the first key into the protocol hardware.

[0132] In some embodiments, the one or more processors, when installing the second key on the protocol hardware based on receiving the first confirmation message, are configured to: program the second key into the protocol hardware after receiving the first confirmation message.

[0133] The present disclosure discloses a non-transitory computer-readable medium storing instructions, the instructions comprising: one or more instructions, when executed by one or more processors of a first network device, causing the one or more processors to: receive encrypted data, the encrypted data identifying a receiving key for decrypting a service and a transmission key for encrypting the service; install the receiving key on protocol hardware associated with a data plane of the first network device; receive a first notification from the data plane, the first notification indicating that the receiving key is installed on the protocol hardware; provide a first key agreement control message identifying the receiving key to a second network device, wherein the first key agreement control message is provided based on receiving the first notification; receive a first confirmation message from the second network device, the first confirmation message ... A confirmation message indicates that the receiving key is installed on the second network device; based on receiving the first confirmation message, the transmission key is installed on the protocol hardware; a second notification is received from the data plane, and the second notification indicates that the transmission key is installed on the protocol hardware; a second key agreement control message identifying the transmission key is provided to the second network device, wherein the second key agreement control message is provided based on receiving the second notification; a second confirmation message is received from the second network device, and the second confirmation message indicates that the transmission key is installed on the second network device; based on receiving the first confirmation message, the service is encrypted using the transmission key to generate encrypted service; and the encrypted service is provided to the second network device so that the second network device decrypts the encrypted service using the receiving key.

[0134] In some embodiments, the one or more instructions that cause the one or more processors to receive the encrypted data cause the one or more processors to: receive the encrypted data identifying the receive key and the transmit key within a specific time period after receiving a previous security key or after some data packets are processed using the previous security key.

[0135] In some embodiments, the first notification and the second notification enable the first network device to provide zero-packet-loss security key rollover.

[0136] In some embodiments, the one or more instructions that cause the one or more processors to install the received key on the protocol hardware cause the one or more processors to: program the received key into the protocol hardware.

[0137] In some embodiments, the one or more instructions that cause the one or more processors to install the transport key on the protocol hardware based on receiving the first confirmation message cause the one or more processors to: program the transport key into the protocol hardware after receiving the first confirmation message.

[0138] In some embodiments, wherein the first confirmation message is based on a third notification indicating that the received key is installed on protocol hardware associated with a data plane of the second network device.

[0139] The above disclosure provides illustration and description, but is not intended to be exhaustive or to limit the implementations to the precise forms disclosed. Modifications and variations may be made in light of the above disclosure or may be acquired from practice of the implementations.

[0140] As used herein, the term "component" is intended to be broadly interpreted as hardware, firmware, or a combination of hardware and software.

[0141] As used herein, a service or content may include a set of packets. A packet may refer to a communication structure for communicating information, such as a protocol data unit (PDU), a service data unit (SDU), a network packet, a datagram, a segment, a message, a block, a frame (e.g., an Ethernet frame), a portion of any of the above, and / or another type of formatted or unformatted data unit capable of being transmitted over a network.

[0142] It is apparent that the systems and / or methods described herein may be implemented using various forms of hardware, firmware, and / or combinations of hardware and software. The actual specialized control hardware or software code used to implement these systems and / or methods is not a limitation of the present implementation. Thus, the operation and behavior of the systems and / or methods are described herein without reference to specific software code, and it should be understood that the systems and / or methods may be implemented using software and hardware based on the description herein.

[0143] Even though particular combinations of features are recited in the claims and / or disclosed in the specification, these combinations are not intended to limit the disclosure of various implementations. In fact, many of these features may be combined in ways not specifically recited in the claims and / or disclosed in the specification. Although each dependent claim listed below may only directly depend on one claim, the disclosure of various implementations includes the combination of each dependent claim with every other claim in the claim set.

[0144] Unless explicitly described as being key or essential, any element, behavior or instruction used herein should not be interpreted as key or essential. In addition, as used herein, the words "one" and "an" are intended to include one or more items and can be used interchangeably with "one or more". In addition, as used herein, the article "said" is intended to include one or more items related to the article "said", and can be used interchangeably with "said one or more". In addition, as used herein, the term "set" is intended to include one or more items (e.g., related items, unrelated items, combinations of related and unrelated items, etc.), and can be used interchangeably with "one or more". In the case of only one item, the phrase "only one" or similar language is used. In addition, as used herein, the term "have", "have", "contain" or similar language is intended to be an open term. In addition, unless otherwise clearly stated, the phrase "based on" is intended to refer to "at least partially based on". In addition, as used herein, the term "or" is intended to be inclusive when used in a series, and can be used interchangeably with "and / or", unless otherwise clearly stated (e.g., if used in combination with "or" or "only one").

Claims

1. A method for processing a key, comprising: The first network device receives encrypted data, wherein the encrypted data identifies: The receiving key used to decrypt the transaction, and The transmission key used to encrypt the transaction; installing, by the first network device, the received key on protocol hardware associated with a data plane of the first network device; receiving a first notification from the data plane of the first network device, the first notification indicating that the reception key is installed on the protocol hardware; providing, by the first network device to the second network device, a first key agreement control message identifying the received key, wherein the first key agreement control message is provided based on receiving the first notification; receiving, by the first network device, a confirmation message from the second network device, the confirmation message indicating that the received key is installed on the second network device; installing, by the first network device, the transmission key on the protocol hardware based on receiving the confirmation message; receiving a second notification from the data plane of the first network device, the second notification indicating that the transport key is installed on the protocol hardware; as well as providing, by the first network device to the second network device, a second key agreement control message identifying the transmission key, wherein the second key agreement control message is provided based on receiving the second notification; The first notification and the second notification enable the first network device to provide security key rollover without causing service loss.

2. The method of claim 1 , wherein the confirmation message is based on an additional notification received by the second network device from a data plane of the second network device, the additional notification indicating that the received key is installed on protocol hardware associated with the data plane of the second network device.

3. The method according to claim 2, further comprising: based on receiving the confirmation message, encrypting the traffic using the transmission key to generate encrypted traffic; as well as The encrypted traffic is provided to the second network device so that the second network device decrypts the encrypted traffic using the received key.

4. The method of claim 1, wherein the protocol hardware is associated with one of: Media Access Control security protocol, or Internet Protocol Security Protocol.

5. The method of claim 1, wherein the first network device comprises a key server network device and the second network device comprises a peer network device.

6. The method of claim 1 , wherein receiving the encrypted data comprises: The encrypted data identifying the received key and the transmitted key is received a certain period of time after receiving a previous security key.

7. A first network device, comprising: one or more memories; as well as One or more processors for: Receive encrypted data, the encrypted data identifying: a first key for decrypting the traffic, and A second key for encrypting the traffic; installing the first key on protocol hardware associated with a data plane of the first network device; receiving a first notification from the data plane, the first notification indicating that the first key is installed on the protocol hardware; providing a first key agreement control message identifying the first key to a second network device, wherein the first key agreement control message is provided based on receiving the first notification; receiving a first confirmation message from the second network device, the first confirmation message indicating that the first key is installed on the second network device; installing the second key on the protocol hardware based on receiving the first confirmation message; receiving a second notification from the data plane, the second notification indicating that the second key is installed on the protocol hardware; providing a second key agreement control message identifying the second key to the second network device, wherein the second key agreement control message is provided based on receiving the second notification; as well as receiving a second confirmation message from the second network device, the second confirmation message indicating that the second key is installed on the second network device; The first notification and the second notification enable the first network device to provide zero-packet-loss security key rollover.

8. The first network device of claim 7, wherein the one or more processors, when receiving the encrypted data, are configured to: The encrypted data identifying the first key and the second key is received after a number of data packets have been processed using a previous security key.

9. The first network device of claim 7, wherein the second network device is included in a plurality of peer network devices associated with the first network device, and the one or more processors are further configured to: receiving a plurality of confirmation messages from the plurality of peer network devices, the plurality of confirmation messages indicating that the first key is installed on each of the plurality of peer network devices; and Based on receiving the plurality of confirmation messages, the traffic is encrypted using the second key to generate encrypted traffic.

10. The first network device of claim 9, wherein the one or more processors are further configured to: The encrypted traffic is provided to one or more peer network devices of the plurality of peer network devices such that the one or more peer network devices of the plurality of peer network devices decrypt the encrypted traffic using the first key.

11. The first network device of claim 7, wherein the one or more processors, when installing the first key on the protocol hardware, are configured to: The first key is programmed into the protocol hardware.

12. The first network device of claim 7, wherein the one or more processors, when installing the second key on the protocol hardware based on receiving the first confirmation message, are configured to: The second key is programmed into the protocol hardware after receiving the first confirmation message.

13. A non-transitory computer readable medium storing instructions, the instructions comprising: One or more instructions that, when executed by one or more processors of a first network device, cause the one or more processors to: receiving encrypted data, the encrypted data identifying a receiving key for decrypting the service and a transmission key for encrypting the service; installing the received key on protocol hardware associated with a data plane of the first network device; receiving a first notification from the data plane, the first notification indicating that the receive key is installed on the protocol hardware; providing a first key agreement control message identifying the received key to the second network device, wherein the first key agreement control message is provided based on receiving the first notification; receiving a first confirmation message from the second network device, the first confirmation message indicating that the received key is installed on the second network device; installing the transport key on the protocol hardware based on receiving the first confirmation message; receiving a second notification from the data plane, the second notification indicating that the transport key is installed on the protocol hardware; providing a second key agreement control message identifying the transport key to the second network device, wherein the second key agreement control message is provided based on receiving the second notification; receiving a second confirmation message from the second network device, the second confirmation message indicating that the transmission key is installed on the second network device; encrypting the traffic using the transmission key to generate encrypted traffic based on receiving the first confirmation message; as well as providing the encrypted traffic to the second network device so that the second network device decrypts the encrypted traffic using the received key; The first notification and the second notification enable the first network device to provide zero-packet-loss security key rollover.

14. The non-transitory computer-readable medium of claim 13, wherein the one or more instructions that cause the one or more processors to receive the encrypted data cause the one or more processors to: The encrypted data identifying the reception key and the transmission key is received a certain period of time after receiving a previous security key or after some data packets have been processed using the previous security key.

15. The non-transitory computer-readable medium of claim 13, wherein the one or more instructions causing the one or more processors to install the received key on the protocol hardware causes the one or more processors to: The receive key is programmed into the protocol hardware.

16. The non-transitory computer-readable medium of claim 13, wherein the one or more instructions causing the one or more processors to install the transport key on the protocol hardware based on receiving the first confirmation message cause the one or more processors to: The transmission key is programmed into the protocol hardware after receiving the first confirmation message.

17. The non-transitory computer-readable medium of claim 13, wherein the first confirmation message is based on a third notification indicating that the received key is installed on protocol hardware associated with a data plane of the second network device.