WO2022016969A1 - 一种数据处理方法及装置 - Google Patents

一种数据处理方法及装置 Download PDF

Info

Publication number
WO2022016969A1
WO2022016969A1 PCT/CN2021/094301 CN2021094301W WO2022016969A1 WO 2022016969 A1 WO2022016969 A1 WO 2022016969A1 CN 2021094301 W CN2021094301 W CN 2021094301W WO 2022016969 A1 WO2022016969 A1 WO 2022016969A1
Authority
WO
WIPO (PCT)
Prior art keywords
data processing
management
control component
processing request
data
Prior art date
Application number
PCT/CN2021/094301
Other languages
English (en)
French (fr)
Inventor
牛小兵
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Priority to US18/017,429 priority Critical patent/US20230275807A1/en
Priority to EP21846800.7A priority patent/EP4187814A4/en
Publication of WO2022016969A1 publication Critical patent/WO2022016969A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/04—Network management architectures or arrangements
    • H04L41/042—Network management architectures or arrangements comprising distributed management centres cooperatively managing the network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0803—Configuration setting
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0803—Configuration setting
    • H04L41/0806—Configuration setting for initial configuration or provisioning, e.g. plug-and-play
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/12—Discovery or management of network topologies
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/34—Signalling channels for network management communication
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
    • H04L43/0876—Network utilisation, e.g. volume of load or congestion level
    • H04L43/0882—Utilisation of link capacity
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/16—Threshold monitoring
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0895—Configuration of virtualised networks or elements, e.g. virtualised network function or OpenFlow elements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0896—Bandwidth or capacity management, i.e. automatically increasing or decreasing capacities
    • H04L41/0897—Bandwidth or capacity management, i.e. automatically increasing or decreasing capacities by horizontal or vertical scaling of resources, or by migrating entities, e.g. virtual resources or entities
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/14—Network analysis or design
    • H04L41/147—Network analysis or design for predicting network behaviour
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/04—Processing captured monitoring data, e.g. for logfile generation
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/20—Arrangements for monitoring or testing data switching networks the monitoring system or the monitored elements being virtualised, abstracted or software-defined entities, e.g. SDN or NFV

