A data processing method and device

Abstract

An embodiment of the present invention provides a data processing method and device, wherein the method includes: receiving a first data processing request, wherein the first data processing request carries data collection information and / or configuration information; determining a target management and control component; generating a second data processing request according to the first data processing request; and sending the second data processing request to the target management and control component, wherein the target management and control component is used to collect or configure data according to the second data processing request, which can solve the problem of how to perform data processing based on user requests for management and control systems in related technologies, and realizes data processing based on user requests.

Description

Technical Field

[0001] The embodiments of the present invention relate to the field of communications, and in particular, to a data processing method and device. Background Art

[0002] Distributed controllers, such as Automatically Switched Optical Network (ASON), can complete distributed connection scheduling by controlling the interaction between components based on signaling, routing, automatic discovery and other mechanisms. It has the advantages of distributed processing and flexible network dynamic control.

[0003] Centralized controllers, such as Software Defined Network (SDN controller), based on a logically centralized control architecture, complete centralized connection scheduling through control components such as connection controller CC (Connection Controller) and routing controller RC (Routing Controller). Because it has global network resource information and can collaboratively process all connection requests, it can optimize resource configuration from the overall perspective.

[0004] Figure 1 is a schematic diagram of SDN controller related components in the related art, such as Figure 1 As shown, it includes a network call controller NCC (Network Call Controller), a link resource manager LRM (Link Resources Manager), a connection controller, a routing controller RC, a notification (Notification), a termination and adaptation executor TAP (Termination and Adaptation Performer) component, and a forwarding plane device network element connected to the TAP.

[0005] Considering that the network management function and the control function are essentially the same, the above-mentioned distributed controllers and centralized controllers, as well as the network management system are collectively referred to as the management control system MCS (Management Control System). In MCS, there is a management control component (MC Component), and the management control function is performed by the management control component (hereinafter, for the sake of simplicity, the management control component is referred to as the management and control component).

[0006] In the software-defined network controller (SDN controller) architecture, the client context represents a component in the service layer controller, which is used for interactive services between the client and service controllers; the service context represents a component in the client layer controller, which is used for interactive services between the client and service controllers.

[0007] In order to further optimize the operating efficiency of the controller and meet the business needs of external customers, the operating data inside the controller also needs to be accurately mastered. Analysis based on relevant data will help improve network control processes, optimize control efficiency, and provide users with more insights to improve network performance.

[0008] In the management and control system MCS, such as the SDN controller or control plane, how to process data based on user requests, such as data collection, analysis, policy decision-making, etc., which components have related interactions, and what are the specific interaction contents, these issues need to be clarified. Summary of the invention

[0009] The embodiments of the present invention provide a data processing method and device to at least solve the problem of how to process data based on user requests in a management control system in the related art.

[0010] According to an embodiment of the present invention, there is provided a data processing method, comprising:

[0011] receiving a first data processing request, wherein the first data processing request carries data collection information and / or configuration information;

[0012] Identify target control components;

[0013] generating a second data processing request according to the first data processing request;

[0014] The second data processing request is sent to the target management and control component, wherein the target management and control component is used to collect or configure data according to the second data processing request.

[0015] In an exemplary embodiment, determining the target control component includes:

[0016] determining a first control component according to the data collection information, wherein the first control component is used to collect data according to the second data processing request, and the target control component is the first control component; and / or

[0017] A second control component is determined according to the configuration information, wherein the second control component is used to perform configuration according to the second data processing request, and the target control component is the second control component.

[0018] In an exemplary embodiment, determining the first control component according to the data collection information includes:

[0019] Determining the first control component based on the first data processing request and directory service information of the control component; or

[0020] Determine that the control component indicated by the data collection information is the first control component.

[0021] In an exemplary embodiment, determining the second control component according to the configuration information includes:

[0022] Determining the second control component based on the first data processing request and the directory service information of the control component; or

[0023] Determine that the management and control component indicated by the configuration information is the second management and control component.

[0024] In an exemplary embodiment, generating the second data processing request according to the first data processing request includes:

[0025] In the case where the target control component is the first control component, a data collection request is generated according to the data collection information, wherein the second data processing request is the data collection request, and the data collection request also carries at least one of the following: the type of data to be collected, the start and end time of data update, and the transmission method of the collected data;

[0026] When the target control component is the second control component, a configuration request is generated according to the configuration information, or the configuration request is generated according to the configuration information and the data processing result returned by the first control component, wherein the second data processing request is the configuration request, and the configuration request carries a configuration interface and parameters.

[0027] In an exemplary embodiment, the data type includes at least one of the following: link occupancy and / or topology.

[0028] In an exemplary embodiment, receiving the first data processing request includes:

[0029] receiving the first data processing request sent by a network call controller; or

[0030] receiving the first data processing request sent by the client context; or

[0031] The first data processing request sent by the protocol controller is received.

[0032] In an exemplary embodiment, after sending the second data processing request to the target management and control component, the method further includes:

