Resource management application processing method and device, storage medium and electronic equipment

Abstract

The invention provides a resource management application processing method and device, a storage medium and electronic equipment. The method comprises the following steps: displaying a resource sharing voucher creation interface in response to a resource sharing voucher creation trigger received in a resource management application; in response to a sharing parameter setting completion operation received in the resource sharing voucher creation interface, displaying a voucher creation permission verification interface; when an authority verification operation performed based on the voucher creation authority verification interface indicates that verification is passed, displaying a voucher display interface; and in response to a voucher distribution operation received by the voucher display interface, distributing the generated resource sharing voucher. According to the method, the resource use convenience can be improved.

Description

Technical Field

[0001] The present disclosure relates to the field of computer technology, and in particular to a processing method, device, storage medium, and electronic device for resource management applications. Background Art

[0002] With the development of Internet technology, payment methods have undergone a transformation from cash payment to cashless payment, which has greatly changed people's consumption habits. Consumers can consume merchants' goods anytime and anywhere.

[0003] As a form of cashless payment, physical card payment does not require the use of the Internet. Consumers can complete payment instantly through a card swiping device, providing stable and reliable payment protection.

[0004] However, physical card payment is limited by the physical card carrier and can only be used by a single user, making resource use inconvenient. Summary of the Invention

[0005] The embodiments of the present disclosure provide a method, device, storage medium, and electronic device for processing resource management applications, which can improve the convenience of resource use.

[0006] A first aspect of the present disclosure provides a method for processing a resource management application, comprising:

[0007] In response to a resource sharing credential creation trigger received in the resource management application, displaying a resource sharing credential creation interface;

[0008] In response to a shared parameter setting completion operation received in the resource sharing credential creation interface, displaying a credential creation permission verification interface;

[0009] When the permission verification operation based on the credential creation permission verification interface indicates that the verification is passed, the credential display interface is displayed;

[0010] In response to the credential distribution operation received by the credential display interface, the generated resource sharing credential is distributed.

[0011] A second aspect of the present disclosure provides a processing device for a resource management application, comprising:

[0012] a first display unit, configured to display a resource sharing credential creation interface in response to a resource sharing credential creation trigger received in the resource management application;

[0013] a second display unit, configured to display a credential creation permission verification interface in response to a sharing parameter setting completion operation received in the resource sharing credential creation interface;

[0014] A third display unit is configured to display a credential display interface when the permission verification operation based on the credential creation permission verification interface indicates that the verification is passed;

[0015] The distribution unit is configured to distribute the generated resource sharing certificate in response to a certificate distribution operation received on the certificate display interface.

[0016] Optionally, in some embodiments, the first display unit includes:

[0017] A first display subunit is configured to display an application function interface of a resource management application, wherein the application function interface includes a resource sharing credential creation control;

[0018] The second display sub-unit is configured to display a resource sharing credential creation interface in response to a triggering operation on the resource sharing credential creation control.

[0019] Optionally, in some embodiments, the second display subunit includes:

[0020] A first display module is configured to display a credential creation setting label in response to a triggering operation on the resource sharing credential creation control, wherein the credential creation setting label includes an account setting control;

[0021] A second display module is configured to display a plurality of candidate accounts in response to a triggering operation on the account setting control;

[0022] The third display module is configured to display a resource sharing credential creation interface in response to a selection operation on a target account from among the plurality of candidate accounts.

[0023] Optionally, in some embodiments, the third display unit includes:

[0024] The third display subunit is used to display the password verification area for the savings entity object on the voucher creation authority verification interface;

[0025] a fourth display subunit, configured to display a password verification interface in response to a password input completion operation received in the password verification area;

[0026] The fifth display subunit is used to display the credential display interface when the password verification received on the password verification interface passes.

[0027] Optionally, in some embodiments, the third display unit includes:

[0028] The sixth display sub-unit is used to display a verification prompt for the hardware wallet on the credential creation permission verification interface;

[0029] The seventh display sub-unit is used to display a credential display interface when the verification of the target hardware wallet is completed based on the verification prompt.

[0030] Optionally, in some embodiments, the second display unit includes:

[0031] An eighth display subunit, configured to display a shared resource quantity input area and a validity period input area in the resource sharing voucher creation interface;

[0032] A first receiving subunit is configured to receive a shared resource amount based on a resource amount input area, and receive a shared validity period based on a validity period input area;

[0033] The ninth display sub-unit is configured to, in response to a creation trigger operation on the resource sharing credential creation interface, display a credential creation permission verification interface based on the shared resource amount and the sharing validity period.

[0034] Optionally, in some embodiments, the first receiving subunit includes:

[0035] A fourth display module is used to display a resource quantity input text box in the resource quantity input area;

[0036] The first receiving module is configured to receive a resource sharing amount based on a resource amount input text box.

[0037] Optionally, in some embodiments, the first receiving subunit includes:

[0038] A fifth display module, configured to display a resource quantity edit control in the resource quantity input area;

[0039] a sixth display module, configured to display a candidate resource amount list in response to a triggering operation on the resource amount editing control, the candidate resource amount list including a plurality of candidate resource amounts;

[0040] The second receiving module is configured to receive, in response to a selection operation on a target resource amount in the candidate resource amount list, a shared resource amount corresponding to the target resource amount based on a resource amount input area.

[0041] Optionally, in some embodiments, the second display unit further includes:

[0042] a tenth display subunit, configured to display a usage scenario input area when the amount of shared resources is greater than a preset resource threshold;

[0043] a second receiving subunit, configured to receive a resource sharing scenario of a shared resource amount based on a usage scenario input area;

[0044] The ninth display subunit includes:

[0045] The seventh display module is configured to, in response to a creation trigger operation on the resource sharing credential creation interface, display a credential creation permission verification interface based on the amount of shared resources, sharing time, and resource sharing scenario.

[0046] Optionally, in some embodiments, the dispatching unit includes:

[0047] An eleventh display subunit is used to display a print function control on the voucher display interface;

[0048] The printing subunit is used to print the generated resource sharing certificate in response to the triggering operation of the printing function control.

[0049] Optionally, in some embodiments, the dispatching unit includes:

[0050] A twelfth display subunit is used to display the sharing function control on the credential display interface;

[0051] a thirteenth display subunit, configured to display a candidate sharing object list in response to a triggering operation on the sharing function control;

[0052] The sending subunit is configured to send the generated resource sharing credential to the target sharing object in response to a selection operation on the target sharing object in the candidate sharing object list.

[0053] Optionally, in some embodiments, the third display unit includes:

[0054] The transceiver subunit is used to send the resource sharing parameters received in the resource sharing credential creation interface to the hardware wallet when the credential creation permission verification interface triggers the verification process, and receive the verification result generated by the hardware wallet based on the resource sharing parameters;

[0055] The fourteenth display subunit is used to display a credential display interface when the verification result indicates that the verification is passed.

[0056] A third aspect of the present disclosure provides a hardware wallet verification device, comprising:

[0057] a fourth display unit, configured to display a resource prompt interface, wherein the resource prompt interface includes resource sharing parameters;

[0058] The generating unit is configured to generate a digital signature based on a preset private key and the resource sharing parameters when receiving a confirmation instruction for the resource sharing parameters in the resource prompt interface, and generate a verification result based on the digital signature.

[0059] Optionally, in some embodiments, the third display unit includes:

[0060] A generating subunit, configured to generate a resource sharing credential based on the digital signature and resource sharing parameters in the verification result;

[0061] The display subunit is used to display the credential display interface, which includes resource sharing credentials.

[0062] A fourth aspect of the present disclosure provides a device for processing resource sharing credentials, including:

[0063] A first acquiring unit is configured to acquire a resource transfer request, where the resource transfer request includes a resource transfer amount;

[0064] The second acquisition unit is used to obtain the digital signature, resource sharing parameters and wallet identifier corresponding to the hardware wallet in the resource sharing certificate;

[0065] A determination unit, configured to determine a public key based on a wallet identifier;

[0066] A verification unit, configured to verify the digital signature based on the public key and resource sharing parameters;

[0067] The resource transfer unit is used to transfer resources to the resource account corresponding to the hardware wallet according to the resource transfer amount when the verification is passed.

[0068] Optionally, in some embodiments, the resource transfer unit includes:

[0069] A determination subunit, configured to determine a remaining amount of resource sharing corresponding to the resource sharing voucher;

[0070] The resource transfer subunit is used to transfer resources to the resource account corresponding to the hardware wallet based on the resource transfer amount and the resource sharing remaining amount, and update the resource sharing remaining amount.

[0071] A fifth aspect of the present disclosure provides a storage medium storing a computer program. When the computer program is executed by a processor, the processing method for the resource management application as described in the first aspect is implemented.

[0072] In a sixth aspect, the present disclosure provides an electronic device, comprising a memory and a processor, wherein the memory stores a computer program, and the processor implements the processing method of the resource management application as described in the first aspect when executing the computer program.

[0073] A seventh aspect of the present disclosure provides a computer program product, which includes a computer program. The computer program is read and executed by a processor of an electronic device, so that the electronic device executes the processing method of the resource management application as described in the first aspect.

[0074] Thus, the present disclosure provides a processing method for a resource management application, which includes displaying a resource sharing credential creation interface in response to a resource sharing credential creation trigger received in the resource management application; displaying a credential creation permission verification interface in response to a sharing parameter setting completion operation received in the resource sharing credential creation interface; displaying a credential display interface when the permission verification operation performed based on the credential creation permission verification interface indicates that the verification is passed; and distributing the generated resource sharing credential in response to a credential distribution operation received on the credential display interface.

[0075] This method receives sharing parameter settings based on a resource sharing credential creation interface using a resource management application. After the resource sharing permission verification is passed, the generated sharing credential can be distributed based on the credential distribution operation, and resources can be used directly through the sharing credential, thereby improving the convenience of resource use.

[0076] Other features and advantages of the present disclosure will be described in the following description, and in part will become apparent from the description, or will be understood by practicing the present disclosure. The purposes and other advantages of the present disclosure can be realized and obtained by the structures particularly pointed out in the description, claims and drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0077] The accompanying drawings are used to provide a further understanding of the technical solution of the present disclosure and constitute a part of the specification. Together with the embodiments of the present disclosure, they are used to explain the technical solution of the present disclosure and do not constitute a limitation to the technical solution of the present disclosure.

[0078] Figure 1 A system architecture diagram for the resource management application processing method in the embodiment of the present disclosure;

[0079] Figure 2 A flowchart of a method for processing a resource management application in an embodiment of the present disclosure is provided;

[0080] Figure 3 A schematic diagram of a resource sharing credential creation interface in an embodiment of the present disclosure;

[0081] Figure 4 This is a schematic diagram of an application function interface in an embodiment of the present disclosure;

[0082] Figure 5 A schematic diagram of selecting a candidate account in an embodiment of the present disclosure;

[0083] Figure 6 A schematic diagram of a credential creation permission verification in an embodiment of the present disclosure;

[0084] Figure 7 A schematic diagram of shared parameter input in an embodiment of the present disclosure;

[0085] Figure 8 A schematic diagram of a resource quantity input text box in an embodiment of the present disclosure;

[0086] Figure 9 This is a schematic diagram of a candidate resource quantity list in an embodiment of the present disclosure;

[0087] Figure 10 This is a schematic diagram of an input area for a usage scenario in an embodiment of the present disclosure;

[0088] Figure 11 This is a schematic diagram of a credential display interface in an embodiment of the present disclosure;

[0089] Figure 12 A schematic diagram of a credential creation permission verification interface in an embodiment of the present disclosure;

[0090] Figure 13 A schematic diagram of a verification prompt in an embodiment of the present disclosure;

[0091] Figure 14 A schematic diagram of printing a resource sharing certificate in an embodiment of the present disclosure;

[0092] Figure 15 A schematic diagram of sharing a resource sharing credential in an embodiment of the present disclosure;

[0093] Figure 16 is another flowchart of a method for processing a resource management application in an embodiment of the present disclosure;

[0094] Figure 17 A schematic diagram of a shared credential creation process in an embodiment of the present disclosure;

[0095] Figure 18 A schematic diagram of a shared credential in an embodiment of the present disclosure;

[0096] Figure 19 A schematic diagram of a payment process based on shared credentials in an embodiment of the present disclosure;

[0097] Figure 20 This is a schematic diagram of a transaction voucher printing template in an embodiment of the present disclosure;

[0098] Figure 21 A schematic diagram of a server executing resource transfer in an embodiment of the present disclosure;

