Cross-manufacturer protocol communication method based on controller, medium and equipment

Abstract

The invention provides a cross-manufacturer protocol communication method based on a controller, a medium and equipment, and belongs to the technical field of network communication. According to the invention, network node attributes and SRv6SID are calculated and managed through the controller, and calculation of a network SRv6 forwarding path and an end-to-end path is realized; the controller calculates the Segment List ID or BSID of the corresponding network element according to the attribute of the network element device passed by each path; and the controller deploys a BSID or a Segment List at a starting point of each section of the same manufacturer path according to a calculation analysis result to form an end-to-end SRv6 complete forwarding path so as to realize cross-manufacturer full-path automatic deployment of the SRv6. According to the method, the forwarding path of the SRv6 can be better deployed in the whole life cycle and the whole process, so that the deployability of the SRv6 protocol is more conveniently supported, and the network evolution based on the SRv6 protocol is promoted.

Description

Technical Field

[0001] The present invention belongs to the technical field of network communication, and particularly relates to a method, medium and device for cross-vendor protocol communication based on a controller. Background Art

[0002] Currently, the SRv6 protocol is continuously maturing and more and more deployments are being made. However, the support levels and versions of SRv6 by various vendors are not completely synchronized, and the interoperability is poor, which affects the deployment and operation of the end-to-end full path of the network SRv6. Regarding the compression of the SRH of SRv6, there are currently multiple solutions, and the compatibility of each solution is not high, which also affects the protocol overhead, bearing efficiency, and MTU of SRv6, resulting in the problem of high hardware requirements not being well solved end-to-end.

[0003] In many data networks, there will be forwarding devices from more than one vendor networking, and the support for SRv6 by devices from different vendors is different. Especially for the compression processing method of SRH, there are multiple protocol solutions such as G-SRv6 and uSID. Each solution has no interoperability. This situation brings high costs and risks to the operation and maintenance of the network, and affects the deployment and application of the SRv6 technology in the network. Summary of the Invention

[0004] In view of the deficiencies in the prior art, the present invention provides a method, medium and device for cross-vendor protocol communication based on a controller, and solves the problems of SRv6 deployment and operation of multi-vendor devices through a method for cross-vendor SRv6 protocol communication based on a controller.

[0005] To achieve the above object, the present invention adopts the following technical solutions:

[0006] In a first aspect, the present invention provides a method for cross-vendor protocol communication based on a controller, including:

[0007] Obtain the SRv6 version information of all devices in the network, and initialize the SIDSpaceID of the devices. Each SIDSpaceID corresponds to a SID value space and also corresponds to the devices applying this SID value space;

[0008] According to the division of SIDSpaceID, uniformly allocate BSID to the devices;

[0009] Calculate the end-to-end path of SRv6 according to the path requirements for SRv6;

[0010] According to the forwarding path information in the end-to-end path, organize the SegmentList of the end-to-end path and each segment of the forwarding path. The Segment List is composed of the SID and BSID of the devices on the path;

[0011] Generate the SRH for the end - to - end path and each segment forwarding path according to the Segment List of the end - to - end path and each segment forwarding path, and distribute them to the corresponding nodes in segments.

[0012] The devices at the corresponding nodes forward the SRv6 packets locally according to the obtained SRH.

[0013] Optionally, initializing the SIDSpaceID of the device is specifically as follows:

[0014] Group the devices of the same manufacturer that use the same SID allocation rule into one category, and use the SIDSpaceID for identification.

[0015] Optionally, different manufacturers' devices that support different SRv6 protocols correspond to different SIDSpaceIDs.

[0016] Optionally, calculating the end - to - end path of SRv6 is specifically as follows:

[0017] Based on the whole - network routing information, calculate the end - to - end path of SRv6 according to the service requirements to obtain the complete path of SRv6 from the source node to the destination node, including each logical path of the unified SRv6Policy.

[0018] Optionally, when calculating the path for each logical path, do not consider the differences in the support of the SRv6 protocol version by each node on the path, nor consider the differences in the compression technology protocol for the SRv6 SRH.

[0019] Optionally, the organization method of the Segment List of each segment forwarding path is as follows:

[0020] Obtain the SIDSpaceID corresponding to each segment forwarding path in sequence, and parse the corresponding SRv6 protocol.

[0021] Generate the Segment List of this segment forwarding path according to the parsed SRv6 protocol.

[0022] Optionally, generating the Segment List of this segment forwarding path is specifically as follows:

[0023] For the nodes on each segment forwarding path, according to the parsed SRv6 protocol, use the SIDs of the devices corresponding to the nodes to form the Segment List of the forwarding path.

