Business processing method, apparatus and system

By working together with the feature acquisition terminal and the business processing party, feature information is converted into account information, decoupling feature information acquisition from business processing. This solves the failure problem caused by logic changes in the traditional business processing chain, and improves compatibility and user experience.

CN115146995BActive Publication Date: 2026-08-04ALIPAY COM CO LTD
View PDF 2 Cites 0 Cited by

Patent Information

Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
ALIPAY COM CO LTD
Filing Date
2020-04-16
Publication Date
2026-08-04

AI Technical Summary

Technical Problem

In traditional business processing chains, when the processing logic of any link changes, subsequent links cannot correctly identify and process business processing information, leading to business processing failure. This requires improvements to the equipment throughout the chain, increasing costs and reducing user experience.

Method used

Feature information is collected by the feature acquisition terminal and converted into account information. The business processing party converts it into a format that can be recognized by subsequent stages, and the business analysis party generates processing instructions. This decouples feature information collection from business processing, making the feature information collection process transparent and imperceptible to subsequent stages.

Benefits of technology

It achieves compatibility across the business processing chain, reduces improvement costs, enhances user experience, and ensures the continuity and efficiency of business processing.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN115146995B_ABST
    Figure CN115146995B_ABST
Patent Text Reader

Abstract

The present specification provides a business processing method, device and system, which can include: a feature collection terminal, the feature collection terminal is used for collecting feature information of a first business participant, and sending the feature information to a business processing party; the business processing party is used for converting the received feature information into first account information corresponding to the first business participant, and returning the first account information to the feature collection terminal, the first account information is used to generate a business processing request; a business receiving party, the business receiving party is used for transmitting the business processing request to a business analysis party; the business analysis party is used for generating a business processing instruction for the business processing party by analyzing the received business processing request, the business processing instruction contains the first account information and a processing mode, to instruct the business processing party to perform corresponding processing operation on the account of the first business participant.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This specification relates to the field of business processing technology, and in particular to a business processing method, apparatus and system. Background Technology

[0002] In traditional business processing chains, the business processing involves multiple links along the entire chain. Each link needs to cooperate with the others. The devices corresponding to each link in the business processing chain need to be able to correctly identify and process the business processing information generated during the business processing process in order to achieve normal business processing.

[0003] When the processing logic of any link in the business processing chain changes, resulting in a change in the generated business processing information, the corresponding devices in subsequent links will no longer be able to correctly identify and process the changed business processing information, leading to business processing failure. It is necessary to make adaptive improvements to the devices corresponding to each link in the entire business processing chain to ensure that the normal processing of the business continues. Summary of the Invention

[0004] In view of this, this specification provides business processing methods, apparatus and systems.

[0005] According to a first aspect of this specification, a business processing system is provided, the system comprising:

[0006] A feature acquisition terminal is used to collect feature information of the first business participant and send the feature information to the business processing party.

[0007] The business processing party is used to convert the received feature information into first account information corresponding to the first business participant, and return the first account information to the feature collection terminal. The first account information is used to generate a business processing request.

[0008] The service receiving party is used to transmit the service processing request to the service analysis party.

[0009] A business analysis party is configured to parse the received business processing request and generate a business processing instruction for the business processing party. The business processing instruction includes the first account information and the processing method, so as to instruct the business processing party to perform corresponding processing operations on the account of the first business participant.

[0010] According to the second aspect of this specification, a business processing method is proposed, applied to a feature acquisition terminal; the method includes:

[0011] Feature collection is performed on the primary business participant to generate feature information;

[0012] The feature information is sent to the business processing party so that the business processing party converts the received feature information into the first account information corresponding to the first business participant;

[0013] Based on the first account information returned by the business processing party, an operation is triggered to generate a business processing request from the first account information; wherein, the business processing request is transmitted by the business receiving party to the business analysis party, so that the business analysis party parses and generates a business processing instruction for the business processing party, the business processing instruction includes the first account information and the processing method, so as to instruct the business processing party to perform corresponding processing operations on the account of the first business participant.

[0014] According to a third aspect of this specification, a business processing method is proposed, applied to a business processing party; the method includes:

[0015] The feature information sent by the feature acquisition terminal is received. The feature information is generated by the feature acquisition terminal for feature acquisition of the first business participant.

[0016] The feature information is converted into first account information corresponding to the first business participant, and the first account information is returned to the feature acquisition terminal. The first account information is used to generate a business processing request. The business processing request is transmitted by the business acceptor to the business analyst, so that the business analyst can parse and generate a business processing instruction for the business processing party. The business processing instruction includes the first account information and the processing method.

[0017] Receive business processing instructions from the business analysis party, and perform corresponding processing operations on the account of the first business participant according to the business processing instructions.

[0018] According to the fourth aspect of this specification, a service processing apparatus is proposed for use in a feature acquisition terminal; the apparatus includes:

[0019] The data acquisition unit is used to collect features from the first business participant and generate feature information.

[0020] A sending unit is configured to send the feature information to a service processing party, so that the service processing party converts the received feature information into first account information corresponding to the first service participant.

[0021] The receiving unit is configured to trigger an operation to generate a business processing request from the first account information returned by the business processing party; wherein the business processing request is transmitted by the business receiving party to the business analysis party, so that the business analysis party parses and generates a business processing instruction for the business processing party, the business processing instruction including the first account information and the processing method, to instruct the business processing party to perform corresponding processing operations on the account of the first business participant.

[0022] According to the fifth aspect of this specification, a business processing apparatus is provided for use in a business processing party; the apparatus includes:

[0023] The feature information receiving unit is used to receive feature information sent by the feature acquisition terminal, wherein the feature information is generated by the feature acquisition terminal for feature acquisition of the first business participant;

