Method, device and apparatus for configuring and using a brush palm payment device

Abstract

The application discloses a palm swiping payment device use method, a configuration method, a device and equipment, and relates to the technical field of artificial intelligence. The method comprises the following steps: in response to a palm swiping operation for paying a first resource, displaying a palm model and a paid resource launched by a third-party platform; in response to a gesture operation for paying the paid resource, displaying a process in which the paid resource is selected by the palm model; and displaying a payment success notification, which is used for indicating that the first resource and the paid resource are successfully paid. The application embodiment can be applied to artificial intelligence, intelligent transportation and the like. The application embodiment supports the palm swiping payment device having a third configuration capability for the paid resource, so that the utilization rate of the palm swiping payment device is improved, and the exposure rate of the paid resource is improved.

Description

Technical Field

[0001] This application relates to the field of artificial intelligence technology, and in particular to a method for using, configuring, assembling, and equipping a palm payment device. Background Technology

[0002] With the development of artificial intelligence technology, the application scenarios of palm verification are increasing, such as palm verification for access control, palm verification for payment, and palm verification for clocking in.

[0003] Among related technologies, there are palm-scanning payment devices that allow users to complete payments for tickets, entrance tickets, goods, and other items simply by scanning their palms. This payment method is convenient and fast.

[0004] However, current palm payment devices have limited functionality and low utilization rates. Summary of the Invention

[0005] This application provides a method for using, configuring, and assembling a palm-swipe payment device, which can improve the utilization rate of palm-swipe payment devices. The technical solution is as follows:

[0006] According to one aspect of the embodiments of this application, a method for using a palm payment device is provided, the method comprising:

[0007] In response to the swipe gesture used to pay for the first resource, a hand model and the paid resources provided by the third-party platform are displayed.

[0008] In response to a gesture operation for paying for the paid resource, the process of the paid resource being selected by the palm model is displayed;

[0009] Display a payment success notification, which indicates that the first resource and the paid resource have been successfully paid for.

[0010] According to one aspect of the embodiments of this application, a method for configuring a palm payment device is provided, the method comprising:

[0011] Display device configuration interface, which is used by third-party platforms to configure the palm payment device;

[0012] In response to an operation for configuring a first palm-swipe payment device, device configuration data is generated, the device configuration data including the identification information and resource allocation information of the first palm-swipe payment device, the resource allocation information being used to indicate the paid resources allocated by the third-party platform;

[0013] The device configuration data is sent to the backend service platform, so that the backend service platform can forward the device configuration data to the first swipe payment device.

[0014] According to one aspect of the embodiments of this application, a device for using a palm payment device is provided, the device comprising:

[0015] The paid resource display module is used to respond to the swipe operation for payment of the first resource, and to display the palm model and the paid resources provided by the third-party platform.

[0016] The paid resource selection module is used to respond to a gesture operation for paying for the paid resource and display the process of the paid resource being selected by the palm model;

[0017] The payment notification display module is used to display a payment success notification, which indicates that the first resource and the paid resource have been successfully paid for.

[0018] In some embodiments, the paid resource display module further includes:

[0019] The palm data acquisition submodule is used to acquire palm data in response to the palm swipe operation used to pay for the first resource;

[0020] The hand model display submodule is used to display the hand model based on the hand data;

[0021] The paid resource display submodule is used to display the paid resources according to the device configuration data; wherein, the device configuration data is obtained by the third-party platform based on the backend service platform corresponding to the first swipe payment device, and the device configuration data includes the identification information and resource deployment information of the first swipe payment device, and the resource deployment information is used to indicate the paid resources deployed by the third-party platform.

[0022] In some embodiments, the device configuration data further includes a payment trigger instruction, which is used to instruct an operation to trigger payment for the paid resources;

[0023] The paid resource display submodule is further configured to display payment trigger prompt information for the paid resource according to the payment trigger instruction of the paid resource, the payment trigger prompt information being used to prompt the operation of triggering payment for the paid resource; and to display the process of the paid resource being selected by the palm model in response to the gesture operation conforming to the payment trigger instruction of the paid resource.

[0024] In some embodiments, the paid resource selection module is further configured to:

[0025] In response to a gesture operation for grasping the paid resource, the process of displaying the paid resource being selected by the palm model is shown;

[0026] Alternatively, in response to a gesture operation for grasping the paid resource and moving the paid resource to a designated area, the process of the paid resource being selected and moved by the palm model is displayed.

[0027] Alternatively, in response to a gesture that triggers the purchase option for the paid resource, the process of the purchase option for the paid resource being triggered by the palm model is displayed;

[0028] Alternatively, in response to a gesture indicating agreement to pay for the paid resource, a process is performed to display the option to purchase the paid resource being selected by the hand model.

[0029] In some embodiments, the resource deployment information further includes background data and display method data;

[0030] The paid resource display submodule is further configured to display a background image related to the paid resource based on the background data; and to display the paid resource according to the display method corresponding to the display method data.

[0031] In some embodiments, the paid resource display submodule is further configured to, upon receiving device configuration data generated by different third-party platforms, sequentially display the paid resources provided by the different third-party platforms in the order in which the device configuration data is received.

[0032] In some embodiments, the payment success notification includes a first sub-payment notification and a second sub-payment notification, wherein the first sub-payment notification indicates that the first resource has been successfully paid for, and the second sub-payment notification indicates that the paid resource has been successfully paid for; the device for using the palm payment device further includes:

[0033] The first order generation module is used to generate a first payment order for the first resource in response to a swipe operation for paying for the first resource.

[0034] The second order generation module is used to generate a second payment order for the paid resource in response to a gesture operation for paying for the paid resource.

[0035] The total order generation module is used to merge the first payment order and the second payment order to generate a total payment order;

[0036] The total order sending module is used to send the total payment order to the backend service platform corresponding to the first palm payment device;

[0037] The payment notification receiving module is used to receive the first payment success notification and the second payment success notification from the backend service platform; wherein, the first payment success notification and the second payment success notification are also sent to the terminal device held by the user currently using the first palm payment device.

[0038] According to one aspect of the embodiments of this application, a configuration device for a palm payment device is provided, the device comprising:

[0039] The configuration interface display module is used to display the device configuration interface, which is used by third-party platforms to configure the palm payment device.

[0040] A configuration data generation module is used to generate device configuration data in response to an operation for configuring the first palm payment device. The device configuration data includes the identification information and resource allocation information of the first palm payment device. The resource allocation information is used to indicate the paid resources allocated by the third-party platform.

[0041] The configuration data sending module is used to send the device configuration data to a first-party platform, so that the first-party platform can forward the device configuration data to the first swipe payment device.

[0042] In some embodiments, the configuration data generation module is further configured to:

[0043] The device configuration interface displays options for multiple paid resources, which are provided by the third-party platform.

[0044] In response to an operation for selecting an option among the plurality of paid resources, resource delivery information corresponding to the at least one paid resource is added to the device configuration data;

[0045] The device configuration interface displays options for multiple palm payment devices, and the payment clients in these multiple palm payment devices are provided with backend services by the backend service platform.

[0046] In response to an operation for selecting an option for the first palm payment device among the plurality of palm payment devices, the identification information of the first palm payment device is added to the device configuration data.

[0047] In some embodiments, the device configuration data further includes a payment trigger instruction, which is used to instruct a gesture operation to trigger payment of the paid resource; the configuration device of the palm payment device further includes:

[0048] The instruction option display module is used to display multiple payment trigger instruction options in the device configuration interface, wherein the multiple payment trigger instructions are provided by the third-party platform;

[0049] The trigger instruction selection module is used to add the first payment trigger instruction into the device configuration data in response to an operation for selecting an option for the first payment trigger instruction among the plurality of payment trigger instructions.

[0050] In some embodiments, the configuration device of the palm payment device further includes:

[0051] Background data generation module, used to generate background data in response to an operation for configuring a background image related to the paid resource;

[0052] The display mode data generation module is used to generate display mode data in response to an operation for configuring the display mode of the paid resources;

[0053] The configuration data generation module is also used to add the background data and the display mode data into the resource delivery information.

[0054] In some embodiments, the configuration device of the palm payment device further includes:

[0055] The notification receiving module is configured to receive a successful setup notification from the backend service platform, which indicates that the first palm payment device has been successfully set up.

[0056] The notification display module is configured to display the successful setup notification and forward the successful setup notification to the third-party platform.

[0057] According to one aspect of the embodiments of this application, a computer device is provided, the computer device including a processor and a memory, the memory storing a computer program, the computer program being loaded and executed by the processor to implement the above-described method of using the palm payment device, or to implement the above-described method of configuring the palm payment device.

[0058] According to one aspect of the embodiments of this application, a computer-readable storage medium is provided, wherein a computer program is stored in the storage medium, the computer program being loaded and executed by a processor to implement the above-described method of using the palm payment device, or to implement the above-described method of configuring the palm payment device.

[0059] According to one aspect of the embodiments of this application, a computer program product is provided, comprising a computer program stored in a computer-readable storage medium. A processor of a computer device reads the computer program from the computer-readable storage medium and executes the computer program, causing the computer device to perform either the method for using the aforementioned palm-swipe payment device or the method for configuring the aforementioned palm-swipe payment device.

