Digital resource display method, device and node

Abstract

Embodiments of the present specification provide a digital resource display method, apparatus and node. In the method, a user device can send a transaction for obtaining a target digital resource to a blockchain system in response to a display tag included in page data of a display page, the display tag corresponding to a resource identifier of the target digital resource, a target decentralized identity (DID) of an organization to which the display page belongs, and a signature based on a private key of the target DID, the transaction including the resource identifier, the target DID and the signature. Subsequently, the user device can receive the target digital resource returned by the blockchain system, which is sent by the blockchain system after determining that the target DID is an authorized DID of the target digital resource. Then, the user device can display the target digital resource in the display page.

Description

Technical Field

[0001] The embodiments in this specification belong to the field of blockchain technology, and in particular relate to digital resource display methods, devices and nodes. Background Technology

[0002] Digital resources (such as images) can be displayed on the current user side (such as web pages or APP pages). These digital resources may be protected resources, such as copyrighted resources.

[0003] There is an urgent need for a reasonable and reliable solution to enable the credible display of digital resources, thereby protecting the owners of digital resources (such as copyright holders) and enhancing users' trust in the digital resources they browse. Summary of the Invention

[0004] The purpose of this invention is to provide a digital resource display scheme that uses display tags in the page data of the display page to reference digital resources authorized by the organization to which the display page belongs in the blockchain system. This allows user devices to obtain authorized resources from the blockchain system, thereby achieving a trustworthy display of digital resources. This is beneficial for protecting the owners of digital resources (such as copyright holders) and enhancing the user's trust in the digital resources they browse.

[0005] This specification provides a method for displaying digital resources, executed by a user device. The method includes: responding to a display tag included in page data of a display page, sending a transaction to a blockchain system for acquiring a target digital resource, wherein the display tag corresponds to a resource identifier of the target digital resource, a target decentralized identity identifier (DID) of the organization to which the display page belongs, and a signature based on a private key of the target DID; the transaction includes the resource identifier, the target DID, and the signature; receiving the target digital resource returned by the blockchain system, which was sent by the blockchain system after determining that the target DID is the authorized DID of the target digital resource; and displaying the target digital resource on the display page.

[0006] A second aspect of this specification provides a method for displaying digital resources, executed by a node in a blockchain system. The method includes: receiving a transaction sent by a user device for acquiring a target digital resource, the transaction being sent by the user device in response to a display tag included in page data of a display page, the display tag corresponding to a resource identifier of the target digital resource, a target decentralized identity identifier (DID) of the organization to which the display page belongs, and a signature based on a private key of the target DID; the transaction including the resource identifier, the target DID, and the signature; verifying the signature by executing the transaction, and in response to the signature passing verification, acquiring authorized DID information corresponding to the target digital resource, and determining whether the target DID is associated with the resource identifier contained in the authorized DID information; in response to a yes determination, acquiring the target digital resource stored in the blockchain system; and returning the target digital resource to the user device.

[0007] A third aspect of this specification provides a digital resource display device applied to a user device. The device includes: a sending unit configured to send a transaction for acquiring a target digital resource to a blockchain system in response to a display tag included in page data of a display page. The display tag corresponds to a resource identifier of the target digital resource, a target decentralized identity identifier (DID) of the organization to which the display page belongs, and a signature based on a private key of the target DID. The transaction includes the resource identifier, the target DID, and the signature. A receiving unit configured to receive the target digital resource returned by the blockchain system, which is sent by the blockchain system after determining that the target DID is the authorized DID of the target digital resource. A display unit configured to display the target digital resource on the display page.

[0008] This specification provides a node in a blockchain system, comprising: a receiving unit configured to receive a transaction sent by a user device for acquiring a target digital resource, the transaction being sent by the user device in response to a display tag included in page data of a display page, the display tag corresponding to a resource identifier of the target digital resource, a target decentralized identity identifier (DID) of the organization to which the display page belongs, and a signature based on a private key of the target DID, the transaction including the resource identifier, the target DID, and the signature; an execution unit configured to verify the signature by executing the transaction, and in response to the signature being verified, to acquire authorized DID information corresponding to the target digital resource, and to determine whether the target DID is associated with the resource identifier being included in the authorized DID information; an acquisition unit configured to acquire the target digital resource stored in the blockchain system in response to a determination result that is yes; and a sending unit configured to return the target digital resource to the user device.

[0009] The fifth aspect of this specification provides a computer-readable storage medium having a computer program stored thereon, which, when executed in a computer, causes the computer to perform the method described in either the first or second aspect.

[0010] A sixth aspect of this specification provides a computing device including a memory and a processor, wherein the memory stores executable code, and the processor, when executing the executable code, implements the method described in either the first or second aspect.

[0011] The seventh aspect of this specification provides a computer program product that, when executed in a computer, causes the computer to perform the method described in either the first or second aspect.

