10.46243/jst.2023.v8.i07.pp193-197 registered
A Protection System For Securing Multimedia Content In The Cloud
Resolves to https://www.jst.org.in/index.php/pub/article/view/779
Held by Longman Publishers (India) · prefix 10.46243 live · DOI address https://doi.org/10.46243/jst.2023.v8.i07.pp193-197
Registered 29 Sep 2026 via crossref · record version 2 · last change 29 Sep 2026, 11:59 PM · record sha256 dc6d133bc851492b…
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
A Protection System For Securing Multimedia Content In The Cloud (PrincipalTitle)
Published 2023-08-07
Part of Journal of Science & Technology · ISSN 2456-5660 · volume 8 · issue 7 · pages 193–197
Agents
- Venkata Sivaram Kumpati Venkata Sivaram Kumpati (author)
- Longman Publishers (publisher)
Identifiers DOI 10.46243/jst.2023.v8.i07.pp193-197
Abstract
Every day, a vast amount of multimedia content is generated and shared on the internet. Unfortunately, it has become all too easy to duplicate copyrighted materials. To address this issue, in this work to introduces an innovative system for safeguarding multimedia content on cloud infrastructures. When these duplicated multimedia materials are illicitly distributed online, Content creators suffer significant revenue losses. Detecting these unauthorized copies of multimedia content is a challenging task. This paper presents a pioneering system designed to protect various types of multimedia content, including 2-D/3-D videos, audios, images, and more. Built upon cloud infrastructure, this system offers rapid access to computing hardware and software resources. Its key components involve generating signatures for 3-D videos and utilizing a distributed index to match multimedia object
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.i07.pp193-197 | doi |
| Referent Type referentType | Creation | referent |
| Referent Sub-Type referentSubType | JournalArticle — an article in a journal | type |
| Referent Name(s) referentName(s) | A Protection System For Securing Multimedia Content In The Cloud (PrincipalTitle, en) | titles |
| Basic Metadata basicMetadata | author: Venkata Sivaram Kumpati Venkata Sivaram Kumpati publisher: Longman Publishers published: 2023-08-07 part of: Journal of Science & Technology · ISSN 2456-5660 · vol. 8 · no. 7 · pp. 193–197 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) | 68 fields set · sha256 676aa0102b1b… |
| 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.
