WO2023109200A1

WO2023109200A1 - Route advertisement method, communication system, and related device

Info

Publication number: WO2023109200A1
Application number: PCT/CN2022/117220
Authority: WO
Inventors: 罗贤龙; 陈春晖; 陈巍
Original assignee: 华为技术有限公司
Priority date: 2021-12-13
Filing date: 2022-09-06
Publication date: 2023-06-22
Also published as: CN116264562A

Abstract

Disclosed in embodiments of the present application are a route advertisement method, a communication system, and a related device, used for realizing cross-domain advertisement of route information. The method of the embodiments of the present application comprises: a distribution SDN controller obtains first route information and first service attribute information from a source-side SDN controller, the first route information comprising address information of a cloud subnet corresponding to a first cloud edge device, and the first service attribute information indicating that the first cloud edge device and a first local edge device are located in different domains in a target service private network; the distribution SDN controller advertises, according to the first service attribute information, the first route information to a first destination-side SDN controller corresponding to the first local edge device, so that the first local edge device stores the first route information.

Description

Route notification method, communication system and related equipment

This application claims priority to a Chinese patent application filed with the State Intellectual Property Office of China on December 13, 2021, with application number 202111517856.2, and titled "Route Advertisement Method, Communication System, and Related Equipment," the entire contents of which are hereby incorporated by reference In this application.

technical field

The embodiments of the present application relate to the communication field, and in particular, to a route notification method, a communication system, and related equipment.

Background technique

With the rapid development of cloud computing, all walks of life gradually move their marketing systems, support systems, and core systems to the cloud, and the importance of cloud-connected networks continues to increase. The optical transport network (OTN) has the advantages of stable low latency, large bandwidth, high reliability, security and hard isolation, and is a high-quality way to enter the cloud.

In the existing routing notification method, the software defined routing (software defined rout, SDR) controller receives the local subnet routing information or cloud subnet routing information reported by the edge OTN device, based on the customer-related edge node information, sends the local Publish the routing information of the subnet to the OTN edge device of the cloud subnet, or publish the routing information of the cloud subnet to the OTN edge device of the local subnet, where the OTN edge device of the cloud subnet and the OTN edge device of the local subnet include in the same OTN domain.

In this method, the OTN edge devices of the cloud subnet and the OTN edge devices of the local subnet are required to be included in the same OTN domain, that is, the routing information advertised by the SDR controller is the routing information of the same OTN domain , the application scenarios are limited, and route notification in cross-domain scenarios cannot be realized.

Contents of the invention

The embodiment of the present application provides a route notification method, a communication system and related equipment, and a hierarchical software-defined network (software network defined, SDN) controller is set, and the service attribute information indicates that the cloud edge device and the local edge device are located in the target service private network In different domains, the SDN controller corresponding to the cloud subnet will report the routing information and service attribute information to the distribution SDN controller, so that the distribution SDN controller will notify the routing information to the corresponding SDN of the local edge device according to the service attribute information. The controller realizes the cross-domain notification of routing information.

The first aspect of the embodiment of the present application provides a route notification method, the method is applied to the distribution SDN controller, the method includes:

With the development of cloud computing, enterprises will deploy access points (that is, edge devices) in different domains, and connect local subnets or cloud subnets through edge devices to form the enterprise's target business private network. That is to say, in addition to the access point, a user's target service private network also includes a cloud subnet and/or a local subnet. According to user needs, different strategies can be set to realize communication between different access points, so as to achieve data into the cloud, inter-cloud interconnection and other effects. Wherein, the cloud subnet may also be called a virtual private cloud (virtual private cloud, VPC) network. The distribution SDN controller can implement routing information notification between different access points, and achieve the above effects through routing notification.

The distribution SDR controller is connected to the source-side SDN controller and the first destination-side SDN controller, and can obtain the first routing information and the first service attribute information from the source-side SDN controller. The source-side SDN controller is connected to the first cloud edge device, and obtains the first routing information and the first service attribute information through the first cloud edge device. The first routing information includes address information of the cloud subnet corresponding to the first cloud edge device, and the first service attribute information indicates that the first cloud edge device and the first local edge device are located in different domains in the target service private network. Wherein, the address information of the cloud subnet corresponding to the first cloud edge device includes address information of at least one virtual machine on the cloud subnet, and the address information is expressed as an IP address or a media access control address (MAC) address , not limited here. The distribution SDN controller sends the first route information to the first destination SDN controller corresponding to the first local edge device according to the first service attribute information, so that the first destination SDN controller sends the first route to the first local edge device Information, the first local edge device stores the first routing information, so as to implement cross-domain routing information notification.

It can be seen from the above technical solutions that the embodiments of the present application have the following advantages:

When the first service attribute information obtained by the distribution SDN controller indicates that the first cloud edge device and the first local edge device are located in different domains in the target service private network, the distribution SDN controller can send the first local The first destination-side SDN controller corresponding to the edge device notifies the first routing information, and the first routing information includes address information of the cloud subnet corresponding to the source-side SDN, thereby implementing cross-domain notification of routing information. At the same time, the address information of the cloud subnet is notified to the cross-domain local edge device, which provides technical support for realizing the cloud-entry service in the target service private network, and improves the practicability of the technical solution of this application. Among them, the cloud-entry service refers to a service that connects the user's local subnet and the cloud subnet.

In some optional embodiments of the first aspect, communication between cross-domain cloud edge devices may also be deployed to provide support for cross-domain inter-cloud interconnection. The first service attribute information sent by the source-side SDN controller may also indicate that the first cloud edge device and the second cloud edge device are located in different domains in the target service private network, that is, the target service private network of the user also includes the second Two cloud edge devices. The distribution SDN controller can send the first routing information to the second destination SDN controller corresponding to the second cloud edge device according to the first service attribute information, so that the second destination SDN controller sends the first routing information to the second cloud edge device. For routing information, the second cloud edge device stores the first routing information.

In the embodiment of the present application, the distribution SDN controller is not only capable of notifying the first destination-side SDN controller corresponding to the cross-domain first local edge device of the first routing information of the cloud subnet corresponding to the first cloud edge device, It can also be notified to the second destination SDN controller corresponding to the cross-domain second cloud edge device, which provides a basis for inter-cloud interconnection and further enriches the application scenarios of the technical solutions of the embodiments of the present application.

In some optional embodiments of the first aspect, the distribution SDN controller may also notify the cross-domain cloud edge device of the routing information of the sub-subnet corresponding to the local edge device. The distribution SDN controller may also obtain the second routing information and the second service attribute information from the first destination SDN controller. The second routing information includes address information of the local subnet corresponding to the first local edge device, the address information of the local subnet includes address information of at least one host in the local subnet, and the address information is expressed as an IP address or a MAC address, specifically There is no limit here. The second service attribute information indicates that the first local edge device and the first cloud edge device are located in different domains in the target service private network. The distribution SDN controller passes the second routing information to the source-side SDN controller corresponding to the first cloud edge device according to the second service attribute information, so that the source-side SDN controller sends the second routing information to the first cloud edge device, and the first The cloud edge device stores the second routing information.

In the embodiment of the present application, the destination-side SDN controller can also notify the source-side SDN controller corresponding to the cross-domain cloud edge device of the first local subnet address information, which further enriches the application scenarios of the technical solution of the embodiment of the present application.

In some optional embodiments of the first aspect, communication between local edge devices across domains may also be deployed to provide support for interconnection between local subnets across domains. The second service attribute information sent by the first destination-side SDN controller may also indicate that the first local edge device and the second local edge device are located in different domains in the target service private network. A second local edge device is included. The distribution SDN controller can send the second routing information to the third destination SDN controller corresponding to the second local edge device according to the second service attribute information, so that the third destination SDN controller sends the second routing information to the second local edge device. For routing information, the second local edge device stores the second routing information.

In this embodiment of the application, the distribution SDN controller can notify the source-side SDN controller corresponding to the cross-domain first cloud edge device of the second routing information corresponding to the first local subnet, and can also notify the cross-domain The third destination-side SDN controller corresponding to the second local edge device provides a basis for realizing the interconnection between local subnets, and improves the flexibility of the technical solution of the present application.

In some optional embodiments of the first aspect, the distribution SDN controller may be based on an SDN northbound interface protocol, or a path computation element communication protocol (path computation element communication protocol, PCEP), or a transmission control protocol (transmission control protocol, TCP ), to obtain transmission routing information and service attribute information from other SDN controllers. Among them, the northbound interface protocol of SDN can be determined according to the network type of the distribution SDN controller and other SDN controllers. There are many situations, such as the NET-CONF protocol or the REST protocol of HTTP. In addition, it can also be other Type of northbound interface protocol, which is not limited here. Exemplarily, the distribution SDN controller may obtain the first routing information and the first service attribute information from the source-side SDN controller based on the PCEP protocol.

In some optional embodiments of the first aspect, the distribution SDN controller may also send routing information to other SDN controllers based on the northbound interface protocol of the SDN, or the PCEP protocol, or the TCP protocol. Exemplarily, the distribution SDN controller may notify the source-side SDN controller of the first routing information based on the PCEP protocol.

In the embodiment of the present application, there are many types of transmission protocols between the SDN controllers, which can be selected according to the needs of practical applications, which further improves the flexibility of the technical solution.

