Business flow conversion system and business handling system

Abstract

The application provides a service flow transfer system, and relates to the field of gas service handling. The service flow transfer system is applied to a server end. The service flow transfer system is configured to be in communication connection with a plurality of different service handling systems. The service flow transfer system comprises: a service receiving module configured to receive a service application sent by a client end; a service distribution module configured to extract a service type of the service application, query a preset service-support system association comparison table, obtain at least one candidate service handling system adapted to the service type, and select one of the candidate service handling systems as a target service handling system based on the adaptation degrees of the candidate service handling systems to the service type; and a service sending module configured to send the service application to the target service handling system and trigger the target service handling system to handle the service application. The system can realize accurate distribution of the service application and improve service flow transfer efficiency.

Description

TECHNICAL FIELD

[0001] The present application relates to the field of gas business handling, in particular to a business flow system and a business handling system. BACKGROUND

[0002] In the field of gas business handling, although some gas companies have provided business application services through online platforms, they have basic business classification functions, but the related technologies have obvious deficiencies. On the one hand, the business flow depends on manual operation, and the staff needs to manually identify the business type and distribute it to the corresponding processing system, which leads to low efficiency, high error rate, and easy misallocation of business and delay of processing. On the other hand, manual operation cannot fully consider the adaptability factor, and often distributes the business according to fixed rules, which cannot be dynamically adjusted. At the same time, the related technologies also have many problems in data transmission security, business processing efficiency, system maintenance cost, and user experience. SUMMARY

[0003] Therefore, it is necessary to provide a business flow system that can receive, distribute and send business applications to achieve efficient and accurate business flow and improve business processing efficiency and accuracy.

[0004] In a first aspect, the present application provides a business flow system applied to a server side, the business flow system being configured to be in communication connection with a plurality of different business handling systems, and the business flow system comprising:

[0005] a business application receiving module, a business application sending module and a business application distribution module.

[0006] The business application receiving module is configured to receive a business application sent by a client side;

[0007] The business application distribution module is configured to extract the business type of the business application, query a preset business-support system association table, obtain at least one candidate business handling system adapted to the business type, and select one of the candidate business handling systems as a target business handling system based on the adaptability of each candidate business handling system to the business type.

[0008] The business application sending module is configured to send the business application to the target business handling system and trigger the target business handling system to handle the business application.

[0009] The business flow conversion system obtains the business application of the client through the business application receiving module, ensures the reception of the business application and the extraction of the business type. The business application distribution module can not only extract the business type information in the business application, but also accurately screen out the candidate business handling system suitable for the business type in combination with the preset business-support system association table. This process reduces manual intervention and reduces the risk of business mismatch caused by human judgment errors. Further, the business application distribution module can evaluate and select the adaptation degree of each candidate system to a specific business type, ensuring that the business application can be distributed to the most suitable business handling system, thereby optimizing resource allocation and avoiding business backlog or system overload. The business application sending module can accurately send the business application to the selected target business handling system and trigger the corresponding business handling process, effectively improving the efficiency and accuracy of business processing and ensuring the smoothness and timeliness of business flow conversion.

[0010] In one of the embodiments, the business flow conversion system further comprises:

[0011] The data acquisition module is configured to acquire at least two indicators of the candidate business handling system for evaluating the system load state;

[0012] The storage module is configured to store a business-resource weight mapping table, the business-resource weight mapping table comprising a mapping relationship between any business type and resource weights of at least two indicators;

[0013] The business application distribution module is further configured to: based on the business type, acquire the resource weights of each indicator corresponding to the business type from the business-resource weight mapping table, and based on the resource weights, normalize the indicators to obtain the system load state of the candidate business handling system;

[0014] The business application distribution module selects one of the candidate business handling systems as the target business handling system based on the system load state and the adaptation degree of the candidate business handling system to the business type.

[0015] In one of the embodiments, the storage module further comprises a business-weight coefficient mapping table, the business-weight coefficient mapping table comprising a mapping relationship between any business type and weight coefficients of different influence factors, the influence factors including a first influence factor based on the adaptation degree, a second influence factor based on the system load state, and a third influence factor based on the historical processing efficiency;

