Hybrid processing method based on concurrent service acceptance

Abstract

The invention discloses a hybrid processing method based on concurrent service acceptance, and relates to the field of computer task processing, and the method comprises the steps: receiving a hybrid service handling request, carrying out verification according to preset protocol configuration information, and carrying out the grouping forwarding of the hybrid service handling request according to a service type; the protocol configuration information is realized by adopting a tree-shaped data structure; each type of business analyzed from the mixed business handling request information is separated, an original corresponding sub-business verification process is called for verification and unified fee calculation, sub-orders of each business type are generated, and processing priorities of the sub-orders are calculated according to the business types and business relations; and submitting the mixed service sub-orders according to the priority sequence. According to the method, the system processing time is shortened through highly concentrated service verification and fee calculation, the processing efficiency is improved, the mixed service sub-order processing sequence is adjusted according to the priority, and flow control of processing each service by multiple services is accepted at the same time.

Description

Technical Field

[0001] The application generally relates to the field of computer task processing, and in particular to a hybrid processing method based on concurrent business acceptance. Background Technology

[0002] A business system is a system that automates and integrates the management of a company's core business processes through a combination of software and hardware components. With the increasing penetration of digital business, business systems need to handle requests from multiple channels such as websites, apps, and offline terminals. These business types are complex and the volume is huge, involving multiple interfaces. In daily operation, there will be a rapid increase in high-concurrency transaction processing requests. It is necessary to rely on the technical architecture to support the efficient reception, parsing, and processing of concurrent requests from multiple channels to ensure the stable operation of business processes.

[0003] In real-world scenarios, multi-channel requests often carry mixed business data from different interfaces. Existing technologies for handling concurrent business, such as CN109949129 A, a high-concurrency order processing system and method, disclose that "at least one channel is set up in the application server, and business division within an order can be achieved through multiple channels, so that one channel handles one type of business, reducing mutual influence between businesses and improving the concurrent processing capability and processing speed of order flow." However, it does not disclose the verification of mixed business before processing, making it impossible to identify potential problems before processing mixed business, resulting in fundamental vulnerabilities in mixed business processing. Summary of the Invention

[0004] This application addresses the shortcomings of the background technology, namely, "the lack of disclosure of verification of mixed services before mixed service processing, which makes it impossible to identify potential problems before mixed service processing, resulting in fundamental vulnerabilities in mixed service processing," by providing a mixed processing method based on concurrent service acceptance.

[0005] This application provides a hybrid processing method based on concurrent service acceptance, including: Step S1: Mixed service access processing: Receive mixed service processing requests, verify them according to the preset protocol configuration information, and group and forward the mixed service processing requests to the mixed service pre-verification stage according to the service type; the protocol configuration information is implemented using a tree data structure; Step S2: Mixed business pre-verification and billing: Based on the business type of the grouped mixed business processing request, the corresponding verification sub-process is called for verification. After the verification is passed, the mixed business data information and order data information are registered. When all business verification sub-processes have passed the verification, the billing is calculated and the billing result is returned to the front end. If any verification sub-process fails the verification, a failure is returned. Step S3: Mixed business data processing: Obtain mixed business data information records with a processing status of pending processing, calculate the priority of each business type under the same mixed order code according to the weight configured by the business type and the business type dependency relationship, and change the status of the business type orders under the same mixed order code to effective in order of priority from small to large. The order data center reads the orders with the effective status and performs order activation processing. After processing is completed, update the order status to completed.

[0006] Preferably, in the tree-like data structure, each tree node stores key information about the transmission parameters in the service processing request message; In the tree-like data structure, the first-level child nodes under the root node are business type nodes, and each business type node contains a subtree of node parameters for that business type. The key information of the transmission parameters in the business processing request message must meet the node parameter subtree information verification of the corresponding business type.

[0007] Preferably, the key information of the transmission parameters includes: whether it is mandatory, whether it can be repeated, whether it can be empty, the default value of the parameter, the length requirement of the parameter value, and the enumerated value; The node parameter subtree information verification includes: verification of the relationship between parameters and verification of key parameter information.

[0008] Preferably, the verification according to the preset protocol configuration information includes: verifying the parameter format and parameter information of the mixed service processing request message parameters.

