Business processing method and apparatus, electronic device, and storage medium

Abstract

This application provides a service processing method, apparatus, electronic device, and storage medium. The method includes: receiving service processing information of a target service; determining execution flow information corresponding to the target service from an engine system based on the type of the target service represented by the service processing information, wherein the execution flow information is pre-stored in the engine system as service execution flow information, and the execution flow information includes the steps of: message parsing, key field verification, user information query, user quota assembly, response message assembly, and billing statement generation; determining the target execution step in the execution flow information based on the key fields and user information in the service processing information; and executing the target service according to the target execution step in the execution flow information. The method of this application increases the flexibility and efficiency of service processing.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to a service processing method, apparatus, electronic device and storage medium. Background Technology

[0002] The BOSS system is a platform for network operators to operate and manage integrated services. It mainly completes functions such as business, billing and accounting for 5G billing messages. All 5G messages are exchanged online via HTTP / 2. At the same time, CHF (Charging Function) also needs to have online message deduplication capabilities. 5G messages use JSON messages to store billing information.

[0003] In existing technologies, the 5G online billing message processing scenario involves the CHF network element receiving the converged billing Nchf message from the SMF, then sending the Nchf message to the home province BOSS system for processing. The CHF receives the Nchf response message from the BOSS system and sends it back to the SMF (Session Management Function). Simultaneously, the CDF (Collect Billing Information Function) generates a CDR (Call Detail Record). The service processing flow is fixed and follows predefined steps or rules. Typically, parameter switches control whether a certain service process is executed. When it is necessary to change the service processing steps, the code is redeveloped.

[0004] However, existing business processing methods suffer from a lack of flexibility, high costs, and low efficiency in specific business processing scenarios. Therefore, they are difficult to adapt to business complexity and cannot meet current business processing needs. Summary of the Invention

[0005] This application provides a business processing method, apparatus, electronic device, and storage medium to address the problems of lack of flexibility, high cost, low efficiency, difficulty in adapting to business complexity, and inability to meet current business processing needs in specific business processing scenarios.

[0006] Firstly, this application provides a business processing method, including:

[0007] Receive business processing information for the target service;

[0008] Based on the type of target business represented by the business processing information, the execution process information corresponding to the target business is determined from the engine system. The execution process information is the business execution process information pre-stored in the engine system. The execution process information includes the following steps: message parsing, key field verification, user information query, user quota assembly, response message assembly, and billing bill generation.

[0009] Based on the key fields and user information in the business processing information, determine the target execution steps in the execution process information;

[0010] Execute the target business based on the target execution steps in the execution process information.

[0011] In this embodiment of the application, the target execution steps in the execution flow information are determined based on key fields in the business processing information and user information, including:

[0012] Based on the key fields in the business processing information, perform key field validation in the execution process information to obtain the key field validation results;

[0013] Based on the user information in the business processing information, perform a user information query in the execution process information to obtain the information query results;

[0014] Based on the key field validation results and data query results, the target execution steps in the execution process information are determined.

[0015] In this embodiment of the application, the target execution steps in the execution process information are determined based on the key field verification results and data query results, including:

[0016] If the key field validation result indicates that the key field validation was successful and the data query result indicates that the query result was successful, then the message parsing, key field validation, user data query, user quota assembly, response message assembly, and billing bill generation are determined as the target execution steps.

[0017] If the key field validation result indicates that the key field validation was successful, and the data query result indicates that the query result failed, then the target execution steps are determined as message parsing, key field validation, user number segment query, user quota assembly, response message assembly, and billing bill generation.

[0018] In this embodiment of the application, the method further includes:

[0019] If the key field validation result indicates that the key field validation has failed, an exception message will be generated based on the key field validation result and displayed to the user.

[0020] In this embodiment of the application, the method further includes:

[0021] Determine the executed steps and the currently executing step in the execution process information;

[0022] Determine if the currently executing step is an end point step;

[0023] If the current execution step is the end point step, then the target execution step in the execution process information is determined based on the executed steps, the current execution step, the key fields in the business processing information, and the user information.

[0024] In this embodiment of the application, after determining whether the current execution step is an end point step, the method further includes:

