# US 2025/0158815 A1 · Prioritized Rekeying of Security Associations

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

- Number: US 2025/0158815 A1
- Document ID: US20250158815A1
- Status: Published application
- Kind: A1
- Application number: 18/695,171
- Filed: 2021-10-12
- Published: 2025-05-15
- Earliest claimed: 2021-10-12
- Applicants: Telefonaktiebolaget LM Ericsson (publ)
- Inventors: Daiying Liu; Congjie Zhang; Daniel Migault
- Web page: https://patentgrep.com/patent/US20250158815A1

## CPC

- H04L 63/061: {for key exchange, e.g. in peer-to-peer networks (cryptographic mechanisms or cryptographic arrangements for key agreement H04L9/0838)}
- H04L 9/0891: {Revocation or update of secret information, e.g. encryption key update or rekeying}
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

Embodiments include methods for a first node to manage rekeying of a security association (SA) between the first node and a second node in a communication network. Such methods include sending to the second node a request indicating a rekey priority of the first node, and receiving from the second node a response indicating a rekey priority of the second node. Such methods also include selectively initiating rekeying of the SA between the first node and the second node based on the request and the response. Other embodiments include complementary methods for the second node, as well as nodes (e.g., hosts, gateways, UEs, base stations, servers, etc.) configured to perform such methods.

## Claims

### Claim at position 1

-38. (canceled)

### Claim 39

A method performed by a first node to manage rekeying of a security association (SA) between the first node and a second node in a communication network, the method comprising:
sending to the second node a request indicating a rekey priority of the first node;
receiving from the second node a response indicating a rekey priority of the second node; and
selectively initiating rekeying of the SA between the first node and the second node based on the request and the response.

### Claim 40 (depends on 39)

The method of claim 39, wherein the request and the response include a message type field that can have any one of a plurality of different values, including a first message type value indicating that the sending node supports rekey priority.

### Claim 41 (depends on 40)

The method of claim 40, wherein when the request includes a message type field that does not have the first message type value, the response also includes a message type field that does not have the first message type value.

### Claim 42 (depends on 40)

The method of claim 40, wherein when the request or the response includes a message type field having the first message type value, the request or the response also includes a rekey priority indicator that can have any one of a plurality of different values.

### Claim 43 (depends on 42)

The method of claim 42, wherein:
when present, the message type field and the rekey priority indicator are included in a Notify message; and
the Notify message is included in an encrypted payload of the request or the response.

### Claim 44 (depends on 42)

The method of claim 42, wherein the plurality of different values of the rekey priority indicator include a plurality of first values that indicate a respective plurality of different rekey priorities configured in the sending node.

### Claim 45 (depends on 44)

The method of claim 44, wherein:
the method further comprises randomly selecting the rekey priority of the first node based on determining that rekeying is enabled but rekey priority is not configured in the first node; and
the request includes one of the first values that indicates the randomly selected rekey priority of the first node.

### Claim 46 (depends on 44)

The method of claim 44, wherein selectively initiating the rekeying of the SA comprises, when the request and the response include respective rekey priority indicators with any of the first values:
initiating the rekeying of the SA when the rekey priority of the first node is greater than or equal to the rekey priority of the second node; and
refraining from initiating the rekeying of the SA when the rekey priority of the first node is less than the rekey priority of the second node.

### Claim 47 (depends on 46)

The method of claim 46, further comprising, when the request and the response include respective rekey priority indicators with any of the first values and the rekey priority of the first node is less than the rekey priority of the second node, completing a rekeying of the SA that was initiated by the second node.

### Claim 48 (depends on 44)

The method of claim 44, wherein:
the plurality of different values of the rekey priority indicator include a second value that indicates rekeying is disabled in the sending node; and
selectively initiating the rekeying of the SA comprises initiating the rekeying of the SA when a rekey priority indicator having the second value is present in the response and rekeying is enabled in the first node.

### Claim 49 (depends on 48)