[0033] Receive the data processing result returned by the target control component;

[0034] The data processing result is sent to the network call controller, the client context or the protocol controller.

[0035] In another exemplary embodiment, the first management and control component includes: a link resource manager LRM, a routing controller RC, a connection controller CC, a network call controller NCC, a routing database RDB, a termination and adaptation executor TAP, and the second management and control component includes: a link resource manager LRM, a routing controller RC, a connection controller CC, a network call controller NCC, a routing database RDB, a termination and adaptation executor TAP.

[0036] According to another embodiment of the present invention, there is further provided a data processing device, comprising:

[0037] A first receiving module, configured to receive a first data processing request, wherein the first data processing request carries data collection information and / or configuration information;

[0038] A determination module is used to determine the target control component;

[0039] A generating module, configured to generate a second data processing request according to the first data processing request;

[0040] The first sending module is used to send the second data processing request to the target management and control component, wherein the target management and control component is used to collect or configure data according to the second data processing request.

[0041] In an exemplary embodiment, the determining module includes:

[0042] A first determining submodule is configured to determine a first control component according to the data collection information, wherein the first control component is configured to collect data according to the second data processing request, and the target control component is the first control component; and / or

[0043] The second determination submodule is used to determine a second control component according to the configuration information, wherein the second control component is used to configure according to the second data processing request, and the target control component is the second control component.

[0044] In an exemplary embodiment, the first determining submodule is further configured to:

[0045] Determining the first control component based on the first data processing request and directory service information of the control component; or

[0046] Determine that the control component indicated by the data collection information is the first control component.

[0047] In an exemplary embodiment, the second determining submodule is further configured to:

[0048] Determining the second control component based on the first data processing request and the directory service information of the control component; or

[0049] Determine that the management and control component indicated by the configuration information is the second management and control component.

[0050] In an exemplary embodiment, the generating module comprises:

[0051] A first generating submodule is used for generating a data collection request according to the data collection information when the target control component is the first control component, wherein the second data processing request is the data collection request, and the data collection request also carries at least one of the following: the type of data to be collected, the start and end time of data update, and the transmission method of the collected data;

[0052] The second generation submodule is used to generate a configuration request according to the configuration information when the target control component is the second control component, or to generate the configuration request according to the configuration information and the data processing result returned by the first control component, wherein the second data processing request is the configuration request, and the configuration request carries a configuration interface and parameters.

[0053] In an exemplary embodiment, the data type includes at least one of the following: link occupancy and / or topology.

[0054] In an exemplary embodiment, the first receiving module includes:

[0055] A first receiving submodule is configured to receive the first data processing request sent by a network call controller; or

[0056] A second receiving submodule is configured to receive the first data processing request sent by a client context; or

[0057] The third receiving submodule is used to receive the first data processing request sent by the protocol controller.

[0058] In an exemplary embodiment, after sending the second data processing request to the target management and control component, the device further includes:

[0059] A second receiving module is used to receive the data processing result returned by the target control component;

[0060] The second sending module is used to send the data processing result to the network call controller, the client context or the protocol controller.

[0061] In another exemplary embodiment, the first management and control component includes: a link resource manager LRM, a routing controller RC, a connection controller CC, a network call controller NCC, a routing database RDB, a termination and adaptation executor TAP, and the second management and control component includes: a link resource manager LRM, a routing controller RC, a connection controller CC, a network call controller NCC, a routing database RDB, a termination and adaptation executor TAP.

[0062] According to yet another embodiment of the present invention, a computer-readable storage medium is provided, in which a computer program is stored, wherein the computer program is configured to execute the steps of any one of the above method embodiments when run.

[0063] According to yet another embodiment of the present invention, there is provided an electronic device, including a memory and a processor, wherein the memory stores a computer program, and the processor is configured to run the computer program to execute the steps in any one of the above method embodiments.

[0064] Through the present invention, a first data processing request is received, a target management and control component is determined based on the information carried in the first data processing request, a second data processing request is generated according to the first data processing request, and sent to the target management and control component for processing. This can solve the problem of how to process data based on user requests for management and control systems in related technologies, and realize data processing based on user requests. BRIEF DESCRIPTION OF THE DRAWINGS

[0065] Figure 1 is a schematic diagram of components related to an SDN controller in the related art;

[0066] Figure 2 is a flow chart of a data processing method according to an embodiment of the present invention;

[0067] Figure 3 is a frame of the data processing device according to the preferred embodiment Figure 1 ;

[0068] Figure 4 is a frame of the data processing device according to the preferred embodiment Figure 2;

[0069] Figure 5 is a frame of the data processing device according to the preferred embodiment Figure 3 ;

[0070] Figure 6 is a frame of the data processing device according to the preferred embodiment Figure 4 ;

[0071] Figure 7 is a frame of the data processing device according to the preferred embodiment Figure 5 ;

[0072] Figure 8 is a frame of the data processing device according to the preferred embodiment Figure 6 ;

