WO2017185992A1 - 一种请求消息传输方法及装置 - Google Patents

一种请求消息传输方法及装置 Download PDF

Info

Publication number
WO2017185992A1
WO2017185992A1 PCT/CN2017/080289 CN2017080289W WO2017185992A1 WO 2017185992 A1 WO2017185992 A1 WO 2017185992A1 CN 2017080289 W CN2017080289 W CN 2017080289W WO 2017185992 A1 WO2017185992 A1 WO 2017185992A1
Authority
WO
WIPO (PCT)
Prior art keywords
driver
controller
group
adaptation plug
adapter
Prior art date
Application number
PCT/CN2017/080289
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 EP17788644.7A priority Critical patent/EP3402123B1/en
Priority to EP20165801.0A priority patent/EP3737039B1/en
Publication of WO2017185992A1 publication Critical patent/WO2017185992A1/zh
Priority to US16/102,625 priority patent/US10884880B2/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
    • 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
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/16—Error detection or correction of the data by redundancy in hardware
    • G06F11/20—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F13/00—Interconnection of, or transfer of information or other signals between, memories, input/output devices or central processing units
    • G06F13/10—Program control for peripheral devices
    • G06F13/105—Program control for peripheral devices where the programme performs an input/output emulation function
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F13/00—Interconnection of, or transfer of information or other signals between, memories, input/output devices or central processing units
    • G06F13/14—Handling requests for interconnection or transfer
    • G06F13/36—Handling requests for interconnection or transfer for access to common bus or bus system
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/445—Program loading or initiating
    • G06F9/44521—Dynamic linking or loading; Link editing at or after load time, e.g. Java class loading
    • G06F9/44526—Plug-ins; Add-ons
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • G06F9/45533—Hypervisors; Virtual machine monitors
    • G06F9/45558—Hypervisor-specific management and integration aspects
    • 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/0805—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/08—Protocols for interworking; Protocol conversion
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • G06F9/45533—Hypervisors; Virtual machine monitors
    • G06F9/45558—Hypervisor-specific management and integration aspects
    • G06F2009/45595—Network integration; Enabling network access in virtual machine instances

