A method and device for troubleshooting an order service line

Abstract

The embodiment of the present application provides a kind of order service line's trouble shooting positioning method and device, comprising: obtaining the flow state when order flows in service line;When flow state is converted across platform, obtain the authentication information for the cross-platform conversion of flow state;When flow state is not converted across platform, if the same flow state flows in multiple platforms, then disassemble the order processing logic inside platform, define corresponding flow substate;According to flow state, flow substate and authentication information, generate order state flow authentication table, so that troubleshooting personnel can locate the link that causes flow state stagnation on service line when flow state stagnates according to order state flow authentication table.The present application defines flow substate by disassembling the order processing logic inside platform, thereby refining order flow state granularity, and generating corresponding order state flow authentication table, so as to quickly and accurately locate the link that causes flow state abnormal stagnation, and shorten troubleshooting time.

Description

Technical Field

[0001] This invention relates to the field of computer technology, and in particular to a troubleshooting and location method for an order business line, a troubleshooting and location device for an order business line, an electronic device, and a computer-readable storage medium. Background Technology

[0002] With the continuous development of science and technology, current communication services are complex and diverse, and customers typically customize services through orders. An order consists of multiple stages. During cross-platform transfers within a complete business line, issues such as missing shared information can cause order status stagnation. In such cases, troubleshooting personnel need to quickly locate and resolve these anomalies to prevent prolonged order stagnation from degrading the user experience.

[0003] However, the granularity of order status defined by business rules is usually not sufficiently correlated with the processing stages of various platform services, making it difficult for troubleshooters to quickly and accurately locate the specific link where the problem is, resulting in a long troubleshooting time. Summary of the Invention

[0004] In view of the above problems, embodiments of the present invention are proposed to provide a troubleshooting and location method for an order business line, a troubleshooting and location device for an order business line, an electronic device, and a computer-readable storage medium to overcome or at least partially solve the above problems.

[0005] To address the aforementioned problems, this invention discloses a troubleshooting and location method for order processing lines, the method comprising:

[0006] Obtain the order flow status in the business line;

[0007] When the flow state undergoes a cross-platform conversion, the authentication information for the cross-platform conversion of the flow state is obtained;

[0008] When the flow state is not converted across platforms, if the same flow state flows between multiple service platforms, the order processing logic within the multiple service platforms is decomposed to obtain the order processing sub-logic corresponding to each of the multiple service platforms, and the flow state corresponding to the order processing sub-logic is defined.

[0009] Based on the order flow status, flow transfer status, and authentication information in the business line, an order status flow authentication table is generated so that troubleshooting personnel can locate the link in the business line that caused the flow status to stagnate when the flow status is stalled.

[0010] Optionally, when the transition state undergoes a cross-platform conversion, obtaining authentication information for the cross-platform conversion of the transition state includes:

[0011] When the flow state undergoes a cross-platform conversion, record the handover information required for the cross-platform conversion of the flow state;

[0012] Based on the handover information and the state transition authentication rules, a state transition authentication rule attribute table is generated; the state transition authentication rules are used to indicate the cross-platform conversion authentication stage that requires the handover information.

[0013] Optionally, after obtaining the order flow status in the business line, the method further includes:

[0014] Map the flow status to the service platform that processes the business function corresponding to the flow status, and determine the service platform corresponding to the flow status;

[0015] Map the transition logic between the flow states to the service platform that executes the transition logic, and determine the service platform corresponding to the transition logic;

[0016] The service platform corresponding to the flow status is integrated with the service platform corresponding to the conversion logic to obtain the mapping relationship between order status flow and service platform;

[0017] During the transition of the order flow status, the service platforms corresponding to the order flow status before the transition and the order flow status after the transition are different, based on the mapping relationship, so as to determine whether the flow status needs to be transitioned across platforms.

[0018] Optionally, generating an order status flow authentication table based on the order flow status, flow transfer status, and authentication information in the business line includes:

[0019] The circulation state, the circulation rotor state, and the service platform corresponding to the state are encoded and registered to obtain the circulation state code, the service platform code corresponding to the circulation state, the circulation rotor state code, and the service platform code corresponding to the circulation rotor state.

[0020] Based on the flow status code, the service platform code corresponding to the flow status, the flow rotor status code, the service platform code corresponding to the flow rotor status, the status flow authentication rule number, and the next flow status code, an order status flow authentication table is generated.

[0021] Optionally, after generating the order status flow authentication table based on the order flow status, flow transfer status, and authentication information in the business line, the method further includes:

[0022] When the flow status is stagnant, the abnormal status of abnormal orders in the business line is obtained so that troubleshooting personnel can find the responsible platform corresponding to the abnormal status from the order status flow authentication table.

[0023] Optionally, it also includes:

[0024] When the order processing logic within the service platform changes, the attribute table of the flow authentication rules is adjusted.

[0025] This invention also discloses a troubleshooting and location device for order processing lines, the device comprising:

[0026] The acquisition module is used to acquire the order transfer status in the business line.

[0027] The recording module is used to obtain authentication information for the cross-platform conversion of the flow state when the flow state undergoes cross-platform conversion;

[0028] The decomposition module is used to decompose the order processing logic within the multiple service platforms when the same flow state is not converted across platforms, so as to obtain the order processing sub-logic corresponding to each of the multiple service platforms, and define the flow state corresponding to the order processing sub-logic.

