Data processing method and related device

Abstract

A data processing method, which relates to the field of media applications. The method comprises: acquiring a configuration statement, wherein the configuration statement represents credibility requirements that need to be met by a media asset; and generating a trust configuration file on the basis of the configuration statement, wherein the trust configuration file comprises the configuration statement. The configuration statement comprises a formula or an expression, wherein the formula or expression represents the requirements of a trust factor in a trust credential, the trust factor being a parameter which represents the credibility of the media asset. The requirements for the credibility of a media asset are recorded by means of a trust configuration file, which facilitates the management of the media asset by a platform, an organization or a user, and credibility evaluation can be performed on the media asset by means of the trust configuration file; and by means of issuing the trust configuration file, platform users can conveniently verify the credibility of the media asset.

Description

A data processing method and related equipment Technical Field

[0001] The present application relates to the field of terminal and media applications, and in particular to a data processing method and related equipment. Background Art

[0002] With the increasing popularity of more convenient camera devices like mobile phones, and the development of simple, efficient, and powerful content editing software (e.g., AIGC), the threshold for people to create and modify media is becoming increasingly lower, and they can publish on various social media platforms. However, the modification of media content has exacerbated the spread of misinformation and false information, undermining the credibility of media content as a carrier of information. Especially with the development of AI technology, the generated false content is difficult to distinguish from real content with the naked eye, and what you see is not necessarily "true". Therefore, technology that can help people more effectively judge the credibility of content is crucial.

[0003] For example, in existing implementations, to detect whether media content contains false information, AI detection models are trained using large sets of real and false images. The detection models then determine whether the input images contain features similar to those in the false images to determine whether the images are credible. However, these AI detection models can only verify the credibility of certain specific false content.

[0004] Therefore, there is an urgent need for a method that can provide credibility proof for media content.

[0005] Summary of the Invention

[0006] In a first aspect, the present application provides a data processing method, comprising: obtaining trust information about a media asset by determining whether one or more trust factors of the media asset correspond to indicator requirements, wherein a user can determine the trustworthiness of the media asset based on the trust information. The media asset includes media content, and the media asset also includes at least one of metadata for the media content and a trust record for the media content, and the trust factor is a parameter indicating the trustworthiness of the media asset.

[0007] In one possible implementation, the method further includes generating trusted information of the media asset.

[0008] In one possible implementation, the trust information may be encapsulated as a trust report.

[0009] In one possible implementation, the one or more trust factors are determined based on at least one of the media content, metadata corresponding to the media content, and a trust record corresponding to the media content. For example, the one or more trust factors may be features extracted from the media content, metadata corresponding to the media content, and trust record corresponding to the media content, or data obtained by processing the media content, metadata corresponding to the media content, and trust record corresponding to the media content.

[0010] In one possible implementation, the trust information indicates whether one or more trust factors meet criteria. The trust factors include parameters indicating the trustworthiness of the media asset. For example, in the case of images, metadata features such as the shooting time, shooting location, photographer, camera lens parameters, and shooting parameters can be selected as metadata trust factors.

[0011] Taking images as media content as an example, the image generation method and image editing method in the trust record can be selected as trust factors of the trust record. The image generation method may include, but is not limited to, whether it is generated through AIGC, whether it is generated through a camera, whether it is generated with the assistance of software, whether it is generated through synthetic media, whether the media content can be used to train the model, and the image editing method may include, but is not limited to, rotation, resizing, cropping, content editing, etc.

[0012] Taking the media content as an image as an example, features such as characters, scenes, object types, positional relationships between objects, and image style (e.g., color, light, brightness) in the media content can be selected as trust factors of the media content.

[0013] In a possible implementation, the indicator corresponding to the trust factor is specified in a configuration file, and first trust configuration information can be obtained, where the first trust configuration information includes an indicator that the media asset needs to meet.

[0014] In a possible implementation, one or more trust factors of the media asset may be determined based on at least one of the media content, metadata corresponding to the media content, and a trust record corresponding to the media content.

[0015] In one possible implementation, the one or more trust factors may be encapsulated in a trust credential.

[0016] In a possible implementation, the method further includes: adding the trust information obtained by determining whether each trust factor satisfies an indicator to the trust record.

[0017] By adding the newly generated trust information to the trust record of the media asset, the trustworthiness of the media asset can be further enhanced.

[0018] In a possible implementation, determining whether the one or more trust factors meet an indicator includes determining whether a trust factor in the indicator is included in the one or more trust factors, or determining whether the one or more trust factors include a trust factor in the indicator.

[0019] That is, the indicator may also include a trust factor, and whether the trust factor of the media asset is included in the indicator (that is, whether the indicator includes the trust factor of the media asset) may be used to determine whether the trust factor of the media asset satisfies the indicator.

[0020] In a possible implementation, the trust record includes a trust list; and adding the trusted information to the trust record includes: adding the trusted information to the trust list.

[0021] In a possible implementation, the method further includes: adding the hash value and signature of the trusted information to the trust list.

[0022] In one possible implementation, the method further includes: obtaining indication information of the media asset; and adding the indication information to the trust record, including: adding the trusted information to the trust record corresponding to the media asset indicated by the indication information based on the indication information. When batch processing of trusted information of multiple media assets is required, the indication information of the media assets can be transmitted during the process.

[0023] In a possible implementation, the method further includes: generating a file associated with the media asset based on the trusted information.

[0024] In one possible implementation, the first trust configuration information includes one of multiple trust configuration information, with different trust configuration information indicating different region or user requirements for the media asset. Different trust information can be generated to meet different requirements for different scenarios (e.g., regions or users), thereby meeting trust evaluation requirements in different scenarios.

[0025] In a possible implementation, the action of obtaining one or more trust factors of the media asset is triggered by hardware sensors capturing the media content or software generating the media content.

[0026] For example, images can be captured by a camera carried by the terminal, or new media content can be generated by media content editing software (e.g., AIGC). When the terminal device obtains media content, it also needs to generate corresponding media assets through the media asset management module. Media assets may include metadata, trust records, etc. In an embodiment of the present application, the media asset management module can collect the media content based on hardware sensors, or generate the media content through software, generate trusted information based on the content in the media asset, and add it to the media asset.

[0027] In a possible implementation, before obtaining the one or more trust factors of the media asset, the method further includes: receiving a trust evaluation request for the media content.

[0028] For example, a user may input a trustworthiness assessment request for the media content through a trustworthiness assessment application.

[0029] For example, the terminal side may input a trustworthiness evaluation request for the media content through an interface of a cloud service that provides a trustworthiness evaluation service.

[0030] In a possible implementation, the media content is at least one of an image, a video, or an audio.

[0031] In a second aspect, the present application provides a data processing method, which includes: obtaining a media asset; the media asset includes media content, and the media asset also includes metadata of the media content and at least one of a trust record of the media content; determining one or more trust factors of the media asset, and the one or more trust factors are used to evaluate the credibility of the media asset.

[0032] Therefore, the extraction of the trust factor can be used to evaluate the credibility of the media asset; when performing the credibility evaluation later, there is no need to read the media asset, and only the information from the trust factor needs to be read to evaluate the credibility of the media asset.

[0033] In one possible implementation, the one or more trust factors are encapsulated in a trust credential.

[0034] In a possible implementation, the one or more trust factors are determined based on at least one of the media content, metadata corresponding to the media content, and a trust record corresponding to the media content.

[0035] In one possible implementation, one or more trust factors TM related to the credibility of the media asset can be determined based on the metadata of the media content. For example, TM can be the generation time of the media content, the author name of the media content, the digital content identifier of the media content, the generation location of the media content, information about the device that generated the media content, the media type of the media content, or the generation method (Media Type) of the media content. For example, the information about the device that generated the media content can include the model of the device, the parameters of the camera, etc. The parameters of the camera can include the focal length, sensitivity, exposure, etc. when the camera takes a picture. It should be understood that TM can also include other information such as copyright information and other information used to describe the media content, and this application does not limit this.

[0036] In one possible implementation, one or more trust factors TR related to the credibility of a media asset can be determined based on the trust record of the media content. For example, the trust record may include the time of creation of the media content, the author name of the media content, the digital content identifier of the media content, the location of creation of the media content, information about the device that created the media content, the media editing method, the media type of the media content, or the media type of the media content. For example, information about the device that created the media content may include the device model and camera parameters. Camera parameters may include the focal length, sensitivity, and exposure when the camera captures the image. It should be understood that TR may also include other information describing the media content, such as copyright information, which is not limited to this application. The media generation method may include, but is not limited to, whether the media content was generated using AIGC, whether it was generated using a camera, whether it was generated with software assistance, whether it was generated using synthetic media, whether the media content can be used to train a model, and media editing methods may include, but are not limited to, rotation, resizing, cropping, and content editing. TR may also include a media declaration, including a thumbnail, whether it can be modified, operating permissions, usage permissions, and the source of the second media content.

[0037] In one possible implementation, one or more trust factors TC related to the credibility of a media asset can be determined based on the media content. For example, features such as characters, scenes, object types, positional relationships between objects, and media style (e.g., color, lighting, brightness) in the media content can be selected as trust factors for the media content.

[0038] In one possible implementation, the one or more trust factors are used to determine trust information of the media asset, and the trust information is used to indicate whether the one or more trust factors meet a criterion.

[0039] In one possible implementation, the indicator includes data indicating a trust factor that the media asset must satisfy. For example, if the indicator indicates the creator, the indicator can be either the creator or the creator's name. For example, if the indicator indicates the location where the media was created, the indicator can be either the location or the name of the location. These are not enumerated here.

[0040] In one possible implementation, the trust factor includes a parameter indicating the trustworthiness of the media asset.

[0041] In a possible implementation, the media content is at least one of an image, a video, or an audio.

[0042] In a third aspect, the present application provides a data processing method, comprising: obtaining first media content; generating a modification record of the first media content, wherein the trust record of the first media content comprises: initial information of the first media content, a hard binding of the first media content, and a first digital signature; the first digital signature is a digital signature of first data, and the first data is data determined based on at least the initial information and the hard binding of the first media content. The trust record can be used to trace the source of the media content and can, to a certain extent, help users determine the authenticity of the media content.

[0043] In one possible implementation, the first data is data that is a combination of at least a hard binding of the first media content and initial information of the first media content, or the first data is data that is a combination of at least a hard binding of the initial information (for example, the hash value AIGC.Hash of AI generating AIGC, the hash value Media Type.Hash of the media generation method) and a hard binding of the first media hard binding (for example, the hash value Media Hash 0.Hash of the first media hash value).

[0044] In one possible implementation, the first data may also be a first combined hash value (Hash(TD)), where the first combined hash value includes a hash value of the initial information of the first media content and the first media hash value. Exemplarily, the first combined hash value includes a hash value of the initial information of the first media content, the first media hash value, and other descriptive information. The other descriptive information may not be other descriptive information in the initial information, for example, information of a tool for generating a Trust Profile or other information describing the initial information of the first media content.

[0045] In a possible implementation, the first data may also be a first combined hash value, which may include a hash value of the hash value of the initial information of the first media content and a hash value of the first media hash value (Media Hash 0.Hash). Exemplarily, the first combined hash value is a hash value of the hash value of the initial information of the first media content, the hash value of the first media hash value, and the hash value of other metadata information. Here, in the case where the initial information of the first media content includes at least two, the hash value of the initial information of the first media content may include the hash value of each of the initial information of the first media content, or the hash value of the initial information of the first media content may include the hash value of all the initial information of the first media content.

[0046] In one possible implementation, the initial information of the media content may refer to the information generated when the media content is generated. Exemplarily, the initial information of the media content includes at least one of the following: the generation time of the media content, the name of the author of the media content, the digital content identifier of the media content, the generation location of the media content, the information of the device that generates the media content, the resolution of the media content, the size of the media content, the media type of the media content, or the generation method (Media Type) of the media content. For example, the information of the device that generates the media content may include the model of the device, the parameters of the camera, etc. The parameters of the camera may include the focal length, sensitivity, exposure, etc. when the camera takes pictures. It should be understood that the initial information of the media content may also include other information such as copyright information and other information used to describe the media content.

[0047] In one possible implementation, media types may include, but are not limited to, images, videos, audios, and graphics. Generation methods may include AI generation and non-AI generation. In one possible approach, the generation method in the initial information may be replaced with an AI generation (AIGC) identifier; for example, when the media content is generated by AI, the value of the AIGC identifier is 1; when the media content is not generated by AI, the value of the AIGC identifier is 0. The author name of the media content may be the name of the creator of the media content or the name of the device used to shoot the media content.

[0048] In a fourth aspect, the present application provides a data processing method, comprising: obtaining a configuration statement, the configuration statement indicating credibility requirements that a media asset must meet; generating a trust profile based on the configuration statement, the trust profile including the configuration statement; the configuration statement including an expression statement, the expression statement including a formula or expression indicating a requirement for a trust factor in a trust credential, the trust factor being a parameter indicating the credibility of the media asset.

[0049] In a possible implementation, the formula or expression is expressed in a JSON formula format.

[0050] In a possible implementation, the method further includes: obtaining metadata of the trust profile; and further generating the trust profile based on the metadata, wherein the trust profile further includes metadata, and the metadata includes a name, issuer, issuance date, and version number of the trust profile.

[0051] In a possible implementation, the name, issuer, and version number of the trust configuration file are expressed in the trust configuration file using a string type.

[0052] In one possible implementation, the trust configuration file is expressed in YAML format.

