Method for transmitting request message and apparatus

1. A method for transmitting a service request message, the method comprising:

receiving, by a dispatcher a service request message, and obtaining information about a first controller from the service request message;

determining, by the dispatcher, a first driver adaptation plug-in group from a data structure indicating a correspondence between information about multiple controllers and a driver adaptation plug-in group, based on the information about the first controller, the first driver adaptation plug-in group having at least one driver adaptation plug-in connected to the first controller;

determining, by the dispatcher, from the at least one driver adaptation plug-in connected to the first controller, at least one to-be-selected driver adaptation plug-in having a running status indicated as normal; and

sending, by the dispatcher, the service request message to the first controller by using one of the at least one to-be-selected driver adaptation plug-in.

2. The method according to claim 1 , wherein the information about the first controller is a route distinguisher that can uniquely identifies the first controller.

3. The method according to claim 1 , wherein each driver adaptation plug-in comprised in the first driver adaptation plug-in group has a same type.

4. The method according to claim 1 , wherein:

the service request message further comprises a first type of a driver adaptation plug-in;

before determining, by the dispatcher, from the at least one driver adaptation plug-in connected to the first controller, at least one to-be-selected driver adaptation plug-in, the method further comprises:

obtaining, by the dispatcher, the first type comprised in the request message; and

determining, by the dispatcher, from the at least one driver adaptation plug-in connected to the first controller, at least one to-be-selected driver adaptation plug-in comprises:

determining, by the dispatcher, from the at least one driver adaptation plug-in, the at least one to-be-selected driver adaptation plug-in whose type is the same as the first type and whose running status is normal.

5. The method according to claim 1 , wherein in the correspondence between information about the multiple controllers and the driver adaptation plug-in group, each of the multiple controllers corresponding to the first driver adaptation plug-in group has a same limited connection quantity, and a quantity of driver adaptation plug-ins comprised in the first driver adaptation plug-in group is less than or equal to the limited connection quantity of each controller corresponding to the first driver adaptation plug-in group.

6. The method according to claim 1 , wherein in the correspondence between information about the multiple controllers and the driver adaptation plug-in group, a home location of each of the multiple controllers corresponding to the first driver adaptation plug-in group is the same as a home location of each driver adaptation plug-in comprised in the first driver adaptation plug-in group.

7. The method according to claim 1 , wherein when a quantity of the at least one to-be-selected driver adaptation plug-in is greater than 1, sending, by the dispatcher, the service request message to the first controller by using one of the at least one to-be-selected driver adaptation plug-in comprises:

determining, by the dispatcher, a target driver adaptation plug-in by performing load balancing processing on the multiple to-be-selected driver adaptation plug-ins, wherein the target driver adaptation plug-in is one of the multiple to-be-selected driver adaptation plug-ins; and

sending, by the dispatcher, the service request message to the first controller by using the target driver adaptation plug-in.

8. A method for generating a correspondence between information about a controller and a driver adaptation plug-in group, the method comprising:

obtaining, by a group manager, information about a controller;

determining, by the group manager, from multiple 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; and

generating, by the group manager, a data structure indicating a correspondence between the information about the controller and a driver adaptation plug-in group, wherein the driver adaptation plug-in group comprises the at least one driver adaptation plug-in.

9. The method according to claim 8 , wherein the information about the controller is a route distinguisher that uniquely identifies the first controller.

10. The method according to claim 8 , wherein determining, by the group manager, in multiple driver adaptation plug-ins, at least one driver adaptation plug-in corresponding to the controller comprises:

obtaining, by the group manager, a type of each driver adaptation plug-in of the multiple driver adaptation plug-ins; and

determining, by the group manager, from the multiple driver adaptation plug-ins, the at least one driver adaptation plug-in having a same type.

11. The method according to claim 8 , wherein a quantity of the at least one driver adaptation plug-in is less than or equal to a limited connection quantity of the controller.

12. The method according to claim 8 , wherein a home location of the at least one driver adaptation plug-in is the same as a home location of the controller.

13. The method according to claim 8 , wherein after generating, by the group manager, the correspondence between the information about the controller and the driver adaptation plug-in group, the method further comprises:

obtaining, by the group manager, a running status of the at least one driver adaptation plug-in.

14. A dispatcher, comprising:

a memory for storing executable program code;

a communications interface; and

at least one processor connected to the memory and the communications interface, wherein the executable program code, when executed by the at least one processor, causes the dispatcher to:

receive a service request message,

obtain information about a first controller from the service request message,

determine a first driver adaptation plug-in group from a data structure indicating a correspondence between information about multiple controllers and a driver adaptation plug-in group, based on the information about the first controller, the first driver adaptation plug-in group having at least one driver adaptation plug-in connected to the first controller, and

determine, from the at least one driver adaptation plug-in connected to the first controller, at least one to-be-selected driver adaptation plug-in having a running status indicated as normal; and

send the service request message to the first controller by using one of the at least one to-be-selected driver adaptation plug-in.

15. The dispatcher according to claim 14 , wherein the information about the first controller is a route distinguisher that uniquely identifies the first controller.

16. The dispatcher according to claim 14 , wherein each driver adaptation plug-in comprised in the first driver adaptation plug-in group has a same type.

17. The dispatcher according to claim 14 , wherein:

the service request message further comprises a first type of a driver adaptation plug-in; and

wherein the executable program code, when executed by the at least one processor, causes the dispatcher to:

before determining, in the at least one driver adaptation plug-in connected to the first controller, the at least one to-be-selected driver adaptation plug-in, obtain the first type comprised in the service request message, and

when determining, in the at least one driver adaptation plug-in connected to the first controller, the at least one to-be-selected driver adaptation plug-in, determine, in the at least one driver adaptation plug-in, the at least one to-be-selected driver adaptation plug-in whose type is the same as the first type and whose running status is normal.

18. The dispatcher according to claim 14 , wherein in the correspondence between information about the multiple controllers and the driver adaptation plug-in group, each of the multiple controllers corresponding to the first driver adaptation plug-in group has a same limited connection quantity, and a quantity of driver adaptation plug-ins comprised in the first driver adaptation plug-in group is less than or equal to the limited connection quantity of each controller corresponding to the first driver adaptation plug-in group.

19. The dispatcher according to claim 14 , wherein in the correspondence between information about the multiple controllers and the driver adaptation plug-in group, a home location of each of the multiple controllers corresponding to the first driver adaptation plug-in group is the same as a home location of each driver adaptation plug-in comprised in the first driver adaptation plug-in group.

20. The dispatcher according to claim 14 , wherein when a quantity of the at least one to-be-selected driver adaptation plug-in is greater than 1, the executable program code, when executed by the at least one processor, causes the dispatcher to:

after determining, in the at least one driver adaptation plug-in connected to the first controller, the multiple to-be-selected driver adaptation plug-ins, and before sending the service request message to the first controller by using one of the at least one to-be-selected driver adaptation plug-in, determine a target driver adaptation plug-in by performing load balancing processing on the multiple to-be-selected driver adaptation plug-ins, wherein the target driver adaptation plug-in is one of the multiple to-be-selected driver adaptation plug-ins; and

send the service request message to the first controller by using the target driver adaptation plug-in.