Message sending method, message processing method, message processing system and device

Abstract

The invention discloses a message sending method, a message processing method and a message processing system and device, and relates to the field of financial science and technology. The method comprises the following steps: acquiring a target merchant number through a message pushing component; determining a geographic position of a collection terminal of the target merchant through a message pushing component; determining a target message receiving component of the to-be-received message according to the geographic position of the collection terminal and the target merchant number through a message pushing component; establishing a data connection between the message pushing component and the target message receiving component; and sending a user payment result determined by the collection terminal to a target message receiving component through a message pushing component according to the data connection. The technical problem that a merchant cashier cannot obtain a collection notification through voice or the collection notification is delayed due to the fact that a data transmission link of transaction information is too long in the prior art is solved.

Description

Technical Field

[0001] The present application relates to the field of financial technology, and specifically, to a message sending method, a message processing method, a message processing system and a device. Background Art

[0002] In the current payment ecosystem, with the popularity of mobile payment, merchant voice broadcast APP is widely used in retail, catering and other industries as a convenient payment notification tool. However, the traditional voice broadcast notification mechanism relies on a multi-layer data transmission link, from the acquiring system to the merchant voice broadcast APP, it needs to pass through multiple backend systems and network nodes. This link usually includes the acquiring system sending the payment result to the message service node, and the message service node pushes the transaction information in text form to the merchant voice broadcast APP through the network, and finally the APP reads and converts it into a voice notification.

[0003] In this complex data transmission process, any abnormality in any link, such as network fluctuations, server failures or system delays, may interrupt or delay the transmission of transaction information. This risk not only affects the immediacy of payment confirmation, but may also cause merchant cashiers to miss important collection notifications, thereby affecting the merchant's operating efficiency and the customer's payment experience. Especially during peak hours, a large number of payment transactions occur intensively, the pressure on the backend system to process messages increases, and the delay problem of message push becomes more prominent, becoming a key bottleneck restricting the efficiency of the payment process.

[0004] To address the above-mentioned problems, no effective solution has been proposed yet. Summary of the invention

[0005] The present application provides a message sending method, a message processing method, a message processing system and a device, so as to at least solve the technical problem in the prior art that due to the long data transmission link of transaction information, an abnormality may occur in any link, which may cause the risk that the message cannot be sent to the merchant's mobile client, resulting in the merchant's cashier being unable to obtain the collection notification by voice, or the collection notification is delayed.

[0006] According to one aspect of the present application, a message sending method is provided, including: obtaining a target merchant number through a message push component, wherein the target merchant number is a merchant identifier assigned to the message push component by the target merchant's payment terminal after detecting that a user scans a payment graphic code; determining the geographical location of the target merchant's payment terminal through the message push component; determining, through the message push component, a target message receiving component to receive a message based on the geographical location of the payment terminal and the target merchant number; establishing a data connection between the message push component and the target message receiving component; and sending, through the message push component, a user payment result determined by the payment terminal to the target message receiving component based on the data connection, wherein the target message receiving component is used to generate voice information based on the user payment result.

[0007] Optionally, the geographic location of the target merchant's payment terminal is determined through a message push component, including: sending a location acquisition request to the target merchant's payment terminal through the message push component, wherein the location acquisition request is used to request the payment terminal to open location determination authority to the message push component; after detecting that the payment terminal agrees to the location acquisition request, reading the geographic location of the payment terminal through the message push component.

[0008] Optionally, a target message receiving component for receiving a message is determined according to the geographic location of the payment terminal through a message push component, including: obtaining access rights to a map software program built into the payment terminal through the message push component; according to the map software program, taking the geographic location of the payment terminal as the center position, expanding a preset distance along a target direction and / or a target angle to obtain a search range; determining N message receiving components that carry merchant numbers within the search range as N alternative message receiving components, wherein N is an integer greater than or equal to 1; and determining the target message receiving component from the N alternative message receiving components according to the target merchant number.

[0009] Optionally, a target message receiving component is determined from N alternative message receiving components according to the target merchant number, including: sending the target merchant number to N alternative message receiving components through a message push component, wherein each alternative message receiving component verifies whether the merchant number it carries is the target merchant number, and sends the verification result to the message push component; through the message push component, the alternative message receiving component that reports that the merchant number it carries is the target merchant number is used as the target message receiving component.

[0010] Optionally, establishing a data connection between the message push component and the target message receiving component includes: sending a request to establish a data connection to the target message receiving component through the message push component; after receiving a reply message from the target message receiving component agreeing to establish the data connection, establishing a data connection between the message push component and the target message receiving component.

[0011] Optionally, after sending the user payment result determined by the payment terminal to the target message receiving component according to the data connection through the message push component, the message sending method also includes: after determining that the target message receiving component has received the user payment result, disconnecting the data connection through the message push component.

[0012] According to another aspect of the present application, a message processing method is also provided, including: receiving a target merchant number sent by a message push component through a target message receiving component, and establishing a data connection between the message push component and the target message receiving component, wherein the target merchant number is a merchant identifier assigned to the message push component by the target merchant's payment terminal after detecting that a user has scanned a payment graphic code; the target message receiving component is determined by the geographic location of the payment terminal and the target merchant number; receiving, through the target message receiving component, a user payment result determined by the payment terminal and sent by the message push component based on the data connection; and generating a voice message based on the user payment result through the target message receiving component.

[0013] According to another aspect of the present application, a message processing system is also provided, including: a payment terminal, which is used to send a target merchant code to a message push component after detecting that a user scans a payment graphic code, wherein the target merchant code is a merchant identifier of the target merchant; a message push component, which is used to determine the geographic location of the payment terminal, and determine a target message receiving component to receive the message based on the geographic location of the payment terminal and the target merchant number; a target message receiving component, which is used to establish a data connection with the message push component, and receive the user payment result determined by the payment terminal and sent by the message push component based on the data connection, and generate voice information based on the user payment result.