[0009] Preferably, the parameters of the mixed service processing request message are validated for both parameter format and parameter information, including: Obtain the parameter nodes contained in each service type in the mixed service processing request message; Determine whether the parameter format of the business type matches the subtree structure of the corresponding business type in the protocol configuration information tree structure. If they match, the verification passes and the verification continues. If they do not match, the verification fails. Determine whether the parameter values ​​contained in the service type meet the corresponding parameter configuration requirements in the protocol configuration information structure tree; if they match, the verification passes and the service group is forwarded; if they do not match, the verification fails.

[0010] Preferably, the mixed service processing requests are grouped and forwarded to the mixed service pre-verification stage according to the service type, including: In the mixed service processing request message, the subtree of the same service type node is transformed into a parameter data object with the same tree data structure. The node of the parameter data object stores key-value pairs composed of the parameter and parameter value of the corresponding node in the mixed service processing request message. The parameter data object for each business type is forwarded to the mixed business pre-verification stage for processing.

[0011] Preferably, the corresponding verification sub-process is invoked based on the business type of the grouped mixed business processing request for verification. After successful verification, the mixed business data information and order data information are registered, including: Based on the business type of the mixed business processing request in the group, the corresponding verification sub-process is invoked for verification, and a unique identifier, the mixed order code, is generated for the mixed business processing request. The validation sub-process performs individual validation and common logic validation; if the validation passes, it continues to the next step; if the validation fails, it exits. Register the mixed business data information and order data information corresponding to the mixed business processing request.

[0012] Preferably, the order data information registration includes: The order data center is called to register order-related information. Each business in the mixed business processing request generates a corresponding order and a corresponding order code. The order status is pre-generated, and orders in the pre-generated status will not be processed.

[0013] Preferably, the mixed business data information includes: mixed order code, business type, order code, priority, and mixed business data status; during the mixed business pre-verification and billing process, the mixed business data information status is pending processing, and the priority field is empty.

[0014] Preferably, step S3 includes: Step S31: Read records with mixed business data information status of pending processing and priority of empty; Step S32: Read the business type weight configuration information and business type dependency configuration information, and determine the business type priority according to the business type priority determination method; Step S33: Update the calculated business type priority to the priority field in the mixed business data information record of the corresponding business type; Step S34: Obtain records of mixed business data information under the same mixed order code whose status is not "complete" and whose priority is not empty. If the acquisition is successful and there are records in the "processing" status, continue to wait for a period of time and then acquire them again until there are no records of mixed business data information under the same mixed order code in the "processing" status. Sort them in ascending order of priority. Step S35: According to the priority from small to large, change the status of orders of the same business type under the same mixed order code to effective. The order data center reads the orders with the effective status and processes them for order activation. After the processing is completed, update the order status to completed.

[0015] Preferably, the business type weight configuration information includes: business type and weight; the business type dependency configuration information includes: dependent business type and dependent business type.

[0016] Preferably, the business type weight configuration information and business type dependency configuration information are read, and the business type priority is determined according to the business type priority determination method, including: Read and match the business type weight configuration information of the mixed business data information records under the same mixed order code with the business type weight configuration information, output the business type weight array list A, and then sort the business type weights in descending order to output the business type weight decreasing array list B. Read the business type dependency configuration information corresponding to the business type of the mixed business data information record under the same mixed order code, sort the business type weights in descending order and output the business type weight decreasing array list R. Take out the business type elements in the array list R one by one and perform the traversal and adjustment process based on the array list B until the array list R is traversed completely, and output the array list C. Iterate through array list C from the beginning, with the first element being 1, and increment by 1. Output array list D with increasing business type priority, and update the business type priority to the priority corresponding to the mixed business data information record.

[0017] Preferably, the traversal adjustment process for the currently retrieved business type element is as follows: start traversing array list B from the first business type element. If array list B contains a dependent business type element of the currently retrieved business type element, and the dependent business type element of the currently retrieved business type element is located after the currently retrieved business type element, then move the dependent business type element of the currently retrieved business type element before the currently retrieved business type element.

