WO2022088685A1

WO2022088685A1 - Semantic name acquisition method and apparatus, device, and storage medium

Info

Publication number: WO2022088685A1
Application number: PCT/CN2021/099024
Authority: WO
Inventors: 闫朝阳
Original assignee: 华为技术有限公司
Priority date: 2020-10-30
Filing date: 2021-06-08
Publication date: 2022-05-05
Also published as: CN114531360A

Abstract

Provided in the embodiments of the present application are a semantic name acquisition method and apparatus, a device, and a storage medium, the method comprising: receiving a packet sent by a first network device, the packet comprising a segment identification and a semantic name of an associated network device, and the semantic name being used for indicating the meaning of the segment identification; and storing the association relationship of the semantic name and the segment identification. Implementing the embodiments of the present application facilitates management and operation of network devices on the basis of semantic names.

Description

A method, device, device and storage medium for acquiring semantic name

This application claims the priority of the Chinese patent application filed on October 30, 2020 with the application number 202011206224X and the application title is "A method, device, equipment and storage medium for acquiring a semantic name", the entire content of which is approved by Reference is incorporated in this application.

technical field

The present application relates to the field of communication technologies, and in particular, to a method, apparatus, device, and storage medium for acquiring a semantic name.

Background technique

In a segment routing for IPv6 (SRv6) environment based on the sixth version of the Internet Protocol, in general, a routing protocol is run to dynamically assign a segment identification (SID) to each node or port in the network, Each SID is used to identify a node or a port. The controller collects the information of each node or port in the network (including the SID, neighbor relationship and other information of each node or port), establishes the network topology according to the collected information, calculates and generates the forwarding policy, and sends the forwarding policy to a certain device On or on multiple devices, each device forwards packets according to the forwarding policy.

In some scenarios, it is necessary to specify that the forwarding policy must pass through a certain link or a certain node, but in the prior art, there is no solution that can conveniently and quickly specify a certain link or a certain node.

SUMMARY OF THE INVENTION

The embodiments of the present application disclose a method, apparatus, device, system and storage medium for acquiring a semantic name, which are convenient for managing and operating network devices according to the semantic name.

In a first aspect, the present application provides a method for acquiring a semantic name. The method includes: receiving a message sent by a first network device, where the message includes a segment identifier and a semantic name of an associated network device, wherein the semantic name is used for Indicate the meaning of the segment identifier; save the association relationship between the semantic name and the segment identifier.

The method can be applied to a target device. The target device receives a message sent by the first network device, and the message includes a segment identifier and a semantic name associated with the network device, and stores the association relationship between the semantic name and the segment identifier. The semantic name is used to indicate the meaning of the segment identifier, which is convenient for the target device to manage or use the segment identifier subsequently according to the semantic name.

Based on the first aspect, in a possible implementation manner, the above-mentioned associated network device is a first network device or a third network device.

The target device receives the message sent by the first network device, and the message includes the segment identifier and semantic name of the associated network device, where the associated device may be the first network device, that is, the first network device sends its own segment identifier and corresponding The associated device may also be a third network device, that is, the first network device sends the segment identifiers and corresponding semantic names of other network devices.

Based on the first aspect, in a possible implementation manner, after saving the association relationship between the semantic name and the segment identifier, the method further includes: displaying the association relationship between the semantic name and the segment identifier.

After saving the relationship between the semantic name and the segment identifier, the target device can also display the relationship between the semantic name and the segment identifier through a graphical user interface, so that the network administrator can manage the segment identifier according to the relationship.

Based on the first aspect, in a possible implementation manner, the semantic name is used to indicate that the segment identifier is used to go to the second network device, and the method further includes: displaying a service view, wherein the service view is used for displaying Topological relationship between the associated network device and the second network device.

When the semantic name is used to indicate the destination of the segment identifier to the second network device, the target device can display the topological relationship between the associated device and the second network device in the service view, so that the network administrator can manage the segment identifier according to the associated relationship.

Based on the first aspect, in a possible implementation manner, the method further includes: generating a forwarding policy, where the forwarding policy includes the segment identifier, wherein the forwarding policy is obtained according to the semantic name; sending the A forwarding policy, where the forwarding policy is used to indicate the use of the segment identifier.

When the target device is a control device, the target device can generate a forwarding policy according to the semantic name, and send the forwarding policy to the underlying network. This makes it more convenient to generate forwarding policies.

In a second aspect, an embodiment of the present application provides a method for acquiring a semantic name. Based on the description of the first network device, the method includes: the first network device sends a first packet to a target device, where the first packet includes an associated network The segment identifier and semantic name of the device, wherein the semantic name is used to indicate the meaning of the segment identifier.

The first network device sends a first packet to the target device, where the first packet includes a segment identifier and a semantic name of the associated network device, where the semantic name is used to indicate the meaning of the segment identifier, specifically, the semantic name may indicate the segment identifier It can also indicate that the segment identifier goes to the network device, and can also indicate that the segment identifier goes to another segment identifier, and so on. The target device may be a control device or a third network device, which is called a third network device here for the purpose of distinguishing it from other network devices.

Based on the second aspect, in a possible implementation manner, the associated network device is the first network device or the second network device.

Based on the second aspect, in a possible implementation manner, the associated network device includes a second network device, and the method further includes: receiving a second packet sent by the second network device, where the second packet includes the segment identifier and the semantic name.

When the target device is a control device and the associated network device is a second network device, the first network device also needs to receive a second packet sent by the second network device, and the second packet includes the segment of the second network device Identification and semantic names.

Based on the second aspect, in a possible implementation manner, the first message includes a segment identification type-length-value TLV field, the TLV field includes a sub-TLV, and the sub-TLV includes the semantic name.

The first message includes a segment identifier and a semantic name, wherein the segment identifier is a type-length-value TLV field, the TLV field includes a sub-TLV, the value in the sub-TLV is the semantic name, and the length in the sub-TLV is the length of the semantic name. .

Based on the second aspect, in a possible implementation manner, the first packet includes a border gateway protocol packet or an interior gateway protocol packet.

When the target device is a third network device, the first network device sends a first packet to the third network device. If the two network devices belong to the same autonomous domain, the first packet is an interior gateway protocol packet. If If the two network devices do not belong to the same autonomous domain, the first packet is a BGP packet.

Based on the second aspect, in a possible implementation manner, the method is applied in a segment routing network.

The method described in any of the above embodiments is applied in a segment routing network, for example, an SRv6 network or an SR-MPLS network.

In a third aspect, an embodiment of the present application provides an apparatus for acquiring a semantic name, including a receiving unit configured to receive a message sent by a first network device, where the message includes a segment identifier and a semantic name of the associated network device, wherein, The semantic name is used to indicate the meaning of the segment identifier; the storage unit is used to store the association relationship between the semantic name and the segment identifier.

Based on the third aspect, in a possible implementation manner, the apparatus further includes: a display unit, configured to display the association relationship between the semantic name and the segment identifier.

Based on the third aspect, in a possible implementation manner, the semantic name is used to indicate that the segment identifier is used to go to the second network device, and the display unit is further configured to display a service view, wherein the service view uses for displaying the topological relationship between the associated network device and the second network device.

Based on the third aspect, in a possible implementation manner, the apparatus further includes: a generating unit, configured to generate a forwarding policy, where the forwarding policy includes the segment identifier, wherein the forwarding policy is obtained according to the semantic name The sending unit is configured to send the forwarding policy, where the forwarding policy is used to indicate the use of the segment identifier.

Each functional unit in the apparatus of the third aspect is used to implement the method described in the first aspect and any implementation manner of the first aspect.

In a fourth aspect, an embodiment of the present application further provides an apparatus for acquiring a semantic name, including: a sending unit configured to send a first message to a target device, where the first message includes a segment identifier and a semantic name of an associated network device , wherein the semantic name is used to indicate the meaning of the segment identifier.

Based on the fourth aspect, in a possible implementation manner, the apparatus further includes a receiving unit, the associated network device includes a second network device, and the receiving unit is configured to receive a second message sent by the second network device The second message includes the segment identifier and the semantic name.

Based on the fourth aspect, in a possible implementation manner, the first message includes a segment identification type-length-value TLV field, the TLV field includes a sub-TLV, and the sub-TLV includes the semantic name.