[0024] The conversion and transmission unit is used to convert the feature information into first account information corresponding to the first business participant, and return the first account information to the feature acquisition terminal. The first account information is used to generate a business processing request. The business processing request is transmitted by the business acceptor to the business analyzer, so that the business analyzer parses and generates a business processing instruction for the business processor. The business processing instruction includes the first account information and the processing method.

[0025] The instruction receiving unit is used to receive business processing instructions from the business analysis party and perform corresponding processing operations on the account of the first business participant according to the business processing instructions.

[0026] According to a sixth aspect of this specification, an electronic device is provided. The electronic device includes:

[0027] processor;

[0028] Memory used to store processor-executable instructions;

[0029] The processor implements the method described in the second or third aspect by running the executable instructions.

[0030] According to a seventh aspect of this specification, a computer-readable storage medium is provided that stores computer instructions thereon, which, when executed by a processor, implement the steps of the method as described in the second or third aspect. Attached Figure Description

[0031] Figure 1 This is a schematic diagram of the architecture of a business processing system shown in this specification.

[0032] Figure 2This is a flowchart illustrating a business processing method as shown in this specification.

[0033] Figure 3 This is a flowchart illustrating another business processing method shown in this specification.

[0034] Figure 4 This is a flowchart illustrating a business processing method as an exemplary embodiment of this specification.

[0035] Figure 5 This is a flowchart of another business processing method as an exemplary embodiment of this specification.

[0036] Figure 6 This is a schematic diagram of the structure of an electronic device shown in an exemplary embodiment of this specification.

[0037] Figure 7 This is a block diagram illustrating a service processing apparatus according to an exemplary embodiment of this specification.

[0038] Figure 8 This is a schematic diagram of the structure of another electronic device illustrated in an exemplary embodiment of this specification.

[0039] Figure 9 This is a block diagram illustrating another service processing apparatus as an exemplary embodiment of this specification. Detailed Implementation

[0040] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numerals in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with one or more embodiments of this specification. Rather, they are merely examples of apparatuses and methods consistent with some aspects of one or more embodiments of this specification as detailed in the appended claims.

[0041] It should be noted that the steps of the corresponding methods are not necessarily performed in the order shown and described in this specification in other embodiments. In some other embodiments, the methods may include more or fewer steps than described in this specification. Furthermore, a single step described in this specification may be broken down into multiple steps in other embodiments; and multiple steps described in this specification may be combined into a single step in other embodiments.

[0042] Figure 1 This is a schematic diagram of the architecture of a business processing system shown in this specification. Figure 1 The system may include a feature acquisition terminal 11, a service processing unit 12, a service acceptance unit 13, and a service analysis unit 14.

[0043] The feature acquisition terminal 11 can collect feature information of the first business participant and send the feature information to the business processing party 12. The feature acquisition terminal 11 can be a device with acquisition function, including user equipment, wireless terminal equipment, mobile terminal equipment, etc.

[0044] The business processing party 12 can convert the received feature information into the first account information corresponding to the first business participant, and return the first account information to the feature acquisition terminal 11. The first account information can be used to generate a business processing request.

[0045] The business receiving party 13 can transmit the business processing request to the business analysis party.

[0046] The business analysis party 14 parses the received business processing request and generates a business processing instruction for the business processing party. The business processing instruction may include the first account information and the processing method to instruct the business processing party to perform corresponding processing operations on the account of the first business participant.

[0047] In related technologies, the business processing involves multiple stages along the entire business processing chain. Each stage needs to cooperate with the others, and the devices corresponding to each stage in the business processing chain must be able to correctly identify and process the business processing information generated during the process in order to achieve normal business processing. Therefore, if the processing logic of any stage in the business processing chain changes, causing the generated business processing information to change, the devices corresponding to subsequent stages will no longer be able to correctly identify and process the changed business processing information, which can easily lead to business processing failure.

[0048] Therefore, this specification addresses the aforementioned technical problems in related technologies by improving business processing methods. A detailed description is provided below with reference to embodiments.

[0049] Figure 2 This is a flowchart illustrating one type of business processing method described in this specification. For example... Figure 2 As shown, this method is applied to a feature acquisition terminal; the method may include the following steps:

[0050] Step 202: Collect features from the first business participant and generate feature information.

[0051] Step 204: Send the feature information to the business processing party so that the business processing party can convert the received feature information into the first account information corresponding to the first business participant.

[0052] In one embodiment, the feature acquisition terminal can respond to a received service triggering instruction, collect features from the first service participant, generate feature information, and convert the feature information into the first account information corresponding to the first service participant through the service processing party.

[0053] In another embodiment, before receiving a service trigger instruction, the feature acquisition terminal can collect features from all objects within its collection range and generate a corresponding set of feature information. All objects include a first service participant. The collected feature information can be converted into corresponding account information by the service processor, whereby the account information may include the object's account and username. The feature acquisition terminal can receive the account information returned by the service processor and can locally cache the mapping relationship between feature information and account information. Therefore, in response to the received service trigger instruction, the feature acquisition terminal can collect features from the first service participant, generate feature information, and determine the first account information corresponding to the first service participant based on the locally cached mapping relationship.

[0054] Step 206: Based on the first account information returned by the business processing party, trigger the operation of generating a business processing request from the first account information.

[0055] The feature acquisition terminal triggers the operation of generating a business processing request from the first account information returned by the business processing party. The business processing request is transmitted by the business processing party to the business analysis party, so that the business analysis party can parse and generate a business processing instruction for the business processing party. The business processing instruction may include the first account information and the processing method, so as to instruct the first business participant to perform the corresponding processing operation on the account of the first business participant.