Definitions

  • Embodiments of the present invention relate to the field of communications, and in particular, to a data processing method and apparatus.
  • ASON Automatically Switched Optical Network
  • a centralized controller such as a software defined network controller (Software Defined Network, referred to as SDN controller) is based on a logically centralized control architecture and controls components such as connection controller CC (Connection Controller) and routing controller RC (Routing Controller).
  • SDN controller Software Defined Network
  • CC Connection Controller
  • RC routing Controller
  • Fig. 1 is a schematic diagram of the related components of the SDN controller in the related art, as shown in Fig. 1, including a network call controller NCC (Network Call Controller), a link resource manager LRM (Link Resources Manager), a connection controller, a routing Controller RC, Notification, Termination and Adaptation Performer TAP (Termination and Adaptation Performer) components, etc., as well as forwarding plane equipment network elements connected to TAP.
  • NCC Network Call Controller
  • LRM Link Resource Manager
  • connection controller a routing Controller RC
  • Notification Termination and Adaptation Performer TAP (Termination and Adaptation Performer) components, etc.
  • TAP Termination and Adaptation Performer
  • MCS Management Control System
  • MC Component management control component
  • the management control function is performed by the management control component (hereinafter, for a simplified description, the management control component is simply referred to as the management control component).
  • the client context Client Context represents a component in the service layer controller controller, which serves for the interaction of the management and control services between the client/service controller;
  • service The context Server Context represents a component in the client layer controller controller, which serves for the interaction of the management and control services between the client/service controllers.
  • the internal operating data of the controller also needs to be accurately grasped. Analysis based on relevant data will help to improve the network control process, optimize the control efficiency, and provide users with more Insights to improve network performance.
  • MCS management control system
  • Embodiments of the present invention provide a data processing method and apparatus, so as to at least solve the problem of how to process data based on a user request for a management control system in the related art.
  • a data processing method comprising:
  • the first data processing request carries data collection information and/or configuration information
  • determining the target management component includes:
  • a first management and control component is determined according to the data collection information, wherein the first management and control component is configured to perform data collection according to the second data processing request, and the target management and control component is the first management and control component; and/or
  • a second management and control component is determined according to the configuration information, wherein the second management and control component is configured to be configured according to the second data processing request, and the target management and control component is the second management and control component.
  • determining the first management and control component according to the data collection information includes:
  • the management and control component indicated by the data collection information is the first management and control component.
  • determining the second management and control component according to the configuration information includes:
  • the management and control component indicated by the configuration information is the second management and control component.
  • generating the second data processing request according to the first data processing request includes:
  • 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 includes It 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;
  • the 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 management and control component, wherein , the second data processing request is the configuration request, and the configuration request carries a configuration interface and parameters.
  • the data type includes at least one of the following: link occupancy and/or topology.
  • receiving the first data processing request includes:
  • the first data processing request sent by the protocol controller is received.
  • the method further includes:
  • the data processing result is sent to the network call controller, the client context or the protocol controller.
  • 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
  • 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, and a termination and adaptation executor TAP.
  • a data processing apparatus comprising:
  • 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 generating module configured to generate a second data processing request according to the first data processing request
  • the first sending module is configured to send the second data processing request to the target management and control component, wherein the target management and control component is configured to perform data collection or configuration according to the second data processing request.
  • the determining module includes:
  • the first determination sub-module is configured to determine a first management and control component according to the data collection information, wherein the first management and control component is used for data collection according to the second data processing request, and the target management and control component is the the first regulatory component; and/or
  • the second determination sub-module is configured to determine a second management and control component according to the configuration information, wherein the second management and control component is configured to be configured according to the second data processing request, and the target management and control component is the second management and control component. control components.
  • the first determination sub-module is further configured as
  • the management and control component indicated by the data collection information is the first management and control component.
  • the second determination sub-module is further set to
  • the management and control component indicated by the configuration information is the second management and control component.
  • the generating module includes:
  • a first generation sub-module configured to generate a data collection request according to the data collection information when the target management and control component is the first management and control component, wherein the second data processing request is the data collection
  • 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;
  • the second generation sub-module is configured to generate a configuration request according to the configuration information or process data returned from the first management and control component according to the configuration information when the target management and control component is the second management and control component As a result, the configuration request is generated, wherein the second data processing request is the configuration request, and the configuration request carries a configuration interface and parameters.
  • the data type includes at least one of the following: link occupancy and/or topology.
  • the first receiving module includes:
  • a first receiving submodule configured to receive the first data processing request sent by the network call controller
  • a second receiving submodule configured to receive the first data processing request sent by the client context
  • the third receiving submodule is configured to receive the first data processing request sent by the protocol controller.
  • the apparatus after sending the second data processing request to the target management and control component, the apparatus further includes:
  • a second receiving module configured to receive the data processing result returned by the target management and control component
  • the second sending module is configured to send the data processing result to the network call controller, the client context or the protocol controller.
  • 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
  • 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, and a termination and adaptation executor TAP.
  • a computer-readable storage medium is also provided, and a computer program is stored in the computer-readable storage medium, wherein the computer program is configured to execute any one of the above methods when running steps in the examples.
  • an electronic device comprising a memory and a processor, wherein the memory stores a computer program, the processor is configured to run the computer program to execute any of the above Steps in Method Examples.
  • the first data processing request is received, the target management and control component is determined based on the information carried in the first data processing request, the second data processing request is generated according to the first data processing request, and sent to the target management and control component for processing.
  • the management control system how to process the data based on the user's request realizes the data processing based on the user's request.
  • FIG. 1 is a schematic diagram of the related components of an SDN controller in the related art
  • FIG. 2 is a flowchart of a data processing method according to an embodiment of the present invention.
  • FIG. 3 is a block diagram 1 of a data processing apparatus according to the present preferred embodiment
  • Fig. 4 is the second block diagram of the data processing apparatus according to the present preferred embodiment.
  • Fig. 5 is the block diagram 3 of the data processing apparatus according to the present preferred embodiment.
  • Fig. 6 is the block diagram 4 of the data processing apparatus according to the present preferred embodiment.
  • Fig. 7 is the block diagram 5 of the data processing apparatus according to the present preferred embodiment.
  • FIG. 8 is a block diagram 6 of the data processing apparatus according to the present preferred embodiment.
  • FIG. 9 is a structural block diagram of a data processing apparatus according to an embodiment of the present invention.
  • FIG. 2 is a flowchart of a data processing method according to an embodiment of the present invention. As shown in FIG. 2 , the flowchart includes the following steps:
  • Step S202 receiving a first data processing request, wherein the first data processing request carries data collection information and/or configuration information;
  • the above step S202 may specifically include: receiving the first data processing request sent by the network call controller; receiving the first data processing request sent by the client context; or receiving the data processing request sent by the protocol controller. the first data processing request.
  • Step S204 determining the target management and control component
  • Step S206 generating a second data processing request according to the first data processing request
  • Step S208 Send the second data processing request to the target management and control component, where the target management and control component is configured to perform data collection or configuration according to the second data processing request.
  • 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, It can solve the problem of how to process the data based on the user's request for the management control system in the related art, and realize the data processing based on the user's request.
  • the foregoing step S202 may specifically include:
  • Determine the first management and control component according to the data collection information further, determine the first management and control component based on the first data processing request and the directory service information of the management and control component; or determine the management and control component indicated by the data collection information is the first management and control component, wherein the first management and control component is used for data collection according to the second data processing request, and the target management and control component is the first management and control component; and/or
  • Determine the second management and control component according to the configuration information further, determine the second management and control component based on the first data processing request and the directory service information of the management and control component; or determine that the management and control component indicated by the configuration information is the The second management and control component, wherein the second management and control component is configured to be configured according to the second data processing request, and the target management and control component is the second management and control component.
  • the first management and control component may specifically include: link resource manager LRM, routing controller RC, connection controller CC, network call controller NCC, routing database RDB, termination and adaptation execution
  • 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, and a termination and adaptation executor TAP.
  • the foregoing step S206 may specifically include:
  • 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 includes It 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;
  • the 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 management and control component, wherein , the second data processing request is the configuration request, and the configuration request carries a configuration interface and parameters.
  • 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.
  • the target management and control component after sending the second data processing request to the target management and control component, receive the data processing result returned by the target management and control component, and send the data processing result to the network call controller, the client context or the protocol controller.
  • the source management and control component in this embodiment refers to a management and control component responsible for collecting data, and the sink management and control component is a management and control component responsible for executing a specified configuration command.
  • This embodiment provides a data processing method, which specifically includes:
  • Step 1 after receiving the first data processing request, determine the source control component to be interacted with
  • the source management and control components to be interacted with are determined according to the data collection information in the first data processing request.
  • Data collection information may include: the type of data to be collected, the management and control components that provide the data, etc.
  • the source management and control components to be interacted with are determined based on the data collection information in the first data processing request and the directory service information between the source management and control components.
  • the data collection information in the first data processing request indicates the source control component to be interacted with
  • the first data processing request comes from a network call controller
  • the first data processing request is from a client context
  • the first data processing request comes from a protocol controller
  • Step 2 if there is an active control component, generate a second data processing request; otherwise, go to Step 5;
  • the second data processing request carries the type of data to be collected, the start and end time of data update, and the transmission method of the collected data, Such as real-time data transmission, and regular updates.
  • Step 3 sending the second data processing request to the source control component
  • the sending sequence of the second data processing request is controlled according to the workflow of the source control component.
  • Step 4 The source control component processes the received data processing request and returns the collected data
  • the source management and control component collects data that meets the collection standard
  • Step 5 Determine the sink management and control component to be interacted with, and if there is a sink management and control component, generate a third data processing request; otherwise, go to Step 8.
  • the sink management and control components to be interacted with are determined based on the configuration information in the first data processing request and the directory service information between the sink management and control components.
  • the configuration information in the first data processing request indicates the sink management and control components to be interacted with
  • the data returned by the source management and control components is analyzed to determine the sink management and control components to be interacted with;
  • 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 management and control components, the set to be configured, etc.; the third data processing request includes the configuration interface and parameters:
  • Step 6 sending the third data processing request to the sink management and control component
  • the sending sequence of the third data processing request is controlled according to the workflow of the sink management and control component.
  • Step 7 the sink management and control component processes the third data processing request and returns the execution result
  • the data controller in this embodiment is configured to, after receiving the first data processing request, determine a source management and control component to interact with; generate a second data processing request; send the second data processing request to the source management and control component; determine The sink management and control component to be interacted with, and the third data processing request; send the third data processing request to the sink management and control component.
  • a source control component (corresponding to the above-mentioned first control component), configured to receive a second data processing request; 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, and the like. Further data collection criteria also include the delivery method of the collected data, such as real-time data transmission, and regular updates. According to the second data processing request, collect data that meets the collection standard; and return the collected data.
  • the sink management and control component (corresponding to the second management and control component) is configured to receive the third data processing request, process the third data processing request, and return the execution result to the data controller.
  • static OTN link topology data and historical topology need to be collected from RDB, and dynamic topology data need to be collected from RC.
  • the static topology data refers to the topology data configured by the network administrator; there are different topologies at different times in the past, which constitute the historical topology; dynamic topology refers to the topology that is dynamically maintained through routing protocols or centralized control, such as in link resources After changes occur, the topology is dynamically refreshed according to resource changes.
  • FIG. 3 is a block diagram 1 of a data processing apparatus according to the present preferred embodiment, as shown in FIG. 3 , including:
  • Step 1 after receiving the first data processing request, determine the source control component to be interacted with
  • the source management and control components to be interacted with are determined based on the directory service information between the first data processing request and the source management and control components.
  • the data controller can learn that data is to be collected from RDB and RC, where RDB and RC are both source management and control components.
  • the directory service configuration maintains the correspondence between data collection requests, including topology collection requests, and management and control components.
  • the LRM component can at least provide the current link resource allocation and usage, as well as the local link topology; NCC can provide at least the number of currently maintained calls and specific information about calls, such as bandwidth and running time etc.; the CC component can at least provide the connection data currently maintained, such as the number of node hops the current connection passes through, the execution of connection protection and recovery, etc.; the TAP component can at least provide the binding relationship between the forwarding point and the sub-network point, indicating that the resource is dedicated Yes, it is still shared.
  • control components can be used as source control components.
  • Step 2 if there is an active control component, generate a second data processing request; otherwise, go to Step 5;
  • 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, and the like. Further data collection criteria also include the delivery method of the collected data, such as real-time data transmission, and regular updates.
  • 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 also include Ethernet link topology, WDM topology, and the like.
  • Step 3 sending the second data processing request to the source control component
  • the sending sequence of the second data processing request is controlled according to the workflow of the source control component.
  • the data controller sends the second data processing request to the source control components RC and RDB.
  • Step 4 The source control component processes the received data processing request and returns the collected data
  • Step 5 Determine the sink management and control component to be interacted with, and if there is a sink management and control component, generate a third data processing request; otherwise, end.
  • the data controller receives an external request to drive the RC module to start rerouting optimization.
  • Step 1 after receiving the first data processing request, determine the source control component to be interacted with
  • Step 5 Determine the sink management and control component to be interacted with, if there is a sink management and control component, generate a third data processing request according to the first data processing request; otherwise, go to Step 8.
  • the configuration information in the first data processing request may include: a sink data type and a configuration set
  • the third data processing request includes: a configuration interface and parameters. Based on the directory service information between the sink data type in the configuration information in the first data processing request and the sink management and control component, the sink management and control component to be interacted with is determined. The configuration combination in the first data processing request is converted into the configuration interface and parameters in the third data processing request.
  • the third data processing request includes: the configuration interface is to start rerouting, and the parameter is the link identifier in the configuration set.
  • the sink data type in the configuration information in the first data processing request that is, route optimization, and the directory service information between the sink management and control component, it is determined that the sink management and control component to be interacted with is the RC. Convert the configuration set in the first data processing request into the configuration interface and parameters in the third data processing request.
  • the configuration information in the first data processing request may further include: a sink management and control component and a configuration set
  • the third data processing request includes: a configuration interface and parameters. Based on the sink management and control component 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.
  • the configuration information in the first data processing request may further include: the sink management and control component is the RC, and the configuration set is the connection identifier to be optimized. Based on the sink management and 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 the restart Route, the parameter is the link ID in the configuration set.
  • the data returned by the source management and control components may also be analyzed, the sink management and control components to be interacted with may be determined, and a third data processing request may be generated, which includes an operation command configured to the sink management and control components.
  • Step 6 sending the third data processing request to the sink management and control component RC;
  • Step 7 the sink management and control component RC processes the third data processing request, and returns the execution result;
  • Fig. 4 is a block diagram 2 of a data processing apparatus according to this preferred embodiment.
  • the data controller receives an external request to monitor the optical transmission network in the LRM (Optical Transmission Net for short) OTN) link resource occupancy, when the specified link resource occupancy rate exceeds a certain threshold, automatically start the connection route optimization through the link.
  • LRM Optical Transmission Net for short
  • Step 1 after receiving the first data processing request, the data controller determines the source control component to be interacted with;
  • the source management and control components to be interacted with are determined based on the directory service information between the first data processing request and the source management and control components.
  • a source control component to be interacted with is specified.
  • the first data processing request indicates that the source management and control component to be interacted with is the LRM.
  • FIG. 5 is a block diagram 3 of a data processing apparatus according to this preferred embodiment.
  • the first data processing request comes from a network call controller;
  • FIG. 6 is a fourth block diagram of a data processing apparatus according to this preferred embodiment, as shown in FIG. 6 , the first data processing request comes from a client context;
  • FIG. 7 is a block diagram 5 of a data processing apparatus according to this preferred embodiment.
  • the first data processing request comes from a protocol controller;
  • Step 2 if there is an active control component, generate a second data processing request; otherwise, go to Step 5;
  • 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, and the like. Further data collection criteria also include the delivery method of the collected data, such as real-time data transmission, and regular updates.
  • the type of data to be collected carried in the second data processing request is the link occupancy rate, specifically the OTN link occupancy rate; the link occupancy rate is returned in real time.
  • Ethernet link occupancy SDH link occupancy, and the like.
  • Step 3 sending the second data processing request to the source control component
  • the data controller sends the second data processing request to the source management and control component LRM.
  • Step 4 The source control component processes the received data processing request and returns the collected data
  • the source management and control component LRM in this embodiment collects data that meets the collection standard, that is, link occupancy data, and returns the data to the data controller;
  • the returned data is sent to the network call controller
  • the network call controller may further forward the returned data to other management and control components or management and control systems.
  • the returned data is sent to the client context
  • the returned data is passed to the service context connected to the client context.
  • the returned data is sent to the protocol controller
  • the returned data is sent to other management systems or applications connected to the protocol controller through the protocol controller.
  • Step 5 Determine the sink management and control component to be interacted with, and if there is a sink management and control component, generate a third data processing request; otherwise, go to Step 8.
  • the designated sink management and control component is the RC.
  • the link occupancy rate data collected by the LRM it is determined whether the link occupancy rate exceeds the specified threshold, and when it exceeds the threshold, route optimization needs to be started, thereby generating a third data processing request, wherein the configuration interface is determined to be restarted Routes, parameters include links whose link occupancy exceeds a specified threshold, and specifies rerouting to avoid the links.
  • CC components can be configured to create and delete connections
  • LRM can be configured to change the management status of link transmission resources
  • NCC can be configured to initiate local or cross Layer network calls
  • TAP can be configured to change the transmission resource crossover and operation and maintenance management to maintain the OAM state.
  • Step 6 sending the third data processing request to the sink management and control component RC;
  • Step 7 the sink management and control component RC processes the third data processing request, and returns the execution result;
  • the network call controller further forwards the execution result to other management and control components or management and control systems.
  • the execution result is passed to the service context connected to the client context.
  • the returned data is sent to other management systems or applications connected to the protocol controller through the protocol controller.
  • Fig. 8 is a block diagram 6 of the data processing apparatus according to the present preferred embodiment.
  • the data controller receives an external request to monitor the OTN link resource occupation in the LRM, and according to the historical occupation data to predict link resource occupancy.
  • the predicted link resource occupancy rate exceeds a certain threshold, the resource redistribution is restricted by modifying the management state of the transmission resource, and the connection in the link is migrated to other links through connection route optimization.
  • Step 1 after receiving the first data processing request, the data controller determines the source control component to be interacted with;
  • the source management and control components to be interacted with are determined based on the directory service information between the first data processing request and the source management and control components.
  • a source control component to be interacted with is specified.
  • the first data processing request indicates that the source management and control components to be interacted with are LRM, RC, and RDB.
  • the first data processing request comes from a network call controller
  • the first data processing request comes from a client context
  • the first data processing request comes from the protocol controller
  • Step 2 if there is an active control component, generate a second data processing request; otherwise, go to Step 5;
  • 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, and the like. Further data collection criteria also include the delivery method of the collected data, such as real-time data transmission, and regular updates.
  • the second data processing request sent to the LRM may carry the data type to be collected as link occupancy, specifically the OTN link occupancy; in the second data processing request sent to the RC
  • the type of data to be collected is topology, specifically OTN topology; the second data processing request sent to the RDB carries the type of data to be collected as historical connection data, which specifically includes connection information maintained within a specified time period, such as the number of connections, Routing information for each connection, etc.
  • the source control component and the corresponding data type may also be specified in the second data processing request.
  • the details are as follows:
  • the type of data to be collected and sent to the LRM is specified as link occupancy, specifically OTN link occupancy.
  • the second data processing request specifies that the type of data sent to the RC to be collected is topology, specifically OTN topology;
  • the second data processing request specifies that the type of data sent to the RDB to be collected is historical connection data, specifically including the specified time period Connection information maintained within the system, such as the number of connections, routing information for each connection, etc.
  • Step 3 sending the second data processing request to the source control component
  • the data controller sends the second data processing request to the source management and control components LRM, RC, and RDB.
  • Step 4 The source control component processes the received data processing request and returns the collected data
  • the source management and control component LRM collects data that meets the collection standard, that is, link occupancy data, and returns the data to the data controller;
  • the source management and control component RC collects data that meets the collection standard, that is, topology data, and sends the data to the data controller. Return to the data controller;
  • the source control component RDB collects data that meets the collection standards, that is, historical connection data, and returns the data to the data controller;
  • the returned data is sent to the network call controller
  • the network call controller may further forward the returned data to other management and control components or management and control systems.
  • the returned data is sent to the client context
  • the returned data is passed to the service context connected to the client context.
  • the returned data is sent to the protocol controller
  • the returned data is sent to other management systems or applications connected to the protocol controller through the protocol controller.
  • Step 5 Determine the sink management and control component to be interacted with, and if there is a sink management and control component, generate a third data processing request; otherwise, go to Step 8.
  • the designated sink management and control components are LRM and RC.
  • Simple prediction judgment methods include linear prediction based on the creation/deletion time of historical connections, the number of connections maintained, etc.
  • a third data processing request sent to the LRM is generated, wherein it is determined that the configuration interface is to modify the management state of the transmission resource, and the parameters include: changing the management state from enable to disable; generating a third data processing request sent to the RC Three data processing requests, wherein it is determined that the configuration interface is to start rerouting, the parameters include links whose predicted link occupancy rate exceeds a specified threshold, and the specified rerouting avoids the links.
  • Step 6 sending the third data processing request to the sink management and control components LRM and RC;
  • Step 7 the sink management and control components LRM and RC process the third data processing request, and return the execution result;
  • the network call controller further forwards the execution result to other management and control components or management and control systems.
  • the execution result is passed to the service context connected to the client context.
  • the returned data is sent to other management systems or applications connected to the protocol controller through the protocol controller.
  • a data processing apparatus is also provided, and the apparatus is used to implement the above-mentioned embodiments and preferred implementations, and what has been described will not be repeated.
  • the term "module” may be a combination of software and/or hardware that implements a predetermined function.
  • the apparatus described in the following embodiments is preferably implemented in software, implementations in hardware, or a combination of software and hardware, are also possible and contemplated.
  • FIG. 9 is a structural block diagram of a data processing apparatus according to an embodiment of the present invention, as shown in FIG. 9 , including:
  • the first receiving module 92 is 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 94 configured to determine a target management and control component
  • a generating module 96 configured to generate a second data processing request according to the first data processing request
  • the first sending module 98 is configured to send the second data processing request to the target management and control component, wherein the target management and control component is configured to perform data collection or configuration according to the second data processing request.
  • the determination module package 94 includes:
  • the first determination sub-module is configured to determine a first management and control component according to the data collection information, wherein the first management and control component is used for data collection according to the second data processing request, and the target management and control component is the the first regulatory component; and/or
  • the second determination sub-module is configured to determine a second management and control component according to the configuration information, wherein the second management and control component is configured to be configured according to the second data processing request, and the target management and control component is the second management and control component. control components.
  • the first determination sub-module is further configured as
  • the management and control component indicated by the data collection information is the first management and control component.
  • the second determination sub-module is further set to
  • the management and control component indicated by the configuration information is the second management and control component.
  • the generating module 96 includes:
  • a first generation sub-module configured to generate a data collection request according to the data collection information when the target management and control component is the first management and control component, wherein the second data processing request is the data collection
  • 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;
  • the second generation sub-module is configured to generate a configuration request according to the configuration information or process data returned from the first management and control component according to the configuration information when the target management and control component is the second management and control component As a result, the configuration request is generated, wherein the second data processing request is the data collection request.
  • the configuration request carries a configuration interface and parameters.
  • the data types include link occupancy and/or topology.
  • the first receiving module 92 includes:
  • a first receiving submodule configured to receive the first data processing request sent by the network call controller
  • a second receiving submodule configured to receive the first data processing request sent by the client context
  • the third receiving submodule is configured to receive the first data processing request sent by the protocol controller.
  • the apparatus after sending the second data processing request to the target management and control component, the apparatus further includes:
  • a second receiving module configured to receive the data processing result returned by the target management and control component
  • the second sending module is configured to send the data processing result to the network call controller, the client context or the protocol controller.
  • 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
  • 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, and a termination and adaptation executor TAP.
  • the above modules can be implemented by software or hardware, and the latter can be implemented in the following ways, but not limited to this: the above modules are all located in the same processor; or, the above modules can be combined in any combination The forms are located in different processors.
  • Embodiments of the present invention further provide a computer-readable storage medium, where a computer program is stored in the computer-readable storage medium, wherein the computer program is configured to execute the steps in any of the above method embodiments when running.
  • the above-mentioned computer-readable storage medium may include, but is not limited to, a USB flash drive, a read-only memory (Read-Only Memory, referred to as ROM for short), and a random access memory (Random Access Memory, referred to as RAM for short) , mobile hard disks, magnetic disks or CD-ROMs and other media that can store computer programs.
  • ROM Read-Only Memory
  • RAM Random Access Memory
  • An embodiment of the present invention also provides an electronic device, comprising a memory and a processor, where a computer program is stored in the memory, and the processor is configured to run the computer program to execute the steps in any of the above method embodiments.
  • the above-mentioned electronic device may further include a transmission device and an input-output device, wherein the transmission device is connected to the above-mentioned processor, and the input-output device is connected to the above-mentioned processor.
  • modules or steps of the present invention can be implemented by a general-purpose computing device, and they can be centralized on a single computing device or distributed in a network composed of multiple computing devices
  • they can be implemented in 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, can be performed in a different order than shown here.
  • the described steps, or they are respectively made into individual integrated circuit modules, or a plurality of modules or steps in them are made into a single integrated circuit module to realize.
  • the present invention is not limited to any particular combination of hardware and software.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Environmental & Geological Engineering (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

本申请提供了一种数据处理方法及装置，其中，该方法包括：接收第一数据处理请求，其中，所述第一数据处理请求中携带有数据收集信息和/或配置信息；确定目标管控组件；根据所述第一数据处理请求生成第二数据处理请求；将所述第二数据处理请求发送给所述目标管控组件，其中，所述目标管控组件用于根据所述第二数据处理请求进行数据收集或配置。本申请针对管理控制系统，可以解决如何基于用户请求进行数据处理的问题，实现了基于用户请求进行数据处理。

Description

一种数据处理方法及装置 技术领域
本发明实施例涉及通信领域，具体而言，涉及一种数据处理方法及装置。
背景技术
分布式控制器，如自动交换光网络(Automatically Switched Optical Network，简称为ASON)，能够基于信令、路由、自动发现等机制通过控制组件之间的交互完成分布式连接调度。具有分布式处理、网络动态控制灵活等优点。
集中式控制器，如软件定义网络控制器(Software Defined Network，简称为SDN controller)，基于逻辑集中的控制架构，通过连接控制器CC(Connection Controller)、路由控制器RC(Routing Controller)等控制组件完成集中式的连接调度。因具有全局网络资源信息并能协同处理全部连接请求，能够从整体来优化资源配置。
图1是相关技术中的SDN控制器相关组件的示意图，如图1所示，包括网络呼叫控制器NCC(Network Call Controller)、链路资源管理器LRM(Link Resources Manager)、连接控制器、路由控制器RC、通告(Notification)、终结和适配执行器TAP(Termination and Adaptation Performer)组件等，以及与TAP相连的转发面设备网元。
考虑网络管理功能与控制功能本质上是相同的，上述分布式控制器和集中式控制器，以及网络管理系统统称为管理控制系统MCS(Management Control System)。在MCS中，包括管理控制组件(MC Component)，管理控制功能通过管理控制组件来执行(后文为简化描述，将管理控制组件简称为管控组件)。
在软件定义网络控制器(SDN controller)架构中，客户上下文Client Context代表服务层控制器controller中的一个组件，该组件是为客户/服务控制器之间的管控服务而进行的交互服务的；服务上下文Server Context代表客户层控制器controller中的一个组件，该组件是为客户/服务控制器之间的管控服务而进行的交互服务的。
为了进一步优化控制器的运行效率、满足外部客户业务需求，控制器内部的运行数据也需求准确掌握，基于相关数据进行分析将有助于改善网络控制流程、优化控制效率，为用户提供更多的提升网络效能的洞见。
在管理控制系统MCS中，如SDN控制器或控制平面，如何基于用户请求进行数据处理，比如数据收集、分析、策略决策等，哪些组件进行相关交互，具体交互内容有哪些，这些问题有待明确。
发明内容
本发明实施例提供了一种数据处理方法及装置，以至少解决相关技术中针对管理控制系统，如何基于用户请求行数据处理的问题。
根据本发明的一个实施例，提供了一种数据处理方法，包括：
接收第一数据处理请求，其中，所述第一数据处理请求中携带有数据收集信息和/或配置 信息；
确定目标管控组件；
根据所述第一数据处理请求生成第二数据处理请求；
将所述第二数据处理请求发送给所述目标管控组件，其中，所述目标管控组件用于根据所述第二数据处理请求进行数据收集或配置。
在一示例性实施例中，确定所述目标管控组件包括：
根据所述数据收集信息确定第一管控组件，其中，所述第一管控组件用于根据所述第二数据处理请求进行数据收集，所述目标管控组件为所述第一管控组件；和/或
根据所述配置信息确定第二管控组件，其中，所述第二管控组件用于根据所述第二数据处理请求进行配置，所述目标管控组件为所述第二管控组件。
在一示例性实施例中，根据所述数据收集信息确定所述第一管控组件包括：
基于所述第一数据处理请求与管控组件的目录服务信息，确定所述第一管控组件；或者
确定所述数据收集信息指示的管控组件为所述第一管控组件。
在一示例性实施例中，根据所述配置信息确定所述第二管控组件包括：
基于所述第一数据处理请求与管控组件的目录服务信息，确定所述第二管控组件；或者
确定所述配置信息指示的管控组件为所述第二管控组件。
在一示例性实施例中，根据所述第一数据处理请求生成所述第二数据处理请求包括：
在所述目标管控组件为所述第一管控组件的情况下，根据所述数据收集信息生成数据收集请求，其中，所述第二数据处理请求为所述数据收集请求，所述数据收集请求中还携带有以下至少之一：待收集的数据类型、数据更新起止时间、收集得到的数据的传递方式；
在所述目标管控组件为所述第二管控组件的情况下，根据所述配置信息生成配置请求或者根据所述配置信息与所述第一管控组件返回的数据处理结果生成所述配置请求，其中，所述第二数据处理请求为所述配置请求，所述配置请求中携带有配置接口及参数。
在一示例性实施例中，所述数据类型包括以下至少之一：链路占用率和/或拓扑。
在一示例性实施例中，接收所述第一数据处理请求包括：
接收网络呼叫控制器发送的所述第一数据处理请求；或者
接收客户上下文发送的所述第一数据处理请求；或者
接收协议控制器发送的所述第一数据处理请求。
在一示例性实施例中，在将所述第二数据处理请求发送给所述目标管控组件之后，所述方法还包括：
接收所述目标管控组件返回的数据处理结果；
将所述数据处理结果发送给所述网络呼叫控制器、所述客户上下文或所述协议控制器。
在另一示例性实施例中，所述第一管控组件包括：链路资源管理器LRM、路由控制器RC、连接控制器CC、网络呼叫控制器NCC、路由数据库RDB、终结和适配执行器TAP，所述第二管控组件包括：链路资源管理器LRM、路由控制器RC、连接控制器CC、网络呼叫控制器NCC、路由数据库RDB、终结和适配执行器TAP。
根据本发明的另一个实施例，还提供了一种数据处理装置，包括：
第一接收模块，设置为接收第一数据处理请求，其中，所述第一数据处理请求中携带有数据收集信息和/或配置信息；
确定模块，设置为确定目标管控组件；
生成模块，设置为根据所述第一数据处理请求生成第二数据处理请求；
第一发送模块，设置为将所述第二数据处理请求发送给所述目标管控组件，其中，所述目标管控组件用于根据所述第二数据处理请求进行数据收集或配置。
在一示例性实施例中，所述确定模块包括：
第一确定子模块，设置为根据所述数据收集信息确定第一管控组件，其中，所述第一管控组件用于根据所述第二数据处理请求进行数据收集，所述目标管控组件为所述第一管控组件；和/或
第二确定子模块，设置为根据所述配置信息确定第二管控组件，其中，所述第二管控组件用于根据所述第二数据处理请求进行配置，所述目标管控组件为所述第二管控组件。
在一示例性实施例中，所述第一确定子模块，还设置为
基于所述第一数据处理请求与管控组件的目录服务信息，确定所述第一管控组件；或者
确定所述数据收集信息指示的管控组件为所述第一管控组件。
在一示例性实施例中，所述第二确定子模块，还设置为
基于所述第一数据处理请求与管控组件的目录服务信息，确定所述第二管控组件；或者
确定所述配置信息指示的管控组件为所述第二管控组件。
在一示例性实施例中，所述生成模块包括：
第一生成子模块，设置为在所述目标管控组件为所述第一管控组件的情况下，根据所述数据收集信息生成数据收集请求，其中，所述第二数据处理请求为所述数据收集请求，所述数据收集请求中还携带有以下至少之一：待收集的数据类型、数据更新起止时间、收集得到的数据的传递方式；
第二生成子模块，设置为在所述目标管控组件为所述第二管控组件的情况下，根据所述配置信息生成配置请求或者根据所述配置信息与所述第一管控组件返回的数据处理结果生成所述配置请求，其中，所述第二数据处理请求为所述配置请求，所述配置请求中携带有配置接口及参数。
在一示例性实施例中，所述数据类型包括以下至少之一：链路占用率和/或拓扑。
在一示例性实施例中，所述第一接收模块包括：
第一接收子模块，设置为接收网络呼叫控制器发送的所述第一数据处理请求；或者
第二接收子模块，设置为接收客户上下文发送的所述第一数据处理请求；或者
第三接收子模块，设置为接收协议控制器发送的所述第一数据处理请求。
在一示例性实施例中，在将所述第二数据处理请求发送给所述目标管控组件之后，所述装置还包括：
第二接收模块，设置为接收所述目标管控组件返回的数据处理结果；
第二发送模块，设置为将所述数据处理结果发送给所述网络呼叫控制器、所述客户上下文或所述协议控制器。
在另一示例性实施例中，所述第一管控组件包括：链路资源管理器LRM、路由控制器RC、连接控制器CC、网络呼叫控制器NCC、路由数据库RDB、终结和适配执行器TAP，所述第二管控组件包括：链路资源管理器LRM、路由控制器RC、连接控制器CC、网络呼叫控制器NCC、路由数据库RDB、终结和适配执行器TAP。
根据本发明的又一个实施例，还提供了一种计算机可读存储介质，所述计算机可读存储介质中存储有计算机程序，其中，所述计算机程序被设置为运行时执行上述任一项方法实施例中的步骤。
根据本发明的又一个实施例，还提供了一种电子装置，包括存储器和处理器，所述存储器中存储有计算机程序，所述处理器被设置为运行所述计算机程序以执行上述任一项方法实施例中的步骤。
通过本发明，接收第一数据处理请求，基于第一数据处理请求中携带的信息确定目标管控组件，根据第一数据处理请求生成第二数据处理请求，并发送给目标管控组件处理，可以解决相关技术中针对管理控制系统，如何基于用户请求行数据处理的问题，实现了基于用户请求进行数据处理。
附图说明
图1是相关技术中的SDN控制器相关组件的示意图；
图2是根据本发明实施例的数据处理方法的流程图；
图3是根据本优选实施例的数据处理装置的框图一；
图4是根据本优选实施例的数据处理装置的框图二；
图5是根据本优选实施例的数据处理装置的框图三；
图6是根据本优选实施例的数据处理装置的框图四；
图7是根据本优选实施例的数据处理装置的框图五；
图8是根据本优选实施例的数据处理装置的框图六；
图9是根据本发明实施例的数据处理装置的结构框图。
具体实施方式
下文中将参考附图并结合实施例来详细说明本发明的实施例。
需要说明的是，本发明的说明书和权利要求书及上述附图中的术语“第一”、“第二”等是用于区别类似的对象，而不必用于描述特定的顺序或先后次序。
在本实施例中提供了一种运行于网络设备中的数据处理方法，图2是根据本发明实施例的数据处理方法的流程图，如图2所示，该流程包括如下步骤：
步骤S202，接收第一数据处理请求，其中，所述第一数据处理请求中携带有数据收集信息和/或配置信息；
在一示例性实施例中，上述步骤S202具体可以包括：接收网络呼叫控制器发送的所述第一数据处理请求；接收客户上下文发送的所述第一数据处理请求；或者接收协议控制器发送的所述第一数据处理请求。
步骤S204，确定目标管控组件；
步骤S206，根据所述第一数据处理请求生成第二数据处理请求；
步骤S208，将所述第二数据处理请求发送给所述目标管控组件，其中，所述目标管控组件用于根据所述第二数据处理请求进行数据收集或配置。
通过上述步骤S202至S208，接收第一数据处理请求，基于第一数据处理请求中携带的信息确定目标管控组件，根据第一数据处理请求生成第二数据处理请求，并发送给目标管控 组件处理，可以解决相关技术中针对管理控制系统，如何基于用户请求行数据处理的问题，实现了基于用户请求进行数据处理。
在一示例性实施例中，上述步骤S202具体可以包括：
根据所述数据收集信息确定第一管控组件，进一步的，基于所述第一数据处理请求与管控组件的目录服务信息，确定所述第一管控组件；或者确定所述数据收集信息指示的管控组件为所述第一管控组件，其中，所述第一管控组件用于根据所述第二数据处理请求进行数据收集，所述目标管控组件为所述第一管控组件；和/或
根据所述配置信息确定第二管控组件，进一步的，基于所述第一数据处理请求与管控组件的目录服务信息，确定所述第二管控组件；或者确定所述配置信息指示的管控组件为所述第二管控组件，其中，所述第二管控组件用于根据所述第二数据处理请求进行配置，所述目标管控组件为所述第二管控组件。在一示例性实施例中，所述第一管控组件具体可以包括：链路资源管理器LRM、路由控制器RC、连接控制器CC、网络呼叫控制器NCC、路由数据库RDB、终结和适配执行器TAP，所述第二管控组件包括：链路资源管理器LRM、路由控制器RC、连接控制器CC、网络呼叫控制器NCC、路由数据库RDB、终结和适配执行器TAP。
在一示例性实施例中，上述步骤S206具体可以包括：
在所述目标管控组件为所述第一管控组件的情况下，根据所述数据收集信息生成数据收集请求，其中，所述第二数据处理请求为所述数据收集请求，所述数据收集请求中还携带有以下至少之一：待收集的数据类型、数据更新起止时间、收集得到的数据的传递方式；
在所述目标管控组件为所述第二管控组件的情况下，根据所述配置信息生成配置请求或者根据所述配置信息与所述第一管控组件返回的数据处理结果生成所述配置请求，其中，所述第二数据处理请求为所述配置请求，所述配置请求中携带有配置接口及参数。
在一示例性实施例中，所述数据类型包括以下至少之一：链路占用率和/或拓扑，其中链路占有率可以是以太链路占用率、SDH链路占用率等。
在一示例性实施例中，在将所述第二数据处理请求发送给所述目标管控组件之后，接收所述目标管控组件返回的数据处理结果，将所述数据处理结果发送给所述网络呼叫控制器、所述客户上下文或所述协议控制器。
本实施例中的源管控组件是指负责收集数据的管控组件，宿管控组件是负责执行指定配置命令的管控组件。
本实施例提供一种数据处理方法，具体包括：
步骤一，收到第一数据处理请求后，确定要交互的源管控组件；
根据第一数据处理请求中的数据收集信息来确定要交互的源管控组件。数据收集信息可包括：要收集的数据类型，提供数据的管控组件等。
优选的，基于所述第一数据处理请求中的数据收集信息与源管控组件之间的目录服务信息，确定要交互的源管控组件。
优选的，所述第一数据处理请求中的数据收集信息，指明要交互的源管控组件；
优选的，所述第一数据处理请求来自网络呼叫控制器；
优选的，所述第一数据处理请求来自客户上下文；
优选的，所述第一数据处理请求来自协议控制器；
步骤二，若有源管控组件，生成第二数据处理请求；否则执行步骤五；
优选的，根据第一数据处理请求中的数据收集信息及步骤一确定的源管控组件，确定所述第二数据处理请求中携带要收集的数据类型、数据更新起止时间、收集数据的传递方式，如实时传回数据，还有定期更新等方式。
步骤三，将所述第二数据处理请求发送给源管控组件；
优选的，按照源管控组件工作流来控制第二数据处理请求的发送顺序。
步骤四，源管控组件处理收到的数据处理请求，并返回收集到的数据；
优选的，所述源管控组件收集符合收集标准的数据；
进一步，将所述返回的数据发送给网络呼叫控制器；
进一步，将所述返回的数据发给客户上下文；
进一步，将所述返回的数据发给协议控制器；
步骤五，确定要交互的宿管控组件，若有宿管控组件，则生成第三数据处理请求；否则，执行步骤八。
优选的，基于所述第一数据处理请求中的配置信息与宿管控组件之间的目录服务信息，确定要交互的宿管控组件。
优选的，所述第一数据处理请求中的配置信息，指明要交互的宿管控组件；
优选的，分析源管控组件返回的数据，确定要交互的宿管控组件；
根据第一数据处理请求中的配置信息来确定所述第三数据处理请求中的配置信息。配置信息可包括：配置的管控组件、要配置的集合，等；第三数据处理请求包括配置接口和参数：
步骤六，将所述第三数据处理请求发送给宿管控组件；
优选的，按照宿管控组件工作流来控制第三数据处理请求的发送顺序。
步骤七，宿管控组件处理第三数据处理请求，返回执行结果；
进一步，将所述执行结果发送给网络呼叫控制器；
进一步，将所述执行结果发给客户上下文；
进一步，将所述执行结果发给协议控制器；
步骤八，结束。
本实施例中的数据控制器，用于收到第一数据处理请求后，确定要交互的源管控组件；生成第二数据处理请求；将所述第二数据处理请求发送给源管控组件；确定要交互的宿管控组件，及第三数据处理请求；向宿管控组件发送第三数据处理请求。
源管控组件(对应上述第一管控组件)，用于接收第二数据处理请求；优选的，所述第二数据处理请求中携带要收集的数据类型、数据更新起止时间等数据收集标准。进一步的数据收集标准还包括收集数据的传递方式，如实时传回数据，还有定期更新等方式。根据第二数据处理请求，收集符合收集标准的数据；返回收集到的数据。
宿管控组件(对应上述第二管控组件)，用于接收第三数据处理请求，处理第三数据处理请求，将执行结果返回给数据控制器。
在本实施例中，需要收集来自RDB中的静态OTN链路拓扑数据以及历史拓扑，需要收集来自RC中的动态拓扑数据。其中，静态拓扑数据是指网络管理者配置的拓扑数据；在过去的不同时刻有不同的拓扑，这些构成了历史拓扑；动态拓扑是通过路由协议或集中控制动态维护的拓扑，如在链路资源发生变化后，根据资源变动情况动态刷新拓扑。
图3是根据本优选实施例的数据处理装置的框图一，如图3所示，包括：
步骤一，接收到第一数据处理请求后，确定要交互的源管控组件；
优选的，基于所述第一数据处理请求与源管控组件之间的目录服务信息，确定要交互的源管控组件。
本实施例中，数据控制器根据第一数据处理请求中的拓扑收集请求与管控组件之间的目录服务配置，可以获知要从RDB和RC中收集数据，其中RDB、RC都是源管控组件。本实施例中，目录服务配置维护着数据收集请求，包括拓扑收集请求，与管控组件之间的对应关系。
除了RDB、RC提供路由数据外，LRM组件至少能提供当前链路资源的分配使用情况，以及本地链路拓扑；NCC至少能提供当前维护的呼叫数目，以及呼叫的具体信息，如带宽、运行时间等；CC组件至少能提供当前维护的连接数据，如当前连接经过的节点跳数，连接保护恢复执行情况等；TAP组件至少能提供转发点与子网点之间的绑定关系，表明资源是专用的，还是共享的。这些管控组件都可以作为源管控组件。
步骤二，若有源管控组件，生成第二数据处理请求；否则执行步骤五；
优选的，所述第二数据处理请求中携带要收集的数据类型、数据更新起止时间等数据收集标准。进一步的数据收集标准还包括收集数据的传递方式，如实时传回数据，还有定期更新等方式。
本实施例中，源管控组件是RDB和RC。生成的第二数据处理请求中数据类型为拓扑，具体为OTN拓扑，其他数据类型还包括以太链路拓扑、WDM拓扑等。
步骤三，将所述第二数据处理请求发送给源管控组件；
优选的，按照源管控组件工作流来控制第二数据处理请求的发送顺序。
本实施例中，数据控制器将第二数据处理请求发送给源管控组件RC和RDB。
步骤四，源管控组件处理收到的数据处理请求，并返回收集到的数据；
步骤五，确定要交互的宿管控组件，若有宿管控组件，则生成第三数据处理请求；否则，结束。
在本实施例中，数据控制器收到外部请求来驱动RC模块启动重路由优化。
步骤一，收到第一数据处理请求后，确定要交互的源管控组件；
本实施例中，没有源管控组件。流程跳转到步骤五。
步骤五，确定要交互的宿管控组件，若有宿管控组件，则根据第一数据处理请求生成第三数据处理请求；否则，执行步骤八。
在一实施例中，所述第一数据处理请求中的配置信息可以包括：宿数据类型、配置集合，第三数据处理请求包括：配置接口和参数。基于所述第一数据处理请求中的配置信息中的宿数据类型与宿管控组件之间的目录服务信息，确定要交互的宿管控组件。将第一数据处理请求中的配置结合转换为第三数据处理请求中的配置接口和参数。
在本实施例中，若宿数据类型为路由优化、配置集合为待优化的连接标识，第三数据处理请求包括：配置接口为启动重路由，参数为配置集合中的链接标识。基于所述第一数据处理请求中的配置信息中的宿数据类型，即路由优化，与宿管控组件之间的目录服务信息，确定要交互的宿管控组件为RC。将第一数据处理请求中的配置集合转换为第三数据处理请求中的配置接口和参数。
在另一实施例中，所述第一数据处理请求中的配置信息还可以包括：宿管控组件、配置集合，第三数据处理请求包括：配置接口和参数。基于所述第一数据处理请求中的配置信息 中的宿管控组件，将第一数据处理请求中的配置集合转换为第三数据处理请求中的配置接口和参数。
在另一实施例中，第一数据处理请求中的配置信息还可以包括：宿管控组件为RC、配置集合为待优化的连接标识。基于所述第一数据处理请求中的配置信息中的宿管控组件RC，将第一数据处理请求中的配置集合，转换为第三数据处理请求中的配置接口和参数，即配置接口为启动重路由，参数为配置集合中的链接标识。
本实施例中，还可以分析源管控组件返回的数据，确定要交互的宿管控组件，并生成第三数据处理请求，其中包括配置到宿管控组件的操作命令。
步骤六，将所述第三数据处理请求发送给宿管控组件RC；
步骤七，宿管控组件RC处理第三数据处理请求，返回执行结果；
步骤八，结束。
图4是根据本优选实施例的数据处理装置的框图二，如图4所示，在本实施例中，数据控制器收到外部请求来监测LRM中的光传送往(Optical Transmission Net，简称为OTN)链路资源占用，当指定的链路资源占用率超过一定门限后，自动启动经过该链路的连接路由优化。
步骤一，数据控制器接收到第一数据处理请求后，确定要交互的源管控组件；
优选的，基于所述第一数据处理请求与源管控组件之间的目录服务信息，确定要交互的源管控组件。
优选的，所述第一数据处理请求中，指明要交互的源管控组件。
本实施例中，所述第一数据处理请求中，指明要交互的源管控组件为LRM。
优选的，图5是根据本优选实施例的数据处理装置的框图三，如图5所示，所述第一数据处理请求来自网络呼叫控制器；
优选的，图6是根据本优选实施例的数据处理装置的框图四，如图6所示，所述第一数据处理请求来自客户上下文；
优选的，图7是根据本优选实施例的数据处理装置的框图五，如图7所示，所述第一数据处理请求来协议控制器；
步骤二，若有源管控组件，生成第二数据处理请求；否则执行步骤五；
优选的，所述第二数据处理请求中携带要收集的数据类型、数据更新起止时间等数据收集标准。进一步的数据收集标准还包括收集数据的传递方式，如实时传回数据，还有定期更新等方式。
本实施例中，第二数据处理请求中携带要收集的数据类型为链路占用率，具体为OTN链路占用率；实时传回链路占用率。
其他数据类型还包括以太链路占用率、SDH链路占用率等。
步骤三，将所述第二数据处理请求发送给源管控组件；
本实施例中，数据控制器将所述第二数据处理请求发送给源管控组件LRM。
步骤四，源管控组件处理收到的数据处理请求，并返回收集到的数据；
本实施例中的源管控组件LRM收集符合收集标准的数据，即链路占用率数据，并将数据返回给数据控制器；
优选的，如图5所示，将所述返回的数据发送给网络呼叫控制器；
网络呼叫控制器可进一步转发所述返回的数据给其他管控组件或管控系统。
优选的，如图6所示，将所述返回的数据发送给客户上下文；
通过客户上下文，将所述返回的数据传递给与该客户上下文连接的服务上下文。
优选的，如图7所示，将所述返回的数据发送给协议控制器；
通过协议控制器将返回的数据发送给与该协议控制器相连的其他管控系统或应用。
步骤五，确定要交互的宿管控组件，若有宿管控组件，则生成第三数据处理请求；否则，执行步骤八。
本实施例中，第一数据处理情况中指定宿管控组件为RC。
根据LRM收集到的链路占用率数据，判断链路占用率是否超过指定阈值门限，当超过门限时，即需要启动路由优化，由此生成第三数据处理请求，其中，确定配置接口为启动重路由，参数包括链路占用率超过指定阈值门限的链路，且指定重路由避开所述链路。
在管控系统中，除了RC可配置进行路由优化，以及路由计算外，CC组件可配置进行连接创建、删除等操作，LRM可配置改变链路传送资源的管理状态，NCC可配置发起本层或跨层的网络呼叫，TAP可配置改变传送资源交叉以及运维管理维护OAM状态。
步骤六，将所述第三数据处理请求发送给宿管控组件RC；
步骤七，宿管控组件RC处理第三数据处理请求，返回执行结果；
进一步，如图5所示，将所述执行结果发送给网络呼叫控制器；
网络呼叫控制器进一步转发所述执行结果给其他管控组件或管控系统。
进一步，如图6所示，将所述执行结果发给客户上下文；
通过客户上下文，将所述执行结果传递给与该客户上下文连接的服务上下文。
进一步，如图7所示，将所述执行结果发给协议控制器；
通过协议控制器将返回的数据发送给与该协议控制器相连的其他管控系统或应用。
步骤八，结束。
图8是根据本优选实施例的数据处理装置的框图六，如图8所示，在本实施例中，数据控制器收到外部请求来监测LRM中的OTN链路资源占用，并根据历史占用数据来预测链路资源占用。当预测的链路资源占用率超过一定门限后，通过修改传送资源的管理状态限制资源再分配，通过连接路由优化来把链路中的连接迁移到其他链路中。
步骤一，数据控制器接收到第一数据处理请求后，确定要交互的源管控组件；
优选的，基于所述第一数据处理请求与源管控组件之间的目录服务信息，确定要交互的源管控组件。
优选的，所述第一数据处理请求中，指明要交互的源管控组件。
本实施例中，所述第一数据处理请求中，指明要交互的源管控组件为LRM、RC和RDB。
优选的，如图5所示，所述第一数据处理请求来自网络呼叫控制器；
优选的，如图6所示，所述第一数据处理请求来自客户上下文；
优选的，如图7所示，所述第一数据处理请求来协议控制器；
步骤二，若有源管控组件，生成第二数据处理请求；否则执行步骤五；
优选的，所述第二数据处理请求中携带要收集的数据类型、数据更新起止时间等数据收 集标准。进一步的数据收集标准还包括收集数据的传递方式，如实时传回数据，还有定期更新等方式。
本实施例中，有多个源管控组件，收集多种数据。
在构造第二数据处理请求时，可以发给LRM的第二数据处理请求中携带要收集的数据类型为链路占用率，具体为OTN链路占用率；发给RC的第二数据处理请求中携带要收集的数据类型为拓扑，具体为OTN拓扑；发给RDB的第二数据处理请求中携带要收集的数据类型为历史连接数据，具体包含指定时间段内维护的连接信息，如连接数量，每条连接的路由信息等。
也可以在第二数据处理请求中，指定源管控组件及对应的数据类型，具体如下：第二数据处理请求中指定发送给LRM要收集的数据类型为链路占用率，具体为OTN链路占用率；第二数据处理请求中指定发送给RC要收集的数据类型为拓扑，具体为OTN拓扑；第二数据处理请求中指定发送给RDB要收集的数据类型为历史连接数据，具体包含指定时间段内维护的连接信息，如连接数量，每条连接的路由信息等。
步骤三，将所述第二数据处理请求发送给源管控组件；
本实施例中，数据控制器将所述第二数据处理请求发送给源管控组件LRM、RC和RDB。
步骤四，源管控组件处理收到的数据处理请求，并返回收集到的数据；
本实施例中的源管控组件LRM收集符合收集标准的数据，即链路占用率数据，并将数据返回给数据控制器；源管控组件RC收集符合收集标准的数据，即拓扑数据，并将数据返回给数据控制器；源管控组件RDB收集符合收集标准的数据，即历史连接数据，并将数据返回给数据控制器；
优选的，如图5所示，将所述返回的数据发送给网络呼叫控制器；
网络呼叫控制器可进一步转发所述返回的数据给其他管控组件或管控系统。
优选的，如图6所示，将所述返回的数据发送给客户上下文；
通过客户上下文，将所述返回的数据传递给与该客户上下文连接的服务上下文。
优选的，如图7所示，将所述返回的数据发送给协议控制器；
通过协议控制器将返回的数据发送给与该协议控制器相连的其他管控系统或应用。
步骤五，确定要交互的宿管控组件，若有宿管控组件，则生成第三数据处理请求；否则，执行步骤八。
本实施例中，第一数据处理情况中指定宿管控组件为LRM和RC。
根据从LRM收集到的链路占用率数据、从RDB收集到的历史连接数据以及从RC收集到的拓扑数据，来预测判断链路占用率可能超过指定阈值门限。简单的预测判断方法包括根据历史连接的创建/删除时间，维护的连接数量等线性预测。当预测超过门限时，生成发给LRM的第三数据处理请求，其中确定配置接口为修改传送资源的管理状态，参数包括：将管理状态从使能改为去使能；生成发给RC的第三数据处理请求，其中，确定配置接口为启动重路由，参数包括预测的链路占用率超过指定阈值门限的链路，且指定重路由避开所述链路。
步骤六，将所述第三数据处理请求发送给宿管控组件LRM和RC；
步骤七，宿管控组件LRM和RC处理第三数据处理请求，返回执行结果；
进一步，如图5所示，将所述执行结果发送给网络呼叫控制器；
网络呼叫控制器进一步转发所述执行结果给其他管控组件或管控系统。
进一步，如图6所示，将所述执行结果发给客户上下文；
通过客户上下文，将所述执行结果传递给与该客户上下文连接的服务上下文。
进一步，如图7所示，将所述执行结果发给协议控制器；
通过协议控制器将返回的数据发送给与该协议控制器相连的其他管控系统或应用。
步骤八，结束。
通过以上的实施方式的描述，本领域的技术人员可以清楚地了解到根据上述实施例的方法可借助软件加必需的通用硬件平台的方式来实现，当然也可以通过硬件，但很多情况下前者是更佳的实施方式。基于这样的理解，本发明的技术方案本质上或者说对现有技术做出贡献的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质(如ROM/RAM、磁碟、光盘)中，包括若干指令用以使得一台终端设备(可以是手机，计算机，服务器，或者网络设备等)执行本发明各个实施例所述的方法。
在本实施例中还提供了一种数据处理装置，该装置用于实现上述实施例及优选实施方式，已经进行过说明的不再赘述。如以下所使用的，术语“模块”可以实现预定功能的软件和/或硬件的组合。尽管以下实施例所描述的装置较佳地以软件来实现，但是硬件，或者软件和硬件的组合的实现也是可能并被构想的。
图9是根据本发明实施例的数据处理装置的结构框图，如图9所示，包括：
第一接收模块92，设置为接收第一数据处理请求，其中，所述第一数据处理请求中携带有数据收集信息和/或配置信息；
确定模块94，设置为确定目标管控组件；
生成模块96，设置为根据所述第一数据处理请求生成第二数据处理请求；
第一发送模块98，设置为将所述第二数据处理请求发送给所述目标管控组件，其中，所述目标管控组件用于根据所述第二数据处理请求进行数据收集或配置。
在一示例性实施例中，所述确定模块包94括：
第一确定子模块，设置为根据所述数据收集信息确定第一管控组件，其中，所述第一管控组件用于根据所述第二数据处理请求进行数据收集，所述目标管控组件为所述第一管控组件；和/或
第二确定子模块，设置为根据所述配置信息确定第二管控组件，其中，所述第二管控组件用于根据所述第二数据处理请求进行配置，所述目标管控组件为所述第二管控组件。
在一示例性实施例中，所述第一确定子模块，还设置为
基于所述第一数据处理请求与管控组件的目录服务信息，确定所述第一管控组件；或者
确定所述数据收集信息指示的管控组件为所述第一管控组件。
在一示例性实施例中，所述第二确定子模块，还设置为
基于所述第一数据处理请求与管控组件的目录服务信息，确定所述第二管控组件；或者
确定所述配置信息指示的管控组件为所述第二管控组件。
在一示例性实施例中，所述生成模块96包括：
第一生成子模块，设置为在所述目标管控组件为所述第一管控组件的情况下，根据所述数据收集信息生成数据收集请求，其中，所述第二数据处理请求为所述数据收集请求，所述数据收集请求中还携带有以下至少之一：待收集的数据类型、数据更新起止时间、收集得到的数据的传递方式；
第二生成子模块，设置为在所述目标管控组件为所述第二管控组件的情况下，根据所述配置信息生成配置请求或者根据所述配置信息与所述第一管控组件返回的数据处理结果生成所述配置请求，其中，所述第二数据处理请求为所述数据收集请求所述配置请求中携带有配置接口及参数。
在一示例性实施例中，所述数据类型包括：链路占用率和/或拓扑。
在一示例性实施例中，所述第一接收模块92包括：
第一接收子模块，设置为接收网络呼叫控制器发送的所述第一数据处理请求；或者
第二接收子模块，设置为接收客户上下文发送的所述第一数据处理请求；或者
第三接收子模块，设置为接收协议控制器发送的所述第一数据处理请求。
在一示例性实施例中，在将所述第二数据处理请求发送给所述目标管控组件之后，所述装置还包括：
第二接收模块，设置为接收所述目标管控组件返回的数据处理结果；
第二发送模块，设置为将所述数据处理结果发送给所述网络呼叫控制器、所述客户上下文或所述协议控制器。
在另一示例性实施例中，所述第一管控组件包括：链路资源管理器LRM、路由控制器RC、连接控制器CC、网络呼叫控制器NCC、路由数据库RDB、终结和适配执行器TAP，所述第二管控组件包括：链路资源管理器LRM、路由控制器RC、连接控制器CC、网络呼叫控制器NCC、路由数据库RDB、终结和适配执行器TAP。
需要说明的是，上述各个模块是可以通过软件或硬件来实现的，对于后者，可以通过以下方式实现，但不限于此：上述模块均位于同一处理器中；或者，上述各个模块以任意组合的形式分别位于不同的处理器中。
本发明的实施例还提供了一种计算机可读存储介质，该计算机可读存储介质中存储有计算机程序，其中，该计算机程序被设置为运行时执行上述任一项方法实施例中的步骤。
在一个示例性实施例中，上述计算机可读存储介质可以包括但不限于：U盘、只读存储器(Read-Only Memory，简称为ROM)、随机存取存储器(Random Access Memory，简称为RAM)、移动硬盘、磁碟或者光盘等各种可以存储计算机程序的介质。
本发明的实施例还提供了一种电子装置，包括存储器和处理器，该存储器中存储有计算机程序，该处理器被设置为运行计算机程序以执行上述任一项方法实施例中的步骤。
在一个示例性实施例中，上述电子装置还可以包括传输设备以及输入输出设备，其中，该传输设备和上述处理器连接，该输入输出设备和上述处理器连接。
本实施例中的具体示例可以参考上述实施例及示例性实施方式中所描述的示例，本实施例在此不再赘述。
显然，本领域的技术人员应该明白，上述的本发明的各模块或各步骤可以用通用的计算装置来实现，它们可以集中在单个的计算装置上，或者分布在多个计算装置所组成的网络上，它们可以用计算装置可执行的程序代码来实现，从而，可以将它们存储在存储装置中由计算装置来执行，并且在某些情况下，可以以不同于此处的顺序执行所示出或描述的步骤，或者 将它们分别制作成各个集成电路模块，或者将它们中的多个模块或步骤制作成单个集成电路模块来实现。这样，本发明不限制于任何特定的硬件和软件结合。
以上所述仅为本发明的优选实施例而已，并不用于限制本发明，对于本领域的技术人员来说，本发明可以有各种更改和变化。凡在本发明的原则之内，所作的任何修改、等同替换、改进等，均应包含在本发明的保护范围之内。

Claims (12)

  1. 一种数据处理方法，包括：
    接收第一数据处理请求，其中，所述第一数据处理请求中携带有数据收集信息和/或配置信息；
    确定目标管控组件；
    根据所述第一数据处理请求生成第二数据处理请求；
    将所述第二数据处理请求发送给所述目标管控组件，其中，所述目标管控组件用于根据所述第二数据处理请求进行数据收集或配置。
  2. 根据权利要求1所述的方法，其中，确定所述目标管控组件包括：
    根据所述数据收集信息确定第一管控组件，其中，所述第一管控组件用于根据所述第二数据处理请求进行数据收集，所述目标管控组件为所述第一管控组件；和/或
    根据所述配置信息确定第二管控组件，其中，所述第二管控组件用于根据所述第二数据处理请求进行配置，所述目标管控组件为所述第二管控组件。
  3. 根据权利要求2所述的方法，其中，根据所述数据收集信息确定所述第一管控组件包括：
    基于所述第一数据处理请求与管控组件的目录服务信息，确定所述第一管控组件；或者
    确定所述数据收集信息指示的管控组件为所述第一管控组件。
  4. 根据权利要求2所述的方法，其中，根据所述配置信息确定所述第二管控组件包括：
    基于所述第一数据处理请求与管控组件的目录服务信息，确定所述第二管控组件；或者
    确定所述配置信息指示的管控组件为所述第二管控组件。
  5. 根据权利要求2所述的方法，其中，根据所述第一数据处理请求生成所述第二数据处理请求包括：
    在所述目标管控组件为所述第一管控组件的情况下，根据所述数据收集信息生成数据收集请求，其中，所述第二数据处理请求为所述数据收集请求，所述数据收集请求中还携带有以下至少之一:待收集的数据类型、数据更新起止时间、收集得到的数据的传递方式；
    在所述目标管控组件为所述第二管控组件的情况下，根据所述配置信息生成配置请求或者根据所述配置信息与所述第一管控组件返回的数据处理结果生成所述配置请求，其中，所述第二数据处理请求为所述配置请求，所述配置请求中携带有配置接口及参数。
  6. 根据权利要求5所述的方法，其中，所述数据类型包括：链路占用率和/或拓扑。
  7. 根据权利要求1所述的方法，其中，接收所述第一数据处理请求包括：
    接收网络呼叫控制器发送的所述第一数据处理请求；或者
    接收客户上下文发送的所述第一数据处理请求；或者
    接收协议控制器发送的所述第一数据处理请求。
  8. 根据权利要求7所述的方法，其中，在将所述第二数据处理请求发送给所述目标管控组件之后，所述方法还包括：
    接收所述目标管控组件返回的数据处理结果；
    将所述数据处理结果发送给所述网络呼叫控制器、所述客户上下文或所述协议控制器。
  9. 根据权利要求1至8中任一项所述的方法，其中，所述第一管控组件包括：链路资源 管理器LRM、路由控制器RC、连接控制器CC、网络呼叫控制器NCC、路由数据库RDB、终结和适配执行器TAP，所述第二管控组件包括：链路资源管理器LRM、路由控制器RC、连接控制器CC、网络呼叫控制器NCC、路由数据库RDB、终结和适配执行器TAP。
  10. 一种数据处理装置，包括：
    第一接收模块，设置为接收第一数据处理请求，其中，所述第一数据处理请求中携带有数据收集信息和/或配置信息；
    确定模块，设置为确定目标管控组件；
    生成模块，设置为根据所述第一数据处理请求生成第二数据处理请求；
    第一发送模块，设置为将所述第二数据处理请求发送给所述目标管控组件，其中，所述目标管控组件用于根据所述第二数据处理请求进行数据收集或配置。
  11. 一种计算机可读存储介质，所述权利要求1至9任一项中所述的方法。
  12. 一种电子装置，包括存储器和处理器，所述存储器中存储有计算机程序，所述处理器被设置为运行所述计算机程序以执行所述权利要求1至9任一项中所述的方法。
PCT/CN2021/094301 2020-07-23 2021-05-18 一种数据处理方法及装置 WO2022016969A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
US18/017,429 US20230275807A1 (en) 2020-07-23 2021-05-18 Data processing method and device
EP21846800.7A EP4187814A4 (en) 2020-07-23 2021-05-18 DATA PROCESSING METHOD AND DEVICE

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202010719569.9 2020-07-23
CN202010719569.9A CN112491574A (zh) 2020-07-23 2020-07-23 一种数据处理方法及装置

Publications (1)

Publication Number Publication Date
WO2022016969A1 true WO2022016969A1 (zh) 2022-01-27

Family

ID=74920088

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/094301 WO2022016969A1 (zh) 2020-07-23 2021-05-18 一种数据处理方法及装置

Country Status (4)

Country Link
US (1) US20230275807A1 (zh)
EP (1) EP4187814A4 (zh)
CN (1) CN112491574A (zh)
WO (1) WO2022016969A1 (zh)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112491574A (zh) * 2020-07-23 2021-03-12 中兴通讯股份有限公司 一种数据处理方法及装置
CN118215160A (zh) * 2022-12-15 2024-06-18 中兴通讯股份有限公司 连接交互方法、通信设备、存储介质和程序产品

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2007019727A1 (fr) * 2005-08-15 2007-02-22 Zte Corporation Nœud de commande complexe dans des réseaux de transport à commutation automatique et méthode de commande de celui-ci
CN107872338A (zh) * 2016-09-26 2018-04-03 中兴通讯股份有限公司 网络管理系统，业务配置、业务配置请求方法及装置
CN111371593A (zh) * 2020-02-24 2020-07-03 中移（杭州）信息技术有限公司 一种业务部署方法、装置、电子设备及存储介质
CN112491574A (zh) * 2020-07-23 2021-03-12 中兴通讯股份有限公司 一种数据处理方法及装置

Family Cites Families (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104113791A (zh) * 2013-04-19 2014-10-22 中兴通讯股份有限公司 一种自动交换光网络演进系统及方法
US9538573B2 (en) * 2014-06-13 2017-01-03 Ciena Corporation Systems and methods for managing call connections from non-originating nodes in networks
CN105991430B (zh) * 2015-03-05 2022-01-14 李明 跨多个自治网络系统的数据路由
US10148496B2 (en) * 2015-05-05 2018-12-04 Citrix Systems, Inc. Systems and methods for configuring a device via a software-defined networking controller
CN107360115A (zh) * 2016-05-09 2017-11-17 中兴通讯股份有限公司 一种sdn网络防护方法及装置
CN108462633B (zh) * 2016-12-09 2021-05-28 中兴通讯股份有限公司 基于sdn的网络安全路由调度方法及系统
CN108989066B (zh) * 2017-05-31 2022-12-20 中兴通讯股份有限公司 设备管理方法及装置
CN107360100B (zh) * 2017-07-31 2019-11-15 中通服咨询设计研究院有限公司 一种基于sdn技术的网络流量编排系统和方法
US10511524B2 (en) * 2017-10-03 2019-12-17 Futurewei Technologies, Inc. Controller communications in access networks
CN108712308B (zh) * 2018-06-06 2021-11-26 郑州云海信息技术有限公司 虚拟网络中检测网络设备的方法和装置

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2007019727A1 (fr) * 2005-08-15 2007-02-22 Zte Corporation Nœud de commande complexe dans des réseaux de transport à commutation automatique et méthode de commande de celui-ci
CN107872338A (zh) * 2016-09-26 2018-04-03 中兴通讯股份有限公司 网络管理系统，业务配置、业务配置请求方法及装置
CN111371593A (zh) * 2020-02-24 2020-07-03 中移（杭州）信息技术有限公司 一种业务部署方法、装置、电子设备及存储介质
CN112491574A (zh) * 2020-07-23 2021-03-12 中兴通讯股份有限公司 一种数据处理方法及装置

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP4187814A4 *

Also Published As

Publication number Publication date
CN112491574A (zh) 2021-03-12
EP4187814A1 (en) 2023-05-31
US20230275807A1 (en) 2023-08-31
EP4187814A4 (en) 2023-12-27

Similar Documents

Publication Publication Date Title
CN113364850B (zh) 软件定义云边协同网络能耗优化方法和系统
CN113448721A (zh) 算力处理的网络系统及算力处理方法
CN108449350B (zh) 一种多协议编排方法及装置
US10893111B1 (en) Developing and implementing migration sequences in data communication networks
WO2022016969A1 (zh) 一种数据处理方法及装置
JP2015522996A (ja) 接続サービス調整器
US10581679B1 (en) Migrating services in data communication networks
EP3100163A1 (en) Methods, systems, and computer readable media for a cloud-based virtualization orchestrator
US20140226975A1 (en) Method and apparatus for boosting data intensive processing through optical circuit switching
US20150263985A1 (en) Systems and methods for intelligent workload routing
Van der Boor et al. Scalable load balancing in networked systems: Universality properties and stochastic coupling methods
CN112532674A (zh) 一种网络边缘计算系统的创建方法、装置及介质
CN114500405A (zh) 一种多类型业务应用的资源分配、获取方法及装置
CN110366056B (zh) 一种ason业务模型的实现方法、装置、设备及存储介质
Liu et al. Service resource management in edge computing based on microservices
CN117149445B (zh) 一种跨集群负载均衡方法及装置、设备及存储介质
US20150372895A1 (en) Proactive Change of Communication Models
CN116886496A (zh) 基于dpu的数据处理方法、装置、设备及可读存储介质
KR102201799B1 (ko) 소프트웨어 정의 네트워크 기반 포그 시스템에서의 동적 로드밸런싱 방법 및 동적 로드밸런싱 장치
Tkachova et al. A load balancing algorithm for SDN
Gadre et al. Centralized approaches for virtual network function placement in SDN-enabled networks
CN114448868B (zh) 一种基于分段路由策略的路径调度方法、装置及设备
WO2022166715A1 (zh) 一种智能流水线处理方法、装置、存储介质及电子装置
Amarasinghe et al. Survivable IaaS management with SDN
US10986036B1 (en) Method and apparatus for orchestrating resources in multi-access edge computing (MEC) network

Legal Events

Date Code Title Description
WWE Wipo information: entry into national phase

Ref document number: 2021846800

Country of ref document: EP

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2021846800

Country of ref document: EP

Effective date: 20230223