A hierarchical watermark binding method and system based on the OPC collaborative creation platform

By using the hierarchical watermark binding method of the OPC collaborative creation platform, an invisible digital copyright watermark is generated and associated with the creation trace data, which solves the problem of broken chain of ownership tracing in copyright protection in collaborative creation scenarios and provides a continuous and verifiable basis for determining copyright ownership.

CN123116227APending Publication Date: 2026-11-17JIANGSU CUDATEC TECH CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202611272720.2
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2026-08-21
Publication Date
2026-11-17

AI Technical Summary

Technical Problem

In collaborative creation scenarios, existing technologies lack the ability to record intermediate data generated during the creation process, leading to a break in the chain of ownership tracing for copyright protection.

Method used

By using the tiered watermarking binding method of the OPC collaborative creation platform, an invisible digital copyright watermark is generated. Combined with creative trace data, the relationship between the work and the traces is established, providing a complete chain of evidence for the creative process.

Benefits of technology

This ensures that copyright ownership determination has continuous and verifiable traceability, solving the problem of broken links in copyright protection caused by the lack of evidence of process creation.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN123116227A_ABST
    Figure CN123116227A_ABST
Patent Text Reader

Abstract

This invention discloses a hierarchical watermark binding method and system based on the OPC collaborative creation platform, relating to the field of digital copyright protection. The method includes: a creator submitting a formally delivered work to the OPC collaborative creation platform and obtaining corresponding creation trace data within the platform; classifying and filtering creation status based on the trace data to generate valid creation trace data; establishing a unique binding relationship between the formally delivered work and the valid creation trace data, generating a binding index; making differentiated watermark embedding decisions based on the watermark binding information corresponding to the formally delivered work to generate an invisible digital copyright watermark; embedding the invisible digital copyright watermark into the formally delivered work, and establishing a correlation between the invisible digital copyright watermark, the binding index, and the valid creation trace data. This application solves the technical problem of broken ownership tracing caused by the lack of process-based creation evidence in existing collaborative creation scenarios.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This application relates to the field of digital copyright protection, and in particular to a hierarchical watermark binding method and system based on the OPC collaborative creation platform. Background Technology

[0002] The tracing of copyright ownership and the determination of original attribution in the field of digital content creation are fundamental issues that urgently need to be addressed in collaborative creation scenarios. Current industry practices mainly include two forms: First, creators submit the final product file to a third-party copyright registration agency after completion, and the agency issues a formal registration certificate as preliminary proof of rights. Second, some creation platforms or legal evidence preservation platforms adopt a single evidence preservation model based on hash values, that is, calculating the hash value of the final work file uploaded by the creator and storing it in a blockchain or trusted timestamp service to prove that a certain version of the file existed at a certain point in time. However, these existing methods only preserve the final form after the creation is completed, completely ignoring the intermediate data generated during the creation process. This results in a lack of objective records that can fully reflect the evolution of the creation process as supporting evidence when ownership disputes occur, making it difficult to effectively prove the original source and evolution path of the idea.

[0003] At present, copyright protection in collaborative creation scenarios faces technical challenges due to the lack of evidence of the creative process, leading to a break in the chain of ownership tracing. Summary of the Invention

[0004] This application provides a hierarchical watermark binding method and system based on the OPC collaborative creation platform. By submitting works and obtaining creative traces, the traces are hierarchically filtered to generate valid traces. The works are bound to the valid traces and an index is generated. Watermarks are generated based on the type of works. Finally, the watermarks are embedded and the relationship between the watermarks, the index, and the traces is established. These technical means solve the technical problem of the broken chain of ownership tracing caused by the lack of process creation evidence in the existing collaborative creation scenario. It achieves the technical effect of providing a complete chain of evidence for the creation process and ensuring that the determination of copyright ownership has continuous and verifiable traceability basis.

[0005] This application provides a hierarchical watermark binding method based on the OPC collaborative creation platform, comprising: a creator submitting a formally delivered work to the OPC collaborative creation platform and obtaining creation trace data within the platform corresponding to the formally delivered work; performing hierarchical filtering of creation status based on the creation trace data within the platform to generate valid creation trace data; establishing a unique binding relationship between the formally delivered work and the valid creation trace data, and generating a binding index based on the unique binding relationship; obtaining watermark binding information corresponding to the formally delivered work, and making differentiated watermark embedding decisions based on the watermark binding information to generate an invisible digital copyright watermark; embedding the invisible digital copyright watermark into the formally delivered work, and establishing an association relationship between the invisible digital copyright watermark, the binding index, and the valid creation trace data.

[0006] In a possible implementation, the creation status is graded and filtered based on the creation trace data within the platform to generate valid creation trace data, and the following processing is performed: multiple creation status parameters corresponding to the creation trace data within the platform are collected; it is determined whether the multiple creation status parameters meet the predetermined creation status, and multiple creation status verification results are obtained; the creation trace data within the platform is filtered based on the multiple creation status verification results to generate the valid creation trace data.

[0007] In a possible implementation, a differentiated watermark embedding decision is made based on the watermark binding information to generate an invisible digital copyright watermark, and the following processes are performed: identifying the work type of the officially delivered work; inputting the work type into a differentiated watermark embedding decision library to obtain a target digital watermark embedding strategy; and obtaining the invisible digital copyright watermark based on the watermark binding information and the target digital watermark embedding strategy.

[0008] In one possible implementation, the creator submits a formally delivered work to the OPC collaborative creation platform and performs the following processing: performs copyright compliance verification on the formally delivered work and obtains the copyright verification result; if the copyright verification result is passed, generates a watermark embedding instruction.