[0016] The business application distribution module is further configured to: based on the business type of the business application, obtain the weight coefficient of each influence factor through a business-weight coefficient mapping table, and perform weight distribution on the influence factors according to the obtained weight coefficients to generate a comprehensive evaluation result of the different candidate business handling systems for the business type, and select the candidate business handling system with the maximum comprehensive evaluation result as the target business handling system.

[0017] In one of the embodiments, the third influence factor is configured to be positively correlated with the inverse of the historical processing efficiency.

[0018] In one of the embodiments, the historical processing efficiency is configured to be the ratio of the average processing time of the business type in the candidate business handling system to the current processing time prediction value, the average processing time is obtained by statistically calculating the historical processing time data of the candidate business handling system for the business type, and the current processing time prediction value is obtained by a time series prediction algorithm in combination with the current business queue length and system resource occupation of the candidate business handling system.

[0019] In one of the embodiments, the second influence factor is configured to be positively correlated with the inverse of the system load state.

[0020] In one of the embodiments, the storage module further includes a business-urgency mapping table, the business-urgency mapping table including a mapping relationship between different business types and business urgency;

[0021] The second influence factor is further configured to be modulated by the business urgency and positively correlated.

[0022] In one of the embodiments, the business flow system further includes:

[0023] The state query module is configured to traverse and query the states of the candidate business handling systems, when it is detected that the candidate business handling system is in a normal state, the data acquisition module acquires the indicators of the candidate business handling system; when it is detected that the candidate business handling system is in a fault state, the candidate business handling system is marked as a fault state, and the data acquisition module is controlled to skip acquiring the indicators of the candidate business handling system and record a skip log.

[0024] In one of the embodiments, the state query module is further configured to: when the data acquisition module fails to acquire the indicators of any candidate business handling system, mark the candidate business handling system as a fault state;

[0025] The data acquisition module is further configured to: when the candidate business handling system is marked as a fault state, based on the historical indicator data of the candidate business handling system within a specified time range and in combination with the resource weight, calculate and obtain the system load state of the candidate business handling system.

[0026] The second aspect also provides a service handling system, the service handling system comprising:

[0027] a plurality of service handling subsystems, each service handling subsystem configured to handle service applications of the same or different service type;

[0028] The service handling system further comprises the service flow system as the first aspect, and the service flow system is configured to be in communication connection with the plurality of service handling subsystems. BRIEF DESCRIPTION OF DRAWINGS

[0029] Figure 1 a service flow system diagram in one embodiment;

[0030] Figure 2 a flow chart for determining a target service handling subsystem based on the adaptation degree in one embodiment;

[0031] Figure 3 a service flow system diagram in another embodiment;

[0032] Figure 4 a flow chart for determining a target service handling subsystem based on the system load value and the adaptation degree in one embodiment;

[0033] Figure 5 a flow chart for determining a target service handling subsystem based on a first impact factor based on the adaptation degree, a second impact factor based on the system load, and a third impact factor based on the historical processing efficiency in one embodiment;

[0034] Figure 6 a flow chart for determining a target service handling subsystem based on a first impact factor based on the adaptation degree, a second impact factor based on the urgency degree and the system load, and a third impact factor based on the historical processing efficiency in one embodiment;

[0035] Figure 7 a service flow system diagram in another embodiment;

[0036] Figure 8 a service handling system diagram in one embodiment. DETAILED DESCRIPTION

[0037] In order to make the purpose, technical scheme and advantages of the present application clearer, the present application will be further described in detail below with reference to the drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and do not limit the present application.

[0038] Embodiment one,

[0039] In one embodiment, as Figure 1As shown, a business flow transfer system is provided, which is applied to a server end, the business flow transfer system is configured to be communicatively connected with a plurality of different business handling systems (e.g. business handling system 1, business handling system 2… business handling system n), the business flow transfer system comprises:

[0040] The business application receiving module, the business application sending module and the business application distribution module.

