Blockchain-based browser component invocation method, apparatus, and storage medium

Abstract

The application discloses a browser component calling method and device based on a block chain, and a storage medium. Browser function components are stored in a block warehouse. When a browser component calling request sent by a client is received, a component list in the component calling request is used to traverse the block warehouse. Component data corresponding to the component list is obtained from a corresponding block node of the block warehouse. A corresponding block is created for the client, and a corresponding block node is generated. The component data is stored in the block node corresponding to the block. The storage and calling of the browser function components are realized based on the block chain. The browser can realize traceless browsing, the local storage pressure is reduced, and the application scenario of browser component nesting is particularly suitable.

Description

Technical Field

[0001] This invention relates to the field of browsers, and more particularly to a method, apparatus, and storage medium for invoking browser components based on blockchain. Background Technology

[0002] When browsing data in a traditional browser, the data is stored locally in multiple forms, such as cache, temporary files, and cookies. Browser-provided components are also added and stored locally as OCX or DLLs. This leaves traces of browser usage and also puts pressure on local storage. Summary of the Invention

[0003] The technical problem to be solved by the present invention is to provide a method, device and storage medium for calling browser components based on blockchain, which can realize incognito browsing and reduce local storage pressure.

[0004] To solve the above-mentioned technical problems, the present invention adopts the following technical solution:

[0005] A method for invoking a browser component based on blockchain, comprising the following steps:

[0006] Receive a browser component invocation request sent by the client, the component invocation request including a component list;

[0007] Traverse the block repository according to the component list, and obtain the component data corresponding to the component list from the corresponding block node in the block repository;

[0008] Create a corresponding block for the client and generate a corresponding block node, and store the component data in the block node corresponding to the block.

[0009] Furthermore, the component data corresponding to different browser components are stored in different block nodes in the block corresponding to the client.

[0010] Furthermore, after receiving the browser component invocation request sent by the client, the following steps are also included:

[0011] Determine whether the component data corresponding to the component list is stored in the block corresponding to the client. If yes, directly call the component data in the block corresponding to the client. If not, execute the step of traversing the block repository according to the component list.

[0012] Furthermore, it also includes the following steps:

[0013] Configure node members for each node in the block repository;

[0014] Receive component functions developed through the component SDK and store the component functions in the node members of the block node corresponding to the component.

[0015] Furthermore, different component functions corresponding to the same component are stored in different node members of the block node corresponding to the component.

[0016] Furthermore, it also includes the following steps:

[0017] Receive an operation request for the blockchain, and perform a corresponding operation on the blockchain according to the operation request. The operation includes adding, deleting, or modifying component data.

[0018] Furthermore, when the operation is to add component data, performing the corresponding operation on the blockchain according to the operation request includes:

[0019] Add a new block node for the block corresponding to the client, and store the component data in the newly added block node;

[0020] When the operation is to delete component data, performing the corresponding operation on the blockchain according to the operation request includes:

[0021] Determine the target block node corresponding to the component data;

[0022] Delete the component data corresponding to the target block node and release the target block node;

[0023] When the operation is to modify component data, performing the corresponding operation on the blockchain according to the operation request includes:

[0024] Determine the target block node corresponding to the component data;

[0025] Modify the component data corresponding to the target block node according to the operation request.

[0026] Furthermore, it also includes the following steps:

[0027] The operation data generated during the client's invocation of the browser component is stored in the block node corresponding to the browser component.

[0028] To solve the above-mentioned technical problems, another technical solution adopted by the present invention is as follows:

[0029] A blockchain-based browser component invocation device includes a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, it implements the steps of the aforementioned blockchain-based browser component invocation method.

[0030] To solve the above-mentioned technical problems, another technical solution adopted by the present invention is as follows:

[0031] A computer-readable storage medium storing computer program instructions thereon, which, when executed by a processor, implement the steps of the aforementioned blockchain-based browser component invocation method.

[0032] The beneficial effects of this invention are as follows: Browser functional components are stored in a blockchain repository. When a browser component invocation request is received from a client, the blockchain repository is traversed based on the component list in the request. Component data corresponding to the component list is obtained from the corresponding block node in the blockchain repository. A corresponding block is created for the client, and a corresponding block node is generated. The component data is stored in the block node corresponding to the block. Based on blockchain, the storage and invocation of browser functional components are realized, enabling incognito browsing and reducing local storage pressure. This is particularly suitable for application scenarios involving nested browser components. Attached Figure Description