[0009] In a possible implementation, the following processing is performed: receiving a copyright dispute request sent to the OPC collaborative creation platform; tracing back the creation process based on the copyright dispute request to generate copyright traceability evidence data; inputting the copyright traceability evidence data into the AI ​​copyright intelligent comparison module built into the OPC collaborative creation platform to obtain preliminary analysis results of the copyright dispute; and performing multi-dimensional evidence cross-validation based on the preliminary analysis results of the copyright dispute to generate a copyright dispute analysis report.

[0010] In a possible implementation, the following processing is performed: the differentiated watermark embedding decision library includes watermark embedding schemes for text works, image works, video works, and audio works.

[0011] In a possible implementation, the following processing is performed: the watermark binding information includes the creator ID, submission time, OPC platform batch number, and creation process number.

[0012] This application also provides a hierarchical watermark binding system based on the OPC collaborative creation platform, comprising: a work submission module for creators to submit officially delivered works to the OPC collaborative creation platform and obtain creation trace data within the platform corresponding to the officially delivered works; a trace hierarchical filtering module for hierarchical filtering of creation status based on the creation trace data within the platform and generating valid creation trace data; a binding index generation module for establishing a unique binding relationship between the officially delivered works and the valid creation trace data, and generating a binding index based on the unique binding relationship; a watermark differentiation decision module for obtaining watermark binding information corresponding to the officially delivered works and making differentiated watermark embedding decisions based on the watermark binding information to generate an invisible digital copyright watermark; and a watermark embedding association module for embedding the invisible digital copyright watermark into the officially delivered works and establishing an association relationship between the invisible digital copyright watermark, the binding index, and the valid creation trace data.

[0013] The proposed hierarchical watermark binding method and system based on the OPC collaborative creation platform involves the following steps: First, the creator submits a formally delivered work to the OPC collaborative creation platform, obtaining corresponding creation trace data within the platform. Then, the creation status is hierarchically filtered based on this data to generate valid creation trace data. Next, a unique binding relationship is established between the formally delivered work and the valid creation trace data, and a binding index is generated based on this unique binding relationship. Then, watermark binding information corresponding to the formally delivered work is obtained, and a differentiated watermark embedding decision is made based on this binding information to generate an invisible digital copyright watermark. Finally, the invisible digital copyright watermark is embedded into the formally delivered work, establishing a correlation between the invisible digital copyright watermark, the binding index, and the valid creation trace data. Through this process, the proposed method and system achieve the technical effect of providing a complete chain of evidence for the creation process and ensuring that copyright ownership determination has continuous and verifiable traceability evidence. Attached Figure Description

[0014] To more clearly illustrate the technical solutions of the embodiments of the present invention, the accompanying drawings of the embodiments of the present invention will be briefly described below. Flowcharts are used in this application to illustrate the operations performed by the system according to the embodiments of the present application. It should be understood that the preceding or following operations are not necessarily performed precisely in sequence. Instead, various steps can be processed in reverse order or simultaneously as needed. Furthermore, other operations can be added to these processes, or one or more steps can be removed from these processes.

[0015] Figure 1 This is a flowchart illustrating the hierarchical watermark binding method based on the OPC collaborative authoring platform provided in this application embodiment.

[0016] Figure 2 This is a schematic diagram of the structure of a hierarchical watermark binding system based on the OPC collaborative authoring platform provided in an embodiment of this application.

[0017] Figure labeling: 10 for submission module, 20 for trace classification and screening module, 30 for binding index generation module, 40 for watermark differentiation decision module, and 50 for watermark embedding association module. Detailed Implementation

[0018] To further illustrate the technical means and effects of the present invention in achieving its intended purpose, the following detailed description of the specific implementation methods, structures, features, and effects of the present invention, in conjunction with the accompanying drawings and preferred embodiments, is provided below.

[0019] This application provides a hierarchical watermark binding method based on an OPC collaborative authoring platform, such as... Figure 1 As shown, the method includes: Step S100: The creator submits the officially delivered work to the OPC collaborative creation platform and obtains the creation trace data within the platform corresponding to the officially delivered work.

[0020] Specifically, after completing their digital content creation locally, creators submit a formal submission request to the OPC collaborative creation platform's server via a client. This request uses the Hypertext Transfer Protocol (HTTP) for data transmission, and the request body contains the formally submitted work file and its metadata, including the work name, work type, and creator identifier. Upon receiving the submission request, the OPC collaborative creation platform's server receives and temporarily stores the formally submitted work file. Simultaneously, based on the creator's identifier, it queries the platform's operation log database to retrieve all of the creator's operations on the platform since the start of the current creation project. The operation log database is implemented using a relational database and stores the creator's identifier, operation type, operation object, operation time, and operation content. The server then executes a structured query language query using the creator's identifier and project number as joint query conditions to retrieve all of the creator's operations during the current creation project, including submission records, modification records, view records, and discussion participation records. The server will store all retrieved operation records as the creation trace data within the platform corresponding to the officially delivered work in the platform's temporary storage area, and store the officially delivered work file in the platform's official work storage area, generating a unique work identifier number for the officially delivered work within the platform.

