WO2024108493A1

WO2024108493A1 - Virtual and real combined dynamic traffic scheduling method and apparatus based on sdn and ndn

Info

Publication number: WO2024108493A1
Application number: PCT/CN2022/134100
Authority: WO
Inventors: 葛俊成; 闫林林; 邹涛; 徐琪; 骆汉光; 张汝云
Original assignee: 之江实验室
Priority date: 2022-11-24
Filing date: 2022-11-24
Publication date: 2024-05-30

Abstract

Disclosed in the present invention are a virtual and real combined dynamic traffic scheduling method and apparatus based on SDN and NDN. The method comprises: constructing an NDN on the basis of network topology, and connecting virtual switches, programmable switches, an SDN controller, producer hosts and consumer hosts; when the producer hosts access or leave the network, sending a request data packet to the controller, and the controller updating producer data according to the request data packet; when the data packet is forwarded between the programmable switches or the virtual switches, the programmable switches or the virtual switches judging the type of the data packet; if the data packet is an IP data packet, carrying out L2/L3 forwarding; if the data packet is an NDN interest packet, forwarding same according to a content storage table, a pending interest table and a forwarding information base, and when the forwarding information base fails to match, the switches sending a request to the controller, and the controller deciding a forwarding path; and if the data packet is an NDN data packet, forwarding same according to the content storage table and the pending interest table.

Description

Virtual-real combined dynamic traffic scheduling method and device based on SDN and NDN

Technical Field

The present invention belongs to the fields of computer network technology and mobile communication technology, and in particular to a virtual-real combined dynamic traffic scheduling method and device based on SDN (Software-Defined Networking) and NDN (Named Data Networking).

Background technique

In traditional network devices, the control plane and forwarding plane are integrated into one piece of hardware and run. The control plane, which is the brain of data forwarding, is distributed to each network node, making it difficult to control the entire network. SDN decouples the control management plane from the data forwarding plane. The network is centrally managed by the control layer without relying on the underlying network devices. It has three major features: "separation of control and forwarding", "virtualization of device resources" and "universal hardware and software programmability".

IP networks are mainly used as communication networks to transmit data packets point-to-point. With the rapid growth of e-commerce, digital media, social networks and smartphone applications, distributed networks are more common than communication networks. Point-to-point communication protocols are complex and error-prone to solve distributed problems. NDN (Named Data Networking) proposes an evolution of the IP architecture, which has two types of data packets: interest packets and data packets. Its natural support for caching and multicasting can be widely used in scenarios such as video streaming, real-time conferencing, and in-vehicle networks. The consumer puts the content name of the required data block in an interest packet and forwards it to the network. Once the interest packet reaches the node with the requested data, it returns a data packet containing the content name and content, as well as a signature bound by the producer's secret key. The forwarding of interest packets and data packets depends on three tables: PIT table (Pending Interest Table, request interest table), FIB table (Forwarding Information Base, forwarding information table), and CS table (Content Store, content storage table). The PIT table stores the content name and input port of the interest packet that has been forwarded but has not yet received the data packet. When a data packet arrives, the NDN router will check the matching data in the CS table. If it exists, the router will forward the data packet according to all the port numbers corresponding to the PIT table. If it does not exist, the router will look up the content name of the interest packet in the PIT table. If there is a matching entry, the router will only add the port number to this matching entry. Otherwise, the router will forward the interest packet to the data producer according to the FIB forwarding table entry and insert the port number information into the PIT table. When the data packet arrives at the router, it will first match the PIT table. If the match is successful, the data packet will be forwarded to all ports corresponding to the PIT table, and then the PIT entry will be deleted and the data packet will be cached in the CS table. If the match to the PIT table fails, the data packet will be discarded.

Virtual network is a local network virtualized by Mininet simulation platform, including virtual switches and virtual hosts. It can flexibly simulate various network topologies according to user needs, but it cannot achieve good forwarding performance due to resource constraints. Programmable switches have good forwarding performance, but when building a large-scale network environment, the equipment maintenance and purchase costs are huge. Therefore, building a large-scale forwarding network that combines virtual and real can meet the needs of scale and authenticity at the same time.

Since NDN content names are richer than IP addresses, interest packet forwarding relies on content name lookup and matching in the FIB, which requires a large amount of SRAM and TCAM resources. The FIB table uses a flooding method to maintain the routing of the entire network through the Link State Routing Protocol (NLSR). Its processing delay increases sharply as the topology increases, which can easily cause problems such as interest packet discarding due to untimely FIB table updates. In addition, the Link State Database (LSDB) on the NDN router can only update data at synchronous cycle intervals. When the producer moves, it cannot be immediately discovered by the NDN router, resulting in a lag in the update of the FIB table.

