CN110784407B

CN110784407B - Interface configuration method, data transmission method and device and electronic equipment

Info

Publication number: CN110784407B
Application number: CN201911058699.6A
Authority: CN
Inventors: 李�诚
Original assignee: Maipu Communication Technology Co Ltd
Current assignee: Maipu Communication Technology Co Ltd
Priority date: 2019-10-31
Filing date: 2019-10-31
Publication date: 2022-03-18
Anticipated expiration: 2039-10-31
Also published as: CN110784407A

Abstract

The application provides an interface configuration method, a data transmission device and electronic equipment. The method comprises the following steps: determining a source PE and at least one destination PE corresponding to the source PE according to a target service; creating a tunnel interface corresponding to the flow characteristics of the target service on the source PE, and acquiring a forwarding path from the source PE to at least one destination PE; and sending the forwarding path from the source PE to at least one destination PE to the source PE, so that the source PE associates the forwarding path with the tunnel interface, and the data traffic of the target service is output to the corresponding at least one destination PE from the tunnel interface. Therefore, when the service has a plurality of destination PEs, the interface consumed by creating the tunnel on the source PE can be reduced, and the problem that the interface resource consumed by creating the tunnel for the service is large is solved.

Description

Interface configuration method, data transmission method and device and electronic equipment

Technical Field

The invention relates to the technical field of data communication, in particular to an interface configuration method, a data transmission device and electronic equipment.

Background

In the field of communication data processing, MPLS (Multiprotocol Label Switching) is a backbone network technology widely used at present, and a connection-oriented Label Switching concept is introduced on a connectionless IP network to combine a third layer routing technology and a second layer Switching technology to exert flexibility of IP routing and simplicity of second layer Switching.

Segment Routing (SR) is a source Routing technology, where a source node selects a path, converts the path into an ordered Segment list, and encapsulates the Segment list into a header, and a network device forwards the packet according to path information in the header. Segment represents any type of instruction for guiding message forwarding, and in the MPLS network, Segment is a label, including two types of SR labels, namely Prefix/Node Segment and Adjacency Segment.

In an SDN (Software defined Network) Network based on SR MPLS, for various traffic services, a Network device may create a tunnel according to a destination PE of the service, where different destination PEs need to create different tunnels, and then introduce data traffic of the service into corresponding tunnels for transmission. At present, the number of interfaces of the network device is limited, and each created tunnel needs to occupy one interface of the network device, so that interface resources consumed by creating a tunnel for a service are large at present.

Disclosure of Invention

The application provides an interface configuration method, a data transmission device and electronic equipment, which can solve the problem that a tunnel is created for a service, and the interface resources are more.

In order to achieve the above purpose, the technical solutions provided in the embodiments of the present application are as follows:

in a first aspect, an embodiment of the present application provides an interface configuration method, which is applied to a controller, and the method includes:

determining a source PE and at least one destination PE corresponding to the source PE according to a target service; creating a tunnel interface corresponding to the traffic characteristics of the target service on the source PE, and acquiring a forwarding path from the source PE to the at least one destination PE; and sending the forwarding path from the source PE to the at least one destination PE to the source PE, so that the source PE associates the forwarding path with the tunnel interface, and the data traffic of the target service is output from the tunnel interface to the corresponding at least one destination PE.

In the foregoing embodiment, the tunnel interface created on the source PE is associated with a service, and when there are multiple destination PEs in the same service, only one tunnel interface may be created on the source PE to be associated with the service, so as to output the data traffic of the service to the multiple destination PEs through the tunnel interface. Therefore, when the service has a plurality of destination PEs, the interface consumed by creating the tunnel on the source PE can be reduced, and the problem that the interface resource consumed by creating the tunnel for the service is large is solved.

With reference to the first aspect, in some optional embodiments, before obtaining the forwarding path from the source PE to the at least one destination PE, the method further includes:

distributing label information to all network equipment in a network where the source PE is located so as to enable all the network equipment to install forwarding entries corresponding to the label information, wherein the forwarding entries are used for sending data to be forwarded with the label information from current network equipment to next network equipment; obtaining a forwarding path from the source PE to the at least one destination PE, comprising: and selecting network equipment passing through from the source PE to each destination PE according to the requirement of the target service, and generating a forwarding path from the source PE to each destination PE according to the label information of each network equipment passing through from the source PE to each destination PE.

In the above embodiment, the label information is allocated to the network device, so that the network device installs the forwarding table entry for forwarding the data, so that the network device can forward the data according to the forwarding path.

With reference to the first aspect, in some optional embodiments, the forwarding path carries address information of a destination PE of the forwarding path, so that the source PE determines the destination PE according to the forwarding path.

In the foregoing embodiment, the address information of the destination PE is carried in the forwarding path, or the label information of the destination PE is carried in the forwarding path, so that the source PE can determine the destination PE according to the forwarding path, and thus the source PE can determine the forwarding path of the data to be forwarded.

In a second aspect, an embodiment of the present application further provides a data transmission method, which is applied to a source PE, and the method includes:

when data traffic is received, determining a tunnel interface corresponding to the traffic characteristics in advance according to the traffic characteristics of the data traffic, and introducing the data traffic to the tunnel interface; determining a forwarding path matched with the corresponding destination PE from at least one forwarding path associated with the tunnel interface as a target forwarding path according to the corresponding destination PE determined by the data traffic message; adding the target forwarding path to the message; and outputting the data traffic added with the target forwarding path from the tunnel interface so that the data traffic is transmitted to the corresponding destination PE according to the target forwarding path.

