WO2020135395A1

WO2020135395A1 - Notification method and device for prefix identifier of cross-interior gateway protocol

Info

Publication number: WO2020135395A1
Application number: PCT/CN2019/127806
Authority: WO
Inventors: 王九明
Original assignee: 华为技术有限公司
Priority date: 2018-12-25
Filing date: 2019-12-24
Publication date: 2020-07-02
Also published as: CN109861913A; CN109861913B

Abstract

Disclosed in the embodiments of the present application are a notification method and device for a prefix identifier of a cross-interior gateway protocol (IGP), for use in implementing notification of a prefix identifier of cross-network equipment. For cross-network equipment of the cross-IGP, the cross-network equipment is respectively accessed to a first network using a first protocol and a second network using a second protocol; wherein the first protocol and the second protocol are both different IGPs; due to the fact that the first protocol and the second protocol are enabled at a local loopback interface of the cross-network equipment, the cross-network equipment can notify the prefix identifier of the cross-network equipment to equipment in the first network according to the first protocol and can also notify the prefix identifier of the cross-network equipment to equipment in the second network according to the second protocol. The problem caused by a cross-network equipment cross-IGP domain mutual leading prefix identifier is solved; that the prefix identifier can use an SR calculation path in a first network and a second network related to the cross-network equipment is ensured; the problem that service recovery is slow due to the fact that a fault scene does not occur is solved; and stability and reliability are improved.

Description

Prefix identification method and device across internal gateway protocol

This application requires the priority of the Chinese patent application filed on December 25, 2018, by the State Intellectual Property Office of China, application number 201811592852.9, and the application name is "a method and device for announcing prefix identification across internal gateway protocols." Incorporated by reference in this application.

Technical field

This application relates to the field of communications, and in particular to the announcement of prefix identification across internal gateway protocols in segmented routing.

Background technique

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.

In the SR scheme, prefix identification (prefix-sid) is used to identify a certain device in the network, and it is unique within the autonomous domain of the network. The prefix-sid can be specified in LoopBack0 of the local loopback interface. By enabling the Interior Gateway (Interior Gateway Protocol, IGP) protocol in LoopBack0, the prefix-sid is notified to each device in the network.

There is only one prefix-sid for a device, which is configured in LoopBack0. It is the key to calculating the path of the SR protocol. For devices that access multiple networks and use different IGP protocols across multiple IGP protocols, this cross-IGP How to announce the prefix-sid of the device of the protocol, so that the devices in multiple networks accessed by the device of the cross-IGP protocol can effectively use the prefix-sid of the device of the cross-IGP protocol is an urgent problem to be solved at present .

Summary of the invention

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.

In a first aspect, an embodiment of the present application provides a prefix identification notification method across internal gateway protocols. For cross-network devices across internal gateway protocols, the cross-network devices are respectively connected to the first network and the second protocol using the first protocol In the second network, 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. Solve the problem caused by the cross-precision of the prefix identification between IGP domains across network devices, and ensure that the prefix identification can use SR to calculate the path in the first network and the second network related to the cross-network equipment, and there is no failure scenario that leads to slow service recovery. Problems, improving stability and reliability.

In a possible implementation manner, the first protocol may be the OSPF protocol, and the second protocol may be the ISIS protocol.

In a possible implementation manner, in order to reduce the bandwidth consumption of the cross-network device notifying the device in the first network of its own prefix-sid, 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. In the embodiment of the present application, before the cross-network device announces the prefix identifier of the cross-network device to the devices in the first network according to the first protocol, 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.

In a possible implementation manner, in order to reduce the bandwidth consumption of the cross-network device notifying the device in the second network of its own prefix-sid, 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. In the embodiment of the present application, before the cross-network device announces the prefix identifier of the cross-network device to the devices in the second network according to the second protocol, 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.

In a possible implementation manner, it can be ensured that the prefix identifier can use the SR calculation path in both the first network and the second network related to the cross-network device. When the device in the first network sends the data packet to the device in the second network, 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.

In a second aspect, 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.

In a possible implementation manner, the first protocol is an open shortest path first OSPF protocol, and the second protocol is an intermediate system-intermediate system ISIS protocol.

In a possible implementation manner, 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.

In a possible implementation manner, 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.

In a possible implementation manner, 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.

In a third aspect, 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.

According to a fourth aspect, 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.

BRIEF DESCRIPTION

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;

3 is a schematic structural diagram of a cross-network device provided by an embodiment of the present application;

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.