[0056] In one embodiment, the feature acquisition terminal can receive first account information returned by the service processing party, while the service acceptance party may include a service acceptance terminal and a service acceptance server, with the service acceptance terminal connected to the feature acquisition terminal. The feature acquisition terminal can send the first account information to the service acceptance terminal, enabling the service acceptance terminal to generate a service processing request based on the first account information and upload the request to the service acceptance server. Although the feature acquisition terminal and the service acceptance terminal are classified as different devices, they can actually reside in the same or different physical entities, and this specification does not impose any limitations on this.

[0057] In another embodiment, the feature acquisition terminal can receive first account information returned by the service processing party, and the service acceptance party may include a service acceptance server. The feature acquisition terminal can generate a service processing request based on the received first account information, and the feature acquisition terminal can upload the service processing request to the service acceptance server.

[0058] In another embodiment, the service acceptor may include a service acceptor server, and the service processing request may include the second account information corresponding to the second service participant. The account data corresponding to the second account information can be maintained by the service acceptor server, so that the service analyst can parse the received service processing request to generate a service processing instruction for the service acceptor server. This service processing instruction can be used by the service acceptor server to perform corresponding processing operations on the account of the second service participant.

[0059] As can be seen from the above technical solutions, the feature acquisition terminal in this specification can send the acquired feature information to the business processing party, which then converts the feature information into account information that can be supported by each link in the subsequent business processing chain. This decouples the feature information acquisition process from the subsequent business processing links. Therefore, the devices corresponding to each link in the subsequent business processing chain no longer need to identify and process the feature information, enabling the subsequent links in the business processing chain to be compatible with different feature information acquisition processes. The subsequent links in the business processing chain are completely transparent and unaware of the feature acquisition process. Even if the feature information acquisition process changes, it will not affect the subsequent business processing links, thereby reducing improvement costs and improving user experience.

[0060] Figure 3 This is a flowchart illustrating another business processing method as shown in this specification. For example... Figure 3 As shown, this method is applied to the business processing side; the method may include the following steps:

[0061] Step 302: Receive feature information sent by the feature acquisition terminal. The feature information is generated by the feature acquisition terminal for feature acquisition of the first business participant.

[0062] Step 304: Convert the feature information into first account information corresponding to the first business participant, and return the first account information to the feature acquisition terminal.

[0063] The service processing party can receive feature information sent by the feature acquisition terminal. This feature information is generated by the feature acquisition terminal through feature acquisition of the first service participant. The service processing party can convert this feature information into the first account information corresponding to the first service participant and return the first account information to the feature acquisition terminal. This first account information can be used to generate a service processing request. The service processing request can be transmitted by the service receiving party to the service analysis party, so that the service analysis party can parse the service processing request and generate a service processing instruction for the service processing party. The service processing instruction includes the first account information and the processing method.

[0064] In one embodiment, the service acceptance party may include a service acceptance terminal and a service acceptance server, with the service acceptance terminal connected to a feature collection terminal. The first account information can then be sent from the feature collection terminal to the service acceptance terminal, enabling the service acceptance terminal to generate a service processing request based on the received first account information and upload the request to the service acceptance server. The service processing request can then be transmitted from the service acceptance server to the service analysis party.

[0065] In another embodiment, the service acceptor may include a service acceptor server. The first account information can be used by the feature collection terminal to generate a service processing request, and the service processing request can be uploaded by the feature collection terminal to the service acceptor server, and then the service acceptor server can transmit the service processing request to the service analyzer.

[0066] In another embodiment, after the feature acquisition terminal responds to the received service triggering instruction, the service processor can receive the feature information of the first service participant sent by the feature acquisition terminal. This feature information is generated by the feature acquisition terminal for feature acquisition of the first service participant. The service processor can convert the feature information into the first account information corresponding to the first service participant and return the first account information to the feature acquisition terminal.

[0067] In another embodiment, before the feature acquisition terminal receives the service trigger instruction, the service processor may receive a set of feature information sent by the feature acquisition terminal. This set of feature information includes feature information of all objects collected by the feature acquisition terminal within the collection range before receiving the service trigger instruction, wherein the objects include the first service participant. The service processor can convert each received feature information into corresponding account information and return the account information to the feature acquisition terminal, thereby enabling the feature acquisition terminal to locally cache the mapping relationship between feature information and account information. After the feature acquisition terminal responds to the received service trigger instruction, the mapping relationship can be used by the feature acquisition terminal to determine the first account information corresponding to the feature information of the first service participant.

[0068] Step 306: Receive a business processing instruction from the business analysis party, and perform corresponding processing operations on the account of the first business participant according to the business processing instruction.

[0069] The business processing party can receive business processing instructions from the business analysis party, and can perform corresponding processing operations on the account of the first business participant according to the first account information and processing method contained in the business processing instructions.

[0070] In one embodiment, the service acceptor may include a service acceptor server, and the service processing request may include the second account information corresponding to the second service participant. The account data corresponding to the second account information can be maintained by the service acceptor server, which can enable the service analyst to parse the received service processing request and generate a service processing instruction for the service acceptor server. The service processing instruction can be used by the service acceptor server to perform corresponding processing operations on the account of the second service participant.

[0071] As can be seen from the above technical solutions, the feature acquisition terminal in this specification can send the acquired feature information to the business processing party, which then converts the feature information into account information that can be supported by each link in the subsequent business processing chain. This decouples the feature information acquisition process from the subsequent business processing links. Therefore, the devices corresponding to each link in the subsequent business processing chain no longer need to identify and process the feature information, enabling the subsequent links in the business processing chain to be compatible with different feature information acquisition processes. The subsequent links in the business processing chain are completely transparent and unaware of the feature acquisition process. Even if the feature information acquisition process changes, it will not affect the subsequent business processing links, thereby reducing improvement costs and improving user experience.

