<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE article PUBLIC "-//NLM//DTD Journal Publishing DTD v2.3 20070202//EN" "journalpublishing.dtd">
<article xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" article-type="research-article" dtd-version="2.3" xml:lang="EN">
<front>
<journal-meta>
<journal-id journal-id-type="publisher-id">Front. Artif. Intell.</journal-id>
<journal-title>Frontiers in Artificial Intelligence</journal-title>
<abbrev-journal-title abbrev-type="pubmed">Front. Artif. Intell.</abbrev-journal-title>
<issn pub-type="epub">2624-8212</issn>
<publisher>
<publisher-name>Frontiers Media S.A.</publisher-name>
</publisher>
</journal-meta>
<article-meta>
<article-id pub-id-type="doi">10.3389/frai.2025.1655709</article-id>
<article-categories>
<subj-group subj-group-type="heading">
<subject>Artificial Intelligence</subject>
<subj-group>
<subject>Original Research</subject>
</subj-group>
</subj-group>
</article-categories>
<title-group>
<article-title>Decentralizing video copyright protection: a novel blockchain-enabled framework with performance evaluation</article-title>
</title-group>
<contrib-group>
<contrib contrib-type="author">
<name>
<surname>Madapati</surname>
<given-names>Sri Lakshmi</given-names>
</name>
<xref ref-type="aff" rid="aff1"><sup>1</sup></xref>
<uri xlink:href="https://loop.frontiersin.org/people/3109954/overview"/>
<role content-type="https://credit.niso.org/contributor-roles/conceptualization/"/>
<role content-type="https://credit.niso.org/contributor-roles/formal-analysis/"/>
<role content-type="https://credit.niso.org/contributor-roles/methodology/"/>
<role content-type="https://credit.niso.org/contributor-roles/software/"/>
<role content-type="https://credit.niso.org/contributor-roles/writing-original-draft/"/>
</contrib>
<contrib contrib-type="author" corresp="yes">
<name>
<surname>Pradhan</surname>
<given-names>Nihar Ranjan</given-names>
</name>
<xref ref-type="aff" rid="aff2"><sup>2</sup></xref>
<xref ref-type="corresp" rid="c001"><sup>&#x002A;</sup></xref>
<uri xlink:href="https://loop.frontiersin.org/people/3118246/overview"/>
<role content-type="https://credit.niso.org/contributor-roles/supervision/"/>
<role content-type="https://credit.niso.org/contributor-roles/validation/"/>
<role content-type="https://credit.niso.org/contributor-roles/visualization/"/>
<role content-type="https://credit.niso.org/contributor-roles/writing-review-editing/"/>
</contrib>
</contrib-group>
<aff id="aff1"><sup>1</sup><institution>School of Computer Science and Engineering (SCOPE), VIT-AP University</institution>, <addr-line>Amaravati, Andhra Pradesh</addr-line>, <country>India</country></aff>
<aff id="aff2"><sup>2</sup><institution>School of Computer Science and Engineering, VIT-AP University</institution>, <addr-line>Amaravati, Andhra Pradesh</addr-line>, <country>India</country></aff>
<author-notes>
<fn fn-type="edited-by" id="fn0001">
<p>Edited by: Shu Hu, Purdue University, United States</p>
</fn>
<fn fn-type="edited-by" id="fn0002">
<p>Reviewed by: Ranjeet Kumar Rout, National Institute of Technology, Srinagar, India</p>
<p>Hadeel Taher, University of Anbar, Iraq</p>
<p>Dongdong Huo, Chinese Academy of Sciences, China</p>
</fn>
<corresp id="c001">&#x002A;Correspondence: Nihar Ranjan Pradhan, <email>nihar.pradhan@vitap.ac.in</email></corresp>
</author-notes>
<pub-date pub-type="epub">
<day>18</day>
<month>08</month>
<year>2025</year>
</pub-date>
<pub-date pub-type="collection">
<year>2025</year>
</pub-date>
<volume>8</volume>
<elocation-id>1655709</elocation-id>
<history>
<date date-type="received">
<day>28</day>
<month>06</month>
<year>2025</year>
</date>
<date date-type="accepted">
<day>25</day>
<month>07</month>
<year>2025</year>
</date>
</history>
<permissions>
<copyright-statement>Copyright &#x00A9; 2025 Madapati and Pradhan.</copyright-statement>
<copyright-year>2025</copyright-year>
<copyright-holder>Madapati and Pradhan</copyright-holder>
<license xlink:href="http://creativecommons.org/licenses/by/4.0/">
<p>This is an open-access article distributed under the terms of the Creative Commons Attribution License (CC BY). The use, distribution or reproduction in other forums is permitted, provided the original author(s) and the copyright owner(s) are credited and that the original publication in this journal is cited, in accordance with accepted academic practice. No use, distribution or reproduction is permitted which does not comply with these terms.</p>
</license>
</permissions>
<abstract>
<sec>
<title>Introduction</title>
<p>Digital content, including images and videos, is increasingly ruling the online world, and so multimedia services form a part of this modern life. However, the digital resources face significant problems, especially regarding copyright infringement. In such an instance, any modification without authority infringes intellectual property rights.</p>
</sec>
<sec>
<title>Methods</title>
<p>Based on Inter Planetary File System (IPFS) and blockchain technology, a decentralized and distributed framework has been proposed in this study for dealing with insecurity over digital assets and openness of multimedia resources. In this respect, secure, transparent, and immutable transactions in regard to the transfer and ownership of creative works have been facilitated by the use of such a framework.</p>
</sec>
<sec>
<title>Results</title>
<p>This paper proposes novel decentralized and Blockchain enabled framework to address the problem of video copyright protection by employing solidity based smart contract in a Ethereum network, that allows the content creators to register their videos. The designed smart contract performs copyright checks and release copyright disputes by generating and comparing perceptual hash&#x2019;s (Phash) for original video and modified video.</p>
</sec>
<sec>
<title>Discussion</title>
<p>Phash techniques play a crucial role in multimedia content analysis, particularly in verifying the integrity and similarity of the video data under various transformations. Additionally, the framework generates Inter Planetary File System (IPFS) main values that signifies the ownership of the video content. Then it compars the phash values, IPFS and similarly score in public Blockchain environment i.e. Ethereum. The framework performance was measured by simulating the contracts of the Application Binary Interface (ABI), JSON file in the Hyperledger Caliper environment. This result shows the performance in the form of video registration, the measured latency was 5.02 seconds with a throughput of 409.87 seconds. For video verification the latency was 4.57 seconds with a throughput of 484.23 seconds.</p>
</sec>
</abstract>
<kwd-group>
<kwd>perceptual hashing</kwd>
<kwd>InterPlanetary File System</kwd>
<kwd>similarity analysis</kwd>
<kwd>video copyright protection</kwd>
<kwd>blockchain</kwd>
</kwd-group>
<counts>
<fig-count count="18"/>
<table-count count="4"/>
<equation-count count="0"/>
<ref-count count="17"/>
<page-count count="14"/>
<word-count count="7621"/>
</counts>
<custom-meta-wrap>
<custom-meta>
<meta-name>section-at-acceptance</meta-name>
<meta-value>AI for Human Learning and Behavior Change</meta-value>
</custom-meta>
</custom-meta-wrap>
</article-meta>
</front>
<body>
<sec sec-type="intro" id="sec1">
<label>1</label>
<title>Introduction</title>
<p>Today, the Internet is the main source of information for everyone. If we need anything, we simply get it by browsing the data, such as text, audio, video, or images, and everything is available. However, we are missing the originality of the data. In the 1920s, television and video content started gaining popularity. At that time, rebroadcasting programs and films became common, which later raised concerns about copyright protection in 1984. The &#x201C;Betamax case&#x201D; addressed the legality of recording content for private use (<xref ref-type="bibr" rid="ref12">Rani et al., 2024</xref>).</p>
<p>The historical development from 1920 to the present covers the period up to 2025. Broadcasting television and video content has become extremely popular, but the unlawful rebroadcasting of movies and programs remains a significant challenge (<xref ref-type="bibr" rid="ref7">Kumar et al., 2021</xref>). VSRs were invented between the 1950s and 1970s, enabling the copying of movies and programs. This eventually led to the&#x201D; Betamax case,&#x201D; which confronted the legality of recording and broadcasting content. From the 1990s to the 2000s, DVDs and the Internet were used for peer-to-peer file sharing through platforms such as Napster, LimeWire, and BitTorrent (<xref ref-type="bibr" rid="ref15">Wu et al., 2022</xref>). From 2010 to the present, streaming platforms have grown in popularity. However, unauthorized uploading and distribution of videos have become a major concern. Video uploaders are identified based on their ID&#x2019;s, but the the copyright regulations remains imperfect. Unauthorized screen recordings and live streaming pose significant challenges. Using such content, individuals often alter the original content due to the availability of video editing software. Blockchain is a decentralized digital ledger that records transactions across several computers while ensuring security, transparency, and immutability (<xref ref-type="bibr" rid="ref11">Ma et al., 2018</xref>). Each transaction is organized into a block, which is linked to the preceding block by cryptographic hashes, resulting in a chronological &#x201C;chain&#x201D; of blocks. Based on its properties, blockchain may provide more security.</p>
<p>However, blockchain provides a safe, transparent, and efficient solution for managing video copyright, empowering creators, combating piracy, and assuring fair pay by using both public and private blockchains. A public blockchain is a decentralized and permissionless network that anyone can access; it is completely open and transparent. It offers global accessibility, allowing anyone with an internet connection to use it (<xref ref-type="bibr" rid="ref9">Lee et al., 2021</xref>; <xref ref-type="bibr" rid="ref3">Garba et al., 2021</xref>). The main problems with public blockchains are scalability issues, energy consumption, and privacy concerns. A controlled environment is provided by private blockchains. A private blockchain also faces some issues such as centralization, scalability issues, security risks, high costs, governance difficulties, compliance requirements, privacy concerns, trust issues, and limited innovation. These can be solved through efficient protocols, strong security, cost-saving solutions, privacy tools, and other measures (<xref ref-type="bibr" rid="ref4">Guo et al., 2020</xref>). A public blockchain is an open, permissionless network that anyone can join to read, write, and validate transactions. It is completely decentralized, with examples including Ethereum and Bitcoin. Blockchain technology provides trust and immutability. In contrast, a private blockchain is a decentralized, permissioned network that is controlled by a single organization or a group of organizations. Only approved users can view or authenticate transactions, providing privacy control. Due to this, it is less decentralized than a public blockchain (<xref ref-type="bibr" rid="ref16">Yang et al., 2020</xref>; <xref ref-type="bibr" rid="ref14">Wang et al., 2023</xref>).</p>
<p>Therefore, a perceptual hash (pHash) function is a neat solution to this problem. A perceptual hash function has the characteristic that the hash of an original input is associated with the hash of a slightly altered input. As a result, perceptual hashing can be used to detect manipulated picture and video frames without substantially changing how they look. The distributed hash table (DHT) technique is a well-known feature of the peer-to-peer file sharing network, the InterPlanetary File System (IPFS). A unique 46-byte hash is assigned to every file, including images and videos, to maximize storage and retrieval (<xref ref-type="bibr" rid="ref6">Hasan and Salah, 2019</xref>). The IPFS hash value is changed when the content creators modifies the image or the video frame in the distributed hash table. Features such as immutability, integrity, dependability, and transaction availability are provided by blockchain technology (<xref ref-type="bibr" rid="ref1">Dave et al., 2022</xref>). Each block that makes up a blockchain contains a number of transactions (<xref ref-type="bibr" rid="ref5">G&#x00FC;rfidan and Ersoy, 2021</xref>). Our method involves storing the perceptual hash of every picture or movie shared on the blockchain network&#x2019;s IPFS distributed file-sharing system (<xref ref-type="bibr" rid="ref10">Li and Wang, 2016</xref>; <xref ref-type="bibr" rid="ref8">Lee and Choi, 2022</xref>; <xref ref-type="bibr" rid="ref13">Singh and Aggarwal, 2018</xref>; <xref ref-type="bibr" rid="ref17">Yu et al., 2022</xref>; <xref ref-type="bibr" rid="ref2">Gangwar et al., 2018</xref>).</p>
<p>We propose a solution to the problem of video copyright protection&#x2014;the use of IPFS-based file sharing and blockchain technology. Blockchain-based solutions have a lot to offer in terms of preventing video copyright violations. We propose a blockchain-based distributed system to prevent copyright violations in videos by utilizing the pHash algorithm. Below is an overview of the contributions made by our study:</p>
<sec id="sec2">
<label>1.1</label>
<title>Major contributions</title>
<list list-type="bullet">
<list-item>
<p>We recommend a blockchain-based and IPFS-based decentralized platform to store videos as transactions, providing copyright protection, availability, immutability, and transparency through peer ledgers and consensus mechanisms.</p>
</list-item>
<list-item>
<p>Our decentralized system stores videos on Ethereum and establishes immutable ownership records, while smart contracts automate copyright verification based on perceptual hashes, thereby being transparent and time-saving and eliminating intermediaries.</p>
</list-item>
<list-item>
<p>The decentralized blockchain system guarantees clear, secure, and verifiable ownership records of the video in a transparent manner and automatically identifies copyright conflicts through perceptual hash comparison. It provides a transparent, blockchain-based resolution process.</p>
</list-item>
<list-item>
<p>It provides a user-friendly UI for creators, users, and other stakeholders to interact with this platform. The platform offers a user-friendly interface, making copyright protection easy and scalable for both individuals and large organizations.</p>
</list-item>
</list>
</sec>
<sec id="sec3">
<label>1.2</label>
<title>Organization</title>
<p>The structure of the paper is as follows: Section 2 deals with the background. Section 3 presents the details of the study. Section 4 describes the proposed approach, and Section 5 deals with the implementation details. Section 6 shows the results and performance analysis of the framework. Finally, Section 7 concludes the study and discusses future work.</p>
</sec>
</sec>
<sec id="sec4">
<label>2</label>
<title>Background</title>
<p>Hashing techniques are very effective for storing, retrieving, and managing data. There are four types of hashing techniques related to images: wavelet hashing (wHash), pHash, difference hash (dHash), and average hash (aHash).</p>
<sec id="sec5">
<label>2.1</label>
<title>pHash (perceptual hash)</title>
<p>This pHash uses the discrete cosine transform (DCT) to capture the low-frequency components of an image. The hash value is generated using perceptual characteristics rather than the pixel value. pHash works well with the image modifications i.e minior changes are also able to identify. pHash is focused on frequency and not on pixel intensity. Therefore, it handles brightness or contrast changes easily. It is very effective for detecting similarities between the images. In addition, it is less affected by the noise. pHash is more effective because it needs more processing power compared to aHash and dHash. Therefore, pHash is mainly used for reverse image and for detecting edited images.</p>
<p>pHash has the ability to capture the perceptual characteristics of video frames, making it robust to common modifications, including minor ones such as resizing and compression. It allows us to measure content similarity, which is the initial step in our framework for detecting altered copies. It also provides greater efficiency compared to other hashing techniques such as wHash, aHash, and dHash, and it is well-suited for video comparisons. Due to these reasons, we chose the pHash technique for frame conversion.</p>
</sec>
<sec id="sec6">
<label>2.2</label>
<title>wHash (wavelet hashing)</title>
<p>wHash uses the Haar wavelet transform to convert an image into frequency components. The wHash technique is similar to the pHash technique; however, it works better with image modifications such as resizing, blurring, and noise. In addition, wHash provides better structural data, such as comparing two images with textures or patterns. It is significantly less sensitive to brightness changes compared to other hashing techniques. wHash is very effective for high-quality image retrieval, particularly in forensic applications. Therefore, the wHash technique is useful for identifying image similarities, retrieving high-quality reverse images, image forensics, and content matching.</p>
</sec>
<sec id="sec7">
<label>2.3</label>
<title>dHash (difference hash)</title>
<p>The dHash technique uses the grayscale value. First, it converts an image to a grayscale image; then, it resizes it to 9&#x002A;8 pixels and compares it with its adjacent pixels. Based on brightness, it assigns 1 or 0 to each pixel; for instance, if the left pixel is brighter than the right pixel, it assigns 1 to it, otherwise it assigns 0. In large-scale image datasets, the dHash technique is useful and faster compared to pHash. It is very good at detecting minor modifications in an image. The dHash technique works well even if images are resized because it is less sensitive to compression and scaling. When an image is cropped, the hash value changes because it is sensitive to the robustness of the image. It is very sensitive to brightness and contrast changes because this hashing technique depends directly on pixel intensity differences. It is not effective for detecting complex transformations, such as adding filters to an image or object movement. pHash is mainly useful for detecting small modifications and fast duplicate image detection only.</p>
</sec>
<sec id="sec8">
<label>2.4</label>
<title>aHash (average hash)</title>
<p>aHash also converts an image to a grayscale image, resizes it to an 8&#x002A;8 image, and calculates the average intensity. Each pixel value is compared with the average value. If the pixel value is above average, it assigns 1 to the pixel; if the pixel value is below average, then it assigns 0 to the pixel. The aHash technique is the fastest method for quick compression by producing similar hash values.</p>
<p>It is highly sensitive to brightness. If brightness is adjusted, the hash value also changes. In addition, it is not effective for cropped and rotated images. dHash is dependent on the pixel intensity value and is not effective when noise is added to images. aHash is only good for finding exact duplicates in an image and lightweight applications.</p>
<p>These techniques are used for detecting visual similarities between videos. To enable a decentralized system, we use the IPFS and Swarm. For storing and accessing data without a central authority, the IPFS and Swarm are used. These provide decentralized, distributed file storage for blockchain-based applications.</p>
</sec>
<sec id="sec9">
<label>2.5</label>
<title>IPFS (InterPlanetary File System)</title>
<p>The IPFS is a peer-to-peer distributed file system. The main aim of the IPFS is to store and share data in a decentralized manner. It uses the CID (Content Addressing), and because of this feature, it provides unique cryptographic hashes for each file. For representing files and directories, it uses DAG. By using this, large data are split into smaller parts, and each part is connected with links. Duplication does not occur because every file has its own address. The IPFS uses the content in the distributed system. It is mainly used in the sharing of files, DApps, websites, etc.</p>
</sec>
<sec id="sec10">
<label>2.6</label>
<title>Swarm</title>
<p>Swarm is an Ethereum-native decentralized storage system. Similar to the IPFS, Swarm also splits files into smaller parts and addresses them, and it also supports updatable feeds. In this system, the filters are updated with a stamp only (proof of payment). BZZ tokens are provided as rewards for storage nodes for motivation. This system supports mutable files and real-time updates. It is suitable for hosting entire DApps, websites, and more. However, setting up the system is more complex compared to the IPFS.</p>
</sec>
</sec>
<sec id="sec11">
<label>3</label>
<title>Related work</title>
<p>With the emergence of blockchain technology, new solutions have arisen to address challenges in digital copyright and Internet business, including video content production. Researchers have argued that conventional means of IP management, including digital watermarking, encryption, and DRM, fall short in providing adequate security and authentication for digital assets. Such centralized systems may be manipulated, pirated, and broadcast without the consent of the creators of such systems.</p>
<p>Blockchain, as designed, provides a shared, decentralized, transparent, and immutable system for operational record-keeping that addresses many of these challenges. Using the concept of blockchain, video content could be registered securely, and the ownership of content could be virtually defensible as it is stored in a decentralized manner. This, in a way, allows creators to assert their ownership of the content, access the path of the material, and prevent piracy. Moreover, the integration of perceptual hashing with blockchain has benefits for security, as video fingerprints can be easily distinguished and stored on the blockchain, decreasing the occurrence of piracy.</p>
<p>The current literature review in <xref ref-type="table" rid="tab1">Table 1</xref> shows that despite the many opportunities blockchain offers in the area of copyright protection, there are many barriers to its effective implementation. Among these promising directions, challenges such as the workability of blockchain for big data, the problem of integration of various blockchain platforms, and the legal regulation of blockchain in the field of intellectual property management stand out. The majority of established blockchain-based copyright protection systems are still under development and remain unproven in real-world conditions. Several projects are currently exploring how various forms of blockchain can be used for content protection. Some projects focus on improving the video watermarking method, while others combine blockchain with smart contracts when it comes to the automation of licensing and copyright infringement. However, to date, the application of blockchain technology in the management of copyrights remains limited due to technical restrictions such as the rate of transactions, energy consumption, and legal or regulatory constraints. Thus, blockchain-based systems present significant potential for the protection and management of copyrights. However, for a more comprehensive solution, it is crucial to focus on further improving the implementation of blockchain solutions in the management of copyrights. More studies are emerging on how this new technology can complement present copyright frameworks, with the goal of designing a stronger and more effective mechanism to safeguard copyright materials, especially in modern societies where content sharing is rapidly increasing.</p>
<table-wrap position="float" id="tab1">
<label>Table 1</label>
<caption>
<p>Blockchain and digital content applications.</p>
</caption>
<table frame="hsides" rules="groups">
<thead>
<tr>
<th align="left" valign="top">References</th>
<th align="center" valign="top">Year</th>
<th align="left" valign="top">Application</th>
<th align="center" valign="top">B</th>
<th align="center" valign="top">S</th>
<th align="center" valign="top">T</th>
<th align="center" valign="top">SC</th>
<th align="center" valign="top">CP</th>
</tr>
</thead>
<tbody>
<tr>
<td align="left" valign="top">1</td>
<td align="center" valign="top">2024</td>
<td align="left" valign="top">Blockchain and non-fungible tokens for educational resources</td>
<td align="center" valign="top">&#x2713;</td>
<td align="center" valign="top"><italic>&#x00D7;</italic></td>
<td align="center" valign="top"><italic>&#x00D7;</italic></td>
<td align="center" valign="top">&#x2713;</td>
<td align="center" valign="top">&#x2713;</td>
</tr>
<tr>
<td align="left" valign="top">2</td>
<td align="center" valign="top">2021</td>
<td align="left" valign="top">pHash and the IPFS for images and videos</td>
<td align="center" valign="top">&#x2713;</td>
<td align="center" valign="top">&#x2713;</td>
<td align="center" valign="top">&#x2713;</td>
<td align="center" valign="top"><italic>&#x00D7;</italic></td>
<td align="center" valign="top">&#x2713;</td>
</tr>
<tr>
<td align="left" valign="top">3</td>
<td align="center" valign="top">2022</td>
<td align="left" valign="top">NSCT-SVD-based zero watermarking for video copyright</td>
<td align="center" valign="top">&#x2713;</td>
<td align="center" valign="top">&#x2713;</td>
<td align="center" valign="top"><italic>&#x00D7;</italic></td>
<td align="center" valign="top"><italic>&#x00D7;</italic></td>
<td align="center" valign="top">&#x2713;</td>
</tr>
<tr>
<td align="left" valign="top">4</td>
<td align="center" valign="top">2018</td>
<td align="left" valign="top">DRM chain for digital content</td>
<td align="center" valign="top">&#x2713;</td>
<td align="center" valign="top"><italic>&#x00D7;</italic></td>
<td align="center" valign="top"><italic>&#x00D7;</italic></td>
<td align="center" valign="top"><italic>&#x00D7;</italic></td>
<td align="center" valign="top"><italic>&#x00D7;</italic></td>
</tr>
<tr>
<td align="left" valign="top">5</td>
<td align="center" valign="top">2021</td>
<td align="left" valign="top">SPDC for digital content</td>
<td align="center" valign="top">&#x2713;</td>
<td align="center" valign="top"><italic>&#x00D7;</italic></td>
<td align="center" valign="top"><italic>&#x00D7;</italic></td>
<td align="center" valign="top"><italic>&#x00D7;</italic></td>
<td align="center" valign="top">&#x2713;</td>
</tr>
<tr>
<td align="left" valign="top">6</td>
<td align="center" valign="top">2019</td>
<td align="left" valign="top">Smart contract for digital multimedia resources</td>
<td align="center" valign="top">&#x2713;</td>
<td align="center" valign="top">&#x2713;</td>
<td align="center" valign="top"><italic>&#x00D7;</italic></td>
<td align="center" valign="top"><italic>&#x00D7;</italic></td>
<td align="center" valign="top">&#x2713;</td>
</tr>
<tr>
<td align="left" valign="top">7</td>
<td align="center" valign="top">2019</td>
<td align="left" valign="top">Ethereum smart contract for the provenance of digital media</td>
<td align="center" valign="top">&#x2713;</td>
<td align="center" valign="top">&#x2713;</td>
<td align="center" valign="top"><italic>&#x00D7;</italic></td>
<td align="center" valign="top"><italic>&#x00D7;</italic></td>
<td align="center" valign="top">&#x2713;</td>
</tr>
<tr>
<td align="left" valign="top">8</td>
<td align="center" valign="top">2021</td>
<td align="left" valign="top">Blockchain for smart home environments</td>
<td align="center" valign="top">&#x2713;</td>
<td align="center" valign="top"><italic>&#x00D7;</italic></td>
<td align="center" valign="top"><italic>&#x00D7;</italic></td>
<td align="center" valign="top"><italic>&#x00D7;</italic></td>
<td align="center" valign="top"><italic>&#x00D7;</italic></td>
</tr>
<tr>
<td align="left" valign="top">9</td>
<td align="center" valign="top">2021</td>
<td align="left" valign="top">Blockchain for multimedia content</td>
<td align="center" valign="top">&#x2713;</td>
<td align="center" valign="top"><italic>&#x00D7;</italic></td>
<td align="center" valign="top"><italic>&#x00D7;</italic></td>
<td align="center" valign="top">&#x2713;</td>
<td align="center" valign="top"><italic>&#x00D7;</italic></td>
</tr>
<tr>
<td align="left" valign="top">10</td>
<td align="center" valign="top">2021</td>
<td align="left" valign="top">Blockchain for music wallets</td>
<td align="center" valign="top">&#x2713;</td>
<td align="center" valign="top"><italic>&#x00D7;</italic></td>
<td align="center" valign="top"><italic>&#x00D7;</italic></td>
<td align="center" valign="top"><italic>&#x00D7;</italic></td>
<td align="center" valign="top"><italic>&#x00D7;</italic></td>
</tr>
<tr>
<td align="left" valign="top">Proposed</td>
<td/>
<td align="left" valign="top">Blockchain for video copyright protection</td>
<td align="center" valign="top">&#x2713;</td>
<td align="center" valign="top">&#x2713;</td>
<td align="center" valign="top">&#x2713;</td>
<td align="center" valign="top">&#x2713;</td>
<td align="center" valign="top">&#x2713;</td>
</tr>
</tbody>
</table>
<table-wrap-foot>
<p>&#x002A;B, blockchain; &#x002A;S, security; &#x002A;T, trust; &#x002A;SC, scalability; &#x002A;CP, copyright protection.</p>
</table-wrap-foot>
</table-wrap>
</sec>
<sec id="sec12">
<label>4</label>
<title>Proposed system model for video copyright protection</title>
<sec id="sec13">
<label>4.1</label>
<title>System architecture</title>
<p>The development of digital media has also posed challenges in the protection of video content from copyright infringement. Traditional systems of copyright management are usually centralized, easy to tamper, and not accessible to most creators. Blockchain is an innovative approach to tackle the problem of counterfeiting and provides a secure platform for the registration of video ownership and the verification of copyright in a decentralized and secure manner. This article presents a proposed framework that implements perceptual hashing of video content and leverages smart contracts on the blockchain to manage and safeguard the registration, verification, and protection of the content. The Ethereum smart contract stores videos by recording their pHash, IPFS hash, and owner address; it checks new videos by comparing pHash values to identify copyright infringement and stores disputes on the blockchain, making ownership secure, transparent, and tamperproof. For the back end, the platform uses Python Flask, and for application program interface (API) testing, the platform uses Postman. The platform interacts with the Ethereum blockchain to securely store and manage ownership data. This system gives power to content creators to safeguard their intellectual property more efficiently and transparently.</p>
<p>The proposed system includes two smart contracts: the Contract Video Registry, used for registering videos, and the ABI of Contract, used for authenticating videos. A mapping function is used to establish a key value data structure, allowing for effective storage and retrieval of values. The function supports conversions, such as from byte32 to video, and computations within the Contract Video Registry. It also plays an important role in the decentralized video-sharing application by simplifying data access and processing.</p>
<p>The video is converted into an <italic>n</italic> number of frames of equal size, and a perceptual hash (pHash) value is computed for each frame to represent its visual features. pHash captures the perceptual content and identifies visually similar frames. It can also detect frames that have undergone transformations such as resizing or compression. We also utilize this pHash for similarity matching by calculating the Hamming distance between the hashes, making pHash highly effective for the detection of duplicate video content.</p>
<p>The main aim of the proposed system model is to ensure secure, tamper-proof, and decentralized video copyright protection using perceptual hashing, the IPFS, and blockchain technology. The architecture mainly contains three functional modules: Hash Value Generation, Secure Blockchain Network, and Multimedia Copyright Protection, as shown in <xref ref-type="fig" rid="fig1">Figure 1</xref>.</p>
<list list-type="order">
<list-item>
<p><bold>Hash Value Generation</bold>: When a video is uploaded by a user initially, a unique digital fingerprint of the video gets generated. This video then undergoes preprocessing, where it is divided into frames based on a time sequence for processing. PHash is generated for each and every frame. A frame-by-frame comparison is conducted using pHash. These hash values represent the visual essence of each frame. Instead of storing and comparing entire frames, the system calculates and stores their hash values only (64bit per frame). During the verification step, the uploaded video goes through the same pre-processing and hashing process. These hashes are then compared with the stored hashes using the Hamming distance to measure similarity. This makes it possible to effectively detect similarities, even small modifications such as resizing and compression. This approach achieves a balance between robustness and resource efficiency, making it scalable for video copyright protection. The final hash values represent the original hash value of a particular video, and this original hash value is used for verification and protection against copyright infringement.</p>
</list-item>
<list-item>
<p><bold>Secured Blockchain Network:</bold> Here, the blockchain network is created using Ethereum and IPFS technologies. This network enables secure registration and verification of video hashes through blockchain smart contracts and decentralized storage.</p>
</list-item>
</list>
<list list-type="bullet">
<list-item>
<p><bold>Smart Contract Deployment:</bold> A smart contract in Solidity is written and compiled. After deploying this code on the Ethereum Virtual Machine (EVM), both the bytecode and application binary interface (ABI) are generated for decentralized execution.</p>
</list-item>
<list-item>
<p><bold>Hyperledger:</bold> Hyperledger handles the actual video copyright ledger. The system employs a configuration file (e.g., netConfig.json) to establish and keep the blockchain network. The recorded video hashes are safely stored on this ledger.</p>
</list-item>
<list-item>
<p><bold>IPFS:</bold> Metadata are stored on the IPFS in a .bib file to provide decentralized and distributed storage. The pHash and IPFS hash are recorded and stored on the blockchain to create tamper-proof records.</p>
</list-item>
</list>
<list list-type="order">
<list-item>
<p><bold>Multimedia Copyright Protection and Integrity Verification:</bold> Multimedia provides continuous surveillance and enforcement of copyright protection.</p>
</list-item>
</list><list list-type="bullet">
<list-item>
<p><bold>Comparison Process:</bold> Whenever a new video is uploaded, its perceptual hash value is calculated and compared with existing pHash values on the blockchain network.</p>
</list-item>
<list-item>
<p><bold>Verification and Decision:</bold> Based on the similarity threshold (i.e&#x202F;&#x003E;&#x202F;=50%), the system determines whether a video is duplicated or unauthorized. If the video matches an existing one in the network, it is marked as copyrighted and flagged as a copyright infringement. If the video is new, it is eligible to be added to the blockchain network along with its IPFS records.</p>
</list-item>
</list>
<fig position="float" id="fig1">
<label>Figure 1</label>
<caption>
<p>Proposed system model for video copyright protection.</p>
</caption>
<graphic xlink:href="frai-08-1655709-g001.tif" mimetype="image" mime-subtype="tiff">
<alt-text content-type="machine-generated">Flowchart illustrating a system for multimedia copyright protection using blockchain. It begins with video upload and preprocessing to generate hash values. A secured blockchain network, utilizing Ethereum and IPFS, stores this data. The process involves Solidity code, compilation, byte code, and deployment in the Ethereum Virtual Machine. The hash content is registered and verified with IPFS, enabling smart contracts. Multimedia copyright protection is achieved through hash comparison. A match results in copyright protection, while a mismatch indicates infringement. The system ensures video integrity and copyright enforcement.</alt-text>
</graphic>
</fig>
<p>The proposed framework ensures the security of videos and operates using <xref ref-type="fig" rid="fig2">Algorithms 1</xref>&#x2013;<xref ref-type="fig" rid="fig4">3</xref>.</p>
<list list-type="bullet">
<list-item>
<p><xref ref-type="fig" rid="fig2">Algorithm 1</xref>: This algorithm is used for registering videos on the Ethereum network. For storing videos in the metadata, we use two parameters they are IPFS hash and address of the uploader. Unique ID is created for every video after that it checks the hash value to know that the video is already registered video or the new one.</p>
</list-item>
</list><list list-type="bullet">
<list-item>
<p><xref ref-type="fig" rid="fig3">Algorithm 2</xref>: This algorithm verifies whether a video already exists or is new using jsonify from Flask. The backend program of our proposed framework is shown in <xref ref-type="fig" rid="fig3">Algorithm 2</xref>. It is a Flask-based backend to interact with the Ethereum network. In addition, the IPFS is used for providing security by supporting video registration and verification. The video is registered on the blockchain using a smart contract. Using the IPFS and pHash values, the system verifies whether a video has already been registered. It provides three functions: registering, verifying, and comparing. All of these are performed based on user requirements.</p>
</list-item>
</list><list list-type="bullet">
<list-item>
<p><xref ref-type="fig" rid="fig4">Algorithm 3</xref>: This algorithm outlines the steps for registering, verifying, and comparing videos. The Postman API facilitates communication among all participants and ensures transparency and security by supporting the creation of video authenticity records. The main purpose of this algorithm is to compare two videos using their IPFS and pHash values. In addition, it extracts audio features from both videos using movie.py to compare their similarity. A threshold value is used to find the difference between frames and audio. By comparing these three parameters, the algorithm identifies whether the input video is identical to an existing one or has been edited.</p>
</list-item>
</list>
<fig position="float" id="fig2">
<label>ALGORITHM 1</label>
<caption>
<p>Video registry.</p>
</caption>
<graphic xlink:href="frai-08-1655709-g002.tif" mimetype="image" mime-subtype="tiff">
<alt-text content-type="machine-generated">Code snippet for a video registration and verification process in a blockchain context. The structure defines a video with an IPFS hash and uploader address. There is a mapping from a byte identifier to a video and an event called VideoRegistered. The code includes two functions: `registerVideo` that declares a video ID, stores video details, and triggers the VideoRegistered event; and `verifyVideo` that retrieves a video and verifies the hash matches the expected value.</alt-text>
</graphic>
</fig>
<fig position="float" id="fig3">
<label>ALGORITHM 2</label>
<caption>
<p>Perceptual hash-based video content identification.</p>
</caption>
<graphic xlink:href="frai-08-1655709-g003.tif" mimetype="image" mime-subtype="tiff">
<alt-text content-type="machine-generated">Algorithm pseudo-code for a system integrating Flask, Ethereum, and IPFS. It initializes a Flask API, connects to Ethereum, loads a smart contract, and connects to IPFS. The system includes procedures for registering and verifying videos on IPFS. The "Register Video" procedure involves a transaction and returns a status or error. "Verify Video" checks registration status. "Compare Videos" checks similarity between two video paths, returning results or errors. There's a basic "Home" route returning "Hello, World!" Finally, the Flask server is set to run in debug mode.</alt-text>
</graphic>
</fig>
<fig position="float" id="fig4">
<label>ALGORITHM 3</label>
<caption>
<p>Video similarity comparison.</p>
</caption>
<graphic xlink:href="frai-08-1655709-g004.tif" mimetype="image" mime-subtype="tiff">
<alt-text content-type="machine-generated">Algorithm flowchart for video similarity detection, detailing five steps: frame extraction, frame comparison using pHash, audio extraction, audio feature extraction and comparison, and decision making. It outlines directory creation, hash computation, audio feature extraction, and decision criteria based on frame and audio thresholds. Final steps involve cleanup and result return.</alt-text>
</graphic>
</fig>
<p>To better understand the process, we designed a flowchart that visually explains the execution flow. <xref ref-type="fig" rid="fig5">Figure 2</xref> presents a block diagram illustrating the workflow of our system (<xref ref-type="bibr" rid="ref7">Kumar et al., 2021</xref>). When a new video is added to the decentralized network, its pHash value and IPFS hash are computed. These values are then compared with those of existing videos in the network. If the similarity exceeds 50%, the video is not added to the blockchain. However, if the similarity is below this threshold, the video is successfully added to the blockchain network.</p>
<fig position="float" id="fig5">
<label>Figure 2</label>
<caption>
<p>System block diagram.</p>
</caption>
<graphic xlink:href="frai-08-1655709-g005.tif" mimetype="image" mime-subtype="tiff">
<alt-text content-type="machine-generated">Flowchart illustrating a process starting with uploading image/video and audio to an IPFS secure layer. It calculates perceptual hashes for video with Flask and audio with Moviepy. If similarity is 50% or more, no update occurs on the blockchain network. If less, video and audio are added to the IPFS P2P system, and the perceptual hash is added to the blockchain network. The process ends here.</alt-text>
</graphic>
</fig>
</sec>
</sec>
<sec id="sec14">
<label>5</label>
<title>Implementation</title>
<p>The system utilizes the Ethereum blockchain to securely register and verify video ownership. <xref ref-type="table" rid="tab2">Table 2</xref> lists the software used for the implementation. Video creators upload their content, and Postman is used to interact with backend APIs, which generate a unique perceptual hash of the video. This hash, a digital fingerprint, is then stored on the blockchain to provide an immutable record of ownership. Key frames are extracted from the video for efficient hashing, ensuring minimal computational overhead. When ownership verification is required, perceptual hashes are compared through smart contracts, automating the process of detecting unauthorized use or ownership disputes. If a mismatch occurs, the system flags the content for further review, ensuring transparency and reducing reliance on third-party intervention. The backend, built using Python and Flask, ensures smooth communication with the blockchain, while Postman is used for testing and interaction with APIs. MetaMask is integrated to manage user authentication securely, allowing only authorized users to perform actions such as video registration or claim ownership. Moreover, the Ethereum blockchain ensures that ownership data are decentralized, and hence, secure, and transparent, thereby instilling confidence in users regarding the authenticity of recorded ownership. The approach combines the security of blockchain with the efficiency of perceptual hashing to create a robust video copyright management system that provides enhanced security and transparency in handling digital content for both creators and consumers alike.</p>
<table-wrap position="float" id="tab2">
<label>Table 2</label>
<caption>
<p>Software requirements and specifications for the proposed video copyright protection system.</p>
</caption>
<table frame="hsides" rules="groups">
<thead>
<tr>
<th align="left" valign="top">Tool/technology</th>
<th align="center" valign="top">Version</th>
</tr>
</thead>
<tbody>
<tr>
<td align="left" valign="top">Solidity</td>
<td align="center" valign="top">0.8.9</td>
</tr>
<tr>
<td align="left" valign="top">VS code</td>
<td align="center" valign="top">1.68</td>
</tr>
<tr>
<td align="left" valign="top">Truffle suite</td>
<td align="center" valign="top">5.4.6</td>
</tr>
<tr>
<td align="left" valign="top">Ganache</td>
<td align="center" valign="top">v6.12.1</td>
</tr>
<tr>
<td align="left" valign="top">MetaMask</td>
<td align="center" valign="top">10.1.0</td>
</tr>
<tr>
<td align="left" valign="top">Python (flask)</td>
<td align="center" valign="top">4.3.4</td>
</tr>
<tr>
<td align="left" valign="top">Postman API</td>
<td align="center" valign="top">9.1.1</td>
</tr>
<tr>
<td align="left" valign="top">Solidity extensions for VS Code</td>
<td align="center" valign="top">0.0.88</td>
</tr>
<tr>
<td align="left" valign="top">Java Script</td>
<td align="center" valign="top">9.1.1</td>
</tr>
</tbody>
</table>
</table-wrap>
<sec id="sec15">
<label>5.1</label>
<title>Testbed setup</title>
<p>The system integrates a Python Flask-based backend with the Ethereum blockchain to provide decentralized video copyright protection. The backend handles user authentication, perceptual hash generation, and communication with the blockchain. Postman is used for testing APIs that manage video registration and ownership verification processes. The Ethereum blockchain ensures secure, immutable storage of perceptual hashes, while smart contracts automate ownership verification and dispute resolution. MetaMask manages user authentication, enabling secure blockchain interactions. This combination of technologies provides a scalable and reliable framework for video copyright management. The software components of the project are designed to ensure secure, efficient, and decentralized management of video copyrights. The backend is developed using Python Flask, which handles API requests for video registration, perceptual hash generation, and blockchain interactions. The APIs are tested and interacted with using Postman, and this makes the communication between the user and the system very easy. The blockchain infrastructure is built on Ethereum, utilizing its robust decentralized framework for storing perceptual hashes and deploying smart contracts written in Solidity. These smart contracts automate processes such as ownership verification and dispute resolution. MetaMask is integrated to manage user authentication and enable secure blockchain transactions. This combination of software ensures a reliable, scalable, and transparent solution for protecting video copyrights.</p>
</sec>
</sec>
<sec id="sec16">
<label>6</label>
<title>Result analysis and discussion</title>
<p>In this section, we analyze and discuss the results with respect to our proposed and implemented framework. <xref ref-type="fig" rid="fig6">Figure 3</xref> depicts the result when the proposed smart contract was deployed on the Ethereum blockchain network. It shows smart contract functions such as registeringVideos, getVideo, and videos as inputs to the blockchain network. The orange-colored button indicates functions that write or update state values in the blockchain network. Similarly, the blue-colored button represents functions that read values from the blockchain network. After successful compilation with the Solidity compiler and deployment of the bytecode.</p>
<fig position="float" id="fig6">
<label>Figure 3</label>
<caption>
<p>Output of the deployed smart contract on the Ethereum blockchain network.</p>
</caption>
<graphic xlink:href="frai-08-1655709-g006.tif" mimetype="image" mime-subtype="tiff">
<alt-text content-type="machine-generated">Interface for deployed smart contracts with functions for registering and retrieving videos. Shows fields for IPFS hash, perceptual hash, and title for video registration, and perceptual hash for retrieving videos. Includes options to transact or call.</alt-text>
</graphic>
</fig>
<p>of the smart contract to the blockchain network, we obtained the transaction status, hash, block hash, block number, contract address, owner address, gas values, and bytecode, as shown in <xref ref-type="fig" rid="fig7">Figure 4</xref>. Client communication with the video copyright framework is facilitated through the Postman API. <xref ref-type="fig" rid="fig8">Figure 5</xref> illustrates the Postman call made when a video content is registered by a content owner. As a result, it returns the InterPlanetary File System (IPFS) value, the owner&#x2019;s externally owned account (EOA) address, and the status of the video registration. <xref ref-type="fig" rid="fig9">Figure 6</xref> verifies whether the video content is from the original owner&#x2019;s address or not. As a result, it shows the IPFS hash value, the owner&#x2019;s EOA address, and whether the video is registered or not. To compare the copyright of a video, we conducted a simulation using an original video and a modified video. <xref ref-type="fig" rid="fig10">Figure 7</xref> shows the output of the video content comparison, which took the path of the original and modified videos and compared their frames using their pHash values. As a result we get the video as original video or copyrighted video.</p>
<fig position="float" id="fig7">
<label>Figure 4</label>
<caption>
<p>Status of the deployed smart contract.</p>
</caption>
<graphic xlink:href="frai-08-1655709-g007.tif" mimetype="image" mime-subtype="tiff">
<alt-text content-type="machine-generated">Interface displaying blockchain transaction details: status indicates success; transaction hash is shown alongside block hash and number, contract address, and involved parties. Gas, transaction and execution costs are detailed, as well as input data.</alt-text>
</graphic>
</fig>
<fig position="float" id="fig8">
<label>Figure 5</label>
<caption>
<p>Video content registration by client (Postman API).</p>
</caption>
<graphic xlink:href="frai-08-1655709-g008.tif" mimetype="image" mime-subtype="tiff">
<alt-text content-type="machine-generated">JSON code snippet showing two sections. The first section contains an "ipfs_hash" with a long alphanumeric string, and an "account" with a hexadecimal value. The second section indicates a "status" of "Video registered".</alt-text>
</graphic>
</fig>
<fig position="float" id="fig9">
<label>Figure 6</label>
<caption>
<p>Video content verification.</p>
</caption>
<graphic xlink:href="frai-08-1655709-g009.tif" mimetype="image" mime-subtype="tiff">
<alt-text content-type="machine-generated">JSON data displays two sections. The first includes "ipfs_hash" with a string value and "account" with a hexadecimal string. The second section shows "is_registered" set to true.</alt-text>
</graphic>
</fig>
<fig position="float" id="fig10">
<label>Figure 7</label>
<caption>
<p>Video content comparison.</p>
</caption>
<graphic xlink:href="frai-08-1655709-g010.tif" mimetype="image" mime-subtype="tiff">
<alt-text content-type="machine-generated">Code snippet displaying JSON format. It specifies two file paths: "video_path_1" pointing to "original.mp4" and "video_path_2" to "edited.mp4". The comparison result states, "The videos are different or one is edited."</alt-text>
</graphic>
</fig>
<p>Ganache is a private network used on the Ethereum platform for testing smart contracts locally. <xref ref-type="fig" rid="fig11">Figures 8</xref>&#x2013;<xref ref-type="fig" rid="fig13">10</xref> show the Ganache accounts and transactions within the Ethereum network. <xref ref-type="fig" rid="fig11">Figure 8</xref> represents the EOA address, Ether account balance, transaction details, and index value. <xref ref-type="fig" rid="fig12">Figure 9</xref> shows the transaction hash value, the sender&#x2019;s address, the contact address, and the amount of gas used for the deployed contract. <xref ref-type="fig" rid="fig13">Figure 10</xref> shows the number of blocks, a timestamp value with date and time, and the amount of gas used for automatically initiated transactions.</p>
<fig position="float" id="fig11">
<label>Figure 8</label>
<caption>
<p>Ethereum externally owned account (EOA).</p>
</caption>
<graphic xlink:href="frai-08-1655709-g011.tif" mimetype="image" mime-subtype="tiff">
<alt-text content-type="machine-generated">Screenshot from a cryptocurrency management interface showing multiple Ethereum addresses, each with an associated balance. The first address has a balance of ninety-nine point ninety-seven ETH and eleven transactions. Other addresses each have a balance of one hundred ETH and zero transactions. The menu displays sections for accounts, blocks, transactions, contracts, events, and logs. The mnemonic phrase is displayed at the top.</alt-text>
</graphic>
</fig>
<fig position="float" id="fig12">
<label>Figure 9</label>
<caption>
<p>Transactions generated by the proposed framework.</p>
</caption>
<graphic xlink:href="frai-08-1655709-g012.tif" mimetype="image" mime-subtype="tiff">
<alt-text content-type="machine-generated">Ganache application interface displaying a list of Ethereum transactions. It shows transaction hashes, from addresses, and contract addresses. Each entry indicates gas used, value, and transaction type, either "Contract Call" or "Contract Creation." The top menu includes options like Accounts, Blocks, Transactions, Contracts, Events, and Logs. The current block, gas limit, gas used, and other network details are also displayed.</alt-text>
</graphic>
</fig>
<fig position="float" id="fig13">
<label>Figure 10</label>
<caption>
<p>Blocks generated by the proposed framework.</p>
</caption>
<graphic xlink:href="frai-08-1655709-g013.tif" mimetype="image" mime-subtype="tiff">
<alt-text content-type="machine-generated">Blockchain application interface displaying a list of blocks with details. Each entry includes block number, mining date, gas usage, and transaction count. Top menu features navigation items like Accounts, Blocks, Transactions, and more. Gas price, limit, and server information are shown at the top.</alt-text>
</graphic>
</fig>
<p>To analyze the framework&#x2019;s performance at increased transactions and to measure its efficiency, tests were conducted on various important functionalities of the model using an EVM node. Operations such as video registration and verification were thoroughly tested at various transaction rates, and the results were noted for future reference. The same simulation was run five more times to find variations, and the average results were taken into consideration. The results are shown in <xref ref-type="table" rid="tab3">Tables 3</xref>, <xref ref-type="table" rid="tab4">4</xref>. All values are rounded to two decimal places. For performance testing using Hyperledger Caliper, we conducted 5,000 transactions, with each transaction consisting of three operations: RegisterVideo, GetVideo, and CompareVideo. Each operation was tested at transaction rates of 1,000, 2,500, and 4,000 transactions per second.</p>
<table-wrap position="float" id="tab3">
<label>Table 3</label>
<caption>
<p>Framework performance based on transactions and types.</p>
</caption>
<table frame="hsides" rules="groups">
<thead>
<tr>
<th align="left" valign="top">Function</th>
<th align="center" valign="top">Txns</th>
<th align="center" valign="top">Succ</th>
<th align="center" valign="top">TPS</th>
<th align="center" valign="top">Latency (Avg.)</th>
<th align="center" valign="top">Throughput (Avg.)</th>
</tr>
</thead>
<tbody>
<tr>
<td align="left" valign="top">RegisterVideo</td>
<td align="center" valign="top">5,000</td>
<td align="center" valign="top">5,000</td>
<td align="center" valign="top">1,000, 2,500, 4,000</td>
<td align="center" valign="top">4.98, 5.06, 5.27</td>
<td align="center" valign="top">410.8, 409.6, 409.2</td>
</tr>
<tr>
<td align="left" valign="top">GetVideo</td>
<td align="center" valign="top">5,000</td>
<td align="center" valign="top">5,000</td>
<td align="center" valign="top">1,000, 2,500, 4,001</td>
<td align="center" valign="top">4.07, 4.38, 4.75</td>
<td align="center" valign="top">502.1, 484.6, 496.3</td>
</tr>
<tr>
<td align="left" valign="top">CompareVideo</td>
<td align="center" valign="top">5,000</td>
<td align="center" valign="top">5,000</td>
<td align="center" valign="top">1,000, 2,500, 4,002</td>
<td align="center" valign="top">4.77, 4.76, 5.03</td>
<td align="center" valign="top">480.8, 454.3, 486.3</td>
</tr>
</tbody>
</table>
</table-wrap>
<table-wrap position="float" id="tab4">
<label>Table 4</label>
<caption>
<p>Performance after completion of all rounds.</p>
</caption>
<table frame="hsides" rules="groups">
<thead>
<tr>
<th align="left" valign="top">Function</th>
<th align="left" valign="top">TPS</th>
<th align="left" valign="top">CPU % Max</th>
<th align="left" valign="top">CPU % Avg.</th>
<th align="left" valign="top">Max memory in MB</th>
<th align="left" valign="top">Avg. memory in MB</th>
<th align="left" valign="top">Traffic in MB</th>
<th align="left" valign="top">Traffic out MB</th>
</tr>
</thead>
<tbody>
<tr>
<td align="left" valign="top" rowspan="3">RegisterVideo</td>
<td align="left" valign="top">1,000</td>
<td align="left" valign="top">81.16</td>
<td align="left" valign="top">54.05</td>
<td align="left" valign="top">956</td>
<td align="left" valign="top">775</td>
<td align="left" valign="top">20.8</td>
<td align="left" valign="top">30.5</td>
</tr>
<tr>
<td align="left" valign="top">2,500</td>
<td align="left" valign="top">76.30</td>
<td align="left" valign="top">44.67</td>
<td align="left" valign="top">761</td>
<td align="left" valign="top">709</td>
<td align="left" valign="top">20.8</td>
<td align="left" valign="top">30.5</td>
</tr>
<tr>
<td align="left" valign="top">4,000</td>
<td align="left" valign="top">74.15</td>
<td align="left" valign="top">46.18</td>
<td align="left" valign="top">911</td>
<td align="left" valign="top">714</td>
<td align="left" valign="top">20.8</td>
<td align="left" valign="top">30.5</td>
</tr>
<tr>
<td align="left" valign="top" rowspan="3">GetVideo</td>
<td align="left" valign="top">1,000</td>
<td align="left" valign="top">78.11</td>
<td align="left" valign="top">43.12</td>
<td align="left" valign="top">1,020</td>
<td align="left" valign="top">749</td>
<td align="left" valign="top">12.1</td>
<td align="left" valign="top">29.4</td>
</tr>
<tr>
<td align="left" valign="top">2,500</td>
<td align="left" valign="top">80.83</td>
<td align="left" valign="top">44.56</td>
<td align="left" valign="top">952</td>
<td align="left" valign="top">684</td>
<td align="left" valign="top">12.1</td>
<td align="left" valign="top">29.4</td>
</tr>
<tr>
<td align="left" valign="top">4,000</td>
<td align="left" valign="top">80.33</td>
<td align="left" valign="top">43.67</td>
<td align="left" valign="top">934</td>
<td align="left" valign="top">712</td>
<td align="left" valign="top">12.1</td>
<td align="left" valign="top">29.4</td>
</tr>
<tr>
<td align="left" valign="top" rowspan="3">CompareVideo</td>
<td align="left" valign="top">1,000</td>
<td align="left" valign="top">74.06</td>
<td align="left" valign="top">42.03</td>
<td align="left" valign="top">955</td>
<td align="left" valign="top">740</td>
<td align="left" valign="top">12</td>
<td align="left" valign="top">28.5</td>
</tr>
<tr>
<td align="left" valign="top">2,500</td>
<td align="left" valign="top">79.70</td>
<td align="left" valign="top">38.35</td>
<td align="left" valign="top">888</td>
<td align="left" valign="top">672</td>
<td align="left" valign="top">12</td>
<td align="left" valign="top">28.7</td>
</tr>
<tr>
<td align="left" valign="top">4,000</td>
<td align="left" valign="top">80.49</td>
<td align="left" valign="top">35.92</td>
<td align="left" valign="top">911</td>
<td align="left" valign="top">698</td>
<td align="left" valign="top">12</td>
<td align="left" valign="top">28.9</td>
</tr>
</tbody>
</table>
</table-wrap>
<p>These functions exhibited consistent latency between 4.07 and 5.27&#x202F;s at different transaction send rates (1,000, 2,500, and 4000TPS) for the 5,000 transactions submitted to an EVM node. Latency represents the interval between a transaction&#x2019;s start and network confirmation. <xref ref-type="fig" rid="fig14">Figure 11</xref> depicts that the RegisterVideo function takes more latency compared to the other subfunctions such as Get Video and Compare Video as RegisterVideo deals with hash values and IPFS values for video ownership. GetVideo is a kind of read transaction. Therefore, it has the lowest latency, that is, 4.4&#x202F;s compared to the other functions and subfunctions. The Compare Video function compares the original video with the edited video/copyright-violated videos by analyzing perceptual hash and IPFS values. Therefore, Compare Video has a latency of approximately 4.85&#x202F;s.</p>
<fig position="float" id="fig14">
<label>Figure 11</label>
<caption>
<p>Variable transaction rate latency.</p>
</caption>
<graphic xlink:href="frai-08-1655709-g014.tif" mimetype="image" mime-subtype="tiff">
<alt-text content-type="machine-generated">Bar chart depicting latency averages in seconds for Register Video, Get Video, and Compare Video across transaction rates of 1000, 2000, and 4000 seconds. Each category has three bars, with Register Video showing consistently higher latency than Get and Compare Video.</alt-text>
</graphic>
</fig>
<p>Furthermore, the number of transactions that are handled by a network per unit time is throughput, and the throughput analysis also demonstrated consistent behavior, with 409 to 502 transactions per second for each function. GetVideo had the highest throughput, while RegisterVideo had the lowest at the same transaction end rates. <xref ref-type="fig" rid="fig15">Figure 12</xref> reveals that the read transaction, i.e., GetVideo, achieves higher throughput compared to the other functions because this function verifies the video using its IPFS hash value and the address of the uploader. Registe Video had the minimum throughput of 409.87&#x202F;s due to its functionality. The Compare Video function compares the original video with the edited video by analyzing perceptual hash and IPFS hash values. Therefore, Compare Video takes 477.23&#x202F;s more. The throughput graph in <xref ref-type="fig" rid="fig15">Figure 12</xref> reveals that the framework performs better under higher loads.</p>
<fig position="float" id="fig15">
<label>Figure 12</label>
<caption>
<p>Transaction rate variation in throughput.</p>
</caption>
<graphic xlink:href="frai-08-1655709-g015.tif" mimetype="image" mime-subtype="tiff">
<alt-text content-type="machine-generated">Bar chart comparing average throughput in seconds for three operations: Register Video, Get Video, and Compare Video across different transaction rates in seconds: 500, 1000, and 1500. Each operation is color-coded and demonstrates similar throughput for each transaction rate.</alt-text>
</graphic>
</fig>
<p>In addition, CPU, memory, and traffic resource usage data were computed and examined. The parameters were examined during the same 5,000 transactions, under transaction input rates of 1,000, 2,500, and 4,000 TPS. The highest CPU usage of the framework was 81.16%, and the average CPU usage was 35.92%, with a highest average range of 54.05%, as illustrated in <xref ref-type="table" rid="tab4">Table 4</xref>. CPU usage for each function is shown in <xref ref-type="fig" rid="fig16">Figure 13</xref>. Memory consumption across all tested functions averaged between 672&#x202F;MB and 775&#x202F;MB, with the highest memory usage of 1,020&#x202F;MB observed for the GetVideo function, as shown in <xref ref-type="fig" rid="fig17">Figure 14</xref>. Based on traffic data, RegisterVideo registered the highest average traffic at 30.5&#x202F;MB, whereas CompareVideo registered the lowest average traffic at 28.7&#x202F;MB. For data traffic, CompareVideo&#x2019;s minimum was 12&#x202F;MB and RegisterVideo&#x2019;s maximum was 20.8&#x202F;MB. <xref ref-type="fig" rid="fig18">Figure 15</xref> displays the traffic data results. From the analysis results, it is evident that the proposed framework guarantees stable performance in stress testing, which can be employed in scalable, efficient, and reliable video services.</p>
<list list-type="bullet">
<list-item>
<p><bold>Regarding computational and storage overhead:</bold> The pHash value is computationally lightweight and more effective than pixel-wise or feature-based matching. Here, the frame-by-frame comparison involves only bitwise operations to calculate the Hamming distance, which is very effective.</p>
</list-item>
<list-item>
<p><bold>Storage Resources:</bold> To store the hash values of frames, we use decentralized storage&#x2014;namely, the IPFS&#x2014;to minimize resource overhead. To store videos, we use traditional databases and MySQL. Hashing 1,000 frames requires approximately 8&#x202F;KB of storage, which is negligible compared to the storage of the original video.</p>
</list-item>
</list>
<fig position="float" id="fig16">
<label>Figure 13</label>
<caption>
<p>CPU usage.</p>
</caption>
<graphic xlink:href="frai-08-1655709-g016.tif" mimetype="image" mime-subtype="tiff">
<alt-text content-type="machine-generated">Bar chart showing CPU Usage percentage (Max/Avg) against Transaction Rate (Seconds). It compares maximum and minimum usage for Register Video, Get Video, and Compare Video across rates 1000 to 4000. Each category is color-coded.</alt-text>
</graphic>
</fig>
<fig position="float" id="fig17">
<label>Figure 14</label>
<caption>
<p>Memory usage.</p>
</caption>
<graphic xlink:href="frai-08-1655709-g017.tif" mimetype="image" mime-subtype="tiff">
<alt-text content-type="machine-generated">Bar chart depicting memory usage in megabytes (MB) against transaction rate in seconds. It shows six series: Register Video Max and Min, Get Video Max and Min, Compare Video Max and Min, using different colors and patterns. Memory usage ranges from 400 MB to 1200 MB across transaction rates of 1000 to 4000 seconds.</alt-text>
</graphic>
</fig>
<fig position="float" id="fig18">
<label>Figure 15</label>
<caption>
<p>Network traffic.</p>
</caption>
<graphic xlink:href="frai-08-1655709-g018.tif" mimetype="image" mime-subtype="tiff">
<alt-text content-type="machine-generated">Bar chart showing network traffic in megabytes (MB) against transaction rate in seconds. Three sets of bars for transaction rates of one thousand, three thousand, and four thousand seconds. Each set has two bars: orange for traffic in and green for traffic out. Traffic out is consistently higher across all transaction rates.</alt-text>
</graphic>
</fig>
<p>This approach achieves a balanced combination of robustness, resource efficiency, and scalability for video copyright protection.</p>
</sec>
<sec sec-type="conclusions" id="sec17">
<label>7</label>
<title>Conclusion</title>
<p>The study successfully demonstrates that a fully decentralized, blockchain-based video copyright protection system is both feasible and effective. This can be achieved using blockchain: when video creators securely register on the blockchain and owners verify their ownership of any piece of content through this mechanism, any alteration or piracy can be easily identified. This study validates the performance of a reliable and efficient system, featuring video registration, verification, and comparison modules that run as designed. It provides a transparent and tamper-proof platform for the open and secure management of copyrights, an essential aspect of copyright protection and intellectual property management.</p>
<p>In the future, additional advanced methods of video analysis can be added to make a more accurate comparison of the contents. In addition, incorporating machine learning algorithms could enable more efficient detection of subtle modifications or plagiarized content. Expanding the platform to other forms of digital media will further increase the number of potential use cases for this blockchain platform. Building an easy-to-use front-end interface will greatly extend the target group and, by that means, foster further diffusion. Deploying the system on a public blockchain network will increase the system&#x2019;s scalability manyfold, with real-world testing across various scenarios. These improvements could solidify the system&#x2019;s role in protecting intellectual property rights in the evolving digital landscape.</p>
</sec>
</body>
<back>
<sec sec-type="data-availability" id="sec18">
<title>Data availability statement</title>
<p>The original contributions presented in the study are included in the article/supplementary material, further inquiries can be directed to the corresponding author.</p>
</sec>
<sec sec-type="author-contributions" id="sec19">
<title>Author contributions</title>
<p>SM: Conceptualization, Formal analysis, Methodology, Software, Writing &#x2013; original draft. NP: Supervision, Validation, Visualization, Writing &#x2013; review &#x0026; editing.</p>
</sec>
<sec sec-type="funding-information" id="sec20">
<title>Funding</title>
<p>The author(s) declare that no financial support was received for the research and/or publication of this article.</p>
</sec>
<sec sec-type="COI-statement" id="sec21">
<title>Conflict of interest</title>
<p>The authors declare that the research was conducted in the absence of any commercial or financial relationships that could be construed as a potential conflict of interest.</p>
</sec>
<sec sec-type="ai-statement" id="sec22">
<title>Generative AI statement</title>
<p>The authors declare that no Gen AI was used in the creation of this manuscript.</p>
</sec>
<sec sec-type="disclaimer" id="sec23">
<title>Publisher&#x2019;s note</title>
<p>All claims expressed in this article are solely those of the authors and do not necessarily represent those of their affiliated organizations, or those of the publisher, the editors and the reviewers. Any product that may be evaluated in this article, or claim that may be made by its manufacturer, is not guaranteed or endorsed by the publisher.</p>
</sec>
<ref-list>
<title>References</title>
<ref id="ref1"><citation citation-type="journal"><person-group person-group-type="author"><name><surname>Dave</surname><given-names>M.</given-names></name> <name><surname>Rastogi</surname><given-names>V.</given-names></name> <name><surname>Miglani</surname><given-names>M.</given-names></name> <name><surname>Saharan</surname><given-names>P.</given-names></name> <name><surname>Goyal</surname><given-names>N.</given-names></name></person-group> (<year>2022</year>). <article-title>Smart fog-based video surveillance with privacy preservation based on blockchain</article-title>. <source>Wirel. Pers. Commun.</source> <volume>124</volume>, <fpage>1677</fpage>&#x2013;<lpage>1694</lpage>. doi: <pub-id pub-id-type="doi">10.1007/s11277-021-09426-8</pub-id></citation></ref>
<ref id="ref2"><citation citation-type="confproc"><person-group person-group-type="author"><name><surname>Gangwar</surname><given-names>A.</given-names></name> <name><surname>Fidalgo</surname><given-names>E.</given-names></name> <name><surname>Alegre</surname><given-names>E.</given-names></name> <name><surname>Gonz&#x2019;alez-Castro</surname><given-names>V.</given-names></name></person-group> <source>Phishfingerprint: a practical approach for phishing web page identity retrieval based on visual cues</source>. <publisher-name>International Conference of Applications of Intelligent Systems</publisher-name> (<year>2018</year>).</citation></ref>
<ref id="ref3"><citation citation-type="journal"><person-group person-group-type="author"><name><surname>Garba</surname><given-names>A.</given-names></name> <name><surname>Dwivedi</surname><given-names>A. D.</given-names></name> <name><surname>Kamal</surname><given-names>M.</given-names></name> <name><surname>Srivastava</surname><given-names>G.</given-names></name> <name><surname>Tariq</surname><given-names>M.</given-names></name> <name><surname>Hasan</surname><given-names>M. A.</given-names></name> <etal/></person-group>. (<year>2021</year>). <article-title>A digital rights management system based on a scalable blockchain</article-title>. <source>Peer Peer Netw Appl</source> <volume>14</volume>, <fpage>2665</fpage>&#x2013;<lpage>2680</lpage>. doi: <pub-id pub-id-type="doi">10.1007/s12083-020-01023-z</pub-id></citation></ref>
<ref id="ref4"><citation citation-type="journal"><person-group person-group-type="author"><name><surname>Guo</surname><given-names>J.</given-names></name> <name><surname>Li</surname><given-names>C.</given-names></name> <name><surname>Zhang</surname><given-names>G.</given-names></name> <name><surname>Sun</surname><given-names>Y.</given-names></name> <name><surname>Bie</surname><given-names>R.</given-names></name></person-group> (<year>2020</year>). <article-title>Blockchain-enabled digital rights management for multimedia resources of online education</article-title>. <source>Multimed. Tools Appl.</source> <volume>79</volume>, <fpage>9735</fpage>&#x2013;<lpage>9755</lpage>. doi: <pub-id pub-id-type="doi">10.1007/s11042-019-08059-1</pub-id></citation></ref>
<ref id="ref5"><citation citation-type="journal"><person-group person-group-type="author"><name><surname>G&#x00FC;rfidan</surname><given-names>R.</given-names></name> <name><surname>Ersoy</surname><given-names>M.</given-names></name></person-group> (<year>2021</year>). <article-title>Blockchain-based music wallet for copyright protection in audio files</article-title>. <source>J. Comput. Sci. Technol.</source> <volume>21</volume>:<fpage>e2</fpage>. doi: <pub-id pub-id-type="doi">10.24215/16666038.21.e2</pub-id></citation></ref>
<ref id="ref6"><citation citation-type="journal"><person-group person-group-type="author"><name><surname>Hasan</surname><given-names>H. R.</given-names></name> <name><surname>Salah</surname><given-names>K.</given-names></name></person-group> (<year>2019</year>). <article-title>Combating deepfake videos using blockchain and smart contracts</article-title>. <source>IEEE Access</source> <volume>7</volume>, <fpage>41596</fpage>&#x2013;<lpage>41606</lpage>. doi: <pub-id pub-id-type="doi">10.1109/ACCESS.2019.2905689</pub-id></citation></ref>
<ref id="ref7"><citation citation-type="journal"><person-group person-group-type="author"><name><surname>Kumar</surname><given-names>R.</given-names></name> <name><surname>Tripathi</surname><given-names>R.</given-names></name> <name><surname>Marchang</surname><given-names>N.</given-names></name> <name><surname>Srivastava</surname><given-names>G.</given-names></name> <name><surname>Gadekallu</surname><given-names>T. R.</given-names></name> <name><surname>Xiong</surname><given-names>N. N.</given-names></name></person-group> (<year>2021</year>). <article-title>A secured distributed detection system based on ipfs and blockchain for industrial image and video data security</article-title>. <source>J Parallel Distrib Comput</source> <volume>152</volume>, <fpage>128</fpage>&#x2013;<lpage>143</lpage>. doi: <pub-id pub-id-type="doi">10.1016/j.jpdc.2021.02.022</pub-id></citation></ref>
<ref id="ref8"><citation citation-type="journal"><person-group person-group-type="author"><name><surname>Lee</surname><given-names>W. Y.</given-names></name> <name><surname>Choi</surname><given-names>Y.-S.</given-names></name></person-group> (<year>2022</year>). <article-title>Reliable integrity preservation analysis of video contents with support of blockchain systems</article-title>. <source>Appl. Sci.</source> <volume>12</volume>:<fpage>10280</fpage>. doi: <pub-id pub-id-type="doi">10.3390/app122010280</pub-id></citation></ref>
<ref id="ref9"><citation citation-type="journal"><person-group person-group-type="author"><name><surname>Lee</surname><given-names>N.-Y.</given-names></name> <name><surname>Yang</surname><given-names>J.</given-names></name> <name><surname>Kim</surname><given-names>C.-S.</given-names></name></person-group> (<year>2021</year>). <article-title>Blockchain-based smart propertization of digital content for intellectual rights protection</article-title>. <source>Electronics</source> <volume>10</volume>:<fpage>1387</fpage>. doi: <pub-id pub-id-type="doi">10.3390/electronics10121387</pub-id></citation></ref>
<ref id="ref10"><citation citation-type="confproc"><person-group person-group-type="author"><name><surname>Li</surname><given-names>Y.</given-names></name> <name><surname>Wang</surname><given-names>P.</given-names></name></person-group> (<year>2016</year>). <article-title>Robust image hashing based on low-rank and sparse decomposition</article-title>. In: <conf-name>2016 IEEE International Conference on Acoustics, Speech and Signal Processing (ICASSP)</conf-name>. <publisher-loc>Shanghai, China</publisher-loc>: <publisher-name>IEEE.</publisher-name> pp. <fpage>2154</fpage>&#x2013;<lpage>2158</lpage>.</citation></ref>
<ref id="ref11"><citation citation-type="journal"><person-group person-group-type="author"><name><surname>Ma</surname><given-names>Z.</given-names></name> <name><surname>Jiang</surname><given-names>M.</given-names></name> <name><surname>Gao</surname><given-names>H.</given-names></name> <name><surname>Wang</surname><given-names>Z.</given-names></name></person-group> (<year>2018</year>). <article-title>Blockchain for digital rights management</article-title>. <source>Futur. Gener. Comput. Syst.</source> <volume>89</volume>, <fpage>746</fpage>&#x2013;<lpage>764</lpage>. doi: <pub-id pub-id-type="doi">10.1016/j.future.2018.07.029</pub-id></citation></ref>
<ref id="ref12"><citation citation-type="journal"><person-group person-group-type="author"><name><surname>Rani</surname><given-names>P.</given-names></name> <name><surname>Sachan</surname><given-names>R. K.</given-names></name> <name><surname>Kukreja</surname><given-names>S.</given-names></name></person-group> (<year>2024</year>). <article-title>Educopyright-chain: an educational resources copyright protection system utilizing permissionless blockchain and non-fungible tokens</article-title>. <source>Peer Peer Netw Appl</source> <volume>17</volume>, <fpage>1</fpage>&#x2013;<lpage>20</lpage>. doi: <pub-id pub-id-type="doi">10.1007/s12083-024-01781-0</pub-id></citation></ref>
<ref id="ref13"><citation citation-type="journal"><person-group person-group-type="author"><name><surname>Singh</surname><given-names>R. D.</given-names></name> <name><surname>Aggarwal</surname><given-names>N.</given-names></name></person-group> (<year>2018</year>). <article-title>Video content authentication techniques: a comprehensive survey</article-title>. <source>Multimedia Systems</source> <volume>24</volume>, <fpage>211</fpage>&#x2013;<lpage>240</lpage>. doi: <pub-id pub-id-type="doi">10.1007/s00530-017-0538-9</pub-id></citation></ref>
<ref id="ref14"><citation citation-type="journal"><person-group person-group-type="author"><name><surname>Wang</surname><given-names>M.</given-names></name> <name><surname>Zhu</surname><given-names>T.</given-names></name> <name><surname>Zuo</surname><given-names>X.</given-names></name> <name><surname>Yang</surname><given-names>M.</given-names></name> <name><surname>Yu</surname><given-names>S.</given-names></name> <name><surname>Zhou</surname><given-names>W.</given-names></name></person-group> (<year>2023</year>). <article-title>Differentially private crowdsourcing with the public and private blockchain</article-title>. <source>IEEE Internet Things J.</source> <volume>10</volume>, <fpage>8918</fpage>&#x2013;<lpage>8930</lpage>. doi: <pub-id pub-id-type="doi">10.1109/JIOT.2022.3233360</pub-id></citation></ref>
<ref id="ref15"><citation citation-type="journal"><person-group person-group-type="author"><name><surname>Wu</surname><given-names>X.</given-names></name> <name><surname>Ma</surname><given-names>P.</given-names></name> <name><surname>Jin</surname><given-names>Z.</given-names></name> <name><surname>Wu</surname><given-names>Y.</given-names></name> <name><surname>Han</surname><given-names>W.</given-names></name> <name><surname>Ou</surname><given-names>W.</given-names></name></person-group> (<year>2022</year>). <article-title>A novel zero-watermarking scheme based on nsct-svd and blockchain for video copyright</article-title>. <source>EURASIP J. Wirel. Commun. Netw.</source> <volume>2022</volume>:<fpage>20</fpage>.</citation></ref>
<ref id="ref16"><citation citation-type="journal"><person-group person-group-type="author"><name><surname>Yang</surname><given-names>R.</given-names></name> <name><surname>Wakefield</surname><given-names>R.</given-names></name> <name><surname>Lyu</surname><given-names>S.</given-names></name> <name><surname>Jayasuriya</surname><given-names>S.</given-names></name> <name><surname>Han</surname><given-names>F.</given-names></name> <name><surname>Yi</surname><given-names>X.</given-names></name> <etal/></person-group>. (<year>2020</year>). <article-title>Public and private blockchain in construction business process and information integration</article-title>. <source>Autom. Constr.</source> <volume>118</volume>:<fpage>103276</fpage>. doi: <pub-id pub-id-type="doi">10.1016/j.autcon.2020.103276</pub-id></citation></ref>
<ref id="ref17"><citation citation-type="journal"><person-group person-group-type="author"><name><surname>Yu</surname><given-names>M.</given-names></name> <name><surname>Tang</surname><given-names>Z.</given-names></name> <name><surname>Zhang</surname><given-names>X.</given-names></name> <name><surname>Zhong</surname><given-names>B.</given-names></name> <name><surname>Zhang</surname><given-names>X.</given-names></name></person-group> (<year>2022</year>). <article-title>Perceptual hashing with complementary color wavelet transform and compressed sensing for reduced-reference image quality assessment</article-title>. <source>IEEE Trans. Circuits Syst. Video Technol.</source> <volume>32</volume>, <fpage>7559</fpage>&#x2013;<lpage>7574</lpage>. doi: <pub-id pub-id-type="doi">10.1109/TCSVT.2022.3190273</pub-id></citation></ref>
</ref-list>
</back>
</article>