# US 9,438,510 B2 · Calculating a route > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 9,438,510 B2 - Document ID: US9438510B2 - Status: Granted - Kind: B2 - Application number: 14/649,158 - Filed: 2013-12-10 - Published: 2015-12-03 - Granted: 2016-09-06 - Earliest claimed: 2012-12-21 - Assignees: Hangzhou H3C Technologies Co., Ltd. - Applicants: Hangzhou H3C Technologies Co., Ltd. - Inventors: Zhiguang Wei - Web page: https://patentgrep.com/patent/US9438510B2 ## CPC - H04L 12/6418: {Hybrid transport} - H04L 45/03: by updating link state protocols - H04L 45/14: {Routing performance; Theoretical aspects} - H04L 45/52: Multiprotocol routers - H04L 61/251: between different IP versions - H04L 2101/668: Internet protocol [IP] address subnets - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) ## Abstract According to an example, in a method for calculating a route, a first network device may add a protocol attribute supported by a link to a link state protocol data unit (LSP) of the first network device according to a protocol attribute supported by a port of the first network device and a protocol attribute supported by a port of a neighbor network device when establishing an adjacency, and may flood the LSP. The first network device may receive a LSP from a neighbor network device, parse a protocol attribute supported by a link contained in the received LSP, record the protocol attribute supported by the link contained in the received LSP in local network topology information, to obtain updated network topology information. And the first network device may calculate a route according to the updated network topology information. A network device and a computing device may calculate a route. ## Claims ### Claim 1 A method for calculating a route, comprising: adding, by a first network device, a protocol attribute supported by a link into a link state protocol data unit (LSP) of the first network device according to a protocol attribute supported by a port of the first network device and a protocol attribute supported by a port of a neighbor network device of the first network device when establishing an adjacency for the first network device; flooding, by the first network device, the LSP; receiving, by the first network device, a LSP from a neighbor network device, parsing the received LSP to obtain a protocol attribute supported by a link contained in the received LSP, recording the protocol attribute contained in the received LSP in local network topology information to obtain updated network topology information; and calculating, by the first network device, a route according to the updated network topology information. ### Claim 2 (depends on 1) The method according to claim 1, wherein the protocol attribute contained in the flooded LSP comprises identifier information that indicates whether Internet Protocol version 4 (IPv4) and/or Internet Protocol version 6 (IPv6) is supported; the protocol attribute contained in the received LSP comprises identifier information that indicates whether IPv4 and/or IPv6 is supported; the protocol attribute supported by the port of the first network device comprises identifier information that indicates whether IPv4 and/or IPv6 is supported; the protocol attribute supported by the port of the neighbor network device comprises identifier information that indicates whether IPv4 and/or IPv6 is supported. ### Claim 3 (depends on 1) The method according to claim 1, further comprising: obtaining, by the first network device, the protocol attribute contained in the flooded LSP by negotiation between the first network device and the neighbor network device through a Hello packet. ### Claim 4 (depends on 2) The method according to claim 2, wherein adding the protocol attribute supported by the link into the LSP of the first network device comprises: when the protocol attribute supported by both the port of the first network device and the port of the neighbor network device comprises IPv4, adding into the LSP, identifier information indicating that the link between the port of the first network device and the port of the neighbor network device supports IPv4 as the protocol attribute contained in the flooded LSP; when the protocol attribute supported by both the port of the first network device and the port of the neighbor network device comprises IPv6, adding into the LSP, identifier information indicating that the link between the port of the first network device and the port of the neighbor network device supports IPv6 as the protocol attribute contained in the flooded LSP; and when the protocol attribute supported by both the port of the first network device and the port of the neighbor network device comprises IPv4 and IPv6, adding into the LSP, identifier information indicating that the link between the port of the first network device and the port of the neighbor network device supports IPv4 and IPv6 as the protocol attribute contained in the flooded LSP. ### Claim 5 (depends on 2) The method according to claim 2, wherein recording the protocol attribute contained in the received LSP comprises: determining whether network topology information, before recording the protocol attribute contained in the received LSP, comprises the link contained in the received LSP; when the network topology information comprises the link contained in the received LSP, comparing a protocol attribute previously recorded in the network topology information with the protocol attribute contained in the received LSP; modifying the protocol attribute previously recorded in the network topology information with the protocol attribute contained in the received LSP when the protocol attribute previously recorded in the network topology information is different from the protocol attribute contained in the received LSP; and when the network topology information does not comprise the link contained in the received LSP, creating the link contained in the received LSP in the network topology information, configuring the protocol attribute supported by the link contained in the received LSP in the network topology information with the protocol attribute contained in the received LSP. ### Claim 6 (depends on 2) The method according to claim 2, wherein calculating the route according to the updated network topology information comprises: calculating an IPv4 route according to the updated network topology information of an IPv4 network; or calculating an IPv6 route according to the updated network topology information of an IPv6 network. ### Claim 7 (depends on 1) The method according to claim 1, wherein calculating the route according to the updated network topology information comprises: using the shortest path algorithm to calculate the route according to the updated network topology information. ### Claim 8 A computing device to calculate a route, comprising: a network interface; a processor; and a memory storing machine readable instructions that when executed by the processor cause the processor to: add a protocol attribute supported by a link into a link state protocol data unit (LSP) of a first network device according to a protocol attribute supported by a port of the first network device and a protocol attribute supported by a port of a neighbor network device of the first network device when establishing an adjacency for the first network device; flood the LSP through the network interface; receive a LSP from a neighbor network device through the network interface, parse the received LSP to obtain a protocol attribute supported by a link contained in the received LSP, record the protocol attribute contained in the received LSP in local network topology information to obtain updated network topology information; and calculate a route according to the updated network topology information. ### Claim 9 (depends on 8) The computing device according to claim 8, wherein the protocol attribute contained in the flooded LSP comprises identifier information that indicates whether Internet Protocol version 4 (IPv4) and/or Internet Protocol version 6 (IPv6) is supported; the protocol attribute contained in the received LSP comprises identifier information that indicates whether IPv4 and/or IPv6 is supported; the protocol attribute supported by the port of the first network device comprises identifier information that indicates whether IPv4 and/or IPv6 is supported; and the protocol attribute supported by the port of the neighbor network device comprises identifier information that indicates whether IPv4 and/or IPv6 is supported. ### Claim 10 (depends on 8) The computing device according to claim 8, wherein the memory further stores machine readable instructions that when executed by the processor further cause the processor to: obtain the protocol attribute contained in the received LSP by negotiation between the first network device and the neighbor network device through a Hello packet. ### Claim 11 (depends on 9) The computing device according to claim 9, wherein the memory further stores machine readable instructions that when executed by the processor cause the processor to: when the protocol attribute supported by both the port of the first network device and the port of the neighbor network device comprises IPv4, add into the LSP, identifier information indicating that the link between the port of the first network device and the port of the neighbor network device comprises IPv4 as the protocol attribute contained in the flooded LSP; when the protocol attribute supported by both the port of the first network device and the port of the neighbor network device comprises IPv6, add into the LSP, identifier information indicating that the link between the port of the first network device and the port of the neighbor network device comprises IPv6 as the protocol attribute contained in the flooded LSP; and when the protocol attribute supported by both the port of the first network device and the port of the neighbor network device comprises IPv4 and IPv6, add into the LSP an identifier information indicating that the link between the port of the first network device and the port of the neighbor network device comprises IPv4 and IPv6 as the protocol attribute contained in the flooded LSP. ### Claim 12 (depends on 9) The computing device according to claim 9, wherein the memory further stores machine readable instructions that when executed by the processor cause the processor to: determine whether network topology information, before recording the protocol attribute contained in the received LSP, comprises the link contained in the received LSP; when the network topology information comprises the link contained in the received LSP, compare a protocol attribute previously recorded in the network topology information with the protocol attribute contained in the received LSP; modify the protocol attribute previously recorded in the network topology information with the protocol attribute contained in the received LSP when the protocol attribute previously recorded in the network topology information is different from the protocol attribute contained in the received LSP; and when the network topology information does not comprise the link contained in the received LSP, create the link contained in the received LSP in the network topology information and configure the protocol attribute contained in the received LSP in the network topology information with the protocol attribute contained in the received LSP. ### Claim 13 (depends on 9) The computing device according to claim 9, wherein the memory further stores machine readable instructions that when executed by the processor cause the processor to: calculate an IPv4 route according to the updated network topology information of an IPv4 network; or calculate an IPv6 route according to the updated network topology information of an IPv6 network. ### Claim 14 (depends on 8) The computing device according to claim 8, wherein the memory further stores machine readable instructions that when executed by the processor cause the processor to: use a shortest path algorithm to calculate the route according to the updated network topology information.