[0025] If the current execution step is not the end point step, then execute the current execution step;

[0026] Based on the execution process information, determine the next execution step for the current execution step;

[0027] Execute the next execution step until the next execution step is the end point step. Based on the executed steps, the current execution step, the next execution step, the key fields in the business processing information, and the user information, determine the target execution step in the execution process information.

[0028] In this embodiment of the application, after executing the target business according to the target execution steps in the execution flow information, the method further includes:

[0029] Obtain the call detail records (CDRs) for the target service.

[0030] Store the call detail records (CDRs) and send them to the billing system for display.

[0031] Secondly, this application provides a business processing apparatus, comprising:

[0032] The receiving module is used to receive the business processing information of the target business.

[0033] The first determination module is used to determine the execution process information corresponding to the target business from the engine system based on the type of target business represented by the business processing information. The execution process information is the business execution process information pre-stored in the engine system, and the execution process information includes the following steps: message parsing, key field verification, user information query, user quota assembly, response message assembly, and billing bill generation.

[0034] The second determination module is used to determine the target execution steps in the execution process information based on the key fields in the business processing information and user information.

[0035] The execution module is used to execute the target business according to the target execution steps in the execution process information.

[0036] Thirdly, this application provides an electronic device, including: a processor, and a memory communicatively connected to the processor;

[0037] The memory stores the instructions that the computer executes;

[0038] The processor executes computer execution instructions stored in the memory to implement the business processing method of the embodiments of this application.

[0039] Fourthly, a computer-readable storage medium stores computer-executable instructions, which, when executed by a processor, are used to implement the business processing method of the embodiments of this application.

[0040] The business processing method, apparatus, electronic device, and storage medium provided in this application receive business processing information of a target business; based on the type of the target business represented by the business processing information, determine the execution flow information corresponding to the target business from the engine system. The execution flow information is pre-stored in the engine system and includes the following steps: message parsing, key field verification, user information query, user quota assembly, response message assembly, and billing statement generation. Based on the key fields and user information in the business processing information, determine the target execution steps in the execution flow information; and execute the target business according to the target execution steps in the execution flow information. This allows the determination of the execution flow information corresponding to the target business in the process engine based on the type of the target business, thus determining the target execution steps in the configured business execution flow information. Since the steps are determined based on the target business, and the target execution steps in the execution flow information are determined based on the key fields and user information in the business processing information, steps corresponding to the target business can be obtained. Therefore, the execution of steps and the execution order can be selected according to business requirements. Because a fixed business processing flow is not required, time and resources can be saved, thereby improving the efficiency of business processing and achieving the effect of meeting business complexity and current business processing needs in specific business processing scenarios. Attached Figure Description

[0041] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application.

[0042] Figure 1 This is a schematic diagram of the communication system architecture provided in the embodiments of this application;

[0043] Figure 2 A flowchart illustrating the business processing method provided in the embodiments of this application;

[0044] Figure 3 A flowchart illustrating another business processing method provided in an embodiment of this application;

[0045] Figure 4 This is a schematic diagram of the structure of the business processing apparatus provided in the embodiments of this application;

[0046] Figure 5 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application.

[0047] The accompanying drawings illustrate specific embodiments of this application, which will be described in more detail below. These drawings and descriptions are not intended to limit the scope of the concept in any way, but rather to illustrate the concept of this application to those skilled in the art through reference to particular embodiments. Detailed Implementation

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

[0049] In existing technologies, the communications industry typically uses BOSS systems for business processing. In traditional frameworks, 5G business processes are fixed, and parameter switches are usually used to control whether a certain business process is executed. If the order of steps needs to be changed or new business steps need to be added, a new set of code must be developed. With the code modified, all business functions must be retested. Therefore, this business processing method lacks flexibility in specific business processing scenarios, has high development costs and low efficiency, and is difficult to adapt to the complexity of business and meet the technical problems of business processing requirements.