[0060] The technical solutions provided in this application embodiment may have the following beneficial effects:

[0061] By displaying paid resources provided by a third-party platform during the user's palm payment process, users can simultaneously pay for these resources while making the palm payment, which helps improve the conversion rate of paid resources and the convenience of payment.

[0062] In addition, by supporting third-party platforms to configure the swipe payment device with related paid resources, the swipe payment device is no longer limited to swipe payment, which helps to improve the utilization rate and use value of the swipe payment device. Attached Figure Description

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

[0064] Figure 1 This is a schematic diagram of the implementation environment of a solution provided in one embodiment of this application;

[0065] Figure 2 This is a flowchart of a configuration method for a palm payment device provided in one embodiment of this application;

[0066] Figure 3 This is a schematic diagram of a configuration method for a palm payment device provided in one embodiment of this application;

[0067] Figure 4 This is a schematic diagram of a configuration method for a palm payment device provided in another embodiment of this application;

[0068] Figure 5 This is a flowchart illustrating a method of using a palm-swipe payment device according to an embodiment of this application;

[0069] Figure 6 This is a schematic diagram of a palm-swiping operation provided in one embodiment of this application;

[0070] Figure 7 This is a schematic diagram of a gesture operation provided in one embodiment of this application;

[0071] Figure 8 This is a schematic diagram of a gesture operation provided in another embodiment of this application;

[0072] Figure 9 This is a schematic diagram of a gesture operation provided in another embodiment of this application;

[0073] Figure 10 This is a schematic diagram of the implementation environment of a solution provided in another embodiment of this application;

[0074] Figure 11 This is a schematic diagram illustrating the method of using a palm-swipe payment device according to an embodiment of this application;

[0075] Figure 12 This is a block diagram of a device for using a palm-swipe payment device according to one embodiment of this application;

[0076] Figure 13 This is a block diagram of a device for using a palm-swipe payment device according to another embodiment of this application;

[0077] Figure 14 This is a block diagram of a configuration device for a palm payment device according to one embodiment of this application;

[0078] Figure 15 This is a block diagram of a configuration device for a palm payment device provided in another embodiment of this application;

[0079] Figure 16 This is a block diagram of a computer device provided in one embodiment of this application. Detailed Implementation

[0080] Before describing the embodiments of this application, the relevant terms involved in this application will be explained.

[0081] 1. Palm recognition technology

[0082] It is a technology that uses palm multimedia information (i.e., palm data) to obtain personal identity information (such as user accounts). For example, a palm payment device is a device that uses palm recognition technology, which allows users to complete payments for a target order by swiping their palm.

[0083] 2. 3D camera

[0084] Similar to traditional cameras, 3D cameras incorporate liveness detection hardware and software, such as depth cameras and infrared cameras, to ensure information security. They possess multiple functions including facial recognition, gesture recognition, 3D measurement, environmental perception, and image acquisition, and are widely used in televisions, mobile phones, robots, autonomous driving, and palm-scanning verification. For example, a 3D camera can be deployed on palm-scanning payment devices to capture multimedia information from the palm.

[0085] 3. SN (Serial Number, string serial number)

[0086] It is an ID (Identity Document) that can uniquely identify a device. For example, the SN of a swipe payment device can be used to uniquely identify that swipe payment device.

[0087] 4. SQLite (Structured Query Language) database

[0088] It is a lightweight database that is a relational database management system that complies with ACID (Atomicity-Consistency-Isolation-Durability).

[0089] 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.

[0090] Artificial intelligence (AI) is the theory, methods, technology, and application systems that use digital computers or machines controlled by digital computers to simulate, extend, and expand human intelligence, perceive the environment, acquire knowledge, and use that knowledge to achieve optimal results. In other words, AI is a comprehensive technology within computer science that attempts to understand the essence of intelligence and produce a new kind of intelligent machine that can react in a way similar to human intelligence. AI studies the design principles and implementation methods of various intelligent machines, enabling them to possess the functions of perception, reasoning, and decision-making.

[0091] Artificial intelligence (AI) is a comprehensive discipline encompassing a wide range of fields, including both hardware and software technologies. Fundamental AI technologies generally include sensors, dedicated AI chips, cloud computing, distributed storage, big data processing, pre-trained model technology, operating / interactive systems, and mechatronics. Among these, pre-trained models, also known as large-scale models or foundational models, can be widely applied to downstream tasks across various AI fields after fine-tuning. AI software technologies primarily include computer vision, speech processing, natural language processing, and machine learning / deep learning.

[0092] Computer vision (CV) is a science that studies how to enable machines to "see." More specifically, it refers to machine vision, which uses cameras and computers to replace human eyes in tasks such as target recognition, tracking, and measurement, and further performs image processing to create images more suitable for human observation or transmission to instruments for detection. As a scientific discipline, computer vision researches related theories and technologies, attempting to build artificial intelligence systems capable of extracting information from images or multidimensional data. Large model technology has brought significant changes to the development of computer vision. Pre-trained models in the field of vision, such as Swin-Transformer, ViT (Vision Transformer), V-MOE (Vision Mixture-of-Experts), and MAE (Masked Autoencoders), can be fine-tuned and quickly and widely applied to specific downstream tasks. Computer vision technologies typically include image processing, image recognition, image semantic understanding, image retrieval, OCR (Optical Character Recognition), video processing, video semantic understanding, video content / behavior recognition, 3D object reconstruction, 3D (Three-Dimensional) technology, virtual reality, augmented reality, simultaneous localization and mapping (SLAM), and other technologies.

[0093] The technical solution provided in this application relates to computer vision technology in artificial intelligence. It utilizes computer vision technology to perform operations such as palm recognition and gesture recognition to complete the identification of user accounts, thereby realizing palm payment, gesture payment, etc.

[0094] The technical solution provided in this application is applicable to any palm payment scenario, such as palm payment for tickets, shopping, and configuring palm payment devices. The technical solution provided in this application can improve the utilization rate of palm payment devices.

[0095] Please refer to Figure 1The diagram illustrates an implementation environment for a solution provided in one embodiment of this application. This implementation environment may include: a terminal device 10, a mobile payment device 20, a backend service platform 30, and a third-party platform 40.

[0096] Terminal device 10 can be an electronic device such as a mobile phone, tablet computer, multimedia playback device, PC (Personal Computer), intelligent robot, vehicle terminal, smart home appliance, intelligent voice interaction device, etc., and this application embodiment does not limit it. A client of a first type of target application can be installed on terminal device 10. This first type of target application can be such as a social chat application, payment application, shopping application, etc., and this application embodiment does not limit it. Optionally, terminal device 10 can refer to the terminal device corresponding to third-party platform 40.

[0097] The palm payment device 20 refers to an electronic device used to implement palm payment, such as a mobile phone, tablet computer, multimedia playback device, PC, intelligent robot, vehicle terminal, smart home appliance, intelligent voice interaction device, access control device, purchasing device, and any electronic device with palm payment function. This application embodiment does not limit this. The palm payment device 20 can install a client of a second type of target application. This second type of target application can be such as a payment application, shopping application, ticketing application, access control application, and any application that supports palm payment function. This application embodiment does not limit this.

[0098] Optionally, the palm payment device 20 includes an image acquisition module and an interface display module. The image acquisition module can be implemented using a 3D camera to acquire images, such as palm images. The interface display module can be implemented as a touch screen to enable human-computer interaction between the user and the palm payment device 20, and to display information to the user. For example, the palm payment device 20 can refer to a palm payment device used for purchasing tickets in scenarios such as subways, buses, and high-speed trains; it can also refer to a palm payment device used for payment and purchasing goods in scenarios such as supermarkets and shopping malls; or it can refer to a palm payment device used for payment in scenarios such as merchants and individuals. This application embodiment does not limit this.

[0099] The backend service platform 30 can refer to the backend service platform for the clients of the first type of target application (such as a social chat application) in the terminal device 10 and the clients of the second type of target application (such as a payment application) in the mobile payment device 20. For example, the backend service platform 30 can be used to provide backend services for the clients of the first type of target application (such as a social chat application) in the terminal device 10 and the clients of the second type of target application (such as a payment application) in the mobile payment device 20. Optionally, the backend service platform 30 can be implemented as a single server, a server cluster consisting of multiple servers, or a cloud computing service center.

[0100] Third-party platform 40 refers to a platform for distributing paid resources, such as paid emoticons, paid articles, paid videos, and paid products. Paid resources are resources that require payment to obtain. These resources can be developed by developers; for example, paid emoticons can be developed by emoticon developers, and paid articles can be written by article writers. Developers may or may not belong to third-party platform 40; this embodiment does not limit this. Third-party platform 40 is different from backend service platform 30. Optionally, third-party platform 40 can be implemented as a single server, a server cluster consisting of multiple servers, or a cloud computing service center.

[0101] Terminal device 10 can communicate with backend service platform 30 and third-party platform 40 via network 50, and the swipe payment device 20 can communicate with backend service platform 30 via network 50. This network 50 can be a wired network or a wireless network.

[0102] For example, third-party personnel of the third-party platform 40 can open the device configuration interface for the swipe payment device through the terminal device 10 corresponding to the third-party platform 40, generate device configuration data through the device configuration interface, and then send the device configuration data to the backend service platform 30 through the terminal device 10, so that the backend service platform 30 can forward the device configuration data to the swipe payment device 20, and the swipe payment device 20 can display paid resources according to the device configuration data.

