WO2020135395A1 - Procédé et dispositif de notification pour un identifiant de préfixe de protocole de passerelle interne transversal - Google Patents

Procédé et dispositif de notification pour un identifiant de préfixe de protocole de passerelle interne transversal Download PDF

Info

Publication number
WO2020135395A1
WO2020135395A1 PCT/CN2019/127806 CN2019127806W WO2020135395A1 WO 2020135395 A1 WO2020135395 A1 WO 2020135395A1 CN 2019127806 W CN2019127806 W CN 2019127806W WO 2020135395 A1 WO2020135395 A1 WO 2020135395A1
Authority
WO
WIPO (PCT)
Prior art keywords
network
cross
protocol
network device
prefix
Prior art date
Application number
PCT/CN2019/127806
Other languages
English (en)
Chinese (zh)
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 华为技术有限公司
Publication of WO2020135395A1 publication Critical patent/WO2020135395A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/52—Multiprotocol routers

Definitions

  • This application relates to the field of communications, and in particular to the announcement of prefix identification across internal gateway protocols in segmented routing.
  • Segment routing (SR) protocol is a source routing protocol.
  • the source node specifies the path for the application message and converts the path into an ordered segment list and encapsulates it in the message header.
  • the intermediate node of the path It only needs to be forwarded according to the path specified in the packet header.
  • the segment type guides the device to process any instruction of the message, such as forwarding the message to the destination according to the shortest path, forwarding the message through the specified interface, and forwarding the message to the specified application/service instance.
  • the SR protocol can make the network more simplified and has good scalability, so it has become a very promising technology at present.
  • prefix-sid prefix identification
  • IGP Interior Gateway
  • Embodiments of the present application provide a method and apparatus for announcing prefix identifiers across internal gateway protocols to implement announcement of prefix identifiers across network devices.
  • an embodiment of the present application provides a prefix identification notification method across internal gateway protocols.
  • the cross-network devices are respectively connected to the first network and the second protocol using the first protocol
  • the first protocol and the second protocol are different internal gateway protocols. Because the first protocol and the second protocol are enabled on the local loopback interface of the cross-network device, the cross-network device can use the first protocol
  • the prefix identifier of the cross-network device is notified to the device in the first network, and the prefix identifier of the cross-network device may be notified to the device in the second network according to the second protocol.
  • the first protocol may be the OSPF protocol
  • the second protocol may be the ISIS protocol
  • the first device in the first network may be notified of its prefix-sid.
  • the first device refers to a device in the access ring of the cross-network device in the first network.
  • the cross-network device may establish OSPF with the first device Neighbors, so that the first device and the cross-network device are devices in the same access ring.
  • the second device in the second network may be notified of its own prefix-sid.
  • the second device refers to a device in the convergence ring of the cross-network device in the second network.
  • the cross-network device may establish an ISIS with the second device Neighbors, so that the second device and the cross-network device are devices in the same convergence ring.
  • the prefix identifier can use the SR calculation path in both the first network and the second network related to the cross-network device.
  • the specific SR calculation method is as follows: the cross-network device obtains the first segment route from the device in the first network-best effort SR-BE forwarding table; the first SR-BE forwarding table is used to identify the path information of the shortest path from the device in the first network to the cross-network device; the cross-network device calculates according to the segmented routing SR protocol And the shortest path of the device in the second network and generate a second SR-BE forwarding table according to the calculation result; the second SR-BE forwarding table is used to identify the shortest path from the cross-network device to the device in the second network Path information of the path.
  • an embodiment of the present application provides a cross-network device, where the cross-network device is respectively connected to a first network using a first protocol and a second network using a second protocol, the first protocol and the second protocol For different internal gateway protocols, the local loopback interface of the cross-network device enables the first protocol and the second protocol.
  • the cross-network device includes:
  • a first notification unit configured to notify the device in the first network of the prefix identifier of the cross-network device according to the first protocol
  • the second notification unit is configured to announce the prefix identifier of the cross-network device to devices in the second network according to the second protocol.
  • the first protocol is an open shortest path first OSPF protocol
  • the second protocol is an intermediate system-intermediate system ISIS protocol.
  • the cross-network device further includes:
  • a first establishing unit configured to establish an OSPF neighbor with a first device, where the first device is a device in the access ring of the cross-network device in the first network;
  • the first notification unit is specifically used for:
  • the cross-network device notifies the first device of the prefix identifier of the cross-network device according to the first protocol.
  • the cross-network device further includes:
  • a second establishing unit configured to establish an ISIS neighbor with a second device, where the second device is a device in the convergence ring of the cross-network device in the second network;
  • the second notification unit is specifically used for:
  • the cross-network device notifies the second device of the prefix identifier of the cross-network device according to the second protocol.
  • the cross-network device further includes:
  • An obtaining unit configured to obtain a first segmented route-best effort SR-BE forwarding table from the device in the first network; the first SR-BE forwarding table is used to identify the device in the first network to the cross Path information of the shortest path of network equipment;
  • the calculation unit is used to calculate the shortest path with the device in the second network according to the segmented routing SR protocol, and generate a second SR-BE forwarding table according to the calculation result; the second SR-BE forwarding table is used for identification Path information of the shortest path from the cross-network device to the device in the second network.
  • an embodiment of the present application provides a cross-network device, the device includes: a processor and a memory; the memory is used to store instructions; and the processor is used to execute the Instructions to execute the method described in any of the first aspect above.
  • an embodiment of the present application provides a computer-readable storage medium, including instructions, which when executed on a computer, causes the computer to execute the method described in any one of the above first aspects.
  • FIG. 1 is a schematic diagram of an application scenario provided by an embodiment of the present application
  • FIG. 2 is a schematic flowchart of a prefix identification notification method across internal gateway protocols provided by an embodiment of the present application
  • FIG. 3 is a schematic structural diagram of a cross-network device provided by an embodiment of the present application.
  • FIG. 4 is a schematic structural diagram of a cross-network device according to an embodiment of the present application.
  • FIG. 5 is a schematic structural diagram of a cross-network device provided by an embodiment of the present application.
  • Embodiments of the present application provide a prefix identification announcement method across internal gateway protocols, which is used to implement announcement of prefix identification across network devices.
  • the prefix-sid of a device is unique, it is the key to the path calculation of the SR protocol. Therefore, for cross-network devices that are connected to multiple networks and have different gateway protocols used by these multiple networks, how can this prefix-sid be announced in these multiple networks, so that devices in multiple networks can be effectively used
  • the prefix-sid of the device that crosses the IGP protocol is a relatively important issue.
  • FIG. 1 is a schematic diagram of an application scenario provided by an embodiment of the present application.
  • a equipment (including A1, A2) is the base station access equipment; B equipment (including B1 and B2) is the regional aggregation equipment; ER (including ER1 and ER2) is the external routing node; EPC-CE is the core Network edge equipment (Evolved, Core-Customer Edge, EPC-CE); EPC is the core network side equipment.
  • the network loop between device A and device B is called the access ring
  • the network loop between device B and ER is called the convergence ring
  • the network loop between ER and EPC-CE is called the core ring.
  • the network where the access ring is located (hereinafter referred to as the access ring network) uses the IGP protocol as the Open Shortest Path First (Open Shortest Path Fist, OSPF) protocol
  • the network where the convergence ring is located hereinafter referred to as the convergence ring network
  • the adopted IGP protocol is the Intermediate System-Intermediate System (Intermediate System to Intermediate System, ISIS) protocol.
  • the B device is a cross-network device connected to the access ring network using the OSPF protocol and the convergence ring network using the ISIS protocol.
  • the B device when data is exchanged between the A device and the EPC device, the B device needs to be used for data forwarding. Therefore, whether it is a device in the access ring network or a device in the convergence ring network, the SR protocol may need to use the prefix-sid of the B device when calculating the data forwarding path.
  • the local loopback interface of the B device can be enabled with the ISIS protocol. In this way, the B device can use the ISIS protocol to announce its prefix-sid in the convergence ring network.
  • the B device cannot use the OSPF protocol to announce its prefix-sid in the access ring network.
  • the external route can be introduced. Specifically, in the access ring network, the OSPF protocol can be used to redistribute ISIS routes.
  • LSA Link-State Advertisement
  • the active and standby B nodes (B1 and B2 in Figure 1) cannot be selected, which will result in a segmented route in the direction of A->B-best effort (Segment Routing-BestEffort, SR-BE ) Topology Independent-Loop Free (Alternat, TI-LFA) protection cannot be formed.
  • the prefix-sid cannot be used correctly, a protection node cannot be formed, and an effective backup next hop cannot be formed, thereby causing the traffic convergence time to exceed the standard.
  • the prefix-sid of the cross-network equipment cannot be determined, so the cause of the failure cannot be located as soon as possible, resulting in a slower service recovery speed.
  • the embodiments of the present application provide a prefix identification announcement method across internal gateway protocols, which is used to solve the problems in the foregoing prefix identification announcement method.
  • FIG. 2 is a schematic flowchart of a prefix identification notification method across internal gateway protocols according to an embodiment of the present application.
  • the method provided in the embodiments of the present application may be implemented by the following steps 201-202, for example.
  • the method for prefix identification notification across internal gateway protocols can be applied to cross-network devices across internal gateway protocols.
  • the embodiment of the present application does not specifically limit the cross-network device.
  • the cross-network device may be a switch.
  • the cross-network device may be a router.
  • cross-network devices are respectively connected to a first network using a first protocol and a second network using a second protocol.
  • the first protocol and the second protocol are both internal gateway protocols, and the first protocol and the second protocol
  • the second protocol is a different gateway protocol.
  • the embodiment of the present application does not specifically limit the first protocol and the second protocol.
  • the first protocol may be the OSPF protocol
  • the second protocol may be the ISIS protocol.
  • the embodiments of the present application also do not specifically limit the first network and the second network.
  • the first network may be, for example, the access ring network described in FIG. 1; the second network may be, for example, the convergence ring described in FIG. 1 The internet.
  • the local loopback interface of the cross-network device only enables one internal gateway protocol (such as the above mentioned ISIS protocol), therefore, when advertising the prefix-sid of the cross-network device to a network using an internal gateway protocol that is not enabled for the local loopback interface, an external route needs to be introduced, which may affect the calculation of subsequent data forwarding paths. problem.
  • the cross-network device in order to avoid the announcement of the prefix-sid of the cross-network device in the first network or the second network, an external route needs to be introduced, and the local loopback interface of the cross-network device enables the first protocol And the second protocol, so that the cross-network device can announce its own prefix-sid in the first network according to the first protocol, and can also announce its own prefix-sid in the second network according to the second protocol.
  • Step 201 The cross-network device notifies the device in the first network of the prefix identifier of the cross-network device according to the first protocol.
  • the device in the first network may be notified of the prefix-sid of the device in the first network by the cross-network device according to the first protocol. It is determined that the prefix-sid is the prefix-sid of the cross-network device. Further, the prefix-sid can be used to calculate the data forwarding path.
  • the cross-network device may notify the prefix identifier of the cross-network device to all devices in the first network according to the first protocol; or may announce the cross-network to some devices in the first network according to the first protocol
  • the prefix identification of the device is not specifically limited in this embodiment of the present application.
  • the first network when the first network is the foregoing access ring network, it is considered that the first network may include several access rings.
  • the cross-network device may be in one or more of the access rings in the first network.
  • the cross-network devices B1 and B2 are both in the access ring A1-B1- In B2, it is also in the access ring A2-B1-B2.
  • the device in one access ring will not forward the data to the device in another access ring. That is to say, for the first network, other than the devices in the access ring of the cross-network device, other devices will not forward data to the cross-network device.
  • the cross-network device is not included in the forwarding path calculated by other devices. Therefore, other devices do not need to use the prefix-sid of the cross-network device.
  • the cross-network device in order to reduce the bandwidth consumption of the cross-network device notifying its own prefix-sid to the device in the first network, it may be notified to the first device in the first network Its own prefix-sid.
  • the first device refers to a device in the access ring of the cross-network device in the first network.
  • Devices located in the same access ring can be understood as devices with neighbor relationships.
  • devices A1 and B1 in FIG. 1 have a neighbor relationship
  • A2 and B1 also have a neighbor relationship
  • the cross-network device may establish an OSPF neighbor with the first device, so that the first device and the cross-network device are devices in the same access ring.
  • the embodiment of the present application does not specifically limit the specific implementation method of establishing an OSPF neighbor between a network device and a first device, and may use the traditional technology to establish an OSPF neighbor between a network device and a first device to establish an OSPF across the network device and the first device. Neighbor relationship.
  • Step 202 The cross-network device notifies the device in the second network of the prefix identifier of the cross-network device according to the second protocol.
  • the cross-network device may notify the prefix identifier of the cross-network device to all devices in the second network according to the second protocol; or may announce the cross-network to some devices in the second network according to the second protocol
  • the prefix identification of the device is not specifically limited in this embodiment of the present application.
  • the second network when the second network is the foregoing convergence ring network, it is considered that the second network may include several convergence rings.
  • the cross-network device may be in one or more convergence rings among several convergence rings in the second network.
  • devices in one convergence ring will not forward data to devices in another convergence ring. That is to say, in the second network, other than the devices in the convergence ring of the cross-network device, other devices will not forward data to the cross-network device.
  • the cross-network device is not included in the forwarding path calculated by other devices. Therefore, other devices do not need to use the prefix-sid of the cross-network device.
  • the second device in the second network may be notified Its own prefix-sid.
  • the second device refers to a device in the convergence ring of the cross-network device in the second network.
  • the cross-network device may establish an ISIS neighbor with the second device, so that the second device and the cross-network device are devices in the same convergence ring.
  • the embodiment of the present application does not specifically limit the specific implementation method of establishing an ISIS neighbor across a network device and a second device, and may use the method of establishing an ISIS neighbor across a network device and a second device in a conventional technology to establish an ISIS across the network device and the second device. Neighbor relationship.
  • step 201 in FIG. 2 is executed before step 202, this is only a schematic illustration. In practical applications, step 201 may be performed after step 202, and step 201 may also be performed simultaneously with step 202.
  • the cross-network devices are respectively connected to the first network using the first protocol and the second network using the second protocol.
  • the protocol and the second protocol are different internal gateway protocols. Since the first protocol and the second protocol are enabled on the local loopback interface of the cross-network device, the cross-network device can send the devices in the first network according to the first protocol
  • the prefix identifier of the cross-network device is announced, and the prefix identifier of the cross-network device is announced to the device in the second network according to the second protocol.
  • the prefix identifier can use the SR calculation path in both the first network and the second network related to the cross-network device.
  • the following describes the specific SR calculation method when the device in the first network sends the data packet to the device in the second network.
  • the devices in the first network combine the prefix-sid of the cross-network devices and the prefix-sid of other devices in the first network, and use the Shortest Path First (SPF) algorithm to calculate from the device in the first network to the cross-network
  • the shortest path of the device obtains the first segment route identifying the path information of the shortest path-best effort SR-BE forwarding table.
  • the first SR-BE forwarding table may specify, for example, local labels to other routes, outgoing labels, local outgoing interfaces, and next hop IP.
  • the device in the first network encapsulates the first SR-BE forwarding table in the header of the data packet, and forwards the data packet.
  • the device that receives the data packet determines the next hop of the data packet according to the first SR-BE forwarding table in the packet header.
  • the cross-network device may obtain the first SR-BE forwarding table from the device in the first network. Specifically, the cross-network device may obtain the first SR-BE forwarding table according to the packet header of the data packet sent by the device in the first network SR-BE forwarding table.
  • the cross-network device calculates the shortest path with the device in the second network according to the SR protocol, and generates a second SR-BE forwarding table that identifies path information of the shortest path from the cross-network device to the device in the second network.
  • the second SR-BE forwarding table may specify, for example, a local label to another route, an out label, a local out interface, a next hop IP, and so on.
  • the device in the second network may send the data message to the intended recipient of the data message according to the second SR-BE forwarding table.
  • both the first network and the second network can also use SR to calculate the path.
  • the following describes the specific SR calculation method when the device in the second network sends the data packet to the device in the first network.
  • the equipment in the second network combines the prefix-sid of the cross-network equipment and the prefix-sid of the other equipment in the second network, and uses the Shortest Path First (SPF) algorithm to calculate from the equipment in the second network to the cross-network
  • the shortest path of the device obtains the third segment route identifying the path information of the shortest path-best effort SR-BE forwarding table.
  • the device in the second network encapsulates the third SR-BE forwarding table in the header of the data packet, and forwards the data packet.
  • the device that receives the data packet determines the next hop of the data packet according to the third SR-BE forwarding table in the packet header.
  • the cross-network device may obtain the third SR-BE forwarding table from the device in the second network. Specifically, the cross-network device may obtain the third SR-BE forwarding table according to the packet header of the data packet sent by the device in the second network SR-BE forwarding table.
  • the cross-network device calculates the shortest path with the device in the first network according to the SR protocol, and generates a fourth SR-BE forwarding table that identifies the path information of the shortest path from the cross-network device to the device in the first network.
  • the device in the first network may send the data message to the intended recipient of the data message according to the fourth SR-BE forwarding table.
  • the first network when the first network is the foregoing access ring network, the first network may include several access rings.
  • each access ring runs SR in the OSPF protocol, and calculates the shortest path according to the SPF of OSPF.
  • the forwarding table specifies the local label to other routes, the outgoing label, the local outgoing interface, the next-hop IP, etc.
  • the forwarding table for SR-BE can also be called a SR-BE tunnel, thus forming a TI -LFA protection.
  • the second network when the second network is the aforementioned convergence ring network, the second network may include several convergence rings.
  • each convergence ring runs SR in the ISIS protocol, calculates the path according to the SPF of ISIS, and calculates the shortest path. Generate a SR-BE tunnel, thereby forming TI-LFA protection.
  • the following also provides cross-network devices for implementing the above prefix identification notification method across internal gateway protocols.
  • the cross-network device is respectively connected to a first network using a first protocol and a second network using a second protocol, where the first protocol and the second protocol are different internal gateway protocols, and the local loopback of the cross-network device
  • the interface enables the first protocol and the second protocol.
  • the cross-network device 300 specifically includes: a first notification unit 310 and a second notification unit 320.
  • the first notification unit 310 is configured to announce the prefix identifier of the cross-network device to devices in the first network according to the first protocol;
  • the second notification unit 320 is configured to announce the prefix identifier of the cross-network device to devices in the second network according to the second protocol.
  • the first protocol is an open shortest path first OSPF protocol
  • the second protocol is an intermediate system-intermediate system ISIS protocol.
  • the cross-network device 300 further includes:
  • a first establishing unit configured to establish an OSPF neighbor with a first device, where the first device is a device in the access ring of the cross-network device in the first network;
  • the first notification unit 310 is specifically used for:
  • the cross-network device notifies the first device of the prefix identifier of the cross-network device according to the first protocol.
  • the cross-network device 300 further includes:
  • a second establishing unit configured to establish an ISIS neighbor with a second device, where the second device is a device in the convergence ring of the cross-network device in the second network;
  • the second notification unit 320 is specifically used for:
  • the cross-network device notifies the second device of the prefix identifier of the cross-network device according to the second protocol.
  • the cross-network device 300 further includes:
  • An obtaining unit configured to obtain a first segmented route-best effort SR-BE forwarding table from the device in the first network; the first SR-BE forwarding table is used to identify the device in the first network to the cross Path information of the shortest path of network equipment;
  • the calculation unit is used to calculate the shortest path with the device in the second network according to the segmented routing SR protocol, and generate a second SR-BE forwarding table according to the calculation result; the second SR-BE forwarding table is used for identification Path information of the shortest path from the cross-network device to the device in the second network.
  • the cross-network device 400 includes a processor 410, a communication interface 420, and a memory 430.
  • the number of processors 410 in the cross-network device 400 may be one or more, and one processor is used as an example in FIG. 4.
  • the processor 410, the communication interface 420, and the memory 430 may be connected through a bus system or in other ways. In FIG. 4, connection through the bus system 440 is used as an example.
  • the processor 410 may be a central processing unit (CPU), a network processor (NP), or a combination of CPU and NP.
  • the processor 410 may further include a hardware chip.
  • the hardware chip may be an application-specific integrated circuit (ASIC), a programmable logic device (PLD), or a combination thereof.
  • ASIC application-specific integrated circuit
  • PLD programmable logic device
  • the above PLD may be a complex programmable logic device (complex programmable logic device, CPLD), a field programmable logic gate array (field-programmable gate array, FPGA), a general array logic (generic array logic, GAL), or any combination thereof.
  • the memory 430 may include volatile memory (English: volatile memory), such as random-access memory (random-access memory, RAM); the memory 430 may also include non-volatile memory (English: non-volatile memory), such as fast Flash memory (English: flash memory), hard disk drive (HDD) or solid-state drive (SSD); memory 430 may also include a combination of the aforementioned types of memory.
  • volatile memory such as random-access memory (random-access memory, RAM
  • non-volatile memory such as fast Flash memory (English: flash memory), hard disk drive (HDD) or solid-state drive (SSD)
  • HDD hard disk drive
  • SSD solid-state drive
  • the memory 430 stores an operating system and programs, executable modules or data structures, or a subset thereof, or an extended set thereof, where the program may include various operation instructions for implementing various operations.
  • the operating system may include various system programs for implementing various basic services and processing hardware-based tasks.
  • the processor 410 can read the program in the memory 430 to implement the storage method provided by the embodiment of the present application.
  • the bus system 440 may be a peripheral component interconnect (PCI) bus or an extended industry standard architecture (EISA) bus, or the like.
  • the bus system 440 can be divided into an address bus, a data bus, and a control bus. For ease of representation, only a thick line is used in FIG. 4, but it does not mean that there is only one bus or one type of bus.
  • the cross-network device may also have a structure as shown in FIG. 5, and FIG. 5 is a schematic structural diagram of yet another cross-network device provided by the embodiment of the present application.
  • the cross-network device may include a processor main control board 510 and an interface board 520.
  • the main control board 510 includes a processor 501 and a memory 502;
  • the interface board 520 includes a processor 503, a memory 504, and an interface card 505.
  • the processor 505 of the interface board is used to call a program in the memory 502 of the interface board to perform message transmission and reception.
  • the processor 501 of the main control board is used to call the program instructions in the memory of the main control board to announce the prefix-sid of the cross-network device in the first network and the second network.
  • For the 501 reference may be made to the description of the processor 410 above, and for the 502, reference may be made to the description of the memory 430 above, which is not repeated here.
  • Embodiments of the present application also provide a computer-readable storage medium, including instructions, which, when run on a computer, cause the computer to execute the method provided by the above method embodiments.
  • the disclosed system, device, and method may be implemented in other ways.
  • the device embodiments described above are only schematic.
  • the division of the units is only a logical function division, and there may be other divisions in actual implementation, for example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored, or not implemented.
  • the displayed or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection through some interfaces, devices or units, and may be in electrical, mechanical, or other forms.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or may be distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units may be integrated into one unit.
  • the above integrated unit can be implemented in the form of hardware or software function unit.
  • the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it may be stored in a computer-readable storage medium.
  • the technical solution of the present application essentially or part of the contribution to the existing technology or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium , Including several instructions to enable a computer device (which may be a personal computer, server, or network device, etc.) to perform all or part of the steps of the methods described in the embodiments of the present application.
  • the aforementioned storage media include: U disk, mobile hard disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), magnetic disk or optical disk and other media that can store program code .