[0041] The business application receiving module is configured to receive a business application sent by a client end; the business application sending module is configured to send the business application to a target business handling system and trigger the target business handling system to handle the business application; and the business application distribution module is configured to extract a business type of the business application, query a preset business-support system association table, obtain at least one candidate business handling system adapted to the business type, and select one of the candidate business handling systems as the target business handling system based on an adaptation degree of each candidate business handling system to the business type.

[0042] Specifically, the business flow transfer system is applied to a server end and can be used to realize full-automation intelligent distribution of gas businesses (e.g. gas resident account opening, gas meter maintenance and other businesses), the core functions of which include receiving a business application, dynamically selecting an optimal target business handling system and forwarding the business application data safely.

[0043] The business application receiving module can be responsible for receiving a business application from a client end (e.g. WeChat public account, mobile App and the like), and performing preliminary analysis on the received business application to extract key business information (e.g. business type, user basic information, application content and the like). The business application distribution module can query a preset business-support system association table (which stores mapping relationships between each type of business and a support system and adaptation degree scores) according to the business type extracted by the business application receiving module, and filter out all candidate business handling systems capable of processing the business. Further, the business application distribution module can compare the adaptation degrees of the candidate business handling systems and select a business handling system based on the adaptation degrees. In an embodiment, the candidate business handling system with the highest adaptation degree value can be selected as the target business handling system.

[0044] If the business application distribution module determines the target business handling system, the business application sending module can accurately send the business application to the target business handling system, ensuring that the business application information can reach the correct processing node in time.

[0045] As an optional implementation manner, the embodiment of the present application schematically provides a business-support system association table, which is specifically shown as follows:

[0046]

[0047] wherein, represents the degree of adaptation of the business type to the target business handling system, and is used to determine whether the target business handling system has the ability to handle the business. The business type is mapped to the preset support relationship of the target business handling system , and the degree of adaptation of the two is returned. If the system supports handling the business , then (an optional value can be given according to the business adaptation priority, such as 1 for a core processing system and 0.5 for an auxiliary system, etc.); if the system does not support handling the business , then .

[0048] The comprehensive evaluation function for selecting the target business handling system based on the degree of adaptation is as follows:

[0049] ;

[0050] wherein, is the business type, and the target business handling system.

[0051] Based on the degree of adaptation of each candidate business handling system to the business type, the candidate business handling system with the highest degree of adaptation can be selected from the candidate business handling systems as the target business handling system.

[0052] After the target business handling system is determined, the business application sending module can accurately and correctly send the business application to the target business handling system, ensuring that the business application information can reach the correct processing node in time. After the business application enters the target business handling system, it can enter the processing task queue of the target business handling system and wait in line for the target business handling system to process the business application.

[0053] According to the above description, the business flow conversion system provided by the embodiment one of the present application obtains the business application of the client through the business application receiving module, ensuring the reception of the business application and the extraction of the business type. The business application distribution module can not only extract the business type information in the business application, but also accurately filter out the candidate business handling system suitable for the business type in combination with the preset business-support system association table. This process reduces manual intervention and reduces the risk of business mismatch caused by human judgment errors. Further, the business application distribution module can evaluate and select the adaptation degree of each candidate system to a specific business type, ensuring that the business application can be distributed to the appropriate business handling system. The business application sending module can accurately send the business application to the selected target business handling system and trigger the corresponding business handling process, effectively improving the efficiency and accuracy of business processing and ensuring the smoothness and timeliness of business flow conversion.

[0054] In order to further illustrate the business flow conversion system provided by the embodiment one of the present application, the steps of determining the target business handling system based on the adaptation degree will be described as follows. Figure 2 As shown in the figure, the steps are as follows:

[0055] Step 201: The user submits a business application in a client such as WeChat public number.

[0056] Step 202: The business application receiving module of the business flow conversion system receives the business application.

[0057] Step 203: The business application receiving module extracts the business type information in the business application.

[0058] Step 204: The business application distribution module receives the business type information in the application and queries the preset business-support system association table.

[0059] Step 205: Based on the association table, the business application distribution module obtains at least one candidate business handling system suitable for the business type.