[0029] The generation module is used to generate an order status flow authentication table based on the order flow status, flow transfer status and authentication information in the business line, so that when the flow status is stuck, troubleshooting personnel can locate the link in the business line that caused the flow status to be stuck based on the order status flow authentication table.

[0030] Optionally, the recording module includes:

[0031] The handover information acquisition submodule is used to record the handover information required for the cross-platform conversion of the flow state when the flow state undergoes cross-platform conversion;

[0032] The attribute table generation submodule is used to generate a transition authentication rule attribute table based on the handover information and the state transition authentication rules; the state transition authentication rules are used to indicate the cross-platform transition authentication stage that requires the handover information.

[0033] Optionally, after obtaining the order flow status in the business line, the method further includes:

[0034] The first mapping module is used to map the flow state to the service platform that processes the business function corresponding to the flow state, and to determine the service platform corresponding to the flow state.

[0035] The second mapping module is used to map the conversion logic between the flow states to the service platform that executes the conversion logic, and to determine the service platform corresponding to the conversion logic;

[0036] The integration module is used to integrate the service platform corresponding to the flow status with the service platform corresponding to the conversion logic to obtain the mapping relationship between order status flow and service platform;

[0037] The cross-platform conversion judgment module is used to determine, based on the mapping relationship, whether the service platforms corresponding to the order flow status before the conversion and the order flow status after the conversion are different when the flow status is converted, so as to determine whether the flow status needs to be converted across platforms.

[0038] Optionally, the generation module includes:

[0039] The encoding registration submodule is used to encode and register the circulation state, the circulation rotor state, and the service platform corresponding to the state, to obtain the circulation state code, the service platform code corresponding to the circulation state, the circulation rotor state code, and the service platform code corresponding to the circulation rotor state.

[0040] The authentication table generation submodule is used to generate an order status flow authentication table based on the flow status code, the service platform code corresponding to the flow status, the flow rotor status code, the service platform code corresponding to the flow rotor status, the status flow authentication rule number, and the next flow status code.

[0041] Optionally, after generating the order status flow authentication table based on the order flow status, flow transfer status, and authentication information in the business line, the method further includes:

[0042] The abnormal status acquisition module is used to acquire the abnormal status of abnormal orders in the business line when the flow status is stagnant, so that troubleshooting personnel can find the responsible platform corresponding to the abnormal status from the order status flow authentication table.

[0043] Optionally, it also includes:

[0044] The attribute table adjustment module is used to adjust the attribute table of the flow authentication rules when the order processing logic inside the service platform changes.

[0045] This invention also discloses an electronic device, including: a processor, a memory, and a computer program stored in the memory and capable of running on the processor. When the computer program is executed by the processor, it implements the steps of the troubleshooting and location method for the order business line as described above.

[0046] This invention also discloses a computer-readable storage medium storing a computer program, which, when executed by a processor, implements the steps of the troubleshooting and location method for the order business line as described above.

[0047] The embodiments of the present invention have the following advantages:

[0048] In this embodiment of the invention, the flow status of orders in the business line can be obtained first. When the flow status is converted across platforms, the authentication information for the cross-platform conversion of the flow status is recorded. When the flow status is not converted across platforms, if the same flow status flows between multiple service platforms, the order processing logic within the service platform is decomposed, and the flow sub-state corresponding to the order processing sub-logic is defined. Finally, based on the flow status of orders in the business line, the flow sub-state, and the authentication information, an order status flow authentication table is generated. This invention decomposes the order processing logic within the service platform, defines corresponding flow rotor states, refines the granularity of order flow states, and generates a corresponding order status flow authentication table based on the order flow status, flow rotor states, and authentication information in the business line. This allows troubleshooters to perform production troubleshooting for internet order-related services based on the order status flow authentication table. When the flow status is abnormally stalled, the link causing the abnormal stall in the business line can be directly located based on the order status flow authentication table. This avoids the inability to quickly locate the problem link due to insufficient correlation between the order status granularity and the service processing stage of the service platform when the status is abnormally stalled, thus quickly locating the responsible platform corresponding to the problem status and shortening the troubleshooting time. Attached Figure Description

[0049] Figure 1 This is a flowchart illustrating the steps of a troubleshooting and location method for an order business line provided by an embodiment of the present invention;

[0050] Figure 2 This is a flowchart of another troubleshooting and location method for order business lines provided by an embodiment of the present invention;

[0051] Figure 3 This is a schematic diagram of an order flow status and corresponding service platform provided by an embodiment of the present invention;

[0052] Figure 4 This is a schematic diagram illustrating the mapping relationship between order status flow and service platform provided by an embodiment of the present invention;

[0053] Figure 5 This is a schematic diagram of a flow state and a flow rotor state provided in an embodiment of the present invention;

[0054] Figure 6This is a flowchart of an order troubleshooting method based on state transition authentication provided in an embodiment of the present invention;

[0055] Figure 7 This is a structural block diagram of a troubleshooting and positioning device for order business lines provided in an embodiment of the present invention. Detailed Implementation

[0056] To make the above-mentioned objects, features and advantages of the present invention more apparent and understandable, the present invention will be further described in detail below with reference to the accompanying drawings and specific embodiments.

[0057] When orders are transferred across platforms within a complete business line, issues can arise where the order status becomes stagnant and timeouts due to a lack of shared information. However, the granularity of order status defined by business rules is not sufficiently correlated with the processing stages of each platform's services, making it difficult for troubleshooters to quickly and accurately pinpoint the specific step where the problem occurs, resulting in lengthy troubleshooting times.