[0099] Figure 22 A schematic diagram of a resource sharing architecture in an embodiment of the present disclosure;

[0100] Figure 23 A schematic diagram of the structure of a processing device for a resource management application in an embodiment of the present disclosure;

[0101] Figure 24 A terminal structure diagram of each method of one embodiment of the present disclosure;

[0102] Figure 25 This is a server structure diagram of each method in one embodiment of the present disclosure. DETAILED DESCRIPTION

[0103] In order to make the purpose, technical solutions and advantages of the present disclosure more clearly understood, the present disclosure is further described in detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present disclosure and are not intended to limit the present disclosure.

[0104] The terms "first," "second," "third," "fourth," and the like (if any) in the specification and claims of the present disclosure and in the accompanying drawings are used to distinguish similar objects and are not necessarily used to describe a particular order or sequential sequence. It should be understood that the terms used in this manner are interchangeable where appropriate, so that the embodiments of the present disclosure described herein can, for example, be implemented in orders other than those illustrated or described herein. In addition, the terms "including" and "corresponding to," and any variations thereof, are intended to cover non-exclusive inclusions, e.g., a process, method, system, product, or apparatus comprising a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.

[0105] The word “exemplary” is used exclusively herein to mean “serving as an example, example, or illustration.” Any embodiment described herein as “exemplary” is not necessarily to be construed as preferred or advantageous over other embodiments.

[0106] In the embodiments of the present disclosure, the term "module" or "unit" refers to a computer program or a part of a computer program that has a predetermined function and works together with other related parts to achieve a predetermined goal, and can be implemented in whole or in part by using software, hardware (such as processing circuits or memories) or a combination thereof. Similarly, a processor (or multiple processors or memories) can be used to implement one or more modules or units. In addition, each module or unit can be part of an overall module or unit that includes the function of the module or unit.

[0107] In addition, numerous specific details are provided in the following detailed description to better illustrate the present disclosure. Those skilled in the art will appreciate that the present disclosure can be practiced without certain specific details. In some instances, methods, means, components, and circuits well known to those skilled in the art are not described in detail in order to highlight the main points of the present disclosure.

[0108] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as those understood by those skilled in the art to which the present disclosure pertains. The terms used herein are for the purpose of describing the embodiments of the present disclosure only and are not intended to limit the present disclosure.

[0109] With the development of internet technology, payment methods have evolved from cash to cashless payments, significantly changing consumer habits and enabling consumers to purchase goods from merchants anytime, anywhere. Physical card payments, as a form of cashless payment, eliminate the need for an internet connection. By swiping a card, consumers can instantly complete payments, providing stable and reliable payment security. Mobile payments can be made by displaying a QR code or using near-field communication (NFC), but executing mobile payments over the internet can pose security risks. Bank cards, bus passes, and other similar cards can use integrated circuit (IC) chips or NFC technology to store payment credentials and account information, but these cards must be carried physically and used through point-of-sale (POS) machines or card readers. Hardware wallets require a physical connection to a computer or phone to authorize transactions, but they can only be used by one person, making them difficult to share with multiple people.

[0110] Based on the above technical problems, the embodiments of the present disclosure provide a method for processing resource management applications to solve the above technical problems.

[0111] System architecture and scenario description of the application of the embodiments of the present disclosure

[0112] Figure 1 This is a system architecture diagram for a resource management application processing method according to an embodiment of the present disclosure, which includes a terminal 140, the Internet 130, a gateway 120, a server 110, and the like.

[0113] Terminal 140 includes various devices with display screens, such as desktop computers, laptops, PDAs (personal digital assistants), mobile phones, in-vehicle terminals, home theater terminals, dedicated terminals, intelligent voice interaction devices, smart appliances, or aircraft. Furthermore, it can be a single device or a collection of multiple devices. Terminal 140 can communicate with Internet 130 via wired or wireless means to exchange data.

[0114] Server 110 is a computer system that provides certain services to terminal 140. Compared to ordinary terminal 140, server 110 has higher requirements in terms of stability, security, and performance. Server 110 can be a high-performance computer in a network platform, a cluster of multiple high-performance computers, a portion of a high-performance computer (such as a virtual machine), or a combination of portions of multiple high-performance computers (such as virtual machines).

[0115] Gateway 120, also known as a gateway or protocol converter, implements network interconnection at the transport layer and is a computer system or device that performs a conversion function. It acts as a translator between two systems using different communication protocols, data formats, languages, or even completely different architectures. Gateways can also provide filtering and security functions. Messages sent from terminal 140 to server 110 are sent through gateway 120 to the corresponding server 110. Messages sent from server 110 to terminal 140 are also sent through gateway 120 to the corresponding terminal 140.

[0116] The processing method for resource management applications provided by the embodiments of the present disclosure may be implemented solely in the terminal 140 , solely in the server 110 , or partially in the terminal 140 and partially in the server 110 .

[0117] When the processing method of the resource management application provided by the embodiment of the present disclosure is implemented separately in the terminal 140, the terminal 140 displays the resource sharing credential creation interface in response to the resource sharing credential creation trigger received in the resource management application; the terminal 140 displays the credential creation permission verification interface in response to the sharing parameter setting completion operation received in the resource sharing credential creation interface; when the permission verification operation based on the credential creation permission verification interface indicates that the verification is passed, the terminal 140 displays the credential display interface; the terminal 140 distributes the generated resource sharing credential in response to the credential distribution operation received in the credential display interface.

[0118] When the processing method of the resource management application provided by the embodiment of the present disclosure is implemented separately in the server 110, the server 110 displays the resource sharing credential creation interface in response to the resource sharing credential creation trigger received in the resource management application; the server 110 displays the credential creation permission verification interface in response to the sharing parameter setting completion operation received in the resource sharing credential creation interface; when the permission verification operation based on the credential creation permission verification interface indicates that the verification is passed, the server 110 displays the credential display interface; the server 110 distributes the generated resource sharing credential in response to the credential distribution operation received in the credential display interface.

[0119] When the processing method of the resource management application provided by the embodiment of the present disclosure is partially implemented in the terminal 140 and partially implemented in the server 110, the terminal 140 displays the resource sharing credential creation interface in response to the resource sharing credential creation trigger received in the resource management application; the terminal 140 displays the credential creation permission verification interface in response to the sharing parameter setting completion operation received in the resource sharing credential creation interface, and sends the received resource sharing parameters to the server 110; the server 110 verifies the resource sharing parameters and sends the verification result to the terminal 140; when the permission verification operation based on the credential creation permission verification interface indicates that the verification is passed, the terminal 140 displays the credential display interface; the terminal 140 distributes the generated resource sharing credential in response to the credential distribution operation received in the credential display interface.

[0120] The electronic devices for processing resource management applications provided by the embodiments of the present disclosure may be various types of terminal devices or servers, wherein the server may be an independent physical server, or a server cluster or distributed system composed of multiple physical servers, or a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, CDN, and big data and artificial intelligence platforms; the terminal may be a smart phone, tablet computer, laptop computer, desktop computer, smart speaker, smart watch, etc., but is not limited thereto. The terminal device and the server may be directly or indirectly connected via wired or wireless communication, which is not limited by the embodiments of the present disclosure.

[0121] Taking servers as an example, it can be a server cluster deployed in the cloud, opening artificial intelligence cloud services (AIaaS, AI as a Service) to objects. The AIaaS platform can split several common AI services and provide independent or packaged services in the cloud. This service model is similar to an AI theme mall. All objects can access one or more artificial intelligence services provided by the AIaaS platform through the application programming interface.

[0122] The embodiments of the present disclosure can be applied in a variety of scenarios. For example, in offline consumption, consumers can use physical cards for offline payments. However, physical card payments are based on a physical card carrier and can only be carried and used by one person. That is, the resources in the resource account corresponding to the physical card can only be used by the consumer carrying the physical card. The processing method of the resource management application using the embodiments of the present disclosure can receive sharing parameter settings. After the resource sharing permission is verified, a shared credential is distributed based on the credential distribution operation. Resources can be used directly through the shared credential, improving the convenience of resource use.

[0123] The above examples do not limit the scope of protection of this case.

[0124] General description of the embodiments of the present disclosure

[0125] The following will illustrate the processing method of the resource management application provided by the embodiment of the present disclosure with reference to the accompanying drawings. The execution subject of the following processing method of the resource management application takes the terminal device as an example, and can be specifically implemented by the terminal device by running the various computer programs mentioned above; of course, based on the understanding of the following, it is not difficult to see that the processing method of the resource management application provided by the embodiment of the present disclosure can also be implemented by the terminal device and the server in collaboration.

[0126] See also Figure 2 ,like Figure 2 FIG2 is a flow chart of a method for processing a resource management application provided by an embodiment of the present disclosure, the method comprising:

[0127] Step 201: In response to a resource sharing credential creation trigger received in a resource management application, a resource sharing credential creation interface is displayed.

[0128] Resource management applications can refer to software applications that allocate resources in any scenario where resources need to be managed and allocated.

[0129] The resource sharing credential creation interface can be a display interface within a resource management application that provides a channel for creating and configuring resource sharing credentials. A resource sharing credential can be a payment credential used to verify identity and authorize access to shared resources, allowing resources to be securely shared with other users. It is understood that other users can access the corresponding resource account by presenting the resource sharing credential, which is then scanned at the point of sale. Upon receiving an instruction to create a resource sharing credential, the resource management application can trigger the display of the resource sharing credential creation interface.

[0130] In one example, the schematic diagram of the resource sharing credential creation interface can be referred to Figure 3 As shown, the display interface 300 of the resource management application includes a function bar, which can distinguish different displayed interfaces. That is, different displayed interfaces can be distinguished in the function bar. Figure 3 In the example, the home page interface 310 may be the initial interface for receiving a trigger for creating a resource sharing credential. Figure 3 In the function bar, a currently displayed interface is indicated by a thick frame. For example, a resource sharing credential creation interface 320 is currently displayed. The user can perform a resource sharing credential creation operation based on the resource sharing credential creation interface 320 .

[0131] In one embodiment, in response to a resource sharing credential creation trigger received in a resource management application, displaying a resource sharing credential creation interface includes:

[0132] Display the application function interface of the resource management application, which includes a resource sharing credential creation control;

[0133] In response to a triggering operation on the resource sharing credential creation control, a resource sharing credential creation interface is displayed.

[0134] In this embodiment, the application function interface can be the main interface of the resource management application, providing a centralized operating platform for users to manage various resources and perform related operations. This interface can include multiple functional modules and controls, through which users can access and use the core functions of the application.

[0135] The resource sharing credential creation control can be an interface element in an application interface that triggers the resource sharing credential creation process. The resource sharing credential creation control can be a button or link. When clicked, the application interface immediately jumps to the resource sharing credential creation interface to begin creating a new resource sharing credential.

[0136] In an example, see Figure 4 The application function interface diagram shown in FIG. Figure 3 The home page interface 310 shown is as follows: Figure 4 As shown in the function bar, the currently displayed interface is indicated by a thick frame, which is the home page interface 310. That is, a resource sharing credential creation control 311 is provided in the home page interface 310. When the resource sharing credential creation control 311 is triggered by the usage object, the display interface 300 jumps to the resource sharing credential creation interface 320. At this time, the resource sharing credential creation interface 320 in the function bar is indicated by a thick frame.

[0137] In one embodiment, in response to a triggering operation on a resource sharing credential creation control, a resource sharing credential creation interface is displayed, including:

[0138] In response to a triggering operation on a resource sharing credential creation control, displaying a credential creation settings tab, the credential creation settings tab including an account settings control;

[0139] In response to a triggering operation on an account setting control, displaying a plurality of candidate accounts;

[0140] In response to a selection operation of a target account from the plurality of candidate accounts, a resource sharing credential creation interface is displayed.

[0141] In this implementation, the Credential Creation Settings tab can be an interface element within the resource management application, providing additional configuration options during the resource-sharing credential creation process. This tab can be considered a centralized configuration platform, allowing users to trigger the resource-sharing credential creation control when creating a resource-sharing credential for detailed configuration and management. Through this tab, users can flexibly set and manage various resource-sharing credential parameters, ensuring that the credential creation process meets their needs.

[0142] The account settings control is an interface element used during the resource sharing credential creation process to allow users to select or configure the account information used to create the resource sharing credential. It provides an interactive interface where users can select or enter account information, thereby specifying the account used to create the resource sharing credential. In other words, the resources shared with the resource sharing credential originate from the resource account specified in the account settings control.