[0053] In one possible implementation, the media asset includes media content, and the media asset also includes at least one of metadata of the media content and a trust record of the media content; the one or more trust factors are determined based on at least one of the media content, metadata corresponding to the media content, and a trust record corresponding to the media content.

[0054] In a possible implementation, the method further includes: receiving a request from a user for obtaining a trust profile; and sending the trust profile to the user.

[0055] In one possible implementation, the method further includes: in response to a user request, obtaining a target trust profile from a profile library, where the profile library includes multiple trust profiles, and the target profile is a trust profile corresponding to the user; and sending the trust profile to the user includes: sending the target trust profile to the user.

[0056] In one possible implementation, the method further includes storing the trust profile.

[0057] In a fifth aspect, the present application provides a data processing method, comprising: obtaining trust credentials and a trust profile; the trust credentials represent the credibility of a media asset, and the trust profile represents the credibility requirements of the media asset; generating a trust report based on the trust credentials and the trust profile, the trust report comprising report metadata and a report statement, the report metadata recording information describing the trust report, the report metadata comprising information extracted from the trust profile, and the report statement comprising a statement of whether the trust credentials meet the credibility requirements in the trust profile.

[0058] In one possible implementation, the trust credential includes a trust factor, which is a parameter representing the credibility of the media asset. The media asset includes media content, and the media asset also includes metadata of the media content and at least one of a trust record of the media content; the one or more trust factors are determined based on at least one of the media content, the metadata corresponding to the media content, and the trust record corresponding to the media content.

[0059] In a possible implementation, the trust profile includes an expression statement, the expression statement includes a formula or an expression, and the formula or expression represents the requirement of the trust factor in the trust credential;

[0060] The method for generating a trust report according to the trust credential and the trust profile includes:

[0061] Reading the trust factor from the trust credential and reading the expression statement from the trust profile;

[0062] Inputting the trust factor of the trust credential into the formula or expression expressing the statement to determine whether the trust factor satisfies the credibility requirement;

[0063] The trust report is generated according to the conclusion of whether the trust factor meets the credibility requirement.

[0064] In one possible implementation, the trust profile includes configuration metadata, where the configuration metadata records information describing the trust profile, including a name, issuer, issuance date, and version number of the trust profile. Generating a trust report based on the trust profile includes:

[0065] Information is extracted from the configuration metadata to generate the report metadata.

[0066] In a possible implementation, the method further includes: adding the trust report to the trust record of the media asset to obtain a new trust record.

[0067] In a possible implementation, before generating the trust report, the method further includes: receiving a trust evaluation request for the media asset.

[0068] In a possible implementation, after generating the trust report, the method further includes: storing and / or sending the trust report.

[0069] In a possible implementation, the media asset is at least one of an image, a video, or an audio.

[0070] In a sixth aspect, the present application provides a data processing device, comprising:

[0071] An acquisition module, configured to acquire one or more trust factors of a media asset; the media asset comprising at least one of media content, metadata corresponding to the media content, and a trust record corresponding to the media content;

[0072] A processing module is configured to determine whether the one or more trust factors meet an indicator.

[0073] In a possible implementation, the acquisition module is further configured to:

[0074] First trust configuration information is obtained, where the first trust configuration information includes indicators that the media asset must meet.

[0075] In a possible implementation, the one or more trust factors are determined based on at least one of the media content, metadata corresponding to the media content, and a trust record corresponding to the media content.

[0076] In one possible implementation, the one or more trust factors are encapsulated in a trust credential.

[0077] In one possible implementation, the indicator includes data indicating a trust factor that the media asset needs to satisfy.

[0078] In a possible implementation, the processing module is specifically configured to:

[0079] Determine whether the trust factor corresponding to the indicator is included in the one or more trust factors, or determine whether the one or more trust factors include the trust factor corresponding to the indicator.

[0080] In a possible implementation, the processing module is further configured to:

[0081] Generate trust information for the media asset, the trust information being used to indicate whether the one or more trust factors meet an indicator, the trust factor including a parameter indicating the trustworthiness of the media asset. In one possible implementation, the processing module is further configured to:

[0082] The trust information is added to the trust record.

[0083] In one possible implementation, the trust record includes a trust list;

[0084] The processing module is specifically used to:

[0085] Add the trusted information to the trust list.

[0086] In a possible implementation, the acquisition module is further configured to:

[0087] Obtaining information indicating the media asset;

[0088] The processing module is specifically used to:

[0089] According to the indication information, the trusted information is added to the trust record corresponding to the media asset indicated by the indication information.

[0090] In a possible implementation, the trust information is encapsulated in a trust report.

[0091] In a possible implementation, the processing module is further configured to:

[0092] A file associated with the media asset is generated based on the trusted information.

[0093] In a possible implementation, the first trust configuration information includes one of a plurality of trust configuration information, and different trust configuration information indicates that different regions or users need to meet index requirements for the media asset.

[0094] In a possible implementation, the action of obtaining one or more trust factors of the media asset is triggered by hardware sensors capturing the media content or software generating the media content.

[0095] In a possible implementation, before obtaining the multiple indicators and configuration files of the media assets, the obtaining module is further configured to:

[0096] A trustworthiness assessment request for the media content is received.

[0097] In a possible implementation, the media content is at least one of an image, a video, or an audio.

[0098] In a seventh aspect, the present application provides a data processing device, comprising:

[0099] An acquisition module, configured to acquire media assets; the media assets include at least one of media content, metadata corresponding to the media content, and a trust record corresponding to the media content;

[0100] A processing module is configured to determine one or more trust factors of the media asset, wherein the one or more trust factors are used to evaluate the credibility of the media asset.

[0101] In one possible implementation, the one or more trust factors are encapsulated in a trust credential.

[0102] In a possible implementation, the one or more trust factors are determined based on at least one of the media content, metadata corresponding to the media content, and a trust record corresponding to the media content.

[0103] In one possible implementation, the one or more trust factors are used to determine trust information of the media asset, and the trust information is used to indicate whether the one or more trust factors meet a criterion.

[0104] In one possible implementation, the indicator includes a trust factor that the media asset needs to satisfy.

[0105] In one possible implementation, the trust factor includes a parameter indicating the trustworthiness of the media asset.

[0106] In a possible implementation, the media content is at least one of an image, a video, or an audio.

[0107] In an eighth aspect, an embodiment of the present application provides a data processing device, the device comprising:

[0108] An acquisition module, configured to acquire first media content;

[0109] A processing module is used to generate a modification record of the first media content, where the trust record of the first media content includes: initial information of the first media content, a hard binding of the first media content, and a first digital signature; the first digital signature is a digital signature of first data, and the first data is data determined based on at least the initial information and the hard binding of the first media content.

[0110] The modules in the data processing device of the eighth aspect of the present application are also used to execute the methods in other possible implementations of the third aspect.

[0111] In a ninth aspect, an embodiment of the present application provides a data processing device, including:

[0112] An acquisition module, configured to configure a statement, wherein the configuration statement indicates credibility requirements that a media asset needs to meet;

[0113] A processing module is configured to generate a trust profile according to the configuration statement, wherein the trust profile includes the configuration statement.

[0114] In one implementation, the processing module is further configured to receive a request from a user, the request being configured to obtain the trust profile;

[0115] The processing module is further configured to send the trust configuration file to the user.

[0116] In one implementation, the acquisition module is further configured to acquire metadata of the trust profile;

[0117] The processing module further generates the trust profile according to the metadata, where the trust profile also includes the metadata, and the metadata includes the name, issuer, issue date, and version number of the trust profile.

[0118] The modules in the data processing device of the ninth aspect of the present application are also used to execute the methods in other possible implementations of the fourth aspect.

[0119] In a tenth aspect, an embodiment of the present application provides a data processing device, including:

[0120] An acquisition module, configured to acquire a trust credential and a trust profile; the trust credential represents the credibility of the media asset, and the trust profile represents the credibility requirement of the media asset;

[0121] and a processing module configured to generate a trust report based on the trust credential and the trust profile, the trust report comprising report metadata and a report statement, the report metadata recording information describing the trust report, the report metadata comprising information extracted from the trust profile, and the report statement comprising a statement as to whether the trust credential satisfies the credibility requirements in the trust profile.

[0122] In one implementation, the trust profile includes an expression statement, which includes a formula or expression, and the formula or expression represents the requirements of the trust factor in the trust credential; the processing module is further used to: read the trust factor from the trust credential, read the expression statement from the trust profile; input the trust factor of the trust credential into the formula or expression of the expression statement, and determine whether the trust factor meets the credibility requirements; and generate the trust report based on the conclusion of whether the trust factor meets the credibility requirements.

[0123] In one implementation, the trust profile includes configuration metadata, which records information describing the trust profile, including the name, issuer, issuance date and version number of the trust profile. The processing module is further used to extract information from the configuration metadata to obtain the report metadata.

[0124] In one implementation, the trust credential includes a trust factor, which is a parameter representing the credibility of the media asset. The media asset includes media content, and the media asset also includes metadata of the media content and at least one of a trust record of the media content; the one or more trust factors are determined based on at least one of the media content, metadata corresponding to the media content, and a trust record corresponding to the media content.

[0125] In one implementation, the trust report is added to the trust record of the media asset to obtain a new trust record.

[0126] The modules in the data processing device of the tenth aspect of the present application are also used to execute the methods in other possible implementations of the fifth aspect.

[0127] In an eleventh aspect, an embodiment of the present application provides a data processing system, including:

[0128] A first device for acquiring media assets;

[0129] a second device, configured to obtain one or more trust factors of the media asset based on the media asset; the first device and the second device may be the same or different devices;

[0130] The third device is configured to generate a trust report based on one or more trust factors and trust configuration information of the media asset. In one possible implementation, the one or more trust factors of the media asset are recorded in a trust credential. In one possible implementation, the second device sends the one or more trust factors of the media asset to the third device in response to a request from the third device. The trust configuration information may be recorded in a trust configuration file. In one possible implementation, the third device may obtain the trust configuration file from a trust configuration file repository; in another possible implementation, the third device may directly read the trust configuration file from local storage.

[0131] In the twelfth aspect, an embodiment of the present application provides a data processing device, which may include a memory and a processor, wherein the memory is used to store programs, and the processor is used to execute programs in the memory to perform the above-mentioned first aspect and any optional method thereof, the above-mentioned second aspect and any optional method thereof, the above-mentioned third aspect and any optional method thereof, the above-mentioned fourth aspect and any optional method thereof, and the above-mentioned fifth aspect and any optional method thereof.

[0132] In the thirteenth aspect, an embodiment of the present application provides a computer-readable storage medium, in which a computer program is stored. When the computer-readable storage medium is run on a computer, the computer executes the above-mentioned first aspect and any optional method thereof, the above-mentioned second aspect and any optional method thereof, the above-mentioned third aspect and any optional method thereof, the above-mentioned fourth aspect and any optional method thereof, and the above-mentioned fifth aspect and any optional method thereof.

[0133] In the fourteenth aspect, an embodiment of the present application provides a computer program product comprising instructions, which, when run on a computer, enables the computer to execute the above-mentioned first aspect and any optional method thereof, the above-mentioned second aspect and any optional method thereof, the above-mentioned third aspect and any optional method thereof, the above-mentioned fourth aspect and any optional method thereof, and the above-mentioned fifth aspect and any optional method thereof.

[0134] In a fifteenth aspect, the present application provides a chip system, which includes a processor for supporting a data processing device in implementing some or all of the functions involved in the above aspects, such as sending or processing the data involved in the above methods; or information. In one possible design, the chip system also includes a memory for storing program instructions and data necessary for the data processing device. The chip system can be composed of a chip or can include a chip and other discrete devices. BRIEF DESCRIPTION OF THE DRAWINGS

[0135] Figure 1 is a schematic diagram of an application scenario;

[0136] FIG2 is a schematic structural diagram of a terminal device;

[0137] FIG3 is a schematic diagram of the structure of a server;

[0138] Figure 4 is a schematic diagram of a cloud service;

[0139] FIG5 is a schematic diagram of an application architecture;

[0140] FIG6A is a schematic diagram of a trust record framework;

[0141] FIG6B is a flow chart of a data processing method;

[0142] FIG7A is a schematic diagram of generating credible information;

[0143] FIG7B is a schematic diagram of generating credible information;

[0144] FIG7C is a schematic diagram of generating a trustworthy report;

[0145] FIG7D is a schematic diagram of generating a trustworthy report;

[0146] FIG8A is a schematic diagram of a trust profile;

[0147] FIG8B is a schematic diagram of a trust profile;

[0148] FIG9 is a flow chart of a data processing method;

[0149] FIG10 is a flow chart of a data processing method;

[0150] FIG11 is a flow chart of a data processing method;

[0151] FIG12 is a flow chart of a data processing method;

[0152] FIG13 is a flow chart of a data processing method;

[0153] FIG14 is a flow chart of a data processing method;

[0154] FIG15 is a flow chart of a data processing method;

[0155] FIG16A is a flow chart of a data processing method;

[0156] FIG16B is a flow chart of a data processing method;

[0157] FIG16C is a flow chart of a data processing method;

[0158] FIG16D is a flow chart of a data processing method;

[0159] FIG16E is a flow chart of a data processing method;

[0160] FIG17 is a schematic structural diagram of a data processing device;

[0161] FIG18 is a schematic structural diagram of a data processing device;

[0162] FIG19 is a schematic diagram of the structure of a server. DETAILED DESCRIPTION