[0018] Compared with the prior art, the beneficial effects of this application are as follows: 1. This application supports the unified submission and processing of multiple business combinations, which can shorten the processing cycle for front-end operators. At the same time, the highly centralized business verification and fee calculation can also shorten the system processing time and improve business processing efficiency.

[0019] 2. This proposal involves relatively few API calls for mixed business processing technologies, which greatly reduces maintenance costs.

[0020] 3. The hybrid business processing technology involved in this application adopts highly centralized business verification, which can obtain the verification result at one time, thus avoiding the problem of having to roll back previously successfully processed business if a certain business fails verification.

[0021] 4. The tree-structured data method used in this application for hybrid service access manages the parameter format and parameter value rules of service request messages, which can separate the service request message format requirements from the service content and also enable rapid adjustment of the service request message format requirements.

[0022] 5. The mixed business processing priority calculation method of this application can flexibly adjust the processing order of mixed business sub-orders according to the business type weight and business dependency relationship, which can solve the process control problem of processing each business when the business processing system accepts multiple businesses at the same time.

[0023] 6. In this application, the pre-verification mechanism for mixed business data before mixed business processing can automatically complete the verification of data format consistency, business logic compliance and other dimensions for mixed business data requested from multiple channels. This design fills the gap in the pre-processing stage of mixed business in existing concurrent processing technologies (such as CN109949129 A). It can not only identify potential problems before business processing and avoid processing vulnerabilities caused by basic data, but also reduce invalid business from flowing into the subsequent processing process. Attached Figure Description

[0024] Figure 1 This is a flowchart illustrating a hybrid processing method based on concurrent service acceptance according to this application; Figure 2 This is a diagram illustrating the application architecture of the hybrid service processing device implemented using this application in the NGBOSS service support system. Figure 3 This is a schematic diagram of the interface protocol structure tree.

[0025] Figure 4 To modify the multi-layered product packet structure in the message of a user's product order / cancellation business type initiated by the front end; Figure 5 A schematic diagram of pre-validation logic for mixed services; Figure 6 This is a flowchart of the business data processing process; Figure 7 A diagram illustrating the array list related to the process of prioritizing business types. Detailed Implementation

[0026] The present application will now be described in further detail with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the application and not intended to limit its scope. Furthermore, it should be noted that, for ease of description, the accompanying drawings show only the parts relevant to the present application, not the entire structure.

[0027] This application provides a hybrid processing method based on concurrent service acceptance, based on Figures 1-7 The scenario describing the technical solution of the embodiments of this application: A hybrid processing method based on concurrent service acceptance includes: Step S1: Mixed Service Access Processing: Receive mixed service processing requests initiated by the front end, verify them according to the preset protocol configuration information, and group and forward the mixed service processing requests to the mixed service pre-verification stage according to the service type; the protocol configuration information is implemented using a tree data structure; Step S2: Mixed Business Pre-verification and Billing: Based on the business type of the grouped mixed business processing request, the corresponding verification sub-process is called for verification (i.e., the mixed business pre-verification step). After the verification is passed, the mixed business data information and order data information are registered. When all business verification sub-processes have passed the verification, the billing is calculated and the billing result is returned to the front end. If any verification sub-process fails the verification, a failure is returned. This application can be applied to the existing NGBOSS system (new generation business operation support system). The billing logic of the existing NGBOSS system is used to perform the billing and the billing result is returned to the front end. The existing NGBOSS system order data center has already implemented the order data design model, order opening process and order billing logic.

[0028] Step S3: Mixed Business Data Processing: Obtain mixed business data records with a processing status of "Pending Processing". Calculate the priority of each business type under the same mixed order code according to the weight configured for the business type and the business type dependency relationship. Change the status of orders of the same business type under the same mixed order code to "Active" in ascending order of priority (smallest priority principle). The order data center reads the orders with the "Active" status for order activation processing. After processing, update the order status to "Completed". See the mixed business data processing flowchart. Figure 6 .

[0029] The front-end application carriers include websites, mobile apps, and front-end pages.

[0030] In the tree-like data structure, each tree node stores key information about the transmission parameters in the service processing request message; In the tree-like data structure, the first-level child nodes under the root node are business type nodes, and each business type node contains a subtree of node parameters for that business type. The key information of the transmission parameters in the business processing request message must meet the node parameter subtree information verification of the corresponding business type.

