notify the pos module on the api s that another channel needs to be created to optimize the channel resources when the channel is created and ready the ma switches from the old channel to the new one then for the particular case of an edge ma when a channel delivers an incoming message to the channel management module the first check is to verify whether the message protocol differs from the native message protocol if it does the channel management module will request the protocol translation engine 618 to convert the incoming messages to the native e g tervela u2122 message protocol when the message is converted it is handed off to the tervela u2122 messaging layer 610 otherwise in the case of a core ma when a channel handles an incoming message the message is handed off to the native tervela u2122 messaging layer assuming that all channels are using this native message protocol and therefore all messages already have the native message format as described earlier all messages that are routed in the publish subscribe network are received or sent on a particular channel see inside message transport layer 612 using these channels the ma communicates with all other physical components in the publish subscribe network these communication interfaces are represented in the diagrams where in fig8 a and 8 b the interface is shown for communications between the p amp m system and the ma in fig1 a and 10 b the interface is shown for communications between the ma and the ce caching engine and in fig1 a and 11 b the interface is shown for communications between the ma and the api there are times when these interfaces.