[0033] Figure 1 This is a flowchart illustrating the steps of a blockchain-based browser component invocation method according to an embodiment of the present invention.

[0034] Figure 2 This is a schematic diagram of the structure of a blockchain-based browser component invocation device according to an embodiment of the present invention;

[0035] Figure 3 This is a diagram illustrating the specific implementation process of a blockchain-based browser component invocation method according to an embodiment of the present invention. Detailed Implementation

[0036] To explain in detail the technical content, objectives, and effects of the present invention, the following description is provided in conjunction with the embodiments and accompanying drawings.

[0037] The blockchain-based browser component invocation method, apparatus, and storage medium described above are applicable to application scenarios such as incognito browsers, embedded browsers, and Web3.0 blockchain browsers. The following detailed implementation methods illustrate these applications:

[0038] In one alternative implementation, such as Figure 1 As shown, a method for invoking a blockchain-based browser component includes the following steps:

[0039] S1. Receive a browser component invocation request sent by the client, wherein the component invocation request includes a component list;

[0040] like Figure 3 As shown, users can submit a list of browser components that need to be called, i.e., a list of required functions;

[0041] S2. Traverse the block repository according to the component list, and obtain the component data corresponding to the component list from the corresponding block node in the block repository;

[0042] That is, after receiving the user's list of requirements, the block node attributes can be traversed in the block repository to determine the block node corresponding to the list of components that meet the user's requirements, and the corresponding component data can be obtained from that block node.

[0043] S3. Create a corresponding block for the client and generate a corresponding block node, and store the component data in the block node corresponding to the block;

[0044] After obtaining the corresponding component data, a unique and exclusive block can be created for each user to store user data, and block nodes can be generated on this block to store the obtained component data.

[0045] Among them, the component data corresponding to different browser components are stored in different block nodes in the block corresponding to the client, and different browser components are stored based on block nodes, which facilitates the allocation and management of browser components;

[0046] For example, if a user requests two functional components: bookmarks and history, these two components belong to the list of user-requested functional components. Since this is the first request, the browser will retrieve them from the repository block. Therefore, the browser will eventually generate two functional components: bookmarks and history. The content of this operation will be stored in the user's unique block and a corresponding functional component block node will be generated. The content of the block node is the data of the corresponding functional component.

[0047] In another alternative implementation, the following steps are also included:

[0048] The operation data generated during the client's invocation of the browser component is stored in the block node corresponding to the browser component.

[0049] In this embodiment, the operation data generated during the user's call to the browser component, such as the allocation result, is also stored, so that the user can directly call it through the data stored in the block when calling it a second time, which is convenient and fast.

[0050] In another alternative implementation, the step of receiving a browser component invocation request from the client is further included:

[0051] Determine whether the component data corresponding to the component list is stored in the block corresponding to the client. If yes, directly call the component data in the block corresponding to the client. If not, execute the step of traversing the block repository according to the component list.

[0052] In this embodiment, when a browser component call request is received from a client, it is first determined whether the corresponding component data has been stored in the corresponding block of the client. If so, the component is called directly without having to traverse the block repository, which improves the efficiency of browser component calls.

[0053] In another alternative implementation, the following steps are also included:

[0054] Configure node members for each node in the block repository;

[0055] Receive component functions developed through the component SDK, and store the component functions in the node members of the block node corresponding to the component;

[0056] In this embodiment, different component functions corresponding to the same component are stored in different node members of the block node corresponding to the component, including function development members. Function development members can develop various component functions with the help of the component SDK and store them in the corresponding node members. That is, the component and function have the same function, but they are developed by different people, and the layout and user experience of the function will be different. This embodiment can realize the diversity of component functions, realize the dynamic loading and running of components, and realize the diversity and richness of browser component functions.

[0057] In another alternative implementation, the following steps are also included:

[0058] Receive an operation request for the blockchain, and perform a corresponding operation on the blockchain according to the operation request. The operation includes adding, deleting, or modifying component data.

[0059] Wherein, when the operation is to add component data, the step of performing the corresponding operation on the blockchain according to the operation request includes:

[0060] Add a new block node for the block corresponding to the client, and store the component data in the newly added block node;