[0143] Candidate accounts are multiple available accounts that can serve as the shared resource source for a resource sharing credential during the resource sharing credential creation process. These accounts can be pre-configured or entered on the fly. Users can trigger the account settings control and select a target account from the displayed candidate accounts. This target account will then provide shared resources for the resource sharing credential created in the resource sharing credential creation interface. Users can directly select a target account from the displayed candidate accounts, improving the user experience.

[0144] In one example, the candidate account selection diagram can refer to Figure 5 As shown, in Figure 4 On the basis of, when the user triggers the resource sharing credential creation control 311, the home page interface 310 displays the credential creation setting label 312. Among them, the credential creation setting label 312 includes an account setting control 3121. When the user triggers the account setting control 3121, the home page interface 310 displays multiple candidate accounts for the user to select, such as Figure 5 Based on the selection operation of any candidate account among the candidate accounts 1-3, the display interface 300 jumps to the resource sharing credential creation interface 320.

[0145] Step 202: In response to the shared parameter setting completion operation received in the resource sharing credential creation interface, a credential creation permission verification interface is displayed.

[0146] The credential creation permission verification interface can be an interface for verifying whether the user has permission to create resource sharing credentials, ensuring that only authorized users can create and manage resource sharing credentials. The credential creation permission verification interface can display prompts such as "Permission Verification" or "Permission Verification", or use clear text and icons (such as a check mark or cross) to inform the user of the current permission status.

[0147] The sharing parameter setting completion operation can be an operation in which the user enters the sharing parameters in the resource sharing credential creation interface and then confirms the operation. That is, the sharable resources are specified to the resource management application, and then the credential creation permission verification process is entered. At this time, the resource management application displays the credential creation permission verification interface.

[0148] In an example, see Figure 6 The diagram of the certificate creation permission verification shown in Figure 3 On the basis of this, after the object enters the resource sharing parameters in the resource sharing credential creation interface 320, it triggers the jump to display the credential creation permission verification interface 330. At this time, the credential creation permission verification interface 330 in the function bar is represented by a thick line frame, and the verification prompt information can be displayed in the credential creation permission verification interface 330.

[0149] In one embodiment, in response to a sharing parameter setting completion operation received in a resource sharing credential creation interface, a credential creation permission verification interface is displayed, including:

[0150] In the resource sharing voucher creation interface, the shared resource quantity input area and the validity period input area are displayed;

[0151] Based on the resource quantity input area, receive the shared resource quantity; based on the validity period input area, receive the shared validity period;

[0152] In response to a creation trigger operation on the resource sharing voucher creation interface, a voucher creation permission verification interface is displayed based on the shared resource amount and the sharing validity period.

[0153] In this embodiment, the shared resource amount input area may refer to a specific interface portion of the resource sharing credential creation interface where a user enters the desired resource amount to be shared. This allows the user to enter the resource amount into the system. The shared resource amount input area herein may be an area where the user enters the shared resource amount, and accordingly, the terminal may receive the data entered by the user in the shared resource amount input area as the shared resource amount.

[0154] The expiration date input area may refer to an interface element within the resource sharing credential creation interface that allows a user to enter the expiration date of the resource sharing credential. This area may include a date selector or input box, through which the user can specify the start and end times of the resource sharing credential. The start and end times of the resource sharing credential may be directly indicated by the start and end times, or the user may enter a time range, with the start and end times determined by the time the resource sharing credential was generated combined with the time range.

[0155] When a user completes parameter settings and triggers a creation operation based on the resource sharing credential creation interface, the system receives these shared parameters and verifies their validity. The resource management application then jumps to the credential creation permission verification interface to verify the entered shared resource quantity and sharing validity period. By providing a dedicated input area, the system can better control the format and content of data entered by the user. For example, using a date picker ensures that the entered date format is correct, avoiding errors caused by inconsistent manually entered date formats and improving data accuracy and reliability.

[0156] In an example, see Figure 7 The shared parameter input diagram shown in Figure 6 Based on this, the user enters resource sharing parameters in the resource sharing credential creation interface 320. The resource sharing credential creation interface 320 includes a shared resource quantity input area 321 and an expiration date input area 322. The user can enter the desired resource quantity in the shared resource quantity input area 321 and the desired expiration date in the expiration date input area 322. After completing the input, the user can trigger the resource sharing credential creation process on the resource sharing credential creation interface 320, causing the display interface 300 to jump to the credential creation permission verification interface 330 to verify the input shared resource quantity and sharing expiration date.

[0157] In one embodiment, receiving the shared resource amount based on the resource amount input region includes:

[0158] Display the resource quantity input text box in the resource quantity input area;

[0159] The resource-based share amount is received in the Resource Quantity input text box.

[0160] In this embodiment, the resource quantity input text box can be an interface element in the resource quantity input area, used to allow the user to input the quantity of resources to be shared. This text box can be a number input box, in which the user can enter the specific resource quantity. Accordingly, after the user enters data in the resource quantity input text box, the resource management application can receive this input data as the resource sharing quantity. The text box can provide clear labels and input prompts, which can better control the format and content of the data entered by the user. For example, using a number input box can ensure that the user enters a valid number, avoiding errors caused by inconsistent input formats.

[0161] In one example, the diagram of the resource quantity input text box can be referred to Figure 8 As shown, a resource amount input text box 3211 is provided in the shared resource amount input area 321. The resource amount input text box 3211 can be configured with clear text, such as "shared resource amount", so that the user can understand the function of the input text box. Among them, the resource amount input text box 3211 can be limited to receiving only numerical data.

[0162] In one embodiment, receiving the shared resource amount based on the resource amount input region includes:

[0163] Display resource quantity edit controls in the resource quantity input area;

[0164] In response to a trigger operation on a resource amount editing control, displaying a candidate resource amount list, the candidate resource amount list including a plurality of candidate resource amounts;

[0165] In response to a selection operation on a target resource amount in the candidate resource amount list, a shared resource amount corresponding to the target resource amount is received based on the resource amount input area.

[0166] In this embodiment, the resource quantity editing control can be a functional control presented in the form of a graphical user interface (GUI) element in the resource quantity input area, such as a button, icon, or drop-down menu item. When the user triggers the resource quantity editing control through a mouse, touch, or other input device, the system responsively displays a list of candidate resource quantities. The list can be presented in the form of a pop-up window, a drop-down menu, or a sidebar, and contains multiple candidate resource quantities. The candidate resource quantities can be preset optional resource quantity sharing options. It is understandable that the candidate resource quantity list can also include editable options, which are not limited here. The user can select any candidate resource quantity from the candidate resource quantity list as the target resource quantity, and the selected target resource quantity can be regarded as the shared resource quantity to be shared.

[0167] In an example, see Figure 9As shown in the schematic diagram of the candidate resource quantity list, a resource quantity editing control 3212 is provided in the shared resource quantity input area 321. The resource quantity editing control 3212 can be a button or an icon, and the user can access the candidate resource quantities by clicking it. When the user clicks the resource quantity editing control 3212, the page can display a drop-down candidate resource quantity list 32121. This candidate resource quantity list 32121 provides multiple candidate resource quantities, and the user can select the target resource quantity from the multiple candidate resource quantities. The design based on the function menu allows the user to easily access the candidate resource quantities, improves the usability of the interactive interface, and makes document management more intuitive and efficient.

[0168] In one embodiment, in response to a creation trigger operation on a resource sharing credential creation interface, before displaying a credential creation permission verification interface based on the amount of shared resources and the sharing time, the method further includes:

[0169] When the amount of shared resources exceeds the preset resource threshold, the usage scenario input area is displayed;

[0170] A resource sharing scenario based on a usage scenario input area receiving a shared resource amount;

[0171] In response to a creation trigger operation on a resource sharing credential creation interface, a credential creation permission verification interface is displayed based on the amount of shared resources and the sharing time, including:

[0172] In response to a creation trigger operation on a resource sharing credential creation interface, a credential creation permission verification interface is displayed based on the amount of shared resources, the sharing time, and the resource sharing scenario.

[0173] In this embodiment, the preset resource threshold may refer to a critical value of a resource amount pre-set by the system. When the amount of shared resources input by the user in the resource sharing credential creation interface exceeds this preset threshold, the system may trigger an additional verification or input process to ensure the security and compliance of resource sharing. A usage scenario limitation process for the resource sharing may be triggered here. When the amount of shared resources is greater than the preset resource threshold, the resource management application may display a usage scenario input area. The user may limit the usage scenario of the resource sharing credential, that is, the resource sharing credential cannot be used for consumption outside of the limited usage scenario. The resource management application may use the data received in the usage scenario input area as a resource sharing scenario to avoid excessive use or abuse of resources. It is understandable that when creating a resource sharing credential, the permission verification process executed by the credential creation permission verification interface also needs to verify the resource sharing scenario input by the user.

[0174] In an example, see Figure 10 The schematic diagram of the usage scenario input area is shown in Figure 7On this basis, when the shared resource quantity input area 321 and the validity period input area 322 are inputted, the resource management application can also first identify whether the shared resource quantity inputted in the shared resource quantity input area 321 exceeds the preset resource threshold. When the input shared resource quantity exceeds the preset resource threshold, the resource sharing credential creation interface 320 displays the usage scenario input area 323 outside the shared resource quantity input area 321 and the validity period input area 322, so that the user can input the resource sharing scenario that limits the usage scenario of the resource sharing credential through the usage scenario input area 323.

[0175] Step 203: When the permission verification operation performed based on the credential creation permission verification interface indicates that the verification is passed, the credential display interface is displayed.

[0176] The credential display interface can be a page that jumps to the detailed information of the generated resource sharing credential after the sharing parameter setting passes the permission verification, and the user can view or use the resource sharing credential. It is understandable that the user can verify the sharing parameter setting based on the credential creation permission verification interface. After the verification passes, the resource management application can generate a resource sharing credential based on the set sharing parameters and display the resource sharing credential on the credential display interface. Among them, the credential creation permission verification interface can display the verification result when determining the verification result, or it can jump directly to the next page without displaying it.

[0177] In one example, the schematic diagram of the voucher display interface can be referred to Figure 11 As shown, in Figure 6 On the basis of this, the object is used to perform a permission verification operation on the credential creation permission verification interface 330. When the permission verification passes, the resource management application jumps to the credential display page 340. At this time, the credential display page 340 in the function bar is represented by a thick line frame, and the resource sharing credential 341 is displayed in the credential display page 340.

[0178] In one embodiment, when the permission verification operation performed based on the credential creation permission verification interface indicates that the verification is passed, the credential display interface is displayed, including:

[0179] The password verification area for the savings entity object is displayed on the voucher creation permission verification interface;

[0180] In response to a password input completion operation received in the password verification area, displaying a password verification interface;

[0181] When the password received on the password verification interface passes the verification, the credential display interface is displayed.

[0182] In this implementation, the savings entity object may be an entity structure representing savings resources, which may be mapped to a resource account. The entity structure may be used for consumption verification during the consumption process.

[0183] The password verification area can be an interface element of the credential creation permission verification interface, which is used to verify whether the resource sharing parameters entered by the object have the permission to save the entity object. It can also be understood as whether the entity object is authorized to share the resources corresponding to the resource sharing parameters.

[0184] The password verification interface can be an interface display for verifying the password corresponding to the savings entity object entered in the password verification area. It can display the verification process or directly display the verification results. The user can directly jump to the password verification interface after entering data in the password verification area, or the user can jump to the password verification interface through a confirmation instruction. If the password verification passes, the system can assume that the resources of the savings entity object have been authorized for sharing, and can then jump to the voucher display interface to display the detailed information of the generated resource sharing voucher. Through password verification, the system can ensure that only authorized resources can be shared, prevent resource abuse, and ensure the reasonable allocation and use of resources.

[0185] In an example, a schematic diagram of the credential creation permission verification interface can be referred to Figure 12 As shown, in Figure 11 On the basis of this, a password verification area 331 is provided in the voucher creation authority verification interface 330. The user can input the verification password of the savings entity object based on the password verification area 331. When the password input is completed, the voucher creation authority verification interface 330 jumps to the password verification interface 350. The password verification interface 350 can display the verification process or wait for verification, etc. If the verification passes, the password verification interface 350 jumps to the voucher display page 340.

[0186] In one embodiment, when the permission verification operation performed based on the credential creation permission verification interface indicates that the verification is passed, the credential display interface is displayed, including:

[0187] Display a hardware wallet verification prompt on the credential creation permission verification interface;

