Figure 6 - Integration of Iot technologies into the Smart Grid

|
Integration of Iot technologies into the Smart GridBog'liq sensors-22-02475-v2Figure 6.
Example of a JSON frame containing the data type description of the IED maintained by
the IEC 61850 Server.
2.
getAllLogicalDevices: This operator allows the Web User to make a request for the
publication of the data structure relevant to the entire set of LDs contained in a specific
IED. Again considering the data model shown by Figure 3, the Web User may specify
the string “BCU1M19/getAllLogicalDevices” in the POST request made to the plat-
form. The topic he will receive from the Platform will be “BCU1M19/LDevices”;
through the subscription to this topic. The JSON frame shown by Figure 7 will be
received, with the description of the LDs contained in the IED. Again, the publication
of this frame occurs according to the same sequence of steps shown by Figure 5. This
allows the Web User to discover the value(s) of the attribute name(s) of the LDs in-
cluded in an IED. This(these) value(s) will be used in all of the following queries to
explore the data model below each LD.
Figure 7.
Example of the JSON frame containing the data type description of the LD belonging to
the IED “BCU1M19”.
Figure 6.
Example of a JSON frame containing the data type description of the IED maintained by
the IEC 61850 Server.
2.
getAllLogicalDevices: This operator allows the Web User to make a request for the
publication of the data structure relevant to the entire set of LDs contained in a
specific IED. Again considering the data model shown by Figure
3
, the Web User may
specify the string “BCU1M19/getAllLogicalDevices” in the POST request made to the
platform. The topic he will receive from the Platform will be “BCU1M19/LDevices”;
through the subscription to this topic. The JSON frame shown by Figure
7
will be
received, with the description of the LDs contained in the IED. Again, the publication
of this frame occurs according to the same sequence of steps shown by Figure
5
.
This allows the Web User to discover the value(s) of the attribute name(s) of the LDs
included in an IED. This(these) value(s) will be used in all of the following queries to
explore the data model below each LD.
Sensors
2022
,
22
, x FOR PEER REVIEW
10 of 18
If the Web User has the need to discover the full or partial structure of the hierarchical
data model starting from a specific element (e.g., the IED), he will perform several POST
requests in order to explore the entire data model, starting from the chosen starting ele-
ment of the data model, until the requested data types are found. In order to achieve this,
a particular syntax was defined to be used in these POST requests. This syntax is based on
the same rules described in Section 4.1 for the definition of the name of the data type
identifier; moreover, the syntax contains particular operators aimed to make the explora-
tion of the data model easier.
The following operators were defined to enable the Web User to explore the hierar-
chical IEC 61850 data model. This is not an exhaustive list, as only the most important
operators are described:
1.
getAllIEDs: If the Web User specifies this operator in his request, it will receive a topic
named “IEDs”, whose subscription to the proper Broker enables a JSON description
of the IEDs maintained by the IEC 61850 Server. Considering the data model shown
by Figure 3, the JSON frame shown by Figure 6 will be received through the subscrip-
tion to this topic. Publication of this frame occurs as shown by Figure 5. In this way,
the Web User discovers the value of the attribute name of the IED. This value will be
used in all the following queries in order to explore the content of the data model
below the IED elements.
|
| |