[0058] One of the core concepts of this invention is to decompose the order processing logic within the service platform, define corresponding flow rotor states, refine the granularity of order flow states, and generate a corresponding order status flow authentication table based on the order flow status, flow rotor states, and authentication information in the business line. This allows troubleshooters to perform production troubleshooting for internet order-related services based on the order status flow authentication table. When the flow status is abnormally stalled, the link causing the abnormal stall in the business line can be directly located based on the order status flow authentication table. This avoids the inability to quickly locate the problem link due to insufficient correlation between the order status granularity and the service processing stage of the service platform when the status is abnormally stalled, thereby quickly locating the responsible platform corresponding to the problem status and shortening the troubleshooting time.

[0059] Reference Figure 1 The diagram illustrates a flowchart of a troubleshooting and location method for an order business line according to an embodiment of the present invention. The method may specifically include the following steps:

[0060] Step 101: Obtain the order transfer status in the business line.

[0061] The troubleshooting and location method for order business lines in this invention can be applied to a server. The server can obtain the flow status of orders during the business line's transfer and determine whether the transition of the flow status is a cross-platform transition, thereby determining whether order information is being transferred between service platforms. When the flow status undergoes a cross-platform transition, the cross-platform transition authentication information for the order's flow status can be recorded, which can then be used to design authentication for order information transfer between service platforms. When the same flow status flows between multiple service platforms, the order processing logic within each service platform can be decomposed, and corresponding platform-internal sub-states can be defined. Based on the main state involved in the order flow, the service platform-internal sub-states, and the authentication information, an order status flow authentication table can be generated. This allows troubleshooters to locate the link causing the flow status stagnation in the business line when the order flow status is abnormally halted during production troubleshooting monitoring of the internet order business line, thereby quickly locating the responsible platform corresponding to the problematic state and shortening troubleshooting time.

[0062] Orders from different business lines have different flow states and use different service platforms during the production process. In this embodiment of the invention, the server can obtain the flow state of orders in multiple parallel business lines and determine whether the flow state of orders in each business line has undergone cross-platform conversion. For example, the server can simultaneously obtain the flow state 'a' of orders in business line A and the flow state 'b' of orders in business line B.

[0063] In practical applications, the troubleshooting and location method for order business lines according to embodiments of the present invention can be applied to various application scenarios. In one example, it can be applied to the health maintenance of order processing services such as internet SIM cards, data packages, and benefits; in another example, it can be applied to optimizing the completion rate of a large number of concentrated orders submitted by users in short periods during online live streaming or other activities; in yet another example, it can be applied to the maintenance of order conversion between the central distribution center and provincial distribution centers; and in yet another example, it can be applied to troubleshooting problematic orders when business opportunity orders are pushed between operators and partners. Those skilled in the art should understand that the above application scenarios are merely examples of the present invention, and they can apply this troubleshooting and location method for order business lines to other scenarios in practical applications.

[0064] Step 102: When the flow state undergoes cross-platform conversion, obtain the authentication information for the cross-platform conversion of the flow state.

[0065] Authentication information can refer to information used to authenticate cross-platform status transitions during order processing. In this embodiment of the invention, within a complete order-related business line, when changes in order processing status involve service platforms responsible for different business functions, authentication information for cross-platform status transitions can be recorded.

[0066] Step 103: When the flow state is not converted across platforms, if the same flow state flows between multiple service platforms, the order processing logic within the multiple service platforms is decomposed to obtain the order processing sub-logic corresponding to each of the multiple service platforms, and the flow state corresponding to the order processing sub-logic is defined.

[0067] In this embodiment of the invention, after determining whether the order flow status in each business line has undergone cross-platform conversion, if the flow status has not undergone cross-platform conversion, it can be determined whether the same flow status flows between multiple service platforms. If the same flow status flows between multiple service platforms, the order processing logic within the service platform can be decomposed, and corresponding sub-states within the service platform can be defined.

[0068] Specifically, if the same flow state flows between multiple service platforms, the order processing logic within each service platform can be decomposed to obtain the corresponding order processing sub-logic for each service platform, and the corresponding flow rotor state can be defined. For example, if flow state a flows between service platform M and service platform N, the order processing logic corresponding to flow state a within service platforms M and N can be decomposed, and flow rotor state a1 corresponding to the order processing sub-logic within service platform M can be defined, and flow rotor state a2 corresponding to the order processing sub-logic within service platform N can be defined. The parent state of flow rotor states a1 and a2 can be flow state a.

[0069] Step 104: Generate an order status flow authentication table based on the order flow status, flow transfer status, and authentication information in the business line, so that troubleshooting personnel can locate the link in the business line that caused the flow status to stagnate when the flow status is stalled.

[0070] By generating an order status flow authentication table based on the order flow status, sub-flow status, and authentication information within the same business line, a data structure for status flow monitoring can be designed for the main status and sub-status within the service platform involved in order flow. This allows troubleshooters to pinpoint the link causing the flow status stagnation in the business line when an order flow status abnormally stops during troubleshooting monitoring of each order business line, thereby quickly locating the responsible platform corresponding to the problematic status.

