Yes, this sounds like a standard implementation of the Command Pattern. The pattern is described e.g. in the book Design Patterns by the "Gang of Four". If you have no hardcopy at hand, you can find it online e.g. on Wikipedia or Blackwasp.
Your CommandExecutor
/CommandDispatcher
seem to be Invoker
s in the Pattern terminology. How the Invoker consumes the Commands is an implementation detail, a FIFO queue is just one way. So there is no specific name for this. But you could use another Design Pattern for this, if it matches your needs, e.g. a scheduler with or without parallel execution of the commands (see also Active Object).
Hint:
If you take a look at the Pattern explanations, you will see that you have merged the Receiver
s and Command
s into one class, since your Commands know the business logic to execute (=sending bytes, process response, etc.). So you can improve your design if you put this business logic into specific Receiver
classes, which are used by the Commands. This way the Command Pattern is just a layer which uses the Receivers/business logic. This enables better testing of the business logic without taking care of the Commands as well as makes the Command Pattern exchangeable.