In the foregoing embodiment, the source PE may introduce data traffic with the same traffic characteristics and different destination PEs into one tunnel interface, and output the data traffic to the corresponding destination PE through the tunnel interface, so as to save interface resources of the source PE.

With reference to the second aspect, in some optional embodiments, before determining, according to a traffic characteristic of the data traffic, a tunnel interface corresponding to the traffic characteristic in advance, the method further includes: receiving a forwarding path from the source PE to at least one destination PE sent by a controller; and associating the forwarding path with the tunnel interface so that the data traffic of the target service is output to the corresponding at least one destination PE from the tunnel interface.

In the foregoing embodiment, the source PE associates the forwarding path to at least one destination PE with the tunnel interface, so that the source PE can output data traffic, which needs to be sent to multiple destination PEs in the target service, from one tunnel interface, thereby saving interface resources of the source PE.

In a third aspect, an embodiment of the present application further provides an interface configuration device, which is applied to a controller, where the interface configuration device includes:

the device comprises an equipment determining unit, a service processing unit and a service processing unit, wherein the equipment determining unit is used for determining a source PE and at least one destination PE corresponding to the source PE according to a target service;

a creating and acquiring unit, configured to create a tunnel interface corresponding to a traffic characteristic of the target service on the source PE, and acquire a forwarding path from the source PE to the at least one destination PE;

a sending unit, configured to send a forwarding path from the source PE to the at least one destination PE to the source PE, so that the source PE associates the forwarding path with the tunnel interface, so that data traffic of the target service is output from the tunnel interface to the corresponding at least one destination PE.

With reference to the third aspect, in some optional embodiments, the interface configuration apparatus further includes a label allocation unit, before the creating and acquiring unit acquires the forwarding path from the source PE to the at least one destination PE, the label allocation unit is configured to: distributing label information to all network equipment in a network where the source PE is located so as to enable all the network equipment to install forwarding entries corresponding to the label information, wherein the forwarding entries are used for sending data to be forwarded with the label information from current network equipment to next network equipment;

the creation acquisition unit is further configured to: and selecting network equipment passing through from the source PE to each destination PE according to the requirement of the target service, and generating a forwarding path from the source PE to each destination PE according to the label information of each network equipment passing through from the source PE to each destination PE.

With reference to the third aspect, in some optional embodiments, the forwarding path carries address information of a destination PE of the forwarding path or carries the label information of the destination PE, so that the source PE determines the destination PE according to the forwarding path.

In a fourth aspect, an embodiment of the present application further provides a data transmission apparatus, which is applied to a source PE, where the data transmission apparatus includes:

the device comprises a determining and introducing unit, a determining and introducing unit and a judging unit, wherein the determining and introducing unit is used for determining a tunnel interface which is corresponding to the flow characteristics in advance according to the flow characteristics of the data flow when the data flow is received, and introducing the data flow to the tunnel interface;

a path determining unit, configured to determine, according to a corresponding destination PE determined by the packet of the data traffic, a forwarding path matched with the corresponding destination PE from at least one forwarding path associated with the tunnel interface as a target forwarding path;

an adding unit, configured to add the target forwarding path to the message;

and the output unit is used for outputting the data traffic added with the target forwarding path from the tunnel interface so as to enable the data traffic to be transmitted to the corresponding destination PE according to the target forwarding path.

With reference to the fourth aspect, in some optional embodiments, the data transmission device further includes a receiving unit and an associating unit, where before the determining and introducing unit determines, according to the traffic feature of the data traffic, a tunnel interface corresponding to the traffic feature in advance, the receiving unit is configured to: receiving a forwarding path from the source PE to at least one destination PE sent by a controller;

the association unit is used for: and associating the forwarding path with the tunnel interface so that the data traffic of the target service is output from the tunnel interface to the at least one destination PE.

In a fifth aspect, an embodiment of the present application further provides an electronic device, where the electronic device includes a memory and a processor that are coupled to each other, and a computer program is stored in the memory, and when the computer program is executed by the processor, the electronic device executes the interface configuration method or the data transmission method.

In a sixth aspect, an embodiment of the present application further provides a computer-readable storage medium, where a computer program is stored in the computer-readable storage medium, and when the computer program runs on a computer, the computer is caused to execute the interface configuration method or the data transmission method.

Drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings needed to be used in the embodiments will be briefly described below. It is appreciated that the following drawings depict only certain embodiments of the application and are therefore not to be considered limiting of its scope, for those skilled in the art will be able to derive additional related drawings therefrom without the benefit of the inventive faculty.

Fig. 1 is a schematic structural diagram of a network system according to an embodiment of the present application.

Fig. 2 is a schematic flowchart of an interface configuration method according to an embodiment of the present application.

Fig. 3 is a schematic diagram of a forwarding path in a network system according to an embodiment of the present application.

Fig. 4 is a functional block diagram of an interface configuration apparatus according to an embodiment of the present application.

Fig. 5 is a schematic structural diagram of an electronic device according to an embodiment of the present application.

Fig. 6 is a schematic flowchart of a data transmission method according to an embodiment of the present application.

Fig. 7 is a functional block diagram of a data transmission device according to an embodiment of the present application.

Icon: 10-a network system; 20-a controller; 30-source PE; 40-mesh PE; 50-an electronic device; 51-a processing module; 52-a communication module; 53-a storage module; 100-interface configuration means; 110-a device determination unit; 120-creation acquisition unit; 130-a transmitting unit; 200-a data transmission device; 210-determining an introduction unit; 220-a path determination unit; 230-an addition unit; 240-output unit.

Detailed Description