[0071] In this embodiment of the invention, the flow status of orders in the business line can be obtained first. When the flow status is converted across platforms, the authentication information for the cross-platform conversion of the flow status is recorded. When the flow status is not converted across platforms, if the same flow status flows between multiple service platforms, the order processing logic within the service platform is decomposed, and the flow sub-state corresponding to the order processing sub-logic is defined. Finally, based on the flow status of orders in the business line, the flow sub-state, and the authentication information, an order status flow authentication table is generated. This invention decomposes the order processing logic within the service platform, defines corresponding flow rotor states, refines the granularity of order flow states, and generates a corresponding order status flow authentication table based on the order flow status, flow rotor states, and authentication information in the business line. This allows troubleshooters to perform production troubleshooting for internet order-related services based on the order status flow authentication table. When the flow status is abnormally stalled, the link causing the abnormal stall in the business line can be directly located based on the order status flow authentication table. This avoids the inability to quickly locate the problem link due to insufficient correlation between the order status granularity and the service processing stage of the service platform when the status is abnormally stalled, thus quickly locating the responsible platform corresponding to the problem status and shortening the troubleshooting time.

[0072] Reference Figure 2 The diagram illustrates a flowchart of another troubleshooting and location method for order business lines provided by an embodiment of the present invention. The method may specifically include the following steps:

[0073] Step 201: Obtain the order transfer status in the business line.

[0074] In an optional embodiment, after obtaining the order flow status in the business line, the method may further include: mapping the flow status to a service platform that processes the business function corresponding to the flow status, and determining the service platform corresponding to the flow status; mapping the conversion logic between the flow states to a service platform that executes the conversion logic, and determining the service platform corresponding to the conversion logic; integrating the service platform corresponding to the flow status and the service platform corresponding to the conversion logic to obtain a mapping relationship between order status flow and service platforms; and when the flow status is converted, determining whether the service platforms corresponding to the order flow status before the conversion and the order flow status after the conversion are different based on the mapping relationship, so as to determine whether the flow status is converted across platforms.

[0075] When an order is transferred to the service platform that processes the business function, the order's transfer status changes accordingly. After obtaining the transfer status of an order within the business line, the transfer status can be mapped to the service platform that processes the corresponding business function to determine the service platform corresponding to that transfer status. For example, refer to... Figure 3 This diagram illustrates the order flow status and corresponding service platforms according to an embodiment of the present invention. As shown, in a complete order-related business line, service platform M is responsible for obtaining user-submitted information and generating an order; service platform N is responsible for various internal system audits such as qualification verification and security verification; service platform O is responsible for verifying the order and shipping the goods; and service platform P is responsible for activating the transaction completion feedback upon user receipt of goods. Specifically, flow status a can be mapped to service platform M, where service platform M is the service platform corresponding to flow status a; flow status b can be mapped to service platform N, where service platform N is the service platform corresponding to flow status b; flow status c can be mapped to service platform O, where service platform O is the service platform corresponding to flow status c; and flow status d can be mapped to service platform P, where service platform P is the service platform corresponding to flow status d.

[0076] Orders from different business lines have different flow states and use different service platforms during the production process. Within a business line, the transition logic between flow states can be mapped to the service platform that executes that transition logic, thus determining the corresponding service platform. For example, the service platform corresponding to the transition logic from flow state a to flow state b can be service platform M, and the service platform corresponding to the transition logic from flow state b to flow state c can be service platform N.

[0077] In this embodiment of the invention, the service platform corresponding to the flow status can be integrated with the service platform corresponding to the conversion logic to obtain the mapping relationship between order status flow and service platforms. To enable those skilled in the art to better understand the mapping relationship between order status flow and service platforms, an example is provided below.

[0078] Reference Figure 4This diagram illustrates the mapping relationship between order status transitions and service platforms, as provided in an embodiment of the present invention. As shown, a transition status can correspond to at least one service platform. The platform to which the "Payment Successful" status S10101 belongs (i.e., the service platform corresponding to this status) can be access platform X101; the platform to which the "System Approved Order" status S10102 belongs can be access platform X101; the platform to which the "Identity Information Verification" status S20101 belongs can be security platform Y201; the platform to which the "Shipped" status S30101 belongs can be production platform Z301 and logistics platform W401; and the platform to which the "Transaction Completed" status S40101 belongs can be reporting platform A501. The transition logic from state S10101 to state S10102 can belong to access platform X101 (both states belong to the same platform), the transition logic from state S10102 to state S20101 can belong to security platform Y201 (only state S10102 belongs to the platform), the transition logic from state S20101 to state S30101 can belong to production platform Z301, and the transition logic from state S30101 to state S40101 can belong to reporting platform A501. There are two cases where the transition logic between two flow states is assigned to the service platform.

[0079] Step 202: When the flow state undergoes cross-platform conversion, obtain the handover information required for the cross-platform conversion of the flow state.

[0080] Handover information refers to order information that the current service platform needs to transfer to the next service platform during the order process. For example, handover information may include delivery address information, user identity information, etc.

[0081] In this embodiment of the invention, when the flow status is changed across platforms, the handover information required for the cross-platform change of the flow status can be recorded, thereby designing the authentication of order information transmission between service platforms. When an abnormal order is stuck in a state, the cross-platform change of the order status can be authenticated. By recording and verifying the handover information required for the cross-platform change of the flow status of abnormal orders, the processing link that causes the order status to be stuck can be quickly and accurately located.

[0082] Step 203: Generate a state transition authentication rule attribute table based on the handover information and the state transition authentication rules; the state transition authentication rules are used to represent the cross-platform conversion authentication stage that requires the handover information.

