Methods, apparatus, devices and storage media for sending virtual item packages
By displaying candidate virtual item pack covers in the payment interface and item pack messages in the chat session interface, the problem that virtual item pack covers could only be updated when the application was updated was solved, realizing flexible configuration and updating of covers, improving user experience and product adaptability.
Patent Information
- Application Number
- CN202310695021.9
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2019-10-16
- Publication Date
- 2026-11-10
- Estimated Expiration
- 2039-10-16
AI Technical Summary
In existing technologies, the cover of virtual item packs can only be configured and updated when the application version is updated, and cannot be flexibly adjusted, which limits users' choices.
The payment interface displays candidate virtual item package covers, and after receiving a payment confirmation instruction, the item package message is displayed in the chat session interface. The payment interface content is updated through server-side configuration, enabling flexible configuration and updating of the covers.
Users can flexibly configure and update virtual item pack covers without updating the application, meeting the needs of different users and improving the product experience and internationalization.
Smart Images

Figure CN116703518B_ABST
Abstract
Description
[0001] This application is a divisional application of the invention patent application filed on October 16, 2019, with application number 201910984625.9 and the invention title "Method, Apparatus, Device and Storage Medium for Sending Virtual Item Packages". Technical Field
[0002] This application relates to the fields of computer and internet technology, and in particular to a method, apparatus, device, and storage medium for sending virtual item packages. Background Technology
[0003] With the development of internet technology, users can now gift resources using virtual item packs on their client applications. These resources can include currency, points, equipment from online games, and virtual pets, among other things.
[0004] Taking the use of virtual item packs as a medium for gifting currency as an example, after receiving the virtual item pack generation instruction, the sending client displays the virtual item pack sending interface and retrieves the virtual item pack parameters entered in the interface. These parameters can include the amount of currency to be gifted, the number of virtual item packs requested, and the amount of currency contained in each pack. After the user completes the input of the virtual item pack parameters, the sending client sends a virtual item pack generation request to the backend server, which includes the virtual item pack parameters. The backend server generates the virtual item packs based on the parameters and sends them to the corresponding receiving client. The user on the receiving client can then open the virtual item packs to obtain the currency within.
[0005] In related technologies, the virtual item package sending interface displayed on the sending client also includes several candidate virtual item package covers. The virtual item package cover is similar to the envelope of a physical red envelope. Users can select a virtual item package cover from the virtual item package sending interface to send a virtual item package with the selected virtual item package cover to the recipient.
[0006] In the aforementioned related technologies, candidate virtual item pack covers are displayed in the virtual item pack sending interface, which can only be updated when the application is updated. Therefore, candidate virtual item pack covers can only be configured and updated when the application is updated, resulting in the inability to flexibly configure and update the virtual item pack covers available for user selection. Summary of the Invention
[0007] This application provides a method, apparatus, device, and storage medium for sending virtual item packages, which can be used to solve the technical problem in related technologies where the virtual item package cover selected by the user cannot be flexibly configured and updated. The technical solution is as follows:
[0008] On one hand, embodiments of this application provide a method for sending virtual item packages, the method comprising:
[0009] Display the virtual item pack sending interface;
[0010] Obtain the virtual item package parameters entered in the virtual item package sending interface; the virtual item package parameters are used to generate the virtual item package.
[0011] After receiving the instruction to send a virtual item package, a payment interface is displayed, which includes at least one candidate virtual item package cover.
[0012] Obtain the selection instruction for the target cover corresponding to the at least one candidate virtual item package cover;
[0013] After receiving the payment confirmation instruction, an item package message is displayed in the chat session interface with the recipient. The item package message is used to claim the virtual item package with the target cover.
[0014] On the other hand, embodiments of this application provide a method for sending virtual item packages, applied to a server, the method comprising:
[0015] Receive a virtual item package sending request sent by a sending client. The virtual item package sending request includes virtual item package parameters and recipient information. The virtual item package parameters are used to generate a virtual item package.
[0016] Based on the request sent for the virtual item package, order information for the virtual item package is generated;
[0017] Send the order information to the sending client;
[0018] Receive a payment request sent by the sending client, the payment request including identification information of a target cover selected from at least one candidate virtual item package cover displayed on the payment interface;
[0019] Execute the payment process according to the payment request;
[0020] After the payment process is successfully executed, an item package message is sent to at least one receiving client based on the recipient information. The item package message is used to claim the virtual item package with the target cover.
[0021] On the other hand, embodiments of this application provide a virtual item package delivery device, the device comprising:
[0022] The sending interface display module is used to display the virtual item package sending interface;
[0023] The item parameter acquisition module is used to acquire the virtual item package parameters input in the virtual item package sending interface, and the virtual item package parameters are used to generate the virtual item package;
[0024] The payment interface display module is used to display the payment interface after receiving the virtual item package sending instruction, wherein the payment interface includes at least one candidate virtual item package cover;
[0025] The selection instruction acquisition module is used to acquire the selection instruction corresponding to the target cover in the at least one candidate virtual item package cover;
[0026] The item message display module is used to display an item package message in the chat session interface with the recipient after receiving a payment confirmation instruction. The item package message is used to claim the virtual item package with the target cover.
[0027] Optionally, the payment interface display module includes:
[0028] A request sending unit is used to send a virtual item package sending request to the server. The virtual item package sending request includes virtual item package parameters and recipient information.
[0029] An order information receiving unit is used to receive order information of the virtual item package sent by the server, wherein the order information includes an order identifier and an order type;
[0030] The payment interface display unit is used to display the payment interface based on the order information.
[0031] Optionally, the order information receiving unit is used for:
[0032] Obtain a payment interface template corresponding to the order type. The payment interface template includes a virtual item package cover configuration field, which is used to configure the virtual item package cover.
[0033] The payment interface is displayed according to the payment interface template.
[0034] Optionally, the sending request sending unit is configured to:
[0035] The virtual item package is sent to the virtual item package server, which is used to send an order generation request to the payment server. The order generation request includes the virtual item package parameters, and the payment server is used to generate the order information according to the order generation request.
[0036] The order information receiving unit is used to receive the order information of the virtual item package sent by the payment server.
[0037] Optionally, the item message display module is used for:
[0038] Send a payment request to the server, the payment request including the identification information of the target cover; receive payment success information sent by the server;
[0039] Based on the payment success information, the item package message is displayed in the chat session interface with the recipient.
[0040] Optionally, the device further includes:
[0041] The selection record storage module is used to store the cover selection history, which is used to indicate that the selected virtual item package cover is the target cover.
[0042] The cover status setting module is used to set the target cover as the default selection state in the payment interface the next time the payment interface is displayed, based on the cover selection history.
[0043] On the other hand, embodiments of this application provide a virtual item package delivery device, the device comprising:
[0044] The sending request receiving module is used to receive a virtual item package sending request sent by the sending client. The virtual item package sending request includes virtual item package parameters and recipient information. The virtual item package parameters are used to generate a virtual item package.
[0045] The order information generation module is used to generate order information for the virtual item package based on the request sent by the virtual item package.
[0046] The order information sending module is used to send the order information to the sending client;
[0047] A payment request receiving module is used to receive a payment request sent by the sending client, wherein the payment request includes identification information of a target cover selected from at least one candidate virtual item package cover displayed on the payment interface;
[0048] The payment process execution module is used to execute the payment process according to the payment request;
[0049] The item message sending module is used to send an item package message to at least one receiving client based on the recipient information after the payment process is successfully executed. The item package message is used to claim the virtual item package with the target cover.
[0050] Optionally, the server includes a virtual item package server and a payment server.
[0051] The virtual item package server is configured to send an order generation request to the payment server based on the virtual item package sending request, wherein the order generation request includes the virtual item package parameters;
[0052] The payment server is used to generate the order information based on the order generation request.
[0053] Optionally, the payment server is configured to send payment success information to the virtual item package server after the payment process is successfully executed, the payment success information including the identification information of the target cover;
[0054] The virtual item package server is configured to send an item package message generation request to the message sending and receiving server after receiving the payment success information. The item package message generation request includes the order information and the recipient information.
[0055] Optionally, the payment server is configured to send a first payment success message to the virtual server synchronously and a second payment success message to the virtual server asynchronously; wherein the first payment success message and the second payment success message contain the identification information of the target cover.
[0056] In some possible designs, the device further includes:
[0057] An information storage module is used to store the relevant information of the virtual item package into the blockchain of the blockchain system. The blockchain system includes n blockchain nodes, and each blockchain node is configured with the blockchain, where n is an integer greater than 1.
[0058] The information related to the virtual item package includes at least one of the following: virtual item package parameters, recipient information, order information, candidate virtual item package covers, and identification information of the target cover.
[0059] In another aspect, embodiments of this application provide a computer device, the computer device including a processor and a memory, the memory storing at least one instruction, at least one program, code set or instruction set, the at least one instruction, the at least one program, the code set or instruction set being loaded and executed by the processor to implement the virtual item package sending method as described above.
[0060] Optionally, the computer device is a terminal or a server.
[0061] In another aspect, embodiments of this application provide a computer-readable storage medium storing at least one instruction, at least one program, code set, or instruction set, wherein the at least one instruction, the at least one program, the code set, or the instruction set is loaded and executed by a processor to implement the virtual item package sending method as described above.
[0062] In another aspect, embodiments of this application provide a computer program product, which, when executed by a processor, is used to implement the above-described virtual item package sending method.
[0063] The technical solutions provided in this application embodiment may have the following beneficial effects:
[0064] This invention displays candidate virtual item bundle covers in the payment interface and, upon receiving a payment confirmation instruction, displays an item bundle message in the chat session with the recipient. This item bundle message is used to claim the virtual item bundle with the target cover. In contrast, related technologies display candidate virtual item bundle covers in the virtual item bundle sending interface, which is the application's native interface and can only be updated when the application is updated. The technical solution provided in this application displays candidate virtual item bundle covers in the payment interface. Since this payment interface is a webpage, the content displayed in it can be configured each time the server issues an instruction to display the payment interface. Therefore, the payment interface can be configured and updated in the background, and then the updated content is presented on the client. This allows users to flexibly configure and update the virtual item bundle covers they choose without updating the application. Attached Figure Description
[0065] Figure 1 This is a schematic diagram of an implementation environment provided in one embodiment of this application;
[0066] Figure 2 This is a schematic diagram of an implementation environment provided in another embodiment of this application;
[0067] Figure 3This is a flowchart of a virtual item package sending method provided in one embodiment of this application;
[0068] Figure 4 An exemplary schematic diagram of a virtual item package sending interface according to this application is shown;
[0069] Figure 5 A schematic diagram of a payment interface according to this application is shown as an example;
[0070] Figure 6 An exemplary diagram illustrating an item package message display according to this application is shown;
[0071] Figure 7 This is a flowchart of a virtual item package sending method provided in another embodiment of this application;
[0072] Figure 8 This is a flowchart of a virtual item package sending method provided in another embodiment of this application;
[0073] Figure 9 An exemplary diagram illustrating the virtual item package redemption process of this application is shown;
[0074] Figure 10 This is a schematic diagram of a blockchain system provided in one embodiment of this application;
[0075] Figure 11 This is an optional schematic diagram of a block structure provided in one embodiment of this application;
[0076] Figure 12 This is a schematic diagram of a system architecture provided in one embodiment of this application;
[0077] Figure 13 This is a block diagram of a virtual item package sending device provided in one embodiment of this application;
[0078] Figure 14 This is a block diagram of a virtual item package sending device provided in another embodiment of this application;
[0079] Figure 15 This is a block diagram of a virtual item package sending device provided in another embodiment of this application;
[0080] Figure 16 This is a block diagram of a virtual item package sending device provided in another embodiment of this application;
[0081] Figure 17 This is a structural block diagram of a terminal provided in one embodiment of this application;
[0082] Figure 18 This is a schematic diagram of the structure of a server provided in one embodiment of this application. Detailed Implementation
[0083] To make the objectives, technical solutions, and advantages of this application clearer, the embodiments of this application will be described in further detail below with reference to the accompanying drawings.
[0084] Please refer to Figure 1 The diagram illustrates an implementation environment provided in one embodiment of this application. This implementation environment may include: a sending terminal 10, a receiving terminal 20, and a server 30.
[0085] In this embodiment of the application, the sending terminal 10 is equipped with a sending client and the receiving terminal 20 is equipped with a receiving client.
[0086] In this embodiment, the sending client and receiving client can be any client capable of sending and receiving virtual item packages. For example, they can be clients of instant messaging applications, social applications, payment applications, clients specifically designed for sending virtual item packages, and so on.
[0087] The sending client and the receiving client can be clients of the same application. For example, the sending client and the receiving client can be clients of the same instant messaging application. For instance, both the sending client and the receiving client are clients of the "X-Message" application. The sending client and the receiving client can be APP (Application) clients installed on a terminal, which can be an electronic device such as a mobile phone, tablet, wearable device, or PC (Personal Computer).
[0088] Server 30 can be a single server, a server cluster consisting of multiple servers, or a cloud computing service center. Server 30 can relay messages sent and received between sending terminal 10 and receiving terminal 20 via wired or wireless networks.
[0089] Optionally, such as Figure 2 As shown, when server 30 is a server cluster consisting of multiple servers, server 30 may include a virtual item package server 31, a payment server 32, and a message transceiver server 33. The virtual item package server 31 is used to perform steps related to virtual item packages; the payment server 32 is used to process fund transfers between accounts; and the message transceiver server 33 allows users to send or receive item package messages. The virtual item package server 31 and the payment server 32 can communicate via a wired network, and the virtual item package server 31 and the message transceiver server 33 can also communicate via a wired network.
[0090] In this embodiment, the virtual item package can also be called a virtual red envelope or electronic red envelope. A virtual item package is a virtual carrier for transferring resources (or virtual items) between at least two users in the form of a gift. These at least two users may or may not be friends in the client and / or real world. The resources (or virtual items) involved in the virtual item package can be currency, game equipment, game materials, game pets, game coins, icons, memberships, titles, value-added services, points, gold coins, gold beans, gift certificates, vouchers, coupons, greeting cards, etc. This embodiment does not limit the type of resources.
[0091] The technical solution of this application will be described and illustrated below through several embodiments.
[0092] Please refer to Figure 3 The document illustrates a flowchart of a virtual item package sending method according to an embodiment of this application. In this embodiment, the method is primarily applied to... Figure 1 The following example illustrates the method using a sending client installed and running on the sending terminal in the implementation environment shown. The method may include the following steps:
[0093] Step 301: Display the virtual item pack sending interface.
[0094] Users can run the aforementioned sending client to display the virtual item pack sending interface. The virtual item pack sending interface includes a virtual item pack parameter input field for users to input virtual item pack parameters; a greeting input field for users to input greetings; and a virtual item pack sending control for users to trigger the sending of the virtual item pack.
[0095] For example, in conjunction with the reference Figure 4 The example illustrates a schematic diagram of a virtual item package sending interface. Assume that a "red envelope" is used as the medium for gifting currency. The virtual item package sending interface 40 includes a virtual item package parameter input field 41, a greeting input field 42, and a virtual item package sending control 43.
[0096] Optionally, before displaying the virtual item package sending interface, the client displays a chat interface, which can be a one-on-one chat interface or a group chat interface; after receiving a trigger signal corresponding to the menu control in the chat interface, a function menu is displayed, which includes operation controls for sending virtual item packages; after receiving a trigger signal corresponding to the operation control, the virtual item package sending interface is displayed.
[0097] Step 302: Obtain the virtual item package parameters entered in the virtual item package sending interface.
[0098] The user enters virtual item package parameters in the parameter input field of the virtual item package sending interface, and the client retrieves these parameters accordingly. These virtual item package parameters are used to generate the virtual item package.
[0099] The above virtual item package parameters include the following possible implementations:
[0100] (1) When sending a virtual item package to a single receiving client (receiving client), the virtual item package parameters include a fixed number of virtual items in the virtual item package;
[0101] (2) When sending virtual item packages to multiple receiving clients respectively, the virtual item package parameters include the total number of virtual items or the fixed number of virtual items in each virtual item package, and optionally also the number of virtual item packages;
[0102] (3) When sending a virtual item package to at least one receiving client belonging to the same group, the virtual item package parameter includes the total number of virtual items or a fixed number of virtual items in each virtual item package, and optionally also includes the number of virtual item packages;
[0103] The total number of virtual items in (2) and (3) above is used to generate the number of virtual items in each virtual item package either by averaging or by randomizing.
[0104] Step 303: After receiving the instruction to send the virtual item package, the payment interface is displayed.
[0105] Users can click the virtual item pack sending control in the aforementioned virtual item pack sending interface to generate a virtual item pack sending command. Correspondingly, after receiving the aforementioned virtual item pack sending command, the client displays the payment interface.
[0106] The payment interface includes at least one candidate virtual item package cover. The virtual item package cover is similar to the envelope of a physical red envelope, allowing the sender to choose a suitable cover based on their needs.
[0107] Optionally, the payment interface may also include a payment method selection bar for users to choose a payment method. The payment method selection bar may include at least two payment methods for users to choose from.
[0108] Optionally, the payment interface may also include a payment confirmation control for users to confirm payment.
[0109] For example, such as Figure 5 As shown, this example illustrates a schematic diagram of a payment interface. The payment interface 50 includes at least one candidate virtual item package cover 51, a payment method selection bar 52, and a payment confirmation control 53.
[0110] Step 304: Obtain the selection instruction for the target cover corresponding to at least one candidate virtual item package cover.
[0111] The sending user can select a cover from at least one of the above-mentioned candidate virtual item package covers, i.e., the target cover. Correspondingly, the sending client can obtain the above-mentioned selection instruction corresponding to the target cover.
[0112] Optionally, there can be multiple target covers. The sender can select multiple target covers from at least one of the candidate virtual item package covers. In this case, the cover of the red envelope received by the recipient can be any one of the multiple target covers. For example, when the sender sends three virtual item packages to a group, and the sender selects two target covers (such as target cover A and target cover B) from the candidate virtual item package covers, the cover of the three virtual item packages can be randomly determined from target cover A and target cover B. For example, the virtual item package received by recipient A in the group has target cover A, the virtual item package received by recipient B in the group has target cover A, and the virtual item package received by recipient C in the group has target cover B.
[0113] Step 305: After receiving the payment confirmation instruction, display the item package message in the chat session with the recipient.
[0114] The payment interface also includes a payment confirmation control for users to confirm their payment. When a user clicks this control, a payment confirmation instruction is generated. The sending client can then receive this instruction and, upon receiving it, displays an item package message in the chat session with the recipient. This item package message is used to claim a virtual item package with the target cover.
[0115] For example, such as Figure 6 As shown, it exemplarily illustrates a schematic diagram of an item package message display. After receiving the above confirmation instruction, the item package message 61 is displayed in the chat session interface 60 with the recipient.
[0116] In summary, the technical solution provided in this application displays candidate virtual item package covers in the payment interface and, after receiving a payment confirmation instruction, displays an item package message in the chat session with the recipient. This item package message is used to claim the virtual item package with the target cover. Compared to related technologies where candidate virtual item package covers are displayed in the virtual item package sending interface, which is the application's native interface and can only be updated when the application is updated, the technical solution provided in this application displays candidate virtual item package covers in the payment interface. Since this payment interface is a webpage, the content displayed in it can be configured each time the server issues an instruction to display the payment interface. Therefore, the payment interface can be configured and updated in the background, and then the updated content is presented on the client. This allows users to flexibly configure and update the virtual item package covers they choose without updating the application.
[0117] Please refer to Figure 7 The diagram illustrates a flowchart of a virtual item package sending method provided in another embodiment of this application. In this embodiment, the method is mainly applied to... Figure 1 The following example illustrates the implementation environment. The method may include the following steps:
[0118] Step 701: The client displays the virtual item pack sending interface.
[0119] This step and Figure 3 Step 301 in the embodiments is the same or similar, and will not be repeated here.
[0120] Step 702: Send the client to obtain the virtual item package parameters entered in the virtual item package sending interface.
[0121] The virtual item pack parameter is used to generate virtual item packs.
[0122] This step and Figure 3 Step 302 in the embodiments is the same or similar, and will not be repeated here.
[0123] Step 703: After receiving the virtual item package sending instruction, the sending client sends a virtual item package sending request to the server.
[0124] Users can click the virtual item pack sending control in the virtual item pack sending interface to generate a virtual item pack sending command. After receiving the virtual item pack sending command, the client sends a virtual item pack sending request to the server. This virtual item pack sending request is used to request the sending of the virtual item pack.
[0125] The virtual item package sending request mentioned above includes virtual item package parameters and recipient information. For details regarding the virtual item package parameters, please refer to [link to relevant documentation]. Figure 3 The details of the embodiments will not be repeated here.
[0126] Recipient information is used to indicate the recipient user of the virtual item package. For example, recipient information can be the identifier of the recipient client (e.g., the user account corresponding to the recipient client), the group identifier of the group to which the recipient client belongs, or the conditions set by the recipient user for the recipient client. For example, the condition could be the recipient client corresponding to a recipient user in Guangzhou aged 20 to 30.
[0127] Correspondingly, the server receives the virtual item package sending request sent by the client.
[0128] Step 704: The server sends a request for the virtual item package and generates order information for the virtual item package.
[0129] After receiving the virtual item package sending request, the server can generate order information for the virtual item package based on the virtual item package parameters and recipient information contained in the sending request.
[0130] The order information above includes an order identifier and an order type. The order identifier identifies the payment order; for example, it could be the order number. The order type indicates the type of service the order belongs to; for example, it could be a virtual item package, a top-up, or a transfer. Additionally, the order information may also include the order amount.
[0131] Step 705: The server sends the order information to the sending client.
[0132] Correspondingly, the sending client receives the order information for the virtual item package sent by the server.
[0133] Step 706: Send the client to display the payment interface based on the order information.
[0134] After receiving the order information, the sending client can display a payment interface based on that information. This payment interface includes at least one candidate virtual item bundle cover. When there are two or more candidate virtual item bundle covers, each cover must be different.
[0135] For example, the virtual item bundle covers can be of different colors. For instance, the cover could be green, red, purple, etc. Since different countries have different preferences for colors, when promoting the application to other countries, providing multiple candidate virtual item bundle covers of different colors can meet the needs of users in different countries, making the virtual item bundle more human-centered, enhancing the product's appeal, and making the application more international.
[0136] Optionally, displaying the payment interface based on the order information includes the following steps:
[0137] (1) Obtain the payment interface template corresponding to the order type.
[0138] Different payment interface templates are pre-set and stored in the server for different order types, enabling the customization of the payment interface.
[0139] When the server receives a virtual item package sending request from the sending client, it can determine that the order type is a virtual item package and send the order type to the sending client. After receiving the order type from the order information, the sending client requests a template from the server to obtain the payment interface template corresponding to the order type. After receiving the template request, the server sends the payment interface template corresponding to the order type to the sending client.
[0140] When the payment type is virtual item bundle, the payment interface template includes a virtual item bundle cover configuration section, which is used to configure the virtual item bundle cover.
[0141] (2) Display the payment interface according to the payment interface template.
[0142] After obtaining the above payment interface template, you can also combine it with the order amount in the order information to form the above payment interface.
[0143] Step 707: Send a selection instruction to the client to obtain the target cover corresponding to at least one candidate virtual item package cover.
[0144] Users can select one cover from at least one of the above candidate virtual item package covers, i.e., the target cover. Correspondingly, the client can obtain the selection instruction corresponding to the target cover.
[0145] Optionally, after obtaining the selection instruction for the target cover corresponding to at least one candidate virtual item package cover, the following steps are further included:
[0146] (1) Save cover selection history.
[0147] The above cover selection history is used to indicate the selected virtual item package cover as the target cover.
[0148] Optionally, the cover selection history can be stored in a cookie to achieve a cover memory function.
[0149] Storing data in cookies can be temporary. In this case, the cover can be set to save history for a specified period (e.g., 30 days). If the specified period is exceeded, the history will be cleared.
[0150] (2) Based on the cover selection history, when the payment interface is displayed again, the target cover will be set as the default selection state in the payment interface.
[0151] By saving the cover selection history, the next time the payment interface is displayed, the cover selected by the user when the last virtual item package was sent will be selected by default, making it more convenient for the user.
[0152] Additionally, the server can choose to store the cover selection history in the sender's user information table, or it can create a new record table to store this cover selection history. When the sender sends a virtual item package again, the server can call the aforementioned user information table or the newly created record table to know the target cover selected by the sender before sending the virtual item package, ensuring the accuracy of the virtual item package cover memory function.
[0153] Step 708: After receiving the payment confirmation instruction, the client sends a payment request to the server.
[0154] The payment interface also includes a payment confirmation control for users to confirm their payment. When a user clicks the payment confirmation control, a payment confirmation instruction is generated; correspondingly, the sending client can receive the payment confirmation instruction and, upon receiving it, send a payment request to the server.
[0155] The payment request described above is used to request the server to make the payment. The payment request includes an order identifier and the target cover's identification information. The order identifier has already been explained above and will not be repeated here; the target cover's identification information is used to uniquely identify the target cover.
[0156] Correspondingly, the server receives the payment request sent by the client.
[0157] Step 709: The server executes the payment process based on the payment request.
[0158] After receiving the payment request, the server can execute the payment process based on the payment request.
[0159] The server can transfer virtual resources from the recipient user's payment account to the recipient user's payment account. After the transfer is successful, the payment process is executed successfully.
[0160] Step 710: After the payment process is successfully executed, the server sends a payment success message to the sending client.
[0161] The aforementioned payment success message indicates that the payment request was successfully completed. Correspondingly, the sending client receives the payment success message from the server.
[0162] Optionally, after the payment process fails, a payment failure message can be sent to the sending client to indicate that the payment request failed. In this case, details of the payment failure can also be displayed.
[0163] Step 711: The sending client displays the item package message in the chat session interface with the recipient based on the payment success information.
[0164] After receiving the payment success information, the sending client can also display an item package message based on the payment success information. This item package message is used to claim a virtual item package with the target cover.
[0165] Step 712: After the payment process is successfully executed, the server sends an item package message to at least one receiving client based on the recipient information.
[0166] The server can determine the recipient of the virtual item pack based on the recipient information and send the item pack message to that recipient.
[0167] When the recipient information is a user account, the server sends an item package message to the recipient client corresponding to that user account. The aforementioned user account can be a single user account or multiple user accounts.
[0168] When the recipient information is a group identifier, the server sends an item package message to the recipient client within the group indicated by the group identifier.
[0169] It should be noted that there is no restriction on the execution order of steps 710-711 and step 712 above.
[0170] In summary, the technical solution provided in this application displays candidate virtual item package covers in the payment interface and, after receiving a payment confirmation instruction, displays an item package message in the chat session with the recipient. This item package message is used to claim the virtual item package with the target cover. Compared to related technologies where candidate virtual item package covers are displayed in the virtual item package sending interface, which is the application's native interface and can only be updated when the application is updated, the technical solution provided in this application displays candidate virtual item package covers in the payment interface. Since this payment interface is a webpage, the content displayed in it can be configured each time the server issues an instruction to display the payment interface. Therefore, the payment interface can be configured and updated in the background, and then the updated content is presented on the client. This allows users to flexibly configure and update the virtual item package covers they choose without updating the application.
[0171] In addition, by providing multiple different candidate virtual item pack covers, the needs of more users can be met, thus enhancing the product's appeal.
[0172] In addition, different payment interface templates are pre-set and stored in the server for different order types, enabling the customization of the payment interface.
[0173] In addition, by saving the cover selection history, the next time the payment interface is displayed, the cover selected by the user when sending the virtual item package will be selected by default, which makes it more convenient for users.
[0174] Please refer to Figure 8 The diagram illustrates a flowchart of a virtual item package sending method according to another embodiment of this application. In this embodiment, the method is mainly applied to... Figure 2 The following example illustrates the implementation environment. The method may include the following steps:
[0175] Step 801: The client displays the virtual item pack sending interface.
[0176] This step and Figure 3 Step 301 in the embodiments is the same or similar, and will not be repeated here.
[0177] Step 802: Send the client to obtain the virtual item package parameters entered in the virtual item package sending interface.
[0178] The virtual item pack parameter is used to generate virtual item packs.
[0179] This step and Figure 3 Step 302 in the embodiments is the same or similar, and will not be repeated here.
[0180] Step 803: After receiving the virtual item package sending instruction, the sending client sends a virtual item package sending request to the virtual item package server.
[0181] Step 804: The virtual item package server sends an order generation request to the payment server based on the virtual item package request.
[0182] The order generation request includes virtual item package parameters.
[0183] Step 805: The payment server generates order information based on the order generation request.
[0184] Step 806: The payment server sends the order information to the sending client.
[0185] Correspondingly, the sending client receives the order information for the virtual item package sent by the payment server.
[0186] Step 807: Send the client to display the payment interface based on the order information.
[0187] Step 808: Send a selection instruction to the client to obtain the target cover corresponding to at least one candidate virtual item package cover.
[0188] Step 809: After receiving the payment confirmation instruction, the sending client sends a payment request to the payment server.
[0189] Correspondingly, the payment server receives the payment request sent by the client.
[0190] Step 810: After the payment process is successfully executed, the payment server sends a payment success message to the virtual item package server.
[0191] The payment success message includes the identification information of the target cover.
[0192] Optionally, the payment server sends payment success information to the virtual item package server, including the following steps:
[0193] (1) The payment server sends the first payment success information to the virtual server in a synchronous manner.
[0194] (2) The payment server sends the second payment success information to the virtual server asynchronously.
[0195] The aforementioned synchronous payment refers to the virtual server immediately sending a first payment success message to the virtual server upon receiving a payment request from the sending client; the aforementioned asynchronous payment refers to the virtual server sending a second payment success message to the virtual server at predetermined intervals. Both the first and second payment success messages contain the identifier information of the target envelope.
[0196] The payment server sends payment success information to the virtual server through both synchronous and asynchronous methods, which can ensure the accuracy and success rate of payment information transmission.
[0197] Step 811: After receiving the payment success information, the virtual item package server sends an item package message generation request to the message sending and receiving server.
[0198] The Item Package Message Generation Request is used to request the message sending and receiving server to generate an item package message. The item package message generation request includes order information and recipient information.
[0199] Step 812: The message sending and receiving server sends an item package message to at least one receiving client based on the recipient information.
[0200] The item pack message is used to claim an item pack with a target cover. The item pack message can include an item pack message bubble.
[0201] Step 813: The receiving client displays an item pack message bubble in the chat session interface with the sender.
[0202] After receiving the above item pack message, the receiving client can display the item pack message bubble in the chat session interface with the sender.
[0203] Optionally, the aforementioned item package message bubble includes content elements used to represent the target cover.
[0204] Step 814: When the receiving client receives the operation signal corresponding to the item pack message bubble, it sends a virtual item pack information retrieval request to the virtual item pack server.
[0205] The aforementioned virtual item pack information retrieval request is used to request relevant information about virtual item packs.
[0206] Step 815: The virtual item pack server sends relevant information about the virtual item pack to the receiving client based on the virtual item pack information retrieval request.
[0207] The information related to the aforementioned virtual item pack may include virtual item pack parameters and target cover.
[0208] Step 816: The receiving client displays the virtual item pack redemption interface.
[0209] The virtual item pack redemption interface includes a greeting message, a target cover, and a control for redeeming the virtual item pack.
[0210] Optionally, when the receiving client receives an operation signal corresponding to the virtual item pack claiming control, it displays the virtual item pack details interface. This interface includes a greeting message, target cover elements, and virtual item pack parameters.
[0211] For example, in conjunction with the reference Figure 9 The example illustrates a schematic diagram of the virtual item pack redemption process, assuming that "red envelopes" are used as the medium for gifting currency. The receiving client displays an item pack message bubble in the chat session interface with the sender; the user clicks on the item pack message bubble to display the virtual item pack redemption interface 90, which includes a virtual item pack redemption control 91. After the user clicks on the virtual item pack redemption control 91, the virtual item pack details interface 92 is displayed.
[0212] In summary, the technical solution provided in this application displays candidate virtual item package covers in the payment interface and, after receiving a payment confirmation instruction, displays an item package message in the chat session with the recipient. This item package message is used to claim the virtual item package with the target cover. Compared to related technologies where candidate virtual item package covers are displayed in the virtual item package sending interface, which is the application's native interface and can only be updated when the application is updated, the technical solution provided in this application displays candidate virtual item package covers in the payment interface. Since this payment interface is a webpage, the content displayed in it can be configured each time the server issues an instruction to display the payment interface. Therefore, the payment interface can be configured and updated in the background, and then the updated content is presented on the client. This allows users to flexibly configure and update the virtual item package covers they choose without updating the application.
[0213] On the other hand, since different countries have different preferences for colors, when the application corresponding to the client is promoted to other countries, providing multiple candidate virtual item package covers of different colors can meet the needs of users in different countries, making the virtual item package more humanistic, enhancing the product's warmth, and making the application more international.
[0214] Based on the above Figure 7 In one alternative embodiment provided by the examples, the server may also perform the following steps:
[0215] The relevant information of the virtual item package is stored in the blockchain of the blockchain system.
[0216] The aforementioned blockchain system comprises n blockchain nodes, each configured with a blockchain, where n is an integer greater than 1. For a detailed introduction to the blockchain system, blockchain, and blockchain nodes, please refer to the following example; further details will not be provided here.
[0217] The information related to the virtual item package includes at least one of the following: virtual item package parameters, recipient information, order information, and identification information of the candidate virtual item package cover and the target cover. Furthermore, the aforementioned information related to the virtual item package may also include the total number of virtual items, the number of virtual items in each virtual item package, payment interface template, payment success information, and other information, but this application embodiment does not limit this.
[0218] Because data in a blockchain is immutable, storing information about virtual item packs in the blockchain system can guarantee the authenticity and credibility of the recorded information.
[0219] Optionally, after the sending client successfully completes payment for the order, it stores the order information and virtual item package parameters on the blockchain. At the same time, the server stores the quantity of virtual items in each virtual item package corresponding to the order on the blockchain. Subsequently, when the sending client needs to query the virtual item package sending record and / or the receiving client needs to query the virtual item package receiving record, the sending client and / or the receiving client can directly query the virtual item package record corresponding to the order (using the order number) from the blockchain to know the quantity of virtual items in the virtual item package actually sent by the sending client and the quantity of virtual items in the virtual item package actually generated by the server, thus preventing the server from stealing virtual items.
[0220] For example, suppose we use "red envelopes" as the medium for gifting currency. After a customer successfully completes payment for an order, the order information (including the order number) and the amount of currency in the red envelope are stored on the blockchain. At the same time, the server stores the amount of currency in each red envelope corresponding to that order on the blockchain. Later, when the sender wants to query the red envelope sending record and / or the receiver wants to query the red envelope receiving record, the sending client and / or receiving client can directly use the order number to query the red envelope record corresponding to that order from the blockchain, so as to know the amount of currency actually sent by the sender and the amount of currency actually sent by the server to the receiver. This can prevent the server from secretly manipulating and stealing the currency sent by the sender.
[0221] The following section describes the blockchain technology involved in the embodiments of this application.
[0222] A blockchain system is a data-sharing system, that is, a system used for data sharing between nodes. Please refer to [link / reference]. Figure 10 This illustration shows a schematic diagram of a blockchain system 100 provided in one embodiment of this application. Figure 1 As shown, the blockchain system 100 may include multiple nodes 101 (also called "blockchain nodes"). Each node 101, in its normal operation, can receive input information and maintain shared data within the blockchain system 100 based on the received input information. To ensure information interoperability within the blockchain system 100, each node 101 in the blockchain system 100 may have direct or indirect information connections, and information can be transmitted between nodes 101 through these connections. For example, when any node in the blockchain system 100 receives input information, other nodes in the blockchain system 100 obtain the input information according to the consensus algorithm and store it as data in the shared data, ensuring that the data stored on all nodes in the blockchain system 100 is consistent.
[0223] Each node 101 in the blockchain system 100 has a corresponding node identifier. Furthermore, each node 101 in the blockchain system 100 can store the node identifiers of other nodes in the blockchain system 100, so that the generated block can be broadcast to other nodes in the blockchain system based on their node identifiers. Each node can maintain a node identifier list as shown in the table below, storing the node name and node identifier in this list. The node identifier can be an IP (Internet Protocol) address or any other information that can be used to identify the node. Table 1 only uses IP addresses as an example.
[0224] Table 1
[0225] Node Name Node identifier Node 1 117.114.151.174 Node 2 117.116.189.145 ... ... Node N 119.123.789.258
[0226] Each node 101 in the blockchain system 100 stores the same blockchain.
[0227] Please refer to Figure 11 This illustrates an optional schematic diagram of a block structure provided in one embodiment of this application. For example... Figure 11As shown, a blockchain consists of multiple blocks. Blockchain 200 consists of multiple blocks 201. The genesis block includes a block header and a block body. The block header stores the input information feature value, version number, timestamp, and difficulty value. The block body stores the input information. The next block after the genesis block takes the genesis block as its parent block. The next block also includes a block header and a block body. The block header stores the input information feature value of the current block, the block header feature value of the parent block, the version number, the timestamp, and the difficulty value, and so on. This ensures that the block data stored in each block of the blockchain is related to the block data stored in the parent block, guaranteeing the security of the input information in the blocks.
[0228] When generating each block 201 in blockchain 200, the node containing the blockchain receives input information, verifies the input information, stores the input information in the memory pool after verification, and updates its hash tree used to record the input information. Then, it updates the timestamp to the time the input information was received, and tries different random numbers to calculate the feature value multiple times, ensuring that the calculated feature value satisfies the following formula:
[0229] SHA256(SHA256(version+prev_hash+merkle_root+ntime+nbits+x)) <TARGET
[0230] Wherein, SHA256 is the feature value algorithm used to calculate the feature value; version (version number) is the version information of the relevant block protocol in the blockchain; prev_hash is the block header feature value of the parent block of the current block; merkle_root is the feature value of the input information; ntime is the update time of the update timestamp; nbits is the current difficulty, which is a fixed value for a period of time and is determined again after exceeding the fixed time period; x is a random number; TARGET is the feature value threshold, which can be determined based on nbits.
[0231] Thus, when a random number satisfying the above formula is calculated, the information can be stored accordingly, generating a block header and a block body to obtain the current block. Subsequently, the node containing the blockchain sends the newly generated block to other nodes in its blockchain system based on the node identifiers of other nodes in the blockchain system. The other nodes verify the newly generated block and add it to their stored blockchain after verification.
[0232] Please refer to Figure 12 This illustrates a schematic diagram of a system architecture provided in one embodiment of this application. Figure 12As shown, the system architecture may include: a blockchain system 310, a server 320, and a terminal 330 (including a sending terminal and a receiving terminal).
[0233] The blockchain system 310 includes n blockchain nodes 311, where n is an integer greater than 1. Each blockchain node 311 can be any computer device with data processing and storage capabilities, such as a server or user terminal. The blockchain nodes 311 can communicate directly or indirectly to achieve data sharing and synchronization.
[0234] In this embodiment, each blockchain node 311 is configured with a blockchain 312. A description of the blockchain 312 structure can be found above and will not be repeated here. In this embodiment, the blockchain 312 can be used to store information related to virtual item packages.
[0235] Server 320 can be a backend server for a product, providing backend services for that product. Server 320 can be a single server, a server cluster consisting of multiple servers, or a cloud computing service center. Furthermore, server 320 can establish a network communication connection with at least one blockchain node 311 in the blockchain system 310, thereby enabling data transmission and reception with the blockchain node 311 through this network communication connection. This network can be a wired network or a wireless network.
[0236] Optionally, when server 320 is a server cluster consisting of multiple servers, each server can be connected to the blockchain system 310. These different servers provide different backend services. For example, server 320 may include a virtual item package server, a payment server, and a message sending and receiving server, all of which interface with the blockchain system 310 and can communicate with blockchain nodes 311.
[0237] Terminal 330 can be an electronic device such as a mobile phone, tablet computer, game console, multimedia playback device, wearable device, or PC (Personal Computer). Clients for the aforementioned products can be installed and run on terminal 330.
[0238] Optionally, the sending and receiving terminals can also be connected to a blockchain system to achieve the above. Figure 7 An optional embodiment is provided in the examples.
[0239] The server can send a request to record information related to a virtual item package to the target blockchain node 311. This request is used to request the recording of information related to the virtual item package in the blockchain. After receiving the request, the target blockchain node 311 reaches a consensus with other blockchain nodes 311 in the blockchain system. After obtaining the permission to add a block in the blockchain, the target blockchain node 311 adds a new block (such as the first block) and sends a block addition instruction to other blockchain nodes 311. After receiving the block addition instruction, the other blockchain nodes 311 first reach a consensus on the data in the first block, that is, they agree that the first block should be written into their respective blockchains. After reaching a consensus, the other blockchain nodes add the first block to their respective blockchains. This application embodiment does not limit the specific form of consensus. That is, consensus can be that all nodes in the blockchain system agree to add the data to the blockchain, or that a majority of nodes in the blockchain system agree to add the data to the blockchain, such as more than 51% of the nodes agreeing to add the data to the blockchain.
[0240] In this embodiment, only the server 320 accessing the blockchain system is used as an example for description. In some other embodiments, the server 320 can also be directly used as a node in the blockchain system. This application embodiment does not limit this.
[0241] In addition, in the case where server 320 is a server cluster consisting of multiple servers, the multiple servers can be connected to the blockchain system 310 respectively, or they can be used as nodes in the blockchain system. This application embodiment does not limit this.
[0242] The following are embodiments of the apparatus described in this application, which can be used to execute the embodiments of the method described in this application. For details not disclosed in the apparatus embodiments of this application, please refer to the embodiments of the method described in this application.
[0243] Please refer to Figure 13 This diagram illustrates a block diagram of a virtual item package sending device according to an embodiment of this application. The device has the function of implementing the virtual item package sending method example on the sending client side of the sending terminal described above. This function can be implemented in hardware or by hardware executing corresponding software. The device can be the sending terminal described above, or it can be installed on the sending terminal. The device 1300 may include: a sending interface display module 1313, an item parameter acquisition module 1320, a payment interface display module 1330, a selection instruction acquisition module 1340, and an item message display module 1350.
[0244] The sending interface display module 1313 is used to display the virtual item package sending interface.
[0245] The item parameter acquisition module 1320 is used to acquire the virtual item package parameters input in the virtual item package sending interface, and the virtual item package parameters are used to generate the virtual item package.
[0246] The payment interface display module 1330 is used to display a payment interface after receiving a virtual item package sending instruction, wherein the payment interface includes at least one candidate virtual item package cover.
[0247] The selection instruction acquisition module 1340 is used to acquire the selection instruction corresponding to the target cover in the at least one candidate virtual item package cover.
[0248] The item message display module 1350 is used to display an item package message in the chat session interface with the recipient after receiving a payment confirmation instruction. The item package message is used to claim the virtual item package with the target cover.
[0249] In summary, the technical solution provided in this application displays candidate virtual item package covers in the payment interface and, after receiving a payment confirmation instruction, displays an item package message in the chat session with the recipient. This item package message is used to claim the virtual item package with the target cover. Compared to related technologies where candidate virtual item package covers are displayed in the virtual item package sending interface, which is the application's native interface and can only be updated when the application is updated, the technical solution provided in this application displays candidate virtual item package covers in the payment interface. Since this payment interface is a webpage, the content displayed in it can be configured each time the server issues an instruction to display the payment interface. Therefore, the payment interface can be configured and updated in the background, and then the updated content is presented on the client. This allows users to flexibly configure and update the virtual item package covers they choose without updating the application.
[0250] In some possible designs, such as Figure 14 As shown, the payment interface display module 1330 includes: a request sending unit 1331, an order information receiving unit 1332, and a payment interface display unit 1333.
[0251] The request sending unit 1331 is used to send a virtual item package sending request to the server. The virtual item package sending request includes the virtual item package parameters and the recipient information.
[0252] The order information receiving unit 1332 is used to receive the order information of the virtual item package sent by the server, wherein the order information includes an order identifier and an order type.
[0253] The payment interface display unit 1333 is used to display the payment interface according to the order information.
[0254] In some possible designs, the order information receiving unit 1332 is used to obtain a payment interface template corresponding to the order type. The payment interface template includes a virtual item package cover configuration field, which is used to configure the virtual item package cover. The payment interface is then displayed according to the payment interface template.
[0255] In some possible designs, the sending request sending unit 1331 is used to send the virtual item package sending request to the virtual item package server, the virtual item package server is used to send an order generation request to the payment server, the order generation request includes the virtual item package parameters, and the payment server is used to generate the order information according to the order generation request.
[0256] The order information receiving unit 1332 is used to receive the order information of the virtual item package sent by the payment server.
[0257] In some possible designs, the item message display module 1350 is used to send a payment request to the server, the payment request including the identification information of the target cover; receive payment success information sent by the server; and display the item package message in the chat session interface with the recipient based on the payment success information.
[0258] In some possible designs, such as Figure 14 As shown, the device 1300 further includes: a selection recording and storage module 1360 and a cover status setting module 1370.
[0259] The selection record storage module 1360 is used to store the cover selection history, which is used to indicate that the selected virtual item package cover is the target cover.
[0260] The cover status setting module 1370 is used to set the target cover as the default selection state in the payment interface the next time the payment interface is displayed, based on the cover selection history.
[0261] Please refer to Figure 15This diagram illustrates a block diagram of a virtual item package sending apparatus according to another embodiment of this application. The apparatus has the functionality to implement the above-described server-side virtual item package sending method example. This functionality can be implemented in hardware or by hardware executing corresponding software. The apparatus 1500 can be the server described above, or it can be installed on a server. The apparatus 1500 may include: a sending request receiving module 1510, an order information generation module 1520, an order information sending module 1530, a payment request receiving module 1540, a payment process execution module 1550, and an item message sending module 1560.
[0262] The sending request receiving module 1510 is used to receive a virtual item package sending request sent by a sending client. The virtual item package sending request includes virtual item package parameters and recipient information. The virtual item package parameters are used to generate a virtual item package.
[0263] The order information generation module 1520 is used to generate order information for the virtual item package based on the request sent by the virtual item package.
[0264] The order information sending module 1530 is used to send the order information to the sending client.
[0265] The payment request receiving module 1540 is used to receive a payment request sent by the sending client, wherein the payment request includes identification information of a target cover selected from at least one candidate virtual item package cover displayed on the payment interface.
[0266] The payment process execution module 1550 is used to execute the payment process according to the payment request.
[0267] The item message sending module 1560 is used to send an item package message to at least one receiving client based on the recipient information after the payment process is successfully executed. The item package message is used to claim the virtual item package with the target cover.
[0268] In summary, the technical solution provided in this application displays candidate virtual item package covers in the payment interface and, after receiving a payment confirmation instruction, displays an item package message in the chat session with the recipient. This item package message is used to claim the virtual item package with the target cover. Compared to related technologies where candidate virtual item package covers are displayed in the virtual item package sending interface, which is the application's native interface and can only be updated when the application is updated, the technical solution provided in this application displays candidate virtual item package covers in the payment interface. Since this payment interface is a webpage, the content displayed in it can be configured each time the server issues an instruction to display the payment interface. Therefore, the payment interface can be configured and updated in the background, and then the updated content is presented on the client. This allows users to flexibly configure and update the virtual item package covers they choose without updating the application.
[0269] In some possible designs, the server includes a virtual item package server and a payment server.
[0270] The virtual item package server is used to send an order generation request to the payment server based on the virtual item package sending request, and the order generation request includes the virtual item package parameters.
[0271] The payment server is used to generate the order information based on the order generation request.
[0272] In some possible designs, the payment server is configured to send payment success information to the virtual item package server after the payment process is successfully executed, the payment success information including the identification information of the target cover.
[0273] The virtual item package server is configured to send an item package message generation request to the message sending and receiving server after receiving the payment success information. The item package message generation request includes the order information and the recipient information.
[0274] In some possible designs, the payment server is used to send a first payment success message to the virtual server synchronously and a second payment success message to the virtual server asynchronously; wherein the first payment success message and the second payment success message contain the identification information of the target cover.
[0275] In some possible designs, such as Figure 16 As shown, the device 1500 also includes an information information storage module 1570.
[0276] The relevant information storage module 1570 is used to store the relevant information of the virtual item package into the blockchain of the blockchain system. The blockchain system includes n blockchain nodes, and each blockchain node is configured with the blockchain, where n is an integer greater than 1.
[0277] The information related to the virtual item package includes at least one of the following: virtual item package parameters, recipient information, order information, candidate virtual item package covers, and identification information of the target cover.
[0278] It should be noted that the apparatus provided in the above embodiments is only illustrated by the division of the above functional modules when implementing its functions. In actual applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above. In addition, the apparatus and method embodiments provided in the above embodiments belong to the same concept, and the specific implementation process can be found in the method embodiments, which will not be repeated here.
[0279] Please refer to Figure 17 The diagram illustrates a structural block diagram of a terminal provided in one embodiment of this application. Typically, the terminal 1700 includes a processor 1701 and a memory 1702.
[0280] Processor 1701 may include one or more processing cores, such as a quad-core processor, an octa-core processor, etc. Processor 1701 may be implemented using at least one hardware form selected from DSP (Digital Signal Processing), FPGA (Field Programmable Gate Array), and PLA (Programmable Logic Array). Processor 1701 may also include a main processor and a coprocessor. The main processor, also known as a CPU (Central Processing Unit), is used to process data in the wake-up state; the coprocessor is a low-power processor used to process data in the standby state. In some embodiments, processor 1701 may integrate a GPU (Graphics Processing Unit), which is responsible for rendering and drawing the content to be displayed on the screen. In some embodiments, processor 1701 may also include an AI (Artificial Intelligence) processor, which is used to handle computational operations related to machine learning.
[0281] The memory 1702 may include one or more computer-readable storage media, which may be non-transitory. The memory 1702 may also include high-speed random access memory and non-volatile memory, such as one or more disk storage devices or flash memory devices. In some embodiments, the non-transitory computer-readable storage media in the memory 1702 are used to store at least one instruction, at least one program, code set, or instruction set, which is executed by the processor 1701 to implement the virtual item package sending method on the sending client side provided in the method embodiments of this application.
[0282] In some embodiments, the terminal 1700 may optionally include a peripheral device interface 1703 and at least one peripheral device. The processor 1701, memory 1702, and peripheral device interface 1703 can be connected via a bus or signal line. Each peripheral device can be connected to the peripheral device interface 1703 via a bus, signal line, or circuit board. Specifically, the peripheral device may include at least one of a communication interface 1704, a display screen 1705, an audio circuit 1706, a camera assembly 1707, a positioning assembly 1708, and a power supply 1709.
[0283] Those skilled in the art will understand that Figure 17 The structure shown does not constitute a limitation on terminal 1700 and may include more or fewer components than shown, or combine certain components, or use different component arrangements.
[0284] Please refer to Figure 18 This illustrates a schematic diagram of the server structure provided in one embodiment of this application. Specifically:
[0285] The server 1800 includes a CPU (Central Processing Unit) 1801, a system memory 1804 including RAM (Random Access Memory) 1802 and ROM (Read Only Memory) 1803, and a system bus 1805 connecting the system memory 1804 and the central processing unit 1801. The server 1800 also includes a basic I / O (Input / Output) system 1806 that facilitates information transfer between various devices within the computer, and a mass storage device 1807 for storing the operating system 1813, application programs 1814, and other program modules 1815.
[0286] The basic input / output system 1806 includes a display 1808 for displaying information and an input device 1809 for user input, such as a mouse or keyboard. Both the display 1808 and the input device 1809 are connected to the central processing unit 1801 via an input / output controller 1810 connected to the system bus 1805. The basic input / output system 1806 may also include the input / output controller 1810 for receiving and processing input from multiple other devices such as a keyboard, mouse, or electronic stylus. Similarly, the input / output controller 1810 also provides output to a display screen, printer, or other types of output devices.
[0287] The mass storage device 1807 is connected to the central processing unit 1801 via a mass storage controller (not shown) connected to the system bus 1805. The mass storage device 1807 and its associated computer-readable media provide non-volatile storage for the server 1800. That is, the mass storage device 1807 may include computer-readable media (not shown) such as a hard disk or a CD-ROM (Compact Disc Read-Only Memory) drive.
[0288] Without loss of generality, the computer-readable medium may include computer storage media and communication media. Computer storage media include volatile and non-volatile, removable and non-removable media implemented using any method or technology for storing information such as computer-readable instructions, data structures, program modules, or other data. Computer storage media include RAM, ROM, EPROM (Erasable Programmable Read Only Memory), flash memory or other solid-state storage technologies, CD-ROM, DVD or other optical storage, magnetic tape cassettes, magnetic tape, disk storage, or other magnetic storage devices. Of course, those skilled in the art will recognize that the computer storage media are not limited to the above-mentioned types. The system memory 1804 and mass storage device 1807 described above can be collectively referred to as memory.
[0289] According to various embodiments of this application, the server 1800 can also be connected to a remote computer on a network, such as the Internet. That is, the server 1800 can be connected to the network 1812 via the network interface unit 1811 connected to the system bus 1805, or the network interface unit 1811 can be used to connect to other types of networks or remote computer systems (not shown).
[0290] The memory also includes at least one instruction, at least one program, code set, or instruction set, wherein the at least one instruction, at least one program, code set, or instruction set is stored in the memory and configured to be executed by one or more processors to implement the above-described server-side virtual item package sending method.
[0291] In an exemplary embodiment, a computer device is also provided. The computer device may be a terminal or a server. The computer device includes a processor and a memory, the memory storing at least one instruction, at least one program, a code set, or an instruction set. The at least one instruction, the at least one program, the code set, or the instruction set is loaded and executed by the processor to implement the aforementioned method for sending virtual item packages on the client side, or to implement the aforementioned method for sending virtual item packages on the server side.
[0292] In an exemplary embodiment, a computer-readable storage medium is also provided, which stores at least one instruction, at least one program, code set, or instruction set. When executed by a processor, the at least one instruction, the at least one program, the code set, or the instruction set implements the above-described method for sending virtual item packages on the client side, or implements the above-described method for sending virtual item packages on the server side.
[0293] In an exemplary embodiment, a computer program product is also provided, which, when executed by a processor, is used to implement the above-described method for sending virtual item packages on the client side or the above-described method for sending virtual item packages on the server side.
[0294] It should be understood that "multiple" as used in this article refers to two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, or B alone. The character " / " generally indicates that the preceding and following related objects have an "or" relationship.
[0295] The above description is merely an exemplary embodiment of this application and is not intended to limit this application. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the protection scope of this application.
Claims
1. A method for sending virtual item packages, characterized in that, The method includes: Display the virtual item pack sending interface; Obtain the virtual item package parameters entered in the virtual item package sending interface; the virtual item package parameters are used to generate the virtual item package. After receiving the instruction to send a virtual item package, a payment interface is displayed. The payment interface includes at least one candidate virtual item package cover. The at least one candidate virtual item package cover can be updated by updating the payment interface through server configuration without updating the application. The payment interface is a web page. Obtain the selection instruction for the target cover corresponding to the at least one candidate virtual item package cover; After receiving the payment confirmation instruction, an item package message is displayed, which is used to claim the virtual item package with the target cover.
2. The method according to claim 1, characterized in that, The payment display interface includes: Send a virtual item package sending request to the server, the virtual item package sending request including the virtual item package parameters; Receive order information for the virtual item package sent by the server, wherein the order information includes an order identifier and an order type; The payment interface is displayed based on the order information.
3. The method according to claim 2, characterized in that, Displaying the payment interface based on the order information includes: Obtain a payment interface template corresponding to the order type. The payment interface template includes a virtual item package cover configuration field, which is used to configure the virtual item package cover. The payment interface is displayed according to the payment interface template.
4. The method according to claim 2, characterized in that, Sending the virtual item package request to the server includes: The virtual item package is sent to the virtual item package server, which is used to send an order generation request to the payment server. The order generation request includes the virtual item package parameters, and the payment server is used to generate the order information according to the order generation request. The receipt of the order information for the virtual item package sent by the server includes: Receive the order information for the virtual item package sent by the payment server.
5. The method according to claim 1, characterized in that, The message displaying the item package includes: Send a payment request to the server, the payment request including the identification information of the target cover; Receive payment success information sent by the server; Based on the payment success information, the item package message is displayed.
6. The method according to any one of claims 1 to 5, characterized in that, After obtaining the selection instruction corresponding to the target cover in the at least one candidate virtual item package cover, the method further includes: Store the cover selection history, which is used to indicate that the selected virtual item package cover is the target cover; Based on the cover selection history, the target cover will be set as the default selection in the payment interface the next time the payment interface is displayed.
7. A method for sending virtual item packages, characterized in that, The method is executed by the server, and the method includes: Receive a virtual item package sending request sent by a client. The virtual item package sending request includes virtual item package parameters, which are used to generate a virtual item package. Based on the request sent for the virtual item package, order information for the virtual item package is generated; Send the order information to the sending client; The system receives a payment request sent by the sending client. The payment request includes identification information of a target cover selected from at least one candidate virtual item package cover displayed on the payment interface. The at least one candidate virtual item package cover is configured to update the payment interface via the server without requiring an application update. The payment interface is a web page. Execute the payment process according to the payment request; After the payment process is successfully executed, an item package message is generated, which is used to claim the virtual item package with the target cover.
8. The method according to claim 7, characterized in that, The server includes a virtual item package server and a payment server; The step of generating order information for the virtual item package based on the request to send the virtual item package includes: The virtual item package server sends an order generation request to the payment server based on the virtual item package request, and the order generation request includes the virtual item package parameters; The payment server generates the order information based on the order generation request.
9. The method according to claim 8, characterized in that, After executing the payment process according to the payment request, the method further includes: After the payment process is successfully executed, the payment server sends payment success information to the virtual item package server, and the payment success information includes the identification information of the target cover; After receiving the payment success information, the virtual item package server sends an item package message generation request to the message sending and receiving server. The item package message generation request includes the order information.
10. The method according to claim 9, characterized in that, The payment server sends payment success information to the virtual item package server, including: The payment server sends the first payment success information to the virtual item package server synchronously. The payment server sends a second payment success message to the virtual item package server asynchronously. The first payment success information and the second payment success information contain the identification information of the target cover.
11. The method according to any one of claims 7 to 10, characterized in that, The method further includes: The relevant information of the virtual item package is stored in the blockchain of the blockchain system, which includes n blockchain nodes, each of which is configured with the blockchain, and n is an integer greater than 1; The information related to the virtual item package includes at least one of the following: virtual item package parameters, recipient information, order information, candidate virtual item package covers, and identification information of the target cover.
12. The method according to any one of claims 7 to 10, characterized in that, The virtual item package sending request also includes recipient information; the method further includes: The item package message is sent to at least one receiving client based on the recipient information.
13. A virtual item package sending device, characterized in that, The device includes: The sending interface display module is used to display the virtual item package sending interface; The item parameter acquisition module is used to acquire the virtual item package parameters input in the virtual item package sending interface, and the virtual item package parameters are used to generate the virtual item package; The payment interface display module is used to display a payment interface after receiving a virtual item package sending instruction. The payment interface includes at least one candidate virtual item package cover. The at least one candidate virtual item package cover can be updated by updating the payment interface through server configuration without updating the application. The payment interface is a web page. The selection instruction acquisition module is used to acquire the selection instruction corresponding to the target cover in the at least one candidate virtual item package cover; The item message display module is used to display an item package message after receiving a payment confirmation instruction. The item package message is used to claim the virtual item package with the target cover.
14. A virtual item package sending device, characterized in that, The device includes: The sending request receiving module is used to receive a virtual item package sending request sent by the sending client. The virtual item package sending request includes virtual item package parameters, which are used to generate a virtual item package. The order information generation module is used to generate order information for the virtual item package based on the request sent by the virtual item package. The order information sending module is used to send the order information to the sending client; A payment request receiving module is used to receive a payment request sent by the sending client. The payment request includes identification information of a target cover selected from at least one candidate virtual item package cover displayed on the payment interface. The at least one candidate virtual item package cover can be updated by updating the payment interface through server configuration without updating the application. The payment interface is a web page. The payment process execution module is used to execute the payment process according to the payment request; The item message sending module is used to generate an item package message after the payment process is successfully executed. The item package message is used to claim the virtual item package with the target cover.
15. A computer device, characterized in that, The computer device includes a processor and a memory, the memory storing at least one program, the at least one program being loaded and executed by the processor to implement the method as claimed in any one of claims 1 to 6, or the method as claimed in any one of claims 7 to 12.
16. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores at least one program, which is loaded and executed by a processor to implement the method as claimed in any one of claims 1 to 6, or the method as claimed in any one of claims 7 to 12.
17. A computer program product, characterized in that, The computer program product is executed by a processor to implement the method as claimed in any one of claims 1 to 6, or the method as claimed in any one of claims 7 to 12.
Citation Information
Patent Citations
Information processing method and system
CN107481059A
An Agency system and method for electronic paymentthrough a computer network
KR1020030048667A