Definitions

  • the present invention relates to the field of communications technologies, and in particular, to a request message transmission method and apparatus.
  • ICT Information and Communications Technology
  • an ICT network mainly including an ICT-Orchestration (ICT-O) system, and a plurality of controllers
  • ICT-O system is also referred to as a service orchestration system
  • the ICT-O system is configured to receive from The user's business request, and the business request is decomposed and redesigned, converted into multiple request messages that the controller in the network can understand and execute, and the multiple request messages are scheduled and processed, and each request is processed.
  • the message is forwarded to a corresponding controller, and the ICT-O system can be divided into multiple logic modules according to different execution functions, for example, a service decomposition design module for decomposing and redesigning the service request, for multiple An executor that requests a message for scheduling processing, a distributor for forwarding each request message, etc.; the controller has a logical control function deployed between the ICT-O system and a network device and/or infrastructure, And sending, according to the received request message in the ICT-O system, a network instruction corresponding to the request message to a network device and/or an infrastructure corresponding to the request message.
  • the ICT-O system and each controller interact in the network via a driver adaptation plug-in.
  • the ICT-O system in the network After receiving the service request made by the user for one type of service, the ICT-O system in the network decomposes the service request to generate multiple request messages, and each request message includes its corresponding target.
  • the controller identifies, and sends the multiple request messages to the distributor through the executor; after receiving a request message, the distributor performs load balancing on multiple driver adaptation plugins, and selects an appropriate one.
  • the present invention provides a request message transmission method and apparatus for solving the problem that the ICT network in the prior art increases the probability of request message transmission failure when transmitting a request message, and reduces the reliability of request message transmission.
  • an embodiment of the present invention provides a request message transmission method, which may be applicable to an ICT-O system in an ICT network, where the distributor may be a distribution function in the ICT-O system.
  • the method includes:
  • the distributor After receiving the request message after the ICT-O system decomposes the service request, the distributor first obtains the information of the first controller included in the request message, for example, the unique identifier of the routing identifier of the first controller, and the like. Determining the first control in the correspondence between the information of the plurality of controllers stored in the local or other storage devices in the ICT-O system and the driver adaptation plug-in group, Corresponding to the first driver adapter group corresponding to the information, wherein the first controller is connected to at least one driver adapter included in the first driver adapter group; the distributor obtains the An operating state of the at least one driver adapter plug-in connected to the first controller included in the driver adapter group, and determining at least one candidate driver adapter plug-in in which the running state is normal; finally, The distributor sends the request message to the first controller through one of the at least one candidate drive adaptation plug-in.
  • the distributor since at least one driver adaptation plug-in included in the first driver adapter group is connected to the first controller, the distributor is guaranteed to be included in the first driver adaptation plug-in group. Any one of the driver adaptation plug-ins can successfully transmit the request message to the first controller, which reduces the probability of request message transmission failure due to the controller not being connected to the driver adaptation plug-in, and improves the request message.
  • the distributor filters out at least one candidate driver adapter that is in a normal running state in the at least one driver adaptation plug-in included in the first driver adapter group, further ensuring The distributor can successfully transmit the request message to the first controller through one of the candidate driver adaptation plug-ins, thereby avoiding a situation in which the request message transmission fails due to abnormal operation of the driver adaptation plug-in.
  • the information of the first controller is a route identifier of the first controller, the route identifier can uniquely identify the first controller, and information of the first controller is also It is information such as the identifier of the first controller.
  • each of the drive adaptation plug-ins included in the first drive adaptation plug-in group is of the same type. Due to different types of driver adaptation plug-ins, the maintained interfaces are different, so that the interface of each of the driver adaptation plug-ins included in the first driver adaptation plug-in group matches the interface of the first controller.
  • the distribution The device can ensure that the request message is successfully transmitted to the first controller by using any one of the driver adaptation plug-ins included in the first driver adaptation plug-in group, thereby reducing the adapter and driver adaptation plug-in.
  • the probability of request message transmission failure caused by interface mismatch improves the reliability of request message transmission.
  • the type of each driver adapter inserted in the first driver adapter group in the above design is the same as that of the first controller. Type match.
  • the request message further includes a first type of the driver adaptation plug-in;
  • the distributor needs to first acquire the first type included in the request message; determine, in the at least one driver adaptation plug-in, the at least one candidate that has the same type as the first type and whose running status is normal
  • the adaptation plug-in is driven to obtain the at least one candidate drive adaptation plug-in.
  • the first type of the driver adaptation plug-in included in the request message indicates that the distributor can successfully transmit the request message to the first controller only through the first type of driver adaptation plug-in. In other words, the interface of the first type of driver adaptation plug-in is matched with the interface of the first controller. Match.
  • the distributor may subsequently select at least one candidate driver adapter of the first type in the first driver adapter group, and the distributor may ensure that the at least one candidate driver is passed.
  • Any one of the adaptation plug-ins can successfully transmit the request message to the first controller, which reduces the probability of request message transmission failure due to mismatch between the controller and the driver adapter interface. Improves the reliability of request message transmission.
  • the number of connection limits of each of the plurality of controllers corresponding to the first driver adapter group is the same And the number of the driver adapters included in the first driver adapter group is less than or equal to the number of connection limits of each controller corresponding to the first driver adapter group.
  • the distributor when the first controller has the connection limit number, the distributor can ensure that the request message can be successfully successfully performed by any one of the first driver adaptation plug-in groups. Transmitting to the first controller to prevent the target driver selected by the distributor when the number of the driver adapters included in the first driver adapter group is greater than the number of connection constraints of the first controller If the request message fails to be transmitted by the first control, the request message transmission fails, which improves the reliability of the request message transmission.
  • the attribution of each controller of the plurality of controllers corresponding to the first driver adapter group is the same.
  • the distributor can ensure that the request message can be successfully transmitted to the first controller by using any one of the first driver adaptation plug-in groups, avoiding When there is a driver adaptation plug-in in the first driver adaptation plug-in group that is different from the home location of the first controller, the target driver adaptation plug-in selected by the distributor is different from the first control attribution.
  • the request message transmission failure condition improves the reliability of the request message transmission.
  • the distributor when the number of the at least one candidate driver adapter is multiple, the distributor is in the candidate driver adapter through the at least one candidate driver adapter. And sending the request message to the first controller, by performing load balancing processing on the plurality of candidate driver adapters, thereby determining a target in the plurality of candidate driver adapters The adaptation plugin is driven, however the request message is sent to the first controller via the determined target drive adaptation plugin.
  • the distributor performs load balancing processing on the at least one candidate driver adapter to determine one of the target driver adapters, and can ensure load balancing of the at least one candidate driver adapter.
  • the method for load balancing processing used by the distributor may include various methods, such as a polling method according to a set order, a random selection method, or the like, or selecting a method conforming to a set feature.
  • the distributor may perform load balancing processing on the at least one candidate driver adaptation plug-in to determine one of the target driver adaptation plug-ins.
  • the embodiment of the present invention further provides a method for generating a correspondence between a controller information and a driver adaptation plug-in group, and the method can be applied to an ICT-O system in an ICT network, and the packet manager in the method.
  • the middle packet manager is deployed in the ICT-O system, and the method includes:
  • At least one driver adaptation plug-in connected to the controller is determined in multiple driver adaptation plug-ins in the ICT network; finally, information and driver of the controller are generated.
  • Adapter plugin Corresponding relationship of the group the at least one driver adaptation plug-in is included in the driver adaptation plug-in group.
  • the distributor since at least one driver adaptation plug-in included in the driver adaptation plug-in group is connected to the controller, the distributor is guaranteed to be adapted by any one of the drivers included in the driver adaptation plug-in group.
  • the plug-in can successfully transmit the request message to the controller, which reduces the probability of request message transmission failure due to the controller not being connected to the driver adapter, and improves the reliability of the request message transmission.
  • the information of the controller is a route identifier of the controller, the route identifier can uniquely identify the controller, and the information of the first controller may also be the Information such as the identity of a controller.
  • the group manager may determine at least one driver adaptation plug-in corresponding to the controller in the plurality of driver adaptation plug-ins by driving the type of the adapter plug-in, that is, acquiring the plurality of The type of each driver adaptation plug-in group in the driver plug-in is driven, and then the at least one driver adapter plug of the same type is determined among the plurality of driver adapter plug-ins.
  • the selected types of the at least one driver adapter are the same, and the interface of the driver adapter of the type matches the interface of the controller, and the distributor can ensure that the at least one driver is Any one of the adaptation plug-ins can successfully transmit the request message to the controller, which reduces the probability of request message transmission failure due to the mismatch between the controller and the driver adapter interface, and improves the request. The reliability of message transmission.
  • the number of the at least one drive adapter is less than or equal to the number of connection limits of the controller. In this way, when the controller has a connection limit number, the distributor can ensure that the request message can be successfully transmitted to the control through any one of the at least one driver adaptation plug-ins. If the number of the at least one driver adaptation plug-in is greater than the number of connection restrictions of the controller, the target drive adaptation plug-in selected by the distributor does not transmit the request message due to the control connection failure, Improve the reliability of request message transmission.
  • the attribution of the at least one drive adapter is the same as the home of the controller.
  • the distributor can ensure that the request message can be successfully transmitted to the controller through any one of the at least one driver adaptation plug-in, avoiding that the at least one driver is suitable
  • the target drive adaptation plug-in selected by the distributor is different from the control attribution, and the request message transmission fails. The reliability of request message transmission.
  • the packet manager after the packet manager generates a correspondence between the information of the controller and the driver adaptation plug-in group, the packet manager obtains an operation status of the at least one driver adaptation plug-in, for example
  • the packet manager may periodically acquire the running status of the at least one driver adapter, or the at least one driver adapter may periodically report the running status of the at least one driver adapter, or
  • the at least one driver adapting plug-in determines that the running status of the driver changes, the current running state of the driver is reported, so that the group manager can perform the running state of the at least one driver adapting plug-in in the driver adapting plug-in group. Update.
  • the packet manager may determine an operating state of each driver adaptation plug-in in the driver adaptation plug-in group corresponding to the controller. After the identifier of the at least one driver adaptation plug-in acquired by the packet manager, the distributor may filter out the operation according to the running state of the at least one driver adaptation plug-in obtained by the packet manager. At least one candidate drive adapter plugin in a normal state.
  • the packet manager pairs the generated information of the controller and the driver adaptation plug-in group The corresponding relationship is post-maintained. For example, when the controller logs out, the group manager deletes the correspondence between the information of deleting the controller and the driver adapter group; the driver adaptation in the driver adapter group When the plug-in is logged out, deleting the deactivated driver adaptation plug-in in the driver adaptation plug-in group corresponding to the controller; when the distributor sends a request message according to a target driver adaptation plug-in in the driver adaptation plug-in group When the controller fails to send, the packet manager may also delete the target driver adaptation plug-in in the driver adaptation plug-in group corresponding to the controller.
  • the group manager can ensure that each driver adaptation plug-in group in the driver adaptation plug-in group in the correspondence between the information of the controller and the driver adaptation plug-in group is at any time
  • the controller is connected to ensure that the request message can be successfully transmitted to the controller after the distributor can drive the adapter through any one of the driver adaptation plug-in groups.
  • an embodiment of the present invention further provides a distributor having a function of implementing a distributor behavior in the above method example.
  • the functions may be implemented by hardware or by corresponding software implemented by hardware.
  • the hardware or software includes one or more modules corresponding to the functions described above.
  • the structure of the distributor includes a receiving unit, a processing unit, and a sending unit, and the units can perform corresponding functions in the foregoing method examples.
  • the units can perform corresponding functions in the foregoing method examples.
  • the structures can perform corresponding functions in the foregoing method examples.
  • the distributor includes a transceiver, a processor, a bus, and a memory for communicating with a device or module connected to the distributor, the processor being It is configured to support the distributor to perform the corresponding functions in the above methods.
  • the memory is coupled to the processor, which holds program instructions and data necessary for the distributor.
  • an embodiment of the present invention further provides a packet manager, the packet manager having a function of implementing a packet manager behavior in the foregoing method instance.
  • the functions may be implemented by hardware or by corresponding software implemented by hardware.
  • the hardware or software includes one or more modules corresponding to the functions described above.
  • the structure of the packet manager includes a processing unit and a generating unit, and the units may perform the corresponding functions in the foregoing method examples.
  • the units may perform the corresponding functions in the foregoing method examples.
  • the processing unit and a generating unit may perform the corresponding functions in the foregoing method examples.
  • the packet manager includes a transceiver, a processor, a bus, and a memory for communicating with other devices connected to the packet manager, the processor It is configured to support the packet manager to perform the corresponding functions in the above methods.
  • the memory is coupled to the processor, which stores program instructions and data necessary for the packet manager.
  • an embodiment of the present invention provides an ICT-O system including a distributor and a packet manager.
  • the distributor has the function of implementing the behavior of the distributor in the above method instance, the packet manager having the function of implementing the packet manager behavior in the above method instance.
  • embodiments of the present invention provide one or more computer program products comprising a software program that, when executed by one or more processors, implements any one or more of the methods described above.
  • the distributor deployed in the ICT-O system determines the first controller according to the information of the first controller included in the request message after receiving a request message.
  • the distributor is at the first
  • the at least one driver adaptation plug-in included in the driver adaptation plug-in group filters out at least one candidate driver adapter plug-in whose operating state is normal, and finally the distributor can send the request through a candidate driver adapter plug-in A message is sent to the first controller.
  • the distributor Since the at least one driver adapter included in the first driver adapter group is connected to the first controller, the distributor is guaranteed to pass Any one of the driver adaptation plug-ins included in the first driver adapter group can successfully transmit the request message to the first controller, which reduces the connection between the controller and the driver adapter. The probability of requesting the transmission of the message is increased, and the reliability of the request message transmission is improved.
  • the distributor filters out at least one driver adaptation plug-in included in the first driver adaptation plug-in group to at least the normal running state.
  • An optional driver adaptation plug-in further ensures that the distributor can successfully transmit the request message to the first controller through one of the candidate driver adaptation plug-ins, thereby avoiding abnormal operation due to the driver adaptation plug-in The situation that caused the request message transmission to fail.
  • FIG. 1 is a schematic structural diagram of an ICT network according to an embodiment of the present disclosure
  • FIG. 2 is a schematic structural diagram of another ICT network according to an embodiment of the present invention.
  • FIG. 3 is a flowchart of a request message transmission method according to an embodiment of the present invention.
  • FIG. 4 is a schematic flowchart of an example of request message transmission according to an embodiment of the present invention.
  • FIG. 5 is a schematic flowchart of determining, by a distributor, a candidate driver adaptation plug-in according to an embodiment of the present disclosure
  • FIG. 6 is a flowchart of a method for generating a correspondence between a controller information and a driver adaptation plug-in group according to an embodiment of the present invention
  • FIG. 7 is a schematic structural diagram of a distributor according to an embodiment of the present disclosure.
  • FIG. 8 is a schematic structural diagram of a group manager according to an embodiment of the present disclosure.
  • FIG. 9 is a structural diagram of a distributor according to an embodiment of the present invention.
  • FIG. 10 is a structural diagram of a group manager according to an embodiment of the present invention.
  • the embodiment of the invention provides a request message transmission method and device, which is used to solve the problem that the ICT network in the prior art increases the probability of request message transmission failure when transmitting the request message, and reduces the reliability of the request message transmission.
  • the method and the device of the present invention are based on the same inventive concept. Since the principles of the method and the device for solving the problem are similar, the implementation of the device and the method can be referred to each other, and the repeated description is not repeated.
  • the distributor deployed in the ICT-O system determines the information corresponding to the information of the first controller according to the information of the first controller included in the request message.
  • a first driver adapter group wherein the first controller is connected to at least one driver adapter included in the first driver adapter group; the distributor is in the first driver adapter
  • the at least one driver adaptation plug-in included in the group filters out at least one candidate driver adapter plug-in whose operating status is normal, and finally the distributor can send the request message to the portal through a candidate driver adapter plug-in. Said first controller.
  • the at least one driver adapter inserted in the first driver adapter group is connected to the first controller, and the distributor is guaranteed to pass any one of the drivers included in the first driver adapter group.
  • the adaptation plug-in can successfully transmit the request message to the first controller, which reduces the probability of request message transmission failure due to the controller not being connected to the driver adaptation plug-in, and improves the reliability of the request message transmission.
  • the distributor filters out at least one candidate driver adapter that is in a normal running state in the at least one driver adaptation plug-in included in the first driver adapter group, further ensuring the The distributor can successfully transmit the request message to the first controller through one of the candidate driver adaptation plug-ins, thereby avoiding a situation in which the request message transmission fails due to abnormal operation of the driver adaptation plug-in.
  • the request message transmission method provided by the embodiment of the present invention is applicable to an ICT network, as shown in FIG. 1 , and is divided according to a logical function in the network, and the network can be classified into an ICT-O system, a management and control layer, and a network device.
  • Layer where
  • the user can access the ICT-O system, and the user can be an operator user (such as a Business Support System (BSS), an Operation Support System (OSS), an administrator, etc.), an enterprise user, Individual users and developers.
  • BSS Business Support System
  • OSS Operation Support System
  • WEB webpage
  • the user can initiate a service request through a webpage (WEB) console to other systems, such as creating a virtual private network (VPN) from Shenzhen or Beijing, or creating a cloud host on the cloud.
  • VPN virtual private network
  • the ICT-O system receives a service request from a user, and performs processing such as decomposition and redesign of the service request, and converts into multiple request messages that can be understood and executed by a controller in the management and control layer in the network. And scheduling the plurality of request messages, and forwarding each request message to a corresponding controller.
  • the ICT-O system interacts with a controller in the management and control layer through a driver adaptation plug-in.
  • the management and control layer includes a plurality of controllers having logic control and management functions, such as an element management system (EMS)/OSS, an access controller (Access Controller), and a virtualized network function.
  • Virtualised Network Function Manager VNFM
  • IP Internet Protocol
  • IP Intelligent
  • CORE Intelligent
  • the controller in the management and control layer manages and controls the corresponding network device and/or infrastructure according to the request message, that is, to the corresponding network device and/or Or the infrastructure sends network commands.
  • the network device layer includes a network device and an infrastructure, and the like, such as a router, a switch, and the like, where the network device and the infrastructure in the network device layer may be, but not limited to, in the following application scenarios.
  • Equipment Mobile broadband (MBB) network, Fixed broadband (FBB) network, Software Defined Network (SDN), Network Function Virtualization (NFV), Hybrid cloud ).
  • MBB Mobile broadband
  • FBB Fixed broadband
  • SDN Software Defined Network
  • NFV Network Function Virtualization
  • Hybrid cloud Hybrid cloud
  • the embodiment of the present invention provides another possible architecture of the ICT network as shown in FIG. 2.
  • the ICT-O system can be divided into multiple logic modules.
  • the ICT-O system includes services and Instance management module, business decomposition design module, executor, distributor, and group manager. among them,
  • the service and instance management module is an entry of the ICT-O system, and is responsible for receiving a service request sent by the user through the WEB console or other system, and managing the life cycle of the service request, and the user can pass the
  • the business and instance management modules perform operations such as adding, modifying, deleting, and viewing services.
  • the service decomposition design module may convert the service request oriented to the user into a controller in the ICT network by decomposing and redesigning according to the network service design service and the service design service maintained by the ICT-O system.
  • a plurality of device-oriented request messages that can be understood and processed, wherein each request message contains information of its corresponding target controller.
  • the executor according to the constraint relationship and the association relationship between the multiple request messages generated by the decomposition, scheduling the multiple request messages, that is, the executor needs to ensure that the device-oriented request message can be executed quickly and reliably For example, for some request messages that can be processed in parallel, the executor executes these request messages in parallel; The request messages that need to be executed in order, the executors sequentially executing the request messages in the order.
  • the distributor in the plurality of driver adaptation plugins, selects a driver adaptation plugin for each request message, so that each request message can be sent to the corresponding target controller through the selected driver adaptation plugin.
  • the packet manager may allocate a corresponding driver adaptation plug-in group for each controller in the ICT network, and generate information and drivers of multiple controllers. Adapting a correspondence between the plug-in groups; the distributor may determine the driver adaptation plug-in group according to the information of the target controller included in each request message, and then select a driver adaptation plug-in included in the driver adaptation plug-in group to send The corresponding request message.
  • the distributor may include a bus having a distribution characteristic, which is not limited by the present invention.
  • the group manager may allocate a corresponding driver adaptation plug-in group to each controller in the ICT network, and generate correspondence between information of multiple controllers and a driver adaptation plug-in group, where any controller At least one drive adapter plug-in included in the corresponding driver adapter group is connected to the controller.
  • the packet manager may allocate a corresponding driver adaptation plug-in group for each controller according to network deployment requirements, geographic location distribution, execution efficiency requirements, multi-user concurrent processing, and reliability requirements, thereby generating The correspondence between the information of multiple controllers and the driver adaptation plug-in group.
  • the driver adaptation plug-in in the ICT network is a bridge connecting the controller and the ICT-O system, wherein one driver adapter plug-in can correspond to at least one controller, and one controller also has at least one driver adapter plug-in. correspond.
  • the ICT network usually adopts service clustering and cloud deployment, so that the number of controllers in the network is higher, and the number of driver adapters is correspondingly higher.
  • the distributor in the ICT-O system after receiving a request message, the distributor in the ICT-O system performs load balancing on all the driver adapters in the ICT network, and selects one of the appropriate driver adapters to transmit the request. Message.
  • the distributor load-balances all the driver adaptation plug-ins, increases the amount of calculation of the distributor, and increases the filtering of the appropriate driver adaptation plug-in. Time, which reduces the user experience;
  • driver adaptation plug-ins in the ICT network cannot establish a connection with some controllers, for example, a controller has a connection limit number, that is, the maximum connectable drive of the controller is suitable.
  • the number of the plug-ins therefore, when the driver adapter plug-in in the ICT network is larger than the number of connection restrictions, a maximum number of connection-adaptive driver plug-ins in the ICT network are connected to the controller, and the rest
  • the driver adapter cannot be connected to the controller; for example, the attribution of a controller is Beijing, and the attribution of some driver adapters is Shenzhen. Therefore, the driver adapter cannot be connected to the controller. .
  • the probability that the load adaptation-compliant drive adaptation plug-in selected by the distributor for the request message is not connected to the target controller corresponding to the request message is large, that is, the probability of the request message transmission failure is large.
  • the reliability of the request message transmission is low.
  • a request message transmission method is applicable to an ICT-O system in an ICT network as shown in FIG. 1 and FIG. 2, and a distributor according to an embodiment of the present invention.
  • Step 301 After receiving the request message, the distributor acquires information about the first controller included in the request message.
  • the request message is one of a plurality of request messages decomposed by the ICT-O system for receiving a service request, where each request message decomposed by the ICT-O system includes a corresponding target control. Information.
  • the first controller is the target controller of the request message.
  • the information of the first controller is information that uniquely identifies the first controller, such as the identifier of the first controller.
  • the information of the first controller is a route identifier of the first controller, and the route identifier can uniquely identify the first controller.
  • the route identifier of the first controller is generated by the ICT-O system when the first controller registers with the ICT-O system, and optionally, the ICT-O system follows a setting rule. Converting the identifier of the first controller to generate a route identifier of the first controller.
  • Step 302 The distributor determines, in the correspondence between the information of the multiple controllers and the driver adaptation plug-in group, the first driver adaptation plug-in group corresponding to the information of the first controller, where the first The controller is coupled to the at least one drive adapter plug-in included in the first driver adapter group.
  • the correspondence between the information of the plurality of controllers and the driver adaptation plug-in group may be stored locally at the distributor or stored in other storage devices (eg, a packet manager) in the ICT-O system.
  • the packet manager in the ICT-O system can assign a corresponding driver adaptation plug-in group to each controller in the ICT network to generate multiple controllers.
  • Corresponding relationship between the information and the driver adaptation plug-in group, and at least one driver adaptation plug-in included in the driver adaptation plug-in group corresponding to any one of the controllers is connected to the controller.
  • the at least one driver adapter inserted in the first driver adapter group is connected to the first controller, and the distributor is guaranteed to pass any one of the drivers included in the first driver adapter group.
  • the adaptation plug-in can successfully transmit the request message to the first controller, which reduces the probability of request message transmission failure due to the controller not being connected to the driver adaptation plug-in, and improves the reliability of the request message transmission. .
  • each type of the driver adaptation plug-in included in the first driver adaptation plug-in group is the same type.
  • the driver adapter can be based on network type (such as SDN, NFV, etc.), device type (such as IP device, Wide Area Network device, etc.), protocol type (such as OpenFlow protocol, expressive state transfer ( Representational State Transfer (REST) protocol, Simple Object Access Protocol (SOAP), etc.) and manufacturers are divided into different types.
  • network type such as SDN, NFV, etc.
  • device type such as IP device, Wide Area Network device, etc.
  • protocol type such as OpenFlow protocol, expressive state transfer ( Representational State Transfer (REST) protocol, Simple Object Access Protocol (SOAP), etc.
  • the Uniform Resource Locator URL
  • the maintained interface is different. Therefore, at least one driver adaptation plug-in in the first driver adaptation plug-in group is The types of the drivers are all the same, and the interface of the driver adaptation plug-in of this type matches the interface of the first controller.
  • the type of each driver adapter in the first driver adapter group is the same as that of the first controller. Type match.
  • the distribution The device can ensure that the request message is successfully transmitted to the first controller by using any one of the driver adaptation plug-ins included in the first driver adaptation plug-in group, thereby reducing the adapter and driver adaptation plug-in.
  • the probability of request message transmission failure caused by interface mismatch improves the reliability of request message transmission.
  • the request message further includes a first type of the driver adaptation plug-in.
  • the first type of the driver adaptation plug-in included in the request message indicates that the distributor can successfully transmit the request message to the first controller only through the first type of driver adaptation plug-in. That is, the interface of the first type of driver adaptation plug-in matches the interface of the first controller.
  • the distributor may subsequently select at least one candidate driver adapter of the first type in the first driver adapter group, and the distributor may ensure that the at least one candidate driver is passed. Any one of the adaptation plug-ins can successfully transmit the request message to the first controller, thereby reducing The probability of failure of the request message transmission caused by the mismatch between the controller and the driver adapter plug-in interface improves the reliability of the request message transmission.
  • the number of connection limits of each controller of the multiple controllers corresponding to the first driver adapter group is the same, and The number of the driver adapters included in the first driver adapter group is less than or equal to the number of connection limits of each controller corresponding to the first driver adapter group.
  • the number of the driver adaptation plugins included in the driver adaptation plug-in group corresponding to any one of the second controllers is less than or equal to the connection of the second controller. Limiting the number, if there are multiple second controllers with the same number of connection restrictions, the plurality of second controllers may correspond to the same driver adaptation plug-in group.
  • the distributor when the first controller has the connection limit number, the distributor can ensure that the request message can be successfully successfully performed by any one of the first driver adaptation plug-in groups. Transmitting to the first controller to prevent the target driver selected by the distributor when the number of the driver adapters included in the first driver adapter group is greater than the number of connection constraints of the first controller If the request message fails to be transmitted by the first control, the request message transmission fails, which improves the reliability of the request message transmission.
  • the attribution of each controller of the plurality of controllers corresponding to the first driver adapter group and the first The attribution of each driver adaptation plug-in included in the driver adaptation plug-in group is the same.
  • the distributor can ensure that the request message can be successfully transmitted to the first controller by using any one of the first driver adaptation plug-in groups, avoiding When there is a driver adaptation plug-in in the first driver adaptation plug-in group that is different from the home location of the first controller, the target driver adaptation plug-in selected by the distributor is different from the first control attribution.
  • the request message transmission failure condition improves the reliability of the request message transmission.
  • Step 303 The distributor determines at least one candidate driver adapter in the at least one driver adapter plugin connected to the first controller included in the first driver adapter group, The operating state of at least one candidate driver adapter is normal.
  • the distributor may determine, in the first driver adaptation plug-in group, a candidate driver adapter that is in a normal running state, and then select a target driver adaptation in the candidate driver adapter. a plug-in, the distributor may ensure that the request message is successfully transmitted to the first controller by any one of the at least one candidate driver adapter, avoiding driver adaptation The probability that the request message transmission fails due to abnormal plug-in operation improves the reliability of the request message transmission.
  • the request message further includes a first type of the driver adaptation plug-in
  • the method further includes:
  • the distributor acquires the first type included in the request message
  • the distributor determines the at least one candidate drive adaptation plug-in, including:
  • the distributor determines, in the at least one driver adaptation plug-in, the at least one candidate drive adapter plug of the same type as the first type.
  • the distributor may subsequently select at least one candidate driver adapter of the first type in the first driver adapter group, and the distributor may ensure that the at least one candidate driver is passed.
  • Adaptation plugin Any one of the driver adaptation plug-ins can successfully transmit the request message to the first controller, which reduces the probability of request message transmission failure due to mismatch between the controller and the driver adapter plug-in interface, and improves the request. The reliability of message transmission.
  • Step 304 The distributor sends the request message to the first controller by using one of the at least one candidate driver adaptation plug-in.
  • the distributor includes:
  • the distributor sends the request message to the first controller via the target drive adaptation plugin.
  • the method for load balancing processing used by the distributor may include multiple types, for example, a polling method according to a setting order, a random selection method, or the like, or a method for selecting a matching feature, which is not limited by the present invention. .
  • the distributor determines load balancing of the at least one candidate driver adapter by determining load balancing of the at least one candidate driver adapter by performing load balancing processing on the at least one candidate driver adapter.
  • the distributor deployed in the ICT-O system determines the number according to the information of the first controller included in the request message after receiving a request message.
  • a first driver adapter group corresponding to information of a controller, wherein the first controller is connected to at least one driver adapter included in the first driver adapter group;
  • the at least one driver adaptation plug-in included in the first driver adaptation plug-in group filters out at least one candidate driver adapter plug-in whose operating status is normal, and finally the distributor can pass a candidate driver adapter plug-in
  • the request message is sent to the first controller.
  • the at least one driver adapter inserted in the first driver adapter group is connected to the first controller, and the distributor is guaranteed to pass any one of the drivers included in the first driver adapter group.
  • the adaptation plug-in can successfully transmit the request message to the first controller, which reduces the probability of request message transmission failure due to the controller not being connected to the driver adaptation plug-in, and improves the reliability of the request message transmission.
  • the distributor filters out at least one candidate driver adapter that is in a normal running state in the at least one driver adapter included in the first driver adapter group, further ensuring the distributor.
  • the request message can be successfully transmitted to the first controller through one of the candidate driver adaptation plug-ins, thereby avoiding a situation in which the request message transmission fails due to abnormal operation of the driver adaptation plug-in.
  • an embodiment of the present invention provides an example of request message transmission.
  • the executor and the distributor are included in the ICT-O system.
  • the process of the example includes:
  • Step 401 The executor sends a request message to the distributor, where the request message carries information of the controller, SDN_controller1.
  • the request message is one of a plurality of request messages that the ICT-O system decomposes a service request.
  • Step 402 The distributor determines, according to the SDN_controller1, a driver adaptation plug-in group corresponding to the SDN_controller1 in the correspondence between the information of the multiple controllers and the driver adaptation plug-in group.
  • the determined driver adaptation plug-in group includes at least one driver adaptation plug-in connected to the controller corresponding to the SDN_controller1, and the distributor shown in FIG. 5 determines step 501 in the flow of the candidate driver adaptation plug-in.
  • Step 403 The distributor filters out at least one candidate driver adaptation plug-in in the determined driver adaptation plug-in group, and the running state of each candidate driver adapter plug-in is normal. As shown in step 502 of FIG. 5, a plurality of driver adaptation plug-ins in the determined driver adaptation plug-in group are obtained; and as shown in step 503, the screening operation status is positive in the plurality of driver adaptation plug-ins. Often two candidate drive adapters.
  • Step 404 The distributor performs load balancing processing on the at least one candidate driver adaptation plug-in to determine a target driver adaptation plug-in.
  • Step 405 The distributor sends the request message to the target driver adaptation plugin.
  • the distributor when the distributor includes a bus and a processing module, after receiving the request message, the bus performs the steps 402 to 404 through the processing module, and adapts the target driver.
  • a plugin ie, an identification of the target driver adaptation plugin
  • the bus performs step 405 again.
  • Step 406 The target driver adaptation plugin sends the request message to a controller corresponding to the SDN_controller1.
  • Step 407 The controller corresponding to the SDN_controller1 returns a response message to the target driver adaptation plug-in.
  • the response message is an execution result of the request message.
  • Step 408 The target driver adaptation plugin returns the response message to the distributor.
  • Step 409 The distributor returns the response message to the executor.
  • the distributor deployed in the ICT-O system determines the driver adaptation plug-in group corresponding to the information of the controller according to the information of the controller included in the request message.
  • the controller is connected to at least one driver adapter plug-in included in the driver adapter group; the distributor filters the at least one driver adapter plug-in included in the driver adapter group And performing at least one candidate driver adapter plug-in that is in a normal running state, and then performing load balancing processing on the at least one candidate driver adapter plug-in, and determining a target driver adapter plug-in in the at least one candidate driver adapter plug-in Finally, the distributor can send the request message to the controller through the target driver adaptation plugin.
  • the distributor Since at least one driver adaptation plug-in included in the driver adaptation plug-in group is connected to the controller, it is ensured that the distributor can use any one of the driver adaptation plug-ins included in the driver adaptation plug-in group. Successfully transmitting the request message to the controller reduces the probability of request message transmission failure due to the controller not being connected to the driver adaptation plug-in, improving the reliability of the request message transmission, and further, the distributor is The at least one driver adaptation plug-in included in the driver adaptation plug-in group filters out at least one candidate driver adapter plug-in whose operating state is normal, further ensuring that the distributor drives the adapter plug-in through the selected target. The request message is successfully transmitted to the controller, avoiding the case where the request message transmission fails due to abnormal operation of the driver adaptation plug-in.
  • the ICT-O system may be an ICT-O system in the ICT network as shown in FIG. 1 or FIG. 2, and the group manager according to the embodiment of the present invention may It is the packet manager shown in Figure 2.
  • the embodiment of the present invention further provides a process for generating a correspondence between a controller information and a driver adaptation plug-in group, including:
  • Step 601 The packet manager obtains information of the controller.
  • the information of the controller is information that can uniquely identify the controller, such as the identifier of the controller.
  • the information of the controller is a route identifier of the controller, and the route identifier can uniquely identify the controller.
  • the routing identifier of the controller is generated by the ICT-O system when the controller registers with the ICT-O system, and optionally, the ICT-O system according to a setting rule
  • the identifier of the controller is converted to generate a route identifier of the controller.
  • Step 602 The group manager determines, in the plurality of driver adaptation plug-ins, at least one driver adaptation plug-in corresponding to the controller, wherein the controller is connected to the at least one driver adaptation plug-in.
  • the grouping manager determines, in the multiple driver adaptation plug-ins, the at least one driver adaptation plug-in corresponding to the controller, including:
  • the group manager acquires a type of each of the plurality of driver adaptation plug-ins
  • the group manager determines the at least one driver adaptation plug-in of the same type among the plurality of driver adaptation plug-ins.
  • the packet manager determines that the interface of the controller matches.
  • the interface of the adaptation plug-in is driven, and then the type of the driver adapter is determined, and it is finally determined that the interface of the driver adapter of the type matches the interface of the controller. Therefore, the packet manager can filter out the at least one driver adaptation plug-in of the same type (ie, of the type) among the plurality of driver adaptation plug-ins.
  • the group manager filters out the first driver adaptation plug-in group that matches the type of the controller.
  • the type of each drive adapter is adapted to the at least one drive adapter of the first controller.
  • the selected types of the at least one driver adapter are the same, and the interface of the driver adapter of the type matches the interface of the controller, and the distributor can ensure that the at least one driver is Any one of the adaptation plug-ins can successfully transmit the request message to the controller, which reduces the probability of request message transmission failure due to the mismatch between the controller and the driver adapter interface, and improves the request. The reliability of message transmission.
  • the number of the at least one driver adapter is less than or equal to the number of connection limits of the controller.
  • the distributor can ensure that the request message can be successfully transmitted to the controller through any one of the at least one driver adaptation plug-ins.
  • the number of the at least one driver adaptation plug-in is greater than the number of connection restrictions of the controller, the target drive adaptation plug-in selected by the distributor is not connected to the control, and the request message transmission fails. The reliability of request message transmission.
  • the attribution of the at least one driver adapter is the same as the attribution of the controller.
  • the distributor can ensure that the request message is successfully transmitted to the controller through any one of the at least one driver adaptation plug-in, avoiding adaptation due to the at least one driver.
  • the target drive adaptation plug-in selected by the distributor is different from the control attribution, and the request message transmission fails. Request the reliability of message transmission.
  • Step 603 The packet manager generates a correspondence between the information of the controller and a driver adaptation plug-in group, where the driver adaptation plug-in group includes the at least one driver adaptation plug-in.
  • the grouping manager generates a correspondence between the controller and the driver adaptation plug-in group, so that the efficiency of the at least one driver adaptation plug-in corresponding to the controller is further improved by the distributor, and at the same time, facilitating the
  • the packet manager manages and controls the correspondence between the controller and the driver adaptation plug-in group.
  • the method further includes:
  • the packet manager obtains an operating status of the at least one driver adaptation plugin.
  • the group management The operating state of the at least one driver adapter may be obtained by timing, or the at least one driver adapter may periodically report the running state of the at least one driver adapter, or the at least one driver adaptation When the plug-in determines that the running state of the plug-in is changed, the current operating state of the current state is reported, which is not limited by the present invention.
  • the packet manager may determine an operating state of each driver adaptation plug-in in the driver adaptation plug-in group corresponding to the controller. After the identifier of the at least one driver adaptation plug-in acquired by the packet manager, the distributor may filter out the operation according to the running state of the at least one driver adaptation plug-in obtained by the packet manager. At least one candidate drive adapter plugin in a normal state.
  • the group manager further performs post-maintenance on the generated correspondence between the information of the controller and the driver adaptation plug-in group, for example, when the controller logs off, the group manager deletes the deletion.
  • the group manager deletes the deletion.
  • the packet manager may also delete the driver corresponding to the controller.
  • the target driver adaptation plugin in the plugin group is a target driver adapter in the driver adaptation plug-in group.
  • the group manager may generate, by using the foregoing method, each correspondence between the information of the multiple controllers and the corresponding relationship of the driver adaptation plug-in group.
  • the packet manager may periodically update the correspondence between the information of the multiple control cores and the driver adaptation plug-in group, and may be configured when a controller or a driver adaptation plug-in registers with the ICT-O system.
  • the manager generates a corresponding relationship between the controller and the driver adaptation plug-in group for the registered controller or the driver adaptation plug-in, which is not limited by the present invention.
  • the packet manager filters the driver adaptation plug-in according to the type of the driver adaptation plug-in, and then generates a correspondence relationship between the controller and the driver adaptation plug-in group, in this way, a new type of controller is developed.
  • the distributor does not need to modify or adjust the original driver adaptation plug-in in the ICT network, so the service is not interrupted, and the controller and the driver adaptation plug-in group generated by the packet manager for the controller are
  • the distributor can select a target driver adaptation plug-in to send a request message to the controller in the driver adaptation plug-in group corresponding to the controller, which shortens the service processing delay and improves the user experience.
  • the method for generating the correspondence between the information of the controller and the driver adaptation plug-in group provided by the embodiment of the present invention, after the packet manager deployed in the ICT-O system acquires information of a controller in the ICT network, Determining, by the plurality of driver adaptation plug-ins in the ICT network, at least one driver adaptation plug-in connected to the controller, and establishing a correspondence between the information of the controller and a driver adaptation plug-in group, wherein the driver The adaptation plugin group includes the at least one drive adaptation plugin.
  • the distributor is guaranteed to pass any one of the driver adapters included in the driver adapter group. Both the request message can be successfully transmitted to the controller, which reduces the probability of request message transmission failure due to the controller not being connected to the driver adapter, and improves the reliability of the request message transmission.
  • the present invention also provides a distributor which may be a module having a distribution function in an ICT-O system in the ICT network as shown in FIGS. 1 and 2.
  • the distributor 700 includes: a receiving unit 701, a processing unit 702, and a sending unit 703, where
  • the receiving unit 701 is configured to receive a request message.
  • the processing unit 702 is configured to acquire information about the first controller included in the request message.
  • the first driver adapter group corresponding to the information of the first controller, wherein the first controller and the first At least one driver adaptation plug-in included in the driver adaptation plug-in group is connected;
  • the sending unit 703 is configured to send the request message to the first controller by using one of the at least one candidate driver adaptation plug-in.
  • the information of the first controller is a route identifier of the first controller, and the route identifier can uniquely identify the first controller.
  • each type of the driver adaptation plug-in included in the first driver adaptation plug-in group is the same type.
  • the request message further includes a first type of a driver adaptation plug-in
  • the processing unit 702 is further configured to:
  • processing unit 702 determines the at least one candidate driver adapter in the at least one driver adapter plugin connected to the first controller included in the first driver adapter group, specifically Used for:
  • the at least one driver adapter Determining, in the at least one driver adapter, that the type is the same as the first type, and the running state is normal, the at least one candidate driver adapter.
  • the number of connection limits of each controller of the multiple controllers corresponding to the first driver adapter group is the same, and The number of the driver adapters included in the first driver adapter group is less than or equal to the number of connection limits of each controller corresponding to the first driver adapter group.
  • the attribution of each controller of the plurality of controllers corresponding to the first driver adapter group and the first The attribution of each driver adaptation plug-in included in the driver adaptation plug-in group is the same.
  • the processing unit 702 is further configured to:
  • the sending unit passes Passing one of the at least one candidate driver adapters to load balance the plurality of candidate driver adapters before sending the request message to the first controller Processing, determining a target driver adaptation plugin, the target driver adaptation plugin being one of the plurality of candidate drive adaptation plugins;
  • the sending unit 703 is specifically configured to:
  • the request message is sent to the first controller by the target driver adaptation plugin.
  • the distributor determines the first driver adaptation plug-in group corresponding to the information of the first controller according to the information of the first controller included in the request message, where
  • the first controller is connected to at least one driver adapter plug-in included in the first driver adapter group; the distributor is adapted to the at least one driver included in the first driver adapter group
  • the plug-in filters out at least one candidate driver adapter that is in a normal running state, and finally the distributor can send the request message to the first controller through a candidate driver adapter.
  • the at least one driver adapter inserted in the first driver adapter group is connected to the first controller, and the distributor is guaranteed to pass any one of the drivers included in the first driver adapter group.
  • the adaptation plug-in can successfully transmit the request message to the first controller, which reduces the probability of request message transmission failure due to the controller not being connected to the driver adaptation plug-in, and improves the reliability of the request message transmission.
  • the distributor filters out at least one candidate driver adapter that is in a normal running state in the at least one driver adapter included in the first driver adapter group, further ensuring the distributor.
  • the request message can be successfully transmitted to the first controller through one of the candidate driver adaptation plug-ins, thereby avoiding a situation in which the request message transmission fails due to abnormal operation of the driver adaptation plug-in.
  • the present invention also provides a packet manager which can be applied to an ICT-O system in an ICT network as shown in FIGS. 1 and 2, the packet manager having a generation controller The function of the information and the correspondence of the driver adaptation plugin group.
  • the packet manager 800 includes: a processing unit 801 and a generating unit 802, where
  • the processing unit 801 is configured to acquire information about the controller
  • the generating unit 802 is configured to generate a correspondence between the information of the controller and the driver adaptation plug-in group, wherein the driver adaptation plug-in group includes the at least one driver adaptation plug-in.
  • the information of the controller is a route identifier of the controller, and the route identifier can uniquely identify the controller.
  • processing unit 801 is specifically configured to:
  • the at least one drive adapter plug of the same type is determined in the plurality of drive adapters.
  • the number of the at least one driver adapter is less than or equal to the number of connection limits of the controller.
  • the attribution of the at least one driver adapter is the same as the attribution of the controller.
  • processing unit 801 is further configured to:
  • the running state of the at least one driver adapter is obtained.
  • the packet manager provided by the embodiment of the present invention, after the information of a controller in the ICT network is acquired, the packet manager filters out the controller in the multiple driver adaptation plugins in the ICT network. Corresponding at least one driver adaptation plug-in, and establishing a correspondence between the controller information and the driver adaptation plug-in group, wherein the driver adaptation plug-in group includes the at least one driver adaptation plug-in. In this way, since at least one of the driver adapters included in the driver adapter group is connected to the controller, the distributor is guaranteed to pass any one of the driver adapters included in the driver adapter group. Both the request message can be successfully transmitted to the controller, which reduces the probability of request message transmission failure due to the controller not being connected to the driver adapter, and improves the reliability of the request message transmission.
  • the division of the unit in the embodiment of the present invention is schematic, and is only a logical function division, and the actual implementation may have another division manner.
  • the functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
  • the above integrated unit can be implemented in the form of hardware or in the form of a software functional unit.
  • the integrated unit if implemented in the form of a software functional unit and sold or used as a standalone product, may be stored in a computer readable storage medium.
  • the technical solution of the present application may contribute to the prior art or all or part of the technical solution may be embodied in the form of a software product.
  • the computer software product is stored in a storage medium and includes instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) or a processor to perform the embodiments of the present application. All or part of the steps of the method.
  • the foregoing storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk, and the like. .
  • the embodiment of the present invention further provides a distributor, which may be a device having a distribution function in an ICT-O system in the ICT network as shown in FIGS. 1 and 2.
  • the distributor 900 includes a transceiver 901, a processor 902, a bus 903, and a memory 904, where
  • the transceiver 901, the processor 902 and the memory 904 are mutually connected by the bus 903; the bus 903 may be a peripheral component interconnect standard (PCI) bus or an extended industry standard structure (extended Industry standard architecture, referred to as EISA) bus.
  • PCI peripheral component interconnect standard
  • EISA extended Industry standard architecture
  • the bus can be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, only one thick line is shown in Figure 9, but it does not mean that there is only one bus or one type of bus.
  • the transceiver 901 is configured to perform communication interaction with other devices connected to the distributor 900.
  • the processor 902 is configured to implement the request message transmission method as shown in FIG. 3, including:
  • the first driver adapter group corresponding to the information of the first controller, wherein the first controller and the first At least one driver adaptation plug-in included in the driver adaptation plug-in group is connected;
  • the request message is sent to the first controller by one of the at least one candidate drive adaptation plug-in.
  • the information of the first controller is a route identifier of the first controller, and the route identifier can uniquely identify the first controller.
  • each type of the driver adaptation plug-in included in the first driver adaptation plug-in group is the same type.
  • the request message further includes a first type of a driver adaptation plug-in
  • the processor 902 is further configured to:
  • processor 902 determines the at least one candidate driver adapter in the at least one driver adapter that is connected to the first controller included in the first driver adapter group, specifically Used for:
  • the number of connection limits of each controller of the multiple controllers corresponding to the first driver adapter group is the same, and The number of the driver adapters included in the first driver adapter group is less than or equal to the number of connection limits of each controller corresponding to the first driver adapter group.
  • the attribution of each controller of the plurality of controllers corresponding to the first driver adapter group and the first The attribution of each driver adaptation plug-in included in the driver adaptation plug-in group is the same.
  • the processor 902 is configured by using one of the at least one candidate driver adapter plug-in, When the request message is sent to the first controller, it is specifically used to:
  • the request message is sent to the first controller by the target driver adaptation plugin.
  • the memory 904 is used to store programs and the like.
  • the program can include program code, the program code including computer operating instructions.
  • the memory 904 may include a volatile memory (English: volatile memory), such as a random access memory (English: random-access memory, abbreviation: RAM); the memory may also be a non-volatile memory (English: non-volatile memory).
  • read-only memory (English: read-only memory, abbreviation: ROM), flash memory (English: flash memory), hard disk (English: hard disk drive, abbreviation: HDD) or solid state drive (English: solid-state drive, Abbreviations: SSD), or memory
  • ROM read-only memory
  • flash memory (English: flash memory)
  • hard disk (English: hard disk drive, abbreviation: HDD)
  • solid state drive (English: solid-state drive, Abbreviations: SSD), or memory
  • the memory can be a combination of the above memories.
  • the processor 902 executes the application stored in the memory 904 to implement the above functions, thereby implementing the request message transmission method as shown in FIG.
  • the distributor determines the first driver adaptation plug-in group corresponding to the information of the first controller according to the information of the first controller included in the request message, where
  • the first controller is connected to at least one driver adapter plug-in included in the first driver adapter group; the distributor is adapted to the at least one driver included in the first driver adapter group
  • the plug-in filters out at least one candidate driver adapter that is in a normal running state, and finally the distributor can send the request message to the first controller through a candidate driver adapter.
  • the at least one driver adapter inserted in the first driver adapter group is connected to the first controller, and the distributor is guaranteed to pass any one of the drivers included in the first driver adapter group.
  • the adaptation plug-in can successfully transmit the request message to the first controller, which reduces the probability of request message transmission failure due to the controller not being connected to the driver adaptation plug-in, and improves the reliability of the request message transmission.
  • the distributor filters out at least one candidate driver adapter that is in a normal running state in the at least one driver adapter included in the first driver adapter group, further ensuring the distributor.
  • One of the candidate driver adaptation plug-ins can successfully transmit the request message to the first controller, thereby avoiding a situation in which the request message transmission fails due to abnormal operation of the driver adaptation plug-in.
  • an embodiment of the present invention further provides a packet manager, which may be in an ICT-O system in an ICT network as shown in FIG. 1 and FIG. 2, where the packet manager has a generation control.
  • the packet manager 1000 includes a transceiver 1001, a processor 1002, a bus 1003, and a memory 1004, where
  • the transceiver 1001, the processor 1002 and the memory 1004 are connected to each other through the bus 1003;
  • the bus 1003 may be a peripheral component interconnect standard (PCI) bus or an extended industry standard structure (extended Industry standard architecture, referred to as EISA) bus.
  • PCI peripheral component interconnect standard
  • EISA extended Industry standard architecture
  • the bus can be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, only one thick line is shown in FIG. 10, but it does not mean that there is only one bus or one type of bus.
  • the transceiver 1001 is configured to perform communication interaction with other devices connected to the packet manager.
  • the processor 1002 is configured to implement a corresponding relationship between the information of the controller and the driver adaptation plug-in group, as shown in FIG.
  • the driver adaptation plug-in group includes the at least one driver adaptation plug-in.
  • the information of the controller is a route identifier of the controller, and the route identifier can uniquely identify the controller.
  • the processor 1002 determines at least one driver adaptation plug-in corresponding to the controller, the processor 1002 is specifically configured to:
  • the at least one drive adapter plug of the same type is determined in the plurality of drive adapters.
  • the number of the at least one driver adapter is less than or equal to the number of connection limits of the controller.
  • the attribution of the at least one driver adapter is the same as the attribution of the controller.
  • processor 1002 is further configured to:
  • an operation state of the at least one driver adaptation plug-in is obtained.
  • the memory 1004 is used to store programs and the like.
  • the program can include program code, the program code including computer operating instructions.
  • the memory 1004 may include a volatile memory (English: volatile memory), such as a random access memory (English: random-access memory, abbreviation: RAM); the memory may also be a non-volatile memory (English: non-volatile memory).
  • read-only memory (English: read-only memory, abbreviation: ROM), flash memory (English: flash memory), hard disk (English: hard disk drive, abbreviation: HDD) or solid state drive (English: solid-state drive, Abbreviations: SSD), or memory
  • ROM read-only memory
  • flash memory (English: flash memory)
  • hard disk (English: hard disk drive, abbreviation: HDD)
  • solid state drive (English: solid-state drive, Abbreviations: SSD), or memory
  • the memory can be a combination of the above memories.
  • the processor 1002 executes the application stored in the memory 1004 to implement the above functions, thereby implementing a correspondence generation method of the controller information and the driver adaptation plug-in group as shown in FIG. 6.
  • the packet manager provided by the embodiment of the present invention, after the information of a controller in the ICT network is acquired, the packet manager filters out the controller in the multiple driver adaptation plugins in the ICT network. Corresponding at least one driver adaptation plug-in, and establishing a correspondence between the controller information and the driver adaptation plug-in group, wherein the driver adaptation plug-in group includes the at least one driver adaptation plug-in. In this way, since at least one of the driver adapters included in the driver adapter group is connected to the controller, the distributor is guaranteed to pass any one of the driver adapters included in the driver adapter group. Both the request message can be successfully transmitted to the controller, which reduces the probability of request message transmission failure due to the controller not being connected to the driver adapter, and improves the reliability of the request message transmission.
  • An embodiment of the present invention provides a request message transmission method and apparatus, in which a dispatcher deployed in an ICT-O system receives a request message according to a first controller included in the request message. And determining, by the first controller, the first driver adapter group corresponding to the information of the first controller, wherein the first controller is connected to the at least one driver adapter included in the first driver adapter group
  • the distributor is in the first drive adapter
  • the at least one driver adaptation plug-in included in the device group filters out at least one candidate driver adapter plug-in whose operating status is normal, and finally the distributor can send the request message to the candidate driver adapter through a candidate driver adapter.
  • the first controller The first controller.
  • the at least one driver adapter inserted in the first driver adapter group is connected to the first controller, and the distributor is guaranteed to pass any one of the drivers included in the first driver adapter group.
  • the adaptation plug-in can successfully transmit the request message to the first controller, which reduces the probability of request message transmission failure due to the controller not being connected to the driver adaptation plug-in, and improves the reliability of the request message transmission.
  • the distributor filters out at least one candidate driver adapter that is in a normal running state in the at least one driver adapter included in the first driver adapter group, further ensuring the distributor.
  • the request message can be successfully transmitted to the first controller by the selected target driver adaptation plug-in, which avoids the situation that the request message transmission fails due to the abnormal operation of the driver adaptation plug-in.
  • embodiments of the present invention can be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment, or a combination of software and hardware. Moreover, the invention can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) including computer usable program code.
  • computer-usable storage media including but not limited to disk storage, CD-ROM, optical storage, etc.
  • the computer program instructions can also be stored in a computer readable memory that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture comprising the instruction device.
  • the apparatus implements the functions specified in one or more blocks of a flow or a flow and/or block diagram of the flowchart.
  • These computer program instructions can also be loaded onto a computer or other programmable data processing device such that a series of operational steps are performed on a computer or other programmable device to produce computer-implemented processing for execution on a computer or other programmable device.
  • the instructions provide steps for implementing the functions specified in one or more of the flow or in a block or blocks of a flow diagram.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Software Systems (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Environmental & Geological Engineering (AREA)
  • Quality & Reliability (AREA)
  • Computer Security & Cryptography (AREA)
  • Small-Scale Networks (AREA)
  • Computer And Data Communications (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

一种请求消息传输方法及装置，用以解决现有技术中的ICT网络在传输请求消息时，会增加请求消息传输失败的概率，降低了请求消息传输的可靠性的问题。该方法为：分发器根据接收的请求消息中包含的第一控制器的信息，确定对应的第一驱动适配插件组，所述第一控制器与所述第一驱动适配插件组中包含的至少一个驱动适配插件相连；所述分发器在所述至少一个驱动适配插件中筛选出运行状态为正常的至少一个待选驱动适配插件，最终通过一个待选驱动适配插件将所述请求消息发送至所述第一控制器。这样，保证了所述分发器通过所述目标驱动适配插件，可以成功将所述请求消息传输至所述第一控制器。

Description

一种请求消息传输方法及装置
本申请要求在2016年04月29日提交中国专利局、申请号为201610289644.6、发明名称为《一种请求消息传输方法及装置》的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本发明涉及通信技术领域，尤其涉及一种请求消息传输方法及装置。
背景技术
信息和通信技术(Information and Communications Technology，ICT)技术是应信息时代对信息技术和通信技术的融合的需求产生的。
在ICT网络中，主要包括ICT编排(ICT-Orchestration，ICT-O)***，以及多个控制器，其中所述ICT-O***又称为业务编排***，所述ICT-O***用于接收来自用户的业务请求，并将该业务请求进行分解和重新设计等处理，转换为该网络中的控制器可以理解并执行的多个请求消息，并将多个请求消息进行调度处理，将每个请求消息转发至相应的控制器，所述ICT-O***中可以根据执行功能的不同分为多个逻辑模块，例如用于将业务请求进行分解和重新设计的业务分解设计模块，用于对多个请求消息进行调度处理的执行器，用于对每个请求消息转发的分发器等；所述控制器具有逻辑控制功能，部署于所述ICT-O***与网络设备和/或基础设施之间，根据接收到的所述ICT-O***中请求消息，将所述请求消息对应的网络指令发送至与所述请求消息相应的网络设备和/或基础设施。在该网络中所述ICT-O***和每个控制器之间通过驱动适配插件进行交互。
为了解决管理容量和可靠性的问题，在该网络中，采用服务集群化和云化部署方式，这样，该网络中的控制器的数量等级较高，驱动适配插件的数量等级也相应较高。
在该网络中的ICT-O***在接收到用户提出的针对一种类型的业务提出的业务请求后，将该业务请求进行分解，生成多个请求消息，每个请求消息中包含其对应的目标控制器标识，并通过所述执行器向所述分发器发送所述多个请求消息；所述分发器在接收到一个请求消息后，对多个驱动适配插件进行负载均衡，选择一个适当的驱动适配插件，并通过选择的该驱动适配插件，将所述请求消息发送给该请求消息包含的目标控制器标识对应的目标控制器，其中，所述分发器选择的该驱动适配插件为所述多个驱动适配插件中的任意一个。
然而，在实际场景中，某些驱动适配插件会无法与一些控制器连接的，这样，在分发器接收到的请求消息的目标控制器与分发器选择的驱动适配插件没有连接的情况下，会导致请求消息传输失败。因此，通过上述方法传输请求消息，会增加请求消息传输失败的概率，降低了请求消息传输的可靠性。
发明内容
本发明提供一种请求消息传输方法及装置，用以解决现有技术中的ICT网络在传输请求消息时，会增加请求消息传输失败的概率，降低了请求消息传输的可靠性的问题。
本发明提供的具体技术方案如下：
一方面，本发明实施例提供了一种请求消息传输方法，该方法可以适用于ICT网络中的ICT-O***，该方法中的分发器可以为所述ICT-O***中的具有分发功能的模块，该方法包括：
分发器接收到所述ICT-O***对一个业务请求分解后的请求消息后，首先获取所述请求消息中包含的第一控制器的信息，例如所述第一控制器的路由标识等唯一标识所述第一控制器的信息，然后在存储在本地或者所述ICT-O***中其他存储设备中的多个控制器的信息与驱动适配插件组的对应关系中，确定所述第一控制器的信息对应的第一驱动适配插件组，其中，所述第一控制器与所述第一驱动适配插件组中包含的至少一个驱动适配插件相连；所述分发器获取所述第一驱动适配插件组中包含的与所述第一控制器相连的所述至少一个驱动适配插件的运行状态，并在其中确定运行状态为正常的至少一个待选驱动适配插件；最终，所述分发器通过所述至少一个待选驱动适配插件中的一个待选驱动适配插件，将所述请求消息发送至所述第一控制器。
通过上述方法，由于所述第一驱动适配插件组中包含的至少一个驱动适配插件均与所述第一控制器相连，保证所述分发器通过所述第一驱动适配插件组中包含的任意一个驱动适配插件，都可以成功将所述请求消息传输至所述第一控制器，降低了由于控制器与驱动适配插件没有连接导致的请求消息传输失败的概率，提高了请求消息传输的可靠性，另外，所述分发器在所述第一驱动适配插件组中包含的至少一个驱动适配插件中筛选出运行状态为正常的至少一个待选驱动适配插件，进一步保证了所述分发器通过其中一个待选驱动适配插件，可以成功将所述请求消息传输至所述第一控制器，避免了由于驱动适配插件运行异常导致请求消息传输失败的情况。
在一个可能的设计中，所述第一控制器的信息为所述第一控制器的路由标识，所述路由标识能够唯一标识所述第一控制器，所述第一控制器的信息还可以为所述第一控制器的标识等信息。
在一个可能的设计中，所述第一驱动适配插件组中包含的每个驱动适配插件的类型相同。由于不同的类型的驱动适配插件，维护的接口不同，因此，所述第一驱动适配插件组中包含的每个驱动适配插件的接口与所述第一控制器的接口相匹配。
通过上述方式，所述第一驱动适配插件组中至少一个驱动适配插件的类型均相同，且该类型的驱动适配插件的接口与所述第一控制器的接口相匹配，所述分发器可以保证通过所述第一驱动适配插件组中包含的任意一个驱动适配插件，都可以成功将所述请求消息传输至所述第一控制器，降低了由于控制器与驱动适配插件接口不匹配导致的请求消息传输失败的概率，提高了请求消息传输的可靠性。
在一个可能的设计中，在控制器也划分为不同的类型时，上述设计中的所述第一驱动适配插件组中包含的每个驱动适配插件的类型与所述第一控制器的类型匹配。
在一个可能的设计中，在所述第一驱动适配插件组中包含至少一个驱动适配插件的类型不同的情况下，所述请求消息中还包含驱动适配插件的第一类型；所述分发器需要首先获取所述请求消息中包含的所述第一类型；在所述至少一个驱动适配插件中确定类型与所述第一类型相同，且运行状态为正常的所述至少一个待选驱动适配插件，从而得到所述至少一个待选驱动适配插件。其中所述请求消息中包含的驱动适配插件的第一类型，表示只有通过该第一类型的驱动适配插件，所述分发器才可以将所述请求消息成功传输给所述第一控制器，换句换说，所述第一类型的驱动适配插件的接口与所述第一控制器的接口相匹 配。
通过上述方法，所述分发器后续可以在所述第一驱动适配插件组中筛选出第一类型的至少一个待选驱动适配插件，所述分发器可以保证通过所述至少一个待选驱动适配插件中的任意一个驱动适配插件，都可以成功将所述请求消息传输至所述第一控制器，降低了由于控制器与驱动适配插件接口不匹配导致的请求消息传输失败的概率，提高了请求消息传输的可靠性。
在一个可能的设计中，在所述多个控制器与驱动适配插件组的对应关系中，所述第一驱动适配插件组对应的多个控制器中每个控制器的连接限制数量相同，且所述第一驱动适配插件组中包含的驱动适配插件的数量小于或等于所述第一驱动适配插件组对应的每个控制器的连接限制数量。
通过上述方法，当所述第一控制器具有连接限制数量时，所述分发器可以保证通过所述第一驱动适配插件组中的任意一个驱动适配插件，都可以成功将所述请求消息传输至所述第一控制器，避免所述第一驱动适配插件组中包含的驱动适配插件的数量大于所述第一控制器的连接限制数量时，所述分发器选择的目标驱动适配插件未与所述第一控制相连导致的请求消息传输失败的情况，提高了请求消息传输的可靠性。
在一个可能的设计中，在所述多个控制器与驱动适配插件组的对应关系中，所述第一驱动适配插件组对应的多个控制器中每个控制器的归属地与所述第一驱动适配插件组中包含的每个驱动适配插件的归属地相同。
通过上述方法，所述分发器可以保证通过所述第一驱动适配插件组中的任意一个驱动适配插件，都可以成功将所述请求消息传输至所述第一控制器，避免由于所述第一驱动适配插件组中存在归属地与所述第一控制器的归属地不同的驱动适配插件时，所述分发器选择的目标驱动适配插件与所述第一控制归属地不同导致的请求消息传输失败的情况，提高了请求消息传输的可靠性。
在一个可能的设计中，当所述至少一个待选驱动适配插件的数目为多个时，所述分发器在通过所述至少一个待选驱动适配插件中的一个待选驱动适配插件，将所述请求消息发送至所述第一控制器时，可以通过对所述多个待选驱动适配插件进行负载均衡处理，从而在所述多个待选驱动适配插件中确定一个目标驱动适配插件，然而通过确定的所述目标驱动适配插件将所述请求消息发送至所述第一控制器。
通过上述方法，所述分发器通过对所述至少一个待选驱动适配插件进行负载均衡处理，确定其中一个目标驱动适配插件，可以保证所述至少一个待选驱动适配插件的负载均衡。
在一个可能的设计中，所述分发器使用的负载均衡处理的方法，可以包括多种，例如按照设定顺序轮询方法，或者随机选择方法等，或者选择符合设定特征的方法等。
通过上述方法，所述分发器可以对所述至少一个待选驱动适配插件进行负载均衡处理，确定其中一个目标驱动适配插件。
另一方面，本发明实施例还提供了一种控制器的信息与驱动适配插件组的对应关系生成方法，该方法可以适用于ICT网络中的ICT-O***，本方法中的分组管理器中分组管理器部署于所述ICT-O***中，该方法包括：
分组管理器获取控制器的信息后，首先在ICT网络中的多个驱动适配插件中，确定出与所述控制器相连的至少一个驱动适配插件；最后生成所述控制器的信息与驱动适配插件 组的对应关系，在所述驱动适配插件组包含所述至少一个驱动适配插件。
通过上述方法，由于所述驱动适配插件组中包含的至少一个驱动适配插件均与所述控制器相连，保证所述分发器通过所述驱动适配插件组中包含的任意一个驱动适配插件，都可以成功将请求消息传输至所述控制器，降低了由于控制器与驱动适配插件没有连接导致的请求消息传输失败的概率，提高了请求消息传输的可靠性。
在一个可能的设计中，所述控制器的信息为所述控制器的路由标识，所述路由标识能够唯一标识所述所述控制器，所述第一控制器的信息还可以为所述第一控制器的标识等信息。
在一个可能的设计中，所述分组管理器可以通过驱动适配插件的类型，在多个驱动适配插件中确定出所述控制器对应的至少一个驱动适配插件，即获取所述多个驱动适配插件中每个驱动适配插件组的类型，然后在所述多个驱动适配插件中确定出类型相同的所述至少一个驱动适配插件。
通过上述方式，筛选出的至少一个驱动适配插件的类型均相同，且该类型的驱动适配插件的接口与所述控制器的接口相匹配，后续所述分发器可以保证通过上述至少一个驱动适配插件中的任意一个驱动适配插件，都可以成功将请求消息传输至所述控制器，降低了由于控制器与驱动适配插件接口不匹配导致的请求消息传输失败的概率，提高了请求消息传输的可靠性。
在一个可能的设计中，所述至少一个驱动适配插件的数量小于或等于所述控制器的连接限制数量。通过这种方法，当所述控制器具有连接限制数量时，所述分发器可以保证通过上述至少一个驱动适配插件中的任意一个驱动适配插件，都可以成功将请求消息传输至所述控制器，避免所述至少一个驱动适配插件的数量大于所述控制器的连接限制数量时，所述分发器选择的目标驱动适配插件未与所述控制相连导致的请求消息传输失败的情况，提高了请求消息传输的可靠性。
在一个可能的设计中，所述至少一个驱动适配插件的归属地与所述控制器的归属地相同。通过这种方法，所述分发器可以保证通过所述至少一个驱动适配插件中的任意一个驱动适配插件，都可以成功将请求消息传输至所述控制器，避免由于所述至少一个驱动适配插件中存在归属地与所述控制器的归属地不同的驱动适配插件时，所述分发器选择的目标驱动适配插件与所述控制归属地不同导致的请求消息传输失败的情况，提高了请求消息传输的可靠性。
在一个可能的设计中，在所述分组管理器生成所述控制器的信息与驱动适配插件组的对应关系后，所述分组管理器获取所述至少一个驱动适配插件的运行状态，例如，所述分组管理器可以通过定时获取所述至少一个驱动适配插件的运行状态，或者所述至少一个驱动适配插件可以定时上报所述至少一个驱动适配插件的运行状态，或者，所述至少一个驱动适配插件确定自身运行状态发生变化时，上报当前自身的运行状态，这样，所述分组管理器可以对所述驱动适配插件组中的所述至少一个驱动适配插件的运行状态进行更新。
通过上述方法，所述分组管理器可以确定所述控制器对应的驱动适配插件组中每个驱动适配插件的运行状态。在后续所述分发器在确定待选驱动适配插件时，可以根据所述分组管理器获取的所述至少一个驱动适配插件的运行状态，在所述至少一个驱动适配插件中筛选出运行状态为正常的至少一个待选驱动适配插件。
在一个可能的设计中，所述分组管理器对生成的所述控制器的信息与驱动适配插件组 的对应关系进行后期维护，例如，当所述控制器注销时，所述分组管理器删除删除所述控制器的信息与驱动适配插件组的对应关系；驱动适配插件组中的驱动适配插件注销时，删除所述控制器对应的驱动适配插件组中的注销的驱动适配插件；当所述分发器根据所述驱动适配插件组中的一个目标驱动适配插件发送请求消息给所述控制器发送失败时，所述分组管理器也可以删除所述控制器对应的驱动适配插件组中的所述目标驱动适配插件。
通过上述方法，所述分组管理器可以保证所述所述控制器的信息与驱动适配插件组的对应关系中的所述驱动适配插件组中的每个驱动适配插件组在任何时刻均与所述控制器相连，保证在后续所述分发器可以通过所述驱动适配插件组中的任意一个驱动适配插件，都可以成功将请求消息传输至所述控制器。
又一方面，本发明实施例还提供了一种分发器，该分发器具有实现上述方法实例中分发器行为的功能。所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的模块。
在一种可能的设计中，所述分发器的结构中包括接收单元、处理单元和发送单元，这些单元可以执行上述方法示例中的相应功能，具体参见方法示例中的详细描述，此处不做赘述。
在一种可能的设计中，所述分发器的结构中包括收发器、处理器、总线以及存储器，所述收发器用于与所述分发器相连的设备或模块进行通信交互，所述处理器被配置为支持所述分发器执行上述方法中相应的功能。所述存储器与所述处理器耦合，其保存所述分发器必要的程序指令和数据。
又一方面，本发明实施例还提供了一种分组管理器，该分组管理器具有实现上述方法实例中分组管理器行为的功能。所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的模块。
在一种可能的设计中，所述分组管理器的结构中包括处理单元和生成单元，这些单元可以执行上述方法示例中的相应功能，具体参见方法示例中的详细描述，此处不做赘述。
在一种可能的设计中，所述分组管理器的结构中包括收发器、处理器、总线以及存储器，所述收发器用于与所述分组管理器相连的其他设备进行通信交互，所述处理器被配置为支持所述分组管理器执行上述方法中相应的功能。所述存储器与所述处理器耦合，其保存所述分组管理器必要的程序指令和数据。
又一方面，本发明实施例提供了一种ICT-O***，该***包括分发器和分组管理器。该分发器具有实现上述方法实例中分发器行为的功能，该分组管理器具有实现上述方法实例中分组管理器行为的功能。
又一方面，本发明实施例提供了一种或多种计算机程序产品，该计算机程序产品中包含软件程序，该软件程序在被一个或多个处理器执行时实现前述任意一个或多个方法。
采用本发明提供的请求消息传输方法，部署于ICT-O***中的分发器在接收到一个请求消息后，根据所述请求消息中包含的第一控制器的信息，确定所述第一控制器的信息对应的第一驱动适配插件组，其中，所述第一控制器与所述第一驱动适配插件组中包含的至少一个驱动适配插件相连；所述分发器在所述第一驱动适配插件组包含的所述至少一个驱动适配插件中筛选出运行状态为正常的至少一个待选驱动适配插件，最终所述分发器可以通过一个待选驱动适配插件将所述请求消息发送至所述第一控制器。由于所述第一驱动适配插件组中包含的至少一个驱动适配插件均与所述第一控制器相连，保证所述分发器通过 所述第一驱动适配插件组中包含的任意一个驱动适配插件，都可以成功将所述请求消息传输至所述第一控制器，降低了由于控制器与驱动适配插件没有连接导致的请求消息传输失败的概率，提高了请求消息传输的可靠性，另外，所述分发器在所述第一驱动适配插件组中包含的至少一个驱动适配插件中筛选出运行状态为正常的至少一个待选驱动适配插件，进一步保证了所述分发器通过其中一个待选驱动适配插件，可以成功将所述请求消息传输至所述第一控制器，避免了由于驱动适配插件运行异常导致请求消息传输失败的情况。
附图说明
图1为本发明实施例提供的一种ICT网络的架构示意图；
图2为本发明实施例提供的另一种ICT网络的架构示意图；
图3为本发明实施例提供的一种请求消息传输方法流程图；
图4为本发明实施例提供的一种请求消息传输示例流程示意图；
图5为本发明实施例提供的一种分发器确定待选驱动适配插件的流程示意图；
图6为本发明实施例提供的一种控制器的信息与驱动适配插件组的对应关系生成方法流程图；
图7为本发明实施例提供的一种分发器的结构示意图；
图8为本发明实施例提供的一种分组管理器的结构示意图；
图9为本发明实施例提供的一种分发器的结构图；
图10为本发明实施例提供的一种分组管理器的结构图。
具体实施方式
为了使本发明的目的、技术方案和优点更加清楚，下面将结合附图对本发明作进一步地详细描述，显然，所描述的实施例仅仅是本发明一部分实施例，而不是全部的实施例。基于本发明中的实施例，本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其它实施例，都属于本发明保护的范围。
本发明实施例提供一种请求消息传输方法及装置，用以解决现有技术中的ICT网络在传输请求消息时，会增加请求消息传输失败的概率，降低了请求消息传输的可靠性的问题。其中，本发明所述方法和装置基于同一发明构思，由于方法及装置解决问题的原理相似，因此装置与方法的实施可以相互参见，重复之处不再赘述。
本发明实施例中，部署于ICT-O***中的分发器在接收到一个请求消息后，根据所述请求消息中包含的第一控制器的信息，确定所述第一控制器的信息对应的第一驱动适配插件组，其中，所述第一控制器与所述第一驱动适配插件组中包含的至少一个驱动适配插件相连；所述分发器在所述第一驱动适配插件组包含的所述至少一个驱动适配插件中筛选出运行状态为正常的至少一个待选驱动适配插件，最终所述分发器可以通过一个待选驱动适配插件将所述请求消息发送至所述第一控制器。由于所述第一驱动适配插件组中包含的至少一个驱动适配插件均与所述第一控制器相连，保证所述分发器通过所述第一驱动适配插件组中包含的任意一个驱动适配插件，都可以成功将所述请求消息传输至所述第一控制器，降低了由于控制器与驱动适配插件没有连接导致的请求消息传输失败的概率，提高了请求消息传输的可靠性，另外，所述分发器在所述第一驱动适配插件组中包含的至少一个驱动适配插件中筛选出运行状态为正常的至少一个待选驱动适配插件，进一步保证了所述 分发器通过其中一个待选驱动适配插件，可以成功将所述请求消息传输至所述第一控制器，避免了由于驱动适配插件运行异常导致请求消息传输失败的情况。
本发明实施例提供的请求消息传输方法，适用于ICT网络中，如图1所示，在该网络中根据逻辑功能进行划分，该网络可以分为ICT-O***、管理与控制层、网络设备层，其中，
用户可以访问所述ICT-O***，所述用户可以为运营商用户(如业务支撑***(Business Support System，BSS)、运营支撑***(Operation Support System，OSS)、管理员等)，企业用户，个人用户以及开发者等。所述用户可以通过网页(WEB)控制台户其他***发起业务请求，例如创建一个从深圳或北京的虚拟专用网络(Virtual Private Network，VPN)，或者在云上创建一个云主机等。
所述ICT-O***接收来自用户的业务请求，并将该业务请求进行分解和重新设计等处理，转换为该网络中的管理与控制层中的控制器可以理解并执行的多个请求消息，并将所述多个请求消息进行调度处理，将每个请求消息转发至相应的控制器。其中，在所述ICT-O***通过驱动适配插件与所述管理与控制层中的控制器进行交互。
所述管理与控制层中包括多个具有逻辑控制以及管理功能的控制器(Controller)，例如网元管理***(Element Management System，EMS)/OSS、访问控制器(Access Controller)、虚拟化网络功能管理器(Virtualised Network Function Manager，VNFM)、互联网协议(Internet Protocol，IP)城域(Metro)控制器、智能(Intellectual Property，IP)核(CORE)控制器等。所述管理与控制层中控制器在接收到所述ICT-O***中的请求消息后，根据所述请求消息管理和控制相应的网络设备和/或基础设施，即向相应的网络设备和/或基础设施发送网络指令。
所述网络设备层中包括网络设备和基础设施等，例如路由器(Router)、交换机(Switch)等，其中，所述网络设备层中的网络设备和基础设施可以但不限于为以下应用场景中的设备：移动宽带(Mobile broadband，MBB)网络、固定宽带(Fixed broadband，FBB)网络、软件定义网络(Software Defined Network，SDN)、网络功能虚拟化(Network Function Virtualization，NFV)以及混合云(hybrid cloud)。
基于如图1所示的ICT网络，本发明实施例提供了另一种可能的如图2示出ICT网络的架构。其中，在该ICT网络中，按照所述ICT-O***的逻辑功能，可以将所述ICT-O***不同分为多个逻辑模块，如图所示，所述ICT-O***中包括业务和实例管理模块、业务分解设计模块、执行器、分发器以及分组管理器等。其中，
所述业务和实例管理模块，为所述ICT-O***的入口，负责接收用户通过WEB控制台或其他***发来的业务请求，并对所述业务请求的生命周期进行管理，用户可以通过所述业务和实例管理模块进行业务的新增、修改、删除和查看等操作。
所述业务分解设计模块，可以根据所述ICT-O***维护的网络业务设计服务、与业务设计服务等，把面向用户的所述业务请求通过分解和重新设计，转换成ICT网络中的控制器可以理解和处理的、面向设备的多个请求消息，其中每个请求消息中包含其对应的目标控制器的信息。
所述执行器，根据分解生成的多个请求消息之间的约束关系以及关联关系，对所述多个请求消息进行调度，即所述执行器需要保证面向设备的请求消息能够快速且可靠的执行，例如对于某些可以并行处理的请求消息，所述执行器并行执行这些请求消息；对于某 些需要按照顺序执行的请求消息，所述执行器按照该顺序依次执行这些请求消息。
所述分发器，在多个驱动适配插件中，为每个请求消息选择一个驱动适配插件，使每个请求消息可以通过选择的驱动适配插件发送至相应的目标控制器。当所述ICT-O***中维护有分组管理器时，所述分组管理器可以为所述ICT网络中的每个控制器分配对应的驱动适配插件组，生成多个控制器的信息和驱动适配插件组的对应关系；所述分发器可以根据每个请求消息中包含的目标控制器的信息，确定驱动适配插件组，然后选择驱动适配插件组中包含的一个驱动适配插件发送相应的请求消息。所述分发器可以包括具有分发特性的总线，本发明对此不做限定。
所述分组管理器，可以为所述ICT网络中的每个控制器分配对应的驱动适配插件组，生成多个控制器的信息和驱动适配插件组的对应关系，其中，任意一个控制器对应的驱动适配插件组中包含的至少一个驱动适配插件与所述控制器相连。其中，所述分组管理器可以根据网络部署需求、地理位置的分布、执行效率的需求、多用户并发处理、可靠性的需要，分别为每个控制器分配对应的驱动适配插件组，从而生成多个控制器的信息和驱动适配插件组的对应关系。
在该ICT网络中的驱动适配插件，是连接控制器和所述ICT-O***的桥梁，其中，一个驱动适配插件可以对应至少一个控制器，而一个控制器也有至少一个驱动适配插件对应。
ICT网络通常情况下采用服务集群化和云化部署方式，这样，该网络中的控制器的数量等级较高，驱动适配插件的数量等级也相应较高。在现有技术中，ICT-O***中的分发器在收到一个请求消息后，对所述ICT网络中的所有驱动适配插件进行负载均衡，选择其中一个适当的驱动适配插件传输该请求消息。然而，由于所述ICT网络中的驱动适配插件的数量等级较高，所述分发器对所有驱动适配插件进行负载均衡，增加分发器的计算量，增加了筛选出适当的驱动适配插件的时间，从而降低了用户的体验；
且所述ICT网络中的某些驱动适配插件与某些控制器之间不能建立连接，例如，某控制器具有连接限制数量，所述连接限制数量即所述控制器最多可连接的驱动适配插件的数量，因此，当所述ICT网络中的驱动适配插件大于所述连接限制数量时，所述ICT网络中最多有连接限制数量的驱动适配插件与所述控制器相连，其余的驱动适配插件不能与所述控制器相连；又例如，某控制器的归属地为北京，而某些驱动适配插件的归属地为深圳，因此，这些驱动适配插件不能与该控制器相连。基于以上描述，所述分发器为某请求消息选择出的符合负载均衡的驱动适配插件与该请求消息对应的目标控制器未连接的概率较大，即该请求消息传输失败的概率较大，该请求消息传输的可靠性较低。
参阅图3所示，本发明实施例提供的一种请求消息传输方法，该方法可以适用于如图1和图2所示的ICT网络中的ICT-O***，本发明实施例涉及的分发器为所述ICT-O***中具有分发功能的模块。该方法的处理流程包括：
步骤301：分发器接收到请求消息后，获取所述请求消息中包含的第一控制器的信息。
其中，所述请求消息为所述ICT-O***对接收的一个业务请求分解得到的多个请求消息中的一个，其中所述ICT-O***分解的每个请求消息中均包含对应的目标控制器的信息。所述第一控制器即为所述请求消息的目标控制器。
所述第一控制器的信息为唯一标识所述第一控制器的信息，例如所述第一控制器的标识等信息。
可选的，所述第一控制器的信息为所述第一控制器的路由标识，所述路由标识能够唯一标识所述第一控制器。所述第一控制器的路由标识为所述第一控制器在向所述ICT-O***注册时，所述ICT-O***生成的，可选的，所述ICT-O***按照设定规则，将所述第一控制器的标识进行转换生成所述第一控制器的路由标识。
步骤302：所述分发器在多个控制器的信息与驱动适配插件组的对应关系中，确定所述第一控制器的信息对应的第一驱动适配插件组，其中，所述第一控制器与所述第一驱动适配插件组中包含的至少一个驱动适配插件相连。
其中所述多个控制器的信息与驱动适配插件组的对应关系可以存储在所述分发器本地，或者存储在所述ICT-O***中的其他存储设备(例如分组管理器)中。
基于图2中对ICT-O***的描述可知，所述ICT-O***中分组管理器可以为所述ICT网络中的每个控制器分配对应的驱动适配插件组，生成多个控制器的信息和驱动适配插件组的对应关系，且任意一个控制器对应的驱动适配插件组中包含的至少一个驱动适配插件与所述控制器相连。
由于所述第一驱动适配插件组中包含的至少一个驱动适配插件均与所述第一控制器相连，保证所述分发器通过所述第一驱动适配插件组中包含的任意一个驱动适配插件，都可以成功将所述请求消息传输至所述第一控制器，降低了由于控制器与驱动适配插件没有连接导致的请求消息传输失败的概率，提高了请求消息传输的可靠性。
可选的，所述第一驱动适配插件组中包含的每个驱动适配插件的类型相同。驱动适配插件可以根据网络类型(如SDN、NFV等)、设备类型(如IP设备、广域网(Wide Area Network)设备等)、协议类型(如开放式流(Openflow)协议、表述性状态传递(Representational State Transfer，REST)协议、简单对象访问协议(Simple Object Access Protocol，SOAP)等)以及生产厂商划分为不同的类型。
由于不同的类型的驱动适配插件，其请求的统一资源定位符(Uniform Resource Locator，URL)不同，维护的接口也不同，因此，所述第一驱动适配插件组中至少一个驱动适配插件的类型的均相同，且该类型的驱动适配插件的接口与所述第一控制器的接口相匹配。可选的，与所述驱动适配插件类似，当控制器也划分为不同的类型时，所述第一驱动适配插件组中每个驱动适配插件的类型与所述第一控制器的类型匹配。
通过上述方式，所述第一驱动适配插件组中至少一个驱动适配插件的类型均相同，且该类型的驱动适配插件的接口与所述第一控制器的接口相匹配，所述分发器可以保证通过所述第一驱动适配插件组中包含的任意一个驱动适配插件，都可以成功将所述请求消息传输至所述第一控制器，降低了由于控制器与驱动适配插件接口不匹配导致的请求消息传输失败的概率，提高了请求消息传输的可靠性。
当所述第一驱动适配插件组中包含至少一个驱动适配插件的类型不同，那么所述请求消息中还包含驱动适配插件的第一类型。
其中所述请求消息中包含的驱动适配插件的第一类型，表示只有通过该第一类型的驱动适配插件，所述分发器才可以将所述请求消息成功传输给所述第一控制器，即所述第一类型的驱动适配插件的接口与所述第一控制器的接口相匹配。
通过上述方法，所述分发器后续可以在所述第一驱动适配插件组中筛选出第一类型的至少一个待选驱动适配插件，所述分发器可以保证通过所述至少一个待选驱动适配插件中的任意一个驱动适配插件，都可以成功将所述请求消息传输至所述第一控制器，降低了由 于控制器与驱动适配插件接口不匹配导致的请求消息传输失败的概率，提高了请求消息传输的可靠性。
可选的，在所述多个控制器与驱动适配插件组的对应关系中，所述第一驱动适配插件组对应的多个控制器中每个控制器的连接限制数量相同，且所述第一驱动适配插件组中包含的驱动适配插件的数量小于或等于所述第一驱动适配插件组对应的每个控制器的连接限制数量。
当所述ICT网络中存在具有连接限制数量的第二控制器时，任意一个第二控制器对应的驱动适配插件组中包含的驱动适配插件的数量小于或等于该第二控制器的连接限制数量，若存在连接限制数量相同的多个第二控制器时，所述多个第二控制器可以对应相同的驱动适配插件组。
通过上述方法，当所述第一控制器具有连接限制数量时，所述分发器可以保证通过所述第一驱动适配插件组中的任意一个驱动适配插件，都可以成功将所述请求消息传输至所述第一控制器，避免所述第一驱动适配插件组中包含的驱动适配插件的数量大于所述第一控制器的连接限制数量时，所述分发器选择的目标驱动适配插件未与所述第一控制相连导致的请求消息传输失败的情况，提高了请求消息传输的可靠性。
可选的，在所述多个控制器与驱动适配插件组的对应关系中，所述第一驱动适配插件组对应的多个控制器中每个控制器的归属地与所述第一驱动适配插件组中包含的每个驱动适配插件的归属地相同。
通过上述方法，所述分发器可以保证通过所述第一驱动适配插件组中的任意一个驱动适配插件，都可以成功将所述请求消息传输至所述第一控制器，避免由于所述第一驱动适配插件组中存在归属地与所述第一控制器的归属地不同的驱动适配插件时，所述分发器选择的目标驱动适配插件与所述第一控制归属地不同导致的请求消息传输失败的情况，提高了请求消息传输的可靠性。
步骤303：所述分发器在所述第一驱动适配插件组中包含的与所述第一控制器相连的所述至少一个驱动适配插件中确定至少一个待选驱动适配插件，所述至少一个待选驱动适配插件的运行状态为正常。
在步骤303中，所述分发器可以在所述第一驱动适配插件组中确定出运行状态为正常的待选驱动适配插件，进而在待选驱动适配插件中选择一个目标驱动适配插件，所述分发器可以保证通过所述至少一个待选驱动适配插件中的任意一个驱动适配插件，都可以成功将所述请求消息传输至所述第一控制器，避免由于驱动适配插件运行异常导致的请求消息传输失败的概率，提高了请求消息传输的可靠性。
可选的，当所述第一驱动适配插件组中包含至少一个驱动适配插件的类型不同，那么所述请求消息中还包含驱动适配插件的第一类型；
在所述分发器在确定所述至少一个待选驱动适配插件之前，所述方法还包括：
所述分发器获取所述请求消息中包含的所述第一类型；
所述分发器在确定所述至少一个待选驱动适配插件，包括：
所述分发器在所述至少一个驱动适配插件中确定类型与所述第一类型相同的所述至少一个待选驱动适配插件。
通过上述方法，所述分发器后续可以在所述第一驱动适配插件组中筛选出第一类型的至少一个待选驱动适配插件，所述分发器可以保证通过所述至少一个待选驱动适配插件中 的任意一个驱动适配插件，都可以成功将所述请求消息传输至所述第一控制器，降低了由于控制器与驱动适配插件接口不匹配导致的请求消息传输失败的概率，提高了请求消息传输的可靠性。
步骤304：所述分发器通过所述至少一个待选驱动适配插件中的一个待选驱动适配插件，将所述请求消息发送至所述第一控制器。
当所述至少一个待选驱动适配插件的数目为多个时，所述分发器在执行步骤304时，包括：
所述分发器通过对所述至少一个待选驱动适配插件进行负载均衡处理，确定目标驱动适配插件，所述目标驱动适配插件为所述至少一个待选驱动适配插件中的一个；
所述分发器通过所述目标驱动适配插件将所述请求消息发送至所述第一控制器。
其中，所述分发器使用的负载均衡处理的方法，可以包括多种，例如按照设定顺序轮询方法，或者随机选择方法等，或者选择符合设定特征的方法，本发明对此不做限定。
所述分发器通过对所述至少一个待选驱动适配插件进行负载均衡处理，确定其中一个目标驱动适配插件，可以保证所述至少一个待选驱动适配插件的负载均衡。
采用本发明上述实施例中的请求消息传输方法，部署于ICT-O***中的分发器在接收到一个请求消息后，根据所述请求消息中包含的第一控制器的信息，确定所述第一控制器的信息对应的第一驱动适配插件组，其中，所述第一控制器与所述第一驱动适配插件组中包含的至少一个驱动适配插件相连；所述分发器在所述第一驱动适配插件组包含的所述至少一个驱动适配插件中筛选出运行状态为正常的至少一个待选驱动适配插件，最终所述分发器可以通过一个待选驱动适配插件将所述请求消息发送至所述第一控制器。由于所述第一驱动适配插件组中包含的至少一个驱动适配插件均与所述第一控制器相连，保证所述分发器通过所述第一驱动适配插件组中包含的任意一个驱动适配插件，都可以成功将所述请求消息传输至所述第一控制器，降低了由于控制器与驱动适配插件没有连接导致的请求消息传输失败的概率，提高了请求消息传输的可靠性，另外，所述分发器在所述第一驱动适配插件组中包含的至少一个驱动适配插件中筛选出运行状态为正常的至少一个待选驱动适配插件，进一步保证了所述分发器通过其中一个待选驱动适配插件，可以成功将所述请求消息传输至所述第一控制器，避免了由于驱动适配插件运行异常导致请求消息传输失败的情况。
基于上述实施例，本发明实施例提供了一种请求消息传输示例，参阅图4所示，其中，在ICT-O***中包括执行器和分发器，该示例的流程包括：
步骤401：所述执行器向所述分发器发送请求消息，所述请求消息中携带控制器的信息——SDN_controller1。其中，所述请求消息为所述ICT-O***将一业务请求进行分解后得多的多个请求消息中的一个。
步骤402：所述分发器根据所述SDN_controller1，在多个控制器的信息与驱动适配插件组的对应关系中，确定SDN_controller1对应的驱动适配插件组。其中确定的驱动适配插件组中包括与所述SDN_controller1对应的控制器相连的至少一个驱动适配插件，如图5所示的分发器确定待选驱动适配插件的流程中的步骤501。
步骤403：所述分发器在确定的驱动适配插件组中筛选出至少一个待选驱动适配插件，每个待选驱动适配插件的运行状态为正常。如图5中的步骤502得到确定的驱动适配插件组中的多个驱动适配插件；再如步骤503所示，在多个驱动适配插件中筛选运行状态为正 常的两个待选驱动适配插件。
步骤404：所述分发器对所述至少一个待选驱动适配插件进行负载均衡处理，确定目标驱动适配插件。
步骤405：所述分发器将所述请求消息发送至所述目标驱动适配插件。
可选的，当所述分发器包括总线和处理模块时，所述总线在收到所述请求消息后，通过所述处理模块执行所述步骤402至步骤404，并将所述目标驱动适配插件(即所述目标驱动适配插件的标识)返回给所述总线。所述总线再执行步骤405。
步骤406：所述目标驱动适配插件将所述请求消息发送至所述SDN_controller1对应的控制器。
步骤407：所述SDN_controller1对应的控制器向所述目标驱动适配插件返回响应消息，可选的，所述响应消息为所述请求消息的执行结果。
步骤408：所述目标驱动适配插件向所述分发器返回所述响应消息。
步骤409：所述分发器向所述执行器返回所述响应消息。
在上述示例中，部署于ICT-O***中的分发器在接收到一个请求消息后，根据所述请求消息中包含的控制器的信息，确定所述控制器的信息对应的驱动适配插件组，其中，所述控制器与所述驱动适配插件组中包含的至少一个驱动适配插件相连；所述分发器在所述驱动适配插件组包含的所述至少一个驱动适配插件中筛选出运行状态为正常的至少一个待选驱动适配插件，然后对所述至少一个待选驱动适配插件进行负载均衡处理，在所述至少一个待选驱动适配插件中确定目标驱动适配插件，最终所述分发器可以通过所述目标驱动适配插件将所述请求消息发送至所述控制器。由于所述驱动适配插件组中包含的至少一个驱动适配插件均与所述控制器相连，保证所述分发器通过所述驱动适配插件组中包含的任意一个驱动适配插件，都可以成功将所述请求消息传输至所述控制器，降低了由于控制器与驱动适配插件没有连接导致的请求消息传输失败的概率，提高了请求消息传输的可靠性，另外，所述分发器在所述驱动适配插件组中包含的至少一个驱动适配插件中筛选出运行状态为正常的至少一个待选驱动适配插件，进一步保证了所述分发器通过选择的目标驱动适配插件，可以成功将所述请求消息传输至所述控制器，避免了由于驱动适配插件运行异常导致请求消息传输失败的情况。
根据以上实施例中的论述可知，在所述ICT-O***中需要维护多个控制器的信息与驱动适配插件组的对应关系，所述多个控制器的信息与驱动适配插件组的对应关系为所述ICT-O***生成，可选的，所述ICT-O***可以如图1或图2所示的ICT网络中的ICT-O***，本发明实施例涉及的分组管理器可以为图2中所示的分组管理器。参阅图6所示，本发明实施例还提供了一种控制器的信息与驱动适配插件组的对应关系生成方法的流程包括：
步骤601：分组管理器获取控制器的信息。
所述控制器的信息为可以唯一标识所述控制器的信息，例如所述控制器的标识等信息。
可选的，所述控制器的信息为所述控制器的路由标识，所述路由标识能够唯一标识所述所述控制器。所述控制器的路由标识为所述控制器在向所述ICT-O***注册时，所述ICT-O***生成的，可选的，所述ICT-O***按照设定规则，将所述控制器的标识进行转换生成所述控制器的路由标识。
步骤602：所述分组管理器在多个驱动适配插件中，确定出所述控制器对应的至少一个驱动适配插件，其中，所述控制器与所述至少一个驱动适配插件相连。
可选的，所述分组管理器在多个驱动适配插件中，确定出所述控制器对应的至少一个驱动适配插件，包括：
所述分组管理器获取所述多个驱动适配插件中每个驱动适配插件组的类型；
所述分组管理器在所述多个驱动适配插件中确定出类型相同的所述至少一个驱动适配插件。
由于不同的类型的驱动适配插件，其请求的统一资源定位符(Uniform Resource Locator，URL)不同，维护的接口也不同，因此，所述分组管理器确定与所述控制器的接口相匹配的驱动适配插件的接口，然后确定该驱动适配插件的类型，最终确定该类型的驱动适配插件的接口与所述控制器的接口相匹配。因此，所述分组管理器可以在多个驱动适配插件中筛选出类型相同的(即为该类型的)所述至少一个驱动适配插件。可选的，与所述驱动适配插件类似，当控制器也划分为不同的类型时，所述分组管理器筛选出与所述控制器的类型匹配的所述第一驱动适配插件组中每个驱动适配插件的类型与所述第一控制器的所述至少一个驱动适配插件。
通过上述方式，筛选出的至少一个驱动适配插件的类型均相同，且该类型的驱动适配插件的接口与所述控制器的接口相匹配，后续所述分发器可以保证通过上述至少一个驱动适配插件中的任意一个驱动适配插件，都可以成功将请求消息传输至所述控制器，降低了由于控制器与驱动适配插件接口不匹配导致的请求消息传输失败的概率，提高了请求消息传输的可靠性。
可选的，所述至少一个驱动适配插件的数量小于或等于所述控制器的连接限制数量。
通过上述方法，当所述控制器具有连接限制数量时，所述分发器可以保证通过上述至少一个驱动适配插件中的任意一个驱动适配插件，都可以成功将请求消息传输至所述控制器，避免所述至少一个驱动适配插件的数量大于所述控制器的连接限制数量时，所述分发器选择的目标驱动适配插件未与所述控制相连导致的请求消息传输失败的情况，提高了请求消息传输的可靠性。
可选的，所述至少一个驱动适配插件的归属地与所述控制器的归属地相同。
通过上述方法，所述分发器可以保证通过所述至少一个驱动适配插件中的任意一个驱动适配插件，都可以成功将请求消息传输至所述控制器，避免由于所述至少一个驱动适配插件中存在归属地与所述控制器的归属地不同的驱动适配插件时，所述分发器选择的目标驱动适配插件与所述控制归属地不同导致的请求消息传输失败的情况，提高了请求消息传输的可靠性。
步骤603：所述分组管理器生成所述控制器的信息与驱动适配插件组的对应关系，其中，所述驱动适配插件组包含所述至少一个驱动适配插件。
所述分组管理器生成所述控制器与驱动适配插件组的对应关系，可以提高后续所述分发器查找所述控制器对应的所述至少一个驱动适配插件的效率，同时，便于所述分组管理器管理和控制所述控制器与驱动适配插件组的对应关系。
可选的，在所述分组管理器生成所述控制器的信息与驱动适配插件组的对应关系后，还包括：
所述分组管理器获取所述至少一个驱动适配插件的运行状态。可选的，所述分组管理 器可以通过定时获取所述至少一个驱动适配插件的运行状态，或者所述至少一个驱动适配插件可以定时上报所述至少一个驱动适配插件的运行状态，或者，所述至少一个驱动适配插件确定自身运行状态发生变化时，上报当前自身的运行状态，本发明对此不做限定。
通过上述方法，所述分组管理器可以确定所述控制器对应的驱动适配插件组中每个驱动适配插件的运行状态。在后续所述分发器在确定待选驱动适配插件时，可以根据所述分组管理器获取的所述至少一个驱动适配插件的运行状态，在所述至少一个驱动适配插件中筛选出运行状态为正常的至少一个待选驱动适配插件。
可选的，所述分组管理器还要对生成的所述控制器的信息与驱动适配插件组的对应关系进行后期维护，例如，当所述控制器注销时，所述分组管理器删除删除所述控制器的信息与驱动适配插件组的对应关系；驱动适配插件组中的驱动适配插件注销时，删除所述控制器对应的驱动适配插件组中的注销的驱动适配插件；当所述分发器根据所述驱动适配插件组中的一个目标驱动适配插件发送请求消息给所述控制器发送失败时，所述分组管理器也可以删除所述控制器对应的驱动适配插件组中的所述目标驱动适配插件。
可选的，所述分组管理器可以通过上述方法，生成多个控制器的信息与驱动适配插件组的对应关系中的每个对应关系。可选的，所述分组管理器可以定期更新多个控制核的信息与驱动适配插件组的对应关系，可以在一个控制器或一个驱动适配插件向ICT-O***注册时，所述分组管理器针对注册的所述控制器或所述驱动适配插件，生成控制器与驱动适配插件组的对应关系，本发明对此也不做限定。
其中，在所述分组管理器根据驱动适配插件的类型，筛选驱动适配插件，进而生成控制器与驱动适配插件组的对应关系的情况下，这样，在新的类型的控制器被开发出来时，所述分发器不需要修改或调整ICT网络中原有的驱动适配插件，因此不会中断业务，通过所述分组管理器针对该控制器生成的该控制器与驱动适配插件组的对应关系，所述分发器可以在该控制器对应的驱动适配插件组中选择一个目标驱动适配插件向改控制器发送请求消息，缩短了业务处理时延，提高了用户的体验。
采用本发明实施例提供的控制器的信息与驱动适配插件组的对应关系生成方法，部署于ICT-O***中的分组管理器在获取ICT网络中的一个控制器的信息后，在所述ICT网络中的多个驱动适配插件中确定出与所述控制器相连的至少一个驱动适配插件，并建立所述控制器的信息与驱动适配插件组的对应关系，其中，所述驱动适配插件组包含所述至少一个驱动适配插件。这样，由于所述驱动适配插件组中包含的至少一个驱动适配插件均与所述控制器相连，保证所述分发器通过所述驱动适配插件组中包含的任意一个驱动适配插件，都可以成功将请求消息传输至所述控制器，降低了由于控制器与驱动适配插件没有连接导致的请求消息传输失败的概率，提高了请求消息传输的可靠性。
基于以上实施例，本发明还提供了一种分发器，该分发器可以为如图1和图2所示的ICT网络中的ICT-O***中具有分发功能的模块。参阅图7所示，该分发器700包括：接收单元701、处理单元702，以及发送单元703，其中，
接收单元701，用于接收请求消息；
处理单元702，用于获取所述请求消息中包含的第一控制器的信息；
在多个控制器的信息与驱动适配插件组的对应关系中，确定所述第一控制器的信息对应的第一驱动适配插件组，其中，所述第一控制器与所述第一驱动适配插件组中包含的至少一个驱动适配插件相连；
在所述第一驱动适配插件组中包含的与所述第一控制器相连的所述至少一个驱动适配插件中确定至少一个待选驱动适配插件，所述至少一个待选驱动适配插件的运行状态为正常；
发送单元703，用于通过所述至少一个待选驱动适配插件中的一个待选驱动适配插件，将所述请求消息发送至所述第一控制器。
可选的，所述第一控制器的信息为所述第一控制器的路由标识，所述路由标识能够唯一标识所述第一控制器。
可选的，所述第一驱动适配插件组中包含的每个驱动适配插件的类型相同。
可选的，所述请求消息中还包含驱动适配插件的第一类型；
所述处理单元702，还用于：
在所述第一驱动适配插件组中包含的与所述第一控制器相连的所述至少一个驱动适配插件中确定所述至少一个待选驱动适配插件之前，获取所述请求消息中包含的所述第一类型；
所述处理单元702在所述第一驱动适配插件组中包含的与所述第一控制器相连的所述至少一个驱动适配插件中确定所述至少一个待选驱动适配插件时，具体用于：
在所述至少一个驱动适配插件中确定类型与所述第一类型相同，且运行状态为正常所述至少一个待选驱动适配插件。
可选的，在所述多个控制器与驱动适配插件组的对应关系中，所述第一驱动适配插件组对应的多个控制器中每个控制器的连接限制数量相同，且所述第一驱动适配插件组中包含的驱动适配插件的数量小于或等于所述第一驱动适配插件组对应的每个控制器的连接限制数量。
可选的，在所述多个控制器与驱动适配插件组的对应关系中，所述第一驱动适配插件组对应的多个控制器中每个控制器的归属地与所述第一驱动适配插件组中包含的每个驱动适配插件的归属地相同。
可选的，当所述至少一个待选驱动适配插件的数目为多个时，所述处理单元702，还用于：
在所述第一驱动适配插件组中包含的与所述第一控制器相连的所述至少一个驱动适配插件中确定所述多个待选驱动适配插件之后，在所述发送单元通过所述至少一个待选驱动适配插件中的一个待选驱动适配插件，将所述请求消息发送至所述第一控制器之前，通过对所述多个待选驱动适配插件进行负载均衡处理，确定目标驱动适配插件，所述目标驱动适配插件为所述多个待选驱动适配插件中的一个；
所述发送单元703，具体用于：
通过所述目标驱动适配插件将所述请求消息发送至所述第一控制器。
采用本发明实施例提供的分发器，所述分发器根据所述请求消息中包含的第一控制器的信息，确定所述第一控制器的信息对应的第一驱动适配插件组，其中，所述第一控制器与所述第一驱动适配插件组中包含的至少一个驱动适配插件相连；所述分发器在所述第一驱动适配插件组包含的所述至少一个驱动适配插件中筛选出运行状态为正常的至少一个待选驱动适配插件，最终所述分发器可以通过一个待选驱动适配插件将所述请求消息发送至所述第一控制器。由于所述第一驱动适配插件组中包含的至少一个驱动适配插件均与所述第一控制器相连，保证所述分发器通过所述第一驱动适配插件组中包含的任意一个驱动 适配插件，都可以成功将所述请求消息传输至所述第一控制器，降低了由于控制器与驱动适配插件没有连接导致的请求消息传输失败的概率，提高了请求消息传输的可靠性，另外，所述分发器在所述第一驱动适配插件组中包含的至少一个驱动适配插件中筛选出运行状态为正常的至少一个待选驱动适配插件，进一步保证了所述分发器通过其中一个待选驱动适配插件，可以成功将所述请求消息传输至所述第一控制器，避免了由于驱动适配插件运行异常导致请求消息传输失败的情况。
基于以上实施例，本发明还提供了一种分组管理器，该分组管理器可以应用于如图1和图2所示的ICT网络中的ICT-O***中，该分组管理器具有生成控制器的信息与驱动适配插件组的对应关系的功能。参阅图8所示，该分组管理器800包括：处理单元801和生成单元802，其中，
处理单元801，用于获取控制器的信息；并
在多个驱动适配插件中，确定出所述控制器对应的至少一个驱动适配插件，其中，所述控制器与所述至少一个驱动适配插件相连；
生成单元802，用于生成所述控制器的信息与驱动适配插件组的对应关系，其中，所述驱动适配插件组包含所述至少一个驱动适配插件。
可选的，所述控制器的信息为所述控制器的路由标识，所述路由标识能够唯一标识所述所述控制器。
可选的，所述处理单元801，具体用于：
获取所述多个驱动适配插件中每个驱动适配插件组的类型；
在所述多个驱动适配插件中确定出类型相同的所述至少一个驱动适配插件。
可选的，所述至少一个驱动适配插件的数量小于或等于所述控制器的连接限制数量。
可选的，所述至少一个驱动适配插件的归属地与所述控制器的归属地相同。
可选的，所述处理单元801，还用于：
在所述生成单元802生成所述控制器的信息与驱动适配插件组的对应关系后，获取所述至少一个驱动适配插件的运行状态。
采用本发明实施例提供的分组管理器，所述分组管理器在获取ICT网络中的一个控制器的信息后，在所述ICT网络中的多个驱动适配插件中筛选出与所述控制器相连的至少一个驱动适配插件，并建立所述控制器的信息与驱动适配插件组的对应关系，其中，所述驱动适配插件组包含所述至少一个驱动适配插件。这样，由于所述驱动适配插件组中包含的至少一个驱动适配插件均与所述控制器相连，保证所述分发器通过所述驱动适配插件组中包含的任意一个驱动适配插件，都可以成功将请求消息传输至所述控制器，降低了由于控制器与驱动适配插件没有连接导致的请求消息传输失败的概率，提高了请求消息传输的可靠性。
需要说明的是，本发明实施例中对单元的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。在本申请的实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能单元的形式实现。
所述集成的单元如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的全部或部分可以以软件产品的形式体现 出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)或处理器(processor)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(ROM，Read-Only Memory)、随机存取存储器(RAM，Random Access Memory)、磁碟或者光盘等各种可以存储程序代码的介质。
基于以上实施例，本发明实施例还提供了一种分发器，该分发器可以为如图1和图2所示的ICT网络中的ICT-O***中具有分发功能的设备。参阅图9所示，所述分发器900包括：收发器901、处理器902、总线903以及存储器904，其中，
所述收发器901、所述处理器902和所述存储器904通过所述总线903相互连接；总线903可以是外设部件互连标准(peripheral component interconnect，简称PCI)总线或扩展工业标准结构(extended industry standard architecture，简称EISA)总线等。所述总线可以分为地址总线、数据总线、控制总线等。为便于表示，图9中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。
所述收发器901，用于与所述分发器900相连的其他设备进行通信交互。
所述处理器902，用于实现如图3所示的请求消息传输方法，包括：
接收到请求消息后，获取所述请求消息中包含的第一控制器的信息；
在多个控制器的信息与驱动适配插件组的对应关系中，确定所述第一控制器的信息对应的第一驱动适配插件组，其中，所述第一控制器与所述第一驱动适配插件组中包含的至少一个驱动适配插件相连；
在所述第一驱动适配插件组中包含与所述第一控制器相连的的所述至少一个驱动适配插件中确定至少一个待选驱动适配插件，所述至少一个待选驱动适配插件的运行状态为正常；
通过所述至少一个待选驱动适配插件中的一个待选驱动适配插件，将所述请求消息发送至所述第一控制器。
可选的，所述第一控制器的信息为所述第一控制器的路由标识，所述路由标识能够唯一标识所述第一控制器。
可选的，所述第一驱动适配插件组中包含的每个驱动适配插件的类型相同。
可选的，所述请求消息中还包含驱动适配插件的第一类型；
所述处理器902，还用于：
在所述第一驱动适配插件组中包含的与所述第一控制器相连的所述至少一个驱动适配插件中确定所述至少一个待选驱动适配插件之前，获取所述请求消息中包含的所述第一类型；
所述处理器902在所述第一驱动适配插件组中包含的与所述第一控制器相连的所述至少一个驱动适配插件中确定所述至少一个待选驱动适配插件时，具体用于：
在所述至少一个驱动适配插件中确定类型与所述第一类型相同，且运行状态为正常的所述至少一个待选驱动适配插件。
可选的，在所述多个控制器与驱动适配插件组的对应关系中，所述第一驱动适配插件组对应的多个控制器中每个控制器的连接限制数量相同，且所述第一驱动适配插件组中包含的驱动适配插件的数量小于或等于所述第一驱动适配插件组对应的每个控制器的连接限制数量。
可选的，在所述多个控制器与驱动适配插件组的对应关系中，所述第一驱动适配插件组对应的多个控制器中每个控制器的归属地与所述第一驱动适配插件组中包含的每个驱动适配插件的归属地相同。
可选的，当所述至少一个待选驱动适配插件的数目为多个时，所述处理器902在通过所述至少一个待选驱动适配插件中的一个待选驱动适配插件，将所述请求消息发送至所述第一控制器时，具体用于：
通过对所述多个待选驱动适配插件进行负载均衡处理，确定目标驱动适配插件，所述目标驱动适配插件为所述多个待选驱动适配插件中的一个；
通过所述目标驱动适配插件将所述请求消息发送至所述第一控制器。
存储器904，用于存放程序等。具体地，程序可以包括程序代码，该程序代码包括计算机操作指令。存储器904可能包含易失性存储器(英文：volatile memory)，例如随机存取存储器(英文：random-access memory，缩写：RAM)；存储器也可以是非易失性存储器(英文：non-volatile memory)，例如只读存储器(英文：read-only memory，缩写：ROM)，快闪存储器(英文：flash memory)，硬盘(英文：hard disk drive，缩写：HDD)或固态硬盘(英文：solid-state drive，缩写：SSD)、或者存储器是能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质，但不限于此。存储器可以是上述存储器的组合。处理器902执行存储器904所存放的应用程序，实现上述功能，从而实现如图3所示的请求消息传输方法。
采用本发明实施例提供的分发器，所述分发器根据所述请求消息中包含的第一控制器的信息，确定所述第一控制器的信息对应的第一驱动适配插件组，其中，所述第一控制器与所述第一驱动适配插件组中包含的至少一个驱动适配插件相连；所述分发器在所述第一驱动适配插件组包含的所述至少一个驱动适配插件中筛选出运行状态为正常的至少一个待选驱动适配插件，最终所述分发器可以通过一个待选驱动适配插件将所述请求消息发送至所述第一控制器。由于所述第一驱动适配插件组中包含的至少一个驱动适配插件均与所述第一控制器相连，保证所述分发器通过所述第一驱动适配插件组中包含的任意一个驱动适配插件，都可以成功将所述请求消息传输至所述第一控制器，降低了由于控制器与驱动适配插件没有连接导致的请求消息传输失败的概率，提高了请求消息传输的可靠性，另外，所述分发器在所述第一驱动适配插件组中包含的至少一个驱动适配插件中筛选出运行状态为正常的至少一个待选驱动适配插件，进一步保证了所述分发器其中一个待选驱动适配插件，可以成功将所述请求消息传输至所述第一控制器，避免了由于驱动适配插件运行异常导致请求消息传输失败的情况。
基于以上实施例，本发明实施例还提供了一种分组管理器，该分组管理器可以为如图1和图2所示的ICT网络中的ICT-O***中，该分组管理器具有生成控制器的信息与驱动适配插件组的对应关系的功能。参阅图10所示，所述分组管理器1000包括：收发器1001、处理器1002、总线1003以及存储器1004，其中，
所述收发器1001、所述处理器1002和所述存储器1004通过所述总线1003相互连接；总线1003可以是外设部件互连标准(peripheral component interconnect，简称PCI)总线或扩展工业标准结构(extended industry standard architecture，简称EISA)总线等。所述总线可以分为地址总线、数据总线、控制总线等。为便于表示，图10中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。
所述收发器1001，用于与所述分组管理器相连的其他设备进行通信交互。
所述处理器1002，用于实现如图6所示的控制器的信息与驱动适配插件组的对应关系生成方法，包括：
获取控制器的信息；
在多个驱动适配插件中，确定出所述控制器对应的至少一个驱动适配插件，其中，所述控制器与所述至少一个驱动适配插件相连；
生成所述控制器的信息与驱动适配插件组的对应关系，其中，所述驱动适配插件组包含所述至少一个驱动适配插件。
可选的，所述控制器的信息为所述控制器的路由标识，所述路由标识能够唯一标识所述所述控制器。
可选的，所述处理器1002在多个驱动适配插件中，确定出所述控制器对应的至少一个驱动适配插件时，具体用于：
获取所述多个驱动适配插件中每个驱动适配插件组的类型；
在所述多个驱动适配插件中确定出类型相同的所述至少一个驱动适配插件。
可选的，所述至少一个驱动适配插件的数量小于或等于所述控制器的连接限制数量。
可选的，所述至少一个驱动适配插件的归属地与所述控制器的归属地相同。
可选的，所述处理器1002，还用于：
在生成所述控制器的信息与驱动适配插件组的对应关系后，获取所述至少一个驱动适配插件的运行状态。
存储器1004，用于存放程序等。具体地，程序可以包括程序代码，该程序代码包括计算机操作指令。存储器1004可能包含易失性存储器(英文：volatile memory)，例如随机存取存储器(英文：random-access memory，缩写：RAM)；存储器也可以是非易失性存储器(英文：non-volatile memory)，例如只读存储器(英文：read-only memory，缩写：ROM)，快闪存储器(英文：flash memory)，硬盘(英文：hard disk drive，缩写：HDD)或固态硬盘(英文：solid-state drive，缩写：SSD)、或者存储器是能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质，但不限于此。存储器可以是上述存储器的组合。处理器1002执行存储器1004所存放的应用程序，实现上述功能，从而实现如图6所示的控制器的信息与驱动适配插件组的对应关系生成方法。
采用本发明实施例提供的分组管理器，所述分组管理器在获取ICT网络中的一个控制器的信息后，在所述ICT网络中的多个驱动适配插件中筛选出与所述控制器相连的至少一个驱动适配插件，并建立所述控制器的信息与驱动适配插件组的对应关系，其中，所述驱动适配插件组包含所述至少一个驱动适配插件。这样，由于所述驱动适配插件组中包含的至少一个驱动适配插件均与所述控制器相连，保证所述分发器通过所述驱动适配插件组中包含的任意一个驱动适配插件，都可以成功将请求消息传输至所述控制器，降低了由于控制器与驱动适配插件没有连接导致的请求消息传输失败的概率，提高了请求消息传输的可靠性。
本发明实施例提供了一种请求消息传输方法及装置，在该方法中，部署于ICT-O***中的分发器在接收到一个请求消息后，根据所述请求消息中包含的第一控制器的信息，确定所述第一控制器的信息对应的第一驱动适配插件组，其中，所述第一控制器与所述第一驱动适配插件组中包含的至少一个驱动适配插件相连；所述分发器在所述第一驱动适配插 件组包含的所述至少一个驱动适配插件中筛选出运行状态为正常的至少一个待选驱动适配插件，最终所述分发器可以通过一个待选驱动适配插件将所述请求消息发送至所述第一控制器。由于所述第一驱动适配插件组中包含的至少一个驱动适配插件均与所述第一控制器相连，保证所述分发器通过所述第一驱动适配插件组中包含的任意一个驱动适配插件，都可以成功将所述请求消息传输至所述第一控制器，降低了由于控制器与驱动适配插件没有连接导致的请求消息传输失败的概率，提高了请求消息传输的可靠性，另外，所述分发器在所述第一驱动适配插件组中包含的至少一个驱动适配插件中筛选出运行状态为正常的至少一个待选驱动适配插件，进一步保证了所述分发器通过选择的目标驱动适配插件，可以成功将所述请求消息传输至所述第一控制器，避免了由于驱动适配插件运行异常导致请求消息传输失败的情况。
本领域内的技术人员应明白，本发明的实施例可提供为方法、***、或计算机程序产品。因此，本发明可采用完全硬件实施例、完全软件实施例、或结合软件和硬件方面的实施例的形式。而且，本发明可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器、CD-ROM、光学存储器等)上实施的计算机程序产品的形式。
本发明是参照根据本发明实施例的方法、设备(***)、和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器，使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方式工作的计算机可读存储器中，使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品，该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上，使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理，从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
尽管已描述了本发明的优选实施例，但本领域内的技术人员一旦得知了基本创造性概念，则可对这些实施例做出另外的变更和修改。所以，所附权利要求意欲解释为包括优选实施例以及落入本发明范围的所有变更和修改。
显然，本领域的技术人员可以对本发明实施例进行各种改动和变型而不脱离本发明实施例的精神和范围。这样，倘若本发明实施例的这些修改和变型属于本发明权利要求及其等同技术的范围之内，则本发明也意图包含这些改动和变型在内。