[0072] The following section describes the interaction process between the feature acquisition terminal, the service processor, the service recipient, and the service analyst, in conjunction with... Figure 4 This specification describes the technical solution, where the service acceptance party includes a service acceptance terminal and a service acceptance server. Taking a resource allocation scenario as an example, the feature collection terminal is a facial recognition device, the first service participant is resource provider 1, which provides resource X to resource recipient A using facial recognition, the service processing party is resource processing party B, the second service participant is resource recipient A, and resource recipient A's account is maintained by resource manager C. The service acceptance party includes a service acceptance terminal and a service acceptance server. The service acceptance terminal is the terminal device deployed by resource recipient A on resource manager C's device, the service acceptance server is resource manager C's acceptance network, and the service analysis party is the resource allocation system. Please refer to [link / reference]. Figure 4 , Figure 4This is a flowchart illustrating a business processing method as an exemplary embodiment of this specification. Figure 4 As shown, the following steps may be included:

[0073] Step 402: Collect facial feature information from resource provider 1.

[0074] Step 404: Send facial feature information.

[0075] In this embodiment, the facial recognition device can receive a resource allocation operation, i.e., a service triggering instruction, triggered by resource provider 1 or resource receiver A. Then, the facial recognition device can collect the facial feature information of resource provider 1 and send the facial feature information to resource processor B.

[0076] Of course, the feature acquisition terminal in this embodiment can also be an iris recognition device, an NFC (Near Field Communication) recognition device, a non-standard QR code recognition device, a machine vision contactless recognition device, or other innovative recognition devices. This specification does not limit this. In fact, the feature information collected by the feature acquisition terminal in this specification can be converted into account information that can be recognized and processed in subsequent business processing stages by the business processing party. Therefore, the feature acquisition terminal can be changed at will according to actual usage needs without affecting the processing operations in subsequent stages.

[0077] Step 406: Convert the facial feature information into the account information of resource provider 1.

[0078] Step 408: Return the account information of resource provider 1.

[0079] In this embodiment, resource processor B can convert the received facial feature information into the account information of resource provider 1 on resource processor B. This account information may include resource provider 1's account, username, etc., but this specification does not limit this. Resource processor B can then return this account information to the facial recognition device. Furthermore, resource processor B can perform account authentication on the user 1's account information obtained after converting the feature information, thereby ensuring the legitimacy of the account information.

[0080] Step 410: Send the account information of resource provider 1.

[0081] Step 412: Generate a business processing request.

[0082] Step 414: Upload the business processing request.

[0083] Step 416: Transmit the service processing request.

[0084] In this embodiment, the facial recognition device can send the account information of resource provider 1 to the terminal device of resource manager C. The facial recognition device is connected to the terminal device of resource manager C, so that the terminal device of resource manager C can generate a corresponding business processing request based on the received account information of resource provider 1. At the same time, the terminal device of resource manager C can also add the account information of resource receiver A to the generated business processing request. The account information can be manually entered by resource receiver A or pre-stored in the terminal device by resource receiver A. This specification does not limit this.

[0085] The terminal device of resource manager C can upload the generated business processing request to the acceptance network of resource manager C. The acceptance network of resource manager C can identify the business processing request and transmit it to the resource allocation system.

[0086] Step 418: Parse and generate business processing instructions.

[0087] Step 420: Send the service processing instruction.

[0088] In this embodiment, the resource allocation system can parse the received service processing request and generate service processing instructions for resource processor B and service processing instructions for the receiving network of resource manager C. The resource allocation system can send the service processing instructions to the receiving networks of resource processor B and resource manager C. The service processing instruction for resource processor B may include the account information of resource provider 1 and the corresponding operation of reducing resource X. The service processing instruction for the receiving network of resource manager C may include the account information of resource receiver A in resource manager C and the corresponding operation of increasing resource X.

[0089] Step 422: Take appropriate action regarding the account of resource provider 1.

[0090] In this embodiment, after receiving a service processing instruction, resource processor B can reduce resource X for the account corresponding to resource provider 1's account information according to the service processing instruction. When resource manager C's receiving network receives a service processing instruction, it can increase resource X for the account corresponding to resource receiver A.

[0091] The following section describes the interaction process between the feature acquisition terminal, the service processor, the service recipient, and the service analyst, in conjunction with... Figure 5 The technical solution described in this specification is as follows, wherein, with Figure 4The difference lies in the fact that the service acceptance party includes the service acceptance server. Taking a resource allocation scenario as an example, the feature collection terminal is a facial recognition device. The first service participant is resource provider 1, which provides resource X to resource recipient A using facial recognition. The service processor is resource processor B. The second service participant is resource recipient A, whose account is maintained by resource manager C. The service acceptance party includes the service acceptance server, which is the service acceptance network of resource manager C. The service analysis party is the resource allocation system. Please refer to [link to relevant documentation]. Figure 5 , Figure 5 This is a flowchart illustrating a business processing method as an exemplary embodiment of this specification.

[0092] like Figure 5 As shown, the following steps may be included:

[0093] Step 502: Collect feature information of all objects within the collection range of the facial recognition device.

[0094] Step 504: Send the feature information set.

[0095] In this embodiment, before receiving a service trigger instruction, the facial recognition device can collect feature information of all objects within its collection range. For example, if there are resource provider 1, resource provider 2, and resource provider 3 within the collection range, the facial recognition device can collect the facial feature information of resource provider 1, resource provider 2, and resource provider 3 respectively, and send the collected facial feature information to resource processing party B.