Summary of the invention

The purpose of the present invention is to address the technical defects of "the routers of the traditional NDN architecture need to use the link state routing protocol NLSR to maintain the routing of the entire network by flooding, the processing delay is too long, and it is easy to cause the interest packet to be discarded due to the untimely update of the FIB", "there is a lag in the update of the FIB table, and the producer cannot be immediately discovered by the NDN router when it moves", and "it is difficult to meet the scalability and authenticity requirements when building a large-scale network environment". A virtual-real dynamic traffic scheduling method based on SDN and NDN is proposed for use in the field of computer network technology to solve the above-mentioned problems existing in the traditional NDN architecture.

In order to achieve the above object, the technical solution of the present invention is as follows: A first aspect of an embodiment of the present invention provides a virtual-real combined dynamic traffic scheduling method based on SDN and NDN, the method comprising:

Build an NDN network based on network topology: several virtual switches form a virtual network topology, several programmable switches form a physical network topology, several virtual network topologies are connected to the physical network topology, and all communicate with the SDN controller; the producer host and consumer host running the NDN protocol stack are randomly connected to a programmable switch or a virtual switch;

When a producer host joins or leaves the NDN network, it sends a request packet to the SDN controller, and the SDN controller updates the producer data based on the request packet;

When forwarding a data packet between programmable switches or virtual switches, the programmable switch or virtual switch determines the type of the data packet; if the data packet is an IP data packet, it performs layer 2 and layer 3 forwarding; if the data packet is an NDN interest packet, it forwards it according to the content storage table, request interest table, and forwarding information table; if the data packet is an NDN data packet, it forwards it according to the content storage table and request interest table.

A second aspect of an embodiment of the present invention provides a virtual-real combined dynamic traffic scheduling device based on SDN and NDN, comprising one or more processors for the above-mentioned virtual-real combined dynamic traffic scheduling method based on SDN and NDN.

A third aspect of an embodiment of the present invention provides a computer-readable storage medium on which a program is stored. When the program is executed by a processor, it is used to implement the above-mentioned virtual-real combined dynamic traffic scheduling method based on SDN and NDN.

The beneficial effects of the present invention are:

The virtual-real combined dynamic traffic scheduling method based on SDN and NDN proposed in the present invention separates the control plane from the data plane, so that the network forwarding decision is determined by the control plane with a global view, and the data plane only needs to forward according to the PIT table, FIB table and CS table, which solves the problem that the routers of the traditional NDN architecture need to use NLSR to maintain the routing of the entire network through flooding, and the processing delay is too long, which easily causes the interest packet discarding problem due to the untimely update of FIB.

In the process of forwarding interest packets and data packets using the method of the present invention, when a producer joins or leaves the NDN network, it will send a request packet to the controller. When the FIB table search fails, the switch will send an input (packet in) request to the controller to determine the forwarding path of the interest packet. This solves the problem of communication failure caused by the lag in the update of the FIB and the failure of the producer to be immediately discovered by the NDN router when it moves.

By building a virtual-real network environment that combines programmable switches and virtual switches, the problem of difficulty in meeting scale and authenticity requirements when building a large-scale network environment is solved.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG1 is a diagram of a virtual-real network deployment based on SDN and NDN provided by the present invention.

FIG2 is a schematic block diagram of a virtual-real combined dynamic traffic scheduling method based on SDN and NDN provided by the present invention.

FIG3 is a flow chart of a virtual-real combined dynamic traffic scheduling method based on SDN and NDN provided by the present invention.

FIG4 is a schematic diagram of an SDN controller.

FIG5 is a schematic diagram of a virtual-real combined dynamic traffic scheduling device based on SDN and NDN provided by the present invention.

Detailed ways

In order to make the purpose, technical scheme and advantages of the present invention clearer, the present invention is further described in detail below in conjunction with specific embodiments and with reference to the accompanying drawings. It should be understood that these descriptions are only exemplary and are not intended to limit the scope of the present invention. In addition, in the following description, the description of well-known structures and technologies is omitted to avoid unnecessary confusion of the concept of the present invention.