[0024] For the nodes across SIDSpaceIDs, use the BSIDs allocated to the devices corresponding to the nodes to map the Segment List.

[0025] Optionally, the Segment List of the end-to-end path is organized as follows:

[0026] For the end-to-end path, use the Segment List of each segment forwarding path and the BSID for mapping the Segment List to form the Segment List of the end-to-end path.

[0027] In a second aspect, the present invention provides a computer-readable storage medium storing a computer program, characterized in that the computer program causes a computer to execute the method for controller-based cross-vendor protocol communication as described in the first aspect.

[0028] In a third aspect, the present invention provides an electronic device, including: a memory, a processor, and a computer program stored on the memory and executable on the processor, wherein when the processor executes the computer program, the method for controller-based cross-vendor protocol communication as described in the first aspect is implemented.

[0029] The beneficial effects of the present invention are as follows:

[0030] 1. Through centralized calculation by the controller, the present invention can be compatible with different versions of SRv6, form an end-to-end SRv6 forwarding path, and achieve interoperability of different compression schemes of multi-vendor SRv6 SRH;

[0031] 2. The present invention is compatible with the compression of SRv6 SRH by different vendors, improving the end-to-end forwarding efficiency of SRv6 Policy.

[0032] 3. By means of BSID adhesion, the present invention solves the problem of incompatibility of SRv6 forwarding packets of other vendors by devices of different vendors, enhancing the flexibility of SRv6 deployment.

[0033] In summary, the present invention enhances the compatibility of multi-vendor devices, reduces the network system upgrade and operation and maintenance costs; enhances the deployability of the end-to-end full path of SRv6, reduces the network operation cost; enhances the end-to-end forwarding efficiency of SRv6, reduces the network forwarding load; and can effectively promote the automated and flexible deployment of the network, promoting the evolution of the SDN (Software Defined Network) network system. BRIEF DESCRIPTION OF THE DRAWINGS

[0034] Figure 1 is a system framework diagram supporting a method for controller-based cross-vendor protocol communication.

[0035] Figure 2 is a processing flow diagram of SRv6 cross-vendor protocol processing.

[0036] Figure 3It is a schematic diagram of the processing of end-to-end node SID calculation.

[0037] Figure 4 It is a schematic diagram of the SRH of the SRv6 forwarded packet at Node A.

[0038] Figure 5 It is a schematic diagram of the SRH of the SRv6 forwarded packet at Node C.

[0039] Figure 6 It is a schematic diagram of the SRH of the SRv6 forwarded packet at Node E. Detailed implementation manners

[0040] Next, the technical solutions in the embodiments of the present application will be clearly and completely described in conjunction with the accompanying drawings in the embodiments of the present application.

[0041] In an embodiment, the present invention proposes a method for cross-vendor protocol communication based on a controller, that is, a system solution of an IPSDN controller and a network forwarding device, so as to achieve the optimization of network deployment and applications, improve the operation and maintenance efficiency of the network system, and reduce the risk of network forwarding. The method includes: the controller calculates and manages the network node attributes and SRv6 (Segment Routing IPv6) SIDs; calculates the SRv6 forwarding path and end-to-end path of the network, and the controller calculates the Segment List ID or BSID (Binding Segment ID) of the corresponding network element according to the attributes of the network element devices passed by each path; according to the calculation and analysis results, the controller deploys the BSID or Segment List at the starting point of each segment of the same-vendor path to form an end-to-end complete SRv6 forwarding path, realizing the cross-vendor full-path automatic deployment of SRv6.

[0042] The system framework supporting the method of the present invention is as Figure 1 shown, mainly including: network element management, network acquisition and control, path calculation, SRH (Segment Routing Header) generation, device forwarding; specifically as follows:

[0043] 1. Network element management: The controller centrally manages the forwarding network element devices of the entire network, including the manufacturers of the network elements, the supported SRv6 protocol, the compression technology protocol of the SRv6 SRH, and the supported protocol for the SRv6 BSID; the process steps are as Figure 3 shown.

[0044] a) There are differences in the support for the SRv6 protocol among different manufacturers. The depth of support for SRH by each manufacturer's device models may also vary. The compression methods and solutions for SRH of the SRv6 protocol and the supported protocol standards may also be different among the devices of each manufacturer. For example: some support the uSID carrier solution, some support the Compress-SRH solution, some support the Unified-SRH solution, and some support the G-SRv6 solution.

[0045] b) The controller first uniformly manages and allocates the SIDs and BSIDs of the entire network. The specific process is as follows:

[0046] For devices using the same SID allocation rule, the controller classifies them into one category and uses SIDSpaceID for identification, that is, each SIDSpaceID corresponds to a SID value space and also corresponds to the devices applying this SID value space;

[0047] The controller uniformly allocates a globally valid BSID, which can be regarded as SIDSpaceID being 0;

[0048] For the SID allocation and use within the same SIDSpaceID, SID values are produced using the same rule; while for different devices in different SID value spaces identified by different SIDSpaceIDs, such as device A corresponding to SIDSpaceID 1 and device B corresponding to SIDSpaceID 2, the SID published by B to A, that is, the SID used from A to B, uses the BSID to identify the SRv6 Segment List starting from device B;

[0049] Devices supporting different SRv6 SRH compression technology protocols can be classified into corresponding different SIDSpaceIDs;

[0050] In special cases, when the SRv6 protocol versions of device A and device B are different, but device A can be compatible with the SID values of device B, including but not limited to SRv6 SRH compression, what is published from device B to device A does not necessarily have to be the global BSID, but the complete Segment List of device B.

[0051] 2. Network acquisition and control: Adopt network protocols to collect network topology, traffic, performance, and status information, and collect SRv6 path information; issue the SRv6 path configuration generated by centralized calculation by the controller and obtain the configuration result information.

[0052] a) For all network devices and interfaces, the controller uses network protocols (such as BGP, IGP, LLDP, etc.) to collect network topology information and status information.

[0053] b) For the interfaces, links, and SRv6 of the entire network, the controller collects traffic and performance data of the network according to network protocols (such as Telemetry, TWAMP, OAM, etc.).

[0054] c) For the SRv6 of the entire network, the controller obtains path information and status information of SRv6 according to network protocols (such as BGP-LS, BFD, etc.).

[0055] d) For the devices of the entire network, the controller distributes the corresponding device configurations and path configurations and information of SRv6 through network protocols (such as Netconf / Yang, CLI, BGP, PCEP, etc.).

[0056] 3. Path calculation: The controller calculates the network forwarding path according to the SRv6 information of the entire network and the triple information of SRv6Policy. According to the calculated SRv6 path, the SRv6 forwarding path L corresponding to each SIDSpaceID on the forwarding path is analyzed i , including the starting point and the ending point.

[0057] a) Based on the unified network-wide routing information that eliminates vendor differences, the controller calculates the end-to-end path of SRv6 according to service requirements (such as attributes like bandwidth, latency, bit error rate, display path, etc.), and obtains the complete path of SRv6 from the source node to the destination node, that is, each logical path of the Candidate Path of the unified SRv6Policy. The path is the queue of each node and node port L n , n = 1, 2, …, N, where N is the total number of logical paths.

[0058] b) For each logical path, when the controller calculates the path, it does not consider the differences in the support of the SRv6 protocol version by each node on the path, nor does it consider the different technical differences in SRv6 SRH compression.

[0059] 4. SRH generation: The controller centrally generates the SRH of each segment of the SRv6 forwarding path and the end-to-end SRH according to the calculation and analysis results of the forwarding path, that is, the calculated logical path of SRv6, and distributes them to the corresponding forwarding devices segment by segment.

[0060] a) For each segment of the logical forwarding path, according to the SID space corresponding to SIDSpaceID, it is divided into the corresponding forwarding paths m is the number of segmented paths corresponding to the logical forwarding path; for each network element on each segmented path l i from the source node to the destination node, according to the SRv6 protocol version supported by the network element, the SRv6 SID corresponding to the SRv6 version supported by the node device is used to form the Segment List of the forwarding path l i .

[0061] b) For nodes across SIDSpaceID, due to technical differences such as the supported SRv6 versions and compression schemes, instead of using the Segment List supported by the device's own SRv6 version, the corresponding BSID assigned by the controller is used to map the corresponding Segment List.

[0062] c) Thus, for the end-to-end path, the Segment List of each segment l i and the corresponding BSID are used to form the Segment List of the end-to-end L n Segment List.

[0063] 5. Device forwarding: The network element device receives the SRv6 forwarding path configuration information sent by the controller, and performs SRv6 packet forwarding at the start and end points of each path segment according to the SRv6 support situation of the corresponding manufacturer. At this time, because the actual forwarding of each router only needs to support the forwarding behavior of the SRv6 version supported by this node and the compression / decompression behavior of the SRH, the dependence on compatibility is reduced, and the forwarding processing logic of the device is greatly simplified.

[0064] The relevant processing flow is as Figure 2 shown.