[0163] The following describes the embodiments of the present invention in conjunction with the accompanying drawings. The terms used in the embodiments of the present invention are only used to explain the specific embodiments of the present invention, and are not intended to limit the present invention.

[0164] The embodiments of the present application are described below in conjunction with the accompanying drawings. Those skilled in the art will appreciate that, with the development of technology and the emergence of new scenarios, the technical solutions provided in the embodiments of the present application are also applicable to similar technical problems.

[0165] The terms "first", "second", etc. in the specification and claims of the present application and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequential order. It should be understood that the terms used in this way can be interchangeable under appropriate circumstances, and this is merely a way of distinguishing the objects of the same attributes when describing them in the embodiments of the present application. In addition, the terms "including" and "having" and any of their variations are intended to cover non-exclusive inclusions, so that the process, method, system, product or equipment comprising a series of units need not be limited to those units, but may include other units that are not clearly listed or inherent to these processes, methods, products or equipment.

[0166] As used herein, the terms "substantially," "about," and similar terms are used as terms of approximation, not as terms of degree, and are intended to take into account the inherent variations in measurements or calculations that one of ordinary skill in the art would recognize. Furthermore, the use of "may" when describing embodiments of the present invention refers to "one or more possible embodiments." As used herein, the terms "use," "using," and "used" may be considered synonymous with the terms "utilize," "utilizing," and "utilized," respectively. Additionally, the term "exemplary" is intended to refer to an example or illustration.

[0167] First, the application scenario of this application is introduced.

[0168] This application can provide users with trustworthy information (or trust reports) that can be used as a basis for determining the trustworthiness of media assets. The trustworthy information can indicate whether one or more trust factors of a media asset meet the requirements of a configuration file. Based on this trustworthy information, users can determine the trustworthiness of the media asset.

[0169] In one scenario, embodiments of the present application may be applied to an application program that provides trusted information about media assets.

[0170] In one scenario, embodiments of the present application may be applied to a cloud service that provides trusted information about media assets.

[0171] In one scenario, an embodiment of the present application can be applied to a media asset management module, which can generate trusted information of media assets and use the trusted information to update trust records in the media assets, or generate associated files of the media assets based on the trusted information to help users judge the credibility of media assets.

[0172] The present application can provide users with a trust factor (or trust credential) used as a basis for judging the credibility of a media asset. The trust factor can include parameters indicating the credibility of the media asset.

[0173] In one scenario, embodiments of the present application may be applied to an application that provides trust credentials.

[0174] In one scenario, the embodiments of the present application can be applied to cloud services that provide trust credentials.

[0175] In one scenario, an embodiment of the present application can be applied to a media asset management module, which can generate trust credentials for media assets and use the trust credentials to update trust records in the media assets, or generate associated files of the media assets based on the trust credentials to help users make credibility judgments on media assets.

[0176] This application can provide users with a trust profile for generating trust information (trust report) of media assets. The trust profile indicates the trustworthiness requirements of the media assets and is used to generate a trust report together with the trust credentials of the media assets.

[0177] In one scenario, the embodiments of the present application may be applied to an application that provides a trust profile.

[0178] In one scenario, the embodiments of the present application may be applied to a cloud service that provides a trust profile.

[0179] In one scenario, the embodiments of the present application may be applied to a trust profile management module, which may generate a trust profile for a media asset.

[0180] Next, we will introduce the above application scenarios respectively:

[0181] Scenario 1. Application.

[0182] In one scenario, the embodiment of the present application is in the form of an application for providing trusted information, trust credentials, or trust profiles of media assets (the embodiment of the present application may be referred to as a trusted judgment application).

[0183] The product form of the embodiment of the present application can be a trustworthy judgment application. The trustworthy judgment application can be run on a terminal device or a cloud-side server.

[0184] In one possible implementation, the trust determination application may present trust information, trust credentials, or a trust profile of the media asset to the user in response to input information indicating the media content or media asset.

[0185] FIG1 is a schematic diagram showing an exemplary application scenario.

[0186] When the user needs to judge the credibility of the media content, he can open the media trusted platform client (such as an application, applet, web page, etc.) in the terminal device to query.

[0187] For example, after user A's mobile phone A receives media content sent by user B's mobile phone B, if user A needs to use the media content (such as forwarding), the credibility of the media content can be judged first. After determining the credibility of the media content, it is determined whether to use the media content.

[0188] It should be understood that mobile phone A may also be other electronic devices with strong computing capabilities, such as a personal computer, a computer workstation, a tablet computer, etc., and this application does not impose any restrictions on this.

[0189] For example, when a user needs to determine the credibility of media content in a smartwatch, the user can send the media content in the smartwatch to a mobile phone, which then determines the credibility of the media content and sends the credibility information to the smartwatch.

[0190] It should be understood that a smartwatch may also be other electronic devices with relatively low computing power, such as media consumption devices, wearable devices, set-top boxes, game consoles, etc., and this application does not limit this. A mobile phone may also be other electronic devices with relatively high computing power, such as personal computers, computer workstations, tablet computers, etc., and this application does not limit this.

[0191] Referring to (1) in FIG1 , the main interface 101 of the media trusted platform may include one or more controls, including but not limited to: an input box, a credibility judgment button, etc., which is not limited in this application.

[0192] For example, a user can click on an input box, and the media trusted platform can display a file selection interface in response to the user's operation. Then, after selecting the corresponding media content in the file selection interface, the user can click a trusted information generation button in the main interface 101; in response, the media trusted platform can obtain trusted information of the media asset in response to the user's operation.

[0193] Exemplarily, the media trusted platform may display trusted information. For example, in an embodiment of the present application, the trusted information may include whether at least one trust factor of a media asset of the media content meets the index requirements in the pre-configured file.

[0194] Referring to (2) in Figure 1, the verification result shown in (2) in Figure 1 includes the satisfaction of the media content with respect to the index requirements specified in the pre-configuration file in terms of trust factors T1, T3, T4 and Tn, for example, trust factor T1 meets the index requirements, trust factor T2 meets the index requirements, trust factor T3 does not meet the index requirements, and trust factor T4 meets the index requirements.

[0195] In one possible approach, the client of the media trusted platform may perform identification of the trusted information of the media asset. For example, when there is only one media asset to be identified, the client of the media trusted platform may perform identification locally.

[0196] In one possible approach, the trusted information of media assets can be identified by the media trusted platform server. For example, when there are multiple media assets to be identified, the media trusted platform client can send the multiple media assets to be identified to the media trusted platform server. The media trusted platform server then identifies the trusted information of the media assets and returns the identified trusted information to the media trusted platform client.

[0197] It should be noted that in this application, whether the identification of trusted information of media assets is performed by the client of the media trusted platform or by the server of the media trusted platform is not limited by the amount of media content to be identified.

[0198] It should be understood that the scenario description corresponding to FIG1 can also be applied to the generation of trust credentials, and the similarities are not repeated here.

[0199] Next, the product form of the terminal 100 is described when the media trusted platform is located on the terminal side;

[0200] The terminal 100 in the embodiment of the present application can be a mobile phone, a tablet computer, a wearable device, an in-vehicle device, an augmented reality (AR) / virtual reality (VR) device, a laptop computer, an ultra-mobile personal computer (UMPC), a netbook, a personal digital assistant (PDA), etc., and the embodiment of the present application does not impose any restrictions on this.

[0201] FIG2 shows a schematic diagram of an optional hardware structure of the terminal 100 .

[0202] 2 , the terminal 100 may include components such as a radio frequency unit 110, a memory 120, an input unit 130, a display unit 140, a camera 150 (optional), an audio circuit 160 (optional), a speaker 161 (optional), a microphone 162 (optional), a processor 170, an external interface 180, and a power supply 190. Those skilled in the art will appreciate that FIG2 is merely an example of a terminal or multi-function device and does not limit the terminal or multi-function device. The terminal or multi-function device may include more or fewer components than shown, or may combine certain components or have different components.

[0203] The input unit 130 can be used to receive input digital or character information and generate key signal input related to user settings and function control of the portable multifunction device. Specifically, the input unit 130 may include a touch screen 131 (optional) and / or other input devices 132. The touch screen 131 can detect user touch operations on or near it (for example, operations performed on or near the touch screen using a finger, joint, stylus, or any other suitable object) and drive corresponding connected devices according to pre-set programs. The touch screen can detect user touch actions on the touch screen, convert the touch actions into touch signals and transmit them to the processor 170. It can also receive and execute commands sent by the processor 170; the touch signals include at least touch point coordinate information. The touch screen 131 provides an input interface and an output interface between the terminal 100 and the user. Touch screens can be implemented using various types, including resistive, capacitive, infrared, and surface acoustic wave. In addition to the touch screen 131, the input unit 130 may also include other input devices. Specifically, the other input devices 132 may include, but are not limited to, one or more of a physical keyboard, function keys (such as a volume control button 132 , a switch button 133 , etc.), a trackball, a mouse, a joystick, and the like.

[0204] The input device 132 may receive a media asset designated for credibility determination.

[0205] The display unit 140 may be used to display information input by the user or provided to the user, various menus of the terminal 100, interactive interfaces, file display, and / or playback of any multimedia file. In an embodiment of the present application, the display unit 140 may be used to display trust information (e.g., a trust report), etc.

[0206] Memory 120 can be used to store instructions and data. It primarily includes an instruction storage area and a data storage area. The data storage area can store various data, such as multimedia files and text. The instruction storage area can store software units such as the operating system, applications, and instructions required for at least one function, or subsets or extensions thereof. It may also include non-volatile random access memory (RAM). It provides processor 170 with management functions for the hardware, software, and data resources within the computing and processing device, supporting control software and applications. It is also used to store multimedia files and running programs and applications.

[0207] The processor 170 is the control center of the terminal 100. It connects all components of the terminal 100 using various interfaces and circuits. By executing instructions stored in the memory 120 and accessing data stored therein, it executes various functions of the terminal 100 and processes data, thereby providing overall control of the terminal device. Optionally, the processor 170 may include one or more processing units. Preferably, the processor 170 may integrate an application processor and a modem processor, with the application processor primarily processing the operating system, user interface, and application programs, while the modem processor primarily handles wireless communications. It is understood that the modem processor may not be integrated into the processor 170. In some embodiments, the processor and memory may be implemented on a single chip; in other embodiments, they may be implemented on separate chips. The processor 170 may also generate corresponding operational control signals and send them to the corresponding components of the computing and processing device. It may also read and process data in the software, particularly the data and programs in the memory 120, to enable the various functional modules therein to perform their corresponding functions, thereby controlling the corresponding components to operate as instructed.

[0208] Among them, the memory 120 can be used to store software codes related to the data processing method, the processor 170 can execute the steps of the chip's data processing method, and can also schedule other units (such as the above-mentioned input unit 130 and display unit 140) to achieve corresponding functions.

[0209] The RF unit 110 (optional) can be used to send and receive information or receive and send signals during a call. For example, after receiving downlink information from the base station, it is passed to the processor 170 for processing; in addition, it sends the designed uplink data to the base station. Generally, the RF circuit includes but is not limited to an antenna, at least one amplifier, a transceiver, a coupler, a low noise amplifier (LNA), a duplexer, etc. In addition, the RF unit 110 can also communicate with network devices and other devices via wireless communication. This wireless communication can use any communication standard or protocol, including but not limited to Global System of Mobile communication (GSM), General Packet Radio Service (GPRS), Code Division Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA), Long Term Evolution (LTE), email, Short Messaging Service (SMS), etc.

[0210] In this embodiment of the present application, the radio frequency unit 110 can send media content to the server 200 and receive trusted information sent by the server 200.

[0211] It should be understood that the radio frequency unit 110 is optional and can be replaced by other communication interfaces, such as a network port.

[0212] The terminal 100 also includes a power supply 190 (such as a battery) for supplying power to various components. Preferably, the power supply can be logically connected to the processor 170 through a power management system, thereby managing functions such as charging, discharging, and power consumption through the power management system.

[0213] The terminal 100 further includes an external interface 180 , which may be a standard Micro USB interface or a multi-pin connector, and may be used to connect the terminal 100 to other devices for communication, or to connect a charger to charge the terminal 100 .

[0214] Although not shown, the terminal 100 may also include a flash, a wireless fidelity (WiFi) module, a Bluetooth module, sensors with different functions, etc., which are not described in detail here. Some or all of the methods described below may be applied to the terminal 100 shown in FIG.

[0215] Next, the product form of the server 200 is described when the media trusted platform is located on the server side;

[0216] FIG3 provides a schematic diagram of the structure of a server 200. As shown in FIG3, the server 200 includes a bus 201, a processor 202, a communication interface 203, and a memory 204. The processor 202, the memory 204, and the communication interface 203 communicate with each other via the bus 201.

[0217] Bus 201 may be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus. Buses can be classified as address buses, data buses, control buses, etc. For ease of illustration, FIG3 shows only one thick line, but this does not mean that there is only one bus or only one type of bus.

[0218] The processor 202 may be any one or more of a central processing unit (CPU), a graphics processing unit (GPU), a microprocessor (MP), or a digital signal processor (DSP).

[0219] The memory 204 may include volatile memory, such as random access memory (RAM). The memory 204 may also include non-volatile memory, such as read-only memory (ROM), flash memory, hard drive (HDD), or solid state drive (SSD).

[0220] The memory 204 may be used to store software codes related to the data processing method, and the processor 202 may execute the steps of the data processing method of the chip, and may also schedule other units to implement corresponding functions.