Based on the fourth aspect, in a possible implementation manner, the packet includes a border gateway protocol packet or an interior gateway protocol packet.

Based on the fourth aspect, in a possible implementation manner, the apparatus is applied in a segment routing network.

Each functional unit in the apparatus of the fourth aspect is used to implement the method described in the second aspect and any implementation manner of the second aspect.

In a fifth aspect, an embodiment of the present application provides a device for acquiring a semantic name, including a memory and a processor, where the memory is used for storing instructions, and the processor is used for calling the instructions stored in the memory to execute the first aspect or A method as recited in any possible embodiment of the first aspect.

In a sixth aspect, an embodiment of the present application provides yet another device for acquiring semantic names, including a memory and a processor, where the memory is used for storing instructions, and the processor is used for calling the instructions stored in the memory to execute the second aspect or the method described in any possible embodiment of the second aspect.

In a seventh aspect, an embodiment of the present application provides a computer storage medium, including program instructions, which, when the program instructions are run on a computer, cause the computer to execute the method described in the first aspect or any implementation manner of the first aspect .

In an eighth aspect, an embodiment of the present application provides a computer storage medium, including program instructions, which, when the program instructions are run on a computer, cause the computer to execute the method described in the second aspect or any implementation manner of the second aspect .

In a ninth aspect, an embodiment of the present application provides a computer program product, the computer program product includes program instructions, and when the computer program product is executed by a first semantic name obtaining device, the first semantic name obtaining device executes the aforementioned first semantic name obtaining device. the method described in the aspect. The computer program product may be a software installation package, and if the method provided by any of the possible designs of the first aspect needs to be used, the computer program product may be downloaded and executed on the first semantic name acquisition device A program product to implement the method of the first aspect or any possible implementation of the first aspect.

In a tenth aspect, the embodiments of the present application provide yet another computer program product, the computer program product includes program instructions, and when the computer program product is executed by a second semantic name obtaining device, the second semantic name obtaining device executes the aforementioned first The method described in the second aspect. The computer program product may be a software installation package, and if the method provided by any of the possible designs of the second aspect needs to be used, the computer program product may be downloaded and executed on the second semantic name acquisition device A program product to implement the method of the second aspect or any possible implementation of the second aspect.

In an eleventh aspect, an embodiment of the present application provides a system, where the system includes a target device and a first network device, wherein the target device is the semantics described in the first aspect or any possible implementation manner of the first aspect A name obtaining apparatus, where the first network device is the semantic name obtaining apparatus described in the second aspect or any possible implementation manner of the second aspect.

Embodiments of the present application provide a method, apparatus, device, and storage medium for obtaining a semantic name, wherein the method includes: a first network device obtains a semantic name of a segment identifier, and the first network device retrieves a segment identifier and a corresponding semantic name. The message is sent to the target device, and the target device receives and saves the segment identifier and the corresponding semantic name. In a possible implementation manner, the target device can also display the association relationship between the segment identifier and the semantic name in the service view, generate a forwarding policy according to the semantic name, and send the forwarding policy to the underlying network. The forwarding policy forwards data packets. In the embodiment of the present application, by configuring a semantic name for the segment identifier, it is convenient to manage the network device, and in an actual scenario application, it is convenient to perform related operations and related processing on the network device according to the semantic name.

Description of drawings

In order to explain the technical solutions of the embodiments of the present application more clearly, the following briefly introduces the accompanying drawings used in the description of the embodiments. For those of ordinary skill, other drawings can also be obtained from these drawings without any creative effort.

1 is a schematic diagram of a software-defined network architecture provided by the present application;

FIG. 2 is an example diagram of a business chain scenario provided by the present application;

3 is a schematic flowchart of a method for obtaining a semantic name provided by the present application;

(a)-(c) in Figure 4 are schematic diagrams of various SID types provided by this application;

5 is a schematic flowchart of another semantic name acquisition method provided by the present application;

6 is a schematic diagram of displaying a semantic name in a business view provided by this application;

7 is a schematic diagram of displaying another semantic name in a business view provided by the present application;

8 is a schematic diagram of a forwarding strategy provided by the present application;

9 is a schematic diagram of a segment list sequence provided by the application;

10 is a schematic flowchart of a method for obtaining a semantic name provided by the application;

11 is a schematic diagram of a sub-TLV field provided by this application;

12 is a schematic flowchart of another semantic name acquisition method provided by the application;

FIG. 13 is an example diagram of an application scenario provided by this application;

14 is a schematic diagram of displaying a semantic name in a business view provided by this application;

15 is a schematic structural diagram of a device for obtaining semantic names provided by the application;

16 is a schematic structural diagram of another semantic name acquisition device provided by the application;

17 is a schematic structural diagram of a network device provided by the application;

18 is a schematic structural diagram of another network device provided by the application;

FIG. 19 is a schematic structural diagram of a system provided by this application.

Detailed ways

The terms used in the embodiments of the present application are only used to explain specific embodiments of the present application, and are not intended to limit the present application.

In this application, the terms "first", "second", "third" and other words are used to distinguish the same or similar items that have substantially the same function and function. It should be understood that "first", "second" and "third" There is no logical or temporal dependency between "three", nor does it limit the quantity and execution order.

In order to facilitate the understanding of this application, some routing protocols involved in this application are briefly explained first.

Routing protocols can be divided into interior gateway protocol (IGP) and exterior gateway protocol (EGP). IGP is generally a routing protocol used in an autonomous system (AS), the main purpose is to discover and calculate routing information in the self-made system, and exchange routing information within the same autonomous system, such as open shortest path first ( The open shortest path first, OSPF) protocol and the intermediate system-to-intermediate system (ISIS) protocol are all interior gateway routing protocols. EGP is generally used between different autonomous systems to dynamically exchange routing information between autonomous systems. Among them, the border gateway protocol (BGP) is the most commonly used external gateway routing protocol, commonly used in Internet gateways between.

The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present application.

Software-defined network (SDN) is a new type of network architecture. The SDN system architecture enables ordinary programmers to use general-purpose software on the general-purpose operating system of a general-purpose server to define network functions and make the network programmable. . It separates the control plane of the network from the data forwarding plane, thereby realizing programmability through the centralized control area, controlling the underlying hardware, and realizing flexible on-demand allocation of network resources. The SDN network architecture is divided into three layers, as shown in FIG. 1 . FIG. 1 is a schematic diagram of an SDN system architecture provided by this application. The architecture 100 includes an application layer, a control layer, and a forwarding layer. The application layer is the upper-layer application program that reflects the user's intention, including various services and applications; the control layer is responsible for processing the data arrangement of the data forwarding plane, maintaining network topology, status information, etc., including network topology collection, routing calculation, and forwarding Generation and distribution of policies, network management and control, etc. The forwarding layer is responsible for traffic forwarding and policy enforcement.

The control layer is the control center of the entire system architecture, the entity implementation of the control layer is the controller, and the controller is also the core component of the system architecture. The control layer is connected to the application layer through the northbound interface, and is connected to the forwarding layer through the southbound interface. The controller sends the calculated forwarding strategy to the forwarder of the forwarding layer through the southbound protocol, and the forwarder forwards the packets according to the forwarding strategy. .

Segment routing (SR) is a protocol designed based on the concept of source routing to control the forwarding of data packets in the network. SR divides the network path into segments, and assigns segment IDs (Segment IDs, SIDs) to these segments and network nodes. By arranging the SIDs in an orderly manner, a SID list (SID List, also known in SR-MPLS) can be obtained. called label stack), SID List can indicate a forwarding path. By carrying the segment identifiers arranged in sequence in the data packet, the data packet can be transmitted through the forwarding path indicated by the segment identifier. Through the SR technology, you can specify the nodes and paths that the data packets carrying the SID List pass through, so as to meet the requirements of traffic optimization. To make an analogy, the data package can be compared to luggage, and SR can be compared to the label attached to the luggage. If you want to send the luggage from area A to area D, and pass through area B and area C, you can send the luggage to area A at the origin. Put a label "first to B area, then to C area, and finally to D area", so that each area only needs to identify the label on the luggage, and forward the luggage from one area to another according to the label of the bag. Can. In SR technology, the source node adds a label to the data packet, and the intermediate node can forward it to the next node according to the label until the data packet reaches the destination node.