[0103] Optionally, the third-party platform 40 may first package the resource data corresponding to the paid resource and send it to the backend service platform 30, so that after the user pays for the paid resource, the backend service platform 30 can directly deliver the resource data of the paid resource to the user. Alternatively, the third-party platform 40 may also send the corresponding resource data of the paid resource to the backend service platform 30 after the user pays for the paid resource, and then the backend service platform 30 can deliver the resource data of the paid resource to the user. This embodiment of the application does not limit this approach.

[0104] Among them, the third-party platform 40 can first provide the details of paid resources to the backend service platform 30 through the terminal device 10, so that the backend service platform 30 can build the device configuration interface and generate the device configuration interface.

[0105] The technical solutions provided in this application will be described below through method embodiments.

[0106] Please refer to Figure 2 It illustrates a flowchart of a method for setting up a palm payment device according to an embodiment of this application. The entity executing each step of the method can be... Figure 1 In the implementation environment of the scheme shown, the terminal device 10, such as the client running in the terminal device 10, may include the following steps (201-203).

[0107] Step 201: Display the device configuration interface, which is used by third-party platforms to configure the palm payment device.

[0108] Optionally, in response to an operation by a third-party user to open the device configuration interface, the client displays the device configuration interface. Here, the third-party user can refer to staff of the third-party platform. The device configuration interface can refer to the user interface provided by the aforementioned first type of target application, which can be used to configure the swipe payment device associated with the backend service platform. The device configuration interface is provided as a background service by the backend service platform.

[0109] For example, the aforementioned client can provide various services, such as payment services, WeChat official account services, chat services, swipe payment device configuration services, and swipe payment services. In response to a third party's triggering action regarding the swipe payment device configuration service options, the client displays the device configuration interface.

[0110] In the case of a terminal device with a touchscreen, the triggering operation can refer to an operation such as clicking, pressing, or double-clicking on an option. In the case of a terminal device with an external device (such as a mouse, keyboard, or joystick), the triggering operation can refer to a triggering operation on an option via the external device; this embodiment of the application does not limit this.

[0111] Optionally, the configuration in this application embodiment may refer to the process of setting content related to paid resources. Paid resources can refer to resources that require payment, such as paid emoticons, paid articles, paid videos, paid images, paid goods, etc., and this application embodiment does not limit this. The paid resources may be provided by a third-party platform, such as those developed by third-party personnel corresponding to the third-party platform.

[0112] The swipe payment device, third-party platform, and backend service platform are the same as those described in the above embodiments. For content not described in the embodiments of this application, please refer to the above embodiments, and they will not be repeated here.

[0113] Step 202: In response to the operation for configuring the first palm payment device, generate device configuration data, which includes the identification information and resource allocation information of the first palm payment device. The resource allocation information is used to indicate the paid resources allocated by the third-party platform.

[0114] The aforementioned first swipe payment device can refer to any swipe payment device associated with the first-party platform. Each swipe payment device has its own unique identification information, which is used to uniquely identify the swipe payment device. For example, the identification information of the first swipe payment device can refer to the SN of the first swipe payment device, which is used to uniquely identify the first swipe payment device.

[0115] The device configuration data in this embodiment refers to the settings data for the first swipe payment device, which is related to paid resources. For example, the resource allocation information included in the device configuration data is used to instruct the third-party platform on the relevant configurations of paid resources in the first swipe payment device, such as the type, quantity, display method, display content, payment method, and purchase method of the paid resources. This embodiment does not limit this aspect.

[0116] In one example, the client displays paid resources as a list to a third party. For instance, in response to a third party's action on a resource selection control in the device configuration interface, the client displays a list of paid resources with multiple options. The selection process for these paid resources can then proceed as follows:

[0117] 1. The device configuration interface displays options for multiple paid resources, which are provided by a third-party platform.

[0118] Optionally, the details of the aforementioned paid resources are provided by a third-party platform, and the options for paid resources can be constructed based on the identification information of the paid resources. For example, the options for paid resources are the name, serial number, and other identification information of the paid resources. The backend service platform generates a list of paid resources based on the identification information of the aforementioned paid resources, which allows third-party personnel to select from them, thereby improving the flexibility of paid resource configuration.

[0119] Optionally, different types of paid resources correspond to different paid resource lists, and different third-party platforms provide different paid resource lists. A particular third-party platform can only configure the paid resources it provides. The client can display the corresponding paid resource list based on the user account of the third-party platform.

[0120] 2. In response to an operation that selects at least one paid resource from a plurality of paid resources, add the resource delivery information corresponding to at least one paid resource into the device configuration data.

[0121] Optionally, a third party may select one or more paid resources each time to deploy them to the first palm payment device. The resource deployment information corresponding to the at least one paid resource may include the identification information of each of the at least one paid resource.

[0122] For example, for paid emoticons, third parties may select a portion of the paid emoticons to distribute each time; for paid articles, third parties may select a portion of the paid articles to distribute each time, such as a section of each paid article. This application embodiment does not limit this.

[0123] In one example, the client displays a list of mobile payment devices to a third party. For instance, in response to a third party's action on the device selection control in the device configuration interface, the client displays a list of mobile payment devices, which includes multiple options for mobile payment devices. The selection process for these devices can be as follows:

[0124] 1. The device configuration interface displays an option for multiple swipe payment devices. The payment client in these multiple swipe payment devices is provided with backend services by the backend service platform.

[0125] Optionally, the options for these multiple swipe payment devices are provided by a backend service platform. These options can be constructed based on the identification information of the paid resources. For example, the options for a swipe payment device include its name, serial number (SN), address, and other identifying information. The backend service platform generates a list of swipe payment devices based on the identification information of the multiple devices for which it provides backend services, allowing third-party users to select, thus improving the configuration flexibility of the swipe payment devices. The payment client within the swipe payment device enables the device to perform payment functions; this payment client can be provided by the backend service platform.

[0126] 2. In response to the operation of selecting the first palm payment device among multiple palm payment devices, add the identification information of the first palm payment device to the device configuration data.

[0127] Optionally, third-party personnel can select one or more mobile payment devices to deploy paid resources each time. For example, third-party personnel can deploy paid resources to all mobile payment devices associated with the backend service platform at once.

[0128] In one example, this application embodiment also supports third-party personnel setting payment trigger instructions for paid resources. Exemplarily, the aforementioned device configuration data also includes payment trigger instructions, which are used to instruct a gesture operation to trigger payment for paid resources.

[0129] Optionally, the client will display payment trigger instructions to the third party in the form of a list. For example, in response to a third party's trigger operation on the instruction selection control in the device configuration interface, the client displays a list of payment trigger instructions, which includes multiple payment trigger instruction options. The selection process for the payment trigger instructions can then be as follows:

[0130] 1. The device configuration interface displays multiple payment trigger commands, which are provided by a third-party platform.

[0131] Optionally, the aforementioned payment trigger instructions are provided by a third-party platform, and the options for these instructions can be constructed based on their identification information. For example, the options for a payment trigger instruction include its name, sequence number, and other identification information. The backend service platform generates a list of payment trigger instructions based on this identification information for third-party personnel to choose from, thus improving the flexibility of payment trigger configuration for paid resources.

[0132] For example, a third party may set the same payment trigger instruction for at least one selected paid resource, or may set a separate payment trigger instruction for each selected paid resource. This application embodiment does not limit this.

[0133] Users of the palm payment device can trigger payment for consumer resources through gesture operations indicated by the payment trigger command. For example, if a user's gesture operation for a certain paid resource triggers the payment command for that resource, the palm payment device assumes that the user agrees to purchase that paid resource.

[0134] Optionally, the gesture operation corresponding to the payment trigger instruction includes at least one of the following:

[0135] 1) Gestures indicating agreement to payment, such as "ok" or "Yes" gestures that signify agreement.

[0136] 2) A continuous grasping action generates a gesture operation, such as grasping a consumer resource to indicate agreement to purchase that consumer resource.

[0137] 3) Gesture operations generated by continuous grabbing and moving actions, such as grabbing a consumer resource and moving the paid resource to a designated area, can indicate agreement to purchase the consumer resource.

[0138] 4) Gesture actions used to trigger the purchase option of paid resources. For example, clicking on the purchase option of a certain consumer resource indicates agreement to purchase that consumer resource.

[0139] 2. In response to an operation that selects the first payment trigger instruction among multiple payment trigger instructions, the first payment trigger instruction is added to the device configuration data.

[0140] Optionally, the first payment trigger instruction can be for a single paid resource or for a selection of multiple paid resources. The client adds the identification information of the first payment trigger instruction to the device configuration data.

[0141] In one example, this application embodiment also supports setting the background image and display mode of paid resources to further improve the flexibility and personalization of paid resource settings. This process may include the following:

[0142] 1. In response to an operation used to configure a background image associated with a paid resource, generate background data.

