WO2016029862A1 - 一种链路状态信息通告方法和设备 - Google Patents

一种链路状态信息通告方法和设备 Download PDF

Info

Publication number
WO2016029862A1
WO2016029862A1 PCT/CN2015/088277 CN2015088277W WO2016029862A1 WO 2016029862 A1 WO2016029862 A1 WO 2016029862A1 CN 2015088277 W CN2015088277 W CN 2015088277W WO 2016029862 A1 WO2016029862 A1 WO 2016029862A1
Authority
WO
WIPO (PCT)
Prior art keywords
network
network device
link state
state information
igp
Prior art date
Application number
PCT/CN2015/088277
Other languages
English (en)
French (fr)
Inventor
王丽星
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to EP15835964.6A priority Critical patent/EP3179679B1/en
Publication of WO2016029862A1 publication Critical patent/WO2016029862A1/zh
Priority to US15/443,385 priority patent/US10200204B2/en

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00Data switching networks
    • H04L12/02Details
    • H04L12/16Arrangements for providing special services to substations
    • H04L12/18Arrangements for providing special services to substations for broadcast or conference, e.g. multicast
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00Routing or path finding of packets in data switching networks
    • H04L45/44Distributed routing
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/12Discovery or management of network topologies
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00Routing or path finding of packets in data switching networks
    • H04L45/02Topology update or discovery
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00Routing or path finding of packets in data switching networks
    • H04L45/16Multipoint routing
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00Routing or path finding of packets in data switching networks
    • H04L45/42Centralised routing
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00Routing or path finding of packets in data switching networks
    • H04L45/52Multiprotocol routers
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00Routing or path finding of packets in data switching networks
    • H04L45/58Association of routers
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00Routing or path finding of packets in data switching networks
    • H04L45/64Routing or path finding of packets in data switching networks using an overlay routing layer