Claims (26)

  1. 一种请求消息传输方法，其特征在于，包括：
    分发器接收到请求消息后，获取所述请求消息中包含的第一控制器的信息；
    所述分发器在多个控制器的信息与驱动适配插件组的对应关系中，确定所述第一控制器的信息对应的第一驱动适配插件组，其中，所述第一控制器与所述第一驱动适配插件组中包含的至少一个驱动适配插件相连；
    所述分发器在所述第一驱动适配插件组中包含的与所述第一控制器相连的所述至少一个驱动适配插件中确定至少一个待选驱动适配插件，所述至少一个待选驱动适配插件的运行状态为正常；
    所述分发器通过所述至少一个待选驱动适配插件中的一个待选驱动适配插件，将所述请求消息发送至所述第一控制器。
  2. 如权利要求1所述的方法，其特征在于，所述第一控制器的信息为所述第一控制器的路由标识，所述路由标识能够唯一标识所述第一控制器。
  3. 如权利要求1或2所述的方法，其特征在于，所述第一驱动适配插件组中包含的每个驱动适配插件的类型相同。
  4. 如权利要求1或2所述的方法，其特征在于，所述请求消息中还包含驱动适配插件的第一类型；
    在所述分发器在所述第一驱动适配插件组中包含的与所述第一控制器相连的所述至少一个驱动适配插件中确定所述至少一个待选驱动适配插件之前，所述方法还包括：
    所述分发器获取所述请求消息中包含的所述第一类型；
    所述分发器在所述第一驱动适配插件组中包含的与所述第一控制器相连的所述至少一个驱动适配插件中确定所述至少一个待选驱动适配插件，包括：
    所述分发器在所述至少一个驱动适配插件中确定类型与所述第一类型相同，且运行状态为正常的所述至少一个待选驱动适配插件。
  5. 如权利要求1-4任一项所述的方法，其特征在于，在所述多个控制器与驱动适配插件组的对应关系中，所述第一驱动适配插件组对应的多个控制器中每个控制器的连接限制数量相同，且所述第一驱动适配插件组中包含的驱动适配插件的数量小于或等于所述第一驱动适配插件组对应的每个控制器的连接限制数量。
  6. 如权利要求1-5任一项所述的方法，其特征在于，在所述多个控制器与驱动适配插件组的对应关系中，所述第一驱动适配插件组对应的多个控制器中每个控制器的归属地与所述第一驱动适配插件组中包含的每个驱动适配插件的归属地相同。
  7. 如权利要求1-6任一项所述的方法，其特征在于，当所述至少一个待选驱动适配插件的数目为多个时，所述分发器通过所述至少一个待选驱动适配插件中的一个待选驱动适配插件，将所述请求消息发送至所述第一控制器，包括：
    所述分发器通过对所述多个待选驱动适配插件进行负载均衡处理，确定目标驱动适配插件，所述目标驱动适配插件为所述多个待选驱动适配插件中的一个；
    所述分发器通过所述目标驱动适配插件将所述请求消息发送至所述第一控制器。
  8. 一种控制器的信息与驱动适配插件组的对应关系生成方法，其特征在于，包括：
    分组管理器获取控制器的信息；
    所述分组管理器在多个驱动适配插件中，确定出所述控制器对应的至少一个驱动适配插件，其中，所述控制器与所述至少一个驱动适配插件相连；
    所述分组管理器生成所述控制器的信息与驱动适配插件组的对应关系，其中，所述驱动适配插件组包含所述至少一个驱动适配插件。
  9. 如权利要求8所述的方法，其特征在于，所述控制器的信息为所述控制器的路由标识，所述路由标识能够唯一标识所述所述控制器。
  10. 如权利要求8或9所述的方法，其特征在于，所述分组管理器在多个驱动适配插件中，确定出所述控制器对应的至少一个驱动适配插件，包括：
    所述分组管理器获取所述多个驱动适配插件中每个驱动适配插件组的类型；
    所述分组管理器在所述多个驱动适配插件中确定出类型相同的所述至少一个驱动适配插件。
  11. 如权利要求8-10任一项所述的方法，其特征在于，所述至少一个驱动适配插件的数量小于或等于所述控制器的连接限制数量。
  12. 如权利要求8-11任一项所述的方法，其特征在于，所述至少一个驱动适配插件的归属地与所述控制器的归属地相同。
  13. 如权利要求8-12任一项所述的方法，其特征在于，在所述分组管理器生成所述控制器的信息与驱动适配插件组的对应关系后，还包括：
    所述分组管理器获取所述至少一个驱动适配插件的运行状态。
  14. 一种分发器，其特征在于，包括：
    接收单元，用于接收请求消息；
    处理单元，用于获取所述请求消息中包含的第一控制器的信息；
    在多个控制器的信息与驱动适配插件组的对应关系中，确定所述第一控制器的信息对应的第一驱动适配插件组，其中，所述第一控制器与所述第一驱动适配插件组中包含的至少一个驱动适配插件相连；
    在所述第一驱动适配插件组中包含的与所述第一控制器相连的所述至少一个驱动适配插件中确定至少一个待选驱动适配插件，所述至少一个待选驱动适配插件的运行状态为正常；
    发送单元，用于通过所述至少一个待选驱动适配插件中的一个待选驱动适配插件，将所述请求消息发送至所述第一控制器。
  15. 如权利要求14所述的分发器，其特征在于，所述第一控制器的信息为所述第一控制器的路由标识，所述路由标识能够唯一标识所述第一控制器。
  16. 如权利要求14或15所述的分发器，其特征在于，所述第一驱动适配插件组中包含的每个驱动适配插件的类型相同。
  17. 如权利要求14或15所述的分发器，其特征在于，所述请求消息中还包含驱动适配插件的第一类型；
    所述处理单元，还用于：
    在所述第一驱动适配插件组中包含的与所述第一控制器相连的所述至少一个驱动适配插件中确定所述至少一个待选驱动适配插件之前，获取所述请求消息中包含的所述第一类型；
    所述处理单元在所述第一驱动适配插件组中包含的与所述第一控制器相连的所述至少一个驱动适配插件中确定所述至少一个待选驱动适配插件时，具体用于：
    在所述至少一个驱动适配插件中确定类型与所述第一类型相同，且运行状态为正常的所述至少一个待选驱动适配插件。
  18. 如权利要求14-17任一项所述的分发器，其特征在于，在所述多个控制器与驱动适配插件组的对应关系中，所述第一驱动适配插件组对应的多个控制器中每个控制器的连接限制数量相同，且所述第一驱动适配插件组中包含的驱动适配插件的数量小于或等于所述第一驱动适配插件组对应的每个控制器的连接限制数量。
  19. 如权利要求14-18任一项所述的分发器，其特征在于，在所述多个控制器与驱动适配插件组的对应关系中，所述第一驱动适配插件组对应的多个控制器中每个控制器的归属地与所述第一驱动适配插件组中包含的每个驱动适配插件的归属地相同。
  20. 如权利要求14-19任一项所述的分发器，其特征在于，当所述至少一个待选驱动适配插件的数目为多个时，所述处理单元，还用于：
    在所述第一驱动适配插件组中包含的与所述第一控制器相连的所述至少一个驱动适配插件中确定所述多个待选驱动适配插件之后，在所述发送单元通过所述至少一个待选驱动适配插件中的一个待选驱动适配插件，将所述请求消息发送至所述第一控制器之前，通过对所述多个待选驱动适配插件进行负载均衡处理，确定目标驱动适配插件，所述目标驱动适配插件为所述多个待选驱动适配插件中的一个；
    所述发送单元，具体用于：
    通过所述目标驱动适配插件将所述请求消息发送至所述第一控制器。
  21. 一种分组管理器，其特征在于，包括：
    处理单元，用于获取控制器的信息；并
    在多个驱动适配插件中，确定出所述控制器对应的至少一个驱动适配插件，其中，所述控制器与所述至少一个驱动适配插件相连；
    生成单元，用于生成所述控制器的信息与驱动适配插件组的对应关系，其中，所述驱动适配插件组包含所述至少一个驱动适配插件。
  22. 如权利要求21所述的分组管理器，其特征在于，所述控制器的信息为所述控制器的路由标识，所述路由标识能够唯一标识所述所述控制器。
  23. 如权利要求21或22所述的分组管理器，其特征在于，所述处理单元，具体用于：
    获取所述多个驱动适配插件中每个驱动适配插件组的类型；
    在所述多个驱动适配插件中确定出类型相同的所述至少一个驱动适配插件。
  24. 如权利要求21-23任一项所述的分组管理器，其特征在于，所述至少一个驱动适配插件的数量小于或等于所述控制器的连接限制数量。
  25. 如权利要求21-24任一项所述的分组管理器，其特征在于，所述至少一个驱动适配插件的归属地与所述控制器的归属地相同。
  26. 如权利要求21-25任一项所述的分组管理器，其特征在于，所述处理单元，还用于：
    在所述生成单元生成所述控制器的信息与驱动适配插件组的对应关系后，获取所述至少一个驱动适配插件的运行状态。