[0096] Of course, the feature acquisition terminal in this embodiment can also be an iris recognition device, an NFC (Near Field Communication) recognition device, a non-standard QR code recognition device, a machine vision contactless recognition device, or other innovative recognition devices. This specification does not limit this. In fact, the feature information collected by the feature acquisition terminal in this specification can be converted into account information that can be recognized and processed in subsequent business processing stages by the business processing party. Therefore, the feature acquisition terminal can be changed at will according to actual usage needs without affecting the processing operations in subsequent stages.

[0097] Step 506: Convert the feature information into account information.

[0098] Step 508: Return account information.

[0099] In this embodiment, the resource processing party B can convert the facial feature information received from resource provider 1, resource provider 2 and resource provider 3 into account information 1 corresponding to resource provider 1, account information 2 corresponding to resource provider 2 and account information 3 corresponding to resource provider 3 respectively, and return all the converted account information to the facial recognition device.

[0100] Step 510: Maintain the mapping relationship between feature information and account information.

[0101] Step 512: Collect feature information of resource provider 1.

[0102] Step 514: Generate a business processing request.

[0103] Step 516: Upload the business processing request.

[0104] In this embodiment, the facial recognition device can receive the returned account information and cache the mapping relationship between feature information and account information locally, that is, the feature information of resource provider 1 corresponds to account information 1, the feature information of resource provider 2 corresponds to account information 2, and the feature information of resource provider 3 corresponds to account information 3.

[0105] When the facial recognition device receives a resource allocation operation (service triggering instruction) triggered by resource provider 1 or resource recipient A, it can collect the facial feature information of resource provider 1 and search for this facial feature information in the locally cached mapping relationship. If it can be found, the device can directly determine the account information 1 corresponding to resource provider 1 based on the mapping relationship. If, after receiving the service triggering instruction, the facial recognition device collects the facial feature information of resource provider 4, and this facial feature information cannot be found in the above mapping relationship, the facial recognition device can send this facial feature information to resource processor B for processing and conversion. Figure 4 Similarly, this will not be elaborated upon here.

[0106] In this embodiment, after receiving a service triggering instruction, the facial recognition device can determine the account information 1 of resource provider 1 based on the mapping relationship in the local cache. The facial recognition device can also directly generate a corresponding service processing request based on the account information 1. At the same time, the facial recognition device can add the account information corresponding to resource recipient A to the generated service processing request. This account information can be manually entered by resource recipient A or pre-stored in the facial recognition device by resource recipient A. This specification does not limit this.

[0107] The facial recognition device can upload business processing requests to the processing network of resource manager C. The facial recognition device is connected to the processing network of resource manager C.

[0108] In this embodiment, the facial recognition device can automatically scan within a preset collection range. As long as a business participant enters the collection range, its feature information can be automatically collected and converted. The mapping relationship between feature information and account information is cached locally for a preset duration. This preset duration can be set according to actual usage and is not limited in this specification. When responding to a business trigger command, the facial recognition device can directly find the corresponding first account information in the mapping relationship based on the collected feature information of the first business participant, eliminating the need to temporarily send it to the business processing unit for conversion. This avoids delays caused by network issues and improves business processing efficiency.

[0109] Step 518: Transmit the service processing request.

[0110] In this embodiment, the receiving network of resource manager C can transmit the acquired service acceptance requests to the resource allocation system.

[0111] Step 520: Parse and generate business processing instructions.

[0112] Step 522: Send the service processing instruction.

[0113] Step 524: Take appropriate action regarding the account of resource provider 1.

[0114] In this embodiment, steps 520-524 can be referred to Figure 4 Steps 418-422 in the illustrated embodiment will not be repeated here.

[0115] In the technical solution of this specification, Figure 4 In the illustrated embodiment, the terminal device of resource manager C generates the corresponding service processing request, which can also be applied to... Figure 5 In the illustrated embodiment; and, Figure 5 In the embodiments described above, the facial recognition device pre-caches the mapping relationship between feature information and account information locally, which can also be applied to... Figure 4 The embodiments shown are not intended to limit the scope of this specification.

[0116] As can be seen from the above technical solutions, the feature acquisition terminal in this specification can send the acquired feature information to the business processing party, which then converts the feature information into account information that can be supported by each link in the subsequent business processing chain. This decouples the feature information acquisition process from the subsequent business processing links. Therefore, the devices corresponding to each link in the subsequent business processing chain no longer need to identify and process the feature information, enabling the subsequent links in the business processing chain to be compatible with different feature information acquisition processes. The subsequent links in the business processing chain are completely transparent and unaware of the feature acquisition process. Even if the feature information acquisition process changes, it will not affect the subsequent business processing links, thereby reducing improvement costs and improving user experience.

[0117] Figure 6 A schematic diagram of an electronic device according to an exemplary embodiment of this specification is shown. Please refer to... Figure 6 At the hardware level, the electronic device includes a processor 602, an internal bus 604, a network interface 606, memory 608, and non-volatile memory 610, and may also include other hardware required for business operations. The processor 602 reads the corresponding computer program from the non-volatile memory 610 into the memory 608 and then runs it, forming a business processing device at the logical level. Of course, in addition to software implementation, this specification does not exclude other implementation methods, such as logic devices or a combination of hardware and software, etc. That is to say, the execution subject of the following processing flow is not limited to individual logic units, but can also be hardware or logic devices.

[0118] Please refer to Figure 7 In the software implementation, the service processing device may include a data acquisition unit 702, a transmission unit 704, and a reception unit 706. Wherein:

[0119] The data acquisition unit 702 is used to collect features from the first business participant and generate feature information.

[0120] The sending unit 704 is used to send the feature information to the service processing party, so that the service processing party converts the received feature information into the first account information corresponding to the first service participant.