[0073] Fig. 9 is a structural block diagram of a data processing device according to an embodiment of the present invention. DETAILED DESCRIPTION

[0074] Hereinafter, embodiments of the present invention will be described in detail with reference to the accompanying drawings and in combination with the embodiments.

[0075] It should be noted that the terms "first", "second", etc. in the specification and claims of the present invention and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence.

[0076] In this embodiment, a data processing method running in a network device is provided. Figure 2 is a flow chart of a data processing method according to an embodiment of the present invention. Figure 2 As shown, the process includes the following steps:

[0077] Step S202, receiving a first data processing request, wherein the first data processing request carries data collection information and / or configuration information;

[0078] In an exemplary embodiment, the above step S202 may specifically include: receiving the first data processing request sent by a network call controller; receiving the first data processing request sent by a client context; or receiving the first data processing request sent by a protocol controller.

[0079] Step S204, determining the target control component;

[0080] Step S206, generating a second data processing request according to the first data processing request;

[0081] Step S208: sending the second data processing request to the target management and control component, wherein the target management and control component is used to collect or configure data according to the second data processing request.

[0082] Through the above steps S202 to S208, a first data processing request is received, a target control component is determined based on the information carried in the first data processing request, a second data processing request is generated according to the first data processing request, and sent to the target control component for processing. This can solve the problem of how to process data based on user requests for management and control systems in related technologies, and realize data processing based on user requests.

[0083] In an exemplary embodiment, the above step S202 may specifically include:

[0084] Determine a first control component according to the data collection information, and further determine the first control component based on the first data processing request and the directory service information of the control component; or determine that the control component indicated by the data collection information is the first control component, wherein the first control component is used to collect data according to the second data processing request, and the target control component is the first control component; and / or

[0085] Determine the second control component according to the configuration information, and further, determine the second control component based on the first data processing request and the directory service information of the control component; or determine that the control component indicated by the configuration information is the second control component, wherein the second control component is used to configure according to the second data processing request, and the target control component is the second control component. In an exemplary embodiment, the first control component may specifically include: a link resource manager LRM, a routing controller RC, a connection controller CC, a network call controller NCC, a routing database RDB, a termination and adapter executor TAP, and the second control component includes: a link resource manager LRM, a routing controller RC, a connection controller CC, a network call controller NCC, a routing database RDB, a termination and adapter executor TAP.

[0086] In an exemplary embodiment, the above step S206 may specifically include:

[0087] In the case where the target control component is the first control component, a data collection request is generated according to the data collection information, wherein the second data processing request is the data collection request, and the data collection request also carries at least one of the following: the type of data to be collected, the start and end time of data update, and the transmission method of the collected data;

[0088] When the target control component is the second control component, a configuration request is generated according to the configuration information, or the configuration request is generated according to the configuration information and the data processing result returned by the first control component, wherein the second data processing request is the configuration request, and the configuration request carries a configuration interface and parameters.

[0089] In an exemplary embodiment, the data type includes at least one of the following: link occupancy and / or topology, wherein the link occupancy may be Ethernet link occupancy, SDH link occupancy, and the like.

[0090] In an exemplary embodiment, after sending the second data processing request to the target management and control component, a data processing result returned by the target management and control component is received, and the data processing result is sent to the network call controller, the client context or the protocol controller.

[0091] The source control component in this embodiment refers to the control component responsible for collecting data, and the sink control component is the control component responsible for executing the specified configuration command.

[0092] This embodiment provides a data processing method, which specifically includes:

[0093] Step 1: After receiving the first data processing request, determine the source control component to interact with;

[0094] The source control component to be interacted is determined according to the data collection information in the first data processing request. The data collection information may include: the type of data to be collected, the control component providing the data, etc.

[0095] Preferably, the source control component to be interacted is determined based on the data collection information in the first data processing request and the directory service information between the source control components.

[0096] Preferably, the data collection information in the first data processing request indicates the source control component to be interacted with;

[0097] Preferably, the first data processing request comes from a network call controller;

[0098] Preferably, the first data processing request comes from a client context;

[0099] Preferably, the first data processing request comes from a protocol controller;

[0100] Step 2: If there is an active control component, generate a second data processing request; otherwise, execute step 5;

[0101] Preferably, based on the data collection information in the first data processing request and the source control component determined in step one, the type of data to be collected, the start and end time of data update, and the method of transmitting the collected data, such as real-time data transmission and regular update, are determined in the second data processing request.

[0102] Step three: sending the second data processing request to the source control component;

[0103] Preferably, the sending order of the second data processing requests is controlled according to the source control component workflow.

[0104] Step 4: The source control component processes the received data processing request and returns the collected data;

[0105] Preferably, the source control component collects data that meets the collection criteria;

[0106] Further, sending the returned data to a network call controller;

[0107] Further, sending the returned data to the client context;

[0108] Further, sending the returned data to the protocol controller;

