WO2019227607A1 - 路由化订单配置及处理方法、以及系统 - Google Patents

路由化订单配置及处理方法、以及系统 Download PDF

Info

Publication number
WO2019227607A1
WO2019227607A1 PCT/CN2018/095276 CN2018095276W WO2019227607A1 WO 2019227607 A1 WO2019227607 A1 WO 2019227607A1 CN 2018095276 W CN2018095276 W CN 2018095276W WO 2019227607 A1 WO2019227607 A1 WO 2019227607A1
Authority
WO
WIPO (PCT)
Prior art keywords
order
processing
queue
asynchronous
verification
Prior art date
Application number
PCT/CN2018/095276
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 WO2019227607A1 publication Critical patent/WO2019227607A1/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
    • G06Q30/00—Commerce
    • G06Q30/06—Buying, selling or leasing transactions
    • G06Q30/0601—Electronic shopping [e-shopping]
    • G06Q30/0633—Lists, e.g. purchase orders, compilation or processing
    • G06Q30/0635—Processing of requisition or of purchase orders
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/48—Program initiating; Program switching, e.g. by interrupt
    • G06F9/4806—Task transfer initiation or dispatching
    • G06F9/4843—Task transfer initiation or dispatching by program, e.g. task dispatcher, supervisor, operating system
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
    • G06F9/5005—Allocation of resources, e.g. of the central processing unit [CPU] to service a request
    • 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
    • G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
    • G06Q40/04—Trading; Exchange, e.g. stocks, commodities, derivatives or currency exchange
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02P—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN THE PRODUCTION OR PROCESSING OF GOODS
    • Y02P90/00—Enabling technologies with a potential contribution to greenhouse gas [GHG] emissions mitigation
    • Y02P90/30—Computing systems specially adapted for manufacturing