[0021] In one possible implementation, the creator submits a formally delivered work to the OPC collaborative creation platform. Step S100 further includes step S110, which verifies the copyright compliance of the formally delivered work and obtains the copyright verification result. Specifically, after receiving the formally delivered work but before generating the watermark embedding instruction, the OPC collaborative creation platform's server calls the platform's built-in copyright compliance verification module to perform copyright verification on the formally delivered work. The copyright compliance verification module includes a material source verification submodule and an overseas copyright adaptation verification submodule. The verification process of the material source verification submodule is as follows: The server reads the list of external material identifiers referenced in the formally delivered work file. This list of external material identifiers is marked by the creator when the creator submits the work or is automatically generated by the platform. For each material identifier in the list of external material identifiers, the server queries the platform's built-in authorized material database. This authorized material database stores authorization records of legally authorized external materials. Each authorization record includes the material identifier, licensor information, scope of authorization, and validity period of authorization. If the material identifier to be verified has a corresponding record in the authorized material database and the current system date is within the authorization validity period, the verification status of the material is marked as passed; if the material identifier to be verified does not have a corresponding record in the authorized material database or the current system date is not within the authorization validity period, the verification status of the material is marked as failed. The verification process of the overseas copyright adaptation verification submodule is as follows: The server obtains the target distribution region information of the officially delivered work. This target distribution region information is selected by the creator from the region option list provided by the platform when submitting. Based on the target distribution region information, the server retrieves the copyright restriction rule list corresponding to that region from the platform's built-in overseas copyright rule database. This copyright restriction rule list includes character image characteristics, plot elements, and voice features prohibited in that region. The server matches the digital content of the officially delivered work file with each prohibited rule in the copyright restriction rule list. If no prohibited rule is matched in the digital content of the officially delivered work, the overseas copyright adaptation verification passes; if at least one prohibited rule is matched, the overseas copyright adaptation verification fails. When the source material verification submodule shows that all materials are marked as passed and the overseas copyright adaptation verification submodule also shows that it is passed, the copyright compliance verification module outputs "pass" as the copyright verification result; otherwise, it outputs "fail" as the copyright verification result.

[0022] Step S120: If the copyright verification result is successful, a watermark embedding instruction is generated. Specifically, the server judges the copyright verification result output in step S110. If the copyright verification result is successful, the server generates a watermark embedding instruction, which is sent to the platform's watermark embedding service module in the form of a message queue message. This watermark embedding instruction contains the unique work identifier of the officially delivered work within the platform and the storage path of the officially delivered work file. If the copyright verification result is unsuccessful, the server generates a copyright verification failure notification, returns the verification failure result and the corresponding failure reason list to the client used by the creator through the platform's message push service, ends the submission process, and does not proceed to the subsequent watermark embedding steps.

[0023] Step S200: Based on the creation trace data within the platform, perform creation status classification and filtering to generate valid creation trace data.

[0024] Specifically, the server reads the creation trace data corresponding to the officially delivered work obtained in step S100 from the platform's temporary storage area. The server performs a creation status hierarchical filtering operation on each operation record in the creation trace data, specifically determining whether the operation record meets the predetermined creation status based on the creation status parameters corresponding to each record. The server marks operation records that meet the predetermined creation status as valid records and marks those that do not as invalid records and discards them, not writing them into the valid creation trace data storage area. After filtering, the server arranges all marked valid operation records in chronological order of operation time, combining them into valid creation trace data, storing it in the platform's official trace storage area, and assigning a unique trace data identifier to each valid creation trace data.

[0025] In one possible implementation, the creation status is graded and filtered based on the creation trace data within the platform to generate valid creation trace data. Step S200 further includes step S210, which involves collecting multiple creation status parameters corresponding to the creation trace data within the platform. Specifically, for each operation record in the creation trace data within the platform obtained in step S100, the server collects multiple creation status parameters corresponding to that operation record. The collection method for creation status parameters is as follows: the server reads the values ​​of each field in the data structure of the operation record. For the submission flag parameter, the server reads the operation type field in the operation record. If the operation type field is "submit", the submission flag parameter is true; otherwise, it is false. For the version completeness score parameter, the server reads the metadata of the work version corresponding to the operation record from the platform's work version management database. This metadata includes a core process flag, a key module flag, and a technical route flag. The values ​​of all three flags are 0 or 1, where 1 indicates that the element has been completed in the version, and 0 indicates that the element has not been completed in the version. The server adds the values ​​of the core process marker, the key module marker, and the technical route marker, then divides the sum by 3. The resulting value is used as the version completeness scoring parameter for the corresponding operation record. For the "Entering the Collaborative Review Stage" marker, the server reads the review status field of the work version corresponding to the operation record in the platform's collaborative review module. If the work version has entered the collaborative review stage, the "Entering the Collaborative Review Stage" marker is set to true; otherwise, it is set to false.

[0026] Step S220: Determine whether the multiple creation status parameters meet the predetermined creation status and obtain multiple creation status verification results. Specifically, the server compares each creation status parameter collected in step S210 with the judgment conditions corresponding to the predetermined creation status. The predetermined creation status includes the following requirements: the submission marker parameter is true, and the collaborative review stage marker parameter is true. The server performs the following judgment on each operation record: if the submission marker parameter and the collaborative review stage marker parameter of the operation record are both true, then the operation record meets the predetermined creation status, and the corresponding creation status verification result is passed; otherwise, the operation record does not meet the predetermined creation status, and the corresponding creation status verification result is failed. The version integrity score parameter is only used as auxiliary record information in this step and does not participate in the judgment conditions of the predetermined creation status.