[0188] When the verification of the target hardware wallet is completed based on the verification prompt, the credential display interface is displayed.

[0189] In this implementation, a hardware wallet is a physical device used to store digital assets, offering greater security and privacy than traditional software wallets. Hardware wallets can have built-in encryption chips and security mechanisms to protect the holder's private keys from being leaked or stolen by malware.

[0190] A verification prompt can be a prompt within the credential creation permission verification interface that guides the user to complete hardware wallet verification. The connection between the hardware wallet and the resource management application can be pre-established or initiated based on the verification prompt. For example, the connection based on the verification prompt can be achieved via short-range wireless communication, such as near-field communication or Bluetooth. For example, the verification prompt can prompt the user to enable NFC or Bluetooth. Alternatively, the hardware wallet and the resource management application can be connected via a data cable. It is understood that the verification process with the hardware wallet is performed by the hardware wallet. Even if the resource management application determines the verification result based on verification information from the connected target hardware wallet, it will jump to the credential display interface when verification is successful.

[0191] In one example, the schematic diagram of the verification prompt can refer to Figure 13 As shown, in Figure 11 Based on the credential creation permission verification interface 330, the verification prompt is used to initiate verification to the hardware wallet, such as Figure 13 In the “Please connect to the hardware wallet”, the user connects the hardware wallet according to the relevant instructions and performs physical verification through the hardware wallet. When the resource management application determines that the verification is passed, the display interface jumps to the credential display page 340.

[0192] In one embodiment, when the permission verification operation performed based on the credential creation permission verification interface indicates that the verification is passed, the credential display interface is displayed, including:

[0193] When the credential creation permission verification interface triggers the verification process, the resource sharing parameters received in the resource sharing credential creation interface are sent to the hardware wallet, and the verification result generated by the hardware wallet based on the resource sharing parameters is received;

[0194] When the verification result indicates that the verification is passed, the certificate display interface is displayed.

[0195] In this implementation, resource sharing parameters can be various parameters input by the user, including resource sharing amount, validity period, resource sharing scenario, etc. The resource management application can send the obtained resource sharing parameters to the connected hardware wallet for verification and determine whether the verification is successful based on the verification result of the resource sharing parameters fed back by the hardware wallet. By confirming the resource sharing parameters on the hardware wallet, the security of resource sharing can be ensured.

[0196] In one embodiment, the verification process of the hardware wallet includes:

[0197] Display resource prompt interface, which includes resource sharing parameters;

[0198] When a confirmation instruction for the resource sharing parameters in the resource prompt interface is received, a digital signature is generated according to the preset private key and the resource sharing parameters, and a verification result is generated according to the digital signature.

[0199] In this embodiment, the resource prompt interface can be a prompt interface displayed on the display screen of the hardware wallet, which can prompt the holder of the hardware wallet of the content that currently needs to be verified. Here, it is the resource sharing parameters that need to be shared. The user can physically confirm through the physical confirmation button of the hardware wallet or the touch button of the display screen.

[0200] A digital signature is a special string generated by processing data using a cryptographic algorithm. Much like a handwritten signature in real life, it identifies the sender and ensures that data has not been tampered with during transmission. This digital signature is uniquely encrypted using a private key stored within the hardware wallet and not exportable. The hardware wallet can provide feedback to the resource management application as a verification result. This feedback indicates that the user has confirmed the resource sharing parameters and that the signature was generated by the hardware wallet, ensuring trust and enhancing security.

[0201] In one embodiment, displaying a credential display interface includes:

[0202] Generate a resource sharing certificate based on the digital signature and resource sharing parameters in the verification result;

[0203] The credential display interface is displayed, which includes resource sharing credentials.

[0204] In this implementation, the resource sharing credential can be a cryptographically-based digital document used to record and verify the resource owner's authorization to share a specific resource. Essentially, it combines the resource sharing parameters confirmed by the hardware wallet holder with a digital signature to create an unalterable, verifiable electronic credential, ensuring the legitimacy and security of the sharing activity.

[0205] In one embodiment, the resource sharing credential processing process includes:

[0206] Obtain a resource transfer request, where the resource transfer request includes a resource transfer amount;

[0207] Obtain the digital signature, resource sharing parameters, and wallet ID corresponding to the hardware wallet in the resource sharing certificate;

[0208] Determine the public key based on the wallet identifier;

[0209] Verify the digital signature based on the public key and resource sharing parameters;

[0210] When the verification is passed, resources are transferred to the resource account corresponding to the hardware wallet according to the resource transfer amount.

[0211] In this embodiment, a resource transfer request is an instruction initiated by a transaction subject to a server to transfer the ownership or usage rights of a specific resource. The resource transfer request may include a resource transfer amount, which indicates the amount of resources to be transferred from the resource account corresponding to the resource sharing voucher.

[0212] In addition to the digital signature and resource sharing parameters, the resource sharing credential may also include the wallet identifier corresponding to the hardware wallet that generated the digital signature. Based on the wallet identifier, the server can retrieve the corresponding public key in the database, blockchain node or distributed storage according to the preset mapping rules to verify the digital signature.

[0213] It is understood that the resource sharing credentials can be directly obtained by the server or indicated by a credential identifier carried in the resource transfer request. Signature verification can be performed by decrypting the digital signature using the public key and determining the signature verification result based on whether the decryption result is consistent with the resource sharing parameters. For example, the resource sharing parameters can be hashed and converted into a fixed-length hash value using a cryptographic hash algorithm. The digital signature is then decrypted using the public key. If the signature was generated using the corresponding private key, the decrypted hash value will be consistent with the original digest. The decrypted hash value is then compared with the hash value corresponding to the resource sharing parameters. If the two are completely consistent, it proves that the resource sharing parameters have not been tampered with during transmission and that the signature was indeed generated by the holder of the private key corresponding to the public key, and the verification process is declared successful. After the signature verification is successful, the server can transfer the resources corresponding to the resource transfer amount from the resource account corresponding to the hardware wallet. Through the coordinated verification of the public key and parameters, reliable authentication of the signer's identity and effective protection of data integrity are achieved.

[0214] In one embodiment, transferring resources to a resource account corresponding to a hardware wallet according to the resource transfer amount includes:

[0215] Determine the remaining amount of resource sharing corresponding to the resource sharing voucher;

[0216] Based on the resource transfer amount and the resource sharing remaining amount, the resource account corresponding to the hardware wallet is transferred, and the resource sharing remaining amount is updated.

[0217] In this embodiment, the resource sharing remaining amount may refer to the total available amount of transferable resources authorized by the resource owner through the voucher, after deducting the amount already transferred, reflecting the remaining available space in the voucher in real time. The server may store account usage information corresponding to the resource sharing voucher, such as resource usage and resource transfer time. When performing a transfer operation on the resource account corresponding to the hardware wallet, the resource transfer amount may be compared with the resource sharing remaining amount in the resource sharing voucher. The server may confirm that the current transfer amount does not exceed the valid remaining amount range, ensuring that the transfer request is within the authorized scope. Once verification is successful, the server may deduct the corresponding resource transfer amount from the hardware wallet's resource account and simultaneously adjust the resource sharing remaining amount to the difference between the original remaining amount and the current transfer amount, thereby completing the dual update of the account balance and the remaining amount in the voucher. By verifying the matching relationship between the transfer amount and the remaining amount, it is ensured that the resource transfer is executed within the preset permissions and that overuse is prevented by real-time updates of the remaining amount, thus forming a closed-loop control over hardware wallet resource management and ensuring the security and compliance of digital asset transfers.

[0218] Step 204: In response to the credential distribution operation received by the credential display interface, the generated resource sharing credential is distributed.

[0219] For resource sharing credentials displayed on the credential display interface, the user can distribute them to the designated shared object. This can be done by providing a credential distribution instruction to the resource management application through the credential distribution operation on the credential display interface. The resource management application can provide the resource sharing credentials to the designated shared object based on the distribution method selected by the user in the credential distribution instruction. After the distribution operation is completed, the resource management device can also provide feedback on the distribution result to the user, informing the user of the specific information of the success or failure of the distribution.

[0220] In one embodiment, in response to a credential distribution operation received on a credential display interface, distributing the generated resource sharing credential includes:

[0221] Display the print function control on the voucher display interface;

[0222] In response to a triggering operation on the print function control, the generated resource sharing voucher is printed.

[0223] In this embodiment, the print function control can be an interactive component for converting digital resource sharing certificates into paper documents. It can be presented in the form of an intuitive icon or text button, such as a "Print Certificate" button with a printer icon, placed in the page operation area or toolbar to facilitate quick positioning and operation of the object.

[0224] When using an object to trigger the print function control, the system can format and convert the voucher data, adapt the page content containing digital signatures, resource sharing parameters and other information to the standard printing format, and then drive the printer to output paper vouchers, completing the conversion from digital to physical. Among them, the resource management application can call the browser or system's print engine, pop up a print settings dialog box, and allow the object to select the printer, paper size, adjust the font size, page margins and layout structure and other parameters. The printed voucher can be carried without an electronic device, making it convenient for consumers to use relevant resources at any time in scenarios without network or device restrictions, thereby improving the convenience of resource use.

[0225] In one example, the resource sharing credential printing diagram can refer to Figure 14 As shown, in Figure 11 On the basis of the voucher display interface, the voucher display page 340 is provided with a print function control 342. When the user clicks the print function control 342, the printing process of the resource sharing voucher 341 is triggered.

[0226] In one embodiment, in response to a credential distribution operation received on a credential display interface, distributing the generated resource sharing credential includes:

[0227] Display sharing function controls on the credential display interface;

[0228] In response to a triggering operation on the sharing function control, displaying a candidate sharing object list;

[0229] In response to a selection operation on a target sharing object in the candidate sharing object list, the generated resource sharing credential is sent to the target sharing object.

[0230] In this implementation, the sharing function control can be an interactive component that distributes resource sharing credentials across entities, and can be presented in the form of a visual button or icon, such as a sharing icon with an outward arrow or a "shared credentials" text button, which is often placed in the toolbar at the top of the page or the operation area at the bottom, and is indicated by color highlighting or motion prompts.

[0231] The candidate sharing object list can be a collection of sharing objects that can receive the credential and is displayed on the credential display interface after the sharing function is triggered. This list can be presented in the form of a pop-up window, drop-down menu, or sidebar, and can include multiple candidate sharing objects. The user can select any candidate sharing object from the candidate sharing object list as the target sharing object, and the resource management application can then send the resource sharing credential to the target sharing object.

[0232] In one example, the resource sharing credential sharing diagram can refer to Figure 15 As shown, in Figure 11On the basis of this, the voucher display page 340 is provided with a sharing function control 343. When the user clicks the sharing function control 343, the voucher display page 340 can pop up a candidate sharing object list 3431. The candidate sharing object list 3431 shows multiple candidate sharing objects (1-3). The user can then select a candidate sharing object from them as the recipient of the resource sharing voucher.

[0233] The processing method of the resource management application provided by the embodiment of the present disclosure includes displaying a resource sharing credential creation interface in response to a resource sharing credential creation trigger received in the resource management application; displaying a credential creation permission verification interface in response to a sharing parameter setting completion operation received in the resource sharing credential creation interface; displaying a credential display interface when the permission verification operation performed based on the credential creation permission verification interface indicates that the verification is passed; and distributing the generated resource sharing credential in response to a credential distribution operation received on the credential display interface.

[0234] This method receives sharing parameter settings based on a resource sharing credential creation interface using a resource management application. After the resource sharing permission verification is passed, the generated sharing credential can be distributed based on the credential distribution operation, and resources can be used directly through the sharing credential, thereby improving the convenience of resource use.

[0235] The embodiments of the present disclosure are described in detail in conjunction with specific application scenarios.

[0236] like Figure 16 FIG. 1 is another flow chart of a method for processing resource management applications provided by the present disclosure. The method specifically includes the following steps:

[0237] Step 1601: The management device obtains resource sharing parameters corresponding to the hardware wallet.

[0238] The management device may be an application device that manages and allocates resources.

[0239] A hardware wallet can be a physical device that stores digital assets, or a physical device that can store assets, such as a bank card. These devices can store private keys in a chip using hardware isolation technology, preventing hackers or malware from accessing them in an online environment.

[0240] Resource sharing parameters include maximum resource volume, sharing time, application scenarios, and regional restrictions. The maximum resource volume can be the upper limit of resources that a hardware wallet can allocate to sharing scenarios; the sharing time can be the time period limit for resource sharing (such as temporary sharing, permanent sharing, or a specified time period); the application scenario can be the business scenario in which the resource can be used; and the regional restriction can be based on geographic location or network environment, limiting consumption to a specific area.