[0012] In the solution provided in the embodiments of this specification, the user equipment can respond to a display tag included in the page data of the displayed page and send a transaction to the blockchain system to obtain a target digital resource. The display tag corresponds to the resource identifier of the target digital resource, the target decentralized identity identifier (DID) of the organization to which the displayed page belongs, and a signature based on the private key of the target DID. The transaction includes the resource identifier, the target DID, and the signature. Subsequently, the user equipment can receive the target digital resource returned by the blockchain system, which is sent by the blockchain system after determining that the target DID is the authorized DID of the target digital resource. Then, the user equipment can display the target digital resource on the displayed page. Thus, by using a display tag in the page data of the displayed page to reference digital resources authorized by the organization to which the displayed page belongs in the blockchain system, the user equipment can obtain authorized resources from the blockchain system, achieving a trusted display of digital resources. This is beneficial for protecting the owners of digital resources (such as copyright holders) and enhancing the user's trust in the digital resources they browse. Attached Figure Description

[0013] To more clearly illustrate the technical solutions of the embodiments in this specification, the drawings used in the description of the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments recorded in this specification. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0014] Figure 1 This is a diagram of a blockchain architecture in one embodiment;

[0015] Figure 2 This is a schematic diagram illustrating one application scenario in which the embodiments of this specification can be applied;

[0016] Figure 3 This is a flowchart of the resource reference authorization application process in the embodiments of this specification;

[0017] Figure 4 This is a flowchart of the digital resource display method in the embodiments of this specification;

[0018] Figure 5 This is a schematic diagram of the structure of the digital resource display device in the embodiments of this specification;

[0019] Figure 6 This is a schematic diagram of the structure of a node in the blockchain system described in the embodiments of this specification. Detailed Implementation

[0020] To enable those skilled in the art to better understand the technical solutions in this specification, the technical solutions in the embodiments of this specification will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this specification, and not all embodiments. Based on the embodiments in this specification, all other embodiments obtained by those skilled in the art without creative effort should fall within the scope of protection of this specification.

[0021] Blockchain is a novel application model of computer technologies such as distributed data storage, peer-to-peer transmission, consensus mechanisms, and cryptographic algorithms. In a blockchain, data blocks are sequentially linked together in a chain-like data structure, and cryptographic methods are used to ensure the immutability and forgery resistance of these data blocks. Due to its decentralized, immutable, and autonomous characteristics, blockchain is receiving increasing attention and application.

[0022] Figure 1 A blockchain architecture diagram from one embodiment is shown. Figure 1 In the blockchain architecture diagram shown, blockchain 100 includes N nodes. Figure 1 The diagram illustrates nodes 1 through 8. The lines connecting the nodes schematically represent P2P (Peer-to-Peer) connections, such as TCP connections, used for data transfer between nodes. These nodes can store the entire ledger, i.e., the state of all blocks and all accounts. Each node in the blockchain can produce the same state by executing the same transactions, and each node can store the same state database.

[0023] In the blockchain field, a transaction refers to a unit of task executed and recorded within the blockchain. A transaction typically includes a From field, a To field, and a Data field. Specifically, in the case of a transfer transaction, the From field represents the account address initiating the transaction (i.e., initiating a transfer task to another account), the To field represents the account address receiving the transaction (i.e., receiving the transfer), and the Data field includes the transfer amount.

[0024] Blockchain provides the functionality of smart contracts. A smart contract on the blockchain is a contract that can be triggered and executed through transactions within the blockchain system. Smart contracts can be defined in the form of code. Calling a smart contract on the blockchain involves initiating a transaction pointing to the smart contract's address, causing each node in the blockchain to run the smart contract code in a distributed manner.

[0025] In a contract deployment scenario, for example, Bob sends a transaction containing information about creating a smart contract (i.e., deploying the contract) to a server such as... Figure 1 In the blockchain shown, the `data` field of the transaction includes the code (such as bytecode or machine code) of the contract to be created, and the `to` field of the transaction is empty, indicating that the transaction is used to deploy the contract. After the nodes reach an agreement through the consensus mechanism, they determine the contract address "0x6f8ae93…". Each node adds a contract account corresponding to the contract address of the smart contract to the state database, allocates state storage corresponding to the contract account, stores the contract code, and saves the hash value of the contract code in the contract's state storage, thus the contract is successfully created.

[0026] In scenarios where contracts are invoked, for example, Bob sends a transaction to invoke a smart contract, such as... Figure 1 In the blockchain shown, the `from` field of this transaction is the address of the account of the transaction initiator (i.e., Bob), the `to` field is the aforementioned "0x6f8ae93…", which is the address of the smart contract being invoked, and the `data` field of the transaction includes the method and parameters for invoking the smart contract. After consensus is reached on this transaction in the blockchain, each node in the blockchain can execute the transaction, thereby executing the contract separately, and updating the state database based on the execution of the contract.

[0027] As mentioned earlier, digital resources (such as images) can be displayed on the current user side (such as web pages or APP pages). These digital resources may be protected resources, such as copyrighted resources.

[0028] This specification provides a digital resource display scheme that uses display tags in the page data of the display page to reference digital resources authorized by the organization to which the display page belongs in the blockchain system. This allows user devices to obtain authorized resources from the blockchain system, enabling the credible display of digital resources. This is beneficial for protecting the owners of digital resources (such as copyright holders) and enhancing the user's trust in the digital resources they browse.

