Fig.2 shows the detailed working flow of robotic services in
the proposed system. Where, WSDL is used to define signature
of robotic services and robotic services are maintained by
UDDI server. A service is requested by wrapping the input arguments
into XML and sent over HTTP using SOAP to robotic
service interface. Robotic interface checks the authentication,
compatibility and availability of service and subsequently
passed to service agent, which in turn execute service. At the
end, the result is passed to the service requester via robotic
service interface. Robotic service handler contains the robotic
services like navigation, path planning, map building, object
recognition etc. It takes the help of map-reduce computing
cluster to process large amount of data. Services at robotic
service handler are independent and one can add or remove
service to it.
Map-reduce computing cluster uses map-reduce programming
model to process data. It implements two functions
namely map and reduce that takes input pair k1, v1 and
produces new pair of key/value pair k2, v2. All same key
values are sent to a single reduce function and reduce function
accept the vice versa and merges these values down to a
smaller value/output. Generally, data is split into 16-64 MB
blocks.