Based on the problems existing in the prior art, the present invention proposes a virtual-real dynamic traffic scheduling method based on SDN and NDN, as shown in Figure 1. The network architecture based on it includes an SDN controller, several programmable switches, virtual switches, and several producer hosts and consumer hosts running the NDN protocol stack. Specifically, in an embodiment of the present invention, the programmable switch of the data plane uses a Tofino switch, the SDN controller uses an ONOS controller, and the virtual switch is built by a server running the Mininet simulation platform. Among them, the controller connects all programmable switches and virtual switches through a control link, and the programmable switch and the virtual switch are connected to the producer host and consumer host running the NDN protocol stack.

The virtual-real dynamic traffic scheduling method based on SDN and NDN includes several nodes; the nodes include a producer host running the NDN protocol stack, a consumer host running the NDN protocol stack, a server running the Mininet virtual network simulation platform, a P4 programmable switch, and an SDN controller. This method combines the original distributed NDN architecture with the SDN architecture, and with the help of the SDN "digital control separation" idea, the data plane only needs to complete the data packet forwarding, and the routing decision is handed over to the central controller.

As shown in FIG. 2 and FIG. 3 , the embodiment of the present invention proposes a virtual-real combined dynamic traffic scheduling method based on SDN and NDN, and the specific implementation steps are as follows:

Step 1: Build an NDN network based on the network topology: several virtual switches form a virtual network topology, several programmable switches form a physical network topology, connect several virtual network topologies with the physical network topology, and then communicate with the SDN controller through the P4runtime southbound interface; and randomly connect several producer hosts and consumer hosts running the NDN protocol stack to a programmable switch or a virtual switch.

The virtual switch builds a virtual network based on the customized network topology through the server running the Mininet simulation platform. The programmable switch establishes a connection with the server through the network cable. The server unbinds the network card from the host machine through the PCI network card transparent transmission method and directly connects to the virtual machine running the Mininet simulation platform. The producer and consumer hosts running the NDN protocol stack are connected to the programmable switch and the virtual switch through a direct network cable.

The SDN controller adds the virtual switch device, link, and device configuration information including the programmable switch and the Mininet simulation platform to the network view of the SDN controller by calling the Netconf protocol interface. Exemplarily, the SDN selects the ONOS controller, and the ONOS controller calls the REST API of the Netconf protocol interface. The REST API interface function consists of the controller's username and password, the controller's instance IP address, and the network configuration file. Exemplarily, the ONOS controller's username and password combination is configured as onos:rocks, the ONOS controller's instance IP address is configured as 192.168.56.111, and the network configuration file is set to /tmp/cfg.json in json format. The network configuration file adds the programmable switch and virtual switch, link, and switch device configuration information to the network view of the ONOS controller by specifying properties such as pipeconf and driver.

As shown in Figure 4, the controller includes a network discovery module, a host service module, an NDN management module, and a network configuration module. The network discovery module is responsible for maintaining the link view between switches, and the controller completes link discovery through the LLDP and BDDP protocols. The host service module is responsible for host discovery and determines the host location in the global view. The controller provides host discovery and positioning functions by monitoring ARP messages and DHCP messages. The NDN management module is responsible for maintaining the producer data table. The producer data table is responsible for recording the producer host information, including the host MAC address, the switch ID to which the host is directly connected, and the hash value of the data packet content name. The network configuration module is responsible for injecting attributes and configuration information into each network component, including device name, management address, device location, owner information, hardware and software versions, and device port type and name.

Step 2: When the producer host joins or leaves the NDN network, it sends a request data packet to the SDN controller, and the controller updates the producer data based on the request data packet.

After the producer host running the NDN protocol stack is connected to the NDN network, it actively sends a request data packet to the SDN controller. The request data packet includes the data packet content name that the producer host can provide services and the corresponding MAC address of the producer host. The format of the request data packet is: source MAC address, destination MAC address, packet type, and payload. Among them, the source MAC address is the MAC address of the producer host network card, the destination MAC address is the multicast address 01:00:5e:00:17:aa, the packet type is 0x8625, and the payload is the TLV information (type-length-value) of the request data packet. The programmable switch or virtual switch directly connected to the producer host running the NDN protocol stack receives the request data packet and inputs it (packet in) to the SDN controller. The NDN management module of the SDN controller obtains the switch ID directly connected to the producer host according to the producer host MAC address in the request data packet, and updates and stores the hash value of the producer host MAC address, the switch ID directly connected to the producer host, and the data packet content name in the producer data. In this example, producer data is stored in the form of a producer data table. The producer data table maintained by the NDN management module in the ONOS controller is shown in Table 1 below:

Table 1: Producer data sheet

主机MAC地址Host MAC address	主机直连的交换机IDID of the switch to which the host is directly connected	数据包内容名的哈希值Hash value of the packet content name
62:f6:67:88:de:21(第一生产者)62:f6:67:88:de:21(first producer)	device:p4-dev-2device:p4-dev-2	0x850c(/NDN1/SWP/PCA/DATA1)0x850c (/NDN1/SWP/PCA/DATA1)
62:f6:67:88:de:21(第一生产者)62:f6:67:88:de:21(first producer)	device:p4-dev-2device:p4-dev-2	0x6b29(/NDN1/SWP/PCB/VIDEO)0x6b29 (/NDN1/SWP/PCB/VIDEO)
62:f6:67:88:de:21(第一生产者)62:f6:67:88:de:21(first producer)	device:p4-dev-2device:p4-dev-2	0x65a3(/NDN1/SWP/SWV/DATA2)0x65a3 (/NDN1/SWP/SWV/DATA2)
4e:c5:57:69:47:fe(第二生产者)4e:c5:57:69:47:fe (second producer)	device:vir-dev-6device:vir-dev-6	0x12af(/NDN2/SWP/DATA3)0x12af(/NDN2/SWP/DATA3)
4e:c5:57:69:47:fe(第二生产者)4e:c5:57:69:47:fe (second producer)	device:vir-dev-6device:vir-dev-6	0x850c(/NDN1/SWP/PCA/DATA1)0x850c (/NDN1/SWP/PCA/DATA1)

When the producer host running the NDN protocol stack is disconnected from the NDN network or does not provide the corresponding service, it actively sends a request data packet to the SDN controller to tell the SDN controller to delete the corresponding table entry in the producer data table to update the producer data table. The format of the request data packet is: source MAC address, destination MAC address, packet type, and payload. Among them, the source MAC address is the MAC address of the producer host network card, the destination MAC address is the multicast address 01:00:5e:00:17:aa, the packet type is 0x8626, and the payload is the TLV information of the request data packet. The programmable switch or virtual switch directly connected to the producer host running the NDN protocol stack receives the request data packet and inputs it (packet in) to the ONOS controller. The ONOS controller searches for these two data in the producer data table according to the MAC address of the producer host network card and the hash value of the data packet content name. If found, the two data are deleted from the producer data table to update the producer data table.

Step 3. When forwarding a data packet between programmable switches or virtual switches, the programmable switch or virtual switch determines the type of the data packet; if the data packet is an IP data packet, it performs layer 2 or 3 forwarding (L2/L3 forwarding); if the data packet is an NDN interest packet, it is forwarded according to the content storage table (CS table, Content Store), request interest table (PIT table, Pending Interest Table) and forwarding information table (FIB table, Forwarding Information Base); if the data packet is an NDN data packet, it is forwarded according to the content storage table and request interest table.

The process of determining the type of a data packet by a programmable switch or virtual switch includes: when the packet type is 0x0806 or 0x0800, the data packet is an IP data packet, and the programmable switch or virtual switch performs layer 2/3 forwarding (L2/L3 forwarding). When the packet type is 0x8624, the programmable switch or virtual switch performs NDN packet parsing. If the packet type is 0x05, the data packet is forwarded as an NDN interest packet. If the packet type is 0x06, the data packet is forwarded as an NDN data packet, otherwise it is discarded.

Among them, the NDN packet includes the NDN interest packet and the NDN data packet. The NDN interest packet/NDN data packet enters the switch directly connected to it, and first obtains the content name of the interest packet/data packet according to the TLV nested information loop and outputs it.

The content name of the NDN interest packet/NDN data packet adopts a hierarchical structure. In this example, the format of the NDN interest packet/NDN data packet is set as: /NDN1/SWP/PCA/DATA1, which means that the content name of the NDN interest packet/NDN data packet has four segments, each of which is NDN1, SWP, PCA, and DATA1. The switch directly connected to the NDN interest packet/NDN data packet hashes the content name into a 32-bit value in sequence through a hash algorithm (HashAlgorithm.crc16). Specifically, when an NDN interest packet/NDN data packet arrives at the switch, the switch reads the content name of the NDN packet /NDN1/SWP/PCA/DATA1 in sequence according to the TLV nesting information, hashes NDN1 to 0xa36d, NDN1 and SWP to 0x12af, NDN1, SWP, and PCA to 0x2ce4, and NDN1, SWP, PCA, and DATA1 to 0x850c, and stores them in the switch as metadata for subsequent processing.