[0109] Step 5: Determine the host control component to be interacted with. If there is a host control component, generate a third data processing request; otherwise, execute step 8.

[0110] Preferably, the sink management and control component to be interacted is determined based on the configuration information in the first data processing request and the directory service information between the sink management and control components.

[0111] Preferably, the configuration information in the first data processing request indicates a sink control component to be interacted with;

[0112] Preferably, the data returned by the source control component is analyzed to determine the sink control component to interact with;

[0113] The configuration information in the third data processing request is determined according to the configuration information in the first data processing request. The configuration information may include: the configured control component, the collection to be configured, etc.; the third data processing request includes a configuration interface and parameters:

[0114] Step 6: Send the third data processing request to the sink control component;

[0115] Preferably, the sending order of the third data processing request is controlled according to the workflow of the host management and control component.

[0116] Step 7: The sink control component processes the third data processing request and returns an execution result;

[0117] Further, sending the execution result to a network call controller;

[0118] Further, sending the execution result to the client context;

[0119] Further, sending the execution result to the protocol controller;

[0120] Step eight, end.

[0121] The data controller in this embodiment is used to determine the source control component to interact with after receiving the first data processing request; generate a second data processing request; send the second data processing request to the source control component; determine the host control component to interact with, and a third data processing request; and send the third data processing request to the host control component.

[0122] The source control component (corresponding to the first control component) is used to receive the second data processing request; preferably, the second data processing request carries data collection standards such as the type of data to be collected and the start and end time of data update. Further data collection standards also include the transmission method of collected data, such as real-time data transmission and regular update. According to the second data processing request, data that meets the collection standards is collected; and the collected data is returned.

[0123] The host control component (corresponding to the above-mentioned second control component) is used to receive the third data processing request, process the third data processing request, and return the execution result to the data controller.

[0124] In this embodiment, it is necessary to collect static OTN link topology data and historical topology from RDB, and dynamic topology data from RC. Static topology data refers to topology data configured by network administrators; there are different topologies at different times in the past, which constitute historical topologies; dynamic topology is topology dynamically maintained by routing protocols or centralized control, such as dynamically refreshing topology according to resource changes after link resources change.

[0125] Figure 3 is a frame of the data processing device according to the preferred embodiment Figure 1 ,like Figure 3 As shown, including:

[0126] Step 1: after receiving the first data processing request, determine the source control component to interact with;

[0127] Preferably, the source control component to be interacted is determined based on the directory service information between the first data processing request and the source control component.

[0128] In this embodiment, the data controller can learn to collect data from RDB and RC based on the topology collection request in the first data processing request and the directory service configuration between the control component, where RDB and RC are both source control components. In this embodiment, the directory service configuration maintains the corresponding relationship between the data collection request, including the topology collection request, and the control component.

[0129] In addition to the routing data provided by RDB and RC, the LRM component can at least provide the current allocation and use of link resources and the local link topology; the NCC can at least provide the number of calls currently maintained and the specific information of the calls, such as bandwidth, running time, etc.; the CC component can at least provide the currently maintained connection data, such as the number of node hops passed by the current connection, the execution status of connection protection and recovery, etc.; the TAP component can at least provide the binding relationship between the forwarding point and the subnet point, indicating whether the resources are dedicated or shared. These control components can all be used as source control components.

[0130] Step 2: If there is an active control component, generate a second data processing request; otherwise, execute step 5;

[0131] Preferably, the second data processing request carries data collection criteria such as the type of data to be collected, the start and end time of data update, etc. Further data collection criteria also include the transmission method of collected data, such as real-time data transmission and regular update.

[0132] In this embodiment, the source control components are RDB and RC. The data type in the generated second data processing request is topology, specifically OTN topology, and other data types include Ethernet link topology, WDM topology, and the like.

[0133] Step three: sending the second data processing request to the source control component;

[0134] Preferably, the sending order of the second data processing requests is controlled according to the source control component workflow.

[0135] In this embodiment, the data controller sends the second data processing request to the source control components RC and RDB.

[0136] Step 4: The source control component processes the received data processing request and returns the collected data;

[0137] Step 5: Determine the host control component to be interacted with. If there is a host control component, generate a third data processing request; otherwise, end.

[0138] In this embodiment, the data controller receives an external request to drive the RC module to start rerouting optimization.

[0139] Step 1: After receiving the first data processing request, determine the source control component to interact with;

[0140] In this embodiment, there is no source control component. The process jumps to step five.

[0141] Step 5: Determine the host control component to be interacted with. If there is a host control component, generate a third data processing request according to the first data processing request; otherwise, execute step 8.

[0142] In one embodiment, the configuration information in the first data processing request may include: a host data type, a configuration set, and the third data processing request includes: a configuration interface and parameters. Based on the host data type in the configuration information in the first data processing request and the directory service information between the host management and control components, the host management and control components to be interacted are determined. The configuration combination in the first data processing request is converted into the configuration interface and parameters in the third data processing request.