The technical solutions in the embodiments of the present application will be described below with reference to the drawings in the embodiments of the present application. It should be noted that the terms "first," "second," and the like are used merely to distinguish one description from another, and are not intended to indicate or imply relative importance.

First embodiment

Referring to fig. 1, an embodiment of the present application provides a network system 10, where the network system 10 may include a controller 20 and a Provider Edge (PE) device. The PE includes, but is not limited to, a router, a switch, and other network devices for transmitting and exchanging data. The PE connected to the data source may be referred to as a source PE30, the source PE30 may be configured to send data to be forwarded to the target endpoint, and the PE connected to the target endpoint may be referred to as a destination PE40 of the source PE 30. Controller 20 may establish a communication connection with one or more PEs over a network for data interaction over the network.

One or more service Provider intermediate devices (Provider, abbreviated as P) are typically required to indirectly effectuate the communication connection between source PE30 and destination PE 40. Of course, when the source PE30 is close to the destination PE40 (the distance may be set according to actual conditions), the source PE30 and the destination PE40 may directly establish a communication connection through the network for data interaction. The service provider intermediate device may be a router, a switch, or the like.

Understandably, the data source may be a device storing data to be forwarded, and may be, but is not limited to, a smart phone, a personal computer, a tablet computer, a personal digital assistant, and the like. The target terminal is a device for receiving data to be forwarded, and may be, but is not limited to, a smartphone mobile internet access device and the like. The data to be forwarded is data to be sent, including but not limited to video, audio, document, picture, application program and the like, and can be set according to actual conditions.

Referring to fig. 2, an embodiment of the present application further provides an interface configuration method, which can be applied to the controller 20, and each step of the interface configuration method can be executed or implemented by the controller 20. In this embodiment, the interface configuration method may include steps S310 to S330.

Step S310, determining a source PE30 and at least one destination PE40 corresponding to the source PE30 according to a target service;

step S320, creating a tunnel interface corresponding to the traffic characteristics of the target service on the source PE30, and acquiring a forwarding path from the source PE30 to the at least one destination PE 40;

step S330, sending a forwarding path from the source PE30 to the at least one destination PE40 to the source PE30, so that the source PE30 associates the forwarding path with the tunnel interface, so that the data traffic of the target service is output from the tunnel interface to the corresponding at least one destination PE 40.

In the above embodiment, the tunnel interface created in the source PE30 is associated with a service, and when there are multiple destination PEs 40 for the same service, only one tunnel interface may be created on the source PE30 to be associated with the service, so as to output the data traffic of the service to the multiple destination PEs 40 through the tunnel interface. Based on this, when there are a plurality of destination PEs 40 in the traffic, it is possible to reduce the interfaces consumed when creating a tunnel on source PE30, thereby improving the problem that creating a tunnel for the traffic consumes many interface resources.

The steps of the interface configuration method shown in fig. 2 will be described in detail below:

step S310, determining a source PE30 and at least one destination PE40 corresponding to the source PE30 according to a target service.

In this embodiment, the target service may be understood as a service corresponding to the traffic data that needs to be forwarded, and the service may be set according to an actual situation. For example, the target service may send video, document waiting forwarding data to one or more target terminals for the user through the terminal device. In the process of sending data to be forwarded from the terminal device to the target terminal and receiving the data, the data to be forwarded generally needs to be forwarded by the source PE30, P and the destination PE40, and finally is output to the target terminal by the destination PE 40.

The source PE30 and the at least one destination PE40 may be selected from a plurality of PEs in the entire network according to actual conditions. For example, a user may specify source PE30 and destination PE40 of a target service through controller 20. The number of source PEs 30 of one service may be one or more. The number of destination PEs 40 corresponding to the source PE30 may be one or more, and is not particularly limited herein.

Step S320, a tunnel interface corresponding to the traffic characteristics of the target service is created on the source PE30, and a forwarding path from the source PE30 to the at least one destination PE40 is obtained.

The traffic characteristics of the target traffic include, but are not limited to, the source IP address, source port, destination IP address, destination port, transport layer protocol, etc. of the data traffic that the target traffic needs to transport. When multiple data flows of the same service need to be output from one source PE30 to multiple destination PEs 40, the flow characteristics of the multiple data flows are matched and associated with one tunnel interface of the source PE 30. The tunnel interface is an interface corresponding to the SR-TE tunnel created on source PE 30.

Understandably, the SR-TE tunnel is an SR tunnel for implementing Traffic Engineering (TE). The traffic engineering avoids network congestion by controlling the forwarding path of traffic in the network, and improves the network performance. An SR tunnel is a tunnel that encapsulates a Segment list into a header on source PE 30. The Segment list is used to represent the forwarding path.

When multiple data traffics of the same service need to be output from one source PE30 to multiple destination PEs 40, the source PE30 may create only one tunnel interface and correspond to the traffic characteristics of the service. When the source PE30 receives a plurality of data flows of a service, it may match a tunnel interface corresponding to the traffic characteristics in advance according to the traffic characteristics of the plurality of data flows, and based on this, even if there are a plurality of destination PEs 40 of the plurality of data flows, the source PE30 may introduce the plurality of data flows to a tunnel interface corresponding to the service (or traffic characteristics) and output the plurality of data flows to the corresponding destination PE40 through a tunnel interface.

In this embodiment, after determining the source PE30 and the at least one destination PE40, the controller 20 may acquire a forwarding path from the source PE30 to the corresponding at least one destination PE 40.