[0060] Step 206: The business application distribution module selects the most suitable target business handling system from the candidate business handling systems based on the adaptation degree of each candidate business handling system to the business type through a comprehensive evaluation function.

[0061] Step 207: The business application sending module sends the business application to the selected target business handling system.

[0062] Step 208: The business application sending module triggers the target business handling system to handle the business application.

[0063] Step 209: The target business handling system receives and processes the business application.

[0064] Embodiment two

[0065] On the basis of the service flow transfer system provided in Embodiment one of the present application, as shown in Figure 3 , the service flow transfer system provided in Embodiment two of the present application further comprises a data acquisition module and a storage module.

[0066] The data acquisition module is configured to acquire at least two indicators of the candidate service handling systems for evaluating system load status; and the storage module is configured to store a service-resource weight mapping table, which includes the mapping relationship between any service type and the resource weight of the at least two indicators.

[0067] Specifically, the data acquisition module continuously acquires the indicators of the candidate service handling systems for evaluating system load status through real-time monitoring API. These indicators can include CPU usage , memory occupancy , network bandwidth utilization , etc. These indicators can be normalized into system load values L i in the range of [0, 1] L i , and the formula of the system load value

[0068] ;

[0069] wherein are the maximum carrying values of the CPU, memory, and network bandwidth of the system , respectively, which can be adjusted according to the importance of system resources to service processing. For example, for a computation-intensive service, the value of can be appropriately increased.

[0070] The storage module can store a service-resource weight mapping table, which can define the weight coefficients of different service types (such as gas meter maintenance, gas safety inspection, etc.) for each indicator . Embodiment two of the present application provides a service-resource weight mapping table as follows:

[0071]

[0072] Based on the system load value and the adaptation degree, a comprehensive evaluation function is calculated to select the candidate service handling system with the maximum comprehensive evaluation function value from the candidate service handling systems as the target service handling system. The comprehensive evaluation function can be represented by the following formula:

[0073] .

[0074] wherein, represents the service type and the degree of adaptation between the service handling system , represents the system load status of the service handling system . is a weight coefficient, in the second embodiment of the present application, .

[0075] It should be noted that, based on the service type, the resource weight of each index corresponding to the service type is obtained from the service-resource weight mapping table, and the index is normalized based on the resource weight to obtain the system load status of the candidate service handling system; the service application distribution module comprehensively considers the system load status and the degree of adaptation of the candidate service handling system with respect to the service type, and selects one of the candidate service handling systems as the target service handling system.

[0076] In order to further illustrate the service flow system provided by the second embodiment of the present application, the steps of determining the target service handling system based on the system load value and the degree of adaptation are described as follows. Figure 4 As shown in FIG. 4, the steps are as follows:

[0077] Step 401: A user submits a service application in a client such as a WeChat public number.

[0078] Step 402: A service application receiving module of the service flow system receives the service application from the client such as the WeChat public number.

[0079] Step 403: The service application receiving module extracts service type information from the received service application.

[0080] Step 404: A service application distribution module queries a preset service-support system association table based on the service type, and according to the service type information and the association table, at least one candidate service handling system capable of processing the service type is obtained, and the degree of adaptation with respect to the service type is obtained based on each candidate service handling system.

[0081] Step 405: For each candidate service handling system, its current system load information is collected through a system monitoring API, including indexes such as CPU usage, memory occupancy, network bandwidth utilization, etc.

[0082] Step 406: The collected system load information is converted into a system load value in the range of [0, 1] using a specific normalization formula, so as to be uniformly evaluated.

[0083] Step 407: Based on the system load value and the service adaptation degree, a comprehensive evaluation function is used to evaluate each candidate service handling system, and a comprehensive score thereof is calculated.

[0084] Step 408: Select the candidate service handling system with the highest comprehensive score as the target service handling system.

[0085] Step 409: The service application sending module sends the service application to the selected target service handling system and triggers the system to start processing the service application.

[0086] Step 410: The target service handling system receives and processes the service application, and executes the corresponding business logic and operations.

[0087] Embodiment Three,