[0143] In this embodiment, if the destination data type is route optimization and the configuration set is a connection identifier to be optimized, the third data processing request includes: the configuration interface is to start rerouting, and the parameter is a link identifier in the configuration set. Based on the destination data type in the configuration information in the first data processing request, i.e., route optimization, and the directory service information between the destination control component, it is determined that the destination control component to be interacted is RC. The configuration set in the first data processing request is converted into the configuration interface and parameters in the third data processing request.

[0144] In another embodiment, the configuration information in the first data processing request may further include: a sink control component, a configuration set, and the third data processing request includes: a configuration interface and parameters. Based on the sink control component in the configuration information in the first data processing request, the configuration set in the first data processing request is converted into a configuration interface and parameters in the third data processing request.

[0145] In another embodiment, the configuration information in the first data processing request may further include: the host control component is RC, and the configuration set is the connection identifier to be optimized. Based on the host control component RC in the configuration information in the first data processing request, the configuration set in the first data processing request is converted into the configuration interface and parameters in the third data processing request, that is, the configuration interface is to start rerouting, and the parameter is the link identifier in the configuration set.

[0146] In this embodiment, the data returned by the source control component may also be analyzed to determine the sink control component to interact with, and generate a third data processing request, which includes an operation command configured to the sink control component.

[0147] Step 6: Send the third data processing request to the sink control component RC;

[0148] Step 7: The sink control component RC processes the third data processing request and returns an execution result;

[0149] Step eight, end.

[0150] Figure 4 is a frame of the data processing device according to the preferred embodiment Figure 2 ,like Figure 4 As shown, in this embodiment, the data controller receives an external request to monitor the optical transmission network (OTN) link resource occupancy in the LRM, and automatically starts the connection route optimization through the link when the specified link resource occupancy exceeds a certain threshold.

[0151] Step 1: After receiving the first data processing request, the data controller determines the source control component to interact with;

[0152] Preferably, the source control component to be interacted is determined based on the directory service information between the first data processing request and the source control component.

[0153] Preferably, the first data processing request specifies a source control component to be interacted with.

[0154] In this embodiment, in the first data processing request, the source control component to be interacted with is specified as LRM.

[0155] Preferably, Figure 5 is a frame of the data processing device according to the preferred embodiment Figure 3 ,like Figure 5 As shown, the first data processing request comes from a network call controller;

[0156] Preferably, Figure 6 is a frame of the data processing device according to the preferred embodiment Figure 4 ,like Figure 6 As shown, the first data processing request comes from a customer context;

[0157] Preferably, Figure 7 is a frame of the data processing device according to the preferred embodiment Figure 5 ,like Figure 7 As shown, the first data processing request comes from the protocol controller;

[0158] Step 2: If there is an active control component, generate a second data processing request; otherwise, execute step 5;

[0159] Preferably, the second data processing request carries data collection criteria such as the type of data to be collected, the start and end time of data update, etc. Further data collection criteria also include the transmission method of collected data, such as real-time data transmission and regular update.

[0160] In this embodiment, the type of data to be collected carried in the second data processing request is link occupancy rate, specifically OTN link occupancy rate; the link occupancy rate is returned in real time.

[0161] Other data types include Ethernet link occupancy rate, SDH link occupancy rate, etc.

[0162] Step three: sending the second data processing request to the source control component;

[0163] In this embodiment, the data controller sends the second data processing request to the source management and control component LRM.

[0164] Step 4: The source control component processes the received data processing request and returns the collected data;

[0165] The source management component LRM in this embodiment collects data that meets the collection criteria, that is, link occupancy data, and returns the data to the data controller;

[0166] Preferably, Figure 5 As shown, the returned data is sent to the network call controller;

[0167] The network call controller may further forward the returned data to other management and control components or management and control systems.

[0168] Preferably, Figure 6 As shown, the returned data is sent to the client context;

[0169] The returned data is passed to the service context connected to the client context through the client context.

[0170] Preferably, Figure 7 As shown, the returned data is sent to the protocol controller;

[0171] The returned data is sent through the protocol controller to other management and control systems or applications connected to the protocol controller.

[0172] Step 5: Determine the host control component to be interacted with. If there is a host control component, generate a third data processing request; otherwise, execute step 8.

[0173] In this embodiment, the designated host control component in the first data processing situation is RC.

[0174] Based on the link occupancy data collected by LRM, determine whether the link occupancy exceeds the specified threshold value. When it exceeds the threshold, it is necessary to start route optimization, thereby generating a third data processing request, wherein the configuration interface is determined to start rerouting, and the parameters include the links whose link occupancy exceeds the specified threshold value, and the specified rerouting avoids the said links.

[0175] In the management and control system, in addition to RC being configurable for route optimization and route calculation, CC components can be configured to perform operations such as connection creation and deletion, LRM can be configured to change the management status of link transmission resources, NCC can be configured to initiate network calls at this layer or across layers, and TAP can be configured to change the transmission resource crossover and operation and maintenance management OAM status.