[0029] See Figure 2 This is a schematic diagram illustrating one application scenario to which the embodiments of this specification can be applied. Figure 2The application scenario shown can include user device 201 (user A), device 202 (organization B), device 203 (resource owner C), and blockchain system 204. User device 201 can be a terminal device supporting page display, such as a smartphone, tablet, laptop, or desktop computer. Device 202 can be a server. Device 203 can be either a terminal device or a server. Blockchain system 204 can include N nodes; for an explanation of these N nodes, please refer to the relevant descriptions above, which will not be repeated here. Furthermore, blockchain system 204 can communicate with user device 201 and device 203 respectively, and user device 201 can communicate with device 202.

[0030] Specifically, device 202 can be a server for any of the software owned by organization B, such as a website, client application (APP), or mini-program, and this server can store page data for each page of that software. At least some of these pages can reference digital resources, such as digital resources owned by other organizations or individuals. These other organizations or individuals can be referred to as resource owners, and organization B can be referred to as resource users.

[0031] When Organization B wants page P on at least some of the aforementioned pages to reference target digital resources (such as target images, target videos, or target 3D models) owned by resource owner C, Organization B can, for example, first negotiate with resource owner C regarding the use of the target digital resources and obtain the right to use the target digital resources from resource owner C. The target digital resources may, for example, be copyrighted resources, such as resources protected by copyright. Afterwards, Organization B can apply to device 203 for a resource reference license related to the target digital resources.

[0032] In one implementation, Figure 2 The application scenario shown can also include device 205 of organization B, which can communicate with device 203. Optionally, device 205 can also communicate with blockchain system 204. Device 205 can be, for example, a terminal device of organization B. Organization B can perform actions such as... Figure 3 The resource reference authorization application process shown is used to request resource reference authorization related to the target digital resource from device 203. Among them, Figure 3 This is a flowchart of the resource reference authorization application process in the embodiments of this specification.

[0033] like Figure 3 As shown, in step S301, device 205 of mechanism B determines the target DID of mechanism B.

[0034] Specifically, device 205 can create a public and private key pair, with the private key stored securely, and can create a target DID (Decentralized Identity Provider) for entity B. For example, device 205 can create the target DID locally and then send the target DID and its public key to the blockchain system 204 for storage. Alternatively, device 205 can request a Decentralized Identity Service (DIS) system to create the target DID.

[0035] DIS is a blockchain-based identity management solution that provides functions such as digital identity creation, verification, and management, thereby achieving standardized management and protection of entity data, ensuring the authenticity and efficiency of information flow, and solving challenges such as cross-institutional identity authentication and data collaboration. The DIS system can be connected to the blockchain system 204. When device 205 requests the DIS system to create a target DID, it can send a DID creation request to the DIS system, including the institution information of institution B (such as qualifications, certificates, etc.) and the institution's public key. Subsequently, in response to the creation request, the DIS system, after verifying the institution information, creates the target DID and its corresponding DIDdoc for institution B. The DIS system can create the target DID based on the institution's public key in the creation request, for example, by calculating the public key using a hash function; or, the DIS system can create the target DID based on other information of institution B in the creation request (which may or may not include the public key). Next, the DIS system can send the target DID and its corresponding DIDdoc to the blockchain system 204 for storage, and return the target DID to device 205. The DIDdoc includes the public key of organization B. Furthermore, the DIDdoc also includes information such as the download address for a verifiable proof of organization B's identity.

[0036] In step S303, device 205 sends a request to device 203 of resource owner C to authorize resource reference for the target DID. The request includes the target DID and the resource identifier of the target digital resource.

[0037] In step S305, in response to the request to authorize resource reference for the target DID, after the identity verification of organization B is passed, device 203 writes the resource identifier associated with the target DID to the target digital resource into the local authorized DID information.

[0038] It should be noted that when verifying the identity of organization B, device 203 can perform local verification or request verification from blockchain system 204.

[0039] When verifying the identity of entity B locally, device 203 can, for example, obtain the DIDdoc corresponding to the target DID from blockchain system 204, generate a string, and send the string to device 205. Device 205 then signs the string using entity B's private key and returns it to device 203. Next, device 203 can verify the signature returned by device 205 using the public key in the DIDdoc. If correct, the identity of entity B is confirmed.

[0040] When requesting verification from blockchain system 204, the request may also include a signature based on the private key of the target DID. Device 203 can send a verification request to blockchain system 204, including the target DID and the signature. Then, blockchain system 204 can verify the signature's correctness based on the public key stored in the DIDdoc corresponding to the target DID. If correct, it returns a verification success result to device 203. Next, device 203 can confirm the identity of organization B based on the received verification success result.

