WO2021129188A1 - 基于图形码的业务处理方法及装置、电子设备、存储介质 - Google Patents

基于图形码的业务处理方法及装置、电子设备、存储介质 Download PDF

Info

Publication number
WO2021129188A1
WO2021129188A1 PCT/CN2020/126970 CN2020126970W WO2021129188A1 WO 2021129188 A1 WO2021129188 A1 WO 2021129188A1 CN 2020126970 W CN2020126970 W CN 2020126970W WO 2021129188 A1 WO2021129188 A1 WO 2021129188A1
Authority
WO
WIPO (PCT)
Prior art keywords
service
business
information
participant
basic information
Prior art date
Application number
PCT/CN2020/126970
Other languages
English (en)
French (fr)
Inventor
尹俊
孙曦
郑吉�
Original Assignee
支付宝实验室(新加坡)有限公司
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by 支付宝实验室(新加坡)有限公司 filed Critical 支付宝实验室(新加坡)有限公司
Publication of WO2021129188A1 publication Critical patent/WO2021129188A1/zh

Links

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/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
    • G06Q20/32—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using wireless devices
    • G06Q20/327—Short range or proximity payments by means of M-devices
    • G06Q20/3276—Short range or proximity payments by means of M-devices using a pictured code, e.g. barcode or QR-code, being read by the M-device