[0031] The key information of the transmission parameters includes: whether it is mandatory, whether it can be repeated, whether it can be empty, the default value of the parameter, the length requirement of the parameter value, and the enumerated value. The node parameter subtree information verification includes: verification of the relationship between parameters and verification of key parameter information.

[0032] The verification according to the preset protocol configuration information includes: verifying the parameter format and parameter information of the mixed service processing request message parameters.

[0033] Perform parameter format validation and parameter information validation on the mixed service processing request message parameters, including: Obtain the parameter nodes contained in each service type in the mixed service processing request message; Determine whether the parameter format of the business type matches the subtree structure of the corresponding business type in the protocol configuration information tree structure (including whether the upper and lower structures match, whether the parameter nodes are missing, and whether they are duplicated). If they match, the verification passes and the verification continues to the next step. If they do not match, the verification fails. Determine whether the parameter values ​​contained in the service type meet the corresponding parameter configuration requirements in the protocol configuration information structure tree (parameter configuration requirements include whether the parameter value can be empty, default value, length, etc.); if they match, the verification passes and the service group is forwarded; if they do not match, the verification fails.

[0034] This includes grouping and forwarding mixed service processing requests to the mixed service pre-verification stage based on service type, including: In the mixed service processing request message, the subtree of the same service type node is transformed into a parameter data object with the same tree data structure. The node of the parameter data object stores key-value pairs composed of the parameter and parameter value of the corresponding node in the mixed service processing request message. The parameter data object for each business type is forwarded to the mixed business pre-verification stage for processing.

[0035] See the interface protocol structure tree configuration information relationship. Figure 3 Examples of tree-based data structures are as follows: The data structure is tree-like, such as XML, where parameters and values ​​appear as key-value pairs. The message parameter structure must match the subtree structure of one or more business types within the protocol configuration information tree structure. For example, in a website, app, or front-end page, the message for initiating a product order / cancellation, changing the business type of a user's product, or the multi-layered product packet structure are shown below. Figure 4 The userinfo node is a node in a subtree under the product order and cancellation business type. The userinfo node contains the prodchinfolist product list node, and the prodchinfolist node contains the ismpackage node and the prodinfo node. If the parameter of the prodinfo node is configured to be repeatable in the interface protocol structure tree configuration information, the prodchinfolist node can contain multiple prodinfo nodes, and so on.

[0036] Specifically, the corresponding verification sub-process is invoked to perform verification based on the business type of the grouped mixed business processing request (see [reference]). Figure 5 After successful verification, register the mixed business data information and order data information, including: Based on the business type of the mixed business processing request in the group, the corresponding verification sub-process is invoked for verification, and a unique identifier, the mixed order code, is generated for the mixed business processing request. The validation sub-process performs individual validation and common logic validation; if the validation passes, it continues to the next step; if the validation fails, it exits. The data information of mixed business processing requests and order data information are registered, and the storage method is not limited to database and session cache.

[0037] The order data registration includes: The order data center is called to register order-related information. Each business in the mixed business processing request generates a corresponding order and a corresponding order code. The order status is pre-generated. Orders in the pre-generated status will not be processed and will not take effect immediately. The order data center will then process the order.

[0038] The mixed business data information includes: mixed order code, business type, order code, priority, and mixed business data status. During the mixed business pre-verification and billing process, the mixed business data information status is pending, and the priority field is empty.

[0039] This application decouples and converges the business verification logic of the current system, breaking down large-granularity verification logic into smaller, independent verification sub-logic. Common, high-frequency small-granularity verification sub-logic is centrally managed using a call pool pattern. Various call pool pattern methods are currently popular, and their details are not described here. For example, common, high-frequency verification logic such as user information verification, product order record verification, and product information verification in the existing NGBOSS system is extracted from the original business logic and then managed independently, providing calls for various business sub-processes.

[0040] Personalized verification refers to logic verification specific to this business type; common logic verification refers to verification by calling certain common verification sub-logic from the common verification common logic call pool. These common verification sub-logic can be called by multiple business verification sub-processes.