[0014] According to another aspect of the present application, a message sending device is also provided, including: a first acquisition unit, which acquires a target merchant number through a message push component, wherein the target merchant number is a merchant identifier assigned to the message push component by the target merchant's payment terminal after detecting that a user scans a payment graphic code; a first determination unit, which determines the geographical location of the target merchant's payment terminal through the message push component; a second determination unit, which determines a target message receiving component to receive a message according to the geographical location of the payment terminal and the target merchant number through the message push component; a first establishment unit, which establishes a data connection between the message push component and the target message receiving component; a third determination unit, which sends the user payment result determined by the payment terminal to the target message receiving component through the message push component according to the data connection, wherein the target message receiving component is used to generate voice information based on the user payment result.

[0015] According to another aspect of the present application, a message sending device is also provided, including: a sending unit, which receives a target merchant number sent by a message push component through a target message receiving component, and establishes a data connection between the message push component and the target message receiving component, wherein the target merchant number is a merchant identifier assigned to the message push component by the payment terminal of the target merchant after detecting that the user scans a payment graphic code; the target message receiving component is determined by the geographic location of the payment terminal and the target merchant number; a receiving unit, which receives, through the target message receiving component, a user payment result determined by the payment terminal and sent by the message push component based on the data connection; and a generating unit, which generates voice information based on the user payment result through the target message receiving component.

[0016] According to another aspect of the present application, a computer-readable storage medium is provided, the computer-readable storage medium including a stored executable program, wherein when the executable program is executed, the device where the computer-readable storage medium is located is controlled to execute the above method.

[0017] According to another aspect of the present application, an electronic device is also provided, comprising one or more processors and a memory, wherein the memory is used to store one or more programs, wherein when the one or more programs are executed by the one or more processors, the one or more processors execute the above-mentioned message sending method or the above-mentioned message processing method.

[0018] According to another aspect of the present application, a computer program product is also provided, comprising computer instructions, which implement the steps of the above method when executed by a processor.

[0019] In the present application, firstly, the target merchant number is obtained through the message push component, wherein the target merchant number is the merchant identifier assigned to the message push component by the payment terminal of the target merchant after detecting that the user scans the payment graphic code. Secondly, the geographical location of the payment terminal of the target merchant is determined through the message push component. Then, the target message receiving component to receive the message is determined through the message push component according to the geographical location of the payment terminal and the target merchant number, and then a data connection between the message push component and the target message receiving component is established. Finally, the user payment result determined by the payment terminal is sent to the target message receiving component through the message push component according to the data connection, wherein the target message receiving component is used to generate voice information based on the user payment result, that is, through the point-to-point instant communication mechanism, the purpose of shortening the transaction information transmission path is achieved, thereby realizing the technical effect of instant and accurate voice payment notification, thereby solving the risk that the message cannot be sent to the merchant's mobile client due to an abnormality in any link caused by the data transmission link of the transaction information in the prior art, resulting in the merchant cashier being unable to obtain the payment notification through voice, or the payment notification is delayed. BRIEF DESCRIPTION OF THE DRAWINGS

[0020] The drawings described herein are used to provide a further understanding of the present application and constitute a part of the present application. The illustrative embodiments of the present application and their descriptions are used to explain the present application and do not constitute an improper limitation on the present application. In the drawings:

[0021] Figure 1 is a flowchart of an optional message sending method according to an embodiment of the present application;

[0022] Figure 2 It is a schematic diagram of an optional structure of a cashier station H5 according to an embodiment of the present application;

[0023] Figure 3 It is a schematic diagram of an optional merchant voice broadcast APP structure according to an embodiment of the present application;

[0024] Figure 4 It is a schematic diagram of an optional merchant logging into a merchant voice broadcast APP according to an embodiment of the present application;

[0025] Figure 5 is a schematic diagram of an optional handshake connection in the customer payment phase according to an embodiment of the present application;

[0026] Figure 6 is a schematic diagram of an optional message broadcast at the customer payment stage according to an embodiment of the present application;

[0027] Figure 7 is a flowchart of an optional message processing method according to an embodiment of the present application;

[0028] Figure 8 is a schematic diagram of an optional message sending device according to an embodiment of the present application;

[0029] Fig. 9 It is a schematic diagram of an optional message processing device according to an embodiment of the present application. DETAILED DESCRIPTION

[0030] In order to enable those skilled in the art to better understand the solution of the present application, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of the present application.

[0031] It should be noted that the terms "first", "second", etc. in the specification and claims of the present application and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchangeable where appropriate, so that the embodiments of the present application described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any of their variations are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device comprising a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0032] It should be noted that the collected information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data for display, data for analysis, etc.) involved in this application are information and data authorized by the user or fully authorized by all parties, and the collection, storage, use, processing, transmission, provision, disclosure and application of relevant data are in compliance with relevant laws, regulations and standards, necessary confidentiality measures are taken, and public order and good customs are not violated, and corresponding operation entrances are provided for users to choose to authorize or refuse. For example, an interface is set up between this system and relevant users or institutions to provide users with corresponding operation entrances for users to choose to agree or refuse the results of automated decision-making; if the user chooses to refuse, the expert decision-making process will be entered.

[0033] According to an embodiment of the present application, a method embodiment of a message sending method is provided. It should be noted that the steps shown in the flowchart of the accompanying drawings can be executed in a computer system such as a set of computer executable instructions, and although a logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in an order different from that shown here.

[0034] Figure 1 is a flowchart of an optional message sending method according to an embodiment of the present application, such as Figure 1 As shown, the method comprises the following steps:

[0035] Step S101, obtaining the target merchant ID through the message push component.

[0036] In step S101, the target merchant number is the merchant identifier assigned to the message push component by the payment terminal of the target merchant after detecting that the user scans the payment graphic code.

[0037] It should be noted that the message push component can be used as the execution subject of the message sending method of the embodiment of the present application. It is understandable that the message sending method provided in the embodiment of the present application can also be executed by other systems or devices, and the embodiment of the present application does not specifically limit this.