[0050] To address the aforementioned issues, the business processing method, apparatus, electronic device, and storage medium provided in this application can, based on a process engine, receive business processing information of a target business, determine the type of the target business, and then determine the execution flow information corresponding to the target business in the process engine according to the type of the target business. This allows for the determination of the target execution steps in the configured business execution flow information. Furthermore, since the steps are determined based on the target business, and the steps corresponding to the target business are obtained from the target execution steps in the execution flow information, it is possible to select whether to execute the steps and the execution order of the steps according to business requirements. This enables business processing to be implemented according to business requirements, saving time and resources, thereby improving the efficiency of business processing and achieving the effect of meeting business complexity and current business processing needs in specific business processing scenarios.

[0051] The technical solution of this application and how the technical solution of this application solves the above-mentioned technical problems are described in detail below with specific embodiments. These specific embodiments can be combined with each other, and the same or similar concepts or processes may not be described again in some embodiments. The embodiments of this application will now be described with reference to the accompanying drawings.

[0052] The execution entity of the business processing method, apparatus, electronic device, and storage medium provided in this application embodiment can be a server. The server can be a computer, mobile phone, tablet, or other device. This embodiment does not impose any particular limitation on the implementation method of the execution entity, as long as the execution entity can receive the business processing information of the target business; determine the execution flow information corresponding to the target business from the engine system based on the type of the target business represented by the business processing information, wherein the execution flow information is business execution flow information pre-stored in the engine system, and the execution flow information includes the following steps: message parsing, key field verification, user information query, user quota assembly, response message assembly, and billing statement generation; determine the target execution steps in the execution flow information based on the key fields and user information in the business processing information; and execute the target business according to the target execution steps in the execution flow information.

[0053] First, let me explain the terms used in this application:

[0054] BOSS (Business & Operation Support System) refers to a system that parses business call records, generates detailed records and bills, and sends them to users for payment. It is divided into billing and settlement system, sales and accounting system, customer service system, and decision support system.

[0055] The business processing method provided in this application can be applied to Figure 1 The diagram shows a schematic of the communication system architecture. Figure 1 As shown, the communication system may include: a 5G CHF network element, a BOSS 5G message processing system, and a BOSS billing system. The BOSS 5G message processing layer may include a process engine, an HTTP / 2 service interface, a billing interface, and a call detail record (CDR) storage interface. In this embodiment, the service processing may include the BOSS 5G message processing system receiving request messages reported by the 5G CHF network element through an HTTP / 2 service, and applying process engine technology to complete the service process execution. The service process may refer to message parsing, key field verification, user information query, user number segment query, user access granting, user authentication, user quota capping, user quota assembly, response message assembly, and billing CDR generation, etc. The sequential relationship, execution status, and exception handling of the above process steps can all be configured and defined through the process engine. The standardized CDRs are then sent to the BOSS billing system through the billing interface, and the CDRs are backed up through the CDR storage interface.

[0056] Figure 2 This is a flowchart illustrating the business processing method provided in this embodiment. The executing entity of this method can be a server or other servers; this embodiment does not impose any special limitations here. Figure 2As shown, this method may include:

[0057] S201. Receive the service processing information of the target service.

[0058] The target service can refer to the service that the base station in the target area needs to perform. The target area can be any province. For example, in some embodiments, the service can be any communication service such as querying user information or generating billing details.

[0059] Business processing information can refer to business processing messages sent by network elements. These messages can be parsed to obtain basic information for completing subsequent business steps. For example, in some embodiments, if the message sent by the network element does not contain a number, the user information query step cannot be performed.

[0060] In some embodiments, the business processing information includes at least one set of processing information related to a target business.

[0061] S202. Based on the type of target business represented by the business processing information, determine the execution process information corresponding to the target business from the engine system. The execution process information is the business execution process information pre-stored in the engine system. The execution process information includes the following steps: message parsing, key field verification, user information query, user quota assembly, response message assembly, and billing bill generation.

[0062] The engine system can refer to a process engine system. The configuration template for this engine system can use a lightweight data exchange format, allowing configuration of business names and execution results, and configuring the process engine according to the execution flow information of the target business. In this embodiment, the process engine can use HTTP / 2 and JSON (JavaScript Object Notation) as application-layer serialization protocols.

[0063] The execution process information can refer to the steps and procedures that must be performed to complete the target business. For example, in this embodiment of the application, when the target business is to generate billing bills, the execution process information may include message parsing, key field verification, user information query, user quota assembly, response message assembly, and billing bill generation. The order of each step in the execution process information can be changed, but the order of the executed steps cannot be changed.