Landscapes

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

Abstract

Les modes de réalisation de la présente invention concernent un procédé et un dispositif de notification pour un identifiant de préfixe d'un protocole de passerelle interne (IGP) transversal, destiné à être utilisé dans la mise en œuvre d'une notification d'un identifiant de préfixe d'un équipement de réseau transversal. Pour un équipement inter-réseau de l'IGP transversal, l'équipement inter-réseau accède respectivement à un premier réseau à l'aide d'un premier protocole et à un second réseau à l'aide d'un second protocole, le premier protocole et le second protocole étant tous deux des IGP différents ; du fait que le premier protocole et le second protocole sont activés au niveau d'une interface de bouclage local de l'équipement inter-réseau, l'équipement inter-réseau peut notifier l'identifiant de préfixe de l'équipement inter-réseau à un équipement dans le premier réseau selon le premier protocole et peut également notifier l'identifiant de préfixe de l'équipement inter-réseau à un équipement dans le second réseau selon le second protocole. Cela résout le problème causé par un identifiant de préfixe principal et mutuel pour des domaines inter-IGP et des équipements inter-réseau ; cela garantit que l'identifiant de préfixe peut utiliser un chemin de calcul SR dans un premier réseau et un second réseau associés à l'équipement inter- réseau ; cela résout aussi le problème de la lenteur du rétablissement de service en raison de l'absence de scène défaillante ; et enfin, cela améliore la stabilité et la fiabilité.
PCT/CN2019/127806 2018-12-25 2019-12-24 Procédé et dispositif de notification pour un identifiant de préfixe de protocole de passerelle interne transversal WO2020135395A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201811592852.9A CN109861913B (zh) 2018-12-25 2018-12-25 一种跨内部网关协议的前缀标识通告方法和装置
CN201811592852.9 2018-12-25