[0027] Step S230: The creation trace data within the platform is filtered based on the multiple creation status verification results to generate the valid creation trace data. Specifically, the server filters the creation trace data within the platform based on the creation status verification results corresponding to each operation record output in step S220. The server iterates through each operation record in the creation trace data within the platform. If the creation status verification result of the operation record is passed, the operation record is retained and copied to the valid creation trace data set; if the creation status verification result of the operation record is failed, the operation record is discarded and not copied to the valid creation trace data set. The server further performs deduplication on the retained operation records: if multiple operation records have the same operation timestamp and the same operation type, the server only retains the first record and deletes the remaining duplicate records. After filtering and deduplication, the server sorts the operation records in the valid creation trace data set according to the operation timestamp from earliest to latest to generate the final valid creation trace data.

[0028] Step S300: Establish a unique binding relationship between the formally delivered work and the valid creative trace data, and generate a binding index based on the unique binding relationship.

[0029] Specifically, the server retrieves the unique work identifier corresponding to the officially delivered work stored in step S100 from the platform's official work storage area, and the trace data identifier corresponding to the valid creation trace data generated in step S230 from the platform's official trace storage area. The server creates a new binding record in the platform's binding relationship database, which includes the following fields: unique work identifier, trace data identifier, and binding creation timestamp. The binding creation timestamp is generated by the server reading the current system time. After the binding record is created, the server generates a binding index based on this record. The binding index is constructed by concatenating the unique work identifier and the trace data identifier according to a preset format: unique work identifier. Trace data identifier. The server stores this binding index in the platform's index cache, and simultaneously writes this binding index as the primary key for join queries into the binding relationship database.

[0030] Step S400: Obtain the watermark binding information corresponding to the officially delivered work, and make a differentiated watermark embedding decision based on the watermark binding information to generate an invisible digital copyright watermark; wherein, the watermark binding information includes creator ID, submission time, OPC platform batch number and creation process number.

[0031] Specifically, the server retrieves the creator's identity identifier from the platform's user information database, the submission timestamp of the officially delivered work from the platform's operation log database, the OPC platform batch number to which the officially delivered work belongs from the platform's batch management module, and the creation process number corresponding to the officially delivered work from the platform's process management module. The server combines the creator's identity identifier, submission timestamp, OPC platform batch number, and creation process number into watermark binding information according to a preset data structure. The data structure of this watermark binding information is a set of key-value pairs, containing four keys: creator identifier key, submission time key, batch number key, and process number key, with corresponding values ​​being the four values ​​retrieved above. After obtaining the watermark binding information, the server identifies the file type of the officially delivered work, selects the corresponding watermark embedding scheme from the differentiated watermark embedding decision library based on the identification result, and then converts the watermark binding information into a binary data stream of an invisible digital copyright watermark according to the scheme.

[0032] In one possible implementation, a differentiated watermark embedding decision is made based on the watermark binding information to generate an invisible digital copyright watermark. Step S400 further includes step S410, identifying the work type of the officially delivered work. Specifically, the server reads the file extension and file header identifier of the officially delivered work file to identify the work type. The server first reads the file extension. If the file extension is "docx", "doc", "txt", "pdf", or "rtf", the server further reads the first four bytes of the file header and confirms them against the platform's built-in file format signature library. The file format signature library stores standard header hexadecimal signatures for various file formats. If the recognition result of the extension and the file header signature are consistent, the server determines the work type of the officially delivered work to be text. If the file extension is "jpg", "jpeg", "png", "bmp", "gif", or "tiff", the server further reads the image format signature corresponding to the file header, confirms it against the file format signature library, and then determines the work type of the officially delivered work to be image. If the filename extension is "mp4", "avi", "mov", "wmv", or "flv", the server further reads the video format signature corresponding to the file header, confirms it against the file format signature library, and determines the work type of the officially delivered work as a video. If the filename extension is "mp3", "wav", "aac", "flac", or "ogg", the server further reads the audio format signature corresponding to the file header, confirms it against the file format signature library, and determines the work type of the officially delivered work as an audio. If none of the above types match, the server determines the work type of the officially delivered work as another type, terminates the watermark embedding process, and returns a notification message indicating that the type is not supported.

[0033] Step S420: Input the work type into the differentiated watermark embedding decision library to obtain the target digital watermark embedding strategy; wherein, the differentiated watermark embedding decision library includes watermark embedding schemes for text works, image works, video works, and audio works. Specifically, the server uses the work type identified in step S410 as the query key and inputs it into the differentiated watermark embedding decision library. The differentiated watermark embedding decision library is stored in the platform's relational database and contains a strategy mapping table, which includes a work type field and a strategy identifier field. The server executes a structured query language query statement, using the work type as the query condition, to retrieve the corresponding strategy identifier from the strategy mapping table. If the work type is text, the retrieved strategy identifier points to a text work watermark embedding scheme. If the work type is image, the retrieved strategy identifier points to an image work watermark embedding scheme. If the work type is video, the retrieved strategy identifier points to a video work watermark embedding scheme. If the work type is audio, the retrieved strategy identifier points to an audio work watermark embedding scheme. The server reads the corresponding policy configuration file from the platform's policy storage area based on the retrieved policy identifier. The policy configuration file contains the embedding algorithm name, embedding strength parameter, and embedding position parameter. The server uses this policy configuration file as the target digital watermark embedding policy.