In some optional embodiments of the first aspect, different domains in the target service private network include different geographical regions, or different technical domains, where the technical domain includes an access domain and a transmission domain. Different technical domains include the case where one edge device is in the access domain and one edge device is in the transport domain; it also includes the situation where one edge device is in technical domain A and the other edge device is in technical domain B; it also includes the case where an edge device is in The case of transport domain A and another edge device in transport domain B is not limited here.

In the embodiment of the present application, multiple types of cross-domain routing information announcements can be realized, which further enriches the application scenarios of the technical solution of the present application.

In some optional embodiments of the first aspect, the types of each SDN controller may include a software defined routing (software defined rout, SDR) controller. The types of the various SDN controllers may be the same or different, which is not specifically limited here. Wherein, each SDN controller includes a distribution SDN controller, a source-side SDN controller, a first destination-side SDN controller, a second destination-side SDN controller, and a third SDN destination-side controller.

In some optional embodiments of the first aspect, the third destination-side SDN controller and the source-side SDN controller may be different SDN controllers, or may be the same SDN controller, that is, the second local edge The device and the first cloud edge device may be located in different domains of the target private network service, or may be located in the same domain of the target service private network, which is not specifically limited here.

In some optional embodiments of the first aspect, the first destination-side SDN controller and the second destination-side SDN controller may be different SDN controllers, or may be the same SDN controller, that is, the first The local edge device and the second cloud edge device may be located in different domains of the target private network service, or may be located in the same domain of the target service private network, which is not specifically limited here.

In some optional embodiments of the first aspect, the second destination SDN controller and the third destination SDN controller may be different SDN controllers, or may be the same SDN controller, that is, the second The cloud edge device and the second local edge device may be located in different domains of the target private network service, or may be located in the same domain of the target service private network, which is not specifically limited here.

The second aspect of the embodiment of the present application provides a route notification method, the method is applied to the source-side SDN controller, and the source-side SDN controller is connected to the first cloud edge device and the distribution SDN controller, and the method includes:

The first cloud edge device will send the first routing information and the first service attribute information to the source-side SDN controller, that is, the source-side SDN controller will obtain the first routing information and the first Business attribute information. Wherein, the first routing information includes address information of the cloud subnet corresponding to the first cloud edge device, that is, address information of the first cloud subnet. The address information of the first cloud subnet includes address information of at least one virtual machine on the first cloud subnet, and the address information is expressed as an IP address or a MAC address, which is not specifically limited here. The first service attribute information can reflect the access point information of the target service private network, indicating that the first cloud edge device and the first local edge device are located in different domains in the target service private network. Since the first service attribute information indicates a cross-domain access point, the source-side SDN controller sends the first routing information and the first service attribute information to the distribution SDN controller, so that the distribution controller performs cross-domain route advertisement. Specifically, the distribution SDN controller will send the first routing information and the first service attribute information to the first destination SDN controller corresponding to the first local edge device according to the first service attribute information, so that the first destination SDN control The first local edge device connected to the router stores the first routing information.

In this embodiment of the application, when the source-side SDN controller receives service attribute information indicating that the first cloud edge device corresponding to the source-side SDN controller is located in a different domain from the other edge devices in the target service private network, the service The attribute information and routing information are sent to the distribution SDN controller, so that the distribution SDN controller performs cross-domain routing notification according to the service attribute information. When the other edge device is the first local edge device, the address information of the first cloud subnet is notified to the cross-domain first local edge device through the distribution SDN controller, so as to provide cloud access services in the target service private network. Provided technical support and improved the practicability of the technical solution of the present application.

In some optional embodiments of the second aspect, the source-side SDN controller may further connect to the second local edge device, so as to obtain the second routing information and the second service attribute information from the second local edge device. The second routing information includes address information of the local subnet corresponding to the second local device, that is, address information of the second local subnet. Specifically, the address information of the second local subnet includes address information of at least one host on the second local subnet, and the address information is expressed as an IP address or a MAC address, which is not specifically limited here. The second service attribute information indicates that the second local edge device and the second cloud edge device are located in different domains in the target service private network. Since the second service attribute information indicates a cross-domain access point, the source-side SDN controller will send the second routing information and the second service attribute information to the distribution SDN controller, so that the distribution controller performs cross-domain route notification. Specifically, the distribution SDN controller will send the second routing information and the second service attribute information to the second destination SDN controller corresponding to the second cloud edge device according to the second service attribute information, so that the second destination SDN control The second cloud edge device connected to the router stores the second routing information.

In this embodiment of the application, in addition to connecting to the first cloud edge device, the source-side SDN controller can also connect to the second local edge device, and send the second routing information to the distribution SDN controller, so that the distribution SDN controller sends the second routing information to the distribution SDN controller. The address information of the second local subnet is notified to the cross-domain second cloud edge device, which enriches the flexibility of the technical solution of the present application.

In some optional embodiments of the second aspect, the source-side SDN controller can also obtain the routing information and service attribute information sent by the distribution SDN controller, and send the route to the relevant local edge device or cloud edge device according to the service attribute information information. Specifically, the source-side SDN controller can obtain third routing information and third service attribute information from the distribution SDN controller, where the third routing information includes the address information of the cloud subnet corresponding to the second cloud edge device, that is, Address information of the second cloud subnet. The third service attribute information indicates that the second cloud edge device and the first cloud edge device are located in different domains in the target service private network. Therefore, the source-side SDN controls to send the third routing information to the first cloud edge device according to the third service attribute information, so that the first cloud edge device stores the third routing information.

In the embodiment of this application, the source-side SDN controller can obtain the address information of the second cloud subnet in other domains, that is, the third routing information, and send the third routing information to the first cloud edge according to the third service attribute information The device enables the first cloud edge to store the third routing information, which provides a basis for cross-domain inter-cloud interconnection, further enriches the application scenarios of the technical solution of this application, and improves the flexibility of the technical solution.

In some optional embodiments of the second aspect, the source-side SDN controller acquires fourth routing information and fourth service attribute information from the distribution SDN controller, where the fourth routing information includes the local sub-network address corresponding to the first local edge device. The address information of the network, that is, the address information of the first local subnet. The address information of the first local subnet includes address information of at least one host on the first local subnet, and the address information is expressed as an IP address or a MAC address, which is not specifically limited here. The fourth service attribute indicates that the first local edge device and the second local edge device are located in different domains in the target service private network. The source-side SDN controller sends fourth routing information to the second local edge device according to the fourth service attribute information, so that the second local edge device stores the fourth routing information.

In the embodiment of the present application, the source-side SDN controller can obtain the address information of the first local subnet in other domains, that is, the fourth routing information, and send the fourth routing information to the second local edge according to the fourth service attribute information The device enables the second local edge device to store the fourth routing information, which provides a basis for interconnection between cross-domain local subnets, and improves the flexibility of the technical solution of the present application.

In some optional embodiments of the second aspect, the source-side SDN controller can obtain routing information and service attributes from the local edge device or cloud edge device based on the SDN southbound interface protocol, or the PCEP protocol, or the TCP protocol information. Among them, the southbound interface protocol of SDN can be determined according to the network type of the source-side SDN controller and the cloud edge device/local edge device connected to it. There are many situations, such as the NET-CONF protocol or the REST protocol of HTTP. In addition, other types of southbound interface protocols may also be used, which are not specifically limited here. Exemplarily, the source-side SDN controller may obtain the first routing information and the first service attribute information from the first cloud edge device based on the PCEP protocol.

In some optional embodiments of the second aspect, the source-side SDN controller may also send routing information and service attribute information to the distribution SDN controller based on the SDN northbound interface protocol, or the PCEP protocol, or the TCP protocol. Exemplarily, the source-side SDN controller may send the first routing information and the first service attribute information to the distribution SDN controller based on the PCEP protocol.

In the embodiment of this application, there are many types of transmission protocols between the source-side SDN controller and the cloud edge device/local edge device, and each SDN controller, which can be selected according to the needs of actual applications, further improving the flexibility of the technical solution sex.

In some optional embodiments of the second aspect, different domains in the target service private network include different geographical areas, or different technical domains, where the technical domain includes an access domain and a transmission domain. Different technical domains include the case where one edge device is in the access domain and one edge device is in the transport domain; it also includes the situation where one edge device is in technical domain A and the other edge device is in technical domain B; it also includes the case where an edge device is in The case of transport domain A and another edge device in transport domain B is not limited here.

In some optional embodiments of the second aspect, the types of each SDN controller may include an SDR controller. The type of the source-side SDN controller and the type of the distribution SDN controller may be the same or different, which are not limited here.

In some optional embodiments of the second aspect, the first destination-side SDN controller and the second destination-side SDN controller may be the same SDN controller or different SDN controllers, that is, the first The local edge device and the second cloud edge device may be located in the same domain of the target service private network, or may be located in different domains of the target service private network, which is not limited here.

The third aspect of the embodiment of the present application provides a communication system, including distribution SDN control, source-side SDN controller and first destination-side SDN controller, source-side SDN connection distribution SDN control and first cloud edge device, the first purpose The side SDN controller is connected to the distribution SDN controller and the first local edge device.

The source-side SDN controller is configured to obtain the first routing information and the first service attribute information from the first cloud edge device. Wherein, the first routing information includes address information of the first cloud subnet corresponding to the first cloud edge device, and the first service attribute information indicates that the first cloud edge device and the first local edge device are located in different domains in the target service private network; Send the first routing information and the first service attribute information to the distribution SDN controller. Distributing the SDN controller, configured to acquire the first routing information and the first service attribute information, and notify the first destination SDN controller corresponding to the first local edge device of the first routing information according to the first service attribute information; The destination-side SDN controller sends the first service attribute information. The second destination-side SDN controller is configured to receive the first routing information and the first service attribute information; and send the first routing information to the first local edge device according to the first service attribute information.