detailed description

The following describes the embodiments of the present application with reference to the drawings.

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 terms "first", "second", "third", "fourth", etc. (if any) in the description and claims of the present invention and the above drawings are used to distinguish similar objects without using To describe a specific order or sequence. It should be understood that the data so used can be interchanged under appropriate circumstances so that the embodiments described herein can be implemented in an order other than what is illustrated or described herein. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions, for example, processes, methods, systems, products or devices that contain a series of steps or units are not necessarily limited to those clearly listed Those steps or units, but may include other steps or units not explicitly listed or inherent to these processes, methods, products, or equipment.

It is understandable that since 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.

For ease of understanding, the description will now be made in conjunction with the scenario shown in FIG. 1, which is a schematic diagram of an application scenario provided by an embodiment of the present application.

As shown in Figure 1, 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, and the network loop between ER and EPC-CE is called the core ring. Among them, 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. In other words, 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.

It can be understood that, 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.

Currently, 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. However, because the local loopback interface of the B device is not enabled with the OSPF protocol, the B device cannot use the OSPF protocol to announce its prefix-sid in the access ring network. For the traditional way in which the B device advertises 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. From the ISIS protocol Obtain the address of the local loopback interface of the B device and the prefix-sid of the B device, thereby introducing the prefix-sid of the B device in the ISIS protocol into the OSPF protocol and notify the device in the access ring network.

However, for the access ring network using the OSPF protocol, the introduction of external routes will generate Link-State Advertisement (LSA) of an external autonomous system (Autonomous System External). Therefore, for a device in the access ring network, it cannot distinguish whether the route introduced by the LSA is the directly connected route of device B or the route learned by device B from the remote end. That is, using the prefix-sid advertised by ASE's LSA, the device in the access ring network cannot determine whether the prefix-sid is the prefix-sid of device B or the prefix-sid learned by device B from the remote end. Therefore, when calculating the data forwarding path, 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. In other words, 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. . Moreover, when the data forwarding fails, 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.

In view of this, 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.

The method is described below with reference to the accompanying drawings. Referring to FIG. 2, this figure 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.

It should be noted that the method for prefix identification notification across internal gateway protocols provided in the embodiments of the present application 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. As an example, the cross-network device may be a switch. As yet another example, the cross-network device may be a router.

In the embodiment of the present application, 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. As an example, the first protocol may be the OSPF protocol, and 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.

Considering that in the traditional technology, when the prefix-sid of a cross-network device is advertised in the first network and the second network, 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. In the embodiment of the present application, 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.

It can be understood that, since the internal gateway protocol used by the first network is 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.

In the embodiment of the present application, 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.

In the embodiment of the present application, 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. For example, as shown in FIG. 1, 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. When data is forwarded, 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. In other words, 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.

In view of this, in a possible implementation manner of the embodiment of the present application, 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. For example, devices A1 and B1 in FIG. 1 have a neighbor relationship, and A2 and B1 also have a neighbor relationship, and so on. In a possible implementation manner of the embodiment of the present application, 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.

In the embodiment of the present application, 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.

In the embodiment of the present application, 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. When data is forwarded, 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. In other words, 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.

In view of this, in a possible implementation manner of the embodiment of the present application, in order to reduce the bandwidth consumption of the cross-network device to notify the device in the second network of its own prefix-sid, 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.

Devices located in the same convergence ring can be understood as devices with neighbor relationships. In a possible implementation manner of the embodiment of the present application, 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.

It should be noted that the embodiment of the present application does not specifically limit the execution steps of step 201 and step 202. Although 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.

It can be known from the above description that, with the solution provided by the embodiments of the present application, for cross-network devices that cross the internal gateway protocol, 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. Solve the problem caused by the cross-precision of the prefix identification between IGP domains across network devices, and ensure that the prefix identification can use SR to calculate the path in the first network and the second network related to the cross-network equipment, and there is no failure scenario that leads to slow service recovery. Problems, improving stability and reliability.

As mentioned above, with the method of the embodiment of the present application, it can be ensured that 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. In the embodiment of the present application, 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. In the embodiment of the present application, 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.

Correspondingly, when the device in the second network sends the data packet to the device in the first network, 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.

As mentioned above, when the first network is the foregoing access ring network, the first network may include several access rings. When there are multiple access rings, each access ring runs SR in the OSPF protocol, and calculates the shortest path according to the SPF of OSPF. Generate a forwarding table for SR-BE. 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.