For example, prior to step S320, the method may further comprise: distributing label information to all network devices in the network where the source PE30 is located, so that all the network devices install forwarding entries corresponding to the label information, where the forwarding entries are used to send data to be forwarded with the label information from a current network device to a next network device. Wherein obtaining a forwarding path from the source PE30 to the at least one destination PE40 comprises: according to the requirement of the target service, network devices passing from the source PE30 to each destination PE40 are selected, and according to the label information of each network device passing from the source PE30 to each destination PE40, a forwarding path from the source PE30 to each destination PE40 is generated.

In this embodiment, the network device may be understood as a service provider intermediate device and a service provider edge device, and may be a router or a switch for relaying/transmitting data. The source PE30 generally includes a plurality of service provider intermediate devices and service provider edge devices in the network. Controller 20 may need to assign label information to all network devices in the network before determining a forwarding path for source PE30 to each destination PE 40. All network devices include source PE30, destination PE40, and service provider intermediate devices. The tag information includes a Node tag (Node tag is a Node tag, which may refer to Prefix/Node Segment), and an Adj tag (Adj tag is an adjacent tag, which may refer to Adjacency Segment), which may be set according to actual situations.

The Node labels are labels allocated to the network devices, and are used for distinguishing identities of the network devices in the network, and the Node labels are unique throughout the network (that is, in the network where the source PE30 is located, Node labels of different network devices are different). The Adj label is a label assigned to a link of a network device, and the network device assigned to the Adj label can forward data according to the Adj label (that is, the Adj label is valid in the node), and an Adj label value represents a link on one network device.

In this embodiment, the manner for the controller 20 to allocate the tag information to the network device includes: the processor of the controller 20 allocates tag information to the network device, or the controller 20 obtains the tag information allocated to the network device by an Interior Gateway Protocol (IGP).

After the Label information is allocated, the network device may install a forwarding entry corresponding to the SR Label, where the forwarding entry may be an Incoming Label Map (ILM for short). Understandably, the forwarding table entry is used for sending the data to be forwarded with the label information from the current network device to the next network device.

In this embodiment, generating a forwarding path from the source PE30 to each destination PE40 according to the label information of each network device passed by from the source PE30 to each destination PE40 may include: for each destination PE40, the label information of each network device passed by the source PE30 to the destination PE40 is assembled to generate a forwarding path according to the sequence of the network devices passed by the source PE30 to the destination PE40, the forwarding path may be assembled into an ordered list, or may be a label stack, a queue, or the like, and the assembling manner of the path is not specifically limited.

Referring to fig. 3, assume network device a is source PE30 and network device Z is destination PE 40. Network device B to network device G are service provider intermediate devices. If controller 20 determines that the forwarding path from source PE30 to destination PE40 is a-B-D-E-G-Z, it needs to assemble the Adj labels corresponding to all links passed by the path into a label stack in sequence, and adds the assembled label stack to the packet for data traffic transmission on network device a. The assembled label stack may serve as a forwarding path from the source PE30 to the destination PE40, where the network device may identify the processing.

For example, in fig. 3, it is assumed that an Adj label of a link from network device a to network device B is 1008, an Adj label of a link from network device B to network device D is 2008, an Adj label of a link from network device D to network device E is 3008, an Adj label of a link from network device E to network device G is 4008, and an Adj label of a link from network device G to network device Z is 5008. Controller 20 may organize Adj labels 1008-5008 into forwarding paths in the order of a-B-D-E-G-Z in the manner of label stacks shown in fig. 3, and then send the label stacks to network device a, so that network device a adds the label stacks or forwarding paths to packets for data traffic transmission when forwarding data traffic.

It should be noted that controller 20 may determine forwarding paths from source PE30 to each destination PE40 according to actual conditions. For example, controller 20 may determine the path having the fewest number of nodes traversed in the path from source PE30 to destination PE40 as the forwarding path from source PE30 to destination PE 40.

In this embodiment, the forwarding path may carry address information of the destination PE40 of the forwarding path or carry tag information of the destination PE40, so that the source PE30 determines the destination PE40 from the forwarding path. By carrying the address information of the destination PE40 or the label information of the destination PE40 in the forwarding path, the source PE30 can determine the destination PE40 according to the forwarding path, so that the source PE30 can determine the forwarding path of the data to be forwarded.

For example, in fig. 3, assuming that the Node label of network device Z is 10000, controller 20 may add Node label 10000 to the label stack shown in the figure, and the addition may be in front of the label stack or behind the label stack; the label stack is then sent to network device a for network device a to determine that the destination PE40 of the label stack is network device Z.

In this embodiment, controller 20 may issue the determined forwarding paths to source PE30, so that source PE30 associates one or more forwarding paths with one tunnel interface. For example, multiple forwarding paths are associated with one tunnel interface, and each of the multiple forwarding paths is a forwarding path that needs to be sent from the same source PE30 to multiple destination PEs 40 in the same service. Based on this, for the service, only one tunnel interface may be created on the source PE30 to satisfy the transmission of the data traffic of the service, and there is no need to create a tunnel interface separately for each destination PE40, so that the number of tunnel interfaces that need to be created can be reduced. In addition, source PE30 can reserve more interfaces that can act as tunnel interfaces for other traffic, thereby helping to extend the number of traffic supported by source PE 30.

Understandably, assuming that a tunnel interface is created separately for each destination PE40, for one source PE30, if the destination PE40 of the service is N, N is an integer greater than 0, it is necessary to create N tunnel interfaces. In the above embodiment, only one tunnel interface is created for the plurality of destination PEs 40 of the traffic, so that the number of tunnel interfaces created for the traffic at the source PE30 can be reduced.