Definitions

  • the present invention relates to the field of software-defined network SDN technologies, and in particular, to a link state information notification method and device.
  • control point In the software defined network (English: Software Defined Network; abbreviation: SDN) scenario, different control points support different protocols.
  • the control point that controls the forwarding table supports the Open flow protocol
  • the control point that controls the routing table supports the Interface to the Routing System (I2RS) protocol
  • I2RS Routing System
  • IGP Interior Gateway Protocol
  • some network devices controlled by one control device support IGP, and some network devices do not support IGP due to low hardware configuration. Network devices that support IGP cannot access network devices that do not support IGP.
  • the embodiment of the present invention provides a link state information advertisement method and device, which are used to solve the problem that a network device supporting IGP in a plurality of network devices controlled by one control device cannot access a network device that does not support IGP. .
  • a link state information notification method including:
  • the first network device receives network topology information sent by the control device, where the network topology information includes link state information between the first network device and the second network device generated by the control device,
  • the first network device supports an internal network protocol IGP, and the second network device does not support the IGP;
  • the first network device advertises link state information between the first network device and the second network device that are carried in the network topology information.
  • the first network device advertises link state information between the first network device and the second network device, including:
  • the first network device stores link state information between the first network device and the second network device carried in the network topology information in a link state database;
  • the first network device advertises a link state broadcast LSA, where the LSA includes link state information between the first network device and the second network device, and Link state information between the first network device and other IGP-enabled network devices.
  • the first network device receives a network topology sent by the control device Information, including:
  • the first network device receives network topology information that is sent by the control device based on the routing system interface I2RS protocol.
  • the network topology information further includes an identifier of the control device
  • Network topology information sent by the control device including:
  • the first network device receives network topology information that the control device transmits based on the extended IGP.
  • the first network device advertises a link between the first network device and the second network device Status information, including:
  • the first network device stores link state information between the first network device and the second network device included in the network topology information into a link state database;
  • the first network device advertises a link state broadcast LSA, where the LSA includes link state information between the first network device and the second network device, and Link state information between the first network device and other IGP-enabled network devices.
  • the network topology information further includes a link state between the first network device and another IGP-enabled network device. information
  • the method further includes: the first network device advertises link state information between the first network device and other supporting IGP devices carried in the network topology information.
  • the method further includes:
  • the first network device preferentially performs route calculation according to the link state information carried in the network topology information.
  • the method further includes:
  • the first network device determines that the identifier of the control device included in the received network topology information is the same as the identifier of the locally stored control device.
  • the extended IGP includes an extended routing link state broadcast Router-LSA and an extended network link state broadcast Networ-LSA.
  • a link state information advertising device including:
  • a receiving module configured to receive network topology information sent by the control device, where the network topology information includes link state information between the first network device and the second network device generated by the control device, where A network device supports an internal network protocol IGP, and the second network device does not support an IGP;
  • the advertisement module is configured to notify the link state information between the first network device and the second network device that are carried in the network topology information that is received by the receiving module.
  • the notification module is configured to: store, by the first network device, link state information between the first network device and the second network device carried in the network topology information into a link state database;
  • the receiving module is specifically configured to receive the control device based on the route.
  • Network topology information sent by the system interface I2RS protocol.
  • the network topology information further includes an identifier of the control device
  • the receiving module is specifically configured to receive network topology information that is sent by the control device based on the extended IGP.
  • the advertising module is specifically configured to use the first network device included in the network topology information.
  • Link state information with the second network device is stored in the link state database;
  • the network topology information further includes a link state between the first network device and another IGP-enabled network device. information
  • the notification module is further configured to notify link state information between the first network device and the other supporting IGP device carried in the network topology information.
  • the link state information advertising device further includes:
  • the route calculation module is configured to perform route calculation based on the link state information carried in the network topology information.
  • the link state information advertising device further includes: a determining module, where:
  • the determining module is configured to determine, after the receiving module receives the network topology information sent by the control device, and before the advertising module announces link state information between the first network device and the second network device,
  • the identifier of the control device included in the network topology information is the same as the identifier of the locally stored control device.
  • the extended IGP includes an extended routing link Status broadcast Router-LSA and extended network link status broadcast Networ-LSA.
  • the first network device of the embodiment of the present invention receives the network topology information sent by the control device, where the network topology information includes the link state between the first network device and the second network device generated by the control device.
  • the first network device supports the internal network protocol IGP
  • the second network device does not support the IGP
  • the first network device advertises the first network device and the second network device that are carried in the network topology information.
  • Link state information between the first network device obtains link state information between the second network device and the second network device that does not support the IGP, and notifies the link state information to other IGP-enabled network devices.
  • the network device supporting the IGP in the plurality of network devices controlled by one control device accesses the network device that does not support the IGP.
  • FIG. 1 is a schematic flowchart of a link state information notification method according to Embodiment 1 of the present invention
  • FIG. 2 is a schematic flowchart of a network topology state adjustment method according to Embodiment 2 of the present invention.
  • Figure 2 (a) is a format diagram of the extended OSPF RFC 4970 protocol packet
  • Figure 2 (b) is a format diagram of extended TLVs in the extended OSPF RFC4970 protocol packet
  • Figure 2 (c) is a format of a packet header of a protocol packet extending the Router-LSA type
  • Figure 2 (d) is a format diagram of protocol packets obtained by extending the Router-LSA type by the extended TLVs;
  • Figure 2 (e) is a format diagram corresponding to the attribute field in Figure 2 (d);
  • FIG. 3 is a schematic structural diagram of a link state information notification method according to Embodiment 3 of the present invention.
  • FIG. 4 is a schematic structural diagram of a link state information advertisement device according to Embodiment 4 of the present invention.
  • FIG. 5 is a schematic structural diagram of a link state information advertisement device according to Embodiment 5 of the present invention.
  • an embodiment of the present invention provides a link state information notification method and device, where a first network device receives network topology information sent by a control device, where the network topology information includes the control Link state information between the first network device and the second network device generated by the device, the first network device supports an internal network protocol IGP, the second network device does not support an IGP, and the first network device Notifying the link state information between the first network device and the second network device that is carried in the network topology information, because the first network device acquires between the second network device and the second network device that does not support the IGP through the control device.
  • Link state information, and the link state information is advertised to other network devices that support the IGP, and the network device that supports the IGP in the plurality of network devices controlled by one control device accesses the network device that does not support the IGP.
  • Embodiment 1 is a diagrammatic representation of Embodiment 1:
  • FIG. 1 is a schematic flowchart diagram of a link state information notification method according to Embodiment 1 of the present invention. The method can be as follows.
  • Step 101 The first device receives network topology information sent by the control device.
  • the network topology information includes link state information between the first network device and the second network device that are generated by the control device, where the first device supports IGP, and the second device does not support IGP.
  • the link state information includes at least one or more of a port, a link type, and a bandwidth.
  • step 101 the control device controls a set of network devices in which the first network device is located and a set of network devices in which the second network device is controlled.
  • the network device included in the network device set where the first network device is located supports the IGP.
  • the network device included in the network device where the second network device is located does not support the IGP.
  • the first network device cannot access the second network device. In other words, there is no routing path between the first network device and the second network device.
  • the control device can obtain information such as an Internet Protocol Protocol (IP) address, a port, and the like of the first network device; Information such as an IP address and a port; and can also generate link state information between the first network device and the second network device.
  • IP Internet Protocol Protocol
  • the link state information between the first network device and the second network device may include bidirectional link state information, that is, the announcer is the first network device, and the first network device is used to the second network device.
  • the control device sends the network topology information to the first network device, and the first network device and the second network are notified. Link status information between devices.
  • the first network device receives network topology information that is sent by the control device based on the routing system interface I2RS protocol.
  • Step 102 The first network device advertises link state information between the first network device and the second network device that are carried in the network topology information.
  • the first network device stores link state information between the first network device and the second network device carried in the network topology information to a link state database of the first network device itself. in.
  • the first network device advertises a link state broadcast (English: Link State Advertisement; abbreviation: LSA).
  • LSA Link State Advertisement
  • the LSA includes link state information between the first network device and the second network device that is carried in the network topology information, and between the first network device and other IGP-enabled network devices. Link status information.
  • IGP domain may be an Open Shortest Path First (OSPF) domain or an Intermediate System to Intermediate System (English: Intermediate System to Intermediate System; In the domain, there is no limit here.
  • OSPF Open Shortest Path First
  • Intermediate System to Intermediate System International Standard
  • the first network device receives the network topology information that is sent by the control device, where the network topology information includes the first network device and the second network device that are generated by the control device.
  • Link state information the first network device supports an internal network protocol IGP
  • the second network device does not support an IGP
  • the first network device advertises the first network device carried in the network topology information Link state information with the second network device, because the first network device acquires link state information between the second network device that does not support the IGP through the control device, and notifies the link state information to the other
  • the network device supporting the IGP realizes that the network device supporting the IGP in the plurality of network devices controlled by one control device accesses the network device that does not support the IGP.
  • Embodiment 2 is a diagrammatic representation of Embodiment 1:
  • FIG. 2 is a schematic structural diagram of a link state information notification method according to Embodiment 2 of the present invention.
  • the method can be as follows.
  • Step 201 The first network device receives network topology information sent by the control device.
  • the network topology information includes an identifier of the control device and link state information between the first network device and the second network device generated by the control device.
  • step 201 when receiving the network topology information sent by the control device, the first network device determines whether the identifier of the control device carried in the network topology information is the same as the identifier of the locally stored control device.
  • the network topology information includes the device identifier of the network device corresponding to the link state information generated by the control device, that is, the device identifier of the first network device and the device identifier of the second network device in the embodiment of the present invention. ).
  • the first network device determines, according to the device identifier of the network device that is carried in the network topology information, whether the link state information generated by the control device is related to the first network device.
  • the device identifier of the network device carried in the network topology information is the same as the device identifier of the first network device, determining that the link state information generated by the control device is related to the first network device.
  • the device identifier of the network device that is carried in the network topology information is different from the device identifier of the first network device, determining that the link state information generated by the control device is not related to the first network device.
  • the first network device receives network topology information that is sent by the control device based on the extended IGP.
  • the extended IGP involved in the embodiment of the present invention includes a field corresponding to the identifier of the control device, so that the network device supporting the IGP can obtain the identifier of the control device, for example, a Router-ID.
  • the extension of the IGP protocol packet can be implemented by extending the OSPF protocol packet as shown in the following figure, or by extending other protocol packets.
  • the extended IGP includes the extended OSPF protocol header, and includes the extended Router-LSA type and the extended Network-LSA type.
  • the TLV field is added to the OSPF RFC4970 protocol header, and the content of the added TLV field is used to indicate the identifier of the control device of the network device supporting the IGP.
  • Figure 2(a) shows the format of the extended OSPF RFC4970 protocol packet.
  • the OSPF RFC4970 packet contains the packet type (that is, the Opaque Type is 4, indicating that this is the No. 4 packet in the OSPF RFC4970 protocol); the packet identifier (that is, the Opaque ID, Corresponding to 0); advertising router (Advertising Router); link state serial number (LS Sequence Number); link state check (LS Checksum); length (Length) and TLVs.
  • the packet type that is, the Opaque Type is 4, indicating that this is the No. 4 packet in the OSPF RFC4970 protocol
  • the packet identifier that is, the Opaque ID, Corresponding to 0
  • advertising router Advertising Router
  • link state serial number LS Sequence Number
  • link state check LS Checksum
  • length Length
  • TLVs TLVs
  • Figure 2(b) is a format diagram of extended TLVs in the extended OSPF RFC4970 protocol message.
  • the extended TLVs include a type field (for example, the content of the Type field may be 1, 2, 3, etc., and 1 may be defined to indicate that the content corresponding to the Value is the identifier of the control device)
  • the length field that is, Length, which means that the content corresponding to Value accounts for 4 bytes
  • the attribute field that is, Value, the corresponding content may be 1.1.1, which indicates the specific content of the identifier of the control device).
  • the No. 4 packet is sent by the control device to the network device supporting the IGP during system initialization, so that the network device supporting the IGP obtains the device identifier of the control device.
  • Figure 2 (c) is a format of a packet header of a protocol packet extending the Router-LSA type.
  • the packet header of the extended protocol-LSA protocol packet contains the packet type (that is, the Opaque Type is 5, indicating that this is the extended Router-LSA type 5 in the OSPF protocol.
  • Packet packet identifier (ie, Opaque ID, corresponding to 0); advertising router identifier (Advertising Router); link state serial number (LS Sequence Number); link state check (LS Checksum); length (Length) and Extend TLVs.
  • the advertisement router identifier can be used to indicate the identifier of the control device.
  • Figure 2 (d) is a format diagram of protocol packets obtained by extending the Router-LSA type by the extended TLVs.
  • the extended TLVs include a type field (Type: 1, indicating that the first type of LSA is extended); a length field (Longth); and an attribute field (Value, as shown in Figure 2(e). Shown).
  • Figure 2(e) is a format diagram corresponding to the attribute field in Figure 2(d).
  • the attribute field contains the link status identifier (Link State ID); the advertising router (Advertising Router); the link state serial number (LS Sequence Number); the link status check. (LS Checksum); Length (Length); Link ID (Link ID); Link Data (Link Data).
  • the advertised router identifier may be the device identifier of the first network device, or may be the device identifier of the second network device.
  • a packet is The advertised router identifier may be the device identifier of the first network device; the advertised router identifier of the other packet may be the device identifier of the second network device, that is, one The packet carries the device identifier of a network device.
  • the extended TLVs are obtained by extending the Router-LSA type, and can also be obtained through the Network-LSA type or through the Summary-LSA.
  • Step 202 The first network device advertises link state information between the first network device and the second network device that are carried in the network network topology information.
  • the first network device stores link state information between the first network device and the second network device included in the network topology information into a link state database;
  • the first network device advertises a link state broadcast LSA, where the LSA includes link state information between the first network device and the second network device, and Link state information between the first network device and other IGP-enabled network devices.
  • the control device Since the first network device acquires link state information between the second network device that does not support the IGP through the control device, and notifies the link state information to other network devices that support the IGP, the control device is controlled by one control device.
  • Network devices that support IGP in multiple network devices access network devices that do not support IGP.
  • Embodiment 3 is a diagrammatic representation of Embodiment 3
  • FIG. 3 is a schematic structural diagram of a link state information notification method according to Embodiment 3 of the present invention.
  • the method can be as follows.
  • Step 301 The first network device receives network topology information sent by the control device.
  • the network topology information includes an identifier of the control device, link state information between the first network device and the second network device generated by the control device, and the first network device and other supporting IGPs. Link status information between network devices.
  • step 301 when receiving the network topology information sent by the control device, the first network device determines whether the identifier of the control device carried in the network topology information is the same as the identifier of the locally stored control device.
  • the network topology information includes the device identifier of the network device corresponding to the link state information generated by the control device, that is, the device identifier of the first network device and the device identifier of the second network device in the embodiment of the present invention. ).
  • the first network device determines, according to the device identifier of the network device that is carried in the network topology information, whether the link state information generated by the control device is related to the first network device.
  • the device identifier of the network device carried in the network topology information is the same as the device identifier of the first network device, determining that the link state information generated by the control device is related to the first network device.
  • the device identifier of the network device that is carried in the network topology information is different from the device identifier of the first network device, determining that the link state information generated by the control device is not related to the first network device.
  • the first network device receives network topology information that is sent by the control device based on the extended IGP.
  • extended IGP in the third embodiment of the present invention is the same as the extended IGP in the second embodiment of the present invention, and details are not described herein.
  • Step 302 The first network device advertises link state information between the first network device and the second network device that is carried in the network topology information, and between the first network device and other supporting IGP devices. Link status information.
  • the first network device advertises, by using the LSA, link state information between the first network device and the second network device that are carried in the network topology information, and the first network device and other support. Link status information between IGP devices.
  • the LSA here may be generated by the control device proxying the first network device. That is, link state information between the first network device and the second network device and link state information between the first network device and other supporting IGP devices are described in the LSA.
  • Step 303 The first network device preferentially performs route calculation according to the link state information carried in the network topology information.
  • step 303 when performing the route calculation, the first network device preferentially selects the link state information carried in the network topology information sent by the control device to perform route calculation.
  • the control device Since the first network device acquires link state information between the second network device that does not support the IGP through the control device, and notifies the link state information to other network devices that support the IGP, the control device is controlled by one control device.
  • the network device supporting the IGP in the plurality of network devices accesses the network device that does not support the IGP, thereby optimizing the routing between the plurality of network devices controlled by the control device.
  • Embodiment 4 is a diagrammatic representation of Embodiment 4:
  • FIG. 4 is a schematic structural diagram of a link state information advertisement device according to Embodiment 4 of the present invention.
  • the link state information notification device respectively has the functions described in Embodiments 1 to 3 of the present invention.
  • the link state information advertising device includes: a receiving module 41 and an advertising module 42, wherein:
  • the receiving module 41 is configured to receive network topology information that is sent by the control device, where the network topology information includes link state information between the first network device and the second network device that are generated by the control device, where The first network device supports an internal network protocol IGP, and the second network device does not support the IGP;
  • the notification module 42 is configured to notify the link state information between the first network device and the second network device that are carried in the network topology information that is received by the receiving module.
  • the notification module 42 is configured to: store, by the first network device, link state information between the first network device and the second network device carried in the network topology information into a link state database;
  • the receiving module 41 is specifically configured to receive network topology information that is sent by the control device based on the routing system interface I2RS protocol.
  • the network topology information further includes an identifier of the control device
  • the receiving module 41 is specifically configured to receive network topology information that is sent by the control device based on the extended IGP.
  • the notification module 42 is specifically configured to store link state information between the first network device and the second network device included in the network topology information into a link state database;
  • the network topology information further includes link state information between the first network device and other IGP-enabled network devices;
  • the notification module 42 is further configured to notify link state information between the first network device and the other supporting IGP device carried in the network topology information.
  • the link state information advertising device further includes: a route calculation module 43, where:
  • the route calculation module 43 is configured to perform route calculation based on the link state information carried in the network topology information.
  • the link state information advertising device further includes: a determining module 44, where:
  • the determining module 44 is configured to determine, after the receiving module receives the network topology information sent by the control device, and before the advertising module announces the link state information between the first network device and the second network device,
  • the identifier of the control device included in the network topology information is the same as the identifier of the locally stored control device.
  • the extended IGP includes an extended routing link state broadcast Router-LSA and an extended network link state broadcast Networ-LSA.
  • the determining module is used in both the second scenario and the third scenario, but the routing computing module performs the calculation in the third scenario according to the manner described in the embodiment of the present invention.
  • the link state information advertisement device in the embodiment of the present invention may be a network element independent of the network device, or may be a logical component integrated in the network device, which is not specifically limited herein.
  • the link state information notification device acquires the link state information between the second network device that does not support the IGP through the control device, and notifies the link state information to other network devices that support the IGP, the control is implemented in one control.
  • the network device supporting the IGP among the plurality of network devices controlled by the device accesses the network device that does not support the IGP, thereby optimizing the routing between the plurality of network devices controlled by the control device.
  • Embodiment 5 is a diagrammatic representation of Embodiment 5:
  • FIG. 5 is a schematic structural diagram of a link state information advertisement device according to Embodiment 5 of the present invention.
  • the link state information notification device has a function of performing the first embodiment of the present invention to the third embodiment of the present invention.
  • the link state information notification device may adopt a general computer system structure, and the computer system may be a processor-based computer.
  • the link state information advertising device entity includes at least one processor 51, a communication bus 52, a memory 53, and at least one communication interface 54.
  • the processor 51 can be a general purpose central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits for controlling the execution of the program of the present invention.
  • CPU central processing unit
  • ASIC application-specific integrated circuit
  • the communication bus 52 can include a path for communicating information between the components.
  • the communication interface 54 uses devices such as any transceiver for communicating with other devices or communication networks, such as Ethernet, Radio Access Network (RAN), Wireless Local Area Networks (WLAN), and the like.
  • RAN Radio Access Network
  • WLAN Wireless Local Area Networks
  • the computer system includes one or more memories 53, which may be read-only memory (ROM) or other types of static storage devices that can store static information and instructions, random access memory (RAM) or Other types of dynamic storage devices that can store information and instructions, or can be electrically erasable programmable read-only memory (EEPROM), CD-ROM (Compact Disc Read-Only Memory, CD-ROM) ) or other disc storage, optical disc storage (including compact discs, laser discs, optical discs, digital versatile discs, Blu-ray discs, etc.), disk storage media or other magnetic storage devices, or capable of carrying or storing in the form of instructions or data structures.
  • ROM read-only memory
  • RAM random access memory
  • EEPROM electrically erasable programmable read-only memory
  • CD-ROM Compact Disc Read-Only Memory
  • CD-ROM Compact Disc Read-Only Memory
  • optical disc storage including compact discs, laser discs, optical discs, digital versatile discs, Blu-ray discs, etc.
  • the memory 53 is used to store application code for executing the solution of the present invention, and the application code for executing the solution of the present invention is stored in a memory and controlled by the processor 51 for execution.
  • the processor 51 is configured to execute an application stored in the memory 53.
  • Network topology information sent by the control device, where the network topology information includes link state information between the first network device and the second network device generated by the control device, where the first network device supports internal Network protocol IGP, the second network device does not support IGP;
  • the processor 51 is specifically configured to perform:
  • the processor 51 is specifically configured to perform:
  • the network topology information sent by the receiving control device based on the routing system interface I2RS protocol.
  • the network topology information further includes an identifier of the control device.
  • the processor 51 is specifically configured to perform:
  • the receiving control device is based on network topology information transmitted by the extended IGP.
  • the processor 51 is specifically configured to perform:
  • the network topology information further includes link state information between the first network device and other IGP-enabled network devices.
  • the processor 51 is specifically configured to perform:
  • the processor 51 is specifically configured to perform:
  • the route calculation is performed according to the link state information carried in the network topology information.
  • the processor 51 is specifically configured to perform:
  • the identifier of the control device included in the topology information is the same as the identifier of the locally stored control device.
  • the extended IGP includes an extended routing link state broadcast Router-LSA and an extended network link state broadcast Networ-LSA.
  • the link state information notification device acquires the link state information between the second network device that does not support the IGP through the control device, and notifies the link state information to other network devices that support the IGP, the control is implemented in one control.
  • the network device supporting the IGP among the plurality of network devices controlled by the device accesses the network device that does not support the IGP, thereby optimizing the routing between the plurality of network devices controlled by the control device.
  • embodiments of the present invention can be provided as a method, apparatus (device), or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment, or a combination of software and hardware. Moreover, the invention can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) including computer usable program code.
  • a computer-usable storage media including but not limited to disk storage, CD-ROM, optical storage, etc.
  • the computer program instructions can also be stored in a computer readable memory that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture comprising the instruction device.
  • the apparatus implements the functions specified in one or more blocks of a flow or a flow and/or block diagram of the flowchart.
  • These computer program instructions can also be loaded onto a computer or other programmable data processing device such that a series of operational steps are performed on a computer or other programmable device to produce computer-implemented processing for execution on a computer or other programmable device.
  • the instructions provide steps for implementing the functions specified in one or more of the flow or in a block or blocks of a flow diagram.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

