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)
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
An Efficient Single Instance Scheme With User Authentication To Cloud Data (PrincipalTitle · en)
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 · en
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
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 10 references; 9 carry a DOI.
| # | Reference | DOI | Held here |
|---|---|---|---|
| 1 | ref1 J. Stanek, A. Sorniotti, E. Androulaki, and L. Kencl, “A secure data duplication scheme for cloud storage,” in Financial Cryptography and Data Security-18th International Conferen… | 10.1007/978-3-662-45472-5_8 | not held here |
| 3 | ref3 M. Bellare, S. Keelveedhi, and T. Ristenpart, “Message-locked encryption and secure duplication,” in Advances in Cryptology-EUROCRYPT 2013, 32nd Annual International Conference on… | 10.1007/978-3-642-38348-9_18 | not held here |
| 4 | ref4 Proceedings, 2013, pp. 296–312.X. Yang, R. Lu, K.-K. R. Choo, F. Yin, and X. Tang, “Achieving efficient and privacy-preserving cross-domain big data duplication in cloud,” IEEE Tr… | 10.1109/tbdata.2017.2721444 | not held here |
| 5 | ref5 M. W. Storer, K. M. Greenan, D. D. E. Long, and E. L. Miller, “Secure data duplication,” in Proceedings of the 2008 ACM Workshop on Storage Security and Survivability, StorageSS 2… | 10.1145/1456469.1456471 | not held here |
| 6 | ref6 X. Yang, R. Lu, K. K. R. Choo, F. Yin and X. Tang, “Achieving Efficient and Privacy-Preserving Cross-Domain Big Data Deduplication in Cloud,” in IEEE Transactions on Big Data, vol… | 10.1109/tbdata.2017.2721444 | not held here |
| 7 | ref7 Wang, Z., Gao, W., Yang, M. et al. Enabling Secure Data sharing with data deduplication and sensitive information hiding in cloud-assisted Electronic Medical Systems. Cluster Comp… | 10.1007/s10586-022-03785-y | not held here |
| 8 | ref8 Liang, X., Yan, Z., Chen, X., Yang, L. T., Lou, W., & Hou, T. (2019). Game Theoretical Analysis on Encrypted Cloud Data Deduplication. IEEE Transactions on Industrial Informatics,… | 10.1109/tii.2019.2920402 | not held here |
| 9 | ref9 Youngjoo Shin, Junbeom Hur, Dongyoung Koo, Joobeom Yun, “Toward Serverless and Efficient Encrypted Deduplication in Mobile Cloud Computing Environments”, Security and Communicatio… | 10.1155/2020/3046595 | not held here |
| 10 | ref10 DING, Wenxiu; YAN, Zheng; and DENG, Robert H.. Secure encrypted data deduplication with ownership proof and user revocation. (2017). Algorithms and architectures for parallel proc… | 10.1007/978-3-319-65482-9_20 | 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) | 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.
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 (276 words) · licence | ● accepted by Crossref | db7a0cc3c41d… |
| 07 Oct 2026, 08:23 | Read back: Crossref's record shows it | ● confirmed | 8b6e46ac1e30… |
2 entries · the last fingerprint 8b6e46ac1e30ad490b9f74ec173034e2e8f9017632a74301477b30d202a4e94f · the history as JSON, each entry with the fingerprint before it, to check them yourself.