[0241] Step 1602: The management device generates a signature request object according to the resource sharing parameter and the wallet identifier corresponding to the hardware wallet, and sends the signature request object to the hardware wallet.

[0242] A wallet ID can be a set of codes or identifiers used to uniquely identify a hardware wallet, similar to the account number of a bank account, to ensure that the wallet is accurately identified and distinguished on the network. It can be a combination of letters, numbers or special symbols, and is unique and cannot be tampered with.

[0243] The signature request object can be structured data encapsulated by the management device based on resource sharing parameters and the hardware wallet's identity, used to trigger the hardware wallet's signature operation. Essentially, it combines transaction intent, permission restrictions, and device identity into standardized instructions and sends them to the hardware wallet, ensuring the legitimacy and security of the signing process.

[0244] Step 1603: The hardware wallet displays the resource sharing parameters in the signature request object on the parameter display interface.

[0245] The parameter display interface can be a visual window for the holder to physically interact with the hardware wallet. The resource sharing parameters in the signature request object can be displayed here. The user can directly verify whether the displayed resource limits are consistent with the resources they want to authorize sharing.

[0246] Step 1604: In response to the confirmation instruction for the resource sharing parameters on the parameter display interface, the hardware wallet encrypts the resource sharing parameters based on the private key, obtains a digital signature, and sends the digital signature to the management device.

[0247] The confirmation instruction may be generated by a physical confirmation operation of the user on the hardware wallet, and may be triggered by a physical button of the hardware wallet or a virtual button on the parameter display interface.

[0248] A digital signature is a cryptographically based electronic authentication technology that uses a private key to encrypt data to generate a unique identifier, used to verify data integrity, sender identity, and ensure non-repudiation. Here, the private key is used to encrypt resource sharing parameters into a digital signature, which is then fed back to the management device to complete the signing process.

[0249] Step 1605: The management device generates a shared credential based on the resource sharing parameter, the digital signature, the credential identifier, and the wallet identifier.

[0250] A shared credential can be structured data generated by a management device based on resource sharing parameters, a digital signature, a credential identifier, and a wallet identifier, used to prove resource sharing permissions. The credential identifier can be a unique identifier within a shared credential, used to accurately distinguish, trace, and verify different credentials within a digital system.

[0251] In an example, the shared credential creation process can refer to Figure 17 As shown, first, use the object login management application software and instruct the create credential function.

[0252] Second, use an object to physically connect the management application software to the hardware wallet, such as through NFC, Bluetooth or USB.

[0253] During the user authentication and hardware wallet connection phase, the user first provides authentication credentials to the management application software through biometrics or passwords. After system verification, a session token is generated. Subsequently, the user physically connects the hardware wallet to the mobile device, and the management application software sends a connection request containing a random challenge value.

[0254] After receiving the request, the hardware wallet generates a temporary public key (tempPublicKey) and session identifier (sessionId), and uses its internal private key to generate a signature (signedChallenge) for the challenge value and returns it to the management application software. This connection method based on a challenge-response mechanism ensures that only hardware wallets holding legitimate private keys can establish a connection, effectively preventing attacks from counterfeit devices.

[0255] After the management application verifies the signature, it performs an Elliptic Curve Diffie-Hellman Ephemeral (ECDHE) key exchange protocol with the hardware wallet, and both parties independently calculate the same shared secret (sharedSecret). This secret is processed using the HMAC-based Key Derivation Function (HKDF) to generate the session key (sessionKey) and initialization vector (IV). All communication data is then encrypted using the Advanced Encryption Standard (AES)-256-Galois / Counter Mode (GCM) algorithm, with a message authentication code (authTag) and an incrementing sequence number (sequenceNumber) appended to prevent replay attacks. This multi-layered secure communication mechanism is the key technical point of this step, providing end-to-end encryption protection and message integrity verification while maintaining high performance.

[0256] Once the connection is established, the management application obtains and verifies device information, confirms compatibility, and caches the session key and device information in preparation for subsequent signature requests. This entire connection process eliminates the need for the user to manually enter a pairing code or perform complex operations, while maintaining a high level of security and significantly improving the system's usability and attack resistance.

[0257] Next, the object is used to set the credential parameters on the management application software. The credential parameter configuration table where the credential parameters can be set can refer to Table 1, including various parameters and the data type and parameter description of each parameter response.

[0258] Table 1 Credential parameter configuration table

[0259] parameter Data Type illustrate Amount limit Decimal The maximum amount that the voucher can be used for Validity period DateTime The time when the certificate expires Usage scenarios String[] Allowed merchant categories Use times Integer Maximum number of times that can be used Security Options Object Additional safety control parameters

[0260] The corresponding data structure can be as follows, and security options can include geographical location restrictions:

[0261]

[0262]

[0263] During the voucher parameter setting and data construction phase, multiple rounds of interaction occur between the user and the management application to construct a complete voucher data structure. First, the user enters basic parameters (userInputParams) through the management application interface, including amount limits (amountLimit), validity period options (validityPeriod), and usage scenarios (usageScenarios). The management application receives these inputs, performs data validation and normalization, and converts the user-friendly input into a system-standard format. For example, to convert a "7-day" validity period option into a precise UTC timestamp (validUntilTimestamp), the calculation method is to add the number of seconds in 7 days (7 * 24 * 60 * 60) to the current time (currentTimestamp).

[0264] The management application then sends the hashed data of the credential parameters to the hardware wallet.

[0265] The management application constructs an initial credential data object (certificateDataObject) based on the user object input and system configuration. The system first generates a globally unique credential ID (certificateId), which can use a UUID v4 algorithm or a combination of a timestamp and a random number. The management application retrieves the currently connected hardware wallet identifier (walletId) from secure storage and adds it to the data object. The system may also generate a cryptographically secure random number (nonce) and the current accurate timestamp (timestamp) to prevent replay attacks and ensure credential validity.

[0266] For advanced security options (securityOptions), if geolocation restrictions are enabled for the user, the management application can obtain the current location coordinates (currentLocation) or the coordinates of the area specified by the user (specifiedLocation), convert them to a standard geocoding format (geoHash), and add them to the credential data. Similarly, if the user notification feature is enabled, the system can encode the user's notification preferences (notificationPreferences) and notification target (notificationTarget, such as a mobile phone number or email address) and add them to the data object.

[0267] After the data object is constructed, the management application serializes the entire object into a compact binary format (binaryData). Efficient encoding methods such as Concise Binary Object Representation (CBOR) or MessagePack can be used to reduce the data size. The system then calculates the SHA-256 hash value (dataHash) of this binary data, which is sent to the hardware wallet as the data to be signed. At the same time, the original credential data object is stored in the management application's temporary secure storage area (secureTemporaryStorage), waiting to be merged with the signature result. The entire process ensures the integrity, uniqueness, and security of the credential data, preparing for the next step of digital signing.

[0268] The hardware wallet then uses its internal private key to encrypt the hash data into a digital signature and returns it to the management application. The signature algorithm can be ECDSA (secp256k1), EdDSA (Ed25519), or ECDSA (P-256). The signature request format is as follows:

[0269]

[0270] The format of the signed response is as follows:

[0271]

[0272] During the hardware wallet signing process, a sophisticated and secure data exchange occurs between the management application and the hardware wallet. First, the management application serializes the previously constructed certificate data object (certificateDataObject) and calculates a SHA-256 hash value (dataHash). It then generates a globally unique request identifier (requestId), which can use the UUID v4 algorithm, and creates a complete signature request object (signatureRequest), which contains dataHash, requestId, the current timestamp (requestTimestamp), and metadata (metadata). The metadata contains key credential information such as the amount (amountValue) and expiry date (expiryDate), which is displayed on the hardware wallet screen.

[0273] The management application encrypts the signature request object using the session key (sessionKey) and the AES-256-GCM algorithm through the previously established secure channel to form an encrypted request (encryptedRequest), attaches a message authentication code (authTag), and sends it to the hardware wallet. After receiving the request, the hardware wallet first uses the session key to decrypt the data, verifies the message authentication code to ensure data integrity, and checks the request timestamp to prevent replay attacks. After verification, the hardware wallet displays key information on its display, including the operation type ("signature request"), amount information, and validity period, and waits for physical confirmation of the user.

[0274] The user object checks the information on the hardware wallet screen. After confirming that it is correct, press the physical confirmation button (physicalButton) on the hardware wallet to authorize the signing operation. At this point, the secure element (secureElement) inside the hardware wallet activates and reads the private key (privateKey) from its tamper-proof storage. The secure element uses the private key and the specified signature algorithm (which can be ECDSAsecp256k1) to calculate the signature of dataHash, generating a digital signature (digitalSignature) and recording the signature timestamp (signatureTimestamp).

[0275] The hardware wallet constructs a signature response object (signatureResponse), which contains the original requestId, the generated digitalSignature (encoded in hexadecimal format), the hardware wallet's unique identifier (walletId), the signature algorithm identifier used (algorithmId), and signatureTimestamp. The response object is also encrypted using the session key to form an encrypted response (encryptedResponse), which is sent back to the management application. After receiving the response, the management application decrypts the data, verifies that the requestId matches to ensure that it is a response to the correct request, and then stores the digitalSignature together with the original certificate data (certificateData) and walletId to complete the signing process. The entire process ensures the security and non-repudiation of the signing operation because the private key is always kept inside the hardware wallet and each signature requires physical confirmation of the object.

[0276] Subsequently, the management application software generates a shared credential based on the credential parameters and digital signature, and previews the shared credential. The data structure of the shared credential can be shown in Table 2, including multiple fields and corresponding field lengths and descriptions.

[0277] Table 2 Shared credential data structure

[0278] Field Length (bytes) illustrate Version 1 Protocol version number CertificateId 16 Credential ID (UUID) WalletId 8 Wallet ID (compressed format) Amount 4 Amount (integer part*100+decimal part) ValidUntil 4 Expiration timestamp (Unix timestamp) Restrictions variable length Usage restrictions (TLV encoding) Signature 64 / 32 Digital Signature (ECDSA / EdDSA) Checksum 2 CRC16 checksum

[0279] The management application integrates all the data elements obtained in the previous steps into the final certificate data structure. First, the management application retrieves the original certificate data object (certificateDataObject) from secure storage and the digital signature (digitalSignature) obtained from the hardware wallet. The system generates a protocol version identifier (protocolVersion, usually 0x01) as the first byte of the data structure to support backward compatibility during future protocol upgrades.

[0280] The management application then begins constructing the binary data package (binaryPackage). The system first writes the protocolVersion, followed by the 16-byte UUID value of the certificate ID (certificateId). To reduce data size, the wallet ID (walletId) is processed using a special compression algorithm, mapping the original identifier to an 8-byte compressed format (compressedWalletId). The amount data (amountValue) is converted to an integer representation, multiplying the amount by 100 and rounding it, such as converting 500.75 yuan to 50075, and stored as a 4-byte integer. The validity period (validUntil) is converted to a Unix timestamp (unixTimestamp) and also stored as a 4-byte integer.

[0281] For usage restriction data (restrictionsData), the system uses the TLV (Tag-Length-Value) encoding format. Each restriction condition consists of a tag byte (tagByte), a length byte (lengthByte), and the actual value. For example, the tag for merchant category restrictions might be 0x01, and the tag for geographic location restrictions might be 0x02. This encoding method allows for the flexible addition of different types of restrictions while only taking up the necessary space. The digital signature (digitalSignature) is directly appended in raw binary form. ECDSA signatures are typically 64 bytes, and EdDSA signatures are 32 bytes. Finally, the system calculates the CRC16 checksum (checksumValue) of the entire data packet (excluding the checksum field) and appends it to the end of the packet as the last 2 bytes.

[0282] After the complete binary data package is constructed, the system applies the DEFLATE compression algorithm to reduce the data volume and generate compressed data (compressedData). To further optimize the complexity of the QR code, the system can also apply Base45 encoding. The processed data serves as the input content of the QR code (qrInputData). The system automatically selects the appropriate QR code version (qrVersion) and error correction level (errorCorrectionLevel) based on the data length, typically selecting level M (15% error correction capability) as a balance between reliability and data density. Using a professional QR code generation library (such as ZXing), the system generates a high-quality QR code image (qrCodeImage) with a resolution of at least 300x300 pixels to ensure scanning reliability after printing.