Correspondingly, when the second network is the aforementioned convergence ring network, the second network may include several convergence rings. When there are multiple 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.

In order to facilitate better implementation of the above solution of the embodiments of the present application, 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.

Referring to FIG. 3, a cross-network device 300 provided by an embodiment of the present application. 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.

Optionally, the first protocol is an open shortest path first OSPF protocol, and the second protocol is an intermediate system-intermediate system ISIS protocol.

Optionally, the cross-network device 300 further includes:

The first notification unit 310 is specifically used for:

Optionally, the cross-network device 300 further includes:

The second notification unit 320 is specifically used for:

Optionally, the cross-network device 300 further includes:

It should be noted that the information interaction and execution process between the above modules/units of the cross-network equipment are based on the same concept as the method embodiments of the embodiments of the present application, and the technical effects brought about by the method implementation of the embodiments of the present application The examples are the same, and the specific content can refer to the description in the method embodiments shown in the foregoing embodiments of the present application, which will not be repeated here.

Next, cross-network devices in embodiments of the present application will be introduced. Referring to FIG. 4, 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. In the embodiment of the present application, 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. 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.

Optionally, 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.

In the embodiment of the present application, 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.

Specifically, 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.

Those skilled in the art can clearly understand that for the convenience and conciseness of the description, the specific working process of the system, device and unit described above can refer to the corresponding process in the foregoing method embodiments, which will not be repeated here.

In the several embodiments provided in this application, it should be understood that the disclosed system, device, and method may be implemented in other ways. For example, the device embodiments described above are only schematic. For example, 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. In addition, 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.

In addition, 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.

If 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. Based on this understanding, 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 .

As mentioned above, the above embodiments are only used to illustrate the technical solutions of the present application, not to limit them; although the present application has been described in detail with reference to the foregoing embodiments, persons of ordinary skill in the art should understand that they can still The technical solutions described in the embodiments are modified, or some of the technical features are equivalently replaced; and these modifications or replacements do not deviate from the spirit and scope of the technical solutions of the embodiments of the present application.

Claims

A prefix identification notification method across internal gateway protocols is characterized in that it is applied to cross-network devices across internal gateway protocols, and the cross-network devices are respectively connected to the first network using the first protocol and the second protocol. In a second network, the first protocol and the second protocol are different internal gateway protocols, and the local loopback interface of the cross-network device enables the first protocol and the second protocol. The method includes:

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 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 method according to claim 1, wherein the first protocol is an open shortest path first OSPF protocol, and the second protocol is an intermediate system-intermediate system ISIS protocol.
The method according to claim 2, wherein before the cross-network device announces the prefix identification of the cross-network device to devices in the first network according to the first protocol, the method further comprises :

The cross-network device establishes an OSPF neighbor with a first device, and the first device is a device in the access ring of the cross-network device in the first network;

The cross-network device notifying the device in the first network of the prefix identifier of the cross-network device according to the first protocol includes:

The cross-network device notifies the first device of the prefix identifier of the cross-network device according to the first protocol.
The method according to claim 2, wherein before the cross-network device announces the prefix identification of the cross-network device to the device in the second network through the second protocol, the method further comprises :

The cross-network device establishes an ISIS neighbor with a second device, and the second device is a device in the convergence ring of the cross-network device in the second network;

The cross-network device notifying the devices in the second network of the prefix identifier of the cross-network device through the second protocol includes:

The cross-network device notifies the second device of the prefix identifier of the cross-network device according to the second protocol.
The method according to any one of claims 1 to 4, wherein the method further comprises:

The cross-network device obtains 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-connect Path information of the shortest path of network equipment;

The cross-network device calculates the shortest path to the device in the second network according to the segmented routing SR protocol, and generates 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.
A cross-network device, characterized in that 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 , The local loopback interface of the cross-network device enables the first protocol and the second protocol, and 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 cross-network device according to claim 6, wherein the first protocol is an open shortest path first OSPF protocol, and the second protocol is an intermediate system-intermediate system ISIS protocol.
The cross-network device according to claim 7, wherein the cross-network device further comprises:

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 according to claim 7, wherein the cross-network device further comprises:

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 according to any one of claims 6-9, wherein the cross-network device further comprises:

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.
A cross-network device, the device includes: a processor and a memory; the memory is used to store instructions;

The processor is configured to execute the instructions in the memory and execute the method according to any one of claims 1-5.
A computer-readable storage medium including instructions, which when executed on a computer, causes the computer to perform the method of any one of claims 1-5 above.