Referring to fig. 4, an interface configuration apparatus 100 is further provided in the present embodiment. The interface configuration apparatus 100 includes at least one software functional module, which can be stored in the form of software or Firmware (Firmware) in the memory of the controller 20 or solidified in the Operating System (OS) of the controller 20. The processor of the controller 20 may be used to execute executable modules stored in the memory, such as software functional modules and computer programs included in the interface configuration apparatus 100.

In this embodiment, the interface configuration apparatus 100 may include a device determining unit 110, a creation acquiring unit 120, and a sending unit 130.

An apparatus determining unit 110, configured to determine, according to a target service, a source PE30 and at least one destination PE40 corresponding to the source PE 30.

A creating and acquiring unit 120, configured to create a tunnel interface corresponding to a traffic characteristic of the target service on the source PE30, and acquire a forwarding path from the source PE30 to the at least one destination PE 40.

A sending unit 130, configured to send a forwarding path from the source PE30 to the at least one destination PE40 to the source PE30, so that the source PE30 associates the forwarding path with the tunnel interface, so that data traffic of the target traffic is output from the tunnel interface to the corresponding at least one destination PE 40.

The interface configuration apparatus 100 may further include a label assignment unit. Before the creation obtaining unit 120 obtains the forwarding path from the source PE30 to the at least one destination PE40, the label distribution unit is configured to: distributing label information to all network devices in the network where the source PE30 is located, so that all the network devices install forwarding entries corresponding to the label information, where the forwarding entries are used to send data to be forwarded with the label information from a current network device to a next network device.

The creation acquiring unit 120 is further configured to: according to the requirement of the target service, network devices passing from the source PE30 to each destination PE40 are selected, and according to the label information of each network device passing from the source PE30 to each destination PE40, a forwarding path from the source PE30 to each destination PE40 is generated.

Optionally, the creation acquiring unit 120 is further configured to: for each destination PE40, the label information of each network device passed by the source PE30 to the destination PE40 is organized to form a forwarding path in the order of the network devices passed by the source PE30 to the destination PE 40.

Wherein the forwarding path carries address information of the destination PE40 of the forwarding path or carries the label information of the destination PE40, so that the source PE30 determines the destination PE40 according to the forwarding path.

Referring to fig. 5, an electronic device 50 is further provided in the embodiments of the present application, where the electronic device 50 may include a processing module 51, a communication module 52, and a storage module 53, and the processing module 51, the communication module 52, and the storage module 53 are directly or indirectly electrically connected to each other to implement data transmission or interaction. For example, the components may be electrically connected to each other via one or more communication buses or signal lines. The electronic device 50 may further include an interface configuration apparatus 100 or a data transmission apparatus 200 (see fig. 7), which is stored in the storage module 53 in the form of software or Firmware (Firmware) or is solidified in an Operating System (OS) of the electronic device 50.

Understandably, the electronic device 50 may be the controller 20 or the source PE 30. The electronic device 50 for performing or implementing the interface configuration method is the controller 20, and the electronic device 50 for performing or implementing the data transfer method is the source PE 30. When the electronic device 50 includes the interface configuration apparatus 100, it may be configured to perform each step of the interface configuration method; the electronic device 50, when including the data transmission apparatus 200, may be configured to perform the steps of the data transmission method.

The processing module 51 may be an integrated circuit chip having signal processing capabilities. The processing module 51 may be a general-purpose processor. For example, the Processor may be a Central Processing Unit (CPU), a Graphics Processing Unit (GPU), a Network Processor (NP), or the like; the method, the steps and the logic block diagram disclosed in the embodiments of the present Application may also be implemented or executed by a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other Programmable logic devices, discrete gates or transistor logic devices, or discrete hardware components.

The memory module 53 may be, but is not limited to, a random access memory, a read only memory, a programmable read only memory, an erasable programmable read only memory, an electrically erasable programmable read only memory, and the like. In this embodiment, the storage module 53 may be configured to store data such as a forwarding table entry and a forwarding path. Of course, the storage module 53 may also be used to store a program, and the processing module 51 executes the program after receiving the execution instruction.

The communication module 52 is used for establishing a communication connection between the electronic device 50 and other devices (such as the controller 20, the PE, the P, and the like) through a network, and transceiving data through the network. For example, when the electronic device 50 is the controller 20, the communication module 52 may be used to establish a communication connection between the electronic device 50 and a network device such as a PE, a P, etc. in a network. The communication module 52 may be used to establish a communication connection for the electronic device 50 with the controller 20 when the electronic device 50 is the source PE 30.

It is understood that the structure shown in fig. 5 is only a schematic structural diagram of the electronic device 50, and the electronic device 50 may further include more components than those shown in fig. 5. The components shown in fig. 5 may be implemented in hardware, software, or a combination thereof.

It should be clearly understood by those skilled in the art that, for convenience and brevity of description, the specific working processes of the electronic device 50 and the interface configuration apparatus 100 described above may refer to the corresponding processes of the steps in the foregoing method, and are not described in detail herein.

Second embodiment

Referring to fig. 6, an embodiment of the present application further provides a data transmission method, which can be applied to the source PE30, and the source PE30 can execute or implement the steps of the data transmission method. The data transmission method may include steps S410 to S440. The following will describe the steps of the data transmission method in detail:

step S410, when data traffic is received, a tunnel interface corresponding to the traffic characteristics in advance is determined according to the traffic characteristics of the data traffic, and the data traffic is introduced into the tunnel interface.

In this embodiment, the traffic characteristics of the data traffic include, but are not limited to, a source IP address, a source port, a destination IP address, a destination port, and a transport layer protocol for transmitting the packet of the data traffic. When multiple data traffics of the same service need to be output from one source PE30 to multiple destination PEs 40, the traffic characteristics of the multiple data traffics are matched and are associated with one tunnel interface of the source PE30 in advance.