[0221] It should be understood that the above-mentioned terminal 100 and server 200 can be centralized or distributed devices, and the processors in the above-mentioned terminal 100 and server 200 (such as processor 170 and processor 202) can be hardware circuits (such as application specific integrated circuit (ASIC), field-programmable gate array (FPGA), general-purpose processor, digital signal processor (DSP), microprocessor or microcontroller, etc.), or a combination of these hardware circuits. For example, the processor can be a hardware system with an instruction execution function, such as a CPU, DSP, etc., or a hardware system without an instruction execution function, such as an ASIC, FPGA, etc., or a combination of the above-mentioned hardware systems without an instruction execution function and hardware systems with an instruction execution function.

[0222] Scenario 2. Cloud service.

[0223] In one scenario, an embodiment of the present application is a cloud service for providing trusted information, trust credentials, or trust profiles of media assets.

[0224] In a possible implementation, the server may provide the client with a query service for trusted information, trust credentials, or trust profiles of media assets through an application programming interface (API).

[0225] Among them, the terminal device can send relevant parameters (such as media assets and other data) to the server through the API provided by the cloud. The server can obtain processing results (such as trusted information or trust credentials, etc.) based on the received parameters and return the processing results to the terminal.

[0226] In one implementation, the server can generate a trust profile and send it to other devices, allowing them to assess the trustworthiness of media assets based on the trust profile. In another implementation, because different regions or platforms may have different trustworthiness requirements for media assets, the server can also store the trust profile locally. Other devices can query the server for the trust profile for the corresponding region to understand the trustworthiness requirements for media assets in that region.

[0227] In one implementation, since different media platforms may have different requirements for the credibility of media assets, media platforms can also set up trust profiles on their own, such as: Douyin, Kuaishou, Xiaohongshu, etc.

[0228] The description of the terminal and the server can be the same as that of the above embodiments, and will not be repeated here.

[0229] FIG4 shows a process of using a credibility judgment function cloud service provided by a cloud platform.

[0230] 1. Activate and purchase content review services.

[0231] 2. Users can download the software development kit (SDK) corresponding to the content review service. Usually, the cloud platform provides multiple development versions of the SDK for users to choose according to the requirements of the development environment, such as JAVA version SDK, Python version SDK, PHP version SDK, Android version SDK, etc.

[0232] 3. After downloading the corresponding version of the SDK to the local computer as needed, the user imports the SDK project into the local development environment, configures and debugs it, and can also develop other functions in the local development environment, forming an application that integrates credibility judgment capabilities.

[0233] 4. When a credibility assessment application needs to perform a credibility assessment during use, it can trigger an API call for the credibility assessment function. When the application triggers the credibility assessment function, it initiates an API request to a running instance of the credibility assessment service in the cloud environment. The API request carries media content, which is then processed by the running instance in the cloud environment to obtain trustworthy information.

[0234] 5. The cloud environment returns the trusted information to the application, thereby completing a call to the credibility judgment function.

[0235] Scenario 3. Media asset management module.

[0236] In this scenario, the terminal device itself can collect or generate media content. For example, it can collect images through its own camera, or generate new media content through media content editing software (such as through AIGC).

[0237] When a terminal device obtains media content, it also needs to generate corresponding media assets through the media asset management module. Media assets may include metadata, trust records, etc.

[0238] In this scenario, the media asset management module may generate trusted information based on the content in the media asset and add the trusted information to the media asset, or use the trusted information as a file associated with the media asset.

[0239] In one implementation, different users may have different requirements for media asset credibility, and users may set a trust profile themselves through a media asset management module of a terminal device.

[0240] FIG5 shows a block diagram of a structure of a terminal device 101 where a media asset management module is located.

[0241] According to one or more embodiments described in this application, the terminal device 101 may include electronic components for performing media project (e.g., media asset) management. The client device 101 may be housed in a single computing system (such as a desktop computer system, a laptop computer system, a tablet computer system, a server computer system, a mobile phone, a media player, a personal digital assistant, a personal communicator, a gaming device, a network router or hub, a wireless access point (AP) or a repeater, a set-top box, or a combination thereof). The components in the terminal device 101 may be spatially separated and implemented on a separate computing system connected by a communication technology 110.

[0242] For one embodiment, one or more components in client device 101 may be implemented as one or more integrated circuits (ICs). For example, at least one of processing unit 104, media content capture device 102, peripheral device 118, sensor 122, or memory 110 may be implemented as a system-on-chip (SoC) IC, a three-dimensional (3D) IC, any other known IC, or a combination of any known ICs. For another embodiment, two or more components in client device 101 may be implemented together as one or more ICs. For example, at least two of processing unit 104, media content capture device 102, peripheral device 118, sensor 122, or memory 110 may be implemented together as a SoC IC. Each component of client device 101 is described below.

[0243] The terminal device 101 may include a media content capture device 102 (e.g., an imaging device for capturing images, an audio device for capturing sounds, a multimedia device for capturing audio and video, any other known user media content capture device, etc.). For one embodiment, the media content capture device 102 may also include a signal processing pipeline implemented as hardware, software, or a combination thereof. The signal processing pipeline may perform one or more operations on data received from one or more components in the device 102. The signal processing pipeline may also provide processed data to the memory 110, the peripheral device 118 (as discussed further below), and / or the processing unit 104.

[0244] The terminal device 101 may include a processing unit 104, such as a CPU, a GPU, other integrated circuits (ICs), a memory, and / or other electronic circuits. In one embodiment, the processing unit 104 may generate media assets 111 associated with media content 114 through the media asset management module 106. In some implementations, the processing unit 104 may generate trust information based on the content in the media asset and add it to the media asset, or provide the trust information as a file associated with the media asset (e.g., the trust report 121 shown in FIG. 5 ). In some implementations, the processing unit 104 may generate a trust profile for the media asset.

[0245] The terminal device 101 may also include peripheral devices 118. In one embodiment, the peripheral devices 118 may include at least one of the following: (i) one or more input devices that interact with or send data to one or more components in the client device 101 (e.g., a mouse, keyboard, etc.); (ii) one or more output devices that provide output from one or more components in the client device 101 (e.g., a monitor, printer, display device, etc.); or (iii) one or more storage devices that store data in addition to the memory 110. The peripheral devices 118 are shown in dashed boxes to indicate that they are optional components of the client device 101. The peripheral device 118 may also refer to a single component or device that can function as both an input device and an output device (e.g., a touch screen, etc.). The client device 101 may include at least one peripheral control circuit (not shown) for the peripheral device 118. The peripheral control circuit may be a controller (e.g., a chip, expansion card, or separate device) that interacts with the peripheral device 118 and directs operations performed by the peripheral device. The peripheral device controller may be a separate processing unit or integrated into the processing unit 104. Peripheral devices 118 may also be referred to as input / output (I / O) devices 118 throughout this document.

[0246] The client device 101 may also include one or more sensors 122, which are shown in dashed lines to illustrate that the sensors may be optional components of the client device 101. In one embodiment, the sensors 122 may detect one or more environmental characteristics. Examples of sensors include, but are not limited to, light sensors, imaging sensors, accelerometers, sound sensors, air pressure sensors, proximity sensors, vibration sensors, gyroscope sensors, compasses, barometers, thermal sensors, rotation sensors, speed sensors, and inclinometers.

[0247] In conjunction with FIG4 and FIG10 , this embodiment provides a trust evaluation system, including:

[0248] A first device for acquiring media assets;

[0249] a second device, configured to obtain one or more trust factors of the media asset based on the media asset; the first device and the second device may be the same or different devices;

[0250] The third device is configured to generate a trust report based on one or more trust factors and trust configuration information of the media asset. In one possible implementation, the one or more trust factors of the media asset are recorded in a trust credential. In one possible implementation, the second device sends the one or more trust factors of the media asset to the third device in response to a request from the third device. The trust configuration information may be recorded in a trust configuration file. In one possible implementation, the third device may obtain the trust configuration file from a trust configuration file repository, which may be located in the fourth device. In one possible implementation, the third device may directly read the trust configuration file from a local storage device.

[0251] 6A, FIG6A is a framework of a trust record of a media asset.

[0252] For example, as shown in FIG7A , media assets may include media content, metadata of the media content, and a trust record of the media content. The metadata and trust record of the media content are bound to the media content, or in other words, the metadata and trust record of the media content are associated with the media content.

[0253] When the media assets of the media content are acquired, the metadata and trust record of the media content are also acquired accordingly. For example, when acquiring an image, the digital image, the metadata of the image, and the trust record of the image can be acquired.

[0254] It should be noted that in some scenarios, media assets are also referred to as media files or digital assets (Media Asset).

[0255] Media content can be images, audio, video, or text.

[0256] Media assets may include trust records. In one implementation, the trust record may be part of the metadata. In one implementation, the trust record may exist independently of the metadata in the media asset. For example, media content may also be referred to as digital content. Media content may be part of a media asset, representing the actual content of the media. Digital content is content of different content types such as text, images, and sounds that exists in digital form. It can be stored on digital carriers such as CDs and hard disks, and disseminated through the Internet and other means. Digital content is the overall product or service that integrates and applies images, text, audio and video content through digital technology. It is the product of the combination of digital media technology and cultural creativity. For example, media content may be the pixel data of an image, as well as any additional technical metadata (e.g., color profiles or encoding parameters) required to understand or present the content.

[0257] Digital technology is a science and technology that has grown alongside computers. It uses specialized equipment to convert various types of information, including images, text, sound, and video, into binary digits (0s and 1s) that computers can interpret, allowing for computation, processing, storage, transmission, dissemination, and restoration. Because computers are used to encode, compress, and decode information during computation and storage, digital technology is also known as digital technology or computer digital technology. It is also called digital control technology.

[0258] For example, metadata may include data describing media content. Metadata may record non-technical information about media assets or media content; for example, metadata may include information describing properties of media content. For example, metadata may include a trust profile (or trust manifest). For example, metadata may include the creation location, creator, annotations, or IP address information of the media content.

[0259] For example, as shown in FIG7B , the trust record of media content may be a type of metadata of the media content (or may not be metadata but be independent of metadata and belong to media assets). The trust record records relevant information on the generation and changes of the media content and may be used to trace the source of the media content.

[0260] In one embodiment, as shown in FIG6A , a trust record may include a trust statement and a trust list.

[0261] For example, a trust declaration can be a trust list, which can be located at the first position of a trust record. A trust declaration can also be a metadata of the media content.

[0262] In a possible implementation, the trust declaration in the trust record may include: initial information of the first media content, hard binding of the first media content, and the first digital signature. sk0 ; The first digital signature is a digital signature of the first data, and the first data is data determined based on at least the hard binding of the initial information and the first media content.

[0263] The first media content may be content of different content types such as text, images, sounds, etc. in digital form. For example, the first media content may be pixel data of an image, as well as any additional technical metadata required to understand or present the content (e.g., a color profile or encoding parameters).

[0264] Hard binding refers to data obtained after hard binding processing is performed on the original data. Hard binding processing is a processing method that prevents the original data from being forged. The original data cannot be obtained by reverse processing the hard binding of the original data. The hard binding of the original data is obtained by performing hard binding processing on the original data. For example, the original data is processed using a one-way function. For example, hash processing can be a type of hard binding processing, that is, the hard binding can include a hash value, and the hard binding of the first media content can also include a first media hash value. The first media hash value (Media Hash 0) is the hash value of the first media content.

[0265] Exemplarily, the first data is data that is a combination of at least the hard binding of the first media content and the initial information of the first media content, or the first data is data that is a combination of at least the hard binding of the initial information (for example, the hash value AIGC.Hash of AI generating AIGC, the hash value Media Type.Hash of the media generation method) and the hard binding of the first media hard binding (for example, the hash value Media Hash0.Hash of the first media hash value).

[0266] Exemplarily, the first data may also be a first combined hash value (Hash(TD)), which includes a hash value of the initial information of the first media content and the first media hash value. Exemplarily, the first combined hash value includes a hash value of the initial information of the first media content, the first media hash value, and other descriptive information. The other descriptive information may not be other descriptive information in the initial information, for example, information of a tool for generating a Trust Profile or other information describing the initial information of the first media content. This application does not impose any restrictions on this.

[0267] Exemplarily, the first data may also be a first combined hash value, which may include a hash value of the hash value of the initial information of the first media content and a hash value of the first media hash value (Media Hash 0.Hash). Exemplarily, the first combined hash value is a hash value of the hash value of the initial information of the first media content, the hash value of the first media hash value, and the hash value of other metadata information. Here, in the case where the initial information of the first media content includes at least two, the hash value of the initial information of the first media content may include the hash value of each of the initial information of the first media content, or the hash value of the initial information of the first media content may include the hash value of all the initial information of the first media content.

[0268] Exemplarily, the initial information of the media content may refer to the information generated when the media content is generated. Exemplarily, the initial information of the media content includes at least one of the following: the generation time of the media content, the name of the author of the media content, the digital content identifier of the media content, the generation location of the media content, the information of the device for generating the media content, the resolution of the media content, the size of the media content, the media type of the media content, or the generation method (Media Type) of the media content. For example, the information of the device for generating the media content may include the model of the device, the parameters of the camera, etc. The parameters of the camera may include the focal length, sensitivity, exposure, etc. when the camera takes pictures. It should be understood that the initial information of the media content may also include other information such as copyright information and other information used to describe the media content, and this application does not impose any restrictions on this.