[0041] In one implementation, after writing the resource identifier associated with the target digital resource into the local authorized DID information, device 203 can proactively synchronize the authorized DID information corresponding to the target digital resource to the blockchain system 204. For example, the blockchain system 204 may include a preset device (such as an oracle), and device 203 can proactively synchronize the authorized DID information corresponding to the target digital resource to this preset device. A blockchain oracle is a middleware connecting the blockchain to the real world; it can bring real-world data and events into the blockchain system for use by smart contracts and decentralized applications (DApps). Alternatively, the blockchain system 204 may deploy a smart contract SC for authorization verification, and device 203 can proactively synchronize the authorized DID information corresponding to the target digital resource to the contract state of the smart contract SC.

[0042] Figure 3 The corresponding embodiment provides a solution in which organization B can apply to resource user C for resource reference authorization related to the target digital resource for the target DID, thereby making the target DID an authorized DID of the target digital resource. In this way, by configuring the target DID and the target digital resource in the page data of page P as described above, page P can reference the target digital resource.

[0043] When configuring the target DID and target digital resource in the page data of page P, in one implementation, organization B can sign the target DID using the private key of the target DID (the private key of organization B described above). Then, organization B can provide the target DID and the signature based on the private key to the website, app, or mini-program where page P resides. The developer can then add a display tag T and a resource identifier, target DID, and signature based on the private key corresponding to the display tag T to the page data of page P. The display tag T is used to represent the digital resource referenced in blockchain system 204. Further, the display tag T can specifically represent a digital resource of a target category in blockchain system 204, where the target category is the resource category to which the target digital resource belongs. A single resource category can be, for example, any one of images, videos, and 3D models.

[0044] Taking page P as a webpage on a website and the target digital resource as the target image as an example, the display tag T could be, for example, a webpage P on a website and a target digital resource as the target image.

[0045] <blockchainimg> ， <blockchainimg>This can be used to characterize digital resources in the image category of the blockchain system 204. Additionally, the image identifier of the target image, the target DID, and a signature based on the private key using the target DID can be written into it.

[0046] <blockchainimg>In the example, taking the target image identifier as "myblockchain:cat.img", the target DID as "***", and the signature as "###", the display tag T written after the image identifier, target DID, and signature can be, for example,...

[0047] <blockChainImg src=‘myblockchain:cat.img’,did=‘***’,signature=‘###’ / >Wherein, src is the parameter name used to represent the resource identifier, did is the parameter name used to represent the decentralized identity identifier, and signature is the parameter name used to represent the signature. It should be noted that... <blockchainimg>The information written therein is merely an example, showing the correspondence between the label content of the label T itself and its resource identifier, target DID, and signature of the private key based on the target DID of the target digital resource. It can be designed according to actual needs, such as according to the encoding specifications of the programming language used by page P, etc., and is not specifically limited here.

[0048] After adding the display tag T and the resource identifier, target DID, and signature based on the private key of the target digital resource corresponding to the display tag T to the page data of page P, the developer can save the page data with this information added to the device 202 of organization B. This allows device 202 to return the page data with this information added after receiving a request to retrieve page P.

[0049] In practice, user A can act as a resource browser, accessing pages of websites, apps, or mini-programs supported by organization B's device 202 from user device 201. For example, when device 202 is a server for a website owned by organization B, user A can access the website's webpages through a browser on user device 201, allowing user device 201 to retrieve the webpage data from device 202 via the browser. When device 202 is a server for an app owned by organization B, the app can be installed on user device 201, and user A can access the app's pages within the app, allowing user device 201 to retrieve the app's page data from device 202 via the app. When device 202 is a server for a mini-program owned by organization B, an app that can call the mini-program can be installed on user device 201, and user A can access pages within the mini-program called by the app, allowing user device 201 to retrieve the page data from device 202 via the mini-program. It is understandable that user device 201 can obtain page data of the page that user A wants to access from device 202 based on the page access operation related to device 202 performed by user A.

[0050] When user A wants to access page P as described above, they can perform a page access operation for page P on user device 201, thereby entering the page P... Figure 4 The digital resource display process is shown below. Among them, Figure 4 This is a flowchart of the digital resource display method in the embodiments of this specification.

[0051] like Figure 4 As shown, in step S401, user equipment 201 sends a request to device 202 of organization B to obtain page P.

[0052] In this process, user equipment 201 may send a request to device 202 to retrieve page P in response to a page access operation performed by user A. This request may include, but is not limited to, the page identifier of page P.

[0053] In step S403, device 202 returns page data of page P to user device 201. The page data includes display tag T, resource identifier of target digital resource corresponding to display tag T, target DID of organization B, and signature of private key based on target DID.

[0054] The preceding text described how developers can add a display tag T and a resource identifier, target DID, and a signature based on the private key of the target digital resource corresponding to the display tag T to the page data of page P, and then save the page data with this information added to device 202. Based on this, in one implementation, device 202 can obtain the page data of page P stored locally and return the page data to user device 201.