Segment routing (SRv6) based on Internet Protocol Version 6 (IPv6): refers to the application of SR technology in IPv6 networks.

In some scenarios, it is necessary to specify the corresponding SID list for the service to determine the path corresponding to the message. For example, FIG. 2 is an example diagram of a service chain scenario provided by this application. In this application scenario, the service chain includes router R1, provider edge routers (Provider Edge, PE) PE1, PE2, PE3 and other devices, wherein router R1 The value-added service device VAS1 and the value-added service device VAS2 are mounted on it, and the service chain requires that the forwarding path of the packets starts from the router PE1, first passes through the value-added service device VAS1, and then passes through the value-added service device VAS2, and forwards them to the router PE3. In this case, after the controller collects the network link status information, during the service chain orchestration process, it can only find the port information of the R1 device in the network link status information first, and then check the R1 device's port information separately by checking the network link status information. The SIDs of the two ports determine which is the port connected to the VAS1 device and which is the port connected to the VAS2 device, and then select the SID of the port connected to the VAS1 device, the SID of the port connected to the VAS2 device, or respectively. Copy the SID of the port connected to the VAS1 device and the SID of the port connected to the VAS2 device to the designated location of the arrangement in order to realize the arrangement of the service chain. However, in a large-scale network, due to the existence of a large number of network devices, it is necessary to find the target device and the SID corresponding to the target device in a large number of network devices. If the deployment method of this forwarding strategy is adopted, the efficiency is extremely low, and it is inconvenient to carry out manage.

In order to solve the above problems, the present application proposes a method for acquiring semantic names, which can be applied to segment routing (SR) networks, and can also be applied to other similar networks.

Based on the above-mentioned SDN system architecture, a semantic name acquisition method proposed in this application is introduced. Referring to FIG. 3 , FIG. 3 is a schematic flowchart of a method for obtaining a semantic name provided by the present application. The method includes but is not limited to the following descriptions of S101 to S103 .

S101. The first network device acquires the semantic name corresponding to the segment identifier of the associated network device.

In an example, the associated network device is the first network device, that is, the first network device obtains a semantic name corresponding to its own segment identifier.

In another example, the associated network device is the second network device, that is, the first network device obtains the segment identifier of the second network device and its corresponding semantic name. Specifically, the second network device first obtains the semantic name of its own segment identifier, and then the second network device sends its own segment identifier and semantic name to the first network device, so that the first network device obtains the segment of the second network device. Identification and semantic names.

SIDs include but are not limited to types such as node SIDs, proxy SIDs, binding SIDs, and the like. Wherein, End SID can be used to identify a certain destination address prefix in the network, for example, see the schematic diagram shown in FIG. 4 , FIG. 4 is a schematic diagram of various SID types provided by this application, (a) network device in FIG. 4 2 are connected to network device 1 and network device 3 respectively. SID A:: of End SID type can be used to identify network device 1, SID B:: to identify network device 2, and SID C:: to identify network device 3; End.X SID can Used to identify a link in the network, for example, referring to the schematic diagram shown in (b) in Figure 4, the network device is a three-layer cross node, and the SID A::1 of the End.X SID type can be used, respectively. SID A::2, SID A::3 identify the corresponding link. The binding SID type can be used to identify a certain tunnel in the network. For example, see the schematic diagram shown in (c) of Figure 4, where the autonomous system boundary router (ASBR) ASBR2, network device P2, network device PE2 Tunnel 1 is formed. Network equipment ASBR3, network equipment P3, and network equipment PE3 form tunnel 2. When representing the forwarding path or segment list, the SID of the binding SID type can be used to identify the entire tunnel 1. The proxy SID type can include End.AD SID, End.AS SID, etc. Among them, End.AS SID is a static SID, which is generally set manually and statically, and End.AD SID is a dynamic SID, which is automatically generated after the routing protocol runs. The proxy SID is used to provide a proxy for an object to control other objects' access to the object. For example, in the example shown in Figure 2, SID1 and SID2 on router R1 are proxy SID types. One proxy SID is to provide a proxy for the value-added device VAS1, and the other proxy SID is to provide a proxy for the value-added device VAS2. For convenience Description, use SID1 of the proxy SID type to identify the proxy port connected to the device VAS1 on the router R1, and use the SID2 of the proxy SID type to identify the proxy port connected to the device VAS2.

The semantic name is used to indicate the meaning of the segment identifier, specifically, the semantic name can be used to indicate the purpose of the segment identifier, the function of the segment identifier, which network device the segment identifier goes to, which SID the segment identifier goes to, and so on. For example, in the example shown in Figure 2, the semantic name SID-of-VAS1 of SID1 is used to indicate that SID1 is used to go to VAS1; the semantic name SID-of-VAS2 of SID2 indicates that SID2 is going to the device VAS2. In the actual application scenario, VAS1 Devices and VAS2 devices may be firewalls, accelerators, filters, etc.

There are several ways to obtain semantic names. For example, static configuration may be performed manually on the first network device to configure a semantic name for the segment identifier. For another example, the first network device can also be based on the relevant information (the relevant information can be the SID, loopback address, port number, virtual local area network to which the first network device belongs, network devices adjacent to the segment identifier, and adjacent segment identifiers. one or more of SIDs, etc.) are dynamically generated. For example, in the example shown in FIG. 2, the first network device is a router R1, and the router R1 generates a semantic name according to the network device adjacent to the segment identifier and a preset format, and the preset format is "SID-of-xxx", Among them, "xxx" is a network device adjacent to the segment identifier, and the semantic names "SID-of-VAS1" and "SID-of-VAS2" are generated. For another example, the first network device may obtain configuration information sent by the controller or the management device, where the configuration information includes a segment identifier and a semantic name, so that a semantic name is configured for the segment identifier.

In an example, there may be one SID or multiple SIDs, and when configuring the SIDs, a semantic name may be configured for each SID.

Before configuring the semantic name for the SID, you may also perform data configuration on each device in the network, such as routing configuration for the routers in the network, including configuring the router's interface address, loopback address, etc.; and then run the routing protocol for Each node or port in the network is assigned a SID, thereby establishing a neighbor relationship between each node in the network.

S102. The first network device sends a packet to the target device, where the packet includes a segment identifier and a semantic name of the associated network device.

The associated network device here may be the above-mentioned first network device or the above-mentioned second network device. That is, the first network device may send its own segment identifier and its corresponding semantic name to the target device, and may also send the segment identifier and its corresponding semantic name of other devices to the target device.

In one example, the target device may be other network devices in the same IGP or BGP network as the first network device.

In another example, the target device may also be a control device.

After acquiring the semantic name of the segment identifier, the first network device sends the packet to the target device. Correspondingly, the target device receives the packet sent by the first network device, where the packet includes the segment identifier of the first network device. and the semantic name, which is used to indicate the meaning of the segment ID.

Optionally, the message further includes link state information of the network, where the link state information of the network includes information such as the capability of each node in the network, the neighbor relationship, and the SID of each device. Among them, border gateway protocol link-state (BGP-LS) is a commonly used way to collect link state information of the network. BGP-LS mainly includes three routes, which are used to carry nodes respectively. , link and route prefix information, the three routes cooperate with each other to complete the transmission of link state information. For example, in the example of the service chain scenario shown in FIG. 2 , the collected link state information is abstracted into nodes, links, and prefixes through BGP-LS and reported to the controller. In one example, the first network device may send the segment identifier and its corresponding semantic name to the target device through a BGP-LS packet. In another example, the first network device may also send the segment identifier and its corresponding semantic name to the target device through a PCEP protocol message. This application does not limit the form in which the first network device sends the segment identifier and its corresponding semantic name to the target device.

S103: The target device stores the association relationship between the semantic name of the associated network device and the segment identifier.

The target device saves the received association relationship between the semantic name of the associated network device and the segment identifier.

It can be seen that the first network device obtains the semantic name corresponding to the segment identifier of the associated device, and the semantic name is used to indicate the meaning of the segment identifier. The network device sends the message to the target device, and the target device receives the message sent by the first network device. The message includes the segment identifier and semantic name of the associated network device, and the association between the segment identifier and semantic name of the associated network device will be saved. relation. In this embodiment, the semantic name can be configured by manual static configuration or dynamically generated by the associated network device, or the controller and the management device can send configuration information to the associated network device, and the associated network device can configure the semantic name according to the configuration information. The semantic name is configured by the method, and the semantic name is configured for the segment identifier, so that the function, function or destination of the segment identifier can be clearly known, and it is convenient to operate the segment identifier according to the semantic name.