[0083] In this embodiment of the invention, when the flow status undergoes a cross-platform transition, the handover information required for the cross-platform transition can be recorded. A flow authentication rule attribute table is generated based on the handover information and the status flow authentication rules, thereby designing authentication for order information transmission between service platforms. When an abnormal order experiences a status stagnation, the handover information of the abnormal order can be verified based on the flow authentication rule attribute table, thereby authenticating the cross-platform status changes during the flow of the abnormal order. This not only allows for quick and accurate location of the processing stage causing the order status stagnation but also makes the internal order processing flow of each platform visible to troubleshooting personnel, improving the accuracy of problem descriptions in troubleshooting feedback.

[0084] Step 204: When the flow state is not converted across platforms, if the same flow state flows between multiple service platforms, the order processing logic within the multiple service platforms is decomposed to obtain the order processing sub-logic corresponding to each of the multiple service platforms, and the flow state corresponding to the order processing sub-logic is defined.

[0085] Reference Figure 5 The figure illustrates a schematic diagram of a flow state and a flow rotor state provided by an embodiment of the present invention. As shown in the figure, the "shipped" state flows between the production platform and the logistics platform. This allows for the decomposition of the order processing logic within the production platform and the service platform, and the definition of corresponding flow rotor states "out of warehouse" and "in delivery". The service platform corresponding to the "out of warehouse" flow rotor state US30102 can be the production platform, and the service platform corresponding to the "in delivery" flow rotor state US30103 can be the logistics platform.

[0086] Step 205: Generate an order status flow authentication table based on the order flow status, flow transfer status, and authentication information in the business line, so that troubleshooting personnel can locate the link in the business line that caused the flow status to stagnate when the flow status is stalled.

[0087] In an optional embodiment, step 205 may include the following sub-steps:

[0088] The circulation state, the circulation rotor state, and the corresponding service platform are encoded and registered to obtain the circulation state code, the service platform code corresponding to the circulation state, the circulation rotor state code, and the service platform code corresponding to the circulation rotor state.

[0089] Based on the flow status code, the service platform code corresponding to the flow status, the flow rotor status code, the service platform code corresponding to the flow rotor status, the status flow authentication rule number, and the next flow status code, an order status flow authentication table is generated.

[0090] In this embodiment of the invention, after dividing and encoding the order processing stages within each platform into sub-states and storing them, authentication rules and data structures for cross-platform order handover can be designed, thereby obtaining an order status transition authentication table. Referring to Table 1, an order status transition authentication table is provided in this embodiment of the invention. The order status transition authentication table may include information such as the current status code, current status name, belonging platform name (i.e., the service platform name corresponding to the status), transition authentication rule number, parent status code, and next transition status code.

[0091]

[0092] Table 1

[0093] In this embodiment of the invention, the user of the order status flow authentication table can be a troubleshooter. The troubleshooter can obtain and combine the real-time status of the order to locate abnormal problems. The troubleshooting team can be responsible for maintaining the data consistency between the main flow status and the order business line process, and between the sub-status and the logical processing within the platform.

[0094] In this embodiment of the invention, after generating the order status flow authentication table, the contact information of the troubleshooting contact person and basic emergency handling plan can be associated with each flow status of the order. Troubleshooting monitoring can be configured according to the complete flow status of the orders in the business line, and an alarm can be triggered when the order status is stagnant. By generating the order status flow authentication table, order flow monitoring specifications for parallel business line processes can be formulated and associated with troubleshooting handling plans. Order troubleshooting is located based on status flow authentication, integrating the main flow status of orders from various business lines and the functional responsibilities of each service platform. This can form an order business monitoring and emergency handling system centered on troubleshooting work, thereby providing troubleshooters with emergency strategies associated with the located abnormal order status.

[0095] Reference Figure 6This is a flowchart illustrating an order troubleshooting method based on state transition authentication, provided by an embodiment of the present invention. First, the flow status of each business line and its various order types is statistically analyzed. Then, all order statuses within the same business line are mapped to corresponding service platforms, and it is determined whether the flow status transition involves platform handover. If the two flow statuses correspond to two different platforms, an authentication mechanism for order information transfer between platforms is designed. If the two flow statuses do not correspond to two different platforms, it is determined whether the same flow status involves multiple platforms. If the same flow status involves multiple platforms, the order processing logic within each platform is decomposed, and corresponding platform-internal sub-states are defined. Finally, a data structure for state transition monitoring is designed for the main state and platform-internal sub-states involved in the order flow, thus creating an order state transition authentication table. After generating the order state transition authentication table, contact information for troubleshooting personnel and basic emergency handling plans can be associated with each order flow status. Troubleshooting monitoring can also be configured based on the complete flow status of orders within a business line, with timeout alarms triggered when an order status stagnates.

[0096] In an optional embodiment, after generating the order status flow authentication table based on the order flow status, flow transfer status and authentication information in the business line, it may further include: when the flow status is stagnant, obtaining the abnormal status of abnormal order flow in the business line, so that troubleshooting personnel can find the responsible platform corresponding to the abnormal status from the order status flow authentication table.

[0097] When handing over work tasks, it is necessary to confirm whether the work required for the current status of the order can be reasonably completed based on the completeness of the existing order information. In a complete order-related business line, issues such as incomplete order information submitted by users or failure of the service platform to hand over the required order information to the next service platform may cause the order status to stagnate. In this embodiment of the invention, when the flow status is stagnant, the abnormal status of the abnormal order can be obtained so that troubleshooting personnel can find the responsible platform for the abnormal status and troubleshoot. For example, if the main information contained in the generated order, such as the user's identity information, is missing before the transition from status a to status b, and the security audit fails, then the authentication of the order flow from status A to status B will fail, and the service platform corresponding to status a will be identified as the responsible platform. If the address in the order information is at the provincial and municipal levels before the transition from status b to status c, but the delivery needs to be accurate to the provincial, municipal, and district levels, then the authentication of the order flow from status b to status c will fail, and the service platform corresponding to status c will be identified as the responsible platform.