[0121] The receiving unit 706 is configured to trigger an operation to generate a business processing request from the first account information returned by the business processing party; wherein the business processing request is transmitted by the business receiving party to the business analysis party, so that the business analysis party parses and generates a business processing instruction for the business processing party, the business processing instruction including the first account information and the processing method, to instruct the business processing party to perform corresponding processing operations on the account of the first business participant.

[0122] Optionally, the service acceptor includes a service accepting terminal and a service accepting server;

[0123] The receiving unit 706 is specifically used to send the first account information to the service acceptance terminal, so that the service acceptance terminal generates the service processing request based on the first account information and uploads the service processing request to the service acceptance server.

[0124] Optionally, the service acceptor includes a service accepting server;

[0125] The receiving unit 706 is specifically used to generate the business processing request based on the received first account information, and upload the business processing request to the business acceptance server.

[0126] Optionally, the service acceptor includes a service acceptor server; the service processing request includes second account information corresponding to the second service participant, and the account data corresponding to the second account information is maintained by the service acceptor server, so that the service analyzer parses the received service processing request and generates a service processing instruction for the service acceptor server, and the service acceptor server uses the service processing instruction to perform corresponding processing operations on the account of the second service participant.

[0127] Optionally, in response to the received service triggering instruction, feature collection is performed on the first service participant to generate feature information.

[0128] Optionally, before receiving the business trigger instruction, feature collection is performed on all objects entering the collection range to generate a feature information set. The objects include the first business participant. The business processing party converts each feature information in the feature information set into corresponding account information and caches the mapping relationship between feature information and account information locally.

[0129] The acquisition unit 702 is specifically used to respond to the received service triggering instruction, collect features of the first service participant, generate feature information, and determine the first account information corresponding to the feature information of the first service participant according to the mapping relationship of the local cache.

[0130] The specific implementation process of the functions and roles of each unit in the above device can be found in the implementation process of the corresponding steps in the above method, and will not be repeated here.

[0131] Figure 8 A schematic diagram of an electronic device according to an exemplary embodiment of this specification is shown. Please refer to... Figure 8At the hardware level, the electronic device includes a processor 802, an internal bus 804, a network interface 806, memory 808, and non-volatile memory 810, and may also include other hardware required for business operations. The processor 802 reads the corresponding computer program from the non-volatile memory 810 into the memory 808 and then runs it, forming a business processing device at the logical level. Of course, in addition to software implementation, this specification does not exclude other implementation methods, such as logic devices or a combination of hardware and software, etc. That is to say, the execution subject of the following processing flow is not limited to individual logic units, but can also be hardware or logic devices.

[0132] Please refer to Figure 9 In the software implementation, the service processing device may include a feature information receiving unit 902, a conversion and transmission unit 904, and an instruction receiving unit 906. Wherein:

[0133] The feature information receiving unit 902 is used to receive feature information sent by the feature acquisition terminal, the feature information being generated by the feature acquisition terminal for feature acquisition of the first business participant;

[0134] The conversion and transmission unit 904 is used to convert the feature information into first account information corresponding to the first business participant, and return the first account information to the feature acquisition terminal. The first account information is used to generate a business processing request. The business processing request is transmitted by the business acceptor to the business analyzer, so that the business analyzer parses and generates a business processing instruction for the business processor. The business processing instruction includes the first account information and the processing method.

[0135] The instruction receiving unit 906 is used to receive business processing instructions from the business analysis party and perform corresponding processing operations on the account of the first business participant according to the business processing instructions.

[0136] Optionally, the service acceptor includes a service accepting terminal and a service accepting server; the first account information is sent by the feature collection terminal to the service accepting terminal, so that the service accepting terminal generates the service processing request based on the received first account information and uploads the service processing request to the service accepting server.

[0137] Optionally, the service acceptor includes a service accepting server; the first account information is used by the feature collection terminal to generate the service processing request, wherein the service processing request is uploaded by the feature collection terminal to the service accepting server.

[0138] Optionally, the service acceptor includes a service accepting terminal; the service processing request includes second account information corresponding to the second service participant, and the account data corresponding to the second account information is maintained by the service accepting server, so that the service analyzer parses the received service processing request and generates a service processing instruction for the service accepting server, and the service accepting server uses the service processing instruction to perform corresponding processing operations on the account of the second service participant.

[0139] Optionally, the feature information is collected by the feature acquisition terminal in response to a received service trigger command.

[0140] Optionally, a set of feature information sent by the feature acquisition terminal is received. The set of feature information includes feature information of all objects collected by the feature acquisition terminal within the acquisition range before receiving the service triggering instruction, wherein the objects include the first service participant.

[0141] The conversion and sending unit 904 is specifically used to convert each feature information in the feature information set into corresponding account information, and return the account information to the feature acquisition terminal, so that the feature acquisition terminal caches the mapping relationship between feature information and account information locally. The mapping relationship is used by the feature acquisition terminal to determine the first account information corresponding to the feature information of the first business participant after responding to the received business triggering instruction.

[0142] The specific implementation process of the functions and roles of each unit in the above device can be found in the implementation process of the corresponding steps in the above method, and will not be repeated here.

[0143] For the device embodiments, since they basically correspond to the method embodiments, the relevant parts can be referred to in the description of the method embodiments. The device embodiments described above are merely illustrative. The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of the modules can be selected to achieve the purpose of the solution in this specification according to actual needs. Those skilled in the art can understand and implement this without creative effort.

[0144] In an exemplary embodiment, a non-transitory computer-readable storage medium including instructions is also provided, such as a memory including instructions, which can be executed by a processor of a message transmitting device to perform the above method, the method including:

[0145] Feature collection is performed on the primary business participant to generate feature information;