[0055] In another implementation, when the digital resource referenced by the display tag T changes frequently, to avoid developers frequently modifying page data and reduce their workload, developers can add the display tag T to the page data of page P, save the page data with the added display tag T to device 202, and set configuration information related to page P in device 202. This configuration information includes resource authorization information corresponding to the display tag T, which includes the resource identifier of the target digital resource, the target DID, and a signature of the private key based on the target DID. Thus, when the digital resource referenced by the display tag T changes, developers only need to update this configuration information without modifying the page data of page P. Based on this, after receiving a request to retrieve page P, device 202 can retrieve the page data of page P stored locally, then read the resource authorization information corresponding to the display tag T from the configuration information based on the display tag T in the page data, add the resource authorization information corresponding to the display tag T to the page data, and then return the page data with the added resource authorization information to user device 201.

[0056] It should be understood that various feasible implementation methods can be adopted so that the page data of page P includes the display label T and the resource identifier of the target digital resource corresponding to the display label T, the target DID of organization B, and the signature of the private key based on the target DID. The embodiments in this specification do not specifically limit this.

[0057] In step S405, in response to the display tag T included in the page data of page P, user equipment 201 sends a transaction Tx1 to blockchain system 204 for acquiring target digital resources. Transaction Tx1 includes the resource identifier of the target digital resources, the target DID, and a signature of the private key based on the target DID.

[0058] Since the display tag T is used to represent the digital resources referenced in the blockchain system 204, such as specifically to represent the digital resources of the target category (the resource category to which the target digital resource belongs) in the blockchain system 204, the device 201 can know that it wants to obtain digital resources from the blockchain system 204 based on the display tag T included in the page data of page P, and thus send transaction Tx1 to the blockchain system 204.

[0059] In step S407, the blockchain system 204 verifies the signature of the private key based on the target DID by executing transaction Tx1, and in response to the signature being verified, obtains the authorized DID information corresponding to the target digital resource, and determines whether the target DID is associated with the resource identifier of the target digital resource contained in the authorized DID information.

[0060] Specifically, nodes in blockchain system 204 can verify the signature of the private key based on the target DID by executing transaction Tx1. For example, the node can obtain the DIDdoc corresponding to the target DID stored in blockchain system 204 and use the public key in the DIDdoc to verify whether the signature is correct. After the signature verification is successful, the node can obtain the authorized DID information corresponding to the target digital resource and determine whether the target DID is associated with the resource identifier of the target digital resource contained in the authorized DID information.

[0061] When obtaining the authorized DID information corresponding to the target digital resource, the node can adopt various feasible acquisition methods.

[0062] As an example, the blockchain system 204 may deploy a smart contract SC for authorization verification as described above, and transaction Tx1 invokes the smart contract SC. In such a case, in one implementation, a node in the blockchain system 204 can connect to a preset device as described above according to the smart contract SC, and receive authorized DID information corresponding to the target digital resource from the preset device. This authorized DID information may be actively synchronized to the preset device by the resource user C's device 203, or it may be obtained by the preset device from device 203 in response to the node's request for the authorized DID information. In another implementation, the authorized DID information may be stored in the contract state of the smart contract SC, and the node in the blockchain system 204 can obtain the authorized DID information from the contract state.

[0063] In step S409, in response to the determination result being yes, the blockchain system 204 acquires the target digital resource stored in the blockchain system 204.

[0064] Specifically, a node in the blockchain system 204 can obtain the target digital resource stored in the blockchain system 204 in response to determining that the resource identifier associated with the target DID is included in the authorized DID information corresponding to the target digital resource.

[0065] In step S411, the blockchain system 204 returns the target digital resource to the user equipment 201.

[0066] In step S413, user equipment 201 displays the target digital resource on page P.

[0067] Specifically, during the rendering of page P, user equipment 201 can display the target digital resource on page P.

[0068] In one implementation, in order to further enhance user A's confidence in the target digital resources displayed on page P, sub-steps S4131 and S4133 may be executed in step S413.

[0069] In sub-step S4131, user equipment 201 adds identification information containing trusted identifiers to the target digital resource.

[0070] The identification information may also include information about the resource owner C, such as the name and / or address of the resource owner C. For example, when the target digital resource is an image, this identification information can be added to the target location on the image. The target location can be any location that does not affect browsing the image content. For example, the target location can be any of the top left, top right, bottom left, and bottom right corners.

[0071] In sub-step S4133, user equipment 201 displays the target digital resource with added tagging information on page P.

[0072] It should be noted that after seeing the tagging information added to the target digital resource, user A can determine that the target digital resource is a trusted authorized resource. When this tagging information includes information about the resource owner C, user A can also determine the owner information of the target digital resource based on this tagging information. Therefore, by adding tagging information containing trusted identifiers to the target digital resource and displaying the target digital resource with the added tagging information on page P, user A's trust in the target digital resource displayed on page P can be further enhanced.

[0073] exist Figure 4 In the corresponding embodiment, user device 201 of user A can respond to the display tag T included in the page data of page P by sending a transaction Tx1 to the blockchain system 204 to obtain a target digital resource. The display tag T corresponds to the resource identifier of the target digital resource, the target DID of the organization B to which page P belongs, and a signature based on the private key of the target DID. Transaction Tx1 includes the resource identifier, the target DID, and the signature. Afterwards, user device 201 can receive the target digital resource returned by the blockchain system 204, which is sent by the blockchain system 204 after determining that the target DID is the authorized DID of the target digital resource. Then, user device 201 can display the target digital resource on page P. Thus, by using the display tag in the page data of the displayed page to reference the authorized digital resource of the organization to which the displayed page belongs in the blockchain system, the user device can obtain the authorized resource of the organization from the blockchain system, achieving a trusted display of the digital resource. This is beneficial for protecting the owner of the digital resource (such as the copyright holder) and improving the user's trust in the digital resource being viewed.