For example, prior to step S410, the method may further comprise: receiving a forwarding path from the source PE30 to at least one destination PE40 sent by controller 20; associating the forwarding path with the tunnel interface for data traffic of the target traffic to be output from the tunnel interface to the at least one destination PE 40.

Understandably, controller 20 may retrieve a forwarding path from source PE30 to at least one destination PE40 and then send the retrieved forwarding path to source PE 30. The step S320 in the first embodiment may be referred to when the controller 20 obtains the forwarding path from the source PE30 to the at least one destination PE40, which is not described herein again.

After the traffic characteristics are associated with (or correspond to) the tunnel interface of the source PE30, when the source PE30 receives data traffic that needs to be transmitted, the traffic characteristics of the data traffic (i.e., the quintuple of the packets such as the source IP address, the source port, and the destination IP address) can be obtained by parsing the packet of the data traffic, and then the tunnel interface corresponding to the traffic characteristics can be determined on the source PE30 based on the parsed traffic characteristics and the correspondence between the traffic characteristics and the tunnel interface. Having determined a tunnel interface, all traffic of the same traffic received by source PE30 corresponding to the traffic characteristics may be directed to the tunnel interface to facilitate outputting of data traffic from the tunnel interface to one or more destination PEs 40.

Step S420, according to the corresponding destination PE40 determined by the packet of the data traffic, determining, from at least one forwarding path associated with the tunnel interface, a forwarding path matched with the corresponding destination PE40 as a target forwarding path.

At least one forwarding path associated with the tunnel interface is implemented by the interface configuration method in the foregoing embodiment. That is, the controller 20 determines a forwarding path from the source PE30 to the at least one destination PE40 through steps S310 to S330, and then transmits the resulting forwarding path to the source PE30, so that the source PE30 associates the forwarding path (i.e., at least one forwarding path) from the source PE30 to the at least one destination PE40 with a tunnel interface. In addition, the principle of determining, as the target forwarding path, the forwarding path matching the corresponding destination PE40 in the at least one forwarding path may be: when the destination address information carried by the forwarding path is the same as the address information of destination PE40, it is determined that the forwarding path matches destination PE 40.

Step S430, add the target forwarding path to the message.

Understandably, after the forwarding path is added to the message, the data traffic that needs to be transmitted can be transmitted to the corresponding destination PE40 according to the forwarding path.

Step S440, outputting the data traffic added with the target forwarding path from the tunnel interface, so that the data traffic is transmitted to the corresponding destination PE40 according to the target forwarding path.

In the above embodiment, the source PE30 may introduce data traffic with the same traffic characteristics and different destination PEs 40 to one tunnel interface, and output the data traffic to the corresponding destination PE40 through the tunnel interface, so that interface resources of the source PE30 can be saved.

For convenience of understanding, the implementation process will be described in the following by taking an interface configuration method and a data transmission method as examples:

for example, in a first step, SR labels (label information) are assigned by the controller 20 to network devices in the entire network, including Node labels for the network devices and Adj labels for links of the network devices. The method for allocating the SR tag may include: may be assigned by the SDN controller (processor) of the controller 20 or may be assigned by the IGP protocol.

If the SDN controller is assigned a label, the process may be: a Border Gateway Protocol (BGP) neighbor is established between an SDN controller and a Network device in a Network, a Network topology is obtained through a BGP-LS (Border Gateway Protocol Link State), then Node tags are allocated to The Network devices in The whole Network, Adj tags are allocated to each Link between The Network devices, The Node tags are issued to all The Network devices in The Network through a Network Configuration Protocol (NETCONF), and The Adj tags are issued to The Network devices where The links are located.

If labels are assigned to the IGP protocol, the process may be: the network device runs an IGP protocol thereon. The IGP protocol may include OSPF (Open Shortest Path First), ISIS (Intermediate System to Intermediate System). The IGP protocol may be extended to support the SR, for example, a Node label may be allocated to a network device running the IGP protocol, an Adj label may be allocated to a link of the network device, and the Node label is notified to the outside, so that all network devices in the entire network can learn. In addition, BGP-LS can be expanded, and when the SDN controller acquires the network topology through the BGP-LS, the SDN controller can also acquire a Node label and an Adj label distributed by an IGP protocol.

Step two, the network device installs an ILM (forwarding table entry) corresponding to the SR tag, which may be as follows: after the network equipment receives the Node label issued by the SDN controller (or after the network equipment distributes the Node label or learns the Node label by operating an IGP protocol), the corresponding ILM is installed: the incoming label is a Node label and the corresponding FEC is the address of the device (usually the address of the ring back port on the device). After the network equipment receives the Adj label issued by the SDN controller (or after the network equipment distributes the Adj label by operating an IGP protocol), installing the corresponding ILM: the incoming label is an Adj label, the outgoing interface is an interface corresponding to the link, and the next hop is the link opposite-end address.

Third, the user defines the service through the SDN controller, and specifies all source PEs 30 of the service and all destination PEs 40 corresponding to the source PEs 30. Then, SR-TE tunnels are created for the services, and only one SR-TE tunnel is created on each source PE30 device of the services, that is, only one tunnel interface is created correspondingly. The tunnel interface can be created manually by a network administrator or automatically issued by an SDN controller through NETCONF.

Fourth, the SDN controller calculates a forwarding path from the source PE30 to each destination PE40 according to the service requirement, for example, the shortest path may be used as the forwarding path from the source PE30 to the destination PE 40.

