WO2021135746A1 - 路由计算方法和数据传输方法 - Google Patents
路由计算方法和数据传输方法 Download PDFInfo
- Publication number
- WO2021135746A1 WO2021135746A1 PCT/CN2020/131839 CN2020131839W WO2021135746A1 WO 2021135746 A1 WO2021135746 A1 WO 2021135746A1 CN 2020131839 W CN2020131839 W CN 2020131839W WO 2021135746 A1 WO2021135746 A1 WO 2021135746A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- delay
- service
- route
- data transmission
- sdn controller
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Ceased
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/12—Shortest path evaluation
- H04L45/121—Shortest path evaluation by minimising delays
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/02—Topology update or discovery
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/70—Routing based on monitoring results
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/76—Routing in software-defined topologies, e.g. routing between virtual machines
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
- H04L47/10—Flow control; Congestion control
- H04L47/28—Flow control; Congestion control in relation to timing considerations
- H04L47/283—Flow control; Congestion control in relation to timing considerations in response to processing delays, e.g. caused by jitter or round trip time [RTT]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W40/00—Communication routing or communication path finding
- H04W40/34—Modification of an existing route
Definitions
- This application relates to the field of Software Defined Network (SDN, Software Defined Network), and specifically to a routing calculation method, a data transmission method, a service processing method, an SDN controller, a terminal, and a computer Readable storage medium.
- SDN Software Defined Network
- SDN is an open network architecture, the main features of which are centralized control and network programmability, allowing network managers to manage and operate the entire network by means of software programming.
- the logic control function and the data forwarding function are separated, and the software-based network controller realizes the logic control function of the network.
- the current SDN network has the function of delay routing, that is, when the service is established, the delay of various routes between two nodes that implement the service can be automatically measured and sorted, so that the delay can be automatically selected The best route.
- the purpose of this application is to provide a route calculation method, a data transmission method, a service processing method, an SDN controller, a terminal, and a computer-readable storage medium.
- a route calculation method which is applied to an SDN controller.
- the route calculation method includes: monitoring the network resource status of the forwarding layer; When the status changes, calculate the optimal route with delay for the monitored scheduled service according to the changed network resources.
- a data transmission method is provided, which is applied to an SDN controller, and the data transmission method includes: determining the optimal route for the delay of the monitored predetermined service according to a predetermined algorithm, wherein The predetermined algorithm is the above-mentioned route calculation method provided by this application; when a predetermined condition is met, the monitored predetermined service is migrated to the optimal delay route.
- a service processing method including: generating a service creation instruction, the service creation instruction includes configuring delay monitoring information or canceling delay monitoring information, and the configuring delay monitoring information is used for
- the SDN controller is controlled to execute the aforementioned data transmission method provided in this application, and the cancellation delay monitoring information is used to control the SDN controller to stop executing the data transmission method; and send a service creation instruction to the SDN controller.
- a routing calculation module including: a monitoring unit for monitoring the network resource status of the forwarding layer; and a calculation unit for monitoring the network resource status of the forwarding layer.
- the optimal route for delay is calculated for the scheduled service to be monitored.
- an SDN controller including: a storage module storing an executable program; one or more processors, the one or more processors calling the executable program, so that The one or more processors implement the foregoing routing calculation method provided in this application, or enable the one or more processors to implement the foregoing data transmission method provided in this application.
- a computer-readable storage medium is provided with an executable program stored thereon.
- the executable program When invoked, it can implement the above-mentioned routing calculation method provided by this application or Provide the above-mentioned data transmission method.
- a terminal device including: an instruction generation module for generating a service creation instruction, the service creation instruction includes configuring delay monitoring information or canceling delay monitoring information, and the configuration time
- the delay monitoring information is used to control the SDN controller to execute the above-mentioned data transmission method provided in this application, and the cancellation delay monitoring information is used to control the SDN controller to stop performing the above-mentioned data transmission provided in this application.
- Method instruction sending module, used to send a service creation instruction to the SDN controller.
- a computer-readable storage medium on which an executable program is stored, and when the executable program is invoked, the above-mentioned service processing method provided by the present application can be implemented.
- FIG. 1 is a flowchart of an implementation manner of the route calculation method provided by the present application
- Figure 2 is a schematic diagram of the architecture of the SDN network
- Figure 3 is a schematic diagram of service rerouting
- Figure 4 is a schematic diagram of multi-service rerouting
- FIG. 5 is a flowchart of another implementation manner of the route calculation method provided by the present application.
- FIG. 6 is a flowchart of an implementation manner of the data transmission method provided by this application.
- FIG. 7 is a flowchart of another implementation manner of the data transmission method provided by this application.
- FIG. 8 is a flowchart of an implementation manner of the service creation method provided by this application.
- FIG. 9 is a schematic diagram of the SDN controller module provided by the present application.
- FIG. 10 is a schematic diagram of the SDN system provided by this application.
- FIG. 11 is a schematic diagram of a terminal device provided by the present application.
- FIG. 12 is a flowchart of Embodiment 1 of the present application.
- FIG. 13 is a flowchart of Embodiment 2 of the present application.
- FIG. 14 is a flowchart of Embodiment 3 of the present application.
- FIG. 15 is a flowchart of Embodiment 4 of the present application.
- the link state of the forwarding layer is always in a state of change.
- it can only ensure that the time delay at the time of service establishment is optimal.
- the state of the network resources of the forwarding layer remains consistent with the time of service establishment, then the service route at the time of service establishment is optimal.
- it is impossible to determine that the delay of the current route of the service is still optimal.
- This application provides a routing calculation method, a data transmission method, a service processing method, an SDN controller, a terminal, and a computer-readable storage medium.
- the route calculation method can make the link still on the optimal delay link after the service starts.
- the route calculation method includes:
- step S110 monitor the network resource status of the forwarding layer
- step S120 when the state of the network resource of the forwarding layer changes, calculate the optimal route of the delay for the scheduled service to be monitored according to the changed network resource.
- the SDN network includes three parts: an application layer 100, an SDN controller 200, and a forwarding layer 300.
- the route calculation method provided in this application is executed by the SDN controller 100.
- the SDN controller 200 communicates with the application layer 100 through the northbound interface, and the SDN controller 200 communicates with the forwarding layer 300 through the southbound interface.
- the SDN network may also include a database 400.
- step S110 by monitoring the network resource status of the forwarding layer in step S110, once the network resource status of the forwarding layer 300 changes, each link in the forwarding layer 300 that can perform the predetermined service The link delay will also change.
- step S120 the time-delay optimal route is recalculated for the monitored scheduled service.
- the user can manually switch the predetermined service to the optimal route for delay, or the SDN controller can automatically switch the predetermined service to the optimal route for delay.
- Optimal routing After calculating the optimal route for delay, the user can manually switch the predetermined service to the optimal route for delay, or the SDN controller can automatically switch the predetermined service to the optimal route for delay.
- the route calculation method provided in this application is used to calculate the optimal route with delay during the execution of the business, and the business is switched according to the result, the optimal route with delay described by the child can be ensured in the entire business execution.
- the business is used on the route with the optimal delay, which can improve the efficiency of executing the business.
- the network resources in the forwarding layer After the status changes, the optimal route for the delay of the predetermined service is calculated as the service route (node A ⁇ node D ⁇ node C) (that is, the route to be migrated for service 1 in FIG. 3).
- the user can manually switch the predetermined service from the route where the service 1 is located to the route to be migrated from the service 1 or the SDN controller can automatically switch the predetermined service from the current route to the route to be migrated from the service 1.
- service route 1 is the optimal route for delay.
- the service route (node A ⁇ node D ⁇ node C) becomes the optimal route for delay. Switching the service from service routing (node A ⁇ node B ⁇ node C) to (node A ⁇ node D ⁇ node C) can ensure that the delay is always optimal during the execution of the service.
- FIG. 3 is a schematic diagram of single-service rerouting, that is, one service is monitored.
- this application is not limited to this, and multiple services can be monitored at the same time.
- two services can be monitored. Calculate the optimal route of delay for these two business at the same time.
- Business 1 can be migrated from business routing (node A ⁇ node B ⁇ node C) to business routing (node A ⁇ node D ⁇ node C), and business 2 can also be migrated from business routing (node A ⁇ node B ⁇ node C) to Service routing (node A ⁇ node D ⁇ node C).
- the change in the state of the network resource may include a change in the topology resource of the network device of the forwarding layer. It may also include changes in the link delay of each link in the forwarding layer that can execute the predetermined service.
- the topology resource change of the network device includes the link resources and/or the network device of the forwarding layer.
- the port resource has changed.
- the change in the topology resource of the network device includes at least one of the following changes:
- the change in the topology resource of the network device includes at least one of the following changes:
- the link alarm disappears (that is, the original obstacle, unavailable link, the obstacle is eliminated, and the link becomes available again), there is a new link, there is a port resource release, and there is a new port.
- the change of the network resource status of the forwarding layer includes:
- the link delay of the link capable of executing the predetermined service in the forwarding layer changes.
- the link delay of each of the above links can be determined by monitoring data whether the link delay of each of the above links has changed. Specifically, when the link delay changes, it can be determined whether the link delay increases or decreases according to the delay before the change and the delay after the change.
- the route calculation method may further include performing after step S110:
- step S115 a link list is generated according to the monitored network resource status, and the link list includes all links that can implement the monitored predetermined service.
- calculating the optimal route for the delay of the monitored scheduled service according to the changed network resource includes:
- step S121 the delay of each link in the link list is compared with the delay of the current link of the predetermined service
- step S122 the link with the best service delay is determined as the route with the best delay.
- step S121 the link list may be traversed to determine the optimal route with delay in step S122.
- the route calculation method provided in the first aspect of this application, it is possible to re-determine the optimal delay route of the monitored scheduled service when the network resource status of the forwarding layer changes, so as to ensure the optimal delay at all times. Prerequisites are provided for performing services on routing.
- the route calculation method provided in the first aspect of this application can be used to recalculate the optimal route with delay, which provides a basis for the execution of the business on the link with the optimal delay at all times.
- the data transmission method includes:
- step S210 the delay optimal route is determined according to a predetermined algorithm, where the predetermined algorithm is the above-mentioned route calculation method provided by this application;
- step S220 when a predetermined condition is met, the monitored predetermined service is migrated to the optimal route for delay.
- the data transmission method provided in this application is still executed by the SDN controller.
- the scheduled service being executed can be migrated to the delay optimal route, thereby ensuring that the service is not only delayed when the service is established.
- the execution on the optimal link can also ensure that the predetermined service can be executed on the optimal route with delay during the execution of the service, so that the efficiency of data transmission can be improved.
- the predetermined conditions are not particularly limited.
- the SND controller may execute to determine whether to switch the route of the predetermined service, or the SDN controller may send the information of the delay optimal route to the application layer, and the corresponding APP to determine whether to switch routes.
- the APP is actually installed on the terminal. In other words, the terminal sends a service creation instruction to the SDN controller through the APP.
- the data transmission method further includes:
- step S211 the time-delay optimal route is sent to a terminal in the application layer that creates a service creation instruction for the monitored predetermined service.
- the meeting the predetermined condition includes: receiving a route switching instruction sent by the terminal.
- the first type is that the APP installed on the terminal that executes the predetermined service and generates the service creation instruction determines whether the delay optimal route reaches a threshold, and if it reaches the threshold, sends the route switching instruction;
- the second type is to display the optimal route with time delay.
- the user inputs switching information through the APP installed on the terminal, and the APP converts the switching information into a route switching instruction, which is issued by the terminal to the SDN controller.
- the data transmission method includes performing before step S220:
- step S212 in response to the manual switching instruction sent by the application layer, the delay optimal route determined this time is compared with the delay optimal route reported when the predetermined service was executed last time;
- step S213 when the delay optimal route determined this time is different from the delay optimal route reported last time, the delay optimal route determined this time is reported to the application layer.
- the SDN controller determines whether to switch according to the comparison between the delay optimal route and the current route
- the second method is to determine whether to automatically switch the service route according to the configuration attribute of the predetermined service.
- the second case is described in detail below: when the application layer configures and creates the scheduled service, it configures the "automatic switch routing attribute" in the configuration attribute of the scheduled service. As long as the SDN controller can obtain this attribute, the current route can be switched to the route with the optimal delay.
- the conditions for performing step S210 are not particularly limited.
- the predetermined service may be a certain service designated by the user. As long as the predetermined service starts to be executed, step S210 is executed, that is, the route calculation method provided in the first aspect of the application is immediately executed.
- the predetermined service is a mail sending service designated by the user. As long as the mail sending service is executed, step S210 is executed.
- monitoring start instruction issued by the APP of the application layer can also be used as the triggering condition for executing step S210.
- the APP at the application layer issues a delay monitoring instruction
- the delay monitoring instruction includes a setting delay monitoring instruction and a service ID list.
- the SDN controller traverses the list of service IDs, determines the service being executed therein, and uses the service as the predetermined service. Then, step S210 is executed, that is, the route calculation method is executed for the predetermined service.
- the data transmission method may further include:
- the monitored service information is retrieved from the database.
- the SDN controller when the SDN controller restarts, it can automatically reply to the delay data before the SDN controller restarts, so that the response speed can be improved.
- the data transmission method includes:
- a service creation instruction is generated, the service creation instruction includes configuring delay monitoring information or canceling delay monitoring information, and the configuration delay monitoring information is used to control the SDN controller to execute the above-mentioned information provided in this application.
- a data transmission method where the cancellation delay monitoring information is used to control the SDN controller to stop executing the data transmission method according to any one of claims 7 to 11;
- step S320 a service creation instruction is sent to the SDN controller.
- the SDN controller can automatically migrate the predetermined service to the optimal route.
- the service creation instruction also includes the automatic switching routing information.
- the service creation instruction may also include non-automatic switching route information, and the non-automatic switching route is used to control the SDN controller to report the delay optimal route to the creation The terminal of the scheduled service. Further, it is reported to the APP installed on the terminal to create the predetermined service.
- the SDN controller may also send the configuration to the APP installed on the terminal after executing the above-mentioned data transmission method provided in this application according to the configuration delay monitoring information in the service creation instruction Success message.
- the SDN controller may also send configuration failure information to the APP installed on the terminal.
- the SDN controller when the SDN controller receives the cancellation of delay monitoring information, it stops executing the above data transmission method provided in this application, and stores the delay monitoring configuration information in the database, and installs it on the terminal
- the APP returns a successful modification message.
- a route calculation module is provided. As shown in FIG. 10, the route calculation module includes a monitoring unit 610 and a calculation unit 620. The route calculation module is used to execute the method described in the first aspect of the present application. The route calculation method provided.
- the monitoring unit 610 is used to monitor the network resource status of the forwarding layer
- the calculating unit 620 is used to monitor the predetermined service according to the changed network resource when the network resource status of the forwarding layer changes. Calculate the optimal route with delay.
- the state change of the network resource includes a change in the topology resource of the network device of the forwarding layer.
- the routing calculation module may include a data model unit 630, which is configured to, after receiving a notification that the topology resource of the network device changes, change the topology resource of the network device before the resource change, and the resource after the resource change.
- the topology resource of the network device is encapsulated, a topology resource change notification is generated, and the topology resource change notification is sent to the monitoring unit 610.
- the calculation unit 620 is configured to analyze the topology resource change notification, and store the delay optimal route in the memory.
- the change in the topology resource of the network device includes the change in the link resource and/or the port resource of the network device of the forwarding layer.
- the change in the topology resource of the network device includes at least one of the following changes:
- Link alarm disappears, there is a new link, there is a port resource release, and there is a new port.
- the storage form of the delay optimal route in the memory is not particularly limited.
- the storage form may be Map ⁇ service_id, delaymonitorinfo>.
- the specific form of the calculation unit 620 is not particularly limited.
- the calculation unit 620 may include a delay calculation subunit 621, a delay routing subunit 622, and a delay measurement subunit 623.
- the delay measurement subunit 623 is configured to calculate the delay of all links capable of executing the predetermined service according to the received network resource status.
- the delay routing subunit 622 is configured to select the optimal route for delay according to the calculation result of the delay calculation subunit 621.
- the delay calculation subunit 621 may generate a link list according to the monitored network resource state.
- the time delay routing sub-unit 622 can traverse the monitored service information list, and retrieve the monitored scheduled service from it.
- the delay routing subunit 622 may also compare the current route of the predetermined service with the link delay in the link list, and determine whether the link delay of the link in the list is better than the current route. To determine the optimal route for the delay.
- the SDN controller provided in the fifth aspect of this application is used to execute the data transmission method provided in the second aspect of this application.
- the SDN controller includes a routing calculation module 710 and a switching module 720 provided in the fourth aspect of the present application.
- the route calculation module 710 is used to calculate the route calculation method provided in the first aspect of the present application.
- the switching module is configured to perform step S210, that is, when a predetermined condition is met, the monitored predetermined service is migrated to the optimal route for delay.
- the data transmission method includes sending the delay optimal route to an application APP in the application layer that creates the monitored predetermined service.
- the SDN controller may further include a delay notification module 730, which is configured to execute the "send the delay optimal route to the application layer to create the monitored predetermined service.
- Application APP steps.
- the SDN controller may further include a service processing module 740, which is configured to allocate various resources, perform route calculation, and cross-connect devices at the forwarding layer.
- a service processing module 740 which is configured to allocate various resources, perform route calculation, and cross-connect devices at the forwarding layer.
- the SDN controller may also include a database storage module 750, which is used to add, delete, modify, and query various data, provide various data access interfaces, and provide Access interfaces to various databases, providing data access resource pools and data factories, etc.
- a database storage module 750 which is used to add, delete, modify, and query various data, provide various data access interfaces, and provide Access interfaces to various databases, providing data access resource pools and data factories, etc.
- an SDN controller including: a storage module storing an executable program; one or more processors, the one or more processors calling the executable program, so that The one or more processors implement the foregoing routing calculation method provided in the first aspect of the present application, or enable the one or more processors to implement the foregoing data transmission method provided in the second aspect of the present application.
- an SDN control system including: a northbound control management layer 120, the northbound control management layer 120 is used to communicate with the application layer; a southbound service layer 130, the southbound service layer 130 Used to communicate with the forwarding layer 300; the above-mentioned SDN controller 100 provided in this application.
- the SDN controller 100 can calculate the optimal route for the delay of the currently executing service according to the network resource status of the forwarding layer 300, thereby improving the efficiency of data transmission.
- the specific structure of the northbound control management layer 120 is not particularly limited.
- the northbound control management layer 120 includes a northbound interface module 121, a feedback module 122, and a conversion module. 123.
- the northbound interface module 121 can implement at least one of the following functions: APP and SDN controller interface conversion, YANG file definition, protobuf file definition, RPC method definition, byte order conversion, notification of execution result messages, Monitoring and so on.
- the feedback module 122 realizes feedback of SDN controller status information, link discovery information, service routing information, service migration information, service return information, link delay information, link recovery information, and real-time topology information to the network management personnel.
- feedback the controller supervision communication status to the network management personnel such as detecting a controller supervision failure, promptly send an alarm to the user, prompting to restart the SDN controller supervision or maintain the controller supervision.
- the conversion module 123 is mainly used to implement the message sent by the APP, such as JSON message, through the northbound adaptation into the data format returned by window maintenance, simulated cutover, fiber cutover, and cutover, such as the data format defined by the YANG file Wait.
- the data format of window maintenance, simulated cutover, fiber cutover, and cutover return report is converted to APP data format and reported, such as converted to JSON data format for reporting.
- the northbound control management layer 120 may also include other reserved applications 124 to monitor the controller, implement the controller software upgrade, enable the log function, and check for memory leaks. , Realize at least one of the functions of controller supervision restart and maintenance, and receiving controller selection and designation from maintenance personnel.
- the southbound service layer 130 implements communication between the SDN controller and the forwarding layer through various southbound protocols (including but not limited to netconf, P4, openflow, etc.).
- the SDN controller is based on a microservice framework.
- the monitoring unit and the routing calculation unit in the SDN controller can be released in the form of microservices.
- the specific method of the microservice is not particularly limited.
- the monitoring unit and the routing calculation unit may be released based on the paaS microservice.
- the SDN controller provided by the present application is based on a microservice framework, the coupling degree between various functional modules is low, and each functional module has the advantages of independence, easy expandability, and easy and difficult attributes.
- microservice framework means that the north and south directions of the SDN controller are implemented by microservices, and each module, unit, and subunit of the SDN controller is a microservice.
- the northbound protocol or tools of the SDN controller are also microservices.
- the northbound protocol or disclosure of the SDN controller includes but not limited to restful, gRPC, tapi, yangtools and other protocols or interfaces, so that even if there are different versions of tapi or yangtools It can also exist at the same time without interfering with each other.
- the SDN controller will not cause incompatibility between new and old functions due to interface changes, and it may also achieve a smooth upgrade of the SDN controller functions.
- southbound protocols there are multiple southbound protocols in the southbound of the SDN controller, and different southbound protocols are released in the form of a microservice. Different versions of the same southbound protocol can exist at the same time, so as to realize the smooth support of the SDN controller for new and old products. At the same time, each southbound agreement facilitates migration to other projects and improves scalability. Since each microservice is easy to uninstall, when a new product is released, unnecessary microservices can be easily removed, which ensures the lightweight of the SDN controller.
- the architecture of the application layer 200 is not specifically limited.
- the applications in the application layer may include:
- Security applications are mainly security service applications accessed in the network, and are used to establish a security defense mechanism for the network;
- Network management/APP application the network management application is specifically an application accessed by the network manager, and the network management is used for network management and monitoring;
- the command line application is specifically an application accessed by the controller manager, through the command line reserved by the controller (not open source) to realize the configuration, query and other operations of the controller, and realize some verification and debugging Features.
- the third-party applications refer to conventional applications that have third-party access, and are used to implement custom functions by calling the open source application programming interface (API, Application Program Interface) of the SDN controller.
- API Application Program Interface
- a computer-readable storage medium is provided with an executable program stored thereon, and when the executable program is invoked, it can implement the routing calculation method provided in the first aspect of the present application or The data transmission method provided by the second aspect of this application.
- the terminal device includes an instruction generating module 810 and an instruction sending module 820.
- the instruction generation module 810 is configured to perform step S310, that is, the instruction generation module 810 is configured to generate a service creation instruction, where the service creation instruction includes configuration delay monitoring information or cancel delay monitoring information, and the configuration delay monitoring information is used for
- the SDN controller is controlled to execute the above data transmission method provided in this application, and the cancellation delay monitoring information is used to control the SDN controller to stop executing the above data transmission method provided in this application.
- the instruction sending module 820 is configured to perform step S320, that is, the instruction sending module 820 is configured to send a service creation instruction to the SDN controller.
- a computer-readable storage medium on which an executable program is stored, and when the executable program is invoked, the above-mentioned service processing method provided by the present application can be implemented.
- the computer-readable storage medium includes volatile and non-volatile, removable, and removable and non-volatile memory devices implemented in any method or technology for storing information (such as computer-readable instructions, data structures, program modules, or other data).
- the media cannot be removed.
- Computer-readable storage media include but are not limited to RAM, ROM, EEPROM, flash memory or other memory technologies, CD-ROM, digital versatile disk (DVD) or other optical disk storage, magnetic cassettes, magnetic tapes, magnetic disk storage or other magnetic storage media, Or any other medium that can be used to store desired information and that can be accessed by a computer.
- Fig. 12 is a flowchart of executing the service creation method provided in Embodiment 1 of the present application in an SDN network, and the specific steps are as follows:
- step 5-1 the terminal device installed with the APP sends a user request to the northbound interface module of the SDN control system through the APP.
- the user request includes a delay operation instruction.
- the method of sending the user request includes but is not limited to restful, gRPC, Protocol interfaces such as http.
- the northbound interface module sends a service creation request to the northbound adaptation module.
- the northbound adaptation module receives the maintenance window creation request of the APP, adapts it to the maintenance window creation request, and sends the request to the northbound adaptation module.
- the conversion module of the control management layer is converted into a data structure type message that the SND controller can handle.
- step 5-3 the SDN controller determines whether to perform delay monitoring services according to the converted service creation request. If so, go to step 5-4, otherwise go to step 5-5.
- step 5-4 the service delay monitoring is configured through the SDN controller, and the delay monitoring information is set in the input object configuration of the created service.
- step 5-5 determine whether the configuration service automatically optimizes the route by analyzing the user request, and whether the configuration of the input object of the creation/modification service automatically optimizes the information.
- steps 5-6 create/modify the business, and execute the normal creation or modification of the business process.
- the delay routing subunit stores the business information in the memory and the database, and the delay module saves the business ID information in the memory to improve the speed of business optimization, and saves the business ID in the database so that the controller can restart the data restore.
- FIG. 13 is a flowchart of batch modification of service delay monitoring configuration in Embodiment 2 of the application.
- step 6-1 the terminal installed with the APP sends a batch modification of the delay monitoring configuration to the SDN controller through the APP, and the APP sends a user request indicating the batch delay monitoring configuration for non-created services to the SDN controller.
- the user request needs to include but is not limited to setting or canceling time delay monitoring information, including automatic or non-automatic replacement service information, including a list of service IDs, etc.
- the SDN controller removes the service ID option from the memory Map ⁇ service_id, delaymonitorinfo>, stores the cancellation delay monitoring configuration information in the database, and returns the success or failure information of each modification.
- step 6-2 the SDN controller traverses the service list B;
- step 6-3 take out the currently executing scheduled service B1;
- step 6-4 it is judged whether the current route of the predetermined service B1 is the route with optimal delay
- step 6-4 When the judgment result in step 6-4 is yes, execute step 6-5, and when the judgment result in step 6-4 is no, execute step 6-7;
- step 6-5 the northbound microservice module calls the data storage interface, stores the optimal route with delay in the database, and returns information about the success or failure of each modification;
- steps 6-7 it is judged whether the business list B has been traversed
- step 6-7 When the judgment result in step 6-7 is yes, end; when the judgment result in step 6-7 is no, skip to step 6-2.
- step 6-6 if the storage is successful, the northbound calls the delay monitoring module to modify the memory of the monitored service ID maintained in the memory, and then stores the service ID and delay monitoring information in the memory, such as Map ⁇ service_id,delaymonitorinfo> .
- the storage method is to store the business ID, whether it is automatically replaced, the pre-calculation result is placed in a class DelayMonitorInfo.java, and then stored in a Map ⁇ service_id,delaymonitorinfo> method to facilitate the maintenance of the delay configuration information, and return the configuration success or failure result .
- FIG. 14 is a flowchart of route selection for resource increase delay in Embodiment 3 of this application.
- the data model unit receives the change in the topology resource of the network device at the forwarding layer and sends a resource change notification.
- the data model unit receives the notification of the change in the topology resource of the network device. Encapsulate information such as notifications after changes, and send notifications of link and port resource changes, including but not limited to link alarm disappearance, new links, port resources are released, and ports are newly added;
- step 7-2 the monitoring unit monitors the data change notification and confirms that it is an increase in capital.
- the monitoring unit of the time-delay microservice monitors the above notification, analyzes the new resource information, and processes different resources differently. Coexist in the delay memory object.
- the memory can be but not limited to the situation of Map ⁇ service_id,delaymonitorinfo>.
- step 7-3 the delay routing subunit obtains the service information list B subject to delay monitoring from the memory, and the delay routing subunit obtains the service information list B subject to delay monitoring from the memory Map ⁇ service_id, delaymonitorinfo>.
- step 7-3 the delay routing subunit obtains the service information list B subject to delay monitoring from the memory, and the delay routing subunit obtains the service information list B subject to delay monitoring from the memory Map ⁇ service_id, delaymonitorinfo>.
- step 7-4 and step 7-5 traverse the service information list B subject to time delay monitoring, and take out the current service B1.
- step 7-6 the pre-calculation determines whether there is a better route, and the pre-calculation is performed according to the service B1 information to determine whether the pre-calculation has a better route, if yes, go to step 7-7, if not, go to step 7-10.
- step 7-7 determine whether the service is automatically replaced.
- step 7-7 If the judgment result in step 7-7 is yes, go to step 7-8, and if the judgment result in step S7-7 is no, go to step 7-11.
- steps 7-8 the optimized replacement of service B1 is performed, and the delay module calls the service module interface to realize the optimized replacement of the service.
- the result of route optimization is reported to the APP, and the delay module sends a notification to the northbound structure module.
- the northbound structure module After receiving the notification, the northbound structure module sends a notification to the APP to notify the APP of the result of the route optimization.
- step 7-10 it is judged whether the traversal of service list B is completed.
- step 7-10 If the result of the judgment in step 7-10 is yes, it ends, and if the result of the judgment in step 7-10 is no, then go to step 7-4.
- the pre-calculation result is reported to the APP, and the SDN controller calls the pre-calculation interface. If the pre-calculation is successful, compare the pre-calculated routing delay and the current service routing delay which is better, such as the pre-calculated routing time The delay is better, and then it is compared whether the pre-calculated route is the same as the one reported last time. If not, the calculated route with the optimal delay is reported to the APP.
- the APP prompts the user whether the path is optimized.
- step 7-12 If the result in step 7-12 is yes, go to step 7-13, and if the result in step 7-12 is no, go to step 7-5.
- the APP calls the interface for creating a preset path, the path calculation module generates an available path, and returns the result to the APP.
- step 7-14 APP calls the interface for executing path optimization, executes the path rerouting function according to the path generated by calculating the path in steps 7-13, and returns the result to APP.
- the APP calls the delete preset path interface, releases the resources, and returns the result to the APP.
- FIG. 15 is a flowchart of route selection for link change delay in Embodiment 4 of this application.
- step 8-1 the data model unit receives the change of the device topology resource and sends a resource change notification.
- the data model unit receives the notification of the change of the device topology resource. After analysis, it will notify the resource before and after the change, etc. Encapsulate information and send notifications of link and port resource changes.
- step 8-2 the monitoring unit monitors the data change notification and confirms that the link delay has changed, including but not limited to subtracting the delay before the change and the delay after the change. , To determine whether the link delay increases or decreases.
- step 8-3 the time delay routing subunit listens to the notification of the link change, and generates a link list A.
- step 8-4 the delay routing subunit obtains the service information list B subject to delay monitoring from the memory.
- step 8-5 traverse the business list B.
- step 8-6 the current business B1 is retrieved from the business list B.
- step 8-7 compare link list A to determine whether service B1 has increased link delay. If the result of the judgment in step 8-7 is yes, then go to step 8-9, if step 8- If the judgment result in 7 is no, then go to step 8-8.
- step 8-8 determine whether there is a reduced link in the link list A that is not on service B1. If the result of the determination in step 8-8 is yes, then go to step 8-9, if step 8-8 If the judgment result in is no, go to step 8-18.
- step 8-9 the pre-calculation determines whether there is a better route, and the controller calls the pre-calculation interface. If it is determined in step 8-9 that there is a better route, then go to step 8-10, if in step 8-9 If there is no better route, go to step 8-18.
- step 8-10 judge whether the service is automatically replaced. If the judgment result of step 8-10 is yes, then perform business optimization replacement. If the judgment result of step 8-10 is no, then go to step 8-13 .
- steps 8-11 the business optimization replacement is performed, and the switching module invokes the service module interface to implement the business optimization replacement.
- the route optimization result is reported to the APP, and the delay module sends a notification to the northbound module. After the northbound module receives the notification, it sends a notification to the APP to notify the APP of the route optimization result.
- the pre-calculation result is reported to the APP, and the SDN controller calls the pre-calculation interface. If the pre-calculation is successful, compare the pre-calculated routing delay and the current service routing delay which is better, such as the pre-calculated routing time The delay is better, and then compare whether the pre-calculated route is the same as the one reported last time. If it is not the same, report the new route to the APP.
- step 8-14 the APP prompts the user whether to optimize the path. If the user selects "Yes” is received, then go to step 8-15, and if the user selects "No” is received, then go to step 8-18.
- the APP calls the interface for creating a preset path, calculates the path to generate an available path, and returns the result to the APP.
- step 8-16 APP calls the interface for executing path optimization, calculates the path generated in step 8-5, executes the path rerouting function, and returns the result to APP.
- the APP calls the delete preset path interface, releases the resources of the path calculation, and returns the result to the APP.
- step 8-18 it is judged whether the traversal of the business list B is completed, if the judgment result in step 8-18 is "Yes", the end is finished, if the judgment result in step 8-18 is otherwise, go to step 8-5 and continue Traverse the business.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
本申请提供一种路由计算方法,应用于SDN控制器,所述路由计算方法包括:监听转发层的网络资源状态;在所述转发层的所述网络资源状态发生变化的情况下,根据变化后的网络资源为受监控的预定业务计算时延最优路由。本申请还提供一种数据传输方法、一种业务处理方法、一种路由计算模块、一种SDN控制器、一种计算机可读存储介质和一种终端设备。
Description
相关申请的交叉引用
本申请基于申请号为201911396549.6、申请日为2019年12月30日的中国专利申请提出,并要求该中国专利申请的优先权,该中国专利申请的全部内容在此以引入方式并入本申请。
本申请涉及软件定义网络领域(SDN,Software Defined Network),具体地,涉及一种路由计算方法、一种数据传输方法、一种业务处理方法、一种SDN控制器、一种终端、一种计算机可读存储介质。
SDN是一种开放的网络架构,主要特点为集中控制性和网络可编程性,允许网络管理人员以软件编程的方式对整个网络进行管理和操作。
SDN网络中,逻辑控制功能和数据转发功能是分离的,基于软件的网络控制器实现对网络的逻辑控制功能。
目前的SDN网络具有时延选路的功能,即,可以在建立业务时,自动对实现该业务的两个节点之间的各种路由的时延进行测算和排序,从而可以自动选出时延最优的路由。
但是,在使用相关技术中时延选路方法的情况下,数据传输效率仍然有待进一步提高。
发明内容
本申请的目的在于提供一种路由计算方法、一种数据传输方法、一种业务处理方法、一种SDN控制器、一种终端、一种计算机可读存储介质。
为了实现上述目的,作为本申请的一个方面,提供一种路由计算方法,应用于SDN控制器,所述路由计算方法包括:监听转发层的网络资源状态;在所述转发层的所述网络资源状态发生变化的情况下,根据变化后的网络资源为受监控的预定业务计算时延最优路由。
作为本申请的第二个方面,提供一种数据传输方法,应用于SDN控制器,所述数据传输方法包括:根据预定算法确定受监控的预定业务的所述时延最优路由,其中,所述预定算法为本申请所提供的上述路由计算方法;在满足预定条件的情况下,将受监控的所述预定业务迁移至所述时延最优路由。
作为本申请的第三个方面,提供一种业务处理方法,包括:生成业务创建指令,所述业务创建指令包括配置时延监控信息或者取消时延监控信息,所述配置时延监控信息用于控制所述SDN控制器执行本申请所提供的上述数据传输方法,所述取消时延监控信息用于控制所述SDN控制器停止执行所述数据传输方法;向SDN控制器发送业务创建指令。
作为本申请的第四个方面,提供一种路由计算模块,包括:监听单元,用于监听转发层的网络资源状态;计算单元,用于在所述转发层的所述网络资源状态发生变化的情况下,根据变化后的网络资源为受监控的预定业务计算时延最优路由。
作为本申请的第五个方面,提供一种SDN控制器,包括:存储模块,存储有可执行程序;一个或多个处理器,所述一个或多个处理器调用所述可执行程序,使得所述一个或多个处理器实现本申请所提供的上述路由计算方法,或者,使得所述一个或多个处理器实现本申请所提供的上述数据传输方法。
作为本申请的第六个方面,提供一种计算机可读存储介质,其上存储有可执行程序,当所述可执行程序被调用时能够实现本申请所提供的上述路由计算方法或者本申请所提供的上述数据传输方法。
作为本申请的第七个方面,提供一种终端设备,包括:指令生成模块,用于生成业务创建指令,所述业务创建指令包括配置时延监控信息或者取消时延监控信息,所述配置时延监控信息用于控制所述SDN控制器执行本申请所提供的上述数据传输方法,所述取消时延监控信息用于控制所述SDN控制器停止执行本申请所提供的上述所述的数据传输方法;指令发送模块,用于向SDN控制器发送业务创建指令。
作为本申请的第八个方面,提供一种计算机可读存储介质,其上存储有可执行程序,当所述可执行程序被调用时能够实现本申请所提供的上述业务处理方法。
附图是用来提供对本申请的进一步理解,并且构成说明书的一部分,与下面的具体实施方式一起用于解释本申请,但并不构成对本申请的限制。在附图中:
图1是本申请所提供的路由计算方法的一种实施方式的流程图;
图2是SDN网络的架构示意图;
图3是但业务重路由的示意图;
图4是多业务重路由的示意图;
图5是本申请所提供的路由计算方法的另一种实施方式的流程图;
图6是本申请所提供的数据传输方法的一种实施方式的流程图;
图7是本申请所提供的数据传输方法的另一种实施方式的流程图;
图8是本申请提供的业务创建方法的一种实施方式的流程图;
图9是本申请所提供的SDN控制器模块示意图;
图10是本申请所提供的SDN系统的示意图;
图11是本申请所提供的终端设备的模块示意图;
图12是本申请实施例1的流程图;
图13是本申请实施例2的流程图;
图14是本申请实施例3的流程图;
图15是本申请实施例4的流程图。
以下结合附图对本申请的具体实施方式进行详细说明。应当理解的是,此处所描述的具体实施方式仅用于说明和解释本申请,并不用于限制本申请。
相关技术中数据传输效率仍然较低的原因如下:
SDN网络中,转发层的链路状态总是处于变化状态。利用相关技术中所公开的方法传输数据时,只能保证业务建立时刻的时延是最优的。在转发层的网络资源状态保持和业务建立时刻一致时,那么业务建立时刻的业务路由便是最优的。可是一旦所述转发层中出现了链路状态变化,即无法确所述业务的当前路由的时延仍然是最优的。
本申请提供一种路由计算方法、一种数据传输方法、一种业务处理方法、一种SDN控制器、一种终端、一种计算机可读存储介质。所述路由计算方法可以使得在业务开始后仍然处于时延最优链路上。
有鉴于此,作为本申请的第一个方面,提供一种基于SDN网络的路由计算方法,如图1所示,所述路由计算方法包括:
在步骤S110中,监听转发层的网络资源状态;
在步骤S120中,在转发层的网络资源状态发生变化的情况下,根据变化后的网络资源为受监控的预定业务计算时延最优路由。
如图2中所示,SDN网络包括应用层100、SDN控制器200、转发层300三个部分,本申请所提供的路由计算方法由SDN控制器100所执行。SDN控制器200通过北向接口与应用层100通信,SDN控制器200通过南向接口与转发层300通信。在一个示例中,SDN网络还可以包括数据库400。
在本申请所提供的路由计算方法中,通过步骤S110中监听转发层的网络资源状态,一旦转发层300的网络资源状态发生变化,那么转发层300中各个能够执行所述预定业务的链路的链路时延也会发生变化。在步骤S120中为受监控的预定业务重新计算时延最优路由。
计算出所述时延最优路由后,可以由用户手动将所述预定业务切换至所述时延最优路由,也可以通过SDN控制器自动地将所述预定业务切换至所述时延最优路由。
由此可知,如果在执行业务的过程中,利用本申请所提供的路由计算方法计算时延最优路由、并根据结果将业务切换孩子所述时延最优路由,即可确保在整个业务执行的过程中,业务用于在时延最优的路由上,从而可以提高执行业务的效率。
下面以图3为例对本申请所提供的路由计算方法进行解释。
假定所述预定业务(即,待优化业务1)的当前路由为业务路由(节点A→节点B→节点C)(即,图3中的业务1所在路由),所述转发层中的网络资源状态发生变化后,计算出所述预定业务的时延最优路由为业务路由(节点A→节点D→节点C)(即,图3中业务1待迁移路由)。用户可以手动地将所述预定业务从业务1所在路由切换至业务1待迁移路由,也可以由所述SDN控制器自动地将所述预定业务从当前路由切换至业务1待迁移路由。在业务开始时, 业务路由1是时延最优路由,当网络资源状态发生变化时,业务路由(节点A→节点D→节点C)变成时延最优路由。将业务从业务路由(节点A→节点B→节点C)切换至(节点A→节点D→节点C),可以确保在执行业务的过程中,始终时延最优。
需要指出的是,图3中所示的实施方式是单业务重路由的示意图,也就是说,对一个业务进行监控。但是,本申请并不限于此,可以同时对多个业务进行监控。例如,如图4中所示,可以对两个业务进行监控。同时为这两个业务计算时延最优路由。业务1可以从业务路由(节点A→节点B→节点C)迁移至业务路由(节点A→节点D→节点C),业务2也可以从业务路由(节点A→节点B→节点C)迁移至业务路由(节点A→节点D→节点C)。
在本申请中,对所述网络资源状态发生变化的具体情况不做特殊的限定,作为一种可选实施方式,所述网络资源状态发生变化可以包括所述转发层的网络设备拓扑资源发生变化,也可以包括转发层中能够执行所述预定业务的各个链路的链路时延发生变化。
在本申请中,对“网络设备拓扑资源发生变化”的类型不做特殊的限定,在一个示例中,所述网络设备拓扑资源发生变化包括所述转发层的网络设备的链路资源和/或端口资源发生变化。
进一步地,所述网络设备拓扑资源发生变化包括以下变化中的至少一者:
链路资源的增加、链路资源的减少、端口资源的释放、端口资源的占用、新增端口、端口减少。
进一步地,所述网络设备拓扑资源发生变化包括以下变化中的至少一者:
链路告警消失(即,原本存在障碍、不可用的链路中,障碍消除,重新变成可用链路)、存在新增链路、存在端口资源释放、存在新增端口。
如上文中所述,所述转发层的网络资源状态发生变化包括:
所述转发层中能够执行所述预定业务的链路的链路时延发生变化。
在监听网络资源状态时,可以通过监听数据的方式判断上述各个链路的链路时延是否发生变化。具体地,当链路时延发生变化时,可以根据变化前时延(before delay)和变化后时延(after delay)来确定链路的时延是增加了还是减小了。
为了便于确定所述时延最优路由,在一个示例中,所述路由计算方法还可以包括在步骤S110之后进行的:
在步骤S115中,根据监听到的网络资源状态生成链路列表,所述链路列表包括所有能够实现受监控的预定业务的链路。
相应地,根据变化后的网络资源为受监控的预定业务计算时延最优路由包括:
在步骤S121中,将所述链路列表中的各个链路的时延与所述预定业务的当前链路的时延进行比较;
在步骤S122中,将业务时延最优的链路确定为所述时延最优路由。
在执行步骤S121时,可以遍历所述链路列表,以在步骤S122中确定所述时延最优路由。
利用本申请第一个方面所提供的路由计算方法,可以在转发层的网络资源状态发生变化时,重新确定受监控的预定业务的时延最优路由,从而为保证时刻在时延最优的路由上执行业务提供了前提条件。
一旦转发层中的网络资源状态发生变化,即可通过本申请第一个方面所提供的路由计算方法重新计算时延最优路由,为业务时刻在时延最优的链路上执行提供了基础。
作为本申请的第二个方面,提供一种数据传输方法,如图4所示,所述数据传输方法包括:
在步骤S210中,根据预定算法确定所述时延最优路由,其中,所述预定算法为本申请所提供的上述路由计算方法;
在步骤S220中,在满足预定条件的情况下,将受监控的预定业务迁移至所述时延最优路由。
本申请所提供的数据传输方法仍然由SDN控制器所执行。在本申请所提供的数据传输方法中,只要满足了预定条件,即可将正在执行的预定业务迁移至所述时延最优路由,从而可以确保所述业务不仅在业务建立的时刻在时延最优的链路上执行,也可以保证在业务执行过程中,可以在时延最优路由上执行所述预定业务,从而可以提高数据传输的效率。
在本申请中,对所述预定条件并不做特殊的限定。作为一种可选实施方式,可以由SND控制器执行判断是否切换所述预定业务的路由,也可以由SDN控 制器将所述时延最优路由的信息发送至应用层,由应用层的相应APP来判断是否切换路由。需要指出的是,APP其实是安装在终端上的。换言之,终端通过所述APP向SDN控制器发送业务创建指令。
相应地,在步骤S220之前,所述数据传输方法还包括:
在步骤S211中,将所述时延最优路由发送至应用层中创建受监控的所述预定业务的业务创建指令的终端。
相应地,所述满足预定条件包括:接收到所述终端发送的路由切换指令。
需要指出的是,所述路由切换指令虽然是终端发出的,但是,仍然存在两种情况:
第一种、执行所述预定业务的终端上安装的生成所述业务创建指令的APP判断所述时延最优路由是否达到门限值,如果达到门限值,则发送所述路由切换指令;
第二种、显示所述时延最优路由,由用户通过终端上安装的APP输入切换信息,APP将所述切换信息转换为路由切换指令,并由所述终端下发至SDN控制器。
如果需要应用层下发所述路由切换指令,就需要将计算获得的时延最优路由上报至应用层。为了节约网络资源,在一个示例中,所述数据传输方法包括在步骤S220之前进行的:
在步骤S212中,响应于应用层发送的手动切换指令,将本次确定的时延最优路由与上次执行所述预定业务时上报的时延最优路由进行对比;
在步骤S213中,当本次确定的时延最优路由不同于上次上报的时延最优路由时,将本次确定的时延最优路由上报至应用层。
在SDN控制器自行决定是否切换业务路由的情况中,仍然包括两种具体情况:
第一种、SDN控制器根据时延最优路由与当前路由之间的对比情况执行确定是否切换;
第二种、根据所述预定业务的配置属性来确定是否自动切换业务路由。
下面详细说明第二种情况:应用层在配置创建所述预定业务时,在所述预定业务的配置属性中配置“自动切换路由属性”。只要SDN控制器能够获取到该属性,即可将当前路由切换至所述时延最优路由。
在本申请中,对执行步骤S210的条件并不做特殊的限定。例如,所述预定业务可以是用户指定的某一项业务,只要该预定业务开始执行,就执行步骤S210, 也即,即刻执行本申请第一个方面所提供的路由计算方法。
例如,所述预定业务为用户指定的邮件发送业务。只要执行了邮件发送业务,就执行步骤S210。
当然,也可以根据应用层的APP下发的监控开始指令作为执行步骤S210的触发条件。
例如,应用层的APP下发时延监控指令,该时延监控指令包括设置时延监控指令、以及业务ID列表。
SDN控制器遍历业务ID列表,确定其中正在执行的业务,并将该业务作为所述预定业务。随后执行步骤S210,即,针对该预定业务执行路由计算方法。
在一个示例中,所述数据传输方法还可以包括:
响应于SDN控制器重启指令,从数据库中调取受监控的业务信息。也就是说,在SDN控制器重启时,能够自动回复SDN控制器重启前的时延数据,从而可以提高响应速度。
作为本申请的第三个方面,提供一种业务处理方法,其中,如图5所示,该数据传输方法包括:
在步骤S310中,生成业务创建指令,所述业务创建指令包括配置时延监控信息或者取消时延监控信息,所述配置时延监控信息用于控制所述SDN控制器执行本申请所提供的上述数据传输方法,所述取消时延监控信息用于控制所述SDN控制器停止执行权利要求7至11中任意一项所述的数据传输方法;
在步骤S320中,向SDN控制器发送业务创建指令。
如上文中所述,当预定业务的配置属性包括自动切换路由信息时,SDN控制器可以自动将所述预定业务迁移至所述最优路由。相应地,所述业务创建指令还包括所述自动切换路由信息。
当然,本申请并不限于此,所述业务创建指令还可以包括非自动切换路由信息,所述非自动切换路由用于控制所述SDN控制器将所述时延最优路由上报至创建所述预定业务的终端。进一步地,上报至所述终端上安装的创建所述预定业务的APP。
为了便于操作人员监控,所述SDN控制器还可以在根据所述业务创建指令中的配置时延监控信息、执行本申请所提供的上述数据传输方法后,向所述终 端上安装的APP发送配置成功信息。当然,如果所述SDN控制器接收到配置时延监控信息、却无法执行本申请所提供的上述数据传输方法时,会向所述终端上安装的APP发送配置失败信息。
如上文中所述,当所述SDN控制器接收到取消时延监控信息时,停止执行本申请所提供的上述数据传输方法,并且将时延监控配置信息存入数据库,并向所述终端上安装的APP返回修改成功信息。
作为本申请的第四个方面,提供一种路由计算模块,如图10所示,该路由计算模块包括监听单元610和计算单元620,所述路由计算模块用于执行本申请第一个方面所提供的路由计算方法。
具体地,监听单元610用于监听转发层的网络资源状态,计算单元620用于在所述转发层的所述网络资源状态发生变化的情况下,根据变化后的网络资源为受监控的预定业务计算时延最优路由。
上文中已经对所述路由计算方法的工作原理以及有益效果进行了详细的描述,这里不再赘述。
如上文中所述,所述网络资源的状态变化包括所述转发层的网络设备拓扑资源发生变化。相应地,所述路由计算模块可以包括数据模型单元630,该数据模型单元630用于在接收到所述网络设备拓扑资源发生变化的通知后,将资源变化前的网络设备拓扑资源、资源变化后的网络设备拓扑资源封装,生成拓扑资源变化通知,并将该拓扑资源变化通知发送至监听单元610。计算单元620用于对所述拓扑资源变化通知进行分析,并将时延最优路由存在内存中。
如上文中所述,所述网络设备拓扑资源发生变化包括所述转发层的网络设备的链路资源和/或端口资源发生变化。
进一步地,所述网络设备拓扑资源发生变化包括以下变化中的至少一者:
链路告警消失、存在新增链路、存在端口资源释放、存在新增端口。
在本申请中,对所述时延最优路由在内存中的存储形式不做特殊的限定,作为一种可选实施方式,所述存储形式可以为Map<service_id,delaymonitorinfo>。
在本申请中,对计算单元620的具体形式也不做特殊限定。作为一种可选实施方式,计算单元620可以包括时延计算子单元621、时延选路子单元622和时延测量子单元623。
具体地,时延测量子单元623用于根据接收到的网络资源状态计算所有能够执行所述预定业务的链路的时延。时延选路子单元622用于根据时延计算子单元621的计算结果选择出所述时延最优路由。
如上文中所述,在执行所述路由计算方法时,时延计算子单元621可以根据监听到的网络资源状态生成链路列表。时延选路子单元622可以遍历受监控的业务信息列表,从中取出受监控的预定业务。并且,时延选路子单元622还可以将所述预定业务的当前路由与所述链路列表中的链路时延进行对比,并根据列表中的链路的链路时延是否优于当前路由的时延来确定所述时延最优路由。
作为本申请还提供一种SDN控制器,本申请第五个方面所提供的SDN控制器用于执行本申请第二个方面所提供的数据传输方法。如图10所示,该SDN控制器包括本申请第四个方面所提供的路由计算模块710和切换模块720。
如上文中所述,路由计算模块710用于计算本申请第一个方面所提供的路由计算方法。此处,切换模块用于执行步骤S210,即,在满足预定条件时,将受监控的预定业务迁移至所述时延最优路由。
如上文中所述,所述数据传输方法包括将所述时延最优路由发送至应用层中创建受监控的所述预定业务的应用程序APP。相应地,所述SDN控制器还可以包括时延通知模块730,该时延通知模块730用于执行该“将所述时延最优路由发送至应用层中创建受监控的所述预定业务的应用程序APP”的步骤。
在一个示例中,所述SDN控制器还可以包括业务处理模块740,该业务处理模块740用于实现分配各种资源、进行算路、并给转发层的设备下交叉。
在一个示例中,所述SDN控制器还可以包括数据库存储模块750,该数据库存储模块750用于实现对各种数据的增、删、改、查等,提供各种数据访问的接口,并提供对各种数据库的访问接口,提供数据访问资源池和数据工厂等。
作为本申请的第五个方面,提供一种SDN控制器,包括:存储模块,存储有可执行程序;一个或多个处理器,所述一个或多个处理器调用所述可执行程序,使得所述一个或多个处理器实现本申请第一个方面所提供的上述路由计算方法,或者,使得所述一个或多个处理器实现本申请第二个方面所提供的上述数据传输方法。
作为本申请还提供一种SDN控制系统,如图10所示,包括:北向控制管理层120,该北向控制管理层120用于与应用层通信;南向服务层130,该南向服务层130用于与转发层300通信;本申请所提供的上述SDN控制器100。
如上文中所述,SDN控制器100可以根据转发层300的网络资源状态,为当前正在执行的业务计算时延最优路由,从而可以提高数据传输的效率。
在本申请中,对北向控制管理层120的具体结构不做特殊的限定,例如,在图10中所示的实施方式中,北向控制管理层120包括北向接口模块121、反馈模块122、转换模块123。
北向接口模块121可以实现以下功能中的至少一者:APP和SDN控制器接口的转换、YANG文件的定义、protobuf文件的定义、RPC方法的定义、字节序的转换、执行结果消息的通知、监听等。
反馈模块122,一方面实现把SDN控制器状态信息、链路发现信息、业务路由信息、业务迁移信息、业务返回信息、链路时延信息、链路恢复信息、实时拓扑信息反馈给网管人员,另一方面向网管人员反馈控制器监管通讯状况,如检测到控制器监管出现故障时,及时向用户发送告警,提示重启SDN控制器监管或对控制器监管进行维护。
转换模块123,主要是实现把APP下发的报文,如JSON报文,经北向适配成窗口维护、模拟割接、光纤割接、割接返回的数据格式,如YANG文件定义的数据格式等。同时把窗口维护、模拟割接、光纤割接、割接返回上报的数据格式转为APP数据格式上报,如转为JSON数据格式上报等。
除了北向接口模块121、反馈模块122、转换模块123之外,北向控制管理层120还可以包括其他的预留应用124,以便于监控控制器、实现控制器软件升级、开启日志功能、检查内存泄露、实现控制器监管重启和维护、接收维护人员的控制器选择指定等功能中的至少一者。
南向服务层130通过各种南向协议(包括但不限于netconf、P4、openflow等)实现SDN控制器与转发层之间的通信。
作为一种可选实施方式,所述SDN控制器基于微服务框架。
也就是说,可以通过微服务的方式,发布SDN控制器中的监听单元以及路由计算单元。在本申请中,对微服务的具体方式不做特殊限定,例如,可以基于paaS微服务的方式,发布监听单元和路由计算单元。
由于本申请所提供的SDN控制器基于微服务框架,各个功能模块之间耦合度低,各个功能模块具有独立性、易扩展性、易不属性等优点。
所谓“微服务框架”是指,SDN控制器北向和南向都是采用微服务实现,SDN控制器的每个模块、每个单元、以及每个子单元都分别是一个微服务。此外,SDN控制器的北向协议或工具也都是微服务,SDN控制器的北向协议或公开包括但不限于restful、gRPC、tapi、yangtools等协议或接口,这样,即使有不同版本的tapi或yangtools也可以同时存在,互不干扰。SDN控制器不会因为接口的变化而导致新旧功能不兼容,也可能实现SDN控制器功能的平滑升级。
SDN控制器的南向存在多个南向协议,不同南向协议都以一个微服务的方式发布,相同的南向协议不同版本可以同时存在,实现SDN控制器对新旧产品的平滑支持。同时各南向协议还便于迁移到其他项目,提高了可扩展性。由于各微服务便于卸载,因此,在新产品发布时,可以很容易地去掉不需要的微服务,保证了SDN控制器的轻量化。
在本申请中,对应用层200的架构不做特殊的限定。在一个示例中,应用层中的应用可以包括:
安全应用,所述安全应用主要是网络中接入的安全服务应用,用于建立网络的安全防御机制;
网管/APP应用,所述网管应用具体是由所述网络管理人员接入的应用,所述网管应用于进行网络的管理和监控;
命令行应用,所述命令行应用具体是由控制器管理人员接入的应用,通过控制器预留的命令行(非开源)实现对控制器的配置,查询等操作,实现一些验证和调试的功能。
第三方应用,所述第三方应用是指有第三方接入的常规应用,用于通过调用SDN控制器的开源应用程序编程接口(API,Application Program Interface)实现自定义的功能。
作为本申请的第六个方面,提供一种计算机可读存储介质,其上存储有可执行程序,当所述可执行程序被调用时能够实现本申请第一个方面所提供的路由计算方法或者本申请第二个方面所提供的数据传输方法。
作为本申请的第七个方面,提供一种终端设备,如图11所示,终端设备包括指令生成模块810和指令发送模块820。
指令生成模块810用于执行步骤S310,即,指令生成模块810用于生成业务创建指令,所述业务创建指令包括配置时延监控信息或者取消时延监控信息, 所述配置时延监控信息用于控制所述SDN控制器执行本申请所提供的上述数据传输方法,所述取消时延监控信息用于控制所述SDN控制器停止执行本申请所提供的上述数据传输方法。
指令发送模块820用于执行步骤S320,即,指令发送模块820用于向SDN控制器发送业务创建指令。
作为本申请的第八个方面,提供一种计算机可读存储介质,其上存储有可执行程序,当所述可执行程序被调用时能够实现本申请所提供的上述业务处理方法。
其中,计算机可读存储介质包括在用于存储信息(诸如计算机可读指令、数据结构、程序模块或其他数据)的任何方法或技术中实施的易失性和非易失性、可移除和不可移除介质。计算机可读存储介质包括但不限于RAM、ROM、EEPROM、闪存或其他存储器技术、CD-ROM、数字多功能盘(DVD)或其他光盘存储、磁盒、磁带、磁盘存储或其他磁存储介质、或者可以用于存储期望的信息并且可以被计算机访问的任何其他的介质。
下面通过具体实施例对本申请所提供的SDN控制系统的工作原理进行详细的描述。
图12为在SDN网络中执行本申请实施例1所提供的业务创建方法的流程图,具体地步骤如下:
在步骤5-1中,安装有APP的终端设备,通过APP向SDN控制系统的北向接口模块发送用户请求,该用户请求包括时延操作指令,发送用户请求的方式包括但不限于restful、gRPC、http等协议接口。
在步骤5-2中,北向接口模块向北向适配模块发送创建业务请求,所述北向适配模块收到APP的维护窗口创建请求,适配成创建维护窗口请求,并将该请求发送给北向控制管理层的转换模块,以转换为SND控制器能够处理的数据结构类型消息。
在步骤5-3中,SDN控制器根据转换后的业务创建请求判断是否要进行时延监控的业务,若是则,转至步骤5-4,否则转至步骤5-5。
在步骤5-4中,通过SDN控制器配置业务时延监控,在创建业务的输入对象配置设置时延监控信息。
在步骤5-5中,通过分析用户请求确定配置业务是否自动优化路由,在创 建/修改业务的输入对象配置是否自动优化信息。
在步骤5-6中,创建/修改业务,执行正常的创建或者修改业务流程。
步骤5-7中,时延选路子单元将业务信息存储在内存和数据库,时延模块将业务ID信息保存在内存,以提高业务优化速度,并将业务ID保存在数据库,以便控制器重启数据恢复。
图13为本申请实施例2中批量修改业务时延监控配置流程图;
在步骤6-1中,安装有APP的终端通过所述APP向SDN控制器发送批量修改时延监控配置,所述APP发送表示非创建业务批量时延监控配置的用户请求至SDN控制器,该用户请求中需要包含但不限于设置或者取消时延监控信息,并包含自动还是非自动替换业务信息,包含业务ID列表等。
如果用户请求中包含的是取消时延监控,则SDN控制器从内存Map<service_id,delaymonitorinfo>移除业务ID选项,把取消时延监控配置信息入库,返回每次修改成功或失败信息。
如果用户请求中包含的是配置时延监控,则执行以下步骤:
在步骤6-2中,SDN控制器遍历业务列表B;
在步骤6-3中,取出当前执行的预定业务B1;
在步骤6-4中,判断所述预定业务B1的当前路由是否为时延最优路由;
当步骤6-4中的判断结果为是时,执行步骤6-5,当步骤6-4中的判断结果为否时,执行步骤6-7;
在步骤6-5中,北向微服务模块调用数据存储接口,将所述时延最优路由存储至数据库中,返回每次修改成功或失败信息;
在步骤6-7中,判断是否遍历完业务列表B;
当步骤6-7中的判断结果为是时,结束;当步骤6-7中的判断结果为否时,跳转至步骤6-2。
在步骤6-6中,如入库成功,则北向调用时延监控模块修改内存中维护的监控业务ID的内存,则把业务ID,时延监控信息存入内存,如Map<service_id,delaymonitorinfo>。存储方式为把业务ID,是否自动替换,预计算结果放在一个类DelayMonitorInfo.java,然后用一个Map<service_id,delaymonitorinfo>的方式存储,以便于维护时延期配置信息,返 回配置成功或失败的结果。
图14为本申请实施例3中资源增加时延选路流程图;
在步骤7-1中,数据模型单元收到转发层的网络设备拓扑资源的变化,发资源变化通知,数据模型单元收到网络设备拓扑资源的变化的通知,经分析后,把资源变化前和变化后的通知等信息封装,发链路和端口资源变化的通知,包括但不限于链路告警消失、有新增链路、端口资源有释放、有新增端口等;
在步骤7-2中,监听单元监听到数据变化通知,并确认是增资增加,时延微服务的监听单元监听到上述通知,并把资源新增信息进行分析,对不同资源进行不同的处理,并存时延内存对象中。内存可以是但不限于Map<service_id,delaymonitorinfo>的形势。
在步骤7-3中,时延选路子单元从内存获取受时延监控的业务信息列表B,时延选路子单元从内存Map<service_id,delaymonitorinfo>中获取受时延监控的业务信息列表B。
在步骤7-3中,时延选路子单元从内存获取受时延监控的业务信息列表B,时延选路子单元从内存Map<service_id,delaymonitorinfo>中获取受时延监控的业务信息列表B。
在步骤7-4、步骤7-5中,遍历受时延监控的业务信息列表B,取出当前业务B1。
在步骤7-6中,预计算判断是否有更优路由,根据业务B1信息,进行预计算,判断预计算是否有更优路由,如是则转步骤7-7,如否则转步骤7-10。
在步骤7-7中,判断是否自动替换的业务。
若步骤7-7中的判断结果为是则转至步骤7-8,若步骤S7-7中的判断结果为否,则转至步骤7-11。
在步骤7-8中,执行业务B1优化替换,时延模块调用业务模块接口实现业务优化替换。
在步骤7-9中,给APP上报路由优化的结果,时延模块给北向结构模块发通知,北向结构模块收到通知后,向APP发通知,把路由优化的结果通知APP。
在步骤7-10中,判断业务列表B是否遍历完。
若步骤7-10中的判断结果为是,则结束,若步骤7-10中的判断结果为否, 则转至步骤7-4。
在步骤7-11中,给APP上报预计算结果,SDN控制器调用预计算接口,如预计算成功,比较预计算的路由时延与当前业务路由时延谁更优,如预计算的路由时延更优,然后比较预计算的路由与上一次上报的是否一样,如不一样,则给APP上报计算获得的时延最优路由。
在步骤7-12中,APP提示用户是否路径优化。
若步骤7-12中的结果为是,则转至步骤7-13,若步骤7-12中的结果为否,则转至步骤7-5。
在步骤7-13中,APP调用创建预置路径接口,算路模块生成可用路径,并返回结果给APP。
在步骤7-14中,APP调用执行路径优化的接口,根据步骤7-13算路生成的路径,执行路径重路由功能,并返回结果给APP。
在步骤7-15中,APP调用删除预置路径接口,释放资源,并返回结果给APP。
图15为本申请实施例4中链路改变时延选路流程图;
在步骤8-1中,数据模型单元收到设备拓扑资源的变化,发资源变化通知,数据模型单元收到设备拓扑资源的变化的通知,经分析后,把资源变化前和变化后的通知等信息封装,发链路和端口资源变化的通知。
在步骤8-2中,监听单元监听到数据变化通知,并确认是链路时延变化,包括但不限于根据变化前的时延(before delay)和变化后的时延(after delay)相减,确定链路时延是增大还是减小。
在步骤8-3中,时延选路子单元监听到链路改变的通知,并生成链路列表A。
在步骤8-4中,时延选路子单元从内存获取受时延监控的业务信息列表B。
在步骤8-5中遍历业务列表B。
在步骤8-6中,从业务列表B中取出当前业务B1。
在步骤8-7中,比较链路列表A,判断业务B1是否有链路时延增大,如果步骤8-7中的判断那结果为是,则转至步骤8-9,如果步骤8-7中的判断结果为否,则转至步骤8-8。
在步骤8-8中,判断链路列表A中是否有减小的链路不在业务B1上,如果 步骤8-8中的判断结果为是,则转至步骤8-9,如果步骤8-8中的判断结果为否,则转至步骤8-18。
在步骤8-9中,预计算判断是否有更优路由,控制器调用预计算接口,如在步骤8-9中判断存在更优路由,则转至步骤8-10,如果在步骤8-9中判不存在更优路由,则转至步骤8-18。
在步骤8-10中,判断是否自动替换的业务,如果步骤8-10的判断结果为是,则执行业务优化替换,如果步骤8-10中的判断结果为否,则转至步骤8-13。
在步骤8-11中,执行业务优化替换,切换模块调用业务模块接口实现业务优化替换。
在步骤8-12中,给APP上报路由优化的结果,时延模块给北向模块发通知,北向模块收到通知后,向APP发通知,把路由优化的结果通知APP。
在步骤8-13中,给APP上报预计算结果,SDN控制器调用预计算接口,如预计算成功,比较预计算的路由时延与当前业务路由时延谁更优,如预计算的路由时延更优,然后比较预计算的路由与上一次上报的是否一样,如不一样,则给APP上报新路由。
在步骤8-14中,APP提示用户是否路径优化,如果接收到用户选择的“是”,则转至步骤8-15,如果接收到用户选择的“否”,则转步骤8-18。
在步骤8-15中,APP调用创建预置路径接口,算路生成可用路径,并返回结果给APP。
在步骤8-16中,APP调用执行路径优化的接口,根据步骤8-5算路生成的路径,执行路径重路由功能,并返回结果给APP。
在步骤8-17中,APP调用删除预置路径接口,释放算路的资源,并返回结果给APP。
在步骤8-18中,判断业务列表B是否遍历完,如果步骤8-18中的判断结果为“是”则结束,如果步骤8-18中的判断结果为否则转至步骤8-5,继续遍历业务。
可以理解的是,以上实施方式仅仅是为了说明本申请的原理而采用的示例性实施方式,然而本申请并不局限于此。对于本领域内的普通技术人员而言,在不脱离本申请的精神和实质的情况下,可以做出各种变型和改进,这些变型和改进也视为本申请的保护范围。
Claims (16)
- 一种路由计算方法,应用于SDN控制器,所述路由计算方法包括:监听转发层的网络资源状态;在所述转发层的所述网络资源状态发生变化的情况下,根据变化后的网络资源为受监控的预定业务计算时延最优路由。
- 根据权利要求1所述的路由计算方法,其中,所述网络资源状态发生变化包括:所述转发层的网络设备拓扑资源发生变化和所述转发层中能够执行所述预定业务的链路的链路时延发生变化,其中,所述网络设备拓扑资源发生变化包括以下变化中的至少一者:链路告警消失、存在新增链路、存在端口资源释放、存在新增端口。
- 根据权利要求1或2所述的路由计算方法,其中,还包括:根据监听到的网络资源状态生成链路列表,所述链路列表包括所有能够实现受监控的预定业务的链路;根据变化后的网络资源为受监控的预定业务计算时延最优路由包括:将所述链路列表中的各个链路的时延与所述预定业务的当前链路的时延进行比较;将业务时延最优的链路确定为所述时延最优路由。
- 一种数据传输方法,应用于SDN控制器,所述数据传输方法包括:根据预定算法确定受监控的预定业务的所述时延最优路由,其中,所述预定算法为权利要求1至3中任意一项所述的路由计算方法;在满足预定条件的情况下,将受监控的所述预定业务迁移至所述时延最优路由。
- 根据权利要求4所述的数据传输方法,其中,在满足预定条件的情况下,将受监控的业务迁移至所述时延最优路由之前,所述数据传输方法还包括:将所述时延最优路由发送至应用层中发送创建受监控的所述预定业务的业务创建指令的终端;所述满足预定条件包括:接收到所述终端发送的路由切换指令。
- 根据权利要求4所述的数据传输方法,其中,在满足预定条件的情况下,将受监控的所述预定业务迁移至所述时延最优路由之前,所述数据传输方法还包括:响应于应用层发送的手动切换指令,将本次确定的时延最优路由与上次执行所述预定业务时上报的时延最优路由进行对比;当本次确定的时延最优路由不同于上次上报的时延最优路由时,将本次确定的时延最优路由上报至应用层。
- 根据权利要求4所述的数据传输方法,其中,所述数据传输方法还包括:获取受监控的所述预定业务的配置属性;所述预定条件包括:所述配置属性包括自动切换路由信息。
- 根据权利要求4至7中任意一项所述的数据传输方法,其中,响应于应用层发送的时延监控指令,执行根据预定算法确定受监控的预定业务的所述时延最优路由的步骤。
- 根据权利要求4至7中任意一项所述的数据传输方法,其中,还包括:响应于SDN控制器重启指令,从数据库中调取受监控的业务信息。
- 一种业务处理方法,包括:生成业务创建指令,所述业务创建指令包括配置时延监控信息或者取消时延监控信息,所述配置时延监控信息用于控制所述SDN控制器执行权利要求4至9中任意一项所述的数据传输方法,所述取消时延监控信息用于控制所述SDN控制器停止执行权利要求4至9中任意一项所述的数据传输方法;向SDN控制器发送业务创建指令。
- 根据权利要求10所述的业务处理方法,其中,还包括:所述业务创建指令还包括自动切换路由信息或者非自动切换路由信息,所述自动切换路由信息用于控制所述SDN控制器将所述预定业务迁移至所述时延最优路由,所述非自动切换路由用于控制所述SDN控制器将所述时延最优路由上报至创建所述预定业务的终端。
- 一种路由计算模块,包括:监听单元,用于监听转发层的网络资源状态;计算单元,用于在所述转发层的所述网络资源状态发生变化的情况下,根据变化后的网络资源为受监控的预定业务计算时延最优路由。
- 一种SDN控制器,包括:存储模块,存储有可执行程序;一个或多个处理器,所述一个或多个处理器调用所述可执行程序,使得所述一个或多个处理器实现权利要求1至3中任意一项所述的路由计算方法,或者,使得所述一个或多个处理器实现权利要求4至9中任意一项所述的数据传输方法。
- 一种计算机可读存储介质,其上存储有可执行程序,当所述可执行程序被调用时能够实现权利要求1至3中任意一项所述的路由计算方法或者权利要求4至9中任意一项所述的数据传输方法。
- 一种终端设备,包括:指令生成模块,用于生成业务创建指令,所述业务创建指令包括配置时延监控信息或者取消时延监控信息,所述配置时延监控信息用于控制所述SDN控制器执行权利要求4至9中任意一项所述的数据传输方法,所述取消时延监控信息用于控制所述SDN控制器停止执行权利要求4至9中任意一项所述的数据传输方法;指令发送模块,用于向SDN控制器发送业务创建指令。
- 一种计算机可读存储介质,其上存储有可执行程序,当所述可执行程序被调用时能够实现权利要求10或11所述的业务处理方法。
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| EP20908493.8A EP4072082A4 (en) | 2019-12-30 | 2020-11-26 | ROUTE CALCULATION METHOD AND DATA TRANSMISSION METHOD |
Applications Claiming Priority (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911396549.6 | 2019-12-30 | ||
| CN201911396549.6A CN113132237A (zh) | 2019-12-30 | 2019-12-30 | 路由计算方法和数据传输方法 |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| WO2021135746A1 true WO2021135746A1 (zh) | 2021-07-08 |
Family
ID=76687286
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| PCT/CN2020/131839 Ceased WO2021135746A1 (zh) | 2019-12-30 | 2020-11-26 | 路由计算方法和数据传输方法 |
Country Status (3)
| Country | Link |
|---|---|
| EP (1) | EP4072082A4 (zh) |
| CN (1) | CN113132237A (zh) |
| WO (1) | WO2021135746A1 (zh) |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114745763A (zh) * | 2022-03-08 | 2022-07-12 | 深圳市欣博跃电子有限公司 | 一种更新最佳网络拓扑的方法及系统 |
| CN115150324A (zh) * | 2022-06-09 | 2022-10-04 | 南京邮电大学 | 一种基于可编程数据平面实现可变重路由阈值的方法及系统 |
| CN115190025A (zh) * | 2022-06-13 | 2022-10-14 | 安世亚太科技股份有限公司 | 一种基于动态均衡的网络数字孪生体资源优化方法 |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105790990A (zh) * | 2014-12-24 | 2016-07-20 | 国家电网公司 | 一种监管配用电通信业务的方法及其系统 |
| CN106130767A (zh) * | 2016-09-23 | 2016-11-16 | 深圳灵动智网科技有限公司 | 一种业务路径故障监控及故障解决的系统和方法 |
| US9571384B2 (en) * | 2013-08-30 | 2017-02-14 | Futurewei Technologies, Inc. | Dynamic priority queue mapping for QoS routing in software defined networks |
| CN108768713A (zh) * | 2018-05-09 | 2018-11-06 | 西安工业大学 | SDN中的一种保障QoS动态路由算法 |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105871755A (zh) * | 2016-06-06 | 2016-08-17 | 中国电子科技集团公司第三十研究所 | 一种基于sdn的网络资源分配方法和系统 |
| CN108512760B (zh) * | 2018-03-09 | 2020-07-28 | 西安电子科技大学 | 基于SDN保障业务QoS的路由方法 |
-
2019
- 2019-12-30 CN CN201911396549.6A patent/CN113132237A/zh active Pending
-
2020
- 2020-11-26 EP EP20908493.8A patent/EP4072082A4/en not_active Withdrawn
- 2020-11-26 WO PCT/CN2020/131839 patent/WO2021135746A1/zh not_active Ceased
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9571384B2 (en) * | 2013-08-30 | 2017-02-14 | Futurewei Technologies, Inc. | Dynamic priority queue mapping for QoS routing in software defined networks |
| CN105790990A (zh) * | 2014-12-24 | 2016-07-20 | 国家电网公司 | 一种监管配用电通信业务的方法及其系统 |
| CN106130767A (zh) * | 2016-09-23 | 2016-11-16 | 深圳灵动智网科技有限公司 | 一种业务路径故障监控及故障解决的系统和方法 |
| CN108768713A (zh) * | 2018-05-09 | 2018-11-06 | 西安工业大学 | SDN中的一种保障QoS动态路由算法 |
Non-Patent Citations (1)
| Title |
|---|
| See also references of EP4072082A4 * |
Cited By (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114745763A (zh) * | 2022-03-08 | 2022-07-12 | 深圳市欣博跃电子有限公司 | 一种更新最佳网络拓扑的方法及系统 |
| CN114745763B (zh) * | 2022-03-08 | 2023-08-22 | 深圳市欣博跃电子有限公司 | 一种更新最佳网络拓扑的方法及系统 |
| CN115150324A (zh) * | 2022-06-09 | 2022-10-04 | 南京邮电大学 | 一种基于可编程数据平面实现可变重路由阈值的方法及系统 |
| CN115150324B (zh) * | 2022-06-09 | 2024-05-10 | 南京邮电大学 | 一种基于可编程数据平面实现可变重路由阈值的方法及系统 |
| CN115190025A (zh) * | 2022-06-13 | 2022-10-14 | 安世亚太科技股份有限公司 | 一种基于动态均衡的网络数字孪生体资源优化方法 |
| CN115190025B (zh) * | 2022-06-13 | 2023-07-25 | 安世亚太科技股份有限公司 | 一种基于动态均衡的网络数字孪生体资源优化方法 |
Also Published As
| Publication number | Publication date |
|---|---|
| EP4072082A4 (en) | 2023-02-08 |
| EP4072082A1 (en) | 2022-10-12 |
| CN113132237A (zh) | 2021-07-16 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN114039846B (zh) | 支持接近实时的服务水平协议 | |
| CN106063223B (zh) | 虚拟网络创建和操作的声明式方法 | |
| US11563601B1 (en) | Proactive tunnel configuration computation for on-demand SD-WAN tunnels | |
| EP4072082A1 (en) | Route calculation method and data transmission method | |
| CN108449350B (zh) | 一种多协议编排方法及装置 | |
| US10298438B2 (en) | Resource state monitoring method, device and communication network | |
| CN112448987A (zh) | 一种熔断降级的触发方法、系统和存储介质 | |
| WO2018121406A1 (zh) | 基于sdn的报文镜像方法及网络流量监控管理系统 | |
| CN111314802B (zh) | 光纤割接方法、装置、sdn控制器、系统及存储介质 | |
| CN108809794B (zh) | 基于sdn的传送网虚拟网络创建方法和装置及传送网络系统 | |
| CN108293007A (zh) | 带有分布式湿式设备管理器的光学通信系统 | |
| CN108476175B (zh) | 使用对偶变量的传送sdn流量工程方法与系统 | |
| WO2013152569A1 (zh) | 网状网中的节点时钟同步规划方法 | |
| WO2025040039A1 (zh) | 一种自动伸缩的无侵入式灰度发布系统 | |
| WO2022016969A1 (zh) | 一种数据处理方法及装置 | |
| US20250373555A1 (en) | Programmable Path Computation Engine | |
| US11961006B1 (en) | Network automation and orchestration using state-machine neural networks | |
| JP2017220240A (ja) | ネットワーク制御システムのためのグラフィカルポリシインタフェース | |
| WO2019134572A1 (zh) | 基于sdn的光传送网保护恢复方法、设备及存储介质 | |
| CN114531393A (zh) | 分段路由策略下发方法、装置、设备、介质及程序产品 | |
| US12237975B2 (en) | Cloud-native approach to support desired state model reconciliation with networking equipment | |
| WO2015135312A1 (zh) | 一种实现sdn网络通信管理的方法及装置 | |
| CN100550695C (zh) | 一种加速链路状态收敛的方法 | |
| WO2016065925A1 (zh) | 控制器替换方法及装置 | |
| US12210861B2 (en) | Decentralized software upgrade image distribution for network device upgrades |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| 121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 20908493 Country of ref document: EP Kind code of ref document: A1 |
|
| ENP | Entry into the national phase |
Ref document number: 2020908493 Country of ref document: EP Effective date: 20220707 |
|
| NENP | Non-entry into the national phase |
Ref country code: DE |
|
| WWW | Wipo information: withdrawn in national office |
Ref document number: 2020908493 Country of ref document: EP |