本发明公开了一种链路状态信息通告方法和设备,包括:第一网络设备接收控制设备发送的网络拓扑信息,其中,所述网络拓扑信息中包括了所述控制设备生成的所述第一网络设备与第二网络设备之间的链路状态信息,所述第一网络设备支持内部网络协议IGP,所述第二网络设备不支持IGP,所述第一网络设备通告所述网络拓扑信息中携带的所述第一网络设备与第二网络设备之间的链路状态信息,由于第一网络设备通过控制设备获取了与不支持IGP的第二网络设备之间的链路状态信息,并将该链路状态信息通告给其他支持IGP的网络设备,实现了在一个控制设备控制的多个网络设备中支持IGP的网络设备访问不支持IGP的网络设备,从而优化了控制设备控制的多个网络设备之间的路由。

Description

一种链路状态信息通告方法和设备
本申请要求于2014年8月30日提交中国专利局、申请号为CN 201410438928.8、发明名称为“一种链路状态信息通告方法和设备”的中国专利申请的优先权,其全部内容通过引用结合在本申请中。
技术领域
本发明涉及软件定义网SDN技术领域,尤其涉及一种链路状态信息通告方法和设备。
背景技术
在软件定义网络(英文:Software Defined Network;缩写:SDN)场景中,不同控制点支持不同协议。例如:控制转发表的控制点支持Open flow(开放流)协议;控制路由表的控制点支持路由系统接口(英文:Interface to the Routing System;缩写:I2RS)协议;等等。
目前,在SDN场景中提出了内部网关协议(英文:Interior Gateway Protocol;缩写:IGP)。所谓IGP是一种专用于自治网络系统中各个网关间交换数据流通道信息的协议。
在实际应用中,一个控制设备控制的多个网络设备中,有些网络设备支持IGP,而有些网络设备由于硬件配置较低不支持IGP。支持IGP的网络设备无法访问不支持IGP的网络设备。
因此,对于一个控制设备控制的多个网络设备中,如何实现支持IGP的网络设备能够访问不支持IGP的网络设备成为亟需解决的问题。
发明内容
有鉴于此,本发明实施例提供了一种链路状态信息通告方法和设备,用于解决在一个控制设备控制的多个网络设备中支持IGP的网络设备无法访问不支持IGP的网络设备的问题。
根据本发明的第一方面,提供了一种链路状态信息通告方法,包括:
第一网络设备接收控制设备发送的网络拓扑信息,其中,所述网络拓扑信息中包括了所述控制设备生成的所述第一网络设备与第二网络设备之间的链路状态信息,所述第一网络设备支持内部网络协议IGP,所述第二网络设备不支持IGP;
所述第一网络设备通告所述网络拓扑信息中携带的所述第一网络设备与第二网络设备之间的链路状态信息。
结合本发明第一方面可能的实施方式,在第一种可能的实施方式中,所述第一网络设备通告所述第一网络设备与第二网络设备之间的链路状态信息,包括:
所述第一网络设备将所述网络拓扑信息中携带的所述第一网络设备与第二网络设备之间的链路状态信息存储至链路状态数据库中;
针对当前的所述链路状态数据库,所述第一网络设备通告链路状态广播LSA,其中,所述LSA中包括了所述第一网络设备与第二网络设备之间的链路状态信息和所述第一网络设备与其他支持IGP的网络设备之间的链路状态信息。
结合本发明第一方面可能的实施方式,或者结合本发明第一方面的第一种可能的实施方式,在第二种可能的实施方式中,所述第一网络设备接收控制设备发送的网络拓扑信息,包括:
所述第一网络设备接收控制设备基于路由系统接口I2RS协议发送的网络拓扑信息。
结合本发明第一方面可能的实施方式,在第三种可能的实施方式中,所述网络拓扑信息中还包括所述控制设备的标识;
所述第一网络设备接收控制设备发送的网络拓扑信息,包括:
所述第一网络设备接收控制设备基于扩展的IGP发送的网络拓扑信息。
结合本发明第一方面的第三种可能的实施方式,在第四种可能的实施方式中,所述第一网络设备通告所述第一网络设备与第二网络设备之间的链路 状态信息,包括:
所述第一网络设备将所述网络拓扑信息中包括的所述第一网络设备与第二网络设备之间的链路状态信息存储至链路状态数据库中;
针对当前的所述链路状态数据库,所述第一网络设备通告链路状态广播LSA,其中,所述LSA中包括了所述第一网络设备与第二网络设备之间的链路状态信息和所述第一网络设备与其他支持IGP的网络设备之间的链路状态信息。
结合本发明第一方面的第三种可能的实施方式,在第五种可能的实施方式中,所述网络拓扑信息中还包括第一网络设备与其他支持IGP的网络设备之间的链路状态信息;
相应地,所述方法还包括:所述第一网络设备通告所述网络拓扑信息中携带的所述第一网络设备与其他支持IGP设备之间的链路状态信息。
结合本发明第一方面的第五种可能的实施方式,在第六种可能的实施方式中,所述方法还包括:
所述第一网络设备优先根据所述网络拓扑信息中携带的链路状态信息进行路由计算。
结合本发明第一方面的第三种可能的实施方式,或者结合本发明第一方面的第四种可能的实施方式,或者结合本发明第一方面的第五种可能的实施方式,或者结合本发明第一方面的第六种可能的实施方式,在第七种可能的实施方式中,在所述第一网络设备接收控制设备发送的网络拓扑信息之后,以及所述第一网络设备通告所述第一网络设备与第二网络设备之间的链路状态信息之前,还包括:
所述第一网络设备确定接收到的所述网络拓扑信息中包含的所述控制设备的标识与本地存储的控制设备的标识相同。
结合本发明第一方面的第三种可能的实施方式,或者结合本发明第一方面的第四种可能的实施方式,或者结合本发明第一方面的第五种可能的实施方式,或者结合本发明第一方面的第六种可能的实施方式,或者结合本发明 第一方面的第七种可能的实施方式,在第八种可能的实施方式中,所述扩展的IGP包括了扩展路由链路状态广播Router-LSA和扩展网络链路状态广播Networ-LSA。
根据本发明的第二方面,提供了一种链路状态信息通告设备,包括:
接收模块,用于接收控制设备发送的网络拓扑信息,其中,所述网络拓扑信息中包括了所述控制设备生成的第一网络设备与第二网络设备之间的链路状态信息,所述第一网络设备支持内部网络协议IGP,所述第二网络设备不支持IGP;
通告模块,用于通告所述接收模块接收到的所述网络拓扑信息中携带的第一网络设备与第二网络设备之间的链路状态信息。
结合本发明第二方面可能的实施方式,在第一种可能的实施方式中,其特征在于,
所述通告模块,具体用于所述第一网络设备将所述网络拓扑信息中携带的第一网络设备与第二网络设备之间的链路状态信息存储至链路状态数据库中;
针对当前的所述链路状态数据库,通告链路状态广播LSA,其中,所述LSA中包括了第一网络设备与第二网络设备之间的链路状态信息和第一网络设备与其他支持IGP的网络设备之间的链路状态信息。
结合本发明第二方面可能的实施方式,或者结合本发明第二方面的第一种可能的实施方式,在第二种可能的实施方式中,所述接收模块,具体用于接收控制设备基于路由系统接口I2RS协议发送的网络拓扑信息。
结合本发明第二方面可能的实施方式,在第三种可能的实施方式中,所述网络拓扑信息中还包括所述控制设备的标识;
所述接收模块,具体用于接收控制设备基于扩展的IGP发送的网络拓扑信息。
结合本发明第二方面的第三种可能的实施方式,在第四种可能的实施方式中,所述通告模块,具体用于将所述网络拓扑信息中包括的第一网络设备 与第二网络设备之间的链路状态信息存储至链路状态数据库中;
针对当前的所述链路状态数据库,通告链路状态广播LSA,其中,所述LSA中包括了第一网络设备与第二网络设备之间的链路状态信息和第一网络设备与其他支持IGP的网络设备之间的链路状态信息。
结合本发明第二方面的第三种可能的实施方式,在第五种可能的实施方式中,所述网络拓扑信息中还包括第一网络设备与其他支持IGP的网络设备之间的链路状态信息;
所述通告模块,还用于通告所述网络拓扑信息中携带的第一网络设备与其他支持IGP设备之间的链路状态信息。
结合本发明第二方面的第五种可能的实施方式,在第六种可能的实施方式中,所述链路状态信息通告设备还包括:
路由计算模块,用于优先根据所述网络拓扑信息中携带的链路状态信息进行路由计算。
结合本发明第二方面的第三种可能的实施方式,或者结合本发明第二方面的第四种可能的实施方式,或者结合本发明第二方面的第五种可能的实施方式,或者结合本发明第二方面的第六种可能的实施方式,在第七种可能的实施方式中,所述链路状态信息通告设备还包括:确定模块,其中:
所述确定模块,用于在所述接收模块接收控制设备发送的网络拓扑信息之后,以及所述通告模块通告第一网络设备与第二网络设备之间的链路状态信息之前,确定接收到的所述网络拓扑信息中包含的所述控制设备的标识与本地存储的控制设备的标识相同。
结合本发明第二方面的第三种可能的实施方式,或者结合本发明第二方面的第四种可能的实施方式,或者结合本发明第二方面的第五种可能的实施方式,或者结合本发明第二方面的第六种可能的实施方式,或者结合本发明第二方面的第七种可能的实施方式,在第八种可能的实施方式中,所述扩展的IGP包括了扩展路由链路状态广播Router-LSA和扩展网络链路状态广播Networ-LSA。
本发明有益效果如下:
本发明实施例第一网络设备接收控制设备发送的网络拓扑信息,其中,所述网络拓扑信息中包括了所述控制设备生成的所述第一网络设备与第二网络设备之间的链路状态信息,所述第一网络设备支持内部网络协议IGP,所述第二网络设备不支持IGP,所述第一网络设备通告所述网络拓扑信息中携带的所述第一网络设备与第二网络设备之间的链路状态信息,由于第一网络设备通过控制设备获取了与不支持IGP的第二网络设备之间的链路状态信息,并将该链路状态信息通告给其他支持IGP的网络设备,实现了在一个控制设备控制的多个网络设备中支持IGP的网络设备访问不支持IGP的网络设备。
附图说明
为了更清楚地说明本发明实施例中的技术方案,下面将对实施例描述中所需要使用的附图作简要介绍,显而易见地,下面描述中的附图仅仅是本发明的一些实施例,对于本领域的普通技术人员来讲,在不付出创造性劳动性的前提下,还可以根据这些附图获得其他的附图。
图1为本发明实施例一提供的一种链路状态信息通告方法的流程示意图;
图2为本发明实施例二提供的一种网络拓扑状态调整方法的流程示意图;
图2(a)为扩展的OSPF RFC4970协议报文格式图;
图2(b)为扩展的OSPF RFC4970协议报文中扩展的TLVs的格式图;
图2(c)为扩展Router-LSA类型的协议报文的报文头格式图;
图2(d)为扩展TLVs通过扩展Router-LSA类型得到的协议报文的格式图;
图2(e)为图2(d)中属性字段对应的格式图;
图3为本发明实施例三提供的一种链路状态信息通告方法的结构示意图;
图4为本发明实施例四提供的一种链路状态信息通告设备的结构示意图;
图5为本发明实施例五提供的一种链路状态信息通告设备的结构示意图。
具体实施方式
为了实现本发明的目的,本发明实施例提供了一种链路状态信息通告方法和设备,第一网络设备接收控制设备发送的网络拓扑信息,其中,所述网络拓扑信息中包括了所述控制设备生成的所述第一网络设备与第二网络设备之间的链路状态信息,所述第一网络设备支持内部网络协议IGP,所述第二网络设备不支持IGP,所述第一网络设备通告所述网络拓扑信息中携带的所述第一网络设备与第二网络设备之间的链路状态信息,由于第一网络设备通过控制设备获取了与不支持IGP的第二网络设备之间的链路状态信息,并将该链路状态信息通告给其他支持IGP的网络设备,实现了在一个控制设备控制的多个网络设备中支持IGP的网络设备访问不支持IGP的网络设备。
下面结合说明书附图对本发明各个实施例作进一步地详细描述。显然,所描述的实施例仅仅是本发明一部分实施例,而不是全部的实施例。基于本发明中的实施例,本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其它实施例,都属于本发明保护的范围。
实施例一:
如图1所述,为本发明实施例一提供的一种链路状态信息通告方法的流程示意图。所述方法可以如下所述。
步骤101:第一设备接收控制设备发送的网络拓扑信息。
其中,所述网络拓扑信息中包括了所述控制设备生成的所述第一网络设备与第二网络设备之间的链路状态信息,所述第一设备支持IGP,所述第二设备不支持IGP。
所述链路状态信息中至少包含了端口、链路类型、带宽中的一种或者多种。
在步骤101中,控制设备控制第一网络设备所在的网络设备集合以及控制第二网络设备所在的网络设备集合。
其中,第一网络设备所在的网络设备集合中所包含的网络设备支持IGP, 第二网络设备所在的网络设备中所包含的网络设备不支持IGP。
由于两个网络设备集合不能共同支持IGP,使得第一网络设备无法访问第二网络设备。也就意味着,第一网络设备与第二网络设备之间不存在路由路径。
作为第一网络设备和第二网络设备共同的控制设备,控制设备能够获取第一网络设备的网际协议(英文:Internetwork Protocol;缩写:IP)地址、端口等信息;也能够获取第二网络设备的IP地址、端口等信息;还能够生成第一网络设备与第二网络设备之间的链路状态信息。
需要说明的是,第一网络设备与第二网络设备之间的链路状态信息可以包括了双向的链路状态信息,即通告者为第一网络设备,由第一网络设备到第二网络设备的链路状态信息;通告者为第二网络设备,由第二网络设备到第一网络设备的链路状态信息。
为了实现第一网络设备能够访问第二网络设备,使第一网络设备与第二网络设备之间存在路由路径,控制设备发送网络拓扑信息给第一网络设备,告知第一网络设备与第二网络设备之间的链路状态信息。
具体地,所述第一网络设备接收控制设备基于路由系统接口I2RS协议发送的网络拓扑信息。
步骤102:所述第一网络设备通告所述网络拓扑信息中携带的所述第一网络设备与第二网络设备之间的链路状态信息。
在步骤102中,所述第一网络设备将所述网络拓扑信息中携带的所述第一网络设备与第二网络设备之间的链路状态信息存储至第一网络设备自身的链路状态数据库中。
针对当前的所述链路状态数据库,所述第一网络设备通告链路状态广播(英文:Link State Advertisement;缩写:LSA)。
其中,所述LSA中包括了所述网络拓扑信息中携带的所述第一网络设备与第二网络设备之间的链路状态信息和所述第一网络设备与其他支持IGP的网络设备之间的链路状态信息。
需要说明的是,IGP域可以是开放式最短路径优先协议(英文:Open Shortest Path First;缩写:OSPF)域,也可以是中间系统到中间系统协议(英文:Intermediate System to Intermediate System;缩写:ISIS)域中,这里不做限定。
通过本发明实施例一的方案,第一网络设备接收控制设备发送的网络拓扑信息,其中,所述网络拓扑信息中包括了所述控制设备生成的所述第一网络设备与第二网络设备之间的链路状态信息,所述第一网络设备支持内部网络协议IGP,所述第二网络设备不支持IGP,所述第一网络设备通告所述网络拓扑信息中携带的所述第一网络设备与第二网络设备之间的链路状态信息,由于第一网络设备通过控制设备获取了与不支持IGP的第二网络设备之间的链路状态信息,并将该链路状态信息通告给其他支持IGP的网络设备,实现了在一个控制设备控制的多个网络设备中支持IGP的网络设备访问不支持IGP的网络设备。
实施例二:
如图2所示,为本发明实施例二提供的一种链路状态信息通告方法的结构示意图。所述方法可以如下所述。
步骤201:第一网络设备接收控制设备发送的网络拓扑信息。
其中,网络拓扑信息中包括了所述控制设备的标识和所述控制设备生成的所述第一网络设备与第二网络设备之间的链路状态信息。
在步骤201中,第一网络设备在接收到控制设备发送的网络拓扑信息时,判断所述网络拓扑信息中携带的所述控制设备的标识是否与本地存储的控制设备的标识相同。
在所述网络拓扑信息中携带的所述控制设备的标识与本地存储的控制设备的标识相同时,执行后续操作。
应理解,网络拓扑信息中包括了所述控制设备生成的链路状态信息对应的网络设备的设备标识(即在本发明实施例中的第一网络设备的设备标识和第二网络设备的设备标识)。
第一网络设备在接收到控制设备发送的网络拓扑信息时,根据所述网络拓扑信息中携带的网络设备的设备标识,判断所述控制设备生成的链路状态信息是否与第一网络设备相关。
具体地,当所述网络拓扑信息中携带的网络设备的设备标识与第一网络设备的设备标识相同时,确定所述控制设备生成的链路状态信息与第一网络设备相关。
当所述网络拓扑信息中携带的网络设备的设备标识与第一网络设备的设备标识不相同时,确定所述控制设备生成的链路状态信息与第一网络设备不相关。
具体地,所述第一网络设备接收控制设备基于扩展的IGP发送的网络拓扑信息。
需要说明的是,这里涉及的扩展的IGP与标准的IGP的区别在于:
本发明实施例中涉及到的扩展的IGP中包括了控制设备的标识对应的字段,使得支持IGP的网络设备能够获取控制设备的标识,例如:Router-ID。
例如:IGP协议报文的扩展可以按照如下图所示的通过扩展OSPF协议报文实现,也可以通过扩展其他协议报文实现,这里不做具体限定。
需要说明的是,扩展的IGP包括了扩展OSPF协议报文头,还包括了扩展Router-LSA类型以及扩展Network-LSA类型。
例如:在OSPF RFC4970协议报文头中增加TLV字段,而增加的TLV字段的内容用来表示支持IGP的网络设备的控制设备的标识。
图2(a)为扩展的OSPF RFC4970协议报文格式图。
从图2(a)中可以看出,OSPF RFC4970协议报文包含了报文类型(即Opaque Type为4,说明这是OSPF RFC4970协议中的4号报文);报文标识(即Opaque ID,对应0);通告路由器标识(Advertising Router);链路状态序列号(LS Sequence Number);链路状态校验(LS Checksum);长度(Length)和TLVs。
图2(b)为扩展的OSPF RFC4970协议报文中扩展的TLVs的格式图。
从图2(b)中可以看出,扩展的TLVs中包括了类型字段(例如:Type字段的内容可以是1、2、3等等,可以定义1表示Value对应的内容为控制设备的标识);长度字段(即Length,表示Value对应的内容占4字节);属性字段(即Value,对应的内容可以是1.1.1,表示控制设备的标识的具体内容)。
需要说明的是,一般该4号报文在系统初始化时由控制设备发送给支持IGP的网络设备,使支持IGP的网络设备获取控制设备的设备标识。
图2(c)为扩展Router-LSA类型的协议报文的报文头格式图。
从图2(c)中可以看出,扩展Router-LSA类型的协议报文的报文头包含了报文类型(即Opaque Type为5,说明这是OSPF协议中扩展Router-LSA类型的5号报文);报文标识(即Opaque ID,对应0);通告路由器标识(Advertising Router);链路状态序列号(LS Sequence Number);链路状态校验(LS Checksum);长度(Length)和扩展TLVs。
需要说明的是,通告路由器标识可以用来表示控制设备的标识。
图2(d)为扩展TLVs通过扩展Router-LSA类型得到的协议报文的格式图。
从图2(d)中可以看出,扩展的TLVs中包括了类型字段(Type:1,表明扩展了第一类LSA);长度字段(Longth);属性字段(Value,如图2(e)所示)。
图2(e)为图2(d)中属性字段对应的格式图。
从图2(e)中可以看出,属性字段包含了链路状态标识(即Link State ID);通告路由器标识(Advertising Router);链路状态序列号(LS Sequence Number);链路状态校验(LS Checksum);长度(Length);链路标识(即Link ID);链路数据(即Link Data)等。
需要说明的是,通告路由器标识可以是第一网络设备的设备标识,也可以是第二网络设备的设备标识,当控制设备通过扩展的IGP向第一网络设备发送报文时,一个报文的通告路由器标识可以是第一网络设备的设备标识;另一报文的通告路由器标识可以是第二网络设备的设备标识,也就是说一个 报文中携带一个网络设备的设备标识。
需要说明的是,扩展TLVs通过扩展Router-LSA类型得到之外,还可以通过Network-LSA类型得到,或者通过Summary-LSA得到。
步骤202:所述第一网络设备通告所述网络网络拓扑信息中携带的所述第一网络设备与第二网络设备之间的链路状态信息。
所述第一网络设备将所述网络拓扑信息中包括的所述第一网络设备与第二网络设备之间的链路状态信息存储至链路状态数据库中;
针对当前的所述链路状态数据库,所述第一网络设备通告链路状态广播LSA,其中,所述LSA中包括了所述第一网络设备与第二网络设备之间的链路状态信息和所述第一网络设备与其他支持IGP的网络设备之间的链路状态信息。
由于第一网络设备通过控制设备获取了与不支持IGP的第二网络设备之间的链路状态信息,并将该链路状态信息通告给其他支持IGP的网络设备,实现了在一个控制设备控制的多个网络设备中支持IGP的网络设备访问不支持IGP的网络设备。
实施例三:
如图3所示,为本发明实施例三提供的一种链路状态信息通告方法的结构示意图。所述方法可以如下所述。
步骤301:第一网络设备接收控制设备发送的网络拓扑信息。
其中,网络拓扑信息中包含了所述控制设备的标识、所述控制设备生成的所述第一网络设备与第二网络设备之间的链路状态信息和所述第一网络设备与其他支持IGP的网络设备之间的链路状态信息。
在步骤301中,第一网络设备在接收到控制设备发送的网络拓扑信息时,判断所述网络拓扑信息中携带的所述控制设备的标识是否与本地存储的控制设备的标识相同。
在所述网络拓扑信息中携带的所述控制设备的标识与本地存储的控制设备的标识相同时,执行后续操作。
应理解,网络拓扑信息中包括了所述控制设备生成的链路状态信息对应的网络设备的设备标识(即在本发明实施例中的第一网络设备的设备标识和第二网络设备的设备标识)。
第一网络设备在接收到控制设备发送的网络拓扑信息时,根据所述网络拓扑信息中携带的网络设备的设备标识,判断所述控制设备生成的链路状态信息是否与第一网络设备相关。
具体地,当所述网络拓扑信息中携带的网络设备的设备标识与第一网络设备的设备标识相同时,确定所述控制设备生成的链路状态信息与第一网络设备相关。
当所述网络拓扑信息中携带的网络设备的设备标识与第一网络设备的设备标识不相同时,确定所述控制设备生成的链路状态信息与第一网络设备不相关。
具体地,所述第一网络设备接收控制设备基于扩展的IGP发送的网络拓扑信息。
需要说明的是,本发明实施例三中涉及的扩展的IGP与本发明实施例二中涉及的扩展的IGP的方式相同,这里不做赘述。
步骤302:所述第一网络设备通告所述网络拓扑信息中携带的所述第一网络设备与第二网络设备之间的链路状态信息和所述第一网络设备与其他支持IGP设备之间的链路状态信息。
在步骤302中,所述第一网络设备通过LSA通告所述网络拓扑信息中携带的所述第一网络设备与第二网络设备之间的链路状态信息和所述第一网络设备与其他支持IGP设备之间的链路状态信息。
这里的LSA可以是由控制设备代理第一网络设备产生的。即在LSA中描述了所述第一网络设备与第二网络设备之间的链路状态信息和所述第一网络设备与其他支持IGP设备之间的链路状态信息。
步骤303:所述第一网络设备优先根据所述网络拓扑信息中携带的链路状态信息进行路由计算。
在步骤303中,第一网络设备在进行路由计算时,优先选择控制设备发送的网络拓扑信息中携带的链路状态信息进行路由计算。
由于第一网络设备通过控制设备获取了与不支持IGP的第二网络设备之间的链路状态信息,并将该链路状态信息通告给其他支持IGP的网络设备,实现了在一个控制设备控制的多个网络设备中支持IGP的网络设备访问不支持IGP的网络设备,从而优化了控制设备控制的多个网络设备之间的路由。
实施例四:
如图4所示,为本发明实施例四提供的一种链路状态信息通告设备的结构示意图。所述链路状态信息通告设备分别具备了本发明实施例一至三中描述的功能。所述链路状态信息通告设备包括:接收模块41和通告模块42,其中:
接收模块41,用于接收控制设备发送的网络拓扑信息,其中,所述网络拓扑信息中包括了所述控制设备生成的第一网络设备与第二网络设备之间的链路状态信息,所述第一网络设备支持内部网络协议IGP,所述第二网络设备不支持IGP;
通告模块42,用于通告所述接收模块接收到的所述网络拓扑信息中携带的第一网络设备与第二网络设备之间的链路状态信息。
第一种应用场景:
所述通告模块42,具体用于所述第一网络设备将所述网络拓扑信息中携带的第一网络设备与第二网络设备之间的链路状态信息存储至链路状态数据库中;
针对当前的所述链路状态数据库,通告链路状态广播LSA,其中,所述LSA中包括了第一网络设备与第二网络设备之间的链路状态信息和第一网络设备与其他支持IGP的网络设备之间的链路状态信息。
所述接收模块41,具体用于接收控制设备基于路由系统接口I2RS协议发送的网络拓扑信息。
第二种应用场景:
所述网络拓扑信息中还包括所述控制设备的标识;
所述接收模块41,具体用于接收控制设备基于扩展的IGP发送的网络拓扑信息。
所述通告模块42,具体用于将所述网络拓扑信息中包括的第一网络设备与第二网络设备之间的链路状态信息存储至链路状态数据库中;
针对当前的所述链路状态数据库,通告链路状态广播LSA,其中,所述LSA中包括了第一网络设备与第二网络设备之间的链路状态信息和第一网络设备与其他支持IGP的网络设备之间的链路状态信息。
第三应用场景:
所述网络拓扑信息中还包括第一网络设备与其他支持IGP的网络设备之间的链路状态信息;
所述通告模块42,还用于通告所述网络拓扑信息中携带的第一网络设备与其他支持IGP设备之间的链路状态信息。
可选地,所述链路状态信息通告设备还包括:路由计算模块43,其中:
路由计算模块43,用于优先根据所述网络拓扑信息中携带的链路状态信息进行路由计算。
可选地,所述链路状态信息通告设备还包括:确定模块44,其中:
所述确定模块44,用于在所述接收模块接收控制设备发送的网络拓扑信息之后,以及所述通告模块通告第一网络设备与第二网络设备之间的链路状态信息之前,确定接收到的所述网络拓扑信息中包含的所述控制设备的标识与本地存储的控制设备的标识相同。
所述扩展的IGP包括了扩展路由链路状态广播Router-LSA和扩展网络链路状态广播Networ-LSA。
需要说明的是,确定模块在第二场景和第三场景中都使用,但是路由计算模块在第三场景中按照本发明实施例所述的方式进行计算。
本发明实施例所述的链路状态信息通告设备可以是独立于网络设备的网元,也可以是集成在网络设备中的逻辑部件,这里不做具体限定。
由于链路状态信息通告设备通过控制设备获取了与不支持IGP的第二网络设备之间的链路状态信息,并将该链路状态信息通告给其他支持IGP的网络设备,实现了在一个控制设备控制的多个网络设备中支持IGP的网络设备访问不支持IGP的网络设备,从而优化了控制设备控制的多个网络设备之间的路由。
实施例五:
如图5所示,为本发明实施例五提供的一种链路状态信息通告设备的结构示意图。所述链路状态信息通告设备具备执行本发明实施例一至本发明实施例三的功能,所述链路状态信息通告设备可以采用通用计算机系统结构,计算机系统可具体是基于处理器的计算机。所述链路状态信息通告设备实体包括至少一个处理器51,通信总线52,存储器53以及至少一个通信接口54。
处理器51可以是一个通用中央处理器(CPU),微处理器,特定应用集成电路(application-specific integrated circuit,ASIC),或一个或多个用于控制本发明方案程序执行的集成电路。
其中,所述通信总线52可包括一通路,在上述组件之间传送信息。所述通信接口54,使用任何收发器一类的装置,用于与其他设备或通信网络通信,如以太网,无线接入网(RAN),无线局域网(Wireless Local Area Networks,WLAN)等。
计算机系统包括一个或多个存储器53,可以是只读存储器(read-only memory,ROM)或可存储静态信息和指令的其他类型的静态存储设备,随机存取存储器(random access memory,RAM)或者可存储信息和指令的其他类型的动态存储设备,也可以是电可擦可编程只读存储器(Electrically Erasable Programmable Read-Only Memory,EEPROM)、只读光盘(Compact Disc Read-Only Memory,CD-ROM)或其他光盘存储、光碟存储(包括压缩光碟、激光碟、光碟、数字通用光碟、蓝光光碟等)、磁盘存储介质或者其他磁存储设备、或者能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质,但不限于此。这些存储器通过总线与 处理器相连接。
其中,所述存储器53用于存储执行本发明方案的应用程序代码,执行本发明方案的应用程序代码保存在存储器中,并由处理器51来控制执行。所述处理器51用于执行所述存储器53中存储的应用程序。
在一种可能的实施方式中,当上述应用程序被所述处理器51执行时,实现如下功能:
接收控制设备发送的网络拓扑信息,其中,所述网络拓扑信息中包括了所述控制设备生成的第一网络设备与第二网络设备之间的链路状态信息,所述第一网络设备支持内部网络协议IGP,所述第二网络设备不支持IGP;
通告所述网络拓扑信息中携带的第一网络设备与第二网络设备之间的链路状态信息。
在一种可能的实施方式中,所述处理器51,具体用于执行:
将所述网络拓扑信息中携带的所述第一网络设备与第二网络设备之间的链路状态信息存储至链路状态数据库中;
针对当前的所述链路状态数据库,通告链路状态广播LSA,其中,所述LSA中包括了第一网络设备与第二网络设备之间的链路状态信息和第一网络设备与其他支持IGP的网络设备之间的链路状态信息。
在一种可能的实施方式中,所述处理器51,具体用于执行:
接收控制设备基于路由系统接口I2RS协议发送的网络拓扑信息。
可选地,所述网络拓扑信息中还包括所述控制设备的标识;
在一种可能的实施方式中,所述处理器51,具体用于执行:
接收控制设备基于扩展的IGP发送的网络拓扑信息。
在一种可能的实施方式中,所述处理器51,具体用于执行:
将所述网络拓扑信息中携带的所述第一网络设备与第二网络设备之间的链路状态信息存储至链路状态数据库中;
针对当前的所述链路状态数据库,通告链路状态广播LSA,其中,所述LSA中包括了第一网络设备与第二网络设备之间的链路状态信息和第一网络 设备与其他支持IGP的网络设备之间的链路状态信息。
可选地,所述网络拓扑信息中还包括第一网络设备与其他支持IGP的网络设备之间的链路状态信息;
在一种可能的实施方式中,所述处理器51,具体用于执行:
通告所述网络拓扑信息中携带的所述第一网络设备与其他支持IGP设备之间的链路状态信息。
在一种可能的实施方式中,所述处理器51,具体用于执行:
优先根据所述网络拓扑信息中携带的链路状态信息进行路由计算。
在一种可能的实施方式中,所述处理器51,具体用于执行:
在所述信号接收器接收控制设备发送的网络拓扑信息之后,以及所述信号发射器通告所述第一网络设备与第二网络设备之间的链路状态信息之前,确定接收到的所述网络拓扑信息中包含的所述控制设备的标识与本地存储的控制设备的标识相同。
所述扩展的IGP包括了扩展路由链路状态广播Router-LSA和扩展网络链路状态广播Networ-LSA。
由于链路状态信息通告设备通过控制设备获取了与不支持IGP的第二网络设备之间的链路状态信息,并将该链路状态信息通告给其他支持IGP的网络设备,实现了在一个控制设备控制的多个网络设备中支持IGP的网络设备访问不支持IGP的网络设备,从而优化了控制设备控制的多个网络设备之间的路由。
本领域的技术人员应明白,本发明的实施例可提供为方法、装置(设备)、或计算机程序产品。因此,本发明可采用完全硬件实施例、完全软件实施例、或结合软件和硬件方面的实施例的形式。而且,本发明可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器、CD-ROM、光学存储器等)上实施的计算机程序产品的形式。
本发明是参照根据本发明实施例的方法、装置(设备)和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图和/ 或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器,使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方式工作的计算机可读存储器中,使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品,该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上,使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理,从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
尽管已描述了本发明的优选实施例,但本领域内的技术人员一旦得知了基本创造性概念,则可对这些实施例作出另外的变更和修改。所以,所附权利要求意欲解释为包括优选实施例以及落入本发明范围的所有变更和修改。
显然,本领域的技术人员可以对本发明进行各种改动和变型而不脱离本发明的精神和范围。这样,倘若本发明的这些修改和变型属于本发明权利要求及其等同技术的范围之内,则本发明也意图包含这些改动和变型在内。