[0034] Step S430: Based on the watermark binding information, the invisible digital copyright watermark is obtained according to the target digital watermark embedding strategy. Specifically, the server encodes and converts the watermark binding information obtained in step S400 according to the target digital watermark embedding strategy obtained in step S420 to generate the invisible digital copyright watermark. The specific encoding and conversion methods are executed according to the work type pointed to by the target digital watermark embedding strategy: If the target digital watermark embedding strategy is a text-based watermark embedding scheme, the server converts the watermark binding information into a binary bit string. This binary bit string is generated as follows: each character of the creator's identity is converted into a Unicode encoding value; the submission timestamp is converted into the number of milliseconds elapsed from Greenwich Mean Time, January 1, 1970, 00:00:00 to the submission time; and the OPC platform batch number and creation process number are converted into decimal numeric strings. Then, the binary representations of these four parts are concatenated end-to-end according to the data structure order of the watermark binding information to form a complete binary bit string. The server uses this binary bit string as the invisible digital copyright watermark to be embedded.

[0035] If the target digital watermark embedding strategy is an image-based watermark embedding scheme, the server converts the watermark binding information into a two-dimensional binary matrix. The two-dimensional binary matrix is ​​generated as follows: the watermark binding information is converted into a binary bit string according to the data structure sequence in step S400; then, the binary bit string is padded with zeros to make its length equal to the square of a preset integer N; finally, the zero-padded binary bit string is arranged into an N-row, N-column two-dimensional binary matrix. The server uses this two-dimensional binary matrix as the invisible digital copyright watermark to be embedded.

[0036] If the target digital watermark embedding strategy is for video works, the server converts the watermark binding information into a binary bit string sequence. This binary bit string sequence is generated as follows: the watermark binding information is converted into a binary bit string, and then the binary bit string is grouped according to a preset bit group length, with each group serving as a watermark unit. The groups are arranged in their original order to form the binary bit string sequence. The server uses this binary bit string sequence as the invisible digital copyright watermark to be embedded.

[0037] If the target digital watermark embedding strategy is for audio works, the server converts the watermark binding information into a binary bit string. This binary bit string is generated in the same way as the conversion method used in text-based watermark embedding schemes. The server then uses this binary bit string as the invisible digital copyright watermark to be embedded.

[0038] Step S500: Embed the invisible digital copyright watermark into the officially delivered work, and establish the association between the invisible digital copyright watermark, the binding index, and the valid creative trace data.

[0039] Specifically, the server embeds the invisible digital copyright watermark generated in step S430 into the officially delivered work file based on the embedding algorithm and embedding parameters specified in the target digital watermark embedding strategy obtained in step S420. The specific embedding method varies depending on the work type. If the final delivered work is text-based, the server uses a text semantic fingerprint watermarking method for embedding. The server performs word segmentation on the text content of the final delivered work file, obtaining a word sequence. For each word in the word sequence, the server queries the platform's built-in synonym replacement encoding table. This table contains multiple sets of synonyms, each synonym in a preset order corresponding to a binary encoding value of 0 or 1. The server, according to each bit of the binary bit string generated in step S430, selects a synonym from the synonym set corresponding to the current word that matches the encoding value of that bit to replace the original word. If the current word is not in the synonym replacement encoding table, it skips that word and continues processing the next word without embedding any bits. The server iterates through all bits of the binary bit string and the words in the word sequence to complete the embedding of all watermark bits.

[0040] If the final delivered work is an image, the server uses a frequency domain invisible watermarking method for embedding. The server performs a discrete cosine transform on the pixel matrix of the final delivered work file to obtain a frequency domain coefficient matrix. The server selects a number of coefficient positions from the mid-frequency region of the frequency domain coefficient matrix equal to the total number of elements in the two-dimensional binary matrix generated in step S430, and determines the coefficient position corresponding to each watermark bit according to a preset position mapping table. For each element value in the two-dimensional binary matrix, the server modifies the frequency domain coefficient value at the corresponding coefficient position according to the embedding strength parameter specified in the target digital watermark embedding strategy: if the watermark bit is 1, the server increases the embedding strength parameter value of the coefficient; if the watermark bit is 0, the server decreases the embedding strength parameter value of the coefficient. The embedding strength parameter is a preset value in the target digital watermark embedding strategy. For example, the embedding strength parameter can be set to 5% of the average value of the coefficients in the mid-frequency region of the frequency domain coefficient matrix. After all watermark bits are embedded, the server performs an inverse discrete cosine transform on the modified frequency domain coefficient matrix to obtain the pixel matrix with the embedded watermark, and encodes the pixel matrix into an image file format for output.

[0041] If the final delivered work is a video, the server uses inter-frame watermarking for embedding. The server reads the video frame sequence of the final delivered work file in chronological order to obtain a frame sequence. The server selects keyframes from the frame sequence at preset frame intervals; for example, the frame interval can be set to select one keyframe every 10 frames. The server embeds each watermark unit in the binary bit string sequence generated in step S430 into each selected keyframe sequentially, with each watermark unit embedded in one keyframe. The embedding method within keyframes is the same as the frequency domain invisible watermark embedding method for image-based works. After embedding, the server recombines the modified keyframes and the unmodified non-keyframes in the original chronological order to form a video frame sequence, which is then encoded into a video file format for output.

[0042] If the final delivered work is audio, the server uses audio spectrum watermarking for embedding. The server performs a short-time Fourier transform on the audio signal of the final delivered work file to obtain a time-spectrum matrix. The server selects coefficient positions from the time-spectrum matrix within a frequency range imperceptible to the human ear (frequency range above 2000Hz and below 20000Hz). The server sequentially embeds each bit of the binary bit string generated in step S430 into the selected coefficient positions, using the same embedding method as for image files, modifying the coefficient values. For example, the embedding strength parameter can be set to 3% of the average value of the coefficients in this imperceptible frequency range. After all watermark bits are embedded, the server performs an inverse short-time Fourier transform on the modified time-spectrum matrix to obtain the watermarked audio signal, which is then encoded into an audio file format for output.