The present application provides another method for acquiring semantic names. Referring to FIG. 5 , FIG. 5 is a schematic flowchart of a method for acquiring semantic names provided by the present application. The method includes but is not limited to the following descriptions of S201 to S207 .

S201. The first network device acquires the semantic name corresponding to the segment identifier of the associated network device.

S202. The first network device sends a packet to the target device, where the packet includes a segment identifier and a semantic name of the associated network device.

S203. The target device stores the association relationship between the semantic name of the associated network device and the segment identifier.

In this embodiment, for the content of S201 to S203, reference may be made to the description of the related content of S101 to S103, which is not repeated here for the sake of brevity of the description.

S204, the target device displays the association relationship between the semantic name of the associated network device and the segment identifier.

The target device displays the relationship between the semantic name and the segment ID of the associated network device through the graphical user interface according to the relationship between the segment ID and the semantic name in the received message, and the network administrator can intuitively see the semantic name corresponding to the SID. , obtain the meaning of the SID according to the semantic name, etc.

In an example, the target device restores the network topology according to the association relationship between the segment identifier and the semantic name, and the target device displays the restored network topology in the service view. For example, in the example of FIG. 2, the associated network device is router R1, and the network topology map restored by the controller can be the schematic diagram shown in FIG. 6, that is, the semantic name of SID1 is displayed on one end of router R1, and the semantic name of SID1 is displayed on the other end of router R1. The semantic name of SID2 is displayed on the display, and network administrators can know the meaning of SID according to the displayed semantic name.

In an example, the semantic name is used to indicate that the segment identifier is used to go to the third network device, and the control device restores the network topology according to the association relationship between the segment identifier and the semantic name, and displays the associated network device and the third network in the service view. Topological relationship between devices. For example, in the example of FIG. 2 , the segment identifier SID1 goes to the value-added device VAS1 (third network device), and the segment identifier SID2 goes to the value-added device VAS2 (third network device), and the network topology in the service view can be as shown in FIG. 7 . The schematic diagram shown, that is, two dots are exposed on the router R1, each dot represents a SID, the name of each SID and the semantic name corresponding to each SID are displayed, and the relationship between SID1 and value-added equipment VAS1 is displayed, The relationship between SID2 and value-added equipment VAS2. The manner of displaying the semantic name of the SID in the business view of the controller may also be other manners, which are not specifically limited in this application.

S205, the target device generates a forwarding policy.

The target device generates a forwarding policy, and the forwarding policy includes the segment identifier of the associated network device, wherein the forwarding policy is obtained according to the semantic name. In this step, the target device is usually a control device, such as a controller.

In one example, the network administrator searches according to the semantics, the semantic name and the corresponding segment identifier are displayed in the retrieval result, the segment identifier to be used is determined, the control device receives the user's selection (or click) operation, and responds to the user's selection (or click) operation. select operation to automatically generate a forwarding policy.

In an example, when the target device calculates the forwarding path, it will automatically obtain all or part of the semantic name, determine the segment identifier to be used, and calculate the forwarding strategy.

Generally, a forwarding strategy can include multiple candidate paths, and each candidate path carries a priority attribute (preference). During packet forwarding, the candidate paths are selected according to the priority from high to low, that is, the candidate path with the highest priority is the preferred path of the forwarding policy, and the candidate path with the second priority is the candidate path of the forwarding policy. The core of each candidate path in the forwarding policy is a segment list sequence, each segment list sequence represents a packet forwarding path, and the forwarding policy also indicates that devices in the network need to follow the specified path to forward packets. For example, referring to FIG. 8, FIG. 8 is a schematic diagram of a forwarding strategy provided by the present application. In FIG. 8, a candidate path includes multiple segment lists, and each segment list carries a weight attribute. At the time, the devices or nodes or links or tunnels represented by each segment list can share the traffic according to the weight. In practical applications, each segment list is an explicit IPv6 or IPv4 address, and the segment list is used to instruct network devices to forward packets.

For example, in the example of Figure 2, the network administrator can use the mode of statically configuring the nodes that must pass through, and first select the SID1 corresponding to the SID-of-VAS1 according to the displayed semantic name, and then select the SID2 corresponding to the SID-of-VAS2, The selection operation here can be understood as the user clicks SID-of-VAS1 first, and then clicks SID-of-VAS2, and the controller calculates the forwarding policy in response to the user's selection. In this example, the arrangement of the segment list sequence in the forwarding policy may be as shown in FIG. 9 , when the controller arranges the forwarding policy, the controller arranges SID1 and SID2 on the router R1 in the forwarding path, and SID1 in the segment list Located at the lower layer of SID2, when a node in the network forwards packets, it will first pass through the port where SID1 is located, and then pass through the port where SID2 is located.

In a practical application scenario, there may be bandwidth requirements for a certain link, for example, the bandwidth of a certain link is required to be 500 Mbps/s. In this case, the controller also receives and responds to the user's operation on link bandwidth selection, calculates the forwarding policy, and finally obtains a forwarding policy that satisfies the condition.

S206, the target device delivers a forwarding policy.

After the target device calculates and obtains the forwarding policy, it will deliver the forwarding policy in some way. Generally speaking, the target device will deliver the forwarding policy to the head node of the preferred path.

In an example, a BGP neighbor is established between the target device and the head node, and after calculating the forwarding policy, the BGP-LS or PCEP message is delivered to the head node of the preferred path. For example, in the service chain scenario shown in Figure 2, the controller can deliver the forwarding policy to the router PE1 through the BGP SR Policy.

S207. The first network device forwards the data packet.

Import the data packet into the forwarding policy, encapsulate the data packet, and forward the data packet. A node or device in the network, which is generally the head node of the preferred path, after receiving the forwarding policy issued by the target device, imports the data packet into the forwarding policy, and encapsulates the data packet, so that the network devices in the network follow the segment. The data packets are forwarded in the order corresponding to the list sequence.

It can be seen that, after configuring the semantic name for the segment identifier, after the first network device sends the message containing the semantic name and segment identifier to the target device, the target device can display the relationship between the semantic name of the associated network device and the segment identifier. , so that network managers can intuitively know the function or role or purpose or destination of the segment identifier based on the semantic name; the target device generates a forwarding policy based on the packet, and then issues the forwarding policy, and the associated network device forwards the data packet according to the forwarding policy. . In this embodiment, the association relationship between the semantic name and the segment identifier is stored in the target device, and the forwarding policy is generated according to the semantic name. Compared with the prior art, the segment identifier is manually searched in the control device, and then the found segment identifier is written into to a designated location, and then generate a forwarding policy according to the written segment identifier, which is more convenient for operation in this embodiment.

An embodiment of the present application provides another method for acquiring a semantic name. Referring to FIG. 10 , FIG. 10 is a schematic flowchart of a method for acquiring a semantic name provided by the present application. The method includes but is not limited to the following descriptions of S301 to S304 .

S301. The second network device acquires the semantic name of the segment identifier.

In one example, the relationship between the second network device and the control device may not be a BGP neighbor relationship.

For this step, reference may be made to the description of the relevant content of S101, and for the sake of brevity of the specification, details are not repeated here.

S302. The second network device sends a packet to the first network device, where the packet includes a segment identifier and a semantic name of the second network device.

The second network device sends a message to the first network device, and correspondingly, the first network device receives the message sent by the second network device, and the message is used to instruct the first network device to obtain the meaning of the segment identifier according to the semantic name. The message may be an IGP protocol message, a BGP protocol message, or other forms of messages. The message includes a segment identifier and a semantic name of the second network device, specifically, the message includes a segment identifier type-length-value (type-length-value, TLV) field, and the TLV field also includes a type sub-TLV, Also called sub-TLV, the value in the sub-TLV is the semantic name, the type is the type of the semantic name, and the length is the length of the semantic name.