In some optional embodiments of the third aspect, the communication system further includes a second destination-side SDN controller, and the second destination-side SDN controller is connected to the distribution SDN controller and the second cloud edge device. The first service attribute information is really that the first cloud edge device and the second cloud edge device are located in different domains in the target service private network. The distribution SDN controller is further configured to notify the second destination SDN controller corresponding to the second cloud edge device of the first routing information according to the first service attribute information; send the first service attribute information to the second destination SDN controller . The second destination-side SDN controller is configured to receive the first routing information and the first service attribute information, and send the second routing information to the second cloud edge device according to the first service attribute information.

In some optional embodiments of the third aspect, the first destination-side SDN controller is further configured to acquire second routing information and second service attribute information from the first local edge device, where the second routing information includes the first The address information of the local subnet corresponding to the local edge device, the second service attribute information indicates that the first local edge device and the first cloud edge device are located in different domains in the target service private network; send the second routing information and The second service attribute information. The distribution SDN controller is also used to obtain the second routing information and the second service attribute information; according to the second service attribute information, send the second routing information to the source-side SDN controller corresponding to the first cloud edge device; send the source-side SDN The controller sends the second service attribute information. The source-side SDN controller is further configured to receive second routing information and second service attribute information; and send the second routing information to the first cloud edge device according to the second service attribute information.

In some optional embodiments of the third aspect, the communication system further includes a third destination-side SDN controller, and the third destination-side connection distribution SDN controller and the second local edge device; the second service attribute information also indicates that the first local The edge device and the second local edge device are located in different domains in the target service private network. The distribution SDN controller is further configured to notify the third destination SDN controller corresponding to the second local edge device of the third route information according to the second service attribute information; and send the second service attribute information to the third destination SDN control. The third destination-side SDN controller is configured to receive the second routing information and the second service attribute information; and send the second routing information to the second local edge device according to the second service attribute information.

In some optional embodiments of the third aspect, routing information and service attribute information may be transmitted (communicated) between the SDN controllers based on the SDN northbound interface protocol, or the PCEP protocol, or the TCP protocol. Exemplarily, the distribution SDN controller may send the first routing information and the first service attribute information to the distribution SDN controller based on the PCEP protocol. Each SDN controller includes a source-side SDN controller, a first destination-side SDN controller, a second destination-side SDN controller, and a third destination-side SDN controller.

In some optional embodiments of the third aspect, the SDN controller connected to the local edge device or the cloud edge device can obtain information from the local edge device or the cloud based on the SDN southbound interface protocol, or the PCEP protocol, or the TCP protocol. Routing information and service attribute information of edge devices. Exemplarily, the source-side SDN controller may obtain the first routing information and the first service attribute information from the first cloud edge device based on the PCEP protocol.

In some optional embodiments of the third aspect, different domains in the target service private network include different geographical areas, or different technical domains, where the technical domain includes an access domain and a transmission domain. Different technical domains include the case where one edge device is in the access domain and one edge device is in the transport domain; it also includes the situation where one edge device is in technical domain A and the other edge device is in technical domain B; it also includes the case where an edge device is in The case of transport domain A and another edge device in transport domain B is not limited here.

In some optional embodiments of the third aspect, the types of each SDN controller may include an SDR controller. The types of the various SDN controllers may be the same or different, which is not specifically limited here. Each SDN controller includes a distribution SDN controller, a source-side SDN controller, a first destination-side SDN controller, a second SDN controller, and a third SDN controller.

In some optional embodiments of the third aspect, the third destination-side SDN controller and the source-side SDN controller may be different SDN controllers, or may be the same SDN controller, that is, the second local edge The device and the first cloud edge device may be located in different domains of the target private network service, or may be located in the same domain of the target service private network, which is not specifically limited here.

In some optional embodiments of the third aspect, the first destination-side SDN controller and the second destination-side SDN controller may be different SDN controllers, or may be the same SDN controller, that is, the first The local edge device and the second cloud edge device may be located in different domains of the target private network service, or may be located in the same domain of the target service private network, which is not specifically limited here.

In some optional embodiments of the third aspect, the second destination SDN controller and the third destination SDN controller may be different SDN controllers, or may be the same SDN controller, that is, the second The cloud edge device and the second local edge device may be located in different domains of the target private network service, or may be located in the same domain of the target service private network, which is not specifically limited here.

The beneficial effect of the third aspect of the embodiment of the present application is similar to that of the first aspect and the second aspect. For details, refer to the description of the first aspect and the second aspect, and details are not repeated here.

The fourth aspect of the embodiment of the present application provides a distribution SDN controller, including:

An acquisition unit, configured to acquire first routing information and first service attribute information from the source-side SDN controller, where the source-side SDN controller is connected to the first cloud edge device, and the first routing information includes the first cloud edge device corresponding The address information of the cloud subnet, and the first service attribute information indicate that the first cloud edge device and the first local edge device are located in different domains in the target service private network.

The sending unit is configured to notify the first destination SDN controller corresponding to the first local edge device of the first routing information according to the first service attribute information, so that the first local edge device stores the first routing information.

The distribution SDN controller is used to implement the method of the aforementioned first aspect, and the beneficial effect shown in this aspect is similar to that of the first aspect, and will not be repeated here.

The fifth aspect of the embodiment of the present application provides a source-side SDN controller, the source-side SDN controller is connected to the first cloud edge device and the distribution SDN controller, and the source-side SDN controller includes:

An acquisition unit, configured to acquire first routing information and first service attribute information from the first cloud edge device, where the first routing information includes address information of the cloud subnet corresponding to the first cloud edge device, and the first service attribute information indicates The first cloud edge device and the first local edge device are located in different domains in the target service private network;

Sending the first routing information and the first service attribute information to the distribution SDN controller, so that the distribution SDN controller notifies the first destination SDN controller corresponding to the first local edge device of the first routing information according to the first service attribute information.

The source-side SDN controller is used to implement the method in the aforementioned second aspect, and the beneficial effects shown in this aspect are similar to those in the second aspect, and will not be repeated here.

The sixth aspect of the embodiment of the present application provides a computer device, including a processor, a memory and a communication interface, the processor, the memory and the communication interface are connected, and the processor is used to execute the method of the first aspect or the second aspect.

The seventh aspect of the embodiments of the present application provides a computer-readable storage medium, in which a program is stored, and when the computer executes the program, the method of the first aspect or the second aspect is executed.

The eighth aspect of the embodiment of the present application provides a computer program product, which is characterized in that, when the computer program product is executed on a computer, the computer executes the method of the first aspect or the second aspect.

The beneficial effects shown in the sixth aspect to the eighth aspect are similar to those in the first aspect or the second aspect, and will not be repeated here.

Description of drawings

FIG. 1 is a schematic structural diagram of a communication system provided by an embodiment of the present application;

FIG. 2 is a schematic flow diagram of a route notification method provided in an embodiment of the present application;

FIG. 3 is a schematic diagram of a scenario of a route notification method provided in an embodiment of the present application;

FIG. 4 is another schematic flowchart of the route notification method provided by the embodiment of the present application;

FIG. 5 is a schematic diagram of another scenario of the route notification method provided by the embodiment of the present application;

FIG. 6 is a schematic diagram of another scenario of the route notification method provided by the embodiment of the present application;

FIG. 7 is a schematic diagram of another scenario of the route notification method provided by the embodiment of the present application;

FIG. 8 is a schematic structural diagram of a distribution SDN controller provided by an embodiment of the present application;

FIG. 9 is a schematic structural diagram of a source-side SDN controller provided in an embodiment of the present application;

FIG. 10 is a schematic structural diagram of a computer device provided by an embodiment of the present application.

Detailed ways

The embodiment of the present application provides a route notification method, a communication system and related equipment. A hierarchical SDN controller is set. When the service attribute information indicates that the cloud edge device and the local edge device are located in different domains in the target service private network, Yunzi The SDN controller corresponding to the network will report the routing information and service attribute information to the distribution SDN controller, so that the distribution SDN controller will notify the routing information to the SDN controller corresponding to the local edge device according to the service attribute information, thereby realizing the routing information cross domain notification.

Embodiments of the present application are described below in conjunction with the accompanying drawings. Those of ordinary skill in the art know that, with the development of technology and the emergence of new scenarios, the technical solutions provided in the embodiments of the present application are also applicable to similar technical problems.

The terms "first", "second" and the like in the specification and claims of the present application and the above drawings are used to distinguish similar objects, and are not necessarily used to describe a specific sequence or sequence. It should be understood that the terms used in this way can be interchanged under appropriate circumstances, and this is merely a description of the manner in which objects with the same attribute are described in the embodiments of the present application. Furthermore, the terms "comprising" and "having", and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, product, or apparatus comprising a series of elements is not necessarily limited to those elements, but may include without other elements explicitly listed or inherent to the process, method, product, or apparatus. In addition, "at least one" means one or more, and "plurality" means two or more. "And/or" describes the association relationship of associated objects, indicating that there can be three types of relationships, for example, A and/or B, which can mean: A exists alone, A and B exist at the same time, and B exists alone, where A, B can be singular or plural. The character "/" generally indicates that the contextual objects are an "or" relationship. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one item (piece) of a, b, or c can represent: a, b, c, a-b, a-c, b-c, or a-b-c, where a, b, c can be single or multiple .