Specifically, the forwarding process when the data packets are IP data packets, NDN interest packets, and NDN data packets is described in detail below.

(A) If the data packet is an IP data packet, Layer 2/L3 forwarding (L2/L3 forwarding) is performed.

When the packet type is 0x0806 or 0x0800, the data packet is an IP data packet, and the programmable switch or virtual switch performs layer 2/3 forwarding (L2/L3 forwarding).

(B) If the data packet is an NDN interest packet, it is forwarded according to the content store table (CS table, Content Store), request interest table (PIT table, Pending Interest Table) and forwarding information table (FIB table, Forwarding Information Base).

The specific steps include:

According to the hash value of the interest packet content name, the matching record is searched from the content storage table (CS table). If the match with the content storage table is successful, it means that there is a data packet that satisfies the NDN interest packet. Then the NDN interest packet is encapsulated into an NDN format message, and the forwarding port set of the request interest table (PIT table) is searched according to the content name. The NDN format message is forwarded from the forwarding port and the interest packet is discarded.

If there is no matching record in the CS table, the hash value of the interest packet content name is used as the key to match the forwarding information table (FIB table). If the match is successful, the NDN interest packet is forwarded from the forwarding port corresponding to the forwarding information table entry, and the inbound port number is inserted into the request interest table (PIT table). The specific format is a key-value pair, that is, the hash value of the content name of the NDN interest packet is used as the key, and the inbound port set is used as the value.

For example, as shown in Figure 1, if the first consumer sends an NDN interest packet with a content name of /NDN1/SWP/PCA/DATA1, the NDN interest packet arrives at the s2 virtual switch from port 3, and the source MAC address in the NDN interest packet is the network card address 00:0c:29:1e:6f:d4 of the first consumer host, the destination MAC address is the multicast address 01:00:5e:00:17:aa, the type is 0x8624, and the payload is the TLV information of the NDN interest packet. At this time, the s2 virtual switch has a FIB table entry: the match domain is the hash value 0x850c of /NDN1/SWP/PCA/DATA1, and the action domain is forwarding from port 1. After the FIB table is matched successfully, the PIT table is queried. The key is the hash value 0x850c of /NDN1/SWP/PCA/DATA1. At this time, the value key is 00000100, indicating that there was an NDN interest packet sent from port 2 to the s2 virtual switch. The value is set to 00001100 through a shift operation, and the value is finally written back to the PIT table. After that, if a data packet with the content name /NDN1/SWP/PCA/DATA1 is received, the s2 virtual switch will forward the data packet from ports 2 and 3.

If the match to the FIB table fails, the outbound port number is set to the controller port number, and the NDN interest packet is forwarded to the SDN controller. After receiving the input (packet in) request, the SDN controller queries the information of the consumer host according to the source MAC address of the interest packet through the host service module, and then queries the access switch ID of the consumer host. The SDN controller queries the producer data table, finds the producer host MAC address corresponding to the content name of the NDN interest packet, and the switch ID set directly connected to the producer host, selects the shortest path from the switch ID set, sends the FIB matching flow table along the path, and sends the output (Packet out) message to the switch directly connected to the producer host, and sets the outbound port of the interest packet.

For example, if the first consumer sends an interest packet with the content name /NDN1/SWP/PCA/DATA1, which arrives at the s2 virtual switch from port 3, the source MAC is the first consumer's network card address 00:0c:29:1e:6f:d4, the destination MAC is the multicast address 01:00:5e:00:17:aa, the type is 0x8624, and the payload is the TLV information of the NDN interest packet. If the switch does not match the FIB table entry at this time, perform the following operations: set the egress port to the controller port number 255, the ingress port to the ingress port number 3 of the virtual switch s2, and set the packet in header field of the request packet to take effect. After receiving the input packet in request, the controller will query the source MAC address of the interest packet. According to the host service module, the access switch ID corresponding to the source MAC address is device:vir-dev-2. Then, according to the hash value 0x850c corresponding to the interest packet content name/NDN1/SWP/PCA/DATA1, the NDN management module of the ONOS controller finds the switch IDs of the host direct connection from the producer data table, which are device:p4-dev-2 and device:vir-dev-6 respectively. Finally, through the topology management module, the path cost from the switch device:vir-dev-2 to device:p4-dev-2 and device:vir-dev-6 is calculated, and the optimal path is selected as S2-S1-P4_1-P4_2. Next, the ONOS controller needs to send a packet out message to the ingress switch device:vir-dev-2, set the outbound port to 1, and then send the FIB flow table to the virtual switch S2, virtual switch S1, and programmable switch P4_1 in turn. Finally, according to the host service module, the port number of the switch P4_2 to which the first producer is connected is determined, and the FIB flow table is sent to the programmable switch P4_2. The FIB flow table sent by the ONOS controller is shown in Table 2.