Definitions

  • the present application relates to the technical field of Internet services, and in particular, to a routing order configuration and processing method and system.
  • the traditional order process is a serial interactive process, that is, for the business request initiated by the client (professional company, or end user), the back-end management system (that is, the server) needs to process each process one by one according to the order process (Sub-process), after the processing is completed, the final processing result can be returned to the client that initiated the business request.
  • the experience is largely dependent on the time-consuming processing of business requests by the server. If the server performs business processing operations that take a very long time and / or are difficult to predict, then This will cause the client to wait forever, and the user does not know the length of the wait. For example, for some order services, the back-office management system may need to access a third party (for example, to query the status of product inventory) to obtain the required information in the processing process, and the response time of the third party is often difficult to accurately grasp. Therefore, if the server and client remain connected for a long time, a large amount of resources will be wasted and the throughput will be low.
  • a third party for example, to query the status of product inventory
  • the main purpose of this application is: for the convenience of users, unify the ordering interface, obtain different business processing processes through the scene parameters therein, and assemble the entire business processing logic, according to the business logic General / special process categories, as well as asynchronous / synchronous processing needs, complete all steps of the transaction order.
  • this application proposes a trading scenario modeling solution, which may include the following aspects:
  • the transaction scenario can be determined based on the parameters of the product provider, product code, primary channel, secondary channel, transaction type, payment method, order management platform, and payment rules in the routing parameters of the scenario;
  • the specific order processes the transaction according to the process, and feedbacks the processing situation to the client in real time.
  • a routing order configuration and processing method is provided, which is characterized by including the following steps:
  • Step 1 Receive an order execution request from a client, and extract scenario routing parameters of the order from the order execution request, where the scenario routing parameters include parameters related to the trading environment of the order;
  • Step 2 Determine the order processing scenario according to the scenario routing parameters, and assign a pre-configured process queue corresponding to the order processing scenario to the order, where the process queue includes processing the order All required processes, including normal processes and verification processes;
  • Step 3 Perform asynchronous judgment on the verification process in the process queue. If the verification process needs to be processed asynchronously, notify the client to wait for the order verification result to be returned, and return the order to the client after the asynchronous processing is completed. Test results,
  • synchronous processing is performed on the verification process, and the order verification result is returned directly to the client after the synchronization process is completed;
  • Step 4 If the verification result of the order received by the client is "verification succeeded", an ordinary process is extracted from the process queue to form an ordinary process queue, and then each of the ordinary process queues is processed in turn. Processes, and feed back the results of process processing to the client.
  • a routed order configuration and processing system for performing the method is provided, which is characterized by including an order acceptance component, an order verification component, an order processing component, an order feedback component, and a process asynchronous judgment.
  • the order acceptance component is configured to receive an order execution request from a client, and extract a scenario routing parameter of the order from the order execution request;
  • the order acceptance component is further configured to determine the order processing scenario according to the scenario routing parameters, and assign a pre-configured process queue corresponding to the order processing scenario to the order;
  • the order verification component is configured to perform an order verification according to a verification process in the process queue, generate an order verification result, and send the order verification result to an order processing component and an order feedback component.
  • the order feedback component is configured to feed back the order verification result and the process processing result to the client.
  • the order processing component is configured to extract an ordinary process from the process queue after the order verification is successful, form an ordinary process queue, and process each process in the ordinary process queue in turn;
  • the process asynchronous judgment component is used to execute the asynchronous judgment of the order process, including the asynchronous judgment of performing the verification process and the asynchronous judgment of the ordinary process.
  • a computer-readable storage medium characterized in that the computer-readable storage medium stores a program for executing a routing order configuration and processing method, and the program is executed by a processor When doing the following:
  • Step 1 Receive an order execution request from a client, and extract scenario routing parameters of the order from the order execution request, where the scenario routing parameters include parameters related to the trading environment of the order;
  • Step 2 Determine the order processing scenario according to the scenario routing parameters, and assign a pre-configured process queue corresponding to the order processing scenario to the order, where the process queue includes processing the order All required processes, including normal processes and verification processes;
  • Step 3 Perform asynchronous judgment on the verification process in the process queue. If the verification process needs to be processed asynchronously, notify the client to wait for the order verification result to be returned, and return the order to the client after the asynchronous processing is completed. Test results,
  • synchronous processing is performed on the verification process, and the order verification result is returned directly to the client after the synchronization process is completed;
  • Step 4 If the verification result of the order received by the client is "verification succeeded", an ordinary process is extracted from the process queue to form an ordinary process queue, and then each of the ordinary process queues is processed in turn. Processes, and feed back the results of process processing to the client.
  • the beneficial effects of this application mainly include: 1. Unified interfaces to various external professional companies; 2. Low system maintenance costs; 3. Pre-configuration of process queues enables manual labor to perform synchronous and asynchronous operations on the same scene. Free switching, and at the same time, the process queues of the same scene can be reused; 4. After the scene modeling, parameterized configuration can go online quickly; 5. Payment channels can be configured, which can be quickly based on the manual preset process. Handle business and solve the business needs of different professional companies in different scenarios.
  • FIG. 1 is a schematic flowchart of part of a routing order configuration and processing method according to an embodiment of the present application
  • FIG. 2 is a schematic flowchart of a part of a routing order configuration and processing method according to another embodiment of the present application
  • FIG. 3 is a functional architecture diagram of a routing order configuration and processing system according to an embodiment of the present application.
  • FIG. 4 is a schematic diagram of an operating environment of a system in which an application is installed according to an embodiment of the present application.
  • the scenario routing parameters of the order are obtained, and the different business processing processes (process configuration and process queue) that the order process should obtain according to its scenario routing parameters.
  • the order process is parameterized and configured, so that the processing method can be quickly applied online.
  • the business can be quickly processed according to the preset process manually, and the business of different scenarios for different professional companies can be solved. demand.
  • the process type parameter is set in the order process configuration to distinguish between ordinary processes and special processes.
  • processes that are not allowed to fail are manually set in advance (for example, verification-type processes). You can send an alarm email to the background and check by human intervention to reduce the failure rate of human error and improve the customer experience.
  • breakpoint reconnection can be achieved by recording the processes interrupted by processing and the processing details of each process.
  • FIG. 1 is a partial flowchart of a routing order process configuration and processing method according to an embodiment of the present application.
  • FIG. 2 is a schematic flowchart of part of a routing order process configuration and processing method according to another embodiment of the present application.
  • an embodiment of the present application provides a routed order configuration and processing method.
  • the process of processing an order includes the order verification, order asynchronous processing judgment, and order process processing.
  • the method include:
  • Step S100 Receive order information from a client, and extract scenario routing parameters of the order from the information;
  • the scenario routing parameters may include specific parameters such as a product provider, a product code, a primary channel, a secondary channel, a transaction type, a payment method, an order management platform, and a payment rule.
  • Different parameter combinations correspond to different order processing scenarios. , That is, the order processing scenario is jointly determined by multidimensional conditions;
  • Step S200 Determine the order processing scenario according to the scenario routing parameters, and assign a pre-configured process queue corresponding to the processing scenario to the order, where the process queue contains the required processing order. All processes, including ordinary processes and special processes, where the special processes include a check process;
  • the order processing scenario can be transformed into a multi-dimensional condition expression form by the scenario routing parameters, each dimension can involve a different processing process / process queue, and the combination of each dimension forms a complete process corresponding to the order processing scenario. , Which is represented by processing processes / process queues;
  • the ordinary process refers to the general process required to process the order, which can be executed synchronously or asynchronously.
  • the execution process and execution result do not affect the execution of other processes, and thus do not affect the processing of the entire order.
  • the processing results of each ordinary process for example, in the case that the processing time of a certain ordinary process may be longer, the ordinary process may be processed asynchronously, such as feedback to the client (or "front end” for short) Messages such as "xx process is being processed", the client users do not need to wait any longer, they only need to passively receive the processing completion message sent by the server, and at the same time, they can feedback to the client the synchronization processing of other common processes in real time;
  • the details of the process can be recorded. If the client then requests the execution of the same order, it can reconnect with a breakpoint, that is, resume processing from the ordinary process that failed to process, without repeating the previous process. Successful processes have been processed;
  • the special process refers to the prerequisite process required to process the order, for example, the verification process, that is, the special process determines the "legality" of the order itself, if the special process fails to execute successfully (for example, the verification fails) ,
  • Step S300 Perform an order verification according to the verification process in the process queue, and generate an order verification result. If the order verification result is "verification passed,” step S400 is performed; otherwise, return to "verification" "Failure” message, the method ends;
  • step S300 the verification process is judged asynchronously, wherein the verification process that needs to be asynchronously executed is added to the asynchronous queue, and "the order is being verified, please wait for notification" is returned to the client, and then asynchronous processing is performed. .
  • Step S400 after the verification succeeds or after the asynchronous processing is completed, extract a common process from the process queue to form a common process queue, and use the first process in the common process queue as the current process;
  • each process in the ordinary process queue can be processed in turn, and the processing status and result of the ordinary process can be generated and summarized.
  • the processing status and result of the ordinary process may include "in processing”, “successful processing", and "processing failure", and are fed back to the client.
  • step S400 the method may further perform the following steps:
  • Step S500 performing asynchronous judgment of the order process
  • the process parameters of the current process for example, the type of business involved in executing the current process, such as payment, query, etc.
  • Step S600 If the current process needs to be processed asynchronously, put the current process into an asynchronous queue, return a "xx process in progress" message to the client, and use the next process in the ordinary process queue as the current process. Return to step S500; otherwise, if it is necessary to perform synchronization processing on the current process, determine that the current process is a synchronization processing process, and execute step S700;
  • the asynchronous queue is maintained by a background management system.
  • the processes that require asynchronous processing are usually relatively time-consuming processes in the order processing process, and / or processes that rely on third-party responses.
  • their processing does not affect Processing of subsequent processes (synchronous processes or asynchronous processes), that is, the processing of subsequent processes (synchronous processes) does not depend on the processing results of the previous process;
  • the background management system can process the processes in the asynchronous queue by broadcasting, for example Process the processes in the asynchronous queue in a regular manner, and in the case where the third party is not responding to the asynchronous process or the processing timeout, the process is repeatedly processed in a loop.
  • calculating a reference time for processing the current process according to the estimated time spent processing the current process and network environment data carried in the current process
  • the network environment data includes: the network type of the currently used network, the network system and / or signal strength, and the network transmission speed of the currently used network;
  • the processing status information of the current process may also be generated, for example, if the current process is suspended for some reason, the status information may be generated and displayed as "xx process remains processing";
  • Step S800 If the current process is successfully processed and the current process is not the last process in the ordinary process queue, return to step S500 as the current process in the ordinary process queue, otherwise, if the current process fails to process , Return the "Order processing failed" message, and record the process processing related information (for future breakpoint reconnection), and end this method;
  • step S900 If the current process is successfully processed, and the current process is the last process in the ordinary process queue, proceed to step S900;
  • step S900 if all the synchronous processing processes are successfully processed, the client is notified of the processing status, for example, the client is notified that "all the synchronous processing processes have been processed, please wait for the processing result notification of the asynchronous processing process".
  • the partial synchronization processing process may be repeatedly performed according to the reason for the processing failure. For example, if the reason for the processing failure is that the third party is not responding or the response times out, the relevant process can be automatically executed in a loop, and the client is notified that "some synchronization processing processes are retrying, please wait".
  • a routed order process configuration and processing system is used to execute each step of the method in this application.
  • the routed order process configuration and processing system mainly includes orders. Acceptance component, order verification component, order processing component, order feedback component, process asynchronous judgment component.
  • the order acceptance component is configured to receive order information from a client, and extract scenario routing parameters of the order from the information;
  • the scenario routing parameters may include specific parameters such as a product provider, a product code, a primary channel, a secondary channel, a transaction type, a payment method, an order management platform, and a payment rule.
  • Different parameter combinations correspond to different order processing scenarios. That is, the order processing scenario is jointly determined by multi-dimensional conditions.
  • the order acceptance component is further configured to determine a processing scenario of the order according to the scenario routing parameters, and allocate a pre-configured process queue corresponding to the processing scenario to the order, and the process queue Contains all processes required to process the order, including ordinary processes and special processes, where the special processes include a verification process;
  • the order verification component is configured to perform an order verification according to a verification process in the process queue, generate an order verification result, and send the order verification result to an order processing component and an order feedback component.
  • the order feedback component is used to feedback the order verification result to the client.
  • the order processing component is configured to extract an ordinary process from the process queue after the order verification is successful, form an ordinary process queue, and use the first process in the ordinary process queue as the current process;
  • the process asynchronous judgment component is used to execute the asynchronous judgment of the order process, including the asynchronous judgment of performing the verification process and the asynchronous judgment of the ordinary process.
  • the order processing component is further configured to: when the current process needs to be processed asynchronously, put the current process into an asynchronous queue, return the "xx process processing" message to the client through the order feedback component, and send all The next process in the ordinary process queue is referred to as the current process;
  • the order processing component is further configured to: if the current process needs to be processed synchronously, execute the corresponding processing to generate the processing result of the current process, and feed back the processing result to the client through the order feedback component;
  • the order processing component is further configured to sequentially execute all processes in the ordinary process queue and record process processing related information.
  • different embodiments of the present application may also be implemented by means of software modules or computer-readable instructions stored on one or more computer-readable media, where the computer-readable instructions are used as processors or device components. When executed, the different embodiments described in this application are executed. Similarly, any combination of software modules, computer-readable media, and hardware components is contemplated by this application.
  • the software module may be stored on any type of computer-readable storage medium, such as RAM, EPROM, EEPROM, flash memory, registers, hard disk, CD-ROM, DVD, and so on.
  • FIG. 4 a running environment of a system in which an application is installed according to an embodiment of the present application is shown.
  • the system for installing an application program is installed and run in an electronic device.
  • the electronic device may be a computing device such as a desktop computer, a notebook, a palmtop computer, and a server.
  • the electronic device may include, but is not limited to, a memory, a processor, and a display.
  • FIG. 4 only shows the electronic device having the above components, but it should be understood that it is not required to implement all the illustrated components, and more or fewer components may be implemented instead.
  • the memory may be an internal storage unit of the electronic device in some embodiments, such as a hard disk or a memory of the electronic device. In other embodiments, the memory may also be an external storage device of the electronic device, such as a plug-in hard disk, a Smart Memory Card (SMC), and a Secure Digital , SD) card, Flash card, etc. Further, the memory may include both an internal storage unit and an external storage device of the electronic device.
  • the memory is used to store application software and various types of data installed on the electronic device, such as program code of the system in which the application program is installed. The memory may also be used to temporarily store data that has been or will be output.
  • the processor may be a central processing unit (CPU), a microprocessor, or other data processing chip, and is configured to run program code or process data stored in the memory, for example, to execute the processor.
  • CPU central processing unit
  • microprocessor microprocessor
  • the processor may be a central processing unit (CPU), a microprocessor, or other data processing chip, and is configured to run program code or process data stored in the memory, for example, to execute the processor.
  • the display may be an LED display, a liquid crystal display, a touch-type liquid crystal display, an OLED (Organic Light-Emitting Diode) touch device, or the like.
  • the display is used to display information processed in the electronic device and to display a visualized client interface, such as an application menu interface, an application icon interface, and the like.
  • the components of the electronic device communicate with each other through a system bus.
  • the methods in the above embodiments can be implemented by means of software plus a necessary universal hardware platform, and of course, can also be implemented by hardware, but in many cases The former is a better implementation.
  • the technical solution of the present application in essence, or a part that contributes to the existing technology, can be embodied in the form of a software product, which is stored in a storage medium (such as ROM / RAM, magnetic disk, The optical disc) includes several instructions for causing a terminal device (which may be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) to execute the methods described in the embodiments of the present application.
  • a terminal device which may be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.
  • a computer-readable storage medium stores a program for executing the method according to the embodiment of the present application.
  • the program When executed by a processor, execute the steps of the method according to the embodiments of the present application.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Business, Economics & Management (AREA)
  • Finance (AREA)
  • General Physics & Mathematics (AREA)
  • Physics & Mathematics (AREA)
  • Accounting & Taxation (AREA)
  • Software Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Development Economics (AREA)
  • Economics (AREA)
  • Marketing (AREA)
  • Strategic Management (AREA)
  • General Business, Economics & Management (AREA)
  • Technology Law (AREA)
  • Computer And Data Communications (AREA)