[0176] Step 6: Send the third data processing request to the sink control component RC;

[0177] Step 7: The sink control component RC processes the third data processing request and returns an execution result;

[0178] Further, if Figure 5 As shown, the execution result is sent to the network call controller;

[0179] The network call controller further forwards the execution result to other management and control components or management and control systems.

[0180] Further, if Figure 6 As shown, the execution result is sent to the client context;

[0181] The execution result is delivered to the service context connected to the client context through the client context.

[0182] Further, if Figure 7 As shown, the execution result is sent to the protocol controller;

[0183] The returned data is sent through the protocol controller to other management and control systems or applications connected to the protocol controller.

[0184] Step eight, end.

[0185] Figure 8 is a frame of the data processing device according to the preferred embodiment Figure 6 ,like Figure 8 As shown, in this embodiment, the data controller receives an external request to monitor the OTN link resource occupancy in the LRM, and predicts the link resource occupancy based on historical occupancy data. When the predicted link resource occupancy exceeds a certain threshold, the management state of the transmission resource is modified to limit resource reallocation, and the connection in the link is migrated to other links through connection routing optimization.

[0186] Step 1: After receiving the first data processing request, the data controller determines the source control component to interact with;

[0187] Preferably, the source control component to be interacted is determined based on the directory service information between the first data processing request and the source control component.

[0188] Preferably, the first data processing request specifies a source control component to be interacted with.

[0189] In this embodiment, in the first data processing request, the source control components to be interacted with are specified as LRM, RC and RDB.

[0190] Preferably, Figure 5 As shown, the first data processing request comes from a network call controller;

[0191] Preferably, Figure 6 As shown, the first data processing request comes from a customer context;

[0192] Preferably, Figure 7 As shown, the first data processing request comes from the protocol controller;

[0193] Step 2: If there is an active control component, generate a second data processing request; otherwise, execute step 5;

[0194] Preferably, the second data processing request carries data collection criteria such as the type of data to be collected, the start and end time of data update, etc. Further data collection criteria also include the transmission method of collected data, such as real-time data transmission and regular update.

[0195] In this embodiment, there are multiple source control components that collect multiple types of data.

[0196] When constructing the second data processing request, the second data processing request sent to the LRM may carry the data type to be collected as link occupancy, specifically OTN link occupancy; the second data processing request sent to the RC may carry the data type to be collected as topology, specifically OTN topology; the second data processing request sent to the RDB may carry the data type to be collected as historical connection data, specifically including connection information maintained within a specified time period, such as the number of connections, routing information of each connection, etc.

[0197] The source control component and the corresponding data type can also be specified in the second data processing request, as follows: the second data processing request specifies that the data type to be collected by LRM is link occupancy, specifically OTN link occupancy; the second data processing request specifies that the data type to be collected by RC is topology, specifically OTN topology; the second data processing request specifies that the data type to be collected by RDB is historical connection data, specifically including connection information maintained within a specified time period, such as the number of connections, routing information of each connection, etc.

[0198] Step three: sending the second data processing request to the source control component;

[0199] In this embodiment, the data controller sends the second data processing request to the source management and control components LRM, RC and RDB.

[0200] Step 4: The source control component processes the received data processing request and returns the collected data;

[0201] The source control component LRM in this embodiment collects data that meets the collection criteria, that is, link occupancy data, and returns the data to the data controller; the source control component RC collects data that meets the collection criteria, that is, topology data, and returns the data to the data controller; the source control component RDB collects data that meets the collection criteria, that is, historical connection data, and returns the data to the data controller;

[0202] Preferably, Figure 5 As shown, the returned data is sent to the network call controller;

[0203] The network call controller may further forward the returned data to other management and control components or management and control systems.

[0204] Preferably, Figure 6 As shown, the returned data is sent to the client context;

[0205] The returned data is passed to the service context connected to the client context through the client context.

[0206] Preferably, Figure 7 As shown, the returned data is sent to the protocol controller;

[0207] The returned data is sent through the protocol controller to other management and control systems or applications connected to the protocol controller.

[0208] Step 5: Determine the host control component to be interacted with. If there is a host control component, generate a third data processing request; otherwise, execute step 8.

[0209] In this embodiment, the designated sink management and control components in the first data processing situation are LRM and RC.

[0210] Based on the link occupancy data collected from the LRM, the historical connection data collected from the RDB, and the topology data collected from the RC, it is predicted that the link occupancy may exceed the specified threshold. Simple prediction and judgment methods include linear predictions based on the creation / deletion time of historical connections, the number of maintained connections, etc. When the prediction exceeds the threshold, a third data processing request is generated to the LRM, wherein the configuration interface is determined to modify the management state of the transmission resources, and the parameters include: changing the management state from enabled to disabled; a third data processing request is generated to the RC, wherein the configuration interface is determined to start rerouting, and the parameters include the link whose link occupancy exceeds the specified threshold, and the specified rerouting avoids the said link.

