ABSTRACT
This chapter describes in detail how to realise the GoCoMo middleware, and presents two prototypes, one for Android-based devices and the other for ns-3 platforms. The GoCoMo service composition process executes in the context of the GoCoMo middleware. Matchmaker is responsible for matching two entities and returning the matchmaking result to CtrlLogic. Matchmaking method can be syntactic or semantic depending on the domain of the operating environment. The GoCoMo middleware shares a provider's services in two ways: planning and advertising. In a planning process, a composition request, parsed by GMsgHelper, is firstly checked by CtrlLogic to find out whether a provider's local microservice satisfies the composition request. A guidepost is a networked element in a dynamic composition overlay network. A guidepost is associated with one GoCoMo composition process, caching information about candidate service composites. The GoCoMo middleware uses Guidepost Manager to oversee a guidepost's life-cycle.