[0269] Exemplarily, media types may include, but are not limited to, images, videos, audios, and graphics. Generation methods may include AI generation methods and non-AI generation methods. In one possible approach, the generation method in the initial information may be replaced with an AI generation (AIGC) identifier; for example, when the media content is generated by AI, the value of the AIGC identifier is 1; when the media content is not generated by AI, the value of the AIGC identifier is 0. The author name of the media content may be the name of the creator of the media content or the name of the shooting device of the media content, and this application does not impose any restrictions on this.

[0270] The digital signature of the first data usually uses a private key to digitally sign the first data to obtain the digital signature of the first data.

[0271] Exemplarily, the private key may be a private key of an electronic device or a user. Exemplarily, the first data may be digitally signed using the private key based on a digital signature algorithm to obtain a digital signature of the first data. It should be understood that this application does not limit the digital signature algorithm.

[0272] For example, a trust manifest records information indicating the source of a media asset. The trust manifest is part of a trust record and can also be a type of metadata.

[0273] Exemplarily, the trust list may include a hard binding of the N+1th media content (e.g., the second media hash value Media hash1). Exemplarily, the media content obtained after editing the Nth media content according to the editing operation, or the media content obtained after modifying the metadata of the Nth media content, or the Nth media content to be forwarded (or shared) may be referred to as the N+1 media content.

[0274] Exemplarily, the trust list may further include a media assertion, which may include copyright information, thumbnails, whether it can be modified, operating permissions, usage permissions, the source of the second media content, and the like.

[0275] Exemplarily, the trust list may further include a second digital signature Signature sk1 The second digital signature is a digital signature of the second data, and the second data may be data determined based on at least the second media hash value and the modification statement.

[0276] Exemplarily, the second data is data composed of at least the N+1th media hash value and the N+1th declaration, or the first data is data composed of at least the hash value of the N+1th declaration (Assertion Hash) and the hash value of the N+1th media hash value.

[0277] Exemplarily, the second data may also be the N+1th combined hash value, where the N+1th combined hash value includes the hash value of the N+1th declaration and the N+1th media hash value combined. Exemplarily, the N+1th combined hash value includes the hash value of the N+1th declaration, the hash value of the N+1th media hash value combined, and the hash value of other descriptive information combined. The other descriptive information may not be other descriptive information in the N+1th declaration, for example, information about a tool for generating a Trust Manifest or other information describing the N+1th declaration, and this application does not impose any restrictions on this.

[0278] Exemplarily, the second data may also be the N+1th combined hash value, which may include a hash value of the combination of the N+1th declared hash value and the N+1th media hash value (e.g., the second media hash value Media Hash 1.Hash). Exemplarily, the N+1th combined hash value is a hash value of the combination of the N+1th declared hash value, the N+1th media hash value, and the hash value of other metadata information (Other Information).

[0279] Exemplarily, the trust list may further include a first uniform resource identifier (URI), where the first URI indicates the initial information of the first media content or the location of the hard binding of the first media content in the modification record of the first media content. For example, URI1 indicates the location of the hard binding of the first media content in the trust record of the first media content, URI2 indicates the location of the Media Type in the trust record of the first media content, URI3 indicates the location of the AIGC in the trust record of the first media content, URI4 indicates the location of the N+1th media content (e.g., the second media hash value Media Hash 1) in the trust record, and URI5 indicates the location of the media assertion in the trust record.

[0280] Exemplarily, the modification record may also include other information, which may be information not used to verify the authenticity of the media content, such as the file name and the name of the hash algorithm used to calculate the hash value mentioned in the above embodiment.

[0281] The following is an example of the method flow of the embodiment of the present application.

[0282] 6B , which is a flow chart of a data processing method provided in an embodiment of the present application. The flow chart mainly describes the process of generating trusted information. As shown in FIG6B , a data processing method provided in an embodiment of the present application includes:

[0283] 601. Obtain one or more trust factors of a media asset; the media asset includes at least one of media content, metadata corresponding to the media content, and a trust record corresponding to the media content.

[0284] Exemplarily, trust indicators are parameters that indicate the credibility of media assets. In one possible implementation, the trust factor of a media asset can be obtained from a trust credential, that is, the trust factor of a media asset is encapsulated in the trust credential; in one possible implementation, the trust factor can be obtained from a media asset, and the corresponding trust factor is directly read from the media asset. In one possible implementation, the media asset includes at least one of media content, metadata corresponding to the media content, and a trust record corresponding to the media content. In an embodiment of the present application, in order to enable a user to judge the credibility of a media asset, one or more trust factors related to the credibility of the media asset can be determined based on the media asset, and based on the verification results of the trust factors, the user can analyze and judge the credibility of the media asset.

[0285] In one possible implementation, as shown in FIG7B , a media asset may include media content and metadata of the media content. The metadata of the media content is bound to the media content, or in other words, the metadata of the media content is associated with the media content. The metadata may include a trust record, or the metadata may not include a trust record, and the trust record and the metadata may be different parts of the media asset. That is, as shown in FIG7B , a media asset may include media content and metadata corresponding to the media content (the trust record is encapsulated in the metadata), and as shown in FIG7A , a media asset may also include media content, metadata corresponding to the media content, and a trust record corresponding to the media content.

[0286] In one possible implementation, a trust record can be further divided into a trust declaration and several trust manifests. Trust manifests are collections of media asset provenance information, while a trust declaration is a special type of trust manifest that only contains mandatory assertions (mandatory provenance information). A trust declaration can appear first in a trust record.

[0287] In one possible implementation, one or more trust factors related to the credibility of the media asset can be determined based on the media asset. Specifically, as shown in FIG7A , one or more trust factors related to the credibility of the media asset can be determined based on at least one of the media content, metadata corresponding to the media content, and a trust record corresponding to the media content. As shown in FIG7B , one or more trust factors related to the credibility of the media asset can be determined based on at least one of the media content and metadata corresponding to the media content (the trust record is part of the metadata).

[0288] For example, the trust factor of a media asset may be features extracted from the media content, the metadata corresponding to the media content, and the trust record corresponding to the media content, or it may be data obtained after certain processing of the features in the media content, the metadata corresponding to the media content, and the trust record corresponding to the media content.

[0289] For example, one or more trust factors TM related to the credibility of the media asset can be determined based on the metadata of the media content. For example, TM can be the generation time of the media content, the author name of the media content, the digital content identifier of the media content, the generation location of the media content, information about the generation device of the media content, the media type of the media content, or the generation method (Media Type) of the media content. For example, the information about the generation device of the media content may include the model of the device, the parameters of the camera, etc. The parameters of the camera may include the focal length, sensitivity, exposure, etc. when the camera takes a picture. It should be understood that TM may also include other information such as copyright information and other information used to describe the media content, and this application does not limit this.

[0290] For example, one or more trust factors related to the credibility of the media asset may be determined based on metadata of the media content and a trust record of the media content.

[0291] For example, one or more trust factors related to the credibility of the media asset may be determined based on metadata of the media content, the media content, and a trust record of the media content.

[0292] For example, one or more trust factors TR related to the credibility of a media asset can be determined based on the trust record of the media content. For example, the trust record may include the time of creation of the media content, the author name of the media content, the digital content identifier of the media content, the location of creation of the media content, information about the device that created the media content, the media editing method, the media type of the media content, or the media type of the media content. For example, information about the device that created the media content may include the device model and camera parameters. Camera parameters may include the focal length, sensitivity, and exposure when the camera captures the image. It should be understood that TR may also include other information describing the media content, such as copyright information, which is not limited to this application. The media generation method may include, but is not limited to, whether the media content was generated using AIGC, whether it was generated using a camera, whether it was generated with software assistance, whether it was generated using synthetic media, whether the media content can be used to train a model, and media editing methods may include, but are not limited to, rotation, resizing, cropping, and content editing. TR may also include a media declaration, including a thumbnail, whether it can be modified, operating permissions, usage permissions, and the source of the second media content.

[0293] For example, one or more trust factors related to the credibility of the media asset may be determined based on the media content and the trust record of the media content.

[0294] For example, one or more trust factors TC related to the credibility of a media asset can be determined based on the media content. For example, features such as characters, scenes, object types, positional relationships between objects, and media style (e.g., color, light, brightness) in the media content can be selected as trust factors for the media content.

[0295] For example, one or more trust factors related to the credibility of a media asset may be determined based on metadata of the media content and the media content.

[0296] The trust factor may be a characteristic description of the media asset. For example, the trust factor may include a parameter indicating the credibility of the media asset.

[0297] In one possible implementation, the trust credential may include the relationship between each trust factor and its corresponding source, that is, which part of the media asset (metadata, trust list, or media content) the trust factor corresponds to. A trust credential is one or more trust factors derived based on a media asset.

[0298] In one possible implementation, when a trust factor is obtained, the trust factor itself can be used as a trust credential. In another possible implementation, when multiple trust factors are obtained, all of the trust factors can be encapsulated to obtain a trust credential. In another possible implementation, the trust factor can also be encapsulated together with other data to obtain a trust credential.

[0299] In one possible implementation, corresponding requirements may be obtained for one or more trust factors of the acquired media assets, that is, evaluation constraints on the trust factors of the media assets in specific scenarios. The evaluation constraints may be considered as constraints related to the credibility of the media assets.

[0300] In embodiments of the present application, the evaluation constraints for the trust factors of media assets can be described by a configuration file, which can include indicator requirements corresponding to each of the trust factors. The configuration file can also be referred to as a trust profile. A trust profile records a set of established trust indicators that can be used to evaluate the trust credentials of a specific media asset.

[0301] 602. Determine whether the one or more trust factors meet an indicator.

[0302] In one implementation, the indicator can be stored in a memory. When a trust evaluation of a media asset is required, one or more trust factors of the media asset are obtained, and the trust factor corresponding to the indicator is matched with the one or more trust factors of the media asset to determine whether the one or more trust factors meet the indicator.

[0303] In one implementation, each indicator specified in the trust profile corresponds to a trust factor. The corresponding trust factor can be obtained from the media asset based on the indicator specified in the profile, and the trust information of the media asset can be obtained based on the trust profile and one or more trust factors of the media asset.

[0304] For example, a trust profile records trust configuration information, which includes metrics that a media asset must meet. Alternatively, the trust configuration information includes metrics that a trust credential must meet. The trust configuration information can be a set of trust factors used to evaluate the trust credential and indicate the credibility of the media asset.

[0305] In one implementation, multiple indicators of the media asset can be obtained first. The multiple indicators may include indicators other than the indicators with constraints in the configuration file. Therefore, based on the indicators specified in the first configuration file, the satisfaction of each trust factor with the indicators can be determined to obtain the trusted information of the media asset.

[0306] In one implementation, the indicator may be data processed based on the trust factor, but it may indicate the corresponding trust factor. In other words, the indicator may be the trust factor of the media asset, the value of the trust factor, or data obtained after a certain processing of the trust factor.

[0307] In one implementation, the metric may include one or more trust factors, and whether the one or more trust factors of the media asset meet the metric may be determined by determining whether the trust factors in the metric are included in the one or more trust factors of the media asset.

[0308] In one implementation, whether one or more trust factors of a media asset meet the indicator is determined by determining whether one or more trust factors of the media asset include a trust factor in the indicator. That is, if a trust factor included in a trust profile is included in the trust factor of a media asset, the media asset's trust factor can be considered to meet the indicator. Alternatively, the trust factor can be content in the media asset's metadata, modification history, or characteristics of the media content. As shown in FIG7A , the indicators in the trust profile include TM1', TR1', TC1', and TM11'. TM1', TR1', TC1', and TM11' correspond to trust factors TM1, TR1, TC1, and TM11, respectively. For example, if TM1 is Shenzhen, Guangdong Province, and TM1' can be a location or China, then TM1 meets the indicator. Since TM11 is not included in one or more trust factors of the media asset, TM11 does not meet the corresponding indicator. In other words, if one or more trust factors of a media asset do not include the trust factor indicated by the indicator in the trust profile, the media asset does not meet the indicator requirements of the trust profile. If the trust factor of a media asset includes the trust factor included in the trust profile, the media asset's trust factor can be considered to meet the indicator.

[0309] As shown in Figure 7B , the indicators in the trust profile include TM1', TM2', TM3', and TC1', and the corresponding trust factors TM1, TM2, TM3, and TC1 are present in the trust credential. In other words, if one or more trust factors of a media asset contain all the trust factors indicated by the indicators in the trust profile, the media asset satisfies the indicator requirements of the trust profile.

[0310] In one implementation, the indicator may include a judgment condition indicating whether a target trust factor exists among one or more trust factors of a media asset. Whether the one or more trust factors satisfy the indicator can be determined by determining whether the judgment condition is satisfied. Trust information can be represented by a trust report, which uses a trust profile and trust credentials as input and generates and records the results of evaluating trust credentials based on the trust profile information. This evaluation assesses the trustworthiness of a given media asset. This result can be provided to users as trust information.

[0311] Subsequently, the trusted information can be used to generate a new trust list (which will be described in detail in subsequent embodiments), or as a file associated with the media asset.

[0312] The trust information may indicate whether one or more trust factors of the media asset satisfy the configuration file. Based on the trust information, the user may determine the trustworthiness of the media asset.

[0313] The above describes the basic process of the method shown in FIG6B . The following provides examples of specific implementations that may be used for some steps in the method shown in FIG6B .