[0074] Based on the foregoing description, the solutions provided in the embodiments of this specification define a new process for obtaining and displaying trusted authorized resources on the client side. For example, when opening a webpage in the future, through extended... <blockchainimg>The tags clearly show which images are copyrighted and from which publishers, giving users greater trust in the information displayed on the page.

[0075] The technical innovations of the solutions provided in the embodiments of this specification may include:

[0076] The current client-side display components have been extended. For example, in addition to traditional web page HTML specifications, a series of tags related to referencing blockchain resources have been added, such as tags for referencing images. <blockchainimg>In addition, by combining the current DID mechanism, a technical solution was designed that can import relevant copyrighted resources through simple tag configuration and reliably display them to end users;

[0077] In addition to web applications, this mechanism can also be applied to various graphical display environments, such as native mobile applications, mini-programs under super apps, and 3D rendering environments. It supports all resources that can be displayed (such as images, videos, 3D models, etc.), providing users with a better and more reliable experience.

[0078] Figure 5 This is a schematic diagram of the digital resource display device described in the embodiments of this specification. This device can be applied to user equipment to perform functions such as... Figure 4 The steps are performed by user equipment 201. The device includes: a sending unit 501, configured to send a transaction for acquiring a target digital resource to a blockchain system in response to a display tag included in the page data of the display page, the display tag corresponding to a resource identifier of the target digital resource, a target DID of the organization to which the display page belongs, and a signature based on a private key of the target DID, the transaction including the resource identifier, the target DID, and the signature; a receiving unit 502, configured to receive the target digital resource returned by the blockchain system, which is sent by the blockchain system after determining that the target DID is the authorized DID of the target digital resource; and a display unit 503, configured to display the target digital resource in the display page.

[0079] Figure 6 This is a schematic diagram of the structure of a node in the blockchain system described in the embodiments of this specification. This node can perform actions such as... Figure 4 The steps are executed by the blockchain system 204. The node includes: a receiving unit 601, configured to receive a transaction sent by a user device for acquiring a target digital resource. This transaction is sent by the user device in response to a display tag included in the page data of a displayed page. The display tag corresponds to a resource identifier of the target digital resource, a target DID of the organization to which the displayed page belongs, and a signature based on the target DID's private key. The transaction includes the resource identifier, the target DID, and the signature; an execution unit 602, configured to verify the signature by executing the transaction, and in response to the signature verification, obtain authorized DID information corresponding to the target digital resource, and determine whether the target DID is associated with the resource identifier contained in the authorized DID information; an acquisition unit 603, configured to acquire the target digital resource stored in the blockchain system in response to a yes-to-be-determined result; and a sending unit 604, configured to return the target digital resource to the user device.

[0080] This specification also provides a computer-readable storage medium having a computer program stored thereon, wherein when the computer program is executed in a computer, it causes the computer to perform actions such as... Figure 3 , Figure 4 The method shown.

[0081] This specification also provides a computing device, including a memory and a processor, wherein the memory stores executable code, and when the processor executes the executable code, it implements, as shown in the embodiment. Figure 3 , Figure 4 The method shown.

[0082] This specification also provides a computer program product, wherein when the computer program product is executed in a computer, it causes the computer to perform the following: Figure 3 , Figure 4 The method shown.

[0083] In the 1990s, improvements to a technology could be clearly distinguished as either hardware improvements (e.g., improvements to the circuit structure of diodes, transistors, switches, etc.) or software improvements (improvements to the methodology). However, with technological advancements, many methodological improvements today can be considered direct improvements to the hardware circuit structure. Designers almost always obtain the corresponding hardware circuit structure by programming the improved methodology into the hardware circuit. Therefore, it cannot be said that a methodological improvement cannot be implemented using hardware physical modules. For example, a Programmable Logic Device (PLD) (such as a Field Programmable Gate Array (FPGA)) is such an integrated circuit whose logic function is determined by the user programming the device. Designers can program and "integrate" a digital system onto a PLD themselves, without needing chip manufacturers to design and manufacture dedicated integrated circuit chips. Furthermore, nowadays, instead of manually manufacturing integrated circuit chips, this programming is mostly implemented using "logic compiler" software. Similar to the software compiler used in program development, the original code before compilation must be written in a specific programming language, called a Hardware Description Language (HDL). There are many HDLs, such as ABEL (Advanced Boolean Expression Language), AHDL (Altera Hardware Description Language), Confluence, CUPL (Cornell University Programming Language), HDCal, JHDL (Java Hardware Description Language), Lava, Lola, MyHDL, PALASM, and RHDL (Ruby Hardware Description Language). Currently, the most commonly used are VHDL (Very-High-Speed ​​Integrated Circuit Hardware Description Language) and Verilog. Those skilled in the art should also understand that by simply performing some logic programming on the method flow using one of these hardware description languages ​​and programming it into an integrated circuit, the hardware circuit implementing the logical method flow can be easily obtained.