[0064] S203. Based on the key fields and user information in the business processing information, determine the target execution steps in the execution process information.

[0065] Among them, key fields can refer to the input fields obtained by parsing the service processing messages sent by the network element. If a key field is missing, the verification will fail and the steps involving the missing field cannot be completed in the subsequent service processing.

[0066] User data can refer to the data composed of basic user information in the service processing messages sent by the network element. It can include basic information such as user name, number, and location. Querying user data can obtain all the user's information. For example, in some embodiments, if the key fields are insufficient and it is not possible to query all the user's data, the user number range can be queried to obtain partial information of the user.

[0067] The target execution step can refer to the execution steps determined based on the execution process information. In this embodiment, when the target service is generating billing invoices, the execution order of billing invoice generation follows user data query, and the execution order of response message assembly follows user quota assembly. There are no specific requirements for the execution order of billing invoice generation and response message assembly. However, once the process engine determines the target execution step for the target service, this execution order is configured and cannot be changed. For example, in some embodiments, if the target service requirement is user quotas, where quotas can refer to quotas in the user center and system quotas, the need to configure a user data query step depends on the specific requirements of the target service. If the target region has no requirement regarding the source of the required quotas, the process engine can configure message parsing, key field validation, user quota assembly, and response message assembly when configuring the target execution step.

[0068] In this embodiment of the application, determining the target execution steps in the execution process information based on key fields and user information in the business processing information may include:

[0069] Based on the key fields in the business processing information, perform key field validation in the execution process information to obtain the key field validation results;

[0070] Based on the user information in the business processing information, perform a user information query in the execution process information to obtain the information query results;

[0071] Based on the key field validation results and data query results, the target execution steps in the execution process information are determined.

[0072] Among them, key field verification can refer to confirming that the input fields obtained by parsing the service processing message sent by the network element include all the information required for the steps involved in the target service in order to complete the subsequent steps. For example, in some embodiments, key field verification can refer to searching the registration list of devices that complete the service based on the service processing information. If the registration information of the steps in the service processing information exists in the registration list, the verification passes; otherwise, the verification fails, an error message is output, and the service processing process ends.

[0073] Based on the key field verification results and data query results, the target execution step in the execution process information can be determined to be the execution of subsequent target execution steps based on the obtained user data when both key field verification and data query are successful. In this embodiment, after the user data query is successful, subsequent steps can also be configured to allow user access, authenticate user, and cap user access.

[0074] In this embodiment of the application, determining the target execution step in the execution process information based on the key field verification results and data query results may include:

[0075] If the key field validation result indicates that the key field validation was successful and the data query result indicates that the query result was successful, then the message parsing, key field validation, user data query, user quota assembly, response message assembly, and billing bill generation are determined as the target execution steps.

[0076] If the key field validation result indicates that the key field validation was successful, and the data query result indicates that the query result failed, then the target execution steps are determined as message parsing, key field validation, user number segment query, user quota assembly, response message assembly, and billing bill generation.

[0077] The target execution step can refer to the executable step obtained after the key field verification is successful. The data query result will affect the configuration and execution of subsequent steps. In this embodiment of the application, the target service can be generated from billing bills. Therefore, the target execution step can include user data query or user number segment query, and the user data query result or user number segment query result is successful.

[0078] In some embodiments, the target execution steps may include message parsing, key field validation, and billing bill generation, that is, billing bill can be generated after the key field validation result is passed.

[0079] User number segment query refers to obtaining the first three digits of a user's mobile phone number, i.e., the network identification number, through message parsing. In this embodiment of the application, if the data query fails, the user's complete mobile phone number cannot be determined. The user's complete mobile phone number is generally 11 digits long, with the first to third digits being the network identification number, the fourth to seventh digits being the area code, and the eighth to eleventh digits being the user number.

[0080] In some embodiments, if both user information query and user number segment query fail, the response message sent to the network element is a failure message. The target execution steps can be message parsing, key field query, and response message assembly. Since the billing billing data transmission system cannot be obtained and there is no downstream transmission destination, the billing billing data generation step is not executed, nor can the user quota assembly step be executed.