[0098] In another example, such as Figure 5As shown, both the "Payment Successful" and "System Review Order" states flow within the access platform. The conversion from "Payment Successful" to "System Review Order" is completed within the access platform, so there is no need to pay special attention to the authentication process between these two states. If issues arise such as missing order information required for the "System Review Order" state or timeouts in the "Payment Successful" state, troubleshooting can be directly located on the access platform.

[0099] In an optional embodiment, the method may further include: adjusting the flow authentication rule attribute table when the order processing logic within the service platform changes.

[0100] Specifically, when the service platform makes logical adjustments related to order status, the flow authentication rules need to be adjusted accordingly. When adjusting the order status logic, corresponding extended attributes can be added, resulting in a flow authentication rule extended attribute table. Referring to Table 2, a flow authentication extended attribute table is provided in an embodiment of the present invention.

[0101]

[0102] Table 2

[0103] After platform services are regularly upgraded due to business needs, troubleshooting personnel may be unable to obtain information on changes in the order processing logic in a timely manner. This leads to increased time consumption in handling new anomalies and affects the order recovery rate. In this embodiment of the invention, when the order processing logic within the service platform changes, the flow authentication rule attribute table can be adjusted to add corresponding extended attributes. Based on the adjusted flow authentication rule attribute table, the processing link causing the order status to stagnate can be quickly located, reducing the time spent handling new anomalies and avoiding impact on the order recovery rate.

[0104] In this embodiment of the invention, the mapping relationship between the order flow status of different business lines and the service platform helps to improve the efficiency of adjusting new business requirements.

[0105] In this embodiment of the invention, by integrating the mapping relationship between the flow status and the service platform, the flow status of orders in the business line and the service platforms involved can be mapped and structured for storage. Combined with the production order status information obtained from troubleshooting, the responsible platform corresponding to the problem status can be located. This can reduce the workload of troubleshooting personnel in dealing with a large number of abnormal orders or orders with tight deadlines, clarify the responsible platform, and shorten the troubleshooting time.

[0106] In this embodiment of the invention, by dividing and encoding the order processing links within each platform into sub-states and storing them, and generating an order status flow authentication table, it is possible to design status flow authentication rules and data structures for the main state and sub-states within the platform involved in the order flow, thereby realizing the problem location and tracking of abnormal orders on different service platforms in troubleshooting work. This enables the troubleshooting platform to play an intermediate supervisory role in helping each service platform clarify its respective responsibilities and reduce flow anomalies caused by the lack or non-standardization of relevant information required for status changes during interactions between different platforms.

[0107] In this embodiment of the invention, after generating the order status flow authentication table, the contact information of the troubleshooting contact person and basic emergency handling plan can be associated with each flow status of the order. Troubleshooting monitoring can be configured according to the complete flow status of the orders in the business line, and an alarm can be triggered when the order status is stagnant. By generating the order status flow authentication table, order flow monitoring specifications for parallel business line processes can be formulated and associated with troubleshooting handling plans. Order troubleshooting is located based on status flow authentication, integrating the main flow status of orders from various business lines and the functional responsibilities of each service platform. This can form an order business monitoring and emergency handling system centered on troubleshooting work, thereby providing troubleshooters with emergency strategies associated with the located abnormal order status.

[0108] In this embodiment of the invention, the flow status of orders in the business line can be obtained first. When the flow status is converted across platforms, the authentication information for the cross-platform conversion of the flow status is recorded. When the flow status is not converted across platforms, if the same flow status flows between multiple service platforms, the order processing logic within the service platform is decomposed, and the flow sub-state corresponding to the order processing sub-logic is defined. Finally, based on the flow status of orders in the business line, the flow sub-state, and the authentication information, an order status flow authentication table is generated. This invention decomposes the order processing logic within the service platform, defines corresponding flow rotor states, refines the granularity of order flow states, and generates a corresponding order status flow authentication table based on the order flow status, flow rotor states, and authentication information in the business line. This allows troubleshooters to perform production troubleshooting for internet order-related services based on the order status flow authentication table. When the flow status is abnormally stalled, the link causing the abnormal stall in the business line can be directly located based on the order status flow authentication table. This avoids the inability to quickly locate the problem link due to insufficient correlation between the order status granularity and the service processing stage of the service platform when the status is abnormally stalled, thus quickly locating the responsible platform corresponding to the problem status and shortening the troubleshooting time.

[0109] It should be noted that, for the sake of simplicity, the method embodiments are all described as a series of actions. However, those skilled in the art should understand that the embodiments of the present invention are not limited to the described order of actions, because according to the embodiments of the present invention, some steps can be performed in other orders or simultaneously. Furthermore, those skilled in the art should also understand that the embodiments described in the specification are preferred embodiments, and the actions involved are not necessarily essential to the embodiments of the present invention.

[0110] Reference Figure 7 The diagram illustrates a structural block diagram of a troubleshooting and positioning device for an order business line according to an embodiment of the present invention, which may specifically include the following modules:

[0111] The acquisition module 701 is used to acquire the flow status of orders during the flow of the business line;

[0112] The recording module 702 is used to obtain authentication information for the cross-platform conversion of the flow state when the flow state undergoes cross-platform conversion;