[0283] The generated QR code, together with the basic certificate information (such as amount and validity period), constitutes a complete certificate preview (certificatePreview), which is displayed to the user for confirmation. At the same time, the system saves the complete certificate data object, binary data package, and generated QR code image to local secure storage (secureStorage), and optionally synchronizes the certificate metadata to the cloud server (cloudServer) for subsequent management and verification.

[0284] Next, the object is used to instruct the management application to print the shared credential. The management application retrieves the credential data and QR code image from secure storage and constructs a print document based on a predefined template. The system combines the credential's key information with the QR code image to generate a complete print layout, ensuring both readability of the key information and machine readability of the QR code.

[0285] The system converts the print layout into the appropriate format based on the capabilities of the target printer, while applying special processing to the QR code area, such as edge enhancement and contrast optimization, to avoid various environmental factors that physical credentials may face during use, such as creases, partial wear or insufficient light.

[0286] The management application then sends a print job for the shared credentials to the printer. The management application supports various printing devices, including network printers, Bluetooth printers, and cloud printing services, through multiple communication protocols, constructing a print job object with precise parameters.

[0287] Then, the printer prints the shared certificate and generates a print result. A schematic diagram of the shared certificate can be referred to Figure 18 As shown, a high-definition QR code is placed in the center of the shared voucher 1800; the title "Hardware Wallet Check Voucher" is displayed at the top; key information is included: upper limit of amount, validity period, purpose, etc.; the voucher ID is displayed at the bottom, and anti-counterfeiting design elements can be optionally added (not shown in the figure). It can be understood that the above position division is only an example.

[0288] The printer then sends the print results to the management application software.

[0289] Finally, the management application software displays the print results. Once printing is complete, the system updates the voucher status to "Printed" and records complete print event information, including timestamp, printer identification, and result status. This ensures data integrity and traceability across the entire system, preventing duplicate printing and unauthorized use of vouchers.

[0290] Step 1606: Scan the client to obtain the payment event and shared credentials.

[0291] A scanning client refers to a terminal application or device that reads by scanning codes (such as QR codes, bar codes) or NFC. The scanning client can scan the goods to be consumed to generate a payment event, which may include payment parameters such as payment resource amount, payment scenario, payment time, and payment location. The payment resource amount can be the amount of assets paid, which is generated by mapping the price of the goods; the payment scenario can be the transaction type (such as "goods purchase", "service payment"), or the type of merchant where the payment is made; the payment time can be the timestamp of the transaction; and the payment location can be the geographical location or network location of the merchant where the transaction is made. Accordingly, the scanning client scans the shared credential to obtain information about the shared credential object.

[0292] Step 1607: The scanning client generates a payment request based on the payment event and the shared credential, and sends the payment request to the server.

[0293] The payment request may be an asset transfer request initiated to the server. The payment request may include the payment parameters in the payment event and the credential identifier corresponding to the shared credential, instructing the server to consume the resource account corresponding to the shared credential based on the payment parameters.

[0294] Step 1608: The server verifies the payment resource amount, payment scenario, payment time, and payment location in the payment request according to the resource sharing parameters of the shared credential corresponding to the credential identifier.

[0295] When the server verifies the payment request based on the resource sharing parameters of the shared credential corresponding to the credential identifier, it can first obtain the complete shared credential from the database through the credential identifier, and at the same time verify the legality of the identifier format and the validity of the shared credential to ensure that the shared credential is in an activated state and has not expired. The server can compare the payment resource amount in the payment request with the maximum resource amount in the shared credential, and reject the request if the payment amount exceeds the shared credential limit. In terms of payment time verification, the server can parse the request time and the sharing time of the shared credential to confirm whether the payment behavior is within the time period allowed by the credential to avoid timeout operations. For the verification of payment scenarios, the server can check whether the requested scenario is in the list of scenarios allowed by the shared credential, and payment requests that do not match the scenario will be blocked. The compliance verification of the payment location includes both geographic location and IP address. The server can determine whether the payment latitude and longitude are within the area allowed by the shared credential.

[0296] Step 1609: When the verification is successful, the server obtains the public key corresponding to the wallet identifier and verifies the validity of the digital signature based on the public key.

[0297] Once the server successfully verifies the payment request, it can retrieve the public key corresponding to the wallet identifier to verify the validity of the digital signature. During this process, the server retrieves the matching public key from the network or local secure storage based on the wallet identifier. This public key forms an asymmetric encryption pair with the private key used for signing in the hardware wallet, ensuring the reliability of the signature verification. After obtaining the public key, the server can decrypt the digital signature in the shared credential and compare the decrypted result with the hash value of the resource sharing parameter in the shared credential. If the results match, the digital signature is proven valid.

[0298] Step 1610: When the verification is successful, the server transfers resources to the resource account corresponding to the shared credential based on the payment resource amount and generates a payment result.

[0299] The payment result may refer to the structured data generated by the server after the digital payment process is completed, which records the entire transaction process. It is the final proof of "whether the payment behavior is successful" and "how the resources are transferred", and may include the transaction amount, time, status, etc.

[0300] Step 1611: The server generates payment prompt information according to the payment result and the payment resource amount, and sends the payment prompt information to the scanning client.

[0301] Payment reminder information can be feedback information generated by the server based on the payment result and payment resource amount after the payment process is completed and sent to the scanning client. It is used to intuitively display the payment status and related details to the consumer. It can clearly indicate "payment successful" or "payment failed" through simple language and icons, and can also highlight the actual amount and type of assets paid. Correspondingly, the scanning client can also generate a printed receipt based on the payment reminder information for the consumer to keep.

[0302] In one example, the payment process based on shared credentials can refer to Figure 19 As shown, first, the scanning client obtains a transaction request. The scanning client can obtain the transaction request from the cash register system, and the transaction request may include the current transaction amount (transactionAmount) and the currency type (currencyCode).

[0303] Next, the scanning client scans the QR code on the paper shared voucher to confirm the voucher information. The check holder hands the paper check voucher to the merchant, who activates the scanning program (scannerModule) using the scanning client's built-in high-definition camera (camera). The scanning client decodes the QR code content from the captured image to obtain the raw binary data (rawBinaryData). The decoded data is first verified by CRC16 (checksumVerification) to ensure integrity, then decompressed (dataDecompression) to restore it to structured certificate data (certificateData), including fields such as protocol version (protocolVersion), certificate ID (certificateId), wallet ID (walletId), amount limit (amountLimit), validity period (validUntil), and digital signature (digitalSignature).

[0304] The scanning client then retrieves the merchant identifier (merchantId) and terminal device identifier (terminalId) from its local configuration and generates a globally unique payment request ID (requestId), for example using the UUID v4 algorithm. The system records the current precise timestamp (currentTimestamp). The scanning client may also collect additional information (additionalInfo), such as the current geographic location coordinates (geoLocation), merchant category code (merchantCategoryCode), and transaction notes (transactionMemo).

[0305] Next, the scanning client generates a payment request based on the transaction amount and voucher identifier and sends it to the server. The scanning client assembles this data into a complete payment request object (paymentRequest), serializes it using a format such as JSON or ProtocolBuffers, and sends it to the payment gateway via a TLS1.3 encrypted channel. After receiving the request, the payment gateway first verifies the request format (requestFormatValidation) and mandatory fields (mandatoryFieldsCheck), generates an internal request identifier (internalRequestId), and stores the mapping between the original request and the internal identifier in the request log (requestLog). The payment gateway can also add additional metadata (gatewayMetadata), such as the gateway node identifier (nodeId), processing timestamp (processingTimestamp), and routing information (routingInfo). It then forwards the enriched request (enrichedRequest) to the server for transaction verification and simultaneously activates the request timeout timer (timeoutTimer) and status monitoring (statusMonitoring) to ensure the reliability and traceability of request processing.

[0306] The server then queries the credential database for complete credential information and verifies the validity of the shared credential. This involves intensive data exchange between the server and the credential database, performing multi-layered security verification. First, the server receives the enriched payment request (enrichedRequest) from the payment gateway, parses the certificate ID (certificateId) and wallet ID (walletId), and constructs a database query request (databaseQuery) containing the certificate ID, query timestamp (queryTimestamp), and request origin identifier (requestOrigin), which it then sends to the credential database.

[0307] After receiving a query request, the credential database first checks the cache layer (cacheLayer) for a corresponding record. If a match exists, the cached data (cachedCertificateData) is directly returned. If a match does not exist, a database query (dbLookup) is performed to retrieve the complete credential record (certificateRecord) from persistent storage. The credential record returned by the database includes information such as the original data at creation (originalCertificateData), current status (currentStatus), used amount (usedAmount), usage history (usageHistory), and last update time (lastUpdateTimestamp). The database also records the query operation (queryOperation) in the audit log (auditLog) and returns the query results to the server.

[0308] After receiving the voucher record, the server first checks the voucher status (statusCheck) to confirm that the voucher is in the "ACTIVE" state, rather than the "REVOKED" or "EXPIRED" states. The server then compares the current time (currentTime) with the voucher's validity period (validUntil) and performs expiry validation (expiryValidation). The system then checks the transaction amount (transactionAmount) against the remaining available amount on the voucher (remainingAmount, which is amountLimit minus usedAmount) to ensure the transaction does not exceed the limit.

[0309] For usage scenario restrictions, the server can compare the merchant category code (merchantCategoryCode) with the list of allowed usage scenarios (allowedScenarios) of the certificate to ensure compliance with the usage restrictions. It can also extract the original data portion (certificateDataWithoutSignature) from the certificate data and calculate the data hash value (computedDataHash) using the same hash algorithm (such as SHA-256); then obtain the corresponding public key (publicKey) from the key management service (keyManagementService) based on the wallet ID; finally, use the public key and signature algorithm (ECDSA or EdDSA) to verify the validity of the digital signature (digitalSignature).

[0310] To prevent replay attacks, the server can also check the usage history of the credentials (usageHistory) to ensure that there is a sufficient time interval between the current transaction and the previous transaction, or that the transaction location has a reasonable geographical distance. All verification results (validationResults) are combined into a comprehensive assessment (overallAssessment), which contains the detailed results of each verification and the final authorization decision (authorizationDecision). If all verifications pass, the server can generate an authorization identifier (authorizationId) to prepare for subsequent account operations; if any verification fails, the server can generate a detailed rejection reason (rejectionReason), including the specific failure item and error code (errorCode).

[0311] Afterwards, the server queries the account system for the available balance of the account associated with the shared voucher, deducts the amount from the associated account based on the transaction amount, generates a payment result, and updates the available balance. Based on the verified shared voucher, a transaction data structure can be generated in conjunction with the payment request. The data structure can be as follows:

[0312]

[0313] During the account processing and transaction execution phase, the server extracts the account identifier (accountId) from the credential information, constructs a query request, and sends it to the account system. After verifying the legitimacy of the request, the account system retrieves account information from the shard database, including data such as balance, status, and transaction limits, and verifies whether the account status and available balance meet the transaction conditions.

[0314] After the balance check passes, the server constructs an execution request, including key information such as transaction type, amount, authorization ID, and voucher ID. The account system generates a globally unique transaction ID, using a time-ordered UUID algorithm to ensure global uniqueness and chronological order. A distributed transaction is then initiated, first creating a record in the transaction log table with a "processing" status, then calculating the new balance and updating the account table. Optimistic or pessimistic locking is used to ensure concurrency. This ensures that account data remains consistent even in the event of a partial system failure, effectively preventing double spending and fund loss.

[0315] After the transaction is completed, the account system returns a transaction response and may send an asynchronous notification to the account owner through the message queue. The server then updates the record in the voucher database, increases the amount used, and adds the new usage record to the history.

[0316] The server can construct a payment result object (paymentResult) containing key transaction information, including basic fields such as the result code, transaction ID, authorization code, and transaction amount. For successful transactions, the system also appends receipt data and voucher status information, such as the remaining amount and expiration date. The payment result data structure can be as follows:

[0317]

[0318] The server then sends the payment result to the scanning client. The server can transmit the payment result to the payment gateway via a secure channel. Upon receiving the payment result, the payment gateway verifies the request-response consistency, performs any necessary format conversions, and adds gateway-specific information before forwarding it to the scanning client.