[0081] In this embodiment of the application, the method may further include:

[0082] If the key field validation result indicates that the key field validation has failed, an exception message will be generated based on the key field validation result and displayed to the user.

[0083] Among them, failure of key field verification may refer to the existence of a business in the configured business steps that is not included in the registration list. The registration list may refer to the list of registration information of business steps that the system device can support. The abnormal prompt message may refer to the information of the unsupported target execution step. In the embodiments of this application, the abnormal prompt message may refer to the information of execution steps other than message parsing, key field verification, user information query, user quota assembly, response message assembly, and billing bill generation.

[0084] In this embodiment of the application, the method may further include:

[0085] Determine the executed steps and the currently executing step in the execution process information;

[0086] Determine if the currently executing step is an end point step;

[0087] If the current execution step is the end point step, then the target execution step in the execution process information is determined based on the executed steps, the current execution step, the key fields in the business processing information, and the user information.

[0088] Among them, determining the executed steps and the current executed steps in the execution process information can refer to confirming the current and executed steps during the execution process based on the execution process information configured in the process engine, and then determining the end point step based on the target business requirements.

[0089] The endpoint step can refer to the business processing information requirements that can be achieved by combining the current execution step and the previously executed steps to reach the target business. In this case, the current execution step is the result point step. In the embodiments of this application, the endpoint step can refer to the generation of billing bills.

[0090] Based on the executed steps, the current executed step, key fields in the business processing information, and user information, the target execution step in the execution process information can be determined. This can refer to configuring subsequent execution steps based on the execution results of the executed steps, whether they are successful or failed, until the next step is the end point step. At this point, the configuration process stops, and the currently determined step becomes the target execution step.

[0091] In this embodiment of the application, after determining whether the current execution step is an end point step, the method may further include:

[0092] If the current execution step is not the end point step, then execute the current execution step;

[0093] Based on the execution process information, determine the next execution step for the current execution step;

[0094] Execute the next execution step until the next execution step is the end point step. Based on the executed steps, the current execution step, the next execution step, the key fields in the business processing information, and the user information, determine the target execution step in the execution process information.

[0095] In this context, determining the next execution step can refer to deciding the next execution step based on the execution result of the current execution step when the current execution step is not the end point step. In this embodiment of the application, the current execution step can refer to user data query. If the execution result is a successful query, the next execution step can be billing bill generation. If the execution result is a failed query, the next execution step can be user number segment query.

[0096] S204. Execute the target business according to the target execution steps in the execution process information.

[0097] The execution of the target service may include the target execution steps to complete the target service, i.e., to complete the downstream requirements, and also includes the response to the network element, i.e. to return to the upstream. For example, in the embodiments of this application, when the billing bill generation step is completed, it can mean that the execution of the target service is partially completed. After the user quota assembly step and the response message assembly step are executed, the response message is fed back to the network element so that the network element can obtain the result of the service processing completion. Then the execution of the target service ends.

[0098] Based on the target execution steps in the execution process information, executing the target business can mean that the process engine first configures the target execution steps in the execution process information corresponding to the target business, and then executes the relevant steps according to the configuration results to complete the processing of the target business.

[0099] In this embodiment of the application, after executing the target business according to the target execution steps in the execution flow information, the method may further include:

[0100] Obtain the call detail records (CDRs) for the target service.

[0101] Store the call detail records (CDRs) and send them to the billing system for display.

[0102] Among them, storing call detail records (CDRs) can refer to backing up CDRs through the CDR storage interface, while sending CDRs to the billing system can refer to sending the standardized CDRs to the BOSS billing system through the billing interface.

[0103] The business processing method provided in this application embodiment can determine the execution process information corresponding to the target business in the process engine according to the type of the target business. It can determine the target execution steps in the configuration business execution process information. Since the steps are determined according to the target business, and the target execution steps in the execution process information are determined according to the key fields and user information in the business processing information, the steps corresponding to the target business can be obtained. Therefore, the execution of steps and the execution order of steps can be selected according to business needs. Since it does not need to follow a fixed business processing process, it can save time and resources, thereby improving the efficiency of business processing and achieving the effect of meeting the business complexity and current business processing needs in specific business processing scenarios.

