2014
DOI: 10.3390/en7095953
|View full text |Cite
|
Sign up to set email alerts
|

A Semantic Middleware Architecture Focused on Data and Heterogeneity Management within the Smart Grid

Abstract: Abstract:There is an increasing tendency of turning the current power grid, essentially unaware of variations in electricity demand and scattered energy sources, into something capable of bringing a degree of intelligence by using tools strongly related to information and communication technologies, thus turning into the so-called Smart Grid. In fact, it could be considered that the Smart Grid is an extensive smart system that spreads throughout any area where power is required, providing a significant optimiz… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
16
0

Year Published

2015
2015
2023
2023

Publication Types

Select...
4
1
1

Relationship

0
6

Authors

Journals

citations
Cited by 18 publications
(16 citation statements)
references
References 23 publications
0
16
0
Order By: Relevance
“…If an open source Enterprise Service Bus is used, though, development can be eased, as in the end the software packages will be mutually understandable in different parts of the distributed systems, as long as the same kind of ESB is used (sometimes, using a slightly different kind of ESB in different sides of the system will still be possible if they have a common ground. For instance, it is shown in [141] that an constrained Apache ServiceMix ESB can work in a seamless way with a JBosslike ESB). 5.…”
Section: Open Issues and Challengesmentioning
confidence: 99%
See 4 more Smart Citations
“…If an open source Enterprise Service Bus is used, though, development can be eased, as in the end the software packages will be mutually understandable in different parts of the distributed systems, as long as the same kind of ESB is used (sometimes, using a slightly different kind of ESB in different sides of the system will still be possible if they have a common ground. For instance, it is shown in [141] that an constrained Apache ServiceMix ESB can work in a seamless way with a JBosslike ESB). 5.…”
Section: Open Issues and Challengesmentioning
confidence: 99%
“…The original idea was to move those interfaces to other components that would have received a different name, but due to the fact that the functionality was already been offered in that component, they were left as URIs accessible from the support component. The finished middleware architecture conceived from e-GOTHAM has been summarized in [141]. After those tags, the variable part of the URI is added: the service name represents the service that is requested, the service identifier is the unique number that the device it belongs to was given during the registration process and the input is a parameter that may be required for the service data delivery; this last parameter is optional, as it may not be needed by the hardware device that will receive the request (for example, if real-time current is requested to a particular device with an identifier there is no need to specify other parameters, but if a device is requested to take an action, such as turning on or off a load, it might need so).…”
Section: Figure 878 Web Service Dependencies Locationmentioning
confidence: 99%
See 3 more Smart Citations