[0038] Optionally, the message push component can be an SDK (Software Development Kit) integrated in the acquiring and cashier H5 (a web application provided by the acquiring institution and embedded in the merchant's payment QR code), where the acquiring and cashier refers to the acquiring institution's payment H5 called by the payment APP when the customer scans the merchant's payment QR code, and the customer enters the amount and payment password in the payment H5 page and submits it to complete the payment.

[0039] Optionally, the target merchant number is a unique identifier of a specific merchant in a payment transaction, and is key information for matching the message push component and the message receiving component.

[0040] Step S102: determining the geographical location of the payment terminal of the target merchant through the message push component.

[0041] Optionally, before the customer completes the payment, the message push component obtains the location information of the payment terminal in real time by calling the mobile phone map location permission. This step is used to narrow the search range so that the message push component can quickly locate the target message receiving component.

[0042] Step S103, through the message push component, the target message receiving component to receive the message is determined according to the geographical location of the payment terminal and the target merchant number.

[0043] Optionally, through the message push component, a nearby target message receiving component is determined according to the geographical location of the payment terminal and the target merchant number.

[0044] Optionally, the target message receiving component can be integrated into the merchant voice broadcast APP. After the customer completes a payment at the merchant, the payment result is notified to the merchant's acquiring institution. After the acquiring institution completes the main process of the acquiring transaction, the transaction result is sent to the merchant voice broadcast APP installed on the merchant's mobile phone. At the same time, the acquiring institution system backend pushes a broadcast notification to the merchant voice broadcast APP, informing the merchant that the payment has been completed and the payment amount.

[0045] Step S104: establishing a data connection between the message push component and the target message receiving component.

[0046] Optionally, after identifying the target message receiving component, the message push component sends a handshake connection request, and after the target message receiving component responds, the two parties establish a data connection. It should be noted that this connection is point-to-point and is established directly between the front ends, avoiding possible delays or failures in the transmission of the background system, and improving the efficiency and reliability of information transmission.

[0047] Step S105: Through the message push component, the user payment result determined by the payment terminal is sent to the target message receiving component according to the data connection.

[0048] In step S105, the target message receiving component is used to generate voice information according to the user payment result.

[0049] Optionally, once the data connection is established, the message push component pushes the payment success information, including the payment result and the payment amount, to the target message receiving component through the data connection. After receiving the information, the target message receiving component generates a voice broadcast message based on the payment result to inform the merchant cashier that the transaction is completed and the specific amount, thus realizing an instant voice notification function.

[0050] Optionally, Figure 2 is a schematic diagram of an optional structure of a cashier station H5 according to an embodiment of the present application, such as Figure 2As shown, the acquiring and cashiering station H5 integrates modules such as password input module, encryption module, message sending module, other modules (functional modules), and message push SDK. Among them, the password input module is mainly responsible for the customer's password input during the payment process. After the customer completes the purchase of goods or services, he needs to enter the payment password or confirm the payment amount on the acquiring and cashiering station H5 to complete the payment process; the encryption module is used to encrypt the payment information (including the payment amount and payment password) entered by the customer to ensure the security of sensitive information during transmission. Encryption is an important step in network security to prevent information from being intercepted or tampered with by a third party during transmission; after completing the payment confirmation, the message sending module is responsible for constructing and sending transaction messages containing payment results and payment amounts. These messages will be sent to the message push SDK for further processing and push; other modules represent other functional modules in the acquiring and cashiering station H5 except for the above three modules. They may include user interface management, payment confirmation logic, error handling and other functions to ensure the normal operation of the acquiring and cashiering station H5 and the smooth completion of the payment process; the message push SDK is integrated in the acquiring and cashiering station The software development kit in the cash register H5 is used to implement the point-to-point message push function. It includes the following key functions: Set the merchant number: The message push SDK needs to set the target merchant number first in order to correctly push the message to the target merchant's payment terminal, obtain the mobile phone location: In order to ensure that the message can be pushed to the correct payment terminal, the SDK needs to obtain the real-time geographic location information of the mobile phone where the cash register H5 is located in real time, send a handshake connection request: The SDK will send a handshake connection request to the nearby merchant voice broadcast APP to find the payment terminal related to the current payment transaction, create a connection: After receiving the consent response from the merchant voice broadcast APP, the message push SDK creates a communication connection with the target message receiving SDK, prepares the necessary communication link for message push, and pushes the message broadcast message: Finally, the message push SDK pushes the message including the payment result and payment amount to the target message receiving SDK, which is used to generate a voice notification in the merchant voice broadcast APP.

[0051] Optionally, Figure 3 is a schematic diagram of an optional merchant voice broadcast APP structure according to an embodiment of the present application, such as Figure 3As shown, the schematic diagram includes a login module, a voice broadcast module, a message receiving module, other modules, and a message receiving SDK. Among them, the login module is the entrance to the merchant voice broadcast APP, allowing the merchant cashier to log in and access the functions in the APP by entering a username and password. The login module ensures that only authorized users can use the APP, thereby improving the security of the system; Voice broadcast module: After receiving the transaction information, the voice broadcast module converts the payment result into a voice notification so that the merchant cashier can hear the payment confirmation immediately. This module uses speech synthesis technology or preset voice files to generate corresponding voice information according to the payment status and amount; Message receiving module: Responsible for receiving transaction messages pushed by the message push SDK in the acquiring cashier H5. The message receiving module is the receiving end of the communication between the message receiving SDK and the cashier, ensuring that the transaction information can be captured and processed by the APP; Message receiving module: Responsible for receiving transaction messages pushed by the message push SDK in the acquiring cashier H5. The message receiving module is the receiving end of the communication between the message receiving SDK and the cashier, ensuring that the transaction information can be captured and processed by the APP Management; Message receiving SDK: It is a key component in the merchant voice broadcast APP, used to realize the front-end point-to-point transaction information reception. Its functions include: Setting the merchant number: The message receiving SDK needs to match the merchant number in the message push SDK to ensure that the received information is for the current merchant, obtaining the mobile phone location: Similar to the message push SDK, the message receiving SDK also needs to obtain the geographical location information of the mobile phone in real time to determine the identity of the recipient when the cashier H5 sends a connection request, answering the connection request: When receiving the connection request from the message push SDK, the message receiving SDK will check the merchant number in the request, and if it matches, it will answer yes, otherwise it will refuse the connection, receiving the broadcast message: Once the connection is established with the message push SDK, the message receiving SDK will receive the transaction message containing the payment result and the payment amount, calling the broadcast module voice broadcast: Finally, the message receiving SDK sends the received payment result to the voice broadcast module, generates a voice notification and plays it to the merchant cashier.

[0052] Optionally, Figure 4 is a schematic diagram of an optional merchant logging into a merchant voice broadcast APP according to an embodiment of the present application, such as Figure 4As shown, the first step: the merchant cashier enters the username and password. This is the beginning of the login process. The user is required to enter his or her registered account and password on the merchant voice broadcast APP to verify his or her identity. This is the first line of defense to ensure that only authorized cashiers can access the APP functions; the second step: call the message receiving SDK method to assign the merchant number of the SDK: once the identity authentication is successful, the merchant voice broadcast APP will call the corresponding method in the message receiving SDK to set the merchant number of the APP. This step is the key to point-to-point communication and ensures that the transaction information associated with the merchant number can be received later; the third step: apply for mobile phone location permission: in order to support location-based communication, the APP needs to obtain the map positioning permission of the mobile phone, which requires the cashier to agree that the APP can access his or her location information so that When receiving a transaction notification, the recipient can be determined based on the geographic location; Step 4: Agree to obtain mobile phone location permissions: The cashier needs to explicitly agree to the APP to obtain location information to ensure that the APP follows the user's wishes when processing sensitive information; Step 5: Real-time acquisition of the mobile phone's location: Once the location permission is obtained, the APP will track and update the location of the mobile phone in real time. This is to quickly identify the nearby merchant cashier after the customer completes the payment, and push voice broadcast transaction notifications to them; Step 6: Activate the receiving connection request interface: After completing all the above settings, the message receiving SDK will be in a listening state, ready to receive connection requests from the acquiring cashier H5 message push SDK. This is a preparatory step for establishing a point-to-point communication link to ensure that the cashier can instantly receive transaction notifications from the payment site.

[0053] It can be seen from the contents of steps S101 to S105 that in the present application, firstly, the target merchant number is obtained through the message push component, wherein the target merchant number is the merchant identifier assigned to the message push component by the payment terminal of the target merchant after detecting that the user scans the payment graphic code. Secondly, the geographical location of the payment terminal of the target merchant is determined through the message push component. Then, the target message receiving component to receive the message is determined through the message push component according to the geographical location of the payment terminal and the target merchant number, and then a data connection between the message push component and the target message receiving component is established. Finally, the message push component is used to send the user payment result determined by the payment terminal to the target message receiving component according to the data connection, wherein the target message receiving component is used to generate voice information based on the user payment result, that is, through the point-to-point instant communication mechanism, the purpose of shortening the transaction information transmission path is achieved, thereby achieving the technical effect of instant and accurate voice payment notification, thereby solving the technical problem that the data transmission link of the transaction information is too long in the prior art, resulting in an abnormality in any link, which will cause the risk that the message cannot be sent to the merchant's mobile client, resulting in the merchant cashier being unable to obtain the payment notification through voice, or the payment notification is delayed.

[0054] In an optional embodiment, a location acquisition request is sent to the target merchant's payment terminal through a message push component, wherein the location acquisition request is used to request the payment terminal to open location determination authority to the message push component, and after detecting that the payment terminal agrees to the location acquisition request, the geographic location of the payment terminal is read through the message push component.

[0055] Optionally, before the customer starts the payment process, the message push component will send a location acquisition request to the target merchant's payment terminal. This request is implemented by calling the positioning function module in the acquiring and cashiering platform H5. Its purpose is to start the positioning service of the payment terminal and obtain its current geographical location information, so that after the payment is successful, it can quickly locate the target message receiving component that is close to the geographical location of the payment terminal.

[0056] Optionally, after the message push component sends a location acquisition request to the target merchant's payment terminal, the payment terminal will decide whether to agree to open the location determination permission to the message push component. This is achieved through the location permission management mechanism provided by the mobile phone operating system. While ensuring user privacy, it also allows the application to obtain necessary geographic location information. After detecting that the payment terminal agrees to the location acquisition request, the message push component will detect this consent signal. The detection mechanism is usually implemented through a callback function or listener. Once the payment terminal agrees, the message push component will begin to obtain its geographic location information in real time.

[0057] As can be seen from the above content, at the beginning of payment, the message push component sends a location acquisition request to the payment terminal, requesting access to its location determination authority, and reads its geographic location after the payment terminal agrees, realizing the accurate acquisition of geographic location in the front-end point-to-point message transmission mechanism. This process ensures that the message push component can accurately identify the target message receiving component with a geographical location close to the payment terminal, so that it can immediately push a voice broadcast message to it after the payment is successful, improving the immediacy and accuracy of the payment notification, while effectively avoiding the delay and stability problems that may be encountered in the transmission of the background system.

[0058] In an optional embodiment, the access permission of the map software program built into the payment terminal is obtained through the message push component, and then according to the map software program, the geographical location of the payment terminal is used as the center position, and a preset distance is expanded along the target direction and / or target angle to obtain a search range, and N message receiving components that carry merchant numbers within the search range are determined as N alternative message receiving components, where N is an integer greater than or equal to 1, and then the target message receiving component is determined from the N alternative message receiving components according to the target merchant number.

[0059] Optionally, when the customer starts the payment process, that is, after scanning the merchant's payment QR code, the message push component integrated in the cashier H5 will immediately request permission to access the map software program built into the payment terminal. This request is intended to obtain location services so that the exact geographic location of the payment terminal can be determined later. The access permission of the map software program is the basis for implementing point-to-point message push, which allows the message push component to obtain mobile phone location information in real time, which is a prerequisite for implementing subsequent functions.

[0060] Optionally, after obtaining the location service permission, the message push component will build a search range based on the current geographic location of the payment terminal as the center, and expand a certain preset distance along the preset target direction and / or target angle. This search range is dynamic and can be parameterized according to the actual application scenario. For example, it may be set to a smaller range in a busy commercial area, and a larger range in an open area. The definition of the search range ensures that the message push component can efficiently search for nearby target message receiving components, reduce unnecessary searches and connection establishment, and improve the system's response speed and resource utilization efficiency. After defining the search range, the message push component will search for all N message receiving components carrying valid merchant numbers within the range, and use them as alternative message receiving components. Finally, the message push component will filter out the only target message receiving component from the N alternative message receiving components based on the target merchant number of the current transaction.

[0061] From the above content, it can be seen that through the combined use of the message push component and the map software program, accurate identification and efficient connection of nearby message receiving components are achieved. It not only improves the success rate and response speed of message push, but also ensures the accuracy and security of the message, and avoids the delays and errors that may be introduced by the traditional backend system's layer-by-layer message push. By dynamically constructing the search range and screening the target message receiving component, this embodiment provides a more flexible and reliable point-to-point transmission mechanism for payment notifications, which significantly improves the work efficiency of merchant cashiers in a busy cashier environment and the customer payment experience.

[0062] In an optional embodiment, the target merchant number is sent to N alternative message receiving components through a message push component, wherein each alternative message receiving component verifies whether the merchant number it carries is the target merchant number, and sends the verification result to the message push component, and through the message push component, the alternative message receiving component that feedbacks that the merchant number it carries is the target merchant number is used as the target message receiving component.

[0063] Optionally, the message push component will broadcast the target merchant number (i.e., the merchant information to which the current payment transaction belongs) to all message receiving components within the search range, i.e., N alternative message receiving components. After each alternative message receiving component receives the target merchant number, it will check its own pre-set merchant number to see if it is consistent with the target merchant number. This is to ensure that the message can be accurately sent to the payment terminal related to the current payment. After the verification is completed, each alternative message receiving component will feedback the verification result to the message push component, indicating whether it belongs to the target merchant. This feedback mechanism is an important part of two-way communication, which enables the message push component to perform the next step based on the feedback information. The message push component screens out the message receiving component that matches the target merchant number based on the received verification result, and determines it as the target message receiving component. This screening process ensures that the transaction message is only sent to the correct payment terminal, avoiding mistransmission of information.

[0064] It can be seen from the above content that by implementing the above steps, this embodiment provides a reliable and efficient message push mechanism, which ensures the accurate transmission of transaction information from the cashier counter (message push component end) to the merchant voice broadcast APP (message receiving component end). This mechanism reduces the delay in the backend system processing messages and avoids the failure of information transmission due to system node failure. At the same time, it also enhances the security and privacy of messages, because only the payment terminal that matches the target merchant number can receive transaction information. In addition, through the direct verification and selection process of the front end, the voice broadcast notification is more immediate and accurate, which effectively improves the efficiency of the merchant's cashier process and user experience. This embodiment demonstrates the application potential of front-end technology in the field of payment notifications, and provides merchants with a more intelligent and convenient way to confirm receipts.

[0065] In an optional embodiment, a data connection establishment request is sent to a target message receiving component through a message push component, and then a data connection is established between the message push component and the target message receiving component after receiving a reply message from the target message receiving component agreeing to establish the data connection.

[0066] Optionally, at the moment of payment confirmation, the message push component immediately sends a request to establish a data connection to the target message receiving component. The purpose of this request is to establish a stable communication channel to directly transmit the voice broadcast information of successful payment between the acquiring and cashiering counter H5 and the merchant's voice broadcast APP. After receiving the reply from the target message receiving component agreeing to establish a data connection, the message push component immediately establishes a data connection with the target message receiving component. This connection is point-to-point, bypassing the complex process of multi-layer message push in the traditional background system, ensuring the immediacy and reliability of information transmission. After the connection is established, the message push component starts sending messages to broadcast the transaction results.

[0067] Optionally, Figure 5 is a schematic diagram of an optional handshake connection in the customer payment phase according to an embodiment of the present application, such as Figure 5 As shown, step 1: the customer scans the merchant's QR code: the starting point of the payment process is that the customer uses his payment APP to scan the QR code displayed by the merchant. The QR code contains the merchant's unique identification information, which is used to identify which merchant the payment should be sent to; step 2: the cashier H5 sends the merchant number to the message push SDK: after the customer scans the QR code, the message push SDK in the cashier H5 will use the merchant number parsed from the QR code as a parameter for subsequent point-to-point message sending; step 3: the message push SDK applies to the customer for permission to obtain the mobile phone location: in order to determine the cashier's real-time location, the message push SDK needs to obtain the map positioning permission of the mobile phone , in order to search and determine the cashier's mobile phone of the merchant closest to the cashier counter; Step 4: The customer agrees to obtain the mobile phone location permission: The customer needs to confirm on the mobile phone and allow the cashier counter H5 to obtain its location information. This is to ensure the customer's privacy and data security, and is also a necessary condition for achieving point-to-point message transmission; Step 5: The message push SDK obtains the location and notifies the nearby message receiving SDK: After obtaining the mobile phone location permission, the message push SDK will monitor and obtain the mobile phone's geographic location information in real time, and then send a handshake connection request to the message receiving SDK integrated in the voice broadcast APP of the nearby merchant (such as within 50 meters); Step 6 Step 1: The message receiving SDK requests a random connection: When the message push SDK sends a connection request, the message receiving SDK in the nearby merchant voice broadcast APP will try to establish a connection. The "random connection" here means randomly selecting one of the multiple connectable SDKs for connection to improve the system's fault tolerance and efficiency; Step 7: The message push SDK verifies the merchant ID of the connection request: After receiving the connection request, the message push SDK will check the merchant ID of the requester to ensure that it matches the merchant ID of the current payment transaction to prevent misconnection or error message sending; Step 8: The message push SDK returns the same merchant ID request Request [Agree]: If the merchant number in the connection request is consistent with the merchant number of the message push SDK, the message push SDK will return [Agree] to allow the connection to be established, otherwise it will return [Reject]; Step 9: The message push SDK returns the same merchant number request [Agree]: If the merchant number in the connection request is consistent with the merchant number of the message push SDK, the message push SDK will return [Agree] to allow the connection to be established. From then on, the message push SDK and the message receiving SDK with the same merchant number complete the handshake connection, otherwise it will return [Reject]. It should be noted that the message push SDK can establish connections with multiple message receiving SDKs at the same time.

[0068] From the above content, it can be seen that through the direct data connection establishment and information push between the message push component and the target message receiving component, the instant voice notification of the payment result is realized, which greatly improves the transmission efficiency and reliability of payment confirmation information. The point-to-point connection mechanism avoids the delay and stability problems that may be encountered in the traditional backend system message push, ensures the synchronization of payment results and voice broadcast notifications, and enhances the transparency of transactions and user experience.

[0069] In an optional embodiment, after determining that the target message receiving component has received the user payment result, the data connection is disconnected through the message pushing component.

[0070] Optionally, when the user completes the payment and the cashier H5 receives the payment success confirmation, it will trigger the message push component to send the payment result and payment amount to the target message receiving component. During the period when the message push component establishes a connection with the target message receiving component, the message push component will continuously monitor the connection status to confirm whether the message has been successfully delivered. This monitoring function is implemented by the communication status management module inside the message push component in the cashier H5, ensuring the reliability and integrity of the message transmission process. Once the message push component confirms that the target message receiving component has successfully received the user's payment result, it will immediately perform a disconnection operation. This operation is implemented by the connection management module in the message push component, which is responsible for terminating the communication session with the target message receiving component and recovering the occupied system resources and network bandwidth.

[0071] Optionally, Figure 6 is a schematic diagram of an optional message broadcast at the customer payment stage according to an embodiment of the present application, such as Figure 6As shown, first, the customer enters the payment amount and payment password, which is the first step of the payment process. The customer enters the specific amount and password required for payment in the acquiring cashier H5 to confirm the payment information; then after the customer completes the payment information input, the acquiring cashier H5 receives this information and prepares to process the payment. The cashier H5 encrypts the payment information entered by the customer and sends it to the acquiring institution's backend system for verification and processing to ensure the security and effectiveness of the payment. After the backend system receives the payment information, it starts to execute the payment logic, including steps such as verifying the payment password and checking the account balance. After the backend system receives the payment information, it starts to execute the payment logic, including steps such as verifying the payment password, checking the account balance, and executing the fund transfer. The cashier H5 receives the confirmation information from the backend system, indicating that the payment has been successfully executed; then After confirming that the payment is successful, the cashier H5 will immediately call the message push SDK integrated in it, send a message to the message receiving SDK, and notify the payment result; then push the message, including the payment result, payment amount, etc.: the message push SDK sends the detailed payment information (including payment results and payment amount) to the message receiving SDK in a point-to-point communication manner, without the need to forward through the traditional multi-layer background system; after the message is pushed, the message push SDK will disconnect from the message receiving SDK, release resources, and recycle the connection thread to ensure the stability and efficiency of the system; finally, the merchant voice broadcast APP (the message receiving SDK is integrated in the APP) generates a voice notification through its integrated voice broadcast module based on the received payment information, informing the merchant cashier that the payment has been successfully completed and the specific payment amount.

[0072] From the above content, we can see that the message push component significantly improves the resource utilization and system response speed of the front-end point-to-point message transmission mechanism by disconnecting the data connection immediately after payment confirmation, avoiding unnecessary long-term connections, reducing the risk of communication delays and network congestion, and also reducing the burden on the system level, leaving more resources and bandwidth for subsequent payment transactions. This optimization measure not only improves the efficiency of the payment process, but also enhances the stability and security of the system, providing merchants and customers with a faster and more reliable payment experience.

[0073] According to an embodiment of the present application, an embodiment of a message processing method is provided. It should be noted that the steps shown in the flowchart of the accompanying drawings can be executed in a computer system such as a set of computer executable instructions, and although a logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in an order different from that shown here.

[0074] It should be noted that the target message receiving component is used as the execution subject of the message processing method of the embodiment of the present application. It is understandable that the message processing method provided in the embodiment of the present application can also be executed by other systems or devices, and the embodiment of the present application does not specifically limit this.

[0075] Figure 7 is a flowchart of an optional message processing method according to an embodiment of the present application, such as Figure 7 As shown, the method comprises the following steps:

[0076] Step S701: The target merchant ID sent by the message push component is received by the target message receiving component, and a data connection between the message push component and the target message receiving component is established.

[0077] In step S701, the target merchant number is the merchant identifier assigned to the message push component by the payment terminal of the target merchant after detecting that the user scans the payment graphic code.

[0078] In step S701, the target message receiving component is determined by the geographical location of the payment terminal and the target merchant number.

[0079] Optionally, after receiving the target merchant number through the target message receiving component, a data connection is established with the message pushing component to achieve direct communication between front ends.

[0080] Step S702, through the target message receiving component, receiving the user payment result determined by the payment terminal and sent by the message pushing component according to the data connection.

[0081] Optionally, the payment status information determined by the payment terminal includes key data such as payment success and payment amount. This is information sent to the target message receiving component by the message push component in real time based on the data connection after the payment is confirmed.

[0082] Step S703: Generate voice information according to the user payment result through the target message receiving component.

[0083] Optionally, based on the user's payment result, a voice notification generated by the target message receiving component is used to announce the payment status, such as "Payment failed, please scan the code again."

[0084] The embodiment of the present application also provides a message processing system. It should be noted that the message processing system of the embodiment of the present application can be used to execute the message sending method and message processing method provided in the embodiment of the present application. The message processing system provided in the embodiment of the present application is introduced below.

[0085] According to the embodiment of the present application, an embodiment of a message processing system is also provided. The system includes: a payment terminal, which is used to send a target merchant code to a message push component after detecting that a user scans a payment graphic code, wherein the target merchant code is a merchant identifier of the target merchant; a message push component, which is used to determine the geographic location of the payment terminal, and determine a target message receiving component to receive a message according to the geographic location of the payment terminal and the target merchant number; a target message receiving component, which is used to establish a data connection with the message push component, and receive a user payment result determined by the payment terminal and sent by the message push component according to the data connection, and generate a voice message according to the user payment result.

[0086] The embodiment of the present application also provides a message sending device. It should be noted that the message sending device of the embodiment of the present application can be used to execute the message sending method provided by the embodiment of the present application. The message sending device provided by the embodiment of the present application is introduced below.

[0087] According to an embodiment of the present application, a message sending device is also provided. Figure 8 is a schematic diagram of an optional message sending device according to an embodiment of the present application, such as Figure 8 As shown, the device includes: a first acquiring unit 801, a first determining unit 802, a second determining unit 803, a first establishing unit 804, and a third determining unit 805.

[0088] Optionally, the first acquisition unit 801 is used to acquire the target merchant number through the message push component, wherein the target merchant number is the merchant identifier assigned to the message push component by the target merchant's payment terminal after detecting that the user scans the payment graphic code; the first determination unit 802 is used to determine the geographical location of the target merchant's payment terminal through the message push component; the second determination unit 803 is used to determine the target message receiving component to receive the message according to the geographical location of the payment terminal and the target merchant number through the message push component; the first establishment unit 804 is used to establish a data connection between the message push component and the target message receiving component; the third determination unit 805 is used to send the user payment result determined by the payment terminal to the target message receiving component through the message push component according to the data connection, wherein the target message receiving component is used to generate voice information based on the user payment result.

[0089] Optionally, the first determination unit 802 includes: a first sending subunit and a first reading subunit. The first sending subunit is used to send a location acquisition request to the payment terminal of the target merchant through the message push component, wherein the location acquisition request is used to request the payment terminal to open the location determination authority to the message push component; the first reading subunit is used to read the geographic location of the payment terminal through the message push component after detecting that the payment terminal agrees to the location acquisition request.

[0090] Optionally, the second determination unit 803 includes: a first acquisition subunit, a first determination subunit, a second determination subunit, and a third determination subunit. The first acquisition subunit is used to obtain the access rights of the map software program built into the payment terminal through the message push component; the first determination subunit is used to expand the preset distance along the target direction and / or target angle according to the map software program with the geographical location of the payment terminal as the center position to obtain the search range; the second determination subunit is used to determine N message receiving components that carry the merchant number within the search range as N candidate message receiving components, wherein N is an integer greater than or equal to 1; the third determination subunit is used to determine the target message receiving component from the N candidate message receiving components according to the target merchant number.

[0091] Optionally, the third determination subunit includes: a first sending module and a first determination module. The first sending module is used to send the target merchant number to N candidate message receiving components through the message push component, wherein each candidate message receiving component verifies whether the merchant number it carries is the target merchant number, and sends the verification result to the message push component; the first determination module is used to use the message push component to use the candidate message receiving component that feedbacks that the merchant number it carries is the target merchant number as the target message receiving component.

[0092] Optionally, the first establishing unit 804 includes: a second sending subunit and a first establishing subunit. The second sending subunit is used to send a data connection establishment request to the target message receiving component through the message push component; the first establishing subunit is used to establish a data connection between the message push component and the target message receiving component after receiving a reply message from the target message receiving component that agrees to establish the data connection.

[0093] Optionally, the message sending device further includes: a processing unit, configured to disconnect the data connection through the message pushing component after determining that the target message receiving component has received the user payment result.

[0094] The embodiment of the present application also provides a message processing device. It should be noted that the message processing device of the embodiment of the present application can be used to execute the message processing method provided by the embodiment of the present application. The message processing device provided by the embodiment of the present application is introduced below.

[0095] According to an embodiment of the present application, a message processing device is also provided. Fig. 9 is a schematic diagram of an optional message processing device according to an embodiment of the present application, such as Fig. 9 As shown, the device includes: a sending unit 901, a receiving unit 902, and a generating unit 903.

[0096] Optionally, the sending unit 901 receives the target merchant number sent by the message push component through the target message receiving component, and establishes a data connection between the message push component and the target message receiving component, wherein the target merchant number is a merchant identifier assigned to the message push component by the target merchant's payment terminal after detecting that the user scans the payment graphic code; the target message receiving component is determined by the geographic location of the payment terminal and the target merchant number; the receiving unit 902 receives, through the target message receiving component, a user payment result determined by the payment terminal and sent by the message push component based on the data connection; the generating unit 903 generates voice information based on the user payment result through the target message receiving component.

[0097] According to another aspect of the present application, a computer-readable storage medium is provided, the computer-readable storage medium including a stored executable program, wherein when the executable program is executed, the device where the computer-readable storage medium is located is controlled to execute the above method.

[0098] According to another aspect of the present application, an electronic device is provided, including: a memory storing an executable program; and a processor for running the program, wherein the above method is executed when the program is running.

[0099] According to another aspect of the present application, a computer program product is also provided, comprising computer instructions, which implement the steps of the above method when executed by a processor.

[0100] The serial numbers of the above-mentioned embodiments of the present application are for description only and do not represent the advantages or disadvantages of the embodiments.

[0101] In the above embodiments of the present application, the description of each embodiment has its own emphasis. For parts that are not described in detail in a certain embodiment, please refer to the relevant description of other embodiments.

[0102] In the several embodiments provided in this application, it should be understood that the disclosed technical content can be implemented in other ways. Among them, the device embodiments described above are only schematic. For example, the division of the units can be a logical function division. There may be other division methods in actual implementation. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of units or modules, which can be electrical or other forms.

[0103] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple units. Some or all of the units may be selected according to actual needs to achieve the purpose of the present embodiment.

[0104] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0105] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application can be essentially or partly or all or partly embodied in the form of a software product that contributes to the prior art. The computer software product is stored in a storage medium, including several instructions for a computer device (which can be a personal computer, a server or a network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: U disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), mobile hard disk, disk or optical disk, etc., which can store program code.