[0084] The controller can be implemented in any suitable manner. For example, it can take the form of a microprocessor or processor and a computer-readable medium storing computer-readable program code (e.g., software or firmware) executable by the (micro)processor, logic gates, switches, application-specific integrated circuits (ASICs), programmable logic controllers, and embedded microcontrollers. Examples of controllers include, but are not limited to, the following microcontrollers: ARC 625D, Atmel AT91SAM, Microchip PIC18F26K20, and Silicon Labs C8051F320. A memory controller can also be implemented as part of the control logic of the memory. Those skilled in the art will also recognize that, in addition to implementing the controller in purely computer-readable program code form, the same functionality can be achieved by logically programming the method steps to make the controller take the form of logic gates, switches, application-specific integrated circuits, programmable logic controllers, and embedded microcontrollers. Therefore, such a controller can be considered a hardware component, and the means included therein for implementing various functions can also be considered as structures within the hardware component. Alternatively, the means for implementing various functions can be considered as both software modules implementing the method and structures within the hardware component.

[0085] The systems, devices, modules, or units described in the above embodiments can be implemented by computer chips or physical entities, or by products with certain functions. A typical implementation device is a server system. Of course, this application does not exclude the possibility that, with the future development of computer technology, the computer implementing the functions of the above embodiments can be, for example, a personal computer, a laptop computer, an in-vehicle human-machine interaction device, a cellular phone, a camera phone, a smartphone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or any combination of these devices.

[0086] While one or more embodiments of this specification provide the steps of operation for the methods described in the embodiments or flowcharts, more or fewer steps may be included based on conventional or non-inventive means. The order of steps listed in the embodiments is merely one possible order of execution among many steps and does not represent the only possible order. In actual device or end product execution, the methods shown in the embodiments or drawings may be executed sequentially or in parallel (e.g., in a parallel processor or multi-threaded processing environment, or even a distributed data processing environment). The terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, product, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, product, or apparatus. Without further limitations, the presence of other identical or equivalent elements in a process, method, product, or apparatus that includes said elements is not excluded. For example, the use of terms such as "first," "second," etc., is to denote names and does not indicate any particular order.

[0087] For ease of description, the above devices are described in terms of function, divided into various modules. Of course, when implementing one or more of these specifications, the functions of each module can be implemented in one or more software and / or hardware components, or a module that performs the same function can be implemented by a combination of multiple sub-modules or sub-units. The device embodiments described above are merely illustrative. For example, the division of units is only a logical functional division; in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces, indirect coupling or communication connection between devices or units, and may be electrical, mechanical, or other forms.

[0088] This invention is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart... Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0089] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0090] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0091] In a typical configuration, a computing device includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.

[0092] Memory may include non-persistent storage in computer-readable media, such as random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash RAM. Memory is an example of computer-readable media.

[0093] Computer-readable media include both permanent and non-permanent, removable and non-removable media that can store information using any method or technology. Information can be computer-readable instructions, data structures, modules of programs, or other data. Examples of computer storage media include, but are not limited to, phase-change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, CD-ROM, digital versatile optical disc (DVD) or other optical storage, magnetic tape, magnetic disk storage, graphene storage or other magnetic storage devices, or any other non-transferable medium that can be used to store information accessible by a computing device. As defined herein, computer-readable media does not include transient computer-readable media, such as modulated data signals and carrier waves.

[0094] Those skilled in the art will understand that one or more embodiments of this specification can be provided as a method, system, or computer program product. Therefore, one or more embodiments of this specification may take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, one or more embodiments of this specification may take the form of a computer program product implemented on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0095] One or more embodiments of this specification can be described in the general context of computer-executable instructions, such as program modules, that are executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc., that perform a particular task or implement a particular abstract data type. One or more embodiments of this specification can also be practiced in distributed computing environments where tasks are performed by remote processing devices connected via a communication network. In distributed computing environments, program modules can reside in local and remote computer storage media, including storage devices.

[0096] The various embodiments in this specification are described in a progressive manner. Similar or identical parts between embodiments can be referred to mutually. Each embodiment focuses on describing the differences from other embodiments. In particular, system embodiments are basically similar to method embodiments, so the description is relatively simple; relevant parts can be referred to the descriptions in the method embodiments. In the description of this specification, the terms "one embodiment," "some embodiments," "example," "specific example," or "some examples," etc., refer to specific features, structures, materials, or characteristics described in connection with that embodiment or example, which are included in at least one embodiment or example of this specification. In this specification, the illustrative expressions of the above terms do not necessarily refer to the same embodiment or example. Furthermore, the specific features, structures, materials, or characteristics described can be combined in any suitable manner in one or more embodiments or examples. Moreover, without contradiction, those skilled in the art can combine and integrate the different embodiments or examples described in this specification and the features of different embodiments or examples.