The method of claim 48, wherein the second value is a particular one of the first values that also indicates a lowest rekey priority.

### Claim 50 (depends on 39)

The method of claim 39, wherein the request and the response comprise one of the following: an IKE_INIT exchange, an IKE_AUTH exchange, or a CREATE_CHILD_SA exchange.

### Claim 51

A method performed by a second node to manage rekeying of a security association (SA) between the second node and a first node in a communication network, the method comprising:
receiving from the first node a request indicating a rekey priority of the first node;
sending to the first node a response indicating a rekey priority of the second node; and
selectively initiating rekeying of the SA between the first node and the second node based on the request and the response.

### Claim 52 (depends on 51)

The method of claim 51, wherein the request and the response include a message type field that can have any one of a plurality of different values, including a first message type value indicating that the sending node supports rekey priority.

### Claim 53 (depends on 52)

The method of claim 52, wherein when the request includes a message type field that does not have the first message type value, the response also includes a message type field that does not have the first message type value.

### Claim 54 (depends on 52)

The method of claim 52, wherein when the request or the response includes a message type field having the first message type value, the request or the response also includes a rekey priority indicator that can have any one of a plurality of different values.

### Claim 55 (depends on 54)

The method of claim 54, wherein:
when present, the message type field and the rekey priority indicator are included in a Notify message; and
the Notify message is included in an encrypted payload of the request or the response.

### Claim 56 (depends on 54)

The method of claim 54, wherein the plurality of different values of the rekey priority indicator include a plurality of first values that indicate a respective plurality of different rekey priorities configured in the sending node.

### Claim 57 (depends on 56)

The method of claim 56, wherein:
the method further comprises randomly selecting the rekey priority of the second node based on determining that rekeying is enabled but rekey priority is not configured in the second node; and
the response includes one of the first values that indicates the randomly selected rekey priority of the second node.

### Claim 58 (depends on 56)

The method of claim 56, wherein selectively initiating the rekeying of the SA comprises, when the request and the response include respective rekey priority indicators with any of the first values:
initiating the rekeying of the SA when the rekey priority of the second node is greater than or equal to the rekey priority of the first node; and
refraining from initiating the rekeying of the SA when the rekey priority of the second node is less than the rekey priority of the first node.

### Claim 59 (depends on 58)

The method of claim 58, further comprising, when the request and the response include respective rekey priority indicators with any of the first values and the rekey priority of the second node is less than the rekey priority of the first node, completing a rekeying of the SA that was initiated by the first node.

### Claim 60 (depends on 57)

The method of claim 57, wherein:
the plurality of different values of the rekey priority indicator include a second value that indicates rekeying is disabled in the sending node; and
selectively initiating the rekeying of the SA comprises initiating the rekeying of the SA when a rekey priority indicator having the second value is present in the request and rekeying is enabled in the second node.

### Claim 61 (depends on 60)

The method of claim 60, wherein the second value is a particular one of the first values that also indicates a lowest rekey priority.

### Claim 62 (depends on 51)

The method of claim 51, wherein the request and the response comprise one of the following: an IKE_INIT exchange, an IKE_AUTH exchange, or a CREATE_CHILD_SA exchange.

### Claim 63

A first node configured to manage rekeying of a security association (SA) between the first node and a second node in a communication network, the first node comprising:
communication interface circuitry arranged for secure communication with the second node; and
processing circuitry operatively coupled to the communication interface circuitry, whereby the processing circuitry and the communication interface circuitry are configured to:
send to the second node a request indicating a rekey priority of the first node;
receive from the second node a response indicating a rekey priority of the second node; and
selectively initiate rekeying of the SA between the first node and the second node based on the request and the response.

### Claim 64 (depends on 51)

A second node configured to manage rekeying of a security association (SA) between the second node and a first node in a communication network, the second node comprising:
communication interface circuitry arranged for secure communication with the first node; and
processing circuitry operatively coupled to the communication interface circuitry, whereby the processing circuitry and the communication interface circuitry are configured to perform the method of claim 51.