Abstract

本申请涉及一种路由化订单配置及处理方法和系统，该方法包括以下步骤：步骤1、从客户端接收订单执行请求，从订单执行请求中提取订单的场景路由参数；步骤2、根据场景路由参数，确定订单处理场景，并将预先配置好的与订单处理场景相对应的进程队列分配给订单；步骤3、对校验进程进行异步判断并根据判断结果执行校验进程；步骤4、若校验成功，则依次处理普通进程队列中的每个进程，并向客户端反馈进程处理结果。根据本公开，通过对进程队列的事先配置，使得以对同一场景是否进行同步异步进行自由切换、并可以进行复用，有利于快速处理业务，解决不同接入方的不同业务需求。

Description

路由化订单配置及处理方法、以及系统
本申请申明享有2018年5月30日递交的申请号为201810537984.5、名称为“路由化订单配置及处理方法、以及系统”的中国专利申请的优先权，该中国专利申请的整体内容以参考的方式结合在本申请中。
技术领域
本申请涉及互联网服务技术领域，尤其涉及一种路由化订单配置及处理方法、以及系统。
背景技术
随着科学技术的发展，人们生活水平的逐步提高，网络已经在社会生活中广泛应用，其中，交易的多样化使得后台管理系统所对接的专业公司(商家)各不相同，每个专业公司所处理的业务亦不相同。市面上很多程序处理交易类流程时对外提供接口比较多，接口多就意味着对接成本和维护成本都变得复杂。
传统的订单流程处理方式是串行的交互过程，即：针对客户端(专业公司、或者最终用户)发起的业务请求，后台管理系统(即，服务端)需要根据订单流程而逐一处理每个进程(子流程)，处理完毕之后，才能够将最终处理结果返回到发起业务请求的客户端。
因此，对于客户端用户来说，其体验很大程度上依赖于服务端对业务请求的处理耗时情况，如果服务端执行耗时非常长和/或耗时难以预估的业务处理操作，那么就会导致客户端一直处于等待状态，而用户并不清楚等待的时长。例如：对于某些订单业务，后台管理系统可能需要再接入第三方(例如，查询商品库存状况)而获得处理流程中的所需信息，而第三方的响应时间往往难以精确掌握。因此，如果服务端与客户端长时间的保持连接状态， 会导致大量的资源被浪费，吞吐能力很低。
由此可见，在后台管理系统对接多个专业公司(商家)的情况下，由于每个专业公司处理的业务并不相同、所涉及的第三方(甚至还有更多参与方)，在这些不同的业务场景中，存在基于交易路由场景理念来解决不同专业公司不同场景的业务需求，以便克服服务端处理效率低、用户等待时间长的问题。
发明内容
考虑到现有技术的上述问题，本申请的主要目的在于：为了方便用户，实现下单接口统一化，通过其中的场景参数获取不同的业务处理流程，组装整个业务处理逻辑，根据业务逻辑中的普通类/特殊类的进程类别、以及异步/同步的处理需要，完成交易订单的所有步骤。
具体地，本申请提出了交易场景建模方案，可包括以下方面：
1、根据场景路由参数中的商品提供方、商品编码、一级渠道、二级渠道、交易类型、支付方式、订单管理平台、支付规则等参数，可确定交易场景；
2、根据确定的场景，获取在该场景下已预先配置的订单预处理功能和通道功能；
3、对于特定订单，根据订单预处理功能和通道功能，组装成一个完整的交易处理流程，即，进一步确定处理进程组合；
4、特定订单根据所述流程处理交易，实时向客户端反馈处理情况。
根据本申请的实施例，提供了一种路由化订单配置及处理方法，其特征在于包括以下步骤：
步骤1、从客户端接收订单执行请求，从所述订单执行请求中提取所述订单的场景路由参数，其中，所述场景路由参数包括与所述订单的交易环境相关的参数；
步骤2、根据所述场景路由参数，确定所述订单处理场景，并将预先配置好的与所述订单处理场景相对应的进程队列分配给所述订单，所述进程队列中包含处理所述订单所需的全部进程，包括普通进程和校验进程；
步骤3、对所述进程队列中的校验进程进行异步判断，若对校验进程需要执行异步处理，则通知客户端等待返回订单校验结果、并在异步处理结束后向客户端返回订单校验结果，
若对校验进程无需执行异步处理，则对校验进程执行同步处理，在同步处理结束后直接向客户端返回订单校验结果；
步骤4、若客户端接收到的所述订单校验结果为“校验成功”，则从所述进程队列中提取普通进程，形成普通进程队列，之后，依次处理所述普通进程队列中的每个进程，并向客户端反馈进程处理结果。
根据本申请的实施例，提供了一种用于执行所述方法的路由化订单配置及处理系统，其特征在于包括订单受理组件、订单校验组件、订单处理组件、订单反馈组件、进程异步判断组件，
其中，所述订单受理组件用于从客户端接收订单执行请求，从所述订单执行请求中提取所述订单的场景路由参数；
所述订单受理组件还用于根据所述场景路由参数，确定所述订单处理场景，并将预先配置好的与所述订单处理场景相对应的进程队列分配给所述订单；
其中，所述订单校验组件用于根据所述进程队列中的校验进程，执行订单校验，并生成订单校验结果，将订单校验结果发送到订单处理组件、以及订单反馈组件。
其中，所述订单反馈组件用于将订单校验结果、以及进程处理结果反馈给客户端，
其中，所述订单处理组件用于在订单校验成功之后，从所述进程队列中提取普通进程，形成普通进程队列，并依次处理所述普通进程队列中的每个 进程；
其中，所述进程异步判断组件用于执行订单进程的异步判断，包括执行所述校验进程的异步判断、以及所述普通进程的异步判断。
根据本申请的实施例，提供了一种计算机可读存储介质，其特征在于，所述计算机可读存储介质上存储有用于执行路由化订单配置及处理方法的程序，所述程序被处理器执行时，执行以下步骤的操作：
步骤1、从客户端接收订单执行请求，从所述订单执行请求中提取所述订单的场景路由参数，其中，所述场景路由参数包括与所述订单的交易环境相关的参数；
步骤2、根据所述场景路由参数，确定所述订单处理场景，并将预先配置好的与所述订单处理场景相对应的进程队列分配给所述订单，所述进程队列中包含处理所述订单所需的全部进程，包括普通进程和校验进程；
步骤3、对所述进程队列中的校验进程进行异步判断，若对校验进程需要执行异步处理，则通知客户端等待返回订单校验结果、并在异步处理结束后向客户端返回订单校验结果，
若对校验进程无需执行异步处理，则对校验进程执行同步处理，在同步处理结束后直接向客户端返回订单校验结果；
步骤4、若客户端接收到的所述订单校验结果为“校验成功”，则从所述进程队列中提取普通进程，形成普通进程队列，之后，依次处理所述普通进程队列中的每个进程，并向客户端反馈进程处理结果。
本申请的有益效果主要在于：1、对外部的各个专业公司可以统一接口；2、系统的维护成本较低；3、通过对进程队列的事先配置，使得人工可以对同一场景是否进行同步异步进行自由切换，同时，同一个场景的进程队列可以进行复用；4、场景建模后，经过参数化配置能够快速上线；5、支付通道可配置化，可以根据人工事先预设好的流程，快速处理业务，解决不同专业公司不同场景的业务需求。
附图说明
图1为根据本申请的一个实施例的路由化订单配置及处理方法的部分流程示意图；
图2为根据本申请的另一个实施例的路由化订单配置及处理方法的部分流程示意图；
图3为根据本申请的实施例的路由化订单配置及处理系统的功能架构示意图；
图4为根据本申请实施例的安装了应用程序的系统的运行环境的示意图。
具体实施方式
下面，结合附图对技术方案的实施作进一步的详细描述。
本领域的技术人员能够理解，尽管以下的说明涉及到有关本申请的实施例的很多技术细节，但这仅为用来说明本申请的原理的示例、而不意味着任何限制。本申请能够适用于不同于以下例举的技术细节之外的场合，只要它们不背离本申请的原理和精神即可。
另外，为了避免使本说明书的描述限于冗繁，在本说明书中的描述中，可能对可在现有技术资料中获得的部分技术细节进行了省略、简化、变通等处理，这对于本领域的技术人员来说是可以理解的，并且这不会影响本说明书的公开充分性。
下文中，将描述用于进行本申请的实施例。注意，将以下面的次序给出描述：1、发明构思的概要；2、路由化订单流程配置及处理方法(图1和2)；3、路由化订单流程配置及处理系统(图3)；4、根据本申请的实施例的安装了应用程序的系统、以及存储所述应用程序的计算机可读介质(图4)。
1、发明构思的概要
本申请的构思要点在于：
1、在订单受理时，通过获取订单的场景路由参数，根据其场景路由参数判断订单流程所应获取的不同业务处理流程(流程配置以及进程队列)。通过前述场景建模以及订单场景路由化，使得订单流程参数化配置，使得处理方法能够快速上线应用；同时，可以根据人工事先预设好的流程，快速处理业务，解决不同专业公司不同场景的业务需求。
2、通过对进程队列的事先配置，使得人工可以对同一场景是否进行同步异步进行自由切换，同时，同一个场景的进程队列可以进行复用。
3、通过在订单流程配置中，设置进程类型参数，来区分普通进程和特殊的进程，对于特殊进程来说，是由人工预先设置好不允许失败的进程(例如，校验类进程)，该进程可通过向后台发出告警邮件，由人工介入查看，降低人为失误的失败率，提升客户体验。
4、在订单处理未成功的情况下，通过记录处理所中断的进程、以及每个进程的处理细节，可以实现断点重连。
2、路由化订单流程配置及处理方法
图1为根据本申请的一实施例的路由化订单流程配置及处理方法的部分流程示意图。图2为根据本申请的另一实施例的路由化订单流程配置及处理方法的部分流程示意图。
如图1所示，本申请的实施例提供了一种路由化订单配置及处理方法，其中，处理订单的过程包括订单校验、订单异步处理判断以及订单进程处理这几个阶段，所述方法包括：
步骤S100、从客户端接收订单的信息，从该信息中提取所述订单的场景路由参数；
其中，所述场景路由参数可包括商品提供方、商品编码、一级渠道、二级渠道、交易类型、支付方式、订单管理平台以及支付规则等具体参数，不同的参数组合对应不同的订单处理场景，即，订单处理场景是由多维条件共 同决定的；
步骤S200、根据所述场景路由参数，确定所述订单处理场景，并将预先配置好的与处理场景相对应的进程队列分配给所述订单，所述进程队列中包含处理所述订单所需的全部进程，包括普通进程和特殊进程，其中，所述特殊进程包括校验进程；
其中，所述订单处理场景可由所述场景路由参数转换为多维条件的表达形式，每个维度都可以涉及不同的处理进程/进程队列，各个维度的组合形成所述订单处理场景所对应的完整流程，其通过处理进程/进程队列来表示；
其中，普通进程指的是处理订单所需的一般进程，其可以同步或者异步执行，其执行过程和执行结果并不影响其它进程的执行、进而也不影响整个订单的处理，因此，可以分别得到各个普通进程的处理结果，例如，在某个/某些普通进程的处理时间可能较久的情况下，可对该普通进程采用异步处理方式，例如向客户端(或简称为“前端”)反馈“xx进程正在处理中”之类的消息，客户端的用户无需继续等待，只需被动接收服务端发送的处理完成的消息即可，同时，可以实时向客户端反馈其他普通进程的同步处理情况；
此外，对于处理失败的普通进程，可记录其处理细节，之后如果客户端再请求同一订单的执行，可以断点重连，即，从处理失败的普通进程处恢复处理，而无需再重复进行之前已经处理成功的进程；
相对应地，特殊进程指的是处理订单所需的先决进程，例如，校验进程，即，特殊进程确定订单本身的“合法性”，如果特殊进程未能执行成功(例如，校验失败)，则服务端的订单处理流程即刻终止，客户端收到“订单处理失败”之类的消息，之后，如果需要再次请求同一订单的执行，则特殊进程必须重新进行；
步骤S300、根据所述进程队列中的校验进程，执行订单校验，并生成订单校验结果，若所述订单校验结果为“校验通过”，则执行步骤S400；否则返回“校验失败”信息，结束本方法；
可选地，在步骤S300中，进行校验进程异步判断，其中，将需要异步执行的校验进程加入异步队列，并向客户端反馈“订单校验中，请等待通知”，之后进行异步处理。
步骤S400、在校验成功、或者所述异步处理完成之后，从所述进程队列中提取普通进程，形成普通进程队列，将所述普通进程队列中的首个进程作为当前进程；
之后，可依次处理普通进程队列中的每个进程，并生成、汇总普通进程的处理状态和结果。例如，所述普通进程的处理状态和结果可包括“处理中”、“处理成功”、“处理失败”，并被反馈到客户端。
可选地，作为步骤S400的替代，所述方法还可执行以下步骤：
步骤S500，进行订单进程异步判断；
具体地，根据当前进程的进程参数(例如，执行当前进程所涉及的业务类型，如支付、查询等)，判断是否需要对当前进程进行异步处理，如需异步处理，则客户端不能即时获得订单的处理结果，相应地，在正常情况下，对当前进程进行同步处理，客户端可以即时获得订单的处理结果；
步骤S600、若需要对当前进程进行异步处理，则将所述当前进程放入异步队列，向客户端返回“xx进程处理中”消息，并将所述普通进程队列中下一进程作为当前进程，返回到步骤S500；否则，若需要对当前进程进行同步处理，判断所述当前进程为同步处理进程，执行步骤S700；
其中，所述异步队列由后台管理系统维护，需要异步处理的进程通常是订单处理进程中相对耗时的进程、和/或依赖于第三方响应的进程；同时，作为示例，其处理并不影响后续进程(同步进程或者异步进程)的处理，也就是说，后续进程(同步进程)的处理并不依赖于前一进程的处理结果；后台管理系统可通过广播方式处理异步队列中的进程，例如，以定期方式处理异步队列中的进程，在第三方对异步进程无响应或处理超时的情况下，循环重复处理所述进程。
作为示例，可通过判断所述当前进程中是否携带了请求异步处理的标识、或通过判断所述当前进程涉及的第三方/业务操作是否被标识为需要采用异步处理方式、或通过判断与所述当前进程对应的业务处理耗时参考值，来判断所述当前进程是否需要进行异步处理；
可选地，根据与所述当前进程相对应的业务处理耗时参考值，估算处理所述当前进程的耗时；
可选地，根据估算的处理所述当前进程的耗时、以及所述当前进程中携带的网络环境数据，计算处理所述当前进程的参考时间；
作为示例，所述网络环境数据包括：当前所用网络的网络类型、网络制式和/或信号强度、当前所用网络的网络传输速度；
步骤S700、对于同步处理进程(当前进程)，执行相应处理，生成当前进程的处理结果；
其中，在执行相应处理的过程中，还可生成所述当前进程的处理状态信息，例如，如果当前进程因为某种原因被挂起，可生成并显示状态信息为“xx进程保持处理中”；
另一方面，如果当前进程处理结束，则生成并显示状态信息为“xx进程处理成功”、或者“xx进程处理失败”；
步骤S800、如果当前进程处理成功、且当前进程不是所述普通进程队列中的最后一个进程，将所述普通进程队列中下一进程作为当前进程，返回到步骤S500，否则，如果当前进程处理失败，返回“订单处理失败”消息，并记录进程处理相关信息(以用于将来的断点重连)，结束本方法；
如果当前进程处理成功、且当前进程是所述普通进程队列中的最后一个进程，则前进到步骤S900；
步骤S900、如果全部同步处理进程均处理成功，则向客户端通知处理情况，例如，向客户端通知“全部同步处理进程已处理完毕、请等待异步处理进程的处理结果通知”。
可选地，如果部分同步处理进程处理失败，则可根据处理失败原因，重复执行部分同步处理进程。例如，如果处理失败原因是第三方无响应或响应超时，则可自动循环执行相关的进程，并向客户端通知“部分同步处理进程正在重试，请等待”。
3、路由化订单流程配置及处理系统
根据本申请的实施例，一种路由化订单流程配置及处理系统用于执行本申请中的所述方法的各个步骤，如图3所示，所述路由化订单流程配置及处理系统主要包括订单受理组件、订单校验组件、订单处理组件、订单反馈组件、进程异步判断组件。
其中，所述订单受理组件用于从客户端接收订单的信息，从该信息中提取所述订单的场景路由参数；
其中，所述场景路由参数可包括商品提供方、商品编码、一级渠道、二级渠道、交易类型、支付方式、订单管理平台以及支付规则等具体参数，不同的参数组合对应不同的订单处理场景，即，订单处理场景是由多维条件共同决定的。
所述订单受理组件还用于根据所述场景路由参数，确定所述订单的处理场景，并将预先配置好的与所述处理场景相对应的进程队列分配给所述订单，所述进程队列中包含处理所述订单所需的全部进程，包括普通进程和特殊进程，其中，所述特殊进程包括校验进程；
其中，所述订单校验组件用于根据所述进程队列中的校验进程，执行订单校验，并生成订单校验结果，将订单校验结果发送到订单处理组件、以及订单反馈组件。
订单反馈组件用于将订单校验结果反馈给客户端。
其中，所述订单处理组件用于在订单校验成功之后，从所述进程队列中提取普通进程，形成普通进程队列，将所述普通进程队列中的首个进程作为 当前进程；
其中，所述进程异步判断组件用于执行订单进程异步判断，包括执行所述校验进程的异步判断、以及所述普通进程的异步判断。
其中，所述订单处理组件还用于：在需要对当前进程进行异步处理时，将所述当前进程放入异步队列，通过订单反馈组件向客户端返回“xx进程处理中”消息，并将所述普通进程队列中下一进程作为当前进程；
其中，所述订单处理组件还用于：若需要对当前进程进行同步处理，执行相应处理，生成当前进程的处理结果，并通过订单反馈组件向客户端反馈处理结果；
其中，所述订单处理组件还用于：依次执行所述普通进程队列中的全部进程，并记录进程处理相关信息。
此外，本申请的不同实施例也可以通过软件模块或存储在一个或多个计算机可读介质上的计算机可读指令的方式实现，其中，所述计算机可读指令是当被处理器或设备组件执行时，执行本申请所述的不同的实施例。类似地，软件模块、计算机可读介质和硬件部件的任意组合都是本申请预期的。所述软件模块可以被存储在任意类型的计算机可读存储介质上，例如RAM、EPROM、EEPROM、闪存、寄存器、硬盘、CD-ROM、DVD等等。
4、根据本申请的实施例的安装了应用程序的系统
参照图4，其示出了根据本申请实施例的安装了应用程序的系统的运行环境。
在本实施例中，所述的安装应用程序的系统安装并运行于电子装置中。所述电子装置可以是桌上型计算机、笔记本、掌上电脑及服务器等计算设备。该电子装置可包括但不限于存储器、处理器及显示器。图4仅示出了具有上述组件的电子装置，但是应理解的是，并不要求实施所有示出的组件，可以替代的实施更多或者更少的组件。
所述存储器在一些实施例中可以是所述电子装置的内部存储单元，例如 该电子装置的硬盘或内存。所述存储器在另一些实施例中也可以是所述电子装置的外部存储设备，例如所述电子装置上配备的插接式硬盘，智能存储卡(Smart Media Card，SMC)，安全数字(Secure Digital，SD)卡，闪存卡(Flash Card)等。进一步地，所述存储器还可以既包括所述电子装置的内部存储单元也包括外部存储设备。所述存储器用于存储安装于所述电子装置的应用软件及各类数据，例如所述安装应用程序的系统的程序代码等。所述存储器还可以用于暂时地存储已经输出或者将要输出的数据。
所述处理器在一些实施例中可以是中央处理单元(Central Processing Unit，CPU)、微处理器或其他数据处理芯片，用于运行所述存储器中存储的程序代码或处理数据，例如执行所述安装应用程序的系统等。
所述显示器在一些实施例中可以是LED显示器、液晶显示器、触控式液晶显示器以及OLED(Organic Light-Emitting Diode，有机发光二极管)触摸器等。所述显示器用于显示在所述电子装置中处理的信息以及用于显示可视化的客户界面，例如应用菜单界面、应用图标界面等。所述电子装置的部件通过系统总线相互通信。
通过以上的实施方式的描述，本领域的技术人员可以清楚地了解，上述实施方式中的方法可借助软件加必需的通用硬件平台的方式来实现，当然也可以通过硬件来实现，但很多情况下前者是更佳的实施方式。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分可以以软件商品的形式体现出来，该计算机软件商品存储在一个存储介质(如ROM/RAM、磁碟、光盘)中，包括若干指令用以使得一台终端设备(可以是手机，计算机，服务器，空调器，或者网络设备等)执行本申请各个实施例所述的方法。
也就是说，根据本申请的实施例，还提供了一种计算机可读存储介质，所述计算机可读存储介质上存储有用于执行根据本申请的实施例所述的方法的程序，所述程序被处理器执行时，执行根据本申请的实施例所述的方法的步骤。
由上，将理解，为了说明的目的，这里已描述了本申请的具体实施例，但是，可作出各个修改，而不会背离本申请的范围。本领域的技术人员将理解，流程图步骤中所绘出或这里描述的操作和例程可以多种方式变化。更具体地，可重新安排步骤的次序，可并行执行步骤，可省略步骤，可包括其它步骤，可作出例程的各种组合或省略。因而，本申请仅由所附权利要求限制。