Please refer to FIG. 1 . FIG. 1 is a schematic structural diagram of a communication system provided by an embodiment of the present application. In the embodiment shown in Figure 1, the user's target service private network includes multiple access points, and these access points are connected to the user's cloud subnet or local subnet through a gateway, and are used to transmit various data packets . As shown in Figure 1, users have deployed access points in Domain 1, Domain 2, and Domain 3. The access points can be edge devices, and the edge devices include cloud edge devices or local edge devices. In domain 1, the local edge device 1021 establishes a communication connection with the local subnet 1023 through the local gateway 1022; in domain 2, the cloud edge device 1031 establishes a communication connection with the cloud subnet 1033 through the cloud gateway 1032; in domain 3, the local The edge device 104 establishes a communication connection with the local subnet 1043 through the local gateway 1042 , and the cloud edge device 1044 establishes a communication connection with the cloud subnet 1046 through the cloud gateway 1045 .

In order to ensure normal communication between each access point, each access point will send its corresponding local subnet routing information or cloud subnet routing information to the corresponding SDN controller in the domain according to the user's needs , the SDN controller determines the way of routing notification according to user requirements. In the embodiment shown in FIG. 1 , the SDN controller 102 corresponds to domain 1 , the SDN controller 103 corresponds to domain 2 , and the SDN controller 104 corresponds to domain 3 .

Assume that the user's requirement is to notify the local edge device 1021 corresponding to the local subnet 1023 and the local edge device 1041 corresponding to the local subnet 1043 of the routing information of the cloud subnet 1033, so as to realize the normal development of the cloud service. Then, the cloud edge device 1031 can learn the routing information of the cloud subnet 1033 and the service attribute information, which indicates that the cloud edge device 1031, the local edge device 1021 and the local edge device 1041 are located in different domains in the target service private network . The cloud edge device 1031 sends the routing information and service attribute information of the cloud subnet 1033 to the SDN controller 103 corresponding to domain 2 . The SDN controller 103 determines that the service is a cross-domain service according to the service attribute information, and sends the routing information and service attribute information of the cloud subnet 1033 to the distribution SDN controller 101 . The distribution SDN controller 101 sends the routing information of the cloud subnet 1033 to the SDN controller 102 corresponding to the local edge device 1021 and the SDN controller 104 corresponding to the local edge device 1041 according to the service attribute information. The local edge device 1021 and the local edge device 1041 will store the routing information of the cloud subnet 1033 locally to establish a routing table. During message transmission, if the local edge device 1021 obtains a message whose destination address contains routing information in the cloud subnet 1033, it can determine the transmission link of the message according to the routing table, so that the cloud service can proceed normally.

It should be noted that the above content is an example of the cloud access service. In actual applications, users may have other needs. The embodiment of this application can perform route notification between any two access points. , including not only cross-domain routing notifications, but also intra-domain routing notifications, which are not limited here. If the routing within the domain passes, it can be completed by the SDN controller corresponding to the domain, without the participation of the distribution SDN controller.

It can be seen from Figure 1 that in the embodiment of the present application, a hierarchical SDN controller is set, and when the service attribute information indicates that multiple edge devices are located in different domains in the target service private network, it is necessary to notify the cloud subnet or the local subnet of the routing information. The SDN controller corresponding to the network will report the routing information and service attribute information to the distribution SDN controller, so that the distribution SDN controller will notify the routing information to the SDN controllers corresponding to other edge devices indicated by the service attribute information according to the service attribute information. In this way, cross-domain notification of routing information is realized.

It should be noted that FIG. 1 is only an example of a communication system. In practical applications, more or fewer access points may be included in the user's target service private network, and these access points may also be included in more In more or fewer domains, the type and quantity of edge devices included in each domain may also be different from those in FIG. 1 , which are not specifically limited here.

Next, with the distribution SDN controller as the execution subject, the method of routing notification provided by the embodiment of the present application will be described, please refer to Figure 2 and Figure 3, Figure 2 is a schematic flow chart of the routing notification method provided by the embodiment of the present application, Fig. 3 is a schematic diagram of a scene provided by the embodiment of this application. As shown in Figure 2, the route notification method provided by the embodiment of the present application includes the following steps:

201. Obtain the first routing information and first service attribute information from the source-side SDN controller, the first routing information includes the address information of the cloud subnet corresponding to the first cloud edge device, and the first service attribute information indicates the first cloud The edge device and the first local edge device are located in different domains in the target service private network.

For clarity of description, the scenario shown in FIG. 3 is taken as an example to describe the route advertisement method provided in the embodiment of the present application. As shown in FIG. 3 , the source-side SDN controller is connected to the distribution SDN controller and the first cloud edge device. Through protocol learning or static configuration, the first cloud edge device learns the first routing information, the first routing information includes the address information of the first cloud subnet, and the address information of the first cloud subnet includes at least Address information of a virtual machine, such address information is expressed as an IP address or a MAC address, which is not specifically limited here. Wherein, the protocol used to learn the first routing information includes extended PCEP protocol, border gateway protocol (border gateway protocol, BGP), etc., in addition to other protocols that can learn routing information, such as address resolution protocol (address resolution protocol, ARP), the details are not limited here. The first cloud edge device can also obtain the first service attribute information. The first service attribute information indicates that the first cloud edge device and the first local edge device are located in different domains in the target service private network, which means that the first routing information needs to be Perform cross-domain route advertisement, and advertise to the first local edge device across domains. The first cloud edge device sends the first routing information and the first service attribute information to the source-side SDN controller corresponding to the first cloud edge device.

After the source-side SDN controller receives the first routing information and the first service attribute information, since the first service attribute information indicates cross-domain routing information, that is, the indicated first local edge device corresponds to the source-side SDN controller The first cloud-local edge device is located in a different domain, therefore, the source-side SDN controller will send the first routing information and the first service attribute information to the distribution SDN controller. The distribution SDN controller can acquire the first routing information and the first service attribute information.

In some optional embodiments, the distribution SDN controller may obtain the first routing information and the first service attribute information based on the northbound interface protocol of the SDN, or the PCEP protocol, or the TCP protocol, which is not specifically limited here. Wherein, if the distribution SDN controller obtains the first routing information and the first service attribute information based on the PCEP protocol, specifically, the distribution SDN controller obtains the first routing information and the first service attribute information based on the extended report message or the extended update message of the extended PCEP protocol. Routing information and first service attribute information.

In the embodiment of the present application, there are many types of transmission protocols for the distribution SDN controller to obtain the first service attribute information and the first routing information, which can be selected according to the needs of practical applications, which further improves the flexibility of the technical solution.

202. According to the first service attribute information, notify the first destination-side SDN controller corresponding to the first local edge device of the first routing information, so that the first local edge device stores the first routing information.

The distribution SDN controller determines, according to the first service attribute information, the first routing information to be sent to the first destination-side SDN controller corresponding to the first local edge device indicated by the first service attribute information. The distribution SDN controller also sends the first service attribute information to the first destination SDN controller, so that the first destination SDN controller sends the first routing information to the first local edge device according to the first service attribute information. The first local edge device stores the first routing information, so as to implement cross-domain routing information notification.

In some optional embodiments, the distribution SDN controller may send the first routing information to the first destination SDN controller based on the northbound interface protocol of the SDN, or the PCEP protocol, or the TCP protocol, which is not specifically limited here.

In the embodiment of the present application, there are multiple possibilities for the distribution SDN controller to send the first routing information to the first destination SDN controller, which improves the flexibility of the technical solution.

In this embodiment of the application, when the first service attribute information acquired by the distribution SDN controller indicates that the first cloud edge device and the first local edge device are located in different domains in the target service private network, the distribution SDN controller can information, to notify the first destination-side SDN controller corresponding to the first local edge device of the first routing information, the first routing information includes the address information of the cloud subnet corresponding to the source-side SDN, thereby realizing cross-domain notification of routing information . At the same time, the address information of the cloud subnet is notified to the cross-domain local edge device, which provides technical support for realizing the cloud-entry service in the target service private network, and improves the practicability of the technical solution of this application.

In some optional embodiments, the target service private network may further include a second cloud edge device, and the second cloud edge device is located in a different domain from the first cloud edge device. The first routing information acquired by the first cloud edge device may also be notified to cross-domain cloud edge devices, providing support for cross-domain inter-cloud interconnection. In this case, the first service attribute information may also indicate that the first cloud edge device and the second cloud edge device are located in different domains in the target service private network. Therefore, after step 201, the distribution SDN control can also notify the second destination SDN controller corresponding to the second cloud edge device of the first routing information according to the first service attribute information, so that the second destination SDN controller according to the first Service attribute information, sending the first routing information to the second cloud edge device. The second cloud edge device stores the first routing information, so as to implement routing information notification between cross-domain cloud edge devices. Wherein, the distributing SDN controller may send the first routing information to the second destination SDN controller based on the northbound interface protocol of the SDN, or the PCEP protocol, or the TCP protocol, which is not specifically limited here.