PCT/CN2017/080289 2016-04-29 2017-04-12 一种请求消息传输方法及装置 WO2017185992A1 (zh)

Priority Applications (3)

Application Number Priority Date Filing Date Title
EP17788644.7A EP3402123B1 (en) 2016-04-29 2017-04-12 Method and apparatus for transmitting request message
EP20165801.0A EP3737039B1 (en) 2016-04-29 2017-04-12 Method for transmitting request message and apparatus
US16/102,625 US10884880B2 (en) 2016-04-29 2018-08-13 Method for transmitting request message and apparatus

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201610289644.6A CN107332814B (zh) 2016-04-29 2016-04-29 一种请求消息传输方法及装置
CN201610289644.6 2016-04-29

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/102,625 Continuation US10884880B2 (en) 2016-04-29 2018-08-13 Method for transmitting request message and apparatus

Publications (1)

Publication Number Publication Date
WO2017185992A1 true WO2017185992A1 (zh) 2017-11-02

Family

ID=60161860

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/080289 WO2017185992A1 (zh) 2016-04-29 2017-04-12 一种请求消息传输方法及装置

Country Status (4)

Country Link
US (1) US10884880B2 (zh)
EP (2) EP3402123B1 (zh)
CN (1) CN107332814B (zh)
WO (1) WO2017185992A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2019123093A1 (en) * 2017-12-21 2019-06-27 Telefonaktiebolaget Lm Ericsson (Publ) Oss dispatcher for policy-based customer request management
CN114466070A (zh) * 2022-01-20 2022-05-10 精伦电子股份有限公司 中间件***、服务请求处理方法、电子设备及存储介质

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109818762B (zh) * 2017-11-20 2022-03-08 中国电信股份有限公司 用于实现sdn控制器自动注册的方法、适配器和***
CN109962788B (zh) * 2017-12-14 2022-03-29 中国电信股份有限公司 多控制器调度方法、装置和***及计算机可读存储介质
US10901823B2 (en) * 2018-12-20 2021-01-26 Accenture Global Solutions Limited System and method for load balancing in computing systems
CN109918147B (zh) * 2019-02-20 2022-03-25 杭州迪普科技股份有限公司 OpenStack下驱动的扩展方法、装置、电子设备

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6138011A (en) * 1999-10-15 2000-10-24 Motorola, Inc. Method and apparatus for providing dispatch service to an existing telephone network
CN101499995A (zh) * 2008-01-29 2009-08-05 华为技术有限公司 一种业务调度的方法及用于业务调度的***、装置
CN101631287A (zh) * 2009-07-31 2010-01-20 华为技术有限公司 一种请求消息处理***、方法及装置和一种聚合代理
US20120023245A1 (en) * 2009-03-24 2012-01-26 France Telecom Method and device for processing a piece of information indicative of a desire to be involved in at least one user application session
CN102891806A (zh) * 2011-07-21 2013-01-23 中兴通讯股份有限公司 一种对使用受限资源的批量操作的调度方法和装置