Claims (20)

  1. 一种路由化订单配置及处理方法，其特征在于包括以下步骤：
    步骤1、从客户端接收订单执行请求，从所述订单执行请求中提取所述订单的场景路由参数，其中，所述场景路由参数包括与所述订单的交易环境相关的参数；
    步骤2、根据所述场景路由参数，确定所述订单处理场景，并将预先配置好的与所述订单处理场景相对应的进程队列分配给所述订单，所述进程队列中包含处理所述订单所需的全部进程，包括普通进程和校验进程；
    步骤3、对所述进程队列中的校验进程进行异步判断，若需要对校验进程执行异步处理，则通知客户端等待返回订单校验结果、并在异步处理结束后向客户端返回订单校验结果，
    若无需对校验进程执行异步处理，则对校验进程执行同步处理，在同步处理结束后直接向客户端返回订单校验结果；
    步骤4、若所述订单校验结果为“校验成功”，则从所述进程队列中提取普通进程，形成普通进程队列，之后，依次处理所述普通进程队列中的每个进程，并向客户端反馈进程处理结果。
  2. 根据权利要求1所述的路由化订单配置及处理方法，其特征在于，所述场景路由参数包括所述订单的商品提供方、商品编码、一级渠道、二级渠道、交易类型、支付方式、订单管理平台以及支付规则，其中，不同的参数组合对应不同的订单处理场景。
  3. 根据权利要求1所述的路由化订单配置及处理方法，其特征在于，所述步骤4包括：
    步骤4-1、对所述普通进程队列中的当前进程进行异步判断；
    步骤4-2、若需要对当前进程执行异步处理，则将所述当前进程放入异步队列，通知客户端“当前进程正在处理中”，并将所述普通进程队列中的 下一进程作为当前进程，返回到步骤4-1；
    步骤4-3、对当前进程执行同步处理，如果当前进程不是所述普通进程队列中的最后一个进程，则在同步处理结束后将所述普通进程队列中的下一进程作为当前进程，返回到步骤4-1；
    步骤4-4、向客户端汇总所述普通进程队列中的每个进程的处理结果。
  4. 根据权利要求1所述的路由化订单配置及处理方法，其特征在于，在步骤3中，根据所述校验进程是否需要与第三方交互，来判断对所述校验进程是否需要执行异步处理。
  5. 根据权利要求3所述的路由化订单配置及处理方法，其特征在于，在步骤4-1中，根据所述当前进程中是否带有请求异步处理的标识，来判断对所述当前进程是否需要执行异步处理。
  6. 根据权利要求3所述的路由化订单配置及处理方法，其特征在于，在步骤4-1中，根据所述当前进程对应的业务处理耗时的参考值，来判断所述当前进程是否需要进行异步处理。
  7. 根据权利要求3所述的路由化订单配置及处理方法，其特征在于，在步骤4-2中，通过广播方式启动异步队列中的进程，并且，在所述异步队列中的进程执行失败的情况下，按照预定重复周期和重复次数，重复执行所述异步队列中的进程。
  8. 根据权利要求3所述的路由化订单配置及处理方法，其特征在于，在步骤4-4之后，再次从客户端接收订单执行请求，从之前未执行成功的普通进程起恢复执行各个进程。
  9. 一种用于执行路由化订单配置及处理方法的路由化订单配置及处理系统，其特征在于包括订单受理组件、订单校验组件、订单处理组件、订单反馈组件、进程异步判断组件，
    其中，所述订单受理组件用于从客户端接收订单执行请求，从所述订单执行请求中提取所述订单的场景路由参数；
    所述订单受理组件还用于根据所述场景路由参数，确定所述订单处理场景，并将预先配置好的与所述订单处理场景相对应的进程队列分配给所述订单；
    其中，所述订单校验组件用于根据所述进程队列中的校验进程，执行订单校验，并生成订单校验结果，将订单校验结果发送到订单处理组件、以及订单反馈组件，
    其中，所述订单反馈组件用于将订单校验结果、以及进程处理结果反馈给客户端，
    其中，所述订单处理组件用于在订单校验成功之后，从所述进程队列中提取普通进程，形成普通进程队列，并依次处理所述普通进程队列中的每个进程；
    其中，所述进程异步判断组件用于执行订单进程的异步判断，包括执行所述校验进程的异步判断、以及所述普通进程的异步判断。
  10. 根据权利要求9所述的路由化订单配置及处理系统，其特征在于，所述订单处理组件还用于：在需要对当前进程进行异步处理时，将所述当前进程放入异步队列，通过订单反馈组件向客户端返回“xx进程处理中”消息，并将所述普通进程队列中下一进程作为当前进程。
  11. 根据权利要求9所述的路由化订单配置及处理系统，其特征在于，所述订单处理组件还用于：若需要对当前进程进行同步处理，执行相应处理，生成当前进程的处理结果，并通过订单反馈组件向客户端反馈处理结果；
  12. 根据权利要求9所述的路由化订单配置及处理系统，其特征在于，所述订单处理组件还用于：依次执行所述普通进程队列中的全部进程，并记录进程处理相关信息。
  13. 一种计算机可读存储介质，其特征在于，所述计算机可读存储介质上存储有用于执行路由化订单配置及处理方法的程序，所述程序被处理器执行时，执行以下步骤的操作：
    步骤1、从客户端接收订单执行请求，从所述订单执行请求中提取所述订单的场景路由参数，其中，所述场景路由参数包括与所述订单的交易环境相关的参数；
    步骤2、根据所述场景路由参数，确定所述订单处理场景，并将预先配置好的与所述订单处理场景相对应的进程队列分配给所述订单，所述进程队列中包含处理所述订单所需的全部进程，包括普通进程和校验进程；
    步骤3、对所述进程队列中的校验进程进行异步判断，若需要对校验进程执行异步处理，则通知客户端等待返回订单校验结果、并在异步处理结束后向客户端返回订单校验结果，
    若无需对校验进程执行异步处理，则对校验进程执行同步处理，在同步处理结束后直接向客户端返回订单校验结果；
    步骤4、若所述订单校验结果为“校验成功”，则从所述进程队列中提取普通进程，形成普通进程队列，之后，依次处理所述普通进程队列中的每个进程，并向客户端反馈进程处理结果。
  14. 根据权利要求13所述的计算机可读存储介质，其特征在于，所述场景路由参数包括所述订单的商品提供方、商品编码、一级渠道、二级渠道、交易类型、支付方式、订单管理平台以及支付规则，其中，不同的参数组合对应不同的订单处理场景。
  15. 根据权利要求13所述的计算机可读存储介质，其特征在于，所述步骤4包括：
    步骤4-1、对所述普通进程队列中的当前进程进行异步判断；
    步骤4-2、若需要对当前进程执行异步处理，则将所述当前进程放入异步队列，通知客户端“当前进程正在处理中”，并将所述普通进程队列中的下一进程作为当前进程，返回到步骤4-1；
    步骤4-3、对当前进程执行同步处理，如果当前进程不是所述普通进程队列中的最后一个进程，则在同步处理结束后将所述普通进程队列中的下一 进程作为当前进程，返回到步骤4-1；
    步骤4-4、向客户端汇总所述普通进程队列中的每个进程的处理结果。
  16. 根据权利要求13所述的计算机可读存储介质，其特征在于，在步骤3中，根据所述校验进程是否需要与第三方交互，来判断对所述校验进程是否需要执行异步处理。
  17. 根据权利要求15所述的计算机可读存储介质，其特征在于，在步骤4-1中，根据所述当前进程中是否带有请求异步处理的标识，来判断对所述当前进程是否需要执行异步处理。
  18. 根据权利要求15所述的计算机可读存储介质，其特征在于，在步骤4-1中，根据所述当前进程对应的业务处理耗时的参考值，来判断所述当前进程是否需要进行异步处理。
  19. 根据权利要求15所述的计算机可读存储介质，其特征在于，在步骤4-2中，通过广播方式启动异步队列中的进程，并且，在所述异步队列中的进程执行失败的情况下，按照预定重复周期和重复次数，重复执行所述异步队列中的进程。
  20. 根据权利要求15所述的计算机可读存储介质，其特征在于，在步骤4-4之后，再次从客户端接收订单执行请求，从之前未执行成功的普通进程起恢复执行各个进程。