Fifthly, after the SDN controller calculates a forwarding path from the source PE30 to the destination PE40, the SDN controller may organize Adj labels corresponding to all links passed by the forwarding path into a label stack form according to a passing order, and issue the label stack onto the source PE30 through NETCONF, so that the source PE30 associates the label stack with a corresponding tunnel interface.

In addition, the controller 20 may further indicate, according to the forwarding path, a destination PE40 corresponding to the forwarding path, and may include: the address of the destination PE40 is carried in the issued forwarding path information at the same time, so that the source PE30 reads the carried address of the destination PE40 from the forwarding path; or, a Node label corresponding to destination PE40 is added at the stack bottom of the label stack corresponding to the forwarding path, where the Node label is unique throughout the network and is learned throughout the network, so that source PE30 can determine destination PE40 from the label stack of the forwarding path.

Sixthly, after receiving forwarding path information issued by the SDN controller, the source PE30 determines a destination PE40 corresponding to the forwarding path, where the determining may include: acquiring a destination PE40 address carried in the issued forwarding path information; or, according to the Node label at the stack bottom of the delivered label stack, searching for a corresponding ILM, where an FEC (Forwarding Equivalence Class) corresponding to the ILM is an address of the destination PE 40. Then, source PE30 records the association relationship between the label stack and the tunnel interface, and records the destination PE40 address corresponding to the label stack.

