Service discovery in DEAPspace

Aspect Oriented Middleware for Internet of Things: A State-of-the Art Survey of Service Discovery Approaches

“…In the purely distributed method, participating nodes in the network stores store the registry locally and distributed querying service spans these registries to compile and present the required information to the user. The drawback of this method is the communication overhead involved in establishing a contact between peers and same is surmounted by adopting multicasting solution instead of broadcasting, [52]. Considering the scalability issues in multicasting domain [43], the solution in terms of minimizing the number of search hops is proposed [44] and the performance selective forwarding [44,45,46] in which the peers that are not able to solve the service discovery query uses the previous knowledge to forward the query to the correct peers.…”

Context-sensitive resource discovery

“…The Service Location Protocol (SLP) focuses on the protocol for automatic discovery [10], Czerwinski et al focus on expressiveness and security [8], and Castro et al deals with inter-domain service discovery [3]. DeapSpace [15] and Heidemann et al [11] propose approaches for discovery in ad-hoc sensor networks. None of these systems, however, has explicit support for context-sensitive names or subscriptions.…”

Outdoor Distributed Computing with Split Smart Messages

“…It uses unicast and broadcast as the communication mechanism and does not provide any service invocation mechanism. DEAPspace [43] proposed by IBM research, is aimed for single-hop ad hoc environments. Nodes cache service information and periodically broadcast it to share the information with each other.…”

“…IP is clearly insufficient; delay tolerant networking solutions [28], store-and-forward mechanisms, and opportunistic routing algorithms [34] are needed. Since the network is not pre-configured, protocols are needed for resource and service discovery [14,43,16,4]. For this to happen, new naming conventions are needed to uniquely identify resources and services, as IP addresses do not scale well to highly dynamic scenarios.…”