Notice of Violation of IEEE Publication Principles: Evaluation of CORBA and Web Services in distributed applications

SMArc: A Proposal for a Smart, Semantic Middleware Architecture Focused on Smart City Energy Management

“…While all these checking and storing operations are being made, the request will be treated as well: after sending the data request to the Inference Engine subsystem, the request will be sent to the class that is used for input and output data (6) and the one that is used for data retrieval from the device (7). Responses (8,9) will be sent back to the service manager (10) and it will process them in a way that will be similar to the one used with requests. In this case, responses will be sent for storage (11) and notified for data inference (12).…”

“…At the same time, the request is sent to the suitable class that will deal with input/output operations (6) and, right afterwards, the needed requests are done (7). What is different in this case from the former one, where simple services were requested, is that not only several services requests are needed in order to gather all the data that the composed services need to be provided with but also one more operation must be performed in order to process the obtained parameters to compose the service (8). After this processing, the response will follow a way very similar to the one followed by a simple service request.…”

“…Thus, the action collector sends back the request as an action to the inference manager (5) that will check (6) and store the action (7) if it is a new triggered one. Meanwhile, the data request is satisfied as it is usually done: the request will be sent to the device class that is controlling input and output data (8) and the query is sent again to the device class bound to the device (9) which will send back the response (10) until it reaches the service manager (11) where it will be checked again (12). Another action is sent from the action collector as the response is obtained (13), checked (14), and stored (15) as it was in former cases.…”

“…As a result, the device will obtain the specific format that should be used to send the data to the ontology (6), which will be sent to a class that is part of the Ontology subsystem (7). As the format provided by the device is the expected one at the latter subsystem, sensing (8) and actuating (9) capabilities can be extracted and sent (10, 11) to a factory that will determine specific devices that can be invoked (12). Additionally, the International Journal of Distributed Sensor Networks services will be stored for future updates in case they have to be changed or removed (13).…”

“…Solutions like Remote Method Invocation or RMI, that is to say, a Java-based middleware architecture made up by three different layers (Stub/Skeleton, Remote Reference Layer, and Transport Layer) used to invoke a Java method on a remote machine [7] and Common Object Request Broker Architecture (CORBA), which can be regarded as a language for independent object buses that interact via a client-server architecture employing Object Requests Brokers [8], tend to fit in well with distributed systems that are deployed on regular equipment like personal computers, laptops, or even smartphones, for they have an abundant amount of computational and energetic resources. [9] or Bicen et al [10].…”