[0106] The above is only a preferred embodiment of the present application. It should be pointed out that for ordinary technicians in this technical field, several improvements and modifications can be made without departing from the principles of the present application. These improvements and modifications should also be regarded as the scope of protection of the present application.

Claims

1. A message sending method, characterized in that: include: Obtaining a target merchant number through a message push component, wherein the target merchant number is a merchant identifier assigned to the message push component by the payment terminal of the target merchant after detecting that the user scans the payment graphic code; Determine the geographical location of the payment terminal of the target merchant through the message push component; Determine, by the message push component, a target message receiving component for receiving the message according to the geographical location of the payment terminal and the target merchant number; Establishing a data connection between the message push component and the target message receiving component; The message push component sends the user payment result determined by the payment terminal to the target message receiving component according to the data connection, wherein the target message receiving component is used to generate voice information according to the user payment result.

2. The message sending method according to claim 1, characterized in that: Determining the geographical location of the payment terminal of the target merchant through the message push component includes: Sending a location acquisition request to the payment terminal of the target merchant through the message push component, wherein the location acquisition request is used to request the payment terminal to open a location determination authority to the message push component; After detecting that the payment terminal agrees to the location acquisition request, the geographical location of the payment terminal is read through the message push component.

3. The message sending method according to claim 1, characterized in that: Determining a target message receiving component for receiving a message according to the geographical location of the payment terminal by the message push component includes: Obtaining access rights to the map software program built into the payment terminal through the message push component; According to the map software program, taking the geographical location of the payment terminal as the center position, expanding the preset distance along the target direction and / or target angle to obtain the search range; Determine N message receiving components that carry merchant codes within the search range as N candidate message receiving components, where N is an integer greater than or equal to 1; The target message receiving component is determined from the N candidate message receiving components according to the target merchant number.

