10.46243/jst.2022.v7.i04.pp60-87 registered
Hybrid Diagonal Transposition Cipher Model for Securing Data in Software Defined Networks
Resolves to https://www.jst.org.in/index.php/pub/article/view/640
Held by Longman Publishers (India) · prefix 10.46243 live · DOI address https://doi.org/10.46243/jst.2022.v7.i04.pp60-87
Registered 29 Sep 2026 via crossref · record version 2 · last change 29 Sep 2026, 11:59 PM · record sha256 eedd3836d573caa3…
Resolve ⬇ Record (JSON) ⬇ Kernel Metadata Declaration (XML) Compare with Crossref Cite (APA · BibTeX · RIS · CSL)
What the DOI identifies
JournalArticle — an article in a journal · Digital · Visual · en
Hybrid Diagonal Transposition Cipher Model for Securing Data in Software Defined Networks (PrincipalTitle)
Published 2022-06-27
Part of Journal of Science & Technology · ISSN 2456-5660 · volume 7 · issue 4 · pages 60–87
Agents
- P.Mohana Priya P.Mohana Priya (author)
- Longman Publishers (publisher)
Identifiers DOI 10.46243/jst.2022.v7.i04.pp60-87
Abstract
Data is an important asset for every organization and hence this article is proposed to secure data from common breaches in software defined network. In this article, hybrid cipher model is proposed to safeguard the communication of data transmitted among the layers in software defined networks. The logic of hybrid cipher model is incorporated in software defined controller which encrypts open flow request and response messages. Software Defined Network is adapted for implementing hybrid cipher model as the network provides customizable platform and act as a unmanned security featured software controller. The proposed Hybrid Diagonal Transposition algorithm is incorporated with software defined wireless sensing node for encrypting user’s data. Hence the unmanned security featured wireless sensing node is situation-aware, it detects malicious traffic flows and encrypts user’s data. Hybrid Diagonal Transposition algorithm prevents data breaches in Software Defined Networks. Results are interpreted for various network and sensor metrics such as routing hops, participating node temperature, battery voltage, humidity, lights, received packets per node, number of network hops, power consumption, radio duty cycle, temperature of sensors, beacon interval, network hops, routing metric and the same work will be extended in future for comparative results.
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.i04.pp60-87 | doi |
| Referent Type referentType | Creation | referent |
| Referent Sub-Type referentSubType | JournalArticle — an article in a journal | type |
| Referent Name(s) referentName(s) | Hybrid Diagonal Transposition Cipher Model for Securing Data in Software Defined Networks (PrincipalTitle, en) | titles |
| Basic Metadata basicMetadata | author: P.Mohana Priya P.Mohana Priya publisher: Longman Publishers published: 2022-06-27 part of: Journal of Science & Technology · ISSN 2456-5660 · vol. 7 · no. 4 · pp. 60–87 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
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) | 129 fields set · sha256 5ff0fd28b0e1… |
| 2 | 29 Sep 2026, 11:59 PM | update record re-read from api.crossref.org | Administrator (admin) | container.titles.0.value: |
Machine-readable: the history as JSON, with the full record after each change.