[0041] Step S3 includes: Step S31: Read records with mixed business data information status of pending processing and priority of empty; Step S32: Read the business type weight configuration information and business type dependency configuration information, and determine the business type priority according to the business type priority determination method; Step S33: Update the calculated business type priority to the priority field in the mixed business data information record of the corresponding business type; Step S34: Obtain records of mixed business data information under the same mixed order code whose status is not "complete" and whose priority is not empty. If the acquisition is successful and there are records in the "processing" status, continue to wait for a period of time and then acquire them again until there are no records of mixed business data information under the same mixed order code in the "processing" status. Sort them in ascending order of priority. Step S35: According to the priority from small to large (small priority), change the status of orders of the same mixed order code to effective. The order data center reads the orders with the effective status and processes them for order activation. After the processing is completed, update the order status to completed.

[0042] The business type priority calculation factors mainly consist of business type weights and business type dependency information. These can be configured according to actual needs to control the order in which orders for various business types are activated. Business type weight configuration information includes: business type, weight; business type dependency configuration information includes: dependent business type, depended business type.

[0043] This includes reading business type weight configuration information and business type dependency configuration information, and determining business type priority according to the business type priority determination method, including: Read and match the business type weight configuration information of the mixed business data information records under the same mixed order code with the business type weight configuration information, output the business type weight array list A, and then sort the business type weights in descending order to output the business type weight decreasing array list B. Read the business type weight configuration information and business type dependency configuration information, and determine the business type priority according to the business type priority determination method, including: Read and match the business type weight configuration information of the mixed business data information records under the same mixed order code with the business type weight configuration information, output the business type weight array list A, and then sort the business type weights in descending order to output the business type weight decreasing array list B. Read the business type dependency configuration information corresponding to the business type of the mixed business data information record under the same mixed order code, sort the business type weights in descending order, and output the business type weight decreasing array list R. Take out the business type elements in the array list R in turn, and perform the traversal and adjustment process based on the array list B until the array list R is traversed. Output the array list C (the array list C is formed after the array list R is adjusted according to the traversal and adjustment process). Iterate through array list C from the beginning, with the first element being 1, and increment by 1. Output array list D with increasing business type priority, and update the business type priority to the priority corresponding to the mixed business data information record.

[0044] The process of traversing and adjusting the currently retrieved business type element is as follows: start traversing array list B from the first business type element. If array list B contains a dependent business type element of the currently retrieved business type element, and the dependent business type element is located after the currently retrieved business type element, then move the dependent business type element before the currently retrieved business type element.

[0045] Assume the business type of the extracted element is business type a, and business type a depends on business type b. Starting from the first element, traverse the array list B. If the array list B contains an element of business type b and the position of the element of business type b is after the element of business type a, then move the element of business type b before the element of business type a. Continue in this manner until the array list R is completely traversed, and output the array list C.

[0046] Iterate through array list C from the beginning, with the first element being 1, and increment by 1. Output array list D with increasing business type priority, and update the business type priority to the priority corresponding to the mixed business data information record.

[0047] See Figure 7 Examples of array lists A, B, C, and D are as follows: The mixed business data information records under a certain mixed order code involve 8 business types: business type 1, business type 2, business type 3, business type 4, business type 5, business type 6, business type 7, and business type 8. According to the business type weight configuration, an array list A can be obtained. The priority order of these 8 business types is calculated as follows: business type 4, business type 5, business type 7, business type 8, business type 3, business type 1, business type 2, and business type 6.

[0048] The mixed business processing method of this application can package multiple business transactions of different numbers and different business types for unified processing, providing mixed business access processing capabilities for external platforms such as websites and apps.

[0049] This application applies to the design of business system processing procedures, especially to the implementation of business support systems that have a business classification concept and support the simultaneous processing of multiple businesses. The hybrid business processing technology involved in this application supports the simultaneous acceptance of multiple different businesses. It can configure corresponding business sub-processes according to business needs to divert and process different businesses, and control the submission of each sub-order. The architecture of this proposal is relatively simple, easy to promote and implement, and has broad application prospects.

[0050] This application method allows the front-end to package and submit multiple services in a unified manner or in batches, breaking the limitation that multiple services must be processed serially and enabling parallel processing of multiple services. For example, one or more services such as number opening, network services, broadband services, and product orders can be combined into a mixed order and submitted to the server for processing. The server calculates the priority based on the weight of the mixed service type and the service relationship, and submits the service order for processing according to the priority. Subsequent processing continues according to the order data center in the original technical solution.