[0211] Step 6: Send the third data processing request to the sink management and control components LRM and RC;

[0212] Step 7: The sink management and control components LRM and RC process the third data processing request and return an execution result;

[0213] Further, if Figure 5 As shown, the execution result is sent to the network call controller;

[0214] The network call controller further forwards the execution result to other management and control components or management and control systems.

[0215] Further, if Figure 6 As shown, the execution result is sent to the client context;

[0216] The execution result is delivered to the service context connected to the client context through the client context.

[0217] Further, if Figure 7 As shown, the execution result is sent to the protocol controller;

[0218] The returned data is sent through the protocol controller to other management and control systems or applications connected to the protocol controller.

[0219] Step eight, end.

[0220] Through the description of the above implementation methods, those skilled in the art can clearly understand that the method according to the above embodiment can be implemented by means of software plus a necessary general hardware platform, and of course can also be implemented by hardware, but in many cases the former is a better implementation method. Based on such an understanding, the technical solution of the present invention, or the part that contributes to the prior art, can be embodied in the form of a software product, which is stored in a storage medium (such as ROM / RAM, a magnetic disk, or an optical disk), and includes a number of instructions for enabling a terminal device (which can be a mobile phone, a computer, a server, or a network device, etc.) to execute the methods described in each embodiment of the present invention.

[0221] In the present embodiment, a data processing device is also provided, which is used to implement the above-mentioned embodiments and preferred implementation modes, and the descriptions that have been made will not be repeated. As used below, the term "module" can implement a combination of software and / or hardware of a predetermined function. Although the devices described in the following embodiments are preferably implemented in software, the implementation of hardware, or a combination of software and hardware, is also possible and conceived.

[0222] Fig. 9 is a structural block diagram of a data processing device according to an embodiment of the present invention. Fig. 9 As shown, including:

[0223] A first receiving module 92, configured to receive a first data processing request, wherein the first data processing request carries data collection information and / or configuration information;

[0224] A determination module 94, used to determine a target control component;

[0225] A generating module 96, configured to generate a second data processing request according to the first data processing request;

[0226] The first sending module 98 is used to send the second data processing request to the target management and control component, wherein the target management and control component is used to collect or configure data according to the second data processing request.

[0227] In an exemplary embodiment, the determining module 94 includes:

[0228] A first determining submodule is configured to determine a first control component according to the data collection information, wherein the first control component is configured to collect data according to the second data processing request, and the target control component is the first control component; and / or

[0229] The second determination submodule is used to determine a second control component according to the configuration information, wherein the second control component is used to configure according to the second data processing request, and the target control component is the second control component.

[0230] In an exemplary embodiment, the first determining submodule is further configured to:

[0231] Determining the first control component based on the first data processing request and directory service information of the control component; or

[0232] Determine that the control component indicated by the data collection information is the first control component.

[0233] In an exemplary embodiment, the second determining submodule is further configured to:

[0234] Determining the second control component based on the first data processing request and the directory service information of the control component; or

[0235] Determine that the management and control component indicated by the configuration information is the second management and control component.

[0236] In an exemplary embodiment, the generating module 96 includes:

[0237] A first generating submodule is used for generating a data collection request according to the data collection information when the target control component is the first control component, wherein the second data processing request is the data collection request, and the data collection request also carries at least one of the following: the type of data to be collected, the start and end time of data update, and the transmission method of the collected data;

[0238] A second generation submodule is used to generate a configuration request according to the configuration information when the target control component is the second control component, or to generate the configuration request according to the configuration information and the data processing result returned by the first control component, wherein the second data processing request is the data collection request and the configuration request carries a configuration interface and parameters.

[0239] In an exemplary embodiment, the data type includes: link occupancy and / or topology.

[0240] In an exemplary embodiment, the first receiving module 92 includes:

[0241] A first receiving submodule is configured to receive the first data processing request sent by a network call controller; or

[0242] A second receiving submodule is configured to receive the first data processing request sent by a client context; or

[0243] The third receiving submodule is used to receive the first data processing request sent by the protocol controller.

[0244] In an exemplary embodiment, after sending the second data processing request to the target management and control component, the device further includes:

[0245] A second receiving module is used to receive the data processing result returned by the target control component;

[0246] The second sending module is used to send the data processing result to the network call controller, the client context or the protocol controller.

[0247] In another exemplary embodiment, the first management and control component includes: a link resource manager LRM, a routing controller RC, a connection controller CC, a network call controller NCC, a routing database RDB, a termination and adaptation executor TAP, and the second management and control component includes: a link resource manager LRM, a routing controller RC, a connection controller CC, a network call controller NCC, a routing database RDB, a termination and adaptation executor TAP.

[0248] It should be noted that the above modules can be implemented by software or hardware. For the latter, it can be implemented in the following ways, but not limited to: the above modules are all located in the same processor; or the above modules are located in different processors in any combination.