[0104] Figure 3 A flowchart illustrating another business processing method provided in this application embodiment is shown below. Figure 3 As shown, the method includes:

[0105] S301, Load process engine configuration information.

[0106] Among them, the process engine configuration information can refer to the information on the business execution steps corresponding to the business needs of different regions.

[0107] S302. Verify whether the steps in the configuration are supported. If there are unsupported steps, output an error message and then end.

[0108] Among them, verifying whether the steps in the configuration are supported can mean that the registration information list contains all the registration information of the steps in the configuration. If there are unsupported steps, an error message will be output and the process will end. Alternatively, if steps outside the registration information list are configured, they cannot be executed after configuration.

[0109] S303. Execute the steps in the configuration, determine if it is the end point, if yes, end the execution process; otherwise, continue execution.

[0110] The execution process can refer to the steps required by the process engine to configure and execute the target business, and the end point of this process can be the target step represented by the business requirements.

[0111] S304. Determine the result of the execution steps. If the execution is successful, find the steps after the success; if the execution fails, find the steps after the failure.

[0112] In this case, if the execution is successful, the next step after success will be found; if the execution fails, the next step after failure will be found. This means that the execution result of the current step can indicate whether it is successful or failed. The execution data information obtained will be different, which will affect the configuration and execution of the next step.

[0113] S305. Repeatedly execute the found steps until the execution ends.

[0114] The process of repeatedly executing the found steps can refer to continuously executing the current step, determining whether the current step is the end point, and finding the next step of the current step. For example, in the embodiments of this application, repeatedly executing the found steps can refer to executing the original message key field verification step. If an exception occurs, it returns failure and ends; if successful, it executes the user information query step. If an exception occurs, it executes the user number segment query step and ends; if successful, it assembles the user quota and ends.

[0115] Figure 4 This is a schematic diagram of the structure of the service processing apparatus provided in an embodiment of this application. Figure 4 As shown, the service processing device 40 includes: a receiving module 401, a first determining module 402, a second determining module 403, and an execution module 404. Wherein:

[0116] The receiving module 401 is used to receive the service processing information of the target service;

[0117] The first determining module 402 is used to determine the execution process information corresponding to the target business from the engine system based on the type of the target business represented by the business processing information. The execution process information is the business execution process information pre-stored in the engine system. The execution process information includes the following steps: message parsing, key field verification, user information query, user quota assembly, response message assembly, and billing bill generation.

[0118] The second determining module 403 is used to determine the target execution steps in the execution process information based on the key fields and user information in the business processing information;

[0119] Execution module 404 is used to execute the target business according to the target execution steps in the execution process information.

[0120] In this embodiment of the application, the second determining module 403 can also be used for:

[0121] Based on the key fields in the business processing information, perform key field validation in the execution process information to obtain the key field validation results;

[0122] Based on the user information in the business processing information, perform a user information query in the execution process information to obtain the information query results;

[0123] Based on the key field validation results and data query results, the target execution steps in the execution process information are determined.

[0124] In this embodiment of the application, the second determining module 403 can also be used for:

[0125] If the key field validation result indicates that the key field validation was successful and the data query result indicates that the query result was successful, then the message parsing, key field validation, user data query, user quota assembly, response message assembly, and billing bill generation are determined as the target execution steps.

[0126] If the key field validation result indicates that the key field validation was successful, and the data query result indicates that the query result failed, then the target execution steps are determined as message parsing, key field validation, user number segment query, user quota assembly, response message assembly, and billing bill generation.

[0127] In this embodiment of the application, the second determining module 403 can also be used for:

[0128] If the key field validation result indicates that the key field validation has failed, an exception message will be generated based on the key field validation result and displayed to the user.

[0129] In this embodiment of the application, the second determining module 403 can also be used for:

[0130] Determine the executed steps and the currently executing step in the execution process information;

[0131] Determine if the currently executing step is an end point step;

[0132] If the current execution step is the end point step, then the target execution step in the execution process information is determined based on the executed steps, the current execution step, the key fields in the business processing information, and the user information.