4. The message sending method according to claim 3, characterized in that: Determining the target message receiving component from the N candidate message receiving components according to the target merchant number includes: The target merchant number is sent to the N candidate message receiving components through the message push component, wherein each candidate message receiving component checks whether the merchant number carried by itself is the target merchant number, and sends the verification result to the message push component; Through the message pushing component, the candidate message receiving component whose merchant number carried in the feedback is the target merchant number is used as the target message receiving component.

5. The message sending method according to claim 1, characterized in that: Establishing a data connection between the message push component and the target message receiving component includes: Sending the data connection establishment request to the target message receiving component through the message push component; After receiving the reply information of the target message receiving component agreeing to establish the data connection, the data connection between the message pushing component and the target message receiving component is established.

6. The message sending method according to claim 1, characterized in that: After the user payment result determined by the payment terminal is sent to the target message receiving component according to the data connection by the message push component, the message sending method further includes: After determining that the target message receiving component has received the user payment result, the data connection is disconnected through the message pushing component.

7. A message processing method, characterized in that: include: The target merchant number sent by the message push component is received by the target message receiving component, and a data connection is established between the message push component and the target message receiving component, wherein the target merchant number is a merchant identifier assigned to the message push component by the payment terminal of the target merchant after detecting that the user scans the payment graphic code; the target message receiving component is determined by the geographical location of the payment terminal and the target merchant number; Receiving, through the target message receiving component, a user payment result determined by the payment terminal and sent by the message pushing component according to the data connection; The target message receiving component generates voice information according to the user payment result.