Publications (1)

Publication Number Publication Date
WO2020135395A1 true WO2020135395A1 (fr) 2020-07-02

Family

ID=66892212

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/127806 WO2020135395A1 (fr) 2018-12-25 2019-12-24 Procédé et dispositif de notification pour un identifiant de préfixe de protocole de passerelle interne transversal

Country Status (2)

Country Link
CN (1) CN109861913B (fr)
WO (1) WO2020135395A1 (fr)

Families Citing this family (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11277334B2 (en) * 2019-07-24 2022-03-15 Juniper Networks, Inc. Using and processing per slice segment identifiers in a network employing segment routing
CN112910773A (zh) * 2019-11-19 2021-06-04 华为技术有限公司 下发oam配置信息的方法及控制节点
CN112929261B (zh) * 2019-12-05 2024-03-12 中兴通讯股份有限公司 分段路由隧道的防断纤方法、装置，入口节点及存储介质
CN110958181B (zh) * 2019-12-06 2021-08-17 Ut斯达康通讯有限公司 ISIS协议发布跨SRv6的切片网络的方法及装置
CN112953822A (zh) * 2019-12-10 2021-06-11 华为技术有限公司 一种减少路由环路的方法、装置及系统
CN111464439B (zh) * 2020-03-31 2022-04-01 新华三信息安全技术有限公司 段标识发布方法和装置
CN114827022A (zh) * 2021-01-18 2022-07-29 华为技术有限公司 路由消息处理方法、发布方法及装置、通信系统
CN115086222B (zh) * 2021-03-15 2023-06-20 中国电信股份有限公司 跨自治域通告方法、自治系统边界路由器和通信系统
CN114696890B (zh) * 2022-03-30 2023-06-20 中国联合网络通信集团有限公司 承载网络及其中断处理方法、设备、存储介质

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101485160A (zh) * 2006-07-05 2009-07-15 思科技术公司 用于高效确定计算机网络中可接受的基于链路的无环路替代的技术
US9660897B1 (en) * 2013-12-04 2017-05-23 Juniper Networks, Inc. BGP link-state extensions for segment routing
WO2017141079A1 (fr) * 2016-02-15 2017-08-24 Telefonaktiebolaget Lm Ericsson (Publ) Extensions is-is destinées à l'assemblage de chemin flexible et sélection destinée à un routage de segment transitant de trafic et réseaux mpls

Family Cites Families (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7978708B2 (en) * 2004-12-29 2011-07-12 Cisco Technology, Inc. Automatic route tagging of BGP next-hop routes in IGP
CN101355487B (zh) * 2007-07-23 2011-04-27 中国移动通信集团公司 一种标签分发方法及装置
CN102025522B (zh) * 2010-12-21 2012-09-05 北京星网锐捷网络技术有限公司 实现不同ip域之间组播的方法及边界网关路由器
US9979629B2 (en) * 2015-08-21 2018-05-22 Cisco Technology, Inc. Distribution of segment identifiers in network functions virtualization and software defined network environments
CN105827529B (zh) * 2016-05-10 2019-02-26 华为技术有限公司 一种路径建立方法及控制器
CN107770063A (zh) * 2016-08-17 2018-03-06 中兴通讯股份有限公司 报文转发方法及装置
US10110470B2 (en) * 2016-09-14 2018-10-23 Juniper Networks, Inc. Preventing data traffic loops associated with designated forwarder selection

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101485160A (zh) * 2006-07-05 2009-07-15 思科技术公司 用于高效确定计算机网络中可接受的基于链路的无环路替代的技术
US9660897B1 (en) * 2013-12-04 2017-05-23 Juniper Networks, Inc. BGP link-state extensions for segment routing
WO2017141079A1 (fr) * 2016-02-15 2017-08-24 Telefonaktiebolaget Lm Ericsson (Publ) Extensions is-is destinées à l'assemblage de chemin flexible et sélection destinée à un routage de segment transitant de trafic et réseaux mpls

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
L.GINSBERG ET AL: "Segment Routing Conflict Resolution, draft-ietf-spring-conflict-resolution-03.txt", NETWORK WORKING GROUP INTERNET-DRAFT, 27 April 2017 (2017-04-27), pages 1 - 17, XP015119374 *

Also Published As

Publication number Publication date
CN109861913A (zh) 2019-06-07
CN109861913B (zh) 2020-03-20

Similar Documents

Publication Publication Date Title
WO2020135395A1 (fr) Procédé et dispositif de notification pour un identifiant de préfixe de protocole de passerelle interne transversal
CN108337157B (zh) 一种网络中传输报文的方法和节点
EP3065342B1 (fr) Mise à jour d'itinéraires mac dans une topologie single-active evpn
US9019814B1 (en) Fast failover in multi-homed ethernet virtual private networks
EP3148127A1 (fr) Protection de sortie pour trafic bum avec défaillances de lien dans evpn
EP3151485A1 (fr) Protection de noeud de sortie dans une topologie epvn toujours active
US11611509B2 (en) Communication method, communications device, and communications system
CN112929274A (zh) 一种处理路由的方法、设备及系统
WO2021164249A1 (fr) Procédé, dispositif et système d'envoi de message
US11646960B2 (en) Controller provided protection paths
CN112422307B (zh) Evpn和vpls共存双活的方法、设备及系统
WO2020119644A1 (fr) Procédé, appareil et dispositif de génération d'entrée de transfert
US9154412B2 (en) Multicast label distribution protocol over a remote loop-free alternative
WO2023274083A1 (fr) Procédé et appareil de publication de route, procédé et appareil de réacheminement de paquets, dispositif, et support de stockage
US10033636B1 (en) Ethernet segment aware MAC address learning
US10158567B1 (en) PBB-EVPN customer MAC synchronization among all-active multi-homing PEs
WO2021109997A1 (fr) Procédé et dispositif anti-rupture de fibre pour tunnel de routage de segment, nœud d'entrée et support de données
CN106789523B (zh) 一种逻辑隧道的创建方法及装置
CN113872843B (zh) 一种路由生成方法、路由处理方法及装置
WO2018040614A1 (fr) Procédé, dispositif associé et système d'établissement de trajet commuté par étiquette pour un réseau privé virtuel
CN116530067A (zh) 使用内部网关协议（interior gateway protocol，IGP）的边缘计算数据和服务发现
WO2022257773A1 (fr) Procédé de détection de routage, dispositif, système, et support de stockage
US10924395B2 (en) Seamless multipoint label distribution protocol (mLDP) transport over a bit index explicit replication (BIER) core
WO2024032187A1 (fr) Procédé et appareil de transmission d'informations de routage
WO2023016550A1 (fr) Procédé d'envoi d'itinéraire et dispositif

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: 19901960

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 19901960

Country of ref document: EP

Kind code of ref document: A1