Definitions

  • One or more embodiments of this specification relate to the field of communication technology, and in particular to a service processing method and device based on graphic codes, electronic equipment, and storage media.
  • Graphic codes can be used to express text and numerical information through certain coding rules, so that they can be automatically read by image input equipment or photoelectric scanning equipment to realize automatic information processing.
  • Graphic codes include two-dimensional codes, bar codes, and so on. Taking a two-dimensional code as an example, a two-dimensional code is a black and white figure distributed on a plane (in a two-dimensional direction) using a specific geometric figure according to a certain rule.
  • the two-dimensional code cleverly uses the concept of "0" and "1" bit streams that constitute the internal logic of the computer in the coding of the code, and uses several geometric shapes corresponding to the binary system to represent the text and numerical information. For example, merchants or individuals can generate a payment code through their own acquiring information, so that other users can scan the payment code for payment and transfer.
  • one or more embodiments of this specification provide a graphic code-based service processing method and device, electronic equipment, and storage medium.
  • a service processing method based on graphic codes is proposed, which is applied to a client of a service requesting party.
  • the method includes: parsing service graphic codes of service participants to obtain The identification information of the business participant, the business participant is associated with at least one business response server, and each associated business response server is configured with corresponding business basic information for the business participant, and each associated The mapping relationship between the business basic information generated by the business response server for the business participant and the identification information is uploaded to the indexing platform for recording; based on the identification information, the indexing platform sends the information for the business participant to the indexing platform.
  • the index platform determines the basic information of the candidate service corresponding to the identification information according to the recorded mapping relationship; obtains basic information of the target service that matches the client of the service requester in the basic information of the candidate service , And implement business processing related to the business participant based on the basic information of the target business and the business supplementary information input by the business requester into the client of the business requester.
  • a service processing method based on graphic codes is proposed, which is applied to an indexing platform, and the method includes: receiving a service requester client and sending information based on the identification information of the service participant For the query request for the business participant, the business participant is associated with at least one business response server, and each associated business response server is configured with corresponding business basic information for the business participant, and each related The mapping relationship between the business basic information and the identification information generated by the business response server for the business participants is uploaded to the index platform for recording, and the identification information is parsed by the business requester client.
  • the service graphic code of the participant is obtained; the candidate service basic information corresponding to the identification information is determined according to the recorded mapping relationship, so that the service requester client is based on the candidate service basic information and the service requester client.
  • the service basic information that matches the end and the service requester enters the service supplementary information of the service requester client to implement service processing related to the service participant.
  • a method for maintaining basic business information which includes: when any business response server establishes an association relationship with a business participant, obtaining any business response
  • the server configures the basic information of the business to be merged for the business participant; and sends an adding request for the mapping relationship between the basic information of the business to be merged and the identification information of the business participant to the indexing platform, so that the indexing platform Record the mapping relationship; wherein the mapping relationship between the identification information and the corresponding business basic information recorded by the index platform is used to receive the service requester client sent by the service requester client based on the identification information on the index platform for the
  • the candidate business basic information corresponding to the identification information is determined, and the business basic information used by the service requester client to process the business related to the business participant is the The basic service information that matches the service requester client in the candidate service basic information, the service supplementary information used by the service requester client to implement the service processing is input by the service requester
  • a service processing device based on graphic codes is proposed, which is applied to a client of a service requesting party.
  • the device includes: an identification analysis unit that analyzes the service graphics of the service participants Code to obtain the identification information of the business participant, the business participant is associated with at least one business response server, and each associated business response server is configured with corresponding business basic information for the business participant, The mapping relationship between the business basic information generated by each associated business response server for the business participant and the identification information is uploaded to the index platform for recording; the sending unit sends to the index platform based on the identification information In response to the query request of the service participant, the index platform determines the basic information of the candidate service corresponding to the identification information according to the recorded mapping relationship; the service processing unit obtains the basic information of the candidate service and the service The basic information of the target business matched by the requester client, and the business processing related to the business participant is implemented based on the basic information of the target business and the business supplementary information input by the service requester of the business request
  • a service processing device based on graphic codes which is applied to an indexing platform.
  • the device includes: a first receiving unit that receives a service requesting client based on service participation A query request for the business participant sent by the identification information of the party, the business participant is associated with at least one business response server, and each associated business response server is configured with a corresponding business for the business participant Basic information, the mapping relationship between the business basic information generated by each associated business response server for the business participant and the identification information is uploaded to the index platform for recording, and the identification information is provided by the business requester client
  • the terminal parses the service graphic code of the service participant to obtain; the determining unit determines the basic information of the candidate service corresponding to the identification information according to the recorded mapping relationship, so that the client of the service requester is based on the basic information of the candidate service
  • the service basic information matched with the service requester client terminal and the service supplementary information of the service requester client input by the service requester in the service requester client are used
  • a device for maintaining basic business information including: an acquiring unit, when any business response server establishes an association relationship with a business participant, acquiring the task
  • a business response server configures the basic information of the business to be merged for the business participant;
  • the sending unit sends to the indexing platform an adding request for the mapping relationship between the basic information of the business to be merged and the identification information of the business participant, So that the indexing platform records the mapping relationship; wherein the mapping relationship between the identification information recorded by the indexing platform and the corresponding business basic information is used to receive the service requester client on the indexing platform based on the identification
  • the candidate service basic information corresponding to the identification information is determined, and the service used by the service requester client to implement the service processing related to the service participant Basic information is the basic service information that matches the service requester client in the candidate service basic information, and the service supplementary information used by the service requester client to implement the service processing is input by the
  • an electronic device including: a processor; a memory for storing executable instructions of the processor; wherein the processor runs the executable instructions In order to realize the service processing method based on the graphic code as described in the above first aspect.
  • an electronic device including: a processor; a memory for storing executable instructions of the processor; wherein the processor runs the executable instructions In order to realize the service processing method based on the graphic code as described in the above second aspect.
  • an electronic device including: a processor; a memory for storing executable instructions of the processor; wherein the processor runs the executable instructions In order to realize the service processing method based on the graphic code as described in the above third aspect.
  • a computer-readable storage medium is provided with computer instructions stored thereon, and when the instructions are executed by a processor, the method as described in any of the above-mentioned first aspects is implemented A step of.
  • a computer-readable storage medium is provided with computer instructions stored thereon, and when the instructions are executed by a processor, the implementation of any of the foregoing Method steps.
  • a computer-readable storage medium is provided with computer instructions stored thereon, and when the instructions are executed by a processor, the implementation is as described in any of the above third aspects. Method steps.
  • Fig. 1 is a schematic structural diagram of a service processing system based on graphic codes provided by an exemplary embodiment.
  • Fig. 2 is a flowchart of a service processing method based on graphic codes provided by an exemplary embodiment.
  • Fig. 3 is a flowchart of another service processing method based on graphic codes provided by an exemplary embodiment.
  • Fig. 4 is a flowchart of a method for maintaining business information according to an exemplary embodiment.
  • Fig. 5 is a schematic diagram of a code scanning payment architecture provided by an exemplary embodiment.
  • Fig. 6 is a schematic diagram of a method for maintaining business information provided by an exemplary embodiment.
  • Fig. 7 is a schematic diagram of payment based on a payment code provided by an exemplary embodiment.
  • Fig. 8 is a schematic structural diagram of a device provided by an exemplary embodiment.
  • Fig. 9 is a block diagram of a service processing device based on a graphic code provided by an exemplary embodiment.
  • Fig. 10 is a schematic structural diagram of another device provided by an exemplary embodiment.
  • Fig. 11 is a block diagram of another apparatus for processing a service based on a graphic code according to an exemplary embodiment.
  • Fig. 12 is a schematic structural diagram of another device provided by an exemplary embodiment.
  • Fig. 13 is a block diagram of an apparatus for maintaining service information according to an exemplary embodiment.
  • the steps of the corresponding method may not be executed in the order shown and described in this specification.
  • the method may include more or fewer steps than described in this specification.
  • a single step described in this specification may be decomposed into multiple steps for description in other embodiments; and multiple steps described in this specification may also be combined into a single step in other embodiments. description.
  • the business response server can establish an association relationship with the business participants to provide corresponding business support to the business participants, and after the association relationship is established, the business response server configures the corresponding business basic information to the business participants For use in processing business.
  • the service requester client interacts with the service response server based on the basic service information and the service supplementary information corresponding to the service to be processed to complete the pending service.
  • the process of handling business For example, the service supplementary information can be input by the service requester to the service requester client.
  • the business participant when the business basic information configured by the business response server is fixed, the business participant (or the business response server, the commissioned technical service provider, etc.) can output the basic business information in the form of graphic codes to The business requester provides basic business information needed to complete the business.
  • the service participant can print and post the graphic code for analysis by the service requester; or, the service participant can display the graphic code to the service requester through the client of the service participant.
  • the service requester can parse the graphic code through the service requester client to obtain basic service information, and enter the service supplementary information of the service to be processed (related to the service participant) in the service requester client, and then based on the obtained The business basic information and the input business supplementary information are processed for the to-be-processed business.
  • each business response server can provide business support to business participants, that is, business participants can establish an association relationship with multiple business response servers, and each associated business response The server is configured with corresponding business basic information for the client of the business participant.
  • each business response server has its own corresponding business requester client, and the business requester client can complete the business processing through the business basic information configured by the business response server matching itself.
  • corresponding graphic codes can be generated for each business basic information configured by each business response server.
  • each graphic code has a one-to-one correspondence with the business response server.
  • the user uses a payment client (such as a mobile phone, that is, the business requester client) installed with a mobile payment App to scan the payment code displayed by the merchant (business participant) (For example, a QR code for receiving payment), the payment code contains the merchant's acquiring information on the corresponding payment platform (business response server) (or the payment code contains the access path to obtain the acquiring information). Access to the back-end server to obtain further information), the mobile payment App obtains the merchant's acquiring information (business basic information) by parsing the payment code and displays it on the App interface for confirmation by the user. The user confirms that the merchant's acquiring information is correct. You can enter order information (that is, business supplementary information, provided by the merchant; for example, transaction amount) and submit a payment application, so that the mobile payment App can be docked with the payment platform to complete the subsequent payment process.
  • a payment client such as a mobile phone, that is, the business requester client
  • a mobile payment App to scan the payment code displayed by the merchant (business participant)
  • the same merchant may cooperate with multiple different payment platforms (for example, with Alipay, WeChat and other payment platforms), and each payment platform will allocate corresponding acquiring information for the merchant (for example, the account and identification assigned to the merchant) Number, payment platform name, payment platform access address, etc.). Then, when a merchant supports multiple payment platforms, each payment platform will generate a corresponding payment code according to the allocated acquiring information for the merchant to display to the user. For example, the merchant can post it on the merchant's storefront for the user to scan the code for payment. In this way, there is a situation of "one household with multiple codes", that is, a merchant's storefront is posted with merchant collection codes generated by multiple payment platforms. Since mobile payment apps are usually associated with payment platforms (that is, each payment platform has a corresponding mobile payment app), users need to select the payment code supported by the mobile payment app installed by themselves to scan to complete the payment.
  • mobile payment apps are usually associated with payment platforms (that is, each payment platform has a corresponding mobile payment app)
  • the same user can register on multiple social platforms (business response server) to obtain account information (business basic information), then when adding friends (business to be processed), the user It is necessary to show the QR codes of each social platform (generated according to the account information) to other users (service requesters) to scan the codes to add friends.
  • account information business basic information
  • service requesters users
  • the QR code to obtain the user's account information through their mobile phones
  • they enter their own verification information ie, supplementary business information; such as their own user name, account, remarks, etc.
  • This manual aims to provide a business processing solution based on graphic codes, which can merge the graphic codes corresponding to the respective services of each business under the condition that the client of the same business participant and multiple business response servers are associated with each other.
  • each service requester can scan the graphic code that supports interoperability to implement service processing related to the client of the service participant.
  • the graphic code corresponding to the new business response server can also be merged without changing the graphic code that supports interoperability, thereby Reduce costs and improve business processing efficiency.
  • Fig. 1 is a schematic structural diagram of a service processing system based on graphic codes provided by an exemplary embodiment.
  • the system may include a server 11, a network 12, and several electronic devices, such as a mobile phone 13, a mobile phone 14, a PC15, and a PC16.
  • the server 11 may be a physical server including an independent host, or the server 11 may be a virtual server carried by a host cluster. During operation, the server 11 serves as an indexing platform for recording basic business information of the clients of each business participant for query.
  • Mobile phones 13-14 and PC15-16 are only two types of electronic devices that can be used by the service participant or service requester. In fact, it is obvious that you can also use electronic devices such as the following types: tablet devices, notebook computers, PDAs (Personal Digital Assistants), wearable devices (such as smart glasses, smart watches, etc.), etc. One or more of this manual This embodiment does not limit this.
  • the electronic device can be used as a client of a service participant or a client of a service requester.
  • the business response server establishes an association relationship with the business participant client, and configures basic business information to the business participant client to be obtained by the business requester client (when there is a pending service between the service participant and the business participant)
  • the configured basic business information is used to complete business processing based on the basic business information and supplementary business information corresponding to the business to be processed.
  • the network 12 that interacts between various electronic devices and the server 11 may include multiple types of wired or wireless networks.
  • the network 12 may include a Public Switched Telephone Network (PSTN) and the Internet.
  • PSTN Public Switched Telephone Network
  • electronic devices such as mobile phones 13-14 and PC15-16 can also communicate and interact through the network 12.
  • Fig. 2 is a flowchart of a service processing method based on graphic codes provided by an exemplary embodiment. As shown in Fig. 2, the method is applied to the client of the service requester and may include steps 202-206.
  • Step 202 Parse the service graphic code of the service participant to obtain the identification information of the service participant.
  • the service participant is associated with at least one service response server, and each associated service response server is specific to the service.
  • the participants are configured with corresponding business basic information, and the mapping relationship between the business basic information generated by each associated business response server for the business participants and the identification information is uploaded to the index platform for recording.
  • the business response server provides support for a certain business to the business participant.
  • the business response server configures basic business information to the business participant.
  • the basic business information is the information needed to implement the business.
  • the business requester can use the business requester client that matches the business response server, based on the business foundation configured by the business response server Information implementation business processing.
  • the service requester includes the payer (that is, the service requester client includes the payment client), the service graphic code includes the payment graphic code, and the business participants include the merchant (that is, the service participant
  • the party client includes the merchant client), the business response server associated with the merchant client includes the payment platform server, and each payment platform server is configured with corresponding acquiring information (ie, basic business information) for the merchant client; for example, Merchant client account information).
  • the payment platform can allocate the corresponding account, identification number and other acquiring information to the merchant as the basic business information of the payment service. Then, when the user needs to pay for the business with the merchant (for example, the user purchases goods from the merchant, and then needs to pay the corresponding fee to the merchant), the user can use the mobile payment App (installed in the user's electronic device) based on the above-mentioned acquiring The information interacts with the payment platform to complete the business of paying fees to the merchant's account registered on the payment platform.
  • an index platform is configured in the business processing system based on graphic codes to record the business basic information of each business participant.
  • the business participant can send a registration request to the indexing platform through the client of the business participant, so that the indexing platform allocates unique identification information to the business participant. Then, the indexing platform can record the mapping relationship between the identification information of the business participant and the business basic information of the business participant.
  • the business graphic code of the business participant is not used to record basic business information as in related technologies, but is used to record the identification information of the business participant. Since the identification information is used to characterize the identity of the business participant, it has the characteristics of being fixed and unique. Therefore, the business graphic code of the business participant does not need to be changed, and is fixed. Then, the service requester client can scan the service graphic code to analyze the identification information of the service participant, and then query the index platform for the basic business information of the service participant through the identification information, thereby using the basic business information of the service participant The basic information of the business supported by itself is processed in the business.
  • Step 204 Send a query request for the service participant to the indexing platform based on the identification information, so that the indexing platform determines the candidate service basic information corresponding to the identification information according to the recorded mapping relationship.
  • the access address of the indexing platform can be recorded in the service graphic code; in another case, it can also be configured in the service request client corresponding to each service response server
  • the access address of the indexing platform for example, can be written into the installation package of the service request client.
  • the service can be generated by the client of the service participant, the indexing platform or other technical service providers that provide the service graphic code to generate the service graphic code based on the identification information of the service participant and the access address of the indexing platform The business graphic code of the participant. Then, the service requester client can parse the service graphic code to obtain the access address of the index platform, and then send a query request to the index platform according to the access address, and the query request includes the identification information of the service participant.
  • Step 206 Obtain the target service basic information that matches the service requester client in the candidate service basic information, and input the service supplementary information of the service requester client based on the target service basic information and the service requester Implement business processing related to the business participant.
  • the mapping relationship between the business basic information of each business participant and the corresponding identification information is uploaded to the indexing platform for recording. Therefore, the indexing platform can find the basic business information corresponding to the identification information contained in the query request as the basic candidate business information according to the recorded mapping relationship.
  • the index platform can identify the target business basic information that matches the service requester client from the candidate business basic information, and return the identified target business basic information to the sender of the query request (ie, business The requester client), then the service requester client can receive the basic information of the target business returned by the indexing platform to obtain the basic information of the target business.
  • the index platform may directly return the basic information of the candidate service to the client of the service requesting party after obtaining the basic information of the candidate service after querying. Then, the service requester client can receive the basic information of the candidate business returned by the index platform, and identify the basic information of the business matching itself in the basic information of the candidate business as the basic information of the target business.
  • the business response server can record its own server identification in the basic business information when configuring the basic business information.
  • any service basic information records the service end identifier of the service end configuring the any service basic information.
  • the basic business information recorded with the target server identifier can be searched in the basic information of the candidate business, and the found basic business information can be used as the basic information of the target business.
  • the service end identifier of the service response server corresponding to the requester client.
  • the client ID of the sender (the client of the service requester) can be recorded in the query request to determine the server ID corresponding to the client ID.
  • the business request can be sent to the business response server corresponding to the business requester client based on the target business basic information and the business supplementary information entered by the business requester.
  • the business response server is the business response server corresponding to the target server identifier.
  • the business participant includes the merchant
  • the business requester includes the payer
  • the business supplementary information includes the order information of the order to be paid
  • the server includes the payment platform server
  • the basic business information configured by each payment platform server for the merchant includes acquiring information.
  • FIG. 3 is a flowchart of a service processing method based on a graphic code provided by an exemplary embodiment. As shown in Figure 3, the method is applied to an indexing platform and may include steps 302-304.
  • Step 302 Receive a query request for the service participant sent by the service requester client based on the identification information of the service participant, where the service participant is associated with at least one service response server, and each associated service response service
  • the terminal is configured with corresponding business basic information for the business participant, and the mapping relationship between the business basic information generated by each associated business response server for the business participant and the identification information is uploaded to the index platform for recording
  • the identification information is obtained by the service requester client analyzing the service graphic code of the service participant.
  • Step 304 Determine the candidate service basic information corresponding to the identification information according to the recorded mapping relationship, so that the service requester client is based on the service that matches the service requester client in the candidate service basic information.
  • the basic information and the service requester input the service supplementary information of the service requester client to implement the service processing related to the service participant.
  • the other response server when a business participant establishes an association relationship with another business response server other than the currently established relationship, can add the configured business basic information to the index platform for recording; or Other response servers generate the corresponding business graphic code from the configured business basic information, and then return the business graphic code to the business participant, so that the business participant interacts with the indexing platform to record the business basic information of the business graphic code Add to the index platform for recording.
  • the indexing platform receives a first addition request sent by other business response servers associated with the business participant client (the first addition request includes the business participant customer The identification information of the other business response server and the first update service basic information configured for the business participant after establishing an association relationship with the business participant), and add the identification information and the first update service basic information configured to the business participant in the mapping relationship. The corresponding relationship of the first update service basic information.
  • the indexing platform receives a second addition request sent by the client of the business participant.
  • the second addition request contains the identification information, and other business response servers are in contact with the business participant.
  • the second update service basic information configured for the service participant is obtained by the service participant client analyzing the update graphic code from the other service response server.
  • the update graphic code is generated by the other service response server according to the second update service basic information.
  • the indexing platform adds the corresponding relationship between the identification information and the second update service basic information in the recorded mapping relationship.
  • FIG. 4 is a flowchart of a method for maintaining business information according to an exemplary embodiment. As shown in FIG. 4, the method is applied to the client of the business participant or the service response server, and may include steps 402-404.
  • Step 402 When any business response server establishes an association relationship with a business participant, obtain the basic information of the business to be merged configured by the any business response server for the business participant.
  • any business response server when any business response server establishes an association relationship with a business participant, any business response server can interact with the indexing platform, and the basic information of the business to be merged can be added to the indexing platform. Or, the client of the business participant interacts with the indexing platform, and then the basic information of the business to be merged is added to the indexing platform.
  • any business response server After any business response server establishes an association relationship with the business participant, it generates the basic information of the business to be merged corresponding to the business participant, and generates it based on the basic information of the business to be merged
  • the corresponding service graphic code and then the service graphic code is sent to the client of the service participant.
  • the service participant client receives the service graphic code (that is, the service graphic code generated by any service response server based on the basic information of the service to be merged), it can parse it to obtain the basic information of the service to be merged.
  • Step 404 Send an adding request for the mapping relationship between the basic information of the business to be merged and the identification information of the service participant to the indexing platform, so that the indexing platform records the mapping relationship.
  • the mapping relationship between the identification information recorded by the indexing platform and the corresponding business basic information is used to receive the service requester client sent by the indexing platform based on the identification information for the business participation
  • the candidate business basic information corresponding to the identification information is determined, and the business basic information used by the service requester client for the business processing related to the business participant is the candidate business
  • the service basic information that matches the service requester client, the service supplementary information used by the service requester client to implement the service processing is input by the service requester, and the service requester client passes Parse the service graphic code of the service participant to obtain the identification information.
  • the service graphic code is merged into a service graphic code that supports interoperability (the identification information allocated by the indexing platform to the service participants), so that each service requester can scan the service graphic code that supports interoperability to implement the service Participant-related business processing.
  • the service graphic code supporting interoperability only needs to include the identification information allocated by the indexing platform to the service participants, and does not need to include the basic service information allocated by each service response server to the service participants.
  • the service graphic code that supports interoperability contains relatively little information, which is beneficial to improve the efficiency of generating the service graphic code, and improve the accuracy and speed of parsing the service graphic code by the service requester client, thereby improving user experience.
  • the business graphic code corresponding to the new business response server can also be merged without changing the service graphic code that supports interoperability. Thereby reducing costs and improving business processing efficiency.
  • the indexing platform only needs to perform query operations for basic business information, and does not need to perform complex operations involving data processing such as generating business graphic codes, aggregating multiple business graphic codes, and assisting the business requester client to implement business processing, so as to avoid occupying More processing resources; therefore, the smooth progress of the business can be ensured when the performance requirements of the indexing platform are not high.
  • the basic business information configured by each business response server is recorded through the index platform, without the need to merge the basic business information configured by each business response server into one graphic code, and the basic business information configured by each business response server can be retained.
  • the original information format allows each business response server to still generate basic business information according to their respective information formats, so as to provide differentiated services to business participants.
  • FIG. 5 is a schematic diagram of a code scanning payment architecture provided by an exemplary embodiment.
  • the architecture includes an index platform 50, a merchant client 51 used by merchants, a payment platform server 52 of a payment platform, and a payment client 53 used by users.
  • the merchant client 51, the payment platform server 52, and the payment client 53 can access the merchant's acquiring information recorded in the index platform 50 through the merchant's merchant identifier.
  • FIG. 6 is a schematic diagram of a method for maintaining service information according to an exemplary embodiment.
  • the interaction process between the parties may include steps 602-610.
  • step 602 the merchant client 51 registers with the index platform 50 to obtain a merchant identifier.
  • step 604 the merchant client 51 obtains the QR code of the merchant to be merged from the payment platform server 52.
  • a merchant can initiate a registration with the payment platform server 52 through the merchant client 51 to obtain account information on the payment platform.
  • the payment platform server 52 can generate a merchant QR code based on the account information, the name of the payment platform, the access address of the payment platform, and other acquiring information.
  • step 606 the merchant client 51 parses the two-dimensional code of the merchant to be merged to obtain the acquiring information to be merged.
  • the merchant client 51 can scan and analyze the two-dimensional code of the merchant to obtain the above-mentioned acquiring information, that is, the acquiring information to be merged.
  • step 608 the merchant client 51 sends the to-be-combined acquiring information and its own merchant identifier to the indexing platform 50.
  • the merchant client 51 creates an adding request for acquiring information, and the adding request includes the merged acquiring information and its own merchant identifier.
  • Step 610 The indexing platform 50 records the correspondence between the acquiring information and the merchant identifier.
  • the indexing platform reads the acquiring information and the merchant identifier contained therein, and establishes the mapping relationship between the acquiring information and the merchant identifier. Specifically, when the index platform allocates a merchant identifier to a merchant, it can allocate a storage space for the merchant identifier for storing the acquiring information corresponding to the merchant identifier. For example, as shown in Table 1:
  • the merchant client, index platform, or other technical service provider that provides the generation of the payment code can generate the merchant's payment code based on the merchant identifier and the access address of the index platform. Then, the user can scan the payment code through the payment client to parse the merchant ID and the access address of the index platform, and then query the index platform for the acquiring information corresponding to the merchant ID through the access address, and then use the queried acquirer Information completes the payment. Description will be given below in conjunction with FIG. 7.
  • FIG. 7 is a schematic diagram of payment based on the payment code provided by an exemplary embodiment. As shown in Figure 7, the payment process may include steps 702-712.
  • Step 702 The payment client 53 scans the merchant's payment code to obtain the merchant's identification and the access address of the index platform.
  • step 704 the payment client 53 sends a query request (including the merchant identifier) to the index platform 50 through the access address.
  • Step 706 The indexing platform 50 searches the recorded mapping relationship for the acquiring information corresponding to the merchant identifier included in the query request.
  • step 708 the indexing platform 50 returns the queried acquiring information (ie, candidate acquiring information) to the payment client 53.
  • the payment platform when it configures the acquiring information, it may record its own server identification in the acquiring information.
  • the acquiring information includes the name of the payment platform, and the name is changed as the above-mentioned server identifier.
  • the acquiring information recorded with the target server identifier can be searched in the candidate acquiring information, and the found acquiring information can be used as the target acquiring information, and the target server is identified as paying The server identification of the payment platform corresponding to the client.
  • the index platform 20 may also identify target acquiring information matching the payment client from the candidate acquiring information, and return the identified target acquiring information to the payment client 53.
  • the payment client 53 may record its own client ID in the query request, so as to determine the server ID corresponding to the client ID.
  • the name of the payment platform A is A
  • the client identification of the payment App (installed in the user's payment client) of the payment platform is a. If the candidate acquiring information is found, there is an acquirer with A recorded Information, the acquiring information is used as the acquiring information supported by the payment client a; otherwise, it means that the payment client s does not support the current merchant, and the transaction is terminated.
  • step 710 the payment client 53 identifies the acquiring information supported by itself in the acquiring information returned by the indexing platform 20 and displays the acquiring information for the user to confirm.
  • step 712 the payment client 63 completes the payment according to the receipt information confirmed by the user and the order information input by the user.
  • the payment client 53 when the payment client 53 completes the payment to the merchant based on the target acquiring information, it may first display the merchant's account information for the user to confirm. After the user completes the merchant account information confirmation and order information interaction, Confirm the submission for payment.
  • the order information is payment information such as the transaction amount of the order the user currently generates with the merchant, and the user asks the merchant, or the merchant actively informs it.
  • the user can fill in the payment information to the payment client 63 and confirm the payment, then the payment client 63 submits a payment request instruction (including the merchant’s account information and the order information filled in by the user) to the payment platform to process the payment instruction by the payment platform , Complete the payment process, and return the payment result to the payment client and merchant client.
  • the collection code that supports interoperability contains a relatively small amount of information, which is beneficial to improve the efficiency of generating the collection code, and improve the accuracy and speed of parsing the collection code by the payment client, thereby improving the user experience .
  • the collection code corresponding to the new payment platform can also be merged without changing the collection code that supports interoperability, thereby reducing costs and increasing Business processing efficiency.
  • the indexing platform only needs to perform query operations for acquiring information, and does not need to perform complex operations involving data processing such as generating a collection code, aggregating multiple collection codes, and assisting payment clients in implementing payment processes, so as to avoid occupying more Processing resources; therefore, the smooth progress of the payment process can be ensured when the performance requirements of the indexing platform are not high.
  • the acquisition information configured by each payment platform is recorded through the index platform, without the need to merge the acquiring information configured by each payment platform into a collection code, and the original information format of the acquiring information configured by each payment platform can be retained. , Allowing each payment platform to still generate acquiring information in accordance with their respective information formats, so as to provide differentiated services to merchants.
  • this specification also provides an embodiment of a service processing device based on a graphic code.
  • the embodiments of the graphic code-based service processing apparatus in this specification can be applied to electronic equipment.
  • the device embodiments can be implemented by software, or can be implemented by hardware or a combination of software and hardware.
  • Taking software implementation as an example as a logical device, it is formed by reading the corresponding computer program instructions in the non-volatile memory into the memory through the processor of the electronic device where it is located.
  • FIG. 8 is a schematic structural diagram of a device provided by an exemplary embodiment.
  • the device includes a processor 802, an internal bus 804, a network interface 806, a memory 808, and a non-volatile memory 810.
  • the processor 802 reads the corresponding computer program from the non-volatile memory 810 to the memory 808 and then runs it to form a graphic code-based service processing device on a logical level.
  • one or more embodiments of this specification do not exclude other implementations, such as logic devices or a combination of software and hardware, and so on. That is to say, the execution subject of the following processing flow is not limited to each
  • the logic unit can also be a hardware or a logic device.
  • the graphic code-based service processing device is applied to the service requester client, and may include an identification resolution unit 91, a sending unit 92, a service processing unit 93, and an address resolution unit 94.
  • the identification analysis unit 91 parses the business graphic code of the business participant to obtain the identification information of the business participant.
  • the business participant is associated with at least one business response server, and each associated business response server is targeted at all.
  • the business participant is configured with corresponding business basic information, and the mapping relationship between the business basic information generated by each associated business response server for the business participant and the identification information is uploaded to the index platform for recording.
  • the sending unit 92 sends a query request for the service participant to the indexing platform based on the identification information, so that the indexing platform determines the candidate service basic information corresponding to the identification information according to the recorded mapping relationship.
  • the service processing unit 93 obtains the target service basic information that matches the service requester client in the candidate service basic information, and inputs the service of the service requester client based on the target service basic information and the service requester
  • the supplementary information implements business processing related to the business participant.
  • it further includes: an address resolution unit 94, which parses the service graphic code to obtain the access address of the index platform; and the sending unit 92 is specifically configured to: send the index platform to the index platform according to the access address.
  • a query request where the query request includes the identification information.
  • the service processing unit 93 is specifically configured to: receive the target service basic information returned by the indexing platform, where the target service basic information is identified by the indexing platform from the candidate service basic information; Or, receiving the candidate service basic information returned by the indexing platform, and identifying, in the candidate service basic information, the service basic information that matches the service requester client as the target service basic information.
  • any service basic information is recorded with the service end identifier of the service server configuring the any service basic information;
  • the target service basic information is identified in the following way: the candidate service basic information is searched and recorded with Business basic information identified by a target server, and use the found business basic information as the target business basic information, and the target server identifier is the server identifier of the business response server corresponding to the business requester client;
  • the service processing unit 93 is specifically configured to send a service request to a service response server corresponding to the service requester client to implement service processing based on the target service basic information and the service supplementary information.
  • the business participant includes a merchant
  • the business requester includes a payer
  • the business supplementary information includes order information of an order to be paid
  • the business response server associated with the merchant client includes a payment platform
  • the basic business information configured by each payment platform server side for the merchant includes acquiring information.
  • the embodiments of the graphic code-based service processing apparatus in this specification can be applied to electronic equipment.
  • the device embodiments can be implemented by software, or can be implemented by hardware or a combination of software and hardware.
  • Taking software implementation as an example as a logical device, it is formed by reading the corresponding computer program instructions in the non-volatile memory into the memory through the processor of the electronic device where it is located.
  • FIG. 10 is a schematic structural diagram of a device provided by an exemplary embodiment.
  • the device includes a processor 1002, an internal bus 1004, a network interface 1006, a memory 1008, and a non-volatile memory 1010, and of course, it may also include hardware required for other services.
  • the processor 1002 reads the corresponding computer program from the non-volatile memory 1010 to the memory 1008 and then runs it to form a service processing device based on graphic codes on a logical level.
  • one or more embodiments of this specification do not exclude other implementations, such as logic devices or a combination of software and hardware, and so on. That is to say, the execution subject of the following processing flow is not limited to each
  • the logic unit can also be a hardware or a logic device.
  • the graphic code-based service processing device is applied to an indexing platform, and may include the following units.
  • the first receiving unit 1101 receives a query request for the service participant sent by the service requester client based on the identification information of the service participant.
  • the service participant is associated with at least one service response server, and each associated The business response server is configured with corresponding business basic information for the business participant, and the mapping relationship between the business basic information generated by each associated business response server for the business participant and the identification information is uploaded to the index
  • the platform records, and the identification information is obtained by the service requester client analyzing the service graphic code of the service participant.
  • the determining unit 1102 determines the candidate service basic information corresponding to the identification information according to the recorded mapping relationship, so that the service requester client is based on the candidate service basic information that matches the service requester client.
  • the service basic information and the service requester input the service supplementary information of the service requester client to implement the service processing related to the service participant.
  • a second receiving unit 1103 which receives a first addition request sent by another service response server associated with the service participant, where the first addition request includes the identification information, and The other service responds to the first update service basic information configured by the service participant after establishing an association relationship with the service participant.
  • the first adding unit 1104 adds the corresponding relationship between the identification information and the first update service basic information to the mapping relationship.
  • a third receiving unit 1105 which receives a second addition request sent by the service participant client, where the second addition request includes the identification information, and other service response servers are in contact with the The second update service basic information configured for the service participant after the service participant establishes an association relationship, and the second update service basic information is analyzed by the service participant client to parse the update from the other service response server The graphic code is acquired, and the update graphic code is generated by the other service response server according to the second update service basic information.
  • the second adding unit 1106 adds the corresponding relationship between the identification information and the second update service basic information to the mapping relationship.
  • the business participant includes a merchant
  • the business requester includes a payer
  • the business supplementary information includes order information of an order to be paid
  • the business response server associated with the merchant client includes a payment platform
  • the basic business information configured by each payment platform server side for the merchant includes acquiring information.
  • the embodiments of the maintenance device for basic business information in this specification can be applied to electronic equipment.
  • the device embodiments can be implemented by software, or can be implemented by hardware or a combination of software and hardware.
  • Taking software implementation as an example as a logical device, it is formed by reading the corresponding computer program instructions in the non-volatile memory into the memory through the processor of the electronic device where it is located.
  • FIG. 12 is a schematic structural diagram of a device provided by an exemplary embodiment.
  • the device includes a processor 1202, an internal bus 1204, a network interface 1206, a memory 1208, and a non-volatile memory 1210.
  • the processor 1202 reads the corresponding computer program from the non-volatile memory 1210 to the memory 1208 and then runs it, forming a maintenance device for basic business information on a logical level.
  • one or more embodiments of this specification do not exclude other implementations, such as logic devices or a combination of software and hardware, and so on. That is to say, the execution subject of the following processing flow is not limited to each
  • the logic unit can also be a hardware or a logic device.
  • the apparatus for maintaining basic business information may include an acquiring unit 1301 and a sending unit 1302.
  • the acquiring unit 1301 when any business response server establishes an association relationship with a business participant, acquires the basic information of the business to be merged configured by the any business response server for the business participant.
  • the sending unit 1302 sends an adding request for the mapping relationship between the basic information of the business to be merged and the identification information of the business participant to the indexing platform, so that the indexing platform records the mapping relationship; wherein, the indexing platform The recorded mapping relationship between the identification information and the corresponding service basic information is used to determine the query request for the service participant sent by the service requester client based on the identification information by the indexing platform.
  • the basic information of the candidate service corresponding to the identification information, the basic information of the service used by the service requester client for the service processing related to the service participant, is the basic information of the candidate service and the client of the service requester
  • the service basic information that matches the end, the service supplementary information used by the service requester client to implement the service processing is input by the service requester, and the service requester client parses the service graphic code of the service participant Obtain the identification information.
  • the obtaining unit 1301 is specifically configured to: parse the service graphic code generated by any service response server based on the basic information of the service to be merged to obtain the basic information of the service to be merged.
  • the service participant includes a merchant
  • the service requester client includes a payment client
  • the service supplementary information includes order information of an order to be paid
  • the terminal includes a payment platform server
  • the basic business information configured by each payment platform server for the merchant includes acquiring information.
  • a typical implementation device is a computer.
  • the computer may be, for example, a personal computer, a laptop computer, a cell phone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or Any combination of these devices.
  • the embodiments of the present invention can be provided as a method, a system, or a computer program product. Therefore, the present invention may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Moreover, the present invention may adopt the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program codes.
  • computer-usable storage media including but not limited to disk storage, CD-ROM, optical storage, etc.
  • program modules include routines, programs, objects, components, data structures, etc. that perform specific tasks or implement specific abstract data types.
  • This specification can also be practiced in distributed computing environments where tasks are performed by remote processing devices connected through a communication network.
  • program modules can be located in local and remote computer storage media including storage devices.
  • These computer program instructions can also be stored in a computer-readable memory that can guide a computer or other programmable data processing equipment to work in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture including the instruction device.
  • the device implements the functions specified in one process or multiple processes in the flowchart and/or one block or multiple blocks in the block diagram.
  • These computer program instructions can also be loaded on a computer or other programmable data processing equipment, so that a series of operation steps are executed on the computer or other programmable equipment to produce computer-implemented processing, so as to execute on the computer or other programmable equipment.
  • the instructions provide steps for implementing the functions specified in one process or multiple processes in the flowchart and/or one block or multiple blocks in the block diagram.
  • the computer includes one or more processors (CPU), input/output interfaces, network interfaces, and memory.
  • the memory may include non-permanent memory in a computer-readable medium, random access memory (RAM) and/or non-volatile memory, such as read-only memory (ROM) or flash memory (flash RAM).
  • RAM random access memory
  • ROM read-only memory
  • flash RAM flash memory
  • Computer-readable media include permanent and non-permanent, removable and non-removable media, and information storage can be realized by any method or technology.
  • the information can be computer-readable instructions, data structures, program modules, or other data.
  • Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, CD-ROM, digital versatile disc (DVD) or other optical storage, Magnetic cassettes, disk storage, quantum memory, graphene-based storage media or other magnetic storage devices, or any other non-transmission media, can be used to store information that can be accessed by computing devices.
  • computer-readable media does not include transitory media, such as modulated data signals and carrier waves.
  • first, second, third, etc. may be used to describe various information in one or more embodiments of this specification, the information should not be limited to these terms. These terms are only used to distinguish the same type of information from each other.
  • first information may also be referred to as second information, and similarly, the second information may also be referred to as first information.
  • word “if” as used herein can be interpreted as "when” or “when” or "in response to determination”.

Landscapes

  • Engineering & Computer Science (AREA)
  • Business, Economics & Management (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Accounting & Taxation (AREA)
  • Strategic Management (AREA)
  • Physics & Mathematics (AREA)
  • General Business, Economics & Management (AREA)
  • General Physics & Mathematics (AREA)
  • Theoretical Computer Science (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Abstract

一种业务处理方法，包括：解析业务参与方的业务图形码，以获取业务参与方的标识信息，业务参与方与至少一个业务响应服务端相关联，各个相关联的业务响应服务端针对业务参与方配置有相应的业务基础信息，各个相关联的业务响应服务端分别为业务参与方产生的业务基础信息和标识信息的映射关系被上传至索引平台进行记录；基于标识信息向索引平台发送针对业务参与方的查询请求，以使得索引平台根据记录的映射关系确定与标识信息对应的候选业务基础信息；获取候选业务基础信息中与业务请求方客户端相匹配的目标业务基础信息，并基于目标业务基础信息和业务请求方输入业务请求方客户端的业务补充信息实施与业务参与方相关的业务处理。

Description

基于图形码的业务处理方法及装置、电子设备、存储介质 技术领域
本说明书一个或多个实施例涉及通讯技术领域，尤其涉及一种基于图形码的业务处理方法及装置、电子设备、存储介质。
背景技术
图形码可通过一定的编码规则，利用图形来表达文字数值信息，从而由图象输入设备或光电扫描设备自动识读以实现信息自动处理。图形码包括二维码、条形码等。以二维码为例，二维码是采用特定的几何图形按照一定规律在平面(二维方向上)上分布的黑白相间的图形。二维码在代码编制上巧妙地利用构成计算机内部逻辑基础的“0”、“1”比特流的概念，使用若干个与二进制相对应的几何形体来表示文字数值信息。比如，商户或个人可通过自身的收单信息生成收款码，以供其他用户通过扫描该收款码进行支付转账等。
发明内容
有鉴于此，本说明书一个或多个实施例提供一种基于图形码的业务处理方法及装置、电子设备、存储介质。
为实现上述目的，本说明书一个或多个实施例提供技术方案如下。
根据本说明书一个或多个实施例的第一方面，提出了一种基于图形码的业务处理方法，应用于业务请求方客户端，所述方法包括：解析业务参与方的业务图形码，以获取所述业务参与方的标识信息，所述业务参与方与至少一个业务响应服务端相关联，各个相关联的业务响应服务端针对所述业务参与方配置有相应的业务基础信息，各个相关联的业务响应服务端分别为所述业务参与方产生的业务基础信息和所述标识信息的映射关系被上传至索引平台进行记录；基于所述标识信息向所述索引平台发送针对所述业务参与方的查询请求，以使得所述索引平台根据记录的映射关系确定与所述标识信息对应的候选业务基础信息；获取所述候选业务基础信息中与所述业务请求方客户端相匹配的目标业务基础信息，并基于所述目标业务基础信息和业务请求方输入所述业务请求方客户端的业务补充信息实施与所述业务参与方相关的业务处理。
根据本说明书一个或多个实施例的第二方面，提出了一种基于图形码的业务处理方法，应用于索引平台，所述方法包括：接收业务请求方客户端基于业务参与方的标识信息发送的针对所述业务参与方的查询请求，所述业务参与方与至少一个业务响应服务端相关联，各个相关联的业务响应服务端针对所述业务参与方配置有相应的业务基础信息，各个相关联的业务响应服务端分别为所述业务参与方产生的业务基础信息和所述标识信息的映射关系被上传至索引平台进行记录，所述标识信息由所述业务请求方客户端解析所述业务参与方的业务图形码得到；根据记录的映射关系确定与所述标识信息对应的候选业务基础信息，以使得所述业务请求方客户端基于所述候选业务基础信息中与所述业务请求方客户端相匹配的业务基础信息和业务请求方输入所述业务请求方客户端的业务补充信息，实施与所述业务参与方相关的业务处理。
根据本说明书一个或多个实施例的第三方面，提出了一种业务基础信息的维护方法，包括：当任一业务响应服务端与业务参与方建立关联关系时，获取所述任一业务响应服务端针对所述业务参与方配置的待合并业务基础信息；向索引平台发送针对所述待合并业务基础信息和所述业务参与方的标识信息的映射关系的添加请求，以使得所述索引平台记录所述映射关系；其中，所述索引平台记录的所述标识信息与相应业务基础信息的映射关系用于在所述索引平台接收到业务请求方客户端基于所述标识信息发送的针对所述业务参与方的查询请求时，确定与所述标识信息对应的候选业务基础信息，所述业务请求方客户端实施的与所述业务参与方相关的业务处理所采用的业务基础信息，为所述候选业务基础信息中与所述业务请求方客户端相匹配的业务基础信息，所述业务请求方客户端实施所述业务处理所采用的业务补充信息由业务请求方输入，所述业务请求方客户端通过解析所述业务参与方的业务图形码得到所述标识信息。
根据本说明书一个或多个实施例的第四方面，提出了一种基于图形码的业务处理装置，应用于业务请求方客户端，所述装置包括：标识解析单元，解析业务参与方的业务图形码，以获取所述业务参与方的标识信息，所述业务参与方与至少一个业务响应服务端相关联，各个相关联的业务响应服务端针对所述业务参与方配置有相应的业务基础信息，各个相关联的业务响应服务端分别为所述业务参与方产生的业务基础信息和所述标识信息的映射关系被上传至索引平台进行记录；发送单元，基于所述标识信息向所述索引平台发送针对所述业务参与方的查询请求，以使得所述索引平台根据记录的映射关系确定与所述标识信息对应的候选业务基础信息；业务处理单元，获取所述候选业务基础信息中与所述业务请求方客户端相匹配的目标业务基础信息，并基于所述目标业务基础信息和业务请求方输入所述业务请求方客户端的业务补充信息实施与所述业务参与 方相关的业务处理。
根据本说明书一个或多个实施例的第五方面，提出了一种基于图形码的业务处理装置，应用于索引平台，所述装置包括：第一接收单元，接收业务请求方客户端基于业务参与方的标识信息发送的针对所述业务参与方的查询请求，所述业务参与方与至少一个业务响应服务端相关联，各个相关联的业务响应服务端针对所述业务参与方配置有相应的业务基础信息，各个相关联的业务响应服务端分别为所述业务参与方产生的业务基础信息和所述标识信息的映射关系被上传至索引平台进行记录，所述标识信息由所述业务请求方客户端解析所述业务参与方的业务图形码得到；确定单元，根据记录的映射关系确定与所述标识信息对应的候选业务基础信息，以使得所述业务请求方客户端基于所述候选业务基础信息中与所述业务请求方客户端相匹配的业务基础信息和业务请求方输入所述业务请求方客户端的业务补充信息，实施与所述业务参与方相关的业务处理。
根据本说明书一个或多个实施例的第六方面，提出了一种业务基础信息的维护装置，包括：获取单元，当任一业务响应服务端与业务参与方建立关联关系时，获取所述任一业务响应服务端针对所述业务参与方配置的待合并业务基础信息；发送单元，向索引平台发送针对所述待合并业务基础信息和所述业务参与方的标识信息的映射关系的添加请求，以使得所述索引平台记录所述映射关系；其中，所述索引平台记录的所述标识信息与相应业务基础信息的映射关系用于在所述索引平台接收到业务请求方客户端基于所述标识信息发送的针对所述业务参与方的查询请求时，确定与所述标识信息对应的候选业务基础信息，所述业务请求方客户端实施的与所述业务参与方相关的业务处理所采用的业务基础信息，为所述候选业务基础信息中与所述业务请求方客户端相匹配的业务基础信息，所述业务请求方客户端实施所述业务处理所采用的业务补充信息由业务请求方输入，所述业务请求方客户端通过解析所述业务参与方的业务图形码得到所述标识信息。
根据本说明书一个或多个实施例的第七方面，提出了一种电子设备，包括：处理器；用于存储处理器可执行指令的存储器；其中，所述处理器通过运行所述可执行指令以实现如上述第一方面中所述的基于图形码的业务处理方法。
根据本说明书一个或多个实施例的第八方面，提出了一种电子设备，包括：处理器；用于存储处理器可执行指令的存储器；其中，所述处理器通过运行所述可执行指令以实现如上述第二方面中所述的基于图形码的业务处理方法。
根据本说明书一个或多个实施例的第九方面，提出了一种电子设备，包括：处理 器；用于存储处理器可执行指令的存储器；其中，所述处理器通过运行所述可执行指令以实现如上述第三方面中所述的基于图形码的业务处理方法。
根据本说明书一个或多个实施例的第十方面，提出了一种计算机可读存储介质，其上存储有计算机指令，该指令被处理器执行时实现如上述第一方面中任一所述方法的步骤。
根据本说明书一个或多个实施例的第十一方面，提出了一种计算机可读存储介质，其上存储有计算机指令，该指令被处理器执行时实现如上述第二方面中任一所述方法的步骤。
根据本说明书一个或多个实施例的第十二方面，提出了一种计算机可读存储介质，其上存储有计算机指令，该指令被处理器执行时实现如上述第三方面中任一所述方法的步骤。
附图说明
图1是一示例性实施例提供的一种基于图形码的业务处理系统的架构示意图。
图2是一示例性实施例提供的一种基于图形码的业务处理方法的流程图。
图3是一示例性实施例提供的另一种基于图形码的业务处理方法的流程图。
图4是一示例性实施例提供的一种业务信息的维护方法的流程图。
图5是一示例性实施例提供的一种扫码支付的架构示意图。
图6是一示例性实施例提供的一种业务信息的维护方法的示意图。
图7是一示例性实施例提供的一种基于收款码进行支付的示意图。
图8是一示例性实施例提供的一种设备的结构示意图。
图9是一示例性实施例提供的一种基于图形码的业务处理装置的框图。
图10是一示例性实施例提供的另一种设备的结构示意图。
图11是一示例性实施例提供的另一种基于图形码的业务处理装置的框图。
图12是一示例性实施例提供的另一种设备的结构示意图。
图13是一示例性实施例提供的一种业务信息的维护装置的框图。
具体实施方式
这里将详细地对示例性实施例进行说明，其示例表示在附图中。下面的描述涉及附图时，除非另有表示，不同附图中的相同数字表示相同或相似的要素。以下示例性实施例中所描述的实施方式并不代表与本说明书一个或多个实施例相一致的所有实施方式。相反，它们仅是与如所附权利要求书中所详述的、本说明书一个或多个实施例的一些方面相一致的装置和方法的例子。
需要说明的是：在其他实施例中并不一定按照本说明书示出和描述的顺序来执行相应方法的步骤。在一些其他实施例中，其方法所包括的步骤可以比本说明书所描述的更多或更少。此外，本说明书中所描述的单个步骤，在其他实施例中可能被分解为多个步骤进行描述；而本说明书中所描述的多个步骤，在其他实施例中也可能被合并为单个步骤进行描述。
在业务处理过程中，业务响应服务端可与业务参与方建立关联关系以向业务参与方提供相应的业务支持，并在建立关联关系后由业务响应服务端向业务参与方配置相应的业务基础信息以供在处理业务时使用。其中，当业务请求方和业务参与方之间存在待处理业务时，由业务请求方客户端基于业务基础信息和与该待处理业务对应的业务补充信息与业务响应服务端进行交互来完成该待处理业务的处理过程。比如，业务补充信息可由业务请求方输入至业务请求方客户端。在相关技术中，当业务响应服务端配置的业务基础信息固定不变时，业务参与方(或业务响应服务端、委托的技术服务商等)可将业务基础信息以图形码的形式输出以向业务请求方提供完成业务所需的业务基础信息。比如，业务参与方可将该图形码打印张贴以由业务请求方解析；或者，通过业务参与方客户端向业务请求方展示该图形码。那么，业务请求方可通过业务请求方客户端解析该图形码获得业务基础信息，并在业务请求方客户端中输入待处理业务(与该业务参与方相关)的业务补充信息，进而基于获得的业务基础信息和输入的业务补充信息对该待处理业务实施处理。
在实际应用中，针对同一种业务，可能存在多个业务响应服务端可向业务参与方提供业务支持，即业务参与方可与多个业务响应服务端建立关联关系，而各个相关联的业务响应服务端针对该业务参与方客户端配置有相应的业务基础信息。同时，各个业务响应服务端分别有各自对应的业务请求方客户端，业务请求方客户端可通过与自身相匹配的业务响应服务端配置的业务基础信息来完成业务处理。在该情况下，可针对各个业务响应服务端配置的每一业务基础信息，分别生成相应的图形码。换言之，每个图形码 与业务响应服务端一一对应。那么，业务请求方在需要发起与该业务参与方相关的业务处理时，可根据实际需求选取图形码，并采用与选取的图形码对应的业务请求方客户端进行扫描以完成业务处理。
然而，在上述场景下，当业务参与方与多个业务响应服务端建立关联关系时，针对每个业务响应服务端配置的业务基础信息都需要生成一个相应的图形码，并且，当业务参与方与其他业务响应服务端又建立关联关系时，针对新关联的业务响应服务端配置的业务基础信息，仍需要再生成相应的图形码进行输出展示，导致成本较高，效率低下。
以商户收款码的应用场景为例，用户(业务请求方)使用安装有移动支付App的支付客户端(比如手机，即业务请求方客户端)扫描商户(业务参与方)展示的收款码(比如，为收款二维码)，该收款码中包含商户在相应支付平台(业务响应服务端)上的收单信息(或者收款码中包含获取该收单信息的访问路径，需访问后台服务器进一步获取到)，移动支付App通过解析收款码获取该商户的收单信息(业务基础信息)并展示在App界面上由用户进行确认，用户在确认商户的收单信息无误后即可输入订单信息(即业务补充信息，由商户提供；比如，交易金额)并提交支付申请，以由移动支付App与支付平台对接来完成后续的支付流程。
同一家商户可能与多个不同的支付平台合作(比如，与支付宝、微信等支付平台合作)，每个支付平台都会为该商户分配相应的收单信息(比如，向该商户分配的账户、标识号、支付平台名称、支付平台的访问地址等)。那么，当商户支持多个支付平台时，各个支付平台均会根据分配的收单信息生成相应的收款码以供商户向用户展示。比如，商户可张贴在商户店面以供用户扫码付款。如此，便出现了“一户多码”的情况，即一个商户的店面张贴有多个支付平台生成的商户收款码。由于移动支付App通常与支付平台相关联(即每个支付平台均开发有相应的移动支付App)，用户需选择自身安装的移动支付App支持的收款码进行扫描来完成支付。
由此可见，当商户与多个支付平台对接时，针对每个支付平台配置的收单信息都需要生成一个相应的收款码以由商户向用户展示。并且，当商户与一家新的支付平台(比如，还可与京东、银联等平台合作)合作时，针对新合作的支付平台配置的收单信息，仍需要再生成相应的收款码进行输出展示，那么商户需要再将该新获得的收款码张贴展示，导致成本较高，效率低下。
类似的，在社交场景中，同一用户(业务参与方)可在多个社交平台(业务响应服务端)注册得到账户信息(业务基础信息)，那么在添加好友(待处理业务)时，该 用户需要向其他用户(业务请求方)分别展示各个社交平台的二维码(根据账户信息生成)以供扫码添加好友。其中，其他用户通过手机扫描二维码得到该用户的账户信息后，输入自身的验证信息(即业务补充信息；比如自身的用户名、账户、备注等)，从而完成对该用户的添加好友申请。
本说明书旨在提供一种基于图形码的业务处理方案，可以在上述同一业务参与方客户端与多个业务响应服务端建立关联关系的情况下，将对应于各个业务相应服务端的图形码合并至一个支持互通性的图形码中，使得各个业务请求方均可以通过扫描该支持互通性的图形码来实施与该业务参与方客户端相关的业务处理。并且，还可在该业务参与方客户端后续与其他新的业务响应服务端建立关联关系时，也可合并对应于新的业务响应服务端的图形码，无需更换该支持互通性的图形码，从而降低成本，提高业务处理效率。
图1是一示例性实施例提供的一种基于图形码的业务处理系统的架构示意图。如图1所示，该系统可以包括服务器11、网络12、若干电子设备，比如手机13、手机14、PC15和PC16。
服务器11可以为包含一独立主机的物理服务器，或者服务器11可以为主机集群承载的虚拟服务器。在运行过程中，服务器11作为索引平台，用于记录各个业务参与方客户端的业务基础信息以供查询。
手机13-14和PC15-16只是业务参与方或业务请求方可以使用的两种类型的电子设备。实际上，显然还可以使用诸如下述类型的电子设备：平板设备、笔记本电脑、掌上电脑(PDAs，Personal Digital Assistants)、可穿戴设备(如智能眼镜、智能手表等)等，本说明书一个或多个实施例并不对此进行限制。在运行过程中，该电子设备可作为业务参与方客户端或业务请求方客户端。其中，业务响应服务端与业务参与方客户端建立关联关系，并向业务参与方客户端配置业务基础信息，以由业务请求方客户端(在与业务参与方之间存在待处理业务时)获取配置的业务基础信息并基于该业务基础信息和对应于待处理业务的业务补充信息完成业务处理。
而对于各个电子设备与服务器11之间进行交互的网络12，可以包括多种类型的有线或无线网络。在一实施例中，该网络12可以包括公共交换电话网络(Public Switched Telephone Network，PSTN)和因特网。同时，手机13-14和PC15-16等电子设备之间也可以通过该网络12进行通讯交互。
请参见图2，图2是一示例性实施例提供的一种基于图形码的业务处理方法的流程 图。如图2所示，该方法应用于业务请求方客户端，可以包括步骤202～206。
步骤202，解析业务参与方的业务图形码，以获取所述业务参与方的标识信息，所述业务参与方与至少一个业务响应服务端相关联，各个相关联的业务响应服务端针对所述业务参与方配置有相应的业务基础信息，各个相关联的业务响应服务端分别为所述业务参与方产生的业务基础信息和所述标识信息的映射关系被上传至索引平台进行记录。
在本实施例中，业务响应服务端向业务参与方提供某一业务的支持，在业务参与方与业务响应服务端建立关联关系后，由业务响应服务端向业务参与方配置业务基础信息，该业务基础信息为实施该业务时所需使用的信息。那么，当业务请求方与业务参与方之间存在实施该业务的需求时，业务请求方可通过与该业务响应服务端相匹配的业务请求方客户端，基于该业务响应服务端配置的业务基础信息实施业务处理。
例如，在上述商户收款码的应用场景中，业务请求方包括支付方(即业务请求方客户端包括支付客户端)，业务图形码包括收款图形码，业务参与方包括商户(即业务参与方客户端包括商户客户端)，与商户客户端相关联的业务响应服务端包括支付平台服务端，各个支付平台服务端针对商户客户端配置有相应的收单信息(即业务基础信息；比如，商户客户端的账户信息)。
商户通过向支付平台注册以与支付平台建立关联关系。支付平台可向商户分配相应的账户、标识号等收单信息作为支付业务的业务基础信息。那么，用户在与商户存在支付业务的需求(比如用户向商户购买商品，进而需要向商户支付相应的费用)时，用户可通过移动支付App(安装于用户的电子设备中)，基于上述收单信息与支付平台进行交互，从而完成向商户在支付平台上注册的账户中支付费用的业务。
在本实施例中，在基于图形码的业务处理系统中配置索引平台用于记录各个业务参与方的业务基础信息。其中，业务参与方可通过业务参与方客户端向索引平台发送注册请求以使得索引平台向业务参与方分配唯一的标识信息。那么，索引平台可记录业务参与方的标识信息与该业务参与方的业务基础信息之间的映射关系。
基于对索引平台的配置，业务参与方的业务图形码并非如相关技术中一样，用于记录业务基础信息，而是用于记录业务参与方的标识信息。而由于标识信息用于表征业务参与方的身份，具有固定且唯一性的特点。因此，业务参与方的业务图形码也随之无需更改，固定不变。那么，业务请求方客户端便可通过扫描业务图形码进而解析得到业务参与方的标识信息，进而通过该标识信息向索引平台查询业务参与方的业务基础信息，从而利用业务参与方的业务基础信息中自身支持的业务基础信息进行业务处理。
步骤204，基于所述标识信息向所述索引平台发送针对所述业务参与方的查询请求，以使得所述索引平台根据记录的映射关系确定与所述标识信息对应的候选业务基础信息。
在本实施例中，在一种情况下，索引平台的访问地址可记录于业务图形码中；在另一种情况下，还可在与各个业务响应服务端对应的业务请求客户端中均配置索引平台的访问地址，比如可写入业务请求客户端的安装包中。
以在业务图形码中记录访问地址为例，可由业务参与方客户端、索引平台或者其他提供生成业务图形码的技术服务提供商，基于业务参与方的标识信息和索引平台的访问地址生成该业务参与方的业务图形码。那么，业务请求方客户端可解析业务图形码以获取索引平台的访问地址，进而根据该访问地址向索引平台发送查询请求，该查询请求中包含业务参与方的标识信息。
步骤206，获取所述候选业务基础信息中与所述业务请求方客户端相匹配的目标业务基础信息，并基于所述目标业务基础信息和业务请求方输入所述业务请求方客户端的业务补充信息实施与所述业务参与方相关的业务处理。
在本实施例中，各个业务参与方的业务基础信息和相应标识信息的映射关系被上传至索引平台进行记录。因此，索引平台可根据记录的映射关系查找出与查询请求中包含的标识信息对应的业务基础信息作为候选业务基础信息。
在一种情况下，可由索引平台从候选业务基础信息中识别得到与业务请求方客户端相匹配的目标业务基础信息，并将识别得到的目标业务基础信息返回至查询请求的发送方(即业务请求方客户端)，那么业务请求方客户端可接收索引平台返回的目标业务基础信息以实现对目标业务基础信息的获取。
在另一种情况下，索引平台在查询得到候选业务基础信息后，可直接将候选业务基础信息返回至业务请求方客户端。那么，业务请求方客户端可接收索引平台返回的候选业务基础信息，并在候选业务基础信息中识别与自身相匹配的业务基础信息以作为目标业务基础信息。
而针对识别目标业务基础信息的方式，业务响应服务端在配置业务基础信息时，可在业务基础信息中记录自身的服务端标识。换言之，任一业务基础信息中记录有配置该任一业务基础信息的业务服务端的服务端标识。基于上述对业务基础信息的设定，可在候选业务基础信息中查找记录有目标服务端标识的业务基础信息，并将查找到的业务 基础信息作为目标业务基础信息，目标服务端标识为与业务请求方客户端对应的业务响应服务端的服务端标识。其中，针对由索引平台识别目标业务基础信息的情况，可在查询请求中记录发送方(业务请求方客户端)的客户端标识，以用于确定与该客户端标识对应的服务端标识。
进一步的，在确定出目标服务端标识后，在实施业务处理时，可基于目标业务基础信息和业务请求方输入的业务补充信息向与业务请求方客户端对应的业务响应服务端发送业务请求以实施业务处理。该业务响应服务端为与目标服务端标识对应的业务响应服务端。
在本实施例中，以商户收款码的应用场景为例，业务参与方包括商户，业务请求方包括支付方，业务补充信息包括待支付订单的订单信息，与商户客户端相关联的业务响应服务端包括支付平台服务端，各个支付平台服务端针对商户配置的业务基础信息包括收单信息。
相应的，请参见图3，图3是一示例性实施例提供的一种基于图形码的业务处理方法的流程图。如图3所示，该方法应用于索引平台，可以包括步骤302～304。
步骤302，接收业务请求方客户端基于业务参与方的标识信息发送的针对所述业务参与方的查询请求，所述业务参与方与至少一个业务响应服务端相关联，各个相关联的业务响应服务端针对所述业务参与方配置有相应的业务基础信息，各个相关联的业务响应服务端分别为所述业务参与方产生的业务基础信息和所述标识信息的映射关系被上传至索引平台进行记录，所述标识信息由所述业务请求方客户端解析所述业务参与方的业务图形码得到。
步骤304，根据记录的映射关系确定与所述标识信息对应的候选业务基础信息，以使得所述业务请求方客户端基于所述候选业务基础信息中与所述业务请求方客户端相匹配的业务基础信息和业务请求方输入所述业务请求方客户端的业务补充信息，实施与所述业务参与方相关的业务处理。
在本实施例中，当业务参与方与除当前建立关联关系以外的其他业务响应服务端建立关联关系时，可由该其他响应服务端将配置的业务基础信息添加至索引平台进行记录；也可由该其他响应服务端将配置的业务基础信息生成相应的业务图形码，再将该业务图形码返回至业务参与方，以由业务参与方与索引平台进行交互，将该业务图形码记录的业务基础信息添加至索引平台进行记录。
针对其他响应服务端添加业务基础信息的情况，索引平台接收与所述业务参与方客户端相关联的其他业务响应服务端发送的第一添加请求(第一添加请求中包含所述业务参与方客户端的标识信息，和所述其他业务响应服务端在与所述业务参与方建立关联关系后针对所述业务参与方配置的第一更新业务基础信息)，并在映射关系中添加所述标识信息与所述第一更新业务基础信息的对应关系。
针对业务参与方添加业务基础信息的情况，索引平台接收业务参与方客户端发送的第二添加请求，第二添加请求中包含所述标识信息，和其他业务响应服务端在与所述业务参与方建立关联关系后针对所述业务参与方配置的第二更新业务基础信息，所述第二更新业务基础信息由业务参与方客户端解析来自于所述其他业务响应服务端的更新图形码获取，所述更新图形码由所述其他业务响应服务端根据所述第二更新业务基础信息生成。在接收到第二添加请求后，索引平台在记录的映射关系中添加所述标识信息与所述第二更新业务基础信息的对应关系。
需要说明的是，业务处理方法的详细过程可参考上述图2所示实施例，在此不再赘述。
相应的，请参见图4，图4是一示例性实施例提供的一种业务信息的维护方法的流程图。如图4所示，该方法应用于业务参与方客户端或业务响应服务端，可以包括步骤402～404。
步骤402，当任一业务响应服务端与业务参与方建立关联关系时，获取所述任一业务响应服务端针对所述业务参与方配置的待合并业务基础信息。
在本实施例中，当任一业务响应服务端与业务参与方建立关联关系时，可由该任一业务响应服务端与索引平台进行交互，进而将待合并业务基础信息添加至索引平台中。或者，由业务参与方客户端与索引平台进行交互，进而将待合并业务基础信息添加至索引平台中。
针对业务参与方添加业务基础信息的情况，该任一业务响应服务端在与业务参与方建立关联关系后，生成对应于该业务参与方的待合并业务基础信息，并基于待合并业务基础信息生成相应的业务图形码，再将该业务图形码发送至业务参与方客户端。那么，该业务参与方客户端在接收到该业务图形码(即该任一业务响应服务端基于待合并业务基础信息生成的业务图形码)后，可解析以得到待合并业务基础信息。
步骤404，向索引平台发送针对所述待合并业务基础信息和所述业务参与方的标识 信息的映射关系的添加请求，以使得所述索引平台记录所述映射关系。
在本实施例中，所述索引平台记录的所述标识信息与相应业务基础信息的映射关系用于在所述索引平台接收到业务请求方客户端基于所述标识信息发送的针对所述业务参与方的查询请求时，确定与所述标识信息对应的候选业务基础信息，所述业务请求方客户端实施的与所述业务参与方相关的业务处理所采用的业务基础信息，为所述候选业务基础信息中与所述业务请求方客户端相匹配的业务基础信息，所述业务请求方客户端实施所述业务处理所采用的业务补充信息由业务请求方输入，所述业务请求方客户端通过解析所述业务参与方的业务图形码得到所述标识信息。需要说明的是，上述业务处理方法的详细过程可参考上述图2所示实施例，在此不再赘述。
由以上实施例可见，通过引入索引平台用于记录各个业务参与方的业务基础信息，可以在同一业务参与方与多个业务响应服务端建立关联关系的情况下，将对应于各个业务响应服务端的业务图形码合并至一个支持互通性的业务图形码(记录索引平台向业务参与方分配的标识信息)中，使得各个业务请求方均可以通过扫描该支持互通性的业务图形码来实施与该业务参与方相关的业务处理。其中，该支持互通性的业务图形码中包含索引平台向业务参与方分配的标识信息即可，而无需包含各个业务响应服务端向业务参与方分配的业务基础信息。一方面，该支持互通性的业务图形码包含的信息量相对较少，有利于提高生成该业务图形码的效率，以及提高业务请求方客户端解析该业务图形码的准确率和速度，进而提升用户体验。另一方面，可在该业务参与方后续与其他新的业务响应服务端建立关联关系时，也可合并对应于新的业务响应服务端的业务图形码，无需更换该支持互通性的业务图形码，从而降低成本，提高业务处理效率。
同时，索引平台仅需执行针对业务基础信息的查询操作，无需执行生成业务图形码、聚合多个业务图形码、协助业务请求方客户端实施业务处理等涉及数据处理的复杂操作，从而避免占用较多的处理资源；因此，可在对索引平台的性能要求不高的情况下，保证业务的顺利进行。
另外，通过索引平台来记录各个业务响应服务端配置的业务基础信息，而无需将各个业务响应服务端配置的业务基础信息合并至一个图形码中，可以保留各个业务响应服务端配置的业务基础信息的原有信息格式，允许各个业务响应服务端仍然可以按照各自的信息格式来生成业务基础信息，从而向业务参与方提供差异化的服务。
为了便于理解，下面以商户收款码的应用场景为例对本说明书的技术方案进行详细说明，社交场景的处理过程与此类似。
请参见图5，图5是一示例性实施例提供的一种扫码支付的架构示意图。如图5所示，该架构中包括索引平台50、由商户使用的商户客户端51、支付平台的支付平台服务端52和由用户使用的支付客户端53。其中，商户客户端51、支付平台服务端52和支付客户端53均可以通过商户的商户标识来访问索引平台50中记录的该商户的收单信息。
请参见图6，图6是一示例性实施例提供的一种业务信息的维护方法的示意图。如图6所示，各方之间的交互过程可以包括步骤602～610。
步骤602，商户客户端51在索引平台50注册得到商户标识。
步骤604，商户客户端51向支付平台服务端52获取待合并的商户二维码。
举例而言，商户可通过商户客户端51向支付平台服务端52发起注册，从而得到在支付平台上的账户信息。同时，支付平台服务端52可基于该账户信息、支付平台名称、支付平台的访问地址等收单信息生成商户二维码。
步骤606，商户客户端51解析待合并的商户二维码得到待合并的收单信息。
承接于上述举例，商户客户端51在获取该商户二维码后，可扫描解析该商户二维码得到上述收单信息，也即待合并的收单信息。
步骤608，商户客户端51向索引平台50发送待合并的收单信息和自身的商户标识。
举例而言，商户客户端51创建针对收单信息的添加请求，该添加请求中包含合并的收单信息和自身的商户标识。
步骤610，索引平台50记录收单信息和商户标识的对应关系。
承接于上述举例，索引平台在接收到添加请求后，读取其中包含的收单信息和商户标识，并建立该收单信息和商户标识的映射关系。具体而言，索引平台在向商户分配商户标识时，可针对该商户标识分配一存储空间，用于存储与该商户标识对应的收单信息。例如，如表1所示：
表1
Figure PCTCN2020126970-appb-000001
在本实施例中，由于商户标识信息用于表征商户在索引平台的身份，具有固定且唯一性的特点。因此，可由商户客户端、索引平台或者其他提供生成收款码的技术服务提供商基于商户标识和索引平台的访问地址生成商户的收款码。那么，用户便可通过支付客户端扫描收款码进而解析得到商户标识和索引平台的访问地址，从而通过访问地址向索引平台查询与该商户标识对应的收单信息，进而利用查询到的收单信息完成支付。下面结合图7进行说明。
请参见图7，图7是一示例性实施例提供的一种基于收款码进行支付的示意图。如图7所示，该支付过程可以包括步骤702～712。
步骤702，支付客户端53扫描商户的收款码得到商户标识和索引平台的访问地址。
步骤704，支付客户端53通过访问地址向索引平台50发送查询请求(包含商户标识)。
步骤706，索引平台50在记录的映射关系中查询与查询请求中包含的商户标识对应的收单信息。
步骤708，索引平台50向支付客户端53返回查询到的收单信息(即候选收单信息)。
在本实施例中，支付平台在配置收单信息时，可在收单信息中记录自身的服务端标识。例如，收单信息中包含支付平台的名称，改名称作为上述服务端标识。基于上述对收单信息的设定，可在候选收单信息中查找记录有目标服务端标识的收单信息，并将查找到的收单信息作为目标收单信息，目标服务端标识为与支付客户端对应的支付平台的服务端标识。
在本实施例中，还可由索引平台20从候选收单信息中识别得到与支付客户端相匹配的目标收单信息，并将识别得到的目标收单信息返回至支付客户端53。在该情况下，支付客户端53可在查询请求中记录自身的客户端标识，以用于确定与该客户端标识对应的服务端标识。
举例而言，支付平台A的名称为A，该支付平台的支付App(安装于用户的支付客户端中)的客户端标识为a，若查找到候选收单信息中存在记录有A的收单信息，则将该收单信息作为支付客户端a支持的收单信息；否则，说明支付客户端s不支持当前商户，交易终止。
步骤710，支付客户端53识别索引平台20返回的收单信息中自身所支持的收单信 息并展示该收单信息以供用户确认。
步骤712，支付客户端63根据用户确认后的收单信息和用户输入的订单信息以完成支付。
在本实施例中，支付客户端53在基于目标收单信息完成对商户的支付时，可先展示商户的账户信息以供用户确认，在用户完成商户账户信息的确认以及订单信息的交互后，确认提交进行支付。例如，订单信息为用户当前与商户产生的订单的交易金额等支付信息，由用户向商户询问，或者商户主动告知等。用户可将支付信息填写至支付客户端63并确认支付，那么支付客户端63向支付平台提交支付请求指令(包含商户的账户信息和用户填写的订单信息)，以由支付平台对支付指令进行处理，完成支付过程，并向支付客户端和商户客户端返回支付结果。
由以上实施例可见，通过引入索引平台用于记录各个商户客户端的收单信息，可以在同一商户客户端与多个支付平台建立关联关系的情况下，将对应于各个支付平台的收款码合并至一个支持互通性的收款码(记录索引平台向商户客户端分配的商户标识)中，使得各个用户均可以通过扫描该支持互通性的收款码来实施与该商户客户端相关的支付业务。其中，该支持互通性的收款码中包含索引平台向商户分配的标识信息即可，而无需包含各个业务响应服务端向商户分配的业务基础信息。一方面，该支持互通性的收款码包含的信息量相对较少，有利于提高生成该收款码的效率，以及提高支付客户端解析该收款码的准确率和速度，进而提升用户体验。另一方面，可在该商户后续与其他新的支付平台建立关联关系时，也可合并对应于新的支付平台的收款码，无需更换该支持互通性的收款码，从而降低成本，提高业务处理效率。
同时，索引平台仅需执行针对收单信息的查询操作，无需执行生成收款码、聚合多个收款码、协助支付客户端实施支付流程等涉及数据处理的复杂操作，从而避免占用较多的处理资源；因此，可在对索引平台的性能要求不高的情况下，保证支付过程的顺利进行。
另外，通过索引平台来记录各个支付平台配置的收单信息，而无需将各个支付平台配置的收单信息合并至一个收款码中，可以保留各个支付平台配置的收单信息的原有信息格式，允许各个支付平台仍然可以按照各自的信息格式来生成收单信息，从而向商户提供差异化的服务。
与上述方法实施例相对应，本说明书还提供了一种基于图形码的业务处理装置的实施例。
本说明书的基于图形码的业务处理装置的实施例可以应用在电子设备上。装置实施例可以通过软件实现，也可以通过硬件或者软硬件结合的方式实现。以软件实现为例，作为一个逻辑意义上的装置，是通过其所在电子设备的处理器将非易失性存储器中对应的计算机程序指令读取到内存中运行形成的。
从硬件层面而言，请参考图8，图8是一示例性实施例提供的一种设备的示意结构图。如图8所示，在硬件层面，该设备包括处理器802、内部总线804、网络接口806、内存808以及非易失性存储器810，当然还可能包括其他业务所需要的硬件。处理器802从非易失性存储器810中读取对应的计算机程序到内存808中然后运行，在逻辑层面上形成基于图形码的业务处理装置。当然，除了软件实现方式之外，本说明书一个或多个实施例并不排除其他实现方式，比如逻辑器件抑或软硬件结合的方式等等，也就是说以下处理流程的执行主体并不限定于各个逻辑单元，也可以是硬件或逻辑器件。
请参考图9，在软件实施方式中，该基于图形码的业务处理装置应用于业务请求方客户端，可以包括标识解析单元91,、发送单元92、业务处理单元93和地址解析单元94。
标识解析单元91，解析业务参与方的业务图形码，以获取所述业务参与方的标识信息，所述业务参与方与至少一个业务响应服务端相关联，各个相关联的业务响应服务端针对所述业务参与方配置有相应的业务基础信息，各个相关联的业务响应服务端分别为所述业务参与方产生的业务基础信息和所述标识信息的映射关系被上传至索引平台进行记录。
发送单元92，基于所述标识信息向所述索引平台发送针对所述业务参与方的查询请求，以使得所述索引平台根据记录的映射关系确定与所述标识信息对应的候选业务基础信息。
业务处理单元93，获取所述候选业务基础信息中与所述业务请求方客户端相匹配的目标业务基础信息，并基于所述目标业务基础信息和业务请求方输入所述业务请求方客户端的业务补充信息实施与所述业务参与方相关的业务处理。
可选的，还包括：地址解析单元94，解析所述业务图形码以获取所述索引平台的访问地址；所述发送单元92具体用于：根据所述访问地址向所述索引平台发送所述查询请求，所述查询请求中包含所述标识信息。
可选的，所述业务处理单元93具体用于：接收所述索引平台返回的所述目标业务基础信息，所述目标业务基础信息由所述索引平台从所述候选业务基础信息中识别得到；或者，接收所述索引平台返回的所述候选业务基础信息，并在所述候选业务基础信息中 识别与所述业务请求方客户端相匹配的业务基础信息以作为所述目标业务基础信息。
可选的，任一业务基础信息记录有配置所述任一业务基础信息的业务服务端的服务端标识；通过以下方式识别出所述目标业务基础信息：在所述候选业务基础信息中查找记录有目标服务端标识的业务基础信息，并将查找到的业务基础信息作为所述目标业务基础信息，所述目标服务端标识为与所述业务请求方客户端对应的业务响应服务端的服务端标识；所述业务处理单元93具体用于：基于所述目标业务基础信息和所述业务补充信息向与所述业务请求方客户端对应的业务响应服务端发送业务请求以实施业务处理。
可选的，所述业务参与方包括商户，所述业务请求方包括支付方，所述业务补充信息包括待支付订单的订单信息，与所述商户客户端相关联的业务响应服务端包括支付平台服务端，各个支付平台服务端针对所述商户配置的业务基础信息包括收单信息。
本说明书的基于图形码的业务处理装置的实施例可以应用在电子设备上。装置实施例可以通过软件实现，也可以通过硬件或者软硬件结合的方式实现。以软件实现为例，作为一个逻辑意义上的装置，是通过其所在电子设备的处理器将非易失性存储器中对应的计算机程序指令读取到内存中运行形成的。
从硬件层面而言，请参考图10，图10是一示例性实施例提供的一种设备的示意结构图。如图10所示，在硬件层面，该设备包括处理器1002、内部总线1004、网络接口1006、内存1008以及非易失性存储器1010，当然还可能包括其他业务所需要的硬件。处理器1002从非易失性存储器1010中读取对应的计算机程序到内存1008中然后运行，在逻辑层面上形成基于图形码的业务处理装置。当然，除了软件实现方式之外，本说明书一个或多个实施例并不排除其他实现方式，比如逻辑器件抑或软硬件结合的方式等等，也就是说以下处理流程的执行主体并不限定于各个逻辑单元，也可以是硬件或逻辑器件。
请参考图11，在软件实施方式中，该基于图形码的业务处理装置应用于索引平台，可以包括以下单元。
第一接收单元1101，接收业务请求方客户端基于业务参与方的标识信息发送的针对所述业务参与方的查询请求，所述业务参与方与至少一个业务响应服务端相关联，各个相关联的业务响应服务端针对所述业务参与方配置有相应的业务基础信息，各个相关联的业务响应服务端分别为所述业务参与方产生的业务基础信息和所述标识信息的映射关系被上传至索引平台进行记录，所述标识信息由所述业务请求方客户端解析所述业务参与方的业务图形码得到。
确定单元1102，根据记录的映射关系确定与所述标识信息对应的候选业务基础信 息，以使得所述业务请求方客户端基于所述候选业务基础信息中与所述业务请求方客户端相匹配的业务基础信息和业务请求方输入所述业务请求方客户端的业务补充信息，实施与所述业务参与方相关的业务处理。
可选的，还包括：第二接收单元1103，接收与所述业务参与方相关联的其他业务响应服务端发送的第一添加请求，所述第一添加请求中包含所述标识信息，和所述其他业务响应服务端在与所述业务参与方建立关联关系后针对所述业务参与方配置的第一更新业务基础信息。
第一添加单元1104，在所述映射关系中添加所述标识信息与所述第一更新业务基础信息的对应关系。
可选的，还包括：第三接收单元1105，接收所述业务参与方客户端发送的第二添加请求，所述第二添加请求中包含所述标识信息，和其他业务响应服务端在与所述业务参与方建立关联关系后针对所述业务参与方配置的第二更新业务基础信息，所述第二更新业务基础信息由所述业务参与方客户端解析来自于所述其他业务响应服务端的更新图形码获取，所述更新图形码由所述其他业务响应服务端根据所述第二更新业务基础信息生成。
第二添加单元1106，在所述映射关系中添加所述标识信息与所述第二更新业务基础信息的对应关系。
可选的，所述业务参与方包括商户，所述业务请求方包括支付方，所述业务补充信息包括待支付订单的订单信息，与所述商户客户端相关联的业务响应服务端包括支付平台服务端，各个支付平台服务端针对所述商户配置的业务基础信息包括收单信息。
本说明书的业务基础信息的维护装置的实施例可以应用在电子设备上。装置实施例可以通过软件实现，也可以通过硬件或者软硬件结合的方式实现。以软件实现为例，作为一个逻辑意义上的装置，是通过其所在电子设备的处理器将非易失性存储器中对应的计算机程序指令读取到内存中运行形成的。
从硬件层面而言，请参考图12，图12是一示例性实施例提供的一种设备的示意结构图。如图12所示，在硬件层面，该设备包括处理器1202、内部总线1204、网络接口1206、内存1208以及非易失性存储器1210，当然还可能包括其他业务所需要的硬件。处理器1202从非易失性存储器1210中读取对应的计算机程序到内存1208中然后运行，在逻辑层面上形成业务基础信息的维护装置。当然，除了软件实现方式之外，本说明书一个或多个实施例并不排除其他实现方式，比如逻辑器件抑或软硬件结合的方式等等，也就是说以下处理流程的执行主体并不限定于各个逻辑单元，也可以是硬件或逻辑器件。
请参考图13，在软件实施方式中，该业务基础信息的维护装置可以包括获取单元1301和发送单元1302。
获取单元1301，当任一业务响应服务端与业务参与方建立关联关系时，获取所述任一业务响应服务端针对所述业务参与方配置的待合并业务基础信息。
发送单元1302，向索引平台发送针对所述待合并业务基础信息和所述业务参与方的标识信息的映射关系的添加请求，以使得所述索引平台记录所述映射关系；其中，所述索引平台记录的所述标识信息与相应业务基础信息的映射关系用于在所述索引平台接收到业务请求方客户端基于所述标识信息发送的针对所述业务参与方的查询请求时，确定与所述标识信息对应的候选业务基础信息，所述业务请求方客户端实施的与所述业务参与方相关的业务处理所采用的业务基础信息，为所述候选业务基础信息中与所述业务请求方客户端相匹配的业务基础信息，所述业务请求方客户端实施所述业务处理所采用的业务补充信息由业务请求方输入，所述业务请求方客户端通过解析所述业务参与方的业务图形码得到所述标识信息。
可选的，所述获取单元1301具体用于：解析所述任一业务响应服务端基于所述待合并业务基础信息生成的业务图形码以得到所述待合并业务基础信息。
可选的，所述业务参与方包括商户，所述业务请求方客户端包括支付客户端方，所述业务补充信息包括待支付订单的订单信息，与所述商户客户端相关联的业务响应服务端包括支付平台服务端，各个支付平台服务端针对所述商户配置的业务信息业务基础信息包括收单信息。
上述实施例阐明的系统、装置、模块或单元，具体可以由计算机芯片或实体实现，或者由具有某种功能的产品来实现。一种典型的实现设备为计算机。具体的，计算机例如可以为个人计算机、膝上型计算机、蜂窝电话、相机电话、智能电话、个人数字助理、媒体播放器、导航设备、电子邮件设备、游戏控制台、平板计算机、可穿戴设备或者这些设备中的任何设备的组合。
为了描述的方便，描述以上装置时以功能分为各种单元分别描述。当然，在实施本说明书时可以把各单元的功能在同一个或多个软件和/或硬件中实现。
本领域内的技术人员应明白，本发明的实施例可提供为方法、系统、或计算机程序产品。因此，本发明可采用完全硬件实施例、完全软件实施例、或结合软件和硬件方面的实施例的形式。而且，本发明可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器、CD-ROM、光学存储器等)上实施的计算机程序产品的形式。
本发明是参照根据本发明实施例的方法、设备(系统)、和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器，使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
本说明书可以在由计算机执行的计算机可执行指令的一般上下文中描述，例如程序模块。一般地，程序模块包括执行特定任务或实现特定抽象数据类型的例程、程序、对象、组件、数据结构等等。也可以在分布式计算环境中实践本说明书，在这些分布式计算环境中，由通过通信网络而被连接的远程处理设备来执行任务。在分布式计算环境中，程序模块可以位于包括存储设备在内的本地和远程计算机存储介质中。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方式工作的计算机可读存储器中，使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品，该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上，使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理，从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。在一个典型的配置中，计算机包括一个或多个处理器(CPU)、输入/输出接口、网络接口和内存。
内存可能包括计算机可读介质中的非永久性存储器，随机存取存储器(RAM)和/或非易失性内存等形式，如只读存储器(ROM)或闪存(flash RAM)。内存是计算机可读介质的示例。
计算机可读介质包括永久性和非永久性、可移动和非可移动媒体可以由任何方法或技术来实现信息存储。信息可以是计算机可读指令、数据结构、程序的模块或其他数据。计算机的存储介质的例子包括，但不限于相变内存(PRAM)、静态随机存取存储器(SRAM)、动态随机存取存储器(DRAM)、其他类型的随机存取存储器(RAM)、只读存储器(ROM)、电可擦除可编程只读存储器(EEPROM)、快闪记忆体或其他内存技术、只读光盘只读存储器(CD-ROM)、数字多功能光盘(DVD)或其他光学存储、磁盒式磁带、磁盘存储、量子存储器、基于石墨烯的存储介质或其他磁性存储设备或任何其他非传输介质，可用于存储可以被计算设备访问的信息。按照本文中的界定， 计算机可读介质不包括暂存电脑可读媒体(transitory media)，如调制的数据信号和载波。
还需要说明的是，术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含，从而使得包括一系列要素的过程、方法、商品或者设备不仅包括那些要素，而且还包括没有明确列出的其他要素，或者是还包括为这种过程、方法、商品或者设备所固有的要素。在没有更多限制的情况下，由语句“包括一个……”限定的要素，并不排除在包括所述要素的过程、方法、商品或者设备中还存在另外的相同要素。
上述对本说明书特定实施例进行了描述。其它实施例在所附权利要求书的范围内。在一些情况下，在权利要求书中记载的动作或步骤可以按照不同于实施例中的顺序来执行并且仍然可以实现期望的结果。另外，在附图中描绘的过程不一定要求示出的特定顺序或者连续顺序才能实现期望的结果。在某些实施方式中，多任务处理和并行处理也是可以的或者可能是有利的。
在本说明书一个或多个实施例使用的术语是仅仅出于描述特定实施例的目的，而非旨在限制本说明书一个或多个实施例。在本说明书一个或多个实施例和所附权利要求书中所使用的单数形式的“一种”、“所述”和“该”也旨在包括多数形式，除非上下文清楚地表示其他含义。还应当理解，本文中使用的术语“和/或”是指并包含一个或多个相关联的列出项目的任何或所有可能组合。
应当理解，尽管在本说明书一个或多个实施例可能采用术语第一、第二、第三等来描述各种信息，但这些信息不应限于这些术语。这些术语仅用来将同一类型的信息彼此区分开。例如，在不脱离本说明书一个或多个实施例范围的情况下，第一信息也可以被称为第二信息，类似地，第二信息也可以被称为第一信息。取决于语境，如在此所使用的词语“如果”可以被解释成为“在……时”或“当……时”或“响应于确定”。
以上所述仅为本说明书一个或多个实施例的较佳实施例而已，并不用以限制本说明书一个或多个实施例，凡在本说明书一个或多个实施例的精神和原则之内，所做的任何修改、等同替换、改进等，均应包含在本说明书一个或多个实施例保护的范围之内。

Claims (30)

  1. 一种基于图形码的业务处理方法，应用于业务请求方客户端，所述方法包括：
    解析业务参与方的业务图形码，以获取所述业务参与方的标识信息，所述业务参与方与至少一个业务响应服务端相关联，各个相关联的业务响应服务端针对所述业务参与方配置有相应的业务基础信息，各个相关联的业务响应服务端分别为所述业务参与方产生的业务基础信息和所述标识信息的映射关系被上传至索引平台进行记录；
    基于所述标识信息向所述索引平台发送针对所述业务参与方的查询请求，以使得所述索引平台根据记录的映射关系确定与所述标识信息对应的候选业务基础信息；
    获取所述候选业务基础信息中与所述业务请求方客户端相匹配的目标业务基础信息，并基于所述目标业务基础信息和业务请求方输入所述业务请求方客户端的业务补充信息实施与所述业务参与方相关的业务处理。
  2. 根据权利要求1所述的方法，
    还包括：解析所述业务图形码以获取所述索引平台的访问地址；
    所述基于所述标识信息向所述索引平台发送针对与所述业务参与方的查询请求，包括：根据所述访问地址向所述索引平台发送所述查询请求，所述查询请求中包含所述标识信息。
  3. 根据权利要求1所述的方法，所述获取所述候选业务基础信息中与所述业务请求方客户端相匹配的目标业务基础信息，包括：
    接收所述索引平台返回的所述目标业务基础信息，所述目标业务基础信息由所述索引平台从所述候选业务基础信息中识别得到；
    或者，接收所述索引平台返回的所述候选业务基础信息，并在所述候选业务基础信息中识别与所述业务请求方客户端相匹配的业务基础信息以作为所述目标业务基础信息。
  4. 根据权利要求1所述的方法，任一业务基础信息记录有配置所述任一业务基础信息的业务服务端的服务端标识；
    通过以下方式识别出所述目标业务基础信息：在所述候选业务基础信息中查找记录有目标服务端标识的业务基础信息，并将查找到的业务基础信息作为所述目标业务基础信息，所述目标服务端标识为与所述业务请求方客户端对应的业务响应服务端的服务端标识；
    所述基于所述目标业务基础信息和业务请求方输入所述业务请求方客户端的业务补充信息实施与所述业务参与方相关的业务处理，包括：基于所述目标业务基础信息和所述业务补充信息向与所述业务请求方客户端对应的业务响应服务端发送业务请求以实施业务处理。
  5. 根据权利要求1所述的方法，所述业务参与方包括商户，所述业务请求方包括支付方，所述业务补充信息包括待支付订单的订单信息，与所述商户客户端相关联的业务响应服务端包括支付平台服务端，各个支付平台服务端针对所述商户配置的业务基础信息包括收单信息。
  6. 一种基于图形码的业务处理方法，应用于索引平台，所述方法包括：
    接收业务请求方客户端基于业务参与方的标识信息发送的针对所述业务参与方的查询请求，所述业务参与方与至少一个业务响应服务端相关联，各个相关联的业务响应服务端针对所述业务参与方配置有相应的业务基础信息，各个相关联的业务响应服务端分别为所述业务参与方产生的业务基础信息和所述标识信息的映射关系被上传至索引平台进行记录，所述标识信息由所述业务请求方客户端解析所述业务参与方的业务图形码得到；
    根据记录的映射关系确定与所述标识信息对应的候选业务基础信息，以使得所述业务请求方客户端基于所述候选业务基础信息中与所述业务请求方客户端相匹配的业务基础信息和业务请求方输入所述业务请求方客户端的业务补充信息，实施与所述业务参与方相关的业务处理。
  7. 根据权利要求6所述的方法，还包括：
    接收与所述业务参与方相关联的其他业务响应服务端发送的第一添加请求，所述第一添加请求中包含所述标识信息，和所述其他业务响应服务端在与所述业务参与方建立关联关系后针对所述业务参与方配置的第一更新业务基础信息；
    在所述映射关系中添加所述标识信息与所述第一更新业务基础信息的对应关系。
  8. 根据权利要求6所述的方法，还包括：
    接收所述业务参与方的客户端发送的第二添加请求，所述第二添加请求中包含所述标识信息，和其他业务响应服务端在与所述业务参与方建立关联关系后针对所述业务参与方配置的第二更新业务基础信息，所述第二更新业务基础信息由所述业务参与方的客户端解析来自于所述其他业务响应服务端的更新图形码获取，所述更新图形码由所述其他业务响应服务端根据所述第二更新业务基础信息生成；
    在所述映射关系中添加所述标识信息与所述第二更新业务基础信息的对应关系。
  9. 根据权利要求6所述的方法，所述业务参与方包括商户，所述业务请求方包括支付方，所述业务补充信息包括待支付订单的订单信息，与所述商户客户端相关联的业务响应服务端包括支付平台服务端，各个支付平台服务端针对所述商户配置的业务基础信息包括收单信息。
  10. 一种业务信息的维护方法，包括：
    当任一业务响应服务端与业务参与方建立关联关系时，获取所述任一业务响应服务 端针对所述业务参与方配置的待合并业务基础信息；
    向索引平台发送针对所述待合并业务基础信息和所述业务参与方的标识信息的映射关系的添加请求，以使得所述索引平台记录所述映射关系；
    其中，所述索引平台记录的所述标识信息与相应业务基础信息的映射关系用于在所述索引平台接收到业务请求方客户端基于所述标识信息发送的针对所述业务参与方的查询请求时，确定与所述标识信息对应的候选业务基础信息，所述业务请求方客户端实施的与所述业务参与方相关的业务处理所采用的业务基础信息，为所述候选业务基础信息中与所述业务请求方客户端相匹配的业务基础信息，所述业务请求方客户端实施所述业务处理所采用的业务补充信息由业务请求方输入，所述业务请求方客户端通过解析所述业务参与方的业务图形码得到所述标识信息。
  11. 根据权利要求10所述的方法，所述获取所述任一业务响应服务端针对所述业务参与方配置的待合并业务基础信息，包括：
    解析所述任一业务响应服务端基于所述待合并业务基础信息生成的业务图形码以得到所述待合并业务基础信息。
  12. 根据权利要求10所述的方法，所述业务参与方包括商户，所述业务请求方客户端包括支付客户端方，所述业务补充信息包括待支付订单的订单信息，与所述商户客户端相关联的业务响应服务端包括支付平台服务端，各个支付平台服务端针对所述商户配置的业务信息业务基础信息包括收单信息。
  13. 一种基于图形码的业务处理装置，应用于业务请求方客户端，所述装置包括：
    标识解析单元，解析业务参与方的业务图形码，以获取所述业务参与方的标识信息，所述业务参与方与至少一个业务响应服务端相关联，各个相关联的业务响应服务端针对所述业务参与方配置有相应的业务基础信息，各个相关联的业务响应服务端分别为所述业务参与方产生的业务基础信息和所述标识信息的映射关系被上传至索引平台进行记录；
    发送单元，基于所述标识信息向所述索引平台发送针对所述业务参与方的查询请求，以使得所述索引平台根据记录的映射关系确定与所述标识信息对应的候选业务基础信息；
    业务处理单元，获取所述候选业务基础信息中与所述业务请求方客户端相匹配的目标业务基础信息，并基于所述目标业务基础信息和业务请求方输入所述业务请求方客户端的业务补充信息实施与所述业务参与方相关的业务处理。
  14. 根据权利要求13所述的装置，
    还包括：地址解析单元，解析所述业务图形码以获取所述索引平台的访问地址；
    所述发送单元具体用于：根据所述访问地址向所述索引平台发送所述查询请求，所 述查询请求中包含所述标识信息。
  15. 根据权利要求13所述的装置，所述业务处理单元具体用于：
    接收所述索引平台返回的所述目标业务基础信息，所述目标业务基础信息由所述索引平台从所述候选业务基础信息中识别得到；
    或者，接收所述索引平台返回的所述候选业务基础信息，并在所述候选业务基础信息中识别与所述业务请求方客户端相匹配的业务基础信息以作为所述目标业务基础信息。
  16. 根据权利要求13所述的装置，任一业务基础信息记录有配置所述任一业务基础信息的业务服务端的服务端标识；
    通过以下方式识别出所述目标业务基础信息：在所述候选业务基础信息中查找记录有目标服务端标识的业务基础信息，并将查找到的业务基础信息作为所述目标业务基础信息，所述目标服务端标识为与所述业务请求方客户端对应的业务响应服务端的服务端标识；
    所述业务处理单元具体用于：基于所述目标业务基础信息和所述业务补充信息向与所述业务请求方客户端对应的业务响应服务端发送业务请求以实施业务处理。
  17. 根据权利要求13所述的装置，所述业务参与方包括商户，所述业务请求方包括支付方，所述业务补充信息包括待支付订单的订单信息，与所述商户客户端相关联的业务响应服务端包括支付平台服务端，各个支付平台服务端针对所述商户配置的业务基础信息包括收单信息。
  18. 一种基于图形码的业务处理装置，应用于索引平台，所述装置包括：
    第一接收单元，接收业务请求方客户端基于业务参与方的标识信息发送的针对所述业务参与方的查询请求，所述业务参与方与至少一个业务响应服务端相关联，各个相关联的业务响应服务端针对所述业务参与方配置有相应的业务基础信息，各个相关联的业务响应服务端分别为所述业务参与方产生的业务基础信息和所述标识信息的映射关系被上传至索引平台进行记录，所述标识信息由所述业务请求方客户端解析所述业务参与方的业务图形码得到；
    确定单元，根据记录的映射关系确定与所述标识信息对应的候选业务基础信息，以使得所述业务请求方客户端基于所述候选业务基础信息中与所述业务请求方客户端相匹配的业务基础信息和业务请求方输入所述业务请求方客户端的业务补充信息，实施与所述业务参与方相关的业务处理。
  19. 根据权利要求18所述的装置，还包括：
    第二接收单元，接收与所述业务参与方相关联的其他业务响应服务端发送的第一添加请求，所述第一添加请求中包含所述标识信息，和所述其他业务响应服务端在与所述 业务参与方建立关联关系后针对所述业务参与方配置的第一更新业务基础信息；
    第一添加单元，在所述映射关系中添加所述标识信息与所述第一更新业务基础信息的对应关系。
  20. 根据权利要求18所述的装置，还包括：
    第三接收单元，接收所述业务参与方的客户端发送的第二添加请求，所述第二添加请求中包含所述标识信息，和其他业务响应服务端在与所述业务参与方建立关联关系后针对所述业务参与方配置的第二更新业务基础信息，所述第二更新业务基础信息由所述业务参与方的客户端解析来自于所述其他业务响应服务端的更新图形码获取，所述更新图形码由所述其他业务响应服务端根据所述第二更新业务基础信息生成；
    第二添加单元，在所述映射关系中添加所述标识信息与所述第二更新业务基础信息的对应关系。
  21. 根据权利要求18所述的装置，所述业务参与方包括商户，所述业务请求方包括支付方，所述业务补充信息包括待支付订单的订单信息，与所述商户客户端相关联的业务响应服务端包括支付平台服务端，各个支付平台服务端针对所述商户配置的业务基础信息包括收单信息。
  22. 一种业务信息的维护装置，包括：
    获取单元，当任一业务响应服务端与业务参与方建立关联关系时，获取所述任一业务响应服务端针对所述业务参与方配置的待合并业务基础信息；
    发送单元，向索引平台发送针对所述待合并业务基础信息和所述业务参与方的标识信息的映射关系的添加请求，以使得所述索引平台记录所述映射关系；
    其中，所述索引平台记录的所述标识信息与相应业务基础信息的映射关系用于在所述索引平台接收到业务请求方客户端基于所述标识信息发送的针对所述业务参与方的查询请求时，确定与所述标识信息对应的候选业务基础信息，所述业务请求方客户端实施的与所述业务参与方相关的业务处理所采用的业务基础信息，为所述候选业务基础信息中与所述业务请求方客户端相匹配的业务基础信息，所述业务请求方客户端实施所述业务处理所采用的业务补充信息由业务请求方输入，所述业务请求方客户端通过解析所述业务参与方的业务图形码得到所述标识信息。
  23. 根据权利要求22所述的装置，所述获取单元具体用于：
    解析所述任一业务响应服务端基于所述待合并业务基础信息生成的业务图形码以得到所述待合并业务基础信息。
  24. 根据权利要求22所述的装置，所述业务参与方包括商户，所述业务请求方客户端包括支付客户端方，所述业务补充信息包括待支付订单的订单信息，与所述商户客户端相关联的业务响应服务端包括支付平台服务端，各个支付平台服务端针对所述商户 配置的业务信息业务基础信息包括收单信息。
  25. 一种电子设备，包括：
    处理器；
    用于存储处理器可执行指令的存储器；
    其中，所述处理器通过运行所述可执行指令以实现如权利要求1-5中任一项所述的方法。
  26. 一种电子设备，包括：
    处理器；
    用于存储处理器可执行指令的存储器；
    其中，所述处理器通过运行所述可执行指令以实现如权利要求6-9中任一项所述的方法。
  27. 一种电子设备，包括：
    处理器；
    用于存储处理器可执行指令的存储器；
    其中，所述处理器通过运行所述可执行指令以实现如权利要求10-12中任一项所述的方法。
  28. 一种计算机可读存储介质，其上存储有计算机指令，该指令被处理器执行时实现如权利要求1-5中任一项所述方法的步骤。
  29. 一种计算机可读存储介质，其上存储有计算机指令，该指令被处理器执行时实现如权利要求6-9中任一项所述方法的步骤。
  30. 一种计算机可读存储介质，其上存储有计算机指令，该指令被处理器执行时实现如权利要求10-12中任一项所述方法的步骤。
PCT/CN2020/126970 2019-12-27 2020-11-06 基于图形码的业务处理方法及装置、电子设备、存储介质 WO2021129188A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201911376165.8A CN111160895A (zh) 2019-12-27 2019-12-27 基于图形码的业务处理方法及装置、电子设备、存储介质
CN201911376165.8 2019-12-27

Publications (1)

Publication Number Publication Date
WO2021129188A1 true WO2021129188A1 (zh) 2021-07-01

Family

ID=70558480

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/126970 WO2021129188A1 (zh) 2019-12-27 2020-11-06 基于图形码的业务处理方法及装置、电子设备、存储介质

Country Status (3)

Country Link
CN (1) CN111160895A (zh)
TW (1) TWI836075B (zh)
WO (1) WO2021129188A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114148107A (zh) * 2021-11-19 2022-03-08 三一筑工科技股份有限公司 构件喷码方法、装置和电子设备

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111160895A (zh) * 2019-12-27 2020-05-15 支付宝实验室(新加坡)有限公司 基于图形码的业务处理方法及装置、电子设备、存储介质
CN116843427A (zh) * 2020-08-03 2023-10-03 支付宝（中国）网络技术有限公司 扫码下单方法、业务码创建方法、装置和电子设备
CN114900537A (zh) * 2021-04-19 2022-08-12 北京京东方技术开发有限公司 一种建立连接的方法、装置、存储介质及服务器

Citations (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20140054369A1 (en) * 2012-08-24 2014-02-27 Michael A. Liberty Debit network routing selection using a qr code
CN104680114A (zh) * 2015-03-03 2015-06-03 黄伟军 一个二维码处理多个请求的方法及其系统
CN105701659A (zh) * 2016-03-11 2016-06-22 广州云移信息科技有限公司 基于二维码的网络支付方法及系统
CN106649478A (zh) * 2016-09-29 2017-05-10 浙江三网科技股份有限公司 一种一码多用的二维码响应式跳转方法
CN108052663A (zh) * 2017-01-17 2018-05-18 海南亚元防伪技术研究所（普通合伙） 一种共用二维码的应用方法及装置
CN111047321A (zh) * 2019-12-27 2020-04-21 支付宝实验室(新加坡)有限公司 业务处理方法及装置、电子设备、存储介质
CN111160895A (zh) * 2019-12-27 2020-05-15 支付宝实验室(新加坡)有限公司 基于图形码的业务处理方法及装置、电子设备、存储介质
CN111178840A (zh) * 2019-12-27 2020-05-19 支付宝实验室(新加坡)有限公司 业务处理方法及装置、系统、电子设备、存储介质
CN111340477A (zh) * 2020-02-07 2020-06-26 支付宝实验室(新加坡)有限公司 业务处理方法及装置、电子设备、存储介质

Family Cites Families (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
AU2013214801B2 (en) * 2012-02-02 2018-06-21 Visa International Service Association Multi-source, multi-dimensional, cross-entity, multimedia database platform apparatuses, methods and systems
US20140337138A1 (en) * 2013-05-08 2014-11-13 Jalpesh K. Chitalia Payment codes for enhanced consumer experience
CN108376362A (zh) * 2018-02-01 2018-08-07 阿里巴巴集团控股有限公司 退税方法、装置及设备
CN108564363B (zh) * 2018-02-28 2020-10-13 阿里巴巴集团控股有限公司 一种交易处理方法、服务器、客户端及系统
CN109447609A (zh) * 2018-09-25 2019-03-08 平安科技（深圳）有限公司 支付方法、装置、计算机设备和存储介质
CN109670804A (zh) * 2018-11-22 2019-04-23 杭州家娱互动网络科技有限公司 一种聚合支付方法、装置及电子设备
CN110135823B (zh) * 2019-04-09 2022-04-08 浙江禾平数据技术有限公司 订单处理方法、装置、计算机设备及可读存储介质

Patent Citations (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20140054369A1 (en) * 2012-08-24 2014-02-27 Michael A. Liberty Debit network routing selection using a qr code
CN104680114A (zh) * 2015-03-03 2015-06-03 黄伟军 一个二维码处理多个请求的方法及其系统
CN105701659A (zh) * 2016-03-11 2016-06-22 广州云移信息科技有限公司 基于二维码的网络支付方法及系统
CN106649478A (zh) * 2016-09-29 2017-05-10 浙江三网科技股份有限公司 一种一码多用的二维码响应式跳转方法
CN108052663A (zh) * 2017-01-17 2018-05-18 海南亚元防伪技术研究所（普通合伙） 一种共用二维码的应用方法及装置
CN111047321A (zh) * 2019-12-27 2020-04-21 支付宝实验室(新加坡)有限公司 业务处理方法及装置、电子设备、存储介质
CN111160895A (zh) * 2019-12-27 2020-05-15 支付宝实验室(新加坡)有限公司 基于图形码的业务处理方法及装置、电子设备、存储介质
CN111178840A (zh) * 2019-12-27 2020-05-19 支付宝实验室(新加坡)有限公司 业务处理方法及装置、系统、电子设备、存储介质
CN111340477A (zh) * 2020-02-07 2020-06-26 支付宝实验室(新加坡)有限公司 业务处理方法及装置、电子设备、存储介质

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114148107A (zh) * 2021-11-19 2022-03-08 三一筑工科技股份有限公司 构件喷码方法、装置和电子设备

Also Published As

Publication number Publication date
CN111160895A (zh) 2020-05-15
TWI836075B (zh) 2024-03-21
TW202125367A (zh) 2021-07-01

Similar Documents

Publication Publication Date Title
WO2021129188A1 (zh) 基于图形码的业务处理方法及装置、电子设备、存储介质
JP6615113B2 (ja) 支払アグリゲータに対する支払のルーティング
CN104378341B (zh) 模板获取方法、模板提供方法、装置及系统
US20150149353A1 (en) Methods and systems for obtaining merchant identification within payment authorization networks
CN111047321A (zh) 业务处理方法及装置、电子设备、存储介质
WO2021155721A1 (zh) 业务处理方法及装置、电子设备、存储介质
US10505922B2 (en) Service implementation method, payment method and apparatus
US20170061502A1 (en) Unified cross-channel advertisement platform
EP4116907A1 (en) Frictionless payment system
van Rossum The blockchain and its potential for science and academic publishing
TW201838431A (zh) 資源傳輸方法及裝置
KR20170116022A (ko) 서비스 구현
TW201530329A (zh) 資訊的展示方法及裝置
US12050630B2 (en) Method, system, and apparatus for rapid geographic search in an actor-based geographic search network
CN113159870A (zh) 推送信息的展示方法、装置及计算机设备
CN117333186A (zh) 额度信息的获取方法、额度管控规则的建立方法及装置
CN110942567A (zh) 自助设备数据处理方法、装置及系统
WO2022237606A1 (zh) 在支付时使用电子券的方法及装置
CN111814014B (zh) 信息交互方法、设备以及存储介质
CN107402825A (zh) 软件服务的实现方法和装置
TWI845681B (zh) 基於條碼支付的實現方法和裝置、基於條碼支付的系統
CN108446926B (zh) 数据处理方法和服务器
CN116128607A (zh) 产品推荐方法、装置、设备及存储介质
CN116823307A (zh) 用户分组处理方法、装置、设备和介质
TW202201307A (zh) 基於條碼支付的實現方法和裝置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 20906279

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 20906279

Country of ref document: EP

Kind code of ref document: A1