[0314] In the above step 602, since different regions or different users may have different index requirements for the same media asset, multiple configuration files may be obtained. The multiple configuration files may be stored in a configuration file library. Each configuration file represents the index requirements for the media asset of a region or user. Therefore, how to obtain the trusted information of the media asset based on the configuration files and the trust factor includes multiple possible implementation methods, which are illustrated below with examples in conjunction with implementation methods A to D.

[0315] Implementation A: There is only one set of indicators for the trust profile.

[0316] There may be only one set of indicators for the trust factor of a media asset. Then, whether the trust factor of the media asset satisfies the set of indicators can be calculated based on the unique corresponding indicator requirement to obtain trustworthy information.

[0317] It should be understood that since there is only one set of indicator requirements, the association between the trust factor indicators and the configuration files may not be stored in the trust information, that is, it does not reflect which region or user's indicator requirements are used to obtain the trust information.

[0318] Implementation B: There are multiple trust profiles for the trust factor, and corresponding trust information is calculated for each trust profile.

[0319] Since different regions or users have different requirements for credibility, each trust profile includes a set of indicators. Different sets of indicators indicate the requirements that different regions or users must meet for the media assets. Furthermore, the satisfaction of the trust factor with respect to multiple indicator requirements can be calculated to obtain multiple pieces of trust information.

[0320] It should be understood that the association between the trust factor and the corresponding indicator requirement can be saved in the trusted information, so as to express which region or user the trusted information is targeted at.

[0321] Implementation C: In the case where there are multiple trust profiles, corresponding trust information is calculated only for a portion of them (eg, one trust profile).

[0322] Since different regions or users have different requirements for credibility, there may be multiple indicator requirements for the trust factor of media assets (different indicator requirements among the multiple requirements correspond to different regions or different users). When the system calculates trust information, the user can specify which group or multiple groups of indicator requirements the trust factor of the media asset meets.

[0323] It should be understood that the association between the trust factor of the media asset and the corresponding index requirement can be stored in the trusted information, so as to express the index requirement of which region or user the trusted information is targeted at.

[0324] Through the above-mentioned method, the present application can generate different trustworthy information corresponding to different indicator requirements for different scenarios (such as regions or users), thereby meeting the trustworthiness judgment needs of different scenarios.

[0325] Implementation D: A trust factor can contain multiple trust configurations. Different trust configurations indicate the index requirements that must be met for the media asset by different regions or users. The multiple trust configurations can be stored in one or more trust profiles. Trust information for the media asset can be obtained based on first configuration information and the trust factor of the media asset. The first configuration is one of the multiple trust configurations.

[0326] After obtaining the trusted information, the media assets can be updated using the trusted information. A specific implementation of updating the media assets using the trusted information is described below.

[0327] Referring to FIG. 7C , FIG. 7C is a schematic diagram of the framework of the trust report of this application;

[0328] In one implementation, the trust report includes report metadata and a report statement, wherein the report metadata records information describing the trust report, the report metadata includes information extracted from the trust profile, and the report statement includes a statement of whether the trust credential meets the credibility requirements in the trust profile.

[0329] In one implementation, the report metadata includes the name, issuer, issue date, and version number of the trust profile; that is, the report metadata includes metadata extracted from the trust profile.

[0330] In one implementation, there may be one or more report statements, and different expressions may be distinguished by expression identifiers.

[0331] In one implementation, a report statement may include different sections, each of which may record different report statements. When statements are expressed in sections, the report statement also includes a section identifier and a section title. The section identifier is used to identify the section in the report. The report statement may also include a description of the section or a description of the report statements in the section.

[0332] In one implementation, the report metadata may also include other information describing the report statements.

[0333] The trust report is explained below with reference to specific examples.

[0334] Refer to Figure 7D, which is a trust report based on AI-generated images.

[0335] In Section 1, the title is Test, the ID of Report Statement 1 is Content, the expression of the ID is that the hash value of the media content is consistent with the media hash value recorded in the trust credential, the report content is that the media content has not been modified, and the value is False, which means that Report Statement 1 indicates that the media content has been modified; in conjunction with Figure 7A, taking TM1 as the media hash value recorded in the trust credential as an example, TM1' is the hash value requirement of the media asset, for example, the requirement can be that the hash value of the media asset is consistent with the media hash value recorded in the trust credential.

[0336] The ID of report statement 2 is AIGC, the report content is that the media asset is generated by artificial intelligence, and the value is true, that is, report statement 2 indicates that the media asset is generated by artificial intelligence.

[0337] The report metadata is the name of the configuration file: AI generated file inspection, the issuer is XX Inspection Governance, the date is 2023.10.30, and the version is 1.0.

[0338] In one implementation, the report metadata may also include a report name and a report generation date.

[0339] Referring to FIG8A , FIG8A is a schematic diagram of the framework of the trust profile of this application;

[0340] In one implementation, the trust profile may include configuration metadata and configuration statements. The configuration metadata records information describing the trust profile, and the configuration statement is used to record statements about media asset credibility requirements or statements for evaluating trust credentials.

[0341] In one implementation, the configuration metadata may include the name, issuer, issue date, version number, etc. of the trust configuration file. In some examples, the configuration metadata may also include the language used by the trust configuration file.

[0342] In one implementation, a configuration statement may include an expression or formula that can be used to evaluate a trust credential. For example, the expression represents a requirement for a trust factor in the trust credential. The expression or formula may take one or more trust factors in the trust credential as input and output an evaluation result. The evaluation result may be a binary, numeric (floating point), text (string), or URI index. These indexes may be internal (JuMBF index) or external (URL).

[0343] In one example, using the media asset type as an example, an expression or formula could be: If the media asset type is AIGC, then the trust profile requires that the media asset type must be AIGC. Using the media hash value as an example, an expression or formula could be: If the hash value of the media content is equal to the media hash value in the trust factor in the trust credential, then the media content has not been modified.

[0344] In some implementations, the trust configuration file may be expressed in YAML format. The name, issuer, and version number of the trust configuration file may be expressed in string type in the trust configuration file. The expression or formula may be expressed in json-formula format.

[0345] In one implementation, a configuration statement may include an expression statement, which is used to record evaluation indicators for credibility assessment. The expression statement may include an expression identifier and an expression. The expression identifier is used to identify the expression statement of the trust profile, and the expression is used to evaluate the trust credentials. In one implementation, the expression statement may also include a description of the expression statement, which may not be referenced by the trust report. In some implementations, the expression statement may also include report content, which may be referenced by the trust report and may record an explanation of the output results of the expression statement. It should be noted that there may be one or more expression statements, and different expressions may be distinguished by the expression identifier.

[0346] In one implementation, a configuration statement may include different sections, each of which may record different expression statements. When expression statements are recorded in sections, the configuration statement also includes a section identifier and a section title, which are used to identify the section in the trust profile. The section title can be referenced by the trust report. The configuration statement may also include a description of the section or a description of the expression statements in the section, which does not need to be referenced by the trust report.

[0347] The following describes the trust configuration file with reference to specific examples.

[0348] In one example, as shown in FIG8B , a trust profile for a JPEG image generated by a camera is used for illustration. As shown in FIG8B , the trust profile can be named "Camera Profile," the publisher can be the XX platform, the release date can be October 30, 2023, and the version number can be 1.0. The camera configuration statement includes two sections. Section 1 is titled "General Information" and can include Expression Statement 1. The expression identifier of Expression Statement 1 can be content, the description of Expression Statement 1 can be "The content has not been modified," the expression of Expression Statement 1 can be "Whether the trust factor in the trust credential meets the condition," and the report content of Expression Statement 1 can be true or false, with true indicating that the media content has not been modified and false indicating that the media content has been modified. Section 2 is titled "GPS and Positioning Information" and can include Expression Statement 1. The expression identifier of Expression Statement 1 can be positioning information, the description of Expression Statement 1 can be "Location in China," the expression of Expression Statement 1 can be "The GPS interval in China where the image was taken," and the report content of Expression Statement 1 can be true or false, with true indicating that the GPS information indicates that the image was taken in China and false indicating that the GPS information indicates that the image was not taken in China.

[0349] Refer to Figure 9, which is a flowchart of a data processing method according to an embodiment of the present application.

[0350] 901. The media content is collected based on a hardware sensor, or the media content is generated by software.

[0351] The terminal device itself can collect media content through hardware sensors, or generate media content through software. For example, it can collect images through its own camera, or generate new media content through media content editing software (such as through AIGC).

[0352] When a terminal device obtains media content, it also needs to generate corresponding media assets through the media asset management module. Media assets may include metadata, trust records, etc.

[0353] In an embodiment of the present application, the media asset management module may collect the media content based on hardware sensors, or generate the media content using software, and generate trusted information based on the content in the media asset and add it to the media asset.

[0354] It should be understood that step 901 can be understood as an action before step 902. For example, step 901 can be a triggering condition for step 902 (optionally, step 901 can be one of multiple triggering conditions for step 902).

[0355] 902. Obtain one or more trust factors of a media asset; the media asset includes at least one of media content, metadata corresponding to the media content, and a trust record corresponding to the media content.

[0356] The description of step 902 can refer to the introduction of step 601 in the above embodiment, and the similarities are not repeated here.

[0357] 903. Determine whether each of the trust factors meets an indicator, and obtain trustworthy information.

[0358] The description of step 903 can refer to the introduction of step 602 in the above embodiment, and the similarities are not repeated here.

[0359] 904. Add the trusted information to the trust record.

[0360] When adding trust information to a trust record, the trust information may be added to assertions.

[0361] Specifically, the trusted information may be signed and added to assertions.

[0362] For example, the trusted information corresponding to a piece of media content can be signed and added to the claim as one of the items of the claim.

[0363] For example, the satisfaction of each indicator or part of the indicators in the trusted information can be signed and added to the claim as one of the items of the claim.

[0364] By adding the newly generated trust information to the trust record of the media asset, the trustworthiness of the media asset can be further enhanced.

[0365] In addition, the hash value of the trust information may be added to the claim in the trust list.

[0366] In addition, the signature of the trusted information may be added to the signature in the trust list.

[0367] Referring to FIG. 10 , FIG. 10 is a flowchart illustrating a data processing method according to an embodiment of the present application. Compared to FIG. 6B , the flowchart of FIG. 10 describes the process of generating trusted information and updating media assets through the relationship between functional modules, specifically including:

[0368] Generation module, extraction module, trust profile storage module, and verification module. The generation module is used to generate media assets. Each media asset consists of three parts: metadata, media content, and trust records. The extraction module takes media assets as input, extracts trust indicators from the media asset's metadata, trust records, and media content, and generates trust credentials for the media asset based on the extracted trust indicators. The trust profile storage module is responsible for storing trust profiles, where trust profiles are predefined by governments, platforms, users, and other entities for specific scenarios. The verification module takes trust credentials and trust profiles as input and evaluates whether the trust indicators in the trust credentials meet this predefined trust profile. Finally, a trust report is generated based on the results of this evaluation.

[0369] Based on Figure 6B, refer to Figures 11 and 12, which are flow charts of a data processing method according to an embodiment of the present application. Compared with Figure 6B, the flow charts of Figures 11 and 12 describe the generation of trusted information and the update process of media assets through the relationship between functional modules. The difference between Figures 11 and 12 is that Figure 11 is a process initiated by a generation algorithm, and Figure 12 is a process initiated by a verification algorithm.

[0370] FIG11 specifically includes:

[0371] 1. The generation algorithm is used to generate media assets. Each media asset consists of metadata, media content, and trust records.

[0372] 2. The generation algorithm passes the media assets to the extraction algorithm.

[0373] 3. The extraction algorithm takes the media asset as input, extracts trust indicators from the metadata, trust records and media content of the media asset, and generates trust credentials for the media asset based on the extracted trust indicators.

[0374] 4. The extraction algorithm passes the trust credentials to the verification algorithm.

[0375] 5. The verification algorithm triggers the verification process.

[0376] 6. The verification algorithm requests a trust profile from the trusted file storage side. The trust profile is predefined by the government, platform, user and other objects for specific scenarios.

[0377] 7. The trusted file storage side passes the trust configuration file to the verification algorithm.

[0378] 8. The verification algorithm takes the trust credential and the trust profile as input, evaluates whether the trust indicators in the trust credential meet this predefined trust profile, and generates a trust report based on the results of the evaluation.

[0379] 9. The verification algorithm uses the trust report to generate a new trust list.

[0380] 10. The verification algorithm returns the trust list to the generation algorithm.

[0381] 11. The generation algorithm will update the media asset by adding the new trust manifest to the trust record.

[0382] FIG12 specifically includes:

[0383] 0. The generation algorithm is used to generate media assets, each of which consists of metadata, media content, and trust records.

[0384] 1. The verification algorithm triggers the verification process.

[0385] 2. The verification algorithm requests a trust profile from the trusted file storage side. The trust profile is predefined by the government, platform, user and other objects for specific scenarios.

[0386] 3. The trusted file storage side passes the trust configuration file to the verification algorithm.

[0387] 4. The verification algorithm requests the trust credentials from the extraction algorithm.

[0388] 5. The extraction algorithm requests the media asset from the generation algorithm.

[0389] 6. The generation algorithm passes the media assets to the extraction algorithm.

[0390] 7. The extraction algorithm takes the media asset as input, extracts trust indicators from the metadata, trust records and media content of the media asset, and generates trust credentials for the media asset based on the extracted trust indicators.

[0391] 8. The extraction algorithm passes the trust credentials to the verification algorithm.

[0392] 9. The verification algorithm takes the trust credential and the trust profile as input, evaluates whether the trust indicators in the trust credential meet this predefined trust profile, and generates a trust report based on the results of the evaluation.