[0043] After the watermark is embedded, the server obtains the storage path of the officially delivered work file after the watermark is embedded. The server creates a relationship record in the platform's relationship database, which includes the following fields: the hash value of the binary data stream of the invisible digital copyright watermark, the binding index generated in step S300, the trace data identifier of the valid creative trace data generated in step S230, and the storage path of the officially delivered work file after the watermark is embedded. The server writes this relationship record to the relationship database, and simultaneously submits the hash value of the binary data stream of the invisible digital copyright watermark and the unique work identifier of the officially delivered work to the platform's unified watermark index for archiving and storage.

[0044] In one possible implementation, the method further includes step S600, receiving a copyright dispute request sent to the OPC collaborative creation platform. Specifically, the server of the OPC collaborative creation platform receives the copyright dispute request through the dispute acceptance interface provided by the platform. The copyright dispute request is sent by the requesting party through a client, transmitted using the Hypertext Transfer Protocol (HTTP), and the request body is in a structured data format, containing the following fields: the identity identifier of the dispute initiator, the unique work identifier number of the disputed work, the dispute type, the dispute description, and the requesting party's electronic signature. After receiving the copyright dispute request, the server verifies the identity identifier of the requesting party, confirming that the user corresponding to the identity identifier is a valid registered user of the platform by querying the platform's user information database. After successful identity verification, the server stores the copyright dispute request in the platform's dispute management database, assigns a unique dispute number to the request, and records the receipt timestamp.

[0045] Step S700: Based on the copyright dispute request, the creation process is traced back to generate copyright tracing evidence data. Specifically, the server queries the binding index corresponding to the unique work identifier of the disputed work in the copyright dispute request received in step S600 from the platform's binding relationship database. The server reads the valid creation trace data generated in step S230 from the platform's official trace storage area based on the trace data identifier in the binding index. The server queries the hash value of the binary data stream of the invisible digital copyright watermark corresponding to the work from the unified watermark index library based on the unique work identifier in the binding index. The server queries all timestamp records corresponding to the unique work identifier of the disputed work from the platform's operation log database, including submission timestamps, modification timestamps, and viewing timestamps in the viewing records. The server combines the retrieved valid creation trace data, the hash value of the invisible digital copyright watermark, and the timestamp records according to a unified data structure to form copyright tracing evidence data. The copyright tracing evidence data adopts a key-value pair data structure, containing trace data keys, watermark hash keys, and timestamp record keys, with corresponding values ​​being the three data items retrieved above. The server stores the combined copyright tracing evidence data in the platform's disputed evidence temporary storage area.

[0046] Step S800: Input the copyright tracing evidence data into the AI ​​copyright intelligent comparison module built into the OPC collaborative creation platform to obtain preliminary analysis results of the copyright dispute. Specifically, the server uses the copyright tracing evidence data generated in step S700 as input and passes it to the AI ​​copyright intelligent comparison module built into the platform. The AI ​​copyright intelligent comparison module includes a work feature extraction submodule, a similarity calculation submodule, and a timeline logical consistency judgment submodule. The work feature extraction submodule calls the corresponding feature extraction algorithm according to the type of the disputed work. If the work type is text, the feature extraction submodule uses the word frequency and inverse document frequency vectorization algorithm to convert the text content of the work into a numerical feature vector. If the work type is image, the feature extraction submodule uses the directional gradient histogram algorithm to convert the image pixel matrix into a gradient direction feature vector. If the work type is video, the feature extraction submodule uses the three-dimensional spatiotemporal gradient histogram algorithm to convert the video frame sequence into a spatiotemporal feature vector. If the work type is audio, the feature extraction submodule uses the Mel frequency cepstral coefficient algorithm to convert the audio signal into a spectral feature vector. The similarity calculation submodule compares the feature vectors of the officially submitted works of both parties in the dispute, calculating the cosine similarity between them. This is achieved by dividing the dot product of the two feature vectors by the product of their magnitudes; the resulting value is used as the work feature similarity score. The timeline logical consistency judgment submodule reads the timestamp records from the copyright tracing evidence data and arranges them chronologically to form an operation timeline sequence. This submodule checks for logical contradictions within the timeline sequence. Logical contradictions include a modification timestamp earlier than the submission timestamp, a timestamp of viewing another's work earlier than the timestamp of that work being submitted to the platform, and two different timestamps for the same operation record. If no such logical contradiction exists, the timeline logical consistency judgment result is consistent; if at least one logical contradiction exists, the result is inconsistent. The AI ​​copyright intelligent comparison module combines the work feature similarity score and the timeline logical consistency judgment result to form a preliminary analysis result of the copyright dispute, outputting it in a structured data format.

