10.46243/jst.2022.v7.i02.pp332-340 registered
ESMVCC: AN ENHANCED SECURE REAL-TIME MULTIVERSION CONCURRENCY CONTROL ALGORITHM
Resolves to https://www.jst.org.in/index.php/pub/article/view/516
Held by Longman Publishers (India) · prefix 10.46243 live · DOI address https://doi.org/10.46243/jst.2022.v7.i02.pp332-340
Registered 29 Sep 2026 via crossref · record version 2 · last change 29 Sep 2026, 11:59 PM · record sha256 86fda50dd8266785…
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
ESMVCC: AN ENHANCED SECURE REAL-TIME MULTIVERSION CONCURRENCY CONTROL ALGORITHM (PrincipalTitle)
Published 2022-07-03
Part of Journal of Science & Technology · ISSN 2456-5660 · volume 7 · issue 2 · pages 332–340
Agents
- Ebrahim Abduljalil Ebrahim Abduljalil (author)
- Longman Publishers (publisher)
Identifiers DOI 10.46243/jst.2022.v7.i02.pp332-340
Abstract
In addition to ensuring database integrity, secure concurrency control techniques must be free of covert channels emerging from data conflicts between transactions. Transactions with higher access classes are mistreated by current secure concurrency control techniques. Because it solves the priority inversion problem more effectively. This paper introduces and evaluates a novel secure multiversion concurrency control technique. These experiments show that when comparing the proposed concurrency con trol algorithm to the SMVCC concurrency control protocol, the proposed algorithm outperforms the SMVCC protocol in terms of total average response time. ESMVCC has the lowest overall average transaction response time and the highest level of fairness among secure concurrency control protocols
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.i02.pp332-340 | doi |
| Referent Type referentType | Creation | referent |
| Referent Sub-Type referentSubType | JournalArticle — an article in a journal | type |
| Referent Name(s) referentName(s) | ESMVCC: AN ENHANCED SECURE REAL-TIME MULTIVERSION CONCURRENCY CONTROL ALGORITHM (PrincipalTitle, en) | titles |
| Basic Metadata basicMetadata | author: Ebrahim Abduljalil Ebrahim Abduljalil publisher: Longman Publishers published: 2022-07-03 part of: Journal of Science & Technology · ISSN 2456-5660 · vol. 7 · no. 2 · pp. 332–340 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) | 72 fields set · sha256 fbe30f37a631… |
| 2 | 29 Sep 2026, 11:59 PM | update record re-read from api.crossref.org | Administrator (admin) | agents.0.name.family: agents.0.name.given: container.titles.0.value: |
Machine-readable: the history as JSON, with the full record after each change.