[0088] On the basis of the service flow system provided in Embodiment Two of the present application, in the service flow system provided in Embodiment Three of the present application, the storage module further includes a business-weight coefficient mapping table, the business-weight coefficient mapping table including a mapping relationship between any business type and different weight coefficients of influence factors, the influence factors including a first influence factor based on the adaptation degree, a second influence factor based on the system load state, and a third influence factor based on the historical processing efficiency.

[0089] Specifically, the historical processing time data of each business type is extracted from the historical business processing database. In each service handling system , the historical processing time data is extracted. The historical processing efficiency is defined as the ratio of the average processing time of the business to the current processing time prediction value , that is: The average processing time can be obtained by statistical calculation on the historical processing time data, and the current processing time prediction value is predicted based on a time series prediction algorithm (such as an ARIMA model) in combination with the current business queue length, system resource occupation, and other factors.

[0090] Specifically, the business-weight coefficient mapping table stores the mapping relationship between any business type and different weight coefficients of influence factors. For example, the business types of gas meter maintenance, gas transfer, and gas case correspond to the first influence factor based on the adaptation degree, the second influence factor based on the system load, and the third influence factor based on the historical processing efficiency. The business-weight coefficient mapping table is as follows:

[0091]

[0092] The business application allocation module is also configured to: based on the business type of the business application, obtain the weight coefficients of each influencing factor through the business-weight coefficient mapping table, and allocate the weights of the influencing factors according to the obtained weight coefficients, generate a comprehensive evaluation result of different candidate business processing systems for the business type, and select the candidate business processing system that makes the comprehensive evaluation result the largest as the target business processing system.

[0093] Specifically, when a service request is received, the service request allocation module can extract the weight coefficients α, β, and γ of each influencing factor corresponding to that service type from the service-weight coefficient mapping table. For example, the gas meter repair service might be configured with α=0.8, β=0.1, and γ=0.1, while the gas transfer service could be set to α=0.2, β=0.5, and γ=0.3. These weight coefficients directly affect the three major influencing factors: the second influencing factor being the system load status. The third influencing factor based on historical processing efficiency The first influencing factor of fitness .

[0094] Second Impact Factor The first factor is configured to be positively correlated with the inverse of the system load state. The second influencing factor (i.e., the system load state factor) is designed to be positively correlated with the system load state value. reciprocal Positively correlated, when the real-time load status value of the candidate business processing system The lower (e.g.) =0.2 indicates that the resource utilization rate is only 20%, and its reciprocal A value of 5 will significantly increase the contribution of this factor to the comprehensive evaluation function, thus prioritizing the selection of low-load systems.

[0095] Third Impact Factor It is configured to be positively correlated with the inverse of historical processing efficiency. This refers to the historical average efficiency of the business workflow system when processing a specific type of business (e.g., gas meter repair). When the time is low (e.g., an average time of 2 hours and a historical average efficiency of 0.5), its reciprocal =2 can significantly increase the contribution value of the third influence factor in the comprehensive evaluation function, thereby reducing the priority of the candidate business processing system.

[0096] A score is generated for each candidate business processing system using a comprehensive evaluation function, and the candidate business processing system that yields the highest comprehensive evaluation result is selected as the target business processing system.

[0097] The formula for the comprehensive evaluation function is as follows:

[0098] ;

[0099] wherein, is a weight coefficient, and The gas company can dynamically adjust the weight coefficient according to actual business needs, such as the business-weight coefficient mapping table described above, and configure each weight coefficient corresponding to the business.

[0100] To further illustrate the business flow conversion system provided by Embodiment Three of the present application, as shown in FIG. 3, the steps of determining the target business handling system based on the first influence factor of the adaptation degree, the second influence factor of the system load, and the third influence factor of the historical processing efficiency are described as follows. Figure 5

[0101] Step 501: A user submits a business application on a client such as a WeChat public account.

[0102] Step 502: A business application receiving module in the business flow conversion system receives the business application from the client such as the WeChat public account.

[0103] Step 503: The business application receiving module extracts business type information from the received business application.

[0104] Step 504: A business application distribution module queries a preset business-support system association table based on the business type to obtain a list of candidate business handling systems supporting the business type.