[0393] 10. The verification algorithm uses the trust report to generate a new trust list.

[0394] 11. The verification algorithm returns the trust list to the generation algorithm.

[0395] 12. The generation algorithm will update the media asset by adding the new trust manifest to the trust record.

[0396] After obtaining the trust information, a file associated with the media asset can be generated using the trust information. The file can be called and viewed by the user and used as a basis for credibility judgment.

[0397] 13 , which is a flow chart of a data processing method according to an embodiment of the present application, including:

[0398] 1301. The media content is collected based on a hardware sensor, or the media content is generated by software.

[0399] The description of step 1301 can refer to the introduction of step 901 in the above embodiment, and the similarities are not repeated here.

[0400] 1302. Obtain one or more trust factors of a media asset; the media asset includes at least one of media content, metadata corresponding to the media content, and a trust record corresponding to the media content;

[0401] The description of step 1302 can refer to the introduction of step 902 in the above embodiment, and the similarities are not repeated here.

[0402] 1303. Determine whether each of the trust factors meets the indicator, and obtain trustworthy information.

[0403] The description of step 1303 may refer to the introduction of step 903 in the above embodiment, and the similarities are not repeated here.

[0404] 1304. Generate a file associated with the media asset based on the trusted information.

[0405] The associated file may be a separately packaged file, which may be bound to the media asset, and the user may determine the credibility of the media content by viewing the file.

[0406] In addition to the automatic triggering based on the hardware sensor collecting the media content or the software generating the media content as described in FIG13 , the generation of the trustworthy information can also be based on the user's active triggering, as described below.

[0407] 14 , which is a flow chart of a data processing method according to an embodiment of the present application, including:

[0408] 1401. Receive a trust evaluation request for the media asset.

[0409] For example, a user may input a credibility assessment request for the media content through a credibility judgment application.

[0410] For example, the terminal side may input a credibility evaluation request for the media content through an interface of a cloud service that provides a credibility judgment service.

[0411] The request can carry media assets.

[0412] 1402. Obtain one or more trust factors of a media asset; the media asset includes at least one of media content, metadata corresponding to the media content, and a trust record corresponding to the media content;

[0413] The description of step 1402 can refer to the introduction of step 902 in the above embodiment, and the similarities are not repeated here.

[0414] 1403. Determine whether each of the trust factors meets the indicator, and obtain trustworthy information.

[0415] The description of step 1403 can refer to the introduction of step 903 in the above embodiment, and the similarities are not repeated here.

[0416] 1404. Send the trusted information to the end side.

[0417] The above embodiment introduces the process of generating trusted information for one media asset. The following describes the process of generating trusted information for multiple media assets in batches.

[0418] 15 , which is a flow chart of a data processing method according to an embodiment of the present application, including:

[0419] 1501. Obtain indication information of the media asset.

[0420] For example, the indication information may be a media asset ID. Since trust reports are generated for multiple media assets in batches, the corresponding media asset IDs need to be transmitted.

[0421] 1502. Acquire, according to the indication information, one or more trust factors of the media asset indicated by the indication information; the media asset includes at least one of media content, metadata corresponding to the media content, and a trust record corresponding to the media content;

[0422] 1503. Determine whether each of the trust factors meets the index and obtain trustworthy information.

[0423] 1504. According to the indication information, add the trusted information to the trust record corresponding to the media asset indicated by the indication information.

[0424] Based on Figure 15, refer to Figure 16A, which is a flow chart of a data processing method according to an embodiment of the present application. Compared with Figure 15, the flow chart of Figure 16A describes the batch generation of trusted information and the update process of media assets through the relationship between functional modules.

[0425] FIG. 16A specifically includes:

[0426] 1. The generation algorithm is used to generate media assets. Each media asset consists of metadata, media content, and trust records.

[0427] 2. The generation algorithm sends a request to generate a trust credential (including the ID of the media asset and the corresponding media asset) to the extraction algorithm.

[0428] 3. The extraction algorithm takes media assets as input, extracts trust indicators from the metadata, trust records and media content of each media asset, and generates trust credentials for each media asset based on the extracted trust indicators.

[0429] 4. The extraction algorithm sends the trust credential to the verification algorithm in the format of (media asset ID, corresponding trust credential).

[0430] 5. The verification algorithm triggers the verification process.

[0431] 6. The verification algorithm requests a trust profile from the trusted file storage side. The trust profile is predefined by the government, platform, user and other objects for specific scenarios.

[0432] 7. The trusted file storage side passes the trust configuration file to the verification algorithm.

[0433] 8. The verification algorithm takes the trust credential and trust profile corresponding to each media asset as input, evaluates whether the trust indicators in the trust credential corresponding to each media asset meet the predefined trust profile, and generates a trust report based on the evaluation results. The verification algorithm generates a trust report for each media asset based on the evaluation results.

[0434] 9. The verification algorithm uses the trust report to generate a new trust manifest for each media asset.

[0435] 10. The verification algorithm returns the trust list to the generation algorithm in the format of (media asset ID, corresponding new trust list).

[0436] 11. The generation algorithm will update the media asset by adding the new trust manifest to the trust record.

[0437] The above-mentioned FIG. 6B to FIG. 16A introduce the process of generating or using the trusted information. Next, the process of generating and using the trust credential will be introduced with reference to the accompanying drawings.

[0438] 16B , which is a flow chart of a data processing method provided in an embodiment of the present application. The flow chart mainly describes the process of generating trusted information. As shown in FIG16B , the data processing method provided in an embodiment of the present application includes:

[0439] S1601. Acquire media assets. The media assets include at least one of media content, metadata corresponding to the media content, and a trust record corresponding to the media content.

[0440] For the description of S1601 , reference may be made to the introduction of media assets in the above embodiment, and similarities will not be repeated here.

[0441] S1602: Determine one or more trust factors of the media asset according to the media asset.

[0442] The description of S1602 may refer to the introduction of the trust factor in the above embodiment, and the similarities are not repeated here.

[0443] The trust factor can be encapsulated in the trust credential.

[0444] In a possible implementation, the trust credential may be added to the trust record to form a new trust record.

[0445] In a possible implementation, a file associated with the media asset may also be generated according to the trust credential.

[0446] The associated file may be a separately packaged file, which may be bound to the media asset, and the user may determine the credibility of the media content by viewing the file.

[0447] By obtaining the trust factor from the media asset, the trust factor of the media asset can be separately encapsulated into a new file. The file containing the trust factor can represent the credibility information of the media asset. When verifying the credibility of the media asset, the trust factor of the media asset can be directly read from the file containing the trust factor, avoiding direct reading of the media asset during the credibility verification of the media asset, which may cause privacy leakage.

[0448] As shown in FIG16C, FIG16C is a schematic diagram of a method for generating a trust record. In combination with FIG6A, this embodiment provides a method for generating a trust record. Optionally, the trust record can also be metadata. The method for generating a trust record includes:

[0449] S161: Acquire first media content;

[0450] Exemplarily, the first media content may be media content generated by the first electronic device, or may be media content received by the first electronic device from another electronic device. For example, if the first media content is an image, then the first media content may be an image captured by the first electronic device, a screenshot, or an AI-generated image, and this application does not limit the manner in which the first electronic device generates the image. Alternatively, the first media content may be an image received by the first electronic device from another electronic device, and this application does not limit this.

[0451] S162: Generate a trust record for the first media content, where the trust record for the first media content includes: initial information of the first media content, a hard binding of the first media content, and a first digital signature; the first digital signature is a digital signature of first data, and the first data is data determined based on at least the initial information and the hard binding of the first media content.

[0452] The technical terms involved in steps S161 and S162 are consistent with the terminology explanations in the above embodiments and are not repeated here.

[0453] As shown in FIG16D , FIG16D is a schematic diagram of a data processing method. The data processing method of this embodiment includes:

[0454] S161D: Obtain a configuration statement; the configuration statement may be input by a user, a platform, or an organization;

[0455] S162D: Get the trust profile according to the configuration statement;

[0456] In one implementation, the issuer information and the configuration statement may be encapsulated to obtain a trust profile.

[0457] In one implementation, the issuer may generate multiple trust profiles and store the multiple trust profiles in a trust profile repository respectively.

[0458] S163D: Store the trust configuration file or send the trust configuration file.

[0459] In one implementation, user A can obtain a trust profile from user B, a platform, or an organization. Upon receiving a request from user A to obtain a trust profile, user B, the platform, or the organization can send the trust profile to user A. In another implementation, user B, the platform, or the organization can obtain the trust profile from a trust profile repository and then send the trust profile to user A. In another implementation, the trust profile repository can store multiple trust profiles, and the target trust profile required by user A can be obtained from the trust profile repository. For example, the target trust profile can be the trust profile required by the region where user A is located, the trust profile required by user A, or the trust profile required by the platform.

[0460] By recording the requirements for media asset credibility through a trust profile, platforms, organizations, or users can manage media assets. Trust profiles can be used to assess the credibility of media assets. By distributing trust profiles, platform users can verify the credibility of media assets.

[0461] The technical terms involved in steps S161D-S163D are consistent with the term explanations in the above embodiments and will not be repeated here.

[0462] The data processing method of this embodiment may further include: obtaining metadata of the trust profile, where the name of the trust profile may be input by the platform, organization, or user, the issuer and issuance date of the trust profile may be read from the system, and the version number may be input by the user or automatically generated.

[0463] A trust profile is further generated based on the metadata of the trust profile, wherein the trust profile includes the metadata of the trust profile. The metadata of the trust profile and the configuration statement can be encapsulated together to obtain the trust profile.

[0464] As shown in FIG16E , FIG16E is a schematic diagram of a data processing method. The data processing method of this embodiment includes:

[0465] S161E: Obtain a trust credential and a trust profile; the trust credential indicates the credibility of the media asset, and the trust profile indicates the credibility requirement of the media asset;

[0466] In one implementation, the trust configuration file may be obtained from a server or other device, or may be read locally; the trust credential may be obtained from other device, or may be sent by the user.

[0467] S162E: Generate a trust report based on the trust credential and the trust profile, the trust report including report metadata and a report statement, the report metadata recording information describing the trust report, the report metadata including information extracted from the trust profile, and the report statement including a statement on whether the trust credential meets the credibility requirements in the trust profile.

[0468] S162E includes: S1621E: reading the trust factor from the trust credential and reading the expression statement from the trust profile;

[0469] S1622E: Input the trust factor of the trust credential into the formula or expression expressing the statement, and determine whether the trust factor satisfies the credibility requirement;

[0470] S1623E: Generate the trust report based on the conclusion of whether the trust factor meets the credibility requirement.

[0471] In one implementation, generating a trust report based on the trust configuration file includes extracting information from configuration metadata to generate report metadata. In one example, the configuration metadata in the trust configuration file can be directly read and copied into the trust report.

[0472] By generating a trust report based on trust credentials and a trust profile, the trustworthiness of the media asset can be assessed by simply reading the trustworthiness information from the trust credentials and the trustworthiness requirements from the profile, rather than having to read the media asset itself. Metadata from the trust profile is also included in the trust report, allowing further verification of the media asset's trustworthiness based on the trust profile information.

[0473] The technical terms involved in steps S161E-S162E are consistent with the terminology explanations in the above embodiments and will not be repeated here.

[0474] 17 , which is a schematic diagram of the structure of a data processing device provided in an embodiment of the present application, wherein the device 1700 includes:

[0475] Acquisition module 1701 is configured to acquire one or more trust factors of a media asset; the media asset includes at least one of media content, metadata corresponding to the media content, and a trust record corresponding to the media content;

[0476] The specific description of the acquisition module 1701 can refer to the description of step 601 in the above embodiment, which will not be repeated here.

[0477] The processing module 1702 is configured to determine whether the one or more trust factors meet an indicator.

[0478] The specific description of the processing module 1702 can refer to the description of step 602 in the above embodiment, which will not be repeated here.

[0479] In a possible implementation, the obtaining module 1701 is further configured to:

[0480] First trust configuration information is obtained, where the first trust configuration information includes indicators that the media asset must meet.

[0481] In a possible implementation, the one or more trust factors are determined based on at least one of the media content, metadata corresponding to the media content, and a trust record corresponding to the media content.

[0482] In one possible implementation, the one or more trust factors are encapsulated in a trust credential.

[0483] In one possible implementation, the indicator includes a trust factor that the media asset needs to satisfy.

[0484] In a possible implementation, the processing module 1702 is specifically configured to:

[0485] It is determined whether the trust factor in the indicator is included in the one or more trust factors, or whether the one or more trust factors include the trust factor in the indicator.

[0486] In a possible implementation, the processing module 1702 is further configured to:

[0487] Generate trust information for the media asset, the trust information being used to indicate whether the one or more trust factors meet an indicator, the trust factor including a parameter indicating the trustworthiness of the media asset. In one possible implementation, the processing module 1702 is further configured to:

[0488] The trust information is added to the trust record.

[0489] In one possible implementation, the trust record includes a trust list;

[0490] The processing module 1702 is specifically configured to:

[0491] Add the trusted information to the trust list.

[0492] In a possible implementation, the obtaining module 1701 is further configured to:

[0493] Obtaining information indicating the media asset;

[0494] The processing module 1702 is specifically configured to:

[0495] According to the indication information, the trusted information is added to the trust record corresponding to the media asset indicated by the indication information.

[0496] In a possible implementation, the trust information is encapsulated in a trust report.