PCT/CN2018/095276 2018-05-30 2018-07-11 路由化订单配置及处理方法、以及系统 WO2019227607A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201810537984.5 2018-05-30
CN201810537984.5A CN108765083B (zh) 2018-05-30 2018-05-30 路由化订单配置及处理方法、以及系统

Publications (1)

Publication Number Publication Date
WO2019227607A1 true WO2019227607A1 (zh) 2019-12-05

Family

ID=64004228

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/095276 WO2019227607A1 (zh) 2018-05-30 2018-07-11 路由化订单配置及处理方法、以及系统

Country Status (2)

Country Link
CN (1) CN108765083B (zh)
WO (1) WO2019227607A1 (zh)

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112686720B (zh) * 2019-10-17 2024-03-19 中国移动通信集团浙江有限公司 订单生产方法、装置、设备及计算机可读存储介质
CN112465599B (zh) * 2020-12-04 2023-11-07 车智互联（北京）科技有限公司 订单处理方法、订单处理系统及计算设备
CN112713964B (zh) * 2020-12-22 2022-08-05 潍柴动力股份有限公司 数据校验加速方法、装置、计算机设备及存储介质
CN117541356A (zh) * 2023-12-04 2024-02-09 广州方舟信息科技有限公司 一种订单执行方法、系统、电子设备和存储介质

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102930428A (zh) * 2012-09-25 2013-02-13 武汉云之翼科技有限公司 一种利用单点接口实现多点支付的方法
CN105741092A (zh) * 2016-01-19 2016-07-06 四川长虹电器股份有限公司 一种支持云端多业务的统一支付方法及系统
US20170193517A1 (en) * 2011-07-15 2017-07-06 Lisa Anderson Method and system for hosted order page/silent order post plus fraud detection
CN107679931A (zh) * 2017-08-17 2018-02-09 平安科技（深圳）有限公司 订单异步处理的方法、装置、存储介质及终端
CN108009805A (zh) * 2017-10-24 2018-05-08 广东康美通信息服务有限公司 一种支付处理方法、存储介质、装置及支付路由系统

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105099989B (zh) * 2014-04-24 2019-11-22 阿里巴巴集团控股有限公司 用于处理业务请求及获取业务处理结果的方法、装置和系统
CN106330769B (zh) * 2016-11-15 2022-03-08 腾讯科技（深圳）有限公司 一种业务处理方法及服务器

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20170193517A1 (en) * 2011-07-15 2017-07-06 Lisa Anderson Method and system for hosted order page/silent order post plus fraud detection
CN102930428A (zh) * 2012-09-25 2013-02-13 武汉云之翼科技有限公司 一种利用单点接口实现多点支付的方法
CN105741092A (zh) * 2016-01-19 2016-07-06 四川长虹电器股份有限公司 一种支持云端多业务的统一支付方法及系统
CN107679931A (zh) * 2017-08-17 2018-02-09 平安科技（深圳）有限公司 订单异步处理的方法、装置、存储介质及终端
CN108009805A (zh) * 2017-10-24 2018-05-08 广东康美通信息服务有限公司 一种支付处理方法、存储介质、装置及支付路由系统