Family Cites Families (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5280610A (en) * 1990-08-14 1994-01-18 Digital Equipment Corporation Methods and apparatus for implementing data bases to provide object-oriented invocation of applications
US5265252A (en) * 1991-03-26 1993-11-23 International Business Machines Corporation Device driver system having generic operating system interface
US5329619A (en) * 1992-10-30 1994-07-12 Software Ag Cooperative processing interface and communication broker for heterogeneous computing environments
US5822585A (en) * 1995-02-21 1998-10-13 Compuware Corporation System and method for cooperative processing using object-oriented framework
US6026404A (en) 1997-02-03 2000-02-15 Oracle Corporation Method and system for executing and operation in a distributed environment
US6098093A (en) * 1998-03-19 2000-08-01 International Business Machines Corp. Maintaining sessions in a clustered server environment
US6973480B2 (en) * 2002-09-26 2005-12-06 Sun Microsystems, Inc. Mechanism for implementing server-side pluglets
US20070240134A1 (en) * 2006-02-28 2007-10-11 Joydeep Buragohain Software packaging model supporting multiple entity types
US9106515B2 (en) * 2012-10-22 2015-08-11 Futurewei Technologies, Inc. System and apparatus of a software-service-defined-network (SSDN)
US9912521B2 (en) * 2013-03-13 2018-03-06 Dell Products L.P. Systems and methods for managing connections in an orchestrated network
CN105515844A (zh) * 2015-12-01 2016-04-20 国家电网公司 一种提高软件定义网络可靠性的***
US9575779B1 (en) * 2016-02-26 2017-02-21 Epro Gmbh Isolated communication structure for machine instruments

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6138011A (en) * 1999-10-15 2000-10-24 Motorola, Inc. Method and apparatus for providing dispatch service to an existing telephone network
CN101499995A (zh) * 2008-01-29 2009-08-05 华为技术有限公司 一种业务调度的方法及用于业务调度的***、装置
US20120023245A1 (en) * 2009-03-24 2012-01-26 France Telecom Method and device for processing a piece of information indicative of a desire to be involved in at least one user application session
CN101631287A (zh) * 2009-07-31 2010-01-20 华为技术有限公司 一种请求消息处理***、方法及装置和一种聚合代理
CN102891806A (zh) * 2011-07-21 2013-01-23 中兴通讯股份有限公司 一种对使用受限资源的批量操作的调度方法和装置

Non-Patent Citations (1)

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

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2019123093A1 (en) * 2017-12-21 2019-06-27 Telefonaktiebolaget Lm Ericsson (Publ) Oss dispatcher for policy-based customer request management
CN114466070A (zh) * 2022-01-20 2022-05-10 精伦电子股份有限公司 中间件***、服务请求处理方法、电子设备及存储介质

Also Published As

Publication number Publication date
US10884880B2 (en) 2021-01-05
EP3737039B1 (en) 2021-10-27
US20180349236A1 (en) 2018-12-06
EP3737039A1 (en) 2020-11-11
EP3402123A4 (en) 2019-02-20
EP3402123B1 (en) 2020-07-22
CN107332814B (zh) 2021-01-01
CN107332814A (zh) 2017-11-07
EP3402123A1 (en) 2018-11-14

Similar Documents

Publication Publication Date Title
WO2017185992A1 (zh) 一种请求消息传输方法及装置
US9999030B2 (en) Resource provisioning method
US10698717B2 (en) Accelerator virtualization method and apparatus, and centralized resource manager
EP3261300B1 (en) Method and device for establishing link between virtual network functions
US9389903B2 (en) Method, system and apparatus for creating virtual machine
US9201644B2 (en) Distributed update service
WO2019184164A1 (zh) 自动部署Kubernetes从节点的方法、装置、终端设备及可读存储介质
RU2683630C2 (ru) Способ обновления дескриптора сетевой службы nsd и устройство
CN107800743B (zh) 云桌面***、云管理***和相关设备
US11240745B2 (en) Network slice instance processing method and apparatus, and system
WO2014169870A1 (zh) 虚拟网元自动装载及虚拟机ip地址获取的方法与***、存储介质
CN111880902A (zh) 一种pod创建方法、装置、设备及可读存储介质
WO2017166136A1 (zh) 一种vnf的资源分配方法及装置
KR102022441B1 (ko) 하드웨어 가속 방법 및 관련 장치
WO2018218977A1 (zh) 一种编排软件定义网络的方法及sdn控制器
WO2017054129A1 (zh) 一种网络功能虚拟化资源处理方法及虚拟网络功能管理器
US9342291B1 (en) Distributed update service
EP4068725A1 (en) Load balancing method and related device
CN108028806A (zh) 网络功能虚拟化nfv网络中分配虚拟资源的方法和装置
CN109067573B (zh) 一种流量调度方法及装置
US10951732B2 (en) Service processing method and device
US20180013860A1 (en) Method and apparatus for determining to-be-uploaded nsd
CN111045778B (zh) 一种虚拟机的创建方法、装置、服务器及存储介质
WO2013097237A1 (zh) 一种部署应用进程的方法、设备和***
CN113900791A (zh) 一种作业处理方法以及相关设备

Legal Events

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

Ref document number: 2017788644

Country of ref document: EP

ENP Entry into the national phase

Ref document number: 2017788644

Country of ref document: EP

Effective date: 20180809

NENP Non-entry into the national phase

Ref country code: DE