[0051] This application enables the business system to handle concurrent mixed business transactions without changing the existing business verification and processing logic and the backend order activation module.

[0052] The beneficial effects of this application are as follows: 1. This application supports the unified submission and processing of multiple business combinations, which can shorten the processing cycle for front-end operators. At the same time, the highly centralized business verification and fee calculation can also shorten the system processing time and improve business processing efficiency.

[0053] 2. This proposal involves relatively few API calls for mixed business processing technologies, which greatly reduces maintenance costs.

[0054] 3. The hybrid business processing technology involved in this application adopts highly centralized business verification, which can obtain the verification result at one time, thus avoiding the problem of having to roll back previously successfully processed business if a certain business fails verification.

[0055] 4. The tree-structured data method used in this application for hybrid service access manages the parameter format and parameter value rules of service request messages, which can separate the service request message format requirements from the service content and also enable rapid adjustment of the service request message format requirements.

[0056] 5. The mixed business processing priority calculation method of this application can flexibly adjust the processing order of mixed business sub-orders according to the business type weight and business dependency relationship, which can solve the process control problem of processing each business when the business processing system accepts multiple businesses at the same time.

[0057] 6. In this application, the pre-verification mechanism for mixed business data before mixed business processing can automatically complete the verification of data format consistency, business logic compliance and other dimensions for mixed business data requested from multiple channels. This design fills the gap in the pre-processing stage of mixed business in existing concurrent processing technologies (such as CN109949129 A). It can not only identify potential problems before business processing and avoid processing vulnerabilities caused by basic data, but also reduce invalid business from flowing into the subsequent processing process.

Claims

1. A hybrid processing method based on concurrent service acceptance, characterized in that, include: Step S1: Mixed service access processing: Receive mixed service processing requests, verify them according to the preset protocol configuration information, and group and forward the mixed service processing requests to the mixed service pre-verification stage according to the service type; The protocol configuration information is implemented using a tree-like data structure; Step S2: Mixed business pre-verification and billing: Based on the business type of the grouped mixed business processing request, the corresponding verification sub-process is called for verification. After the verification is passed, the mixed business data information and order data information are registered. When all business verification sub-processes have passed the verification, the billing is calculated and the billing result is returned to the front end. If any verification sub-process fails the verification, a failure is returned. Step S3: Mixed business data processing: Obtain mixed business data information records with a processing status of pending processing, calculate the priority of each business type under the same mixed order code according to the weight configured by the business type and the business type dependency relationship, and change the status of the business type orders under the same mixed order code to effective in order of priority from small to large. The order data center reads the orders with the effective status and performs order activation processing. After processing is completed, update the order status to completed.

2. The hybrid processing method based on concurrent service acceptance according to claim 1, characterized in that, In the tree-like data structure, each tree node stores key information about the transmission parameters in the service processing request message; In the tree-like data structure, the first-level child nodes under the root node are business type nodes, and each business type node contains a subtree of node parameters for that business type. The key information of the transmission parameters in the business processing request message must meet the node parameter subtree information verification of the corresponding business type.

3. The hybrid processing method based on concurrent service acceptance according to claim 2, characterized in that, The key information of the transmission parameters includes: whether it is mandatory, whether it can be repeated, whether it can be empty, the default value of the parameter, the length requirement of the parameter value, and the enumerated value. The node parameter subtree information verification includes: verification of the relationship between parameters and verification of key parameter information.

4. The hybrid processing method based on concurrent service acceptance according to claim 1, characterized in that, The verification according to the preset protocol configuration information includes: verifying the parameter format and parameter information of the mixed service processing request message parameters.

5. The hybrid processing method based on concurrent service acceptance according to claim 4, characterized in that, Perform parameter format validation and parameter information validation on the mixed service processing request message parameters, including: Obtain the parameter nodes contained in each service type in the mixed service processing request message; Determine whether the parameter format of the business type matches the subtree structure of the corresponding business type in the protocol configuration information tree structure. If they match, the verification passes and the verification continues. If they do not match, the verification fails. Determine whether the parameter values ​​contained in the service type meet the corresponding parameter configuration requirements in the protocol configuration information structure tree; if they match, the verification passes and the service group is forwarded; if they do not match, the verification fails.