In some optional embodiments, the distribution SDN controller can also obtain the second routing information and the second service attribute information from the first destination SDN controller. The specific obtaining method is the same as obtaining the first routing information and the first The manner of service attribute information is similar, see the description of step 201 for details, and will not be repeated here. Wherein, the second routing information includes address information of the local subnet corresponding to the first local edge device, and the address information of the local subnet includes address information of at least one host in the local subnet, and the address information is expressed as an IP address or a MAC address , not limited here. The second service attribute information indicates that the first local edge device and the first cloud edge device are located in different domains in the target service private network, which means that the second routing information needs to be advertised across domains, and is advertised to the cross-domain The first cloud edge device. Therefore, the distribution SDN controller determines, according to the second service attribute information, the second routing information to be sent to the source-side SDN controller corresponding to the first cloud edge device indicated by the second service attribute information. The distribution SDN controller also sends the second service attribute information to the source-side SDN controller, so that the source-side SDN controller sends the second routing information to the first cloud edge device according to the second service attribute information. The first cloud edge device stores the second routing information, so as to implement cross-domain routing information notification. Wherein, the distribution SDN controller may send the second routing information to the source-side SDN controller based on the northbound interface protocol of the SDN, or the PCEP protocol, or the TCP protocol, which is not specifically limited here.

In some optional embodiments, the technical solution of the present application can also implement route notification between local edge devices across domains. Specifically, the target service private network may further include a second local edge device, and the second service attribute information may also indicate that the first local edge device and the second local edge device are located in different domains. The distributed SDN control may also notify the third destination SDN controller corresponding to the second local edge device of the second routing information according to the second service attribute information, so that the third destination SDN controller sends the second routing information according to the second service attribute information. The second routing information is sent to the second local edge device. The second local edge device stores the second routing information, so as to implement routing information notification between cross-domain local edge devices. Wherein, the distributing SDN controller may send the second routing information to the third destination SDN controller based on the northbound interface protocol of the SDN, or the PCEP protocol, or the TCP protocol, which is not specifically limited here.

In some optional embodiments, the second destination-side SDN controller and the third destination-side SDN controller shown in FIG. 3 may also be the same SDN controller. In this case, the second cloud edge device and The second local edge device is located in the same domain in the target service private network.

In some optional embodiments, the source-side SDN controller and the third destination-side SDN controller shown in FIG. 3 may also be the same SDN controller. In this case, the first cloud edge device and the second The local edge device is located in the same domain in the target service private network. And/or, the second destination-side SDN controller and the first destination-side SDN controller shown in FIG. 3 may also be the same SDN controller. In this case, the second cloud edge device and the first local edge device Located in the same domain in the target business private network.

In some optional embodiments, the technical solution of the present application can perform intra-domain route notification in addition to cross-domain route notification. Assume that in the embodiment shown in FIG. 3 , the second cloud edge device and the second local edge device are located in the same domain in the target service private network, and both correspond to the second destination-side SDN controller. The second cloud edge device sends routing information of the second cloud subnet and service attribute information to the second destination SDN controller. The service attribute information indicates that the second local edge device and the second cloud edge device are located in the same domain in the target service private network. The second destination-side SDN controller sends the routing information of the second cloud subnet to the second local edge according to the service attribute information, so that the second local edge device stores the routing information to implement intra-domain routing notification. Since in the embodiment of the present application, the intra-domain route notification is not the focus, it will not be repeated here.

In general, in this embodiment of the application, by defining service attribute information, route notification between any two access points in the target service private network can be realized.

It should be noted that FIG. 3 is only an example of an application scenario, and in the embodiment of the present application, the number and types of edge devices connected to each SDN controller are not limited.

Next, with the source-side SDN controller as the execution subject, the route notification method provided by the embodiment of the present application will be described, please refer to Figure 4 and Figure 5, Figure 4 is a schematic flow chart of the route notification method provided by the embodiment of the present application, Fig. 5 is a schematic diagram of a scenario of the route advertisement method provided in the embodiment of the present application. As shown in Figure 4, the route notification method provided by the embodiment of the present application includes the following steps:

401. Obtain the first routing information and first service attribute information from the first cloud edge device, the first routing information includes the address information of the cloud subnet corresponding to the first cloud edge device, and the first service attribute information indicates the first cloud The edge device and the first local edge device are located in different domains in the target service private network;

For clarity of description, the scenario shown in FIG. 5 is taken as an example to describe the route advertisement method provided in the embodiment of the present application. As shown in FIG. 5 , the source-side SDN controller is connected to the first cloud edge device and the distribution SDN controller. The first cloud edge device learns the first routing information through protocol learning or static configuration. The first routing information includes the address information of the first cloud subnet, and the address information of the first cloud subnet includes at least Address information of a virtual machine, such address information is expressed as an IP address or a MAC address, which is not specifically limited here. Wherein, the protocol for learning the first routing information has been described in step 201, and will not be repeated here. The first cloud edge device can also acquire first service attribute information, where the first service attribute information indicates that the first cloud edge device and the first local edge device are located in different domains in the target service private network. After obtaining the first routing information and the first service attribute information, the first cloud edge device sends these information to the source-side SDN controller.

The source-side SDN controller acquires the first routing information and the first service attribute information based on the southbound interface protocol of the SDN, or the PCEP protocol, or the TCP protocol. Among them, the southbound interface protocol of SDN can be determined according to the network type of the source-side SDN controller and the edge device of the first cloud. There are many situations, such as the NET-CONF protocol or the REST protocol of HTTP. It can be other types of southbound interface protocols, which are not limited here.

In the embodiment of the present application, there are various types of transmission protocols between the source-side SDN controller and the cloud edge device, which can be selected according to actual application requirements, further improving the flexibility of the technical solution.

402. Send the first routing information and the first service attribute information to the distribution SDN controller, so that the distribution SDN controller notifies the first destination SDN controller corresponding to the first local edge device of the first route according to the first service attribute information information.

Since the first service attribute information indicates that the first cloud edge device and the first local edge device in the target service private network are located in different domains, that is to say, it is necessary to perform cross-domain routing advertisement on the first routing information. Therefore, the source-side SDN control The device sends the first route information and the first service attribute information to the distribution SDN controller, so that the distribution SDN controller performs cross-domain route advertisement. Specifically, the distribution SDN controller will send the first routing information and the first service attribute information to the first destination SDN controller corresponding to the first local edge device according to the first service attribute information, so that the first destination SDN control The first local edge device connected to the router stores the first routing information. Wherein, the source-side SDN controller may send the first routing information and the first service attribute information to the distribution SDN controller based on the SDN northbound interface protocol, or the PCEP protocol, or the TCP protocol, which is not specifically limited here.

In some optional embodiments, if there are other edge devices in a different domain from the first cloud edge device in the target service private network, and the first service attribute information indicates the edge device in a different domain, it means that the second The routing information of a cloud subnet is advertised in multiple different domains, and the distribution SDN controller sends the first routing information and the first service attribute information to the SDN controllers corresponding to different domains according to the first service attribute information.

In the embodiment of the present application, there are various types of transmission protocols between the source-side SDN controller and the distribution SDN controller, which can be selected according to actual application requirements, further improving the flexibility of the technical solution.

In some optional embodiments, the source-side SDN controller is further connected to the second local edge device, so as to obtain the second routing information and the second service attribute information from the second local edge device. Wherein, the second routing information includes address information of the second local subnet, and specifically refers to address information of at least one host on the second local subnet. The manner in which the second local edge device obtains the second routing information is similar to the manner in which the first cloud edge device obtains the first routing information, which will not be repeated here.

Since the second service attribute information indicates that the second local edge device and the second cloud edge device are located in different domains in the target service private network, that is, indicates a cross-domain access point, the source-side SDN controller sends the distribution SDN The controller sends the second routing information and the second service attribute information, so that the distribution controller performs cross-domain routing advertisement. Specifically, the distribution SDN controller will send the second routing information and the second service attribute information to the second destination SDN controller corresponding to the second cloud edge device according to the second service attribute information, so that the second destination SDN control The second cloud edge device connected to the router stores the second routing information. Wherein, the manner in which the source-side SDN controller sends the second routing information and the second service attribute information to the distribution SDN controller is similar to the manner in which the first routing information and the first service attribute information are sent to the distribution SDN controller. Let me repeat.

In some optional embodiments, if there are other edge devices in a different domain from the second local edge device in the target service private network, and the second service attribute information indicates the edge device in a different domain, it means that the second local edge device needs to be The routing information of the local subnet is advertised in multiple different domains, and the distribution SDN controller sends the second routing information and the second service attribute information to the SDN controllers corresponding to different domains according to the second service attribute information.

In the embodiment of this application, in addition to sending routing information and service attribute information to the distribution SDN controller, the source-side SDN controller implements cross-domain notification of the routing information of the cloud subnet or local subnet corresponding to the source-side SDN controller. In addition, the source-side SDN controller can also obtain the routing information of the cross-domain cloud subnet or local subnet, and send corresponding information to the local edge device or cloud edge device connected to the source-side SDN controller according to the corresponding business attribute information. routing information.

In some optional embodiments, the source-side SDN controller can obtain the third route information and the third service attribute information from the distribution SDN controller, and the third route information and the third service attribute information are the second destination-side edge The device is sent to the distribution SDN controller. The third routing information includes address information of the cloud subnet corresponding to the second cloud edge device, that is, routing information of the second cloud subnet, including address information of at least one virtual machine on the second cloud subnet. Since the third service attribute information indicates that the second cloud edge device and the first cloud edge device are located in different domains in the target service private network, the source-side SDN controller will send a message to the first cloud edge device according to the third service attribute information The third routing information, so that the first cloud edge device stores the third routing information.

In some optional embodiments, if the third service attribute information also indicates that the second cloud edge device and the second local edge device are located in different domains in the target service private network, then the source-side SDN controller will attribute information, sending the third routing information to the second local edge device, so that the second local edge device stores the third routing information.