[0113] The disassembly module 703 is used to disassemble the order processing logic within the multiple service platforms when the flow state is not converted across platforms, if the same flow state flows between multiple service platforms, to obtain the order processing sub-logic corresponding to each of the multiple service platforms, and to define the flow state corresponding to the order processing sub-logic.

[0114] The generation module 704 is used to generate an order status flow authentication table based on the order flow status, flow transfer status and authentication information in the business line, so that when the flow status is stagnant, troubleshooting personnel can locate the link in the business line that caused the flow status stagnation based on the order status flow authentication table.

[0115] In one optional embodiment, the recording module includes:

[0116] The handover information acquisition submodule is used to record the handover information required for the cross-platform conversion of the flow state when the flow state undergoes cross-platform conversion;

[0117] The attribute table generation submodule is used to generate a transition authentication rule attribute table based on the handover information and the state transition authentication rules; the state transition authentication rules are used to indicate the cross-platform transition authentication stage that requires the handover information.

[0118] In an optional embodiment, after obtaining the order flow status in the business line, the method further includes:

[0119] The first mapping module is used to map the flow state to the service platform that processes the business function corresponding to the flow state, and to determine the service platform corresponding to the flow state.

[0120] The second mapping module is used to map the conversion logic between the flow states to the service platform that executes the conversion logic, and to determine the service platform corresponding to the conversion logic;

[0121] The integration module is used to integrate the service platform corresponding to the flow status with the service platform corresponding to the conversion logic to obtain the mapping relationship between order status flow and service platform;

[0122] The cross-platform conversion judgment module is used to determine, based on the mapping relationship, whether the service platforms corresponding to the order flow status before the conversion and the order flow status after the conversion are different when the flow status is converted, so as to determine whether the flow status needs to be converted across platforms.

[0123] In one optional embodiment, the generation module includes:

[0124] The encoding registration submodule is used to encode and register the circulation state, the circulation rotor state, and the service platform corresponding to the state, to obtain the circulation state code, the service platform code corresponding to the circulation state, the circulation rotor state code, and the service platform code corresponding to the circulation rotor state.

[0125] The authentication table generation submodule is used to generate an order status flow authentication table based on the flow status code, the service platform code corresponding to the flow status, the flow rotor status code, the service platform code corresponding to the flow rotor status, the status flow authentication rule number, and the next flow status code.

[0126] In an optional embodiment, after generating the order status flow authentication table based on the order flow status, flow transfer status, and authentication information in the business line, the method further includes:

[0127] The abnormal status acquisition module is used to acquire the abnormal status of abnormal orders in the business line when the flow status is stagnant, so that troubleshooting personnel can find the responsible platform corresponding to the abnormal status from the order status flow authentication table.

[0128] In an optional embodiment, it further includes:

[0129] The attribute table adjustment module is used to adjust the attribute table of the flow authentication rules when the order processing logic inside the service platform changes.

[0130] In this embodiment of the invention, the flow status of orders in the business line can be obtained first. When the flow status is converted across platforms, the authentication information for the cross-platform conversion of the flow status is recorded. When the flow status is not converted across platforms, if the same flow status flows between multiple service platforms, the order processing logic within the service platform is decomposed, and the flow sub-state corresponding to the order processing sub-logic is defined. Finally, based on the flow status of orders in the business line, the flow sub-state, and the authentication information, an order status flow authentication table is generated. This invention decomposes the order processing logic within the service platform, defines corresponding flow rotor states, refines the granularity of order flow states, and generates a corresponding order status flow authentication table based on the order flow status, flow rotor states, and authentication information in the business line. This allows troubleshooters to perform production troubleshooting for internet order-related services based on the order status flow authentication table. When the flow status is abnormally stalled, the link causing the abnormal stall in the business line can be directly located based on the order status flow authentication table. This avoids the inability to quickly locate the problem link due to insufficient correlation between the order status granularity and the service processing stage of the service platform when the status is abnormally stalled, thus quickly locating the responsible platform corresponding to the problem status and shortening the troubleshooting time.

[0131] As the device embodiment is basically similar to the method embodiment, the description is relatively simple, and relevant parts can be found in the description of the method embodiment.

[0132] This invention also provides an electronic device, comprising:

[0133] It includes a processor, a memory, and a computer program stored in the memory and capable of running on the processor. When the computer program is executed by the processor, it implements the various processes of the above-described troubleshooting and location method embodiments for the order business line and achieves the same technical effect. To avoid repetition, it will not be described again here.

[0134] This invention also provides a computer-readable storage medium storing a computer program. When the computer program is executed by a processor, it implements the various processes of the above-described troubleshooting and location method embodiments for order business lines and achieves the same technical effect. To avoid repetition, it will not be described again here.

[0135] The various embodiments in this specification are described in a progressive manner, with each embodiment focusing on the differences from other embodiments. The same or similar parts between the various embodiments can be referred to each other.

[0136] Those skilled in the art will understand that embodiments of the present invention can be provided as methods, apparatus, or computer program products. Therefore, embodiments of the present invention can take the form of entirely hardware embodiments, entirely software embodiments, or embodiments combining software and hardware aspects. Furthermore, embodiments of the present invention can take the form of computer program products implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0137] This invention is described with reference to flowchart illustrations and / or block diagrams of methods, terminal devices (systems), and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing terminal device to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing terminal device, generate instructions for implementing the flowchart illustrations and / or block diagrams. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0138] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing terminal device to operate in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0139] These computer program instructions can also be loaded onto a computer or other programmable data processing terminal equipment, causing a series of operational steps to be performed on the computer or other programmable terminal equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable terminal equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0140] Although preferred embodiments of the present invention have been described, those skilled in the art, upon learning the basic inventive concept, can make other changes and modifications to these embodiments. Therefore, the appended claims are intended to be interpreted as including the preferred embodiments as well as all changes and modifications falling within the scope of the embodiments of the present invention.