[0065] In the forwarding network with a mixed network of multi-vendor devices as Figure 3 shown, the customer service requires that the traffic goes from A to F. In the corresponding network path, there is a network path A - B - C - D - E - F as shown in the figure, which needs to pass through network devices of three different manufacturers, namely network forwarders. Forwarders A and B belong to manufacturer A, forwarders C and D belong to manufacturer B, and forwarders E and F belong to manufacturer C. And the processing details of the SRH of SRv6 of each manufacturer are not exactly the same, and the compression of the SRH is also different. That is, there is a problem of non-interoperability of SRv6 end-to-end.

[0066] Then the controller will calculate the forwarding path of the Candidate Path of SRv6Policy according to the network topology information, performance data, traffic information and status information, as well as the requirements of the service for the path, performance, bandwidth, etc., such as the path: A - B - C - D - E - F.

[0067] Using the method of the present invention, the controller will analyze and calculate the SRv6 SRH protocol support situation of the end-to-end path devices, analyze the SID values locally supported by all nodes from source A to destination F, as well as the BSIDs from B to C across manufacturers and the BSIDs from D to E across manufacturers.

[0068] For the SRH of the path of the continuous transponders of each manufacturer, the Segment List can be directly used. For the devices of the manufacturer in the front of the path to the devices of other manufacturers in the back, the globally allocated BSID by the controller can be directly used.

[0069] For example, the SID values supported by the local device corresponding to the ABCDEF nodes are: SID1, SID2, SID3, SID4, SID5, SID6 respectively. The BSID from B to C is BSID1, and the BSID from D to E is BSID2.

[0070] Then at the head node A, the SRH encapsulated in the path information of SRv6 is SID2, BSID1, BSID2; the information is as Figure 4 shown. At this time, Segment List = 2, and the SID2 that can be processed by node A is used for forwarding.

[0071] At the intermediate node C, after the device receives BSID1, it performs SRH replacement processing on BSID1, that is, replaces BSID1 with the SID of the version of SRv6 supported by transponder C, such as uBID or G-SRv6. After replacement, on transponder C, the path information encapsulated in the SRH is: SID4, BSID2; the information is as Figure 5 shown. At this time, Segment List = 1, and the SID4 that can be processed by node C is used for forwarding.

[0072] At the intermediate node E, after the device receives BSID2, it performs SRH replacement processing on BSID2, that is, replaces BSID2 with the SID of the version of SRv6 supported by transponder E, such as Compress-SRH or Unified-SRH. After replacement, on transponder C, the path information encapsulated in the SRH is: SID6; the information is as Figure 6 shown. At this time, Segment List = 0, and the SID6 that can be processed by node E is used for forwarding.

[0073] Therefore, each node on the end-to-end SRv6 path will forward the packets according to the Segment List of the packet forwarding of each conversion node calculated and allocated by the controller, and according to the SID forwarding behavior supported by this node. That is, each continuous connection of transponders of the same version of each manufacturer is regarded as a forwarding segment, such as A-B, C-D, E-F are all forwarding segments. Except for the head node, other forwarding segments are identified using the globally unified BSID allocated by the controller.

[0074] After the controller calculates and organizes the Segment List of each translation node and the BSID-related configurations of devices from different device manufacturers, it distributes the Segment List entries to each translation node device as needed (source node A, cross-vendor nodes C and E) through the network control protocol.

[0075] After the forwarding device obtains this organized Segment List information, the forwarding device can perform local SRv6 packet forwarding based on the corresponding Segment List and BSID according to the support situation of this device for the SRv6 protocol.

[0076] For more complex network situations, such as multiple paths from B to E, or more complex networking with forwarding devices from different manufacturers, etc., the system can be processed according to the method of the present invention, and there is no essential difference.

[0077] Of course, other detection protocols such as OAM can also be deployed, and the basic method is similar to BFD.

[0078] Furthermore, for multiple Candidate Paths of SRv6Policy, the controller can also support path calculation and deployment for all Candidate Paths according to the method of the present invention. At this time, there is no special feature for the paths of Candidate Paths, but it is equivalent to multiple Segment Lists, and each Segment List can support path forwarding across devices from different manufacturers.

[0079] Because the present invention is an end-to-end full-path deployment, providing the SRv6 full path for devices from different device manufacturers with different levels of support for SRv6Policy, the present invention can better deploy the SRv6 forwarding path throughout the entire life cycle and the whole process, thus more conveniently supporting the deployability of the SRv6 protocol and promoting the network evolution based on the SRv6 protocol.

[0080] In another embodiment, the present invention proposes a computer-readable storage medium storing a computer program, and the computer program causes a computer to execute the method for cross-vendor protocol communication based on a controller in the foregoing embodiment.