[0143] Optionally, after selecting a paid resource, a third party can create a background image, such as a poster corresponding to the paid resource, using the image of that resource. The client then generates background data based on this background image. This background data refers to the payment device displaying the paid resource to the user using a background image (such as a poster). Optionally, this background image can be triggered by the user to purchase the paid resource, which helps to further increase the exposure of the paid resource and increase the touchpoints between the user and the paid resource.

[0144] 2. In response to operations used to configure the display method of paid resources, generate display method data.

[0145] Display method data is used to indicate the display method of paid resources, and the display method of paid resources includes at least one of the following:

[0146] 1) Paid resources are displayed in a drop-down manner.

[0147] 2) Paid resources are displayed randomly in the interface.

[0148] 3) Paid resources are dynamically displayed on the interface with a specified trajectory.

[0149] 4) Paid resources are displayed in a fixed location on the interface.

[0150] For example, paid emojis can be displayed in a falling manner from top to bottom; paid articles can be displayed in a fixed position on the interface.

[0151] 3. Add background data and display method data to the resource delivery information.

[0152] Optionally, the client can bind and store background data and display mode data with the consumed resources.

[0153] In one example, a third party can also configure when the paid resource is displayed. For instance, the display timing of the paid resource may include at least one of the following:

[0154] 1) Display paid resources during the user's swipe process.

[0155] 2) Display paid resources before the user swipes their palm.

[0156] 3) After the user successfully pays by swiping their palm, the paid resources are displayed.

[0157] Step 203: Send the device configuration data to the backend service platform so that the backend service platform can forward the device configuration data to the first swipe payment device.

[0158] Optionally, after generating device configuration data, the client cannot directly configure the mobile payment device. Therefore, it needs to forward the configuration through the backend service platform to configure the first mobile payment device. Upon receiving the device configuration data, the first mobile payment device loads the configuration data to complete the configuration related to paid resources and generates a configuration success notification. The first mobile payment device sends the configuration success notification to the backend service platform, which then sends it to the client. This configuration success notification indicates that the first mobile payment device has been successfully configured.

[0159] Optionally, after receiving a successful setup notification from the backend service platform, the client displays the successful setup notification and forwards it to a third-party platform to inform the first swipe payment device that it has been successfully set up.

[0160] For example, refer to Figure 3 and Figure 4 Third-party personnel 301 perform configuration operations for the palm payment device through client 302. Optionally, third-party personnel 301 first selects the paid resources through client 302, then selects the payment trigger instruction, and finally selects the palm payment device to be configured through client 302. In response to the completion of the configuration operation by third-party personnel 301, client 302 generates device configuration data for palm payment device 304 and sends the device configuration data to the backend service platform 303.

[0161] A persistent connection is established between the backend service platform 303 and the mobile payment device 304. Based on this persistent connection, the backend service platform 303 sends device configuration data to the mobile payment device 304. The mobile payment device 304 loads the configuration data, generates a configuration result (such as the configuration success notification mentioned above), and returns the configuration result to the backend service platform 303 via the persistent connection. The backend service platform 303 then returns the configuration result to the client 302 and the third-party platform.

[0162] In summary, the technical solution provided in this application, by displaying paid resources provided by a third-party platform during the user's palm payment process using a palm payment device, allows the user to simultaneously pay for paid resources while making a palm payment, which helps to improve the conversion rate of paid resources and the convenience of payment.

[0163] In addition, by supporting third-party platforms to configure the swipe payment device with related paid resources, the swipe payment device is no longer limited to swipe payment, which helps to improve the utilization rate and use value of the swipe payment device.

[0164] In addition, this application embodiment supports third-party platforms in setting the quantity of paid resources, payment trigger instructions, display methods, background images, and display timing for the swipe payment device, which helps to improve the personalization of paid resource configuration.

[0165] Please refer to Figure 5 It illustrates a flowchart of a method for using a palm-swipe payment device according to an embodiment of this application. The entity executing each step of the method can be... Figure 1 The method may include the following steps (501-503) in the following scenarios: a mobile payment device 20 in the implementation environment of the scheme shown, such as a client running in the mobile payment device 20.

[0166] Step 501, in response to the palm-swiping operation used to pay for the first resource, displays the palm model and the paid resources provided by the third-party platform.

[0167] The "first resource" can refer to the resources provided by the native platform corresponding to the current mobile payment device. The aforementioned backend service platform can refer to a platform that collaborates with the native platform to support the mobile payment device in realizing payment functionality. The native platform provides the first resource to the user. This first resource includes at least one of the following: tickets, goods, and permissions. For example, a mobile payment device provided by a ticketing platform is used for payment of tickets, while a mobile payment device provided by a shopping platform is used for payment of goods.

[0168] A palm-swiping operation can be an action where you point your palm at a palm-swiping payment device, allowing the device to collect your palm data. For example, see reference... Figure 6 The user unfolds their palm 602 with the palm facing the image acquisition device 603 of the palm payment device 601 to perform the palm swipe operation.

[0169] The aforementioned hand model can refer to a pre-set simulation model or a virtual model constructed based on the user's hand data; this application embodiment does not limit this. Paid resources, palm payment devices, third-party platforms, and backend service platforms are described in the same way as in the above embodiments. Content not described in this application embodiment can be referred to in the above embodiments and will not be repeated here.

[0170] In one example, step 501 may also include the following:

[0171] 1. In response to the palm-swiping operation used for payment of primary resources, obtain palm data.

[0172] Optionally, in response to the palm-swiping operation used for payment of the first resource, the payment client in the palm-swiping payment device can capture streaming media data (such as a palm image) of the user's current palm by calling a 3D camera. After acquiring the streaming media data of the palm, the client optimizes the streaming media. For example, the client comprehensively evaluates and selects the optimal palm image (i.e., palm data) based on factors such as palm size, angle, image contrast, image brightness, and clarity.

[0173] 2. Display the hand model based on the hand data.

[0174] Optionally, after acquiring the palm data, the client displays a pre-set palm model at a specified initial position; or, after acquiring the palm data, the client constructs a palm model based on the palm data and displays the palm model at a specified initial position. In a feasible example, the client determines the initial position of the palm model in the user interface based on the position of the palm in the image acquisition device, and displays the palm model at that initial position.

[0175] 3. Display paid resources based on device configuration data; wherein, the device configuration data is obtained by the third-party platform based on the backend service platform corresponding to the FirstPayPay device. The device configuration data includes the identification information and resource allocation information of the FirstPayPay device. The resource allocation information is used to indicate the paid resources allocated by the third-party platform.

[0176] Optionally, the client displays paid resources based on the aforementioned resource delivery information, which includes the identifier of the paid resources. The client obtains the rendering data of the paid resources based on the identifier and displays the paid resources accordingly. The rendering data, used to render and display the paid resources, may include the images and descriptions of the paid resources.

[0177] For example, refer to Figure 7 During the process of the user performing a palm-swiping operation with the palm 602, the user interface 604 of the palm-swiping payment device 601 displays multiple paid resources, as well as a palm model 605 corresponding to the palm 602, which can move along with the palm 602.

[0178] Optionally, the resource delivery information mentioned above also includes background data and display method data. The client can display background images related to the paid resources based on the background data, and display the paid resources based on the display method corresponding to the display method data.

[0179] For example, the client can display a background image in the user interface of the first palm-swiping payment device before, during, or after the user swipes their palm to show the user the paid resources corresponding to that background image.

[0180] Optionally, the client displays paid resources provided by the third-party platform in a top-to-bottom falling manner; or, the client displays paid resources provided by the third-party platform in a random display manner; or, the client displays paid resources provided by the third-party platform in a manner that moves along a specified trajectory; or, the client displays paid resources provided by the third-party platform in a manner that is specified in a specified position. This embodiment of the application does not limit this. For example, for paid emoticons, the client can display each paid emoticon in a top-to-bottom falling manner; for paid articles, the client can display excerpts of each paid article in a specified position in the user interface.

[0181] In one feasible example, the resource delivery information mentioned above also includes the display timing of paid resources. The client can display paid resources according to the display timing. For example, the client can display paid resources before swiping. For instance, the client can display paid resources during the display of the first resource; or, the client can display paid resources during the swiping process, for example, the client displays paid resources in response to the swiping operation; or, the client can also display paid resources after swiping, such as the client displaying paid resources on the payment success interface corresponding to the first resource. This application embodiment does not limit this.

[0182] In one example, the same swipe payment device supports configurations for different third-party platforms, which can further improve the efficiency of the swipe payment device. The embodiments of this application may also include the following: upon receiving device configuration data generated by different third-party platforms, the paid resources provided by the different third-party platforms are displayed sequentially according to the order in which the device configuration data is received.

[0183] The receiving order refers to the order in which the swipe payment settings receive the device configuration data. For example, if third-party platforms A, B, and C all configure the first swipe payment device, and third-party platform A's configuration time is earlier than third-party platform B's, and third-party platform B's configuration time is earlier than third-party platform C's, then the client will display the paid resources deployed by third-party platform A, third-party platform B, and third-party platform C in that order.

[0184] Optionally, if there is sufficient space in the user interface of the swipe payment device, the client can also simultaneously display paid resources from different third-party platforms.

[0185] Step 502, in response to a gesture operation used to pay for a paid resource, displays the process of the paid resource being selected by the palm model.

[0186] Optionally, the aforementioned device configuration data may also include a payment trigger instruction, which is used to instruct the operation of triggering payment of resources. In this case, step 502 may further include the following:

[0187] 1. Based on the payment trigger instruction for the paid resource, display the payment trigger prompt information for the paid resource. This payment trigger prompt information is used to prompt the operation of triggering payment for the paid resource.

[0188] Optionally, the client determines the corresponding gesture operation for the paid resource based on the payment trigger instruction of the paid resource, then generates a payment trigger prompt message based on the gesture operation, and finally displays the payment trigger prompt message during the display of the paid resource to indicate which gesture operation the user should use to purchase the paid resource.

[0189] This application does not limit the style of the payment trigger prompt message, such as it can be text, image, or animation. For example, if the gesture operation corresponding to the paid resource is a grab gesture, the payment trigger prompt message could be: "Grab xx to complete the purchase of xx."

[0190] 2. In response to gesture operations that match the payment trigger command for paid resources, display the process of the paid resource being selected by the palm model.

[0191] Optionally, the client can identify the user's hand gestures in real time based on palm data to determine the type of the gesture and then detect whether the gesture matches the payment trigger instruction for the paid resource; or, the client can send palm data to the backend service platform in real time so that the backend service platform can identify the user's hand gestures to determine the type of the gesture and then detect whether the gesture matches the payment trigger instruction for the paid resource.

[0192] For example, the client acquires a palm image through the image acquisition module of the palm payment device, and collects real-time motion information of the palm, such as finger position, direction of movement, speed, acceleration, and angle. Based on the collected palm data, the client extracts feature information of the gesture operation, such as the number of fingers, the shape of the gesture, and the direction of the gesture. The client then compares the extracted feature information with a pre-trained gesture model to determine the category of the gesture operation. The client can employ machine learning algorithms for gesture operation category recognition, such as Support Vector Machine (SVM), neural networks, decision trees, and pre-trained models.

[0193] After determining the type of gesture operation, the client compares it with the type corresponding to the payment trigger instruction. If they match, the gesture operation is determined to be in accordance with the payment trigger instruction for the paid resource; otherwise, it is determined to be in accordance with the payment trigger instruction for the paid resource. When the gesture operation is in accordance with the payment trigger instruction for the paid resource, the client displays the process of the paid resource being selected by the palm model, meaning the client can determine that the user agrees to pay for the paid resource.

[0194] In one example, the scenarios in which paid resources are triggered to pay include at least one of the following:

[0195] 1) In response to a gesture used to grab a paid resource, display the process of the paid resource being selected by the palm model.

[0196] Optionally, the aforementioned hand model changes synchronously with the brushing operation, such as in position and posture. For example, refer to... Figure 8 Users can move the hand model 605 from its initial position to the target paid resource through gesture operation. In response to the user's control of the hand 602 to perform a grasping gesture operation, the client controls the hand model 605 to grasp the target paid resource and automatically add it to the shopping cart to realize the purchase of the target paid resource.

[0197] 2) In response to a gesture operation used to grab paid resources and move them to a specified area, the process of the paid resources being selected and moved by the hand model is displayed.

[0198] The designated area can be set and adjusted according to actual usage needs. Optionally, the designated area can be implemented as a shopping cart style.

[0199] For example, refer to Figure 8 and Figure 9 Users can move the hand model 605 from its initial position to the target paid resource using gestures. In response to the user's control of the hand 602 to perform a grasping gesture, the client controls the hand model 605 to grasp the target paid resource. In response to the user's control of the hand 602 to move the hand model 605 towards the shopping cart 606 in a grasping posture, the client displays the process of the target paid resource being grasped and moved to the shopping cart 606 by the hand model 605. Once the target paid resource is moved to the shopping cart 606, it indicates that the user agrees to purchase the target paid resource.

[0200] 3) In response to a gesture that triggers the purchase option for a paid resource, display the process of the purchase option for the paid resource being triggered by the palm model.

[0201] Optionally, a corresponding purchase option is displayed around the paid resource. The user can move the hand model to the purchase option by gesture and make gestures such as clicking or pressing. The client will then assume that the user agrees to purchase the paid resource.

[0202] 4) In response to a gesture indicating agreement to pay for a paid resource, the process of displaying the option to purchase the paid resource being selected by the palm model.

[0203] Optionally, the client displays a gesture trigger prompt to guide the user to perform the corresponding gesture, thus completing the purchase of the paid resource associated with that gesture. For example, if the gesture for the target paid resource is "OK," then after the user performs the "OK" gesture, the client assumes that the user agrees to purchase the target paid resource.

[0204] Step 503: Display a payment success notification, which indicates that the first resource and the paid resource have been successfully paid for.

[0205] Optionally, the payment process for the orders corresponding to the first resource and the paid resource can be completed by the backend service platform. For example, the client sends palm data, along with the orders corresponding to the first resource and the paid resource, to the backend service platform. Upon receiving the palm data, the backend service platform extracts features from the palm data to obtain palm feature information. Based on this feature information, it performs a full database search to identify the user account corresponding to the palm, and then processes the payment for the first resource and the paid resource for that user account.

[0206] In one example, the payment success notification includes a first sub-payment notification and a second sub-payment notification. The first sub-payment notification indicates that the first resource has been successfully paid for, and the second sub-payment notification indicates that the paid resource has been successfully paid for, so that the user can clearly know which orders have been paid for. Then, step 503 also includes the following:

[0207] 1. In response to the swipe operation used to pay for the first resource, generate the first payment order for the first resource.

[0208] Optionally, the first payment order is determined based on the amount and quantity of the first resource.

[0209] 2. In response to a gesture operation used to pay for a paid resource, generate a second payment order for the paid resource.

[0210] Optionally, a second payment order may be determined based on the amount and quantity of the paid resources. Optionally, each order may correspond to a unique order number, payment amount, and other information.

[0211] 3. Merge the first payment order and the second payment order to generate the total payment order.

[0212] Optionally, the total amount of the first payment order and the second payment order can be obtained, and then a total payment order can be generated based on the total amount.

[0213] 4. Send the total payment order to the backend service platform corresponding to the first swipe payment device.

[0214] After completing the total payment order, the backend service platform splits it into two separate payment success notifications: a first payment success notification and a second payment success notification. This accelerates the payment process and improves efficiency. The backend service platform then adds both notifications to a message queue to facilitate their transmission.

[0215] 5. Receive the first payment success notification and the second payment success notification from the backend service platform.

[0216] The client displays the first payment success notification and the second payment success notification respectively to inform the user that the payment for the first resource and the paid resource has been completed.

[0217] Optionally, the first payment success notification and the second payment success notification are also sent to the terminal device held by the user currently using the first swipe payment device, so that the user can view the specific order information.

[0218] Optionally, if the paid resource is displayed after the first payment order is completed, the backend service platform executes the payment processes for the first resource and the paid resource respectively. If the paid resource is displayed before the first payment order is generated, the client can directly include the paid resource in the first payment order, and the backend service platform can execute the payment process for the first payment order to complete the payment for the first resource and the paid resource.

[0219] Optionally, after the initial resource and paid resource have been paid for, the backend service platform will deliver the initial resource and paid resource to the user. For example, for paid emoticons, the backend service platform can add them to the emoticon list of the user's client; for paid articles, the backend service platform can push them to the user via WeChat official account messages to achieve delivery.

[0220] In some embodiments, reference Figure 10 and Figure 11The backend service platform 1001 integrates a palm recognition module, an order processing module, and an application module. These modules can also be implemented as sub-platforms, and this embodiment does not limit this implementation. The palm recognition module is used to identify the user account performing the payment operation. The order processing module executes the processing flow for payment orders. The application module provides backend services to the client in the terminal device 1002, such as emoji services and WeChat official account services.

[0221] The palm payment device 1003 integrates a long-connection communication module, a palm / gesture acquisition and recognition module, a configuration management module, and a payment merging module. The long-connection communication module establishes a long-term communication connection with the backend service platform 1001. The palm / gesture acquisition and recognition module collects palm data, and the configuration management module configures the paid resources based on the device configuration data. The payment merging module merges orders for the primary resource and the paid resource.

[0222] Optionally, in response to a user's palm-swiping operation on the palm payment device 1003, the palm payment device 1003 displays the paid resources and generates a first payment order. In response to the user's gesture matching the payment trigger instruction for the paid resources, a second payment order is generated. The palm payment device 1003 merges the first and second payment orders to generate a total payment order payment instruction, and sends this payment instruction and palm data to the backend service platform 1001. After processing the total payment order, the backend service platform 1001 pushes a payment success notification message and delivers the paid resources to the user's terminal device 1002.

[0223] In one example, to promptly push third-party configured device configuration data to the mobile payment device, this embodiment employs a highly available push message architecture. This architecture is responsible for receiving messages (such as device configuration data) and pushing them to the mobile payment device. To ensure high availability, this embodiment uses multiple push service instances and employs load balancing technology to distribute traffic (the traffic required for device configuration data) across different instances to achieve the push of device configuration data.

[0224] In addition, to ensure the reliability and persistence of messages (such as device configuration data), this embodiment also stores messages in a reliable data storage system, such as a relational database (e.g., SQLite database) or a distributed storage system. Furthermore, to improve message push performance, this embodiment also uses message queue technology to cache and asynchronously process messages (such as device configuration data, payment success notifications, configuration success notifications, etc.). Message queues can distribute message push tasks to multiple worker threads to improve the concurrency and throughput of message push.