Referring to Fig. 11, Fig. 11 is a schematic diagram of a sub-TLV field provided by the application. The sub-TLV is composed of type Type, length Length and value Value, wherein value Value is the semantic name of SID, and length is used to indicate the sub-TLV. The length of the type field is used to indicate that the sub-TLV is a semantic name. In an example, the length of Value is variable, and the maximum length is 255*8 bits, the length of Length is 8 bits, and the length of Type is 8 bits.

The first network device receives the message sent by the second network device, and obtains the segment identifier of the second network device and the corresponding semantic name from the message. For example, the service chain scenario shown in Figure 2 belongs to an autonomous system, so the router R1 sends the interior gateway protocol packet to the router reflector RR, and the router reflector RR obtains the semantic name of the segment identifier of the router R1. The gateway protocol message may be an ISIS protocol message, an OSPF protocol message, or other forms of messages.

S303. The first network device sends a message to the control device, where the message includes the segment identifier and the semantic name of the second network device.

In an example, the first network device may be a device that has established a BGP neighbor relationship with the controller, and may send the packet to the control device through a BGP-LS or PCEP packet. For example, in the example of FIG. 2 , the first network device may be a router reflector RR (not shown in the figure), the router R1 sends the packet to the router reflector RR, and the router reflector RR uploads the packet to the control device.

S304. The control device saves the association relationship between the semantic name of the second network device and the segment identifier.

It can be seen that, in this embodiment, a semantic name is configured for the segment identifier of the second network device, and then the second network device sends a packet to the first network device, and the packet includes the segment identifier and semantic name of the second network device. , the first network device sends the message to the control device, and the control device saves the association relationship between the segment identifier and the semantic name. The message is an IGP protocol message or a BGP protocol message. In this embodiment, a semantic name is configured for the segment identifier of the second network device, so that the control device can operate the segment identifier of the second network device according to the semantic name.

This embodiment provides another method for acquiring semantic names. Referring to FIG. 12 , FIG. 12 is a schematic flowchart of a method for acquiring semantic names provided by this application. The method includes but is not limited to the following descriptions of S401 to S408 .

S401. The second network device acquires the semantic name of the segment identifier.

S402. The second network device sends a packet to the first network device, where the packet includes a segment identifier and a semantic name of the second network device.

S403. The first network device sends a message to the control device, where the message includes a segment identifier and a semantic name of the second network device.

S404. The control device saves the association relationship between the semantic name of the second network device and the segment identifier.

S405. The control device displays the association relationship between the semantic name of the second network device and the segment identifier.

S406. The control device generates a forwarding policy.

S407. The control device delivers a forwarding policy.

S408. The second network device forwards the data packet.

In this embodiment, the content of S401 to S404 can refer to the description of the related content of S301 to S304, and the content of S405 to S408 can refer to the description of the related content of S204 to S207.

It can be seen that in this embodiment, after obtaining the segment identifier and semantic name of the second network device, the control device generates a forwarding policy according to the semantic name. Compared with the prior art, the control device manually searches for the segment identifier, and then uses The found segment identifier is written to a specified location, and then a forwarding policy is generated according to the written segment identifier, which is more convenient for operation in this embodiment.

In order to understand the present application more clearly, the method embodiments provided by the present application are exemplarily described below with reference to the application scenario shown in FIG. 13 .

In the scenario shown in Figure 13, router PE3, router ASBR1, and router ASBR2 constitute MAN 1, router PE4, router ASBR3, and router ASBR4 constitute MAN 2, and there exists a network between MAN 1 and MAN 2. Two backbone networks of an operator: backbone network 1 and backbone network 2. In this example, BGP EPE (Egress Peer Engineering) egress peer traffic engineering is configured on router ASBR1 and router ASBR2 respectively. BGP EPE can dynamically configure BGP EPE SIDs for the outbound interface of router ASBR1 and the outbound interface of router ASBR2 respectively. Including: SID1 and SID2, for the convenience of description, in the embodiment of this application, the SID configured for the outbound interface connecting the router ASBR1 to the backbone network 1 is called SID1, and the SID configured for the outgoing interface connecting the router ASBR1 to the backbone network 2 Called SID2. Similarly, BGP EPE egress peer traffic engineering is also configured on ASBR3 and ASBR4 to dynamically configure BGP EPE SIDs for the outgoing interface of ASBR3 and the outgoing interface of ASBR4. The user now needs to carry some services on the backbone network 1 through the outbound interface SID1 of the router ASBR1, and carry some services on the backbone network 2 through the outbound interface SID2 of the router ASBR1. Configure the semantic name, and then select the corresponding port to deploy the service according to the semantic name in the service view of the controller.

The method embodiments described in FIG. 5 or FIG. 12 can be applied to the above scenarios. First, configure the semantic name EPE-SID1-to-backbone network 1 for SID1 of router ASBR1, where EPE-SID1-to-backbone network 1 is used to indicate that the segment identifier SID1 is the SID going to backbone network 1, and configure the semantic name EPE- SID2-to-backbone network 2, EPE-SID2-to-backbone network 2 is used to indicate that the segment identifier SID2 is the SID destined for the backbone network 2. Then, router ASBR1 sends the packet to the control device, and accordingly, the control device receives the packet, which includes SID1, EPE-SID1-to-backbone 1, SID2, and EPE-SID2-to-backbone 2 . Secondly, the control device saves and displays the association between SID1 and EPE-SID1-to-backbone 1, and the association between SID2 and EPE-SID2-to-backbone 2 through a graphical user interface. Finally, the control device generates a forwarding policy according to the semantic name, and sends the forwarding policy to the underlying network, and each network device in the underlying network forwards the data packet according to the forwarding policy.

Among them, if the router ASBR1 cannot interact with the control device, it can send the SID and its corresponding semantic name to other network devices that can interact with the control device, such as the router ASBR2, and the router ASBR2 sends the SID and its corresponding semantic name. to the control device.

In an example, the control device displays the relationship between SID1 and EPE-SID1-to-backbone 1, and the relationship between SID2 and EPE-SID2-to-backbone 2 in the service view, as shown in FIG. 14 , FIG. 14 is a schematic diagram of displaying a semantic name in a service view provided by an embodiment of the present application. A network administrator can intuitively see through the service view that there are two SIDs on router ASBR1, where the semantic name of SID1 is EPE-SID1- to-backbone 1, the semantic name of SID2 is EPE-SID2-to-backbone 2. In this embodiment, the display manner of the SID and the semantic name is not specifically limited.

FIG. 15 is a schematic structural diagram of an apparatus 600 for obtaining a semantic name provided by an embodiment of the present application. The apparatus 600 has the first network device or the second network device or the third network in the above-mentioned FIG. 3 or FIG. 5 or FIG. 10 or FIG. 12 . any function of the device. As shown in FIG. 15, the apparatus 600 includes: a sending unit 601, configured to send a first packet to a target device, where the first packet includes a segment identifier and a semantic name of the associated device, for example, the sending unit 601 is configured to execute the S102 in 3, S202 in FIG. 5, S303 in FIG. 10, S403 in FIG. 12, etc.; the receiving unit 602 is used to receive or obtain a message, for example, the receiving unit 602 is used to perform S101 in FIG. 3, S201 in FIG. 5 , S302 in FIG. 10 , S402 in FIG. 12 , and the like. Optionally, the semantic name acquiring apparatus 600 further includes a processing unit (not shown in the figure), which is used for processing and the above-mentioned steps of acquiring and managing the semantic name.

The semantic name obtaining apparatus 600 corresponds to the first network device in the above method embodiment, and the units in the semantic name obtaining apparatus 600 and the other operations and/or functions described above are respectively implemented to implement the first network device in the method embodiment. For the specific details of various steps and methods, reference may be made to the descriptions of the above methods, which are not repeated here for brevity.

When the semantic name obtaining device 600 obtains the semantic name, only the division of the above-mentioned functional units is used for illustration. The internal structure is divided into different functional units to complete all or part of the functions described above.