[0319] Finally, the scanning client displays the payment result and prints the transaction receipt. The scanning client can generate the receipt content according to the preset template and send it to the printing device through the standard interface to complete the physical receipt output. The transaction receipt printing template can refer to Figure 20 As shown, the top of the transaction receipt printout template 2000 includes space for the merchant's name, address, and contact number. The transaction date is XX / XX / XX, the time is 2:30:45 PM, and the payment number is T12345678. The payment method is a hardware wallet check, the receipt ID is HwCT-********-9C31, and the transaction amount is 120.50 yuan. Finally, it clearly indicates the transaction is successful, and expresses gratitude to the customer with the phrase "Thank you for your patronage."

[0320] In one example, the schematic diagram of the server performing resource transfer can be referred to as Figure 21 As shown, transaction processing server 2101 initiates a resource transfer to account information system 2102 based on the transaction amount and shared voucher. Account information system 2102 uses the account query service to query the account database 2103 for the account information corresponding to the shared voucher, such as the account balance and transaction details. It then transfers resources to the account corresponding to the shared voucher based on the account balance and transaction amount, updates the account information in account database 2103, and records the transaction-related information in transaction log database 2104. Asynchronous communication is implemented through message queue 2105, notifying consumers of transaction results and other information.

[0321] In one example, the resource sharing architecture diagram in the embodiment of the present disclosure can refer to Figure 22 As shown, a four-layer architecture is adopted, which is respectively composed of the user object layer 221, the hardware layer 222, the terminal layer 223 and the background service layer 224 from top to bottom. The user object layer 221 includes merchants 2211, sharing parties 2212 and shared parties 2213.

[0322] Merchant 2211: A commercial entity that accepts check vouchers for transaction settlement.

[0323] Shared Party 2212: The owner of the hardware wallet, responsible for creating and distributing check vouchers through the management application software.

[0324] Shared party 2213: A secondary user of the voucher, who receives the voucher distributed by the user and uses it for payment.

[0325] The hardware layer 222 includes a hardware wallet 2221, management application software 2222, a printer 2223, and a paper shared certificate 2224;

[0326] Hardware wallet 2221: A secure hardware device that stores the shared party’s assets and keys.

[0327] Management application software 2222: an application that interacts with the hardware wallet, providing an interactive interface and credential generation functions.

[0328] Printer 2223: A device that converts digital certificates into physical carriers.

[0329] Paper shared certificate 2224: A physical certificate that carries payment authorization information, including a QR code and transaction restriction information.

[0330] The terminal layer 223 includes a scanning client 2231 and a payment gateway 2232. The scanning client 2231 is a terminal device that receives and processes payment requests, responsible for scanning the voucher QR code and initiating transactions. The payment gateway 2232 is an intermediate layer connecting the merchant terminal and the backend server, responsible for forwarding transaction requests and returning results.

[0331] The backend service layer 224 includes a transaction processing service module 2241 and a data storage service module 2242;

[0332] Transaction processing service module 2241 includes transaction verification service module 22411, signature verification module 22412, and credit limit control module 22413. Transaction verification service module 22411 serves as the central control unit for transaction processing, coordinating various modules to complete transaction verification. Signature verification module 22412 verifies the authenticity of the voucher signature to ensure that the voucher has not been tampered with. Credit limit control module 22413 checks whether the transaction amount exceeds the voucher limit, enabling precise credit limit management.

[0333] The data storage service module 2242 includes an account system 22421, a voucher management system 22422, a transaction database 22423, and a voucher database 22424. Among them, the account system 22421 manages the assets and balance information of the sharing party, and is responsible for receiving account queries, fund deductions, and updates from the transaction verification service module 22411. The voucher management system 22422 handles the lifecycle management of vouchers, including creation, use, and expiration, as well as accepting voucher queries and voucher status updates from the transaction verification service module 22411. The transaction database 22423 stores all transaction records and supports transaction tracing and reconciliation of the account system 22421. The voucher database 22424 stores all voucher information, including status, usage records, and validity period, and accepts data reading and writing from the voucher management system 22422.

[0334] Description of the apparatus and device of the present disclosure

[0335] It is to be understood that, although the steps in the above-mentioned flowcharts are shown in sequence according to the arrow representations, these steps are not necessarily performed in sequence according to the order represented by the arrows. Unless otherwise specified in the present embodiment, there is no strict order restriction on the execution of these steps, and these steps can be performed in other orders. Moreover, at least a portion of the steps in the above-mentioned flowcharts may include multiple steps or multiple stages, and these steps or stages are not necessarily performed at the same time, but can be performed at different times, and the execution order of these steps or stages is not necessarily performed in sequence, but can be performed in turn or alternately with other steps or at least a portion of the steps or stages in other steps.

[0336] It should be noted that in each specific embodiment of the present disclosure, when it comes to the need to perform relevant processing based on data related to the characteristics of the target object, such as the target object attribute information or attribute information set, the permission or consent of the target object will be obtained first, and the collection, use and processing of such data will comply with the relevant laws, regulations and standards of the relevant region. In addition, when the embodiment of the present application needs to obtain the attribute information of the target object, the target object's separate permission or separate consent will be obtained through a pop-up window or by jumping to a confirmation page. After clearly obtaining the target object's separate permission or separate consent, the necessary target object-related data for the normal operation of the embodiment of the present application will be obtained.

[0337] Figure 23 This is a schematic diagram of the structure of a processing device 2300 for a resource management application provided in an embodiment of the present disclosure. The device includes:

[0338] The first display unit 2301 is configured to display a resource sharing credential creation interface in response to a resource sharing credential creation trigger received in the resource management application;

[0339] The second display unit 2302 is configured to display a credential creation permission verification interface in response to a sharing parameter setting completion operation received in the resource sharing credential creation interface;

[0340] The third display unit 2303 is configured to display a credential display interface when the permission verification operation based on the credential creation permission verification interface indicates that the verification is passed;

[0341] The distribution unit 2304 is configured to distribute the generated resource sharing voucher in response to a voucher distribution operation received on the voucher display interface.

[0342] Optionally, in some embodiments, the first display unit 2301 includes:

[0343] A first display subunit is configured to display an application function interface of a resource management application, wherein the application function interface includes a resource sharing credential creation control;

[0344] The second display sub-unit is configured to display a resource sharing credential creation interface in response to a triggering operation on the resource sharing credential creation control.

[0345] Optionally, in some embodiments, the second display subunit includes:

[0346] A first display module is configured to display a credential creation setting label in response to a triggering operation on the resource sharing credential creation control, wherein the credential creation setting label includes an account setting control;

[0347] A second display module is configured to display a plurality of candidate accounts in response to a triggering operation on the account setting control;

[0348] The third display module is configured to display a resource sharing credential creation interface in response to a selection operation on a target account from among the plurality of candidate accounts.

[0349] Optionally, in some embodiments, the third display unit 2303 includes:

[0350] The third display subunit is used to display the password verification area for the savings entity object on the voucher creation authority verification interface;

[0351] a fourth display subunit, configured to display a password verification interface in response to a password input completion operation received in the password verification area;

[0352] The fifth display subunit is used to display the credential display interface when the password verification received on the password verification interface passes.

[0353] Optionally, in some embodiments, the third display unit 2303 includes:

[0354] The sixth display sub-unit is used to display a verification prompt for the hardware wallet on the credential creation permission verification interface;

[0355] The seventh display sub-unit is used to display a credential display interface when the verification of the target hardware wallet is completed based on the verification prompt.

[0356] Optionally, in some embodiments, the second display unit 2302 includes:

[0357] An eighth display subunit, configured to display a shared resource quantity input area and a validity period input area in the resource sharing voucher creation interface;

[0358] A first receiving subunit is configured to receive a shared resource amount based on a resource amount input area, and receive a shared validity period based on a validity period input area;

[0359] The ninth display sub-unit is configured to, in response to a creation trigger operation on the resource sharing credential creation interface, display a credential creation permission verification interface based on the shared resource amount and the sharing validity period.

[0360] Optionally, in some embodiments, the first receiving subunit includes:

[0361] A fourth display module is used to display a resource quantity input text box in the resource quantity input area;

[0362] The first receiving module is configured to receive a resource sharing amount based on a resource amount input text box.

[0363] Optionally, in some embodiments, the first receiving subunit includes:

[0364] A fifth display module, configured to display a resource quantity edit control in the resource quantity input area;

[0365] a sixth display module, configured to display a candidate resource amount list in response to a triggering operation on the resource amount editing control, the candidate resource amount list including a plurality of candidate resource amounts;

[0366] The second receiving module is configured to receive, in response to a selection operation on a target resource amount in the candidate resource amount list, a shared resource amount corresponding to the target resource amount based on a resource amount input area.

[0367] Optionally, in some embodiments, the second display unit 2302 further includes:

[0368] a tenth display subunit, configured to display a usage scenario input area when the amount of shared resources is greater than a preset resource threshold;

[0369] a second receiving subunit, configured to receive a resource sharing scenario of a shared resource amount based on a usage scenario input area;

[0370] The ninth display subunit includes:

[0371] The seventh display module is configured to, in response to a creation trigger operation on the resource sharing credential creation interface, display a credential creation permission verification interface based on the amount of shared resources, sharing time, and resource sharing scenario.

[0372] Optionally, in some embodiments, the dispatch unit 2304 includes:

[0373] An eleventh display subunit is used to display a print function control on the voucher display interface;

[0374] The printing subunit is used to print the generated resource sharing certificate in response to the triggering operation of the printing function control.

[0375] Optionally, in some embodiments, the dispatch unit 2304 includes:

[0376] A twelfth display subunit is used to display the sharing function control on the credential display interface;

[0377] a thirteenth display subunit, configured to display a candidate sharing object list in response to a triggering operation on the sharing function control;

[0378] The sending subunit is configured to send the generated resource sharing credential to the target sharing object in response to a selection operation on the target sharing object in the candidate sharing object list.

[0379] Optionally, in some embodiments, the third display unit 2303 includes:

[0380] The transceiver subunit is used to send the resource sharing parameters received in the resource sharing credential creation interface to the hardware wallet when the credential creation permission verification interface triggers the verification process, and receive the verification result generated by the hardware wallet based on the resource sharing parameters;

[0381] The fourteenth display subunit is used to display a credential display interface when the verification result indicates that the verification is passed.

[0382] A third aspect of the present disclosure provides a hardware wallet verification device, comprising:

[0383] a fourth display unit, configured to display a resource prompt interface, wherein the resource prompt interface includes resource sharing parameters;

[0384] The generating unit is configured to generate a digital signature based on a preset private key and the resource sharing parameters when receiving a confirmation instruction for the resource sharing parameters in the resource prompt interface, and generate a verification result based on the digital signature.

[0385] Optionally, in some embodiments, the third display unit 2303 includes:

[0386] A generating subunit, configured to generate a resource sharing credential based on the digital signature and resource sharing parameters in the verification result;

[0387] The display subunit is used to display the credential display interface, which includes resource sharing credentials.

[0388] A fourth aspect of the present disclosure provides a device for processing resource sharing credentials, including:

[0389] A first acquiring unit is configured to acquire a resource transfer request, where the resource transfer request includes a resource transfer amount;

[0390] The second acquisition unit is used to obtain the digital signature, resource sharing parameters and wallet identifier corresponding to the hardware wallet in the resource sharing certificate;

[0391] A determination unit, configured to determine a public key based on a wallet identifier;

[0392] A verification unit, configured to verify the digital signature based on the public key and resource sharing parameters;

[0393] The resource transfer unit is used to transfer resources to the resource account corresponding to the hardware wallet according to the resource transfer amount when the verification is passed.

[0394] Optionally, in some embodiments, the resource transfer unit includes:

[0395] A determination subunit, configured to determine a remaining amount of resource sharing corresponding to the resource sharing voucher;

[0396] The resource transfer subunit is used to transfer resources to the resource account corresponding to the hardware wallet based on the resource transfer amount and the resource sharing remaining amount, and update the resource sharing remaining amount.

[0397] Reference Figure 24 , Figure 24 The following is a block diagram of the structure of a terminal 140 for implementing the processing method of the resource management application according to an embodiment of the present disclosure. The terminal 140 includes: a radio frequency (RF) circuit 2410, a memory 2415, an input unit 2430, a display unit 2440, a sensor 2450, an audio circuit 2460, a wireless fidelity (WiFi) module 2470, a processor 2480, and a power supply 2490. It will be understood by those skilled in the art that Figure 24 The illustrated structure of the terminal 140 does not limit the structure of a mobile phone or a computer, and may include more or fewer components than shown in the figure, or combine certain components, or arrange the components differently.

