CN110689334A - Payment method, server, client and system based on multi-person order ordering - Google Patents
Payment method, server, client and system based on multi-person order ordering Download PDFInfo
- Publication number
- CN110689334A CN110689334A CN201910918561.2A CN201910918561A CN110689334A CN 110689334 A CN110689334 A CN 110689334A CN 201910918561 A CN201910918561 A CN 201910918561A CN 110689334 A CN110689334 A CN 110689334A
- Authority
- CN
- China
- Prior art keywords
- order
- payment
- data record
- service
- user
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 46
- 230000001960 triggered effect Effects 0.000 claims abstract description 46
- 238000004891 communication Methods 0.000 claims description 15
- 238000012545 processing Methods 0.000 description 6
- 230000006870 function Effects 0.000 description 5
- 238000010586 diagram Methods 0.000 description 4
- 230000000694 effects Effects 0.000 description 4
- 238000013459 approach Methods 0.000 description 2
- 238000004590 computer program Methods 0.000 description 2
- 239000003999 initiator Substances 0.000 description 2
- 230000007547 defect Effects 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 238000001514 detection method Methods 0.000 description 1
- 235000013305 food Nutrition 0.000 description 1
- 238000013507 mapping Methods 0.000 description 1
- 235000012054 meals Nutrition 0.000 description 1
- 238000011022 operating instruction Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/08—Payment architectures
- G06Q20/10—Payment architectures specially adapted for electronic funds transfer [EFT] systems; specially adapted for home banking systems
- G06Q20/102—Bill distribution or payments
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/22—Payment schemes or models
Landscapes
- Business, Economics & Management (AREA)
- Accounting & Taxation (AREA)
- Finance (AREA)
- Strategic Management (AREA)
- Physics & Mathematics (AREA)
- General Business, Economics & Management (AREA)
- General Physics & Mathematics (AREA)
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Development Economics (AREA)
- Economics (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
The invention discloses a payment method, a server, a client and a system based on multi-person ordering, which relate to the field of electronic information and comprise the following steps: according to a service equipment identifier and a user identifier contained in each received order service request, creating an order data record corresponding to the service equipment identifier; the order identification code of the order data record comprises the service equipment identification and a plurality of user identifications associated with the service equipment identification; generating a payment order corresponding to the order data record, and respectively pushing the payment order to a user terminal corresponding to each user identifier contained in the order identifier of the order data record; and paying the payment order according to the received payment request triggered aiming at the payment order. The method ensures that each order user has the authority to pay the order, and improves the flexibility of order payment.
Description
Technical Field
The invention relates to the field of electronic information, in particular to a payment method, a server, a client and a system based on multi-person ordering.
Background
At present, many services can perform electronic ordering operation through the Internet, so that the complicated inconvenience of manual ordering is eliminated. In most service scenarios, the service user is personal, and accordingly, only a single user needs to perform a click-to-order operation. However, in some service scenarios, a service user is a group of services commonly used by multiple users, for example, multiple users all want to participate in a single-click operation, but the conventional service architecture only supports the single-click operation of a single user and does not support a coordinated single-click operation among multiple users.
In order to solve the above problems, in patent application No. 2015100461021, a family ordering system in which a family participates in ordering is disclosed, which is that an originator logs in first, and after entering the system, the originator searches restaurant information and selects a restaurant, and then the originator initiates ordering, and selects a member group chat, thereby inviting friends to order together. The demand of ordering food by multiple persons at the same time is realized through the member group chat function.
However, the inventor finds that the above mode in the prior art has at least the following defects in the process of implementing the invention: in the above manner, although a plurality of users can participate in ordering, for the order background, the order can be identified only according to the information of the order initiator, and the order cannot be identified according to the information of other ordering users. Correspondingly, only the order initiator has the right to pay the order, and other users participating in ordering do not have the right to pay, so that the order payment mode is single.
Disclosure of Invention
In view of the above, the present invention has been made to provide a multi-person ordering-based payment method, server, client and system that overcome or at least partially solve the above problems.
According to an aspect of the present invention, there is provided a multi-person ordering-based payment method, including:
according to a service equipment identifier and a user identifier contained in each received order service request, creating an order data record corresponding to the service equipment identifier; the order identification code of the order data record comprises the service equipment identification and a plurality of user identifications associated with the service equipment identification;
generating a payment order corresponding to the order data record, and respectively pushing the payment order to a user terminal corresponding to each user identifier contained in the order identifier of the order data record;
and paying the payment order according to the received payment request triggered aiming at the payment order.
Optionally, the paying the payment order according to the received payment request triggered by the payment order specifically includes:
judging whether the user identification contained in the payment request is matched with the order identification code of the order data record corresponding to the payment order or not;
and if so, paying the payment order according to the payment request.
Optionally, the paying the payment order according to the received payment request triggered by the payment order specifically includes:
when a payment request triggered by the payment order is received, judging whether the payment order corresponding to the order data record is paid or not according to a service state field contained in the order data record corresponding to the payment order;
if not, the payment order is paid according to the received payment request triggered aiming at the payment order, and the service state field contained in the order data record corresponding to the payment order is updated according to the payment result.
Optionally, after determining whether the payment order corresponding to the order data record has been paid, the method further includes:
and if so, rejecting the payment request and pushing a paid notification to a user terminal corresponding to the payment request.
Optionally, the paying the payment order according to the received payment request triggered by the payment order specifically includes:
determining a paid user corresponding to the payment order according to a user identifier contained in the payment request;
determining at least one unpaid user corresponding to the payment order according to the order identification code of the order data record corresponding to the payment request;
determining the amount to be paid corresponding to each unpaid user according to the order amount data of the payment order and the number of the unpaid users;
and sending a payment notification message containing the amount to be paid to each unpaid user, and updating account data corresponding to the user account of the paid user according to the payment request when receiving the payment request triggered by each unpaid user aiming at the payment notification message.
Optionally, the generating a payment order corresponding to the order data record, and pushing the payment order to the user terminals corresponding to the user identifiers included in the order identifier of the order data record respectively includes:
when an order submission request triggered by the order data record is received, generating a payment order corresponding to the order data record;
and copying the payment order into a plurality of copies according to the number of the user identifications contained in the order identification code of the order data record, and respectively pushing each copied payment order to each user terminal corresponding to the user identification contained in the order identification code of the order data record.
Optionally, the creating, according to the service device identifier and the user identifier included in each received ordering service request, an order data record corresponding to the service device identifier includes:
when a ordering service request is received, acquiring a service equipment identifier and a user identifier contained in the received ordering service request, and judging whether an effective ordering identifier associated with the service equipment identifier exists in a preset ordering data table or not;
if yes, acquiring the created order data record corresponding to the service equipment identifier and the effective order opening identifier, and adding the user identifier contained in the order service request received this time into the order identifier of the order data record;
if not, generating an effective billing identifier associated with the service equipment identifier, storing the service equipment identifier and the effective billing identifier in the billing data table in an associated manner, and creating an order data record corresponding to the service equipment identifier and the effective billing identifier, wherein the order identifier of the order data record comprises the service equipment identifier, the effective billing identifier and a user identifier contained in the received order service request.
Optionally, the ordering service request includes: and scanning the code order request based on the information code, wherein the information code comprises a service equipment identifier.
Optionally, the payment order includes an order identification code of the order data record, and the payment request triggered for the payment order includes: and the order identification code of the order data record corresponding to the payment order to be paid.
According to still another aspect of the present invention, there is provided a multi-person ordering-based payment method, including:
sending a ordering service request containing a service equipment identifier and a user identifier to an ordering server so that the ordering server can create an order data record corresponding to the service equipment identifier; the order identification code of the order data record comprises the service equipment identification and a plurality of user identifications associated with the service equipment identification;
and receiving a payment order which is pushed by the order ordering server and corresponds to the order data record so as to carry out payment according to the payment order.
According to still another aspect of the present invention, there is provided a multi-person ordering-based payment server, including:
the receiving module is suitable for creating order data records corresponding to the service equipment identifications according to the service equipment identifications and the user identifications contained in the received ordering service requests; the order identification code of the order data record comprises the service equipment identification and a plurality of user identifications associated with the service equipment identification;
the generating module is suitable for generating a payment order corresponding to the order data record and pushing the payment order to the user terminals corresponding to the user identifications contained in the order identification codes of the order data record;
and the payment module is suitable for paying the payment order according to the received payment request triggered aiming at the payment order.
Optionally, the payment module is specifically adapted to:
judging whether the user identification contained in the payment request is matched with the order identification code of the order data record corresponding to the payment order or not;
and if so, paying the payment order according to the payment request.
Optionally, the payment module is specifically adapted to:
when a payment request triggered by the payment order is received, judging whether the payment order corresponding to the order data record is paid or not according to a service state field contained in the order data record corresponding to the payment order;
if not, the payment order is paid according to the received payment request triggered aiming at the payment order, and the service state field contained in the order data record corresponding to the payment order is updated according to the payment result.
Optionally, the payment module is further adapted to: and when the payment order corresponding to the order data record is judged to be paid, rejecting the payment request and pushing a paid notice to a user terminal corresponding to the payment request.
Optionally, the payment module is specifically adapted to:
determining a paid user corresponding to the payment order according to a user identifier contained in the payment request;
determining at least one unpaid user corresponding to the payment order according to the order identification code of the order data record corresponding to the payment request;
determining the amount to be paid corresponding to each unpaid user according to the order amount data of the payment order and the number of the unpaid users;
and sending a payment notification message containing the amount to be paid to each unpaid user, and updating account data corresponding to the user account of the paid user according to the payment request when receiving the payment request triggered by each unpaid user aiming at the payment notification message.
Optionally, the generating module is specifically adapted to:
when an order submission request triggered by the order data record is received, generating a payment order corresponding to the order data record;
and copying the payment order into a plurality of copies according to the number of the user identifications contained in the order identification code of the order data record, and respectively pushing each copied payment order to each user terminal corresponding to the user identification contained in the order identification code of the order data record.
Optionally, the receiving module is specifically adapted to:
when a ordering service request is received, acquiring a service equipment identifier and a user identifier contained in the received ordering service request, and judging whether an effective ordering identifier associated with the service equipment identifier exists in a preset ordering data table or not;
if yes, acquiring the created order data record corresponding to the service equipment identifier and the effective order opening identifier, and adding the user identifier contained in the order service request received this time into the order identifier of the order data record;
if not, generating an effective billing identifier associated with the service equipment identifier, storing the service equipment identifier and the effective billing identifier in the billing data table in an associated manner, and creating an order data record corresponding to the service equipment identifier and the effective billing identifier, wherein the order identifier of the order data record comprises the service equipment identifier, the effective billing identifier and a user identifier contained in the received order service request.
Optionally, the ordering service request includes: and scanning the code order request based on the information code, wherein the information code comprises a service equipment identifier.
Optionally, the payment order includes an order identification code of the order data record, and the payment request triggered for the payment order includes: and the order identification code of the order data record corresponding to the payment order to be paid.
According to still another aspect of the present invention, there is provided a multi-person ordering-based payment client, including:
the system comprises a sending module, a receiving module and a sending module, wherein the sending module is suitable for sending a ordering service request containing a service equipment identifier and a user identifier to an ordering server so that the ordering server can create an order data record corresponding to the service equipment identifier; the order identification code of the order data record comprises the service equipment identification and a plurality of user identifications associated with the service equipment identification;
and the receiving module is suitable for receiving the payment order which is pushed by the ordering server and corresponds to the order data record so as to carry out payment according to the payment order.
According to another aspect of the present invention, a multi-person ordering-based payment system is provided, which includes the above-mentioned multi-person ordering-based payment server and payment client.
According to still another aspect of the present invention, there is provided an electronic apparatus including: the system comprises a processor, a memory, a communication interface and a communication bus, wherein the processor, the memory and the communication interface complete mutual communication through the communication bus;
the memory is used for storing at least one executable instruction, and the executable instruction enables the processor to execute the operation corresponding to the payment method based on the multi-person ordering.
According to still another aspect of the present invention, there is provided a computer storage medium having at least one executable instruction stored therein, the executable instruction causing a processor to perform operations corresponding to the above-mentioned multi-person ordering-based payment method.
In the payment method, the server, the client and the system based on the multi-person ordering, firstly, an order data record corresponding to a service equipment identifier is established according to the service equipment identifier and the user identifier contained in each received ordering service request; the order identification code of the order data record comprises a service equipment identifier and a plurality of user identifiers associated with the service equipment identifier; then, generating a payment order corresponding to the order data record, and respectively pushing the payment order to a user terminal corresponding to each user identifier contained in the order identifier of the order data record; and finally, paying the payment order according to the received payment request. Therefore, in the above manner, the order identification code of the order data record includes the service device identifier and the plurality of user identifiers associated with the service device identifier, accordingly, an order can be uniquely identified based on the service device identifier, and a plurality of payment orders are generated according to the plurality of user identifiers associated with the service device identifier, so that each order user is ensured to have authority to pay the order, and the flexibility of order payment is improved.
The foregoing description is only an overview of the technical solutions of the present invention, and the embodiments of the present invention are described below in order to make the technical means of the present invention more clearly understood and to make the above and other objects, features, and advantages of the present invention more clearly understandable.
Drawings
Various other advantages and benefits will become apparent to those of ordinary skill in the art upon reading the following detailed description of the preferred embodiments. The drawings are only for purposes of illustrating the preferred embodiments and are not to be construed as limiting the invention. Also, like reference numerals are used to refer to like parts throughout the drawings. In the drawings:
fig. 1 is a flowchart illustrating a payment method based on multi-person ordering according to an embodiment of the present invention;
fig. 2 is a flowchart illustrating a payment method based on multi-person ordering according to a second embodiment of the present invention;
fig. 3 is a diagram illustrating a structure of a payment server based on a multi-person order form according to a third embodiment of the present invention;
fig. 4 shows a schematic structural diagram of an electronic device according to a fifth embodiment of the present invention.
Detailed Description
Exemplary embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. While exemplary embodiments of the present disclosure are shown in the drawings, it should be understood that the present disclosure may be embodied in various forms and should not be limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art.
Example one
Fig. 1 shows a flowchart of a payment method based on multiple ordering lists according to an embodiment of the present invention. As shown in fig. 1, the method includes:
step S110: creating order data records corresponding to the service equipment identifications according to the service equipment identifications and the user identifications contained in the received ordering service requests; the order identification code of the order data record comprises a service equipment identification and a plurality of user identifications associated with the service equipment identification.
The ordering service request is used for realizing ordering operation, and can be sent in various modes such as code scanning and the like. The order service request comprises a service equipment identifier and a user identifier. The service equipment identifier is as follows: the service equipment may be electronic equipment, or various equipment such as a service desk and a service room. The user identification means: and sending an identifier of the user requesting the order service, such as a user account. In this embodiment, based on the service device identifier included in each received order service request, multiple user identifiers corresponding to the same service device identifier are associated together, and then a corresponding order data record is established, where the order data record can be identified by the service device identifier.
Step S120: and generating a payment order corresponding to the order data record, and respectively pushing the payment order to the user terminals corresponding to the user identifications contained in the order identification code of the order data record.
Specifically, in order to facilitate the effect of multi-user payment, after a payment order corresponding to the order data record is generated, each user identifier included in the order identifier of the order data record is queried. And pushing the payment order to the user terminals corresponding to the user identifications contained in the order identification codes of the order data records respectively according to the query result. The payment order is used for realizing an order payment function and comprises information such as service item details to be paid, payment amount and payment entry elements. This approach enables each user participating in the ordering to receive a corresponding payment order.
Step S130: and paying the payment order according to the received payment request triggered aiming at the payment order.
Wherein each ordering user receiving a payment order is able to trigger a payment request for the received payment order. For example, the payment request may be triggered by a payment entry element contained in the payment order. Correspondingly, the background server pays the payment order according to the received payment request triggered aiming at the payment order.
Therefore, in the above manner, the order identification code of the order data record includes the service device identifier and the plurality of user identifiers associated with the service device identifier, accordingly, an order can be uniquely identified based on the service device identifier, and a plurality of payment orders are generated according to the plurality of user identifiers associated with the service device identifier, so that each order user is ensured to have authority to pay the order, and the flexibility of order payment is improved.
Example II,
Fig. 2 shows a flowchart of a payment method based on multiple ordering lists according to a second embodiment of the present invention. As shown in fig. 2, the method includes:
step S210: creating order data records corresponding to the service equipment identifications according to the service equipment identifications and the user identifications contained in the received ordering service requests; the order identification code of the order data record comprises a service equipment identification and a plurality of user identifications associated with the service equipment identification.
Specifically, when a ordering service request is received, a service device identifier and a user identifier included in the ordering service request received this time are acquired, and whether an effective ordering identifier associated with the service device identifier exists in a preset ordering data table or not is judged; if yes, acquiring the created order data record corresponding to the service equipment identifier and the effective order opening identifier, and adding the user identifier contained in the order service request received this time into the order identifier of the order data record; if not, generating an effective billing identifier associated with the service equipment identifier, storing the service equipment identifier and the effective billing identifier in a billing data table in an associated manner, and creating an order data record corresponding to the service equipment identifier and the effective billing identifier, wherein an order identifier of the order data record comprises the service equipment identifier, the effective billing identifier and a user identifier contained in the received order service request. The ordering service request is used for realizing ordering operation, and can be sent in various modes such as code scanning and the like. For example, in a specific example, an information code in the form of a two-dimensional code or the like is provided on the service device, and the information code includes a service device identifier, and accordingly, the order service request is a code scanning order request based on the information code. Specifically, the order service request includes a service device identifier and a user identifier. The service equipment identifier is as follows: the service equipment may be electronic equipment, or various equipment such as a service desk and a service room. The user identification means: and sending an identifier of the user requesting the order service, such as a user account.
In specific implementation, when receiving the ordering service request, the corresponding service device is judged whether to execute the ordering processing according to the service device identifier contained in the ordering service request. Wherein, the order processing means: the existing service user performs a ordering operation for the service device, that is: the service device has transitioned from an idle state to a non-idle state. Specifically, the determination is performed according to whether an effective billing identifier associated with the service device identifier exists in a preset billing data table. The billing data table is used for storing effective billing identifications corresponding to the service equipment identifications, and the service equipment can be identified to be in an idle or non-idle state through the effective billing identifications. Specifically, the billing data table is used for storing the billing data, and accordingly, the billing serial number associated with the service device identifier is generated according to the billing data record, and the billing serial number is used as the effective billing identifier. Because the open stream number contains the timestamp information, whether one service device is idle or not can be accurately identified.
When the valid billing identifier associated with the service device identifier exists in the billing data table, it indicates that the corresponding service device is currently in a non-idle state, and therefore, a service user has executed billing processing for the service device. Correspondingly, the created order data record corresponding to the service equipment identifier and the effective order opening identifier is obtained, and the user identifier contained in the order service request received this time is added to the order identifier code of the order data record. By the method, the number of the service users associated with the service equipment identifier can be expanded, so that the order data record corresponding to the service equipment identifier comprises the user identifiers of a plurality of service users.
When the valid billing identifier associated with the service device identifier does not exist in the billing data table, it indicates that the corresponding service device is currently in an idle state and needs to execute billing processing. Correspondingly, generating effective billing identification associated with the business equipment identification and storing the business equipment identification and the effective billing identification association into a billing data table so as to realize billing processing aiming at the business equipment, thereby identifying that the business equipment is in a non-idle state. And then, creating an order data record corresponding to the service equipment identifier and the effective order-opening identifier, wherein the order identifier of the order data record comprises the service equipment identifier, the effective order-opening identifier and the user identifier contained in the order-ordering service request received this time.
It can be seen that the order identification code created in the present application includes: a first field for storing service equipment identification, a second field for storing effective billing identification and a third field for storing user identification; the third field further includes a plurality of subfields respectively corresponding to different user identities, and each user identity respectively corresponds to each received order service request. By the method, a plurality of single users can be associated according to the service equipment identifier, so that order data records are created based on the service equipment identifier. The order data record is used for storing business records of all business links from creation to payment of an order.
Step S220: and carrying out multi-person ordering operation according to the created order data record.
Specifically, the service item data associated with the service device identifier is pushed to the user terminal corresponding to the user identifier included in the received order service request, so that when a service item addition request triggered by the user terminal for the service item data is received, the service item included in the service item addition request is added to the service item field included in the order data record. Namely: and adding a service item corresponding to the service item adding request into a service item field contained in the order data record according to the received service item adding request triggered aiming at the order data record. The business item field is used for recording the name and the quantity of each business item corresponding to the order data record so as to provide business service for the user based on the business item field. When the service equipment is a service table (such as a dining table), the service item data can be meal data of a restaurant for a user to select. Therefore, after a receipt service request is received, based on a service device identifier included in the receipt service request, service item data corresponding to the service device identifier is pushed to a corresponding receipt user, which can be specifically realized by querying a preset service item database, where the service item database is used to store mapping relationships between each service device and a corresponding service item. By the mode, a plurality of code scanning click list users corresponding to the same service equipment can perform click list operation based on service item data. Correspondingly, when the background server receives the service item adding request, the order data record corresponding to the service item adding request is determined according to the service equipment identifier contained in the service item adding request, and then the service item in the service item adding request is recorded into the service item field of the order data record. Therefore, a plurality of different service users can trigger service item adding requests aiming at the same service equipment, correspondingly, the background server collects service items in the service item adding requests triggered by different service users aiming at the same service equipment into the service item fields of the corresponding order data records, and therefore the effect that multiple users simultaneously make an order is achieved.
Step S230: when an order submission request triggered for an order data record is received, a payment order corresponding to the order data record is generated.
Specifically, when the order ordering process is finished, an order submission request is initiated by any one of a plurality of order users. Correspondingly, when an order submitting request triggered by the order data record is received, a payment order corresponding to the order data record is generated according to each added service item in the service item field contained in the order data record, and the order amount of the payment order is determined according to the number of each added service item in the service item field and the service resource cost corresponding to the service item. The service item adding request triggered by the order data record comprises a plurality of service item adding requests sent by user terminals corresponding to user identifications contained in the order identification code of the order data record.
Therefore, in the embodiment, the order data record is used for storing business records of each business link, such as creation of an order, addition of business items, payment and the like. Namely: the order data record is used for storing information of each business link and each business layer of the order in a centralized manner so as to comprehensively describe the state of one order. A payment order is an order derived from the order data record that is specific to the payment function being implemented. The payment order is associated with its corresponding order data record by an order identification code. Because the payment order is independent of the order data record and can be copied into a plurality of copies, the invention realizes the effect that a plurality of users have authority to pay by separating the order data record and the payment order.
Step S240: and copying the payment order into a plurality of copies according to the number of the user identifications contained in the order identification code of the order data record, and respectively pushing each copied payment order to each user terminal corresponding to the user identification contained in the order identification code of the order data record.
Specifically, in order to facilitate the effect of multi-user payment, after a payment order corresponding to the order data record is generated, each user identifier included in the order identifier of the order data record is queried. And pushing the payment order to the user terminals corresponding to the user identifications contained in the order identification codes of the order data records respectively according to the query result. The payment order is used for realizing an order payment function and comprises information such as service item details to be paid, payment amount and payment entry elements. This approach enables each user participating in the ordering to receive a corresponding payment order.
Step S250: and paying the payment order according to the received payment request triggered aiming at the payment order.
Wherein each ordering user receiving a payment order is able to trigger a payment request for the received payment order. For example, the payment request may be triggered by a payment entry element contained in the payment order. Correspondingly, the background server pays the payment order according to the received payment request triggered aiming at the payment order.
Specifically, in order to prevent the end point single user from paying the order of the adjacent table by mistake, in this step, it is necessary to check whether the payment user is matched with the order to be paid: judging whether a user identifier contained in a received payment request aiming at the payment order is matched with an order identifier code of an order data record corresponding to the payment order; and if so, paying the payment order according to the payment request. For example, when the user identifier included in the received payment request for the payment order matches one of the plurality of user identifiers stored in the order identifier of the order data record corresponding to the payment order, it is said that the payment user matches the payment order, and thus the payment is made; otherwise, the payment user is not matched with the payment order, and the user is prompted to check the payment order.
In addition, since any one of a plurality of individual users can pay for an order, collision detection is required to prevent the occurrence of a phenomenon of repeated payment. Correspondingly, when payment is performed on the payment order according to the received payment request triggered by aiming at the payment order, the payment is specifically realized in the following way: when a payment request triggered by a payment order is received, judging whether the payment order corresponding to the order data record is paid or not according to a service state field contained in the order data record corresponding to the payment order; if not, the payment order is paid according to the received payment request triggered aiming at the payment order, and the service state field contained in the order data record corresponding to the payment order is updated according to the payment result; and if so, rejecting the payment request and pushing a payment notification to a user terminal corresponding to the payment request. The order data record further comprises a service status field, wherein the service status field is used for indicating whether the service resource corresponding to the order is paid, and accordingly repeated payment can be prevented by inquiring the value of the service status field, so that only one user in a plurality of users can be ensured to be successful in payment.
By the mode, the order payment process can be completed by any one of the plurality of single users. In addition, considering that a plurality of single users may need to perform apportionment operation on business resources corresponding to the order, in order to facilitate apportionment of business resources among the plurality of single users, when payment is performed on the payment order according to a received payment request triggered for the payment order, a paid user corresponding to the payment order is determined according to a user identifier included in the payment request; determining at least one unpaid user corresponding to the payment order based on the order identification code of the order data record corresponding to the payment request; determining the amount to be paid corresponding to each unpaid user according to the order amount data of the payment order and the number of the unpaid users; and sending a payment notification message containing the amount to be paid to each unpaid user, and updating account data corresponding to the user account of the paid user according to the payment request when receiving the payment request triggered by each unpaid user aiming at the payment notification message. Therefore, through the method, the notification message containing the amount to be paid can be automatically sent to the rest unpaid users to guide the rest unpaid users to finish payment, and the payment amount of each unpaid user is transferred to the user account of the paid user, so that the aim of distributing service resources among the single users at each point is fulfilled. The method is particularly suitable for the service scene of ordering by multiple persons.
Therefore, in the above mode provided by the invention, the order can be identified through the service equipment identifier, so that a plurality of single users corresponding to the same service equipment identifier can be conveniently associated. The order identification code of this embodiment at least includes a service device identifier and user identifiers of multiple point order users associated with the service device identifier, and accordingly, a payment order generated according to an order data record also includes the order identification code, and a payment request triggered for the payment order also includes the order identification code of an order data record corresponding to the payment order to be paid. Therefore, the order identification code in the embodiment runs through each business link of the order, and therefore, through the business equipment identification and the user identifications recorded in the order identification code, a plurality of users can be ensured to pay for the order.
The invention can respectively push the payment order to each ordering user so that each ordering user has the authority to pay. In the above manner, the order amounts of the payment orders received by the individual ordering users are the same, and in order to facilitate user sharing, a notification message may be further sent to each unpaid user, so that each unpaid user completes payment to the paid user.
In addition, the service device identifier in the present invention may be a table code, a store code, and the present invention is not limited thereto. In addition, the invention also provides a payment method based on multi-person ordering, which is applied to a client and comprises the following steps:
step one, sending a ordering service request containing a service equipment identifier and a user identifier to an ordering server so that the ordering server can create an order data record corresponding to the service equipment identifier; the order identification code of the order data record comprises the service equipment identification and a plurality of user identifications associated with the service equipment identification;
and step two, receiving a payment order which is pushed by the order ordering server and corresponds to the order data record so as to carry out payment according to the payment order.
Finally, it should be emphasized that the valid billing identification in step S210 is not necessary, and in some simple service scenarios, the service devices are all disposable, so the valid billing identification can be omitted. Correspondingly, in step S210, a service device-based order service request sent by the user terminal is received, and a service device identifier and a user identifier included in the received order service request are obtained; and determining an order data record associated with the service equipment identifier, and storing the user identifier and the service equipment identifier contained in the order service request received this time into an order identifier code of the order data record in an associated manner, so as to create the order data record corresponding to the service equipment identifier. When the order data record associated with the service equipment identifier is determined, the user identifier contained in the order service request received this time is stored in the order identifier of the order data record in an associated manner with the service equipment identifier, and when the order data record associated with the service equipment identifier is determined to be created, the user identifier contained in the order service request received this time is added to the order identifier of the created order data record associated with the service equipment identifier; when the order data record associated with the business equipment identification is determined not to be created, creating the order data record associated with the business equipment identification; and storing the service equipment identifier and the user identifier contained in the order service request received this time into the order identifier of the created order data record associated with the service equipment identifier.
EXAMPLE III
Fig. 3 is a schematic structural diagram illustrating a payment server based on multiple ordering lists according to a third embodiment of the present invention, where the server includes:
the receiving module 31 is adapted to create an order data record corresponding to the service equipment identifier according to the service equipment identifier and the user identifier included in each received order service request; the order identification code of the order data record comprises the service equipment identification and a plurality of user identifications associated with the service equipment identification;
the generating module 32 is adapted to generate a payment order corresponding to the order data record, and push the payment order to the user terminals corresponding to the user identifiers included in the order identifier of the order data record;
the payment module 33 is adapted to pay the payment order according to the received payment request triggered for the payment order.
Optionally, the payment module is specifically adapted to:
judging whether the user identification contained in the payment request is matched with the order identification code of the order data record corresponding to the payment order or not;
and if so, paying the payment order according to the payment request.
Optionally, the payment module is specifically adapted to:
when a payment request triggered by the payment order is received, judging whether the payment order corresponding to the order data record is paid or not according to a service state field contained in the order data record corresponding to the payment order;
if not, the payment order is paid according to the received payment request triggered aiming at the payment order, and the service state field contained in the order data record corresponding to the payment order is updated according to the payment result.
Optionally, the payment module is further adapted to: and when the payment order corresponding to the order data record is judged to be paid, rejecting the payment request and pushing a paid notice to a user terminal corresponding to the payment request.
Optionally, the payment module is specifically adapted to:
determining a paid user corresponding to the payment order according to a user identifier contained in the payment request;
determining at least one unpaid user corresponding to the payment order according to the order identification code of the order data record corresponding to the payment request;
determining the amount to be paid corresponding to each unpaid user according to the order amount data of the payment order and the number of the unpaid users;
and sending a payment notification message containing the amount to be paid to each unpaid user, and updating account data corresponding to the user account of the paid user according to the payment request when receiving the payment request triggered by each unpaid user aiming at the payment notification message.
Optionally, the generating module is specifically adapted to:
when an order submission request triggered by the order data record is received, generating a payment order corresponding to the order data record;
and copying the payment order into a plurality of copies according to the number of the user identifications contained in the order identification code of the order data record, and respectively pushing each copied payment order to each user terminal corresponding to the user identification contained in the order identification code of the order data record.
Optionally, the receiving module is specifically adapted to:
when a ordering service request is received, acquiring a service equipment identifier and a user identifier contained in the received ordering service request, and judging whether an effective ordering identifier associated with the service equipment identifier exists in a preset ordering data table or not;
if yes, acquiring the created order data record corresponding to the service equipment identifier and the effective order opening identifier, and adding the user identifier contained in the order service request received this time into the order identifier of the order data record;
if not, generating an effective billing identifier associated with the service equipment identifier, storing the service equipment identifier and the effective billing identifier in the billing data table in an associated manner, and creating an order data record corresponding to the service equipment identifier and the effective billing identifier, wherein the order identifier of the order data record comprises the service equipment identifier, the effective billing identifier and a user identifier contained in the received order service request.
Optionally, the ordering service request includes: and scanning the code order request based on the information code, wherein the information code comprises a service equipment identifier.
Optionally, the payment order includes an order identification code of the order data record, and the payment request triggered for the payment order includes: and the order identification code of the order data record corresponding to the payment order to be paid.
The specific structure and operation principle of each module described above may refer to the description of the corresponding part in the method embodiment, and are not described herein again.
In addition, the invention also provides a payment client based on the multi-person ordering, which comprises:
the system comprises a sending module, a receiving module and a sending module, wherein the sending module is suitable for sending a ordering service request containing a service equipment identifier and a user identifier to an ordering server so that the ordering server can create an order data record corresponding to the service equipment identifier; the order identification code of the order data record comprises the service equipment identification and a plurality of user identifications associated with the service equipment identification;
and the receiving module is suitable for receiving the payment order which is pushed by the ordering server and corresponds to the order data record so as to carry out payment according to the payment order.
In addition, the invention also provides a payment system based on the multi-person ordering, which comprises: the payment server and the payment client are provided.
Example four
The fourth embodiment of the present application provides a non-volatile computer storage medium, where the computer storage medium stores at least one executable instruction, and the computer executable instruction may execute the payment method based on multi-person ordering in any of the above method embodiments. The executable instructions may be specifically configured to cause a processor to perform respective operations corresponding to the above-described method embodiments.
EXAMPLE five
Fig. 4 is a schematic structural diagram of an electronic device according to a fifth embodiment of the present invention, and the specific embodiment of the present invention does not limit the specific implementation of the electronic device.
As shown in fig. 4, the electronic device may include: a processor (processor)402, a Communications Interface 406, a memory 404, and a Communications bus 408.
Wherein:
the processor 402, communication interface 406, and memory 404 communicate with each other via a communication bus 408.
A communication interface 406 for communicating with network elements of other devices, such as clients or other servers.
The processor 402 is configured to execute the program 410, and may specifically execute relevant steps in the above-described multi-order payment method embodiment.
In particular, program 410 may include program code comprising computer operating instructions.
The processor 402 may be a central processing unit CPU, or an application specific Integrated circuit asic, or one or more Integrated circuits configured to implement an embodiment of the present invention. The electronic device comprises one or more processors, which can be the same type of processor, such as one or more CPUs; or may be different types of processors such as one or more CPUs and one or more ASICs.
And a memory 404 for storing a program 410. The memory 404 may comprise high-speed RAM memory, and may also include non-volatile memory (non-volatile memory), such as at least one disk memory.
The program 510 may be specifically configured to enable the processor 502 to execute the corresponding operations in the above method embodiments.
The algorithms and displays presented herein are not inherently related to any particular computer, virtual machine, or other apparatus. Various general purpose systems may also be used with the teachings herein. The required structure for constructing such a system will be apparent from the description above. Moreover, the present invention is not directed to any particular programming language. It is appreciated that a variety of programming languages may be used to implement the teachings of the present invention as described herein, and any descriptions of specific languages are provided above to disclose the best mode of the invention.
In the description provided herein, numerous specific details are set forth. It is understood, however, that embodiments of the invention may be practiced without these specific details. In some instances, well-known methods, structures and techniques have not been shown in detail in order not to obscure an understanding of this description.
Similarly, it should be appreciated that in the foregoing description of exemplary embodiments of the invention, various features of the invention are sometimes grouped together in a single embodiment, figure, or description thereof for the purpose of streamlining the disclosure and aiding in the understanding of one or more of the various inventive aspects. However, the disclosed method should not be interpreted as reflecting an intention that: that the invention as claimed requires more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive aspects lie in less than all features of a single foregoing disclosed embodiment. Thus, the claims following the detailed description are hereby expressly incorporated into this detailed description, with each claim standing on its own as a separate embodiment of this invention.
Those skilled in the art will appreciate that the modules in the device in an embodiment may be adaptively changed and disposed in one or more devices different from the embodiment. The modules or units or components of the embodiments may be combined into one module or unit or component, and furthermore they may be divided into a plurality of sub-modules or sub-units or sub-components. All of the features disclosed in this specification (including any accompanying claims, abstract and drawings), and all of the processes or elements of any method or apparatus so disclosed, may be combined in any combination, except combinations where at least some of such features and/or processes or elements are mutually exclusive. Each feature disclosed in this specification (including any accompanying claims, abstract and drawings) may be replaced by alternative features serving the same, equivalent or similar purpose, unless expressly stated otherwise.
Furthermore, those skilled in the art will appreciate that while some embodiments described herein include some features included in other embodiments, rather than other features, combinations of features of different embodiments are meant to be within the scope of the invention and form different embodiments. For example, in the following claims, any of the claimed embodiments may be used in any combination.
The various component embodiments of the invention may be implemented in hardware, or in software modules running on one or more processors, or in a combination thereof. Those skilled in the art will appreciate that a microprocessor or Digital Signal Processor (DSP) may be used in practice to implement some or all of the functions of some or all of the components in a voice input information based lottery system according to embodiments of the present invention. The present invention may also be embodied as apparatus or device programs (e.g., computer programs and computer program products) for performing a portion or all of the methods described herein. Such programs implementing the present invention may be stored on computer-readable media or may be in the form of one or more signals. Such a signal may be downloaded from an internet website or provided on a carrier signal or in any other form.
It should be noted that the above-mentioned embodiments illustrate rather than limit the invention, and that those skilled in the art will be able to design alternative embodiments without departing from the scope of the appended claims. In the claims, any reference signs placed between parentheses shall not be construed as limiting the claim. The word "comprising" does not exclude the presence of elements or steps not listed in a claim. The word "a" or "an" preceding an element does not exclude the presence of a plurality of such elements. The invention may be implemented by means of hardware comprising several distinct elements, and by means of a suitably programmed computer. In the unit claims enumerating several means, several of these means may be embodied by one and the same item of hardware. The usage of the words first, second and third, etcetera do not indicate any ordering. These words may be interpreted as names.
Claims (10)
1. A multi-person ordering-based payment method, comprising:
according to a service equipment identifier and a user identifier contained in each received order service request, creating an order data record corresponding to the service equipment identifier; the order identification code of the order data record comprises the service equipment identification and a plurality of user identifications associated with the service equipment identification;
generating a payment order corresponding to the order data record, and respectively pushing the payment order to a user terminal corresponding to each user identifier contained in the order identifier of the order data record;
and paying the payment order according to the received payment request triggered aiming at the payment order.
2. The method of claim 1, wherein the paying for the payment order according to the received payment request triggered for the payment order specifically comprises:
judging whether the user identification contained in the payment request is matched with the order identification code of the order data record corresponding to the payment order or not;
and if so, paying the payment order according to the payment request.
3. The method of claim 1, wherein the paying for the payment order according to the received payment request triggered for the payment order specifically comprises:
when a payment request triggered by the payment order is received, judging whether the payment order corresponding to the order data record is paid or not according to a service state field contained in the order data record corresponding to the payment order;
if not, the payment order is paid according to the received payment request triggered aiming at the payment order, and the service state field contained in the order data record corresponding to the payment order is updated according to the payment result.
4. The method of claim 3, wherein after determining whether the payment order corresponding to the order data record has been paid, further comprising:
and if so, rejecting the payment request and pushing a paid notification to a user terminal corresponding to the payment request.
5. A multi-person ordering-based payment method, comprising:
sending a ordering service request containing a service equipment identifier and a user identifier to an ordering server so that the ordering server can create an order data record corresponding to the service equipment identifier; the order identification code of the order data record comprises the service equipment identification and a plurality of user identifications associated with the service equipment identification;
and receiving a payment order which is pushed by the order ordering server and corresponds to the order data record so as to carry out payment according to the payment order.
6. A multi-person order-based payment server comprising:
the receiving module is suitable for creating order data records corresponding to the service equipment identifications according to the service equipment identifications and the user identifications contained in the received ordering service requests; the order identification code of the order data record comprises the service equipment identification and a plurality of user identifications associated with the service equipment identification;
the generating module is suitable for generating a payment order corresponding to the order data record and pushing the payment order to the user terminals corresponding to the user identifications contained in the order identification codes of the order data record;
and the payment module is suitable for paying the payment order according to the received payment request triggered aiming at the payment order.
7. A multi-person order-based payment client, comprising:
the system comprises a sending module, a receiving module and a sending module, wherein the sending module is suitable for sending a ordering service request containing a service equipment identifier and a user identifier to an ordering server so that the ordering server can create an order data record corresponding to the service equipment identifier; the order identification code of the order data record comprises the service equipment identification and a plurality of user identifications associated with the service equipment identification;
and the receiving module is suitable for receiving the payment order which is pushed by the ordering server and corresponds to the order data record so as to carry out payment according to the payment order.
8. A multi-person ordering-based payment system, comprising: the payment server of claim 6, and the payment client of claim 7.
9. An electronic device, comprising: the system comprises a processor, a memory, a communication interface and a communication bus, wherein the processor, the memory and the communication interface complete mutual communication through the communication bus;
the memory is used for storing at least one executable instruction, and the executable instruction causes the processor to execute the operation corresponding to the payment method based on the multi-person order form in any one of claims 1-4.
10. A computer storage medium having stored therein at least one executable instruction to cause a processor to perform operations corresponding to the multi-person ordering-based payment method according to any one of claims 1-4.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910918561.2A CN110689334A (en) | 2019-09-26 | 2019-09-26 | Payment method, server, client and system based on multi-person order ordering |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910918561.2A CN110689334A (en) | 2019-09-26 | 2019-09-26 | Payment method, server, client and system based on multi-person order ordering |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN110689334A true CN110689334A (en) | 2020-01-14 |
Family
ID=69110466
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910918561.2A Pending CN110689334A (en) | 2019-09-26 | 2019-09-26 | Payment method, server, client and system based on multi-person order ordering |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110689334A (en) |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111667349A (en) * | 2020-06-30 | 2020-09-15 | 拉扎斯网络科技（上海）有限公司 | Order combining method, client, server and system based on social application |
| CN111784481A (en) * | 2020-08-03 | 2020-10-16 | 支付宝(杭州)信息技术有限公司 | Code scanning ordering method, service code creating device and electronic equipment |
| CN112288552A (en) * | 2020-11-23 | 2021-01-29 | 拉扎斯网络科技（上海）有限公司 | Order combining method, server, client and system |
| CN113592486A (en) * | 2020-04-30 | 2021-11-02 | 华为技术有限公司 | Payment method, system and related equipment based on cloud application example |
Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103985046A (en) * | 2014-04-18 | 2014-08-13 | 谭君 | Intelligent terminal synergetic food ordering system and method based on two-dimension codes and NFC labels |
| CN104978697A (en) * | 2015-06-24 | 2015-10-14 | 西南石油大学 | Two-dimensional code-based cooperative intelligent ordering method and system |
| CN104992357A (en) * | 2015-07-10 | 2015-10-21 | 拉扎斯网络科技（上海）有限公司 | Order combining method and device |
| CN106096940A (en) * | 2016-06-03 | 2016-11-09 | 乐视控股（北京）有限公司 | A kind of method of payment and device |
| CN107909442A (en) * | 2017-11-22 | 2018-04-13 | 北京新弘宝科技有限公司 | A kind of Duo Ren groups dining binding and deactivation system, method and intelligent table |
| CN108053301A (en) * | 2018-01-22 | 2018-05-18 | 杭州迪火科技有限公司 | Multi-person synergy ordering system and multi-person synergy ordering method |
| CN108717671A (en) * | 2018-05-16 | 2018-10-30 | 浙江口碑网络技术有限公司 | User's service for life relation recognition method and device based on table code mark |
| CN109635213A (en) * | 2018-12-14 | 2019-04-16 | 口碑(上海)信息技术有限公司 | A kind of implementation method that more people order, device and electronic equipment |
| CN109739890A (en) * | 2018-12-29 | 2019-05-10 | 浙江口碑网络技术有限公司 | Data processing method, device and equipment |
| CN109816473A (en) * | 2018-12-19 | 2019-05-28 | 平安科技（深圳）有限公司 | Payment and settlement processing method, apparatus and system based on cloud transmission |
-
2019
- 2019-09-26 CN CN201910918561.2A patent/CN110689334A/en active Pending
Patent Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103985046A (en) * | 2014-04-18 | 2014-08-13 | 谭君 | Intelligent terminal synergetic food ordering system and method based on two-dimension codes and NFC labels |
| CN104978697A (en) * | 2015-06-24 | 2015-10-14 | 西南石油大学 | Two-dimensional code-based cooperative intelligent ordering method and system |
| CN104992357A (en) * | 2015-07-10 | 2015-10-21 | 拉扎斯网络科技（上海）有限公司 | Order combining method and device |
| CN106096940A (en) * | 2016-06-03 | 2016-11-09 | 乐视控股（北京）有限公司 | A kind of method of payment and device |
| CN107909442A (en) * | 2017-11-22 | 2018-04-13 | 北京新弘宝科技有限公司 | A kind of Duo Ren groups dining binding and deactivation system, method and intelligent table |
| CN108053301A (en) * | 2018-01-22 | 2018-05-18 | 杭州迪火科技有限公司 | Multi-person synergy ordering system and multi-person synergy ordering method |
| CN108717671A (en) * | 2018-05-16 | 2018-10-30 | 浙江口碑网络技术有限公司 | User's service for life relation recognition method and device based on table code mark |
| CN109635213A (en) * | 2018-12-14 | 2019-04-16 | 口碑(上海)信息技术有限公司 | A kind of implementation method that more people order, device and electronic equipment |
| CN109816473A (en) * | 2018-12-19 | 2019-05-28 | 平安科技（深圳）有限公司 | Payment and settlement processing method, apparatus and system based on cloud transmission |
| CN109739890A (en) * | 2018-12-29 | 2019-05-10 | 浙江口碑网络技术有限公司 | Data processing method, device and equipment |
Cited By (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113592486A (en) * | 2020-04-30 | 2021-11-02 | 华为技术有限公司 | Payment method, system and related equipment based on cloud application example |
| CN113592486B (en) * | 2020-04-30 | 2024-04-12 | 华为云计算技术有限公司 | Payment method, system and related equipment based on cloud application instance |
| CN111667349A (en) * | 2020-06-30 | 2020-09-15 | 拉扎斯网络科技（上海）有限公司 | Order combining method, client, server and system based on social application |
| CN111667349B (en) * | 2020-06-30 | 2021-03-09 | 拉扎斯网络科技（上海）有限公司 | Order combining method, client, server and system based on social application |
| CN111784481A (en) * | 2020-08-03 | 2020-10-16 | 支付宝(杭州)信息技术有限公司 | Code scanning ordering method, service code creating device and electronic equipment |
| CN111784481B (en) * | 2020-08-03 | 2023-08-08 | 支付宝（中国）网络技术有限公司 | Code scanning ordering method, service code creating method, device and electronic equipment |
| CN112288552A (en) * | 2020-11-23 | 2021-01-29 | 拉扎斯网络科技（上海）有限公司 | Order combining method, server, client and system |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110738479B (en) | Order management method and system based on multi-person ordering | |
| CN110689334A (en) | Payment method, server, client and system based on multi-person order ordering | |
| CN110728505A (en) | Payment method, server, client and system based on multi-person order ordering | |
| EP3574965A1 (en) | Method for realizing user matching and related device | |
| CN111667349B (en) | Order combining method, client, server and system based on social application | |
| CN111770184B (en) | Method and device for realizing service based on small program | |
| CN111667348A (en) | Order splicing method and device | |
| CN112162806B (en) | Popup display method, terminal and computer storage medium | |
| CN110706070A (en) | Multi-user order ordering method, server, client and system | |
| CN109523336A (en) | Data processing method, device, electronic equipment and readable storage medium storing program for executing | |
| CN108122124B (en) | Information pushing method, platform and system | |
| CN110930163B (en) | Method, system and storage medium for implementing house source entrusting business | |
| CN111111216B (en) | Matching method, device, server and storage medium | |
| CN110545233B (en) | Information pushing method and device, electronic equipment and storage medium | |
| CN112905295B (en) | Data intercommunication method, computing device and computer storage medium | |
| CN110852603A (en) | High-throughput wind control data processing method, device, equipment and storage medium | |
| CN110889073A (en) | Page request response method, server and computer storage medium | |
| CN111147568B (en) | Identity data synchronization method and device | |
| CN113132928B (en) | Charging method and device for video short message service | |
| CN110175182B (en) | Data checking method and device | |
| CN112749190B (en) | Data query method and device, computing equipment and computer storage medium | |
| CN111031052A (en) | Data processing method based on multiple application programs, computing equipment and storage medium | |
| TWI659635B (en) | System and method for service matching of instant message software | |
| CN112016881B (en) | Method and system for triggering business activities | |
| WO2023029830A1 (en) | Electronic certificate generation method and apparatus, electronic device, and readable storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20200114 |
|
| RJ01 | Rejection of invention patent application after publication |