2012 Third International Workshop on Software Engineering for Sensor Network Applications (SESENA) 2012
DOI: 10.1109/sesena.2012.6225732
|View full text |Cite
|
Sign up to set email alerts
|

Building portable middleware services for heterogeneous cyber-physical systems

Abstract: Software development in wireless sensor networks has traditionally focused on stand-alone applications statically linked with the operating system code, and relying on fixed models for scheduling, synchronization, and resource allocation. Middleware services and network protocols, are usually considered to be part of the operating system. As the number of available WSN platforms and operating systems grows, and the emergence of cyber-physical systems results in the creation of networks of hetrogeneous devices … Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
4
0

Year Published

2017
2017
2024
2024

Publication Types

Select...
4
3
1

Relationship

0
8

Authors

Journals

citations
Cited by 8 publications
(4 citation statements)
references
References 9 publications
0
4
0
Order By: Relevance
“…It is important to note that our proposal from Figure 1, which claims to offer layered and component-based software architectures for hosting mediation, does not differ too much from the ideas of breaking a tight integration between software applications, middleware services and operating systems as it was prevalent in mid-2000 (Mechitov and Agha, 2012). The paper maybe uses old fashioned terminology, appropriate for the time when it was published, but this type of separation of concerns in modern software engineering is still the only way forward.…”
Section: Applications Of the Proposalmentioning
confidence: 98%
“…It is important to note that our proposal from Figure 1, which claims to offer layered and component-based software architectures for hosting mediation, does not differ too much from the ideas of breaking a tight integration between software applications, middleware services and operating systems as it was prevalent in mid-2000 (Mechitov and Agha, 2012). The paper maybe uses old fashioned terminology, appropriate for the time when it was published, but this type of separation of concerns in modern software engineering is still the only way forward.…”
Section: Applications Of the Proposalmentioning
confidence: 98%
“…Another topic of interest of the service based IoMT is the deployment of adequate middleware, which adds a level of abstraction to the control of devices by proposing a generic interface for the connected objects. Service oriented middleware architecture has been detailed, either using low level C structures [99] or higher level XML description targeted at objects integration to large scale IPv6 networks [100].…”
Section: Iomt Service Layer: An Unexplored Approachmentioning
confidence: 99%
“…The SOA consists of different components including the service provider, service registry, service customer, and message-based interaction protocol as shown in Figure 3 [15]. Moreover, SOA enables different services for Heterogeneous Cyber-Physical-Systems that can be selected and shared among various applications as proposed in [16]. …”
Section: Background and Conceptmentioning
confidence: 99%