FIG. 16 is a schematic structural diagram of another semantic name obtaining apparatus 700 provided by an embodiment of the present application. The apparatus 700 has any function of the target device in FIG. 3 or FIG. 5 or FIG. 10 or FIG. 12 . As shown in FIG. 16 , the apparatus 700 includes: a receiving unit 701, configured to receive a packet sent by a first network device, wherein the packet includes a segment identifier and a semantic name of the associated device, for example, the receiving unit 701 is configured to execute the process shown in FIG. 3 S102 in FIG. 5, S202 in FIG. 5, S303 in FIG. 10, S403 in FIG. 12, etc.; storage unit 702, for saving the association relationship between semantic names and segment identifiers, for example, performing S404, S304, S203 and S103; display The unit 703 is used to display the association relationship between the semantic name and the segment identifier, or when the semantic name indicates that the segment identifier goes to the second network device, the display unit 703 is used to display the relationship between the associated network device and the second network device in the service view. Topological relationship, for example, perform S204, S405; generating unit 704, for generating a forwarding policy, for example, performing S205, S406; sending unit 705, for sending a forwarding policy, for example, the sending unit is used for performing S206, S407 and so on.

The semantic name obtaining apparatus 700 corresponds to the target device or the control device in the above method embodiments, and the units in the semantic name obtaining apparatus 700 and the other operations and/or functions mentioned above are respectively for realizing the target device or the control device in the method embodiment. For the specific details of the various steps and methods to be implemented, reference may be made to the descriptions of the above methods, which are not repeated here for brevity.

When the semantic name obtaining device 700 performs network management, only the division of the above-mentioned functional units is used for illustration. The structure is divided into different functional units to perform all or part of the functions described above.

Corresponding to the method embodiments and the virtual apparatus embodiments provided in the present application, the embodiments of the present application further provide a network device, and the hardware structure of the network device is introduced below.

The network device 800 or the network device 1000 described below corresponds to the first semantic name obtaining device 600 or the second semantic name obtaining device 700 in the above method embodiments, and the hardware, modules and the above-mentioned other devices in the network device 800 or the network device 1000 The operations and/or functions are respectively in order to realize various steps and methods implemented by the first semantic name obtaining apparatus 600 or the second semantic name obtaining apparatus 700 in the method embodiment, and the information about how the network device 800 or the network device 1000 obtains the semantic name. As well as the detailed process of the related processing after acquiring the semantic name, the specific details can be found in the foregoing method embodiments, which are not repeated here for brevity. The steps in FIG. 3 or FIG. 5 or FIG. 10 or FIG. 12 above are completed by instructions in the form of hardware integrated logic circuits or software in the network device 800 or the processor of the network device 1000 . The steps of the methods disclosed in conjunction with the embodiments of the present application may be directly embodied as executed by a hardware processor, or executed by a combination of hardware and software modules in the processor. The software modules may be located in random access memory, flash memory, read-only memory, programmable read-only memory or electrically erasable programmable memory, registers and other storage media mature in the art. The storage medium is located in the memory, and the processor reads the information in the memory, and completes the steps of the above method in combination with its hardware. To avoid repetition, detailed description is omitted here.

The network device 800 or the network device 1000 corresponds to the device 600 or the device 700 in the above virtual device embodiment, and each functional unit in the device 600 or the device 700 is implemented by the software of the network device 800 or the network device 1000 . In other words, the functional units included in the apparatus 600 or the apparatus 700 are generated after the processor of the network device 800 or the network device 1000 reads the program code stored in the memory.

Referring to FIG. 17, FIG. 17 shows a schematic structural diagram of a network device 800 provided by an exemplary embodiment of the present application, where the network device 800 may be configured as a first network device or a target device. The network device 800 may be implemented by a general bus architecture.

Network device 800 includes at least one processor 801 , communication bus 802 , memory 803 , and at least one communication interface 804 .

The processor 801 may be a general-purpose CPU, NP, microprocessor, or may be one or more integrated circuits for implementing the solutions of the present application, such as application-specific integrated circuits (ASIC), programmable logic A device (programmable logic device, PLD) or a combination thereof. The above-mentioned PLD can be a complex programmable logic device (CPLD), a field-programmable gate array (FPGA), a general-purpose array logic (generic array logic, GAL) or any combination thereof.

The communication bus 802 is used to transfer information between the aforementioned components. The communication bus 802 can be divided into an address bus, a data bus, a control bus, and the like. For ease of presentation, only one thick line is used in the figure, but it does not mean that there is only one bus or one type of bus.

The memory 803 can be read-only memory (ROM) or other types of static storage devices that can store static information and instructions, or can be random access memory (RAM) or can store information and instructions. Other types of dynamic storage devices, it can also be electrically erasable programmable read-only memory (electrically erasable programmable read-only memory, EEPROM), compact disc read-only memory (CD-ROM) or other optical disk storage , optical disc storage (including compact disc, laser disc, optical disc, digital versatile disc, blu-ray disc, etc.), magnetic disk storage medium or other magnetic storage device, or can be used to carry or store desired program code in the form of instructions or data structures and any other medium that can be accessed by a computer, but is not limited thereto. The memory 803 may exist independently and be connected to the processor 801 through the communication bus 802 , and the memory 803 may also be integrated with the processor 801 .

Communication interface 804 uses any transceiver-like device for communicating with other devices or a communication network. The communication interface 804 includes a wired communication interface, and may also include a wireless communication interface. The wired communication interface may be, for example, an Ethernet interface, and the Ethernet interface may be an optical interface, an electrical interface, or a combination thereof. The wireless communication interface may be a wireless local area network (wireless local area networks, WLAN) interface, a cellular network communication interface or a combination thereof, and the like.

In a specific implementation, as an embodiment, the processor 801 may include one or more CPUs, such as CPU0 and CPU1 as shown in FIG. 17 .

In a specific implementation, as an embodiment, the network device 800 may include multiple processors, such as the processor 801 and the processor 805 shown in FIG. 17 . Each of these processors can be a single-core processor (single-CPU) or a multi-core processor (multi-CPU). A processor herein may refer to one or more devices, circuits, and/or processing cores for processing data (eg, computer program instructions).

In a specific implementation, as an embodiment, the network device 800 may further include an output device 806 and an input device 807 . The output device 806 is in communication with the processor 801 and can display information in a variety of ways. For example, the output device 806 may be a liquid crystal display (LCD), a light emitting diode (LED) display device, a cathode ray tube (CRT) display device, a projector, or the like . The input device 807 communicates with the processor 801 and can receive user input in various ways. For example, the input device 807 can be a mouse, a keyboard, a touch screen device or a sensor device.

In some embodiments, the memory 803 is used to store the program code 810 for executing the solutions of the present application, and the processor 801 can execute the program code 810 stored in the memory 803 . That is, the network device 800 can implement the method provided by the method embodiment of FIG. 3 or FIG. 5 or FIG. 10 or FIG. 12 through the processor 801 and the program code 810 in the memory 803 .

The network device 800 in this embodiment of the present application may correspond to the first network device or the target device in each of the above method embodiments, and the processor 801, the communication interface 804, etc. in the network device 800 may implement the above various method embodiments. The functions and/or the various steps and methods implemented by the device. For brevity, details are not repeated here.

The sending unit 601 and the receiving unit 602 in the apparatus 600 may be equivalent to the communication interface 804 in the network device 800 .

The receiving unit 701 and the sending unit 705 in the apparatus 700 may be equivalent to the communication interface 804 in the network device 800; the saving unit 702 in the apparatus 700 may be equivalent to the memory 803 in the network device 800; the generating unit 704 in the apparatus 700 may be equivalent The processor 801 in the network device 800 ; the display unit 703 in the apparatus 700 may be equivalent to the output device 806 in the network device 800 .

Referring to FIG. 18, FIG. 18 shows a schematic structural diagram of a network device 1000 provided by an exemplary embodiment of the present application, where the network device 1000 may be configured as a first network device or a target device. The network device 1000 includes: a main control board 1010 and an interface board 1030 .

The main control board 1010 is also called the main processing unit (main processing unit, MPU) or the route processor card (route processor card). The main control board 1010 is used to control and manage various components in the network device 1000 Management, equipment maintenance, protocol processing functions. The main control board 1010 includes: a central processing unit 1011 and a memory 1012 .

The interface board 1030 is also called a line processing unit (LPU), a line card (line card) or a service board. The interface board 1030 is used to provide various service interfaces and realize the forwarding of data packets. The service interfaces include but are not limited to Ethernet interfaces, POS (Packet over SONET/SDH) interfaces, etc. The Ethernet interfaces are, for example, flexible Ethernet service interfaces (flexible Ethernet service interfaces). ethernet clients, FlexE Clients). The interface board 1030 includes: a central processing unit 1031 , a network processor 1032 , a forwarding table entry storage 1034 and a physical interface card (PIC) 1033 .