[0146] The feature information is sent to the business processing party so that the business processing party converts the received feature information into the first account information corresponding to the first business participant;

[0147] Based on the first account information returned by the business processing party, an operation is triggered to generate a business processing request from the first account information; wherein, the business processing request is transmitted by the business receiving party to the business analysis party, so that the business analysis party parses and generates a business processing instruction for the business processing party, the business processing instruction includes the first account information and the processing method, so as to instruct the business processing party to perform corresponding processing operations on the account of the first business participant.

[0148] Optionally, the service acceptor includes a service accepting terminal and a service accepting server;

[0149] The operation of triggering the generation of the first account information into a business processing request includes: sending the first account information to the business acceptance terminal, so that the business acceptance terminal generates the business processing request based on the first account information and uploads the business processing request to the business acceptance server.

[0150] Optionally, the service acceptor includes a service accepting server;

[0151] The operation of triggering the generation of the first account information into a business processing request includes: generating the business processing request based on the received first account information;

[0152] The method further includes uploading the business processing request to the business acceptance server.

[0153] Optionally, the service acceptor includes a service acceptor server; the service processing request includes second account information corresponding to the second service participant, and the account data corresponding to the second account information is maintained by the service acceptor server, so that the service analyzer parses the received service processing request and generates a service processing instruction for the service acceptor server, and the service acceptor server uses the service processing instruction to perform corresponding processing operations on the account of the second service participant.

[0154] Optionally, in response to the received service triggering instruction, feature collection is performed on the first service participant to generate feature information.

[0155] Optionally, before receiving the business trigger instruction, feature collection is performed on all objects entering the collection range to generate a feature information set. The objects include the first business participant. The business processing party converts each feature information in the feature information set into corresponding account information and caches the mapping relationship between feature information and account information locally.

[0156] The step of collecting features from the first business participant and generating feature information includes: in response to the received business triggering instruction, collecting features from the first business participant, generating feature information, and determining the first account information corresponding to the feature information of the first business participant based on the mapping relationship of the local cache.

[0157] The non-transitory computer-readable storage medium may be ROM, random access memory (RAM), CD-ROM, magnetic tape, floppy disk and optical data storage device, etc., and this specification does not limit it.

[0158] In an exemplary embodiment, another non-transitory computer-readable storage medium including instructions is also provided, such as a memory including instructions, which can be executed by a processor of a message transmitting device to perform the above method, the method including:

[0159] The feature information sent by the feature acquisition terminal is received. The feature information is generated by the feature acquisition terminal for feature acquisition of the first business participant.

[0160] The feature information is converted into first account information corresponding to the first business participant, and the first account information is returned to the feature acquisition terminal. The first account information is used to generate a business processing request. The business processing request is transmitted by the business acceptor to the business analyst, so that the business analyst can parse and generate a business processing instruction for the business processing party. The business processing instruction includes the first account information and the processing method.

[0161] Receive business processing instructions from the business analysis party, and perform corresponding processing operations on the account of the first business participant according to the business processing instructions.

[0162] Optionally, the service acceptor includes a service accepting terminal and a service accepting server;

[0163] The first account information is sent by the feature collection terminal to the service acceptance terminal, so that the service acceptance terminal generates the service processing request based on the received first account information and uploads the service processing request to the service acceptance server.

[0164] Optionally, the service acceptor includes a service accepting server;

[0165] The first account information is used by the feature collection terminal to generate the business processing request, wherein the business processing request is uploaded by the feature collection terminal to the business acceptance server.

[0166] Optionally, the service acceptor includes a service accepting terminal; the service processing request includes second account information corresponding to the second service participant, and the account data corresponding to the second account information is maintained by the service accepting server, so that the service analyzer parses the received service processing request and generates a service processing instruction for the service accepting server, and the service accepting server uses the service processing instruction to perform corresponding processing operations on the account of the second service participant.

[0167] Optionally, the feature information is collected by the feature acquisition terminal in response to a received service trigger command.

[0168] Optionally, a set of feature information sent by the feature acquisition terminal is received. The set of feature information includes feature information of all objects collected by the feature acquisition terminal within the acquisition range before receiving the service triggering instruction, wherein the objects include the first service participant.

[0169] Converting the feature information into first account information corresponding to the first business participant and returning the first account information to the feature acquisition terminal includes: converting each feature information in the feature information set into corresponding account information and returning the account information to the feature acquisition terminal, so that the feature acquisition terminal locally caches the mapping relationship between feature information and account information, and the mapping relationship is used by the feature acquisition terminal to determine the first account information corresponding to the feature information of the first business participant after responding to the received business triggering instruction.

[0170] The systems, devices, modules, or units described in the above embodiments can be implemented by computer chips or entities, or by products with certain functions. A typical implementation device is a computer, which can take the form of a personal computer, laptop computer, cellular phone, camera phone, smartphone, personal digital assistant, media player, navigation device, email sending and receiving device, game console, tablet computer, wearable device, or any combination of these devices.

[0171] In a typical configuration, a computer includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.

[0172] Memory may include non-persistent storage in computer-readable media, such as random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash RAM. Memory is an example of computer-readable media.

[0173] Computer-readable media includes both permanent and non-permanent, removable and non-removable media that can store information using any method or technology. Information can be computer-readable instructions, data structures, modules of programs, 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 technologies, CD-ROM, digital versatile optical disc (DVD) or other optical storage, magnetic tape, magnetic magnetic disk storage or other magnetic storage devices, or any other non-transferable medium that can be used to store information accessible by a computing device. As defined herein, computer-readable media does not include transient computer-readable media, such as modulated data signals and carrier waves.