Table 2: FIB flow table sent by ONOS controller

交换机IDSwitch ID	匹配域Matching Domains	动作域Action Domain
device:vir-dev-2device:vir-dev-2	meta.name_hash＝0x850cmeta.name_hash = 0x850c	egress_spec＝1egress_spec=1
device:vir-dev-1device:vir-dev-1	meta.name_hash＝0x850cmeta.name_hash = 0x850c	egress_spec＝1egress_spec=1
device:p4-dev-1device:p4-dev-1	meta.name_hash＝0x850cmeta.name_hash = 0x850c	egress_spec＝2egress_spec=2
device:p4-dev-2device:p4-dev-2	meta.name_hash＝0x850cmeta.name_hash = 0x850c	egress_spec＝3egress_spec=3

(C) If the data packet is an NDN data packet, it is forwarded according to the content store table (CS table, Content Store) and the request interest table (PIT table, Pending Interest Table).

When it is determined to be an NDN data packet, the switch will first query the PIT table to see if there is a content name corresponding to the NDN data packet. If the query is successful, the NDN data packet will be forwarded to all forwarding ports listed in the PIT table, the PIT entry will be deleted, and then the CS table will be searched according to the hash value 0x850c of the content name of the NDN data packet. If the corresponding table entry in the CS table is found, it means that the content library already has the corresponding data and no processing is performed. Otherwise, the corresponding key-value pair is inserted in the CS table and the data is cached in the content library. If the query to the PIT table fails, the NDN data packet is discarded.

Exemplarily, when the first producer receives a request packet with a content name of /NDN1/SWP/PCA/DATA1 from the first consumer, it will send a data packet to the first consumer. Among them, the source MAC address is the network card address 00:0c:29:ea:85:b2 of the first producer, the destination MAC address is the multicast address 01:00:5e:00:17:aa, the type is 0x8624, and the payload is the TLV information of the NDN data packet. When the programmable switch P4_2 receives the data packet, it first queries the content name of the NDN data packet according to the PIT table. If the corresponding table entry is found in the PIT table, where the key key is 0x850c and the value key value is 00000110, the data packet is forwarded from the

outbound ports

1 and 2 of the programmable switch P4_2 respectively. Then, the CS table is searched according to the content name hash value 0x850c. If the corresponding table entry of the CS table is found, where the key key is 0x850c and the value key value is 1, it means that the content library already has the corresponding data and no processing is performed. Otherwise, insert an entry with key 0x850c and value 1 into the CS table and cache the data in the content library. If no corresponding entry is found in the PIT table, discard the data packet.

Corresponding to the aforementioned embodiment of the virtual-real combined dynamic traffic scheduling method based on SDN and NDN, the present invention also provides an embodiment of the virtual-real combined dynamic traffic scheduling device based on SDN and NDN.

Referring to FIG. 5 , an embodiment of the present invention provides a virtual-real combined dynamic traffic scheduling device based on SDN and NDN, including one or more processors for implementing the virtual-real combined dynamic traffic scheduling method based on SDN and NDN in the above embodiment.

The embodiment of the virtual-real combination dynamic traffic scheduling device based on SDN and NDN of the present invention can be applied to any device with data processing capabilities, and the any device with data processing capabilities can be a device or apparatus such as a computer. The device embodiment can be implemented by software, or by hardware or a combination of software and hardware. Taking software implementation as an example, as a device in a logical sense, it is formed by the processor of any device with data processing capabilities in which it is located to read the corresponding computer program instructions in the non-volatile memory into the memory for execution. From the hardware level, as shown in Figure 5, it is a hardware structure diagram of any device with data processing capabilities where the virtual-real combination dynamic traffic scheduling device based on SDN and NDN of the present invention is located. In addition to the processor, memory, network interface, and non-volatile memory shown in Figure 5, any device with data processing capabilities where the device in the embodiment is located can also include other hardware according to the actual function of the device with data processing capabilities, which will not be described in detail.