[0081] In another embodiment, the present invention proposes an electronic device, including: a memory, a processor, and a computer program stored on the memory and executable on the processor. When the processor executes the computer program, it implements the method for cross-vendor protocol communication based on a controller in the foregoing embodiment.

[0082] In the embodiments disclosed in the present application, the computer storage medium may be a tangible medium that can contain or store a program for use by or in connection with an instruction execution system, apparatus, or device. The computer storage medium may include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination of the foregoing. More specific examples of the computer storage medium would include electrical connections based on one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fibers, portable compact disk read-only memory (CDROM), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing.

[0083] Those of ordinary skill in the art will recognize that the units and algorithm steps of the examples described in connection with the embodiments disclosed in the present application can be implemented in electronic hardware or a combination of computer software and electronic hardware. Whether these functions are executed in hardware or software depends on the specific application and design constraints of the technical solution. Skilled artisans may use different methods for each specific application to implement the described functions, but such implementation should not be considered to exceed the scope of the present application.

[0084] The above are only the preferred embodiments of the present invention, and the protection scope of the present invention is not limited to the above embodiments. All technical solutions falling within the idea of the present invention belong to the protection scope of the present invention. It should be noted that for those of ordinary skill in the art in this technical field, several improvements and refinements made without departing from the principle of the present invention should be regarded as within the protection scope of the present invention.

Claims

1. A method for cross-vendor protocol communication based on a controller, characterized in that, Including: Obtain the SRv6 version information of all network devices and initialize the SIDSpaceID of the devices. Each SIDSpaceID corresponds to a SID value space and also corresponds to the devices applying this SID value space; According to the division of SIDSpaceID, uniformly allocate BSID to the devices; Calculate the end-to-end path of SRv6 according to the path requirements for SRv6; According to the forwarding path information in the end-to-end path, organize the SegmentList of the end-to-end path and each forwarding path. The Segment List consists of the SID and BSID of the devices on the path; Generate the SRH of the end-to-end path and each forwarding path according to the Segment List of the end-to-end path and each forwarding path, and segment and distribute it to the corresponding nodes; The devices at the corresponding nodes perform local SRv6 packet forwarding according to the obtained SRH.

2. The method for cross-vendor protocol communication based on a controller according to claim 1, characterized in that: The initialization of the SIDSpaceID of the device is specifically: Group the devices of the same manufacturer using the same SID allocation rule into one category and use SIDSpaceID for identification.

3. The method for cross-vendor protocol communication based on a controller according to claim 2, wherein: Devices of different manufacturers supporting different SRv6 protocols correspond to different SIDSpaceIDs.

4. The method for cross-vendor protocol communication based on a controller according to claim 1, characterized in that: The calculation of the end-to-end path of SRv6 is specifically: Based on the network-wide routing information, calculate the end-to-end path of SRv6 according to the service requirements to obtain the complete path of SRv6 from the source node to the destination node, including each logical path of the unified SRv6 Policy.

5. The method for cross-vendor protocol communication based on a controller according to claim 4, characterized in that: When calculating each logical path, do not consider the differences in the support of the SRv6 protocol version by each node on the path, nor consider the differences in the compression technology protocol for SRv6 SRH.

6. The method for cross-vendor protocol communication based on a controller according to claim 1, wherein: The organization method of the Segment List of each forwarding path is: Sequentially obtain the SIDSpaceID corresponding to each forwarding path and parse the corresponding SRv6 protocol; Generate the Segment List of this forwarding path according to the parsed SRv6 protocol.

7. The method for cross-vendor protocol communication based on a controller according to claim 6, wherein: The generation of the Segment List of this forwarding path is specifically: For the nodes on each forwarding path, according to the parsed SRv6 protocol, use the SID of the device corresponding to the node to form the Segment List of the forwarding path; For the nodes across SIDSpaceIDs, use the BSID allocated to the device corresponding to the node to map the Segment List.

8. The method for cross-vendor protocol communication based on a controller according to claim 7, characterized in that: The organization method of the Segment List of the end-to-end path is: For the end-to-end path, use the Segment List of each forwarding path and the BSID for mapping the Segment List to form the Segment List of the end-to-end path.

9. A computer-readable storage medium storing a computer program, characterized in that, The computer program causes the computer to execute the method for cross-vendor protocol communication based on a controller as described in any one of claims 1-8.

10. An electronic device, characterized in that, Including: A memory, a processor, and a computer program stored on the memory and executable on the processor, wherein when the processor executes the computer program, a method for controller-based cross-vendor protocol communication as described in any one of claims 1-8 is implemented.

Images