In the embodiment of this application, the source-side SDN controller can obtain the address information of the second cloud subnet in other domains, that is, the third routing information, and send the third routing information to the second local edge device, so that the second local The edge device stores third-party routing information, which provides support for cross-domain cloud access services.

In some optional embodiments, the source-side SDN controller can also obtain fourth routing information and fourth service attribute information from the distribution SDN controller, where the fourth routing information and the fourth service attribute information are The edge device sends to the distribution SDN controller. The fourth routing information includes address information of the local subnet corresponding to the first local edge device, that is, address information of the first local subnet, including address information of at least one host on the first local subnet. Since the fourth service attribute information indicates that the first local edge device and the second local edge device are located in different domains in the target service private network, the source-side SDN controller will send a message to the second local edge device according to the fourth service attribute information The fourth routing information, so that the second local edge device stores the fourth routing information.

In some optional embodiments, if the fourth service attribute information also indicates that the first cloud edge device and the second local edge device are located in different domains in the target service private network, then the source-side SDN controller will attribute information, sending fourth routing information to the first cloud edge device, so that the first cloud edge device stores the fourth routing information.

In the embodiment of the present application, the source-side SDN controller can obtain the address information of the first local subnet in other domains, that is, the fourth routing information, and send the fourth routing information to the first cloud edge device, so that the second cloud The edge device stores fourth routing information.

In the embodiment of the present application, the source-side SDN controller can obtain routing information and service attribute information sent from the distribution SDN controller based on the northbound interface protocol of the SDN, or the PCEP protocol, or the TCP protocol.

The source-side SDN controller can send routing information and service attribute information to the local edge device or cloud edge device connected to the source-side SDN controller based on the SDN southbound interface protocol, PCEP protocol, or TCP protocol.

In some optional embodiments, the technical solution of the present application can perform intra-domain route notification in addition to cross-domain route notification. Exemplarily, in the embodiment shown in FIG. 5, the first cloud edge device and the second local edge device are located in the same domain in the target service private network, and both correspond to the source-side SDN controller. The first cloud edge device sends routing information of the first cloud subnet and service attribute information to the source-side SDN controller. The service attribute information indicates that the second local edge device and the first cloud edge device are located in the same domain in the target service private network. The source-side SDN controller sends the routing information of the first cloud subnet to the second local edge according to the service attribute information, so that the second local edge device stores the routing information to implement intra-domain routing notification. Since in the embodiment of the present application, the intra-domain route notification is not the focus, it will not be repeated here.

It should be noted that FIG. 5 is only an example of an application scenario, and in the embodiment of the present application, the number and types of edge devices connected to each SDN controller are not limited.

In the embodiment of the present application, different domains in the target service private network, including different geographical regions or different technical domains, will be described in conjunction with Figure 6 and Figure 7, both of which are route notifications provided by the embodiment of the present application Scenario diagram of the method.

As shown in Figure 6, different domains include different geographic regions. Assuming that a province is a domain, through the route notification method provided in the embodiment of this application, cloud access services across provinces and within a province can also be implemented, which is not limited here.

As shown in Figure 7, different domains also include different technical domains, and the technical domains include the access domain and the transmission domain. The access domain is connected to the local gateway and the local subnet, and the local edge devices in the access domain include an optical line terminal (ONT) or an optical network terminal (OLT). Among them, P2MP means point-to-multipoint service, and CPE means customer premise equipment.

Optionally, there are many possibilities for two edge devices located in different technical domains, including one edge device in the access domain and one edge device in the transport domain; it also includes one edge device in technical domain A and the other The case where the edge device is in the technical domain B; it also includes the case where one edge device is in the transport domain A and the other edge device is in the transport domain B, which is not limited here.

In some optional embodiments, each type of SDN controller may include an SDR controller. The types of the various SDN controllers may be the same or different, which is not specifically limited here. Wherein, each SDN controller includes a distribution SDN controller, a source-side SDN controller, a first destination-side SDN controller, a second destination-side SDN controller, and a third SDN destination-side controller.

In the embodiment shown in FIG. 7 , the SDR controller is taken as an example for illustration. The high-level SDR controller corresponds to the distribution SDN controller, and the low-level SDR controller corresponds to the source-side SDN controller or each destination-side SDN controller.

Next, the communication system provided by the embodiment of the present application will be described.

In some optional embodiments, the communication system includes a distribution SDN controller, a source-side SDN controller, and a first destination-side SDN controller. Wherein, the source-side SDN is connected to the distribution SDN controller and the first cloud edge device, and the first destination-side SDN controller is connected to the distribution SDN controller and the first local edge device.

In some optional embodiments, the communication system further includes a second destination-side SDN controller, and the second destination-side SDN controller is connected to the distribution SDN controller and the second cloud edge device. The first service attribute information is really that the first cloud edge device and the second cloud edge device are located in different domains in the target service private network. The distribution SDN controller is further configured to notify the second destination SDN controller corresponding to the second cloud edge device of the first routing information according to the first service attribute information; send the first service attribute information to the second destination SDN controller . The second destination-side SDN controller is configured to receive the first routing information and the first service attribute information, and send the second routing information to the second cloud edge device according to the first service attribute information.

In some optional embodiments, the first destination-side SDN controller is further configured to acquire second routing information and second service attribute information from the first local edge device, where the second routing information includes the first local edge device The address information of the corresponding local subnet, the second service attribute information indicates that the first local edge device and the first cloud edge device are located in different domains in the target service private network; send the second routing information and the second service to the distribution SDN controller attribute information. The distribution SDN controller is also used to obtain the second routing information and the second service attribute information; according to the second service attribute information, send the second routing information to the source-side SDN controller corresponding to the first cloud edge device; send the second routing information to the source-side SDN The controller sends the second service attribute information. The source-side SDN controller is further configured to receive second routing information and second service attribute information; and send the second routing information to the first cloud edge device according to the second service attribute information.

In some optional embodiments, the communication system further includes a third destination-side SDN controller, and the third destination-side connection distribution SDN controller and the second local edge device; the second service attribute information also indicates that the first local edge device and The second local edge device is located in a different domain in the target service private network. The distribution SDN controller is further configured to notify the third destination SDN controller corresponding to the second local edge device of the third route information according to the second service attribute information; and send the second service attribute information to the third destination SDN control. The third destination-side SDN controller is configured to receive the second routing information and the second service attribute information; and send the second routing information to the second local edge device according to the second service attribute information.

In some optional embodiments, the communication system may also include a greater number of cloud edge devices or local edge devices, and each SDN controller may also be connected to a greater number of cloud edge devices or local edge devices, based on the above principles , to implement cross-domain routing notification to meet the different needs of different users, which is not limited here.

In some optional embodiments, routing information and service attribute information may be transmitted (communicated) between the SDN controllers based on the SDN northbound interface protocol, or the PCEP protocol, or the TCP protocol. Exemplarily, the distribution SDN controller may send the first routing information and the first service attribute information to the distribution SDN controller based on the PCEP protocol. Each SDN controller includes a source-side SDN controller, a first destination-side SDN controller, a second destination-side SDN controller, and a third destination-side SDN controller.

In some optional embodiments, the SDN controller connected to the local edge device or the cloud edge device can obtain information from the local edge device or the cloud edge device based on the SDN southbound interface protocol, or the PCEP protocol, or the TCP protocol. Routing information and business attribute information. Exemplarily, the source-side SDN controller may obtain the first routing information and the first service attribute information from the first cloud edge device based on the PCEP protocol.

In some optional embodiments, different domains in the target service private network include different geographical regions, or different technical domains, where the technical domain includes an access domain and a transmission domain.

In some optional embodiments, each type of SDN controller may include an SDR controller. The types of the various SDN controllers may be the same or different, which is not specifically limited here. Each SDN controller includes a distribution SDN controller, a source-side SDN controller, a first destination-side SDN controller, a second SDN controller, and a third SDN controller.

In some optional embodiments, the third destination-side SDN controller and the source-side SDN controller may be different SDN controllers, or may be the same SDN controller, that is, the second local edge device and the first A cloud edge device may be located in a different domain in the target private network service, or in the same domain in the target service private network, which is not limited here.

In some optional embodiments, the first destination-side SDN controller and the second destination-side SDN controller may be different SDN controllers, or may be the same SDN controller, that is, the first local edge device The edge device of the second cloud may be located in a different domain of the target private network service, or may be located in the same domain of the target service private network, which is not specifically limited here.

In some optional embodiments, the second destination-side SDN controller and the third destination-side SDN controller may be different SDN controllers, or may be the same SDN controller, that is, the second cloud edge device The second local edge device and the second local edge device may be located in different domains of the target private network service, or may be located in the same domain of the target service private network, which is not specifically limited here.

In the following, related devices provided in the embodiments of the present application will be described.

Please refer to FIG. 8. FIG. 8 is a schematic structural diagram of the distribution SDN controller provided by the embodiment of the present application. The distribution SDN controller 800 includes:

The obtaining unit 801 is configured to obtain first routing information and first service attribute information from the source-side SDN controller, the source-side SDN controller is connected to the first cloud edge device, and the first routing information includes the first cloud edge device corresponding The address information of the cloud subnet, the first service attribute information indicates that the first cloud edge device and the first local edge device are located in different domains in the target service private network.

