10.46243/jst.2023.v8.i06.pp152-157 registered
An Efficient Single Instance Scheme With User Authentication To Cloud Data
Resolves to https://www.jst.org.in/index.php/pub/article/view/752
Held by Longman Publishers (India) · prefix 10.46243 live · DOI address https://doi.org/10.46243/jst.2023.v8.i06.pp152-157
Registered 29 Sep 2026 via crossref · record version 2 · last change 29 Sep 2026, 11:59 PM · record sha256 b7334a6da580adce…
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
An Efficient Single Instance Scheme With User Authentication To Cloud Data (PrincipalTitle)
Published 2023-08-07
Part of Journal of Science & Technology · ISSN 2456-5660 · volume 8 · issue 7 · pages 152–157
Agents
- Boini Vandana Boini Vandana (author)
- Longman Publishers (publisher)
Identifiers DOI 10.46243/jst.2023.v8.i06.pp152-157
Abstract
Cloud Storage is a computer data storage method where digital data is stored on servers in off-site locations, managed by a third-party provider. This enables organizations to store, access, and maintain data without owning and operating their own data centers. Cloud storage is scalable, allowing organizations to expand or reduce their data footprint depending on their needs. Users upload data to servers via internet, which is saved on a virtual machine on a physical server. Cloud providers often spread data to multiple virtual machines in global data centers to maintain availability and redundancy. Google Cloud offers various scalable options for organizations to store their data in the cloud. The widespread use of cloud computing has made data sharing and storage more accessible, but concerns about data integrity, efficiency, and privacy remain. Duplication, a popular method of data compression, is used to reduce duplicate copies of data in cloud storage. However, data duplication also raises security and privacy concerns, as users' confidential data is vulnerable to attacks from insiders and outsiders. Traditional solutions for duplication, based on convergent encryption, provide confidentiality but do not maintain duplicate checks based on differential permissions. This paper proposes an approved data duplication plan that counts the number of users with differential privileges in the duplicate check.Users with differential privileges are added to the duplicate check, and files are encrypted with differential privilege keys to maintain stronger security. Users can only access files marked with matching privileges for copy checks. A third-party auditor can confirm file occurrence after duplication in the cloud, ensuring timely uploads. This paper offers advantages for both storage providers and users through duplication systems and auditing methods
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.2023.v8.i06.pp152-157 | doi |
| Referent Type referentType | Creation | referent |
| Referent Sub-Type referentSubType | JournalArticle — an article in a journal | type |
| Referent Name(s) referentName(s) | An Efficient Single Instance Scheme With User Authentication To Cloud Data (PrincipalTitle, en) | titles |
| Basic Metadata basicMetadata | author: Boini Vandana Boini Vandana publisher: Longman Publishers published: 2023-08-07 part of: Journal of Science & Technology · ISSN 2456-5660 · vol. 8 · no. 7 · pp. 152–157 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) | 81 fields set · sha256 c264530b72de… |
| 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.