[0225] In summary, the technical solution provided in this application, by displaying paid resources provided by a third-party platform during the user's palm payment process using a palm payment device, allows the user to simultaneously pay for paid resources while making a palm payment, which helps to improve the conversion rate of paid resources and the convenience of payment.

[0226] In addition, by supporting third-party platforms to configure the swipe payment device with related paid resources, the swipe payment device is no longer limited to swipe payment, which helps to improve the utilization rate and use value of the swipe payment device.

[0227] 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.

[0228] refer to Figure 12 This diagram illustrates a block diagram of a user apparatus for a palm-swipe payment device according to an embodiment of this application. The apparatus has the functionality to implement the method example described above; this functionality can be implemented in hardware or by hardware executing corresponding software. The apparatus can be the computer device described above, or it can be installed within a computer device. For example... Figure 12 As shown, the device 1200 includes: a paid resource display module 1201, a paid resource selection module 1202, and a payment notification display module 1203.

[0229] The paid resource display module 1201 is used to respond to the swipe operation for paying for the first resource and display the palm model and the paid resources provided by the third-party platform.

[0230] The paid resource selection module 1202 is used to display the process of the paid resource being selected by the palm model in response to a gesture operation for paying for the paid resource.

[0231] The payment notification display module 1203 is used to display a payment success notification, which indicates that the first resource and the paid resource have been successfully paid for.

[0232] In some embodiments, such as Figure 13 As shown, the paid resource display module 1201 includes: a palm data acquisition submodule 1201a, a palm model display submodule 1201b, and a paid resource display submodule 1201c.

[0233] The palm data acquisition submodule 1201a is used to acquire palm data in response to the palm swipe operation used to pay for the first resource.

[0234] The hand model display submodule 1201b is used to display the hand model based on the hand data.

[0235] The paid resource display submodule 1201c is used to display the paid resources according to the device configuration data; wherein, the device configuration data is obtained by the third-party platform based on the backend service platform corresponding to the first swipe payment device, and the device configuration data includes the identification information and resource deployment information of the first swipe payment device, and the resource deployment information is used to indicate the paid resources deployed by the third-party platform.

[0236] In some embodiments, the device configuration data further includes a payment trigger instruction, which is used to instruct an operation to trigger payment for the paid resources;

[0237] The paid resource display submodule 1201c is further configured to display payment trigger prompt information for the paid resource according to the payment trigger instruction of the paid resource, the payment trigger prompt information being used to prompt the operation of triggering payment for the paid resource; and to display the process of the paid resource being selected by the palm model in response to the gesture operation conforming to the payment trigger instruction of the paid resource.

[0238] In some embodiments, the paid resource selection module 1202 is used for:

[0239] In response to a gesture operation for grasping the paid resource, the process of displaying the paid resource being selected by the palm model is shown;

[0240] Alternatively, in response to a gesture operation for grasping the paid resource and moving the paid resource to a designated area, the process of the paid resource being selected and moved by the palm model is displayed.

[0241] Alternatively, in response to a gesture that triggers the purchase option for the paid resource, the process of the purchase option for the paid resource being triggered by the palm model is displayed;

[0242] Alternatively, in response to a gesture indicating agreement to pay for the paid resource, a process is performed to display the option to purchase the paid resource being selected by the hand model.

[0243] In some embodiments, the resource deployment information further includes background data and display method data;

[0244] The paid resource display submodule 1201c is further configured to display a background image related to the paid resource based on the background data, and to display the paid resource according to the display method corresponding to the display method data.

[0245] In some embodiments, the paid resource display submodule 1201c is further configured to, upon receiving device configuration data generated by different third-party platforms, sequentially display the paid resources provided by the different third-party platforms in the order in which the device configuration data is received.

[0246] In some embodiments, the payment success notification includes a first sub-payment notification and a second sub-payment notification, wherein the first sub-payment notification is used to indicate that the first resource has been successfully paid for, and the second sub-payment notification is used to indicate that the paid resource has been successfully paid for;

[0247] like Figure 13 As shown, the device 1200 further includes: a first order generation module 1204, a second order generation module 1205, a total order generation module 1206, a total order sending module 1207, and a payment notification receiving module 1208.

[0248] The first order generation module 1204 is used to generate a first payment order for the first resource in response to a swipe operation for payment of the first resource.

[0249] The second order generation module 1205 is used to generate a second payment order for the paid resource in response to a gesture operation for paying for the paid resource.

[0250] The total order generation module 1206 is used to merge the first payment order and the second payment order to generate a total payment order.

[0251] The total order sending module 1207 is used to send the total payment order to the backend service platform corresponding to the first palm payment device.

[0252] The payment notification receiving module 1208 is used to receive the first payment success notification and the second payment success notification from the backend service platform; wherein, the first payment success notification and the second payment success notification are also sent to the terminal device held by the user currently using the first palm payment device.

[0253] In summary, the technical solution provided in this application, by displaying paid resources provided by a third-party platform during the user's palm payment process using a palm payment device, allows the user to simultaneously pay for paid resources while making a palm payment, which helps to improve the conversion rate of paid resources and the convenience of payment.

[0254] In addition, by supporting third-party platforms to configure the swipe payment device with related paid resources, the swipe payment device is no longer limited to swipe payment, which helps to improve the utilization rate and use value of the swipe payment device.

[0255] refer to Figure 14 This diagram illustrates a block diagram of a configuration apparatus for a palm-swipe payment device according to an embodiment of this application. The apparatus has the functionality to implement the method example described above; this functionality can be implemented in hardware or by hardware executing corresponding software. The apparatus can be the computer device described above, or it can be installed within a computer device. For example... Figure 14 As shown, the device 1400 includes: a configuration interface display module 1401, a configuration data generation module 1402, and a configuration data sending module 1403.

[0256] The configuration interface display module 1401 is used to display the device configuration interface, which is used by third-party platforms to configure the palm payment device.

[0257] The configuration data generation module 1402 is used to generate device configuration data in response to the operation of configuring the first palm payment device. The device configuration data includes the identification information and resource allocation information of the first palm payment device. The resource allocation information is used to indicate the paid resources allocated by the third-party platform.

[0258] The configuration data sending module 1403 is used to send the device configuration data to the first-party platform, so that the device configuration data can be forwarded to the first swipe payment device through the first-party platform.

[0259] In some embodiments, the configuration data generation module 1402 is configured to:

[0260] The device configuration interface displays options for multiple paid resources, which are provided by the third-party platform.

[0261] In response to an operation for selecting an option among the plurality of paid resources, resource delivery information corresponding to the at least one paid resource is added to the device configuration data;

[0262] The device configuration interface displays options for multiple palm payment devices, and the payment clients in these multiple palm payment devices are provided with backend services by the backend service platform.

[0263] In response to an operation for selecting an option for the first palm payment device among the plurality of palm payment devices, the identification information of the first palm payment device is added to the device configuration data.

[0264] In some embodiments, the device configuration data further includes a payment trigger instruction, which is used to instruct a gesture operation to trigger payment for the paid resource; such as Figure 15As shown, the device 1400 further includes: an instruction option display module 1404 and a trigger instruction selection module 1405.

[0265] The instruction option display module 1404 is used to display multiple payment trigger instruction options in the device configuration interface, wherein the multiple payment trigger instructions are provided by the third-party platform.

[0266] The trigger instruction selection module 1405 is used to add the first payment trigger instruction into the device configuration data in response to an operation for selecting an option of the first payment trigger instruction among the plurality of payment trigger instructions.

[0267] In some embodiments, such as Figure 15 As shown, the device 1400 further includes a background data generation module 1406 and a mode data generation module 1407.

[0268] Background data generation module 1406 is used to generate background data in response to an operation for configuring a background image associated with the paid resource.

[0269] The mode data generation module 1407 is used to generate display mode data in response to an operation for configuring the display mode of the paid resources.

[0270] The configuration data generation module 1402 is also used to add the background data and the display mode data into the resource delivery information.

[0271] In some embodiments, such as Figure 15 As shown, the device 1400 further includes: a setting notification receiving module 1408 and a setting notification display module 1409.

[0272] The setting notification receiving module 1408 is used to receive a setting success notification from the backend service platform, which indicates that the first palm payment device has been successfully set up.

[0273] The notification display module 1409 is configured to display the setting success notification and forward the setting success notification to the third-party platform.

[0274] In summary, the technical solution provided in this application, by displaying paid resources provided by a third-party platform during the user's palm payment process using a palm payment device, allows the user to simultaneously pay for paid resources while making a palm payment, which helps to improve the conversion rate of paid resources and the convenience of payment.

[0275] In addition, by supporting third-party platforms to configure the swipe payment device with related paid resources, the swipe payment device is no longer limited to swipe payment, which helps to improve the utilization rate and use value of the swipe payment device.

[0276] 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.

[0277] Please refer to Figure 16 This diagram illustrates the structural block diagram of a computer device provided in one embodiment of this application. This computer device can be used to implement the configuration method or usage method of the palm payment device provided in the above embodiments, and may specifically include the following:

[0278] The computer device 1600 includes a central processing unit (such as a CPU, GPU, or FPGA) 1601, a system memory 1604 including RAM (Random-Access Memory) 1602 and ROM (Read-Only Memory) 1603, and a system bus 1605 connecting the system memory 1604 and the central processing unit 1601. The computer device 1600 also includes a basic input / output system 1606 to facilitate information transfer between various devices within the server, and a mass storage device 1607 for storing the operating system 1613, application programs 1614, and other program modules 1615.

[0279] The basic input / output system 1606 includes a display 1608 for displaying information and an input device 1609 for user input, such as a mouse or keyboard. Both the display 1608 and the input device 1609 are connected to the central processing unit 1601 via an input / output controller 1610 connected to the system bus 1605. The basic input / output system 1606 may also include the input / output controller 1610 for receiving and processing input from multiple other devices such as a keyboard, mouse, or electronic stylus. Similarly, the input / output controller 1610 also provides output to a display screen, printer, or other types of output devices.

[0280] The mass storage device 1607 is connected to the central processing unit 1601 via a mass storage controller (not shown) connected to the system bus 1605. The mass storage device 1607 and its associated computer-readable media provide non-volatile storage for the computer device 1600. That is, the mass storage device 1607 may include computer-readable media (not shown) such as a hard disk or a CD-ROM (Compact Disc Read-Only Memory) drive.

[0281] 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), EEPROM (Electrically Erasable Programmable Read-Only Memory), flash memory or other solid-state storage technologies, CD-ROM, DVD (Digital Video Disc) 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 medium is not limited to the above-mentioned types. The system memory 1604 and mass storage device 1607 described above can be collectively referred to as memory.

[0282] According to an embodiment of this application, the computer device 1600 can also be connected to a remote computer on a network, such as the Internet. That is, the computer device 1600 can be connected to the network 1612 via the network interface unit 1611 connected to the system bus 1605, or the network interface unit 1611 can be used to connect to other types of networks or remote computer systems (not shown).

[0283] The memory also includes a computer program stored in the memory and configured to be executed by one or more processors to implement the above-described configuration method or usage method of the palm payment device.

[0284] In some embodiments, a computer-readable storage medium is also provided, wherein a computer program is stored therein, which, when executed by a processor, implements the above-described configuration method or usage method of the palm payment device.

[0285] Optionally, the computer-readable storage medium may include: ROM (Read-Only Memory), RAM (Random-Access Memory), SSD (Solid State Drives), or optical disc, etc. The random access memory may include ReRAM (Resistance Random Access Memory) and DRAM (Dynamic Random Access Memory).

[0286] In some embodiments, a computer program product is also provided, the computer program product comprising a computer program stored in a computer-readable storage medium. A processor of a computer device reads the computer program from the computer-readable storage medium, and the processor executes the computer program, causing the computer device to perform the above-described configuration method or usage method of the palm-swiping payment device.

[0287] It should be noted that, in this application embodiment, before and during the collection of user-related data, a prompt interface, pop-up window, or voice prompt message can be displayed. This prompt interface, pop-up window, or voice prompt message is used to inform the user that their relevant data is being collected. This ensures that the application only begins executing the steps related to collecting user-related data after receiving confirmation from the user regarding the prompt interface or pop-up window; otherwise (i.e., without receiving confirmation from the user), the steps to collect user-related data end, meaning no user-related data is collected. In other words, all user data collected in this application is processed strictly in accordance with the requirements of relevant national laws and regulations. The informed consent or separate consent of the personal information subject is obtained only with the user's consent and authorization. Subsequent data use and processing are conducted within the scope of laws, regulations, and the authorization of the personal information subject. Furthermore, the collection, use, and processing of relevant user data must comply with the relevant laws, regulations, and standards of the relevant countries and regions. For example, user accounts, palm data, and gesture operations involved in this application are all obtained with full authorization.

[0288] It should be understood that "multiple" as used herein 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 are in an "or" relationship. Furthermore, the step numbers described herein are merely illustrative of one possible execution order. In some other embodiments, the steps may not be executed in numerical order, such as two steps with different numbers being executed simultaneously, or two steps with different numbers being executed in the reverse order of the illustration. This application does not limit this.

[0289] 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 of using a palm-swipe payment device, characterized in that, The method comprises: In response to a palm swiping operation for paying a first resource, a palm model is displayed; in a case where device configuration data generated by different third-party platforms is received, paid resources launched by the different third-party platforms are displayed according to display timing of the paid resources set by the third-party platforms; wherein the paid resources launched by the different third-party platforms are displayed in a sequence according to a receiving sequence of the device configuration data, or the paid resources launched by the different third-party platforms are synchronously displayed in a case where a space of a user interface of the palm swiping payment device is sufficient; the display timing comprises at least one of displaying the paid resources during a palm swiping process of a user, displaying the paid resources before the palm swiping of the user, and displaying the paid resources after the palm swiping payment of the user is successful; the paid resources comprise paid emoticons, paid articles, paid videos, paid goods, and paid images; and a display method of the paid resources comprises at least one of displaying the paid resources in a falling manner from top to bottom, randomly displaying the paid resources in an interface, and dynamically displaying the paid resources in a specified track in the interface; wherein display manners of different paid resources are the same or different; A gesture operation for the paid resources is received, the gesture operation is synchronous with a change of the palm model; According to a payment trigger instruction of the paid resources, payment trigger prompt information for the paid resources is displayed, the payment trigger instruction is an instruction pre-configured by the third-party platform for the paid resources, the payment trigger prompt information is used for prompting an operation of triggering payment of the paid resources, and a style of the payment trigger prompt information comprises a text style, an image style, and an animation style; wherein payment trigger instructions of different paid resources are the same or different; In response to a gesture operation for grabbing the paid resources, a process in which the paid resources are selected by the palm model is displayed; or in response to a gesture operation for grabbing the paid resources and moving the paid resources to a specified region, a process in which the paid resources are selected and moved by the palm model is displayed; the gesture operation conforms to the payment trigger instruction of the paid resources; and the specified region can be set and adjusted according to actual use requirements. In a case where the first resource and the paid resources are paid based on the palm swiping operation and the gesture operation, a first sub-payment notification and a second sub-payment notification are displayed, the first sub-payment notification is used for indicating that the first resource is successfully paid, and the second sub-payment notification is used for indicating that the paid resources are successfully paid.

2. The method of claim 1, wherein, The response to the palm swiping operation for paying the first resource, the display of the palm model, and the paid resources launched by the third-party platforms comprises: In response to the palm swiping operation for paying the first resource, palm data is acquired; According to the palm data, the palm model is displayed; According to the device configuration data, the paid resource is displayed; wherein the device configuration data is obtained by the third-party platform based on a backend service platform corresponding to the first palm payment device, and the device configuration data includes identification information of the first palm payment device and resource delivery information, and the resource delivery information is used to indicate the paid resource delivered by the third-party platform.

3. The method of claim 2, wherein, The device configuration data further includes the payment trigger instruction, and the payment trigger instruction is used to indicate triggering payment of the paid resource.

4. The method of claim 3, wherein, The method further includes: In response to a gesture operation for triggering a purchase option of the paid resource, a process in which the purchase option of the paid resource is triggered by the palm model is displayed; Or, In response to a gesture operation for agreeing to pay the paid resource, a process in which the purchase option of the paid resource is selected by the palm model is displayed.

5. The method of claim 2, wherein, The resource delivery information further includes background data and display mode data; According to the device configuration data, the paid resource is displayed, including: According to the background data, a background image related to the paid resource is displayed; According to a display mode corresponding to the display mode data, the paid resource is displayed.

6. The method of claim 1, wherein, Before the payment success notification is displayed, the method further includes: In response to a palm operation for paying the first resource, a first payment order for the first resource is generated; In response to a gesture operation for paying the paid resource, a second payment order for the paid resource is generated; The first payment order and the second payment order are combined to generate a total payment order; The total payment order is sent to a backend service platform corresponding to the first palm payment device; The first sub-payment notification and the second sub-payment notification are received from the backend service platform; wherein the first sub-payment notification and the second sub-payment notification are also sent to a terminal device held by a user currently using the first palm payment device.