Claims (18)

  1. 一种链路状态信息通告方法,其特征在于,包括:
    第一网络设备接收控制设备发送的网络拓扑信息,其中,所述网络拓扑信息中包括了所述控制设备生成的所述第一网络设备与第二网络设备之间的链路状态信息,所述第一网络设备支持内部网络协议IGP,所述第二网络设备不支持IGP;
    所述第一网络设备通告所述网络拓扑信息中携带的所述第一网络设备与第二网络设备之间的链路状态信息。
  2. 如权利要求1所述的方法,其特征在于,所述第一网络设备通告所述第一网络设备与第二网络设备之间的链路状态信息,包括:
    所述第一网络设备将所述网络拓扑信息中携带的所述第一网络设备与第二网络设备之间的链路状态信息存储至链路状态数据库中;
    针对当前的所述链路状态数据库,所述第一网络设备通告链路状态广播LSA,其中,所述LSA中包括了所述第一网络设备与第二网络设备之间的链路状态信息和所述第一网络设备与其他支持IGP的网络设备之间的链路状态信息。
  3. 如权利要求1至2任一所述的方法,其特征在于,所述第一网络设备接收控制设备发送的网络拓扑信息,包括:
    所述第一网络设备接收控制设备基于路由系统接口I2RS协议发送的网络拓扑信息。
  4. 如权利要求1所述的方法,其特征在于,所述网络拓扑信息中还包括所述控制设备的标识;
    所述第一网络设备接收控制设备发送的网络拓扑信息,包括:
    所述第一网络设备接收控制设备基于扩展的IGP发送的网络拓扑信息。
  5. 如权利要求4所述的方法,其特征在于,所述第一网络设备通告所述第一网络设备与第二网络设备之间的链路状态信息,包括:
    所述第一网络设备将所述网络拓扑信息中包括的所述第一网络设备与第二网络设备之间的链路状态信息存储至链路状态数据库中;
    针对当前的所述链路状态数据库,所述第一网络设备通告链路状态广播LSA,其中,所述LSA中包括了所述第一网络设备与第二网络设备之间的链路状态信息和所述第一网络设备与其他支持IGP的网络设备之间的链路状态信息。
  6. 如权利要求4所述的方法,其特征在于,所述网络拓扑信息中还包括第一网络设备与其他支持IGP的网络设备之间的链路状态信息;
    相应地,所述方法还包括:所述第一网络设备通告所述网络拓扑信息中携带的所述第一网络设备与其他支持IGP设备之间的链路状态信息。
  7. 如权利要求6所述的方法,其特征在于,所述方法还包括:
    所述第一网络设备优先根据所述网络拓扑信息中携带的链路状态信息进行路由计算。
  8. 如权利要求4至7任一所述的方法,其特征在于,在所述第一网络设备接收控制设备发送的网络拓扑信息之后,以及所述第一网络设备通告所述第一网络设备与第二网络设备之间的链路状态信息之前,还包括:
    所述第一网络设备确定接收到的所述网络拓扑信息中包含的所述控制设备的标识与本地存储的控制设备的标识相同。
  9. 如权利要求4至8任一所述的方法,其特征在于,所述扩展的IGP包括了扩展路由链路状态广播Router-LSA和扩展网络链路状态广播Networ-LSA。
  10. 一种链路状态信息通告设备,其特征在于,包括:
    接收模块,用于接收控制设备发送的网络拓扑信息,其中,所述网络拓扑信息中包括了所述控制设备生成的第一网络设备与第二网络设备之间的链路状态信息,所述第一网络设备支持内部网络协议IGP,所述第二网络设备不支持IGP;
    通告模块,用于通告所述接收模块接收到的所述网络拓扑信息中携带的 第一网络设备与第二网络设备之间的链路状态信息。
  11. 如权利要求10所述的链路状态信息通告设备,其特征在于,
    所述通告模块,具体用于所述第一网络设备将所述网络拓扑信息中携带的第一网络设备与第二网络设备之间的链路状态信息存储至链路状态数据库中;
    针对当前的所述链路状态数据库,通告链路状态广播LSA,其中,所述LSA中包括了第一网络设备与第二网络设备之间的链路状态信息和第一网络设备与其他支持IGP的网络设备之间的链路状态信息。
  12. 如权利要求10至11任一所述的链路状态信息通告设备,其特征在于,
    所述接收模块,具体用于接收控制设备基于路由系统接口I2RS协议发送的网络拓扑信息。
  13. 如权利要求10所述的链路状态信息通告设备,其特征在于,所述网络拓扑信息中还包括所述控制设备的标识;
    所述接收模块,具体用于接收控制设备基于扩展的IGP发送的网络拓扑信息。
  14. 如权利要求13所述的链路状态信息通告设备,其特征在于,
    所述通告模块,具体用于将所述网络拓扑信息中包括的第一网络设备与第二网络设备之间的链路状态信息存储至链路状态数据库中;
    针对当前的所述链路状态数据库,通告链路状态广播LSA,其中,所述LSA中包括了第一网络设备与第二网络设备之间的链路状态信息和第一网络设备与其他支持IGP的网络设备之间的链路状态信息。
  15. 如权利要求13所述的链路状态信息通告设备,其特征在于,所述网络拓扑信息中还包括第一网络设备与其他支持IGP的网络设备之间的链路状态信息;
    所述通告模块,还用于通告所述网络拓扑信息中携带的第一网络设备与其他支持IGP设备之间的链路状态信息。
  16. 如权利要求15所述的链路状态信息通告设备,其特征在于,所述链路状态信息通告设备还包括:
    路由计算模块,用于优先根据所述网络拓扑信息中携带的链路状态信息进行路由计算。
  17. 如权利要求13至16任一所述的链路状态信息通告设备,其特征在于,所述链路状态信息通告设备还包括:确定模块,其中:
    所述确定模块,用于在所述接收模块接收控制设备发送的网络拓扑信息之后,以及所述通告模块通告第一网络设备与第二网络设备之间的链路状态信息之前,确定接收到的所述网络拓扑信息中包含的所述控制设备的标识与本地存储的控制设备的标识相同。
  18. 如权利要求13至17任一所述的链路状态信息通告设备,其特征在于,所述扩展的IGP包括了扩展路由链路状态广播Router-LSA和扩展网络链路状态广播Networ-LSA。