[0249] An embodiment of the present invention further provides a computer-readable storage medium, in which a computer program is stored, wherein the computer program is configured to execute the steps of any of the above method embodiments when running.

[0250] In an exemplary embodiment, the computer-readable storage medium may include, but is not limited to, various media that can store computer programs, such as a USB flash drive, a read-only memory (ROM), a random access memory (RAM), a mobile hard disk, a magnetic disk or an optical disk.

[0251] An embodiment of the present invention further provides an electronic device, including a memory and a processor, wherein a computer program is stored in the memory, and the processor is configured to run the computer program to execute the steps in any one of the above method embodiments.

[0252] In an exemplary embodiment, the electronic device may further include a transmission device and an input / output device, wherein the transmission device is connected to the processor, and the input / output device is connected to the processor.

[0253] For specific examples in this embodiment, reference may be made to the examples described in the above embodiments and exemplary implementation modes, and this embodiment will not be described in detail herein.

[0254] Obviously, those skilled in the art should understand that the above modules or steps of the present invention can be implemented by a general computing device, they can be concentrated on a single computing device, or distributed on a network composed of multiple computing devices, they can be implemented by a program code executable by a computing device, so that they can be stored in a storage device and executed by the computing device, and in some cases, the steps shown or described can be executed in a different order than here, or they can be made into individual integrated circuit modules, or multiple modules or steps therein can be made into a single integrated circuit module for implementation. Thus, the present invention is not limited to any specific combination of hardware and software.

[0255] The above description is only a preferred embodiment of the present invention and is not intended to limit the present invention. For those skilled in the art, the present invention may have various modifications and variations. Any modification, equivalent replacement, improvement, etc. made within the principle of the present invention shall be included in the protection scope of the present invention.

Claims

1. A data processing method, characterized in that: include: receiving a first data processing request, wherein the first data processing request carries data collection information and / or configuration information; Determine the target management and control components, wherein the target management and control components include: a link resource manager LRM, a routing controller RC, a connection controller CC, a network call controller NCC, a routing database RDB, and a termination and adaptation actuator TAP; generating a second data processing request according to the first data processing request; The second data processing request is sent to the target management and control component, wherein the target management and control component is used to collect or configure data according to the second data processing request.

2. The method according to claim 1, characterized in that Determining the target control components includes: determining a first control component according to the data collection information, wherein the first control component is used to collect data according to the second data processing request, and the target control component is the first control component; and / or A second control component is determined according to the configuration information, wherein the second control component is used to perform configuration according to the second data processing request, and the target control component is the second control component.

3. The method according to claim 2, characterized in that Determining the first control component according to the data collection information includes: Determining the first control component based on the first data processing request and directory service information of the control component; or It is determined that the control component indicated by the data collection information is the first control component.

4. The method according to claim 2, characterized in that: Determining the second control component according to the configuration information includes: Determining the second control component based on the first data processing request and the directory service information of the control component; or Determine that the management and control component indicated by the configuration information is the second management and control component.

5. The method according to claim 2, characterized in that: Generating the second data processing request according to the first data processing request includes: In the case where the target control component is the first control component, a data collection request is generated according to the data collection information, wherein the second data processing request is the data collection request, and the data collection request also carries at least one of the following: the type of data to be collected, the start and end time of data update, and the transmission method of the collected data; When the target control component is the second control component, a configuration request is generated according to the configuration information, or the configuration request is generated according to the configuration information and the data processing result returned by the first control component, wherein the second data processing request is the configuration request, and the configuration request carries a configuration interface and parameters.

6. The method according to claim 5, characterized in that The data types include: link occupancy and / or topology.

7. The method according to claim 1, characterized in that Receiving the first data processing request includes: receiving the first data processing request sent by a network call controller; or receiving the first data processing request sent by the client context; or Receive the first data processing request sent by the protocol controller.

8. The method according to claim 7, characterized in that After sending the second data processing request to the target management and control component, the method further includes: Receive the data processing result returned by the target control component; The data processing result is sent to the network call controller, the client context or the protocol controller.

9. A data processing device, characterized in that: include: A first receiving module, configured to receive a first data processing request, wherein the first data processing request carries data collection information and / or configuration information; A determination module, used to determine a target management and control component, wherein the target management and control component includes: a link resource manager LRM, a routing controller RC, a connection controller CC, a network call controller NCC, a routing database RDB, and a termination and adaptation actuator TAP; A generating module, configured to generate a second data processing request according to the first data processing request; The first sending module is used to send the second data processing request to the target management and control component, wherein the target management and control component is used to collect or configure data according to the second data processing request.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, wherein the computer program is configured to execute the method according to any one of claims 1 to 8 when executed.

11. An electronic device comprising a memory and a processor, characterized in that: A computer program is stored in the memory, and the processor is configured to run the computer program to perform the method according to any one of claims 1 to 8.

Images