[0061] When the operation is to delete component data, performing the corresponding operation on the blockchain according to the operation request includes:

[0062] Determine the target block node corresponding to the component data;

[0063] Delete the component data corresponding to the target block node and release the target block node;

[0064] When the operation is to modify component data, performing the corresponding operation on the blockchain according to the operation request includes:

[0065] Determine the target block node corresponding to the component data;

[0066] Modify the component data corresponding to the target block node according to the operation request;

[0067] In this embodiment, the user can conveniently and quickly perform operations on the corresponding block through the operation request, which greatly improves the user's operational flexibility.

[0068] In another alternative implementation, such as Figure 2 As shown, a blockchain-based browser component invocation device includes a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, it implements the steps of the blockchain-based browser component invocation method described in any of the above embodiments.

[0069] In another alternative embodiment, a computer-readable storage medium stores computer program instructions that, when executed by a processor, implement the steps of a blockchain-based browser component invocation method as described in any of the above embodiments.

[0070] In summary, the present invention provides a blockchain-based browser component invocation method, apparatus, and storage medium. Browser functional components are stored in a block repository. When a browser component invocation request is received from a client, the block repository is traversed based on the component list in the request. Component data corresponding to the component list is obtained from the corresponding block node in the block repository. A corresponding block and corresponding block node are created for the client, and the component data is stored in the block node corresponding to the block. Node members are also configured to enable open development of browser components and achieve component sharing. When the client makes a secondary invocation, the component data stored in the corresponding block on the client can be directly invoked. Based on blockchain, the storage and invocation of browser functional components are flexibly and efficiently realized, enabling incognito browsing and reducing local storage pressure. It is particularly suitable for application scenarios involving nested browser components.

[0071] The above description is merely an embodiment of the present invention and does not limit the patent scope of the present invention. Any equivalent modifications made based on the content of the present invention specification and drawings, or direct or indirect applications in related technical fields, are similarly included within the patent protection scope of the present invention.

Claims

1. A blockchain-based method for invoking a browser component, characterized in that, The method comprises the steps of: receiving a browser component calling request sent by a client, the component calling request comprising a component list; after receiving the browser component calling request sent by the client, the method further comprises the steps of: determining whether the component data corresponding to the component list is stored in the block corresponding to the client, if yes, directly calling the component data in the block corresponding to the client, if not, performing the step of traversing the block repository according to the component list; traversing the block repository according to the component list, and obtaining the component data corresponding to the component list from the block node corresponding to the block repository; creating a corresponding block for the client, generating a corresponding block node, and storing the component data into the block node corresponding to the block; setting a node member for each node in the block repository; receiving a component function developed through a component SDK, and storing the component function into the node member of the block node corresponding to the component; storing different component functions corresponding to the same component into different node members of the block node corresponding to the component. 2.The method of claim 1, wherein, storing the component data corresponding to different browser components into different block nodes in the block corresponding to the client.

3. The method of claim 1 or 2, wherein, The method further comprises the steps of: receiving an operation request for the block chain, and performing a corresponding operation on the block chain according to the operation request, the operation comprising adding, deleting or modifying component data.

4. The method of claim 3, wherein, When the operation is to add component data, the step of performing a corresponding operation on the block chain according to the operation request comprises: adding a block node to the block corresponding to the client, and storing the component data into the added block node; When the operation is to delete component data, the step of performing a corresponding operation on the block chain according to the operation request comprises: determining a target block node corresponding to the component data; deleting the component data corresponding to the target block node, and releasing the target block node; When the operation is to modify component data, the step of performing a corresponding operation on the block chain according to the operation request comprises: determining a target block node corresponding to the component data; modifying the component data corresponding to the target block node according to the operation request.

5. The method of claim 1 or 2, wherein, The method further comprises the step of: storing operation data generated in the process of calling the browser component by the client into the block node corresponding to the browser component. 6.A blockchain-based browser component calling apparatus, comprising a memory, a processor, and a computer program stored in the memory and capable of running on the processor, and characterized in that, The processor executes the computer program to implement the steps of the browser component calling method based on the block chain according to any one of claims 1 to 5.

7. A computer-readable storage medium having stored thereon computer program instructions, wherein, The computer program instructions are executed by the processor to implement the steps of the browser component calling method based on the block chain according to any one of claims 1 to 5.

Images