[0141] Finally, it should be noted that in this document, relational terms such as "first" and "second" are used only to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or terminal device that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or terminal device. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or terminal device that includes said element.

[0142] The present invention has provided a detailed description of a troubleshooting and location method and apparatus for order business lines. Specific examples have been used to illustrate the principles and implementation methods of the present invention. The description of the above embodiments is only for the purpose of helping to understand the method and core ideas of the present invention. At the same time, for those skilled in the art, there will be changes in the specific implementation methods and application scope based on the ideas of the present invention. Therefore, the content of this specification should not be construed as a limitation of the present invention.

Claims

1. A troubleshooting and location method for order processing lines, characterized in that, The method includes: Obtain the order flow status in the business line; When the flow state undergoes a cross-platform conversion, the authentication information for the cross-platform conversion of the flow state is obtained; When the flow state is not converted across platforms, if the same flow state flows between multiple service platforms, the order processing logic within the multiple service platforms is decomposed to obtain the order processing sub-logic corresponding to each of the multiple service platforms, and the flow state corresponding to the order processing sub-logic is defined. Based on the order flow status, flow transfer status, and authentication information in the business line, an order status flow authentication table is generated so that when the flow status is stalled, troubleshooting personnel can locate the link in the business line that caused the flow status stall based on the order status flow authentication table. When the transition state undergoes a cross-platform conversion, the authentication information for the cross-platform conversion of the transition state is obtained, including: When the flow state undergoes a cross-platform conversion, record the handover information required for the cross-platform conversion of the flow state; Based on the handover information and the state transition authentication rules, a state transition authentication rule attribute table is generated; the state transition authentication rules are used to indicate the cross-platform conversion authentication stage that requires the handover information.

2. The method according to claim 1, characterized in that, After obtaining the order flow status in the business line, the process further includes: Map the flow status to the service platform that processes the business function corresponding to the flow status, and determine the service platform corresponding to the flow status; Map the transition logic between the flow states to the service platform that executes the transition logic, and determine the service platform corresponding to the transition logic; The service platform corresponding to the flow status is integrated with the service platform corresponding to the conversion logic to obtain the mapping relationship between order status flow and service platform; During the transition of the order flow status, the service platforms corresponding to the order flow status before the transition and the order flow status after the transition are different, based on the mapping relationship, so as to determine whether the flow status needs to be transitioned across platforms.

3. The method according to claim 2, characterized in that, The step of generating an order status flow authentication table based on the order flow status, flow transfer status, and authentication information in the business line includes: The circulation state, the circulation rotor state, and the service platform corresponding to the state are encoded and registered to obtain the circulation state code, the service platform code corresponding to the circulation state, the circulation rotor state code, and the service platform code corresponding to the circulation rotor state. Based on the flow status code, the service platform code corresponding to the flow status, the flow rotor status code, the service platform code corresponding to the flow rotor status, the status flow authentication rule number, and the next flow status code, an order status flow authentication table is generated.

4. The method according to claim 1, characterized in that, After generating the order status flow authentication table based on the order flow status, flow transfer status, and authentication information in the business line, the method further includes: When the flow status is stagnant, the abnormal status of abnormal orders in the business line is obtained so that troubleshooting personnel can find the responsible platform corresponding to the abnormal status from the order status flow authentication table.

5. The method according to claim 1, characterized in that, Also includes: When the order processing logic within the service platform changes, the attribute table of the flow authentication rules is adjusted.

6. A troubleshooting and positioning device for order processing lines, characterized in that, The device includes: The acquisition module is used to acquire the order transfer status in the business line. The recording module is used to obtain authentication information for the cross-platform conversion of the flow state when the flow state undergoes cross-platform conversion; The decomposition module is used to decompose the order processing logic within the multiple service platforms when the same flow state is not converted across platforms, so as to obtain the order processing sub-logic corresponding to each of the multiple service platforms, and define the flow state corresponding to the order processing sub-logic. The generation module is used to generate an order status flow authentication table based on the order flow status, flow transfer status and authentication information in the business line, so that when the flow status is stuck, troubleshooting personnel can locate the link in the business line that caused the flow status to be stuck based on the order status flow authentication table. The recording module includes: The handover information acquisition submodule is used to record the handover information required for the cross-platform conversion of the flow state when the flow state undergoes cross-platform conversion; The attribute table generation submodule is used to generate a transition authentication rule attribute table based on the handover information and the state transition authentication rules; the state transition authentication rules are used to indicate the cross-platform transition authentication stage that requires the handover information.

7. An electronic device, characterized in that, include: A processor, a memory, and a computer program stored in the memory and capable of running on the processor, wherein the computer program, when executed by the processor, implements the steps of the troubleshooting and location method for an order business line as described in any one of claims 1-5.

8. A computer-readable storage medium, characterized in that, A computer program is stored on the computer-readable storage medium, which, when executed by a processor, implements the steps of the troubleshooting and location method for an order business line as described in any one of claims 1 to 5.

Images