The central processing unit 1031 on the interface board 1030 is used to control and manage the interface board 1030 and communicate with the central processing unit 1011 on the main control board 1010 .

The network processor 1032 is used to implement packet forwarding processing, and the form of the network processor 1032 may be a forwarding chip. Specifically, the network processor 1032 is configured to forward the received message based on the forwarding table stored in the forwarding table entry memory 1034. If the destination address of the message is the address of the network device 1000, the message is sent to the CPU ( If the destination address of the message is not the address of the network device 1000, the next hop and outgoing interface corresponding to the destination address are found from the forwarding table according to the destination address, and the message is forwarded to The outbound interface corresponding to the destination address. Wherein, the processing of the uplink packet includes: processing the incoming interface of the packet, and searching the forwarding table; processing of the downlink packet: searching the forwarding table, and so on.

The physical interface card 1033 is used to realize the interconnection function of the physical layer, the original traffic enters the interface board 1030 through this, and the processed packets are sent from the physical interface card 1033 . The physical interface card 1033 is also called a daughter card, which can be installed on the interface board 1030 and is responsible for converting the optoelectronic signal into a message and forwarding the message to the network processor 1032 for processing after checking the validity of the message. In some embodiments, the central processing unit may also perform the functions of the network processor 1032 , such as implementing software forwarding based on a general-purpose CPU, so that the network processor 1032 is not required in the physical interface card 1033 .

Optionally, the network device 1000 includes multiple interface boards, for example, the network device 1000 further includes an interface board 1040 , and the interface board 1040 includes a central processing unit 1041 , a network processor 1042 , a forwarding table entry storage 1044 and a physical interface card 1043 .

Optionally, the network device 1000 further includes a switch fabric board 1020, and the switch fabric board 1020 may also be referred to as a switch fabric unit (switch fabric unit, SFU). When the network device has multiple interface boards 1030 , the switch fabric board 1020 is used to complete data exchange between the interface boards. For example, the switch fabric board 1020 can communicate between the interface boards 1030 and the interface boards 1040 .

The main control board 1010 and the interface board 1030 are coupled. For example, the main control board 1010, the interface board 1030, the interface board 1040, and the switch fabric board 1020 are connected to the system backplane through a system bus to implement intercommunication. In a possible implementation manner, an inter-process communication (inter-process communication, IPC) channel is established between the main control board 1010 and the interface board 1030, and the main control board 1010 and the interface board 1030 communicate through the IPC channel.

Logically, the network device 1000 includes a control plane and a forwarding plane, the control plane includes the main control board 1010 and the central processing unit 1031, and the forwarding plane includes various components that perform forwarding, such as the forwarding entry storage 1034, the physical interface card 1033 and the network processing device 1032. The control plane performs functions such as routers, generating forwarding tables, processing signaling and protocol packets, configuring and maintaining device status, etc. The control plane delivers the generated forwarding tables to the forwarding plane. On the forwarding plane, the network processor 1032 is based on the control plane. The delivered forwarding table forwards the packets received by the physical interface card 1033 by looking up the table. The forwarding table issued by the control plane may be stored in the forwarding table entry storage 1034. In some embodiments, the control plane and the forwarding plane may be completely separated and not on the same device.

If the network device 1000 is configured as the first network device, the physical interface card 1033 receives or obtains the packet of the associated network device, and sends it to the network processor 1032. After the network processor 1032 processes the packet, the packet is sent from the physical interface card 1033 send out.

If the network device 1000 is configured as a target device or a control device, the physical interface card 1033 receives a packet sent by the first network device, and the packet includes the segment identifier and semantic name of the associated network device, and sends it to the network processor 1032 for processing by the network. The controller 1032 generates a forwarding policy according to the semantic name, and sends the forwarding policy to the network device through the physical interface card 1033 .

The sending unit 601 and the receiving unit 602 in the apparatus 600 are equivalent to the physical interface card 1033 in the network device 1000 .

The receiving unit 701 and the sending unit 705 in the apparatus 700 are equivalent to the physical interface card 1033 in the network device 1000 ; the generating unit 704 in the apparatus 700 may be equivalent to the network processor 1032 or the central processing unit 1011 ; the saving unit 702 in the apparatus 700 It is equivalent to the forwarding entry storage 1034 or the storage 1012 in the network device 1000 ; the display unit 703 is equivalent to the main control board 1010 in the network device 1000 .

The operations on the interface board 1040 in the embodiment of the present application are the same as the operations on the interface board 1030, and are not repeated for brevity. The network device 1000 in this embodiment may correspond to the first network device or the target device in the foregoing method embodiments, and the main control board 1010, the interface board 1030 and/or 1040 in the network device 1000 may implement the foregoing method embodiments For the sake of brevity, the functions possessed by the first network device or the target device and/or the various steps implemented are not repeated here.

It is worth noting that there may be one or more main control boards, and when there are multiple main control boards, they may include the main main control board and the backup main control board. There may be one or more interface boards. The stronger the data processing capability of the network device, the more interface boards are provided. There can also be one or more physical interface cards on the interface board. There may be no switch fabric boards, or there may be one or more boards. When there are multiple boards, they can jointly implement load sharing and redundant backup. Under the centralized forwarding architecture, the network device does not need to switch the network board, and the interface board undertakes the processing function of the service data of the entire system. Under the distributed forwarding architecture, a network device may have at least one switching network board, and the switching network board realizes data exchange between multiple interface boards, providing large-capacity data exchange and processing capabilities. Therefore, the data access and processing capabilities of network devices in a distributed architecture are greater than those in a centralized architecture. Optionally, the form of the network device can also be that there is only one board, that is, there is no switching network board, and the functions of the interface board and the main control board are integrated on this board. The central processing unit on the board can be combined into a central processing unit on this board to perform the functions of the two superimposed, the data exchange and processing capacity of this form of equipment is low (for example, low-end switches or routers and other networks. equipment). The specific architecture used depends on the specific networking deployment scenario, and there is no restriction here.

In some possible embodiments, the above-mentioned first network device or target device may be implemented as a virtualized device.

For example, the virtualization device may be a virtual machine (virtual machine, VM) running a program for sending a message, and the virtual machine is deployed on a hardware device (eg, a physical server). A virtual machine refers to a complete computer system with complete hardware system functions simulated by software and running in a completely isolated environment. The virtual machine can be configured as a network device. For example, the first network device or the target device may be implemented based on a general physical server in combination with a network functions virtualization (NFV) technology, where the first network device or the target device is a virtual host, a virtual router or a virtual switch. Those skilled in the art can virtualize a first network device or a target device having the above functions on a general physical server in combination with the NFV technology by reading this application, and details are not described herein again.

For example, the virtualization device can be a container, which is an entity used to provide an isolated virtualization environment. For example, the container can be a docker container, and the container can be configured as a first network device or a target device. The image of the proxy-container can be used to create the first network device or target device. For example, through the image of proxy-container (a container that provides proxy services), two container instances can be created for the proxy-container, namely the container instance proxy-container1 and the container instance proxy. -container2, provide the container instance proxy-container1 as the first network device, and provide the container instance proxy-container2 as the target device. When implemented using the container technology, the first network device or the target device can run using the kernel of the physical machine, and multiple first network devices or target devices can share the operating system of the physical machine. Different first network devices or target devices can be isolated through the container technology. The containerized first network device or target device may run in a virtualized environment, for example, may run in a virtual machine, and the containerized first network device or target device may also run directly in a physical machine.

For example, a virtualized device can be a Pod, and a Pod is Kubernetes (Kubernetes is a container orchestration engine open sourced by Google, abbreviated as K8s in English) as the basic unit for deploying, managing, and orchestrating containerized applications. A Pod can include one or more containers, and each container in the same Pod is usually deployed on the same host, so each container in the same Pod can communicate through the host and can share the host's storage resources and network resource. The Pod can be configured as the first network device or the target device, for example, specifically, a container as a service (container as a service, CaaS, which is a container-based PaaS service) can be instructed to create a Pod and provide the Pod as the first network device. Network device or target device.

Of course, the first network device or the target device may also be other virtualized devices, which will not be listed here.

In some possible embodiments, the above-mentioned first network device or target device may also be implemented by a general-purpose processor. For example, the general purpose processor may be in the form of a chip. Specifically, the general-purpose processor that implements the first network device or the target device includes a processing circuit, an input interface and an output interface that are internally connected and communicated with the processing circuit. The processing circuit is configured to perform the receiving step in the above method embodiments through the input interface, and the processing circuit is configured to perform the sending step in the above method embodiments through the output interface. Optionally, the general-purpose processor may further include a storage medium, and the processing circuit is configured to use the storage medium to perform the storage steps in each of the foregoing method embodiments. The storage medium may store instructions executed by the processing circuit, where the processing circuit is configured to execute the instructions stored in the storage medium to perform the above-mentioned various method embodiments.

Referring to FIG. 19 , an embodiment of the present application provides a system 1100 , where the system 1100 includes: a first network device 1101 and/or a target device 1102 . Optionally, the first network device 1101 is, for example, the device 600 , the network device 800 or the network device 1000 , and the target device 1102 is, for example, the device 700 , the network device 800 or the network device 1000 .

An embodiment of the present application provides a computer program product, which, when the computer program product runs on a first network device or a target device, enables the first network device or the target device to execute the above-mentioned FIG. 3 or FIG. 5 or FIG. 10 or FIG. 12 described method embodiments.

The above apparatuses in various product forms respectively have any functions of the first network device or the target device in the above method embodiments, which will not be repeated here.

Those of ordinary skill in the art can realize that, in combination with the method steps and units described in the embodiments disclosed herein, they can be implemented in electronic hardware, computer software, or a combination of the two. Interchangeability, the steps and components of the various embodiments have been generally described in terms of functions in the above description. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Persons of ordinary skill in the art may use different methods of implementing the described functionality for each particular application, but such implementations should not be considered beyond the scope of this application.

Those skilled in the art can clearly understand that, for the convenience and brevity of description, for the specific working process of the above-described systems, devices and units, reference may be made to the corresponding processes in the foregoing method embodiments, which are not repeated here.

In the several embodiments provided in this application, the disclosed systems, devices and methods may be implemented in other manners. For example, the apparatus embodiments described above are only illustrative. For example, the division of the unit is only a logical function division. In actual implementation, there may be other division methods, for example, multiple units or components may be combined or Integration into another system, or some features can be ignored, or not implemented. In addition, the shown 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 also be electrical, mechanical or other forms of connection.

The unit described as a separate component may or may not be physically separated, and the component displayed as a unit may or may not be a physical unit, that is, it may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solutions of the embodiments of the present application.

In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically alone, or two or more units may be integrated into one unit. The above-mentioned integrated units may be implemented in the form of hardware, or may be implemented in the form of software functional units.

The integrated unit, if implemented in the form of a software functional unit and sold or used as a stand-alone product, may be stored in a computer-readable storage medium. Based on this understanding, the technical solutions of the present application are essentially or part of contributions to the prior art, or all or part of the technical solutions can be embodied in the form of software products, and the computer software products are stored in a storage medium , including several instructions to cause a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods in the various embodiments of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM), random access memory (RAM), magnetic disk or optical disk and other media that can store program codes .