The sending unit 802 is configured to notify the first destination SDN controller corresponding to the first local edge device of the first routing information according to the first service attribute information, so that the first local edge device stores the first routing information.

In some optional embodiments, the first service attribute information further indicates that the first cloud edge device and the second cloud edge device are located in different domains in the target service private network.

The sending unit 802 is further configured to notify the second destination SDN controller corresponding to the second cloud edge device of the first routing information according to the first service attribute information, so that the second cloud edge device stores the first routing information.

In some optional embodiments, the obtaining unit 801 is further configured to obtain the second routing information and the second service attribute information from the first destination SDN controller, the second routing information includes the information corresponding to the first local edge device The address information of the local subnet, and the second service attribute information indicate that the first local edge device and the first cloud edge device are located in different domains in the target service private network.

The sending unit 802 is further configured to notify the source-side SDN controller corresponding to the first cloud edge device of the second routing information according to the second service attribute information, so that the first cloud edge device stores the second routing information.

In some optional embodiments, the second service attribute information further indicates that the first local edge device and the second local edge device are located in different domains in the target service private network. The sending unit 802 is further configured to notify the third destination SDN controller corresponding to the second local edge device of the second routing information according to the second service attribute information, so that the second local edge device stores the second routing information.

The distribution SDN controller 800 may execute the operations performed by the distribution SDN controller in the embodiments shown in FIGS. 1 to 6 and the operations performed by the high-level SDR controller in the embodiment shown in FIG. 7 , which will not be repeated here.

Please refer to FIG. 9. FIG. 9 is a schematic structural diagram of a source-side SDN controller provided in an embodiment of the present application. The source-side SDN controller 900 is connected to the first cloud edge device and the distribution SDN controller. The source-side SDN controller 900 includes :

The obtaining unit 901 is configured to obtain first routing information and first service attribute information from the first cloud edge device, where the first routing information includes address information of the cloud subnet corresponding to the first cloud edge device, and the first service attribute information It indicates that the first cloud edge device and the first local edge device are located in different domains in the target service private network.

The sending unit 902 is configured to send the first routing information and the first service attribute information to the distribution SDN controller, so that the distribution SDN controller sends the first destination-side SDN controller corresponding to the first local edge device according to the first service attribute information Advertise the first routing information.

In some optional embodiments, the source-side SDN controller 900 is further connected to the second local edge device. The obtaining unit 901 is further configured to obtain second routing information and second service attribute information from the second local edge device, where the second routing information includes address information of the local subnet corresponding to the second local edge device, and the second service attribute information The information indicates that the second local edge device and the second cloud edge device are located in different domains in the target service private network.

The sending unit 902 is further configured to send the second routing information and the second service attribute information to the distribution SDN controller, so that the distribution SDN controller controls the second destination SDN corresponding to the second cloud edge device according to the second service attribute information. The router advertises the second routing information.

In some optional embodiments, the acquiring unit 901 is further configured to acquire third routing information and third service attribute information from the distribution SDN controller, where the third routing information includes the cloud subnet corresponding to the second cloud edge device address information, and the third service attribute information indicates that the second cloud edge device and the first cloud edge device are located in different domains in the target service private network.

The sending unit 902 is further configured to send third routing information to the first cloud edge device according to the third service attribute information, so that the first cloud edge device stores the third routing information.

In some optional embodiments, the obtaining unit 901 is further configured to obtain fourth routing information and fourth service attribute information from the distribution SDN controller, where the fourth routing information includes the local subnet corresponding to the first local edge device The fourth service attribute information indicates that the first local edge device and the second local edge device are located in different domains in the target service private network.

The sending unit 902 is further configured to send fourth routing information to the second local edge device according to the fourth service attribute information, so that the second local edge device stores the fourth routing information.

The source-side SDN controller 900 may perform the operations of the source-side SDN controller in the embodiments shown in FIGS. 1 to 6 and the operations of the lower-layer SDR controller in the embodiment shown in FIG. 7 , which will not be repeated here.

Next, the computer device provided by the embodiment of the present application will be described, please refer to FIG. 10 , which is a schematic structural diagram of the computer device provided by the embodiment of the present application. The computer device 1000 includes: a processor 1001 and a memory 1002, and the memory 1002 stores one or more application programs or data.

Wherein, the storage 1002 may be a volatile storage or a persistent storage. The program stored in the memory 1002 may include one or more modules, and each module may be used to perform a series of operations performed by the computer device 1000 . Furthermore, the processor 1001 can communicate with the memory 1002 , and execute a series of instruction operations in the memory 1002 on the computer device 1000 . The processor 1001 may be a central processing unit (central processing units, CPU), or a single-core processor, or other types of processors, such as a dual-core processor, which are not specifically limited here.

The computer device 1000 may also include one or more communication interfaces 1003, and one or more operating systems, such as Windows Server ^™ , Mac OS X ^™ , Unix ^™ , Linux ^™ , FreeBSD ^™ , etc.

The computer device 1000 can execute the operations performed by the distribution SDN controller or the source-side SDN controller in the embodiments shown in FIGS. The operations performed by the controller computer device will not be repeated here.

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

In the several embodiments provided in this application, it should be understood that the disclosed system, device and method can be implemented in other ways. For example, the device embodiments described above are only illustrative. For example, the division of the units is only a logical function division. In actual implementation, there may be other division methods. For example, multiple units or components can be combined or May be integrated into another system, or some features may be ignored, or not implemented. In another point, the mutual coupling or direct coupling or communication connection shown or discussed may be through some interfaces, and the indirect coupling or communication connection of devices or units may be in electrical, mechanical or other forms.

The units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or may be distributed to multiple network units. Part or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.

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

If the integrated unit is realized in the form of a software function unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application is essentially or part of the contribution to the prior art or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium , including several instructions to make a computer device (which may be a personal computer, a server, or a network device, etc.) execute all or part of the steps of the methods described in the various embodiments of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (read-only memory, ROM), random access memory (random access memory, RAM), magnetic disk or optical disc and other media that can store program codes. .

Claims

A route notification method, characterized in that the method is applied to distributing software-defined network SDN controllers, the method comprising:

Obtaining first routing information and first service attribute information from a source-side SDN controller connected to a first cloud edge device, where the first routing information includes the corresponding The address information of the cloud subnet, the first service attribute information indicates that the first cloud edge device and the first local edge device are located in different domains in the target service private network;

Notifying the first destination SDN controller corresponding to the first local edge device of the first routing information according to the first service attribute information, so that the first local edge device stores the first routing information .
The method according to claim 1, wherein the first service attribute information also indicates that the first cloud edge device and the second cloud edge device are located in different domains in the target service private network; the method Also includes:

According to the first service attribute information, notify the second destination SDN controller corresponding to the second cloud edge device of the first routing information, so that the second cloud edge device stores the first routing information .
The method according to claim 1 or 2, characterized in that the method further comprises:

Acquire second routing information and second service attribute information from the first destination SDN controller, where the second routing information includes address information of the local subnet corresponding to the first local edge device, and the second The second service attribute information indicates that the first local edge device and the first cloud edge device are located in different domains in the target service private network;

Notifying the source-side SDN controller corresponding to the first cloud edge device of the second routing information according to the second service attribute information, so that the first cloud edge device stores the second routing information .
The method according to claim 3, wherein the second service attribute information also indicates that the first local edge device and the second local edge device are located in different domains in the target service private network; the method Also includes:

Notifying a third destination SDN controller corresponding to the second local edge device of the second routing information according to the second service attribute information, so that the second local edge device stores the second routing information .
The method according to any one of claims 1 to 4, wherein said obtaining the first routing information and the first service attribute information from the source-side SDN controller comprises:

The first route information and the first service attribute information from the source-side SDN controller are acquired based on a northbound interface protocol of a software-defined network, or a path computation unit communication protocol, or a transmission control protocol.
The method according to any one of claims 1 to 5, wherein the notifying the first destination SDN controller of the first routing information includes:

Notifying the first destination SDN controller of the first routing information based on a northbound interface protocol of a software-defined network, or a path computation unit communication protocol, or a transmission control protocol.
The method according to any one of claims 1 to 6, wherein the different domains include different geographical areas, or different technical domains, and the technical domains include an access domain and a transmission domain.
The method according to any one of claims 1 to 7, wherein the type of the distribution SDN controller, the type of the source-side SDN controller, and the type of the first destination-side SDN controller include Software Defined Routing SDR Controller.
A route notification method, characterized in that the method is applied to a source-side SDN controller, and the source-side SDN controller is connected to a first cloud edge device and a distribution SDN controller, and the method includes:

Acquire first routing information and first service attribute information from the first cloud edge device, where the first routing information includes address information of the cloud subnet corresponding to the first cloud edge device, and the first service The attribute information indicates that the first cloud edge device and the first local edge device are located in different domains in the target service private network;

sending the first route information and the first service attribute information to the distribution SDN controller, so that the distribution SDN controller sends the first destination corresponding to the first local edge device according to the first service attribute information The side SDN controller notifies the first routing information.
The method according to claim 9, wherein the source-side SDN controller is also connected to a second local edge device, and the method further comprises:

Obtain second routing information and second service attribute information from the second local edge device, where the second routing information includes address information of the local subnet corresponding to the second local edge device, and the second service The attribute information indicates that the second local edge device and the second cloud edge device are located in different domains in the target service private network;

sending the second routing information and the second service attribute information to the distribution SDN controller, so that the distribution SDN controller sends the second destination corresponding to the second cloud edge device according to the second service attribute information The side SDN controller notifies the second routing information.
The method according to claim 9 or 10, characterized in that the method further comprises:

Obtain third routing information and third service attribute information from the distribution SDN controller, where the third routing information includes address information of the cloud subnet corresponding to the second cloud edge device, and the third service attribute information indicates The second cloud edge device and the first cloud edge device are located in different domains in the target service private network;

Sending the third routing information to the first cloud edge device according to the third service attribute information, so that the first cloud edge device stores the third routing information.
The method according to claim 10 or 11, wherein the method further comprises:

Obtain fourth routing information and fourth service attribute information from the distribution SDN controller, where the fourth routing information includes address information of the local subnet corresponding to the first local edge device, and the fourth service attribute information indicates The first local edge device and the second local edge device are located in different domains in the target service private network;

Sending the fourth routing information to a second local edge device according to the fourth service attribute information, so that the second local edge device stores the fourth routing information.
The method according to any one of claims 9 to 12, wherein the acquiring the first routing information and the first service attribute information from the first cloud edge device comprises:

The first routing information and the first service attribute information from the first cloud edge device are acquired based on a southbound interface protocol of software defined networking, or a path computation unit communication protocol, or a transmission control protocol.
The method according to any one of claims 9 to 13, wherein the sending the first routing information and the first service attribute information to the distribution SDN controller comprises:

Sending the first routing information and the first service attribute information to the distribution SDN controller based on a northbound interface protocol of a software-defined network, or a path computation unit communication protocol, or a transmission control protocol.
The method according to any one of claims 9 to 14, wherein the different domains include different geographical areas, or different technical domains, and the technical domains include an access domain and a transmission domain.
The method according to any one of claims 9 to 15, wherein the type of the distribution SDN controller and the type of the source-side SDN controller include an SDR controller.
A communication system, characterized in that the communication system includes a distribution SDN controller, a source-side SDN controller and a first destination-side SDN controller, and the source-side SDN controller is connected to the distribution SDN controller and the first A cloud edge device, the first destination SDN controller is connected to the distribution SDN controller and the first local edge device;

The source-side SDN controller is configured to:

Acquire first routing information and first service attribute information from the first cloud edge device, where the first routing information includes address information of a first cloud subnet corresponding to the first cloud edge device, and the first Service attribute information indicating that the first cloud edge device and the first local edge device are located in different domains in the target service private network;

sending the first routing information and the first service attribute information to the distribution SDN controller;

The distribution SDN controller is used for:

Acquiring the first routing information and the first service attribute information;

Notifying the first destination SDN controller corresponding to the first local edge device of the first routing information according to the first service attribute information;

sending the first service attribute information to the first destination SDN controller;

The first destination-side SDN controller is configured to:

receiving the first routing information and the first service attribute information;

Sending the first routing information to the first local edge device according to the first service attribute information.
The communication system according to claim 17, wherein the communication system further comprises a second destination-side SDN controller, and the second destination-side SDN controller is connected to the distribution SDN controller and the second cloud edge device ;

The first service attribute information also indicates that the first cloud edge device and the second cloud edge device are located in different domains in the target service private network;

The distribution SDN controller is also used for:

Notifying the second destination SDN controller corresponding to the second cloud edge device of the first routing information according to the first service attribute information;

sending the first service attribute information to the second destination SDN controller;

The second destination-side SDN controller is configured to:

receiving the first routing information and the first service attribute information;

Sending the second routing information to the second cloud edge device according to the first service attribute information.
The communication system according to claim 17 or 18, wherein the first destination SDN controller is further used for:

Acquire second routing information and second service attribute information from the first local edge device, where the second routing information includes address information of the local subnet corresponding to the first local edge device, and the second service The attribute information indicates that the first local edge device and the first cloud edge device are located in different domains in the target service private network;

sending the second routing information and the second service attribute information to the distribution SDN controller;

The distribution SDN controller is also used for:

Acquiring the second routing information and the second service attribute information;

Sending the second routing information to the source-side SDN controller corresponding to the first cloud edge device according to the second service attribute information;

sending the second service attribute information to the source-side SDN controller;

The source-side SDN controller is also used for:

receiving the second routing information and the second service attribute information;

Sending the second routing information to the first cloud edge device according to the second service attribute information.
The communication system according to claim 19, wherein the communication system further comprises a third destination SDN controller, and the third destination connects the distribution SDN controller and the second local edge device; The second service attribute information also indicates that the first local edge device and the second local edge device are located in different domains in the target service private network;

The distribution SDN controller is further configured to notify the third destination SDN controller corresponding to the second local edge device of the third routing information according to the second service attribute information;

sending the second service attribute information to the third destination SDN control;

The third destination-side SDN controller is configured to:

receiving the second routing information and the second service attribute information;

Sending the second routing information to the second local edge device according to the second service attribute information.
The communication system according to any one of claims 17 to 20, wherein the different domains include different geographical areas, or different technical domains, and the technical domains include an access domain and a transmission domain.
The communication system according to any one of claims 17 to 21, wherein the type of the distribution SDN controller, the type of the source-side SDN controller, and the type of the first destination-side SDN controller Includes software-defined routing SDR controller.
A distribution SDN controller, characterized in that, comprising:

An obtaining unit, configured to obtain first routing information and first service attribute information from a source-side SDN controller, the source-side SDN controller is connected to the first cloud edge device, and the first routing information includes the first Address information of a cloud subnet corresponding to a cloud edge device, the first service attribute information indicating that the first cloud edge device and the first local edge device are located in different domains in the target service private network;

A sending unit, configured to notify the first destination SDN controller corresponding to the first local edge device of the first routing information according to the first service attribute information, so that the first local edge device stores the the first routing information.
The distribution SDN controller according to claim 23, wherein the first service attribute information also indicates that the first cloud edge device and the second cloud edge device are located in different domains in the target service private network;

The sending unit is further configured to notify the second destination SDN controller corresponding to the second cloud edge device of the first routing information according to the first service attribute information, so that the second cloud edge The device stores the first routing information.
The distribution SDN controller according to claim 23 or 24, characterized in that:

The acquiring unit is further configured to acquire second routing information and second service attribute information from the first destination-side SDN controller, the second routing information including the local subnet corresponding to the first local edge device. Network address information, the second service attribute information indicates that the first local edge device and the first cloud edge device are located in different domains in the target service private network;

The sending unit is further configured to notify the source-side SDN controller corresponding to the first cloud edge device of the second routing information according to the second service attribute information, so that the first cloud edge The device stores the second routing information.
The distribution SDN controller according to claim 25, wherein the second service attribute information also indicates that the first local edge device and the second local edge device are located in different domains in the target service private network;

The sending unit is further configured to notify the third destination SDN controller corresponding to the second local edge device of the second routing information according to the second service attribute information, so that the second local edge The device stores the second routing information.
A source-side SDN controller, wherein the source-side SDN controller is connected to a first cloud edge device and a distribution SDN controller, and the source-side SDN controller includes:

an obtaining unit, configured to obtain first routing information and first service attribute information from the first cloud edge device, where the first routing information includes address information of a cloud subnet corresponding to the first cloud edge device, The first service attribute information indicates that the first cloud edge device and the first local edge device are located in different domains in the target service private network;

A sending unit, configured to send the first routing information and the first service attribute information to the distribution SDN controller, so that the distribution SDN controller sends the first local edge device according to the first service attribute information The corresponding first destination-side SDN controller notifies the first routing information.
The source-side SDN controller according to claim 27, wherein the source-side SDN controller is also connected to a second local edge device;

The acquiring unit is further configured to acquire second routing information and second service attribute information from the second local edge device, the second routing information including the local subnet corresponding to the second local edge device Address information, the second service attribute information indicating that the second local edge device and the second cloud edge device are located in different domains in the target service private network;

The sending unit is further configured to send the second routing information and the second service attribute information to the distribution SDN controller, so that the distribution SDN controller sends the second routing information to the second service attribute information according to the second service attribute information. The second destination SDN controller corresponding to the cloud edge device notifies the second routing information.
The source-side SDN controller according to claim 27 or 28, wherein the obtaining unit is further configured to obtain third routing information and third service attribute information from the distribution SDN controller, the The third routing information includes the address information of the cloud subnet corresponding to the second cloud edge device, and the third service attribute information indicates that the second cloud edge device is located in a different location in the target service private network than the first cloud edge device. area;

The sending unit is further configured to send the third routing information to the first cloud edge device according to the third service attribute information, so that the first cloud edge device stores the third routing information.
According to the source-side SDN controller according to claim 28 or 29, wherein the obtaining unit is further configured to obtain fourth routing information and fourth service attribute information from the distribution SDN controller, the first The fourth route information includes the address information of the local subnet corresponding to the first local edge device, and the fourth service attribute information indicates that the first local edge device and the second local edge device are located in different domains in the target service private network ;

The sending unit is further configured to send the fourth routing information to a second local edge device according to the fourth service attribute information, so that the second local edge device stores the fourth routing information.
A computer device, characterized in that it includes: a processor, a memory, and a communication interface;

The processor and the memory are connected to the communication interface;

The processor is configured to execute the method of any one of claims 1-16.
A computer-readable storage medium, characterized in that the computer-readable storage medium stores instructions, and when the instructions are run on a computer, the computer executes the method described in any one of claims 1 to 16. method.
A computer program product, characterized in that, when the computer program product is executed on a computer, the computer executes the method according to any one of claims 1 to 16.