The implementation process of the functions and effects of each unit in the above-mentioned device is specifically described in the implementation process of the corresponding steps in the above-mentioned method, and will not be repeated here.

For the device embodiment, since it basically corresponds to the method embodiment, the relevant parts can refer to the partial description of the method embodiment. The device embodiment described above is only illustrative, wherein the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the scheme of the present invention. A person of ordinary skill in the art can understand and implement it without paying creative labor.

An embodiment of the present invention further provides a computer-readable storage medium on which a program is stored. When the program is executed by a processor, the virtual-real combined dynamic traffic scheduling method based on SDN and NDN in the above embodiment is implemented.

The computer-readable storage medium may be an internal storage unit of any device with data processing capability described in any of the aforementioned embodiments, such as a hard disk or a memory. The computer-readable storage medium may also be any device with data processing capability, such as a plug-in hard disk, a smart media card (SMC), an SD card, a flash card, etc. equipped on the device. Furthermore, the computer-readable storage medium may also include both an internal storage unit of any device with data processing capability and an external storage device. The computer-readable storage medium is used to store the computer program and other programs and data required by any device with data processing capability, and may also be used to temporarily store data that has been output or is to be output.

Those skilled in the art will readily appreciate other embodiments of the present application after considering the description and practicing the contents disclosed herein. The present application is intended to cover any variations, uses or adaptations of the present application, which follow the general principles of the present application and include common knowledge or customary technical means in the art that are not disclosed in the present application. The description and examples are intended to be exemplary only.

It should be understood that the present application is not limited to the exact construction that has been described above and shown in the drawings, and that various modifications and changes may be made without departing from the scope thereof.

Claims

A virtual-real combined dynamic traffic scheduling method based on SDN and NDN, characterized in that the method comprises:

Build an NDN network based on network topology: virtual switches form a virtual network topology, programmable switches form a physical network topology, connect the virtual network topology with the physical network topology, and both communicate with the SDN controller; the producer host and consumer host running the NDN protocol stack are randomly connected to a programmable switch or a virtual switch;

When a producer host joins or leaves the NDN network, it sends a request packet to the SDN controller, and the SDN controller updates the producer data based on the request packet;

When forwarding data packets between programmable switches or virtual switches, the programmable switch or virtual switch determines the type of data packet; if the data packet is an IP data packet, it is forwarded at layer 2 or 3; if the data packet is an NDN interest packet, it is forwarded according to the content storage table, request interest table, and forwarding information table. When the forwarding information table fails to match, the switch sends a request to the controller, which decides the forwarding path; if the data packet is an NDN data packet, it is forwarded according to the content storage table and request interest table.
The virtual-real combined dynamic traffic scheduling method based on SDN and NDN according to claim 1 is characterized in that the process of building an NDN network based on the network topology also includes:

The SDN controller adds the link and device configuration information corresponding to the programmable switch and virtual switch to the network view of the SDN controller by calling the Netconf protocol interface; the SDN controller communicates with the programmable switch and virtual switch through the P4runtime southbound interface.
The virtual-real combined dynamic traffic scheduling method based on SDN and NDN according to claim 1 is characterized in that the SDN controller comprises:

The network discovery module is used to maintain the link view between programmable switches and virtual switches, and complete link discovery through the LLDP protocol and BDDP protocol;

The host service module is responsible for host discovery, determining the location of producer hosts and consumer hosts in the global view, and providing host discovery and positioning functions by monitoring ARP and DHCP messages;

NDN management module, responsible for maintaining producer data; producer data includes the MAC address of the producer host, the ID of the switch directly connected to the producer host, and the hash value of the data packet content name;

The network configuration module is responsible for injecting attributes and configuration information into each network component, including device name, management address, device location, owner information, hardware and software versions, and device port type and name.
The virtual-real combined dynamic traffic scheduling method based on SDN and NDN according to claim 1 is characterized in that when the producer host accesses the NDN network, it sends a request data packet to the controller, and the process in which the controller updates the producer data according to the request data packet includes:

After the producer host running the NDN protocol stack accesses the NDN network, it actively sends a request data packet to the SDN controller. After receiving the request data packet, the programmable switch or virtual switch directly connected to the producer host forwards the request data packet to the SDN controller. The SDN controller obtains the ID of the switch directly connected to the producer host based on the producer host MAC address in the request data packet, and updates the hash value of the producer host MAC address, the switch ID directly connected to the producer host, and the data packet content name and stores them in the producer data.
The virtual-real combined dynamic traffic scheduling method based on SDN and NDN according to claim 1 is characterized in that when the producer host leaves the NDN network, it sends a request data packet to the controller, and the process in which the controller updates the producer data according to the request data packet includes:

Before the producer host running the NDN protocol stack disconnects from the NDN network, it actively sends a request data packet to the SDN controller. After receiving the request data packet, the programmable switch or virtual switch directly connected to the producer host forwards the request data packet to the SDN controller. The SDN controller searches for the corresponding entry in the producer data table based on the MAC address of the producer host and the hash value of the data packet content name and deletes it, thereby updating the producer data.
According to the virtual-real combined dynamic traffic scheduling method based on SDN and NDN according to claim 4 or 5, it is characterized in that the format of the request data packet is: source MAC address, destination MAC address, packet type, and payload.
According to the virtual-real combination dynamic traffic scheduling method based on SDN and NDN according to claim 4 or 5, it is characterized in that the process of the programmable switch or virtual switch determining the type of the data packet includes:

When the packet type is 0x0806 or 0x0800, the data packet is an IP data packet. When the packet type is 0x8624, the programmable switch or virtual switch performs NDN packet parsing. If the packet type is 0x05, the data packet is an NDN interest packet. If the packet type is 0x06, the data packet is an NDN data packet.
According to the virtual-real dynamic traffic scheduling method based on SDN and NDN according to claim 7, it is characterized in that the process of the programmable switch or virtual switch determining the type of data packet also includes: hashing the content name of the NDN interest packet and/or the NDN data packet through a hash algorithm to obtain a hash value of the content name.
The virtual-real combined dynamic traffic scheduling method based on SDN and NDN according to claim 1 or 7 is characterized in that:

If the data packet is an NDN interest packet, the process of forwarding according to the content storage table, the request interest table, and the forwarding information table includes:

According to the hash value of the content name of the interest packet, a matching record is searched from the content storage table; if the match with the content storage table is successful, the NDN data packet is found from the content library of the switch according to the hash value of the content name, and the forwarding port set of the PIT table is searched according to the content name, and forwarded from the forwarding port, while the NDN interest packet is discarded;

If the match with the content storage table fails, the hash value of the interest packet content name is used as the key to match the forwarding information table. If the match succeeds, the NDN interest packet is forwarded from the corresponding forwarding port in the forwarding information table, and the inbound port number is inserted into the request interest table;

If the match with the forwarding information table is unsuccessful, the outbound port number is set to the controller port number, and then the NDN interest packet is forwarded to the SDN controller. After receiving the input request, the SDN controller queries the information of the consumer host according to the source MAC address of the NDN interest packet, and then queries the access switch ID of the consumer host; the SDN controller queries the producer data, finds the producer host MAC address corresponding to the content name of the NDN interest packet, and the switch ID set directly connected to the producer host, selects the shortest path from the switch ID set, sends the FIB matching flow table to the virtual switch or programmable switch along the path, and sends the output message to the switch directly connected to the producer host, and sets the outbound port of the NDN interest packet.
The virtual-real combined dynamic traffic scheduling method based on SDN and NDN according to claim 1 or 7 is characterized in that:

If the data packet is an NDN data packet, the process of forwarding according to the request interest table and the content storage table includes:

When it is determined to be an NDN data packet, the switch will first query the request interest table to see if there is a content name corresponding to the NDN data packet. If the query is successful, the NDN data packet will be forwarded to all forwarding ports listed in the request interest table, and the corresponding entry in the request interest table will be deleted. Then, the content storage table will be searched according to the hash value of the content name of the NDN data packet. If the corresponding table entry in the content storage table is found, no processing will be performed; otherwise, the corresponding key-value pair will be inserted into the content storage table, and the NDN data packet will be cached in the switch content library; if the query to the request interest table fails, the NDN data packet will be discarded.
A virtual-real combined dynamic traffic scheduling device based on SDN and NDN, characterized by comprising one or more processors for implementing the virtual-real combined dynamic traffic scheduling method based on SDN and NDN as described in any one of claims 1-10.
A computer-readable storage medium having a program stored thereon, characterized in that when the program is executed by a processor, it is used to implement the virtual-real combined dynamic traffic scheduling method based on SDN and NDN as described in any one of claims 1-10.