Also Published As

Publication number Publication date
CN108765083A (zh) 2018-11-06
CN108765083B (zh) 2023-06-02

Similar Documents

Publication Publication Date Title
WO2019227606A1 (zh) 订单流程处理方法和系统
WO2019196244A1 (zh) 实时回调订单的方法和系统
WO2019227607A1 (zh) 路由化订单配置及处理方法、以及系统
US9167028B1 (en) Monitoring distributed web application transactions
WO2019223142A1 (zh) 应用程序测试方法、装置、计算机设备及存储介质
WO2020024419A1 (zh) 业务场景的测试方法、电子装置及可读存储介质
EP3177997A2 (en) Policy based resource management and allocation system
WO2019227634A1 (zh) 批量文件部分回盘处理方法和系统
CN108933695B (zh) 用于处理信息的方法和装置
WO2016022925A2 (en) Policy based resource management and allocation system
CN112882863A (zh) 恢复数据的方法、装置、系统和电子设备
CN110955640A (zh) 跨系统数据文件的处理方法、装置、服务器和存储介质
CN112445866A (zh) 数据处理方法、装置、计算机可读介质及电子设备
US20110106712A1 (en) Cost-Aware Service Aggregation
US11935004B2 (en) Reading and writing processing improvements as a single command
US11488232B2 (en) Document evaluation, alerting and validation system
CN111475388A (zh) 数据推送的测试方法、装置、计算机设备及存储介质
US11416318B1 (en) Application programming interface for integration flow design
WO2020047390A1 (en) Systems and methods for hybrid burst optimized regulated workload orchestration for infrastructure as a service
CN112148762A (zh) 一种实时数据流的统计方法和装置
CN110574018A (zh) 基于通信交换来管理异步分析操作
CN115617480A (zh) 一种任务调度方法、装置、系统及存储介质
CN112860770A (zh) 报表生成的方法、装置、电子设备和存储介质
CN111338642A (zh) 确定应用下载途径的方法、设备、终端及存储介质
JP5048537B2 (ja) ワークフロー処理装置

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: 18920595

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: 18920595

Country of ref document: EP

Kind code of ref document: A1