[0105] Step 505: For each candidate business handling system, a first influence factor based on business adaptation degree is calculated.

[0106] Step 506: Current load information (such as CPU usage, memory occupancy, network bandwidth utilization, etc.) of each candidate business handling system is collected, and a second influence factor based on system load is calculated.

[0107] Step 507: Historical processing data of each candidate business handling system is extracted from a historical business processing database, and a third influence factor based on historical processing efficiency is calculated.

[0108] Step 508: The above three influence factors are substituted into a comprehensive evaluation function, and a preset weight coefficient is combined to calculate a comprehensive score of each candidate business handling system.

[0109] Step 509: According to the comprehensive score, the system with the highest score is selected from the candidate business handling systems as the target business handling system.

[0110] Step 510: A business application sending module sends the business application to the selected target business handling system and triggers the system to start processing the business application.

[0111] ​Step 511: The target service handling system receives and processes the service application, and executes corresponding service logic and operations.

[0112] Embodiment four,

[0113] On the basis of embodiment three, the service flow system provided in embodiment four of the present application further comprises a service-urgency mapping table, and the service-urgency mapping table comprises a mapping relationship between different service types and service urgency.

[0114] The second influence factor is further configured to be modulated by the service urgency and positively related.

[0115] Specifically, the service-urgency mapping table is as follows:

[0116]

[0117] According to the service type, the service-urgency mapping table is referred to to assign an urgency value to the service application . The service-urgency mapping table is formulated according to factors such as potential risks of the service and influence degree on the user's life. For example, the service urgency of gas meter maintenance (with leakage) is set to 5, and the service urgency of gas transfer is set to 1.

[0118] Further, the target service handling system is determined based on the first influence factor of the adaptation degree, the second influence factor of the urgency and the system load, and the third influence factor of the historical processing efficiency. The target service handling system can be selected by calculating a comprehensive function, and the calculation formula is as follows:

[0119] ;

[0120] The score of each candidate service handling system is generated by the comprehensive evaluation function, and the candidate service handling system with the maximum comprehensive evaluation result is selected as the target service handling system.

[0121] When calculating the second influence factor, the urgency value can be used as a modulation coefficient and multiplied by the reciprocal of the load state to form an emergency weighted load factor . For example, when the load L of the target service handling system is 0.4, the second influence factor value of the ordinary maintenance service (E=3) is 7.5, and the second influence factor value of the leakage repair (E=10) is as high as 25, which ensures that the emergency service must be allocated to the low-load system first. When calculating the second influence factor, the service urgency modulation and the weight coefficient a form a double regulation, and in the comprehensive evaluation function, a larger a value (such as leakage repair a=0.8) is usually configured for high-urgency services, further strengthening the decision weight of the second influence factor.

[0122] To further illustrate the service flow system provided by Embodiment Four of the present application, as shown in Figure 6 The following describes the steps of determining the target service handling system based on the first impact factor based on the adaptation degree, the second impact factor based on the emergency level and system load, and the third impact factor based on the historical processing efficiency, as follows:

[0123] Step 601: A user submits a service application through a client such as a WeChat public account.

[0124] Step 602: A service application receiving module of the service flow system receives the service application from the client such as the WeChat public account.

[0125] Step 603: The service application receiving module extracts service type information from the received service application.

[0126] Step 604: A service application distribution module queries a preset service-support system association table based on the service type to obtain a list of candidate service handling systems supporting the service type.

[0127] Step 605: For each candidate service handling system, a first impact factor based on service adaptation degree is calculated.

[0128] Step 606: The emergency level of the service is evaluated, and a second impact factor based on the emergency level and system load is calculated in combination with the current load information (such as CPU usage, memory occupancy, network bandwidth utilization, etc.) of each candidate service handling system.

[0129] Step 607: Historical processing data of each candidate service handling system is extracted from a historical service processing database, and a third impact factor based on historical processing efficiency is calculated.

[0130] Step 608: The above three impact factors are substituted into a comprehensive evaluation function, and a comprehensive score of each candidate service handling system is calculated in combination with preset weight coefficients.

[0131] Step 609: According to the comprehensive score, the system with the highest score is selected from the candidate service handling systems as the target service handling system.

