Interior gateway protocol and traffic engineering sleep state for a network

US2025106163A1 · US · A1

Patent metadata
FieldValue
Publication numberUS-2025106163-A1
Application numberUS-202418643201-A
CountryUS
Kind codeA1
Filing dateApr 23, 2024
Priority dateSep 26, 2023
Publication dateMar 27, 2025
Grant date

How to read this patent

A practical reading order for non-experts. Skip the full description unless you need deep technical detail.

  1. Title

    What the patent document calls the invention.

  2. Abstract

    A short plain-language summary of the technical disclosure.

  3. Assignees and inventors

    Who owns or filed the patent and who is credited as inventor.

  4. Key dates

    Filing, priority, publication, and grant dates set the timeline.

  5. First independent claim

    The legal scope of protection — read this for what is actually claimed.

  6. CPC / IPC classifications

    Technology tags used to group this patent with similar filings.

  7. Citations and related patents

    Prior art links and similar publications in this corpus.

Abstract

Official abstract text for this publication.

A first network device may identify one or more components to transition to a sleep state, and may power down the one or more components to cause a link with a second network device to be in a sleep state. The first network device may provide, to the second network device, a link sleep state message identifying the link, and may provide updated link sleep state messages to the second network device while the sleep state of the link is maintained.

First claim

Opening claim text (preview).

What is claimed is: 1 . A method, comprising: identifying, by a first network device, one or more components to transition to a sleep state; powering down, by the first network device, the one or more components to cause a link with a second network device to be in a sleep state; providing, by the first network device and to the second network device, a link sleep state message identifying the link; and providing, by the first network device, updated link sleep state messages to the second network device while the sleep state of the link is maintained. 2 . The method of claim 1 , further comprising: maintaining a neighbor adjacency with the second network device based on the updated link sleep state messages. 3 . The method of claim 1 , further comprising: receiving link sleep state messages from the second network device; and maintaining a neighbor adjacency with the second network device based on the link sleep state messages. 4 . The method of claim 1 , wherein the second network device is configured to power down one or more components of the second network device and associated with the link. 5 . The method of claim 1 , wherein the updated link sleep state messages cause the second network device to maintain a neighbor adjacency with the first network device. 6 . The method of claim 1 , wherein the link sleep state message includes a sleep request bit set in a sleep type length value message. 7 . The method of the claim 1 , wherein each of the updated link sleep state messages includes a sleep request bit set in a sleep type length value message. 8 . A first network device, comprising: one or more memories; and one or more processors to: identify one or more components to transition to a sleep state; power down the one or more components to cause a link with a second network device to be in a sleep state; provide, to the second network device, a link sleep state message identifying the link; and provide updated link sleep state messages to the second network device while the sleep state of the link is maintained, wherein each of the updated link sleep state messages includes a sleep request bit set in a sleep type length value message. 9 . The first network device of claim 8 , wherein the one or more processors are further to: store data identifying the link and the sleep state of the link in a link state database. 10 . The first network device of claim 8 , wherein the one or more processors are further to: prune the link for shortest-path tree calculations. 11 . The first network device of claim 8 , wherein the one or more processors are further to: move a traffic engineering tunnel away from the link. 12 . The first network device of claim 8 , wherein the sleep state associated with the one or more components includes one or more of a power off state, a reset state, a low-power consumption state, a slowing clock-rates state, or a wake-on-arrival state. 13 . The first network device of claim 8 , wherein the one or more processors are further to: transition the one or more components and the link from the sleep state to an active state based on a traffic demand. 14 . The first network device of claim 8 , wherein the one or more processors are further to: perform a health check of the link to ensure that the link maintains the sleep state. 15 . A non-transitory computer-readable medium storing a set of instructions, the set of instructions comprising: one or more instructions that, when executed by one or more processors of a first network device, cause the first network device to: identify one or more components to transition to a sleep state; power down the one or more components to cause a link with a second network device to be in a sleep state; provide, to the second network device, a link sleep state message identifying the link; provide updated link sleep state messages to the second network device while the sleep state of the link is maintained; and maintain a neighbor adjacency with the second network device based on the updated link sleep state messages. 16 . The non-transitory computer-readable medium of claim 15 , wherein the one or more instructions further cause the first network device to: receive link sleep state messages from the second network device; and maintain the neighbor adjacency with the second network device based on the link sleep state messages. 17 . The non-transitory computer-readable medium of claim 15 , wherein the one or more instructions further cause the first network device to: store data identifying the link and the sleep state of the link in a link state database; and prune the link for shortest-path tree calculations. 18 . The non-transitory computer-readable medium of claim 15 , wherein the one or more instructions further cause the first network device to: move a traffic engineering tunnel away from the link. 19 . The non-transitory computer-readable medium of claim 15 , wherein the one or more instructions further cause the first network device to: transition the one or more components and the link from the sleep state to an active state based on a traffic demand. 20 . The non-transitory computer-readable medium of claim 15 , wherein the one or more instructions further cause the first network device to: perform a health check of the link to ensure that the link maintains the sleep state.

Assignees

Inventors

Classifications

  • involving simulating, designing, planning or modelling of a network · CPC title

  • Routing actions in the presence of nodes in sleep or doze mode · CPC title

  • where the received signal is a power saving command · CPC title

  • H04L47/125Primary

    by balancing the load, e.g. traffic engineering · CPC title

  • minimising geographical or physical path length · CPC title

Patent family

Related publications grouped by family.

External sources

Frequently asked questions

Answers are generated from the same data shown on this page.

What does patent US2025106163A1 cover?
A first network device may identify one or more components to transition to a sleep state, and may power down the one or more components to cause a link with a second network device to be in a sleep state. The first network device may provide, to the second network device, a link sleep state message identifying the link, and may provide updated link sleep state messages to the second network de…
Who is the assignee on this patent?
Juniper Networks Inc
What technology area does this patent fall under?
Primary CPC classification H04L47/125. Mapped technology areas include Electricity.
When was this patent published?
Publication date Thu Mar 27 2025 00:00:00 GMT+0000 (Coordinated Universal Time) (A1). Legal status and post-grant events are not shown on this page.
What related patents are in patentsdb?
We list 4 related publications on this page (citations in our corpus or others sharing the same primary CPC).