[0133] In this embodiment of the application, the second determining module 403 can also be used for:

[0134] If the current execution step is not the end point step, then execute the current execution step;

[0135] Based on the execution process information, determine the next execution step for the current execution step;

[0136] Execute the next execution step until the next execution step is the end point step. Based on the executed steps, the current execution step, the next execution step, the key fields in the business processing information, and the user information, determine the target execution step in the execution process information.

[0137] In this embodiment of the application, the execution module 404 can also be used for:

[0138] Obtain the call detail records (CDRs) for the target service.

[0139] Store the call detail records (CDRs) and send them to the billing system for display.

[0140] As can be seen from the above, the service processing device in this embodiment comprises a receiving module 401 for receiving service processing information of the target service; a first determining module 402 for determining execution flow information corresponding to the target service from the engine system based on the type of the target service represented by the service processing information, wherein the execution flow information is information of the service execution flow pre-stored in the engine system, and the execution flow information includes the steps of: message parsing, key field verification, user information query, user quota assembly, response message assembly, and billing bill generation; a second determining module 403 for determining the target execution steps in the execution flow information based on the key fields and user information in the service processing information; and an execution module 404 for executing the target service according to the target execution steps in the execution flow information. Therefore, this application embodiment can determine the execution process information corresponding to the target business in the process engine according to the type of the target business, and can determine the target execution steps in the configuration business execution process information. Since the steps are determined according to the target business, and the target execution steps in the execution process information are determined according to the key fields and user information in the business processing information, the steps corresponding to the target business can be obtained. Therefore, the execution of steps and the execution order of steps can be selected according to business needs. Since it is not necessary to follow a fixed business processing process, time and resources can be saved, thereby improving the efficiency of business processing and achieving the effect of meeting the business complexity and current business processing needs in specific business processing scenarios.

[0141] Figure 5 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Figure 5 As shown, the electronic device 50 includes:

[0142] The electronic device 50 may include a processor 501 with one or more processing cores, a memory 502 with one or more computer-readable storage media, a communication component 503, and other components. The processor 501, memory 502, and communication component 503 are connected via a bus 504.

[0143] In the specific implementation process, at least one processor 501 executes computer execution instructions stored in memory 502, causing at least one processor 501 to perform the above-mentioned business processing method.

[0144] The specific implementation process of processor 501 can be found in the above method embodiments, and its implementation principle and technical effect are similar. It will not be repeated here.

[0145] In the above Figure 5 In the illustrated embodiments, it should be understood that the processor can be a Central Processing Unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), etc. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the method disclosed in this invention can be directly implemented by a hardware processor, or implemented by a combination of hardware and software modules within the processor.

[0146] The memory may include random access memory (RAM) and may also include non-volatile memory (NVM), such as at least one disk storage device.

[0147] The bus can be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus, etc. Buses can be categorized as address buses, data buses, control buses, etc. For ease of illustration, the buses shown in the accompanying drawings are not limited to a single bus or a single type of bus.

[0148] In some embodiments, a computer program product is also provided, including a computer program or instructions that, when executed by a processor, implement the steps in any of the above-described business processing methods.

[0149] For details on the implementation of each of the above operations, please refer to the previous examples, which will not be repeated here.

[0150] Those skilled in the art will understand that all or part of the steps in the various methods of the above embodiments can be performed by instructions, or by instructions controlling related hardware. These instructions can be stored in a computer-readable storage medium and loaded and executed by a processor.

[0151] Therefore, embodiments of this application provide a computer-readable storage medium storing a plurality of instructions that can be loaded by a processor to execute steps in any of the business processing methods provided in embodiments of this application.

[0152] The storage medium may include: read-only memory (ROM), random access memory (RAM), disk or optical disk, etc.

[0153] According to one aspect of this application, a computer program product or computer program is provided, the computer program product or computer program including computer instructions stored in a computer-readable storage medium.

[0154] Since the instructions stored in the storage medium can execute the steps of any of the business processing methods provided in the embodiments of this application, the beneficial effects that any of the business processing methods provided in the embodiments of this application can achieve can be realized. For details, please refer to the previous embodiments, which will not be repeated here.