Seventhly, the SDN controller issues drainage configuration to the source PE30 through NETCONF, and data traffic to different destination PE40 is introduced to the same tunnel interface corresponding to the SR-TE tunnel. For example, data traffic of the same service can be introduced to one tunnel interface through a plurality of ways such as Routing, PBR (Policy Based Routing, etc. (by setting the outgoing interface as the corresponding tunnel interface).

And eighthly, introducing the data traffic to a tunnel interface corresponding to the SR-TE tunnel through a route or PBR (provider backbone transport protocol) mode after the data traffic reaches the source PE30, searching an IP route according to a destination address of an IP message of the data traffic, determining a gateway address according to the IP route, matching destination PE40 addresses corresponding to all label stacks associated with the tunnel interface according to the gateway address, and pressing the matched label stacks into the message to be sent out. Based on this, the data traffic of different destination PEs 40 can be output from one tunnel interface of the source PE30, and the corresponding destination PE40 can receive the corresponding data traffic, so that the number of tunnel interfaces created on the source PE30 can be reduced, and the consumption of interface resources can be reduced.

In addition, when a service needs to add or reduce the destination PE40 to the source PE30, a forwarding path to the destination PE40 may be issued or deleted to the corresponding source PE30, and corresponding tunnel interfaces do not need to be created or deleted on all the source PEs 30, so that the network deployment is simple and easy to expand.

Referring to fig. 7, an embodiment of the present application further provides a data transmission apparatus 200, which can be applied to the source PE30 described above and can be used to execute or implement each step in the data transmission method. The data transmission apparatus 200 may include: a determination introduction unit 210, a path determination unit 220, an addition unit 230, and an output unit 240.

The determining and introducing unit 210 is configured to determine, when receiving a data traffic, a tunnel interface corresponding to a traffic characteristic in advance according to the traffic characteristic of the data traffic, and introduce the data traffic to the tunnel interface.

A path determining unit 220, configured to determine, according to the corresponding destination PE40 determined by the packet of the data traffic, a forwarding path matched with the corresponding destination PE40 from at least one forwarding path associated with the tunnel interface as a target forwarding path.

An adding unit 230, configured to add the target forwarding path to the message.

An output unit 240, configured to output, from the tunnel interface, the data traffic added with the target forwarding path, so that the data traffic is transmitted to the corresponding destination PE40 according to the target forwarding path.

Optionally, the data transmission apparatus 200 may further include a receiving unit and an associating unit.

Before the determining and introducing unit 210 determines a tunnel interface corresponding to the traffic characteristics in advance according to the traffic characteristics of the data traffic, the receiving unit is configured to receive a forwarding path from the source PE30 to the corresponding at least one destination PE40, where the forwarding path is sent by the controller 20.

The associating unit is configured to associate the forwarding path with the tunnel interface, so that data traffic of the target service is output from the tunnel interface to the at least one destination PE 40.

It should be clearly understood by those skilled in the art that, for convenience and brevity of description, the specific working process of the data transmission apparatus 200 described above may refer to the corresponding process of each step in the foregoing data transmission method, and will not be described in detail herein.

The embodiment of the application also provides a computer readable storage medium. The readable storage medium has stored therein a computer program that, when run on a computer, causes the computer to execute the interface configuration method described in the above embodiments or to execute the above data transmission method.

From the above description of the embodiments, it is clear to those skilled in the art that the present application can be implemented by hardware, or by software plus a necessary general hardware platform, and based on such understanding, the technical solution of the present application can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (which can be a CD-ROM, a usb disk, a removable hard disk, etc.), and includes several instructions to enable a computer device (which can be a personal computer, a controller, or a network device, etc.) to execute the method described in the embodiments of the present application.

In summary, the present application provides an interface configuration method, a data transmission method, an apparatus and an electronic device. The method comprises the following steps: determining a source PE and at least one destination PE corresponding to the source PE according to a target service; creating a tunnel interface corresponding to the flow characteristics of the target service on the source PE, and acquiring a forwarding path from the source PE to at least one destination PE; and sending the forwarding path from the source PE to at least one destination PE to the source PE, so that the source PE associates the forwarding path with the tunnel interface, and the data traffic of the target service is output to the corresponding at least one destination PE from the tunnel interface. In the scheme, the tunnel interface created in the source PE is associated with a service, and when multiple destination PEs exist for the same service, only one tunnel interface may be created on the source PE to be associated with the service, so as to output the data traffic of the service to the multiple destination PEs through the tunnel interface. Therefore, when the service has a plurality of destination PEs, the interface consumed by creating the tunnel on the source PE can be reduced, and the problem that the interface resource consumed by creating the tunnel for the service is large is solved.

In the embodiments provided in the present application, it should be understood that the disclosed apparatus, system, and method may be implemented in other ways. The apparatus, system, and method embodiments described above are illustrative only, as the flowcharts and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present application. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions. In addition, functional modules in the embodiments of the present application may be integrated together to form an independent part, or each module may exist separately, or two or more modules may be integrated to form an independent part.

The above description is only a preferred embodiment of the present application and is not intended to limit the present application, and various modifications and changes may be made by those skilled in the art. Any modification, equivalent replacement, improvement and the like made within the spirit and principle of the present application shall be included in the protection scope of the present application.

Claims

1. An interface configuration method, applied to a controller, the method comprising:

determining a source PE and at least one destination PE corresponding to the source PE according to a target service;

creating a tunnel interface corresponding to the traffic characteristics of the target service on the source PE, and acquiring a forwarding path from the source PE to the at least one destination PE, wherein the traffic characteristics of the same service correspond to the same tunnel interface;

and sending the forwarding path from the source PE to the at least one destination PE to the source PE, so that the source PE associates the forwarding path with the tunnel interface, and the data traffic of the target service is output from the tunnel interface to the corresponding at least one destination PE.

2. The method of claim 1, wherein prior to obtaining the forwarding path from the source PE to the at least one destination PE, the method further comprises:

distributing label information to all network equipment in a network where the source PE is located, so that all the network equipment installs forwarding entries corresponding to the label information;

obtaining a forwarding path from the source PE to the at least one destination PE, comprising:

and selecting network equipment passing through from the source PE to each destination PE according to the requirement of the target service, and generating a forwarding path from the source PE to each destination PE according to the label information of each network equipment passing through from the source PE to each destination PE.

3. The method according to claim 2, wherein the forwarding path carries address information of a destination PE of the forwarding path, so that the source PE determines the destination PE according to the forwarding path.

4. A data transmission method, applied to a source PE, the method comprising:

when data traffic is received, determining a tunnel interface corresponding to the traffic characteristics according to the traffic characteristics of the data traffic, and introducing the data traffic to the tunnel interface, wherein the traffic characteristics of the same service correspond to the same tunnel interface;

determining a corresponding destination PE according to the data traffic message, and determining a forwarding path matched with the corresponding destination PE from at least one forwarding path associated with the tunnel interface as a target forwarding path;

adding the target forwarding path to the message;

and outputting the data traffic added with the target forwarding path from the tunnel interface so that the data traffic is transmitted to the corresponding destination PE according to the target forwarding path.

5. The method according to claim 4, wherein before determining a tunnel interface corresponding to the traffic characteristics in advance according to the traffic characteristics of the data traffic, the method further comprises:

receiving a forwarding path from the source PE to at least one destination PE sent by a controller;

and associating the forwarding path with the tunnel interface so that the data traffic of the target service is output to the corresponding at least one destination PE from the tunnel interface.

6. An interface configuration device, applied to a controller, the interface configuration device comprising:

a creating and acquiring unit, configured to create a tunnel interface corresponding to a traffic characteristic of the target service on the source PE, and acquire a forwarding path from the source PE to the at least one destination PE, where traffic characteristics of the same service correspond to the same tunnel interface;

7. The interface configuration apparatus according to claim 6, wherein the interface configuration apparatus further comprises a label allocation unit, before the creation obtaining unit obtains the forwarding path from the source PE to the at least one destination PE, the label allocation unit is configured to: distributing label information to all network equipment in a network where the source PE is located, so that all the network equipment installs forwarding entries corresponding to the label information;

8. The interface configuration apparatus according to claim 7, wherein the forwarding path carries address information of a destination PE of the forwarding path, so that the source PE determines the destination PE according to the forwarding path.

9. A data transmission apparatus, applied to a source PE, the data transmission apparatus comprising:

the system comprises a determining and introducing unit, a determining and introducing unit and a judging unit, wherein the determining and introducing unit is used for determining a tunnel interface which is corresponding to the flow characteristics in advance according to the flow characteristics of the data flow when receiving the data flow, and introducing the data flow to the tunnel interface, wherein the flow characteristics of the same service correspond to the same tunnel interface;

a path determining unit, configured to determine a corresponding destination PE according to the packet of the data traffic, and determine, from at least one forwarding path associated with the tunnel interface, a forwarding path matched with the corresponding destination PE as a target forwarding path;

an adding unit, configured to add the target forwarding path to the message;

10. The data transmission apparatus according to claim 9, wherein the data transmission apparatus further includes a receiving unit and an associating unit, and before the determining unit determines, according to the traffic characteristics of the data traffic, a tunnel interface corresponding to the traffic characteristics in advance, the receiving unit is configured to: receiving a forwarding path from the source PE to at least one destination PE sent by a controller;

11. An electronic device, characterized in that the electronic device comprises a memory and a processor coupled to each other, the memory having stored therein a computer program, which, when executed by the processor, causes the electronic device to execute the interface configuration method according to any one of claims 1-3, or to execute the data transmission method according to claim 4 or 5.

12. A computer-readable storage medium, in which a computer program is stored which, when run on a computer, causes the computer to perform an interface configuration method according to any one of claims 1 to 3, or to perform a data transmission method according to claim 4 or 5.