[0174] It should also be noted that the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0175] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numerals in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this specification. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this specification as detailed in the appended claims.

[0176] The terminology used in this specification is for the purpose of describing particular embodiments only and is not intended to be limiting of this specification. The singular forms “a,” “the,” and “the” as used in this specification and the appended claims are also intended to include the plural forms unless the context clearly indicates otherwise. It should also be understood that the term “and / or” as used herein refers to and includes any and all possible combinations of one or more of the associated listed items.

[0177] It should be understood that although the terms first, second, third, etc., may be used in this specification to describe various information, this information should not be limited to these terms. These terms are only used to distinguish information of the same type from one another. For example, without departing from the scope of this specification, first information may also be referred to as second information, and similarly, second information may also be referred to as first information. Depending on the context, the word "if" as used herein may be interpreted as "when," "when," or "in response to determination."

[0178] The above description is merely a preferred embodiment of this specification and is not intended to limit this specification. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this specification should be included within the scope of protection of this specification.

Claims

1. A business processing system, comprising: A feature acquisition terminal is used to acquire feature information of a first business participant and determine first account information corresponding to the feature information of the first business participant based on a locally cached mapping relationship. The feature information includes facial features. The mapping relationship is a mapping relationship between feature information and account information of all objects actively acquired by the feature acquisition terminal within the acquisition range. The account information is obtained by sending the acquired feature information to a business processing party, which then converts the feature information accordingly. The business processing party is used to convert the received feature information into first account information corresponding to the first business participant, and return the first account information to the feature collection terminal. The first account information is used to generate a business processing request. A service receiving party, which is used to transmit the service processing request to a service analysis party; A business analysis party is configured to parse the received business processing request and generate a business processing instruction for the business processing party. The business processing instruction includes the first account information and the processing method, so as to instruct the business processing party to perform corresponding processing operations on the account of the first business participant.

2. The system according to claim 1, wherein the service recipient comprises: A service acceptance terminal, which is connected to the feature collection terminal, is used to obtain the first account information from the feature collection terminal and generate the service processing request. The service acceptance server is used to receive the service processing request uploaded by the service acceptance terminal and send the service processing request to the service analysis party.

3. The system according to claim 2, wherein the service acceptance server is further configured to: The second account information of the second business participant is added to the business processing request. The account information of the second business participant is maintained by the business acceptance server.

4. In the system according to claim 2, the service acceptance terminal and the feature acquisition terminal are located in the same or different physical entities.

5. The system according to claim 1, wherein the feature acquisition terminal is further configured to generate the service processing request based on the first account information; The service-receiving party includes: The service acceptance server is used to receive the service processing request uploaded by the feature collection terminal and send the service processing request to the service analysis party.

6. The system according to claim 1, wherein the service acceptor includes a service accepting server; the service processing request includes second account information corresponding to the second service participant, and the account data corresponding to the second account information is maintained by the service accepting server; The business analysis party is also used to parse the received business processing request and generate a business processing instruction for the business acceptance server, so as to instruct the business acceptance server to perform corresponding processing operations on the account of the second business participant.

7. The system according to claim 1, wherein the service processing party is further configured to: After converting the received feature information into the first account information corresponding to the first business participant, account authentication is performed on the first account information to ensure the legitimacy of the first account information.

8. A business processing method applied to a feature acquisition terminal; the method includes: Feature collection is performed on the first business participant to generate feature information, and the first account information corresponding to the feature information of the first business participant is determined according to the mapping relationship cached locally; wherein, the feature information includes facial features; the mapping relationship is the mapping relationship between the feature information and account information of all objects entering the collection range actively collected by the feature collection terminal; the account information is obtained by sending the collected feature information to the business processing party, and the business processing party converting the feature information respectively; Based on the first account information returned by the business processing party, the operation of generating a business processing request from the first account information is performed; wherein, the business processing request is transmitted by the business receiving party to the business analysis party, so that the business analysis party parses and generates a business processing instruction for the business processing party, the business processing instruction includes the first account information and the processing method, so as to instruct the business processing party to perform corresponding processing operations on the account of the first business participant.

9. The method according to claim 8, wherein the service accepting party includes a service accepting terminal and a service accepting server; The operation of generating the first account information as a business processing request comprises: The first account information is sent to the service acceptance terminal, so that the service acceptance terminal generates the service processing request based on the first account information and uploads the service processing request to the service acceptance server.

10. The method according to claim 9, wherein the business processing request further includes the account information of the second business participant added by the business acceptance server, and the account information of the second business participant is maintained by the business acceptance server.

11. The method according to claim 9, wherein the service acceptance terminal and the feature acquisition terminal are located in the same or different physical entities.

12. The method according to claim 8, wherein the service acceptor includes a service accepting server; the operation of generating the first account information as a service processing request includes: The business processing request is generated based on the received first account information; The business processing request is uploaded to the business acceptance server.

13. The method according to claim 8, wherein the service acceptor includes a service accepting server; the service processing request includes second account information corresponding to the second service participant, the account data corresponding to the second account information is maintained by the service accepting server, so that the service analyzer parses the received service processing request and generates a service processing instruction for the service accepting server, the service processing instruction is used by the service accepting server to perform corresponding processing operations on the account of the second service participant.

14. The method according to claim 8, further comprising: After determining the first account information corresponding to the feature information of the first business participant based on the mapping relationship of the local cache, account authentication is performed on the first account information to ensure the legitimacy of the first account information.

15. An electronic device comprising: processor; Memory used to store processor-executable instructions; The processor implements the method as described in any one of claims 8-14 by executing the executable instructions.

16. A computer-readable storage medium having stored thereon computer instructions that, when executed by a processor, implement the steps of the method as claimed in any one of claims 8-14.