[0155] Other embodiments of this application will readily occur to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of this application that follow the general principles of this application and include common knowledge or customary techniques in the art not disclosed herein. The specification and examples are to be considered exemplary only, and the true scope and spirit of this application are indicated by the following claims.

[0156] It should be understood that this application is not limited to the precise structure described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of this application is limited only by the appended claims.

Claims

1. A business processing method, characterized in that, The method includes: Receive business processing information for the target service; Based on the type of the target service characterized by the business processing information, the execution process information corresponding to the target service is determined from the engine system. The execution process information is business execution process information pre-stored in the engine system, and the execution process information includes the following steps: message parsing, key field verification, user information query, user quota assembly, response message assembly, and billing bill generation. Based on the key fields and user information in the business processing information, determine the target execution steps in the execution process information; Execute the target business according to the target execution steps in the execution process information; The step of determining the target execution steps in the execution flow information based on the key fields and user information in the business processing information includes: Based on the key fields in the business processing information, perform key field validation in the execution process information to obtain the key field validation result; Based on the user information in the business processing information, perform the user information query in the execution process information to obtain the information query results; If the key field verification result indicates that the key field verification is successful and the data query result indicates that the query result is successful, then the message parsing, the key field verification, the user data query, the user quota assembly, the response message assembly, and the billing bill generation are determined as the target execution steps. If the key field verification result indicates that the key field verification was successful and the data query result indicates that the query result failed, then the message parsing, the key field verification, the user number segment query, the user quota assembly, the response message assembly, and the billing bill generation are determined as the target execution steps.

2. The method according to claim 1, characterized in that, The method further includes: If the key field validation result indicates that the key field validation has failed, an exception message is generated based on the key field validation result and displayed to the user.

3. The method according to claim 1, characterized in that, The method further includes: Determine the executed steps and the currently executed step in the execution process information; Determine whether the currently executing step is an end point step; If the current execution step is an end point step, then the target execution step in the execution process information is determined based on the executed steps, the current execution step, the key fields in the business processing information, and the user information.

4. The method according to claim 3, characterized in that, After determining whether the currently executed step is an end point step, the method further includes: If the current execution step is not an end point step, then the current execution step is executed; Based on the execution flow information, determine the next execution step of the current execution step; The next execution step is executed until it becomes the end point step. Based on the executed steps, the current execution step, the next execution step, the key fields in the business processing information, and the user information, the target execution step in the execution process information is determined.

5. The method according to claim 1, characterized in that, After executing the target business according to the target execution step in the execution flow information, the method further includes: Obtain the call detail records (CDRs) for the target service being executed; The call detail records (CDRs) are stored and sent to the billing system for display.

6. A business processing apparatus, characterized in that, include: The receiving module is used to receive the business processing information of the target business. The first determining module is used to determine the execution process information corresponding to the target service from the engine system based on the type of the target service characterized by the business processing information. The execution process information is business execution process information pre-stored in the engine system, and the execution process information includes the following steps: message parsing, key field verification, user information query, user quota assembly, response message assembly, and billing bill generation. The second determining module is used to determine the target execution steps in the execution process information based on the key fields and user information in the business processing information. The execution module is used to execute the target business according to the target execution steps in the execution process information; The second determining module is specifically used for: Based on the key fields in the business processing information, perform key field validation in the execution process information to obtain the key field validation result; Based on the user information in the business processing information, perform the user information query in the execution process information to obtain the information query results; If the key field verification result indicates that the key field verification is successful and the data query result indicates that the query result is successful, then the message parsing, the key field verification, the user data query, the user quota assembly, the response message assembly, and the billing bill generation are determined as the target execution steps. If the key field verification result indicates that the key field verification was successful and the data query result indicates that the query result failed, then the message parsing, the key field verification, the user number segment query, the user quota assembly, the response message assembly, and the billing bill generation are determined as the target execution steps.

7. An electronic device, comprising: A processor, and a memory communicatively connected to the processor; The memory stores computer-executed instructions; The processor executes computer execution instructions stored in the memory to implement the method as described in any one of claims 1 to 5.

8. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer-executable instructions, which, when executed by a processor, are used to implement the method as described in any one of claims 1 to 5.

Images