6. The hybrid processing method based on concurrent service acceptance according to claim 1, characterized in that, The mixed service processing requests are grouped and forwarded to the mixed service pre-verification stage according to the service type, including: In the mixed service processing request message, the subtree of the same service type node is transformed into a parameter data object with the same tree data structure. The node of the parameter data object stores key-value pairs composed of the parameter and parameter value of the corresponding node in the mixed service processing request message. The parameter data object for each business type is forwarded to the mixed business pre-verification stage for processing.

7. The hybrid processing method based on concurrent service acceptance according to claim 1, characterized in that, Based on the business type of the grouped mixed business processing request, the corresponding verification sub-process is invoked for verification. After successful verification, the mixed business data information and order data information are registered, including: Based on the business type of the mixed business processing request in the group, the corresponding verification sub-process is invoked for verification, and a unique identifier, the mixed order code, is generated for the mixed business processing request. The validation sub-process performs individual validation and common logic validation; if the validation passes, it continues to the next step; if the validation fails, it exits. Register the mixed business data information and order data information corresponding to the mixed business processing request.

8. A hybrid processing method based on concurrent service acceptance according to claim 7, characterized in that, Order data registration includes: The order data center is called to register order-related information. Each business in the mixed business processing request generates a corresponding order and a corresponding order code. The order status is pre-generated, and orders in the pre-generated status will not be processed.

9. A hybrid processing method based on concurrent service acceptance according to claim 7, characterized in that, The mixed business data information includes: mixed order code, business type, order code, priority, and mixed business data status. During the mixed business pre-verification and billing process, the mixed business data information status is pending, and the priority field is empty.

10. A hybrid processing method based on concurrent service acceptance according to claim 1, characterized in that, Step S3 includes: Step S31: Read records with mixed business data information status of pending processing and priority of empty; Step S32: Read the business type weight configuration information and business type dependency configuration information, and determine the business type priority according to the business type priority determination method; Step S33: Update the calculated business type priority to the priority field in the mixed business data information record of the corresponding business type; Step S34: Obtain records of mixed business data information under the same mixed order code whose status is not "complete" and whose priority is not empty. If the acquisition is successful and there are records in the "processing" status, continue to wait for a period of time and then acquire them again until there are no records of mixed business data information under the same mixed order code in the "processing" status. Sort them in ascending order of priority. Step S35: According to the priority from small to large, change the status of orders of the same business type under the same mixed order code to effective. The order data center reads the orders with the effective status and processes them for order activation. After the processing is completed, update the order status to completed.

11. A hybrid processing method based on concurrent service acceptance according to claim 10, characterized in that, The business type weight configuration information includes: business type and weight; the business type dependency configuration information includes: dependent business type and dependent business type.

12. A hybrid processing method based on concurrent service acceptance according to claim 10, characterized in that, Read the business type weight configuration information and business type dependency configuration information, and determine the business type priority according to the business type priority determination method, including: Read and match the business type weight configuration information of the mixed business data information records under the same mixed order code with the business type weight configuration information, output the business type weight array list A, and then sort the business type weights in descending order to output the business type weight decreasing array list B. Read the business type dependency configuration information corresponding to the business type of the mixed business data information record under the same mixed order code, sort the business type weights in descending order and output the business type weight decreasing array list R. Take out the business type elements in the array list R one by one and perform the traversal and adjustment process based on the array list B until the array list R is traversed completely, and output the array list C. Iterate through array list C from the beginning, with the first element being 1, and increment by 1. Output array list D with increasing business type priority, and update the business type priority to the priority corresponding to the mixed business data information record.

13. A hybrid processing method based on concurrent service acceptance according to claim 12, characterized in that, The traversal adjustment process for the currently retrieved business type element is as follows: start traversing array list B from the first business type element. If array list B contains a dependent business type element of the currently retrieved business type element, and the dependent business type element is located after the currently retrieved business type element, then move the dependent business type element before the currently retrieved business type element.

Images