[0132] Step 610: A service application sending module sends the service application to the selected target service handling system and triggers the system to start processing the service application.

[0133] Step 611: The target service handling system receives and processes the service application and executes corresponding service logic and operations.

[0134] As an optional implementation manner, as shown in Figure 7 The service flow system further includes a state query module.

[0135] The state query module is configured to traverse the state of the query candidate business handling system, when it is detected that the candidate business handling system is in a normal state, the data collection module collects the indicators of the candidate business handling system; when it is detected that the candidate business handling system is in a fault state, the candidate business handling system is marked as a fault state, and the data collection module is controlled to skip collecting the indicators of the candidate business handling system, and a skip log is recorded.

[0136] In the embodiments of the present application, the state query module can adopt a combination of heartbeat detection (for example, HTTP / HTTPS health check interface) and performance threshold judgment (response time > 500 ms or error rate > 5% for 30 seconds) to poll the running state of all candidate business handling systems at an interval of 5 seconds. When the candidate business handling system responds normally (status code 200 and performance indicators within the threshold), the data collection module is triggered to collect real-time indicators such as CPU usage and memory occupation through a standard monitoring interface (for example, Prometheus interface); if the candidate business handling system is detected to be abnormal (3 consecutive detection failures or resource over-limit), a three-level processing procedure is performed: marking the system as a fault state (setting a fault identifier and an expiration time), sending a shielding instruction to the data collection module (asynchronous notification is realized through a message queue), and finally recording a structured skip log (including system ID, fault type, timestamp and detection indicators) to an ELK log system.

[0137] In one embodiment, the state query module is further configured to mark the candidate business handling system as a fault state when the data collection module fails to collect the indicators of any candidate business handling system.

[0138] The data collection module is further configured to, when the candidate business handling system is marked as a fault state, calculate the system load state of the candidate business handling system based on historical indicator data of the candidate business handling system within a specified time range and in combination with resource weights.

[0139] In the embodiments of the present application, when the data collection module fails to obtain real-time indicators of a certain candidate business handling system (for example, API call timeout or data parsing exception), the state query module will immediately mark the candidate business handling system as a fault state (set a fault mark with a TTL of 15 minutes), and trigger a degradation processing procedure, that is, the data collection module will automatically switch to a backup data source, calculate an approximate system load state value based on historical indicator data of the candidate business handling system within the last 30 minutes (stored in a time series database) and in combination with resource weights corresponding to the current business type through a weighted moving average algorithm.

[0140] Based on the same concept, the present application also provides a business handling system, which comprises:

[0141] a plurality of service handling subsystems, each service handling subsystem configured to handle service applications of the same or different service type;

[0142] The service handling system further comprises the service flow system as described above, which is configured to be in communication connection with the plurality of service handling subsystems.

[0143] Each service handling subsystem (such as the revenue system, the security check system, the work order system, etc.) focuses on the capability building in a specific service field, and some subsystems are designed to process a single service type (such as the security check system is specialized in the detection and maintenance of gas equipment), and some other subsystems have the ability to process multiple services (such as the work order system can handle maintenance, transfer, etc. at the same time), this mixed deployment mode of specialization + generalization not only guarantees the processing quality of core services, but also improves the utilization rate of system resources.

[0144] The service flow system as the central nervous system keeps real-time communication with all subsystems through standardized interfaces, dynamically maintains the adaptation relationship between service types and subsystems through the business-support system association table, continuously monitors the health status (normal / fault) of each subsystem through the state query module, automatically triggers service flow scheduling when the subsystem failure rate exceeds the threshold, and realizes intelligent distribution of service applications based on service type, load status, historical efficiency, and emergency degree, etc.

[0145] Each technical feature of the above embodiments can be combined arbitrarily, and to make the description concise, each technical feature in the above embodiments is not described in all possible combinations, however, as long as the combination of these technical features does not exist contradictory, it should be considered as the scope of the present application.

