Integration of Iot technologies into the Smart Grid

Download 2,35 Mb. Pdf ko'rish
bet	16/21
Sana	13.05.2024
Hajmi	2,35 Mb.
	#230078

1 ... 13 14 15 16 17 18 19 20 21

Bog'liq
sensors-22-02475-v2

Figure 7. Example of the JSON frame containing the data type description of the LD belonging to the IED “BCU1M19”. Figure 7.

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 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 7.
Example of the JSON frame containing the data type description of the LD belonging to the
IED “BCU1M19”.
3.
getAllLogicalNodes: This allows the Web User to make a request for the publication of top-
ics relevant to the entire set of LNs contained in a LD. Considering the example of Figure
3
,
the Web User may realize the following request “BCU1M19/C1/getAllLogicalNodes”.
He will receive the topic “BCU1M19/C1/LNodes” from the Platform; through the sub-
scription to this topic, the Web User will have the details about the LNs, including the LN
whose identifier is “LBAYMMXU1”, as seen before, which can be used in the following
queries.
4.
getAllDataObjects: This allows the Web User to make a request for the publication
of details relevant to the entire set of Data Objects contained in a Logical Node.
Considering the example seen before, the Web User may perform a request specifying
the string “BCU1M19/C1/LBAYMMXU1/getAllDataObjects”. The topic he will
receive from the Platform will be “BCU1M19/C1/LBAYMMXU1/DObjects”; through
the subscription to this topic, the Web User will receive the details about the DOs
contained in the LN, including the DO with the attribute name = “A”.
5.
getAllSDO: This is used in the request aimed at acquiring information about the entire set
of Structured Data Objects and the relevant Data Attributes inside a Structured Data Object.
Considering the example shown by Figure
3
, let us assume that the Web User performs a
POST request specifying the string “BCU1M19/C1/LBAYMMXU1/A/getAllSDO”. The

Sensors
2022
,
22
, 2475
11 of 17
Web User will receive the topic “BCU1M19/C1/LBAYMMXU1/A/SDO”, and through
the relevant subscription, the Web User will receive the details (in JSON format) about
the Structured Data Objects and the relevant content, as shown by Figure
8
. As can be
seen, the JSON content reflects the data model structure shown by Figure
3
. As previously
noted, the JSON frame is received by the Web User according to a sequence of steps very
similar to those shown by Figure
5
.
6.
&: Through this operator, the Web User may request the publication of several
elements. For example, he may specify the string “ied1/Inverter/getAllLogicalNodes
& ied1/Battery/getAllLogicalNodes” in the POST request; in this way, the Web User
requires knowledge of the structure of the Logical Nodes contained in the Inverter
and Battery logical devices of the IED “ied1”.
Sensors

Download 2,35 Mb.

1 ... 13 14 15 16 17 18 19 20 21

Download 2,35 Mb.

Pdf ko'rish