The above descriptions are only specific implementations of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art can easily think of various equivalent modifications within the technical scope disclosed in the present application. or replacement, these modifications or replacements should be covered within the protection scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

In the above-mentioned embodiments, it may be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented in software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer program instructions. When the computer program instructions are loaded and executed on a computer, the procedures or functions according to the embodiments of the present application are generated in whole or in part. The computer may be a general purpose computer, a special purpose computer, a computer network, or other programmable device. The computer instructions may be stored in or transmitted from one computer readable storage medium to another computer readable storage medium, for example, the computer program instructions may be transmitted from a website site, computer, server or data center via Wired or wireless transmission to another website site, computer, server or data center. The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server, data center, etc. that includes one or more available media integrated. The available media may be magnetic media (eg, floppy disks, hard disks, magnetic tapes), optical media (eg, digital video discs (DVDs), or semiconductor media (eg, solid state drives), and the like.

Those of ordinary skill in the art can understand that all or part of the steps of implementing the above embodiments can be completed by hardware, or can be completed by instructing relevant hardware through a program, and the program can be stored in a computer-readable storage medium. The storage medium can be read-only memory, magnetic disk or optical disk, etc.

The above descriptions are only optional embodiments of the present application, and are not intended to limit the present application. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principles of the present application should be included in the protection scope of the present application. within.

Claims

A method for acquiring a semantic name, comprising:

receiving a message sent by the first network device, where the message includes a segment identifier and a semantic name of the associated network device, wherein the semantic name is used to indicate the meaning of the segment identifier;

The association relationship between the semantic name and the segment identifier is saved.
The method according to claim 1, wherein after saving the association relationship between the semantic name and the segment identifier, the method further comprises: displaying the association relationship between the semantic name and the segment identifier .
The method according to claim 1 or 2, wherein the semantic name is used to indicate that the segment identifier is used to go to the second network device, and the method further comprises:

A service view is displayed, wherein the service view is used to display the topology relationship between the associated network device and the second network device.
The method according to any one of claims 1-3, wherein the method further comprises:

generating a forwarding policy, the forwarding policy including the segment identifier, wherein the forwarding policy is obtained according to the semantic name;

The forwarding policy is sent, where the forwarding policy is used to indicate the use of the segment identifier.
A method for acquiring a semantic name, comprising:

The first network device sends a first packet to the target device, where the first packet includes a segment identifier and a semantic name of the associated network device, where the semantic name is used to indicate the meaning of the segment identifier.
The method according to claim 5, wherein the associated network device comprises a second network device, the method further comprising: receiving a second packet sent by the second network device, the second packet Include the segment identifier and the semantic name.
The method according to claim 5 or 6, wherein the first message includes a segment identification type-length-value TLV field, the TLV field includes a sub-TLV, and the sub-TLV includes the semantic name.
The method according to any one of claims 5-7, wherein the first message comprises: a border gateway protocol message or an interior gateway protocol message.
The method according to any one of claims 5-8, wherein the method is applied in a segment routing network.
A device for acquiring semantic names, comprising:

a receiving unit, configured to receive a message sent by the first network device, where the message includes a segment identifier and a semantic name of the associated network device, wherein the semantic name is used to indicate the meaning of the segment identifier;

A saving unit, configured to save the association relationship between the semantic name and the segment identifier.
The apparatus of claim 10, wherein the apparatus further comprises:

A display unit, configured to display the association relationship between the semantic name and the segment identifier.
The apparatus according to claim 10 or 11, wherein the semantic name is used to indicate that the segment identifier is used to go to the second network device, and the display unit is further configured to display a service view, wherein the The service view is used to display the topological relationship between the associated network device and the second network device.
The device according to any one of claims 10-12, wherein the device further comprises:

a generating unit, configured to generate a forwarding strategy, where the forwarding strategy includes the segment identifier, wherein the forwarding strategy is obtained according to the semantic name;

A sending unit, configured to send the forwarding policy, where the forwarding policy is used to instruct to use the segment identifier.
A device for acquiring semantic names, comprising:

A sending unit, configured to send a first packet to the target device, where the first packet includes a segment identifier and a semantic name of the associated network device, where the semantic name is used to indicate the meaning of the segment identifier.
The apparatus according to claim 14, wherein the apparatus further comprises a receiving unit, and the associated network device comprises a second network device,

The receiving unit is configured to receive a second packet sent by the second network device, where the second packet includes the segment identifier and the semantic name.
The apparatus according to claim 14 or 15, wherein the first message includes a segment identification type-length-value TLV field, the TLV field includes a sub-TLV, and the sub-TLV includes the semantic name.
The apparatus according to any one of claims 14-16, wherein the message includes a border gateway protocol message or an interior gateway protocol message.
The apparatus according to any one of claims 14-17, wherein the apparatus is applied in a segment routing network.
A computer storage medium, characterized in that it includes program instructions, which, when executed on a computer, cause the computer to perform the method according to any one of claims 1-9.
A system, characterized in that the system includes a target device and a first network device, wherein the target device is the semantic name acquisition device according to any one of claims 10-13, and the first network device is the device according to claim 10 The semantic name acquisition device according to any one of 14-18.