[0146] The above embodiments only express several implementation manners of the present application, and the description is more specific and detailed, but it should not be understood as a limitation on the scope of the patent of the present application. It should be noted that for ordinary skilled in the art, without departing from the concept of the present application, some modifications and improvements can be made, which are all within the protection scope of the present application. Therefore, the protection scope of the present application should be subject to the appended claims.

Claims

1. A business workflow system, applied on the server side, characterized in that, The business workflow system is configured to communicate with multiple different business processing systems, and the business workflow system includes: The service application receiving module is configured to receive service applications sent by clients; The business application allocation module is configured to extract the business type of the business application, query a preset business-support system association lookup table, obtain at least one candidate business processing system that is compatible with the business type, and select one of the candidate business processing systems as the target business processing system based on the compatibility of each candidate business processing system with respect to the business type. The business application sending module is configured to send the business application to the target business processing system and trigger the target business processing system to process the business application; The business workflow system also includes: A data acquisition module, configured to collect at least two indicators from the candidate business processing system for evaluating system load status; A storage module configured to store a service-resource weight mapping table, the service-resource weight mapping table including a mapping relationship between any service type and the resource weights of at least two of the indicators; The business application allocation module is further configured to: based on the business type, obtain the resource weights of each indicator corresponding to the business type from the business-resource weight mapping table, and normalize the indicators based on the resource weights to obtain the system load status of the candidate business processing system; The business application allocation module comprehensively considers the system load status and the adaptability of the candidate business processing systems to the business type, and selects one of the candidate business processing systems as the target business processing system.

2. The business workflow system according to claim 1, characterized in that, The storage module also includes a business-weight coefficient mapping table, which includes a mapping relationship between any business type and the weight coefficients of different influencing factors. The influencing factors include a first influencing factor based on the adaptability, a second influencing factor based on the system load status, and a third influencing factor based on historical processing efficiency. The business application allocation module is further configured to: based on the business type of the business application, obtain the weight coefficients of each influencing factor through the business-weight coefficient mapping table, allocate the weights of the influencing factors according to the obtained weight coefficients, generate a comprehensive evaluation result of different candidate business processing systems for the business type, and select the candidate business processing system that makes the comprehensive evaluation result the largest as the target business processing system.

3. The business workflow system according to claim 2, characterized in that, The third influencing factor is configured to be positively correlated with the inverse of historical processing efficiency.

4. The business workflow system according to claim 3, characterized in that, The historical processing efficiency is configured as the ratio of the average processing time of the business type in the candidate business processing system to the current predicted processing time. The average processing time is obtained by statistically calculating the historical processing time data of the business type in the candidate business processing system. The current predicted processing time is obtained by using a time series prediction algorithm, combined with the current business queue length and system resource usage of the candidate business processing system.

5. The business workflow system according to claim 2, characterized in that, The second influencing factor is configured to be positively correlated with the inverse of the system load state.

6. The business workflow system according to claim 5, characterized in that, The storage module also includes a service-urgency mapping table, which includes the mapping relationship between different service types and service urgency levels; The second influencing factor is also configured to be positively correlated with the business urgency level.

7. The business workflow system according to claim 1, characterized in that, The business workflow system also includes: The status query module is configured to traverse and query the status of the candidate business processing system. When the candidate business processing system is detected to be in a normal state, the data acquisition module collects the indicators of the candidate business processing system. When the candidate business processing system is detected to be in a fault state, the candidate business processing system is marked as faulty, and the data acquisition module is controlled to skip collecting the indicators of the candidate business processing system and record the skip log.

8. The business workflow system according to claim 7, characterized in that, The status query module is further configured to mark the candidate business processing system as faulty when the data acquisition module fails to acquire any of the indicators of the candidate business processing system. The data acquisition module is further configured to: when the candidate business processing system is marked as faulty, calculate the system load status of the candidate business processing system based on the historical indicator data of the candidate business processing system within a specified time range and in combination with the resource weight.

9. A business processing system, characterized in that, The business processing system includes: Multiple business processing subsystems, each of which is configured to process business applications of the same or different business types; The business processing system further includes a business workflow system as described in any one of claims 1 to 8, wherein the business workflow system is configured to communicate with the plurality of business processing subsystems.

Images