[0047] Step S900: Based on the preliminary analysis results of the copyright dispute, perform multi-dimensional evidence cross-verification to generate a copyright dispute analysis report. Specifically, the server reads the valid creative trace data from the copyright tracing evidence data generated in step S700, extracts the operation timestamps and operation types of each operation record from the valid creative trace data, and forms an independent timestamp evidence chain. The server queries the corresponding invisible digital copyright watermark record from the unified watermark index library based on the unique work identifier of the disputed work, obtains the creator identity identifier and submission timestamp stored in the watermark record, and forms an independent watermark evidence chain. The server compares and verifies each timestamp in the timestamp evidence chain with the submission timestamp in the watermark evidence chain: if there is an operation record in the timestamp evidence chain that matches the submission timestamp, the cross-verification result of the time evidence and the watermark evidence is consistent; otherwise, it is inconsistent. The server compares the work feature similarity value in the preliminary analysis results of the copyright dispute output in step S800 with a preset similarity threshold. For example, the preset similarity threshold can be set to 0.8. If the similarity score of the works is greater than or equal to the preset similarity threshold, the similarity judgment result is highly similar; if it is less than the preset similarity threshold, the similarity judgment result is not highly similar. The server summarizes the cross-validation results of timestamp evidence and watermark evidence, the similarity judgment results, and the timeline logical consistency judgment results output in step S800. The server generates a copyright dispute analysis report based on the summarized results. This report includes the following sections: basic dispute information, timeline retrospective records, watermark parsing results, AI similarity comparison data, and multi-dimensional evidence cross-validation conclusions. The server outputs the generated copyright dispute analysis report in a structured data format and stores it in the platform's dispute management database. At the same time, it sends report generation notifications to the dispute initiator and the dispute counterpart through the platform's message push service.

[0048] This application's embodiments address the technical problem of broken ownership tracing caused by the lack of process-based creative evidence in copyright protection under existing collaborative creation scenarios. This is achieved by submitting works and obtaining creative traces, classifying and filtering the traces to generate valid traces, binding works with valid traces and generating indexes, generating watermarks based on work type, and finally embedding the watermarks and establishing the association between watermarks, indexes, and traces. It achieves the technical effect of providing a complete chain of evidence for the creative process and ensuring that the determination of copyright ownership has continuous and verifiable traceability basis.

[0049] In the above text, refer to Figure 1 This paper describes in detail a hierarchical watermark binding method based on an OPC collaborative authoring platform according to an embodiment of the present invention. Next, we will refer to... Figure 2 This invention describes a hierarchical watermark binding system based on an OPC collaborative authoring platform according to an embodiment of the present invention.

[0050] The hierarchical watermark binding system based on the OPC collaborative creation platform according to embodiments of the present invention addresses the technical problem of broken ownership tracing caused by the lack of process-based creative evidence in existing collaborative creation scenarios. It achieves the technical effect of providing a complete chain of evidence for the creative process and ensuring that copyright ownership determination has continuous and verifiable traceability basis. The hierarchical watermark binding system based on the OPC collaborative creation platform includes: a work submission module 10, a trace hierarchical screening module 20, a binding index generation module 30, a watermark differentiation decision module 40, and a watermark embedding association module 50.

[0051] The work submission module 10 is used for creators to submit officially delivered works to the OPC collaborative creation platform and obtain the creation trace data within the platform corresponding to the officially delivered works; the trace classification and filtering module 20 is used to classify and filter creation status according to the creation trace data within the platform and generate valid creation trace data; the binding index generation module 30 is used to establish a unique binding relationship between the officially delivered works and the valid creation trace data, and generate a binding index according to the unique binding relationship; the watermark differentiation decision module 40 is used to obtain the watermark binding information corresponding to the officially delivered works, and make a differentiated watermark embedding decision according to the watermark binding information to generate an invisible digital copyright watermark; the watermark embedding association module 50 is used to embed the invisible digital copyright watermark into the officially delivered works and establish an association relationship between the invisible digital copyright watermark, the binding index and the valid creation trace data.

[0052] The detailed configuration of the trace grading and filtering module 20 is explained as follows: As mentioned above, the trace grading and filtering module 20 performs grading and filtering of creation status based on the creation trace data within the platform to generate valid creation trace data. The trace grading and filtering module 20 may further include: a status parameter acquisition unit for acquiring multiple creation status parameters corresponding to the creation trace data within the platform; a creation status determination unit for determining whether the multiple creation status parameters meet a predetermined creation status and obtaining multiple creation status verification results; and an valid trace filtering unit for filtering the creation trace data within the platform based on the multiple creation status verification results to generate the valid creation trace data.

[0053] The detailed description of the specific configuration of the watermark differentiation decision module 40 is as follows: As mentioned above, the watermark differentiation decision module 40 performs differentiated watermark embedding decisions based on the watermark binding information to generate an invisible digital copyright watermark. The watermark differentiation decision module 40 may further include: a work type identification unit for identifying the work type of the officially delivered work; an embedding strategy matching unit for inputting the work type into the differentiated watermark embedding decision library to obtain a target digital watermark embedding strategy; and a watermark generation unit for obtaining the invisible digital copyright watermark based on the watermark binding information and the target digital watermark embedding strategy.

[0054] The detailed description of the specific configuration of the work submission module 10 is as follows: As mentioned above, when a creator submits a formally delivered work to the OPC collaborative creation platform, the work submission module 10 may further include: a copyright compliance verification unit for performing copyright compliance verification on the formally delivered work and obtaining the copyright verification result; and an embedding instruction triggering unit for generating a watermark embedding instruction if the copyright verification result is passed.

[0055] The system may further include: a dispute request receiving module for receiving copyright dispute requests sent to the OPC collaborative creation platform; a creation process retrospective module for retrospectively analyzing the creation process based on the copyright dispute request and generating copyright traceability evidence data; an AI intelligent comparison module for inputting the copyright traceability evidence data into the AI ​​copyright intelligent comparison module built into the OPC collaborative creation platform to obtain preliminary analysis results of the copyright dispute; and a dispute analysis report generation module for performing multi-dimensional evidence cross-validation based on the preliminary analysis results of the copyright dispute and generating a copyright dispute analysis report.

