10.46243/jst.2023.v8.i06.pp140-145 registered
Secure Mobile Cloud Storage
Resolves to https://www.jst.org.in/index.php/pub/article/view/747
Held by Longman Publishers (India) · prefix 10.46243 live · DOI address https://doi.org/10.46243/jst.2023.v8.i06.pp140-145
Registered 29 Sep 2026 via crossref · record version 2 · last change 29 Sep 2026, 11:59 PM · record sha256 a749345aaf35deff…
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
Secure Mobile Cloud Storage (PrincipalTitle)
Published 2023-08-07
Part of Journal of Science & Technology · ISSN 2456-5660 · volume 8 · issue 7 · pages 140–145
Agents
- Bodasu Manisha Bodasu Manisha (author)
- Longman Publishers (publisher)
Identifiers DOI 10.46243/jst.2023.v8.i06.pp140-145
Abstract
Data may be stored on a cloud and accessible from anywhere using mobile devices thanks to mobile cloud storage (MCS). MCS services are provided for commercial use by sizable firms like Apple I Cloud, Dropbox, Microsoft One Drive, and Google Drive. Since customers may not fully trust clouds, data security may be achieved using encryption techniques. However, sensitive data, including location data, is frequently included in location-based apps. This exposed data can be used to deduce the client's behavior and encrypted data. For instance, 80% of search queries may be recognized by a searchable encryption system using a generic inference attack with access pattern leaking and little prior knowledge. The activity of the client can also be inferred via oblivious technologies, such as oblivious transfer and oblivious storage.This study presents a mobile cloud storage system that simultaneously safeguards data confidentiality and privacy while being effective, secure, and privacy-preserving. An oblivious selection and update (OSU) protocol built on onion additive homo morphic encryption with constant encryption layers serves as the underlying primitive. This dramatically lowers computation and transmission costs by enabling clients to covertly retrieve encrypted data items from the cloud and update them with new information. The suggested approach is more appropriate for MCS situations because it has beneficial characteristics such a fine-grained data structure, minimal client-side processing, and constant communication overhead. The "verification chunks" technique also confirms that the strategy is resistant to malicious cloud assaults. According to the comparison and assessment, the suggested plan is more effective than currently available oblivious storage options in terms of client .A valuable tool for distant storage, akin to cloud storage, is remote data integrity checking.
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.pp140-145 | doi |
| Referent Type referentType | Creation | referent |
| Referent Sub-Type referentSubType | JournalArticle — an article in a journal | type |
| Referent Name(s) referentName(s) | Secure Mobile Cloud Storage (PrincipalTitle, en) | titles |
| Basic Metadata basicMetadata | author: Bodasu Manisha Bodasu Manisha publisher: Longman Publishers published: 2023-08-07 part of: Journal of Science & Technology · ISSN 2456-5660 · vol. 8 · no. 7 · pp. 140–145 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) | 82 fields set · sha256 dad4e382b15c… |
| 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.