[0398] The RF circuit 2410 may be used for receiving and sending signals during information transmission or calls. In particular, after receiving downlink information from the base station, it is sent to the processor 2480 for processing. In addition, the designed uplink data is sent to the base station.

[0399] The memory 2415 may be used to store software programs and modules. The processor 2480 executes various functional applications and document editing of the terminal by running the software programs and modules stored in the memory 2415 .

[0400] The input unit 2430 may be configured to receive input digital or character information and generate key signal input related to the terminal's settings and function control. Specifically, the input unit 2430 may include a touch panel 2431 and other input devices 2432 .

[0401] The display unit 2440 may be configured to display input information or provided information and various menus of the terminal. The display unit 2440 may include a display panel 2441.

[0402] The audio circuit 2460 , the speaker 2461 , and the microphone 2462 may provide an audio interface.

[0403] In this embodiment, the processor 2480 included in the terminal 140 can execute the processing method of the resource management application in the previous embodiment.

[0404] The terminal 140 in the embodiment of the present disclosure includes but is not limited to a mobile phone, a computer, an intelligent voice interaction device, a smart home appliance, a vehicle-mounted terminal, an aircraft, etc.

[0405] Figure 25 A structural block diagram of a portion of a server 110 for implementing the processing method of a resource management application according to an embodiment of the present disclosure. The server 110 may vary greatly due to different configurations or performances, and may include one or more central processing units (CPUs) 2522 (e.g., one or more processors) and a storage device 2532, and one or more storage media 2530 (e.g., one or more mass storage devices) for storing application programs 2542 or data 2544. The storage device 2532 and the storage medium 2530 may be temporary storage or permanent storage. The program stored in the storage medium 2530 may include one or more modules (not shown in the figure), and each module may include a series of instruction operations on the server 110. Furthermore, the central processing unit 2522 may be configured to communicate with the storage medium 2530 to execute a series of instruction operations in the storage medium 2530 on the server 110.

[0406] The server 110 may also include one or more power supplies 2526, one or more wired or wireless network interfaces 2550, one or more input and output interfaces 2558, and / or one or more operating systems 2541, such as Windows Server™, Mac OS X™, Unix™, Linux™, FreeBSD™, etc.

[0407] The central processor 2522 in the server 110 may be configured to execute the processing method of the resource management application according to the embodiment of the present disclosure.

[0408] The embodiments of the present disclosure further provide a storage medium for storing program code, and the program code is used to execute the processing method of the resource management application of each of the aforementioned embodiments.

[0409] The present disclosure also provides a computer program product, which includes a computer program. A processor of an electronic device reads and executes the computer program, so that the electronic device executes the processing method for implementing the resource management application.

[0410] The terms "first," "second," "third," "fourth," and the like (if any) in the specification of the present disclosure and the accompanying drawings are used to distinguish similar objects and are not necessarily used to describe a particular order or precedence. It should be understood that the terms used in this manner are interchangeable where appropriate, so that the embodiments of the present disclosure described herein, for example, can be implemented in orders other than those illustrated or described herein. In addition, the terms "comprises" and "comprising," and any variations thereof, are intended to cover non-exclusive inclusions, e.g., a process, method, system, product, or apparatus comprising a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such process, method, product, or apparatus.

[0411] It should be understood that in the present disclosure, "at least one (item)" refers to one or more, and "plurality" refers to two or more. "And / or" is used to describe the association relationship of associated objects, indicating that three relationships may exist. For example, "A and / or B" can mean: only A exists, only B exists, and A and B exist at the same time, where A and B can be singular or plural. The character " / " generally indicates that the previous and next associated objects are in an "or" relationship. "At least one of the following items" or similar expressions refers to any combination of these items, including any combination of single items or plural items. For example, at least one of a, b or c can mean: a, b, c, "a and b", "a and c", "b and c", or "a and b and c", where a, b, c can be single or multiple.

[0412] It should be understood that in the description of the embodiments of the present disclosure, the meaning of multiple (or multiple items) is more than two, greater than, less than, exceed, etc. are understood to exclude the number itself, and above, below, within, etc. are understood to include the number itself.

[0413] In the several embodiments provided in the present disclosure, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are merely schematic. For example, the division of units is only a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be an indirect coupling or communication connection through some interfaces, devices or units, which can be electrical, mechanical or other forms.

[0414] Units described as separate components may or may not be physically separate, and components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of these units may be selected to achieve the purpose of this embodiment according to actual needs.

[0415] In addition, the functional units in the various embodiments of the present disclosure may be integrated into a single processing unit, or each unit may exist physically separately, or two or more units may be integrated into a single unit. The aforementioned integrated units may be implemented in the form of hardware or software functional units.

[0416] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a storage medium. Based on this understanding, the technical solution of the present disclosure is essentially or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes several instructions for enabling a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the various embodiments of the present disclosure. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM), random access memory (RAM), disk or optical disk, and other media that can store program code.

[0417] It should also be understood that the various implementations provided in the embodiments of the present disclosure can be arbitrarily combined to achieve different technical effects.

[0418] The above is a specific description of the implementation methods of the present disclosure, but the present disclosure is not limited to the above implementation methods. Those skilled in the art can make various equivalent modifications or substitutions without violating the spirit of the present disclosure. These equivalent modifications or substitutions are all included in the scope defined by the claims of the present disclosure.

Claims

1. A method for processing resource management applications, characterized in that: include: In response to a resource sharing credential creation trigger received in the resource management application, displaying a resource sharing credential creation interface; In response to a sharing parameter setting completion operation received in the resource sharing credential creation interface, displaying a credential creation authority verification interface; When the permission verification operation based on the credential creation permission verification interface indicates that the verification is passed, the credential display interface is displayed; In response to the credential distribution operation received by the credential display interface, the generated resource sharing credential is distributed.

2. The method according to claim 1, characterized in that The method of displaying a resource sharing credential creation interface in response to a resource sharing credential creation trigger received in the resource management application includes: Displaying an application function interface of a resource management application, wherein the application function interface includes a resource sharing credential creation control; In response to a triggering operation on the resource sharing credential creation control, a resource sharing credential creation interface is displayed.

3. The method according to claim 2, characterized in that The displaying of the resource sharing credential creation interface in response to the triggering operation on the resource sharing credential creation control includes: In response to a triggering operation on the resource sharing credential creation control, displaying a credential creation setting label, the credential creation setting label including an account setting control; In response to a triggering operation on the account setting control, displaying a plurality of candidate accounts; In response to a selection operation on a target account from the plurality of candidate accounts, a resource sharing credential creation interface is displayed.

4. The method according to claim 1, wherein When the permission verification operation based on the credential creation permission verification interface indicates that the verification is passed, the credential display interface is displayed, including: Displaying a password verification area for the savings entity object on the voucher creation authority verification interface; In response to a password input completion operation received in the password verification area, displaying a password verification interface; When the password verification received by the password verification interface passes, the credential display interface is displayed.

5. The method according to claim 1, wherein When the permission verification operation based on the credential creation permission verification interface indicates that the verification is passed, the credential display interface is displayed, including: Displaying a verification prompt for the hardware wallet on the credential creation permission verification interface; When the verification of the target hardware wallet is completed based on the verification prompt, the credential display interface is displayed.

6. The method according to claim 1, characterized in that The step of displaying a credential creation permission verification interface in response to a shared parameter setting completion operation received in the resource sharing credential creation interface includes: Displaying a shared resource amount input area and a validity period input area in the resource sharing voucher creation interface; receiving a shared resource amount based on the resource amount input area, and receiving a shared validity period based on the validity period input area; In response to a creation trigger operation on the resource sharing credential creation interface, a credential creation permission verification interface is displayed based on the shared resource amount and the sharing validity period.

7. The method according to claim 6, characterized in that The receiving the shared resource amount based on the resource amount input area includes: Displaying a resource quantity input text box in the resource quantity input area; A resource sharing amount is received in the text box based on the resource amount input.

8. The method according to claim 6, characterized in that The receiving the shared resource amount based on the resource amount input area includes: Displaying a resource quantity edit control in the resource quantity input area; In response to a triggering operation on the resource amount editing control, displaying a candidate resource amount list, the candidate resource amount list including a plurality of candidate resource amounts; In response to a selection operation on a target resource amount in the candidate resource amount list, a shared resource amount corresponding to the target resource amount is received based on the resource amount input area.

9. The method according to claim 6, characterized in that Before displaying the credential creation permission verification interface based on the shared resource amount and the sharing time in response to the creation trigger operation of the resource sharing credential creation interface, the method further includes: When the amount of shared resources is greater than a preset resource threshold, displaying a usage scenario input area; receiving a resource sharing scenario of the shared resource amount based on the usage scenario input area; The step of displaying a credential creation permission verification interface based on the shared resource amount and the sharing time in response to a creation trigger operation on the resource sharing credential creation interface includes: In response to a creation trigger operation on the resource sharing credential creation interface, a credential creation permission verification interface is displayed based on the shared resource amount, the sharing time, and the resource sharing scenario.

10. The method according to any one of claims 1 to 8, characterized in that The step of distributing the generated resource sharing voucher in response to the voucher distribution operation received on the voucher display interface includes: Displaying a print function control on the voucher display interface; In response to the triggering operation on the print function control, the generated resource sharing certificate is printed.

11. The method according to any one of claims 1 to 8, characterized in that The step of distributing the generated resource sharing voucher in response to the voucher distribution operation received on the voucher display interface includes: Displaying a sharing function control on the credential display interface; In response to a triggering operation on the sharing function control, displaying a candidate sharing object list; In response to a selection operation on a target sharing object in the candidate sharing object list, the generated resource sharing credential is sent to the target sharing object.

12. The method according to claim 1, characterized in that When the permission verification operation based on the credential creation permission verification interface indicates that the verification is passed, the credential display interface is displayed, including: When the credential creation permission verification interface triggers the verification process, the resource sharing parameters received in the resource sharing credential creation interface are sent to the hardware wallet, and the verification result generated by the hardware wallet based on the resource sharing parameters is received; When the verification result indicates that the verification is passed, the certificate display interface is displayed.

13. The method according to claim 12, characterized in that The verification process of the hardware wallet includes: Displaying a resource prompt interface, wherein the resource prompt interface includes the resource sharing parameters; When a confirmation instruction for the resource sharing parameter in the resource prompt interface is received, a digital signature is generated according to a preset private key and the resource sharing parameter, and a verification result is generated according to the digital signature.

14. The method according to claim 13, characterized in that The credential display interface includes: Generate a resource sharing credential based on the digital signature and the resource sharing parameter in the verification result; A credential display interface is displayed, wherein the credential display interface includes the resource sharing credential.

15. The method according to claim 14, characterized in that The resource sharing credential processing process includes: Obtaining a resource transfer request, wherein the resource transfer request includes a resource transfer amount; Obtaining the digital signature, the resource sharing parameters, and the wallet identifier corresponding to the hardware wallet in the resource sharing credential; Determine the public key based on the wallet identifier; Performing signature verification on the digital signature according to the public key and the resource sharing parameter; When the verification is passed, resources are transferred to the resource account corresponding to the hardware wallet according to the resource transfer amount.

16. The method according to claim 15, characterized in that The transferring of resources to the resource account corresponding to the hardware wallet according to the resource transfer amount includes: Determining a remaining amount of resource sharing corresponding to the resource sharing voucher; Based on the resource transfer amount and the resource sharing remaining amount, resources are transferred to the resource account corresponding to the hardware wallet, and the resource sharing remaining amount is updated.

17. A processing device for a resource management application, characterized in that: include: a first display unit, configured to display a resource sharing credential creation interface in response to a resource sharing credential creation trigger received in the resource management application; a second display unit, configured to display a credential creation permission verification interface in response to a sharing parameter setting completion operation received in the resource sharing credential creation interface; a third display unit, configured to display a credential display interface when the permission verification operation performed based on the credential creation permission verification interface indicates that the verification is passed; The distribution unit is configured to distribute the generated resource sharing certificate in response to a certificate distribution operation received by the certificate display interface.

18. A storage medium storing a computer program, characterized in that: When the computer program is executed by a processor, the processing method of the resource management application according to any one of claims 1 to 16 is implemented.

19. An electronic device comprising a memory and a processor, wherein the memory stores a computer program, wherein: When the processor executes the computer program, the method for processing the resource management application according to any one of claims 1 to 16 is implemented.

20. A computer program product, comprising a computer program, wherein the computer program is read and executed by a processor of an electronic device, so that the electronic device executes the resource management application processing method according to any one of claims 1 to 16.

Images