[0056] The embedding strategy matching unit may further include: the differentiated watermark embedding decision library includes watermark embedding schemes for text works, image works, video works, and audio works.

[0057] The watermark differentiation decision module 40 may further include: the watermark binding information includes creator ID, submission time, OPC platform batch number and creation process number.

[0058] The hierarchical watermark binding system based on the OPC collaborative creation platform provided in this embodiment of the invention can execute the hierarchical watermark binding method based on the OPC collaborative creation platform provided in any embodiment of the invention, and has the corresponding functional modules and beneficial effects of the execution method.

[0059] Although this application makes various references to certain modules in the system according to the embodiments of this application, any number of different modules can be used and run on user terminals and / or servers. The various units and modules included are only divided according to functional logic, but are not limited to the above division, as long as the corresponding functions can be achieved; in addition, the specific names of each functional unit are only for easy distinction between each other and are not used to limit the scope of protection of this invention.

[0060] The above description is merely a preferred embodiment of the present invention and is not intended to limit the present invention in any way. Although the present invention has been disclosed above with reference to preferred embodiments, it is not intended to limit the present invention. Any person skilled in the art can make some modifications or alterations to the above-disclosed technical content to create equivalent embodiments without departing from the scope of the present invention. Any modifications, equivalent changes, and alterations made to the above embodiments based on the technical essence of the present invention without departing from the scope of the present invention shall still fall within the scope of the present invention.

Claims

1. A hierarchical watermark binding method based on an OPC collaborative creation platform, characterized in that, The method includes: Creators submit their officially delivered works to the OPC collaborative creation platform and obtain the creation trace data within the platform corresponding to the officially delivered works. Based on the creation trace data within the platform, the creation status is graded and filtered to generate valid creation trace data; Establish a unique binding relationship between the officially delivered work and the valid creative trace data, and generate a binding index based on the unique binding relationship; Obtain the watermark binding information corresponding to the officially delivered work, and make differentiated watermark embedding decisions based on the watermark binding information to generate an invisible digital copyright watermark; The invisible digital copyright watermark is embedded in the officially delivered work, and a relationship is established between the invisible digital copyright watermark, the binding index, and the valid creative trace data.

2. The hierarchical watermark binding method based on the OPC collaborative creation platform as described in claim 1, characterized in that, Based on the creation trace data within the platform, the creation status is graded and filtered to generate valid creation trace data, including: Collect multiple creation status parameters corresponding to the creation trace data within the platform; Determine whether the multiple creation state parameters meet the predetermined creation state, and obtain the multiple creation state verification results; Based on the results of the multiple creative status checks, the creative trace data within the platform is filtered to generate the valid creative trace data.

3. The hierarchical watermark binding method based on the OPC collaborative creation platform as described in claim 1, characterized in that, Based on the watermark binding information, a differentiated watermark embedding decision is made to generate an invisible digital copyright watermark, including: Identify the type of work in the officially delivered work; Input the work type into the differentiated watermark embedding decision library to obtain the target digital watermark embedding strategy; Based on the watermark binding information, the invisible digital copyright watermark is obtained according to the target digital watermark embedding strategy.

4. The hierarchical watermark binding method based on the OPC collaborative creation platform as described in claim 1, characterized in that, Creators submit their final works to the OPC collaborative creation platform, including: Perform copyright compliance verification on the officially delivered work and obtain the copyright verification results; If the copyright verification result is successful, a watermark embedding instruction is generated.

5. The hierarchical watermark binding method based on the OPC collaborative creation platform as described in claim 1, characterized in that, The method includes: Receive copyright dispute requests sent to the OPC collaborative creation platform; Based on the copyright dispute request, the creation process is traced back to generate copyright traceability evidence data; The copyright traceability evidence data is input into the AI ​​copyright intelligent comparison module built into the OPC collaborative creation platform to obtain preliminary analysis results of copyright disputes; Based on the preliminary analysis results of the copyright dispute, multi-dimensional evidence cross-validation is performed to generate a copyright dispute analysis report.

6. The hierarchical watermark binding method based on the OPC collaborative creation platform as described in claim 3, characterized in that, The differentiated watermark embedding decision library includes watermark embedding schemes for text works, image works, video works, and audio works.

7. The hierarchical watermark binding method based on the OPC collaborative creation platform as described in claim 1, characterized in that, The watermark binding information includes creator ID, submission time, OPC platform batch number, and creation process number.

8. A hierarchical watermark binding system based on an OPC collaborative creation platform, characterized in that, The system is used to implement the hierarchical watermark binding method based on the OPC collaborative authoring platform as described in any one of claims 1-7, and the system comprises: The work submission module is used for creators to submit officially delivered works to the OPC collaborative creation platform and obtain the creation trace data within the platform corresponding to the officially delivered works. The trace classification and filtering module is used to classify and filter the creation status based on the creation trace data in the platform and generate valid creation trace data. The binding index generation module is used to establish a unique binding relationship between the officially delivered work and the valid creative trace data, and to generate a binding index based on the unique binding relationship; The watermark differentiation decision module is used to obtain the watermark binding information corresponding to the officially delivered work, and make a differentiated watermark embedding decision based on the watermark binding information to generate an invisible digital copyright watermark. The watermark embedding association module is used to embed the invisible digital copyright watermark into the officially delivered work and establish an association between the invisible digital copyright watermark, the binding index, and the valid creative trace data.