[0497] In a possible implementation, the processing module 1702 is further configured to:

[0498] A file associated with the media asset is generated based on the trusted information.

[0499] In a possible implementation, the first trust configuration information includes one of a plurality of trust configuration information, and different trust configuration information indicates that different regions or users need to meet index requirements for the media asset.

[0500] In a possible implementation, the action of obtaining one or more trust factors of the media asset is triggered by hardware sensors capturing the media content or software generating the media content.

[0501] In a possible implementation, before obtaining the multiple indicators and configuration files of the media assets, the obtaining module 1701 is further configured to:

[0502] A trustworthiness assessment request for the media content is received.

[0503] In a possible implementation, the media content is at least one of an image, a video, or an audio.

[0504] In addition, an embodiment of the present application further provides a data processing device, the device comprising:

[0505] Acquisition module 1701 is used to acquire media assets; the media assets include at least one of media content, metadata corresponding to the media content, and trust records corresponding to the media content;

[0506] The specific description of the processing module 1701 can refer to the description of step 1601 in the above embodiment, which will not be repeated here.

[0507] The processing module 1702 is configured to determine one or more trust factors of the media asset, where the one or more trust factors are used to evaluate the credibility of the media asset.

[0508] The specific description of the processing module 1702 can refer to the description of step 1602 in the above embodiment, which will not be repeated here.

[0509] In one possible implementation, the one or more trust factors are encapsulated in a trust credential.

[0510] In a possible implementation, the one or more trust factors are determined based on at least one of the media content, metadata corresponding to the media content, and a trust record corresponding to the media content.

[0511] In one possible implementation, the one or more trust factors are used to determine trust information of the media asset, and the trust information is used to indicate whether the one or more trust factors meet a criterion.

[0512] In one possible implementation, the indicator includes a trust factor that the media asset needs to satisfy.

[0513] In one possible implementation, the trust factor includes a parameter indicating the trustworthiness of the media asset.

[0514] In a possible implementation, the media content is at least one of an image, a video, or an audio.

[0515] In addition, an embodiment of the present application further provides a data processing device, the device comprising:

[0516] Acquisition module 1701 is used to acquire trust credentials and trust profiles; the trust credentials represent the credibility of the media asset, and the trust profile represents the credibility requirements of the media asset;

[0517] Processing module 1702 is used to generate a trust report based on the trust credentials and the trust profile, where the trust report includes report metadata and a report statement, where the report metadata records information describing the trust report, the report metadata includes information extracted from the trust profile, and the report statement includes a statement on whether the trust credentials meet the credibility requirements in the trust profile.

[0518] In one implementation, the processing module 1702 is further configured to

[0519] Reading the trust factor from the trust credential and reading the expression statement from the trust configuration file;

[0520] Inputting the trust factor of the trust credential into a formula or expression expressing the statement and determining whether the trust factor satisfies the credibility requirement;

[0521] A trust report is generated based on the conclusion of whether the trust factor meets the credibility requirements.

[0522] The processing module 1702 is further configured to store and / or send the trust report.

[0523] In addition, an embodiment of the present application further provides a data processing device, the device comprising:

[0524] An acquisition module 1701 is configured to acquire a configuration statement, wherein the configuration statement indicates credibility requirements that a media asset must meet.

[0525] Processing module 1702 generates a trust profile based on the configuration statement, where the trust profile includes the configuration statement; the configuration statement includes an expression statement, and the expression statement includes a formula or expression, where the formula or expression represents a requirement for a trust factor in the trust credential, where the trust factor is a parameter representing the credibility of the media asset.

[0526] In one implementation, the acquisition module 1701 further acquires metadata of the trust profile;

[0527] The processing module 1702 further generates the trust profile according to the metadata. The trust profile also includes the metadata, and the metadata includes the name, issuer, issue date, and version number of the trust profile.

[0528] In one implementation, the processing module 1702 further receives a request from a user, the request being for obtaining the trust profile; and sends the trust profile to the user.

[0529] In one implementation, the processing module 1702 further obtains a target trust profile from a profile library in response to the user's request, the profile library including a plurality of trust profiles, and the target profile is a trust profile corresponding to the user;

[0530] The sending the trust profile to the user includes: sending the target trust profile to the user.

[0531] In one implementation, the processing module 1702 further stores the trust profile.

[0532] Next, an execution device provided in an embodiment of the present application is introduced. Please refer to Figure 18. Figure 18 is a structural schematic diagram of the execution device provided in an embodiment of the present application. The execution device 1800 can be specifically manifested as a mobile phone, a tablet, a laptop computer, a smart wearable device, etc., which is not limited here. Specifically, the execution device 1800 includes: a receiver 1801, a transmitter 1802, a processor 1803 and a memory 1804 (wherein the number of processors 1803 in the execution device 1800 can be one or more, and Figure 18 takes one processor as an example), wherein the processor 1803 may include an application processor 18031 and a communication processor 18032. In some embodiments of the present application, the receiver 1801, the transmitter 1802, the processor 1803 and the memory 1804 may be connected via a bus or other means.

[0533] Memory 1804 may include read-only memory and random access memory, and provides instructions and data to processor 1803. A portion of memory 1804 may also include non-volatile random access memory (NVRAM). Memory 1804 stores processor and operation instructions, executable modules, or data structures, or subsets or extended sets thereof. The operation instructions may include various operation instructions for implementing various operations.

[0534] Processor 1803 controls the operation of the execution device. In specific applications, the various components of the execution device are coupled together via a bus system. In addition to a data bus, the bus system may also include a power bus, a control bus, and a status signal bus. However, for clarity, all bus systems are referred to as a bus system in the figure.

[0535] The methods disclosed in the above embodiments of the present application can be applied to or implemented by processor 1803. Processor 1803 can be an integrated circuit chip with signal processing capabilities. During implementation, each step of the above method can be completed by hardware integrated logic circuits or software instructions in processor 1803. The above processor 1803 can be a general-purpose processor, a digital signal processor (DSP), a microprocessor, or a microcontroller, and can further include an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. The processor 1803 can implement or execute the various methods, steps, and logic block diagrams disclosed in the embodiments of the present application. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the methods disclosed in conjunction with the embodiments of the present application can be directly implemented and executed by a hardware decoding processor, or by a combination of hardware and software modules in the decoding processor. The software module can be located in a storage medium well-known in the art, such as random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, etc. The storage medium is located in memory 1804, and processor 1803 reads information from memory 1804 and, in conjunction with its hardware, completes the steps of the above method.

[0536] Receiver 1801 can be used to receive input digital or character information and generate signal input related to executing relevant settings and function control of the device. Transmitter 1802 can be used to output digital or character information; transmitter 1802 can also be used to send instructions to the disk group to modify the data in the disk group.

[0537] In an embodiment of the present application, in one case, the processor 1803 is used to execute the steps of the data processing method in the embodiments corresponding to Figures 6B to 16A.

[0538] The present application also provides a server. Please refer to Figure 19, which is a schematic diagram of the structure of a server provided by the present application. Specifically, the server 1900 is implemented by one or more servers. The server 1900 may vary greatly due to different configurations or performance. It may include one or more central processing units (CPUs) 1919 (for example, one or more processors) and memory 1932, and one or more storage media 1930 (for example, one or more mass storage devices) for storing application programs 1942 or data 1944. Among them, the memory 1932 and the storage medium 1930 can be temporary storage or permanent storage. The program stored in the storage medium 1930 may include one or more modules (not shown in the figure), each module may include a series of instruction operations in the server. Furthermore, the central processing unit 1919 can be configured to communicate with the storage medium 1930 to execute a series of instruction operations in the storage medium 1930 on the server 1900.

[0539] The server 1900 may also include one or more power supplies 1919, one or more wired or wireless network interfaces 1950, one or more input and output interfaces 1958; or, one or more operating systems 1941, such as Windows Server™, Mac OS X™, Unix™, Linux™, FreeBSD™, etc.

[0540] In the embodiment of the present application, the central processing unit 1919 is used to execute the steps of the data processing method in the embodiments corresponding to Figures 6B to 16A.

[0541] An embodiment of the present application also provides a computer program product including computer-readable instructions, which, when executed on a computer, enables the computer to execute the steps executed by the aforementioned execution device, or enables the computer to execute the steps executed by the aforementioned training device.

[0542] A computer-readable storage medium is also provided in an embodiment of the present application, which stores a program for signal processing. When the computer-readable storage medium is run on a computer, it enables the computer to execute the steps executed by the aforementioned execution device, or enables the computer to execute the steps executed by the aforementioned training device.

[0543] It should also be noted that the device embodiments described above are merely illustrative, wherein the units described as separate components may or may not be physically separate, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed across multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the present embodiment. In addition, in the drawings of the device embodiments provided in this application, the connection relationship between the modules indicates that there is a communication connection between them, which can be specifically implemented as one or more communication buses or signal lines.

[0544] Through the description of the above embodiments, those skilled in the art can clearly understand that the present application can be implemented by means of software plus necessary general hardware, and of course can also be implemented by special hardware including application-specific integrated circuits, special CPUs, special memories, special components, etc. In general, all functions performed by computer programs can be easily implemented with corresponding hardware, and the specific hardware structures used to implement the same function can also be diverse, such as analog circuits, digital circuits or special circuits, etc. However, for the present application, software program implementation is a better implementation method in most cases. Based on this understanding, the technical solution of the present application is essentially or the part that contributes to the prior art can be embodied in the form of a software product, which is stored in a readable storage medium, such as a computer's floppy disk, USB flash drive, mobile hard disk, ROM, RAM, magnetic disk or optical disk, etc., and includes a number of instructions to enable a computer device (which can be a personal computer, training equipment, or network equipment, etc.) to execute the methods described in each embodiment of the present application.

[0545] In the above embodiments, all or part of the embodiments may be implemented by software, hardware, firmware, or any combination thereof. When implemented by software, all or part of the embodiments may be implemented in the form of a computer program product.

[0546] The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function described in the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instructions can be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can be transmitted from a website, a computer, a training device or a data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) mode to another website, a computer, a training device or a data center. The computer-readable storage medium can be any available medium that a computer can store or a data storage device such as a training device, a data center, etc. that includes one or more available media integrations. The available medium can be a magnetic medium, (e.g., a floppy disk, a hard disk, a tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a solid-state drive (SSD)).

Claims

1. A data processing method, characterized in that: The method comprises: Obtaining a configuration statement, wherein the configuration statement indicates a trustworthiness requirement to be satisfied by a media asset; A trust profile is generated according to the configuration statement, wherein the trust profile includes the configuration statement; the configuration statement includes a formula or an expression, wherein the formula or expression represents a requirement of a trust factor in a trust credential, wherein the trust factor is a parameter representing the credibility of the media asset.

2. The data processing method according to claim 1, characterized in that: The formula or expression is expressed in the format of json formula.

3. The data processing method according to claim 1, characterized in that: The method further comprises: Get the metadata of the trust profile; The trust profile is further generated according to the metadata, wherein the trust profile also includes the metadata, and the metadata includes the name, issuer, issue date and version number of the trust profile.

4. The data processing method according to claim 3, characterized in that: The name, issuer and version number of the trust configuration file are expressed in the trust configuration file using a string type.

5. The data processing method according to any one of claims 1 to 4, characterized in that: The trust configuration file is expressed in YAML format.

6. The data processing method according to claim 2, characterized in that: The media asset includes media content, and the media asset also includes at least one of metadata of the media content and a trust record of the media content; the one or more trust factors are determined based on the media content, metadata corresponding to the media content, and at least one of a trust record corresponding to the media content.

7. The data processing method according to claim 1, characterized in that: The method further comprises: receiving a request from a user, the request being used to obtain the trust profile; The trust profile is sent to the user.

8. The data processing method according to claim 7, characterized in that: The method further comprises: In response to a request from the user, obtaining a target trust profile from a profile library, the profile library including a plurality of trust profiles, the target profile being a trust profile corresponding to the user; The sending the trust profile to the user includes: sending the target trust profile to the user.

9. The data processing method according to claim 1, characterized in that: The method also includes storing the trust profile.

10. A data processing device, characterized in that: include: An acquisition module, configured to configure a statement, wherein the configuration statement indicates a credibility requirement to be satisfied by a media asset; A processing module is used to generate a trust profile according to the configuration statement, wherein the trust profile includes the configuration statement, and the configuration statement includes a formula or an expression, wherein the formula or expression represents a requirement of a trust factor in a trust credential, and the trust factor is a parameter representing the credibility of the media asset.

11. The data processing device according to claim 10, characterized in that: The processing module is further used to receive a request from a user, where the request is used to obtain the trust configuration file; The processing module is further configured to send the trust configuration file to the user.

12. The data processing device according to claim 10, characterized in that: The acquisition module is also used to acquire metadata of the trust configuration file; The processing module further generates the trust profile according to the metadata, wherein the trust profile also includes the metadata, and the metadata includes the name, issuer, issue date and version number of the trust profile.

13. A data processing device, characterized in that: The device includes a memory and a processor; the memory stores codes, and the processor is configured to obtain the codes and execute the method according to any one of claims 1 to 9.

14. A computer-readable storage medium, characterized in that: The method comprises computer-readable instructions, which, when executed on a computer device, cause the computer device to execute the method according to any one of claims 1 to 9.

15. A computer program product, characterized in that The method comprises computer-readable instructions, and when the computer-readable instructions are executed on a computer device, the computer device is caused to execute the method according to any one of claims 1 to 9.