8. A message processing system, characterized in that: include: The payment terminal is used to send a target merchant code to the message push component after detecting that the user scans the payment graphic code, wherein the target merchant code is a merchant identifier of the target merchant; The message push component is used to determine the geographical location of the payment terminal, and determine the target message receiving component to receive the message according to the geographical location of the payment terminal and the target merchant number; The target message receiving component is used to establish a data connection with the message pushing component, receive the user payment result determined by the payment terminal and sent by the message pushing component based on the data connection, and generate voice information based on the user payment result.

9. A message sending device, characterized in that: include: A first acquisition unit acquires a target merchant number through a message push component, wherein the target merchant number is a merchant identifier assigned to the message push component by a payment terminal of the target merchant after detecting that a user scans a payment graphic code; A first determining unit, which determines the geographical location of the payment terminal of the target merchant through the message push component; A second determining unit, through the message pushing component, determines a target message receiving component to receive the message according to the geographical location of the payment terminal and the target merchant number; A first establishing unit is used to establish a data connection between the message push component and the target message receiving component; The third determination unit sends the user payment result determined by the payment terminal to the target message receiving component through the message push component according to the data connection, wherein the target message receiving component is used to generate voice information according to the user payment result.

10. A message processing device, characterized in that: include: The sending unit receives the target merchant number sent by the message push component through the target message receiving component, and establishes a data connection between the message push component and the target message receiving component, wherein the target merchant number is a merchant identifier assigned to the message push component by the payment terminal of the target merchant after detecting that the user scans the payment graphic code; the target message receiving component is determined by the geographical location of the payment terminal and the target merchant number; A receiving unit, receiving, through the target message receiving component, a user payment result determined by the payment terminal and sent by the message push component according to the data connection; A generating unit generates voice information according to the user payment result through the target message receiving component.

11. A computer-readable storage medium, characterized in that: The computer-readable storage medium includes a stored executable program, wherein when the executable program is running, the device where the computer-readable storage medium is located is controlled to execute the message sending method described in any one of claims 1 to 6 or the message processing method described in claim 7.

12. An electronic device, characterized in that: It includes one or more processors and a memory, wherein the memory is used to store one or more programs, wherein when the one or more programs are executed by the one or more processors, the one or more processors execute the message sending method described in any one of claims 1 to 6 or the message processing method described in 7.

13. A computer program product comprising computer instructions, characterized in that: When the computer instructions are executed by the processor, the steps of the message sending method described in any one of claims 1 to 6 or the message processing method described in claim 7 are implemented.

Images