[0097] The above description is merely an embodiment of one or more embodiments of this specification and is not intended to limit the scope of these embodiments. Various modifications and variations can be made to these embodiments by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this specification should be included within the scope of the claims.< / blockchainimg> < / blockchainimg> < / blockchainimg> < / blockchainimg> < / blockchainimg> < / blockchainimg>

Claims

1. A method for displaying digital resources, executed by a user device, the method comprising: Receive the display page from the target organization's server; In response to the display tag included in the page data of the display page, a transaction for acquiring the target digital resource is sent to the blockchain system. The display tag corresponds to the resource identifier of the target digital resource, the target decentralized identity identifier (DID) of the target institution to which the display page belongs, and a signature based on the private key of the target DID. The transaction includes the resource identifier, the target DID, and the signature. The blockchain system receives the target digital resource returned by the blockchain system, which is sent by the blockchain system after determining that the target DID is the authorized DID of the target digital resource, wherein the authorized DID is generated by the resource owner in response to the resource reference authorization initiated by the institution for the target DID; The target digital resource is displayed on the display page.

2. The method according to claim 1, wherein, Displaying the target digital resource on the display page includes: Add identification information containing a trusted identifier to the target digital resource; The target digital resource after the identification information has been added is displayed on the display page.

3. The method according to claim 2, wherein, The target digital resource is the target image; Adding identification information containing a trusted identifier to the target digital resource includes: Add the identification information to the target location on the target image.

4. The method according to claim 2, wherein, The identification information also includes information about the owner of the target digital resource.

5. The method according to claim 1, wherein, The blockchain system has smart contracts deployed for authorization verification, and the transaction invokes the smart contracts.

6. The method according to claim 1, wherein, The target digital resource is a copyrighted resource.

7. The method according to any one of claims 1-6, wherein, The display label is used to characterize digital resources referencing a target category in the blockchain system, where the target category is the resource category to which the target digital resource belongs.

8. A method for displaying digital resources, executed by a node in a blockchain system, the method comprising: The user equipment receives a transaction for acquiring a target digital resource. The transaction is sent by the user equipment in response to a display tag included in the page data of the display page. The display tag corresponds to the resource identifier of the target digital resource, the target decentralized identity identifier (DID) of the organization to which the display page belongs, and a signature based on the private key of the target DID. The transaction includes the resource identifier, the target DID, and the signature. By executing the transaction, the signature is verified, and in response to the signature being verified, the authorized DID information corresponding to the target digital resource is obtained, and it is determined whether the target DID is associated with the resource identifier contained in the authorized DID information; In response to a yes determination, the target digital resource stored in the blockchain system is acquired; The target digital resource is returned to the user equipment.

9. The method according to claim 8, wherein, The blockchain system is equipped with smart contracts for authorization verification, and the transaction invokes the smart contracts. The step of obtaining the authorized DID information corresponding to the target digital resource includes: Connect to a preset device according to the smart contract, and receive the authorized DID information from the preset device.

10. A digital resource display device, applied to a user equipment, the device comprising: The receiving unit is configured to receive the display page from the target organization's server; The sending unit is configured to send a transaction to the blockchain system in response to a display tag included in the page data of the display page, for acquiring a target digital resource. The display tag corresponds to the resource identifier of the target digital resource, the target decentralized identity identifier (DID) of the target institution to which the display page belongs, and a signature based on the private key of the target DID. The transaction includes the resource identifier, the target DID, and the signature. The receiving unit is further configured to receive the target digital resource returned by the blockchain system, which is sent by the blockchain system after determining that the target DID is the authorized DID of the target digital resource, wherein the authorized DID is generated by the resource owner in response to the resource reference authorization initiated by the institution for the target DID; The display unit is configured to display the target digital resource on the display page.

11. A node in a blockchain system, comprising: A receiving unit is configured to receive a transaction sent by a user equipment for acquiring a target digital resource. The transaction is sent by the user equipment in response to a display tag included in the page data of a display page. The display page is received by the user equipment from a server of a target structure. The display tag corresponds to a resource identifier of the target digital resource, a target decentralized identity identifier (DID) of the target organization to which the display page belongs, and a signature based on the private key of the target DID. The transaction includes the resource identifier, the target DID, and the signature. An execution unit is configured to verify the signature by executing the transaction, and in response to the signature being verified, obtain authorized DID information corresponding to the target digital resource, and determine whether the target DID is associated with the resource identifier contained in the authorized DID information, wherein the authorized DID is generated by the resource owner in response to the resource reference authorization initiated by the institution for the target DID; The acquisition unit is configured to acquire the target digital resource stored in the blockchain system in response to a determination result of yes; The sending unit is configured to return the target digital resource to the user equipment.

12. A computer-readable storage medium having a computer program stored thereon, which, when executed in a computer, causes the computer to perform the method of any one of claims 1-9.

13. A computing device comprising a memory and a processor, wherein the memory stores executable code, and the processor, when executing the executable code, implements the method of any one of claims 1-9.

Images