10.46243/jst.2022.v7.i09.pp169-182-168 registered
Using Software Defined Networking to manage and control IEC61850-based systems
Resolves to https://www.jst.org.in/index.php/pub/article/view/880
Held by Longman Publishers (India) · prefix 10.46243 live · DOI address https://doi.org/10.46243/jst.2022.v7.i09.pp169-182-168
Registered 29 Sep 2026 via crossref · record version 2 · last change 29 Sep 2026, 11:59 PM · record sha256 85d24149e927a0f7…
Resolve ⬇ Record (JSON) ⬇ Kernel Metadata Declaration (XML) Compare with Crossref Cite (APA · BibTeX · RIS · CSL)
Also as schema.org JSON-LD · Turtle · RDF/XML · DataCite XML · Crossref UNIXREF · Crossref UNIXSD — the formats of the DOI content-negotiation service, from this record (which carries what).
What the DOI identifies
JournalArticle — an article in a journal · Digital · Visual · en
Using Software Defined Networking to manage and control IEC61850-based systems (PrincipalTitle · en)
Published 2022-05-11
Part of Journal of Science & Technology · ISSN 2456-5660 · volume 7 · issue 9 · pages 169–182
Agents
- D Rajeev Naik D Rajeev Naik (author)
- Longman Publishers (publisher)
Identifiers DOI 10.46243/jst.2022.v7.i09.pp169-182-168
Abstract · en
Smart Grid makes use of Information and Communications Technology (ICT) infrastruc- tures for the management of the generation, transmission and consumption of electrical energy to increase the efficiency of remote control and automation systems. One of the most widely accepted standards for power system communication is IEC 61850, which defines services and protocols with different requirements that need to be fulfilled with traffic engineering techniques. In this paper, we discuss the implementation of a novel management framework to meet these requirements through control and monitoring tools that provide a global view of the network. With this purpose, we provide an overview of relevant Software Defined Networking (SDN) related approaches, and we describe an archi- tecture based on OpenFlow that establishes different types of flows according to their needs and the network status. We present the implementation of the architecture and evaluate its capabilities using the Mininet network emulator.
System metadata — ISO 26324:2025, Annex B · DOI Handbook 10.1
Each element by the standard's name (Annex B: reference elements, then administrative) and the Handbook's (in grey), read off the record above.
| Element | Value | In the record |
|---|---|---|
| DOI Name DOI name | 10.46243/jst.2022.v7.i09.pp169-182-168 | doi |
| Referent Type referentType | Creation | referent |
| Referent Sub-Type referentSubType | JournalArticle — an article in a journal | type |
| Referent Name(s) referentName(s) | Using Software Defined Networking to manage and control IEC61850-based systems (PrincipalTitle, en) | titles |
| Basic Metadata basicMetadata | author: D Rajeev Naik D Rajeev Naik publisher: Longman Publishers published: 2022-05-11 part of: Journal of Science & Technology · ISSN 2456-5660 · vol. 7 · no. 9 · pp. 169–182 language: en form: Digital · Visual · Language | agents, dates, container, language, structural_type, modes, characters |
| Referent Identifier(s) alternateIdentifier(s) | none besides the DOI | identifiers, relations (IsSameAs) |
| Registration Authority registrationAuthorityCode | Crossref — issued by Crossref (member 25296); held here as a copy | record.source_agency (our code, ra_doi_name, for names issued here once appointed) |
| Created Date issueDate | 2024-02-16 | record.registered (when the DOI name was first registered) |
| relatedIdentifiers | none needed — the descriptive metadata is in this record | container, relations (only where the descriptive metadata lives at another identifier) |
complete Every System Metadata element is here, with the basic metadata a journal article needs.
The System Metadata Declaration (JSON) · the Kernel Metadata Declaration (XML) · what each sub-type needs
Cited by — in this registry
No record held in this registry cites this DOI.
Counts only records held in this registry; a citation from a work held elsewhere is not seen here. The list as JSON
References with DOIs
The record lists 3 references; 2 carry a DOI.
| # | Reference | DOI | Held here |
|---|---|---|---|
| 1 | ref1 Li F, Qiao W, Sun H, Wan H, Wang J, Xia Y, et al. Smart transmission grid: vision and framework. IEEE Trans Smart Grid 2010;1(2):168–77. http:// dx.doi.org/10.1109/TSG.2010.2053726 | 10.1109/tsg.2010.2053726 | not held here |
| 2 | ref2 Open Networking Foundation (ONF). Software defined networking: the new norm for networks. Technical report; 2012. IEC TC57. Communication networks and systems for power utility au… | 10.3403/03062344 | not held here |
Relations
The record states no relation, and no record held here states one with this DOI.
Funding
The record names no funder.
Each funder's page lists every work held here that names it. ROR IDs open at ror.org; Funder Registry IDs resolve at doi.org.
History — the ledger
Every change to this DOI, in order, as it was recorded. Entries are only ever added, never changed or removed.
| # | When | What | By | Changes |
|---|---|---|---|---|
| 1 | 29 Sep 2026, 10:00 PM | register registered at Crossref; record read from api.crossref.org | Administrator (admin) | 60 fields set · sha256 4052e243aa27… |
| 2 | 29 Sep 2026, 11:59 PM | update record re-read from api.crossref.org | Administrator (admin) | abstract.value: container.titles.0.value: |
Machine-readable: the history as JSON, with the full record after each change.
Changes made at Crossref through DOI Doctor
Every deposit Smart Scholars' DOI Doctor made for this DOI, oldest first, with Crossref's own answer. Each fingerprint is the SHA-256 of its entry and of the fingerprint before it, so a change to any earlier entry changes every fingerprint after it.
| When | What changed | Crossref | Fingerprint |
|---|---|---|---|
| 07 Oct 2026, 07:37 | Metadata completed abstract (147 words) · licence | ● accepted by Crossref | 85cd5f463acd… |
| 07 Oct 2026, 08:49 | Read back: Crossref's record shows it | ● confirmed | f2a711422192… |
2 entries · the last fingerprint f2a7114221924c2192ee88815db48a9933cb2099d81b71bca6231647197a4506 · the history as JSON, each entry with the fingerprint before it, to check them yourself.



