Pragmatic Sensory Data Semantics With Service-Oriented Computing

Pragmatic Sensory Data Semantics With Service-Oriented Computing

Robin Singh Bhadoria (Indian Institute of Technology Indore, Gwalior, India) and Narendra S. Chaudhari (Visvesvaraya National Institute of Technology, Nagpur, India)
Copyright: © 2019 |Pages: 15
DOI: 10.4018/JOEUC.2019040102
OnDemand PDF Download:
No Current Special Offers


The importance of an architectural semantic for service-oriented computing starts with the characteristics of software systems that has been recognized with sharing and the utilization of resources. However, an architectural characteristic for service-oriented based applications depends on interaction patterns that utilizes a data format in communication. These patterns also help in establishing communication between service components. The goal of service-oriented computing methodologies could be achieved by adopting a logical separation of services from the actual mechanism of resource assignment and allotment. This shows that how services are reliable as interaction patterns between service provider and requester. It generates the binding patterns between these two and establishes communication between them. This article discusses the mathematical-based semantic model that presents an architectural view for systems that follows a service-oriented computing methodology. It also briefs describes about different execution states and routes, which addresses the service specifications in service-oriented computing.
Article Preview

1. Introduction

Service-oriented computing is an emerging paradigm where services are platform-independent computational entities. These services could be published, delivered, executed and discarded based on the quality of service (QoS) requirement (Phillips, 2013). It also supports the distributed, interoperable, and integration of services on common and shared platform called enterprise service bus (ESB). This platform aims at developing a novel approach for extending the features of service-oriented architecture (SOA) that support combining the “off-the-shelf” component-based software engineering. “QoS” may refer to extending the meaning of functional as well as non-functional support to service properties, protocol and business logic. This is well explained with building template to quality assurance as discussed in thesis (Reinecke et al, 2010; Kyusakov et al., 2013). Quality assurance methods typically inferred the service execution patterns which helps in better understanding the actual need for service integration in legacy application like sensor network. Whereas fundamental theories and methodologies associated with data acquisition for sensor network need to address issues associated with service invocation. Communication could be strengthened by well-define ‘link’ between correspondent ‘node’. Here, ‘node’ could be client or just sensor node which actually rise request for services and communication between them is governed by a ‘link’. The service execution ensures the quality of data which is being exchanged between multiple nodes with help of desired protocol (Fiadeiro et al., 2012).

Figure 1.

Sensory data streaming over local and cloud server


The streaming of sensory data could be possible with both local as well as cloud server. Whenever, such data is stored at a repository through a local server, its access is limited with specific number of user. On the other hand, when such data is make available at cloud databases through global server, its access is vital and rapid through various distributed algorithms and techniques. This scenario is well depicted in Figure 1 in which sensory data is traffic through cloud infrastructure at global resources. This arrangement could be possible with different service modeling in SOA systems.

1.1. Service Modeling

The business conversation is important style in engagement of services between its clients. This could efficiently be organized through exchange of correlated messages (Myers et al., 2010; Klaus et al., 2015). For example, an insurance company client may request for status update to his/her insurance refund. This creates an ‘event’ that does the invocation and integration of multiple services. This service invocation could either commit the refund or cancel it on basis of certain predefined features. Such features are governed by service-oriented computing and it also models the service for which conversation is supported (Cámara et al., 2016). This concept can be conceived for sensory data acquisition in which following action is required to get an update:

  • Interaction must be based on exchanging information within the system for which typically event must be occurred. This may include requests, reply, commit, cancel or invoke for each interaction;

  • Interpretation must be done using predefined business patterns, usually defined in term of enterprise integration patterns (EIP). Such procedures enable the interaction between communicating party;

  • Execution must be governed by ‘state’ of service and there has to be predefined path or route which justifies the transition of event from one ‘state’ to another;

  • Invocation in business conversation must be done on ‘parity’ flag basis. This flag clears the interest of different ‘Node’ whether it want to interact with communicating other party.

Complete Article List

Search this Journal:
Volume 34: 1 Issue (2022): Forthcoming, Available for Pre-Order
Volume 33: 6 Issues (2021): 4 Released, 2 Forthcoming
Volume 32: 4 Issues (2020)
Volume 31: 4 Issues (2019)
Volume 30: 4 Issues (2018)
Volume 29: 4 Issues (2017)
Volume 28: 4 Issues (2016)
Volume 27: 4 Issues (2015)
Volume 26: 4 Issues (2014)
Volume 25: 4 Issues (2013)
Volume 24: 4 Issues (2012)
Volume 23: 4 Issues (2011)
Volume 22: 4 Issues (2010)
Volume 21: 4 Issues (2009)
Volume 20: 4 Issues (2008)
Volume 19: 4 Issues (2007)
Volume 18: 4 Issues (2006)
Volume 17: 4 Issues (2005)
Volume 16: 4 Issues (2004)
Volume 15: 4 Issues (2003)
Volume 14: 4 Issues (2002)
Volume 13: 4 Issues (2001)
Volume 12: 4 Issues (2000)
Volume 11: 4 Issues (1999)
Volume 10: 4 Issues (1998)
Volume 9: 4 Issues (1997)
Volume 8: 4 Issues (1996)
Volume 7: 4 Issues (1995)
Volume 6: 4 Issues (1994)
Volume 5: 4 Issues (1993)
Volume 4: 4 Issues (1992)
Volume 3: 4 Issues (1991)
Volume 2: 4 Issues (1990)
Volume 1: 3 Issues (1989)
View Complete Journal Contents Listing