7. A configuration method of a brush palm payment device, characterized by, The method includes: A device configuration interface is displayed, and the device configuration interface is used for the third-party platform to configure the palm payment device; In response to an operation for configuring the first palm payment device, device configuration data is generated, and the device configuration data includes identification information of the first palm payment device and resource delivery information, and the resource delivery information is used to indicate the paid resource delivered by the third-party platform; The device configuration data is sent to a backend service platform, so that the device configuration data is forwarded to the first palm payment device by the backend service platform. The first palm payment device is configured to display a palm model based on a palm operation of paying for a first resource, and is further configured to, in a case where device configuration data generated by different third-party platforms is received, display paid resources provided by the different third-party platforms according to display timing of the paid resources set by the third-party platforms; the display of the paid resources provided by the different third-party platforms is performed in a sequence according to a receiving order of the device configuration data, or, in a case where a user interface of the palm payment device has sufficient space, the paid resources provided by the different third-party platforms are displayed synchronously; the display timing includes at least one of displaying the paid resources during a palm operation of a user, displaying the paid resources before the palm operation of the user, and displaying the paid resources after the palm operation of the user is successful; the paid resources include paid emoticons, paid articles, paid videos, and paid goods; the display method of the paid resources includes at least one of displaying the paid resources in a falling manner from top to bottom, displaying the paid resources randomly in the interface, and displaying the paid resources dynamically in the interface according to a specified track; the display methods of different paid resources are the same or different; the first palm payment operation is further configured to receive a gesture operation for the paid resources, and the gesture operation changes synchronously with the palm model; the first palm payment device is further configured to display payment trigger prompt information for the paid resources according to a payment trigger instruction of the paid resources, the payment trigger instruction being an instruction preconfigured by the third-party platform for the paid resources, and the payment trigger prompt information being used to prompt an operation of triggering payment of the paid resources; the style of the payment trigger prompt information includes a text style, an image style, and an animation style; the payment trigger instructions of different paid resources are the same or different; the first palm payment device is further configured to, in response to a gesture operation of grabbing the paid resources, display a process in which the paid resources are selected by the palm model; or, in response to a gesture operation of grabbing the paid resources and moving the paid resources to a specified area, display a process in which the paid resources are selected and moved by the palm model; the gesture operation meets the payment trigger instruction of the paid resources; the specified area can be set and adjusted according to actual use requirements; the first palm payment device is further configured to, in a case where the first resource and the paid resources are paid based on the palm operation and the gesture operation, display a first sub-payment notification and a second sub-payment notification, the first sub-payment notification being used to indicate that the first resource is paid successfully, and the second sub-payment notification being used to indicate that the paid resources are paid successfully; a payment success notification is displayed, and the payment success notification is used to indicate that the first resource and the paid resources are paid successfully.

8. The method of claim 7, wherein, The device configuration data is generated in response to an operation of configuring the first palm payment device, and includes: In the device configuration interface, options of a plurality of paid resources are displayed, and the plurality of paid resources are provided by the third-party platforms. in response to an operation for selecting an option of the at least one of the plurality of paid resources, adding resource placement information corresponding to the at least one of the plurality of paid resources into the device configuration data; displaying, in the device configuration interface, options of a plurality of palm payment devices, a payment client in the plurality of palm payment devices being provided with background service by the backend service platform; in response to an operation for selecting an option of the first palm payment device in the plurality of palm payment devices, adding identification information of the first palm payment device into the device configuration data.

9. The method of claim 7, wherein, The device configuration data further includes payment trigger instructions for instructing a gesture operation for triggering payment of the paid resource; and the method further includes: displaying, in the device configuration interface, options of a plurality of payment trigger instructions, the plurality of payment trigger instructions being provided by the third-party platform; in response to an operation for selecting an option of a first payment trigger instruction in the plurality of payment trigger instructions, adding the first payment trigger instruction into the device configuration data.

10. The method of claim 7, wherein, after generating the device configuration data in response to the operation for configuring the first palm payment device, the method further includes: in response to an operation for configuring a background image related to the paid resource, generating background data; in response to an operation for configuring a display mode of the paid resource, generating display mode data; adding the background data and the display mode data into the resource placement information.

11. The method of claim 7, wherein, after sending the device configuration data to the backend service platform to forward the device configuration data to the first palm payment device through the backend service platform, the method further includes: receiving a setting success notification from the backend service platform, the setting success notification being used to indicate that the first palm payment device is set successfully; displaying the setting success notification and forwarding the setting success notification to the third-party platform.

12. A device for using a brush palm payment device, characterized by, The apparatus includes: The payment resource display module is configured to display a palm model in response to a palm swiping operation for paying for a first resource; and display payment resources launched by different third-party platforms according to display timing of the payment resources set by the third-party platforms in a case where device configuration data generated by the different third-party platforms is received; wherein the payment resources launched by the different third-party platforms are displayed in a sequence according to a receiving order of the device configuration data, or the payment resources launched by the different third-party platforms are synchronously displayed in a case where a user interface of the palm swiping payment device has sufficient space; the display timing includes at least one of displaying the payment resources during palm swiping of a user, displaying the payment resources before palm swiping of the user, and displaying the payment resources after palm swiping payment of the user is successful; the payment resources include payment emoticons, payment articles, payment videos, and payment goods; and a display method of the payment resources includes at least one of displaying the payment resources in a falling manner from top to bottom, displaying the payment resources randomly in an interface, and dynamically displaying the payment resources in a specified track in the interface; wherein display methods of different payment resources are the same or different. The payment resource selection module is configured to receive a gesture operation for the payment resources, the gesture operation being changed synchronously with the palm model; display payment trigger prompt information for the payment resources according to a payment trigger instruction of the payment resources, the payment trigger instruction being an instruction preconfigured by the third-party platform for the payment resources, the payment trigger prompt information being used to prompt an operation of triggering payment of the payment resources, and a style of the payment trigger prompt information including a text style, an image style, and an animation style; wherein payment trigger instructions of different payment resources are the same or different; display a process in which the payment resources are selected by the palm model in response to a gesture operation for grabbing the payment resources; or display a process in which the payment resources are selected and moved by the palm model in response to a gesture operation for grabbing the payment resources and moving the payment resources to a specified region; the gesture operation conforms to the payment trigger instruction of the payment resources; and the specified region can be set and adjusted according to actual use requirements. The payment notification display module is configured to display a first sub-payment notification and a second sub-payment notification in a case where the first resource and the payment resources are paid based on the palm swiping operation and the gesture operation; the first sub-payment notification is used to indicate that the first resource is successfully paid; and the second sub-payment notification is used to indicate that the payment resources are successfully paid.

13. A configuration device of a brush palm payment apparatus, characterized by, The device includes: A configuration interface display module configured to display a device configuration interface, the device configuration interface being used for a third-party platform to configure a palm swiping payment device; A configuration data generation module configured to generate device configuration data in response to an operation for configuring a first palm swiping payment device, the device configuration data including identification information of the first palm swiping payment device and resource launch information, the resource launch information being used to indicate payment resources launched by the third-party platform. The configuration data sending module is configured to send the device configuration data to the first-party platform, so as to forward the device configuration data to the first palm payment device through the first-party platform. The first palm payment device is configured to display a palm model based on a palm payment operation of a first resource, and is further configured to, in a case where device configuration data generated by different third-party platforms is received, display paid resources launched by the different third-party platforms according to display timing of the paid resources set by the third-party platforms; wherein the paid resources launched by the different third-party platforms are displayed in a sequence of receipt of the device configuration data, or, in a case where a space of a user interface of the palm payment device is sufficient, the paid resources launched by the different third-party platforms are displayed synchronously; the display timing includes at least one of displaying the paid resources during a palm operation of a user, displaying the paid resources before the palm operation of the user, and displaying the paid resources after the palm payment operation of the user is successful; the paid resources include paid emoticons, paid articles, paid videos, and paid goods; the display method of the paid resources includes at least one of displaying the paid resources in a falling manner from top to bottom, displaying the paid resources randomly in the interface, and displaying the paid resources dynamically in the interface in a specified track; wherein the display methods of different paid resources are the same or different; the first palm payment operation is further configured to receive a gesture operation for the paid resources, and the gesture operation changes synchronously with the palm model; the first palm payment device is further configured to display payment trigger prompt information for the paid resources according to a payment trigger instruction of the paid resources, the payment trigger instruction being an instruction preconfigured by the third-party platform for the paid resources, and the payment trigger prompt information being used to prompt an operation of triggering payment of the paid resources; a style of the payment trigger prompt information includes a text style, an image style, and an animation style; wherein the payment trigger instructions of different paid resources are the same or different; the first palm payment device is further configured to, in response to a gesture operation for grabbing the paid resources, display a process in which the paid resources are selected by the palm model; or, in response to a gesture operation for grabbing the paid resources and moving the paid resources to a specified area, display a process in which the paid resources are selected and moved by the palm model; the gesture operation complies with the payment trigger instruction of the paid resources; the specified area can be set and adjusted according to actual use requirements; the first palm payment device is further configured to, in a case where the first resource and the paid resources are paid based on combination of the palm operation and the gesture operation, display a first payment notification and a second payment notification, the first payment notification being used to indicate that the first resource is paid successfully, and the second payment notification being used to indicate that the paid resources are paid successfully; and a payment success notification is displayed, the payment success notification being used to indicate that the first resource and the paid resources are paid successfully.

14. A computer device, comprising: The computer device comprises a processor and a memory, and the memory stores a computer program which is loaded and executed by the processor to implement the use method of the palm swiping payment device according to any one of claims 1 to 6, or the configuration method of the palm swiping payment device according to any one of claims 7 to 11.

15. A computer-readable storage medium, characterized in that, The computer readable storage medium stores a computer program which is loaded and executed by the processor to implement the use method of the palm swiping payment device according to any one of claims 1 to 6, or the configuration method of the palm swiping payment device according to any one of claims 7 to 11.

16. A computer program product, characterised in that, The computer program product comprises a computer program stored in a computer readable storage medium, and the processor reads and executes the computer program from the computer readable storage medium to implement the use method of the palm swiping payment device according to any one of claims 1 to 6, or the configuration method of the palm swiping payment device according to any one of claims 7 to 11.

Images