PCT/CN2015/088277 2014-08-30 2015-08-27 一种链路状态信息通告方法和设备 WO2016029862A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP15835964.6A EP3179679B1 (en) 2014-08-30 2015-08-27 Method and device for link state information announcement
US15/443,385 US10200204B2 (en) 2014-08-30 2017-02-27 Link state information advertisement method and device

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201410438928.8 2014-08-30
CN201410438928.8A CN105376162B (zh) 2014-08-30 2014-08-30 一种链路状态信息通告方法和设备

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US15/443,385 Continuation US10200204B2 (en) 2014-08-30 2017-02-27 Link state information advertisement method and device

Publications (1)

Publication Number Publication Date
WO2016029862A1 true WO2016029862A1 (zh) 2016-03-03

Family

ID=55377981

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2015/088277 WO2016029862A1 (zh) 2014-08-30 2015-08-27 一种链路状态信息通告方法和设备

Country Status (4)

Country Link
US (1) US10200204B2 (zh)
EP (1) EP3179679B1 (zh)
CN (1) CN105376162B (zh)
WO (1) WO2016029862A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018219103A1 (zh) * 2017-05-31 2018-12-06 华为技术有限公司 一种链路状态确定方法及设备

Families Citing this family (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105376162B (zh) * 2014-08-30 2019-05-10 华为技术有限公司 一种链路状态信息通告方法和设备
US10958559B2 (en) * 2016-06-15 2021-03-23 Juniper Networks, Inc. Scaled inter-domain metrics for link state protocols
CN107517157B (zh) * 2016-06-16 2020-09-11 华为技术有限公司 一种路径确定方法、装置和系统
WO2019111154A1 (en) * 2017-12-04 2019-06-13 Telefonaktiebolaget Lm Ericsson (Publ) Network link verification
PL3598698T3 (pl) * 2018-07-20 2021-04-19 Ovh Sposób i urządzenie do migracji urządzeń
US10999183B2 (en) 2019-08-12 2021-05-04 Juniper Networks, Inc. Link state routing protocol adjacency state machine
CN113014481B (zh) * 2019-12-20 2022-06-24 华为技术有限公司 传输链路状态通告的方法、装置、设备及存储介质
CN111444186B (zh) * 2020-03-30 2023-08-04 北京信而泰科技股份有限公司 一种信息管理方法、测试仪、设备和计算机可读存储介质

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101547139A (zh) * 2008-03-28 2009-09-30 华为技术有限公司 网络拓扑变化的通告方法及装置
CN102263688A (zh) * 2010-05-26 2011-11-30 华为技术有限公司 一种选择标签转发路径的方法和网络装置
CN102437932A (zh) * 2011-12-30 2012-05-02 华为技术有限公司 低速链路链路状态信息管理的方法、装置及系统
CN103036756A (zh) * 2011-10-08 2013-04-10 中兴通讯股份有限公司 一种基于共享通道的混合环网保护方法及系统
US20140146828A1 (en) * 2009-03-04 2014-05-29 Telefonaktiebolaget L M Ericsson (Publ) Ldp igp synchronization for broadcast networks

Family Cites Families (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN100527745C (zh) * 2006-12-31 2009-08-12 中国科学院计算技术研究所 一种ospf全邻接条件下lsa被动式采集方法
CN101330448B (zh) * 2007-06-21 2010-12-08 华为技术有限公司 一种通告链路状态信息及确定组播转发路径的方法及装置
CN101453405A (zh) * 2007-11-30 2009-06-10 华为技术有限公司 建立路由的方法、系统和控制管理设备
US20110022728A1 (en) * 2009-07-22 2011-01-27 Telefonaktiebolaget Lm Ericsson (Publ) Link state routing protocols for database synchronization in gmpls networks
US9100328B1 (en) * 2012-03-12 2015-08-04 Juniper Networks, Inc. Forwarding mechanisms for fast reroute using maximally redundant trees
US9571387B1 (en) * 2012-03-12 2017-02-14 Juniper Networks, Inc. Forwarding using maximally redundant trees
CN102664809B (zh) * 2012-04-28 2015-05-13 杭州华三通信技术有限公司 一种igp与ldp在广播网同步的实现方法及路由器
US9178801B1 (en) * 2012-06-27 2015-11-03 Juniper Networks, Inc. Automated service discovery in computer networks
CN103067277B (zh) 2013-01-06 2016-06-22 华为技术有限公司 建立控制通道的方法、转发设备和控制设备
US10193801B2 (en) * 2013-11-25 2019-01-29 Juniper Networks, Inc. Automatic traffic mapping for multi-protocol label switching networks
CN105376162B (zh) * 2014-08-30 2019-05-10 华为技术有限公司 一种链路状态信息通告方法和设备

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101547139A (zh) * 2008-03-28 2009-09-30 华为技术有限公司 网络拓扑变化的通告方法及装置
US20140146828A1 (en) * 2009-03-04 2014-05-29 Telefonaktiebolaget L M Ericsson (Publ) Ldp igp synchronization for broadcast networks
CN102263688A (zh) * 2010-05-26 2011-11-30 华为技术有限公司 一种选择标签转发路径的方法和网络装置
CN103036756A (zh) * 2011-10-08 2013-04-10 中兴通讯股份有限公司 一种基于共享通道的混合环网保护方法及系统
CN102437932A (zh) * 2011-12-30 2012-05-02 华为技术有限公司 低速链路链路状态信息管理的方法、装置及系统

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3179679A4 *

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018219103A1 (zh) * 2017-05-31 2018-12-06 华为技术有限公司 一种链路状态确定方法及设备
CN108989204A (zh) * 2017-05-31 2018-12-11 华为技术有限公司 一种链路状态确定方法及设备
US11245615B2 (en) 2017-05-31 2022-02-08 Huawei Technologies Co., Ltd. Method for determining link state, and device

Also Published As

Publication number Publication date
CN105376162B (zh) 2019-05-10
US20170171058A1 (en) 2017-06-15
EP3179679B1 (en) 2023-05-17
CN105376162A (zh) 2016-03-02
EP3179679A4 (en) 2017-10-11
EP3179679A1 (en) 2017-06-14
US10200204B2 (en) 2019-02-05

Similar Documents

Publication Publication Date Title
WO2016029862A1 (zh) 一种链路状态信息通告方法和设备
US10924389B2 (en) Segment routing based on maximum segment identifier depth
US11128611B2 (en) Method for determining path computation element and communications device
US10291555B2 (en) Service based intelligent packet-in buffering mechanism for openflow switches by having variable buffer timeouts
EP2869512A1 (en) Dynamic area filtering for link-state routing protocols
US9509631B2 (en) Quality of service (QoS) for information centric networks
WO2015109821A1 (zh) 一种管理业务链的方法、系统及装置
EP3190754B1 (en) Method and apparatus for processing a modified packet
EP3043520B1 (en) Forwarding entry generation method, forwarding node, and controller
WO2017055965A1 (en) Route refresh mechanism for border gateway protocol link state
WO2018121257A1 (zh) 报文发送方法、装置、系统以及存储介质
EP4046351A1 (en) Rtps discovery in kubernetes
US20230084470A1 (en) Method and apparatus for controlling network traffic path
US20150256452A1 (en) System and method for reflecting fec route information
EP3166263B1 (en) Routing calculation method and device for trill isis
US20210281507A1 (en) Parameter notification and obtaining methods and devices, and storage medium
CN106576076B (zh) 互联网交换点的路由控制方法
EP3016330A1 (en) Route table entries generating method and border gateway protocol speaker
WO2017162202A1 (zh) 链路状态信息处理
WO2014164073A1 (en) System and method for reflecting forwarding equivalence class route information
WO2023173989A1 (zh) 转发表的生成方法及装置、存储介质、电子装置
US11627093B1 (en) Generic layer independent fragmentation of non-internet protocol frames
WO2020021558A1 (en) Methods, apparatus and machine-readable media relating to path computation in a communication network
WO2023016550A1 (zh) 一种路由发送方法及设备
WO2014149960A1 (en) System, method and apparatus for lsp setup using inter-domain abr indication

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 15835964

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

REEP Request for entry into the european phase

Ref document number: 2015835964

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 2015835964

Country of ref document: EP